[07:59] jawn-smith: next time I'll try to consider whether it's within your waking hours if clicking links means that much to you ;-) [13:02] schopin: if you see them of course feel free to click. I'm just eager to stay involved [13:11] Is there an environment variable to make snapcraft verbose? [13:14] * ogra only knows --verbose and --verbosity= as cmdline options [13:16] Yes, and I usually forget to pass that (maybe because snapcraft is the only build tool I know that does such a thing)... time to make an alias then. [13:17] well, snapcraft 7 is ... all former versions actually showed you built output 🙂 [13:17] (i think it is an insane decision to quieten a built tool down to a spinner graphic ... but who am i anyway 😛 ) [13:18] Haha well I think it's odd too. I just requested old behavior in bug 2020892, please add yourself to the bug count then (: [13:18] -ubottu:#ubuntu-devel- Bug 2020892 in snapcraft (Ubuntu) "Request: Make build verbose by default" [Undecided, New] https://launchpad.net/bugs/2020892 [13:27] me too'ed ... 🙂 [16:37] Hello, dear #ubuntu-devel. I am trying to setup some development environment for myself and I am stuck at running command 'sudo pbuilder create'. Here is the result of the command: http://ix.io/4wLB I tried google about this problem but I am not sure what is the problem [16:42] Looks like maybe you have "devel" in sources.list and pbuilder (well, debootstrap) doesn't support that directly. Try "sudo pbuilder create --distribution=mantic" [16:56] I tried this command and there is same error message [16:57] bkonecki@mothership:~$ sudo pbuilder create --distribution mantic [16:57] I: Distribution is mantic. [16:57] I: Current time: Fri May 26 18:44:38 CEST 2023 [16:57] I: pbuilder-time-stamp: 1685119478 [16:57] I: Building the build environment [16:57] I: running debootstrap [16:57] E: No such script: /usr/share/debootstrap/scripts/mantic [16:57] E: debootstrap failed [16:57] E: debootstrap.log not present [16:57] W: Aborting with an error [17:00] bkonecki_: I guess then either you aren't running mantic, or you aren't fully up to date. What release of Ubuntu do you believe you're running? [17:07] Ubuntu 22.04.2 lts [17:11] I just did apt update and apt upgrade, tried pbuilder create again and error message is the same. Do I need to upgrade to next version? [17:43] danilogondolfo: I'm looking at sudo again and it looks like the target branch for your MP here is debian/sid. IIUC the debian/sid branch should match what's in Debian and the merge should be done on another branch like mantic [17:45] jawn-smith: this is in the documentation; it's an arbitrary thing IMHO because a merge review needs to look at a three-way diff against both debian/sid and ubuntu/devel [17:45] ("in the documentation" uh wherever that was that vpa1977 pointed out to me when I had the same objection) [17:46] vorlon: I've generated the three-way diff locally and checked that everything is good. Just was about to merge and noticed that the branch looked suspicious [17:46] also, good to see you o/ [17:46] nice to see you :) [17:46] jawn-smith: fwiw I've started looking at libcap2 for danilogondolfo this morning [17:47] ack, thanks for that. I'll keep plugging away on sudo [17:47] so is the action here to just merge to the debian/sid branch? Or do an upload and let the auto-sync stuff do magic? [17:49] thanks folks, this is the documentation I followed https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageMerging.md#submit-merge-proposal [17:50] Thanks for the link [17:50] jawn-smith, as I understand you don't "git merge" it, right? I guess you'll git clone it, debuild it and dput? I've never seen the other side of the merge :P [17:51] bkonecki_: --distribution=jammy then [17:52] looks like jammy is working alright [17:54] danilogondolfo: That's how I've usually done these, yeah [17:58] danilogondolfo: the merge is done by the bot on the launchpad side (*if* you use git-ubuntu prepare-upload args, otherwise it just clobbers) [17:59] danilogondolfo: fwiw I normally strip bug numbers from merge changelogs; they don't matter much technically but in principle we're not re-closing the bugs so I think it's cleaner (and makes for a shorter changelog). The bug links should still be present in the original changelog entries [18:17] bryceh: were you working on the nginx transition? libnginx-mod-http-geoip2 [18:17] bryceh: were you working on the nginx transition? libnginx-mod-http-geoip2 needs an ubuntu-server subscription [18:23] juliank: uh going to need some explanation on this fwupd-efi sync to lunar, given there's a package of this version already in mantic-proposed [18:24] (with build records both accepted and rejected for all archs, neat https://launchpad.net/ubuntu/+source/fwupd-efi/1:1.4-1) [18:26] vorlon: it's further up in the backlog saying I synced the same one by accident to lunar again when I should have done only kinetic downward [18:27] juliank: ack [19:07] rbasak: looks like https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/sg3-utils/+git/sg3-utils/+merge/373440 was landed (loooong ago) and should be closed out [19:07] xnox: huh how did https://code.launchpad.net/~xnox/ubuntu/+source/casper/+git/casper/+merge/373690 end up in the sponsorship queue? === JanC is now known as Guest3921 === JanC_ is now known as JanC [23:47] vorlon, re libnginx-mod-http-geoip2 sub - done [23:47] bryceh: ta