[09:13] <klebers> wgrant, hi! I opened a support question yesterday about a linux-riscv kernel that's currently blocked because we can't build it: https://answers.launchpad.net/launchpad/+question/695551
[09:13] <klebers> wgrant, would you be able to help us with that?
[09:43] <cjwatson> klebers: I'm going to be working on this today
[09:44] <klebers> cjwatson, thanks!
[11:06] <mop> Hi all, for a last second bug discovered I must revert a package that was overrided by "Replaces" directive in the package control file
[11:07] <mop> the Replacing package now is removed but I doesn't still see the old version package using apt-cache policy is there something that I can do ?
[11:09] <mop> or is just matter to wait some scheduled script ?
[11:26] <cjwatson> mop: it would help to have some more specifics if you want us to investigate something - archive URL and package names and versions
[11:52] <mop> repo: https://launchpad.net/~openquake/+archive/ubuntu/ppa/
[11:52] <mop> package "resurrected": oq-python3.6 , package removed: oq-python3.8
[11:52] <mop> oq-python3.8 had "Replaces" directive against oq-python3.6
[11:52] <mop> my actions were:
[11:53] <mop>  - upload oq-python3.6
[11:53] <cjwatson> So at the publishing level Replaces is basically irrelevant to anything FWIW.  Of course it matters a good deal to dpkg/apt
[11:53] <mop>  - upload oq-python3.8
[11:53] <mop>  - remove oq-python3.8
[11:53] <mop> apt-get update
[11:53] <mop> apt-cache policy oq-python3.6 -> no packages
[11:54] <cjwatson> What Ubuntu release are you using?
[11:54] <mop> bionic
[11:54] <cjwatson> Since this PPA supports multiple releases
[11:55] <cjwatson> Can you share a pastebin with the output of the apt-get update and apt-cache policy commands?
[11:55] <mop> sure
[11:56] <rbasak> I get the impression that what's happened here is that a new source package produced a binary package with the same name, so overwrote the binary produced by the old source package.
[11:56] <cjwatson> Right, that's certainly a possibility but I want to make sure I have all the details
[11:57] <mop> https://pastebin.ubuntu.com/p/JR2HpNbrx7/
[11:57] <juliank> heh apt itself doesn't care about replaces, they're just no-ops that tell dpkg not to error out on file conflicts - update-manager has some hackery in it to u
[11:57] <rbasak> Sorry, yes, I'm getting ahead of things here.
[11:57]  * rbasak leaves you to it
[11:57] <cjwatson> s'ok
[11:58] <cjwatson> I don't see any recent upload of oq-python3.6, so I assume when you said "- upload oq-python3.6" you mean the upload in 2018
[11:58] <mop> I copied from another repo
[11:58] <cjwatson> Ah
[11:58] <cjwatson> Recently?
[11:59] <mop> 1 hour ago
[11:59] <mop> more or less
[11:59] <mop> there is some job that must run ?
[11:59] <cjwatson> You can see on https://launchpad.net/~openquake/+archive/ubuntu/ppa/+packages that no such copy has been processed
[11:59] <cjwatson> Have you checked your email for failures?
[11:59] <cjwatson> Including spam folders or whatever
[11:59] <cjwatson> Copies are processed by a job, but it's much more frequent than hourly
[11:59] <mop> no, the web interface seems correct ...
[12:00] <cjwatson> The versions of oq-python3.6 in your PPA were published on 2018-09-06
[12:01] <cjwatson> I don't even see any attempts to copy oq-python3.6 from anywhere to anywhere today in our logs
[12:01] <mop> oh, it's correct, sorry it was just for oq-libs package
[12:01] <cjwatson> Ah
[12:02] <mop> oq-python3.8 and oq-python3.6 was both on the repo for a while
[12:02] <mop> then I just removed oq-python3.8
[12:03] <cjwatson> So in that case it's as rbasak said: your oq-python3.8 source package produced a higher-versioned oq-python3.6 binary package which overwrote the old one, and then when you removed the oq-python3.8 source package the lower-versioned oq-python3.6 binary package was not automatically resurrected
[12:03] <cjwatson> Are you aware that clients with the higher-versioned oq-python3.6 binary package already installed probably won't automatically be downgraded to the lower version?
[12:04] <mop> yes but newer stay there for minutes
[12:04] <cjwatson> A single source package that (I think?) builds all of Python 3.5, 3.6, and 3.8 and gives them all a 3.8 version number seems ambitious at best, but that's your problem :)
[12:04] <cjwatson> OK, so you can probably repair the situation with a self-copy
[12:05] <mop> copy the package on the same repo from the same repo ?
[12:05] <cjwatson> Go to https://launchpad.net/~openquake/+archive/ubuntu/ppa/+copy-packages, select the oq-python3.6 source packages there, select "This PPA", "The same series", and "Copy existing binaries", and copy
[12:06] <mop> done
[12:07] <cjwatson> OK, so that will take a little while to process but then it should be sorted
[12:07] <cjwatson> I'll keep an eye on it
[12:09] <mop> tnx, always reactive, tnx a lot
[12:25] <cjwatson> mop: Looks right now
[12:26] <mop> cjwatson, yessss
[12:26] <mop> tnx a lot
[12:27] <cjwatson> no problem
[13:17] <mop> cjwatson, a question related to what happens: keep oq-python3.6 and oq-python3.8 both on the repo was the right choice to be able to get older version of 3.6, correct ?
[13:23] <cjwatson> mop: If you want both sets of binaries to exist at the same time, then you should build them from separate source packages and make sure that the sets of binary names built from each of those source packages don't overlap.