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

Bug#675968: transition: biosig4c++



On 2012-06-04 19:11, Yaroslav Halchenko wrote:
> Thank you Niels,
> 
> On Mon, 04 Jun 2012, Niels Thykier wrote:
>> I am not entirely sure if this was implied or not in your sentence, but
>> we would prefer getting a transition bug before the package is uploaded
>> to sid.
> 
> yes -- that is what I meant (I have sinned twice btw -- just yesterday
> uploaded fresh libguac -- it is in NEW -- will report transition bug
> again). but for upcoming upload of libcomedi will report first (may be
> today)
> 

For the record, you can ask the ftp-masters to reject packages in NEW
(e.g. for stuff like this).  Anyhow, in the given case, we can probably
let it slide for now.  Though, I will follow up on the #675976 about
libguac.

> 
>>> Transition is tiny -- just 2 dependent packages on libbiosig-dev
>>> packages (below). "Transition bug" against biosig4c++ source is
>>> #675967.
>> The bts is acting up a bit, so I cannot actually read the contents of
>> #675967 right now.  Anyhow, it appears to be RC, which will stall the
>> transition so please close it or downgrade it.  For the purpose of
>> tracking the transition, this bug is sufficient.
> 
> that was a fresh bugreport which I filed to prevent biosig4c++ to
> migrate to wheezy before all depends are fine (i.e. trying to do
> "transition" manually).  I guess I mixed up the meaning of 'transition
> bug' and #675967 wasn't really necessary -- closing with this email.
> 

Yeah, in a transition we generally want packages to migrate "sooner
rather than later", so a new RC bug will just make things worse actually. :)

> [...]
> 
>> We already scheduled the binNMUs for these earlier today and indeed
>> sigviewer appears to be doing fine (still waiting for mipsel and armhf
>> though).  openwalut is still building, but I hope it will be as painless
>> as you expect.
> 
> actually openwalnut I haven't tested yet locally so there might be
> surprises.
> 
> [...]

The first results on openwalnut appears to be positive[1], so it is
probably not going to be an issue.  But if something fails I expect you
(i.e. the maintainers of biosig4c++) to help solve the issue.

~Niels

[1]
https://buildd.debian.org/status/package.php?p=openwalnut,sigviewer&compact=compact




Reply to: