Bug#824841: libgtk-3-0: Properly include upstream changelog
Am 06.09.2016 um 16:17 schrieb Aaron M. Ucko: > Source: gtk+3.0 > Followup-For: Bug #824841 > > It looks like this changelog is now present, and adding 3.6M to each > binary package (some of which had been quite small). Could you please > arrange to avoid this duplication? The ChangeLog is autogenerated, basically a git log dump. tbh, I don't find that particularly helpful. Maybe you can convince upstream to cut-off the log, say only include the changes between major versions, like from 3.x..3.x+1 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#824841: libgtk-3-0: Properly include upstream changelog
Source: gtk+3.0 Followup-For: Bug #824841 It looks like this changelog is now present, and adding 3.6M to each binary package (some of which had been quite small). Could you please arrange to avoid this duplication? Thanks!
Bug#824841: libgtk-3-0: Properly include upstream changelog
Yes, that was a typo. Fortunately my bug subject line was correct and also I referred to the upstream changelog by the correct filename. Could you add this address https://git.gnome.org/browse/gtk+ in addition to the current "fake" upstream changelog, please? I also strongly recommend adding the actual upstream git log into debian/upstream/changelog - for example like how many xul-ext-* packages do. Especially since upstream git is almost 300MiB in size - it would save users and volunteers a great deal of time if we could just read it directly, instead of needing a fast and stable internet connection, and waiting for a few minutes. Then there is the extra step of figuring out which git tag to use, to avoid seeing commits not relevant to the currently-installed version. All of these steps do not make for a pleasant debugging experience especially when my UI is fucked. X D. B.: > You asked for "the upstream bug [log, presumably]", so it was reasonable > for people to presume you wanted a list of bugfixes. > > upstream is git.gnome.org and browse for gtk+ > > > > On Fri, May 20, 2016 at 4:15 PM, Ximin Luowrote: > >> Michael Biebl: >>> Am 20.05.2016 um 12:15 schrieb Ximin Luo: Package: libgtk-3-0 Version: 3.20.4-1 Severity: important Dear Maintainer, Whilst investigating a bug involving GTK themes, I found that the >> contents of the upstream bug is useless: $ zcat /usr/share/doc/libgtk-3-0/changelog.gz A git checkout and git-log is required to generate this file Please fix this - if necessary by generating the changelog from git and repacking the Debian "orig" tarball to include this generated version. Otherwise it makes bug tracking much harder. >>> >>> All bugs are mentioned in the NEWS file. >>> For a complete and more detailed list, a git checkout is much, much >>> better anyway. >>> >> >> The NEWS file contains a list of bugs that have just been fixed, but >> doesn't contain details of major changes that might have resulted in new >> bugs. Obviously the latter is what I'm interested in - I wouldn't be trying >> to read about bugs that were just fixed, since I hopefully wouldn't be >> experiencing them in the first place. >> >> Where is the upstream git? It would be helpful to include the address of >> this repository in changelog.gz, as well as the actual commands I need to >> run (including its dependencies) to generate it. Saving people time really >> helps to avoid user frustration, especially if upstream is prone to making >> backward-incompatible changes that break everything. >> >> X >> >> -- >> GPG: ed25519/56034877E1F87C35 >> GPG: rsa4096/1318EFAC5FBBDBCE >> git://github.com/infinity0/pubkeys.git >> >> > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
Bug#824841: libgtk-3-0: Properly include upstream changelog
You asked for "the upstream bug [log, presumably]", so it was reasonable for people to presume you wanted a list of bugfixes. upstream is git.gnome.org and browse for gtk+ On Fri, May 20, 2016 at 4:15 PM, Ximin Luowrote: > Michael Biebl: > > Am 20.05.2016 um 12:15 schrieb Ximin Luo: > >> Package: libgtk-3-0 > >> Version: 3.20.4-1 > >> Severity: important > >> > >> Dear Maintainer, > >> > >> Whilst investigating a bug involving GTK themes, I found that the > contents of > >> the upstream bug is useless: > >> > >> $ zcat /usr/share/doc/libgtk-3-0/changelog.gz > >> A git checkout and git-log is required to generate this file > >> > >> Please fix this - if necessary by generating the changelog from git and > >> repacking the Debian "orig" tarball to include this generated version. > >> > >> Otherwise it makes bug tracking much harder. > > > > All bugs are mentioned in the NEWS file. > > For a complete and more detailed list, a git checkout is much, much > > better anyway. > > > > The NEWS file contains a list of bugs that have just been fixed, but > doesn't contain details of major changes that might have resulted in new > bugs. Obviously the latter is what I'm interested in - I wouldn't be trying > to read about bugs that were just fixed, since I hopefully wouldn't be > experiencing them in the first place. > > Where is the upstream git? It would be helpful to include the address of > this repository in changelog.gz, as well as the actual commands I need to > run (including its dependencies) to generate it. Saving people time really > helps to avoid user frustration, especially if upstream is prone to making > backward-incompatible changes that break everything. > > X > > -- > GPG: ed25519/56034877E1F87C35 > GPG: rsa4096/1318EFAC5FBBDBCE > git://github.com/infinity0/pubkeys.git > >
Bug#824841: libgtk-3-0: Properly include upstream changelog
Michael Biebl: > Am 20.05.2016 um 12:15 schrieb Ximin Luo: >> Package: libgtk-3-0 >> Version: 3.20.4-1 >> Severity: important >> >> Dear Maintainer, >> >> Whilst investigating a bug involving GTK themes, I found that the contents of >> the upstream bug is useless: >> >> $ zcat /usr/share/doc/libgtk-3-0/changelog.gz >> A git checkout and git-log is required to generate this file >> >> Please fix this - if necessary by generating the changelog from git and >> repacking the Debian "orig" tarball to include this generated version. >> >> Otherwise it makes bug tracking much harder. > > All bugs are mentioned in the NEWS file. > For a complete and more detailed list, a git checkout is much, much > better anyway. > The NEWS file contains a list of bugs that have just been fixed, but doesn't contain details of major changes that might have resulted in new bugs. Obviously the latter is what I'm interested in - I wouldn't be trying to read about bugs that were just fixed, since I hopefully wouldn't be experiencing them in the first place. Where is the upstream git? It would be helpful to include the address of this repository in changelog.gz, as well as the actual commands I need to run (including its dependencies) to generate it. Saving people time really helps to avoid user frustration, especially if upstream is prone to making backward-incompatible changes that break everything. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
Bug#824841: libgtk-3-0: Properly include upstream changelog
Am 20.05.2016 um 12:15 schrieb Ximin Luo: > Package: libgtk-3-0 > Version: 3.20.4-1 > Severity: important > > Dear Maintainer, > > Whilst investigating a bug involving GTK themes, I found that the contents of > the upstream bug is useless: > > $ zcat /usr/share/doc/libgtk-3-0/changelog.gz > A git checkout and git-log is required to generate this file > > Please fix this - if necessary by generating the changelog from git and > repacking the Debian "orig" tarball to include this generated version. > > Otherwise it makes bug tracking much harder. All bugs are mentioned in the NEWS file. For a complete and more detailed list, a git checkout is much, much better anyway. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#824841: libgtk-3-0: Properly include upstream changelog
Package: libgtk-3-0 Version: 3.20.4-1 Severity: important Dear Maintainer, Whilst investigating a bug involving GTK themes, I found that the contents of the upstream bug is useless: $ zcat /usr/share/doc/libgtk-3-0/changelog.gz A git checkout and git-log is required to generate this file Please fix this - if necessary by generating the changelog from git and repacking the Debian "orig" tarball to include this generated version. Otherwise it makes bug tracking much harder. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgtk-3-0 depends on: ii libatk-bridge2.0-0 2.18.1-3 ii libatk1.0-0 2.20.0-1 ii libc6 2.22-7 ii libcairo-gobject2 1.14.6-1+b1 ii libcairo2 1.14.6-1+b1 ii libcolord2 1.3.2-1 ii libcups22.1.3-5 ii libepoxy0 1.3.1-1 ii libfontconfig1 2.11.0-6.4 ii libfreetype62.6.3-3+b1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-02.48.0-1 ii libgtk-3-common 3.20.4-1 ii libjson-glib-1.0-0 1.2.0-1 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libpangoft2-1.0-0 1.40.1-1 ii librest-0.7-0 0.7.93-1 ii libsoup2.4-12.52.2-1 ii libwayland-client0 1.10.0-2 ii libwayland-cursor0 1.10.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 11.1.3-1 ii libx11-62:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1 ii libxdamage1 1:1.1.4-2+b1 ii libxext62:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.6-1 ii libxinerama12:1.1.3-1+b1 ii libxkbcommon0 0.5.0-1 ii libxml2 2.9.3+dfsg1-1 ii libxrandr2 2:1.5.0-1 ii shared-mime-info1.5-2 Versions of packages libgtk-3-0 recommends: ii libgtk-3-bin 3.18.9-1 Versions of packages libgtk-3-0 suggests: ii gvfs 1.28.1-1 ii librsvg2-common 2.40.15-1 -- no debconf information