https://launchpad.net/ubuntu/+source/sbuild/0.88.3ubuntu3 is there now and started building - that is the ahrd pre-dep for an SRU.
Looking at SRUs ... Setting plucky version to 0.88.3ubuntu2.1 for an SRU => All else was fine - sponsoring for Plucky Oracular for the same rules needs to be 0.85.10ubuntu1.1 the former one should have been 0.1 but anyway - let us continue correctly from ubuntu1 to ubuntu1.1 (see https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/VersionStrings.md if you ever struggle, I tried to put all conditions in one place) It also missed to run update-maintainer => Both fixed up and sponsored for oracular Noble also missed update-maintainer Fixed and sponsored after double checking debdiff again => sponsored into Noble SRU unapproved queue -- You received this bug notification because you are a member of Debcrafters packages, which is subscribed to sbuild in Ubuntu. https://bugs.launchpad.net/bugs/2109853 Title: [SRU] Make sbuild usable for '[email protected]' users Status in sbuild package in Ubuntu: Fix Committed Status in sbuild source package in Noble: In Progress Status in sbuild source package in Oracular: In Progress Status in sbuild source package in Plucky: In Progress Bug description: [Impact] With the increasing adoption of tools like authd, it's very likely that Linux desktop users in corporate environments end up with their usernames like '[email protected]', what doesn't play nice with sbuild/schroot. Without properly escaping the username, the '@' character ends up being interpreted as a string interpolation what breaks the lock_chroot() subroutine. Fore more information about the issue, please check the upstream bug: https://salsa.debian.org/debian/sbuild/-/issues/4 [ Test plan ] 1. Make sure to have a user account containing the '@' character in its name, such as '[email protected]'. 2. Make sure to have a schroot environment ready. `mk-sbuild oracular` for example to create one for oracular. Note: the mk-sbuild command is provided by the ubuntu-dev-tools package, so make sure to have it installed. 3. Retrieve the sources of a simple package: `pull-lp-source hello noble` 4. Build the binary package with sbuild: `cd hello-2.10/ && sbuild -d noble-amd64` (adjust the schroot environment name according to your computer's architecture) Expected results without the patches herein proposed is a failure like: ``` I: NOTICE: Log filtering will replace 'var/run/schroot/mount/plucky-amd64-c9a17ed0-5932-4df1-ad6e-d4df512a37b0' with '<<CHROOT>>' Possible unintended interpolation of @org in string at -e line 50. Global symbol "@org" requires explicit package name (did you forget to declare "my @org"?) at -e line 50. Execution of -e aborted due to compilation errors. E: Error locking chroot session: skipping livecd-rootfs ``` Building the package should proceed normally with the patches applied. [ Where problems could occur ] The scope of the changes herein proposed is so small and self-contained that I don't expect any issues arising from it under any circumstances. [ Other Info ] I'm skipping 'Questing', as I expect it to receive the fix via debian merges, sbuild version 0.89.2 (just accepted into Debian unstable) contains this patch (alongside other stuff). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/2109853/+subscriptions -- Mailing list: https://launchpad.net/~debcrafters-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~debcrafters-packages More help : https://help.launchpad.net/ListHelp
