Re: Second Plucky Puffin test rebuild

2025-05-14 Thread Graham Inggs
The test rebuild is now finished for all components on riscv64. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250314-plucky-plucky.html -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubu

Re: +1 Maintenance Report

2025-04-09 Thread Graham Inggs
Thanks Utkarsh and Simon! On Wed, 9 Apr 2025 at 16:06, Utkarsh Gupta wrote: > > The new version of last-align also caused a regression in nanook, > > which was removed from Debian testing. I updated LP: #2103924 > > requesting removal of nanook. > > Thanks - RM'd nanook. But why is the bug also

+1 Maintenance Report

2025-04-07 Thread Graham Inggs
I was on +1 maintenance from 2025-04-01 until 2025-04-04. Below are the things I worked on. mariadb autopkgtests fails since DST change === This was mentioned by tjaalton on matrix. I scheduled migration-reference tests so that it would not block other pac

Re: Second Plucky Puffin test rebuild

2025-04-04 Thread Graham Inggs
On Tue, 25 Mar 2025 at 12:54, Matthias Klose wrote: > The second test rebuild of Plucky Puffin was started on March 19, 2024 > for all architectures and all components. The rebuild is finished for > the main component on all architectures except riscv64, and still > running for universe and multiv

Re: +1 Maintenance Report

2025-01-14 Thread Graham Inggs
On Tue, 14 Jan 2025 at 08:39, Sebastien Bacher wrote: > I've handled those requests now Thanks very much! I see most of them have migrated already, except repmgr and posgis needed some migration-reference/0 tests on armhf. I did start filing a bug for removal of postgresql-16 (LP: #2094797), bu

+1 Maintenance Report

2025-01-13 Thread Graham Inggs
I was on +1 maintenance from 2025-01-07 until 2025-01-10. Below are the things I worked on. retrying autopktest regressions === Due to the state of the autopgtests queues (amd64 having almost a week of backlog), I avoided mass retries, and instead manually retried some

Second Oracular Oriole test rebuild

