=== mwhudson changed the topic of #launchpad to: Launchpad login issues are being investigated | Launchpad is now open sourced: https://dev.launchpad.net/ | Help contact: - | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com | #launchpad-dev is the developer channel [03:51] bohrium is freeze again [03:51] anyone can help? === stevie is now known as heHATEme === heHATEme is now known as vorian [09:41] wgrant: it's freezing again! === vorian is now known as buttercup [16:17] hi, something is wrong with the site? [16:17] <[lan3y]> dont think so why? [16:18] i'm getting Sorry, there was a problem connecting to the Launchpad server. [16:18] gour: What URL? [16:18] bazaar.launchpad.net? [16:18] http://bazaar.launchpad.net/~openerp/openobject-server/5.0/annotate/head%3A/doc/Changelog [16:18] and http://bazaar.launchpad.net/~openerp/openobject-client/5.0/annotate/head%3A/doc/Changelog [16:19] <[lan3y]> bazaar then [16:19] ahh, the same url :-/ [16:19] bazaar.launchpad.net is having some issues at the moment. Try refreshing in a couple of minutes. [16:19] If that doesn't work, you might just have to wait. [16:19] that's what i do :-) [16:31] huh...now it works... [16:51] er [17:35] what is the easiest method to make launchpad a compile for every series? [17:35] split the package or upload without any extra name (no ~ppaX~%distroY) and copy it to X series? is it possible? [17:36] err, sec [17:36] shiki-: you may be looking for https://help.launchpad.net/Packaging/PPA/Uploading#Using%20packages%20from%20other%20distributions [17:36] I used the split method. Created jaunty packages first from karmic, sid, scratch. Uploaded them. Then copy jaunty folder, wrote a script which renames them. [17:36] ah ty [17:37] hmm.. dont know.. [17:37] (disclaimer: no firsthand experience with that) [17:37] maybe the split is still better choice [17:37] (since if one breaks, I can fix it easily) [17:37] I'll use this from now on anyway. Ty. [17:37] (once a problem occurs, just make a split for series X :)) [17:44] wondering about this command: dput my-ppa-force-hardy P_V_source.changes [17:44] correct syntax is: dput ppa:shiki/personal-force-hardy ? oO [17:45] ehm..okay this is not the correct one.. [17:57] shiki-: no, ec [17:57] "create a new dput configuration section using incoming = ~/ppa/ubuntu/" [17:57] lemme pastebin [17:58] shiki-: paste.pocoo.org/show/136978 is what's in my ~/.dput.cf. I don't think you can do this without a ~/.dput.cf conveniently. [17:59] shiki-: (just look at the [ppa] section in /etc/dput.cf, if I understand the syntax correctly you can't append the suite if you use the "ppa:" shortcut) [18:10] shiki-: If you want LP to compile the same packagename for different series within the same PPA, you absolutely must change the version for each series [18:11] Let me pastebin the script I use [18:11] IC [18:11] ty [18:11] then the way I used is OK..? [18:14] http://paste.ubuntu.com/261536/ [18:14] is what I wrote to automate the process of building additional source packages for upload one to each series [18:15] Forcing a series different to that appearing in the changes file is not useful here, since you still need to change the version [18:15] (Because the name+version needs to be unique for every binary package which is built) === abentley1 is now known as abentley === doctormo__ is now known as doctormo === abentley1 is now known as abentley [19:24] ah, so what I said was wrong then. Sorry! [21:11] When will the new overview page be released? [21:12] Is it going to happen before next saturday or after it? [21:41] <\u03b5> :o that completely changed [21:41] <\u03b5> lacks colors :< [21:44] <\u03b5> especially the Report a bug button [21:44] <\u03b5> it's in stealth mode, litterally [22:50] How long does it take for packages to appear in ppa after dput? [22:51] up to 5 minutes for the upload processor to notice the new source [22:51] Then whatever time it takes for the builds to happen [22:51] ok cool, I thought it would be longer [22:52] results of builds are published to the download site at 0, 20, and 40 minutes past the hour [22:52] so prolly I see something in couple of minutes? [22:52] (it's basically only 1 python script in a package) [22:53] you should be able to see the status on your PPA's webpage once the initial 5 minutes have passed [22:54] plus you should also get a confirmation email at that point [22:54] that should be about now :) [22:55] hmmz [22:55] Rejected: [22:55] Unable to find distroseries: unstable [22:55] should that be Distribution: Karmic? [22:57] lowercase, but yes, assuming you actually want to build in the development distroseries [22:58] maxb: I'm on karmic, but it *should* work on jaunty too [22:59] ah, if you're already running karmic, makes sense to upload for that [22:59] (I am too, but most people don't like to live on the bleeding edge) [23:08] hmmz, how do I tell dpkg-build to build for karmic instead of unstable? Can't seem to find it in the man page [23:14] dpkg-buildpackage that is [23:19] blizzkid: it's controlled by the header line in debian/changelog [23:23] maxb: Actually, publishing has been */5 (not */20) for some months now. [23:32] maxb: I found it indeed, but now I have another issue... it got rejected because it contained binaries, so I did dpkg-buildpackage -S, but then dput complains it can't find the .changes file because that's now .source.changes [23:33] blizzkid: dpkg-buildpackage -S will create a *_source.changes. You need to upload that. [23:33] What do you mean "dput can't find"? dput doesn't find changes files, you tell it where they are on the command line. [23:34] maxb wgrant my bad, I forgot to change the dput command : [23:34] :( [23:58] yay it worked