Hello Ivo, 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. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981371 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. > 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. 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. If arduino will migrate automatically, if the one outstanding package will get fixed, then I'm fine to wait a bit longer. 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. 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. -- Regards Carsten
