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

Bug#836917: marked as done (transition: openmpi)

Your message dated Tue, 11 Oct 2016 00:10:15 +0200
with message-id <9adcb9f9-ee51-94d9-b5ef-22335e19ac32@debian.org>
and subject line Re: Bug#836917: transition: openmpi
has caused the Debian Bug report #836917,
regarding transition: openmpi
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.)


-- 
836917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836917
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
Control: forwarded -1 https://release.debian.org/transitions/html/auto-openmpi.html

It sadly seems to be the season of uncoordinated transitions, with some
maintainers not learning for their past mistakes. Very disappointing.

The upload of openmpi (2.0.1-3) to unstable has triggered another
transition. Because of the large number of affected packages, you
(OpenMPI Maintainers) really should have waited for an ACK from the
Release Team. Please imprint the transition documentation in your mind

 https://wiki.debian.org/Teams/ReleaseTeam/Transitions

And most importantly, adhere to the workflow whenever library package
are renamed for SONAME bumps! OpenMPI 2.0 should have stayed in
experimental until the Release Team was ready for the transition.

Kind Regards,

Bas (an unhappy maintainer of affected packages)

--- End Message ---
--- Begin Message --- 
On 25/09/16 14:00, Emilio Pozuelo Monfort wrote:
> Control: tags -1 pending
> 
> On 07/09/16 10:25, Bas Couwenberg wrote:
>> The upload of openmpi (2.0.1-3) to unstable has triggered another
>> transition.
> 
> This needed a big hammer to get it into testing. The fact that the different
> libopenmpi versions conflict with each other doesn't really help.
> 
> This is just pending the boost1.58 removal from testing.
> 

That's done and this is finished. Closing.

Emilio

--- End Message ---
Reply to: