Hi, On Mon, Feb 01, 2021 at 08:07:02PM +0100, Carsten Schoenert wrote: > Am 01.02.21 um 19:33 schrieb Ivo De Decker: > > There are 2 packages that depend on arduino-core: > > > > Output from dak rm: > > > > Checking reverse dependencies... > > # Broken Depends: > > arduino-mighty-1284p: arduino-mighty-1284p > > arduino-mk: arduino-mk > > > > Dependency problem found. > > the package arduino-mighty-1284p got fixed about a hour ago by myon.
Nice :) > For arduino-mk, I reassigned #981300 which was originally opened against > arduino. > > > I don't know if these still work with the new arduino. If so, they will need > > to be updated to have the right dependency. Otherwise, they will have to be > > removed (at least from testing), as they would become uninstallable if > > arduino-core goes away. > > That's possible true, but we are down to one package that would get > uninstallable right now. Packages are generally not removed by ftp-master if there are still reverse dependencies in unstable, unless you explicitly clarify why you think it would be best to do so anyway. If you think that is the way to go, feel free to remove the moreinfo tag from this bug. > > However, given the timing of the freeze, it might be better to reintroduce > > arduino-core as a transitional package, and deal with the removal after the > > bullseye release. > > The package arduino has already that Provides so there must be something > not working correctly then. If arduino-mk is updated we could also drop > that non needed Provides line too. It seems the depends is versioned (arduino-core (>= 1:1.0+dfsg-8)). An unversioned provides doesn't satisfy a versioned dependency. Apart from that, I don't know if the dak rm dependency checking correctly handles provides. > Any way, looking at the reassigned bug report #981300 there is movement > from Simon John to get the package fixed. So I expect that the potential > uninstall ability will go away soon. OK :) > If arduino will migrate automatically, if the one outstanding package > will get fixed, then I'm fine to wait a bit longer. OK. > I see the following info on the tracker site for arduino > > > Issues preventing migration: > > missing build on all > > arch:all not built yet, autopkgtest delayed > > So I was assuming that any old all cruft is around and that's why I > created this report here. That is correct. You'll need to remove the moreinfo tag from this bug to get it removed. If the fix for arduino-mk is coming soon, it might be best to wait for that. > I also expect arduino will still not migrate > after removing the old all package in unstable due breakage of the > version from arduino-mk in testing. That's also correct. Note that I just pinged #976930 to reset the autoremoval counter, to avoid getting arduino removed over this in a few days. If arduino-mk isn't fixed, it will need to be removed from testing before arduino can migrate. But as you noted in https://bugs.debian.org/981300#45, it can just be fixed by changing that dependency, so that's probably a more elegant way to fix this. Thanks, Ivo
