[06:00] <ginggs> bdmurray: because no tests have been requested for 2.1.5-2 in unstable, and nothing has triggered a migration-reference/0 in testing yet
[06:01] <ginggs> you can see 2.1.5-2 results for the migration tests here though: https://ci.debian.net/packages/p/pygrib/testing/amd64/
[08:13] <adrien_> I'm looking at ncurses' migration (I dealt with ruby3.1 a few weeks ago and started wanting the package to migrate, no other reason); I re-tried a bunch of tests yesterday and all passed except for the autopkgtest for ncurses itself on i386
[08:13] <adrien_> https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/i386/n/ncurses/20240208_162839_a4355@/log.gz
[08:14] <adrien_> the issue seems to start with "Investigating (0) ncurses-bin:i386 < none -> 6.4+20240113-1 @un puN Ib >" \n "Broken ncurses-bin:i386 Conflicts on ncurses-bin:amd64 < 6.4+20240113-1 @ii K Ib >"
[08:15] <adrien_> but I feel like I'm missing some bit of information to properly understand the issue; does that ring a bell to anyone?
[08:16] <adrien_> my first question would be why the i386 has all the amd64 repos (I don't think I had to think about this for i386 so far)
[10:30] <dviererbe> dotnet8 on jammy proposed is in the pending publication state for nearly a day now. Is this normal or is something stuck on launchpad?
[10:30] <dviererbe> See: https://launchpad.net/ubuntu/+source/dotnet8
[10:41] <rbasak> It needs NEW processing by an AA.
[10:41] <rbasak> (binNEW specifically)
[10:42] <rbasak> I think you can highlight ubuntu-archive in #ubuntu-release.
[10:42] <rbasak> (but perhaps ordinary human binNEW takes more than a day normally anyway)
[10:43] <seb128> rbasak, dviererbe, accepted, thanks for the ping :-)
[10:43] <rbasak> Thank you! :)
[10:43] <dviererbe> Thank you :)
[10:44] <seb128> we don't review NEW queue from stable serie often afaik
[13:42] <sudip> rbasak: since you sponsored LP: #2024325 last time, can you please have another look when you have some time
[13:42] -ubottu:#ubuntu-devel- Launchpad bug 2024325 in trac (Ubuntu Jammy) "[SRU] trac crashes while importing a library in Ubuntu 20.04 (ImportError: cannot import name 'soft_unicode' from 'jinja2.utils')" [Undecided, Confirmed] https://launchpad.net/bugs/2024325
[13:50] <rbasak> sudip: re-sponsored
[13:51] <sudip> thanks rbasak, and sorry again for being a pain :(
[13:51] <rbasak> No worries.
[17:13] <bdmurray> ginggs: thanks, from what I see pygrib is core dumping in Ubuntu so I'll add it to big packages
[18:33] <bdmurray> For those wondering what happened to pygrib when added to big_packages - it still dumped core!
[18:36] <sudip> mfo: from #ubuntu-release about weex, only timestamp was the problem ? I am still wondering why it was building properly when -proposed is added
[18:41] <arraybolt3> this is mostly out of curiosity, but... usually for package building I run sbuild. However, I see there's a tool called pbuilder that seems to be advertised all over the place in Debian packaging. Why do we use sbuild rather than pbuilder?
[18:43] <bdmurray> I use it because I'm an old man and have a hard time learning new tricks.
[18:44] <sudip> I use it as the buildd uses sbuild and I prefer to have similar environment like that to avoid nasty shocks later
[19:42] <jbicha> I believe most of the pbuilder recommendations are old, sbuild has become more of a standard over time
[19:54] <mapreri> arraybolt3: sbuild is what is used by the official buildds.  I believe pbuilder was born because historically sbuild was way too hard to set up locally.  Now sbuild is much easier than 20 years ago to set up locally
[19:55] <mapreri> but I'm the (slightly inactive) current maintainer of pbuilder, so I'm going to tell you to go and use pbuilder :P
[19:55] <arraybolt3> haha :)
[19:55] <arraybolt3> I might try it.
[19:56] <mapreri> Eickmeyer: sorry for leaving it in the bpo queue, I went through it yesterday, and thank you for the ping!
[19:56] <Eickmeyer> mapreri: NP! Thanks for the accept!
[21:44] <arraybolt3> Why. Is. CC-BY-SA-4.0. Not. In. /usr/share/common-licenses.
[21:44] <arraybolt3> The number of times I've had to format that tome^Uwall of text for a debian/copyright  file is immense.
[22:05] <Eickmeyer> arraybolt3: Good question, but considering that's a Debian thing, I'd say probably something that needs to be pushed upstream.
[22:06] <Eickmeyer> (Same with CC-BY-4.0, etc.)