-
Notifications
You must be signed in to change notification settings - Fork 32
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
fix(integrity): expect pkg mgmt files #488
Conversation
434e951
to
94c444b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, sorry for missing that
Missed that, too, as i was looking for exclude lists, not allow lists. Even visited this repo :-/ |
Signed-off-by: Arthur Schiwon <[email protected]>
94c444b
to
7c58e2a
Compare
/backport to stable27 |
The backport to stable27 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable27
git pull origin stable27
# Create the new backport branch
git checkout -b fix/foo-stable27
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
These files also now exist in the v25.0.11 release artifact. Was that intentional? It appears to be causing issues like nextcloud/server#40456 since the updater in v25 doesn't have this awareness. |
upgading to 27.1.0 RC3 failes because these files are included intentionally
building the phar files for me thoughmanaged to