[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1041750: apt-get changelog nvidia-driver fails with "Changelog unavailable"



On Sat, Jul 22, 2023 at 11:14:43PM -0400, Allan Wind wrote:
> $ apt-get changelog nvidia-driver
> Err:1 https://metadata.ftp-master.debian.org nvidia-graphics-drivers 525.125.06-1~deb12u1 Changelog
>   Changelog unavailable for nvidia-graphics-drivers=525.125.06-1~deb12u1 (404  Not Found [IP: 146.75.34.132 443])
> E: Failed to fetch https://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_525.125.06-1%7edeb12u1_changelog  Changelog unavailable for nvidia-graphics-drivers=525.125.06-1~deb12u1 (404  Not Found [IP: 146.75.34.132 443])
> 
> The information exist as I was able to find it via:
> 
> https://www.debian.org/News/2023/20230722 ->
> https://packages.debian.org/search?searchon=sourcenames&keywords=nvidia-graphics-drivers ->
> https://packages.debian.org/source/bullseye/nvidia-graphics-drivers ->
> https://metadata.ftp-master.debian.org/changelogs//non-free-firmware/n/nvidia-graphics-drivers/nvidia-graphics-drivers_525.125.06-1~deb12u1_changelog

The problem here is that the (binary) package you request is in section
non-free, while the source package this boils down to is in section
non-free-firmware.

A similar situation could arise with main/contrib or contrib/non-free
I presume, so this isn't a new problem.


`pkgAcqChangelog::URI(pkgCache::VerIterator const&)` in
apt-pkg/acquire-item.cc would need to be changed from using
a VerFileIterator from the binary package to going 'manually' on the
hunt for a (= there be many…) Sources file(s) containing the source
package and from there get the Section and from that also the Release
file.

Alternatively, the server side could just merge the components as there
can't really be different source packages with the same name in different
components and the metadata hopefully doesn't have the same restrictions
applied to it than the packages itself…


Either way, that just as a comment as I won't be working on a fix for
now as I remember people talking about completely overhauling the
implementation/setup client and/or server anyhow.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


Reply to: