A user just claimed that the new kernel packages allow themselves to install on
systems that don't have new enough libc6. Shouldn't there be libc6>=2.33
dependency in the .deb so that it won't allow itself to install?
https://github.com/bkw777/mainline/issues/87#issuecomment-831777690
** Bug
Indeed, why does it? There are files under /usr/local/lib/python2.7 and
3.7, probably the result of pip and pip3?, but so what? Why isn't
anything else broken by their existense?
I don't see any python-related variables in my env exept:
PYTHONPYCACHEPREFIX=/var/cache/python
"python" resolves to:
Public bug reported:
bkw@negre:~$ apt info krop
Package: krop
Version: 0.5.1+ds-1
Priority: optional
Section: universe/utils
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Alexandre Mestiashvili
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 148 kB
Depends:
*** This bug is a duplicate of bug 1597840 ***
https://bugs.launchpad.net/bugs/1597840
** Tags added: disco eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793582
Title:
package
** Tags added: disco eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597840
Title:
package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade:
trying to overwrite
Correction to that date I write above: 2019 02 06 not 2019 02 26 blargh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To
... Ah I see, it does look like possibly the debian upstream might have
fixed it, and merely the ubuntu package has not yet got it. Which is
what this bug declares at the top, so no discrepency there after all.
They mention signed images, where in my own case I have uefi boot
security disabled
On 19.04 I still get my grub.cfg broken by normal updates. Not by kernel
updates, and not by running update-grub. But there is some package that
whenever that package is updated, part of the update process generates a
new grub.cfg, and it's a broken one because it makes a bad assumption
somewhere.
** Also affects: muon (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: muon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685376
Title:
Synaptic rebuilds search
Wow still present in 19.04
bkw@negre:~$ axi-cache
No module named 'ConfigParser': only help functions are implemented, for the
sake of help2man
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612948
10 matches
Mail list logo
