Bug#824841: libgtk-3-0: Properly include upstream changelog

[Ximin Luo]

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 Luo <infinity0 at debian.org> wrote:
> 
>> 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