Re: SRU Developer Application by Matthew Ruffell
Hello, On Tue, Aug 27, 2024 at 8:32 AM Matthew Ruffell wrote: > I have added my name to the DMB's agenda for the meeting on Monday 2024-09-30, > since I would like to apply for SRU Developer upload permissions. > > I selected 2024-09-30 due to sitting at 19:00 UTC, which is 07:00 +1 (Tuesday) > NZST, in my APAC timezone. I can't make any 04:00 NZST meetings unfortunately. > > Please review my SRU Developer application wiki page: > https://wiki.ubuntu.com/mruffell/SRUDeveloperApplication DMB unanimously voted in favor of Matthew's application. Please join me in welcoming Matthew as the newest member of the SRU dev team. Matthew, you should have all the ACL in order now, please let me know if you have any questions or concerns. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: PPU Application (s390-tools) by Frank Heimes
Hello, On Tue, Aug 6, 2024 at 9:13 PM Frank Heimes wrote: > I've added my application to the DMB's agenda for the meeting > on Monday 2024-08-19, since I would like to apply for PPU upload > rights for the s390-tools package(s). DMB unanimously voted in favor of Frank's application for s390-tools* PPU. Please join me in welcoming him as an Ubuntu member, too. Frank, you should have all the ACL in order now, please let me know if you have any questions or concerns. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Cloud-init PPU application by Alberto Contreras
Hello, On Wed, Sep 11, 2024 at 12:41 PM Alberto Contreras wrote: > As the meeting on 2024-09-30 did not happen, I rescheduled > my application for 2024-09-16. I hope that is alright. DMB unanimously voted in favor of Alberto's application for cloud-init PPU. Please join me in welcoming him as an Ubuntu member, too. Alberto, you should have all the ACL in order now, please let me know if you have any questions or concerns. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Reminder of temporary jammy-updates freeze for 22.04.5
Hello everyone, Just a quick reminder that for the duration of the point release preparation (that is till the end of this week) the jammy-updates pocket will stay frozen and will only release SRUs whenever they're necessary for the .5 milestone. Thank you! On behalf of the Ubuntu Release Team, Utkarsh Gupta -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Requesting help/no response to pings
Hey, On Tue, Aug 27, 2024 at 12:29 PM Christian Ehrhardt wrote: > - Release team: I asked utkarsh2102 and his management chain, > and they donated his time for Tue/Wed/Thu. > Thanks to his team for spending his time - it is important to us! Just to summarize my involvement in the last couple of days - ### 24.10 - Oracular Feature Freeze - Assessed all the FFe in the backlog - over 20 of them. - Most of them have been approved but I've asked for more information. - If you're someone who filed an FFe, please take a look. - If by chance your FFe slipped through, please reach out to me. - Sponsored a few uploads for fellow contributors. - Sync'd a package as requested. - Added hints for lxqt qt6 transition for RikMills. - Helped with some other transitions ongoing. - Triggered rebuild for Edubuntu on Erich's request. ### 24.04.1 - Noble point release I assisted Lukasz for the Noble point release with the following: - Checking phased updates. Raising questions when things look "not good". :) - Analyzing package diffs for each participating flavour. - Assisting w/ riscv64 testing - thanks Christian and Lukas. - Updating wiki. - Pinged IS to clear content-cache for changelogs*. - Moderating mail on ubuntu-announce@. - Disabling the SRU freeze. - Assisting flavours with their testing - thanks arraybolt3 for Ubuntu Unity & MATE tests. - And all the other small items here and there. ### 22.04.5 - Jammy point release Given how strenuous Noble point release was, I wanted to look for blockers and resolve them ahead of Jammy point release, scheduled on 12th September. - Updating wiki. - Assisting Mate with cd-boot-images-* along w/ Christian, Andreas and Robie. - And all the other small items here and there. ### Release/DMB I also assisted a few people blocked who were blocked for things ACL wise by adding packages to packageset - - Added 3 packages to kubuntu packageset as requested by Scarlett. - Added 15 packages to kernel-dkma packageset as requested by Timo. - Added 4 packages to kernel packageset as requested by Timo. Let me know if I missed anything. Hope it helped & unblocked a bunch of things. :) - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 maintenance report
Hello,
Last week was an interesting week of +1 maintenance - glibc & ruby3.3
transition, clogged builders & queues, firewall misconfiguration for
autopkgtest runners, and so on.
Anyway, the good thing is that the misconfiguration has been fixed and
the builders are not clogged anymore. Hugs to the QA team. :)
Read on for the my week of +1 maintenance -
retrying-autopkgtest-regressions
Throughout the week, with the availability of the runners, I kept
retrying autopkgtest regressions (105+92+71+21 tests triggered).
I also triggered some migration-reference/0 tests for those that still
failed (73+24 tests triggered).
livecd-rootfs/libpff
Whilst I was focused on the devel uploads, ensuring livecd-rootfs/2.765.46
passes all autopkgtests in Jammy was crucial. The s390x tests were failing
because it couldn't open the ~ubuntu-archive/seeds/ubuntu.jammy/STRUCTURE,
apparently. With further debugging, it appeared that libpff was also affected
the same way on s390x for Oracular, amongst other packages. And further
conversations with the colleagues revealed that is was a firewall
misconfiguration for s390x autopkgtest runners in the bos03 region. This
was resolved by the QA team and on re-triggering, things are now passing!
On another note, I also sponsored an upload[0] of livecd-rootfs for Oracular.
ruby3.3 transition
==
With my Release team hat on, I gave a go-ahead[1] to the Server team to start
the Ruby 3.3 transition. This meant some additional re-triggers of builds
and autopkgtest of various Ruby libraries. Most needed the right set of
triggers and seemed to be passing but a lot of them still need help!
Those who are on +1, please consider helping -
https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#ruby-defaults.
chrony/ruby-sdbm/ruby3.3
We hit an interesting situation with the upload of chrony to Oracular, which
got entangled with the ongoing Ruby transition. One of the Ruby modules
wasn't rebuilt with the right libruby version and therefore the chrony builds
were failing as it was expecting libruby < 3.3. However, after a long
conversation with Andreas and Lucas around this, the rebuilds went through
and chrony built just fine with them. Chrony, in fact, migrated to the
-release pocket, too.
FTBFS of ruby3.3 on ppc64el is a different story altogether. :)
gdisk
=
LP: #2039594 was reported for gdisk - unexpected behavior with decimal point
in partition size specification. This looked like a bug that upstream fixed
so I was going to forward it to Debian but the maintainer was ready with
the new upstream version upload, which sync'd in Oracular timely and therefore
this bug is fixed. It'd be good to SRU the patch to stable releases though. :)
node-{ssri,yarnkpkg}
This looks like a fallout from the merge we did in Ubuntu - tests seem to
pass in Debian but failing in Ubuntu for all the architectures - looks like
it's trying to access the internet. I've pinged Zixing to take a look and
drive this further. node-ssri can also get a pair of eyes once node-yarnpkg
is unblocked. I've indicated the same to Zixing.
ikwiki
==
Per Graham's mail about the FTBFS in Oracular
(cf:
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20241209-oracular-oracular.html),
I looked at ikiwiki as it was
also a problem on the Debian side. The bug report had the root cause and a
patch associated with it. Simon uploaded the fix by the time I completed my
testing so I sync'd the version from unstable to Oracular.
ruby-xmlparser
==
Per Graham's mail about the FTBFS in Oracular
(cf:
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20241209-oracular-oracular.html),
I looked at ruby-xmlparser,
which was FTBFS'ing with GCC-14. The patch was available and simple, so I
uploaded it to Debian and sync'd it to Oracular.
zlib
The build of 1:1.3.dfsg+really1.3.1-1ubuntu1 upload was failing on s390x
and some reverse-{build-}dependencies had their autopkgtest failing on
different architectures. I triggered the build and the autopkgtest with
right triggers and they're passing. 3 packages still fail on s390x - osmpbf,
snapd, and zfs-linux. Those are on +1 this week, can you take over, please? :)
simple re-triggers
==
There were few packages that needed simple rebuilds or autopkgtest re-triggers
(w/ triggers) to get them going -
- python-sphinx-contributors - in -release now.
- ugrep & misspell-fixer - in -release now.
- golang-github-charmbracelet-lipgloss - in -release now.
- blinkpy - in -release now.
- persistent-cache-cpp - in -release now.
- intel-microcode & check-dfsg-status - both in -release now.
- libayatana-common - in -release now.
- calmzip - not blocking ocaml anymore.
- govee-ble - in -release now.
- libtext-csv-xs-perl & restfuldb - in -release now.
- and more which I couldn't keep up with. :)
assisting other
Re: +1 maintenance report
Hey, On Fri, Jul 12, 2024 at 5:50 PM Robie Basak wrote: > Looking at further rust issues, rust-chrono seems blocked on some > regressions in dep8 for rust-schemars and rust-serde-with. It looks like > some test runs at least are running out of disk space now, so I prepared > and submitted a merge proposal for these to be added to the big_packages > list. Right, thanks. I'm still waiting for you to get back with the result of retries and other bits before we can merge it. :) - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Motu Application: Sudip Mukherjee
Hey, On Fri, May 3, 2024 at 8:38 PM Sudip Mukherjee wrote: > I hereby apply to become an Ubuntu Motu. > > You can find my application at: > > https://wiki.ubuntu.com/sudipmuk/MotuApplication DMB unanimously voted in favor of Sudip's application. Please join me in welcoming Sudip as the newest member of the MOTU team. Sudip, you should have all the ACL in order now, please let me know if you have any questions or concerns. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Oracular Oriole is now open for development
We're pleased to announce that Oracular Oriole is now open for development. auto-sync has been enabled and will run soon. As usual, we expect a large influx of builds and autopkgtests in this initial period, which will cause delays. Please help fixing any breakage that occurs. The release schedule can be found at https://discourse.ubuntu.com/t/oracular-oriole-release-schedule/36460 Please see the release schedule page for information about any major changes and for all milestone dates. Please check your uploads in a oracular chroot. See [1] or [2] for details on how to set up such a development chroot. You can subscribe to the oracular-changes mailing list [3] to receive the changelog entry of package uploads to the archive for oracular. [1] https://wiki.ubuntu.com/SimpleSbuild [2] https://wiki.ubuntu.com/DebootstrapChroot [3] https://lists.ubuntu.com/mailman/listinfo/oracular-changes On behalf of the Ubuntu Release Team, Utkarsh Gupta -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report
Hi Pushkar, On Wed, Feb 7, 2024 at 6:17 AM Pushkar Kulkarni wrote: > I was on my first +1 maintenance shift last week. I began the week > with some reading of +1 report of the past shifts, to get a basic idea > of what to do and how to do it. Nice, thanks for your good work and excellent report. I have a few comments below. > === ccache === > Autopkgtests fail because a new upstream change causes uncaught > exceptions which bring down the ccache utility with a SIGABRT. > Interestingly, the test which core-dumps is deemed as passed, but the > core-dump messages on stderr cause tests to fail. > > I started a discussion on the upstream repository, which was later > accepted as a bug [3] and there is a fix committed. The upstream > maintainer, who also happens to maintain the Debian package mentioned > on the Debian bug report [4] that the fix will be out through a new > upstream release next week. Just in case, it doesn't happen, I have a > merge-proposal with a work-around [5]. > > [3] https://github.com/ccache/ccache/discussions/1390 > [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062810 > [5] > https://code.launchpad.net/~pushkarnk/ubuntu/+source/ccache/+git/ccache/+merge/459639 I've added a comment on the MP. But since the package is already manually sync'd now, can you reject the MP, please? > === asterisk-espeak === > This package represents an asterisk module related to speech > synthesis. The failing test just tried to load the module into > asterisk, but failed. I have an Ubuntu merge proposal [6] as well as a > Debian merge request [7] for this. Please read the connected bug > reports for more details. > > [6] > https://code.launchpad.net/~pushkarnk/ubuntu/+source/asterisk-espeak/+git/asterisk-espeak/+merge/459769 > [7] https://salsa.debian.org/pkg-voip-team/asterisk-espeak/-/merge_requests/2 Paride has left a comment on the bug and the MP, please take a look whenever you have a sec. > === freedombox/bootstrapform === > The freedombox package depends on bootstrapform. Autopkgtests of the > former fail because the latter imports distutils. I did a Debian MR > [15] to replace distutils.StrictVersion with packaging.Version. But I > now see bootstrapform also failing, independent of this merge request, > with Python 3.12. Test pipelines on the MR are failing and this needs > more investigation. > > [15] > https://salsa.debian.org/freedombox-team/python-django-bootstrap-form/-/merge_requests/4 I wonder what upstream thinks about it. Also it'd be nice to have this forwarded to upstream and get a review before landing it. > === glueviz === > This needs a migration from package "imp", which was purged in Python > 3.12, to package "importlib". I submitted a Debian merge request [16] > for it. > > [16] https://salsa.debian.org/debian-astro-team/glue/-/merge_requests/3 I think it'd be super helpful if this is done upstream and not downstream. This way we can avoid carrying patches and just get the new upstream version. > === factory-boy === > An autopkgtest of factory-boy, evidently picks up zero tests to run, > at least since the past four releases. In Python 3.12, the behaviour > of package "unittest" was modified to return failure (exit code 5) if > zero tests were selected. As a result, the factory-boy autopkgtest > began failing. I submitted a Debian merge request [17]. > > [17] > https://salsa.debian.org/python-team/packages/factory-boy/-/merge_requests/1 I don't think disabling the tests would be the right approach here. The correct and the ideal fix would be to get the tests running. :) Let me know if you have any questions or concerns; many thanks. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Noble Numbat is now open for development
We're pleased to announce that Noble Numbat is now open for development. Auto-sync has been enabled and will run soon. As usual, we expect a large influx of builds and autopkgtests in this initial period, which will cause delays. Please help with fixing any breakage that occurs. The release schedule can be found at: https://discourse.ubuntu.com/t/noble-numbat-release-schedule/ Please check your uploads in a noble chroot. See [1] or [2] for details on how to set up such a development chroot. Please see the release schedule page for information about any major changes and for all milestone dates. On behalf of the Ubuntu Release team, Utkarsh Gupta --- [1] https://wiki.ubuntu.com/SimpleSbuild [2] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Merge ubuntu-motu@lists into ubuntu-devel-discuss@lists?
Hey, On Wed, Oct 18, 2023 at 1:44 AM Steve Langasek wrote: > I'd therefore like to propose we close this mailing list and forward the > address on to ubuntu-devel-disc...@lists.ubuntu.com, which at least has a > larger subscriber base and is more likely to result in users getting help > with their questions. > > Opinions? I'd mostly agree, it'd only make sense. Perhaps we could set a redirect or something other than just stopping the list altogether? But also, what's the harm in keeping the other one alive for posterity? - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Contributing Developer and livecd-rootfs Per Package Upload rights application: Phil Roche (philroche)
Hey, On Thu, Sep 21, 2023 at 4:38 PM Phil Roche wrote: > I am applying to become a Contributing Developer and for livecd-rootfs Per > Package Upload rights: > https://wiki.ubuntu.com/philroche/ContributingDeveloperAndPerPackageUploadApplication In the last meeting, DMB unanimously voted in favor of Phil's PPU application. Please welcome Phil as the newest member of the Ubuntu uploader's team. \o/ Phil, I've added you to ~ubuntu-dev and your ACL for livecd-rootfs is adjusted as well. Whilst you have the upload rights now, please be mindful of the freezes, et al, as discussed during the meeting. I am always around to help with that. ;) Should you have any questions or concerns, please do not hesitate in reaching out. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Duplicate Requests in autopkgtest-cloud
Hi Tim, On Thu, Jul 27, 2023 at 4:01 PM Tim Andersson wrote: > In the Ubuntu QA team we recently made and deployed a change > which now makes it impossible to queue duplicate requests. Super, this is great stuff! However, this isn't working as advertised. Or perhaps I've gotten it wrong. But I wanted to trigger 'livecd-rootfs/23.10.12' for mantic/ppc64el and I did but just to try the whole duplicating thing, I did another time, and it did again. On the third time, however, it said it's already queued. Upon checking https://autopkgtest.ubuntu.com/running, I can confirm that the autopkgtest is running twice, triggered 9 seconds apart. Is that anyhow expected? - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Core Dev application: Nick Rosbrook (enr0n)
Hello, On Sat, Jun 17, 2023 at 2:08 AM Nick Rosbrook wrote: > I am applying to become a Core Dev: > https://wiki.ubuntu.com/enr0n/CoreDeveloperApplication > > I have added myself to the agenda for the 2023-07-10 meeting: During the meeting, the DMB unanimously voted in favor of Nick's application. Please welcome Nick as the newest member of Ubuntu Core Developer. Congratulations, Nick. I've adjusted your ACL and you're all set. Please let me know if you have any questions or concerns. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: PPU upload rights application for sosreport
Hello again, On Fri, Jun 30, 2023 at 2:02 PM Utkarsh Gupta wrote: > Nikhil, I've added you to ~ubuntu-dev and a TB member shall soon > adjust ACL for the sosreport package. This has been done by Robie already. You're good to go now. :) - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: PPU upload rights application for sosreport
Hello, On Mon, May 29, 2023 at 2:06 PM Nikhil Kshirsagar wrote: > I am the maintainer of the Ubuntu sosreport package > (https://launchpad.net/ubuntu/+source/sosreport/) since the last one > year. > > I'd like to apply for PPU upload rights for sosreport. This is my > application - > https://wiki.ubuntu.com/nkshirsagar/UbuntuPerPackageUploaderApplication In the last meeting, DMB unanimously voted in favor of Nikhil's PPU application. Please welcome Nikhil as the newest member of the Ubuntu uploader's team. \o/ Nikhil, I've added you to ~ubuntu-dev and a TB member shall soon adjust ACL for the sosreport package. Should you have any questions or concerns, please do not hesitate in reaching out. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: PPU upload rights application for firmware test suite(FWTS)
Hello, On Tue, Feb 7, 2023 at 1:21 PM ivanhu wrote: > I am the developer and maintainer of firmware test suite(FWTS) > for more than ten years, need to release FWTS every two month. > > https://wiki.ubuntu.com/FirmwareTestSuite > > So, I'd like to apply the PPU upload rights for firmware test suite(FWTS). After assessing Ivan's application, DMB voted in his favor and thus granted him the PPU rights for the fwts package (with some suggestions and remarks). Congratulations and thanks for all your work! :) Utkarsh, On behalf of DMB -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report
Hi Nick, On Mon, Feb 13, 2023 at 4:18 AM Nick Rosbrook wrote: > ### openlibm FTBFS on armhf > > LP: #2006501 > > Debian already has a fix committed, but has not released for a few > months now. I verified the fix works for us, and proposed uploading > the fix with a `maysync` version to allow the next Debian upload to > autosync. I am still looking for a sponsor for this patch. As promised before and discussed on #ubuntu-devel, I've sponsored your upload. ;) - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: MOTU application: Frank Heimes (continuation)
Hello, On Thu, Aug 25, 2022 at 1:20 AM Frank Heimes wrote: > Dear DMB, > I would like to continue my MOTU application on Mo Sept the 5th. > At the last meeting (2022-07-25) we were late and didn't had enough time to > finish. > > I've also added myself to the next DMB agenda. After some back and forth and finally voting via the mailing list (due to lack of quorum during the meeting), DMB voted in Frank's favor and thus we'd like to welcome Frank to the MOTU family. Congratulations and welcome aboard. :) Utkarsh, On behalf of DMB -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: MOTU application
Hello, On Tue, Nov 15, 2022 at 2:51 PM Dave Jones wrote: > Having climbed into my TARDIS, I am applying for MOTU membership ... erm > ... yesterday. My application is available at > https://wiki.ubuntu.com/DaveJones/MOTUApplication and I have added the > topic to the agenda of the 14th November meeting which is *definitely* > in the future (the timestamp on this email is obviously a glitch in the > space-time continuum). DMB voted in Dave's favor and thus we'd like to welcome Dave to the MOTU family. Congratulations and welcome aboard. :) Utkarsh, On behalf of DMB -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report
Hey, On Mon, Sep 12, 2022 at 8:20 PM Lucas Kanashiro wrote: > # rails > > It is stuck in -proposed because the new version contains a fix for > CVE-2022-32224 which introduced a behavior change in the way > hashes are serialized. I filed LP: #1988782 and tagged it as > update-excuse. Utkarsh as one of the Debian maintainers will be > pushing this forward. I looked at it during my +1 as well. I fixed it in Debian sid and that has migrated now. Whilst trying to syncpackage today, I found out that it was already sync'd in by someone else so just waiting for the test results and will close the bug once it has migrated here. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Call for testing: 22.04.1 release candidate images ready!
Hi Lukasz, On Thu, Aug 11, 2022 at 2:55 PM Utkarsh Gupta wrote: > > I'd be happy to do some install testing of Mate if someone can provide > > me with a correct link. In the mean time I'll go test Kylin. > > Did you get around to testing Kylin? How'd it go? I did a smoke test for Kylin, too. It went well. I could do the basic stuff - change resolution, launch browser, et al. I did some extra random stuff to be sure as well. :) So we're good to go now. Let's release .1! \o/ - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Call for testing: 22.04.1 release candidate images ready!
Hi Heather, On Wed, Aug 3, 2022 at 11:57 PM Heather Ellsworth wrote: > I'd be happy to do some install testing of Mate if someone can provide > me with a correct link. In the mean time I'll go test Kylin. Did you get around to testing Kylin? How'd it go? - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Log-rotation doesn't work for catalina.out in src:tomcat9 as intended
Hi Andreas, On Thu, May 12, 2022 at 6:17 PM Andreas Hasenack wrote: > This reminded me that frr is also affected by this: > https://bugs.launchpad.net/ubuntu/+source/frr/+bug/1958162 > > And frr is in main now. I'll work on it. Ah. D'you think there could be somewhat of a common solution here? Or are each of them going to be very different from each other? - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Log-rotation doesn't work for catalina.out in src:tomcat9 as intended
Hello, A few weeks ago, LP: #1964881/tomcat9 was opened by Evren (also CC'd here), mentioning that Logging/Log rotation does not work for catalina.out as expected. Since this was in sync w/ Debian, we forwarded this there via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008668. If you follow the thread, you'll see two observations: a) This is Ubuntu-specific because of the changes introduced in src:rsyslog over a decade ago, which basically doesn't let it run as root, which is where I think the problem(s) started to originate. However, I am kinda stumped that it took more than 13 years to get to this bug. :) b) Markus (an implicit co-maintainer of tomcat* in Debian) said that the approach to fix the same, whilst being Ubuntu-specific, doesn't make sense to him. So since I am not very well-versed with src:tomcat*, I am confused about what we should do here then. What do y'all think? I think I am convinced that if a) is true, then this will indeed be a delta which we'll have to maintain forever (or at least until we re-sync rsyslog :)). What do you think should be the correct path? If there's someone who has more experience with the package, can they take a look? - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report
Hiya, On Mon, Jan 24, 2022 at 9:51 PM Utkarsh Gupta wrote: > ## node-pbkdf2 (LP: #191828) > > The tests have been failing on s390x because of it > being big-endian but I've been in touch with people > on the Debian side (we're all part of the JS team) > and we're trying to fix this. The upstream is dead > but we've proposed a first patch, which whilst doesn't > fully resolve the issue, it brings us a lot closer > to fix the issue at hand. I'll keep working with > them and keep updating the bug as and when we have > an update. This has now been fixed via 3.1.2-2 and the package has migrated. \o/ - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 maintenance report
Hello, Amidst the mid-cycle sprints and being partly sick, I was on +1 last week and did the following things: ## node-pbkdf2 (LP: #191828) The tests have been failing on s390x because of it being big-endian but I've been in touch with people on the Debian side (we're all part of the JS team) and we're trying to fix this. The upstream is dead but we've proposed a first patch, which whilst doesn't fully resolve the issue, it brings us a lot closer to fix the issue at hand. I'll keep working with them and keep updating the bug as and when we have an update. ## bagel One of the tests, ASD_DMRG, seemed to be failing on s390x but when asked upstream, that test is "meant to fail". Only by chance, it's failing on s390x for us, so as intended upstream, I've patched bagel to skip this test and everything seems to be working (and passing) in bagel/1.2.2-3ubuntu1. ## mat2 (debbug #1002418) src:mat2 was regressing with the new libimage-exiftool-perl upload, resulting in an AssertionError. This was already addressed upstream but not in Debian or Ubuntu. Since there was an RC bug (#1002418) open in Debian, I uploaded an NMU there and things are now fixed via the mat2/0.12.2-1.1 upload. ## ugrep src:ugrep was stuck in proposed migration as it was regressing src:forensics-extra on armhf. Simply re-triggering the package on armhf made it pass and src:ugrep has now migrated. ## esys-particles Both, Gianfranco and myself, took a look at this and the more we look at it, the crazier it gets. :) This seems to be working in Debian perfectly but somehow not on Ubuntu and the log says that it can't find the said modules and this is very much reproducible in an LXD container but we couldn't find what was up with that. We suspect that as the Python transition moves forward, this will settle on its own, with a simple re-trigger. So until then, we've left this as-is and will revisit later, towards the end of the cycle. ## ruby-fast-gettext (debbug #1002103) There seemed to be FTBFS due to two reasons - one, because of ruby3.0, related to tainting of code, and two, because of API change in rails 6. I was able to reproduce and fix them both via 2.0.3-1ubuntu2. Also, fixed the same in Debian via 2.0.3-2 and furthermore, sent the patch upstream via PR #136. ## python-sop src:python-sop was stuck in proposed migration as it was failing autopkgtest on armhf. Simply re-triggering the package on armhf made it pass and src:python-sop has now migrated. ## cmark-gfm (LP: #1958235) This will probably be the highlight of my +1, heh. cmark-gfm/0.29.0.gfm.2-1, which got auto-sync'd from Debian was a soname bump and it started a transition. It also slipped the maintainer's eye and it resulted in breaking a handful of packages, namely, pandoc, pandoc-citeproc, blogliterately, gitit, and patat, at least. Christian noticed this immediately and opened the bug and asked me to TAL. I reverted the upstream version back to what it was to temporarily stop the (bad) transition and uploaded a fix via 0.29.0.gfm.2-1+really.0.29.0.gfm.0ubuntu1. Quite a version, I know. :) Meanwhile, this is being handled on the Debian side and I'll make this a sync again later next week. ## phpmyadmin (LP: #1955284) Two of the tests had been failing for so long on s390x in Debian and Ubuntu, both. Whilst Debian's failure doesn't prevent the migration, Ubuntu's does. These tests have a problem on 32-bit problem and I wrote a patch for upstream and it got accepted a few weeks back. However, now it looks like these tests don't really help with anything and are somewhat useless, we (I and upstream) have decided to drop this. As a result, I've dropped this in Ubuntu and uploaded a fix via 4:5.1.1+dfsg1-5ubuntu1. ## php-symfony-polyfill src:php-symfony-polyfill FTBFS'd with PHP 8.1. I added a patch as a delta since Debian hasn't yet reached that point of transition and uploaded a fix via 1.24.0-1ubuntu1. It now works well w/ PHP 8.1 and gets us closer to completing the transition. ## php-league-commonmark src:php-league-commonmark has a "risky" test that was failing on s390x which stopped the migration of php-symfony-polyfill upload. A couple of re-tries made it pass and so did php-symfony-polyfill. ## libmarc-xml-perl src:libxml-libxml-perl was stuck in proposed migration as it regressed src:libmarc-xml-perl. However, during the LHF, I investigated a bit more and Gregor uploaded a fix and I re-triggered the package with the right triggers and both, src:libxml-libxml-perl and src:libmarc-xml-perl have migrated. ## sdlgfx src:sdlgfx was stuck in proposed migration as it was regressing src:libalien-sdl-perl and src:libsdl-perl on armhf. Since I am also a part of the Perl team and I knew this was a false-positive, simply re-triggering made it pass and src:sdlgfx migrated to Jammy. ## libtap-parser-sourcehandler-pgtap-perl src:libtap-parser-sourcehandler-pgtap-perl was stuck in proposed migration as it was failing autopkgtest on armhf. Simply re-triggering th
Re: liburing1 -> liburing2 transition
Hello, On Fri, Dec 3, 2021 at 10:01 PM Paride Legovini wrote: > [...] > > Here the ball goes to the Archive Admins. Thank you for sorting out the libopenmpt bit. I wonder if an AA can TAL at LP: #1952918 for sorting out the fluidsynth issue? Dropping fluidsynth from -proposed and re-syncing it later looks like the best plausible solution to me. I'd be very happy to consider other alternatives, too. :) - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 Maintenance Report
Hi Graham, On Mon, Sep 27, 2021 at 6:14 PM Graham Inggs wrote: > I think I can answer this now. Previously, python-meshio was writing > and reading STL files in native byte order, so the STL test passed on > big-endian systems. However, the data should have been in > little-endian byte order [1], so python-meshio was creating invalid > STL binary files on big-endian systems. > > Upstream caused the files to be written in little-endian byte order in > commit 59a19d1. All that was missing was for the files to be read in > little-endian byte order as well. I submitted a PR and it was > accepted. Very well, thank you for the explanation! \o/ - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 Maintenance Report
Hello, On Thu, Sep 23, 2021 at 7:57 PM Graham Inggs wrote: > python-meshio > = > python-meshio's autopkgtest on s390x has been failing since 4.3.11-1. > I found bryceh had looked at this previously in LP: #1939057. I then > found utkarsh2102 had reported an issue upstream, so I left a link in > the LP bug. I was able to bisect and find the commit which broke the > test and left a comment in the upstream issue. Whilst working through this, do you happen to know "what" exactly happened? I took a look but unsure how things are now breaking in the s390x environment. - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: PHP 8.0 transition plan
Hello, On Wed, May 12, 2021 at 9:42 PM Bryce Harrington wrote: > For impish the server team will be transitioning PHP to 8.0 over the > coming weeks. (LP: #1927264) [0] After 3-4 weeks of continuous rebuilds, fixes, retriggers, and dealing w/ circular dependencies, php-defaults has finally migrated and php7.4 has been consequently removed, thereby marking the end of the PHP 8.0 transition! \o/ Many thanks to everybody involved, especially the Archive Admins, the Release team, et al. :) - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
(shadowed) +1 maintenance report
Hello, This week I partly shadowed Christian on his +1 maintenance. Whilst I don't have the core-dev powers yet, Christian & Gianfranco sponsored uploads & did re-triggers on my request. So a huge thanks to them! As Christian mentioned, transitions were actively being driven and things were already being looked at, so I decided to work on things which didn't get enough attention, hoping that my Ruby experience could help. :) Here's what I did: ### schleuder ### This has been lurking around since so long. The armhf failure isn't reproducible and passes locally everytime, even with different armhf setups. Passes in Debian, too. Since this has become so hard to debug & blocks other packages, added a hint[1] & has now migrated. [1]: https://code.launchpad.net/~utkarsh/britney/+git/britney/+merge/404025 ### ruby-httpclient ### ruby-httpclient had some HTTP_PROXY issues (which were LP builders specific) and some test_proxy_ssl which resulted in FTBFS randomly (cf: debbug #861456). We hit some in the past and decided to disable on the Debian side and not forward them because these work fine locally & only hangs in specific environments, more so in LP's builders. Anyhow, uploaded the fixed package, ruby-httpclient/2.8.3-3, to Debian which built fine on all architectures & the package migrated. ### ruby-gitlab-pg-query ### This package didn't build on any architecture (ever) because of FTBFS as it accesses the internet during the build (cf: debbug #981878). This was initially packaged because src:gitlab needed it but now gitlab has switched to using the original source, ruby-pg-query, and stopped relying on its fork, therefore, this isn't needed by any package anymore. Opened LP: #1931257, requesting its removal; thanks to Iain Lane for processing that. ### python-django-debug-toolbar ### Did a loop-rebuild on amd64 to ensure that it wasn't actually a legit failure. Asked Christian to re-trigger python-django-debug-toolbar/1:3.2.1-1 for amd64 and it passed & migrated. ### ruby-loofah ### The package is blocked by the regression induced in ruby-rails-html-santizier because of some API changes in ruby-loofah. The tests weren't adjusted and were recently patched upstream. Cherry-picking those patches makes it happy and so got it uploaded to Debian to avoid "delta"; thanks Hideki for doing that. Simultaneously, uploaded newer ruby-loofah, too, to Debian and both of them are happy. ruby-rails-html-sanitizer already migrated and ruby-loofah should soon do, too. Asked Gianfranco to re-trigger the tests (w/ triggers) on all architectures and it passed, as expected. ### ruby-stackprof | ruby-ferret | ruby-hiredis ### glibc had these three blockers^. The first two needed a re-trigger on amd64 & the last one needed a re-trigger on armhf. I did a loop-rebuild to ensure there are no legit failures, turns out there weren't. So I requested Gianfranco to do it for me & all of them passed & migrated. ### ruby-excon ### Long-due failure on s390x. Not reproducible; passes locally & also in a s390x canonistack VM. So opened an issue upstream, explaining the same, and added a hint[2]. Hopefully it will migrate soon. [2]: https://code.launchpad.net/~utkarsh/britney/+git/britney/+merge/404113 - u -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
