Hi Sanad, thanks for reporting this. The fix has been backported to
jammy in version `2.20.11-0ubuntu82.8`. Could you confirm if this fixed
the issue?
Thanks again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Nice catch, I didn't realize the `-` was replaced with `_`. Apart from
that I got a handful of test failures related to coreutils (a couple
more than the ones you mentioned). I only replaced assertions to refer
to `coreutils-from-gnu` instead of `coreutils` to get tests to pass and
came up with the
Public bug reported:
Apport 2.32.0-0ubuntu5 FTBFS on questing due to an error in a custom
setuptools command:
```
error: error in setup.cfg: command 'build_java' has no such option
'minimum-java-release'
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1:
/usr/bin/python3
Public bug reported:
`python-virtualenv` ftbfs on noble due to an (outdated?) build
dependency which is unsatisfiable. This is the output I get on a clean
noble VM:
```
$ apt source python-virtualenv; cd python-virtualenv-20.25.0+ds; debuild
Reading package lists... Done
NOTICE: 'python-virtualen
Public bug reported:
During compilation of unit tests the following error arised:
```
cd /<>/obj-x86_64-linux-gnu/test/unittest && /usr/bin/c++
-I/<>/include -isystem /usr/src/gtest/include -isystem
/usr/src/gtest -g -O3 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/
