[01:35]  * SamB wonders if he has reported https://bugs.launchpad.net/launchpad-bazaar/+bug/339380 in the right place
[01:35] <ubottu> Ubuntu bug 339380 in launchpad-bazaar "push doesn't work when default stacking branch is a mirror that has failed to update ?" [Undecided,New]
[01:35]  * SamB wonders a bit about https://bugs.launchpad.net/launchpad-bazaar/+bug/339379 too ...
[01:35] <ubottu> Ubuntu bug 339379 in launchpad-bazaar "lp: urls are not expanded in the --stacked-on option for push" [Undecided,New]
[01:37] <savvas> SamB: try #bzr or #ubuntu-bugs if no-one replies  :)
[01:38] <SamB> why #ubuntu-bugs ? I'm on Debian ;-P
[01:38] <jml> SamB: oh hi
[01:38] <jml> SamB: so, you don't need to specify --stacked-on to do what you are doing.
[01:38] <jml> SamB: but the bugs you've reported are definitely bugs, and are in the right place.
[01:38] <SamB> jml: oh don't I ?
[01:39] <SamB> #339380 is how I ran into #339379, really
[01:39] <jml> SamB: ahh I see.
[01:40] <savvas> SamB: I just recommended alternative ways in case someone didn't reply - which they did :P
[01:41] <jml> SamB: so, is there a canonical bzr branch for dvc?
[01:42] <savvas> shouldn't the links be "lp:~naesten/dvc/styleNdocs" instead of "lp:///~naesten/dvc/styleNdocs" ?
[01:42] <jml> savvas: yeah, but both will work.
[01:43] <jml> SamB: so, stacking on non-trunk branches is basically not supported on Launchpad right now.
[01:44] <jml> SamB: we'd like to fix that -- and we will -- but right now the only way to get it to work is really fiddly.
[01:44] <jml> SamB: 'bzr push --no-stacked' ought to work.
[01:44] <wgrant> jml: Can't one manually specify http://bazaar.launchpad.net/~path/to/branch URLs to stack on?
[01:44] <jml> wgrant: one can. I keep forgetting about that, since I work on a proprietary code base, for which that won't work.
[01:45] <wgrant> Ahhh, true.
[01:45] <jml> SamB: so, what wgrant said is right.
[01:46] <SamB> jml: there is a canonical branch, but for some reason launchpad has trouble mirroring it ...
[01:46] <jml> SamB: it's generating 403s, even in my web browser.
[01:47] <SamB> jml: that's because you are trying to look at it
[01:47] <SamB> it works fine otherwise
[01:47] <SamB> well, except for bzr info
[01:47] <SamB> see https://answers.launchpad.net/launchpad/+question/63191
[01:49] <jml> SamB: I see.
[01:49] <wgrant> Why is it 403ing everything unknown?
[01:49] <jml> SamB: Launchpad inspects the branch before pulling it, because we need to check out some things about the branch before we pull it.
[01:49] <SamB> wgrant: maybe you should ask that in the question ?
[01:50] <SamB> Stefan Reichör is the one that runs that server, not me
[01:50] <wgrant> Ah.
[01:54] <SamB> do you think that question should maybe be converted to a bug, since launchpad could obviously do with being a bit more articulate about the problem ?
[01:54] <jml> SamB: I think there are already bugs about error messages there.
[01:55] <SamB> oh
[01:55] <SamB> right
[01:55] <jml> SamB: also I don't understand stefan's comments in that thread
[01:55] <wgrant> It could also be a bug in bzr.
[01:55] <wgrant> That it doesn't take a 403 as a failure to get that file.
[01:55] <wgrant> But I suppose that's not a good idea.
[01:56] <SamB> well, I mean, launchpad could at least say that something like "bzr info" is failing, or give the URL ... just a thought
[01:56] <jml> SamB: it's not doing bzr info, it's doing something much more complex
[01:57] <SamB> yeah
[01:57] <SamB> thought maybe
[01:57] <jml> SamB: we are very defensive in the way we pull arbitrary data from user-supplied branches
[01:57] <SamB> sensible
[01:57] <SamB> users are always changing things
[01:58] <jml> or being deliberately malicious.
[01:58] <jml> although we haven't come across that yet, at least not in the form of a security attack :)
[01:59] <SamB> well, assuming malice is a decent approximation for all the things users can do by accident anyway
[02:05]  * SamB wonders if he should report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517770 on launchpad, Debian isn't responding and he has no reason to believe this is a Debian problem ...
[02:05] <ubottu> Debian bug 517770 in bzr "bzr: BZR_PROGRESS_BAR is ignored" [Normal,Open]
[02:13] <james_w> SamB: it should go to launchpad really, apologies for not having done it already
[02:14]  * james_w does it now
[02:15] <james_w> bug 339385
[02:15] <ubottu> Launchpad bug 339385 in bzr "bzr: BZR_PROGRESS_BAR is ignored" [Undecided,New] https://launchpad.net/bugs/339385
[03:50] <MTecknology> Ursula-logbot: *tap*tap*
=== sale_ is now known as sale
[14:48] <terrex> ppa builders for amd64 & i386  seems to be hang
[15:13] <terrex> ok, now ppa builders are working.
[16:13] <G__81> i am new to Ubuntu and am trying hard to become an Ubuntero but i am getting problems
[16:13] <G__81> i ve sent the keys to the keyserver and i ve got an email from LP asking me to confirm the key
[16:14] <G__81> and it asks me to do gpg --clearsign filename
[16:14] <G__81> but when i do
[16:14] <G__81> touch new
[16:14] <G__81> gpg --clearsign key
[16:14] <G__81> it asks me to enter passphrase and after i enter it i get back to the prompt and nothing is written onto the "key"
[16:35] <G__81> can someone help me ?
[16:35] <G__81> what exactly should i paste in the LP confirmation mail
[16:45] <SamB> G__81: try pressing ^D
[16:45] <SamB> oh, wait, you get back to the prompt ?
[16:52] <G__81> SamB, ok now finally i ve made it to accept
[16:53] <G__81> SamB, i ve got an email from LP saying that my code of conduct has been acknowledged
[16:53] <G__81> but my Ubuntero status is still No
[16:53] <G__81> :o
[16:54] <G__81> yes got it :)
[16:55] <G__81> finally
[17:02] <G__81> thanks SamB
[17:04] <nhandler> Could someone here try and reproduce a bug with the PPAs for me?
[17:12] <hyperair> nhandler: what bug is this?
[17:14] <nhandler> hyperair: Upload a package to your ppa. Do a search for that package in the web interface. Watch the Build Status column as it goes from needs building to building to complete. For me, once it starts building, I end up with several arch names right next to each other (no space between them). However, if I refresh the page, a space is added
[17:15] <hyperair> hmmm need to find a package to upload
[17:16] <nhandler> If I had to guess, this probably is some ajax bug
[17:16] <hyperair> probably
[18:09] <fidji> hi
[18:09] <fidji> somebody can help me in french ?
[18:09] <fidji> I have some questions about tag revision and ppa
[18:17] <mib_y16t8vj1> what's up with staging.launchpad.net? It just doesnt work here
[18:26] <fidji> I'm on #ubuntu-fr-scripts channel
[18:30] <mib_y16t8vj1> doesnt anyone know why staging doesnt work?!
[18:42] <bcurtiswx> Hi all, im a bug traiger for ubuntu.  I'm wondering how possible it would be to gather OS version and package version (depending on a package is provided in the bug report) to bug reports on submit.  this i guess would regard the manual submissions, as apport on ubuntu will report this automatically.
[18:58] <jpds> bcurtiswx: apt-cache policy <package> - shall give you the package version, while uname -a <- OS version.
[18:59] <bcurtiswx> jpds: yes i do know this.  what i mean, is can launchpad be built to do this on submit of bug reports... so this way triagers arent wasting time asking for this information
[19:00] <jpds> Yeah, you'll have to ask them for manual submissions.
[19:00] <bcurtiswx> jpds: right now its just a couple of asterisks on the bottom of the submit form.. and people who are just filling in the fields will typically ignore that..
[19:01] <bcurtiswx> jpds: since this is important information in bug reports, i imagine having launchpad obtain this information automatically on submit would be extremely beneficial
[19:04] <jpds> bcurtiswx: Can't see any way of doing that really.
[19:06] <bcurtiswx> jpds: ok.. the only other idea I had for this.. would be to insert an input field to the bug reports to have the user input OS version and/or package versions
[19:07] <bcurtiswx> jpds: bug managers like bugzilla gnome have a section devoted to finding version information out
[19:08] <jpds> bcurtiswx: You might want to file a bug against launchpad-bugs about that.
[19:09] <bcurtiswx> jpds: ok, i wasn't sure if a bug report was more efficient way to get this addressed.
[19:09] <LarstiQ> bcurtiswx: for Debian, the canonical method of using 'reportbug' takes care of that
[19:11] <bcurtiswx> LarstiQ: is there an example i can look at (sorry if this is a dumb question)
[19:13] <jpds> bcurtiswx: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512694
[19:13] <ubottu> Debian bug 512694 in pidgin-facebookchat "pidgin-facebookchat: package should depend on the pidgin package" [Normal,Open]
[19:14] <bcurtiswx> jpds: is there a way to push that for launchpad bug reports?
[19:17] <LarstiQ> bcurtiswx: you'll have to have a culture of people using reportbug
[19:18] <bcurtiswx> hmm
[19:19] <bcurtiswx> LarstiQ, how similar or dissimilar are apport/reportbug (could they be combined?)
[19:19] <LarstiQ> bcurtiswx: no clue
[19:19] <LarstiQ> bcurtiswx: but reportbug is a Debian tool
[19:20] <jpds> bcurtiswx: Actually, I think https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-February/000535.html - may just be what you want.
[19:21] <bcurtiswx> ah yes, package hooks.. i know about those.. but as of right now they need hooks made for tons of other important packages
[19:24] <bcurtiswx> jpds: this is a good way to grab that info.. but its more after the fact... im going for gathering this information on the initial report
[19:25] <jpds> bcurtiswx: You're going to have to hope that the user does as requested then :(
[19:27] <bcurtiswx> https://bugs.launchpad.net/ubuntu/+source/splix/+bug/338442
[19:27] <ubottu> Ubuntu bug 338442 in system-config-printer "bug reports would benefit from an apport hook" [Undecided,In progress]
[19:28] <LarstiQ> bcurtiswx: there are different ways people can report bugs
[19:29] <LarstiQ> bcurtiswx: also, what works for Ubuntu won't for other upstream projects
[19:29] <LarstiQ> bcurtiswx: so imo you should have your own bug reporting workflow documented anyway
[19:33] <bcurtiswx> LarstiQ:  https://bugs.launchpad.net/ubuntu/+filebug isnt a stellar start to a bug report... and the typical bug reporter wont go to advanced options.  Should I file a bug against changing that process around?
[19:38] <LarstiQ> bcurtiswx: I guess allowing projects to customize the bug reporting a bit might be a good idea
[19:38] <LarstiQ> bcurtiswx: though I suspect there would already be requests for that
[19:40] <bcurtiswx> LarstiQ, I love that first option.  i think that would be a great thing.  In ubuntu, triagers are always asking reporters for package and OS versions... so allowing us to collect that in bug reports that we can customize would be awesome
[19:54] <bcurtiswx> LarstiQ: how would I go about getting this in the works?
[19:56] <LarstiQ> bcurtiswx: look through the answers/bugs filed on launchpad for something similar?
[20:05] <thumper> morning
=== oojah_ is now known as oojah
[21:35] <technopagan> I'm stuck: I want to upload code to LP/Bazaar. I've tried bzr push lp:MYPROJECTPATH --use-existing-dir while being on my local code-folder, but Bazaar replies that it's "Not a branch". How do I upload code fo the first time?
[21:36] <lifeless> technopagan: bzr push lp:~USERNAME/PROJECT/BRANCHNAME
[21:38] <fidji> hi
[21:38] <fidji> somebody know how I can resole this problem http://paste.ubuntu-fr-secours.org/src-11304
[21:39] <technopagan> lifeless: I did that. I get "Not a branch" as an error.
[21:39] <fidji> resolve*
[21:41] <lifeless> technopagan: could you please pastebin the exact command and response you get please
[21:42] <technopagan> lifeless: http://pastebin.com/d2a8d9caf
[21:44] <technopagan> lifeless: I created a new project, now I want to give it some code so that team-members can start commiting. This should not be that difficult. What am I doing wrong?
[21:44] <fidji> I need to get the Makefile for my branch in ubuntu-fr-scripts
[21:44] <lifeless> technopagan: ok, this - bzr: ERROR: Not a branch: "/home/baldur/bin/woof/branch/". - says that the local directory you are in is not a branch
[21:45] <lifeless> technopagan: is this an existing project or a new project?
[21:46] <technopagan> lifeless: A new project.
[21:48] <fidji> technopagan: cd myproject && bzr init && bzr add && bzr commit -m "any comment" && bzr push lp:~USERNAME/PROJECT/BRANCHNAME
[21:52] <technopagan> fidji: Thank you!!
[21:53] <fidji> nobody for my problem ?
[21:54] <fidji> http://paste.ubuntu-fr-secours.org/src-11304
[21:55]  * thumper looks at fidji's problem
[21:56] <fidji> thank's thumper
[21:57] <thumper> fidji: not sure I'm afraid, I can suggest bigjools or noodles when they come on line though
[21:57] <fidji> dscverify: loggedfs_0.5-0ubuntu1.dsc failed signature check:
[21:57] <thumper> technopagan: once the branch is up for your project, you can link it as the primary branch for your project
[22:03] <technopagan> thumper: I've created a branch, but Launchpad says "A development focus branch hasn't been specified". Is this the same thing? Should I mark my branch the "development focus branch" ?
[22:05] <mwhudson> technopagan: yes
[22:07] <technopagan> mwhudson: Done. Thank you!
[22:07]  * SamB whispers http://bugs.darcs.net/issue833
[22:08] <mwhudson> SamB: in the wrong channel perhaps?
[22:08] <SamB> no, I was just wondering what that bot would say about it is all
[22:08] <thumper> technopagan: yes
[22:08] <thumper> mwhudson: ah, thanks
[22:08] <thumper> SamB: not much I hope