[08:11] <doko> what is needed to make ubuntu-dev-tools (reverse-depends) work with hirsute?
[08:16] <RikMills> doko: I think tumbleweed has to do some updates on ubuntuwire at least?
[08:17] <alkisg> Hi, groovy's rsync misbehaves (https://github.com/WayneD/rsync/issues/109), but if I build the groovy package locally in focal with dkpg-buildpackage, rsync then works fine!
[08:17] <alkisg> Any clues on how to troubleshoot rsync runtime issues when they're caused by the build environment?
[08:23] <alkisg> I just tested, focal's rsync, when built on groovy, misbehaves as well. Something in the build environment upgrade, from focal to groovy, breaks rsync.
[08:24] <alkisg> I've no idea where to file such a bug report, "build environment breaks rsync" is too generic, and rsync upstream closed the issue that I filed there with "not an rsync issue"
[08:50] <doko> kanashiro: could you have a look at ruby in hirsute? e.g. installation of b-d's for libprelude are broken (ruby-rubygems)
[08:59] <doko> mwhudson: looks like the autosyncs made golang 1.15 the default. do you want to go with this, or delay that until 1.16?
[11:04] <rbasak> alkisg: if rsync is broken on Groovy, I'd file a bug against rsync in Ubuntu with steps to reproduce
[11:04] <rbasak> It can always be moved later
[11:05] <rbasak> Sounds like something to do with a glibc difference to me
[11:41] <doko> cpaelzer: looks like we started a postgres transition with the syncs
[11:45] <alkisg> Thank you rbasak, doing so
[12:02] <cpaelzer> I have no capacity to do PG-13 now and from my last check (not too long ago) way too many deps aren't ready yet
[12:03] <cpaelzer> doko: did you mean PG-13 or just 12.4-3 ?
[12:04] <cpaelzer> if it is PG-13 we ahve to remove things from hirsute as of now and revisit ~january
[12:04] <doko> 13
[12:04] <cpaelzer> last time the depending projects needed ~1year to pick up PG-12 as needed
[12:04] <doko> the component mismatches
[12:04] <doko> see the ...
[12:04] <cpaelzer> Debian allows multiple postgres versions which is why they can slow-roll
[12:04] <cpaelzer> we don't and would like to have one, but one working
[12:04] <cpaelzer> therefore PG-12.x it is (for now)
[12:05] <doko> then please fix postgresql-common
[12:05] <cpaelzer> I'm happy if PG-13 turns out to be way less transition pain than what PG-12 was
[12:08] <cpaelzer> I'll need to talk to Myon
[12:08] <cpaelzer> gladly I'm totally overloaded right now :-/
[12:08] <cpaelzer> thanks for the ping thou @doko
[12:13] <cpaelzer> I'll either tune back 13->12 in postgresql-common OR try to find time to get things moving
[13:41] <LocutusOfBorg> seb128, thanks for sane-backends fix, can you please also forward the patch to the Debian bug? I think Debian maintainer is doing a different fix... not sure which one is better (or if they are both needed)
[13:42] <seb128> LocutusOfBorg, the patch is more a workaround, I didn't want to start creating the lock from code and then have to do with group membership etc
[13:42] <seb128> it can probably be overwritten with a fix from upstream or Debian when they have one
[13:44] <LocutusOfBorg> seb128, https://jff.email/cgit/sane-backends.git/commit/?id=736573a8db4bd098da28a4831ce4c601f880aacd
[13:44] <LocutusOfBorg> this is the fix mentioned on the Debian bug
[13:45] <LocutusOfBorg> looks "sane" enough to me (sorry for the pun)
[13:45] <seb128> LocutusOfBorg, that's not going to work, /var/lock is not a persistent dir
[13:45] <seb128> (that was mentioned on the Debian bug)
[13:45] <seb128> the file is going to not be there anymore after a restart
[13:46] <LocutusOfBorg> ack thanks
[14:04] <mitya57> I'm going to start Qt 5.14 → 5.15 transition in a few hours. If something is entangled with it and I should wait, please let me know.
[14:22] <doko> mitya57: we currently have a broken ruby, e.g. no gems can be built
[14:25] <mitya57> doko: I hope that won't be a problem for Qt
[14:39] <LocutusOfBorg> mitya57, what about doing it in bileto?
[14:39] <LocutusOfBorg> the queue is really huge, not sure if entangling will help in making it faster, specially for autopkgtests
[14:40] <LocutusOfBorg> I would like also to do haskell and ocaml and nodejs, but I prefer to wait some more days
[14:40] <LocutusOfBorg> or is it already ready to land?
[14:41] <LocutusOfBorg> in that case, meh :D
[15:00] <mitya57> LocutusOfBorg: I have started the work in Bileto (4316), but I want to publish it today because otherwise Qt will be autosynced from Debian (and it will be worse because it needs bootstrapping).
[15:01] <LocutusOfBorg> oh...
[15:01] <LocutusOfBorg> so better publish :)
[16:13] <doko> Missing build dependencies: fonts-urw-base35 (< 20170801.1.0~)
[16:15] <doko> tkamppeter: ^^^ ghostscript needs an update, everything b-d on ghostscript can't be built
[16:16] <tkamppeter> doko, OK, I think Debian has done this already, so I will take over what Debian did, or better merge their GS.
[16:17] <doko> ta
[17:58] <alkisg> I managed to pinpoint the issue better: AC_CHECK_FUNC(lchmod) says "checking for lchmod... yes" in Ubuntu 20.10, while it said "no" in 20.04.
[17:58] <alkisg> But from what I understand, lchmod isn't supported in Linux (and it's failing when /proc isn't mounted), so that would be a bug in coreutils?
[18:07] <alkisg> https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109
[18:56] <mitya57> doko: speaking about ruby, maybe it's better to remove ruby-defaults 1:2.7+2 from groovy-proposed until rubygems is built?
[18:57] <mitya57> That version doesn't seem to have major changes apart from the change that broke it. So 1:2.7+1 should work fine.
[18:59] <doko> kanashiro: ^^^
[19:06] <mitya57> Btw it's also broken in Debian, see Debian #972490
[19:35] <LocutusOfBorg> tkamppeter, I can do ghostscript if you want
[19:42] <LocutusOfBorg> syncing/merging
[19:55] <LocutusOfBorg> tkamppeter, looks like the sync built just fine on ppc64el
[19:55] <LocutusOfBorg> so no more delta
[19:56] <LocutusOfBorg> what is your opinion?
[20:14] <tumbleweed> doko: I was waiting for a name for Hirsuite, to do distro-info updates. But it seems we've got it now
[21:10] <ivzhh> [y5kvpn7km] (unsupported message type)