[03:05] <saiarcot895> Something doesn't like OpenSceneGraph 3.2.0~rc1 in Saucy (https://launchpad.net/~saiarcot895/+archive/flightgear-edge/+build/5622881 and https://launchpad.net/~saiarcot895/+archive/flightgear-edge/+build/5622880)
[04:23] <ESphynx> Hey guys, how come I'm nor earning karma for commits imported from git->bzr?
[04:30] <wgrant> ESphynx: Which branch?
[04:32] <ESphynx> wgrant: https://code.launchpad.net/~jerstlouis/ecere/master
[04:32] <wgrant> What's your Launchpad username?
[04:32] <ESphynx> jerstlouis
[04:34] <ESphynx> Is it because the branch is under my user rather than the project?
[04:35] <wgrant> Did you only add your @ecere.com email address to your Launchpad account recently?
[04:35] <wgrant> It doesn't look like it was there a week ago.
[04:35] <ESphynx> there was another account generated with a weird ID, and I claimed/linked it
[04:35] <ESphynx> but even the newer commits on the branch didn't generate karma :P
[04:36] <wgrant> When did you do that?
[04:36] <ESphynx> the merge 2-3 days ago maybe
[04:36] <wgrant> Branch karma is only allocated daily, and you're unlikely to get it retrospectively.
[04:37] <ESphynx> Feb 18 is when I did that
[04:38] <wgrant> I'd expect you to start getting karma from revisions created about 24 hours after the merge
[04:38] <wgrant> But that itself may take 24 hours to process
[04:38] <ESphynx> ah... cool then ;)
[04:38] <wgrant> Some the involved tables have several billion rows, so not all this data is processed terribly frequently...
[04:39] <ESphynx> billions eh! :)
[04:39] <wgrant> Yup :/
[04:40] <ESphynx> I just always thought it looked silly that everyone else doing a few translation than me writing all the code :P
[04:40] <ESphynx> everyone else are showing as top contributors* :P
[04:40] <wgrant> That should fix itself up once a few weeks of commits are attributed to you, hopefully :)
[04:40] <wgrant> Branch karma is fairly valuable.
[04:41] <ESphynx> hehe yeah, somehow I just assumed it didn't work because I wasn't using bzr :P
[04:42] <ESphynx> thanks for the clarifiations :)
[04:43] <wgrant> np
[12:22] <Doctor_Nick> quit
[17:43] <Doctor_Nick> How do I submit changes to a source build record with launchpad lib?
[17:43] <Doctor_Nick> I changed a status from "Superseded" to "Published" and I don't know how to submit that change
[18:01] <cjwatson> Doctor_Nick: You can't do it that way
[18:01] <cjwatson> Doctor_Nick: What are you trying to do, exactly?
[18:02] <cjwatson> Doctor_Nick: Are you trying to undelete a package?
[18:05] <Doctor_Nick> no
[18:05] <Doctor_Nick> cjwatson: Somehow the most current package in my repo got marked as Superseded
[18:06] <cjwatson> Can you give me a link or something?
[18:07] <Doctor_Nick> cjwatson: https://launchpad.net/~nzatkovich/+archive/bleediergraphics/+packages?field.name_filter=&field.status_filter=&field.series_filter=
[18:08] <Doctor_Nick> llvm-toolchain-snapshot, version 201753-2~nickz~trusty
[18:09] <cjwatson> That shows as Published for me, although ...~saucy is superseded.  Is that what you meant?
[18:09] <cjwatson> 1:3.5~svn201822-2~nickz~trusty is Deleted
[18:09] <Doctor_Nick> yes
[18:10] <Doctor_Nick> the trusty package is published, but the saucy package is superseded
[18:10] <cjwatson> Anyhow, looks like it's been confused by you uploading newer versions which you then deleted
[18:10] <Doctor_Nick> yeah
[18:10] <Doctor_Nick> probably
[18:10] <cjwatson> You should be able to fix this by copying the old version of the package over itself
[18:10] <Doctor_Nick> tried that
[18:10] <Doctor_Nick> won't let me
[18:10] <cjwatson> You can use copy-package from lp:ubuntu-archive-tools to do that
[18:10] <cjwatson> I would want to see the specific invocation and error message
[18:11] <Doctor_Nick> File llvm-toolchain-snapshot_3.5~svn201753-2~nickz~saucy.debian.tar.gz already exists in Bleedier Edgier Graphics Drivers, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
[18:11] <cjwatson> copy-package -p nzatkovich --ppa-name bleediergraphics -s trusty -e 1:3.5~svn201753-2~nickz~trusty llvm-toolchain-snapshot
[18:12] <cjwatson> Yeah, that's not an error from a copy, that's an error from a fresh upload, AFAICS
[18:12] <Doctor_Nick> ah
[18:12] <cjwatson> Er not the above
[18:12] <cjwatson> copy-package -p nzatkovich --ppa-name bleediergraphics -s trusty -e 1:3.5~svn201753-2~nickz~trusty -b llvm-toolchain-snapshot
[18:12] <cjwatson> Since you want to copy the binaries as well
[18:13] <Doctor_Nick> cjwatson: what's the package associated with ubuntu-archive-tools?
[18:15] <cjwatson> There isn't one
[18:15] <cjwatson> bzr branch lp:ubuntu-archive-tools
[18:16] <Doctor_Nick> ok
[18:21] <Doctor_Nick> cjwatson: the status hasn't changed yet, does it take a while to sync?
[18:23] <Doctor_Nick> ah, no wait, there it goes.
[18:23] <cjwatson> Doctor_Nick: I believe it needs a PPA publisher run, so expected time somewhere south of 10 minutes
[18:24] <cjwatson> Doctor_Nick: Your copy for saucy failed because the version you were trying to copy never built and thus has no binaries to copy, so you'll probably need to copy that one without -b
[18:24] <cjwatson> Doctor_Nick: Ah, you did that already
[18:24] <Doctor_Nick> yeah
[18:25] <Doctor_Nick> thanks for that
[18:25] <cjwatson> So yeah, that's Pending now and it'll be flipped to Published by the next publisher run
[18:40] <Doctor_Nick> cjwatson: welp, it's published now, but the builds are still superseded and I can't retry them
[18:42] <dobey> what is superseded exactly?
[18:43] <Doctor_Nick> I've stopped caring to fix this
[18:43] <dobey> when you upload a new version, the old version is superseded
[18:43] <cjwatson> mm, yes, I think you might just have to reupload in the saucy case
[18:43] <Doctor_Nick> I'll just wait until the script triggers tomorrow
[18:43] <cjwatson> seems like a bug that we can't unsupersede those builds when copying an old source back
[18:44] <Doctor_Nick> The only reason I was trying to fix this was because it takes 4 hours for that particular package to build