Your message dated Sun, 15 Jul 2018 10:44:07 +0200
with message-id <dd754905-5e34-b615-8bdb-c1c1b6923...@debian.org>
and subject line Re: Bug#903697: nmu: ros-geometry2_0.6.2-6
has caused the Debian Bug report #903697,
regarding nmu: ros-geometry2_0.6.2-6
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 ow...@bugs.debian.org
immediately.)
--
903697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
Due to being stuck in new due to the transition, this was build against
the old ros-ros-comm, can you please schedule a rebuild? Thanks!
nmu ros-geometry2_0.6.2-6 . amd64 . unstable . -m "Rebuild against ros-ros-comm
1.14.2."
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: armhf (armv7l)
Kernel: Linux 4.16.0-2-armmp (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 13/07/18 13:20, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: binnmu
>
> Due to being stuck in new due to the transition, this was build against
> the old ros-ros-comm, can you please schedule a rebuild? Thanks!
>
> nmu ros-geometry2_0.6.2-6 . amd64 . unstable . -m "Rebuild against
> ros-ros-comm 1.14.2."
Scheduled.
Emilio
--- End Message ---
