[07:15] <mvo> 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] <wgrant> mvo: Done.
[07:59] <mvo> wgrant: \o/ thank you!
[08:25] <wgrant> mvo: np
[23:06] <nacc> 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] <wgrant> 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] <wgrant> 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] <nacc> wgrant: ack, and historical, so maybe tooling is better now
[23:28] <nacc> but means i can't really import it
[23:29] <nacc> not sure how to resolve that yet
[23:29] <nacc> i've seen a few debian pacakges do this (epoch bump without version bump)
[23:29] <nacc> let me see if i can override it in our importer easily
[23:30] <tsimonq2> nacc: Just curious, why isn't the version bumped when the epoch is bumped?
[23:31] <wgrant> 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] <sarnold> tsimonq2: the version might have been reset to 0 or something and independently eventually gotten to the same version number
[23:32] <nacc> tsimonq2: in this case, the uploaded 8.36-1 and want to go backwards
[23:33] <nacc> so i guess they bumped epoch and went down a version
[23:33] <nacc> but that version had already been published in the pervious epoch
[23:33] <nacc> *previous
[23:33] <nacc> sarnold's point is valid in general, though