-
Notifications
You must be signed in to change notification settings - Fork 0
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
tunnel v1.4.5 (r4.1) #54
Comments
Package for fc34 was built (build log) and uploaded to current-testing repository |
Package for fc35 was built (build log) and uploaded to current-testing repository |
Package for centos-stream8 was built (build log) and uploaded to current-testing repository |
Package for bullseye was built (build log) and uploaded to current-testing repository |
Package for buster was built (build log) and uploaded to current-testing repository |
Package for fc36 was built (build log) and uploaded to current-testing repository |
Package for centos-stream8 was uploaded to stable repository |
Package for fc34 was uploaded to stable repository |
Package for bullseye was uploaded to stable repository |
Package for fc35 was uploaded to stable repository |
Package for buster was uploaded to stable repository |
@fepitre I don't know if this is the right place to ask or even how the build processes for the Qubes contrib repository work in detail, but I have noticed that no version of qubes-tunnel has ever been marked as stable for fc36. Is this something that needs to be done manually? Does it indicate that it is not as stable as on other platforms (for fc35, it has been uploaded almost five months ago)? Come to think of it, almost no package is available in fc36 stable (https://contrib.qubes-os.org/yum/r4.1/current/vm/fc36/rpm/ just contains qubes-split-browser). |
All of this is manual operations indeed. It means I need to go through all components to trigger build and I've just been elsewhere. |
-----BEGIN PGP SIGNED MESSAGE----- Upload tunnel 6ab467044d17ce58bb4966c6a65a2af5c96e6884 r4.1 current repo iQIzBAEBCAAdFiEEn6ZLkvlecGvyjiymSEAQtc3FduIFAmOCQTwACgkQSEAQtc3F |
Package for centos-stream8 was uploaded to stable repository |
Package for fc37 was built (build log) and uploaded to current-testing repository |
Package for bullseye was uploaded to stable repository |
Package for buster was uploaded to stable repository |
Package for fc35 was uploaded to stable repository |
Package for fc36 was uploaded to stable repository |
-----BEGIN PGP SIGNED MESSAGE----- Upload tunnel 6ab467044d17ce58bb4966c6a65a2af5c96e6884 r4.1 current vm-fc37 repo iQIzBAEBCAAdFiEEn6ZLkvlecGvyjiymSEAQtc3FduIFAmRs1KMACgkQSEAQtc3F |
Package for fc37 was uploaded to stable repository |
Package for fc38 was built (build log) and uploaded to current-testing repository |
Update of tunnel to v1.4.5 for Qubes r4.1, see comments below for details.
Built from: QubesOS-contrib/qubes-tunnel@6ab4670
Changes since previous version:
QubesOS-contrib/qubes-tunnel@6ab4670 version 1.4.5
QubesOS-contrib/qubes-tunnel@3b39c74 Ensure notify-send is available
Referenced issues:
QubesOS/qubes-issues#889
If you're release manager, you can issue GPG-inline signed command:
Upload tunnel 6ab467044d17ce58bb4966c6a65a2af5c96e6884 r4.1 current repo
(available 7 days from now)Upload tunnel 6ab467044d17ce58bb4966c6a65a2af5c96e6884 r4.1 current (dists) repo
, you can choose subset of distributions, likevm-fc24 vm-fc25
(available 7 days from now)Upload tunnel 6ab467044d17ce58bb4966c6a65a2af5c96e6884 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).
The text was updated successfully, but these errors were encountered: