[00:00] i've created and validated now an openpgp key. then i've called "debuild -S". and then "dput ...". But what I get now is:Checksum doesn't match for ../window-picker-applet_0.4.24-ep3.dsc. But the signature seems to be good, which is mentioned 1 line above. What's wrong here? [00:01] mb741: Did dput tell you that the checksum doesn't match? [00:01] yes [00:01] Compare the checksum in the .chnages with the actual checksum of the .dsc. [00:02] Yes this seems to fail [00:02] Why? [00:02] If they differ, you've uploaded the wrong .changes. debuild -S again. [00:02] And make sure you dput the _source.changes. [00:02] I've called dpkg-buildpackage before. Could that be the problem? [00:03] If you did it after you generated the .changes, yes. [00:03] Same error with recalling debuild -S [00:03] Sure you're uploading the right .changes? [00:04] ah i see now. that was the binary changes file [00:05] Right. [00:05] It would have been rejected even if the .dsc wasn't wrong. [00:05] is there a possibility to upload binaries? i would need it for a testing branch for the kernel [00:06] No, you cannot upload binaries. [00:06] Why do you need to? [00:07] 2 reasons: uploading the kernel sources needs about 65MB compared to 18MB of the binary [00:08] second reaons: when i build the source package the whole kernel tree is cleaned first. so when i only make small changes to any of the drivers i'll have to rebuild the whole kernel tree which takes ~3 hours on my netbook. [00:09] mb741: Why not maintain a separate source tree and build the source package from that? [00:09] so when i can spread a binary test package then rebuilding the kernel tree only takes a few minutes because the other object files already exist [00:09] That's what I do for my packages. [00:09] I make the changes in my development tree, commit them, then merge them into the packaging tree and build the package from there. [00:09] the kernel tree is rather large [00:10] Not terribly. [00:13] and do i have to upload 65MB for each change i make? [00:14] mb741: Not if you keep the base code in an orig.tar.gz, like almost every package does. [00:14] Then only the packaging changes (in the .diff.gz) need to be uploaded each time. [00:14] ah ok [00:15] hi all [00:15] and what about branches. i've created some branches. uploading is no problem. but there is no way to build binaries of it. so what is the sence of branches? [00:16] mb741: Branches are for storing code. You can't yet have Launchpad build a package out of a branch. [00:16] ok thx [00:17] friend, who is using ati radeon hd 3650 [00:17] downloaded xorg patch from launchpad and the card is working correctly === Edwin is now known as Guest35382 [00:18] if he upgrade the xorg, it will be ok on no? [00:18] r [00:18] kurthy: This isn't the right channel. Which patch? [00:19] wgrant,i thought that,but only i would like to get information [00:20] because i would like to buy a notebook lenovo t500 which have same graphic card with intel integrated [00:20] Try #ubuntu, perhaps. [00:20] ok, [00:20] This definitely isn't the right channel. [00:20] ok [00:21] and it isnt a best time :D [00:21] i go to sleep, have a nice night :) [00:21] hi [00:27] Hey, y'all, how can I get a .po file to work with a program? [00:27] Namely, keryx [00:28] Apparently (looking at the source code) the locale directory is ./locale [00:28] I dropped a .po file in there, I just wonder where to go from here. [00:54] anybody around who can help with multiple PPAs [00:54] ? [00:54] !ask | LaserJock [00:54] LaserJock: Please don't ask to ask a question, simply ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) [00:54] yeah, yeah [00:54] lol [00:54] can I delete a PPA or rename it? [00:54] Heh. [00:54] No. [00:54] umm, bummer [00:55] You can get an admin to disable a PPA, but that won't do much until 2.2.9. [00:55] Er, 3.0 [00:55] let's see, I think I can work around this [00:55] You could possibly convince a LOSA to rename it. [00:55] But I'm not sure. [00:55] there are issues.... [00:56] I think I've got a way to work around it [00:56] spm: Hm, so there are. [00:56] I wanted 2 PPAs with a particular name [00:56] Forgot about the indices. [00:56] if you're package free in the given PPA, rename isn't too hard, if you have packages and want to retain them, aiui, it gets... complex in evil ways [00:56] but I'll just make the first PPA a generic team PPA and add the other two I want after [00:56] I'm just creating them now [00:57] It'd be nice if there was a way to trigger careful publication of a particularly PPA. That would make renames of people and PPAs easy. [00:57] Yeah, I have "(unused default PPA)" on a couple of my teams, because I want named PPAs [00:58] I believe the issue is around key signing of packages - or some such. IMBW here, this is somewhat overheard parroting. [00:58] The signing key is now shared between all of a Person's PPAs (except a couple of mine, which were created early on), so that's not an issue. [00:58] I can't see a problem with renaming people and PPAs other than breaking extant sources.lists [00:59] maybe I'm confusing with renaming an accuont/ppa [00:59] But the archive indices carry the PPA name. [01:00] best bet is to ask for the definitive answer on the lp dev list [01:01] If publish-distro noticed that the directory was missing from the filesystem and automatically went careful, that would eliminate the need for LOSAs to move things around manually, and fix the indices. [01:01] And only break sources.lists, which is inevitable. === cprov-afk is now known as cprov === Ursinha is now known as Ursinha-afk [02:32] hello === mac9416 is now known as macOut === Znova_ is now known as Snova_ [03:15] Where do I report bugs in launchpad itself? [03:16] First one would be there's no visible "Report a bug" for launchpad ;) [03:16] (or am I too blind?) [03:17] akurei: bugs.launchpad.net/launchpad/+filebug [03:18] Awesome, thanks! [03:50] When I'm using a local Launchpad's codehosting instance, how do I push/pull branches? [03:52] JoaoJoao: Use lp://dev/~path/to/branch URLs. [03:53] https://dev.launchpad.net/Code/HowToUseCodehostingLocally [03:56] how do I lp-login to my local launchpad instance? [03:57] I think the setup process might do something along those lines. [03:58] At least it puts sabdfl in the SSH config. [04:02] There's a script to add a user to the local db, IIRC. [04:02] make-lp-user? [04:02] That sounds like it. [04:02] JoaoJoao: yes [04:02] Under utilities/ somewhere. [04:06] okay, I created the admin user and tried to bzr push lp://dev/~admin/myproject/trunk [04:07] it asks me for my "joao@bazaar.launchpad.dev's password:" (joao is my os user) [04:13] um [04:14] JoaoJoao: do you have a bazaar.launchpad.dev section in ~/.ssh/config? [04:14] launchpad will never ask for a password, it sounds like you're connecting to port 22 still [04:22] dammit I had to generate new ssh keys :( [04:22] Why? [04:23] make-lp-user Just Worked for me. It even added my SSH keys. [04:23] I forgot the password [04:27] do I have to generate a new launchpad_id_dsa file? [04:32] no [04:33] that key is associated with the sabdfl account in the sample data [04:33] Oh I see [04:34] Looks like I screwed my instance beyond repair, I'm just going to create a new one [04:49] what do I need to add to .ssh/config exactly? [04:50] JoaoJoao: rocketfuel-setup does it for you. [04:53] hmm didn't do it for me [04:54] Actually, maybe it just tells you to do it. [04:54] I don't remember. [04:54] It certainly printed out the config snippet for me. [04:57] I created this .ssh/config: http://pastebin.com/m59d1f69c [04:58] and when I try to "bzr branch lp://dev/~joao/ae/trunk" it tells me "Agent admitted failure to sign using the key." [05:00] JoaoJoao: your ssh config is for bazaar.launchpad.dev, but your url has just "dev". [05:01] spiv: uh, no? [05:01] mwhudson: oh, duh [05:01] JoaoJoao: nevermind me :) [05:01] mwhudson: thanks :) [05:01] spiv: ;) [05:02] I'm sure I'm doing something stupid, as I always do [05:02] JoaoJoao: so what happens if you run "ssh @bazaar.launchpad.dev" ? [05:03] same thing [05:04] then i guess your ssh keys aren't set up right === _thumper_ is now known as thumper [05:18] I ran ssh-keygen again [05:23] dammit, ssh-keygen is generated wrong keys [05:23] generating [05:24] Why don't you just use your existing key? [05:25] I don't have one [05:25] Didn't [05:25] WOw. [05:25] It's been a while since I last used this computer [05:35] finally, it works [05:41] thanks for you help, wgrant, mwhudson [05:43] np [05:43] np === noodles775 is now known as noodles === noodles is now known as noodles775 [10:10] yo [10:10] i got a messed up stacked branch at lp:~aafshar/vellum/vellum-sphinx-docs, anyone knows how to fix [10:19] One question about the PPA package system [10:19] If I have my source in launchpad [10:19] the PPa is built automatically ? [10:19] mattions: not quite yet, but soon. [10:20] bigjools: are there details somewhere about source package branches and publishing to PPAs? ^^ [10:20] not yet [10:20] ok, I'll watch the launchpad blog [10:20] it's still being designed [10:21] that will be just amazing [10:21] anyone? [10:21] :) [10:21] :D [10:21] ronny: define "messed up" ? [10:21] bigjools: cant pull/branch it [10:21] i get a trace about some factory thing [10:21] ouch, absent content factory... [10:22] ronny: there is a bug in bzr versions < 1.16.1 [10:22] you need to get bzr 1.1.6.1 at least, preferably 1.17 [10:23] then you need to reconcile your local repo, delete the branch on LP, and re-push [10:24] bigjools: its not my own branch, someone else made it [10:24] let me try pulling it [10:25] ronny: right, I can't pull it either, the person who owns it needs to do what I just said [10:25] bigjools: There is a script around to fix branches like that. [10:25] oh really? [10:25] even better [10:25] (without having a good copy) [10:25] * wgrant searches. [10:26] good to know [10:26] * bigjools idly wonders if LP can reject clients with a certain version [10:26] Probably bug #354036, which has a script attached. [10:26] Launchpad bug 354036 in bzr "ErrorFromSmartServer - AbsentContentFactory object has no attribute 'get_bytes_as' exception while pulling from Launchpad" [Undecided,Confirmed] https://launchpad.net/bugs/354036 [10:49] wgrant: works fine, thanks [11:01] ronny: Great. [11:44] jtv: (or anyone else familiar with soyuz and translations). We're trying to fix bug 376686. It is a translation bug in Kubuntu, and we'd need to upload a new version of the kde-l10n-eu package (that's the one containing the POT and PO files to be imported into Rosetta) into -proposed. The question is whether translations for uploads in -proposed are also picked up in Rosetta. I think the answer is "no", but I'd like to check that with an LP dev :) [11:44] Launchpad bug 376686 in language-pack-kde-eu "Errors in KDE4 basque translation - Cyrillic characters and wrong names" [Undecided,New] https://launchpad.net/bugs/376686 [11:44] Wait... Cyrillic in the Basque translation!? [11:45] Ah, that's what the bug says. [11:46] dpm: if the packages aren't in main (or restricted iirc), they won't get picked up. [11:46] If they are in both main and proposed, it depends on what Soyuz does. [11:46] the package is in main and proposed [11:54] could any soyuz guys help us on that one ^? [11:54] dpm: I'm not sure myself, but bigjools might know? [11:55] I don't remember offhand, let me check [11:59] dpm, noodles775, jtv: translations are processed when they're in -proposed [12:00] bigjools: thanks a lot, noodles775, thanks for pointing us in the right direction :) [12:01] * jtv signs off, back later tonight === noodles775 is now known as noodles775-afk === mrevell is now known as mrevell-lunch === salgado-afk is now known as salgado === mrevell-lunch is now known as mrevell === noodles775-afk is now known as noodles775 === verterok_ is now known as verterok === kfogel changed the topic of #launchpad to: https://launchpad.net/ | Launchpad is now open sourced: https://dev.launchpad.net/ | Help contact: kfogel | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com | #launchpad-dev is the developer channel [14:01] can it be that the source code showing part of launchpad is down? [14:01] e.g. check out http://bazaar.launchpad.net/~mozillateam/mozilla-devscripts/mozilla-devscripts/revision/218 [14:01] bdrung_: the code browser may be down. it's not that uncommon. will check what's going on [14:04] bdrung_: yeah, I'm seeing that page down too [14:05] an unrelated issue is that the bazaar import failes. after some time it dies because of a timeout or connection problem. the last tries died after 200 minutes. https://code.launchpad.net/~vcs-imports/gnome-colors/trunk [14:05] bdrung_: sorted. thanks for letting us know [14:05] intellectronica: to wich one do you refer? [14:06] bdrung_: the source browser being down [14:06] intellectronica: no problem. :) [14:06] bdrung_: as for the code import, could you please open a question? someone can take a look at it later [14:07] intellectronica: for the vcs-imports group? [14:08] bdrung_: https://answers.edge.launchpad.net/launchpad/+addquestion [14:15] intellectronica: ok, done [14:15] https://answers.launchpad.net/launchpad/+question/78630 [14:42] hi === oubiwann_ is now known as oubiwann [14:48] could someone tell me where is the APIs source code? [14:50] eLBati: depends what you mean by API. the mechanism is implemented in lazr.restul. the launchpad api itself is annotated on the interfaces exposed. the python library for accessing the api is in launchpadlib [14:51] eLBati: you might be dissapointed to learn that there isn't a view or middleware to the API.. it really is a raw interface, where the result is returned to the client [14:52] Daviey: why is that disappointing? [14:53] thanks intellectronica. Daviey I knew [15:02] mrevell: I'm not sure how to handle https://answers.edge.launchpad.net/launchpad/+question/78131 ... advice? [15:02] * mrevell looks [15:02] mrevell: redirect to become a bug report against soyuz, maybe? [15:03] kfogel: I'd ask cprov to take a look [15:03] mrevell: thx [15:06] intellectronica: I assumed there were get/set methods tbh. [15:07] Daviey: you can create setters if necessary [15:07] intellectronica: really?! [15:07] Daviey: see for example how IBug.status is annotated [15:08] intellectronica: i care about get requests.. [15:09] Daviey: why is that? anyway, you can do that too, by exporting a new property and renaming it. but that's a bit of a hack === ursula_ is now known as Ursinha [15:15] cprov: can you take a look at https://answers.edge.launchpad.net/launchpad/+question/78131 ? I think you're more qualified to know what to do with it than I am. [15:15] kfogel: sure [15:15] cprov: thanks! [15:16] intellectronica: I was going to work on bug #340640 .. i thought it would be pretty trivial with an abstraction layer.. i didn't fully realise it was the raw return from the result. [15:16] Launchpad bug 340640 in launchpad-registry "Standard way of finding mugshot url, default if not set" [Low,Triaged] https://launchpad.net/bugs/340640 [15:19] Daviey: i think it would be better if you didn't have to implement this property every time you want to get the url of something. it's worth talking to leonardr and see if he thinks there's a nice general way to solve this problem [15:20] intellectronica: yeah.. with get/set methods it would have been trivial :P [15:20] daviey, intellectronica, can you give me a little background or should i just look at that bug? [15:21] Daviey: trivial to add, but not trivial to maintain. anyway, it's not difficult to do, but i'm not sure that's the right way to do it [15:21] leonardr: the bug does describe it quite well. [15:21] leonardr: the bug gives a pretty good description [15:22] leonardr: essentially, i think what Daviey wants is a nice way to get the url of an asset using the API. he suggested adding a new property the returns that, but i'm wondering if it can be solved in a more general way, since the object itself is already available via the API [15:23] intellectronica, daviey: it's been proposed to give a binary file object a json representation which would contain metadata, including a self_link [15:23] that self_link would be what you want, iiuc [15:23] yeah, that sounds like a good solution to me [15:23] and you only have to do that once [15:25] let me see if there's a bug for that already [15:27] \o/ [15:31] Someone is messing with the bugs in my launchpad project :( [15:31] bluesteelerwheeler [15:32] See https://bugs.edge.launchpad.net/sapidlib/+bug/181270 for example [15:32] Launchpad bug 181270 in sapidlib/lpuni-final "banned" [High,Fix committed] [15:41] daviey, intellectronica: https://bugs.edge.launchpad.net/ubuntu/+bug/406912 [15:41] Launchpad bug 406912 in ubuntu "Publish a JSON representation of a binary file containing metadata" [Undecided,New] [15:41] nice leonardr :) === deryck is now known as deryck[lunch] [16:25] mrevell: I'm going through the feedback@ queue right now. One fellow says "I didn't get a registrations mail. Please look up this problem." I have his real name, but searching for that in the lp front page search box turns up nothing. Should I just ask him what user account name he created, or is there some way to find it out? [16:25] kfogel: I think sinzui should be able to find his registration in the d/b, based on his email address. [16:26] mrevell: kfogel: I do not have db access [16:26] mrevell: I'd rather bother the requester than sinzui, though. I'll just ask him. (We shouldn't need db access for this, though, hmm.) [16:26] I search https://launchpad.net/people for the user name or the email address to find people [16:27] sinzui: thank you [16:27] kfogel: if the email address is not there, he does not have a profile... [16:27] kfogel, sinzui: I thought the issue here, though, was that the person hadn't received their confirmation token. Sinzui, haven't you previously approved accounts when this has happened? [16:28] kfogel: The confusion is that those email do not come from launchpad. that the SSO [16:29] mrevell, sinzui: first I want to make sure he was at the right URL, so I've followed up and we'll get more information. [16:29] kfogel: when a user uses the token in the email to create an account, a second process steps in also created a launchpad profile [16:29] aaaaaaaaaaack [16:29] mrevell, sinzui: his next mail says "problem solved". Note to self: look down the list for more mails from the same person. [16:30] :) [16:30] \o/ [16:31] mrevell: hey, is feedback@ archived anywhere? I want to be able to point to specific mails... [16:31] OH [16:31] mrevell: nm, I got it I think === yofel_ is now known as yofel [16:32] kfogel: Cool [16:32] mrevell: I went to lists.launchpad.net/.../feedback, but (interestingly) feedback@ is not hosted at launchpad. I think that's a bit odd, and maybe should change now, but that's a separate issue. [16:32] mrevell: it's at lists.canonical.com [16:33] kfogel, mrevell: yeah, it's interesting that it's not hosted here, but somehow.. I feel creating a new team for that list is just wrong! [16:33] kfogel: Yeah, but the feedback list itself is kinda incidental: it just happens to be a good way of getting it to more than one person. Ideally we'd probably have a ticketing system behind that email address, rather than a mailing list. [16:34] kiko: that's a feeling we'll keep having, then, since there are plenty of times when one wants a mailing list but not a team :-). [16:34] kiko: But, in this case, a team actually isn't a bad idea maybe... ? [16:34] kfogel, I hear you're going to talk to barry and sinzui about it.. [16:34] kiko: oh, the conversation is ongoing :-). But we haven't prioritized resolving it (or anyway I haven't) because the workaround is so easy: create a team despite the yucky feeling. [16:36] kiko, mrevell: oh, my main concern turns out to be moot anyway: "feedback {AT} launchpad.net" is the advertised address, which is great. [16:37] kfogel: Yeah, like I say, the list behind the addr. is kinda incidental as no one other than a handful of us ever see it. [16:38] mrevell: +1 === noodles775_ is now known as noodles775 === beuno is now known as beuno-lunch === noodles775 is now known as noodles775-afk === matsubara is now known as matsubara-lunch === deryck[lunch] is now known as deryck === dpm is now known as dpm-afk [17:44] Hi All! I got a problem when I upload source package to PPA. [17:44] "The source betaradio - 0.1.2-1ubuntu1 is already accepted in ubuntu/karmic and you cannot upload the same version within the same distribution. You have to modify the source version and re-upload." [17:45] But I think I have removed all packages in https://launchpad.net/~fourdollars/+archive/ppa [17:47] FourDollars: you can't upload the same version more than once, even if you delete it [17:49] bigjools: So I should change from 0.1.2-1ubuntu1 to what? Any suggest? [17:50] Ideally you would never use a vresion like 0.1.2-1ubuntu1 in a PPA since it looks like something that could be in Ubuntu itself [17:50] FourDollars: anything, just bump the version and it will work, I'll leave it to others to suggest appropriate versions for PPAs [17:50] like that :) [17:50] * bigjools -> out [17:52] hey guys. I try to import translations on launchpad from a branch. The pot file has been succefully imported, but the french translation is still "needs review" (and I can delete it otherwise), you to get it approved? Only the project leader can? https://translations.edge.launchpad.net/quickly/0.x/+imports [17:53] bigjools: maxb: Thanks for your suggestion. I think I have some idea. :D [17:54] I would probably carry on calling them -1ubuntu2, -1ubuntu3, etc. until the next upstream version is released, at which point you can change to -0ppa1 -0ppa2 etc. [17:54] or -0fourdollars1 etc. if you prefer [17:55] The essential aim is to make your PPA version less than the Debian/Ubuntu version that the package would have if it was added to the official distro [17:58] maxb: I am the upstream. :) [17:58] Ah :-) [17:59] maxb: So any suggestion about if ppa user is also the upstream. [17:59] Unless you have an intention of submitting it to Debian soon, I would probably just go with plain numbered revisions then [17:59] 0.1.2-2 etc. [18:03] If another guy package my software and submit it to Debian, there may be some conflict about the version. === mrevell is now known as mrevell-dinner [18:05] Are you planning to submit your package to Ubuntu itself rather than just a PPA? [18:05] The original source tar ball named betaradio-0.1.2.tar.bz2 so that Debian packager conventionally will name version as 0.1.2-1, right? [18:05] yes [18:06] maxb: This software is broken right now. ^^| [18:06] heh [18:06] I would probably carry on calling them -1ubuntu2, -1ubuntu3, etc. until the next upstream version is released, at which point you can change to -0ppa1 -0ppa2 etc. [18:06] I'd stick with that suggestion for now [18:07] maxb: But actually it is broken because of libmms borken. :P [18:07] It's fairly short and doesn't create any conflicts with potential future Debian/Ubuntu versions than already exists [18:09] maxb: So I have to fix libmms. https://code.launchpad.net/~fourdollars/libmms/devel [18:10] 0.1.2-1 < 0.1.2-1ubuntu1 or 0.1.2-1 > 0.1.2-1ubuntu1 ? [18:11] Is there any easy way to "copy packages" from karmic to my ppa, targetting jaunty? (I know this'll only work for _some_ packages, not all of them...) [18:12] I mean the official karmic builds, not packages from some ppa... [18:15] I have the similar question. I want to package for karmic/jaunty/intrepid/hardy. [18:15] But I have to edit debian/changelog four times. [18:16] FourDollars: no, you can just "copy packages" and target a different series... [18:17] alkisg: I tred that. Launchpad don't let me do that. [18:17] FourDollars: I do that frequently, so you must have selected something wrong... [18:18] alkisg: Thanks for your information. I will try that again. :) [18:21] alkisg: Yes there is but the page is somewhat buried. Let me find it. [18:21] Thank you maxb [18:23] * betaradio 0.1.2-1ubuntu2 in karmic (same version already building in the destination archive for Karmic) [18:23] I think I choose "Destination series" as Jaunty. [18:24] Choose "Copy options" as "Rebuild the copied sources" [18:24] FourDollars: try with "Copy existing binaries", I don't remember which of the two did the trick [18:26] alkisg: "Copy existing binaries" doesn't rebuild from source code right? So this option may cause some compatible problem. === matsubara-lunch is now known as matsubara [18:27] Yeah, I guess you're right on this. [18:28] * betaradio 0.1.2-1ubuntu2 in karmic (source has no binaries to be copied) [18:29] alkisg: So i have edit debian/changelog four times for karmic/jaunty/intrepid/hardy. [18:30] FourDollars: I'm not experienced with launchpad, I don't know if there's any other alternatives. Well I know one other alternative, you can specify the full path to the series in dput.cf [18:30] http://www.centos.org/ <--- this is precisely why I request that teams have an option for a "co-owner" [18:31] * kfogel is away: kfogel-food [18:31] FourDollars: i.e. incoming = ~username/ppa/ubuntu/jaunty to upload specifically to jaunty === kfogel is now known as kfogel-food [18:32] alkisg: https://help.launchpad.net/Packaging/PPA/Uploading [18:33] ? [18:33] alkisg: That page mention "incoming = ~//ubuntu/" [18:34] Yes, that uses the series from the changelog, and the method I'm saying uses the series from dput.cf, what's your point? [18:35] So I think you can have 4 sections in dput.cf, one for each series... [18:36] alkisg: Have you try that at any PPA? [18:36] Yes, I used it to upload a package of mine that had "stable" in the changelog, and I put it to jaunty series [18:38] alkisg: I see. Thanks for your suggestion. I will try that. :) === beuno-lunch is now known as beuno [18:45] leonardr: did you mean for bug 406912 to go somewhere else? [18:45] Launchpad bug 406912 in ubuntu "Publish a JSON representation of a binary file containing metadata" [Undecided,New] https://launchpad.net/bugs/406912 [18:46] bdmurray: aargh, yes. i meant to file it in lazr.restful [18:48] alkisg: The source betaradio - 0.1.2-1ubuntu2 is already accepted in ubuntu/karmic and you cannot upload the same version within the same distribution. You have to modify the source version and re-upload. [18:50] alkisg: The URL you want is https://launchpad.net/ubuntu/+archive/primary/+copy-packages?field.series_filter=karmic&field.name_filter=PACKAGE_YOU_WANT [18:50] FourDollars: That was all I know, can't tell you anything else :) [18:50] maxb: thanks a lot ! [18:50] Because the number of packages in the primary archive is so huge you have to go straight to the URL including some filters, or the DB query times out [18:50] Ah, ok, that's not a problem [18:51] Wow, that was perfect, it'll be really really handy for backporting stuff for some schools I administer. Thanks again! [18:52] alkisg: I do *not* recommend this for backporting [18:53] maxb: don't worry, I'll only use it when I know it'll work [18:53] If you do this, I recommend you only do it with the "copy binaries" option [18:53] ok [18:53] If you use the "rebuild sources" option, you risk seriously screwing up future upgrades of the machines in question [18:54] alkisg: Have you ever upload to jaunty, and upload to others like karmic/intrepid/hardy? [18:54] maxb: Hmmm I don't understand why would that affect upgrading. Of course I'll trust what you're saying and do it, but if you have some time to explain, I'm all ears :) [18:55] FourDollars: only with the "copy binaries" option [18:56] alkisg: If you copy the source with a particular version number into a previous series, rebuilding the binary, you get a *different* binary deb with the same version number as the official one - but potentially built with different dependencies and series-specific quirks. [18:56] alkisg: You use dput to upload source package, then use "copy binaries" option to copy from jaunty to others like karmic/intrepid/hardy right? [18:56] Because the version number is the same, the package manager will NOT know to upgrade it to the official one for the proper later series when an upgrade is eventually done. [18:56] FourDollars: right [18:57] maxb: but if I use "copy binaries", and an update is later on available, it'll update it? [18:57] * alkisg needs to read the debian/ubuntu policy once more :( [18:58] alkisg: no - but it means you downloaded the official binary for that version in the first place - not a differently built version masquerading as it === dpm-afk is now known as dpm [18:59] But still, it wasn't the official binary for my series; it was the official binary for another series, so if I wanted to do this right I should have put a ~ppa1 in it to get it properly upgraded... [19:00] But ok, I get your point now, thanks :) [19:00] didrocks: you probably have noticed, but they've already been imported and quickly is now translatable at https://translations.edge.launchpad.net/quickly/0.x :) [19:00] So I have to edit debian/changelog and upload four times for karmic/jaunty/intrepid/hardy. XD [19:01] FourDollars: yes. I use a script to do this. [19:01] http://paste.ubuntu.com/237079/ for example [19:01] maxb: That's a good idea. :D [19:04] Hello launchpad friends! Anyone know why https://code.launchpad.net/wxbanker seems to be lying to me? The branch lp:~kolmis/wxbanker/transaction-tagging says "Last modified" 47 hours ago in the summary but if you click there hasn't been a commit in weeks. [19:12] Why do I have (community) beside my name after I performed a review on a merge proposal? [19:21] I know this is probably offtopic, but more developers hang out in here than do in #ubuntu, but is there a global configuration directive for "submit anonymous usage statistics" anywhere in ubuntu or gnome? === kfogel-food is now known as kfogel [19:26] dpm: thanks, yes. It was not obvious to me that it was a question of time :) I only wonder why I can't associate ~quickly/quickly/translations as an export translation branch === salgado_ is now known as salgado [19:29] didrocks: hehe. You might also consider choosing a different translations permission rather than Open. Open is good for casual contributions, but sometimes those translation suffer from lower quality and inconsistency. I'd recommend Structured and assigned to the launchpad-translators group (if quickly is not associated to a distro) or ubuntu-translators (if it is associated to Ubuntu). You'll find more information here, which will help you decide what's [19:29] best for the project -> https://help.launchpad.net/Translations/YourProject#Choosing%20a%20permissions%20policy === noodles775-afk is now known as noodles775 [19:43] bigjools or cprov: can you please kick the PPA buildd "osmium"? looks like it got stuck: https://edge.launchpad.net/builders/osmium [19:44] geser: let me check [19:44] hi, has the osmium builder got stuck? it should not take 24hours to compile a small package [19:50] geser: source being built by other builder, osmium reset. [19:53] cprov thanks === deryck is now known as deryck[break] === Guest35382 is now known as Edwin-lunch === deryck[break] is now known as deryck === sale_ is now known as sale [20:47] dpm: thanks for the advice. I will consider it. I just have to see why I can't associate the auto export in branch, but it will come :) [21:07] hey, can someone help me with a ppa? === Edwin-lunch is now known as EdwinGrubbs [21:10] what's the question/problem? [21:12] geser: can i delete old imports to the ppa? i haven't been able to [21:20] geser: i have changed the versioning scheme on a package... and so an older version appears to be newer than what i am trying to upload... causes the new version to be rejected [21:22] pace_t_zulu: in that case you need to introduce an epoch in the version. making in that way bigger the current one [21:23] geser: funny you should mention that... the old version is using an epoch [21:23] geser: i decided to go back to the date [21:23] I'm not sure how exactly the deletion works, but it's mostly marking a package as deleted as you can resurrect it for some time so LP will now about that version for that time too [21:24] pace_t_zulu: then you need to increase the epoch [21:24] and your users will benefit from it too else they don't get any updates from your PPA [21:24] geser: so the answer to my question is that packages cannot be deleted from a ppa... perhaps i can delete the ppa and create it again === salgado is now known as salgado-afk [21:24] geser: shouldn't have any users of my ppa just yet [21:25] IIRC you can't delete a PPA yet, but you should be able to mark it as disabled and start a new one if you want to go this way [21:26] geser: seems as if PPAs are still a bit rough in terms of implementation... [21:29] some parts yes, but most parts work correctly === mwhudson_ is now known as mwhudson === fta_ is now known as fta [22:05] What do y'all make of this? (pardon me pasting) [22:05] mac9416@mac9416-laptop:~/devel$ bzr commit -m "Added meta.py to libkeryx and keryx.py to the root directory" [22:05] Committing to: /home/mac9416/devel/ [22:05] aborting commit write group: PointlessCommit(No changes to commit) [22:05] bzr: ERROR: no changes to commit. use --unchanged to commit anyhow [22:05] mac9416@mac9416-laptop:~/devel$ [22:06] bzr does not believe there are any changes to commit. [22:06] mac9416, what does "bzr status" say? [22:06] I'm very certain I have made changes. Can I fool bzr? [22:06] Lemme check [22:06] mac9416: try "bzr status" [22:06] see what that reports [22:06] mac9416: have you made changes to versioned files? [22:07] did you use 'bzr add' for your new files/directories? :) [22:07] 0_o, let me post the results of bzr status :-) [22:07] mac9416@mac9416-laptop:~/devel$ bzr status [22:07] unknown: [22:07] keryx.py [22:07] libkeryx/meta.py [22:07] mac9416@mac9416-laptop:~/devel$ [22:07] there you go. [22:07] mac9416, you have not added those files [22:07] Ah, OK [22:08] So, bzr add filename? [22:08] pace_t_zulu, seems everyone I know hangs out here ;-) [22:09] mac9416: indeed [22:09] mac9416, or "bzr add", which will add everything [22:09] OK, that's simple enough. Thanks [22:09] mac9416: bzr add keryx.py libkeryx/meta.py [22:09] mac9416: bzr commit -m "Added meta.py to libkeryx and keryx.py to the root directory" [22:09] It worked! :-) [22:10] word [22:11] And as if I haven't caused enough trouble already: [22:11] mac9416@mac9416-laptop:~/devel$ bzr push lp:~mac9416/keryx/devel/trunk [22:11] Enter passphrase for key '/home/mac9416/.ssh/id_rsa': [22:11] bzr: ERROR: Permission denied: "/~mac9416/keryx/devel/trunk": : Cannot create branch at '/~mac9416/keryx/devel/trunk' [22:11] mac9416@mac9416-laptop:~/devel$ bzr lp-login mac9416 [22:11] mac9416@mac9416-laptop:~/devel$ bzr push lp:~mac9416/keryx/devel/trunk [22:12] Enter passphrase for key '/home/mac9416/.ssh/id_rsa': [22:12] bzr: ERROR: Permission denied: "/~mac9416/keryx/devel/trunk": : Cannot create branch at '/~mac9416/keryx/devel/trunk' [22:12] Can y'all tell I'm new at this? [22:12] Nah [22:13] mac9416, you seem to have too many parameters? [22:13] devel/trunk? [22:14] Perhaps, I thought I was supposed to put /devel there, so I did :-P [22:14] the /trunk bit should be dropped [22:14] OK [22:14] https://code.edge.launchpad.net/~keryx/keryx/devel [22:15] mac9416, and, you seem to have configured your name incorrectly [22:15] I know, it's wierd [22:15] try: bzr whoami "Firstname Lastname " [22:16] and make sure you register that email address in Launchpad to get those commits linked to you === kklimonda is now known as Guest41062 [22:17] Well, I think it's registered. That's where I get emails from, is that good? [22:17] Bug reports and such [22:18] yes [22:18] just need to fix the whoami in bzr then [22:18] OK, the push worked. [22:18] OK, did that. [22:19] Everything appears to have worked. Thanks! === _kklimonda is now known as kklimonda_ === kklimonda_ is now known as Guest67854 === Guest67854 is now known as kklimonda__ [22:22] mac9416: paste.ubuntu.com in the future... [22:23] pace_t_zulu, my humble apologies [22:23] mac9416: no prob man :) ... just trying to help [22:23] * mac9416 == lazy [22:23] S'alright :-) === matsubara is now known as matsubara-dinner === kfogel changed the topic of #launchpad to: https://launchpad.net/ | 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 === kklimonda__ is now known as kklimonda === kklimonda is now known as Guest30301 === Guest30301 is now known as kklimonda