=== JanC_ is now known as JanC === BlackMage_ is now known as BlackMage === pbek_ is now known as pbek === chihchun_afk is now known as chihchun [07:15] hey cjwatson, hope you are the right person to ask. can we get "powerpc" enabled on https://launchpad.net/~snappy-dev/+archive/ubuntu/edge/+packages please? [07:21] mvo: Done. [07:59] wgrant: \o/ thank you! [08:25] mvo: np === chihchun is now known as chihchun_afk [23:06] cjwatson: is this a bug in launchpad? https://launchpad.net/debian/+source/pcre3/1:8.35-3.2 and https://launchpad.net/debian/+source/pcre3/2:8.35-3.2 show different SHA256 for the same-named file and point to the same DSC file [23:22] nacc: Hmm, that's arguably a bug in dak. Epochs aren't included in filenames, so you're not meant to reuse a version that differs from another only by epoch. LP enforces this invariant on its own archives, but apparently Debian doesn't. [23:22] It's arguably a bug in LP that one of the links is wrong, but it's not clear how to fix it. [23:28] wgrant: ack, and historical, so maybe tooling is better now [23:28] but means i can't really import it [23:29] not sure how to resolve that yet [23:29] i've seen a few debian pacakges do this (epoch bump without version bump) [23:29] let me see if i can override it in our importer easily [23:30] nacc: Just curious, why isn't the version bumped when the epoch is bumped? [23:31] nacc: I can retrieve the URL to the original file from the DB manually, which would help this case, but there's no way to get that automatically. [23:31] tsimonq2: the version might have been reset to 0 or something and independently eventually gotten to the same version number [23:32] tsimonq2: in this case, the uploaded 8.36-1 and want to go backwards [23:33] so i guess they bumped epoch and went down a version [23:33] but that version had already been published in the pervious epoch [23:33] *previous [23:33] sarnold's point is valid in general, though