[08:59] <LocutusOfBorg> ddstreet, hello you there?
[09:00] <LocutusOfBorg> some changes you did on ubuntu-dev-tools broke launchpad login
[09:00] <LocutusOfBorg> http://launchpadlibrarian.net/520965621/ubuntu-dev-tools_0.178_0.178ubuntu1.diff.gz
[09:00] <LocutusOfBorg> in specific, reverting this change in jammy
[09:00] <LocutusOfBorg> -            self.login()
[09:00] <LocutusOfBorg> +            self.login_anonymously()
[09:00] <LocutusOfBorg> works as expected and my ubuntu-build is back
[09:02] <LocutusOfBorg> otherwise...
[09:02] <LocutusOfBorg> ubuntu-build --batch --retry openimageio
[09:02] <LocutusOfBorg> Traceback (most recent call last):
[09:02] <LocutusOfBorg>   File "/usr/bin/ubuntu-build", line 282, in <module>
[09:02] <LocutusOfBorg>     main()
[09:02] <LocutusOfBorg>   File "/usr/bin/ubuntu-build", line 260, in main
[09:02] <LocutusOfBorg>     can_retry = options.retry and me.canUploadPackage(ubuntu_archive,
[09:02] <LocutusOfBorg> AttributeError: 'NoneType' object has no attribute 'canUploadPackage'
[09:03] <LocutusOfBorg> can you please have a look?
[09:04] <Unit193> LocutusOfBorg: Can you successfully use ubuntu-dev-tools with current python3-ubuntutools?  I have an older version pinned because I run into issues if I upgrade.  I can't remember which tool precisely, but I mainly use syncpackage, backportpackage, and...uh...
[09:04] <LocutusOfBorg> no.
[09:04] <Unit193> merge-changelogs I'm also having some issue with now, I see traceback.
[09:05] <LocutusOfBorg> I had the same issues, and I fixed by changing that line login_anonymously into login
[09:05] <LocutusOfBorg>  /usr/lib/python3/dist-packages/ubuntutools/lp/lpapicache.py line 108
[09:05] <LocutusOfBorg> please try
[09:05] <LocutusOfBorg> back to focal, I reverted to an older version, but now there is the incompatibility with new python and collections.abc
[09:10] <LocutusOfBorg> ddstreet, (see #launchpad chan too if you want)
[09:11] <LocutusOfBorg> Unit193, please let me know if this fixes the issue for you
[09:11] <Unit193> Hmm, can't test this without something to actually sync, and LP isn't picking up my latest upload to experimental I want to pull yet.
[09:13] <LocutusOfBorg> Unit193, syncpackage -f ruby-certificate-authority ?
[09:15] <Unit193> Nope, didn't need the lpapicache edit for that. :/
[09:19] <Unit193> LocutusOfBorg: Well thanks for making me try python3-ubuntutools again, not sure what's changed in the meantime but backportpackage and syncpackage work, sooo..
[09:38] <LocutusOfBorg> lol
[09:52] <bluca> bdmurray: still seeing "Received HTTP code 403 from proxy after CONNECT" on new runs on !amd64 this morning
[09:52] <bluca> it worked briefly yesterday afternoon
[12:08] <Payam> Hi,I do build my package to .deb from a python application. but when I install the .deb package and try to run it what I get is "osim: comman not found". Here is my rules file : https://dpaste.org/giZBx
[12:08] <Payam> What am I doing wrong?
[13:17] <arraybolt3[m]> Payam: Does /opt/osim exist?
[13:18] <arraybolt3[m]> Also, are you building this with sbuild?
[13:19] <Payam> I use pybuild, opt/osim should created during installation of deb file and I use dpkg-buildpackage -uc -us -b
[13:19] <Payam> I used python-virtualenv before in ubuntu 18 and it worked but now it doesn't anymore
[13:21] <arraybolt3[m]> Hmm. Well something is happening that's causing /opt/osim to not exist - if the build process itself creates it in whatever virtual environment you're using, then I would guess either something weird with the package you're building, or the build steps aren't executing in the order you think they are and so osim is needed before it's created.
[13:22] <arraybolt3[m]> (That's just a very generic take on it - seeing the console output of whatever you're building would help, and knowing what software you're trying to build would also be helpful.)
[13:22] <arraybolt3[m]> Also, check your build dependencies in debian/control.
[13:23] <arraybolt3[m]> Wait... the package is building properly, but then when you try to run it you're told osim: command not found?
[13:23] <arraybolt3[m]> In that case I'd check your install files (debian/*.install) and your installation dependencies.
[13:23] <Payam> yes exacly
[13:23] <Payam> The problem is I don't know where the files ends up after the installation of .deb file
[13:25] <arraybolt3[m]> Payam: A trick you can use is to open the .deb file in an archiver program, and browse around in it - you can see exactly where it's going to put all its files by doing this.
[13:25] <arraybolt3[m]> That might give you a clue as to what's going wrong.
[13:28] <Payam> ÿeah. it should end up under usr/bin/
[13:28] <Payam> but the usr/bin/osim is just an empty file
[13:30] <arraybolt3[m]> And osim is not an empty file in the actual source code, right? Or it's the output of the build process?
[13:41] <Payam> Now I changed it to this : https://dpaste.org/tfzzn#L36
[13:41] <Payam> and it worked but the packages are missing. It is almost like it doesn't install alla pip dependencies.
[13:42] <Payam> like with python-virtualenv
[14:14] <bdmurray> bluca: It likely has to do with which datacenter the tests run in. I spent some time looking at firewall rules yesterday and didn't spot anything wrong but I'll keep looking into things today.
[14:32] <bluca> thanks!
[15:45] <bdmurray> bluca: Can you remind me where to find the systemd-upstream test logs?
[15:46] <bluca> https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream
[15:46] <bluca> running jobs are under there
[15:46] <bluca> finished ones I don't know if they are listed anywhere, I get them from the github PR, latest one to fail: https://autopkgtest.ubuntu.com/results/autopkgtest-focal-upstream-systemd-ci-systemd-ci/focal/arm64/s/systemd-upstream/20220720_153900_496b3@/log.gz
[15:47] <bdmurray> bluca: in that log I see prod-proposed-migration-4@bos01-arm64-5. Are there any failures since yesterday with "@bos02"?
[15:50] <bluca> there are 5/6 failures today and they are all on bos01, didn't see any on bos02
[15:51] <bluca> you can see the list of PRs here: https://github.com/systemd/systemd/pulls
[15:51] <bluca> each PR has the list of CI jobs, and the focal-<arch> have the link to the logs
[16:55] <dbungert> vorlon: looks like you're doing some ffmpeg transition work, I'm on +1, shall I avoid or assist?
[16:55] <vorlon> dbungert: assist please :)
[16:55] <vorlon> there are a lot of revdeps that ftbfs
[16:56] <dbungert> no joke
[17:00] <dbungert> vorlon: working backwards then, starting xpra