On Sun, 2023-09-24 at 06:52 +0300, Michael Tokarev wrote: > 23.09.2023 23:45, Adam D. Barratt wrote: > > Control: tags -1 confirmed > > > > On Thu, 2023-08-17 at 12:54 +0300, Michael Tokarev wrote: > > > There's a next upstream qemu stable/bugfix release, fixing a > > > big number of various issues, including 3 (minor) security > > > issues too. The full list is in the changelog below and > > > in the upstream git (mirrored in salsa too). > ... > > > Please go ahead. > > It is a "good" timing, Adam. Just 2 days ago I sent announcement > for a new qemu stable-7.2.6 release fixing a bunch of more bugs, > and fixing an important class of security issues too. > > https://lore.kernel.org/qemu-devel/bf422038-5f0a-e9ca-1eb3-ed25442c7...@tls.msk.ru/ > > "Good" because I forgot to send a note to this bug report about the > upcoming release (it was planned) and as a result we clashed. > > I prepared debian package (based on this new 7.2.6), it is in testing > now on my local machine. > > Will it be easier to upload the reviewed 7.2+dfsg-7+deb12u2 (based on > 7.2.5) and close this bug#, and later make 7.2+dfsg-7+deb12u3 (based > on 7.2.6), or update current bug# with new release? > > I guess it's better to do it step by step, closing this bug# and > filing a new one. >
That might depend when you expect to be ready with the newer update. The window for 12.2 closes next weekend, so if you'd rather have more time to test and work on the 7.2.6 update, it would make sense to upload the 7.2.5-based update for 12.2, and then the newer update for 12.3. Regards, Adam
