Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #275088
| From | Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Succint changelogs for Debian packages |
| Date | 2024-12-01 12:40 +0100 |
| Message-ID | <JOQsV-cYKB-3@gated-at.bofh.it> (permalink) |
| References | <JOQjg-cYHw-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web