[00:41] <ubotu> New bug: #209570 in bzr "http cannot tunnel smart protocol (dup-of: 207558)" [Critical,New] https://launchpad.net/bugs/209570
[00:58] <sachetto> join #ubuntu-br-tradutores
[00:58] <sachetto> oops
=== emgent is now known as bakunin
=== bakunin is now known as emgent
[02:21] <slangasek> hi, it seems I'm not able to mark bugs (or at least, one particular bug) as 'fix released' in launchpad: bug #217254, OOPS-837A174 ?
[02:21] <ubotu> Launchpad bug 217254 in open-vm-tools "open-vm-tools is an alpha quality release" [Critical,New] https://launchpad.net/bugs/217254
[02:21] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/837A174
[02:22] <slangasek> ...ah, because in the time between I loaded the page and submitted the form, it was marked as targetted to a release
[03:14] <poolie> mpt, thanks very much for your review of the branch page
=== rockstar` is now known as rockstar_
[04:06] <Kamping_Kaiser> other then commit to a branch, is there something i need to do to subsribe to it?
[04:08] <mwhudson> yes, there's a 'subscribe' item in the actions portlet
[04:10] <Kamping_Kaiser> thanks, i'll try and find it
[04:10] <Kamping_Kaiser> got it, cheers :)
[04:12] <mwhudson> :)
=== asac_ is now known as asac
[07:18] <Kamping_Kaiser> what time does launchpad generate the karma stats ? i thought it was midnight utc, but its happened in the last 30 minutes
[08:09] <carlos> morning
[08:40] <ubotu> New bug: #218066 in malone/1.2 "Associate e-mail replies to imported comments with the bug watch" [Undecided,Confirmed] https://launchpad.net/bugs/218066
=== doko_ is now known as doko
[08:46] <mdke> bzr commits seem to be really slow still - I'm pushing a very small change, and it has been over 5 minutes, I think
[08:46] <mdke> FTR i'm pushing to bzr+ssh://mdke@bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-doc/xubuntu-hardy/, if it helps anyone diagnose
[08:48] <jamesh> mdke: any difference in the branch types?
[08:48] <jamesh> and what version of bzr?
[08:50] <mdke> jamesh: 1.3 from my end. branch format is dirstate-with-subtree - i'm aware that this is a slow format, but it has always been quite nippy in the past. But recently it has been very slow
[08:51] <mdke> jamesh: actually, on checking = 1.4rc
[08:51] <jamesh> mdke: okay.  There is some speed regressions with knit-to-pack pushes with 1.4rc1
[08:51] <jamesh> mdke: that's why I was suggesting you check the branch formats at both the local and remote ends
[08:52] <mdke> jamesh: ah, that's the problem. it's a pack-to-knit push
[08:52] <mdke> I forgot I had upgraded on my end
[08:53] <mdke> jamesh: thanks
[08:53] <jamesh> mdke: so there are two things you can try: (1) downgrade to bzr-1.3.1 or (2) upgrade the remote end
[08:54] <mdke> jamesh: I'm planning on doing (2) after we have got the release out the way, so shortly
[08:54] <jamesh> for (2), I'd suggest using lftp to do a recursive delete of the .bzr directory via SFTP and then push your pack version
[08:54] <jamesh> upgrade over the net is slow
[08:54] <mdke> jamesh: lifeless advised me to do it from a datacentre computer, I can do it from doc.ubuntu.com
[08:54] <mdke> is that relatively reliable, if I use upgrade?
[08:55] <jamesh> mdke: I've done the delete-then-push method for a few of my branches
[08:55] <jamesh> mdke: an upgrade over the net effectively requires bzr to download everything off the remote end and then write back the new version
[08:56] <mdke> jamesh: ok. I might have to ask you to walk me through that when the time comes, if you don't mind
[08:56] <jamesh> mdke: doing an upgrade over the net from the datacentre is better because the latency won't hit you as hard
[08:56] <mdke> ah
[08:57] <jamesh> but if you've already got the branch data locally, delete-then-push is likely to be faster
[08:57] <jamesh> and less traffic
[08:57] <mpt> Goooooooooooooooood morning Launchpadders!
[08:57] <mdke> jamesh: I see, thanks. I have to run now, I'm late for work
[08:58] <mdke> as usual :(
[08:58] <mdke> morning mpt
[08:58] <Kamping_Kaiser> mpt, morning
[09:06] <ubotu> New bug: #218080 in malone "no information about the date when a attachment was added in /+text view" [Undecided,New] https://launchpad.net/bugs/218080
[09:11] <ubotu> New bug: #218084 in soyuz "on bug page, show if PPA upload fixes the bug" [Undecided,New] https://launchpad.net/bugs/218084
[09:15] <cprov> that's a good idea.
[11:15] <rzr> hi
[11:15] <rzr> probally issue w/ ntp server
[11:15] <rzr> 16 Apr 10:09:00 ntpdate[999]: no server suitable for synchronization found
[11:15] <rzr> http://launchpadlibrarian.net/13503014/buildlog_ubuntu-hardy-i386.tuxguitar-snapshot_0.0.20080401-0ubuntu0%7Eppa84_CHROOTWAIT.txt.gz
[11:16] <elmo> rzr: what PPA is that from?
[11:16] <rzr> mine
[11:16] <rzr> https://launchpad.net/~rzr/+archive/+builds?build_text=&build_state=all
=== rzr is now known as rZr
[11:23] <elmo> rZr: do you know which buildd that happened on?
[11:24] <Fujitsu> ppa84. Wow.
=== mrevell is now known as mrevell-lunch
[12:14] <infinito> hello
[12:14] <infinito> has anyone here experience with PPA? i have some doubts...
[12:14] <artfwo> yes, I've been actively using it recently
[12:14] <Fujitsu> !ask
[12:14] <ubotu> Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-)
[12:15] <infinito> i wuold like to know how to upoad packages frmo the same upstream version but for differenet ubuntu versions
[12:16] <Fujitsu> What issues do you have with it?
[12:16] <infinito> Fujitsu: i just don't know how to do it, i mean, just changing the target dist on changelog doesn't work
[12:17] <Fujitsu> Oh. Different Ubuntu *releases*, like Gutsy, Hardy?
[12:17] <infinito> may i add something to version? something like app-0.5-0ubuntu1~ppa1~gutsy or semthing like thtat?
[12:17] <infinito> Fujitsu: yes, different releases
[12:17] <infinito> sorry
[12:17] <Fujitsu> Append ~gutsy1, and change the distribution in the changelog.
[12:17] <artfwo> i guess releases should be specified in the changelog, not?
[12:19] <infinito> Fujitsu: so something like 0.5.0-0ubuntu1~ppa~gutsy1 is correct?
[12:20] <Fujitsu> ~ppa1~gutsy1, perhaps.
[12:21] <infinito> Fujitsu: ummm maybe (0.5.0-0ubuntu1~ppa1~gutsy is better? so next ppa version for gutsy should be (0.5.0-0ubuntu1~ppa2~gutsy
[12:21] <Fujitsu> The standard is ~releaseX.
[12:21] <Fujitsu> As you might need to make another source change for the backport.
[12:21] <infinito> Fujitsu: ok
[12:21] <infinito> one more question
[12:22] <infinito> the dependencies versions are handled automatically?
[12:22] <artfwo> what about using only ~ppaX withouth ~releaseX?
[12:22] <Fujitsu> artfwo: One must change the version.
[12:24] <artfwo> Fujitsu: I meant, is this also considered standard?
[12:24] <Fujitsu> That would be for an upload for the latest release, yes.
[12:24] <artfwo> thanks :)
[12:26] <infinito> Fujitsu: but thinking in the future, is not better to add the ~releaseX for every upload?
[12:26] <Fujitsu> Quite possibly so.
[12:27] <Fujitsu> Particularly at this stage.
[12:27] <infinito> Fujitsu: and what about the deps? should i change the control file for every release?
[12:29] <Fujitsu> Why would you do that?
[12:29] <Fujitsu> Which deps?
=== warp10_ is now known as warp10
[12:29] <artfwo> build-deps
[12:29] <Fujitsu> Why do you need to?
[12:29] <Fujitsu> Why are they so versioned?
[12:29] <infinito> Fujitsu: because build-deps for hardy are not the same versions as gutsy
[12:30] <Fujitsu> Why are you build-depending on such strict versions?
[12:33] <infinito> Fujitsu: i've always thought that it was important to have something like "Build-Depends: debhelper (>= 5.0.38), cdbs (>= 0.4.49)"
[12:34] <infinito> instead of this without versions
[12:40] <Fujitsu> infinito: Only if you use features only in that version.
=== mrevell-lunch is now known as mrevell
[15:00] <fta> is ppa.launchpad.net dead ?
[15:00] <fta> http://paste.ubuntu.com/7198/
[15:01] <fta> from http://launchpadlibrarian.net/13505477/buildlog_ubuntu-hardy-i386.miro_1.5~svn20080415r6733-0ubuntu1~fta1_MANUALDEPWAIT.txt.gz
[15:01] <cprov> fta: it works from here.
[15:01] <fta> same on amd64: http://launchpadlibrarian.net/13505478/buildlog_ubuntu-hardy-amd64.miro_1.5~svn20080415r6733-0ubuntu1~fta1_MANUALDEPWAIT.txt.gz
[15:01] <fta> since yesterday
[15:04] <cprov> fta: have you retried them recently ?
[15:04] <fta> yes
[15:05] <fta> few minutes ago
[15:05] <fta> https://edge.launchpad.net/~fta/+archive/+builds?build_text=&build_state=all
=== danilo__ is now known as danilos
[15:55] <ubotu> New bug: #218224 in launchpad "Making N changes to preferred languages produces N informational alerts" [Undecided,New] https://launchpad.net/bugs/218224
[16:01] <fta> cprov, so, what should I do ? retry once again ?
[16:02] <cprov> fta: I've asked IS, but no answer yet. Keep retrying if you want.
[16:05] <ubotu> New bug: #218228 in malone "Attachment form is distracting on bug-reporting page" [Undecided,New] https://launchpad.net/bugs/218228
[16:11] <cprov> fta: please, retry the build now, it will work.
[16:12] <fta> cprov, ok, done.
=== elmargol_ is now known as elmargol
[16:20] <jcastro> cprov: you interested in PPA talks for ubuntu openweek?
[16:21] <cprov> jcastro: yes, I could do a session.
[16:21] <jcastro> cprov: awesome
[16:26] <Hobbsee> ooh, mroe sessions
[16:39] <cprov> fta: did it work ?
[16:40] <fta> let me check...
[16:40] <fta> cprov, yes! thanks
[16:40] <cprov> fta: great, thanks for pointing it.
[16:43] <fta> cprov, no problem. btw, it would be nice to get an email if it still fails after n automatic retries so users would notice
[16:44] <cprov> fta: you get a email on every failure, no ?
[16:44] <fta> no
[16:44] <fta> just for FTBFS, not for MANUALDEPWAIT
[16:45] <fta> cprov, ^^
[16:46] <cprov> uhm, right.
[16:46] <cprov> fta: could you please file a bug about it ?
[16:46] <fta> yep, which project ?
=== Mez is now known as fishfinder
=== fishfinder is now known as Mez
[17:04] <komputes> Does anyone know how to view all code revisions, not just the last 10?
[17:06]  * soren likes the new /+archive page
=== salgado is now known as salgado-lunch
[17:21] <ubotu> New bug: #218252 in launchpad "Can only view 10 recent revisions of code" [Undecided,New] https://launchpad.net/bugs/218252
[17:24] <fta> cprov, bug 218261
[17:24] <ubotu> Launchpad bug 218261 in soyuz "uploaders should get emails/notifications for packages in depwait mode" [Undecided,New] https://launchpad.net/bugs/218261
[17:24] <cprov> fta: thanks
[17:31] <ubotu> New bug: #218261 in soyuz "uploaders should get emails/notifications for packages in depwait mode" [Undecided,New] https://launchpad.net/bugs/218261
=== matsubara is now known as matsubara-lunch
[17:59] <rZr> elmo: i am back it's seems to be fixed isnt it ?
=== rZr is now known as RzR
[18:00] <elmo> RzR: err, sure, it was only ever a transient failure
[18:00] <elmo> RzR: if you're still seeing it, I need to know on which buildd
[18:00] <elmo> but it really shouldn't happen anymore
[18:00] <RzR> ok
[18:00] <ubotu> New bug: #218273 in launchpad-buildd "Can't write average time/space when build is done" [Undecided,New] https://launchpad.net/bugs/218273
[18:01] <ubotu> New bug: #218271 in blueprint "Dependencies between more than one project" [Undecided,New] https://launchpad.net/bugs/218271
[18:02] <ubotu> New bug: #218272 in blueprint "Allow blueprints to be registered on more than one project" [Undecided,New] https://launchpad.net/bugs/218272
[18:26] <ubotu> New bug: #218285 in launchpad "Long team memberships cause the mugshot page to take forever or cause browsers to lock up" [Undecided,New] https://launchpad.net/bugs/218285
[18:37] <nand> hi!
[18:38] <nand> Anyone also having a "This team's mailing list will be available within a few minutes." since a week? 
[18:38]  * nand wonders if this was related to bug 215118
[18:38] <ubotu> Launchpad bug 215118 in launchpad "Odd mailing list resync behavior" [High,Fix released] https://launchpad.net/bugs/215118 - Assigned to Barry Warsaw (barry)
=== salgado-lunch is now known as salgado
[18:42] <barry> nand: it's related, but really bug 198368 is blocking this right now
[18:42] <ubotu> Bug 198368 on http://launchpad.net/bugs/198368 is private
[18:43] <nand> barry: ok thanks for the info! No need to fill a bug then I guess
[18:43] <barry> nand: the fix for that has been committed and we're just waiting for approval to roll it out.  i expect to happen today or tomorrow
[18:43] <barry> nand: nope.  once that bug fix is released, all pending mailing lists should magically appear :)
[18:44] <nand> barry: Ok thanks :) I'll keep you in touch
[18:44] <barry> nand: thanks!
=== matsubara-lunch is now known as matsubara
[19:08] <ubotu> New bug: #28682 in malone "Filing a bug: source package doesnt exist, suggestion list doesn't accept input" [Medium,Confirmed] https://launchpad.net/bugs/28682
=== kiko-fud is now known as kiko
[19:55] <sidnei> niemeyer: ping?
[20:15] <niemeyer> sidnei: Heya!
[20:16] <sidnei> niemeyer: not going to fisl, are you?
[20:16] <niemeyer> sidnei: Unfortunately not :(
[20:16] <sidnei> too bad :(
[20:16] <niemeyer> sidnei: Yeah.. I'd really enjoy to see you guys there
[20:17] <niemeyer> sidnei: How're things going? Lots of plone-related hacking?
[20:18] <sidnei> niemeyer: so so, mostly fixing upgrade issues, we (enfold) are about 6 months late with our releases due to that
[20:18] <sidnei> plone 3.1 is about to come out and we haven't made a release of a 3.0-based enfold server yet!
[20:20] <niemeyer> sidnei: You mean upgrades of applications you're in charge of from Plone 3.0 to 3.1, or of the custom changes you have on top of Plone?
[20:21] <sidnei> niemeyer: actually plone's own upgrades were messed up
[20:22] <niemeyer> sidnei: Uh oh.. sounds painful
[20:22] <sidnei> i can't describe how bad it is
=== kiko is now known as kiko-phone
=== kiko-phone is now known as kiko
[21:51] <nand> barry: The mailing list just went live! thanks!
[21:51] <barry> nand: yes, we're psyched!  btw, did you get a notification with a bogus host name in its subscription link?
[21:52] <nand> barry: yes, indeed.
[21:52] <barry> nand: :(  i was afraid of that
[21:52] <nand> barry: want the URL?
[21:52] <barry> nand: okay, thanks.  we're working on that.  but your mailing list should still be working.  can you give it a try?
[21:52] <barry> nand: naw, we all got them too ;)
[21:52] <nand> barry: I just subscribed, seems okay
[21:53] <barry> nand: cool.  try sending the list a message and see if it shows up in your archive
[21:53] <nand> brainstorm-dev@gangotri.canonical.com ?
[21:53] <barry> nand: brainstorm-dev@lists.launchpad.net
[21:54] <barry> nand: were did the wrong host name (gangotri) show up?
[21:54] <nand> barry: https://launchpad.net/~brainstorm-dev/+contactaddress
[21:54] <barry> nand: i'm not authorized to see that page unfortunately
[21:55] <barry> nand: but i'll take your word for it
[21:55] <nand> "E-mail notifications for this team should go to:" [x] "The Launchpad mailing list for this team - brainstorm-dev@gangotri.canonical.com"
[21:55] <barry> nand: are you on edge?
[21:56] <nand> barry: no.
[21:56] <barry> nand: okay, thanks
[21:56] <barry> nand: i appreciate the feedback.  would it be okay to ping you again later if i have more questions?
[21:56] <ubotu> New bug: #218384 in malone "OOPS processing Mantis bugwatches" [Undecided,New] https://launchpad.net/bugs/218384
[21:57] <nand> barry: Unfortunately I'll go to sleep soonish. But whenever you want after, yes.
[21:57] <barry> nand: cool, thanks
[21:58] <nand> barry: Have to go, see ya.
[21:58] <barry> nand: see ya
=== salgado is now known as salgado-brb
[22:23] <TeTeT> barry: as you're online, just got a mail for a mailing list pointing to https://xmlrpc.lp.internal/~tspindler/+editemails
[22:23] <TeTeT> barry: maybe a known problem?
[22:24] <barry> TeTeT: known problem, we're working on it!
[22:24] <TeTeT> barry: ok, good luck
[22:24] <barry> TeTeT: thanks ;)
=== RzR is now known as rZr
=== salgado-brb is now known as salgado
=== synico is now known as synic
[23:36] <ubotu> New bug: #218429 in launchpad "OpenID What's This?" [Undecided,New] https://launchpad.net/bugs/218429
[23:37] <LaserJock> barry: so are we supposed to ignore those emails?
[23:51] <barry> LaserJock: the emails mean the mailing list is live (yay), but the urls are wrong (boo), but we have a fix working its way through that will fix them (yay) but no second notification will be sent (yay or boo :)
[23:52] <LaserJock> barry: but I'm already a member of the list I got an email for
[23:52] <barry> LaserJock: was the list live and working before you got that email?
[23:52] <LaserJock> yeah
[23:52] <LaserJock> we've been using it for weeks
[23:53] <LaserJock> Rinchen: did you get one?
[23:53] <barry> LaserJock: ok, thanks.  you can ignore it, but definitely let me know if you ever get it again for that list. 
[23:53] <LaserJock> barry: k, I wasn't sure what I was supposed to do with it but I figured I could ignore it
[23:53] <LaserJock> barry: just wanted to make sure it wasn't a bug
[23:54] <barry> LaserJock: thanks, i appreciate the feedback!
[23:56] <Rinchen> barry, I'm sending out an email to -users 
[23:56] <Rinchen> be out in a few minutes...just checking my urls work
[23:56] <barry> Rinchen: cool.  note that we still have two patches to cp before everything should be working normally
=== salgado is now known as salgado-afk