Thanks for the detailed description and bug report, this will really help getting it through faster :)
I still have one request: it’s to the reporter to check which packages are in main and if new dependencies needs MIR in main, not the MIR team which is only doing a double check ("bretelles et chaussures" check) :)
So, can you please amend the description after confirming exactly those 2 points:
* --> ALL THESE BINARY PACKAGES MUST GET PROMOTED INTO MAIN (IF THEY ARE
NOT ALREADY THERE).
Please list packages that are not in main and do this research work.
* --> SO MOST PROBABLY NO NEW DEPENDENCIES IN PACKAGES ALREADY EXISTING
IN MAIN AND NO NEW SEEDS ARE NEEDED TO ACTUALLY GET EVERYTHING
INTO MAIN AFTER THE APPROVAL OF THIS MIR.
Please ensure this. there is no "probably", but it’s part of the reporter's work to do the checking. Once this work is done, feel free to assign the 3 bug tasks to me and revert the status to NEW.
Thanks for the detailed description and bug report, this will really help getting it through faster :)
I still have one request: it’s to the reporter to check which packages are in main and if new dependencies needs MIR in main, not the MIR team which is only doing a double check ("bretelles et chaussures" check) :)
So, can you please amend the description after confirming exactly those 2 points:
* --> ALL THESE BINARY PACKAGES MUST GET PROMOTED INTO MAIN (IF THEY ARE
NOT ALREADY THERE).
Please list packages that are not in main and do this research work.
* --> SO MOST PROBABLY NO NEW DEPENDENCIES IN PACKAGES ALREADY EXISTING
IN MAIN AND NO NEW SEEDS ARE NEEDED TO ACTUALLY GET EVERYTHING
INTO MAIN AFTER THE APPROVAL OF THIS MIR.
Please ensure this. there is no "probably", but it’s part of the reporter's work to do the checking. Once this work is done, feel free to assign the 3 bug tasks to me and revert the status to NEW.