| exarkun | maxb: I hope you're still interested :) | 02:03 |
|---|---|---|
| stalcup | how does one configure the new ppa to uploads | 03:37 |
| stalcup | does dput.cfg need edited? | 03:38 |
| wgrant | stalcup: Does the PPA page not have dput instructions at the top? | 04:06 |
| stalcup | wgrant: firgured it out, thanks | 04:08 |
| stalcup | I'm going old-school | 04:08 |
| === Ursinha-afk is now known as Ursinha | ||
| === Lcawte|Away is now known as Lcawte | ||
| leoquant | error ID OOPS-1834G743 i | 10:24 |
| ubot5 | https://lp-oops.canonical.com/oops.py/?oopsid=1834G743 | 10:24 |
| wgrant | leoquant: What were you doing? | 10:26 |
| leoquant | view this page: Mailing List Beta Testers | 10:27 |
| leoquant | via: https://launchpad.net/~ubuntu-loco-enthusiasts | 10:28 |
| wgrant | leoquant: That team has been deleted. I'm not sure why it's still showing up there. | 10:29 |
| leoquant | ok thx wgrant | 10:29 |
| === yofel_ is now known as yofel | ||
| === Lcawte is now known as Lcawte|Away | ||
| === oubiwann_ is now known as oubiwann | ||
| billi | i | 13:07 |
| billi | hi | 13:07 |
| billi | i have a proble with launchpad | 13:07 |
| billi | it seems that renaming a branch somehow messed all of my repository | 13:08 |
| === Lcawte|Away is now known as Lcawte | ||
| === shadeslayer is now known as kshadeslayer | ||
| StylusEater | when I try to access ... bazaar.launchpad.net/~maria-captains/maria/5.3/annotate/head:/sql/field.cc ... I get a "Sorry, there was a problem connecting to the launchpad server." I first encountered this last night 10:00PM (GMT-5) and it still an issue this morning 10:52AM | 15:52 |
| === apachelogger is now known as kgnomelogger | ||
| === kshadeslayer is now known as kglibslayer | ||
| === kglibslayer is now known as kshadeslayer | ||
| bullgard4 | Launchpad stinks: "GNOME Panel does not use Launchpad for bug tracking." | 17:52 |
| jelmer | bullgard4: how so? GNOME panels are probably tracked in GNOME's bugzilla. | 17:55 |
| bullgard4 | jelmer: I do not understand your "how so?" It is too short to be comprehensible. -- WWW: "Launchpad is a large web application that Ubuntu uses for collaboration, translation, bug tracking, revision control." | 18:02 |
| jcsackett | bullgard4: gnome panel tracks its bugs in gnome's bugzilla, as jelmer said. https://bugzilla.gnome.org/browse.cgi?product=gnome-panel | 18:05 |
| jcsackett | b/c launchpad encourages connection to upstream projects, it provides the option for project maintainers to set how they use launchpad. | 18:06 |
| jcsackett | if they don't use launchpad's bug tracking utility, they can set it to tell people that, so that bugs are not filed somewhere that won't necessarily be looked at. | 18:06 |
| mgedmin | http://bazaar.launchpad.net/~mgedmin/gtimelog/app-indicator/revision/148 gives me an Oops! | 18:57 |
| mgedmin | I can't bzr branch lp:~mgedmin/gtimelog/app-indicator -- bzr gives me some kind of obscure error | 18:57 |
| lifeless | mgedmin: just upgrade the other branch too | 19:40 |
| lifeless | mgedmin: there is a button on lp to cause that to happen | 19:41 |
| mgedmin | I pressed it a while ago | 19:41 |
| mgedmin | http://bazaar.launchpad.net/~mgedmin/gtimelog/app-indicator/revision/148 still oopses | 19:42 |
| lifeless | !oops | 19:42 |
| ubot5 | An OOPS is a system error in launchpad, please see https://help.launchpad.net/Oops | 19:42 |
| mgedmin | https://code.launchpad.net/~mgedmin/gtimelog/app-indicator kept saying "the branch is being upgraded" for a long time, now it stopped... | 19:42 |
| lifeless | blah what I mean to say is that I need the oops code | 19:44 |
| lifeless | to help | 19:44 |
| mgedmin | I'm pretty sure if you click on that url, you'll get one :) | 19:44 |
| lifeless | but if it hadn't finished the upgrade, it will be the incompatible exception | 19:44 |
| lifeless | if its finished upgrading, try again | 19:44 |
| mgedmin | that's what I'm saying: the branch was broken, I pressed the upgrade button 50 minutes ago, now it appears to have been upgraded, and it is still broken | 19:45 |
| mgedmin | brokenness manifests by oopes on the launchpad branch browser | 19:45 |
| mgedmin | and bzr exceptions while trying to bzr branch lp:~mgedmin/gtimelog/app-indicator | 19:45 |
| mgedmin | actually it appears that the upgrade failed, since repository format is still the same as it was before | 19:47 |
| mgedmin | hmm | 19:52 |
| mgedmin | there are actually three stacked repositories here: ~gtimelog-dev/gtimelog/trunk -> ~mgedmin/gtimelog/trunk -> ~mgedmin/gtimelog/app-indicators | 19:52 |
| mgedmin | the first one is using 2a, the other two knitpack6richroot | 19:52 |
| mgedmin | what if I try to upgrade the middle one? | 19:53 |
| lifeless | mgedmin: thats a good thing to do | 19:54 |
| lifeless | mgedmin: as for whether I see it or not, thats beside the point: user authentication and privileges can affect who gets what oops | 19:54 |
| lifeless | mgedmin: and there is a delayed rsync to get them to the analysis server | 19:54 |
| lifeless | mgedmin: so I *always* get the OOPS id the user has seen rather than looking at the link myself | 19:55 |
| mgedmin | sounds reasonable | 19:55 |
| mgedmin | and it looks like upgrading the middle repository fixed everything | 19:56 |
| lifeless | great! | 19:56 |
| lifeless | what was one of the OOPS please; I want to file a bug (thats a normal [but undesirable] situation and we shouldn't error like that) | 19:56 |
| mgedmin | putting OOPS numbers into page titles was a *great* idea | 19:57 |
| lifeless | huh? it should be in the body | 19:57 |
| mgedmin | I can recover them from my browser history now that all those tabs are long closed | 19:57 |
| mgedmin | OOPS-1834CBB6546 | 19:57 |
| ubot5 | https://lp-oops.canonical.com/oops.py/?oopsid=1834CBB6546 | 19:57 |
| lifeless | oh, as-well, nice | 19:57 |
| lifeless | thank you | 19:57 |
| mgedmin | and there was also OOPS-1834CBB6545 but it'll probably be the same | 19:58 |
| ubot5 | https://lp-oops.canonical.com/oops.py/?oopsid=1834CBB6545 | 19:58 |
| mgedmin | if you want the backstory | 19:58 |
| mgedmin | there was a ~mgedmin/gtimelog/trunk, I branched ~mgedmin/gtimelog/app-indicator off it, then I changed the owner of gtimelog/trunk to ~gtimelog-dev/ | 19:59 |
| mgedmin | this broke the app-indicator branch (stacked branches don't like it when you move their parent from under them; I don't recall if I filed a bug about that, but I should've) | 19:59 |
| mgedmin | and I had to push my ~gtimelog-dev/gtimelog/trunk into ~mgedmin/gtimelog/trunk to unbreak the app-indicator branch | 20:00 |
| mgedmin | that's how -- entirely unintentionally -- I ended up with a chain of three stacked repos | 20:00 |
| mgedmin | and that's why I completely forgot about the middle one | 20:00 |
| vishy | Hello, everyone. I'm trying to upload a package to a ppa. It is failing to build because it needs a newer version of another package. There is another ppa that has this package, so I would like to download the package from that ppa and upload it to mine. I've done apt-get source <package> to get the relevant files. Is there any way to upload this directly without changes? Or do I need to build the package and generate a changes fil | 20:04 |
| vishy | upload. | 20:04 |
| lifeless | vishy: why don't you just copy it in the web ui ? | 20:06 |
| vishy | lifeless: there is a way to copy packages from other ppas in the web ui? | 20:07 |
| lifeless | yes | 20:07 |
| lifeless | biab | 20:07 |
| vishy | ah add ppa dependencies? | 20:08 |
| kshadeslayer | isnt 'When Complete' on https://code.launchpad.net/~neon/+recipe/project-neon-kdebindings << a bit vague? | 21:21 |
| kshadeslayer | possibly change it to 'ETA' | 21:22 |
| kshadeslayer | or something similar | 21:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!