Hello, On Thu 31 Oct 2024 at 07:01am GMT, Adam D. Barratt wrote:
> On Thu, 2024-10-31 at 13:14 +0800, Sean Whitton wrote: >> I just uploaded 1.1.1n-0+deb11u5 to bullseye-security, but then saw >> there is 1.1.1w-0+deb11u1 in bullseye. So my update will not get >> installed anywhere. >> >> 1.1.1w-0+deb11u1 was not pushed to the debian/bullseye branch in git, >> and I didn't realise we could get into this situation where there was >> still an old version in bullseye-security -- I thought it could only >> exist temporarily, before dak removed the older version. > > As the two dak instances are separate, removal of old versions only > occurs within each. That is, an upload of a new version to -security > will remove older versions within the security suite, but has no impact > on the main archive (until a point release). Likewise uploads to the > main archive have no impact on the security archive. In that case, wouldn't the final bullseye point release have fixed this? >> Regardless, I'm sorry for the mistake here. >> >> I think that I should go ahead and slightly-forward-port my patches, >> upload 1.1.1w-0+deb11u1 to bullseye-security, and release DLA-3942-2. > > +deb11u*2*, presumably? Otherwise it's still not newer than the main > archive. Yes, thanks. -- Sean Whitton
signature.asc
Description: PGP signature
