[00:00] <maco> er...oh. so you have an @ubuntu and an @kubuntu?
[00:00] <nhandler> yeah
[00:00] <Hobbsee> nhandler: you are using kubuntu.org, aren't you.
[00:00] <Hobbsee> not kubuntu.com?
[00:00] <nhandler> Right, I am using kubuntu.org
[00:00] <Hobbsee> good ;)
[00:00] <nhandler> It was bouncing up until toda
[00:01] <nhandler> s/toda/today/
[00:02] <Hobbsee> check your spam?
[00:03]  * Hobbsee also notes that setting your @ubuntu.com address as your primary has been known to cause problems in the past, but isn't sure it's still an issue now
[00:04] <nhandler> Hobbsee: I got your email. But for some reason, I still can't get any of the emails I send to nhandler@kubuntu.org
[00:04]  * jpds points at the docs he wrote for these kinds of situations: https://wiki.ubuntu.com/UbuntuEmail
[00:05] <Hobbsee> jpds: oh, thankyou!
[00:09] <nhandler> Hobbsee: Thanks for your help. They were getting put under All Mail and skipping the inbox. Another great gmail feature
[00:09] <Hobbsee> nhandler: gotta love gmail's "features"
[00:09]  * Hobbsee just autoforwards all mail from there
[00:18] <Peng_> Is it just me, or are both launchpad-users mailing lists still being used?
[00:20] <mthaddon> Peng_: there was a temporary problem with the redirect from the old list to the new one, but it's now been fixed
[00:22] <soc> question:
[00:22] <soc> i uploaded a package to my ppa, but i got this error via mail:
[00:22] <soc> Rejected:
[00:22] <soc> Could not find person 'soc-nw-krg'
[00:22] <soc> Unable to find distroseries: unstable
[00:22] <soc> Further error processing not possible because of a critical previous error.
[00:22] <soc> what's wrong?
[00:22] <Peng_> mthaddon: Okay. :)
[00:23] <Hobbsee> soc: well, soc-nw-krg doesn't seem to exist, according to launchpad, and launchpad doesn't know about 'unstable', as that's a debian release name, not an ubuntu one.
[00:24] <soc> mhhh ... i can't remember using anything of that ...
[00:24] <Hobbsee> you would have, in dput.cf which you modified
[00:24] <soc> my .dput.cf looks like this:
[00:24] <soc> [soc-nw-krg]\n fqdn = ppa.launchpad.net\n method = ftp\n incoming = ~soc-nw-krg/ubuntu/\n login = anonymous\n allow_unsigned_uploads = 0
[00:25] <soc> \n means break
[00:25] <Hobbsee> right
[00:25] <Peng_> mthaddon: THanks for the quick response. :)
[00:25] <Hobbsee> look at where you have soc-nw-krg in that.
[00:25] <soc> yes ...
[00:25] <soc> ~soc-krg-nw is the url of my page on launchpad
[00:26] <spiv> soc: soc-krg-nw != soc-nw-krg
[00:26] <Hobbsee> https://launchpad.net/~soc-nw-krg comes up as a 404
[00:26] <soc> ouch
[00:27] <soc> sorry, i'm stupid
[00:27] <soc> sure, that's the mistake!
[00:27] <Hobbsee> oops ;)
[00:28] <soc> now i get "Already uploaded to ppa.launchpad.net" when i try to upload it again ...
[00:28] <Hobbsee> use dput -f, but did you fix both errors?
[00:29] <soc> that distroseries error?
[00:29] <Hobbsee> yes
[00:29] <soc> mhh, where can i correct "unstable"?
[00:29] <Hobbsee> debian/changelog
[00:29] <soc> it's not in the dput.cf
[00:29] <soc> ah k
[00:29] <Hobbsee> then rebuild your source
[00:29] <soc> mom
[00:30] <soc> what should it read instead of unstable?
[00:30] <soc> main?
[00:30] <Hobbsee> which ubuntu release do you want to build for?
[00:30] <Hobbsee> intrepid?  jaunty?  hardy?
[00:30] <soc> intrepid/jaunty?
[00:30] <soc> i hope the package gets included in jaunty
[00:30] <soc> but i hope to use it on my intrepid system
[00:31] <Hobbsee> right
[00:31] <Hobbsee> so to test it out, start with intrepid
[00:31] <soc> ok
[00:31] <Hobbsee> then you can copy it to jaunty later, iirc
[00:31] <soc> btw, how can i get a package accepted in ubuntu?
[00:31] <Hobbsee> new package, or change to existing?
[00:32] <soc> new package
[00:32] <soc> it doesn't exist in debian
[00:33] <Hobbsee> https://wiki.ubuntu.com/MOTU/Contributing#Preparing%20New%20Packages, it appears
[00:34] <MTecknology> Hobbsee: Any chance you'd be able to do that little thing on the wiki for me? if you have time?
[00:38] <MTecknology> hrm - what's making the LP people so busy?
[00:39] <MTecknology> It seems like all of a sudden it's taking a long time to get anything done
[00:39] <Hobbsee> MTecknology: holidays, maybe?
[00:40] <MTecknology> OH!
[00:40] <MTecknology> wow - the worst part is that's an actual epiphany
[00:40] <soc> Hobbsee: mhh, the bug already exists ... so i basically have to write a shell script to fetch the source file from the git and clean it?
[00:41] <Hobbsee> soc: you need to put the package itself on revu - do a checkout from the git, iirc.
[00:41]  * Hobbsee isn't overly familiar with git
[00:44] <soc> ah k
[01:06] <CarlFK> lp doesn't have wiki yet.  where is the appropriate place to put install instructions?
[01:07] <CarlFK> I am thinking either blueprint, check in INSTALL.txt, or maybe open a bug.
[01:25] <jamesh> CarlFK: probably neither of those.
[01:26] <maxb> What sort of install instructions? I don't think launchpad is supposed to replace a project website entirely
[01:26] <jamesh> CarlFK: I'd suggest one of (1) a file inside your branch/tarball, (2) the notes associated with the project release registered on launchpad or (3) the project description on Launchpad
[01:35] <CarlFK> jamesh: project description is reasonable.
[01:38] <CarlFK> it's really just wget/tar/cd/cd/bzr branch lp.../
[01:39] <CarlFK> maybe i can just link to head%3A/INSTALL.txt
[02:17] <soc> *sigh*
[02:17] <soc> what's wrong now?
[02:18] <soc> Rejected:
[02:18] <soc> ttf-droid_1.00~b112-1.dsc: Section 'X11' is not valid\n ttf-droid_1.00~b112.orig.tar.gz: Section 'X11' is not valid\n ttf-droid_1.00~b112-1.diff.gz: Section 'X11' is not valid
[02:18] <soc> Further error processing not possible because of a critical previous error.
[02:18] <soc> does it make a difference between X11 and x11?
[02:19] <Hobbsee> likely
[02:19] <Hobbsee> !section
[02:19] <soc> damit ...
[02:19] <soc> it takes hours to upload that again ...
[02:19] <Hobbsee> everything else is, so..
[02:19] <Hobbsee> you can build with -sd if you're not changing the original tarball, and it'll only upload the rest of it
[02:20] <Hobbsee> !section is <reply> Please see http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections for a list of valid sections that you can use in your debian/control file, for debian packaging
[02:34] <soc> grrrrrrrr
[02:34] <soc> Rejected:
[02:34] <soc> Unable to find ttf-droid_1.00~b112.orig.tar.gz in upload or distribution.
[02:34] <soc> Files specified in DSC are broken or missing, skipping package unpack verification.
[02:34] <soc> i give up
[02:34] <soc> good night
[06:04] <CarlFK> oh yeah... I changed my username.  so now bzr push doesn't....
[06:05] <CarlFK> how do I straighten that out?
[06:05] <jamesh> CarlFK: bzr push --remember lp:whatever
[06:05] <jamesh> that'll remember the new location for future invocations
[06:08] <CarlFK> http://dpaste.com/105863/   target:  https://code.edge.launchpad.net/~carlfk/web2conf/badges
[06:09] <spiv> CarlFK: you need to do "bzr launchpad-login carlfk"
[06:10] <CarlFK> Pushed up to revision 48.   - thanks
[06:54] <CarlFK> https://edge.launchpad.net/~carlfk/+archive  installed python-poppler and it didn't apply the patch
[06:55] <CarlFK> I think it has something to do with odd build requirements: "apt-get build-dep python-poppler" errored: unmet depandencies
[06:55] <CarlFK> but aptitude build-dep python-poppler installed what was needed
[10:03] <f4> Hi, to use the "decentralized with human gatekeeper workflow" i have to set me as the owner of the trunk branch right?
[10:03] <dlynch> Is it possible to make releases without having any series or milestones? My project is modest - so far, I'm the only developer.
[10:03] <f4> i've got an unruly developper :)
[10:06] <jml> f4: that's right.
[10:07] <al-maisan> dlynch: what do you mean?
[10:07] <f4> thanks
[10:07] <dlynch> al-maisan: I have read the documentation on series and milestones, which concludes by talking about releases
[10:07] <al-maisan> aha
[10:08] <dlynch> does that mean I cannot make a release from trunk, without using series?
[10:09] <al-maisan> dlynch: just a minute..
[10:09] <dlynch> al-maisan: thank you
[10:13] <al-maisan> dlynch: I think you will need to have a series at a minimum.
[10:14] <dlynch> al-maisan: can i make my "series" be identical to trunk? :)
[10:15] <al-maisan> dlynch: "trunk" is really the tip of your source branch and hence a "moving target"
[10:16] <dlynch> al-maisan: I understand that part. Does that mean I should get into the discipline of making a new series even if all it does is represent a snapshot of trunk? My project is currently so modest, that's all that a release amounts to
[10:17] <al-maisan> if all you want is trunk then there's no need for a relase either
[10:17] <al-maisan> trunk means bleeding edge
[10:17] <al-maisan> a release has to be identified somehow and that's what a series is there for
[10:19] <al-maisan> .. and yes, just checked that, a product release requires a product series.
[10:19] <dlynch> thanks for looking into this
[10:19] <al-maisan> dlynch: you are welcome.
[10:20] <dlynch> and one more thing: the documentation is generally excellent - it sure looks pretty too :)
[10:21] <al-maisan> dlynch: oh, thanks :)
[10:21] <al-maisan> that's very kind of you!
[10:29] <f4> what about PQM is there a good documentation about it somewhere?
[10:31] <al-maisan> f4: PQM is part of the launchpad-internal build/integration test infrastructure.
[10:32] <al-maisan> What would you like to know about it?
[10:34] <f4> how it works/how to use it with a laucnhpad project
[10:34] <f4> it looks interesting
[10:34] <al-maisan> f4: PQM is used by the team is bulding launchpad proper
[10:35] <al-maisan> there is no need to use it with any projects *registered with* launchpad
[10:35] <al-maisan> .. by the team *that* is bulding launchpad proper ..
[10:37] <LarstiQ> f4: the Bazaar team uses pqm, but I don't think it's possible to use pqm in a fully integrated way with launchpad
[10:38] <asabil> hi all
[10:39] <f4> ok i was expecting that since it's not really documented
[10:40] <LarstiQ> f4: if you'd want you could set it up yourself, but indeed, it's a bit underdocumented
[10:40] <LarstiQ> people have been known to succeed though :)
[10:41] <f4> i was using https://code.launchpad.net/bzr as a "template" for my own project (to see how they work) and they use it
[10:41] <LarstiQ> right, we do
[10:42] <LarstiQ> f4: the way that is set up, the canonical trunk branch is controlled by pqm and lives at http://bazaar-vcs.org/bzr/bzr.dev. lp:bzr is then mirrored from there
[10:42] <f4> but anyway i don't need it. we're only 2 working on a small project, should be a few more in a few weeks/month but not much
[10:43] <f4> i was just curious :)
[10:43] <LarstiQ> right, pqm is overkill in that situation :)
[10:46] <f4> but i think i'm going to act as gatekeeper because my mate keeps pushing untested/incomplete code on the trunk branch
[10:47] <f4> and it's still interesting to manage it like a big project even if it's not :) i'm still a student i'm here to learn :)
[10:51] <LarstiQ> f4: human gatekeeper sounds like a good solution
[11:15] <f4> one more question, my mate is creating many small branches instead of going on with the same one for a task, but he claims he's keeping the same. in fact he uses bzr pull to get last trunk revision before he works
[11:15] <f4> is that the reason? he should be merging trunk into the feature branch right?
[11:20] <LarstiQ> f4: the situation isn't clear to me
[11:28] <f4> well it looks like this http://bluebox.selfip.com/vrac/bazaar_bad.png while it should look more like this http://bluebox.selfip.com/vrac/bazaar_good.png (sry for bad quality "image hack" ^^)
[11:29] <LarstiQ> f4: neither is particularly wrong
[11:29] <LarstiQ> f4: in general, there is no right or wrong approach, you can use the workflow you want
[11:29] <f4> the branch i linked ont the second picture are related to the same task
[11:29] <LarstiQ> f4: however, there seems to be a difference of opinion on what workflow you two want to use
[11:29] <f4> tash which has a blueprint
[11:30] <f4> only the first one is actually linked to the blueprint (the red one)
[11:31] <f4> no we agreed on that, in his head he was doing the second picture :)
[11:32] <f4> so the "problem" is that he's doing pull instead of merging the trunk in his branch i suppose
[11:39] <LarstiQ> I still don't see what the problem is
[11:48] <f4> the problem is there is 3 branches while he though he was working on the same one
[11:51] <f4> he though he was doing the same as the branch going from rev 25 to 28
[12:41] <Hobbsee> thankyou, launchpad users mailing list, for the spam.
[12:41]  * Hobbsee thought the DC ran a spam filter
[12:42] <beuno> Hobbsee, you mean the autoreply?  ;)
[12:45] <Hobbsee> beuno: by subject only, it appears.  the content doesn't look to be an autoreply ;)
[12:45] <Hobbsee> apart from the fact that it's very late, it looks rather non-autoreply-ish
[12:49] <beuno> ay
[12:49] <beuno> more noise
[12:50] <beuno> barry, did anything change in the ML settings for lp-users?
[12:50] <Hobbsee> ...and there goes the second one
[12:52] <Hobbsee> ...and the third.
[12:52]  * Hobbsee wonders hwy they're sending to lists.canonical.com
[12:54] <barry> beuno: yes, elmo fixed the forwarding yesterday so now it's working the way it was supposed to :)
[12:55] <beuno> barry, why weren't we getting these annoying emails before?
[12:55] <beuno> where some users blocked and not migrated over?
[12:55] <barry> what annoying emails?
[12:55] <beuno> vacation and away replies
[12:56] <Hobbsee> which are actually trying to sell things
[12:56] <barry> beuno: can you check the list copies and be sure they have a Precedence: list header?
[12:57] <barry> are you seeing them only when you try to send a message to the list?  i didn't see any on my test yesterday
[12:57] <beuno> barry, Precedence: list
[12:57] <beuno> the one from: consultoriatelecon@hotmail.com
[12:58] <beuno> to: launchpad-users@lists.canonical.com
[12:58] <barry> okay, so our lists are doing the right thing, but those vacation responders are broken
[12:58] <beuno> possibly, but I wonder why *now*
[12:58] <beuno> maybe because those users are now subscribed and they weren't before?
[12:59] <barry> if on the old list the email address was linked to a lp user, we subscribed that address to the new list
[13:00] <barry> but there were lots of new subscribers to just the new team/list
[13:00] <barry> so it's very possible you're getting the bounces from them
[13:01] <superm1> Hi guys, i can't seem to figure out how to delete a team from LP.  Is the UI missing for it, or am I just missing it?
[13:01] <beuno> barry, cool. So now we start blocking users?  :)
[13:02] <al-maisan> superm1: https://answers.edge.launchpad.net/launchpad/+faq/47
[13:03] <superm1> al-maisan, that's for closing accounts though, is it valid for teams too?
[13:03] <al-maisan> superm1: I think so.
[13:04] <superm1> al-maisan, no in the change details section of the team, there is nothing on deactivating it
[13:04] <barry> beuno: on python.org we get medieval on people with broken replybots :)
[13:05] <al-maisan> superm1: OK .. let me find out more.
[13:05] <superm1> i should clarify; i dont want to just remove myself from the team.  i want to remove the team from existing
[13:05] <superm1> i'm the team administrator
[13:05] <beuno> barry, that's the spirit!
[13:06] <al-maisan> superm1: that's understood.
[13:14] <superm1> i've gone through and removed all members of the team (including myself) and all team memberships and still nothing is presented anywhere in the UI that I can find for removing the team: https://edge.launchpad.net/~mythbuntu-trunk
[13:15] <sinzui> superm1: make a request (ask a question) to at answers.launchpad.net/launchpad. An Admin can deactivate the team
[13:15] <superm1> sinzui, ah great thanks.
[13:16] <sinzui> superm1: The process of deactivate is an admin privilege because the changes a lot of users, bugs, etc...
[13:17] <superm1> sinzui, even for teams though?  I would think that teams wouldn't be commenting on bugs, and at least an empty team wouldn't require changing any users
[13:17] <sinzui> superm1: They can be subscribed to bugs, blueprints, answers. They have translations powers too
[13:18] <superm1> ah.  all things i never used the team for i suppose
[13:47] <balor> Is there any way to create a new project in lp so that I can upload my local bzr repo?  i.e. I don't want to import (because the bzr repo is not on a public server)
[13:48] <superm1> yeah shouldn't you be able to make a project and just bzr push?
[13:49] <balor> superm1: What's the link to make a project?  I can only find to register a branch
[13:50] <superm1> balor, https://launchpad.net/projects/+new-guided
[13:50] <balor> thanks
[14:13] <Shred00> somebody advised I come ask here: can we have the production of -dbg packages enabled for PPA builds?  it helps greatly with reporting crashes if stack traces have symbols.
[14:21] <al-maisan> Shred00: https://bugs.edge.launchpad.net/soyuz/+bug/285205
[15:01] <adiroiban> hi guys.﻿ do you know where I could find the Launchpad OpenID plugin for moinmoin ? the same one used on help.ubuntu.com/community ?
[15:02] <andrea-bs> adiroiban: help.ubuntu.com uses the default MoinMoin plugin for OpenID support
[15:05] <fjlacoste> andrea-bs: not sure of that
[15:05] <andrea-bs> fjlacoste: I have the same in my MoinMoin instance
[15:05] <adiroiban> it's moinmoin 1.7 ?
[15:05] <fjlacoste> adiroiban: the default OpenID plugin should work, but if you want Launcphpad team support, that extension hasn't been pushed upstream yet
[15:05] <adiroiban> i thought it's 1.6
[15:05] <fjlacoste> andrea-bs: the default extension lacks team integration
[15:06] <adiroiban> can I get the LP plugin from downstream ?
[15:06] <andrea-bs> flacoste: is there a team integration for MoinMoin?
[15:09] <flacoste> andrea-bs: yes
[15:09] <flacoste> andrea-bs: you can use launchpad team in ACL
[15:09] <flacoste> but this hasn't been released yet
[15:11] <andrea-bs> flacoste: cool, could you tell me when will it be released? I can't find anything on dev.launchpad.net :(
[15:11] <flacoste> andrea-bs: don't know yet, i'll take to the people doing it, last month we released the Dupal extensions, the Moin ones should follow soon
[15:12] <andrea-bs> thanks, flacoste
[15:13] <adiroiban> flacoste, can we have the unrelease code ? I would like to integrate it into our loco wiki page
[15:14] <flacoste> adiroiban: can you file a question on answers.launchpad.net/launchpad/+addquestion about this?
[15:14] <adiroiban> sure
[15:14] <adiroiban> i'd do this right away
[15:14] <flacoste> adiroiban: that way we could track it there, i'll ask the guys who are in charge of that process to comment on it
[15:15] <adiroiban> ok. No problem. I was thinking the code is somewhere in a bzr branch and it's just me who can not  find it
[15:16] <coolbhavi> hello
[15:16] <coolbhavi> Please see : https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/314308
[15:17] <coolbhavi> bug was not reported properly so I changed the package and description and asked for more info
[15:18] <al-maisan> coolbhavi: yes, ..?
[15:18] <coolbhavi> but rude and arrogant answers
[15:19] <coolbhavi> esp : https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/314308/comments/4
[15:19] <al-maisan> coolbhavi: I see .. somebody will look into this.
[15:19] <coolbhavi> look at the whole comment by expanding the links
[15:19] <coolbhavi> please
[15:27] <al-maisan> coolbhavi: please explain what you find so offensive about that comment .. I believe the user was using that quote as a signature and it was not specifically targeting you.
[15:28] <al-maisan> I understand that it may have hurt your feelings but that comment does not appear to be outright and intentionally offensive.
[15:35] <coolbhavi> al-maisan, I know him pretty well
[15:35] <al-maisan> personally?
[15:36] <coolbhavi> al-maisan, yup, his signature is only his name
[15:36] <al-maisan> hmm..
[15:36]  * al-maisan looks at that comment again
[15:37] <CarlFK> can I see the code that builds PPA binaries ?
[15:37] <al-maisan> CarlFK: what do you mean?
[15:37] <al-maisan> the build system?
[15:37] <CarlFK> what I get from my PPA is not what I get when I apt-get source and build it local
[15:37] <al-maisan> hmm .. what are the differences?
[15:38] <CarlFK> the patch isn't applied
[15:38] <coolbhavi> al-maisan, okay leave it he is a beginner and I ve marked it incomplete :)
[15:38] <CarlFK> https://edge.launchpad.net/~carlfk/+archive  Intrepid is the only one I have tested
[15:38] <al-maisan> coolbhavi: thank you very much .. I believe this is the best course of action .. give him the benefit of doubt
[15:39] <coolbhavi> al-maisan, :)
[15:39] <al-maisan> :)
[15:40] <CarlFK> I think it has something to do with odd build requirements: "apt-get build-dep python-poppler" errored: unmet dependencies, but aptitude build-dep python-poppler installed what was needed
[15:40] <al-maisan> CarlFK: did you apt-get source from the PPA?
[15:40] <CarlFK> al-maisan: yes
[15:40] <al-maisan> hmm .. that's a bit odd.
[15:40] <CarlFK> the upstream version has no patches.  I have 1 patch that adds 2 chars.  so pretty easy to track
[15:43] <maxb> CarlFK: Your package has an odd version number. How can it be based on 0.8.1-2 when unstable and jaunty only have 0.8.1-1 ?
[15:45] <CarlFK> maxb: " increase the Ubuntu version number and add a suffix of ~ppan " https://help.launchpad.net/Packaging/PPA#Versioning
[15:45] <maxb> hrm
[15:46] <maxb> Should probably have been 0.8.1-1ubuntu0~ppa1 in this case
[15:46] <al-maisan> CarlFK: my guess is that it's related to the unmet "build-dep python-poppler" dependencies
[15:47] <CarlFK> al-maisan: cept then it should have errored, not build a binary
[15:47] <maxb> Also, ideally your package would be in .orig.tar.gz and .diff.gz form - but it has accidentally ended up transformed into single-tarball form
[15:47] <al-maisan> CarlFK: please point me to your PPA
[15:47] <CarlFK>  https://edge.launchpad.net/~carlfk/+archive  Intrepid is the only one I have tested
[15:51] <al-maisan> CarlFK: so, what were the unmet dependencies that apt-get build-dep complained about?
[15:51] <CarlFK> al-maisan: give me a sec - I think I have a fresh ibex box..
[15:51] <al-maisan> OK
[15:52] <maxb> CarlFK: It is an error to include a hyphen within the release portion of the version number. That is why your packaging has gone into single-tarball style
[15:55] <maxb> CarlFK: Your patch is not being applied because you have improperly integrated quilt into debian/rules
[15:55]  * mpt is getting confused by duplicate bug report messages
[15:56] <CarlFK> maxb: that wouldn't surprise me.
[15:56] <CarlFK> al-maisan: my ibex install was waiting for me to confirm disk partitioning... so that's gonna be a few min (u-server, so maybe 10 min)
[15:57] <al-maisan> CarlFK: fair enough .. but I believe maxb found the root cause of your problem anyway
[15:57] <CarlFK> maxb: shouldn't the PPA build process have aborted?
[15:59] <maxb> No, because your rules file was genuinely configured to not apply the patch! :-)
[15:59] <CarlFK> doh
[16:00] <CarlFK> so whad I do wrong?
[16:01] <maxb> CarlFK: configure should stay depending on configure-stamp. configure-stamp should get an extra dependency on $(QUILT_STAMPFN)
[16:02] <CarlFK> I remember wondering about that
[16:02] <CarlFK> thanks
[16:10] <mpt> al-maisan, seen <https://launchpad.net/cs-112---assignment-6>? :-)
[16:10]  * al-maisan looks
[16:11] <bigjools> ha - does someone want his homework done for him?
[16:11] <mpt> bigjools, I see the top contributor is someone else :-)
[16:12] <al-maisan> strange project indeed :)
[16:13] <al-maisan> This person "david" seems to be an aspiring "project manager" :)
[16:16] <Kmos> ftp.launchpad.net is down ?
[16:16] <Kmos> can't upload to PPA
[16:17] <al-maisan> Kmos: any error messages?
[16:17] <Kmos> ppa.launchpad.net i mean (connection refued)
[16:17] <Kmos> refused
[16:17] <Kmos> it worked yesterday :)
[16:18] <al-maisan> please show me your dput conf file
[16:18] <bigjools> al-maisan: I can't get to it either
[16:18] <al-maisan> ah
[16:18] <bigjools> poppy is probably down
[16:19] <bigjools> cprov: ^
[16:19] <al-maisan> Kmos: what bigjools said.
[16:19] <Kmos> al-maisan: http://paste.ubuntu.com/101125/
[16:19] <Kmos> ah :)
[16:19] <al-maisan> thanks :)
[16:19] <Kmos> np
[16:25] <coolbhavi> Check your network (111, 'Connection refused') while trying to upload to PPA
[16:26] <al-maisan> coolbhavi: thanks for the hint .. we are already looking at it.
[16:27] <coolbhavi> al-maisan, :)
[16:31] <ahasenack> hey guys, quick question: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/306360 is not listed at https://bugs.launchpad.net/ubuntu/+source/landscape-client even though one task is not yet resolved. How can I change that?
[16:34] <beuno> ahasenack, I think that's a bug in Launchpad
[16:34] <beuno> BjornT, gmb?
[16:35] <RainCT> Hi
[16:35] <RainCT> I'm getting "Connection failed, aborting. Check your network (111, 'Connection refused')" trying to dput to a private PPA. Some days ago I had no problem with this. Any idea on what may be the problem?
[16:36] <gmb> beuno: Looking...
[16:36] <beuno> you *can* see it if you look at "All bugs ever reported"
[16:36] <bigjools> RainCT: we're on it
[16:36] <RainCT> bigjools: so it's not only me?
[16:37] <coolbhavi> RainCT, +1
[16:37] <bigjools> RainCT: unfortunately correct
[16:37] <RainCT> OK, thanks
[16:37] <ahasenack> beuno: but that includes the closed ones?
[16:38] <gmb> ahasenack: The task that would appear at https://bugs.edge.launchpad.net/ubuntu/+source/landscape-client has been resolved - it's Fix Released.
[16:38] <gmb> ahasenack: I think that that page only shows...
[16:38] <ahasenack> gmb: so I need to change the task that is tracked to the other one?
[16:38] <CarlFK> ~$ ftp ppa.launchpad.net
[16:38] <CarlFK> ftp: connect: Connection refused
[16:38] <gmb> ahasenack: Ah hang on, I might be talking out of my hat.
[16:39] <CarlFK> is that me, or does it go off line now and then?
[16:39] <coolbhavi> CarlFK, +1  seems ftp is down
[16:39] <CarlFK> coolbhavi: thanks.
[16:39] <ahasenack> gmb: my confusion is that there doesn't seem to be a simple way to list all open bugs against a package. That was my intention with the https://bugs.launchpad.net/ubuntu/+source/landscape-client URL
[16:40] <gmb> ahasenack: Right... Ah, I see the problem now.
[16:41] <gmb> ahasenack: So, this is sort of a bug, sort of not.
[16:41] <alefteris> Hi all. Is there a way to search all launchpad ppa with a package name?
[16:41] <gmb> ahasenack: The problem is that because the bug has been targetted to a series (Jaunty and Intrepid in this case) the original task is no longer considered a task (that's why it says "status tracked in... blah").
[16:41] <bigjools> alefteris: not right now, no
[16:42] <gmb> ahasenack: So when you look at just the package page it will show you only the ones assigned to the package, not the ones targetted to a particualr series (well, it might show the ones for Jaunty because it's the current series; I haven't established that for sure yet).
[16:43] <ahasenack> gmb: so, how do I change where the status is tracked?
[16:46] <gmb> ahasenack: Well, I was right; the Jaunty tasks will show up at +source/landscape-client (because it's the current series). (see https://bugs.staging.launchpad.net/ubuntu/+source/landscape-client for an example)
[16:46] <gmb> ahasenack: As for changing where it's tracked, I'm not sure you can.
[16:47] <gmb> Since Jaunty is the current series for Ubuntu, so that's where the changes are tracked for the Ubuntu package.
[16:47] <gmb> Which, yes, is a bug.
[16:47] <ahasenack> gmb: yeah, because that means I'm better off opening another ticket for intrepid instead of another task at that ticket
[16:47] <ahasenack> gmb: because or else the ticket just "disappears" from the bug listing as was this case
[16:48] <gmb> ahasenack: For tracking purposes, yes, which sucks massively.
[16:48] <gmb> Absolutely blows.
[16:48] <ahasenack> gmb: ok, is there a bug open for it? If not, should I open one?
[16:48] <ahasenack> gmb: I'm not even sure how to search for this in launchpad to see if there is a bug already open or not :)
[16:48] <gmb> ahasenack: I'll file a bug about this (or find if there is one; *someone* must have seen this before)
[16:49] <ahasenack> gmb: cool, many thanks!
[16:49] <gmb> ahasenack: Sorry it had to bite you.
[16:49] <ahasenack> gmb: now that I'm aware of how it works, it's ok for the time being
[16:49] <ahasenack> gmb: thanks for the help
[16:49] <gmb> np
[16:49] <soc> does someone know how long it will take to restore uploading?
[16:50] <bigjools> not yet
[16:51] <al-maisan> alefteris: https://answers.edge.launchpad.net/launchpad/+faq/203
[16:51] <bigjools> something filled up the disk, the admins are investigating
[16:54] <alefteris> al-maisan, thanks :)
[16:55] <alefteris> al-maisan, the results listing is not very usufull though, it would be nice if the packages where listed
[16:57] <bigjools> alefteris: https://bugs.edge.launchpad.net/soyuz/+bug/280958
[16:58] <maxb> ooi, does anyone know how far off signed PPAs are? Just roughly days/weeks/months?
[16:58] <beuno> cprov, ^
[16:58] <bigjools> maxb: days
[16:58] <superm1> Hi guys, for the purposes of an automated package builder, how long does the publisher take to publish a .orig.tar.gz on a PPA?  We're doing builds for hardy and intrepid, but only want to upload orig.tar.gz once, so the first upload will have orig.tar.gz, and second wouldn't
[16:59] <bigjools> superm1: up to 20 minutes
[16:59] <superm1> bigjools, okay so sleeping for say 25 minutes should be a safe estimate then
[16:59] <bigjools> superm1: as long as it is accepted, yeah
[16:59] <superm1> there's no cirumstances that it will be larger right?
[17:00] <bigjools> superm1: can you wait for the acceptance mail or is that not an option?
[17:00] <superm1> bigjools, well it would be a bit difficult to do so the way the job is cronned, so a static time would be a lot better
[17:00] <bigjools> if it's not, add your voice to bug 305331 :)
[17:00] <alefteris> bigjools, this is not related to my complain.. what i said is that the result listing of the ppa search doesn't list by package name, but by uploader
[17:01] <bigjools> alefteris: ah I see
[17:01] <bigjools> superm1: we process them every 20 minutes, so give it 30 in case there's unforseen delays and you should be ok
[17:01] <superm1> bigjools, okay great.  and yes that bug would be awesome.  i'll add a comment
[17:04] <cprov> superm1: for the record, reusing the orig in a subsequent upload is immediately possible for all source uploads. It doesn't require the source to be published on disk.
[17:04] <bigjools> of course, good point
[17:04] <cprov> superm1: it won't be possible only if the source get stuck on queue (for ubuntu uploads)
[17:05] <superm1> cprov, oh so, there wouldn't be a rejection for a .diff.gz/dsc only on the second upload if it was immediately after?
[17:06] <cprov> superm1: no, assuming the previous upload was accepted.
[17:06] <superm1> cprov, ah wonderful, then we'll just nuke the sleep between uploads.  thanks!
[17:07] <cprov> superm1: right, dput will block and upload processing is serialized. It should work, let us know if it doesn't.
[17:07] <superm1> cprov, okay thanks
[17:08] <cprov> superm1: you are welcome.
[17:11] <ahasenack> gmb: once you have the bug number (either by finding an already filed bug, or filing a new one), could you let me know? I would like to subscribe to it
[17:11] <gmb> ahasenack: I've filed it as bug 314432
[17:12] <ahasenack> gmb: cool, thanks
[17:12] <cprov> al-maisan: it's already fixed.
[17:13] <cprov> nevermind
[17:15] <superm1> Daviey, ask cprov^
[17:15] <Daviey> cprov: when was it fixed?
[17:15] <Daviey> cprov: About an hour ago, i could only get it working using passive ftp
[17:16] <Daviey> Is that related?
[17:16] <cprov> Daviey: fixed 5 minutes ago, I'm not sure if the passive-ftp issue was related.
[17:17] <cprov> Daviey: probably not.
[17:17] <Daviey> meh, i was getting conenction refused - oh well i've changed my settings to passive and it seems to be working.
[17:21] <cprov> Daviey: check w/o it, it should work as well.
[17:21] <Daviey> cprov: will do, when i next push in 20 mins
[17:22] <cprov> Daviey: great, thanks.
[17:28] <Daviey> cprov: yep, non passive worked fine then - i guess it was related.
[17:28] <Daviey> (active)
[17:28] <cprov> Daviey: probably. Anyway, all fixed now.
[17:29] <Daviey> woot
[18:07] <CarlFK> um... looking at my build logs: WARNING: The following packages cannot be authenticated!
[18:07] <CarlFK> http://launchpadlibrarian.net/20955285/buildlog_ubuntu-intrepid-i386.python-poppler_0.8.1-2~ppa3~intrepid1_FAILEDTOBUILD.txt.gz
[18:12] <LaserJock> can somebody give me details on who's allowed to see private bugs?
[18:12] <beuno> LaserJock, whoever has permissions on the project, or is subscribed to the bug
[18:12] <LaserJock> beuno: would that include bug supervisors?
[18:12] <LaserJock> or do you need to be explicitly subscribed
[18:13] <beuno> LaserJock, I'd expect the bug supervisor to see them, but I don't know for sure
[18:13] <beuno> permissions is a blurry area for me  :)
[18:14] <LaserJock> *cough* that's why you make lists *cough*
[18:14] <beuno> right, one of the plans is to have all permissions in one page, and you can configure them from there
[18:24] <CarlFK> so if my ppa build fails, I can't apt-get source it?
[18:25] <bigon> hi, is there any plan to add rmadison support to ppa?
[18:32] <james_w> bigon: it appears you could script it with the api
[18:33] <bdmurray> Is the assigner of a bug task tracked anywhere other than the the activity log / table?
[18:33] <james_w> for source package at least
[18:33] <james_w> bdmurray: assignee, or the person that created the task?
[18:34] <bdmurray> james_w: the person that assigned the bug task to an assignee
[18:35] <CarlFK> maxb: can you help me out - brain is getting overloaded, and I have 20 min before a meeting... really like to get this fixed before then. rules/results: http://dpaste.com/106056/
[18:36] <CarlFK> perhaps cookies and coffe for lunch was not part of a well balanced breakfast...
[18:41] <gsuveg> re
[18:50] <LaserJock> beuno: a bug supervisor doesn't seem to be sufficient
[18:50] <LaserJock> that's a tad problematic :(
[19:01] <bigon> I'm trying to use python-launchpadlib (example https://help.launchpad.net/API/launchpadlib) and I get a time out when connection to the stagin service
[19:18] <james_w> bigon: I've got a quick ppamadison here if you like
[19:19] <bigon> james_w: oh it would be nice
[19:29] <Pres-Gas> Okay, I have an Inspiron Mini 9 that is completely freezing when trying to join up with a wpa 2 enterprise g network.  I am getting no usable logs it freezes so hard.  Whare should I start in reporting this kind of bug?
[19:30] <rockstar> Pres-Gas, I think #ubuntu-bugs could probably help you more.
[19:30] <Pres-Gas> I am not sure to ping wpa-suplicant, or NM, or the kernel
[19:30] <Pres-Gas> Okay
[19:30] <Pres-Gas> The problem was how to start reporting it, you know, rockstar?
[19:31] <Pres-Gas> If I get usable logs, that would help
[19:31] <Pres-Gas> :P
[19:31] <rockstar> Pres-Gas, yeah, I understand.  #launchpad is more for specific issues with Launchpad though.
[19:31] <rockstar> It's a common mistake though.  We should fix that.
[19:31] <Pres-Gas> Excellent, and I thought so...I have been on launchpad for a bit...but forgot about the bugs channel
[19:31] <Pres-Gas> duh
[19:43] <CarlFK> https://bugs.edge.launchpad.net/~web2-conf/  there should be about 20+ items there
[19:44] <CarlFK> at least 5 open ones.  whered they go?
[19:45] <CarlFK> https://bugs.edge.launchpad.net/web2conf/+bugs  there they are
[20:09] <maxb> CarlFK: Got it to work in the end? I was afk
[20:09] <CarlFK> maxb: i think so
[20:09] <CarlFK> in meeing... will get back to in in 30 min or so
[20:11] <iulian> Hiya. I'd like to remove a project created by me some time ago. I initially created it to maintain some scripts using Bazaar. The project is 'iulian' (https://edge.launchpad.net/iulian). I believe it is not worth to keep it if I don't use it anymore.
[20:15] <maxb> iulian: I believe you need to file a request in https://answers.launchpad.net/launchpad for that to happen
[20:17] <iulian> maxb: Ah-ha, thanks!
[20:17] <iulian> Will do that.
[20:17] <iulian> Cheerio.
[20:56] <bigon> james_w: do you have already put the code somewhere?
[20:56] <james_w> bigon: I didn't
[20:57] <james_w> I wanted to see if it was going in to u-d-t, or whether I should write my own credentials handling routine
[22:25] <Jaearess> Is there an open source system similar to Launchpad available? One that can be hosted by a company internally and that brings together all the pieces that Launchpad.net does?
[23:26] <maxb> ooi, why does launchpad do everything over https ?
[23:28] <beuno> maxb, yes
[23:28] <beuno> except code browse (aka loggerhead)
[23:30] <jml> maxb: there are plans to allow http access, iirc.
[23:31] <jml> there certainly *were* plans.
[23:31] <maxb> It's not a problem for me, I'm just curious why it does it
[23:42] <jml> maxb: aiui, it's because a) we need https for secure authentication, b) it makes information on LP reliable as information *from* LP (which can be important for things like security bugs), c) mixing plain http and https takes a fair bit of dev work, so all https is easier.