Bug#1055487: marked as done (nmu: openstructure_2.6.0~rc-1~exp spglib_2.1.0-1~exp)
Your message dated Fri, 17 Nov 2023 07:44:31 +0100
with message-id <ZVcLzwdxByDVKlCC@ramacher.at>
and subject line Re: Bug#1055487: nmu: openstructure_2.6.0~rc-1~exp spglib_2.1.0-1~exp
has caused the Debian Bug report #1055487,
regarding nmu: openstructure_2.6.0~rc-1~exp spglib_2.1.0-1~exp
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.)
--
1055487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055487
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: binnmu
Hello,
I want to request binNMU on amd64 for packages recently accepted to
experimental.
nmu openstructure_2.6.0~rc-1~exp . amd64 . experimental . -m "Rebuild
on buildd"
nmu spglib_2.1.0-1~exp . amd64 . experimental . -m "Rebuild on buildd"
Thanks,
Andrius
--- End Message ---
--- Begin Message ---
On 2023-11-09 17:03:50 +0200, Andrius Merkys wrote:
> Hi,
>
> On 2023-11-09 15:57, Sebastian Ramacher wrote:
> > We can of course schedule the binNMUs, but I am wondering why are those
> > required?
>
> I wanted to check whether they rebuild successfully on buildd. I have not
> done this before, just wanted to be extra careful this time. But of course I
> may as well proceed with transitions without the binNMUs.
Scheduled openstructure in experimental.
Cheers
--
Sebastian Ramacher
--- End Message ---
Reply to: