Your message dated Sun, 17 Jun 2018 22:49:06 -0400
with message-id <4272370.r2QHyzz4MA@kitterma-e6430>
and subject line Re: r-cran-dbi changed from arch=any to arch=all which makes
it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks
autopkgtests of r-bioc-summarizedexperiment in testing)
has caused the Debian Bug report #898354,
regarding RM: r-cran-dbi [amd64 arm64 armel armhf i386 mips mips64el mipsel
powerpc ppc64el s390x hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- NBS; package
is now binary-all
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.)
--
898354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898354
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
My r-cran-dbi package was by my mistake 'Arch: any' when it should have been
'Arch: all'. That has been corrected in the most recent upload 1.0.0-1.
But as you can see eg at https://packages.debian.org/search?keywords=r-cran-dbi
the previous versions 0.8-1 (and even 0.7-1+b1) are still lurking.
This may need a manual removal from unstable. Could you do this, please?
(Do we need the same for testing, stable, ... as well?)
Thanks, Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | [email protected]
--- End Message ---
--- Begin Message ---
On Thu, 10 May 2018 22:10:43 +0200 Paul Gevers <[email protected]> wrote:
> Hi Andreas
>
> On 10-05-18 22:08, Andreas Tille wrote:
> > On Thu, May 10, 2018 at 12:57:54PM -0500, Dirk Eddelbuettel wrote:
> >> |
> >> | ftp.debian.org is the right pseudo-package for removal (of the 0.8-1
> >> | packages) from unstable.
> >>
> >> Ok, thanks, filed as #898354.
> >
> > Seems that bug is somehow needed for this specific issue. However, I
> > think I had other packages moved from Arch=any to Arch=all without any
> > trouble. So my question is: Did something changed in the software
> > dealing with those uploads recently or is that package in some other
> > aspect different which might cause the observed issue?
>
> You may be right, or maybe somebody behind the scene took action. I now
> looked up the cruft report, and r-cran-dbi is mentioned.
>
> https://ftp-master.debian.org/cruft-report-daily.txt
>
It's gone now.
Scott K
--- End Message ---
