Re: Excuse for plaso lists fixed bug as preventing migration
Soren Stoutner <[email protected]>
| Newsgroups | gmane.linux.debian.devel.forensics,gmane.linux.debian.devel.quality-assurance |
|---|---|
| Organization | Debian |
| Message-ID | <1810383.BvlX8tHGu9@soren-desktop> |
On Thursday, February 13, 2025 3:41:37 PM MST Sven Geuer wrote: > Hello QA Team, > > plaso's bug #1093745 [1] has been marked as fixed and closed on Feb. 6, > however, migration still is blocked with the excuse that the very same > bug would be introduced into testing [2]. > > The only peculiarity regarding this bug I know of is that it was closed > manually, instead by means of a "Closes" tag in d/changelog [3]. > > What is missing to make the migration happen? This bug is marked found in plaso/20241006-2 and pinfo/0.6.13-1.3, but it is only marked fixed in plaso/20241006-3. For migration to happen you either need to mark it fixed in a version of pinfo that can migrate or you need to mark it not-found in pinfo/0.6.13-1.3. -- Soren Stoutner [email protected]
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmeuduoACgkQwufLJ66w tgPDjxAAk/1fD5vRDvltaBhtrPBaEdfAPLW/hbpWwL/yxrsPQfqqzAg9m3PeeB7Y D38rUDcH9HRK0Qw08KVD4KBknKaWjDErUH89C9+7r4YR7ycJgubVbzgy+abuhstw 2RYGV7o9TNuTr87RF4DLan/0B5aSkq+scBzBxpA34lJa+DpPr3TRTrKJFwvks0aT /in4l2SwJyuRbcGsThHRuP0RQ6Wbtit5iR7MbbQ5M6w1SfJXRUXe5e+SMwOk++gU MMdrnj33Y0NmP/ncPjsF3luhL3grCc8X8iwggfgXvM02f1xOcAmkvpbTvUO1vipa 4LJz8RjXrCb+QhISknYCTakp42O5Arz8niWya6p4b7Qd14vyvbtPSj+CFiz4twU/ aW09HlgqZyacdn/ugZpTckVtTb1KGlyPhrWr9kr80jfWOMNsmiYTGmBFEv3vXMxE sLI8h55+TUJf5yPW8T1Ho3zqhhAXGMi4ZUuXusZWlrmMbn96DYVaDI0dnKRd0oiR q2mDH3WsDOTu2UgIqK+7O/9wN6j1oOOyUxy+xFCLHQGQrPhDYetlSh2O/L9FZCKA yk2ksN1KyFtevW8RF1nvi2B72AGghf/fQ3tlI+40b7nJpy9dCoiZQqBLxuNmYgB4 RwBgECLdb53St9WX4EPv5BdnT1tUVC6c/4fw7rTULs3eGEZ24Dk= =o7om -----END PGP SIGNATURE-----