Your message dated Thu, 17 Oct 2019 13:13:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#942496: nmu: libopenvdb5.2_5.2.0-6
has caused the Debian Bug report #942496,
regarding nmu: libopenvdb5.2_5.2.0-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 [email protected]
immediately.)
--
942496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942496
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
I messed up the openvdb binary upload on amd64 (build with older libopenexr23)
So please schedule a binNMU:
nmu libopenvdb5.2_5.2.0-6 . amd64 . -m 'Rebuild against libopenexr24
to correct dependency'
Thanks
--- End Message ---
--- Begin Message ---
On 17/10/2019 11:33, Mathieu Malaterre wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
>
> I messed up the openvdb binary upload on amd64 (build with older libopenexr23)
>
> So please schedule a binNMU:
>
> nmu libopenvdb5.2_5.2.0-6 . amd64 . -m 'Rebuild against libopenexr24
> to correct dependency'
You have other problems:
Not built on buildd: arch amd64 binaries uploaded by [email protected]
Not built on buildd: arch all binaries uploaded by [email protected],
a new source-only upload is needed to allow migration
So even if I did binNMU it, the package would still not migrate to testing
because of the arch:all packages. Thus you better perform a source-only upload
(and change your workflow to always do that unless you have a reason to upload
binaries, e.g. for NEW processing).
Cheers,
Emilio
--- End Message ---
