[03:22] <caraka> Question: Is it possible to dput one set of signed source packages and have lp build across the 4 current releases?
[11:44] <ovidiu-florin> hello world
[11:45] <ovidiu-florin> I'm trying to register the KDevelop project in LP so we can have a project for Kubuntu from where to serve KDevelop packages before they go in the Kubuntu archive or backports
[11:45] <ovidiu-florin> but I'm getting an error that says that the project is registered
[11:46] <ovidiu-florin> but when I go to http://launchpad.net/kdevelop I get a 404
[11:46] <ovidiu-florin> why is that?
[11:47] <cjwatson> because it was previously registered and now inactive
[11:48] <ovidiu-florin> I found this: https://launchpad.net/~kdevelop
[11:48] <ovidiu-florin> is it related?
[11:48] <cjwatson> no
[11:49] <cjwatson> ovidiu-florin: I've renamed the old inactive project out of the way; you should be able to register it now
[11:50] <ovidiu-florin> thank you
[11:56] <ovidiu-florin> It's created https://launchpad.net/kdevelop
[12:39] <KNRO_> I'm getting an odd import error here: http://launchpadlibrarian.net/287070586/mutlaqja-kstars-bleeding-master.log
[12:39] <KNRO_> but my git repo does not contain any submodules
[12:39] <KNRO_> so what's going on?
[12:39] <cjwatson> It must have them in the history somewhere
[12:40] <KNRO_> cjwatson: how to find this out? the import was working fine up until a week or two ago
[12:52] <cjwatson> KNRO_: 7cd2ae86cc875247528cf4e1235147f0864e101e adds a submodule at kstars/kstarslite/kirigami and is in your history
[13:01] <KNRO_> cjwatson: thanks, is there a way to remove this?
[13:01] <cjwatson> not without rewriting your history :(
[13:01] <cjwatson> we should have native git-to-git imports this year though, which won't have that limitation
[13:02] <KNRO_> well, I can't wait till then, I have folks relying on the PPA
[13:02] <cjwatson> as a stopgap you could build source packages manually, though I know that's not great
[13:03] <cjwatson> might be tolerable for a month or two
[13:05] <KNRO_> cjwatson: but the submodule was removed, why is this still a problem?
[13:05] <cjwatson> KNRO_: because the entire point of an import is to represent each revision in the history
[13:05] <cjwatson> KNRO_: if it can't represent a revision then it's going to fail, regardless of whether the changes introduced by that revision were later reverted
[13:07]  * KNRO_ is screwed
[13:07] <cjwatson> sorry, I don't have a better alternative to offer at the moment although I wish I did
[13:09] <KNRO_> cjwatson: you said there was a way by rewriting the history? is this plausible? I never heard of it until now
[13:10] <cjwatson> git filter-branch or similar, but it's very intrusive - it'd cause problems for anyone with a git checkout
[13:11] <cjwatson> manual source uploads to the PPA for the time being are probably a more viable workaround
[13:12] <KNRO_> cjwatson: looks like I'll go that path until git import is fixed by launchpad
[13:12] <KNRO_> ETA a month of two? :D
[13:13] <KNRO_> well it also looks like I'll go back to snapcraft again
[14:18] <cjwatson> KNRO_: the other thing you could do is manually push the git repository to git.launchpad.net every so often and create a recipe from that instead
[14:31] <mg983> Is there an outage currently?
[14:31] <mg983> Fetched 3,022 kB in 3s (972 kB/s)
[14:31] <mg983> W: Size of file /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_trusty-security_restricted_binary-amd64_Packages.gz is not what the server reported 20228 20231
[14:32] <cjwatson> #launchpad doesn't operate security.ubuntu.com frontends
[14:32] <cjwatson> try #canonical-sysadmin, though see if it's reproducible first
[14:32] <mg983> sorry!!
[19:13] <caraka> Speaking of manual source uploads to a PPA (from a few hours ago), is it possible to dput a single set of sources and have it build across multiple releases?
[19:14] <caraka> Or is it just the one release mentioned in the changelog, requiring a unique source for each release?
[19:15] <dobey> if you are doing manual uploads, you need to create different .dsc for each release, yes
[19:44] <cjwatson> caraka: yeah, the answer to your question as stated is no it's not possible, but if the binaries built for the oldest release will do then you can upload to the oldest, wait for it to build, copy forward to all the newer ones
[19:44] <cjwatson> caraka: you could also use recipes to automate multiple uploads if that makes sense in your case
[19:47] <caraka> YOu've piqued my interest cjwatson. How would one use a recipe to automate multiple uploads? Is there an example of that somewhere that I can go poke around and get my head into?
[19:48] <cjwatson> caraka: https://help.launchpad.net/Packaging/SourceBuilds is the top of our documentation on this
[19:48] <cjwatson> depending on the exact situation it may not suit you, but could be worth looking at
[19:51] <caraka> That is what I had before. Now that the devs use gpgsigs, the imports from github fail.
[19:51] <caraka> I tried setting up a git repo on lp, but I couldn't figure out how to make it work with github as the upstream.
[19:52] <dobey> you have to clone/push manually at the moment i think, to get a mirror on lp
[19:53] <caraka> yes - that's what I couldn't make work, using the instructiuons here. I think there are some asusmptions in the instructions on how things should work that are not apparent to a noob. That's why I've resorted to multiple dputs
[19:54] <caraka> I just couldn't figure out how to manage it with git.
[19:56] <caraka> after a whole Satruday messing with it, I knew that it should be easier than it was and that the ignorance was on my end.  :P
[20:06] <caraka> Do you know of any lp projects that are managed this way, so I can go look at how they are set up at lp versus github? That way I might be able to figure out how they manage and name branches,etc.
[20:07] <cjwatson> I don't know if anyone is doing a manual clone/push thing at the moment
[20:08]  * cjwatson eyes his git-import-model branch, 600-odd lines in
[20:20]  * caraka stumbles on a git mirroring article he wish he had found last Saturday
[20:23] <caraka> If I figure out an elegant/straightforward way to explain this I'll document it and share it. I know you are not asking the impossible for us to mirror into git at the moment.