[00:08] <spiv> Another victim of https://bugs.edge.launchpad.net/launchpad-foundations/+bug/287154 :(
[00:10] <Andre_Gondim> does any one can help me? I can't see any suggest here https://translations.edge.launchpad.net/ubuntu/jaunty/+source/apt/+pots/apt-all/pt_BR/173/+translate you too?
[00:12] <savvas> Andre_Gondim: no, not all translations have suggestions
[00:12] <Andre_Gondim> savvas, I have someone who told there is a suggest there =/
[00:14] <savvas> Andre_Gondim: true, you're using edge, in normal there is a suggestion
[00:14] <MTecknology> spiv: that doesn't make any sense. It's a weird looking button that sits right next to the edit it's referring to. It's Yellow which is the best color you could use for edit. If you hover, it says Edit this [thing]. On pages like the bugs, it has the word "Update" right next to it.
[00:14] <savvas> Andre_Gondim: disable edge redirection on this site: https://launchpad.net/
[00:15] <savvas> Andre_Gondim: and visit: https://translations.launchpad.net/ubuntu/jaunty/+source/apt/+pots/apt-all/pt_BR/173/+translate
[00:16] <spiv> MTecknology: the icon is supposed to depict a pencil, so that it self-evidently means "edit"
[00:16] <Andre_Gondim> savvas, thanks
[00:17] <MTecknology> spiv: it doesn't make sense how that represents a pencil, but it's use just seems obvious...
[00:17] <spiv> MTecknology: but here we had a user that figured out, somehow, that the icon meant edit (on that page at least), but calls it the "! icon"
[00:17] <MTecknology> lol
[00:18] <spiv> i.e., that bug struck again
[00:18] <spiv> MTecknology: I'm glad its use seems obvious to you.  Can we transplant your brain to all of our users, please? :)
[00:19] <MTecknology> :P
[00:19] <MTecknology> spiv: I am confused....
[00:19] <MTecknology> /@@/edit
[00:20] <MTecknology> what does that link to?
[00:22] <spiv> MTecknology: I'm not sure I understand your question.  /@@/edit is the location of the edit icon on the launchpad site...
[00:24] <MTecknology> what is @@
[00:24] <MTecknology> I've never seen that before
[00:26] <spiv> It's part of a URL ;)
[00:26] <spiv> It's a convention from Zope 3, IIRC.
[00:26] <spiv> @@ sort of looks like a pair of eyes, so it is used for "view"-related things.
[00:27] <MTecknology> oh
[00:27] <MTecknology> that's the actual directory name then?
[00:28] <MTecknology> interesting
[00:28] <spiv> Um, no...
[00:28] <MTecknology> https://launchpad.net/@@/edit
[00:28] <spiv> What makes you think URLs have anything to do with directories on a filesystem :)
[00:29] <MTecknology> lol - I'll just let it go - I'm not touching that source code when it's released - too much knowledge poured into this thing :P
[00:32] <MTecknology> spiv: I hope that comment is useful
[00:33] <MTecknology> that in place editing of titles is really really neat
[00:34] <spiv> Yeah, it is.  Except that it turns out the green tick on the grey circle is invisible to people red-green colour blindness...
[00:35] <spiv> (I guess the moral of the story is that icon design is hard...)
[00:35] <MTecknology> ...
[00:35] <MTecknology> weird
[00:35] <MTecknology> lighter grays?
[00:41] <cyberix> jml: the people in the group design the software and write the code
[00:41] <cyberix> jml: so for Launchpad this is an out-of-band relation
[00:42] <cyberix> jml: we created the group so people could find each other
[00:42] <jml> cyberix: well, those people could conceivably own the trunk branch, or something?
[00:42] <jml> cyberix: you could also just put the URL of the team in the project description.
[01:41] <seiflotfy> Added new clutter pre-prototype UI To start it up instead of running sh zeitgeist.sh do sh zeitgeist2.sh
[01:41] <seiflotfy> ooops
[01:41] <seiflotfy> sorry
[01:41] <seiflotfy> i have a problem
[01:42] <seiflotfy> seif@Schroeder:~/Projects/gnome-doc-centric-playground$ bzr push
[01:42] <seiflotfy> Using saved location: http://bazaar.launchpad.net/~gnome-doc-centric-playground/gnome-doc-centric-playground/gnome-journal-prototype/
[01:42] <seiflotfy> bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/%7Egnome-doc-centric-playground/gnome-doc-centric-playground/gnome-journal-prototype/.bzr/branch/lock): Transport operation not possible: http does not support mkdir()
[01:42] <seiflotfy> what to do
[01:42] <seiflotfy> i just pushed things up a couple of ddays ago
[01:56] <mwhudson> seiflotfy: bzr launchpad-login
[01:57] <mwhudson> seiflotfy: also, you must be using a fairly old bzr to not get a more helpful message
[01:58] <mwhudson> :(
[01:59] <jml> where is the love?
[02:10] <spm> jml: "make love"
[02:10] <spm> ... sadly. modern make's no longer respond "not war"
[02:14] <lifeless> spm: you could put that in the default ruleset
[02:19] <NCommander> cprov, http://launchpadlibrarian.net/22839233/buildlog_ubuntu-jaunty-hppa.kdebindings_4%3A4.2.0-0ubuntu2~ppa1_NEEDSBUILD.txt.gz - I broke LP :-)
[08:43] <wgrant> mpt: What caused you to growl at my bug?
[14:06] <loic-m> If I upload a new version of a library to my ppa, how do I make sure other packages uploaded to my ppa build with this version instead of the one in ubuntu's repos?
[14:06] <soren> loic-m: That happens automatically.
[14:06] <soren> ...as long as the version of you library package is higher than the one in the Ubuntu archive.
[14:07] <loic-m> soren: thanks a lot
[14:08] <loic-m> Can I import Jaunty source packages in my ppa for rebuilding directly in launchpad, or do I have to apt-get source then dput them?
[14:24] <geser> loic-m: uploading a new .diff.gz should be enough (IIRC), the PPA buildd will pull the .orig.tar.gz from the primary archive
[14:25] <loic-m> geser: that still means I need to update the changelog and create a new version of the packages I want to test rebuild though, doesn't it?
[14:26] <bigjools> no, you can upload the same version
[14:26] <geser> PPA doesn't complain about the version being also in the primary archive?
[14:26] <bigjools> of course not, it's a separate archive
[14:27] <geser> does one need then a full source upload?
[14:27] <bigjools> well as you already said, you can leave out the .orig.tar.gz
[14:28] <geser> so only the version space is separa
[14:28] <geser> separate?
[14:29] <loic-m> bigjools: tried with dput ppa foo.diff.gz and dput wants a source.changes
[14:29] <soren> Can you guys see the IP's my account has been used from within the last week or so? I have a hunch that I'd like to get confirmed/rejected.
[14:29] <bigjools> you can reference the .orig in the dsc and LP will find it based on the md5
[14:29] <bigjools> loic-m: yes you need to make a changes file
[14:30] <geser> loic-m: fetch source, extract it, cd <pkg>, run dpkg-genchanges -S
[14:30] <loic-m> bigjools: it's becoming slightly OT, sorry, but to generate a changes file don't I need to update the changelog?
[14:31] <loic-m> geser, bigjools: thanks
[14:31] <bigjools> what he said. :)
[14:40] <loic-m> dpkg-genchanges -S doesn't ask me for my key password, and dput complains there's no valid signature.
[14:42] <geser> loic-m: run debsign <pkg>.changes afterwards
[14:43] <geser> don't forget to redirect the output from dpkg-genchanges to a file
[14:43] <loic-m> geser: thanks. The later was easy to find, but the former wasn't ;)
[14:47] <loic-m> it worked!
[15:00] <savvas> Is there a time limitation in PPAs? I mean is there a limit for how much time a package takes to compile?
[15:01] <Ursinha> cprov, ^
[15:02] <cprov> savvas: no, there isn't such thing.
[15:02] <cprov> savvas: why do you ask ?
[15:02] <savvas> cprov: https://edge.launchpad.net/~medigeek/+archive/ppa/+build/875553
[15:02] <savvas> it took a while to build boost1.35 to try out a fix, but it failed
[15:03] <savvas> the only changes I introduced was adding 'Provides:' in debian/control for several binary packages
[15:03] <cprov> savvas: let me check the buildlog, one sec
[15:04] <savvas> cprov: ok, in the meantime I'm compiling it locally to see if there's a difference
[15:05] <cprov> savvas: great.
[15:19] <cprov> savvas: i don't know what happens to cause dpkg to die
[15:20] <cprov> savvas: it could an abnormal memory consumption due to the compiling errors (just guessing)
[15:22] <savvas> cprov: should I retry one of the failed ones in launchpad?
[15:23] <cprov> savvas: yes, try it one more time, if the problem persist raise it on #motu
[15:24] <savvas> cprov: ok, will do!
[15:26] <cprov> savvas: thanks for bringing this problem up. Let see if it can be debugged and fixed accordingly soon.
[15:30] <savvas> sure, no problem
[15:33] <savvas> cprov: locally it was built successfully, I'm retrying i386 and amd64 builds on launchpad
[16:46] <MagicFab> Hi all
[16:46] <MagicFab> is it possible to change one's LP ID ?
[16:47] <andrea-bs> MagicFab: you can change your own ID here: https://launchpad.net/people/+me/+edit
[16:49] <MagicFab> andrea-bs, excellent, thanks!
[17:31] <Tumie> how do i delete a team on launchpad ?
[17:32] <andrea-bs> Tumie: you have to ask a question to the LP admins: https://answers.launchpad.net/launchpad
[17:34] <Tumie> ok, done
[17:35] <andrea-bs> now, just wait :)
[17:36] <Tumie> :)
[17:36] <Tumie> ty :)
[17:36] <loic-m> Is it possible to rebuild some packages in my ppa even though they already built fine?
[17:37] <loic-m> (to test rebuilding with a new version of the lib they build depend on)
[17:37] <bigjools> loic-m: no, same rules as Ubuntu apply, you need to bump up the version and re-upload
[17:38] <loic-m> thanks. painpainpainpainpain
[17:38] <bigjools> :(
[17:38] <loic-m> Can't I just delete them, then reupload after a while?
[17:39] <bigjools> no, it remembers what you already uploaded
[17:39] <loic-m> I don't want to bump the version, they're packages straight from ubuntu repos
[17:39] <loic-m> too bad
[17:39] <bigjools> just make a ~ppa1 version
[17:40] <bigjools> um, +ppa1 in this case
[17:40] <loic-m> I'll try
[17:41] <MagicFab> after changing one's LP ID, the CoC signature is not linked anymore
[17:41]  * MagicFab check for existing bugs
[17:44] <MagicFab> is there any obvious way to fix this ?
[17:45] <joey> MagicFab, really? Hmm I just changed mine.  Let me look!
[17:46] <joey> so MagicFab, explain that a bit to me. Mine appear ok.
[17:48] <joey> the only gotcha I had when changing my LP id is that I also had to change my bzr settings
[17:48] <joey> in bazaar.conf, authentication.conf, and locations.conf
[17:50] <MagicFab> joey, https://bugs.edge.launchpad.net/launchpad/+bug/331678
[17:51] <joey> MagicFab, odd, it works for me
[17:51] <joey> MagicFab, it's linked to https://edge.launchpad.net/~tatica1/+codesofconduct
[17:52] <joey> MagicFab, maybe I'm bitten by my admin privs though.
[17:57] <MagicFab> joey,  I uploaded a screenshot
[18:01] <ondrej> Hi, the help page for PPA: https://help.launchpad.net/Packaging/PPA#Using packages from other distributions, says that I can upload packages for other distributions unmodified
[18:01] <joey> MagicFab, ok, I get it now. :-)
[18:01] <ondrej> but I keep getting: Rejected:
[18:01] <ondrej> Could not find suite 'unstable'
[18:01] <ondrej> when I upload a package for Debian sid.
[18:01] <joey> cprov, bigjools - still around? ^^
[18:02] <bigjools> I'm just finishing
[18:02] <ondrej> so how can I do it? Or should the help page be improved?
[18:02] <bigjools> ondrej: you need to change to a valid Ubuntu series
[18:02] <bigjools> yeah, it could be better
[18:02] <cprov> ondrej: what's in your dput.cf ?
[18:02] <ondrej> my .dput.cf is:
[18:03] <ondrej> [ppa]
[18:03] <ondrej> fqdn = ppa.launchpad.net
[18:03] <ondrej> method = ftp
[18:03] <ondrej> #incoming = ~ondrej-certik/ppa/ubuntu
[18:03] <ondrej> incoming = ~ondrej-certik/ppa/ubuntu/unstable
[18:03] <ondrej> login = anonymous
[18:03] <ondrej> allow_unsigned_uploads = 0
[18:03] <cprov> ondrej: ERRRRR!
[18:03] <ondrej> (I tried both incoming lines and neither works)
[18:03] <cprov> :)
[18:03] <bigjools> heh
[18:03] <cprov> incoming = .../hardy  or intrepid or jaunty
[18:03] <ondrej> cprov, but I want to upload packages for Debian unstable
[18:03] <ondrej> the help page says it should work
[18:04] <maxb> ondrej: *from* unstable *for* jaunty (etc.)
[18:04] <ondrej> ah
[18:04] <cprov> ondrej: we don't support debian native building,  we support uploading pristine debian packages to ubuntu series
[18:04] <ondrej> ah, I got it now
[18:04] <ondrej> let me try it
[18:05] <cprov> ondrej: that's what a flaky help text causes, confusion.
[18:05] <cprov> ondrej: do you have any *specific* suggestion to make that clearer on the current text ?
[18:05] <ondrej> yes
[18:05] <ondrej> say that the incoming line must be ppa/ubuntu/<some *ubuntu* distrib>
[18:05] <cprov> ondrej: fire it :)
[18:06] <ondrej> but you can upload packages from Debian and other deb distros unmodified, as long as you upload it to some ubuntu distro.
[18:08] <ondrej> cprov, is there any reason (besides manpower) that ubuntu doesn't support Debian sid?
[18:08] <ondrej> I created:
[18:08] <ondrej> https://blueprints.edge.launchpad.net/lp-dev-utils/+spec/ppa-debian-unstable
[18:08]  * MagicFab -> lunch
[18:09] <cprov> ondrej: lp-dev-utils ? funny
[18:10] <ondrej> cprov, I didn't find PPA
[18:10] <cprov> ondrej: anyway, yes, the main factor is manpower
[18:10] <ondrej> cprov, ok -- can I help with this somehow?
[18:10] <cprov> ondrej: unfortunately it has to happen within the company
[18:11] <ondrej> cprov, I asked about this Steve Langasek and Christian Reis at the ubuntu developer summit in Prague
[18:11] <cprov> ondrej: unrelated, but why have you created a spec in a random project instead of filing a bug on soyuz (they is already one for debian-ppas, IIRC)
[18:12] <cprov> ondrej: you could have talked to me, I was there too :)
[18:12] <ondrej> cprov, and they said it would probably happen, that they only need to build the schroot, so I offered them help with this and Christian said to send him an email, so I did and he never replied
[18:12] <ondrej> cprov, ah great, I didn't know
[18:13] <cprov> ondrej: https://help.launchpad.net/Packaging/PPA (edited)
[18:13] <ondrej> cprov, as to the spec, feel free to delete it and provide there a link to the bug about this
[18:13] <cprov> ondrej: https://bugs.edge.launchpad.net/soyuz/+bug/188564
[18:13] <ondrej> cprov, I am a bit confused as to where to fill what in the launchpad. thanks for the link
[18:15] <cprov> ondrej: there are other aspects of debian-ppas mentioned there, I'm looking forward to see what you have in mind.
[18:15] <ondrej> cprov, what do you mean by other aspects?
[18:15] <ondrej> I don't see any
[18:16] <cprov> ondrej: err, not there yet, I will post a comment latter today, subscribe to it.
[18:16] <ondrej> cprov, thanks for updating the help page, now it's clearer
[18:17] <ondrej> cprov, --- will you post it to the bug?
[18:17] <cprov> ondrej: yes
[18:17] <ondrej> cprov, registered and posted a support comment. :)
[18:18] <cprov> ondrej: cool, thanks
[18:18] <ondrej> cprov, thanks for the help. I hope this happens eventually
[18:19] <cprov> ondrej: it will
[18:19] <ondrej> cprov, btw here are my notes from UDS http://ondrejcertik.blogspot.com/2008/05/ubuntu-developer-summit-in-prague.html
[18:19] <ondrej> I must have missed you
[18:19] <cprov> ondrej: aha, I see a lot of people eating :)
[18:21] <ondrej> :)
[18:21] <ondrej> yeah!
[18:21] <ondrej> you probably recognize most of them
[18:22] <cprov> yup
[18:28] <ondrej> cprov, so I just verified sid->jaunty works without a modification. looking forward for sid->sid. need to go, see you later
[19:10] <joey> bigjools, cprov - thanks.
[19:11] <cprov> joey: you're welcome
[19:13] <joey> swapped out the unpostable list for the team with the mailing list
[20:23] <savvas> cprov: the retry failed again: https://launchpad.net/~medigeek/+archive/ppa/+build/875552/+files/buildlog_ubuntu-jaunty-amd64.boost1.35_1.35.0-8ubuntu4_FAILEDTOBUILD.txt.gz
[20:35] <charlie-tca> bac: I got another one, need to set the project for it if you want to see it
[20:36] <bac> charlie-tca: sure
[20:36] <charlie-tca> https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/331751
[20:36] <charlie-tca> needs to have the upstream bug set
[20:37] <bac> charlie-tca: ok, do it and if you get assigned the project i'll replicate your steps on staging
[20:37] <charlie-tca> Do I need to list the steps here?
[20:38] <bac> charlie-tca:  not yet.  let's see if you get re-assigned first
[21:01] <oliver_g_> hi
[21:02] <oliver_g_> I want to make a fork of a bzr branch hosted at launchpad
[21:02] <oliver_g_> (https://code.launchpad.net/~delfick/+junk/projectMarker to be exact)
[21:02] <oliver_g_> I already have a launchpad account
[21:02] <oliver_g_> so what is the quickest way to make such a fork? For publishing some bugfixes?
[21:07] <mwhudson> oliver_g_: bzr pull lp:///~delfick/+junk/projectMarker; hack hack hack; bzr push lp:///~<you>/project/branchname
[21:10] <oliver_g_> so out of curiosity, what's the +junk part in the original bzr url then?
[21:10] <oliver_g_> do I have to include it in my own url as well?
[21:37] <maxb> +junk is launchpad's convention for indicating a branch not associated with a launchpad project
[21:38] <maxb> launchpad requires that there be a project component in branch URLs
[21:38] <maxb> It provides the option of +junk for ad-hoc branches for which you do not wish to register a project
[21:47] <cprov> savvas: right, we need support from the fantatisc-motu guys
[21:47] <mwhudson> oliver_g_: you need to put +junk or the name of a project in there
[21:48] <oliver_g_> yes, I noticed that makes it work :-)
[21:49] <oliver_g_> btw. does the original author of the project get a notification about my branch?
[21:54] <geser> cprov: if it's about the boost FTBFS, then it was sort of resolved in the meantime. It's because of the recent python changes in jaunty.
[21:54] <cprov> geser: yes, it's about boost. Very nice, you guys rock !
[22:02] <savvas> cprov, geser: thanks for the time you dedicated for this, I'm trying out a new patched (rookie-style :) ) build
[22:03] <savvas> https://edge.launchpad.net/%7Emedigeek/+archive/ppa/+files/boost1.35_1.35.0-8ubuntu4_1.35.0-8ubuntu4~ppajaunty1.diff.gz