Not fixed in python-apt 0.9.3.5ubuntu2
$ sudo apt install python-apt
...
Get:1 http://mirror.nl.leaseweb.net/ubuntu/ trusty-updates/main python-apt
amd64 0.9.3.5ubuntu2 [141 kB]
...
Unpacking python-apt (0.9.3.5ubuntu2) over (0.9.3.5ubuntu1) ...
Setting up python-apt (0.9.3.5ubuntu2) ...
$
Fixed on Trusty after upgrading python3-apt
--
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/1503979
Title:
ubuntu-support-status throws exeption No date tag found
This does not appear to be fixed in either Trusty or Wily.
me@a-trusty-system:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename: trusty
me@a-trusty-system:~$ apt-cache policy python-apt python3-apt
root@controller:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename: trusty
root@controller:~# apt-cache policy python-apt python3-apt update-manager-core
python-apt:
Installed: 0.9.3.5ubuntu2
Candidate:
I can confirm that Vivid is still affected.
$ apt-cache policy python-apt
python-apt:
Telepítve: 0.9.3.11build1
Jelölt:0.9.3.11build1
Verziótáblázat:
*** 0.9.3.11build1 0
500 http://ubuntu.mirror.lrz.de/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
$
Vivid reaches End of Life this month, so I'm not certain it is worth the
effort to SRU this there.
--
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/1503979
Title:
This also affects vivid, yes? It seems like many people will be running
this on vivid as it approaches end of life.
--
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/1503979
This bug was fixed in the package python-apt - 0.9.3.5ubuntu2
---
python-apt (0.9.3.5ubuntu2) trusty-proposed; urgency=medium
* Do not only look at Release files, but look at InRelease files as well.
Change the code to open Release and InRelease files with
This bug was fixed in the package python-apt - 1.0.1ubuntu0.1
---
python-apt (1.0.1ubuntu0.1) wily; urgency=medium
* Do not only look at Release files, but look at InRelease files as well.
Change the code to open Release and InRelease files with
This bug was fixed in the package python-apt - 1.1.0~beta1
---
python-apt (1.1.0~beta1) unstable; urgency=medium
* Upload to unstable
[ Michael Vogt ]
* Do not show pulse progress when the output is not a tty
* Fix build-dependencies parsing from debian/control
* Print the
I reproduced the issue with python-apt 1.0.1ubuntu0.1 in Wily, and can
confirm that the proposed version 1.0.1ubuntu0.1 solves the issue.
$ ubuntu-support-status
Support status summary of 'wily-amd64':
You have 2237 packages (85.3%) supported until July 2016 (9m)
You have 4 packages (0.2%)
Hello Morty, or anyone else affected,
Accepted python-apt into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/0.9.3.5ubuntu2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Morty, or anyone else affected,
Accepted python-apt into wily-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.0.1ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** No longer affects: update-manager (Ubuntu)
** No longer affects: update-manager (Ubuntu Trusty)
** No longer affects: update-manager (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
Fixed with python-apt (0.9.3.5ubuntu2) on Trusty.
$ ubuntu-support-status
Support status summary of 'mathew-VGN-FW455D':
You have 220 packages (10.0%) supported until February 2015 (9m)
You have 1879 packages (85.2%) supported until May 2019 (5y)
You have 12 packages (0.5%) supported until
Julian - given that open_maybe_clear_signed_file() doesn't exist in
Trusty how could I go about fixing this for that release? Would it be
easy to add that function?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt
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-
** Also affects: python-apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: update-manager (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: python-apt (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects:
I've upload the fix for this to the SRU queue for Trusty and Wily. The
Trusty changes also included a fix for a test that is currently failing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
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.
** Changed in: update-manager (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/1503979
Title:
ubuntu-support-status throws
Why this bug suddenly became 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/1503979
Title:
ubuntu-support-status throws exeption No date tag found
Hi, not really relate to the bug but my apport window listed an invalid
duplicate bug #1509643, please checkout the attatched screenshot:
** Attachment added: "Apport screenshot."
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1503979/+attachment/4526905/+files/Ubuntu_022.png
This bug has been fixed upstream in commit
d18826071a2a7fda9ff52fba215494074a528651, you can see the commit at:
https://anonscm.debian.org/cgit/apt/python-
apt.git/commit/?id=d18826071a2a7fda9ff52fba215494074a528651
The changelog message is:
commit d18826071a2a7fda9ff52fba215494074a528651
This is fixed in upstream release 1.1.0~beta1, which is a stable release
accompanying the APT 1.1 release.
It's a beta because it still uses some deprecated code...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt
There's no real point doing that:
+if path.endswith('InRelease'):
+data = os.fdopen(apt_pkg.open_maybe_clear_signed_file(path))
+else:
+data = open(path)
Just use the open_maybe_clear_signed_file path all the time, that's why
it's "maybe" after all.
+for
How do I apply this patch?
--
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/1503979
Title:
ubuntu-support-status throws exeption No date tag found (regression)
Status
** Changed in: python-apt (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
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/1503979
Title:
Brian, this patch both works for and looks good to me (not sure what
upstream thinks of it). Thanks.
--
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/1503979
Title:
Thanks for looking into this Steve. This is a complete patch which
resolves the issue for me on Xenial.
** Patch added: "bug-1503979.patch"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1503979/+attachment/4524726/+files/bug-1503979.patch
** Tags added: xenial
--
You
I've worked on a patch for this but it doesn't look like
open_maybe_clear_signed_file() exists in Trusty.
--
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/1503979
Title:
** Changed in: update-manager (Ubuntu)
Status: Incomplete => Confirmed
--
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/1503979
Title:
ubuntu-support-status
Same here:
$ ubuntu-support-status
Traceback (most recent call last):
File "/usr/bin/ubuntu-support-status", line 135, in
pkg.name, support_tag)
File "/usr/bin/ubuntu-support-status", line 51, in get_maintenance_status
raise Exception("No date tag found")
Exception: No date tag
** Changed in: python-apt (Ubuntu)
Importance: Undecided => Medium
--
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/1503979
Title:
ubuntu-support-status throws
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
Here it is in patch form. Note that it doesn't entirely address the
issue as passing the _InRelease file to python-apt's
get_release_date_from_release_file(path) function ends up handing the
file to pkg_apt.TagFile() which doesn't recognize the inline gpg signed
file as a RFC 2822 tag formatted
Julian, sorry, but python-apt in get_release_filename_for_pkg()
hardcodes the string '_Release' to the path returned by the function
regardless of whether apt has downloaded a _Release or _InRelease file.
Here's a prototype patch I worked up to address that:
diff -Nru
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
The attachment "python-apt-fix_hardcoded_release_path.patch" seems to be
a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
Here's what I see on wily when making the following change:
--- /usr/bin/ubuntu-support-status 2015-10-08 22:07:36.0 -0700
+++ ./ubuntu-support-status 2015-10-23 14:49:44.092719697 -0700
@@ -48,7 +48,7 @@
# check the release date and show support information
# based on
Note that on a trusty host I have where ubuntu-support-status doesn't
throw a traceback, the following files exist:
-rw-r--r-- 1 root root 64441 Oct 22 23:53
/var/lib/apt/lists/ubuntu-mirror.nxnw.org_ubuntu_dists_trusty-security_InRelease
-rw-r--r-- 1 root root 63459 Oct 1 23:28
42 matches
Mail list logo
