=== kiko is now known as kiko-afk === RAOF_ is now known as RAOF === asac_ is now known as asac === popey_ is now known as popey [09:15] New bug: #190407 in launchpad "(view key text) link from PPA build page gives 404 error" [Undecided,New] https://launchpad.net/bugs/190407 === Seveaz is now known as Seveas [11:10] Any reason for https://launchpad.net/bugs/162021 to link to https://bugs.edge.launchpad.net/ubuntu/+source/gnome-control-center/+bug/16202 but not for https://bugs.edge.launchpad.net/bugs/162021/comments/4 not to link to https://bugs.edge.launchpad.net/ubuntu/+source/gnome-control-center/+bug/162021/comments/4 ? [11:10] Launchpad bug 162021 in gnome-control-center "Cannot use Konsole as default terminal application" [Wishlist,New] - Assigned to Ubuntu Desktop Bugs (desktop-bugs) [14:48] hi channel [14:48] how do I publish a package in my PPA for both Gutsy and Hardy [14:51] if I change in the changelog from gutsy to hardy and again try to dput, it says "Already uploaded, doing nothing for package_version_source.changes" [14:51] so do I need to change version also, hmm...? [15:09] abbe: remove the .upload file from the last upload and dput then [15:50] geser: thanks [16:02] geser: it says MD5 sum of uploaded file does not match existing file in archive. I did s/gutsy/hardy/ to 'debian/changelog' file [16:03] abbe: have you also changed the version number, you can have only one version number of a package for all releases [16:05] geser: nop [16:05] geser: I've not change any version no. in packages [16:06] abbe: your upload to your hardy PPA was accepted, right? [16:06] geser: nop, it reject with above error [16:07] geser: I've that same version package already built in gutsy PPA [16:08] ok [16:08] geser: it seems I need to modify version field [16:09] geser: any other thing I can try [16:09] abbe: modifing the version should do it (if there is no other error) [16:11] geser: shall I need name of distro also in version field, like kde4 PPA has [16:15] abbe: there is no requirement to do it this way, but often the release is placed into the version string to have different version for each release [16:15] geser: okay, then whats the preferred way ? if you want I can pastebin the whole mail somewhere [16:17] abbe: it's a matter of personal style how you do it, but the easiest way should be to append the release to the version string [16:18] geser: okay, but in my case I'm getting that error, I didn't wanted to change version string [16:19] abbe: what's the version string you use for your gutsy PPA? [16:19] geser: 5.1-2 [16:19] geser: here is the PPA: http://ppa.launchpad.net/wahjava/ubuntu/pool/main/f/freenet6/ [16:22] abbe: if you want it also in your hardy PPA, you need to change the version to e.g. 5.1-2hardy or something like that [16:23] geser: okay, thanks [16:31] is it possible to use gutsy-backports packages in PPA? [16:31] or for that matter packages from other PPAs? [16:32] I want to package a plasmoid for gutsy which obviously needs libplasma, which is not in gutsy but only in either the backports or PPAs === abbe_ is now known as abbe [18:49] I'm trying to upload a patched 2.6.22 kernel for Gutsy, but it is rejecting it due to having a Hardy kernel in my PPA already. This is the error: "linux-libc-dev_2.6.22-14.51.0cwi2_amd64.deb: Version older than that in the archive. 2.6.22-14.51.0cwi2 <= 2.6.24-5.9.cwi2" [18:49] is there any way to work around this? [18:56] New bug: #190529 in launchpad "Launchpad has conflicting email address matching rules" [Low,Confirmed] https://launchpad.net/bugs/190529 [19:01] bah! nevermind, i used dch on my changelog on the hardy machine, which changed the DIST. [19:45] hey all [19:47] didn't see any mention in the help pages nor "answers", but how do you set a meeting in LP ? [19:52] No`, launchpad.net/+sprints [19:52] errr... error page [19:53] sorry. [19:53] https://edge.launchpad.net/sprints [19:54] ok [19:54] kiko: can I register an IRC meeting? [19:54] well, not really [19:54] you should probably just use a project announcement for that [19:55] all right, thanks [19:55] most welcome [19:56] kiko: could be nice to have a "send message to all team member" action somewhere [19:56] IMHO [19:57] yeah, that's a long-standing request. [19:57] heh [19:58] maybe submitting a bug to the project notifies all team members, and... [19:58] :) [20:03] it does indeed ;) [20:52] Hi there, I am having trouble with "bzr get lp:viewmail", it gets redirected to a URl which seems to be wrong, but IMHO should be ok. [20:57] bzr branch lp:viewmail [20:57] lp:viewmail is redirected to bzr+ssh://hack-robf@bazaar.launchpad.net/~hack-robf/viewmail/trunk/ [20:57] bzr: ERROR: Not a branch: "bzr+ssh://hack-robf@bazaar.launchpad.net/~hack-robf/viewmail/trunk/". [20:58] hmmm [20:58] seem like there's no branch there! [20:59] rjwf, does branching that URL directly work? bet not. [21:01] rjwf, is hack-robf your LP user? [21:02] if not, make sure you run: bzr launchpad-login yourusername [21:02] Yes, hack-robf that's me. [21:02] And yes the branch from the URL works. [21:03] E.g. "bzr branch http://bazaar.launchpad.net/~hack-robf/viewmail/trunk" work, just from lp:viewmail it does not. [21:03] well [21:03] that's not the exact same URL [21:03] bzr branch bzr+ssh://hack-robf@bazaar.launchpad.net/~hack-robf/viewmail/trunk/ would be [21:03] rjwf, why "get"? have you aliased it? [21:04] oh, wait, it's a standard alias [21:04] :X [21:04] "get" was there since I know BZR. [21:05] yes yes, my bad [21:06] Yes, it is not the same URL, but it is the URL which works. The otherone is the URL I pushed to. [21:06] Both URLs taken from https://code.launchpad.net/~hack-robf/viewmail/trunk [21:07] rjwf, I'm thinking it might have something to do with the - in your user name, I'm looking for bugs related to that [21:07] And there is another oddity, if I try to push now I get [21:08] bzr: ERROR: Target directory bzr+ssh://hack-robf@bazaar.launchpad.net/%7Ehack-robf/viewmail/trunk/ already exists, but does not have a valid .bzr directory. Supply --use-existing-dir to push there anyway. [21:08] Must I wait for some time after the initial push before I can download and push to that URL? [21:09] rjwf, not normally, no [21:11] rjwf, you might want to move it to #bzr, more people might be able to help there :D [21:14] Hmm are those in #bzr are also working on LP? [21:16] o.k. I try my luck at #bzr, thanks and bye. [21:28] The answer was: My bzr-dev was not uptodate. === kiko is now known as kiko-afk === doko_ is now known as doko