Re: [Emc-developers] 2.9.2
Github CI is failing with: E: Failed to fetch http://deb.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.1.0-14-rt-amd64_6.1.64-1_amd64.deb 403 Access denied - broken package [IP: 199.232.30.132 80] E: Failed to fetch http://deb.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-rt-amd64_6.1.64-1_amd64.deb 403 Access denied - broken package [IP: 199.232.30.132 80] Is that a problem in our CI YAML or with the Debian server? -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] 2.9.2
On Sun, 10 Dec 2023 at 10:36, Steffen Möller via Emc-developers wrote: > Please allow me to fix the double-installation of that one manual page prior > to the release. I think it's a double-installation of all of the man3 folder? I was expecting to fix that myself, but I am more than happy for someone else to do it who is more likely to know how. > Concerning the tag and ensuring that you exactly know what you are tagging, > does it help that you can specify the commit that you want to tag? Not really, the issue is with what prompts the buildbot to build a set of release debs into http://buildbot.linuxcnc.org/release/ (and the equivalent for buildbot2, which does not actually seem to be responding right now) -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] 2.9.2
Am 10.12.23 um 01:18 schrieb andy pugh: There are a number of important bug fixes waiting for release (including that I broke run-from-line in Axis. Oops). I plan to make a 2.9.2 release in the next few days. This is largely predicated on me figuring out how to fix the Bullseye builds, which looks to be just putting the newer po4a where the Bullseye buildbot can find it. I am hoping not to have to hand-build all the debs again, like I did for the 2.9.1 release. Why did I have to do that? Because between me creating the tag and pushing it, there was a commit made. Well. maybe my fault, I could have done a --dry-run, but that still leaves a window of opportunity for a commit to break the process. This was nobody's fault, but it meant that the tag got pushed, but not the commit (or vice-versa) and the buildbot didn't make the debs. The build notes at http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ReleaseCheckList do say: "Ideally make it so no one will commit to the release branch while you're working, but I'm not sure how to do this." So, two requests: 1) Tell me now if there is anything that you are working on that you want to see in 2.9.2 This one please: https://github.com/LinuxCNC/linuxcnc/pull/2772 2) From now until I say otherwise, please check this mailing list for a post entitled "2.9 frozen until further notice" ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] 2.9.2
> Gesendet: Sonntag, 10. Dezember 2023 um 01:18 Uhr > Von: "andy pugh" > An: "EMC developers" > Betreff: [Emc-developers] 2.9.2 ... > I am hoping not to have to hand-build all the debs again, like I did > for the 2.9.1 release. > > Why did I have to do that? Because between me creating the tag and > pushing it, there was a commit made. Well. maybe my fault, I could > have done a --dry-run, but that still leaves a window of opportunity > for a commit to break the process. Please allow me to fix the double-installation of that one manual page prior to the release. Once that is fixed i would like to add the installation of all our .debs as part of the CI - anything placed redundantly in separate packages should then show up as a conflict. Concerning the tag and ensuring that you exactly know what you are tagging, does it help that you can specify the commit that you want to tag? NAME git-tag - Create, list, delete or verify a tag object signed with GPG SYNOPSIS git tag [-a | -s | -u ] [-f] [-m | -F ] [-e] [ | ] git tag -d ... git tag [-n[]] -l [--contains ] [--no-contains ] [--points-at ] [--column[=] | --no-column] [--create-reflog] [--sort=] [--format=] [--merged ] [--no-merged ] [...] git tag -v [--format=] ... Best, Steffen ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
