Re: [Sts-sponsors] Please review and sponsor bind9-libs for LP1926139
Hi Matthew, I'm looking at it today. Thanks, On Tue, Jan 17, 2023 at 1:14 AM Matthew Ruffell wrote: > > Hi everyone, > > Can I get a courageous person to help sponsor bind9-libs for Focal and > Jammy in LP1926139: > > https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139 > > Microsoft Azure have been putting a bit of pressure on me about this > case, in SF337873. Not in the case itself, but this went from not > important at all to this is very important and need daily updates mid > last week to getting pings every day from Kyler and Melissa about > status updates so they can keep them calm over email. > > Its a little complicated, and the analysis is a bit long, but the LP > bug explains what is happening. You might go mad reading it. Turned > out to be a one line fix though, as all complicated fixes are. > > Press the edit description button to see code indentation. > > Thanks, > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] [Bug 1999711] [NEW] Snmptrapd cannot reconnect to MySQL server after hitting MySQL wait_timeout
Hey Chengen,
On Thu, Jan 12, 2023, 22:07 Chengen Du wrote:
> Hi Mauricio,
>
> Sorry for not asking about the correct flow.
>
No worries at all!
This should be in our docs / onboarding, for people not to have to ask, so
it's not on you, but on us :)
Sorry; we'll be working on that.
I added the LP bug URL in Salesforce.
> Thanks for your help.
>
Cool. Glad to help!
Thank you for all your work on this!
> Best regards,
> Chengen Du
>
> On Thu, Jan 12, 2023 at 8:57 PM Mauricio Oliveira
> wrote:
> >
> > Hi Chengen!
> > How are you?
> >
> > I just found out this bug that needs SRU sponsorship for your ticket
> SF#341744.
> >
> > Please excuse our lack of documentation; I'll be working on that,
> > but the reason our sponsor team (or at least me) was because
> > the 'SE SRU Sponsors' team was not _subscribed_ to the bug.
> >
> > I see you added a `sts-sponsor` tag, but unfortunately it doesn't
> > generate any notification -- you can actually not use it anymore. :)
> >
> > I went ahead and subscribed us (in the future, you can do this
> > by clicking "Subscribe someone else" and "SE SRU Sponsors"
> > (sts-sponsors).
> >
> > And another important very step is to add the LP Bug URL in
> > Salesforce, in the 'Public Bug URL' field, e.g.,
> > https://bugs.launchpad.net/bugs/1999711
> >
> > This allows our scripts to check for the SRUs in SF cases
> > and keep them moving forward until they are released!
> >
> > Thanks for your upstream patch and bug report!
> > We'll take a look at it!
> >
> > cheers,
> > Mauricio
> >
> >
> >
> >
> > -- Forwarded message -
> > From: Launchpad Bug Tracker <1999...@bugs.launchpad.net>
> > Date: Thu, Jan 12, 2023 at 9:37 AM
> > Subject: [Sts-sponsors] [Bug 1999711] [NEW] Snmptrapd cannot reconnect
> > to MySQL server after hitting MySQL wait_timeout
> > To:
> >
> >
> > You have been subscribed to a public bug by Mauricio Faria de Oliveira
> (mfo):
> >
> > [Impact]
> > wait_timeout is the number of seconds the MySQL server waits for
> > activity before closing the connection.
> > MySQL v8.0.24 writes the reason for the connection before closing it,
> > and the client receives a more informative error message
> > (ER_CLIENT_INTERACTION_TIMEOUT).
> > Snmptrapd does not handle this error code, so the connection will not
> > reconnect to the MySQL server afterward.
> >
> > [Test Plan]
> > 1. Setup MySQL server and modify wait_timeout to 15 in
> > /etc/MySQL/mysql.conf.d/mysqld.cnf
> > 2. Setup snmptrapd and execute snmptrap command
> > 3. Sleep 15 seconds and re-execute snmptrap command, then the
> > connection will fail until the snmptrapd service restarted
> >
> > [Where problems could occur]
> > Once the error happens, snmptrapd will keep the sql commands and
> > resend it after reconnecting to the MySQL server.
> > The regression can be considered as low.
> >
> > [Other Info]
> >
> > ** Affects: net-snmp (Ubuntu)
> > Importance: Undecided
> > Assignee: ChengEn, Du (chengendu)
> > Status: In Progress
> >
> > ** Affects: net-snmp (Ubuntu Bionic)
> > Importance: Undecided
> > Assignee: ChengEn, Du (chengendu)
> > Status: In Progress
> >
> > ** Affects: net-snmp (Ubuntu Focal)
> > Importance: Undecided
> > Assignee: ChengEn, Du (chengendu)
> > Status: In Progress
> >
> > ** Affects: net-snmp (Ubuntu Jammy)
> > Importance: Undecided
> > Assignee: ChengEn, Du (chengendu)
> > Status: In Progress
> >
> > ** Affects: net-snmp (Ubuntu Kinetic)
> > Importance: Undecided
> > Assignee: ChengEn, Du (chengendu)
> > Status: In Progress
> >
> > ** Affects: net-snmp (Ubuntu Lunar)
> > Importance: Undecided
> > Assignee: ChengEn, Du (chengendu)
> > Status: In Progress
> >
> >
> > ** Tags: bionic focal jammy kinetic lunar patch sts sts-sponsor
> > --
> > Snmptrapd cannot reconnect to MySQL server after hitting MySQL
> wait_timeout
> > https://bugs.launchpad.net/bugs/1999711
> > You received this bug notification because you are a member of SE SRU
> > ("STS") Sponsors, which is subscribed to the bug report.
> >
> > --
> > Mailing list: https://launchpad.net/~sts-sponsors
> > Post to : sts-sponsors@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~sts-sponsors
> > More help : https://help.launchpad.net/ListHelp
> >
> >
> > --
> > Mauricio Faria de Oliveira
>
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help : https://help.launchpad.net/ListHelp
[Sts-sponsors] Fwd: [Bug 1999711] [NEW] Snmptrapd cannot reconnect to MySQL server after hitting MySQL wait_timeout
Hi Chengen!
How are you?
I just found out this bug that needs SRU sponsorship for your ticket SF#341744.
Please excuse our lack of documentation; I'll be working on that,
but the reason our sponsor team (or at least me) was because
the 'SE SRU Sponsors' team was not _subscribed_ to the bug.
I see you added a `sts-sponsor` tag, but unfortunately it doesn't
generate any notification -- you can actually not use it anymore. :)
I went ahead and subscribed us (in the future, you can do this
by clicking "Subscribe someone else" and "SE SRU Sponsors"
(sts-sponsors).
And another important very step is to add the LP Bug URL in
Salesforce, in the 'Public Bug URL' field, e.g.,
https://bugs.launchpad.net/bugs/1999711
This allows our scripts to check for the SRUs in SF cases
and keep them moving forward until they are released!
Thanks for your upstream patch and bug report!
We'll take a look at it!
cheers,
Mauricio
-- Forwarded message -
From: Launchpad Bug Tracker <1999...@bugs.launchpad.net>
Date: Thu, Jan 12, 2023 at 9:37 AM
Subject: [Sts-sponsors] [Bug 1999711] [NEW] Snmptrapd cannot reconnect
to MySQL server after hitting MySQL wait_timeout
To:
You have been subscribed to a public bug by Mauricio Faria de Oliveira (mfo):
[Impact]
wait_timeout is the number of seconds the MySQL server waits for
activity before closing the connection.
MySQL v8.0.24 writes the reason for the connection before closing it,
and the client receives a more informative error message
(ER_CLIENT_INTERACTION_TIMEOUT).
Snmptrapd does not handle this error code, so the connection will not
reconnect to the MySQL server afterward.
[Test Plan]
1. Setup MySQL server and modify wait_timeout to 15 in
/etc/MySQL/mysql.conf.d/mysqld.cnf
2. Setup snmptrapd and execute snmptrap command
3. Sleep 15 seconds and re-execute snmptrap command, then the
connection will fail until the snmptrapd service restarted
[Where problems could occur]
Once the error happens, snmptrapd will keep the sql commands and
resend it after reconnecting to the MySQL server.
The regression can be considered as low.
[Other Info]
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Assignee: ChengEn, Du (chengendu)
Status: In Progress
** Affects: net-snmp (Ubuntu Bionic)
Importance: Undecided
Assignee: ChengEn, Du (chengendu)
Status: In Progress
** Affects: net-snmp (Ubuntu Focal)
Importance: Undecided
Assignee: ChengEn, Du (chengendu)
Status: In Progress
** Affects: net-snmp (Ubuntu Jammy)
Importance: Undecided
Assignee: ChengEn, Du (chengendu)
Status: In Progress
** Affects: net-snmp (Ubuntu Kinetic)
Importance: Undecided
Assignee: ChengEn, Du (chengendu)
Status: In Progress
** Affects: net-snmp (Ubuntu Lunar)
Importance: Undecided
Assignee: ChengEn, Du (chengendu)
Status: In Progress
** Tags: bionic focal jammy kinetic lunar patch sts sts-sponsor
--
Snmptrapd cannot reconnect to MySQL server after hitting MySQL wait_timeout
https://bugs.launchpad.net/bugs/1999711
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help : https://help.launchpad.net/ListHelp
--
Mauricio Faria de Oliveira
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please Review and Sponsor php7.4 for LP1999598
Hi Matthew, No worries at all -- sponsoring is what we're here for! :) By the way, you could apply for _sru-dev_ upload rights, instead of core-dev, which is the privilege level our group has at the moment; this is sufficient for most of our team's work/uploads (SRUs). However, please feel free to apply for core-dev directly if you'd like, as we don't have one anymore, and when our work/uploads depend on the development release being patched, we need to ask other teams. And don't feel bad about the delayed application -- I wanted to apply for core-dev back in September (...). But we know/certainly understand that other work/tickets may get in the way with higher priority. If you'd like any help/mentoring with your application process (to either privilege level), I'd be happy to help you with what I can. cheers, ... Some links about the different upload rights/teams: https://wiki.ubuntu.com/UbuntuDevelopers#Ubuntu_Core_Developers https://launchpad.net/~ubuntu-core-dev https://wiki.ubuntu.com/UbuntuDevelopers#SRU_developers https://launchpad.net/~ubuntu-sru-developers On Wed, Dec 14, 2022 at 3:08 AM Matthew Ruffell wrote: > > Hi everyone, > > Sorry to be a real bother, I need to apply for core-dev, and stop > talking about it and do it, I promise to start my application tomorrow > even. > > But in the meantime, can you please review and consider sponsoring > php7.4 in the below launchpad bug. > > https://bugs.launchpad.net/ubuntu/+source/php7.4/+bug/1999598 > > Thanks, > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
sts-sponsors@lists.launchpad.net
Hey Matthew, I'll handle it. On Fri, Jul 22, 2022 at 12:10 AM Matthew Ruffell wrote: > > Hi Dariusz, Heitor, Maurico, > > Could I please get this debdiff reviewed and sponsored? AT&T have been > asking for it. > > https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933 > > Thanks, > Matthew > > On Tue, Jul 5, 2022 at 10:44 AM Matthew Ruffell > wrote: > > > > Hi everyone, > > > > Can you please review and sponsor LP #1979933, net-snmp? > > > > https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1979933 > > > > AT&T are happy with their test package and it fixes the issue for them. > > > > It is another straightforward SRU. > > > > Thanks, > > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please sponsor openssl for Focal for LP #1960863
Hey Matthew, I'll take it. Process wise, please feel free to just subscribe sts-sponsors to the bug (I guess the tag isn't used?). I just did it for this bug, so don't worry about it. :) The heads-up regarding priority/impact is welcome, nonetheless. And your application for SRU developer would be even more welcome! Thank you! On Mon, Feb 14, 2022 at 8:35 PM Matthew Ruffell wrote: > > Hello, > > Can you please sponsor openssl for Focal in LP #1960863 for me? > > https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863 > > AWS would really like this fixed. > > I also need to apply to become a SRU developer sometime... > > Thanks, > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please review and consider sponsoring LP #1909950 Bind9 on Focal
Hey Matthew, Sure, I'll take it. cheers, On Tue, Feb 9, 2021 at 2:19 AM Matthew Ruffell wrote: > > Hello everyone, > > Can you please review and sponsor LP #1909950 for Bind9 on Focal? > > https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950 > > I managed to figure out how to reproduce it, and I also have good test > results from both Adam (LP reporter) and Richard in SF299354. > > Also, yes, I would like to work toward putting an SRU Developer application > together sometime this year. > > Thanks, > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please review and sponsor LP#1912122 for rsyslog
Hi Dan, Eric, Matthew got an ack from the security team in email and the LP bug (thanks, Matthew!) Could you please review LP#1912122 to sponsor for Hirsute? I know Eric is on a 'sprint' this week, so I guess this is more on you Dan, sorry x) but the LP bug is not a high priority -- the case has been closed already. I can take care of Groovy when I get back next week, or maybe Dariusz, or you if you wanna tackle both at once :) Just let me know. cheers, On Mon, Jan 18, 2021 at 11:36 PM Matthew Ruffell wrote: > > Hi Mauricio, > > The security team have acked the bug, see the email, and the comment in the > bug. > > I uploaded new debdiffs with the extra step Steve suggested, I built > it and tested it, > and it works great. > > Please sponsor. > > Thanks, > Matthew > > On Tue, Jan 19, 2021 at 2:54 AM Mauricio Oliveira > wrote: > > > > Hey Matthew, > > > > This seems straightforward and the 'right thing to do', and maybe even > > Groovy isn't an issue since the kernel config option is already there. > > > > However, we probably need a review/ack from the security team on it, > > since it's more on their court than ours. > > > > Could you please subscribe the security team to the bug, and ask for > > their review/ack in a new comment? > > I've seen good responsiveness from them in a case like this in the > > past; but if they don't you may also ping them in their channel. > > > > Thanks, > > Mauricio > > > > On Mon, Jan 18, 2021 at 12:32 AM Matthew Ruffell > > wrote: > > > > > > Hi Eric, Mauricio, > > > > > > Could you please review and consider sponsoring the rsyslog debdiffs on LP > > > 1912122? > > > > > > https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122 > > > > > > VISA opened a case and mentioned that /var/log/dmesg is 0644, and I > > > should have > > > really caught this and changed it to 0640 during my campaign to get > > > DMESG_RESTRICT enabled. > > > > > > So, fixing it up here. > > > > > > I am aware that this might not be possible to SRU to Groovy, or would get > > > stuck in block-proposed, but its the upload to hirsute that really > > > matters. > > > > > > Please review and sponsor. You can put timecards under: > > > SF301554 - VISA - /var/log/dmesg file pemission > > > > > > Thanks, > > > Matthew > > > > > > -- > > > Mailing list: https://launchpad.net/~sts-sponsors > > > Post to : sts-sponsors@lists.launchpad.net > > > Unsubscribe : https://launchpad.net/~sts-sponsors > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > -- > > Mauricio Faria de Oliveira -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please review and sponsor LP#1912122 for rsyslog
Hey Matthew, This seems straightforward and the 'right thing to do', and maybe even Groovy isn't an issue since the kernel config option is already there. However, we probably need a review/ack from the security team on it, since it's more on their court than ours. Could you please subscribe the security team to the bug, and ask for their review/ack in a new comment? I've seen good responsiveness from them in a case like this in the past; but if they don't you may also ping them in their channel. Thanks, Mauricio On Mon, Jan 18, 2021 at 12:32 AM Matthew Ruffell wrote: > > Hi Eric, Mauricio, > > Could you please review and consider sponsoring the rsyslog debdiffs on LP > 1912122? > > https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122 > > VISA opened a case and mentioned that /var/log/dmesg is 0644, and I should > have > really caught this and changed it to 0640 during my campaign to get > DMESG_RESTRICT enabled. > > So, fixing it up here. > > I am aware that this might not be possible to SRU to Groovy, or would get > stuck in block-proposed, but its the upload to hirsute that really matters. > > Please review and sponsor. You can put timecards under: > SF301554 - VISA - /var/log/dmesg file pemission > > Thanks, > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] Please review and consider sponsoring LP1910307 and LP1908473 (librelp)
Hey Matthew, Great work on those. I'd be happy to review/sponsor for the SRUs after the merge is released. Could you please ping me once that happens? and I'll take care of it. cheers, On Wed, Jan 6, 2021 at 2:12 AM Matthew Ruffell wrote: > > Hello Eric, > > I followed the instructions you posted on Mattermost yesterday on how to > perform > a merge. > > The merge bug for librelp is: > > https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1910307 > > I have attached debdiffs from Debian, and the last Ubuntu version, just like > the merge document mentioned. Please review and merge if it is okay. > > Once librelp has been merged, I also need sponsorship for patches to fix the > file descriptor leak in librelp in Groovy and Focal. The LP bug is: > > https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473 > > Please review and consider sponsoring. I hope the versions are a bit > more correct > this time around. > > Thanks, > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] [URGENT] Please review and sponsor LP1772556. This needs to make 18.04.5 LTS.
Just to close the loop on this (the d-i build failure due to the regression in kmod), this has been reported on LP#1889297, and the fix is already in bionic-proposed. The debootstrap changes (original work from SF case) too, and verified (thanks Matthew!) So, all good! On Mon, Jul 27, 2020 at 1:01 PM Mauricio Oliveira wrote: > > Hi Matthew, > > Nice tricks you found out. > > So, I checked w/ Łukasz today, and he's more aware of the d-i problem; > and welcomed help to fix it. > > He would have to rebuild d-i anyway to bump the kernels, so fixing it > is on their critical path too. > (Thus we don't have to worry about having our fix for d-i/kmod/systemd > being neglected :-) > > As for timing for release, now that I have more energy to think about it, > we don't need the d-i rebuilt to actually pick debootstrap in the ISO > (which is the timing sensitive part), > just the new/fixed package available in the archive. > Because debootstrap does not go into the initrd (which is what d-i > builds), but in the ISO "archive" only (I guess it's debian-cd which > does it.) > [see below] > > And similarly, it seems that the network installer pulls debootstrap > as well -- it's not in initrd either. > So, fixing debootstrap in the archive is the only thing needed to get > it on both ISO and netinst. :-) > > Today I've done some more testing w/ debootstrap, for the SRU team to > be a bit happier, > and uploaded to B/F. Łucasz has ACKed. :) > > I've got to go for the day, but should be able to check MM in a few hours. > (And later today or tomorrow get into the fun of > > [ISO checks for debootstrap] > > $ sudo mount -o loop,ro ubuntu-18.04.4-server-amd64.iso mnt > > $ find mnt/ -name '*debootstrap*' > mnt/pool/main/d/debootstrap > mnt/pool/main/d/debootstrap/debootstrap-udeb_1.0.95ubuntu0.5_all.udeb > > $ mkdir initrd > $ cd initrd > $ gzip -dc ../mnt/install/initrd.gz | cpio -H newc -mid > $ find . -name '*debootstrap*' > $ > > [netinst checks for debootstrap] > > $ wget > http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz > $ gzip -dc initrd.gz | cpio -H newc -mid > $ find . -name '*debootstrap*' > $ > > On Sun, Jul 26, 2020 at 11:02 PM Matthew Ruffell > wrote: > > > > Hi Mauricio, > > > > Thanks for your awesome analysis! > > > > > At this point I think that *if* the case/matter is only about the > > > network installer, > > > not the ISO (which is indeed critical with 18.04.5), then it can be > > > fixed via SRU, > > > without any concerns. > > > > > Would you please evaluate this w/ customer/Lukasƶ on Monday? > > > > The customer was not interested in the mini.iso image, they use the network > > installer, with vmlinuz and initrd.gz. So, that's good to hear that it can > > be > > fixed via SRU without any concerns. > > > > I suppose there is no need to rush now. > > > > > You may notice that even before the --add-udeb flag removal, > > > libkmod2-udeb *did not* > > > ship that shared library! > > > > > > I wondered how the installer worked. It DOES have that library in > > > /lib/libkmod.so.2. > > > And I have no idea where it pulled it from. > > > > > I checked MANIFEST files, d-i build log, even download all udebs in > > > bionic/bionic-updates, > > > extracted, but nothing shipped it. > > > > > This might be some d-i build magic, which I didn't look/find yet. > > > > You and me both! I hit the problem when I was making the test mini.iso and > > test vmlinuz / initrd.gz files. What I did to workaround it was do a grep > > over > > the local repository cache d-i keeps when building images, and then do a > > cheeky > > sed -i s/libkmod2/libkmod2-udeb/g, commands below: > > > > "sed -i "s/Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), > > libkmod2, util-linux-udeb/Depends: libblkid1-udeb (>= 2.31), > > libc6-udeb (>= 2.27), libkmod2-udeb, util-linux-udeb/g" > > ./apt.udeb/state/lists/nz.archive.ubuntu.com_ubuntu_dists_bionic-updates_main_debian-installer_binary-amd64_Packages" > > > > "sed -i "s/Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), > > libkmod2, util-linux-udeb/Depends: libblkid1-udeb (>= 2.31), > > libc6-udeb (>= 2.27), libkmod2-udeb, util-linux-udeb/g" > > ./apt.udeb/state/lists/security.ubuntu.com_ubuntu_dists_bionic-updates_main
Re: [Sts-sponsors] [URGENT] Please review and sponsor LP1772556. This needs to make 18.04.5 LTS.
e install image. That's cheating =p
>
> As for the fix, well, I think the path of least resistance is to simply revert
> the change to libkmod2, and get it to start building libkmod2-udeb
> again (in bionic).
>
> Sure, it will incorrectly advertise itself as containing something useful when
> it really doesn't, but everything was fine for the two years it existed in the
> archive. I wouldn't revert it on anything beyond Bionic though.
>
> I'll send the above to Lukasz in case he has seen the dependency problem and
> had been looking into it.
>
> Thanks,
> Matthew
>
> On Sat, Jul 25, 2020 at 12:49 PM Mauricio Oliveira
> wrote:
> >
> > Hi Matthew,
> >
> > Long story short, the debian-installer rebuild on PPA fails on Bionic.
> >
> > The fix for this should apparently involve changes to kmod and systemd,
> > at least systemd, and I think this may get push back from release team
> > at this time before the point release (however small the change is.)
> >
> > If the fix is needed only in the network-installer, that can be an SRU
> > later.
> >
> > Let me explain, and hopefully you can start addressing it with Lukasƶ
> > on your Monday, before I join.
> >
> > The d-i build on PPA fail because 'udev-udeb' cannot pull 'libkmod2'.
> >
> > Building dependency tree...
> > Installing libslang2-udeb as Depends of cdebconf-newt-udeb
> > udev-udeb:amd64 Depends on libkmod2:amd64 < none @un H > can't
> > be satisfied!
> >
> > ...
> >
> > The following packages have unmet dependencies:
> > udev-udeb : Depends: libkmod2 but it is not installable
> > E: Unable to correct problems, you have held broken packages.
> > Makefile:620: recipe for target
> > 'stamps/get_udebs-cdrom_isolinux-stamp' failed
> > make[7]: *** [stamps/get_udebs-cdrom_isolinux-stamp] Error 100
> >
> > This is correct, because the d-i build does configure sources only for udeb
> > packages, and libkmod2 is a regular deb.
> >
> > Previously it worked because udev-udeb pulled libkmod2-udeb (note suffix.)
> >
> > This is a regression in the dependencies of udev-udeb in 237-3ubuntu10.40:
> >
> > https://launchpad.net/ubuntu/bionic/amd64/udev-udeb/237-3ubuntu10.39
> > Depends on: libkmod2-udeb
> >
> > https://launchpad.net/ubuntu/bionic/amd64/udev-udeb/237-3ubuntu10.40
> > Depends on: libkmod2
> >
> > This happened because the build dependency kmod (which you're familiar with
> > :)
> > changed versions in between, 24-1ubuntu3.2 to 3.3:
> >
> > On u10.39: Get:45 http://ftpmaster.internal/ubuntu
> > bionic-updates/main amd64 libkmod2 amd64 24-1ubuntu3.2 [40.0 kB]
> > On u10.40: Get:45 http://ftpmaster.internal/ubuntu
> > bionic-updates/main amd64 libkmod2 amd64 24-1ubuntu3.3 [40.1 kB]
> >
> > And this change caused this:
> >
> > kmod (24-1ubuntu3.3) bionic; urgency=medium
> > ...
> > * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
> > actually contain a library. (Closes: #939779)
> > ...
> >
> > This still builds/ships the libkmod2-udeb package, but...
> >
> > The lack of dh_makeshlibs with --add-udeb causes the libkmod2
> > (non-udeb)'s "shlibs"
> > file to no longer indicate that udeb packages which depend on that
> > library package
> > should depend on the -udeb package instead (exactly what happens here.)
> >
> > From dh_makeshlibs(1):
> >
> >--add-udeb=udeb
> >Create an additional line for udebs in the shlibs file and
> > use udeb as the package name for udebs to depend on instead of the
> > regular library package.
> >
> > This can be confirmed with:
> >
> > $ pull-lp-debs -a amd64 libkmod2 bionic 24-1ubuntu3.2
> > $ pull-lp-debs -a amd64 libkmod2 bionic 24-1ubuntu3.3
> >
> > $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb
> > libkmod2-32-control
> > $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb
> > libkmod2-33-control
> >
> > $ cat libkmod2-32-control/shlibs
> > libkmod 2 libkmod2
> > udeb: libkmod 2 libkmod2-udeb
> >
> > $ cat libkmod2-33-control/shlibs
> > libkmod 2 libkmod2
> >
> > And according to systemd/debian/control file's entry for udev-udeb:
> >
> > Package: udev-udeb
> > ...
> > Depends: ${shlibs:Depends},
> > ${m
Re: [Sts-sponsors] [URGENT] Please review and sponsor LP1772556. This needs to make 18.04.5 LTS.
epends on libkmod2 shared library because of udevadm, for the kmod built-in. You may notice that even before the --add-udeb flag removal, libkmod2-udeb *did not* ship that shared library! I wondered how the installer worked. It DOES have that library in /lib/libkmod.so.2. And I have no idea where it pulled it from. I checked MANIFEST files, d-i build log, even download all udebs in bionic/bionic-updates, extracted, but nothing shipped it. This might be some d-i build magic, which I didn't look/find yet. Finally, I'm a bit tired to think now, so I'll give you the ball for now to play a bit on considerations of 1) should this really be fixed before release for ISO, or just network installer is OK? and more fun in 2) how to properly fix this :) Thanks and have a great weekend! P.S.: I'm attaching my hacky notes about this today, in case it might help. On Fri, Jul 24, 2020 at 7:27 PM Mauricio Oliveira wrote: > > Matthew, > > By the way, per the SF case, the customer uses the network install method. > This can be fixed post-release, as SRUs to debian-installer will > produce new netboot images. > > Hopefully they (and other people) don't plan to try to use HTTPS on > the _ISO_ installer? > The ISO image is what is more strictly tied to the release date. > I'm not sure how much that scenario makes sense. > (there may be the case of trying to use HTTPS for the ISO installer to > download updates though?) > > I'm saying this because this is now (of course!) heading into systemd :-) > specifically the dependencies of the udev-udeb package. And that may > be just an adventure > to try to fix / SRU before release date. :) > > I'll give more details later. > > cheers, > > > On Fri, Jul 24, 2020 at 6:30 PM Mauricio Oliveira > wrote: > > > > Definitely looking at it right now. :) > > > > The debootstrap portion is OK. However, > > > > there's a PPA build error with the required rebuild of d-i in Bionic > > (not on Focal -- there's always fun on the releases we actually need!) > > due to udev-udeb changing dependencies from libkmod2-udeb to libkmod2 > > (non-udeb), which I just tracked down to kmod 24-1ubuntu3.3. > > > > I'll provide a write up on the LP bug (and mention internally in SF > > case) and hopefully it should be relatively simple to fix. > > > > As mentioned, debootstrap looks good; so I'll move that one soon. > > > > cheers, > > > > On Fri, Jul 24, 2020 at 6:25 PM Dan Streetman > > wrote: > > > > > > Hi Matthew, > > > > > > As @mfo has done work in this (installer image) area before (LP: > > > #1807023) I asked him to take a look; I'm cc'ing our sts sponsors > > > email list (which includes Mauricio) also. > > > > > > I think he's handling the sponsoring, so hopefully it'll make it for > > > the point release! > > > > > > Thanks! > > > > > > On Fri, Jul 24, 2020 at 1:14 AM Matthew Ruffell > > > wrote: > > > > > > > > Hi Dan and Eric, > > > > > > > > [URGENT] Please review and sponsor LP1772556. This needs to make > > > > 18.04.5 LTS. > > > > > > > > https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1772556 > > > > > > > > I have written to Lukasz Zemczak and made him aware of this bug, and I > > > > have also > > > > asked him to review and sponsor the debdiffs, since he was the last to > > > > modify > > > > debootstrap in Bionic, and is also in charge of producing 18.04.5 LTS > > > > images. > > > > > > > > I haven't heard back from Lukasz though. I emailed him on my Wednesday, > > > > and > > > > on my Thursday. > > > > > > > > Could you please maybe ping Lukasz during your day to make sure he got > > > > my email? > > > > > > > > The debdiffs in the LP bug are kinda weird. debootstrap uses "3.0 > > > > (native)" > > > > instead of "3.0 (quilt)", and the debdiff seems to take diffs of all > > > > the ubuntu > > > > releases, even though they are all symlinks to a single file that got > > > > changed, > > > > which is "gutsy". > > > > > > > > Anyway, please nudge Lukasz, or sponsor my debdiffs. Konica Minolta > > > > filed a > > > > L2 about this in SF289200, and it needs to make 18.04.5 LTS or it will > > > > never be > > > > fixed. > > > > > > > > Thanks! > > > > Matthew > > > > > > -- > > > Mailing list: https://launchpad.net/~sts-sponsors > > > Post to : sts-sponsors@lists.launchpad.net > > > Unsubscribe : https://launchpad.net/~sts-sponsors > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > -- > > Mauricio Faria de Oliveira > > > > -- > Mauricio Faria de Oliveira -- Mauricio Faria de Oliveira 0724 Description: Binary data -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] [URGENT] Please review and sponsor LP1772556. This needs to make 18.04.5 LTS.
Matthew, By the way, per the SF case, the customer uses the network install method. This can be fixed post-release, as SRUs to debian-installer will produce new netboot images. Hopefully they (and other people) don't plan to try to use HTTPS on the _ISO_ installer? The ISO image is what is more strictly tied to the release date. I'm not sure how much that scenario makes sense. (there may be the case of trying to use HTTPS for the ISO installer to download updates though?) I'm saying this because this is now (of course!) heading into systemd :-) specifically the dependencies of the udev-udeb package. And that may be just an adventure to try to fix / SRU before release date. :) I'll give more details later. cheers, On Fri, Jul 24, 2020 at 6:30 PM Mauricio Oliveira wrote: > > Definitely looking at it right now. :) > > The debootstrap portion is OK. However, > > there's a PPA build error with the required rebuild of d-i in Bionic > (not on Focal -- there's always fun on the releases we actually need!) > due to udev-udeb changing dependencies from libkmod2-udeb to libkmod2 > (non-udeb), which I just tracked down to kmod 24-1ubuntu3.3. > > I'll provide a write up on the LP bug (and mention internally in SF > case) and hopefully it should be relatively simple to fix. > > As mentioned, debootstrap looks good; so I'll move that one soon. > > cheers, > > On Fri, Jul 24, 2020 at 6:25 PM Dan Streetman > wrote: > > > > Hi Matthew, > > > > As @mfo has done work in this (installer image) area before (LP: > > #1807023) I asked him to take a look; I'm cc'ing our sts sponsors > > email list (which includes Mauricio) also. > > > > I think he's handling the sponsoring, so hopefully it'll make it for > > the point release! > > > > Thanks! > > > > On Fri, Jul 24, 2020 at 1:14 AM Matthew Ruffell > > wrote: > > > > > > Hi Dan and Eric, > > > > > > [URGENT] Please review and sponsor LP1772556. This needs to make 18.04.5 > > > LTS. > > > > > > https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1772556 > > > > > > I have written to Lukasz Zemczak and made him aware of this bug, and I > > > have also > > > asked him to review and sponsor the debdiffs, since he was the last to > > > modify > > > debootstrap in Bionic, and is also in charge of producing 18.04.5 LTS > > > images. > > > > > > I haven't heard back from Lukasz though. I emailed him on my Wednesday, > > > and > > > on my Thursday. > > > > > > Could you please maybe ping Lukasz during your day to make sure he got my > > > email? > > > > > > The debdiffs in the LP bug are kinda weird. debootstrap uses "3.0 > > > (native)" > > > instead of "3.0 (quilt)", and the debdiff seems to take diffs of all the > > > ubuntu > > > releases, even though they are all symlinks to a single file that got > > > changed, > > > which is "gutsy". > > > > > > Anyway, please nudge Lukasz, or sponsor my debdiffs. Konica Minolta filed > > > a > > > L2 about this in SF289200, and it needs to make 18.04.5 LTS or it will > > > never be > > > fixed. > > > > > > Thanks! > > > Matthew > > > > -- > > Mailing list: https://launchpad.net/~sts-sponsors > > Post to : sts-sponsors@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~sts-sponsors > > More help : https://help.launchpad.net/ListHelp > > > > -- > Mauricio Faria de Oliveira -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] [URGENT] Please review and sponsor LP1772556. This needs to make 18.04.5 LTS.
Definitely looking at it right now. :) The debootstrap portion is OK. However, there's a PPA build error with the required rebuild of d-i in Bionic (not on Focal -- there's always fun on the releases we actually need!) due to udev-udeb changing dependencies from libkmod2-udeb to libkmod2 (non-udeb), which I just tracked down to kmod 24-1ubuntu3.3. I'll provide a write up on the LP bug (and mention internally in SF case) and hopefully it should be relatively simple to fix. As mentioned, debootstrap looks good; so I'll move that one soon. cheers, On Fri, Jul 24, 2020 at 6:25 PM Dan Streetman wrote: > > Hi Matthew, > > As @mfo has done work in this (installer image) area before (LP: > #1807023) I asked him to take a look; I'm cc'ing our sts sponsors > email list (which includes Mauricio) also. > > I think he's handling the sponsoring, so hopefully it'll make it for > the point release! > > Thanks! > > On Fri, Jul 24, 2020 at 1:14 AM Matthew Ruffell > wrote: > > > > Hi Dan and Eric, > > > > [URGENT] Please review and sponsor LP1772556. This needs to make 18.04.5 > > LTS. > > > > https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1772556 > > > > I have written to Lukasz Zemczak and made him aware of this bug, and I have > > also > > asked him to review and sponsor the debdiffs, since he was the last to > > modify > > debootstrap in Bionic, and is also in charge of producing 18.04.5 LTS > > images. > > > > I haven't heard back from Lukasz though. I emailed him on my Wednesday, and > > on my Thursday. > > > > Could you please maybe ping Lukasz during your day to make sure he got my > > email? > > > > The debdiffs in the LP bug are kinda weird. debootstrap uses "3.0 (native)" > > instead of "3.0 (quilt)", and the debdiff seems to take diffs of all the > > ubuntu > > releases, even though they are all symlinks to a single file that got > > changed, > > which is "gutsy". > > > > Anyway, please nudge Lukasz, or sponsor my debdiffs. Konica Minolta filed a > > L2 about this in SF289200, and it needs to make 18.04.5 LTS or it will > > never be > > fixed. > > > > Thanks! > > Matthew > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] easy bugs for seyeongkim to take
Thought? Yes, that sounds like a great Friday night! On Mon, Mar 30, 2020 at 10:34 AM Eric Desrochers wrote: > > I like "sts-sponsor-volunteer" > > Mauricio, your concern about skill levels make a lot of sense. > Note to myself, don't pick tag name on Friday night without thinking too much > about it while watching Star Wars with the kids. ;) > > Thought ? > > Eric > > On Mon, Mar 30, 2020 at 7:08 AM Mauricio Oliveira > wrote: >> >> I do like the tag idea too. >> >> However, I think we should not use wording associated with skill >> levels (no matter how great and cool padawan is :-) to avoid the >> impression a bug requires less skill from the assignee to handle it >> (even though it may be the case, technically.) >> >> If that makes sense, perhaps tags like "sts-sponsor-volunteer" or >> "sts-sponsor-help" indicate a more proactive attitude from the person >> willing to take it. >> >> Then a search link for the tag, with a banner like "We need you for >> SRUs!" (lol, just kidding) prompting people to volunteer for >> fixes/SRUs to help with their own review/sponsoring practice, would >> help! :-) >> >> cheers, >> >> On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers >> wrote: >> > >> > I like the tag idea. What about "sts-sponsor-padawan" ? >> > >> > On Fri, Mar 27, 2020 at 5:19 PM Dan Streetman >> > wrote: >> >> >> >> going thru my old watched bugs, here are some bugs that should be easy >> >> to handle. Maybe we should figure out a LP bug tag to use for bugs >> >> that we find that are good for potential sponsors, like seyeongkim, to >> >> take? >> >> >> >> https://bugs.launchpad.net/ubuntu/bionic/+source/nvme-cli/+bug/1800544 >> >> -super easy bug >> >> >> >> https://bugs.launchpad.net/ubuntu/bionic/+source/python-etcd3gw/+bug/1820083 >> >> -the actual patch is trivial, but this needs fixing in debian as well >> >> and setting up a reproducer to verify might be difficult. This >> >> originally came from a case from Bloomberg, so setuid might be able to >> >> help with reproducer and/or verification. >> >> >> >> https://bugs.launchpad.net/ubuntu/xenial/+source/drbd-utils/+bug/1673255 >> >> -i have not actually looked at this one in a long time, so i'm not >> >> sure if it is still needed, but should be easy enough to check if it's >> >> still needed, and if so then it should be easy to patch >> >> >> >> -- >> >> Mailing list: https://launchpad.net/~sts-sponsors >> >> Post to : sts-sponsors@lists.launchpad.net >> >> Unsubscribe : https://launchpad.net/~sts-sponsors >> >> More help : https://help.launchpad.net/ListHelp >> > >> > -- >> > Mailing list: https://launchpad.net/~sts-sponsors >> > Post to : sts-sponsors@lists.launchpad.net >> > Unsubscribe : https://launchpad.net/~sts-sponsors >> > More help : https://help.launchpad.net/ListHelp >> >> >> >> -- >> Mauricio Faria de Oliveira -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
Re: [Sts-sponsors] easy bugs for seyeongkim to take
I do like the tag idea too. However, I think we should not use wording associated with skill levels (no matter how great and cool padawan is :-) to avoid the impression a bug requires less skill from the assignee to handle it (even though it may be the case, technically.) If that makes sense, perhaps tags like "sts-sponsor-volunteer" or "sts-sponsor-help" indicate a more proactive attitude from the person willing to take it. Then a search link for the tag, with a banner like "We need you for SRUs!" (lol, just kidding) prompting people to volunteer for fixes/SRUs to help with their own review/sponsoring practice, would help! :-) cheers, On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers wrote: > > I like the tag idea. What about "sts-sponsor-padawan" ? > > On Fri, Mar 27, 2020 at 5:19 PM Dan Streetman > wrote: >> >> going thru my old watched bugs, here are some bugs that should be easy >> to handle. Maybe we should figure out a LP bug tag to use for bugs >> that we find that are good for potential sponsors, like seyeongkim, to >> take? >> >> https://bugs.launchpad.net/ubuntu/bionic/+source/nvme-cli/+bug/1800544 >> -super easy bug >> >> https://bugs.launchpad.net/ubuntu/bionic/+source/python-etcd3gw/+bug/1820083 >> -the actual patch is trivial, but this needs fixing in debian as well >> and setting up a reproducer to verify might be difficult. This >> originally came from a case from Bloomberg, so setuid might be able to >> help with reproducer and/or verification. >> >> https://bugs.launchpad.net/ubuntu/xenial/+source/drbd-utils/+bug/1673255 >> -i have not actually looked at this one in a long time, so i'm not >> sure if it is still needed, but should be easy enough to check if it's >> still needed, and if so then it should be easy to patch >> >> -- >> Mailing list: https://launchpad.net/~sts-sponsors >> Post to : sts-sponsors@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~sts-sponsors >> More help : https://help.launchpad.net/ListHelp > > -- > Mailing list: https://launchpad.net/~sts-sponsors > Post to : sts-sponsors@lists.launchpad.net > Unsubscribe : https://launchpad.net/~sts-sponsors > More help : https://help.launchpad.net/ListHelp -- Mauricio Faria de Oliveira -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
