Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][MIG] report_py3o_fusion_server #696

Merged
merged 31 commits into from
Nov 7, 2023

Conversation

alexis-via
Copy link
Contributor

Requires report_py3o that I migrated in v16 in this PR: #695

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 16, 2023
@github-actions github-actions bot closed this May 21, 2023
@alexis-via alexis-via reopened this Jun 2, 2023
@github-actions github-actions bot closed this Jul 9, 2023
@alexis-via alexis-via reopened this Oct 23, 2023
@alexis-via alexis-via added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Oct 23, 2023
@alexis-via alexis-via force-pushed the 16-mig-report_py3o_fusion_server branch from e17cbc4 to ad97bed Compare October 23, 2023 09:53
hbrunn and others added 21 commits November 2, 2023 22:56
use libreoffice for conversions in the base version. Fixes OCA#179
…bility of py3o report

Before this change it was not possible to install modules declaring py3o report into a non native format without specifying a Fusion server once the module py3o_report_fusion_server was installed. With theses changes, we now take care of the availability of the libreoffice runtime to display/log a warning message when the report is in a non native runtime.
Co-Authored-By: lmignon <laurent.mignon@acsone.eu>
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: reporting-engine-12.0/reporting-engine-12.0-report_py3o_fusion_server
Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-12-0/reporting-engine-12-0-report_py3o_fusion_server/
* Update README for report_py3o and report_py3o_fusion_server

Convert README to the new readme subdirectory
(without these a CacheMiss error is thrown by odoo)
@alexis-via alexis-via force-pushed the 16-mig-report_py3o_fusion_server branch from ad97bed to 6d7a023 Compare November 2, 2023 21:58
Migration of report_py3o_fusion_server from v14 to v16
@alexis-via alexis-via force-pushed the 16-mig-report_py3o_fusion_server branch from 6d7a023 to b1ab01e Compare November 2, 2023 22:24
@HviorForgeFlow
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 16.0-ocabot-merge-pr-696-by-HviorForgeFlow-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit c17c303 into OCA:16.0 Nov 7, 2023
5 of 6 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 5bc5792. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved merged 🎉 no stale Use this label to prevent the automated stale action from closing this PR/Issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.