Merged upstream (=debian), needs a release name bump for questing but otherwise
all of these look correct.
And they are more and more needed the more people bump into that using a laptop
deployment making their user be [email protected] :-)
I'm not merging 0.89.2 as I'm no subject matter expert and the list
0.88.3->0.89.2 is many pages long.
But this fix as proposed make sense to be applied immediately.
While testing if this would build fine (or fall victim to massive perl
changes) I was testing the very change already applying it manually on
my noble system. Got it to work well - sbuild builds the pkg just fine
now!
Double checked debdiff as git-ubuntu was down made me use some detours, all
good.
Sponsoring for questing
** Changed in: sbuild (Ubuntu)
Status: In Progress => Fix Committed
--
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
