This does not even matter, Brian. The bug is invalid.
(a) autoreconf is provided by autoconf (and the name sort of implies that, it
re-runs autoconf)
(b) APT does not have any sort of alias database, it uses package provides
(c) It does not make sense to provide autoreconf from autoconf, as
Yes that's true IIRC. And update explicitly rebuilds the cache. That's
not a huge issue, unless you are sitting around running apt-get update
in loops.
It is not possible to rebuild only changed parts, except for
/var/lib/dpkg/status changes. For making that work, a second cache is
generated; we
Which version are you talking about? The mirror list is updated on the
upload. Utopic on 2014-10-24, and vivid on 2014-09-24.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
That does not make sense as an APT bug, not sure who's to blame here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1397740
Title:
Apt-get autoremove delete localized files
Should be fixed since some time. Try apt-get moo moo. Normal moo keeps
the classic cow.
** Changed in: apt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Seems like an unintended ABI break in APT.
** Package changed: python-apt (Ubuntu) = apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1385689
Title:
ubuntu-bug,
Can't read that, but it should not happen anymore, as packaging changed
a lot since then, if it even was python-apt's fault, which seems
unlikely.
** Changed in: python-apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Closing as invalid, there's nothing we can do here. It might just be a
broken cache file.
** Changed in: python-apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
Not sure what happened there, but it definitely should not happen
anymore.
** Changed in: python-apt (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
Reassigning to APT, that's APT function
** Package changed: python-apt (Ubuntu) = apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/842676
Title:
aptd crashed with
System seems broken it's segfaulting
** Changed in: python-apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1458148
Title:
As said, the servers are not in the server list exposed by launchpad.
** Changed in: python-apt (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
Seems like something else was broken if the postinst script segfaults.
** Changed in: python-apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
As there's nothing we can do about that without breaking other use
cases, we have to declare that working as intended.
Please clear your configuration before setting RootDir like options and
then re-init the config.
Sorry
** Changed in: python-apt (Ubuntu)
Status: Confirmed = Opinion
--
Closing, maverick is not supported anymore
** Changed in: python-apt (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/764384
** Package changed: python-apt (Ubuntu) = apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/984523
Title:
apt_pkg.Cache() E: Read error - read (21: is a directory)
** Package changed: python-apt (Ubuntu) = apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/992311
Title:
apt_pkg: E:The package lists or status file could not be
It's not in wily anymore, don't know about older releases, but if it's
not fixed in vivid yet, it will be fixed soon, as the build system
automatically updates the list.
** Changed in: python-apt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a
This should do the trick:
http://anonscm.debian.org/cgit/apt/python-
apt.git/commit/?id=165c3e534716c7f300a6419e2f0ccc331f63c0c9
** Changed in: python-apt (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Seems to be in 1.0.0~beta3
** Changed in: python-apt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1420279
Title:
Adding a
This bug was fixed in the package python-apt - 1.0.0~beta3
** Changed in: python-apt (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
** Changed in: python-apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1059975
Title:
KeyError in weak ref package cache
Python provides PyUnicode_EncodeLocale(), but that returns a new bytes
object. We can get a char* from that, but we'd not be able to delete the
bytes object anymore, as we don't know the life time of the char* and
our function only returns a char*
--
You received this bug notification because
We could fix it in that direction due to PyUnicode_DecodeLocale, but
there's nothing we can do for encoding Python strings to the system's
locale without a memory leak, so it does not make a lot of sense to
support only one direction.
--
You received this bug notification because you are a
Fix is already in Debian, will be in Ubuntu soon (today/tomorrow)
** Changed in: python-apt (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
For python-apt, that's a duplicate of bug 1445949. This has been fixed
in the 1.0 beta in Debian unstable.
Here's the function I used to translate the Debian version to the PEP440
(in most cases it works, there are some corner cases like ~ubuntu that
are not expressible):
Just looked at the apturl diff: The proposed fix does not handle
rebuilds. In my function, I opted to strip them away, and translate the
ubuntu part to a local label, that is 1.0ubuntu1 becomes 1.0+ubuntu1.
1.0ubuntu1build1 would be the same PEP440 version number, but that's
fine.
--
You
It would be great to have a function we could call during build to check
if the version number passes PEP440 and raise an exception otherwise.
And a translation for the ~ubuntu type of releases would be good to have
as well.
** Changed in: python-apt (Ubuntu)
Status: New = Fix Committed
Not sure what's happening, you might want to try rebuilding it, it's a
GPG failure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1451531
Title:
python-apt fails to
It's basically irrelevant, is it not? We only use the setup.py for
building, python-apt cannot be used by any of Python's package
installation tools.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
` is still confusing people. As it was
stated by Julian Andres Klode (juliank) in
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/565364/comments/8:
The pin value displayed after the version does not actually
correspond to the version, but is the pin value of the candidate
version
This bug is fixed in git's debian/experimental branch with a new policy
algorithm that assigns pins to versions. It will most likely not hit
Ubuntu 15.10, but I'm hopeful it will be included in 16.04.
** Changed in: apt (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug
APT does not support proxy auto-configuration, and never will, as this
requires a JavaScript engine, which is not a good idea to run as root
and depend on in a package with Priority: important.
But you should be able to write your own implementation by writing a
script and set
I'm marking this as fix released, as the bug is probably fixed in recent
APT versions. If this is still reproducible in wily, please reopen.
** Changed in: apt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I committed a fix for this upstream in the debian/experimental branch,
which will likely be part of Ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1332106
Title:
I committed a fix for this upstream in the debian/experimental branch,
which will likely be part of Ubuntu 16.04.
** Changed in: apt (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I'm marking this as fix released, as the bug is probably fixed in recent
APT versions. If this is still reproducible in wily, please reopen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
We will not add support for NTLM proxies in APT.
** Changed in: apt (Ubuntu)
Status: Confirmed = Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/137418
Title:
If I judge cjwatson's message correctly, this seems to be fixed:
Ah, this fix is sufficient:
apt (0.8.16~exp6) experimental; urgency=low
[ Christopher Baines ]
* enable APT in unpack/configure ordering to handle loops as well
as tight dependencies between immediate packages
Marking as fixed, as bug 957231 is marked fixed.
** Changed in: apt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/854090
Fix committed upstream in debian/experimental. Expect that to hit Ubuntu
16.04.
** Changed in: apt (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
This is your opinion. These example files exist to demonstrate defaults
and/or specific features such as multiple components. Therefore we do
not want to change it.
** Changed in: apt (Ubuntu)
Status: Confirmed = Opinion
--
You received this bug notification because you are a member of
I'm marking this as opinion. We already provide -V which outputs one
package per line, so we do not really need the 2 spaces outputting.
** Changed in: apt (Ubuntu)
Status: Confirmed = Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
We're not going to do that precisely because the launchpad changelog is
HTML.
** Changed in: apt (Ubuntu)
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Closing this, since this seems to be a broken cache file.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/843316
Closing this bug, we believe it's fixed in recent APT version.
** Changed in: apt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Closing this, since this seems to be a broken cache file.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/842676
Title:
We believe that this bug is caused by an invalid cache file, broken
hardware, or that it is fixed in recent APT versions, and I am thus
closing the bug, so we can focus on others.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you
We believe that this bug is caused by an invalid cache file, broken
hardware, or that it is fixed in recent APT versions, and I am thus
closing the bug, so we can focus on newer ones.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because
We believe that this bug is caused by an invalid cache file, broken
hardware, or that it is fixed in recent APT versions, and I am thus
closing the bug, so we can focus on newer ones.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are
We believe that this bug is caused by an invalid cache file, broken
hardware, or that it is fixed in recent APT versions, and I am thus
closing the bug, so we can focus on newer ones.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because
We believe that this bug is caused by an invalid cache file, or broken
hardware, and I am thus closing the bug, so we can focus on newer ones.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
We believe that this bug is caused by an invalid cache files, and I am
thus closing the bug, so we can focus on newer ones.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
We believe that it is fixed in recent APT versions, and I am thus
closing the bug, so we can focus on newer ones.
** Changed in: apt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This should be fixed. If it is reproducible in wily, please reopen.
** Changed in: apt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
This is fixed.
** Changed in: apt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1220013
Title:
python-apt can SIGSEGV when
Hi, thanks for reporting the bug.
This seems like a broken libstdc++ or broken hardware.
I am closing it, so we can focus on more recent bugs.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Either your hardware flipped a bit somewhere or the C++ standard library
was broken, but it was not an APT bug, as the destructor is
automatically generated, and we only deal with values (no pointers or
references in sight), and are thus safe.
** Changed in: apt (Ubuntu)
Status: New =
Hi, thanks for reporting the bug.
This seems like a broken libstdc++ or broken hardware.
I am closing it, so we can focus on more recent bugs.
** Changed in: apt (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This should be fixed in recent versions.
** Changed in: apt (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1098738
Title:
Should be fixed in recent versions.
** Changed in: apt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1118615
Title:
apt: Add
*** This bug is a duplicate of bug 981360 ***
https://bugs.launchpad.net/bugs/981360
** This bug has been marked a duplicate of bug 981360
synaptic crashed with SIGSEGV in pkgCacheGenerator::ListParser::NewProvides()
--
You received this bug notification because you are a member of
Thanks for your bug report. This might be fixed in the meantime. If you
can still reproduce it in wily, please re-open.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks for your bug report. This might be a broken cache and/or a
problem fixed in the meantime. If you can still reproduce it in wily,
please re-open.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks for your bug report. I am closing the bug, as it is old and
probably a bug we fixed in the meantime, if it was our bug (I can see no
potentially unsafe handling of strings there, so that's a bit weird)
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug
Thanks for your bug report. This might be a broken cache and/or a
problem fixed in the meantime. If you can still reproduce it in wily,
please re-open.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for your bug report. Your cache file was too short, apparently it
was corrupted somehow. I am thus closing the bug, as it may have been a
hardware bug or a bug we likely fixed in the meantime.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Thanks for your bug report. This seems to be a broken cache file, and we
believe that it was either a hardware bug or a bug fixed in recent APT
versions that caused it. I am thus closing it.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because
Thanks for your bug report. The generator code has changed a lot in the
mean time. I am thus closing the bug, as it may be a bug we likely fixed
in the meantime.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of
Thanks for your bug report. This seems to be a broken cache file, and we
believe that it was either a hardware bug or a bug fixed in recent APT
versions that caused it. I am thus closing it.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification
Thanks for your bug report. It seems like your cache was broken somehow.
I am thus closing the bug, as it may have been a hardware bug or a bug
we likely fixed in the meantime.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
This bug report is missing a stack trace for further analysis. Anyway,
it is over 2 years old, and thus might be fixed already. Therefore, I am
closing it.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
OK, marking as fixed then.
** Changed in: apt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1464801
Title:
apt-get update
This bug report is missing a complete stack trace and can thus not be
analysed further.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1445436
Title:
Segmentation faults in
This bug report is missing a complete stack trace and can thus not be
analysed further.
** Changed in: apt (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
This is fixed in Debian unstable's 0.9.10 (and possibly earlier
versions), so it is fixed in wily's 1.0.9.10 as well.
** Changed in: apt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Closing this. If you can still reproduce it in wily, please re-open.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Thanks for your bug report. This should be fixed in the meantime. If you
can still reproduce it in wily, please re-open.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Not a bug in python-apt, but in the update-manager, so I'm marking the
python-apt task as invalid.
** Changed in: python-apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
OK, that makes sense. Sorry, I did not see that from the bug report and
did not remember apt.utils existing.
To ignore the signature, we need to open the InRelease file using
apt_pkg.open_maybe_clear_signed_file() and pass the returned file descriptor to
the TagFile, AFAICT.
--
You received
*** This bug is a duplicate of bug 1051935 ***
https://bugs.launchpad.net/bugs/1051935
The bug fixes for bug #1051935 might be incomplete.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
I'm not sure, but I think the changes in python-apt 1.0 could improve
the situation, as I changed it to avoid reference cycles in the
apt.Cache class (and related classes).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
*** This bug is a duplicate of bug 1445949 ***
https://bugs.launchpad.net/bugs/1445949
** This bug has been marked a duplicate of bug 1445949
Version does not conform to PEP440
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It's backported in git already, we just need to get a permission to
upload and upload it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1445949
Title:
Version does
*** This bug is a duplicate of bug 1445949 ***
https://bugs.launchpad.net/bugs/1445949
Will be fixed again with the next upload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
*** This bug is a duplicate of bug 1445949 ***
https://bugs.launchpad.net/bugs/1445949
Nah, we just had a temporary hick up with the ~beta3.1 thing, which
should have been ~beta4.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1445949 ***
https://bugs.launchpad.net/bugs/1445949
If you guys want this to track the pip bug, then please unduplicate it,
and drop the python-apt bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This is not a bug. First of all, it's not a bug in python-apt because we
use APT to parse. Secondly, we have no intention of ignoring unreadable
sources.list files as that would present an inconsistent view of the
available sources.
** Changed in: python-apt (Ubuntu)
Status: Triaged =>
This is fixed in upstream 1.0, the bug number linked is the wrong one
though unfortunately.
I asked infinity about syncing this half a month ago, as it's the final
release of 1.0, and fixes another important bug that is currently in
vivid for example, namely other tools complaining about invalid
Well if the file is not there, python-(APT) cannot use it... Since this
is apparently created by a PPA package, and I cannot reassign things
there, I'm closing it.
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Can we close this now?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1476740
Title:
python-apt ftbfs using GCC 5
Status in python-apt package in Ubuntu:
Fix
Not sure what happened, but definitely not python-apt's problem.
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
I'm not sure why you think /var/run/ipa/services.list is a python-apt
bug. python-apt has nothing to do with that file, so it does not make
sense to report a bug here. Talk to the person providing the PPA
instead.
--
You received this bug notification because you are a member of Ubuntu
Touch
which we do not want.
That release also deprecates some code that will be dropped
in the next release, so it's kind of important to have that.
Changelog entries since current wily version 1.0.0~beta3.1ubuntu1:
python-apt (1.0.0) unstable; urgency=medium
[ Julian Andres Klode ]
* Fix pep8
hangelog entries since current wily version 1.0.0~beta3.1ubuntu1:
python-apt (1.0.0) unstable; urgency=medium
[ Julian Andres Klode ]
* Fix pep8 1.6.2 issues
* setup.py: Pass -std=c++11 and -Wno-write-strings to the compiler
* Convert from SPtr and SPtrArray to unique_ptr a
According to git, the function was first shipped in APT 0.9.8, so you
should be able to just apply
http://anonscm.debian.org/cgit/apt/python-
apt.git/commit/?id=d92026e96db4a4d03cec9f135b5407804892c55f
to trusty's python-apt , and maybe:
http://anonscm.debian.org/cgit/apt/python-
Only the Update manager task became invalid, the python-apt task is
still confirmed.
This is fixed in proposed already with python-apt 1.1 beta 1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
Reassigning, this is happening in pyclean.
** Package changed: python-apt (Ubuntu) => python-defaults (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
This is not a bug in APT. Please do not go mass bug filing stupid bugs
everywhere. Thank you.
** Changed in: apt (Ubuntu)
Status: In Progress => Invalid
** Changed in: apt (Ubuntu)
Assignee: Alberto Salvia Novella (es20490446e) => (unassigned)
** Changed in: apt
Status: In
Like APT, synaptic shows the packages to be installed; as such the user
sees that a lot of packages are installed and can make a descision. If
the user cannot make a decision based on that fact, said user is not the
target audience.
** Changed in: synaptic (Ubuntu)
Status: In Progress =>
1 - 100 of 2457 matches
Mail list logo
