Your message dated Thu, 26 May 2016 22:23:00 +0200 with message-id <57475b24.1020...@debian.org> and subject line Re: Bug#825415: nmu: bppphyview_0.3.0-1 has caused the Debian Bug report #825415, regarding nmu: bppphyview_0.3.0-1 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.) -- 825415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825415 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 nmu bppphyview_0.3.0-1 . ANY . unstable . -m "Rebuild against libbpp-core2v5" rebuild worked fine on amd64 Andreas
--- End Message ---
--- Begin Message ---On 26/05/16 20:21, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian....@packages.debian.org > Usertags: binnmu > > nmu bppphyview_0.3.0-1 . ANY . unstable . -m "Rebuild against libbpp-core2v5" > > rebuild worked fine on amd64 According to cruft-report there are other rdeps: * source package libbpp-core version 2.2.0-2 no longer builds binary package(s): libbpp-core2 on amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,powerpc,ppc64el,s390x - suggested command: dak rm -m "[auto-cruft] NBS (no longer built by libbpp-core)" -s unstable -a amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,powerpc,ppc64el,s390x -p -R -b libbpp-core2 - broken Depends: bppphyview: bppphyview bppsuite: bppsuite libbpp-phyl: libbpp-phyl9 libbpp-qt: libbpp-qt1 libbpp-seq: libbpp-seq9 I have binnmu'ed all of them. Cheers, Emilio
--- End Message ---
