Hi Paul, Sorry for the late response.
On Wed, Aug 20, 2025 at 07:50:35AM +0200, Paul Gevers wrote: > If infrastructure related, it's bin:autopkgtest and not src:debci. Ack. > > > That's fine, the autopkgtest fails, but succeeds :-) and we move on. > > The > > problem happens when the regression testing kicks in to check if adding > > only curl from unstable breaks prometheus-mysqlrouter-exporter's > > autopkgtests. In doing that, unstable is added and curl is pinned to > > unstable, that's also fine and expected. But somehow (maybe we need to > > set unstable's preference to -1?) mysql-router and mysql-router are also > > picked from the unstable feed [4]. So basically we have the reference and > > the regression testing doing two extremely different things. > > > That's indeed a consequence of using skip-not-installable. So, shouldn't we pin the unstable as -1 and only pin the package that triggered the regression testing to 900, in order to always make sure nothing else come from unstable? I think I might be missing some implications of this behaviour, right? Anyway, thanks for reassigning. I saw it was fixed today. > I regret that I ever invented skip-not-installable, because the current > situation is one result of it. Oh, well, we all regret something... But you can always remove it in a future major release ;-) Cheers, Charles
