[04:24] <odin_> hello, how do I make a recipie again... I'm sure there was a dialog in the web UI for it
[04:25] <wgrant> odin_: You'll find a link on the branch page
[04:25] <wgrant> "Create packaging recipe"
[04:31] <odin_> ah yes thanks found it, I really should get a launchpad expert to look over out project to explain how to clean it up better
[04:31] <odin_> how do we get old PPAs properly deleted?
[04:32] <odin_> 2 are greyed out, and 2 others can be removed, to keep just the 1
[04:32] <wgrant> It's not currently possible to entirely get rid of a PPA. The history of a deleted PPA remains visible to the owner.
[04:36] <odin_> in bzr is it possible to point a branch at the current commit without commiting anything, "bzr push --create-prefix" action seems to make a new commit number
[04:37] <odin_> I use pristine upstream in / and then overlay launchpad project into /debian
[04:37] <wgrant> bzr push doesn't commit
[04:38] <wgrant> wgrant@lamuella:/tmp/a$ bzr push /tmp/b
[04:38] <wgrant> Created new branch.
[04:38] <wgrant> wgrant@lamuella:/tmp/a$ bzr revno
[04:38] <wgrant> 1
[04:38] <wgrant> wgrant@lamuella:/tmp/a$ bzr revno ../b
[04:38] <wgrant> 1
[04:38] <odin_> I have a script that edits the debian overlay files, and does a push per Ubuntu release to its own branch (containing just /debian/**)
[04:39] <odin_> the I can respin my project on all ubuntu releases
[04:39] <wgrant> push pushes the latest commit. You can't push uncommitted changes
[04:41] <odin_> ok maybe no is not the best time for me to look properly..  have pushed a packaging fix (filename changed), and added raring target, no I just wait one test builds on raring/quantal
[04:41] <odin_> before manually starting older versions building
[04:42] <odin_> actuall I look at commit log and it is only doing new commit id for when files changes, so to cover 8 Ubuntu releases there are 4 commits (as many recent ubuntu all share common control files)
[04:47] <odin_> ok thanks for help I updated things and I look back tomorrow to check it
[15:01] <hrw> hi
[15:01] <hrw> is there a way to get download statistics for PPA?
[15:01] <jpds> hrw: Yes.
[15:02] <hrw> jpds: how?
[15:02] <hrw> I would like to see were some of my packages used by someone before I will drop any kind of support for those
[15:02] <jpds> hrw: Comment #66: https://bugs.launchpad.net/launchpad/+bug/139855
[15:03] <hrw> thanks
[15:06] <hrw> works great
[15:06] <hrw> have a nice day
[15:56] <aboudreault> hey
[15:57] <aboudreault> I have packageX in my PPA. This packageX has a dependency packageY, which is not in my PPA, but only in official ubuntu repo.
[15:58] <aboudreault> I'm upgrading a package in my PPA: packageZ. This packageZ is a dependency of packageY, which is not in my PPA.
[15:58] <aboudreault> how should we handle this?
[15:59] <aboudreault> I mean... users of my ppa  will try to install packageX, this will install packageY (ubuntu repo) then packageZ (PPA), since it is higher in version
[15:59] <aboudreault> but the packageY will be broken. isn't it?
[16:00] <aboudreault> looks like  math school problem :)
[16:03] <maxb> aboudreault: Why will packageY be broken?
[16:03] <maxb> Are you saying packageY will break if the version of packageZ is too new
[16:03] <maxb> ?
[16:04] <aboudreault> maxb, it has be built with packageZ version 4.7, and my PPA has the same package version 4.8
[16:04] <aboudreault> well.. because of the ABI
[16:04] <maxb> I guess you will need to supply an updated packageY too then
[16:05] <aboudreault> ok, that's what I thought.. but wasn't sure.