Re: Bug#944930: RFS: libt3highlight/0.4.6-2
Thanks for the extensive feedback! I'll have a look at going through the
intended process. For now I'll close this bug and either reopen it when I do
get approval or open a new bug specifically for that upload.
Thanks a lot!
Regards,
Gertjan Halkes
On Thu, 28 Nov 2019 03:06:17 +0100, Adam Borowski <kilobyte@angband.pl> wrote:
>Control: tags -1 +moreinfo
>
>On Wed, Nov 27, 2019 at 09:11:07AM +0100, Gertjan Halkes wrote:
>> I would like to kindly bring this bug to your attention again. I think it may
>> have fallen through the cracks as I accidentally didn't wait for the upload
>> to finish and it got rejected on the first try. I would very much like to
>> have some feedback on whether I correctly packaged the fix for the stable
>> release.
>
>Alas, the cracks are pretty wide :/
>
>> On Sun, 17 Nov 2019 19:57:23 +0100, Gertjan Halkes <debian@ghalkes.nl> wrote:
>> >I have prepared a fix for the stable version of my package "libt3highlight".
>> >It is a simple back-port of a fix that is already available in
>> >unstable/testing. I would appreciate it if you could have a look and provide
>> >guidance on whether I have packaged this correctly (this is the first time
>> >I'm preparing a bug-fix for a package in stable).
>
>I'm afraid that there's a non-trivial process for a stable update.
>
>It is described in developers-reference section 5.5.1.:
>https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions
>
>First, you need to file a bug on release.debian.org explaining the reason
>and including the debdiff between 0.4.6-1 and the new upload. Only once
>approved, we can continue with actually uploading.
>
>> >* Package name : libt3highlight
>> > Version : 0.4.6-2
>
>The version must end with +deb10u1 (u2 for second update, etc; deb11 for
>Bullseye, ...). So it'd be 0.4.6-1+deb10u1 .
>
>> >Changes since the last upload:
>> >
>> > * Back-port of bugfix from version 0.4.8 that prevents crashes due to
>> > calling free on an invalid pointer.
>
>It would be good to describe all other changes as well.
>Adding a way to verify upstream signatures is good.
>Making the build verbose may get allowed, but I'm not sure.
>
>So, you need to seek the stable release team's approval, then come back
>here. Good luck!
>
>
>Meow!
>--
>⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
>⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
>⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
>⠈⠳⣄⠀⠀⠀⠀ etc), let the drink age at least 3-6 months.
>
Reply to: