If srcpkg is in main but a binary package is in universe, `apt changelog` fails

Bug #1672555 reported by Nish Aravamudan on 2017-03-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
extract-changelogs
Undecided
Unassigned
apt (Ubuntu)
Undecided
Unassigned

Bug Description

$ apt changelog qemu
Err:1 http://changelogs.ubuntu.com qemu 1:2.8+dfsg-3ubuntu2 Changelog
  Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404 Not Found)
E: Failed to fetch http://changelogs.ubuntu.com/changelogs/pool/universe/q/qemu/qemu_2.8+dfsg-3ubuntu2/changelog Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404 Not Found)

This is because the binary package's component is used to generate the URI, but the source is in main and changelogs are organized by source.

Based upon IRC conversation with slangasek and juliank, it possibly makes sense to flatten the pool/ changelogs to drop the component subdirectory (with symlinks for BC) and then change apt to not use the component in the URI generation

Related branches

Nish Aravamudan (nacc) on 2017-03-13
Changed in extract-changelogs:
assignee: nobody → Nish Aravamudan (nacc)
status: New → In Progress
Nish Aravamudan (nacc) wrote :

Thanks to juliank on IRC: https://gist.github.com/julian-klode/600237d0b61cf92b01748b25cf5921d7 A potential configuration-only change for old clients backwards-compatiblity.

Nish Aravamudan (nacc) on 2017-03-22
Changed in extract-changelogs:
status: In Progress → Invalid
Changed in apt (Ubuntu):
status: New → Invalid
Changed in extract-changelogs:
assignee: Nish Aravamudan (nacc) → nobody
Nish Aravamudan (nacc) wrote :

This was fixed on c.u.c by using Julian's suggested mod_rewrite changes. No changes are needed to extract-changelogs or apt.

Seth Arnold (seth-arnold) wrote :
Julian Andres Klode (juliank) wrote :

That seems more like a missing changelog. The URL is for universe, and the source is in universe.

On Wed, Mar 22, 2017 at 09:53:48PM -0000, Seth Arnold wrote:
> I suspect this transition isn't finished yet:
>
> http://packages.ubuntu.com/precise/abiword -> "ubuntu changelog" -> 404
> for url
> http://changelogs.ubuntu.com/changelogs/pool/universe/a/abiword/abiword_2.9.2+svn20120213-1/changelog

I think there are actually some changelogs for packages missing from the
server due to a hardware failure last year sometime and an incomplete
recreation of them.

There are no changelogs for the version of abiword in precise nor for
the version of abiword from the release pocket for trusty.

http://changelogs.ubuntu.com/changelogs/pool/universe/a/abiword/

I don't worry so much about precise given its impending EoL but it'd be
good to sort out trusty.

--
Brian Murray

Seth Arnold (seth-arnold) wrote :

Oh yeah, it's more nuanced than I expected. Consider bash:

http://packages.ubuntu.com/search?keywords=bash

precise, precise-updates, trusty, and trusty-updates all 404. xenial, xenial-updates, yakkety, and zesty all work fine.

Thanks

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers