<div dir="ltr"><div dir="ltr"><div>Hi Lukas, please find my answers to your questions.<br></div><div><br></div><div>1) Dariusz has responded to this point.</div><div><br></div><div>2) A typical situation for an SRU MRE is when upstream releases many fixes together as a new minor release. That new upstream release can be SRU'd as a single release, instead of backporting the patches individually, as an MRE.</div><div>So it allows backporting several patches at once without needing to open LP bugs for each of those, and also allows testing the entire release as a whole instead of unit testing each scenario with and without the individual patches. It does not allow making changes to the build system, for eg. introducing new lib dependencies, or any drastic changes from the earlier point release.</div><div><br></div><div>3) Autopkgtest failures for uploads done to <b>stable</b> series have been handled by me in the past, so I can talk about what I did when I saw those failures. I did see specifically cleaner/mask issues in <a href="https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/comments/14">https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/comments/14</a> (opened <a href="https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1962733">https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1962733</a> and <a href="https://github.com/sosreport/sos/issues/2873">https://github.com/sosreport/sos/issues/2873</a>). I then visited the excuses page to check the failures in detail, and then decided to go ahead with the release of the sos 4.3 package after consultation with other SEG folks) as well as the recent (not yet released to updates) SRU for sosreport 4.5.3 (<a href="https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2018270/comments/20">https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2018270/comments/20</a>) where I analysed the focal/bionic autopkgtest failures and ruled them out as a problem. I've also learned about the hints repository (<a href="https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu">https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu</a>) which would be used to manually get packages into proposed for devel, in spite of autopkgtest failures that would block the CI/CD process from pushing it to release automatically.</div><div><br></div><div>4) </div><div>1:1.6.1-0ubuntu3.1 - the first 1 is the epoch, (the major version, often bumped if naming schemes change that would otherwise destroy the greater than/lesser than logic for comparing package versions). The 1.6.1 is the package version. The 0 before the Ubuntu implies there is no debian equivalent of this particular version. This is a devel package, with the ubuntu3 implying its 3rd Ubuntu release, and the .1 is an update, typically from the ~updates pocket. </div><div><br></div><div>2.102-1-2ubuntu0.23.04.1 - "2.102-1" is the upstream version of the package, the -2 after that is the debian revision of it. Ubuntu has used that revision as it is without any extra patches applied on it for its Lunar stable release.<br></div><div><br></div><div>Regards,</div><div>Nikhil.</div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 29, 2023 at 10:06 PM Lukasz Zemczak <<a href="mailto:lukasz.zemczak@canonical.com">lukasz.zemczak@canonical.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Nikhil!<br>
<br>
As at today's DMB meeting we were not able to achieve quorum and the<br>
next DMB application slot is already taken, we have decided to try and<br>
handle Nikhil's application via e-mail. If we're unable to progress<br>
sufficiently fast, we can always discuss the application in one of the<br>
subsequent meetings.<br>
To not delay this into infinity, let's use the next 2-3 days for<br>
questions and then instantly move to voting.<br>
<br>
Nikhil, could you please introduce yourself briefly in a reply to this message?<br>
<br>
As a reminder, Nikhil's application can be found here:<br>
<a href="https://wiki.ubuntu.com/nkshirsagar/UbuntuPerPackageUploaderApplication" rel="noreferrer" target="_blank">https://wiki.ubuntu.com/nkshirsagar/UbuntuPerPackageUploaderApplication</a><br>
and already contains an introduction, but it's always a nice to have a<br>
time-slot to be able to say something more. Especially regarding your<br>
motivations for getting the PPU rights for the package.<br>
<br>
Since there's no actual need to wait, I'll start off with my few<br>
initial questions. The floor is open for questions from other DMB<br>
members as well.<br>
<br>
1) A bit of a formal nitpick, but I see Dariusz on your application is<br>
listed as a 'commenter' instead of an 'endorser'. His comment feels<br>
like an endorsement however - is that a mistake? Would Dariusz be able<br>
to endorse your application?<br>
2) Can you tell me what an SRU MRE is? What is the meaning? What are<br>
the limitations? What does it allow and what not?<br>
3) Let's say an upload that you did for both the devel series and a<br>
stable series, say, jammy, reports autopkgtest failures. What does it<br>
mean to the uploads (both devel and jammy). How would you proceed?<br>
Elaborate on a few possible scenarios here.<br>
4) Could you explain to me in detail the meaning of the following<br>
Ubuntu package versions?<br>
a) 1:1.6.1-0ubuntu3.1<br>
b) 2.102-1-2ubuntu0.23.04.1<br>
<br>
Those should suffice for now. Thank you!<br>
<br>
Best regards,<br>
<br>
<br>
On Mon, 29 May 2023 at 10:36, Nikhil Kshirsagar<br>
<<a href="mailto:nikhil.kshirsagar@canonical.com" target="_blank">nikhil.kshirsagar@canonical.com</a>> wrote:<br>
><br>
> Hello,<br>
><br>
> I am the maintainer of the Ubuntu sosreport package<br>
> (<a href="https://launchpad.net/ubuntu/+source/sosreport/" rel="noreferrer" target="_blank">https://launchpad.net/ubuntu/+source/sosreport/</a>) since the last one<br>
> year.<br>
><br>
> I'd like to apply for PPU upload rights for sosreport. This is my<br>
> application - <a href="https://wiki.ubuntu.com/nkshirsagar/UbuntuPerPackageUploaderApplication" rel="noreferrer" target="_blank">https://wiki.ubuntu.com/nkshirsagar/UbuntuPerPackageUploaderApplication</a><br>
><br>
> I have added my name for the the IRC meeting today at 4 PM UTC.<br>
> (<a href="https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda" rel="noreferrer" target="_blank">https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda</a>)<br>
><br>
> I was not aware I needed to send this email a week earlier, apologies for that.<br>
><br>
> Regards,<br>
> Nikhil.<br>
><br>
> --<br>
> Devel-permissions mailing list<br>
> <a href="mailto:Devel-permissions@lists.ubuntu.com" target="_blank">Devel-permissions@lists.ubuntu.com</a><br>
> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/devel-permissions" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/devel-permissions</a><br>
<br>
<br>
<br>
--<br>
Łukasz 'sil2100' Zemczak<br>
Foundations Team<br>
Tools Squad Interim Engineering Manager<br>
<a href="mailto:lukasz.zemczak@canonical.com" target="_blank">lukasz.zemczak@canonical.com</a><br>
<a href="http://www.canonical.com" rel="noreferrer" target="_blank">www.canonical.com</a><br>
</blockquote></div></div>