[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#868825: marked as done (Please handle broken binNMUs more gracefully)

Your message dated Wed, 13 Nov 2019 14:03:12 +0100
with message-id <20191113130312.GA17457@jcristau-z4>
and subject line Re: Bug#868825: Please handle broken binNMUs more gracefully
has caused the Debian Bug report #868825,
regarding Please handle broken binNMUs more gracefully
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
868825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868825
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: snapshot.debian.org

As it happened for #868824 there might be more broken binNMUs coming in
the future.  It would be cool if snapshot could handle that case better.

Possibilities are:
 * stripping off the binNMU version from the source listing
 * ignoring binNMUs for source listing
 * stripping off the binNMU version iff there is no binNMU-versioned
   source (?) or some weird situation like that.
 * something more weird…
In all situations it would mean that snapshot would hardcode the current
version pattern '+bX' used for binNMUs.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Wed, Jul 19, 2017 at 02:37:49AM +0200, Mattia Rizzolo wrote:
> Package: snapshot.debian.org
> 
> As it happened for #868824 there might be more broken binNMUs coming in
> the future.  It would be cool if snapshot could handle that case better.
> 
> Possibilities are:
>  * stripping off the binNMU version from the source listing
>  * ignoring binNMUs for source listing
>  * stripping off the binNMU version iff there is no binNMU-versioned
>    source (?) or some weird situation like that.
>  * something more weird…
> In all situations it would mean that snapshot would hardcode the current
> version pattern '+bX' used for binNMUs.
> 
I don't believe that's something snapshot should do.  The hardcoded +bX
pattern has generally been replaced with the binary-only .changes field
as far as dpkg and the archive are concerned, AFAIK.

Cheers,
Julien

--- End Message ---
Reply to: