There is downstream software depending on python3-packaging to work
correctly. That library is affected, too, because it checks for strict
compliance to PEP 440. And, obviously, it can't be fixed by fixing the
packaging library, as it does its work correctly.
Example downstream usage: https://gith
> Setuptools is not in bionic
I don't understand. I clearly see it there:
https://webcache.googleusercontent.com/search?q=cache:fZGhFT_sSb8J:https://packages.ubuntu.com/bionic/python-
setuptools . Or am I missing something?
--
You received this bug notification because you are a member of Ubuntu
> We ship setuptools in Ubuntu, and the version of setuptools shipped
in these releases does not trigger the issue.
It does for me (on Bionic).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs
Ah, now I get it, thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606
Title:
Invalid PEP440 package version breaking setuptools >= 60
Status in devscript
> Changed in python-debian (Ubuntu Bionic):
> status: New → Invalid
Can I ask about this change? How is it invalid for bionic? The name of
the package is wrong there, too... (for both python-distro-info an
python3-distro-info).
--
You received this bug notification because you are a membe
I successfully work around this issue by the steps described at
https://askubuntu.com/a/907249/153828 :
Disable and stop the systemd-resolved service:
sudo systemctl disable systemd-resolved.service
sudo systemctl stop systemd-resolved
Then put the following line in the [main] section of your
/e
Reinstall doesn't help.
The problematic line is in postinst:
[ -x /bin/systemctl ] && [ -d /run/systemd/system ] && systemctl enable
pcscd.socket
On my Trusty system, even calling this command from commandline (with
sudo at systemctl) fails with the same error.
Using strace I found out that on
So, has anyone found out if this is an ibus bug or Gnome bug? How could
we proceed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1276186
Title:
System becomes unresponsive,
Requested the update for Trusty:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1563305 . Please,
click "This bug also affects me" in that bugreport, so that we get some
weigh on the need for the update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Based on the number of "+1 for Trusty"s in
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1512956 , I change
the status to Confirmed.
** Changed in: ibus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
This is a copy of (
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1512956 ) for
Trusty:
newest release of Intellj IDEA does shows a warning:
"IBus prior to 1.5.11 may cause input problems."
that's why i request for an update of ibus to that version.
Version 1.5.5 dist
Trusty would also need this update. I'm not sure if the SRU requirement
is specifically meant as a precondition for Trusty, or for all non-beta
releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://
I confirm this on current 14.04 LTS release.
However, I no longer have problems regarding bug #1256419, so it seems
the printers.py file syntax has already been updated in upstream.
So just commenting out the two lines Simon Suggests solves the issue for
me (however, I'm not doing any multiarch r
13 matches
Mail list logo
