+1 Maintenance Report
I was on +1 maintenance last week and worked on the following:
nanopolish: this package had a chain of broken dependencies,
nanopolish -> libslow5lib -> libstreamvbyte. libstreamvbyte states
that it only works on little endian architectures, so I investigated
working around this dependency, and after realizing it was not
possible I uploaded new versions of these packages to disable building
on s390x.
varnish: This package suffered from an FTBFS. I have uploaded a new
version and submitted the fix upstream. I worked on this package
because it blocked quite a few others, but they still may need some
test retriggers.
python3-defaults: Lots of investigation into which sets of triggers
would get certain packages to no longer be blocking python3-defaults.
I managed to get the regressions list down quite a bit.
The one thing that I really got stuck on this week was xpra. It is
FTBFS on arm{hf,64}, but I have been completely unable to recreate the
failure locally. I have tried many different configurations and PPA
uploads to try to resolve the problem, but have come up short. Whoever
is on +1 maintenance next week, if you figure out what's wrong with
this package please let me know :).
Also while working +1 maintenance I was using mclemenceau's
visual-excuses snap and thought it would benefit from adding a `--age`
flag to only show packages that were stuck in proposed for a certain
number of days. I have opened a PR to add this.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 Maintenance Report
This week I was on +1 maintenance and I decided to work on the large amount of NBS packages [1] caused by the ffmpeg 5 transition. xmms2: This was being affected by the "successful builds but Launchpad still says the build failed" issue. After enough retries I got it migrated. telegram-desktop: I believe this is being affected by Launchpad build flakiness as well. I have retried the build a few times and I always get a different error message. It builds fine for me in a local sbuild. octave-video: I updated the code to work with the ffmpeg5 libraries and forwarded the fix to Debian. unpaper: I worked on packaging new upstream version 7, but then realized it was already uploaded to Debian but had been stuck in the delayed queue. Dbungert had mentioned this in his +1 maintenance report but I didn't make the connection when looking at the NBS report. This has now successfully synced to Ubuntu. olive-editor: There is a new upstream version that is compatible with ffmpeg 5. In order to package this new upstream version, a new version of opencolorio must also be packaged. I have done this, uploaded it to Ubuntu, and forwarded to Debian. I also needed to resolve the FTBFS issues for the versions of opencv and openimageio in -proposed to get olive-editor building. I have gotten opencv to build, and will upload openimageio after opencolorio has finished building so it will build against the new opencolorio v2. I have packaged the new version of olive-editor in a PPA [2], but there is still a linker error preventing it from building. If the next person on +1 maintenance would like to look at this I can sponsor, otherwise I will try to find some time to look at it. A community member also requested that I look into hugo not migrating. This just required a sync of golang-github-aws-aws-sdk-go from Debian. Thank you, William [1]: https://people.canonical.com/~ubuntu-archive/nbs.html [2]: https://launchpad.net/~jawn-smith/+archive/ubuntu/devel-proposed/+packages -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 Maintenance Report
Steve, Thank you for your work on this. I apologize for the lack of detail in my earlier email. In order to get g-g-j-pgtype to build in my PPA with g-g-j-pgx version 3.x, I had to change a line in d/control. I changed the dependency "golang-github-jackc-pgx-v4-dev" to "golang-github-jackc-pgx-dev" which is the name of the binary package from version 3.x. It then built successfully in a PPA: https://launchpad.net/~jawn-smith/+archive/ubuntu/devel-proposed/+packages So I may have misunderstood Bryce's instructions. I was under the impression I could: 1. Build the modified pgtype package with the dependency change (and some version number like 1.10.0-0ubuntu1) 2. Build the pgx package now that the pgtype package is no longer in NEW 3. Re-sync the pgtype package from Debian and have it build with the now available pgx-v4 package Is this not correct? If this is correct can you please delete the pgtype package again so I can upload the modified version? William On Fri, Jul 1, 2022 at 1:32 PM Steve Langasek wrote: > On Fri, Jul 01, 2022 at 11:28:25AM -0700, Steve Langasek wrote: > > > So, I think the bootstrap solution might be: > > > > 1. Verify that g-g-j-pgtype (1.10.0-3) actually does build > > > successfully against g-g-j-pgx-dev (3.6.2-2). (This is probably > > > best to verify in a PPA.) If so, then... > > > > 2. Request an Archive Admin to delete from -proposed: > > > - golang-github-jackc-pgtype (1.10.0-4) source & binary > > > - golang-github-jackc-pgx (4.15.0-4) source & binary > > > > 3. Prepare and upload g-g-j-pgtype (1.10.0-3), and verify it > > > builds ok. Then proceed with syncpackage on both packages to pull > > > in the newer versions. > > > Of course, when an in-archive bootstrap is possible, this is always > nicer! > > > Since William has already confirmed that the above works, I'm not waiting > > for him to ask on Monday and have done the above. > > However, it doesn't appear to have worked in the archive. > > https://launchpad.net/ubuntu/+source/golang-github-jackc-pgtype/1.10.0-3/+build/24130112 > shows the package is dep-wait on golang-github-jackc-pgx-v4-dev, from the > newer golang-github-jackc-pgx that we're trying to bootstrap. > > So I'll hand this back over to y'all to debug and tell me what's missing :) > > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer https://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 Maintenance Report
Bryce, Thanks for replying here and in IRC. it does appear g-g-j-pgtype does successfully build with g-g-j-pgx 3.6.2-2. I'm about to EOW but will contact an AA next week about the next steps. Thanks again! William On Fri, Jul 1, 2022 at 12:08 PM Bryce Harrington < bryce.harring...@canonical.com> wrote: > On Fri, Jul 01, 2022 at 11:34:13AM -0500, William Wilson wrote: > > Greetings ubuntu-devel, > > > > This week I was on +1 maintenance and I noticed an odd circular > dependency > > between two packages. > > > >- Package golang-github-jackc-pgtype is in NEW and is dependency wait > on > >golang-github-jackc-pgx-v4-dev. > >- Package golang-github-jackc-pgx-v4-dev is a new binary package to be > >built from src:golang-github-jackc-pgx as it migrates from major > version v3 > >to v4. > >- src:golang-github-jackc-pgx can not build any v4 binaries without > >golang-github-jackc-pgtype-dev, which is built from > >src:golang-github-jackc-pgtype > > > > > > The TL;DR of this is that src:golang-github-jackc-pgtype cannot build > > without binaries from src:golang-github-jackc-pgx, which cannot build > > without binaries from src:golang-github-jackc-pgtype, and thus there is a > > circular dependency. > > > > Are there any methods for dealing with this type of circular dependency? > In > > Debian I can see they did a binary-only upload to fix this, but as far > as I > > know there is no such thing in Ubuntu. > > Right, that's not generally an available option for us. The two > approaches I've had success with are a) bypassing test-during-build, and > b) bootstrapping from earlier versions. Towards the end of this page is > a section on handling circular dependencies that explain these two: > > > https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/ProposedMigration.md1 > > In this case, it doesn't look like the dependency is due to testing so > option (b) may be worth looking at. It appears that g-g-j-pgtype > used to depend on g-g-j-pgx-dev, at version 1.10.0-3, which is currently > available in kinetic. > > So, I think the bootstrap solution might be: > > 1. Verify that g-g-j-pgtype (1.10.0-3) actually does build > successfully against g-g-j-pgx-dev (3.6.2-2). (This is probably > best to verify in a PPA.) If so, then... > > 2. Request an Archive Admin to delete from -proposed: > - golang-github-jackc-pgtype (1.10.0-4) source & binary > - golang-github-jackc-pgx (4.15.0-4) source & binary > > 3. Prepare and upload g-g-j-pgtype (1.10.0-3), and verify it > builds ok. Then proceed with syncpackage on both packages to pull > in the newer versions. > > If step #1 does *not* work, then the problem is more complex. It might > be worth checking in with the Debian maintainer for ideas at that point. > > Bryce > > > I briefly thought about combining the packages, but that is not idea > > for a few reasons: > > > >1. It breaks our golang-github-- packaging convention. > >2. It would install possibly un-needed source code on people's > machines > >if they install the combined package but really only needed one. > > > > Now for the report of things I was able to solve: I usually focus mainly > on > > failed tests, but I noticed there were quite a few FTBFS packages, so I > > decided to focus on those. > > > > libdigidoc - openssl v3 related regression. This is fixed in Ubuntu and I > > have created a QA upload for Debian. This will be sponsored by ginggs. > > > > rinutils - filed https://launchpad.net/bugs/1980243 and > > https://bugs.debian.org/1014169 to explain that it needs new > dependencies > > packaged > > > > golang-github-masterminds-sprig - I fixed a regression in this package > > which unblocked: > > * golang-step-crypto > > * golang-step-cli-utils > > * golang-github-smallstep-certificates > > Thanks to seb128 for helping shepherd some of these binary packages > through > > the NEW queue > > > > golang-oras-oras-go - Fixed a regression in Ubuntu and forwarded to > Debian > > > > golang-mongodb-mongo-driver - Fixed a regression in Ubuntu (and forwarded > > to Debian) which unblocks: > > * golang-github-go-openapi-strfmt > > * golang-github-go-openapi-validate > > * golang-github-go-openapi-runtime > > > > golang-github-openshift-imagebuilder: Fixed regression in Ubuntu and > > forwarded to Debian > > > > scamper - Fixed a regression in Ubuntu and forwarded to Debian > > > > Thank you for reading, > > > > William 'jawn-smith' Wilson > > > -- > > ubuntu-devel mailing list > > ubuntu-devel@lists.ubuntu.com > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel > > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 Maintenance Report
Greetings ubuntu-devel, This week I was on +1 maintenance and I noticed an odd circular dependency between two packages. - Package golang-github-jackc-pgtype is in NEW and is dependency wait on golang-github-jackc-pgx-v4-dev. - Package golang-github-jackc-pgx-v4-dev is a new binary package to be built from src:golang-github-jackc-pgx as it migrates from major version v3 to v4. - src:golang-github-jackc-pgx can not build any v4 binaries without golang-github-jackc-pgtype-dev, which is built from src:golang-github-jackc-pgtype The TL;DR of this is that src:golang-github-jackc-pgtype cannot build without binaries from src:golang-github-jackc-pgx, which cannot build without binaries from src:golang-github-jackc-pgtype, and thus there is a circular dependency. Are there any methods for dealing with this type of circular dependency? In Debian I can see they did a binary-only upload to fix this, but as far as I know there is no such thing in Ubuntu. I briefly thought about combining the packages, but that is not idea for a few reasons: 1. It breaks our golang-github-- packaging convention. 2. It would install possibly un-needed source code on people's machines if they install the combined package but really only needed one. Now for the report of things I was able to solve: I usually focus mainly on failed tests, but I noticed there were quite a few FTBFS packages, so I decided to focus on those. libdigidoc - openssl v3 related regression. This is fixed in Ubuntu and I have created a QA upload for Debian. This will be sponsored by ginggs. rinutils - filed https://launchpad.net/bugs/1980243 and https://bugs.debian.org/1014169 to explain that it needs new dependencies packaged golang-github-masterminds-sprig - I fixed a regression in this package which unblocked: * golang-step-crypto * golang-step-cli-utils * golang-github-smallstep-certificates Thanks to seb128 for helping shepherd some of these binary packages through the NEW queue golang-oras-oras-go - Fixed a regression in Ubuntu and forwarded to Debian golang-mongodb-mongo-driver - Fixed a regression in Ubuntu (and forwarded to Debian) which unblocks: * golang-github-go-openapi-strfmt * golang-github-go-openapi-validate * golang-github-go-openapi-runtime golang-github-openshift-imagebuilder: Fixed regression in Ubuntu and forwarded to Debian scamper - Fixed a regression in Ubuntu and forwarded to Debian Thank you for reading, William 'jawn-smith' Wilson -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
PSA for those using encrypted filesystems on jammy
Hello all, If you are running an encrypted root filesystem on jammy, please be aware of an issue with cryptsetup and busybox not working well together. The issue stems from a recent cryptsetup upload that requires the busybox-initramfs to contain the dirname applet. See https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083 for more information. The best way to avoid this issue is to avoid upgrading cryptsetup until busybox can also be upgraded. Thank you, William 'jawn-smith' Wilson -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
