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

Bug#942554: marked as done (transition: soapysdr)

Your message dated Sun, 3 Nov 2019 18:42:58 +0100
with message-id <b0cec18a-8d34-a745-0166-4c6c239e59cb@debian.org>
and subject line Re: Bug#942554: transition: soapysdr
has caused the Debian Bug report #942554,
regarding transition: soapysdr
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.)


-- 
942554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942554
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi release team,

I want to transition soapysdr and limesuite with it. These would be the
auto-soapysdr and auto-limesuite trackers that appear to look fine.

There are a whole bunch of additional auto-soapy* trackers that
correspond to all the plugin module packages that are in a cross
dependency situation with the core soapysdr. They can be ignored as they
will be uploaded together with soapysdr (all of them are ready in
experimental).

limesuite provides a soapysdr plugin that needs to transition
together with the others, but it also has its own library transition
going. My fault, I haven't been paying attention to a team member upload
when preparing soapysdr. But it adds only one package, so rather than
disentangle I'd like to do both in one go.

I've test built the reverse dependencies and they all compiled fine with
the exception of srslte, which is already FTBFS due to libbladerf
changes, and gr-limesdr, which is FTBFS in unstable but has a fixed
version in experimental.


Ben file:
title = "soapysdr+limesuite";
is_affected = .depends ~ "libsoapysdr0.6" | .depends ~ "liblimesuite18.06-1" | .depends ~ "libsoapysdr0.7" | .depends ~ "liblimesuite19.04-1";
is_good = .depends ~ "libsoapysdr0.7" | .depends ~ "liblimesuite19.04-1";
is_bad = .depends ~ "libsoapysdr0.6" | .depends ~ "liblimesuite18.06-1";

--- End Message ---
--- Begin Message --- 
Hi,

On 18-10-2019 09:49, Emilio Pozuelo Monfort wrote:
> On 18/10/2019 03:10, Andreas Bombe wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian.org@packages.debian.org
>> Usertags: transition
>>
>> Hi release team,
>>
>> I want to transition soapysdr and limesuite with it. These would be the
>> auto-soapysdr and auto-limesuite trackers that appear to look fine.
>>
>> There are a whole bunch of additional auto-soapy* trackers that
>> correspond to all the plugin module packages that are in a cross
>> dependency situation with the core soapysdr. They can be ignored as they
>> will be uploaded together with soapysdr (all of them are ready in
>> experimental).
>>
>> limesuite provides a soapysdr plugin that needs to transition
>> together with the others, but it also has its own library transition
>> going. My fault, I haven't been paying attention to a team member upload
>> when preparing soapysdr. But it adds only one package, so rather than
>> disentangle I'd like to do both in one go.
>>
>> I've test built the reverse dependencies and they all compiled fine with
>> the exception of srslte, which is already FTBFS due to libbladerf
>> changes, and gr-limesdr, which is FTBFS in unstable but has a fixed
>> version in experimental.
> 
> Go ahead.

This seems to be finished, closing.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: