[00:53] I am trying to merge two nearly identical launchpad branches with the command "bzr merge --remember lp:~bbot+core+developers/bbottheircbot/BBot_Githubt --force" but I get a no common ancestor error. Is there a way to force it without the common ancestor (and hopefully make it a common ancestor) [01:58] aj00200: That's going to be difficult if you're maintaining and separately committing to both bzr and git trunks. [01:58] aj00200: #bzr may be able to offer advice on how to achieve what you desire. [01:59] Forcing a one-off merge now won't help the future. [04:06] i'm getting a gpg error from apt trying to update from a private ppa [04:06] is this known at all? [04:07] poolie: No. [04:07] poolie: Which? [04:07] And what's the error?/ [04:07] canonical-ux [04:07] "The following signatures were invalid: BADSIG 6D8F9D432E7" [04:07] BADSIG? [04:07] Ew. [04:07] walled-garden? [04:07] yes [04:07] natty? [04:07] Or oneiric? [04:08] strangely enough if i download the Release and .gpg file through chrome they do verify ok [04:08] oneiric [04:08] That's what I was just checking. [04:08] Sounds like your local apt cache may be broken? [04:08] It uses If-Modified-Since. [04:09] sudo rm /var/lib/apt/lists/*walled-garden*, perhaps. [04:09] yes it does sound like that [05:05] wgrant: well, https://bugs.launchpad.net/launchpad/+bug/836419 [05:05] Ubuntu bug 836419 in Launchpad itself "badsig error on update from private ppa" [Undecided,New] [05:05] not going to do anything new with it now [05:05] s/new/ [05:07] Ew. [05:07] We write Release files directly into dists/ [05:07] WTF [05:07] Who needs atomicity. [05:08] so it could be race between apache and the writer? [05:08] that would account for it [05:08] Right, it could just be very, very bad timing. [05:08] this is a bit worse than the other one because it doesn't get unstuck unless you manually delete the local cache file [05:08] Since the file contents are precalculated. [05:08] Yeah. [05:09] ok, that seems like the likely explanation then [05:09] maverick's final ISOs ended up with a similar sort of situation with extras.ubuntu.com, required some future-touching of its indices to stop apt errors. [05:09] It would be nice if apt detected the conflict and considered that the files might not be valid. [05:09] mm [05:10] arguably if the signature's invalid it shouldn't cache the file etc [05:10] Right. [05:10] Eventually everything will use InRelease and that won't be so much of a problem, hopefully. [05:10] We'll just have terrible vulnerabilities instead... [05:14] is that just a release file with an inline signature? [05:16] Yes. [05:16] So there's no inconsistency, and it can more easily invalidate all involved files if the sig is bad. [05:18] right [05:18] but why terrible vulnerabilities then? [05:21] Well, inline OpenPGP signatures have a habit of not being correctly implemented. I think I've reported all the obvious holes in apt's implementation, but you never know. [05:22] I generally consider them a bad idea, because correct implementations are rare. [05:22] And difficult. [05:23] oh, because gpg tends to default to saying "yes, something in here was signed", as you aluded to? [05:23] i agree [05:24] i just wasn't sure if you meant the specific combination with nonatomic writes was a probelm [05:25] No, no, unrelated. Just saying that neither approach has a history of being well-implemented, so we probably can't win. [05:25] probably not :) [08:35] hi all [08:35] https://launchpadlibrarian.net/78452640/upload_2841727_log.txt [08:35] any clue what went wrong there? [08:36] I don't see any epoch defined in my package? [08:36] nor the previous package [08:37] pmjdebruijn: The old kvm binary package must have an epoch in its version. [08:37] Which PPA is this? [08:37] it this have this: dh_gencontrol -pkvm -- -v1:$(DEB_VERSION) [08:37] wgrant: https://launchpad.net/~unnet-pkg-master/+archive/kvm-spice-release/+packages [08:42] pmjdebruijn: https://launchpad.net/~unnet-pkg-master/+archive/kvm-spice-release/+build/2746647 [08:42] kvm-1:84+dfsg-0ubuntu16+0.14.1+noroms+0ubuntu2unnet1~lucid [08:42] right [08:42] though the new package should generate kvm-1:84+dfsg-0ubuntu16+0.15.0+noroms+0ubuntu2unnet1~lucid [08:42] but it seems it doesn't [08:43] That would be a bug in your package. [08:45] it's just a debian backport :D [08:45] hmmmm [08:45] I'm not sure that Debian's packaging is compatible with Ubuntu's. [08:45] Our virt stacks differ significantly in parts. [08:46] I backported 0.14.1 previous without issues [08:46] oh wait [08:46] erhm [08:46] crap [08:46] I got the other from ubuntu onoiric [08:46] * pmjdebruijn hits himself in the head [08:47] neverind [08:47] and thanks for being my rubberduck :) [08:51] sorry for wasting your time [09:17] ah [09:17] wgrant: dh_gencontrol -pkvm -- -v1:$(DEB_VERSION) [09:17] vs [09:17] wgrant: dh_gencontrol -pkvm -- -v1:84+dfsg-0ubuntu16+$(debsrc_ver)+$(debian_rev) [09:17] that bit me === henninge changed the topic of #launchpad to: https://launchpad.net/ | Help contact: henninge | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [09:31] pmjdebruijn: Right. I guess Ubuntu long ago used the upstream KVM version. [09:52] indeed === henninge is now known as henninge-lunch === henninge-lunch is now known as henninge [12:05] adeuring: Hi! ;-) [12:08] hi henninge, I'll change the tpopic === adeuring changed the topic of #launchpad to: https://launchpad.net/ | Help contact: adeuring | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [12:08] adeuring: thanks ;) === jtv is now known as jtv-eat === jtv-eat is now known as jtv === brianchidester_ is now known as brianchidester === yofel_ is now known as yofel [14:56] hi [14:57] hi daker [14:57] adeuring, I'll take IRC now. === deryck changed the topic of #launchpad to: https://launchpad.net/ | Help contact: deryck | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [14:57] deryck: thanks! [14:58] adeuring, np. I really should be taking it an hour earlier than now, but forget sometimes. So I don't mind a ping from you about it. :) [15:02] deryck, i need some help [15:02] daker, what sort of help? [15:02] the recipie is failing on the lp builders, but not locally in a pbuild chroot [15:03] https://code.launchpad.net/~daker/+archive/slumber/+build/2750501 [15:03] deryck, https://code.launchpad.net/~daker/+recipe/slumber-daily [15:03] there's a reason it gives you the build logs you know... just sayin [15:04] its a python issue [15:04] when its building it cant find a specified module [15:04] so it fails and errors out [15:04] the lp build is not pulling in a needed build-dep (python-setuptools) [15:06] TheEvilPhoenix, deryck python-setuptools is in build-deps but the lp build doesn't pull it [15:07] wasnt there an issue with the builders not taking into account PPA dependencies too, deryck? [15:07] coulda sworn several people were here complaining about that a few weeks ago [15:07] I'm not sure actually. [15:07] bigjools or abentley, can one of you help here? I'm dumb about recipes. [15:07] (me included) [15:08] deryck: i dont think the issue is the recipe [15:08] i think the issue is the builders [15:08] i.e. its not reading dependencies for building [15:08] or if it is [15:08] its not grabbing them [15:08] * bigjools looks at build log [15:09] ummm [15:09] Build-Depends: debhelper (>= 7.0.50~), cdbs (>= 0.4.49) [15:09] buggy package/recipe [15:09] LOL [15:09] daker: failed build-deps line in control [15:10] TheEvilPhoenix, can you explain ? [15:10] daker: read bigjools's line [15:10] <(ID+)bigjools> Build-Depends: debhelper (>= 7.0.50~), cdbs (>= 0.4.49 [15:10] that's whats in the control file [15:10] so... [15:10] that explains why its not installing the build dep [15:10] unless you can provide other proof stating that the control file *has* the package you need [15:11] <(ID+)bigjools> buggy package/recipe <--- that's basically what i just said [15:11] deryck: I had a look, but istm that bigjools has it in hand. [15:11] abentley, yes, thanks anyway abentley. [15:11] and thanks bigjools! :) [15:11] TheEvilPhoenix, bigjools my control doesn't actualy look like this [15:11] control file* [15:12] the package is from a recipe, right? [15:12] so is it grabbing the packaging branch you expect? [15:13] it's grabbing the packaging from another branch [15:13] look at "Recipe contents" https://code.launchpad.net/~daker/+recipe/slumber-daily [15:13] and whats the control file in that branch say [15:13] I can see the control file in the packaging branch has got the right build-depends [15:14] ninja'd :P [15:15] bigjools, so my control file is correct ? [15:15] the one in the packaging branch has the dependency you talked about [15:16] oh [15:16] ha [15:16] the recipe build failed [15:16] ImportError: No module named setuptools [15:16] yet the build is reported as successful [15:16] abentley: see https://code.launchpad.net/~daker/+archive/slumber/+recipebuild/76990 [15:17] [python-module-clean/slumber] Error 1 (ignored) [15:17] bigjools: looking [15:17] not sure it should be ignoring that! [15:18] * daker is rolling his eyes [15:18] abentley: the build is OK but the log says otherwise. It's ignored the error though, and the package ends up with an incorrect control file it seems. [15:19] I don't know which component decided to ignore it, my recipe knowledge is limited [15:19] bigjools: yes, I see that. I'm trying to see how that could happen. I don't think our code is ignoring the error. [15:19] so I shall hand back to deryck / abentley [15:19] abentley: yeah it might be one of the build tools [15:20] bigjools: would this be /usr/lib/pbuilder/pbuilder-satisfydepends ? [15:20] no idea [15:20] something didn't install setuptools [15:21] bigjools: it looks like dpkg-buildpackage is emitting 0 even though it failed. [15:21] abentley: yes see the "[python-module-clean/slumber] Error 1 (ignored)" [15:23] what is a "subteam"? === matsubara is now known as matsubara-lunch [15:24] bigjools: I don't know enough to know whether this invocation is sane: "/usr/bin/dpkg-buildpackage -i -I -us -uc -S". If it is, then it's a problem we can't fix. [15:25] abentley: unfortunately I don't know either [15:25] bigjools: okay, who do we have who knows packaging? [15:26] bigjools: btw, the relevant file is lib/canonical/buildd/buildrecipe [15:26] jelmer might know [15:28] at a first glance, it looks like a missing build dep on python-setuptools [15:29] jelmer: right. We're trying to figure out how to make that a recipe build failure, because right now, the error is ignored. [15:31] jelmer, abentley this line Build-Depends: debhelper (>= 7.0.50~), cdbs (>= 0.4.49) is from an old rev of the packaging branch [15:32] so the lp builder is not pulling the last rev [15:32] abentley, bigjools: cdbs adds a "-" at the front of the "setup.py clean" line [15:33] abentley, bigjools: causing make to ignore non-zero exit codes [15:33] see /usr/share/cdbs/1/class/python-distutils.mk:135 [15:34] this is an issue in the package, not the recipe builder [15:35] jelmer: thanks. [15:35] jelmer, what should i do to fix it ? [15:36] daker: add a build dependency on python-setuptools [15:36] there is a bug open in debian about cdbs ignoring errors from commands run in the clean target [15:36] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441020 [15:36] Debian bug 441020 in cdbs "cdbs: don't ignore errors in make clean target" [Normal,Open] [15:37] jelmer, don't make crasy [15:37] jelmer, look http://bazaar.launchpad.net/~daker/slumber/deb-packaging/view/head:/debian/control [15:37] and as i said : [15:37] jelmer, abentley this line Build-Depends: debhelper (>= 7.0.50~), cdbs (>= 0.4.49) is from an old rev of the packaging branch [15:37] so the lp builder is not pulling the last rev [15:38] daker: your debian version hasn't changed, so it won't do a new build [15:39] daker: you probably want to update it to include the packaging branch revno [15:44] jelmer, how can i do that? any wiki page ? [15:46] add something like ~ppa{revno:packaging} to the end of the version string [15:50] thanks for helping jelmer [15:52] daker: The wiki is here: https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted#The%20anatomy%20of%20a%20recipe === daker is now known as daker_ === deryck is now known as deryck[lunch] === matsubara-lunch is now known as matsubara [16:48] I downloaded codes of project docky through bzr. The question is how to reconstruct a project from these codes in ide like eclispe, so that I could read, run and debug? Is there any tutorial on it? [16:50] huangkan: that really depends on the project, it's out of scope for #launchpad === med_out is now known as medberry [16:51] huangkan: the docky help/developer channels are probably a better place to ask [16:51] jelmer:thx === deryck[lunch] is now known as deryck [17:31] ciao [17:32] is it possible to understand where a branch has been branched from ? :-) [17:33] eLBati, you mean locally or in the web UI? bzr info locally should tell you something about the branch. but I'm guessing you mean web UI? [17:34] deryck, in the web UI [17:35] moreover , bzr info doesn't tell me it, since I originally branched using another pc [17:35] eLBati, yeah, I don't think we have anything like that in the web ui. [17:35] eLBati, what's the branch url on lp? Can I see it? [17:35] deryck, https://code.launchpad.net/~openobject-italia-core-devs/openobject-italia/l10n_it_fix_partially_deductible_vat [17:36] deryck, how can I know what branch should I propose the merge to? [17:37] I have 2 options :-) [17:37] eLBati, well, it's stacked on lp:openobject-italia so I'd guess that as a starting point. [17:37] uhm no [17:38] deryck, the options are this https://code.launchpad.net/~openerp/openobject-addons/trunk or this https://code.launchpad.net/~openerp/openobject-addons/6.0 [17:38] eLBati, there's probably a bzr command to see common branch starting points, but my bzr foo is not that strong. maybe abentley can help us? [17:39] abentley, see eLBati above. he doesn't know what branch he branched from and wants to figure that out. [17:46] Hi, can I make a mailinglist for a team open while keeping the PPA uploading privileges away? === dpm is now known as dpm-afk [18:05] hey everyone, i'm trying to get started with bzr colo, so I ran bzr colo-init lp:unity but it errors out with bzr: ERROR: File exists: '/srv/bazaar.launchpad.net/mirrors/00/05/66/af/.bzr' [18:05] am I doing it wrong? [18:07] yes..i a [18:07] am [18:25] eLBati, deryck: bzr doesn't track branch points, but you can look back at old revisions and see what their branch nick was using "bzr log --long". [18:25] eLBati, deryck: Or you can compare your branch with the candidates using "bzr missing . https://code.launchpad.net/~openerp/openobject-addons/trunk". [18:26] eLBati, deryck: Or you can compare your branch with the candidates using "bzr missing . https://code.launchpad.net/~openerp/openobject-addons/trunk" [18:27] eLBati, deryck: or you can see what changes would be merged by doing "bzr diff -r ancestor:https://bazaar.launchpad.net/~openerp/openobject-addons/trunk" [18:40] many thanks abentley deryck [18:40] eLBati: np [18:54] abentley, I'll hand over IRC to you now. === deryck changed the topic of #launchpad to: https://launchpad.net/ | Help contact: abentley | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [18:54] deryck: okay === beuno is now known as beuno-lunch === beuno-lunch is now known as beuno === matsubara is now known as matsubara-afk [19:59] hello, its possible branch a project on LP w/o LP account ? [20:00] yes === daker_ is now known as daker [21:32] abentley? [21:32] can you delete a project page for me? [22:08] GTRsdk2: projects are never deleted, only deactivated. Please file a question to request that === abentley changed the topic of #launchpad to: https://launchpad.net/ | Help contact: - | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad === medberry is now known as med_out === yofel_ is now known as yofel