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

Bug#884845: marked as done (release.debian.org: rdma-core does not migrate to testing)

Your message dated Wed, 20 Dec 2017 11:59:27 +0000
with message-id <0a0f41fd94f5116bb9f83103736f6673@mail.adam-barratt.org.uk>
and subject line Re: Bug#884845: release.debian.org: rdma-core does not migrate to testing
has caused the Debian Bug report #884845,
regarding release.debian.org: rdma-core does not migrate to testing
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.)


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

Hi,

rdma-core is the new source package that takes over several rdma related
source packages. Therefore it takes over several binary packages, but it
does not break the API of the existing binary library packages. The
package builds on all linux architectures and the excuses for rdma-core
look good:

* Migration status: OK: Will attempt migration (Any information below
  is purely informational)
* 8 days old (needed 5 days)
* Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdma-core.html
* Valid candidate

Is there a reason why the package does not migrate? Can you push it to
migrate?

PS: Is this type of bug report the correct way to handle non-working
testing migrations?

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.drung@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg

--- End Message ---
--- Begin Message --- 
On 2017-12-20 10:35, Benjamin Drung wrote:
rdma-core is the new source package that takes over several rdma related source packages. Therefore it takes over several binary packages, but it 
does not break the API of the existing binary library packages. The
package builds on all linux architectures and the excuses for rdma-core
look good:

* Migration status: OK: Will attempt migration (Any information below
  is purely informational)
* 8 days old (needed 5 days)
* Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdma-core.html 
* Valid candidate

Is there a reason why the package does not migrate?


If there weren't a reason, it would have migrated, surely?

The (publicly available via HTTP, and DD-accessible via SSH) log says:

trying: rdma-core
skipped: rdma-core (0, 22, 197)
    got: 32+0: a-2:i-24:a-0:a-0:a-0:m-2:m-3:m-0:p-0:s-1
    * mips: libibverbs1-dbg, librdmacm1-dbg
mips is essentially a random architecture at this point, the issue would occur on all architectures.
The problem is that the new combined source package now builds -dbgsym packages instead of the -dbg packages. When britney tries to migrate rdma-core, the binaries it has not taken over from the old separate source packages are left in testing and become uninstallable due to their strongly versioned dependencies on other packages which are now built from the new source package. In order to resolve that, the old source packages (at least those with affected -dbg packages) need to be removed from testing at the same time as the new one migrates. 


Can you push it to migrate?


I've added this hint, which seems to work fine in a test run:

easy rdma-core/16.0-1 -librdmacm/1.1.0-2 -libibverbs/1.2.1-2

Regards,

Adam

--- End Message ---
Reply to: