=== pushkarnk1 is now known as pushkarnk
[06:34] <tjaalton> meh, ubuntu-packaging-guide still shows how to run pre-4.0 autopkgtest, so it's at least 8y old
[06:36] <tjaalton> i guess the whole guide is outdated, and ubuntu-maintainers-handbook is the successor?
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
[08:28] <ricotz> mapreri, hi, could you handle libreoffice/amd64 NEW at https://launchpad.net/ubuntu/+source/libreoffice/4:24.2.5-0ubuntu0.24.04.1~bpo22.04.1
=== sil2100_ is now known as sil2100
[10:34] <Skia> mapreri: I'm on holiday for the next two weeks, but maybe you will have time during that to have another look at the "import-bug-from-debian: handle multipart messages" MP? (https://code.launchpad.net/~hyask/ubuntu-dev-tools/+git/ubuntu-dev-tools/+merge/468091)
=== pushkarnk1 is now known as pushkarnk
[11:19] <dviererbe> tjaalton: The ubuntu packaging guide is currently  undergoing a major overhaul to bring it up to date. See the latest preview here: https://canonical-ubuntu-packaging-guide.readthedocs-hosted.com/en/latest/; Repository here: https://github.com/canonical/ubuntu-packaging-guide
[11:20] <dviererbe> until we have a full 2.0 version the ubuntu-maintainers-handbook is strongly recommended
[11:21] <tjaalton> dviererbe: yup, thanks
[14:19] <john-cabaj> How can I view previous autopkgtest runs for packages in -proposed?
[14:22] <jbicha> john-cabaj: visit https://autopkgtest.ubuntu.com/packages/bash for the bash package and click in the oracular column
[14:23] <john-cabaj> jbicha: Thanks, that's perfect
=== pushkarnk1 is now known as pushkarnk
=== liushuyu1 is now known as liushuyu
=== dbungert1 is now known as dbungert
=== pushkarnk1 is now known as pushkarnk
=== Rubennn2 is now known as Rubennn
[18:16] <peat-psuwit> Hello. Seems like python3-apt 2.7.7ubuntu2, recently start phasing on Noble, is uninstallable on armhf.
[18:16] <peat-psuwit> python3-apt : Depends: libapt-pkg6.0t64 (>= 2.8.1) but 2.7.14build2 is to be installed
[18:16] <peat-psuwit> (And apt 2.8.2 is in noble-proposed)
[18:26] <jbicha> bdmurray: if you're around, could you halt phasing for python-apt ^
[18:27] <jbicha> ubuntu-release: ^
[18:28] <jbicha> qa-help: I'm pinging in case you have the ability to pause phasing
[18:28] <jbicha> it's interesting that the issue affected armhf but not amd64
[18:30] <peat-psuwit> That's what I'm curious too. According to build log, both amd64 and armhf did have libapt-pkg6.0t64 2.8.1 during build. Perhaps symbol difference?
[19:20] <Eickmeyer> jbicha: Afaik, the only people who can halt phasing are AAs.
[19:21] <jbicha> ubuntu-archive: ^
[19:34] <sarnold> jbicha: i imagine bdmurray is enjoying time away from the computer for a few weeks
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
[23:34] <RAOF> Looks like I'm too late to stop phasing there - https://ubuntu-archive-team.ubuntu.com/phased-updates.html
[23:58] <jbicha> RAOF: I don't think so, it looks like it was only accepted into updates "today" & the phasing report lags by several hours
[23:59] <jbicha> https://launchpad.net/ubuntu/noble/amd64/python3-apt