> Do we need the libqt5sql5-sqlite Depends in this SRU?
note that I didn't explicitly ask to add the new dependency, just if it was needed (hence the "needs information" status of the bug). It's your call, and I'm happy to take your decision be it add the new dep or not.
About the upload, since 23.08.5-0ubuntu4.1 was not accepted into proposed, that version wasn't "burned". The new upload should have been 23.08.5-0ubuntu4.1 again, with the change, instead of 23.08.5-0ubuntu4.2.
So, to proceed, we have the following options:
a) You decide that libqt5sql5-sqlite is not needed as a dependency, and we can proceed with the original 23.08.5-0ubuntu4.1 upload and reject 23.08.5-0ubuntu4.2
b) Oops, yes, libqt5sql5-sqlite is needed. In this case, I will reject both 23.08.5-0ubuntu4.1 and 23.08.5-0ubuntu4.2 and you can upload a new 23.08.5-0ubuntu4.1 with the dependency added, and a note in the changelog entry saying this was also added
I'm not on my SRU shift today, but since I have the context on this bug, I can act on it once you tell me which option forward you prefer. I'm inclined towards (b), because of the reasoning in comment #3, but I'm not familiar with this package.
Hi Scarlett,
> Do we need the libqt5sql5-sqlite Depends in this SRU?
note that I didn't explicitly ask to add the new dependency, just if it was needed (hence the "needs information" status of the bug). It's your call, and I'm happy to take your decision be it add the new dep or not.
About the upload, since 23.08.5-0ubuntu4.1 was not accepted into proposed, that version wasn't "burned". The new upload should have been 23.08.5-0ubuntu4.1 again, with the change, instead of 23.08.5-0ubuntu4.2.
So, to proceed, we have the following options:
a) You decide that libqt5sql5-sqlite is not needed as a dependency, and we can proceed with the original 23.08.5-0ubuntu4.1 upload and reject 23.08.5-0ubuntu4.2
b) Oops, yes, libqt5sql5-sqlite is needed. In this case, I will reject both 23.08.5-0ubuntu4.1 and 23.08.5-0ubuntu4.2 and you can upload a new 23.08.5-0ubuntu4.1 with the dependency added, and a note in the changelog entry saying this was also added
I'm not on my SRU shift today, but since I have the context on this bug, I can act on it once you tell me which option forward you prefer. I'm inclined towards (b), because of the reasoning in comment #3, but I'm not familiar with this package.