Bug#890935: transition: console-bridge

[Jose Luis Rivero]

uploaded to unstable.

On 23 Feb 2018 13:51, "Emilio Pozuelo Monfort"  wrote:

> Control: tags -1 confirmed
>
> On 23/02/18 12:14, Jose Luis Rivero wrote:
> > On 23/02/18 10:13, Emilio Pozuelo Monfort wrote:
> >>>
> >>> Please schedule binNMUs for the above mentioned packages on all
> >>> architectures.
> >>
> >> First you need to upload console-bridge to unstable. Before doing that,
> have you
> >> tested that those packages build fine with the new console-bridge?
> >>
> >
> > I ran ratt against the changes file and all the packages listed above
> > passed the build in experimental (same versions than unstable) without
> > any error. I assume that the next step is upload console-bridge to
> > unstable.
>
> Yes, go ahead.
>
> Emilio
>

Processed: Re: Bug#890935: transition: console-bridge

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #890935 [release.debian.org] transition: console-bridge
Added tag(s) confirmed.

-- 
890935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#890935: transition: console-bridge

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 23/02/18 12:14, Jose Luis Rivero wrote:
> On 23/02/18 10:13, Emilio Pozuelo Monfort wrote:
>>>
>>> Please schedule binNMUs for the above mentioned packages on all
>>> architectures.
>>
>> First you need to upload console-bridge to unstable. Before doing that, have 
>> you
>> tested that those packages build fine with the new console-bridge?
>>
> 
> I ran ratt against the changes file and all the packages listed above
> passed the build in experimental (same versions than unstable) without
> any error. I assume that the next step is upload console-bridge to
> unstable.

Yes, go ahead.

Emilio

Bug#890935: transition: console-bridge

[Jose Luis Rivero]

On 23/02/18 10:13, Emilio Pozuelo Monfort wrote:
>>
>> Please schedule binNMUs for the above mentioned packages on all
>> architectures.
>
> First you need to upload console-bridge to unstable. Before doing that, have 
> you
> tested that those packages build fine with the new console-bridge?
>

I ran ratt against the changes file and all the packages listed above
passed the build in experimental (same versions than unstable) without
any error. I assume that the next step is upload console-bridge to
unstable.

Thanks Emilio.

Bug#890935: transition: console-bridge

[Emilio Pozuelo Monfort]

On 20/02/18 20:14, Jose Luis Rivero wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear release team:
> 
> console-bridge 0.4.0 is now in experimental, we can start the transition
> for the existing packages to the archive currently using console-bridge.
> The following source packages need to be rebuild:
> 
> ros-actionlib_1.11.12-1
> ros-class-loader_0.3.8-1
> ros-geometry2_0.5.16-1
> ros-rosconsole-bridge_0.5.1-1
> ros-roscpp-core_0.6.7-1
> urdfdom_1.0.0-2
> ros-bond-core_1.8.1-2
> ros-ros-comm_1.13.5+ds1-1
> ros-dynamic-reconfigure_1.5.49-1
> ros-geometry_1.11.9-1
> 
> I think that in terms of 'ben' lingo, the transition has the following
> parameters:
> 
> title = "console-bridge";
> is_affected = .depends ~ "libconsole-bridge0.2v5" | .depends ~ 
> "libconsole-bridge0.4";
> is_good = .depends ~ "libconsole-bridge0.4";
> is_bad = .depends ~ "libconsole-bridge0.2v5";
> 
> Please schedule binNMUs for the above mentioned packages on all
> architectures.

First you need to upload console-bridge to unstable. Before doing that, have you
tested that those packages build fine with the new console-bridge?

Cheers,
Emilio

Bug#890935: transition: console-bridge

[Jose Luis Rivero]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Dear release team:

console-bridge 0.4.0 is now in experimental, we can start the transition
for the existing packages to the archive currently using console-bridge.
The following source packages need to be rebuild:

ros-actionlib_1.11.12-1
ros-class-loader_0.3.8-1
ros-geometry2_0.5.16-1
ros-rosconsole-bridge_0.5.1-1
ros-roscpp-core_0.6.7-1
urdfdom_1.0.0-2
ros-bond-core_1.8.1-2
ros-ros-comm_1.13.5+ds1-1
ros-dynamic-reconfigure_1.5.49-1
ros-geometry_1.11.9-1

I think that in terms of 'ben' lingo, the transition has the following
parameters:

title = "console-bridge";
is_affected = .depends ~ "libconsole-bridge0.2v5" | .depends ~ 
"libconsole-bridge0.4";
is_good = .depends ~ "libconsole-bridge0.4";
is_bad = .depends ~ "libconsole-bridge0.2v5";

Please schedule binNMUs for the above mentioned packages on all
architectures.

Thanks you.
 Jose