| === funkyHat is now known as funkyCat | ||
| === funkyCat is now known as funkyHat | ||
| === lamont` is now known as lamont | ||
| tsimpson | Gnea: the one at https://launchpad.net/~<user>/+archive/<ppa name> | 04:28 |
|---|---|---|
| tsimpson | not at ppa.launchpad.net | 04:28 |
| Gnea | tsimpson: it's not there | 04:34 |
| tsimpson | which PPA? | 04:34 |
| Gnea | pulseaudio | 04:34 |
| wgrant | I seem to be missing context. | 04:34 |
| Gnea | https://launchpad.net/~bogdanb/+archive/ppa/pulseaudio | 04:34 |
| Gnea | I'm trying to obtain the key for the pulseaudio ppa so that I can download it | 04:35 |
| wgrant | Argh, bug. | 04:35 |
| wgrant | There's no PPA named pulseaudio there. | 04:35 |
| Gnea | yeah... and I wonder if I even have the right username | 04:36 |
| wgrant | I doubt it. | 04:36 |
| dtchen | you probably don't | 04:36 |
| Gnea | it's just not obvious | 04:36 |
| Gnea | ah ha https://launchpad.net/~ubuntu-audio-dev/+archive/ppa | 04:37 |
| wgrant | That's the one. | 04:37 |
| dtchen | i probably need to blog about that more widely | 04:37 |
| Gnea | thank you | 04:37 |
| Gnea | okay, I thought ppa's were for jaunty as well as karmic - did I miss the bus on this one? | 04:42 |
| wgrant | Gnea: They are for whatever the owner decides. | 04:43 |
| wgrant | This one only has packages for Karmic. | 04:43 |
| Gnea | I see | 04:44 |
| Gnea | just found the ones by themosu | 04:44 |
| wgrant | His should be good. | 04:44 |
| Gnea | they look like they've been around for a bit | 04:45 |
| dtchen | we're not building for jaunty in that ppa [yet] | 04:45 |
| Gnea | ok cool | 04:45 |
| dtchen | particularly since upstream git keeps sprouting versioned build-deps, like automake 1.11 and crackful libtool | 04:45 |
| Gnea | ok, now dist-upgrade is working properly | 04:46 |
| wgrant | dtchen: Loooovely. | 04:46 |
| Gnea | that's totally out of my range :) | 04:46 |
| jmarsden | I'm getting a Timeout Error (Error ID: OOPS-1323F679) when trying to file a bug in LP ... not on edge, on the real LP... is this a known issue? | 07:11 |
| ubottu | https://lp-oops.canonical.com/oops.py/?oopsid=1323F679 | 07:11 |
| wgrant | jmarsden: Sort of. Try reducing the number of terms in your initial summary -- once it gives you the list of possible duplicates, you can restore it to the full length. | 07:14 |
| jmarsden | Strange... OK, thanks. | 07:14 |
| wgrant | This will eventually be fixed by doing the search that times out via AJAX. | 07:14 |
| Hilikus | how can i add a dependency in my package on a package that's in the backport repo? | 08:09 |
| wgrant | Hilikus: You could copy the package from -backports into your PPA, or tell your PPA that it can depend on all backports. | 08:10 |
| wgrant | The latter is easier, but obviously might have other side-effects. | 08:11 |
| Hilikus | i also depend on a package from another PPA. i didn't know i could copy other packages to my ppa | 08:11 |
| wgrant | Sometimes depending on the whole other PPA is better. | 08:11 |
| wgrant | But if you just want to copy a package, you can go to the PPA with the package and select 'Copy packages' | 08:12 |
| Hilikus | wgrant: why do you say sometimes it's better? | 08:13 |
| wgrant | Hilikus: Sometimes I might be maintaining a PPA for one piece of software, and then create another PPA for something which depends on the first piece of software. | 08:14 |
| wgrant | It's much easier to declare a dependency on the first PPA, so I don't have to worry about copying new versions around. | 08:14 |
| wgrant | It will just magically get them from the other PPA. | 08:14 |
| Hilikus | i see | 08:16 |
| Hilikus | wgrant: ok i managed to copy the package from the other PPA but i don't know how to copy the one from backport | 08:22 |
| wgrant | Hilikus: If you're lucky, you'll be able to use https://edge.launchpad.net/ubuntu/+archive/primary/+copy-packages?field.name_filter=debhelper&field.status_filter=published&field.series_filter=any. But that is unsupported and very often times out, so you might have to use the API. | 08:25 |
| === ripps_ is now known as ripps | ||
| === sale_ is now known as sale | ||
| === cprov-afk is now known as faces | ||
| === faces is now known as cprov | ||
| TLE | hallo I was wondering if any of you can tell em why lauchpad don't attribute my commits to me | 13:28 |
| TLE | https://code.launchpad.net/~pyg3t-dev-team/pyg3t/trunk | 13:29 |
| TLE | as you can see, there are written as if some, to launchpad unknown person har commited | 13:30 |
| wgrant | TLE: You're missing the angled brackets around your email address. It should be something like 'Some Person <blah@example.com>' | 13:31 |
| TLE | I will try | 13:32 |
| TLE | Do'h! | 13:50 |
| TLE | thanks wgrant, it works | 13:50 |
| * TLE hides | 13:50 | |
| wgrant | TLE: Excellent. | 13:50 |
| === JanC_ is now known as JanC | ||
| Ampelbein | hi there. what's up with the armel builders? 160 queued items and they idle around... did they take a day off? ;-) | 19:17 |
| Hilikus | hey guys | 19:48 |
| Hilikus | i dled a package from a ppa that doesnt build. i fixed it and now it works. but the othre PPA keeps producing a nightly failde build. is there some way i can keep like a patch of the fix to apply it to the newer packages? | 19:49 |
| Ampelbein | Hilikus: how about notifying the the owner of the failing ppa about the issue? that way it can be fixed for real. | 19:57 |
| Hilikus | Ampelbein: they're busy doing something else. this is the amarok nightly build. they said it is going to be fixed in 1-2 months | 19:57 |
| Daviey | Hilikus: surely if you have a working patch, they wouldn't mind applying it to their trunk? | 19:58 |
| Hilikus | its not a patch on the code. its a patch on the packaging | 19:58 |
| Hilikus | just different dependencies in debian/control | 19:58 |
| Hilikus | if i can make a patch of the packaging and not on the code itself i could try to send it to them | 19:59 |
| Daviey | Hilikus: i'm saying, if there builds are failing every night.. and it looks like you have a 1 line patch.. surely the ppa owner team would apply it | 19:59 |
| === _neversfelde is now known as neversfelde | ||
| pcabido | Hi, is there any easy way to reverse the latest pushed code to a branch? | 23:16 |
| beuno | pcabido, you need to uncommit, and push --overwrite | 23:16 |
| pcabido | beuno: I see.. and what if it was the result of a merge? | 23:17 |
| pcabido | that's my case | 23:17 |
| pcabido | I don't have the source of the merge any more | 23:17 |
| wgrant | Is the code that you want to revert inside the merge? | 23:19 |
| wgrant | Or just before it? | 23:19 |
| wgrant | Do you want to revert the entire merge? | 23:19 |
| pcabido | wgrant: I want to revert the entire merge, but I don't have the source of the merge (the main branch) anymore, and that main branch that I don't have is what I want to get out of the mess | 23:22 |
| pcabido | is it possible? | 23:22 |
| wgrant | pcabido: This is getting complicated. Can you explain the whole situation? | 23:23 |
| wgrant | If you've merged those revisions into another branch, it's easy enough to get the old branch back. | 23:23 |
| pcabido | wgrant: yes, I mage bzr merge ../br2 and now I want to see if I can the br2 branch back | 23:23 |
| pcabido | mage = made | 23:25 |
| wgrant | pcabido: Well, first take a backup of the branches, just in case. | 23:26 |
| wgrant | pcabido: Then we need to find out the ID of the last revision that was on br2. Do that using 'bzr log -n0 --show-ids' | 23:26 |
| pcabido | wgrant: did that | 23:26 |
| wgrant | pcabido: Once you have that revision ID, 'bzr pull -r revid:<REVISIONID> .' should turn the current branch into your old branch. | 23:28 |
| pcabido | wgrant: thanks for the help, the problem is now solved :) | 23:39 |
| wgrant | pcabido: np | 23:39 |
| === spOO` is now known as spO | ||
| === spOO` is now known as spO | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!