On Tue, Jan 13, 2026 at 10:50:11AM +0900, Charles Plessy wrote: > > Le Sun, Jan 11, 2026 at 11:39:33AM +0100, Paul Gevers a écrit : > > > PS: note that the migration failure of r-cran-av is one of the reasons > > > why the ffmpeg transition isn't done yet. > > Le Sun, Jan 11, 2026 at 10:12:10PM +0900, Charles Plessy a écrit : > > > > I am really sorry for the trouble r-cran-av causes, but I do not have > > the tools to see it happening. As of now the tracker page of the > > package does not mention that it is involved in a transition. > > I looked at the ffmpeg tracker page and I see that it has the same version in > unstable and it only mentions automatic transitions in which r-cran-av is not > listed. Where can I track the nuisance of r-cran-av on transitions?
https://release.debian.org/transitions/html/auto-ffmpeg.html shows it for the ffmpeg transition. > > I tried to compute the reverse-dependency graph of r-cran-av but it > > seems that there are circular dependencies between the package imports > > (represented by Debian Depends) and the package regression tests > > (represented by Debian Recommmends because we can not distinguish > > between true Recommends and debian/test/control dependencies), is > > is 10pm and I will not be able to open a RM bug today… [..] > Interestingly no package directly depends on r-cran-av. If it is useful to > file a RM bug on r-cran-av's removed architecture please let me know. > Otherwise, we will have to wait because I think that the 819 other packages > are > not ready yet. > > At the moment I am still doing the architecture restrictions by hand on > packages having new upstream releases. Once it is done, I will do it with > automated source uploads on the other packages. Given you uploaded the package, why not file the RM: bug for the now broken architectures at upload time? What is the benefit in waiting? Chris
