Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #275087 > unrolled thread

Succint changelogs for Debian packages

Back to article view | Back to linux.debian.user

Contents

  Succint changelogs for Debian packages jman <debian-user@city17.xyz> - 2024-12-01 12:30 +0100
    Re: Succint changelogs for Debian packages Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2024-12-01 12:40 +0100
      Re: Succint changelogs for Debian packages jman <debian-user@city17.xyz> - 2024-12-01 13:30 +0100
        Re: Succint changelogs for Debian packages Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2024-12-01 14:10 +0100

#275087 — Succint changelogs for Debian packages

Hi,

I've been using Debian for years and one of the question I've always been afraid to ask is: why are 
Debian changelogs always so succint?

For example, I've just upgraded the package file-roller from 44.3 to 44.4 on my testing (trixie) and 
apt changelog says "New upstream release".
In reality the upstream project has actually resolved 2 annoying bugs I was following on their issue 
tracker.

Is there a workflow or something else I can do to actually get an actual summary of upstream 
changes, without jumping through loops trying to reach the upstream project itself? Ideally this is 
something I would like to do when upgrading my Debian packages.

Thanks!

[toc] | [next] | [standalone]

#275088

On 01/12/2024 08:08, jman wrote:
> 
> Hi,
> 
> I've been using Debian for years and one of the question I've always 
> been afraid to ask is: why are Debian changelogs always so succint?

Because the Debian changelog only refers to changes in the Debian 
package itself, not to upstream changes. This is documented somewhere in 
the Debian policy.

> Is there a workflow or something else I can do to actually get an actual 
> summary of upstream changes, without jumping through loops trying to 
> reach the upstream project itself? Ideally this is something I would 
> like to do when upgrading my Debian packages.

Usually if the upstream provides a list of changes, it is included in 
/usr/share/<package-name>. But there isn't a standard for its name (and 
much less for its contents), so look for names like NEWS, Changelog, 
etc. Often it is gzipped.

-- 
Didn't I buy a 1951 Packard from you last March in Cairo?

Eduardo M KALINOWSKI
eduardo@kalinowski.com.br

[toc] | [prev] | [next] | [standalone]

#275092

Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> writes:

> Usually if the upstream provides a list of changes, it is included in
> /usr/share/<package-name>. But there isn't a standard for its name
> (and much less for its contents), so look for names like NEWS,
> Changelog, etc. Often it is gzipped.

The path you probably mean is /usr/share/doc/<package-name>
I didn't think about looking there and now I've found a lot of changelogs. I'll keep it in mind.

Thanks for the tip!

Cheers,

[toc] | [prev] | [next] | [standalone]

#275095

On 01/12/2024 09:04, jman wrote:
> Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> writes:
> 
>> Usually if the upstream provides a list of changes, it is included in
>> /usr/share/<package-name>. But there isn't a standard for its name
>> (and much less for its contents), so look for names like NEWS,
>> Changelog, etc. Often it is gzipped.
> 
> The path you probably mean is /usr/share/doc/<package-name>
> I didn't think about looking there and now I've found a lot of 
> changelogs. I'll keep it in mind.

Yes, of course it should have been /usr/share/doc.


-- 
What is algebra, exactly?  Is it one of those three-cornered things?
		-- J. M. Barrie

Eduardo M KALINOWSKI
eduardo@kalinowski.com.br

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web