[01:47] doko: dnspython should be fixed up now === guiverc2 is now known as testing [04:35] jamespage: I am preparing a number of patches for SRU to the OVN package, in that breath I see that ovn 20.12 is cut which contain all the fixes. Due to the holidays they will most likely postpone actual release until January, but I wonder if we would consider updating the package in hirsute early so that we get one less release to target for the patches. === cpaelzer__ is now known as cpaelzer [07:37] doko: I don't understand your request, the only shebangs I see in ironic are: https://pastebin.ubuntu.com/p/YXZCSZXTMV/ [08:21] icey: you're looking into the source, not the package: https://paste.ubuntu.com/p/8Pw4KFJx45/ [08:22] doko: indeed, can you point me at any docs about what to change to resolve that, as I don't know where the versioned shebangs are coming from [08:23] icey: the debian package doesn't ship these binaries at all [08:24] icey: dh_python3 --shebang=/usr/bin/python3 should do the trick [08:24] icey: probably not just ironic. might be a good idea to scan all the openstack packages for python3.8 / python3.9 shebangs [08:25] doko: decent time for it as it's OpenStack milestones time :) === lan3y is now known as Laney [09:30] could anyone point me to the script generating component-mismatches.txt ? [09:33] seb128: lp:ubuntu-archive-tools component-mismatches [09:34] Laney, thanks, I was looking in -script which has process-component-mismatches-diff , the split between those repository keeps confusing me [09:35] yeah I usually end up looking in the other one if it's not in the first === sem2peie- is now known as sem2peie [13:28] jibel: thank you for the review and rebase! [13:28] You rock [13:29] sil2100, yw [14:47] seb128: use comm -12 on these two, and only process those === cpaelzer__ is now known as cpaelzer [15:55] Does anyone here use podman in hirsute? [15:55] I can do podman -t run debian:stretch (for example), but then I can't input anything into the shell, like the tty is not attached [16:05] doko: given that the package isn't doing anything to override the shebang, it feels like this could be an update to dh-python to make it default to a less strict shebang unless specified? [16:08] icey: send a patch? you only change the specific shebang to the python3 one, if it's the default version (this only matters when we have two supported versions during transitions) [16:09] doko: so you're suggesting making overriding these shebangs to python3 _just_ for hirsute? [16:09] I'm trying to really understand the need [16:11] icey: for the 3.10 transition ... if we have python3.9 shebangs, then things are not automagically tested for the next python, and we'll issues only later [16:12] doko what is the target for 3.10? [16:12] October 2021 [16:12] so, we'll want the python3 shebang for the next ~year? === cpaelzer__ is now known as cpaelzer === sem2peie- is now known as sem2peie [17:54] rbasak: cpaelzer so the latest update-notifier upload queued to -proposed is still seeing pep8 include errors "FileNotFoundError: [Errno 2] No such file or directory: 'pep8'". Yet if I can download the update-notifier source on xenial-proposed and run mk-build-deps --install debian/control I can see both pep8 and python3-pep8 installed as build-depends on a system that doesn't yet have pep8 [17:54] https://paste.ubuntu.com/p/ZQqrPTJdSg/ [17:54] any thoughts on what I could be missing in the autopkgtest environment? [17:54] I can see that the debian/control of the source package does require pep8, maybe I also need to be exlicit on python3-pep8 too? === sem2peie- is now known as sem2peie === ijohnson is now known as ijohnson|lunch === sem2peie- is now known as sem2peie === ijohnson|lunch is now known as ijohnson [23:04] turns out the above was my own oversight on xenial-only.... pep8 was required only for autopkgtests (not package build) so that dependency needed to be in d/tests/control not in debian/control Build-Depends