2024-09-16 Thread Graham Inggs
The second test rebuild of Oracular Oriole was started on September 12, 2024 for all architectures and all components. The rebuild is finished for the main component on all architectures except riscv64, and is still running for universe and multiverse. Results (please also look at the superseded

First Oracular Oriole test rebuild

2024-08-14 Thread Graham Inggs
The first test rebuild of Oracular Oriole was started on August 12, 2024 for all architectures (except arm64 and armhf, due to capacity concerns), and all components. The rebuild is finished for the main component on all architectures except riscv64, and still running for universe and multiverse.

+1 Maintenance Report

2024-08-12 Thread Graham Inggs
I was on +1 maintenance from 2024-08-05 until 2024-08-09. Below are the things I worked on. retrying autopktest regressions === At the start of my shift, the autopkgtest queues were empty so I retried all autopkgtest regressions (876 tests triggered). Once these had

+1 Maintenance Report

2024-05-29 Thread Graham Inggs
I was on +1 maintenance from 2024-05-23 until 2024-25-29. Below are the things I worked on. The autopkgtest queues were completely empty following the Mardid sprint. I noticed the update_excuses report [1] still showed many running tests in various states. I was able to re-queue these using re

Re: Any hint how to fix python 3.11 pth files errors? (Was, First Noble Numbat test rebuild)

2024-01-12 Thread Graham Inggs
Hi Sébastien Both of those packages have FTBFS bugs filed in Debian [1][2] since a rebuild there in October 2023. I'd guess it was some change made in pybuild / dh-python. I don't recall seeing similar failures in any of the recent Python rebuilds happening in Ubuntu. I did ask in # debian-pyth

Re: Any hint how to fix python 3.11 pth files errors? (Was, First Noble Numbat test rebuild)

2024-01-11 Thread Graham Inggs
Hi Sébastien On Thu, 11 Jan 2024 at 15:59, Sebastien Bacher wrote: > I noticed that a bunch of the desktop failures are python 3.11 problems > similar to the one discussed in Would you name some of those packages please? Regards Graham -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.co

First Noble Numbat test rebuild

2024-01-02 Thread Graham Inggs
The first test rebuild of Noble Numbat was started on December 15, 2023 for all architectures, all components. The rebuild is finished for all architectures for the main component and still running for universe and multiverse on s390x and riscv64. There were some buildd issues with s390x, but we h

First Mantic Minotaur test rebuild

2023-09-06 Thread Graham Inggs
The first test rebuild of Mantic Minotaur was started on August 30, 2023 for all architectures, all components. The rebuild is finished for the main component on all architectures except riscv64, and still running for universe and multiverse. Results (please also look at the superseded builds) can

Question to flavours: touch-base on flavour participation for 23.10!

2023-05-03 Thread Graham Inggs
Hello flavours! As we do around the start of every new cycle, I am reaching out to all the current official Ubuntu flavours to confirm active participation in the upcoming Ubuntu release - 23.10. Working towards a release requires a lot of effort, so we'd like to make sure all the flavours are re

Mantic Minotaur is now open for development

2023-05-03 Thread Graham Inggs
We're pleased to announce that Mantic Minotaur 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 sc

+1 Maintenance Report

2023-04-17 Thread Graham Inggs
I was on +1 maintenance for the week of April 10-14. Below are the things I worked on. cataclysm-dda / eztrace / libretro-bsnes-mercury These packages FTBFS everywhere except armhf and risc64, which are the architectures where LTO is not enabled by

Second Lunar Lobster test rebuild

2023-03-28 Thread Graham Inggs
The second test rebuild of Lunar Lobster was started on March 24, 2023 for all architectures, all components. The rebuild is finished for the main component on all architectures except riscv64, and still running for universe/multiverse. Results (please also look at the superseded builds) can be fo

Lunar Lobster (23.04) Beta milestone reminder

2023-03-24 Thread Graham Inggs
Hello everyone! This is a gentle reminder about the nearing Beta milestone for Lunar Lobster (23.04) next week, along with the usual Beta Freeze on Monday. Please make sure to get as much as possible into the release pocket before that time - the Beta is usually a great occasion to test how things

+1 Maintenance Report

2023-01-23 Thread Graham Inggs
I was on +1 maintenance for the week of January 16-20. Below are the things I worked on. TL;DR see 'Packages still needing attention' at the bottom. Various syncs and merges I looked through Merge-o-Matic for universe and found several packages that would help with propos

First Lunar Lobster test rebuild

2023-01-06 Thread Graham Inggs
The first test rebuild of Lunar Lobster was started on December 15, 2022 for all architectures, all components. The rebuild is finished for all architectures for the main component and still running for universe and multiverse on riscv64. Thanks to everybody keeping the buildds going during the en

Second Kinetic Kudu test rebuild

2022-09-19 Thread Graham Inggs
The second test rebuild of Kinetic Kudu was started on September 14, 2022 for all architectures, all components. The rebuild is finished for the main component on all architectures, finished for universe/multiverse on amd64, i386 and ppc64el, and still running on the other architectures. Results (

+1 Maintenance Report

2022-09-13 Thread Graham Inggs
I was on +1 maintenance for the week of September 5-9. Below are the things I worked on. TL;DR see 'Package still in need of attention' at the bottom. r-cran-cppparallel == Reverse-dependencies of r-cran-cppparallel needed to be rebuilt against onetbb, but this was only possible a

+1 Maintenance Report

2022-06-28 Thread Graham Inggs
I was on +1 maintenance for the week of June 20-24. Below are the things I worked on. On Monday, I found many packages had FTBFS without logs, or failed to upload, and I retried these. On Tuesday, the autopkgtest queues were empty so I scheduled retries of all regressed autopkgtests (826 in tota

First Kinetic Kudu test rebuild

2022-06-23 Thread Graham Inggs
The first test rebuild of Kinetic Kudu was started on June 17, 2022 for all architectures, all components. The rebuild is finished for all architectures for the main component and still running for universe and multiverse. Results (please also look at the superseded builds) can be found at https:

Re: +1 maintenance report

2022-05-16 Thread Graham Inggs
Hi Robie On Fri, 13 May 2022 at 23:04, Robie Basak wrote: > octave is in dep-wait on riscv64 for libpetsc-real3.16-dev > Produced by src:petsc which FTBFS on riscv64 > FTBFS is because of missing symbol SCOTCH_ParMETIS_V3_NodeND > On amd64 this is shipped in libptscotchparmetisv3-7.0.1.so in > l

Re: autopkgtest running wrong version of tests?

2022-05-12 Thread Graham Inggs
Hi Robie On Thu, 12 May 2022 at 09:46, Robie Basak wrote: > On +1 maintenance this week, I noticed an unusual failure of icinga2 on > kinetic with a trigger of boost1.74/1.74.0-14ubuntu4: > > https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/i/icinga2/20220509_190945_354db@

Question to flavors: touch-base on flavor participation for 22.10!

2022-05-11 Thread Graham Inggs
Hello flavors! As we do around the start of every new cycle, I am reaching out to all the current official Ubuntu flavors to confirm active participation in the upcoming Ubuntu release - 22.10. Working towards a release requires a lot of effort, so we'd like to make sure all the flavors are ready

+1 Maintenance Report

2022-04-26 Thread Graham Inggs
I was on +1 maintenance for the week of April 11-15 and continued into release week, as time permitted. Below are the packages I investigated. python-sparse/hyperspy/sfepy/python-cogent == Numba and several of its reverse dependencies were removed in LP: #1

Re: Second Jammy Jellyfish test rebuild

2022-03-29 Thread Graham Inggs
Hi Christian On Tue, 29 Mar 2022 at 08:19, Christian Ehrhardt wrote: > - Dns-root-data is actually an issue in ldns fixed in jammy-proposed ldns migrated, so I retried dns-root-data > - postgresql-14 was broken by llvm-14, a fix is uploaded to jammy and > built fine (https://launchpad.net/bugs/1

Re: Second Jammy Jellyfish test rebuild

2022-03-25 Thread Graham Inggs
The latest report, dated 2022-03-25 14:05:01 UTC, no longer has broken links to build logs that do not exist. Instead, '!Log' is shown for these. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Second Jammy Jellyfish test rebuild

2022-03-24 Thread Graham Inggs
The second test rebuild of Jammy Jellyfish was started on March 17, 2022 for all architectures, all components. The rebuild is finished for the main component, and finished for universe/multiverse on amd64 and i386, and still running on the other architectures. Results (please also look at the sup

Re: First Jammy Jellyfish test rebuild

2022-01-14 Thread Graham Inggs
Hi Sergio On Thu, 13 Jan 2022 at 23:11, Sergio Durigan Junior wrote: > While at it, there's this annoying bug that happens when the packageset > and the team names are the same; in this case, the internal links will > point to the same place as well (packageset currently, because that's > what co

Re: First Jammy Jellyfish test rebuild

2022-01-14 Thread Graham Inggs
Hi Christian On Thu, 13 Jan 2022 at 15:23, Christian Ehrhardt wrote: > The links to the builds are ok, and it seems they generated no log at > all, example > https://launchpad.net/ubuntu/+archive/test-rebuild-20211217-jammy-gcc12/+build/22817139 > > Maybe a fix to the script regenerating that mig

First Jammy Jellyfish test rebuild

2022-01-13 Thread Graham Inggs
The first test rebuild of Jammy Jellyfish was started on December 17 2021 for all architectures, all components. The rebuild is finished for all architectures for the main component and still running for universe and multiverse on arm64, armhf and riscv64. Thanks to everybody keeping the buildds g

+1 Maintenance Report

2022-01-11 Thread Graham Inggs
I was on +1 maintenance last week and below are the packages I investigated. During the week, I found a number of failed builds with no logs and retried those. gnustep-base/gnustep-back/gnustep-gui transition Uploaded no-change rebuilds and all migr

+1 Maintenance Report

2021-12-01 Thread Graham Inggs
I was on +1 maintenance last week and below are the packages I investigated. numpy = numba was the last blocker preventing the migration of numpy 1:1.20.2-1ubuntu1. It takes upstream some time to add support for new major python versions, and in the course of the python 3.9 transition it was

Second Impish Indri test rebuild

2021-10-01 Thread Graham Inggs
The second test rebuild of Impish Indri was started on September 27 2021 for all architectures, all components. The rebuild is finished for the main component, it's still running for the other components. Results (please also look at the superseded builds) can be found at https://people.canonical

Re: Switching from fuse2 to fuse3 in main

2021-09-30 Thread Graham Inggs
A quick status update. Thanks to everyone who has been working on this! > Bugs have been filed for the following packages that need to be > adapted to build with fuse3: > > * grub2 / grub2-unsigned [2] Patch from OpenMandriva tested > * open-vm-tools [3] Patch submitted upstream > * s390-tools

Re: +1 Maintenance Report

2021-09-27 Thread Graham Inggs
On Thu, 23 Sept 2021 at 17:41, Utkarsh Gupta wrote: > Whilst working through this, do you happen to know "what" exactly > happened? 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. Howe

Re: +1 Maintenance Report

2021-09-24 Thread Graham Inggs
On Thu, 23 Sept 2021 at 19:59, Bryce Harrington wrote: > Looking at the commit Graham points to at the upstream bug, there > appears to be a change from using np.uint32() to .astype(" presumably issue is differences in platform datatype assumptions between > these two routines? In NumPy, the '<'

+1 Maintenance Report

2021-09-23 Thread Graham Inggs
I spent Monday and Tuesday this week on +1 maintenance. Below are the packages I looked at. monero == The last upload of monero was blocked by a FTBFS on riscv64. I was able to work around this by building with -O1. LP: #1940505 shows a similar issue was fixed upstream in binutils, so this

+1 Maintenance Report

2021-09-07 Thread Graham Inggs
I had a short shift +1 from August 23 - 25, and then another last week from August 30 - September 3. I intended to write the report for the first shift in-between, but got caught up in glibc migration things. So below are the packages I looked at during both shifts. delve = There was an autop

+1 Maintenance Report

2021-07-26 Thread Graham Inggs
Last week was my first shift on +1 maintenance. Below are the packages I looked at, grouped by their current status. FIXED moment-timezone.js == I found that the autopkgtests had already regressed in Debian since January 2021 (Debian bug #988836). I confirmed that version 0.5.

Switching from fuse2 to fuse3 in main

2021-07-14 Thread Graham Inggs
Fuse3 is a requirement for qemu 6 [1]. Since we don't want to support two versions of fuse in main, we'd like reverse-dependencies of fuse to switch to fuse3. A test rebuild of packages in main with a build-dependency on libfuse-dev was done, switching the build-dependency to libfuse3-dev. The fo

Transition from wine1.6 to wine packages from Debian

2016-09-15 Thread Graham Inggs
Hi Ubuntu developers Wine has been maintained separately from Debian in Ubuntu since forever, and almost single-handedly by Scott Richie (thanks!). Sadly, the Wine packages in Ubuntu have recently fallen behind, and nobody stepped up to fill Scott's shoes. Earlier this year, I filed a bug [1] wh