Hi, On 21-07-2024 1:14 p.m., Adrian Bunk wrote:
The proper solution would be that release team tooling automatically schedules rebuilds and autopkgtests with the rebuilt packages for transitions prepared in experimental.
But even with experimental that isn't always possible because there might be newer versions there already than we're interested into testing. We'd need an archive per "transition", i.e. bikesheds.
every (re)upload of an auto-* transition package should start a CI run that does everything you are currently asking people to do manually.
That's close to what I was saying, except we currently lack the place and tooling to do that. That was *exactly* what I was hinting at.
Don't assume that tooling would be the only issue, and that all DDs would have hardware capable of doing rebuilds. Some DDs might have more RAM than others have diskspace.
My laptop is rather bare. I know exactly what you're talking about: 4GB RAM, 100 GB disk.
Many DDs appear to have desktops/laptops that are badly equipped for rebuilds involving larger packages.
Like mine.
Trying to build larger C++ sources with less than 4 GB RAM per virtual core can be a horrible experience.
I'm not even trying, I hardly ever build on my system and off-load most builds to debomatic for that reason. Luckily I don't maintain much packages.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
