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

dist-upgrade v4.1.0 (r4.1) #3954

Closed
qubesos-bot opened this issue Aug 14, 2023 · 2 comments
Closed

dist-upgrade v4.1.0 (r4.1) #3954

qubesos-bot opened this issue Aug 14, 2023 · 2 comments

Comments

@qubesos-bot
Copy link

Update of dist-upgrade to v4.1.0 for Qubes r4.1, see comments below for details.

Built from: QubesOS/qubes-dist-upgrade@e7326a7

Changes since previous version:
QubesOS/qubes-dist-upgrade@e7326a7 version 4.1.0
QubesOS/qubes-dist-upgrade@521b0ae Merge remote-tracking branch 'origin/pr/11'
QubesOS/qubes-dist-upgrade@6600304 Review comments: fix some policy file names
QubesOS/qubes-dist-upgrade@34ccbf3 Make dom0 snapshot before upgrade
QubesOS/qubes-dist-upgrade@985fe78 Another attempt to make debian stop complaining
QubesOS/qubes-dist-upgrade@dca6cb3 Fix kernel name
QubesOS/qubes-dist-upgrade@01197e7 Check if policy files exist
QubesOS/qubes-dist-upgrade@6c90a60 Merge branch 'release4.0'
QubesOS/qubes-dist-upgrade@067fa98 Order options like they appear in help
QubesOS/qubes-dist-upgrade@46e60fa Fix file paths and options
QubesOS/qubes-dist-upgrade@11955a4 First draft of 4.2 update
QubesOS/qubes-dist-upgrade@483da7b Drop TravisCI and add GitlabCI

Referenced issues:
QubesOS/qubes-issues#7832

If you're release manager, you can issue GPG-inline signed command:

  • Upload dist-upgrade e7326a7ef9ae733b0654e6356d0289c3cd4dc388 r4.1 current repo (available 7 days from now)
  • Upload dist-upgrade e7326a7ef9ae733b0654e6356d0289c3cd4dc388 r4.1 current (dists) repo, you can choose subset of distributions, like vm-fc24 vm-fc25 (available 7 days from now)
  • Upload dist-upgrade e7326a7ef9ae733b0654e6356d0289c3cd4dc388 r4.1 security-testing repo

Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).

@qubesos-bot
Copy link
Author

Package for dom0 was built (build log) and uploaded to current-testing repository

@marmarek
Copy link
Member

Superseded by #3955

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants