/srv/irclogs.ubuntu.com/2024/12/11/#ubuntu-devel.txt

=== dviererbe1 is now known as dviererbe
=== nnmwxqlrjfvropmn is now known as tozbizcuiihbmdyn
=== tozbizcuiihbmdyn is now known as georgiag
=== JanC is now known as Guest7955
=== guiverc2 is now known as guiverc
=== JanC is now known as Guest4504
=== dviererbe1 is now known as dviererbe
schopin@pilot in08:50
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Oracular | Patch Pilots: schopin
adrienCan someone look at https://code.launchpad.net/~adrien/ubuntu/+source/adios2/+git/adios2/+merge/477906 ? I think it is needed for the openmpi transition. Thanks. :)09:05
enycHrrm;  wonder what I should read, which MOTU maintainer or process best approached.09:27
enychttps://sourceforge.net/p/gscan2pdf/bugs/430/  <- very easy fix in universe 'gscan2pdf' package in ubuntu 24.04LTS needs patching-in ,  not really a backport / whole version09:28
-ubottu:#ubuntu-devel- sourceforge.net/p/gscan2pdf/bugs 430 "gscan2pdf not running under Linux Mint 22beta" [Pri: 5, Closed: Fixed]09:28
enycconfusingly, it affects whomever has an  /etc/upstream-release/  e.g.  unofficial ubuntu variants  but it is really a gscan2pdf bug (fixed) in the ubuntu package09:28
enycjust needs few line change put into   ubuntu universe package by a MOTU maintainer  so LTS works properly with  the many derivatives  where  /etc/upstream-release/ directory exists09:29
enycI should say (fixed upstream)09:30
schopinenyc: is it fixed in Plucky and Oracular?09:30
schopinIf you feel like it I can actually walk you through the entire process and sponsor an upload for you :)09:31
enycschopin: confirmed the patched code is already in  gscan2pdf  Plucky version 2.13.4-4;  noble has 2.13.2-109:37
enycwent through deb-src and got the source loaded etc09:37
enycschopin: I greatly appreciate your offer; but also wary I shortly need to be hurriedly connecting heating pipes and repairing outside lights and other backlogged irl tasks!09:38
enycschopin: I have no doubt this would be instructive, in short; either, can you do this, or; can you guide me another day ?09:38
schopinWell, right now I'm the current Patch Pilot, which means it's my job for the next few hours to do the guiding and sponsoring (rather than doing the actual work. We don't *always* have a patch pilot on duty but we try to.09:40
schopinThe point of this *is* to be instructive ;)09:41
enycschopin: schedule?  here similar time tomorrow?  etc09:41
schopinI don't think the schedule is publically available, but I do know that bdrung will be on shift tomorrow around noon UTC (1PM CET) and would be happy to help you and/or pick up where we leave off.09:43
schopinOh, the schedule is somewhat available, if not very helpful: https://calendar.google.com/calendar/u/0/embed?showPrint=0&showCalendars=0&mode=WEEK&src=Y184ZWRhZjk2OTllYWFmMWFmMmNjYTY2ZTYyOGZkNDEwODQ2ZTkwMjcwNmQ2YTMzMTU1OTNmODhiOTk0ZTZlOWE2QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20&color=%23F4511E (from https://discourse.ubuntu.com/t/ubuntu-patch-pilots/37705 )09:46
gjollyhi there, where can I find a [good] documentation on how to run autopkgtest?10:58
Skiagjolly: you mean locally, or in the infra?11:00
gjollySkia: locally11:00
Skiain any case, a not too bad start is there: https://wiki.ubuntu.com/ProposedMigration#autopkgtests11:01
Skiaotherwise, `man autopkgtest`, and `man autopkgtest-virt-*`11:01
Skia`zless /usr/share/doc/autopkgtest/README.running-tests.rst.gz` is not too bad also11:03
Skiaand for Ubuntu, there is the `autopkgtest-buildvm-ubuntu-cloud` that is very handy with the `qemu` virt-server11:03
gjollySkia: thanks! I think everything I'm looking for is in /usr/share/doc/autopkgtest actually.11:08
Skiagjolly: nice! This folder just seems to miss mentionning `autopkgtest-buildvm-ubuntu-cloud`, but otherwise should be great11:10
gjollySkia: I will check what these `autopkgtest-virt-*` do because I would love to have something like `autopkgtest-virt-azure`11:15
Skiaoh, I see. Then you might want to study how we do in production with OpenStack: in autopkgtest src code, we have `ssh-setup/nova`, that is used in combination with the `ssh` virt-server. You can find the full command line at the top of the logs in autopkgtest.u.c. This `nova` script will spawn the VM, check for SSH access, and then hand back to autopkgtest. It's also responsible for destroying the VM11:18
Skiaand a few other things. I guess that would be a good start to be adapted for `azure`.11:18
Skiathere is even a `ssh-setup/SKELETON` file, that gives the boilerplate to implement such thing11:19
jamespagedoko: could you take a look at bug 2091540 for me - I think there might be a problem with error handling between Python and openssl for the new version of openssl in proposed11:19
-ubottu:#ubuntu-devel- Bug 2091540 in python-eventlet (Ubuntu) "ssl test failures with openssl >= 3.4.0" [Undecided, New] https://launchpad.net/bugs/209154011:20
jamespagebut I may be wrong11:20
Skiagjolly: https://salsa.debian.org/ci-team/autopkgtest/-/tree/master/ssh-setup11:20
Skiagiven that there is already `nova` and `maas` upstream, I guess an `azure` script could likely make its way to the repo, but paride would be better placed to answer that11:22
Skiayou would end-up with a command line looking like this: `autopkgtest ... -- ssh -s azure -- azure_arg1=value ...`11:24
gjollySkia: that would be great. Thank you very much for your help. I have a lot of things to read and a few things to try now.11:26
Skiasure, come back any time if you need further guidance. We don't know azure at all in the team, but it's conceptually the same thing that's running in production on OpenStack.11:26
=== gurupras- is now known as guruprasad
paridegjolly, hi, this is not the first time an idea likes that comes up, see https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/21013:25
-ubottu:#ubuntu-devel- Merge 210 in ci-team/autopkgtest "Add ssh-setup/ec2" [Opened]13:25
paridegjolly, that's for aws of course13:25
paridegjolly, as you can see there, there are two concern points: (1) who owns the new functionality? this is something we can define in some sensible way I believe, I don't see it being a blocker. (2) that comment about "a reorganization of the logic in autopkgtest". afaik that idea didn't go far yet, but has not been abandoned, so it's something to13:30
paridekeep in mind13:30
paridegjolly, also: we'd need something like autopkgtest-build-azure, to prepare azure images to be used as testbeds13:31
paridetoabctl, ^^ that's your MR I mentioned13:32
gjollyAH I shouldn't be surprised that toabctl tried to do that with AWS already13:33
toabctlparide, wouldn't it be possible to just use the default ubuntu images on aws or azure and use cloud-init for whatever is required to prepare the testbed? or is there something special required?13:58
adrienCan someone retry https://launchpad.net/ubuntu/+source/paraview/5.13.1+dfsg-9build2 ? I don't know if it's going to work but I think it's worth a try, thanks. :)14:41
mirespaceahasenack (or any other sru member if around), when around:  I have been asked for an estimation of when walinuxagent would be SRUprocessed... sorry for the direct ping, and thankyou14:46
mfoadrien, I retried the failed builds for arm64/armhf/riscv64.14:57
paridetoabctl, well, it should be doable. having a dedicated image is of course going to be faster is you want to run many tests, but it's also a chore to maintain14:58
paridetoabctl, the setup we do on autopkgtest images is basically: https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/setup-commands/setup-testbed?ref_type=heads14:58
paridewhich is mostly about minimization14:58
paridetoabctl, autopkgtest-buildvm-ubuntu cloud already uses cloud-init to prepare the image: https://salsa.debian.org/ci-team/autopkgtest/-/blob/a1af98e6106f395372e459bfee936172205ff3f5/tools/autopkgtest-buildvm-ubuntu-cloud#L31914:59
adrienmfo: thanks! :)15:02
schopin@pilot out15:17
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Oracular | Patch Pilots: N/A
enr0n@pilot in18:01
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Oracular | Patch Pilots: enr0n
cpaelzerenr0n: to Hawaii please then18:02
enr0nworks for me!18:03
ahasenackjuliank: hi, https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/update_excuses.html#packagekit says packagekit depends on apt also "migrating", but I think that does not apply here in noble, am I right?18:12
ahasenackno soname change, and I just tested installing new packagekit from noble-proposed without updating apt, seems to work fine18:13
ahasenackand the test case would have caught something, all good I think18:19
ahasenackreleasing18:19
juliankahasenack: it does apply *on armhf*, because the dependencies are broken due to t64 changes in apt18:58
juliankNobody noticed before the release, I forgot to put a fixed symbols file into the latest unapproved SRU too19:00
juliankOr it might be older than the last time this happened19:00
juliankThe C++ mangling changed due to long long long19:03
juliankI need to push another SRU out on top of the current one with more apt-ftparchive fixes for launchpad, so I can remember updating the symbols file for it and back versioning the symbols it accordingly19:04
juliankThis also affects oracular of course, and plucky still19:06
juliankThe plan for plucky is to bump the soname in January19:06
=== mfo_ is now known as mfo

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!