[02:30] <MTeck> I want to start a project. It's taking something that's being developed in git and modifying it signaficantly. I doubt we'll continue on this project once our efforts are merged into the main branch. So it will be somewhat displosable... Any suggestions for how to handle it?
[02:50] <thumper> MTeck: request a git import for the project
[02:50] <thumper> MTeck: then you can work with the bzr copy
[02:51] <MTeck> thumper: I was just wondering if I should make a whole new team for it
[02:51] <thumper> MTeck: so your changes are intended to be merged back into the git trunk?
[02:51] <MTeck> hope so
[02:51] <thumper> MTeck: well, register the project in LP, request a git import and mark it as the trunk branch
[02:52] <thumper> MTeck: what is the rationale about wanting a team?
[02:52] <thumper> MTeck: individuals can work colaboratively too without teams
[02:52] <MTeck> It's a few people that will be working on the project
[02:53] <MTeck> I think just 4, but I don't want access to trunk to be given to just one person
[02:53] <thumper> MTeck: sure, register a team, it's pretty simple
[02:53] <thumper> MTeck: well, trunk will be owned by ~vcs-imports initially
[02:53] <thumper> MTeck: your version can be owned by whomever you want
[02:53] <MTeck> I was mostly concerned if it would be worth the new project
[02:54] <MTeck> Thinking about it - it might be
[02:54] <thumper> if you are intending your code to be merged back
[02:54] <thumper> I don't see the point of a new project
[02:54] <thumper> it is just new work for the existing project
[02:54] <MTeck> oh, ok
[02:54] <thumper> that may or may not be merged back
[02:54] <thumper> if the direction changes and effectively forks
[02:54] <MTeck> I have the new team - no project until I click a button
[02:54] <thumper> then it is worthwhile registering a new project
[02:55] <MTeck> I doubt a fork will happen :P
[02:55] <thumper> in which case
[02:55] <thumper> stick with the original project
[02:55] <MTeck> ok
[02:55] <MTeck> so.. how do I request the merge?
[02:55] <MTeck> import*
[02:56] <thumper> MTeck: which project?
[02:56] <MTeck> coreutils
[02:57] <thumper> MTeck: https://code.edge.launchpad.net/code-imports/+new
[02:57] <thumper> oops
[02:57] <thumper> not that
[02:57] <MTeck> I lost something :(
[02:57] <MTeck> was it my mind?
[02:58] <thumper> MTeck: https://code.edge.launchpad.net/+code-imports/+new
[02:58] <MTeck> so - I need to create a project for it then?
[02:58] <thumper> there is a coreutils project
[02:58] <thumper> The Gnu Core Utilities
[02:58] <thumper> is that it?
[02:58] <MTeck> ok
[02:58] <MTeck> ya
[03:01] <MTeck> now I just wait?
[03:01] <thumper> yep
[03:01] <thumper> MTeck: shouldn't be long
[03:02] <MTeck> thumper: then I can be given the repo?
[03:02] <thumper> MTeck: the import is running
[03:02] <thumper> MTeck: I can't remember if we email you when it is done or not :)
[03:05] <arand> Are there currently problems with the remote bug watching for gnome bugzilla?
[03:05] <thumper> arand: not sure sorry
[03:05] <thumper> spm: any idea?
[03:08] <arand> I noticed Bug #246177
[03:09] <MTeck> thumper: so that machine is doing 3 imports.
[03:09] <arand> " Launchpad couldn't import bug #563275 from GNOME Bug Tracker. "
[03:09] <MTeck> lp is confusing - always new features
[03:11] <MTeck> what is a heartbeat?
[03:11] <thumper> MTeck: we could slow down if you like?
[03:11] <spm> thumper: I know in passing that gmb has been doing some things around the watcher (or so I construed), but to actual issues - not aware of any.
[03:11] <thumper> MTeck: it means that the import slave is alive :)
[03:11] <thumper> MTeck: if we stop getting heartbeats, it has zombied, so we kill it :)
[03:12] <MTeck> thumper: What is a heartbeat though?
[03:12] <thumper> MTeck: it is the import slave talking to the import controller
[03:13] <MTeck> oh
[03:15] <MTeck> thumper: you've had an import runnign for 1/2 mo ?
[03:15] <thumper> MTeck: heh, that's the linux kernel
[03:15] <thumper> MTeck: we try it every now and then
[03:15] <MTeck> lol - how long does it usually take?
[03:16] <thumper> MTeck: well, the new bzr repo format should make that go much faster
[03:16] <thumper> MTeck: we normally kill it before it has finished
[03:18] <MTeck> YOu should move "Last heartbeat" to the right a few spaces
[03:18] <thumper> MTeck: the new 3.0 layout has changed some things
[03:18] <thumper> MTeck: table padding is one
[03:18] <thumper> MTeck: we will be fixing it soonish :)
[03:19] <MTeck> whenever the new layout is finished? :P
[03:20] <thumper> MTeck: it should be for 3.0
[03:20] <thumper> in about 3ish weeks
[03:20] <MTeck> cool
[03:20] <MTeck> This import is going to take a while, isn't it?
[03:21]  * thumper looks again
[03:22] <thumper> MTeck: yes
[03:22] <MTeck> at least I started now instead of when I needed it :P
[03:22] <MTeck> any guesses how long?
[03:25] <MTeck> So, after the import, do I just take ownership of the branch and if I ever need, request an import of a fresh one?
[03:41] <thumper> MTeck: well it started 40 minutes ago and is 1/3 through
[03:41] <thumper> MTeck: so check back in 1.5h
[03:41] <MTeck> ok, cool
[03:41] <MTeck> and the last question? :)
[03:41] <MTeck> thumper: thanks for checking too
[03:42] <thumper> MTeck: no, the import will track the changes
[03:42] <thumper> MTeck: you branch it and have a personal copy
[03:42] <thumper> MTeck: you should set the import as the development focus
[03:42] <thumper> MTeck: actually you can't, it is owned by registry admins
[03:42] <MTeck> ok, thanks
[03:42] <thumper> spm: can you set the import as the dev focus for coreutils?
[03:43] <charles_> hello
[03:43] <charles_> new here
[04:15] <days_of_ruin> Could someone change the permissions on this blueprint: https://blueprints.launchpad.net/giftwrap/+spec/use-libunique I am a member of the giftwrap-devs and I cannot edit this blueprint, I can edit all of the other ones.
[04:16] <days_of_ruin> I think it is because there used to be a different team that that branch was registered under.
[04:26] <days_of_ruin> Any lp admins on?
[04:28] <micahg> days_of_ruin: if no one answers, you can file a request here: https://answers.launchpad.net/launchpad
[04:30] <MTeck> days_of_ruin: You need to file a request for something like that anyway
[04:30] <MTeck> afaik
[04:31] <days_of_ruin> MTeck, ok thanks for the info.
[04:32] <MTeck> days_of_ruin: oh - I call the lp admins "rubber duckies"
[04:32] <days_of_ruin> lol
[04:32] <days_of_ruin> why?
[04:34] <MTeck> days_of_ruin: look at the bottom - https://edge.launchpad.net/~spm
[04:35] <days_of_ruin> xD
[04:37] <thumper> days_of_ruin: it is the icon of the admin team :)
[04:37] <MTeck> thumper: https://edge.launchpad.net/~hardware-certification
[04:37] <MTeck> s/towards/toward/
[04:38] <thumper> MTeck: what about it?
[04:38] <MTeck> thumper: I just thought I'd let somebody know it's wrong
[04:39] <MTeck> towards isn't actually a word
[04:41] <thumper> MTeck: yep it is
[04:41] <thumper> kinda depends who you ask
[04:41] <thumper> I'll check my shorter oxford later
[04:41] <mwhudson> maybe a us/uk thing?
[04:41] <MTeck> No - an English vs. Bad English thing
[04:42] <mwhudson> http://en.wiktionary.org/wiki/toward#Usage_notes
[04:42] <MTeck> it's like when people say probly instead of probably
[04:42] <mwhudson> MTeck: no it isn't
[04:43] <MTeck> ok....
[04:43] <mwhudson> however
[04:43]  * MTeck world has been flipped
[04:43] <mwhudson> launchpad is mostly us-ian english
[04:44] <MTeck> mwhudson: thanks for that link
[04:44] <MTeck> I need to run off now
[04:44] <mthaddon> towards something, perhaps...
[05:04] <thumper> mthaddon: heh
[05:05] <mthaddon> :)
[05:57] <spiv> Hmm, Launchpad is confused about me upgrading a hosted branch to 2a.
[05:58] <mwhudson> spiv: how so
[05:58] <spiv> lp:~spiv/bzr/insert-stream-check-chk-root is now 2a.  It is stacked on lp:bzr/2.0, which is also 2a.  But LP says: "
[05:58] <spiv> lp:~spiv/bzr/insert-stream-check-chk-root is now 2a.  It is stacked on lp:bzr/2.0, which is also 2a.  But LP says: "CHKInventoryRepository('lp-mirrored:///~bzr-pqm/bzr/2.0/.bzr/repository') is not compatible with KnitPackRepository('lp-mirrored:///~spiv/bzr/insert-stream-check-chk-root/.bzr/repository') different rich-root support
[05:58] <spiv> « No branches proposed for merging into this one. "
[05:59] <mwhudson> spiv: hey, the puller is open source now, feel free to fix it :)
[05:59] <spiv> The wrong piece of that puzzle would appear to be that lp-mirrored:///~spiv/bzr/insert-stream-check-chk-root/ is apparently not upgraded.
[06:00] <mwhudson> spiv: i guess we're trying to open the branch in it's mirrored area to determine it's format
[06:00] <mwhudson> and of course, if we could open it, we'd find it was different from the format in the hosted area and delete it
[06:00] <thumper> heh
[06:01] <thumper> oops
[06:01] <thumper> \o/ finally have tests for this annoying email bug
[06:01] <mwhudson> thumper: are you working on the merge proposal listing bug?
[06:01] <thumper> no
[06:01] <mwhudson> poolie elevated it to critical
[06:01] <thumper> and I reduced it to high
[06:01] <mwhudson> ok
[06:02] <spiv> mwhudson: oh, so the issue is that it needs to open it to find out the format, but because the branch is now unopenable because the stacked-on is now incompatible, it all falls over in a big heap?
[06:02] <mwhudson> spiv: that's my guess
[06:03] <mwhudson> spiv: haven't looked at the code yet though
[06:03] <spiv> mwhudson: that can probably be worked around by opening just the repository directly, I guess.
[06:03] <mwhudson> spiv: we want to check the branch format too though?
[06:03] <spiv> mwhudson: sure, but if the repository formats don't match you don't need to check the branch :)
[06:03] <mwhudson> i guess
[06:04] <spiv> Alternatively,
[06:04] <spiv> There's an ignore_fallbacks flag on open_branch now.
[06:04] <mwhudson>         except errors.NotBranchError:
[06:04] <spiv> You could probably use that.
[06:04] <mwhudson> ->         except (errors.NotBranchError, whatevers raised here):
[06:04] <mwhudson> in puller/worker.py:310 would also do it
[06:04] <mwhudson> but it's a bit of a hack
[06:06] <spiv> mwhudson: I'll file a bug I guess.  This is pretty important though because it means no existing 1.9 bzr branches that are stacked can be upgraded.
[06:06]  * mwhudson points spiv at his build engineer hat
[06:07] <mwhudson> spiv: but yes
[06:07] <spiv> mwhudson: that would be a hard hat, I suppose.
[06:07] <mwhudson> spiv: it has special attachments to collect the tears of blood
[06:14] <spiv> mwhudson: would it be excessively rude to file it with Critical priority?
[06:15] <thumper> spiv: yes
[06:15] <thumper> spiv: high is fine
[06:16] <spiv> thumper: So "high" would merely be rude, rather than excessively so? ;)
[06:16] <thumper> :)
[06:16] <spiv> thumper: #424136
[06:16] <thumper> spiv: do you know how to fix this?
[06:17] <thumper> spiv: because to speed it up we could get some branches copied to staging, and try it there
[06:17] <spiv> thumper: yes; see the conversation I just had with mwhudson or the bug description
[06:17] <thumper> spiv: feel free to provide a branch that fixes it :)
[06:17] <thumper> spiv: and I'll support the criticality of it
[06:42] <MTeck> thumper: it doesn't look like the import finished correctly
[06:42] <MTeck> it ran 3hr 20min
[06:42] <MTeck> http://launchpadlibrarian.net/31298189/coreutils-ddhash-log.txt
[06:46] <MTeck> gah - how do you guys pick server names :S
[06:50] <spm> depends on how vindictive the dce is feeling when it comes time to name them
[06:50] <MTeck> dce?
[06:50] <spm> data centre engineer
[06:51] <MTeck> galapagos isn't so bad - but neumayer and russkaya ....
[06:51] <MTeck> way over my head
[06:51] <MTeck> some of the others are just way out there too :P
[06:51] <spm> mind you... we typically use ssh cmd completion so it's no such a big deal ;-)
[06:52] <spm> praseodymium aka prasé
[06:52] <MTeck> ?
[06:52] <MTeck> I've tried learning other languages - never could
[06:52] <spiv> spm: so the acute on that é is the notation for where to use TAB completion? ;)
[06:52] <spm> is one of the ... controller servers fwiw.
[06:52] <MTeck> 2 years and all I have is , mas cervas por favor
[06:53] <MTeck> adn puedo ir al bano
[06:53] <spm> spiv: nah, was james having a troll at mwhudson and myself when we started shortning praseodymium to prase. he felt it had earnt the é :-)
[06:53] <mwhudson> MTeck: all the importd slaves are named after antartic research stations
[06:53] <MTeck> oh
[06:53] <mwhudson> fwiw
[06:54] <MTeck> I'd name them like importslave01
[06:54] <spm> MTeck: I didn't know you were studying accountancy at Uni? ;-)
[06:54] <MTeck> hm?
[06:55] <spm> call it the zen of sysadmin. always give servers real names. not numerical ones. they tend to be... cared for??? better.
[06:55] <MTeck> I've been studying accounting - failed two classes so far
[06:55] <spm> MTeck: my meaning being that only accounting/managerial types tend to want "professional server names".
[06:55] <MTeck> I wouldn't really name them like that - I do like simple names though
[06:56] <MTeck> like carpo, sermo, inferno, etc
[06:57] <MTeck> oh - yes, I do likey the latin spins
[06:57] <spm> having real names has the advantage that the servers are... distinct. You dont get gobbledegook like CBTG01FP07
[06:57] <MTeck> you mean like what happens in windows? :P
[06:57] <spm> no comment
[06:58] <spm> :-)
[06:58] <ojwb> C3P0 and R2D2?
[06:58] <MTeck> every server name I get has some light spin from this - http://www.math.ubc.ca/~cass/frivs/latin/latin-dict-full.html
[06:58] <spm> heh. nice!
[06:58] <spm> minerals was one prior favourite
[06:59] <MTeck> I'm just thinking - if I had a honeypot system, what would I call it
[06:59] <spm> I did laugh at how the Centre for Information Technology Research named all their machines after fruit. CITR == citrus == fruit.
[06:59] <spm> winnie
[07:00] <MTeck> corip is what I would name a honeypot system
[07:00] <MTeck> corripio :  to seize, snatch up, steal, (of a disease) attack
[07:02] <MTeck> I just like short easy to pronounce names :P
[07:03] <MTeck> spm: that's interesting
[07:08] <jml> MTeck, prase is a terrible name :)
[08:21] <dreamcat4> hi all
[08:21] <dreamcat4> launchpad/code: registering a new branch
[08:22] <dreamcat4> what's the difference between 'hosted' and 'mirrored' choice?
[08:22] <radix> mirrored means that launchpad will pull the code from somewhere else
[08:23] <radix> hosted means you will push the code with bzr directly to launchpad
[08:23] <dreamcat4> does it have to be another bzr repository or can it be github ?
[08:23] <radix> if you want to host code directly on launchpad, you don't actually have to "register a branch", you just need to push to lp:~<user-or-team>/<project-name>/<branch-name>
[08:23] <jml> dreamcat4, if you want, you can import a branch from github.
[08:24] <dreamcat4> radix, that's pretty cool
[08:24] <dreamcat4> okay looks like i should go the hosted route
[08:24] <dreamcat4> thanks all
[08:25] <dreamcat4> actually... i have written up a page about bzr-git importing
[08:25] <dreamcat4> http://dreamcat4.jottit.com/working_together_-_git_and_bzr
[08:25] <dreamcat4> you are welcome to put it in the ubuntu wiki
[08:39] <uwesch> Hi
[08:40] <uwesch> I#ve a question about projects and translations
[08:40] <uwesch> someone here who can answer?
[08:41] <dpm> uwesch: please post the question first :-)
[08:42] <uwesch> dpm: okay ;)
[08:43] <uwesch> I am a translator in the inkscape project https://bugs.launchpad.net/inkscape
[08:43] <uwesch> there is a button "Translatins" but there is nothing inside
[08:44] <uwesch> i would like to use this for my translations
[08:44] <uwesch> Who can help here?
[08:46] <dpm> uwesch: I seem to remember that inkscape does not use Launchpad for translations. They only use it for bugs. Let me check...
[08:46] <uwesch> i know
[08:47] <uwesch> and i don't know how other translation teams work together
[08:47] <uwesch> I'm in the German Team and i would like to use launchpad for translation issues
[08:47] <dpm> oh, I understand your question now...
[08:48] <dpm> well there would be 2 options, if I'm not mistaken:
[08:50] <uwesch> okay?
[08:50] <henninge> uwesch:  https://help.launchpad.net/Translations/
[08:50] <henninge> uwesch: https://help.launchpad.net/Translations/YourProject
[08:51] <dpm> 1) Only inkscape upstream can decide on this, so you could contact them and convince them to use Launchpad for translations
[08:51] <uwesch> henninge: thx
[08:52] <dpm> henninge: he's not upstream, though. He's a translator and would like to use LP for inkscape translations (which are not currently in LP)
[08:52] <dpm> uwesch: you can point upstream to the links henninge showed you
[08:54] <uwesch> okay, thank you
[08:58] <dpm> uwesch: or 2) you (or upstream) can create a translation group (https://translations.edge.launchpad.net/+groups/) for inkscape and have it translatable in LP only for those teams who wish to use LP (see Gnucash as an example -> https://translations.edge.launchpad.net/gnucash). I've never done this myself, so I cannot help you much with the details, but danilo, henninge or jtv might be able to assist you if you'd like to go down that route
[09:00] <henninge> dpm: ah, ok. I did that out of reflex .... ;)
[09:01] <dpm> :-)
[09:08] <uwesch> thanks a lot
[09:09] <philn> hi
[09:10] <dpm> uwesch: and one last note: for 1) getting upstream's translations into Launchpad would be as easy as mirroring upstream's SVN repo from http://inkscape.svn.sourceforge.net/viewvc/inkscape/ in a bzr branch in LP and importing their translations. And with the new "commit translations to branches" feature, they could even set up a bzr branch where translations can be committed to automatically and they can then import them to their SVN
[09:10] <dpm> But upstream would have to decide on that
[09:11] <philn> i need to delete a team... :/ and send every current member a message, there's no mailing list configured for the team... can someone help me please?
[09:11] <uwesch> dpm: I've to talk to the maintainers of the inkscape project ;)
[09:12] <dpm> uwesch: sure, I just wanted to let you know the options :)
[09:12] <wgrant> philn: Only an admin can delete a team, but you can easily email all the members if you're a member.
[09:12] <wgrant> philn: https://launchpad.net/~someteam/+contactuser
[09:13] <philn> i am admin
[09:13] <wgrant> philn: A Launchpad administrator, sorry.
[09:13] <philn> ok
[09:13] <wgrant> philn: You can ask somebody to deactivate the team for you at https://answers.launchpad.net/launchpad/+addquestion
[09:14] <philn> ok
[09:14] <philn> i'll first send the goodbye message
[09:19] <henninge> uwesch: I looked at the inkscape translations
[09:19] <henninge> uwesch: it looks like it would be pretty easy to start using Launchpad Translations.
[09:19] <uwesch> henninge: really?
[09:20] <henninge> uwesch: They already generate a template file
[09:20] <henninge> uwesch: inkscape.pot in http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/po/
[09:20] <philn> i'm trying to log in to the wiki... but the connection page keeps loading, endlessly
[09:20] <uwesch> okay. so what would be the next steps?
[09:21] <henninge> uwesch: to setup code imports into Launchpad from that svn repository
[09:21] <henninge> uwesch: and then activate translation import from bzr
[09:21] <uwesch> bzr?
[09:21] <henninge> uwesch: bazaar
[09:22] <henninge> ubottu: http://www.bazaar-vcs.org/
[09:22] <henninge> uwesch: ^
[09:22] <henninge> ;)
[09:23] <henninge> uwesch: when the svn repository is imported into Launchpad it is converted to bzr.
[09:23] <henninge> a bazaar repository, I mean.
[09:23] <henninge> uwesch: and Launchpad Translations can import directly from there.
[09:23] <henninge> uwesch: BUT
[09:24] <uwesch> never heared about a bazaar repository
[09:25] <henninge> uwesch: to use the translations made in Launchpad, they will have to be exported again and then merged into inkscapes svn repository.
[09:25] <henninge> uwesch: yeah, we were discussing that problem on the mailing list .... ;-)
[09:25] <henninge> uwesch: I mean, that not enough people even know a about Bazaar.
[09:26] <henninge> uwesch: Bazaar is a great alternative to subversion.
[09:26] <henninge> uwesch: it is a distributed version control system, not centralized like subversion is.
[09:27] <henninge> uwesch: anyway, I am sure the inkscape people do know about it since they seem to have been working with Launchpad for longer.
[09:27] <henninge> uwesch: You might hear a common prejudice (Voruteil) concerning Launchpad Translations
[09:28] <henninge> uwesch: Vorurteil
[09:28] <henninge> meine Güte
[09:28] <henninge> predjudice
[09:28] <henninge> pardon my spelling, English and German ;)
[09:28] <uwesch> wir können auch deutsch reden ;)
[09:37] <henninge> uwesch: The predjudice is that Translations in  Launchpad are bad because anybody can add translations.
[09:37] <henninge> uwesch: that is OLD and has been fixed a long time ago.
[09:37] <uwesch> okay, that make sense
[09:38] <uwesch> i should really takl to the maintainers of the inkscape project
[09:38] <henninge> uwesch: Launchpad Translations has mechanisms in place to let anybody make *suggestions* which are then approved by the core translators.
[09:39] <henninge> uwesch: yes, you should. Maybe there are other translations teams for incscape that would like to use Launchpad, too.
[09:39] <henninge> uwesch: raise it on the mailing list
[09:39] <henninge> I assume there is one ;-)
[09:39] <uwesch> henninge: that's a very good idea, thank you
[09:40] <henninge> uwesch: my pleasure
[10:42] <SiDi> Hi people
[10:43] <SiDi> Is the server hosting bazaar's web interface down ? I can't browse revisions at the moment
[10:43] <Kamping_Kaiser> Hi all. Does LP provide read-only mirrors of bzr branches, or are all branches on LP read-write?
[10:47] <intellectronica> Kamping_Kaiser: they're all read/write, but only by the user the branch belongs to
[10:48] <intellectronica> Kamping_Kaiser: so, ~intellectronica/launchpad/my-branch is read/write to me, but read-only to you
[10:48] <intellectronica> Kamping_Kaiser: and ~kamping_kaiser/yourproject/yourbranch is read/write to you but read-only to me
[10:49] <intellectronica> Kamping_Kaiser: you can use teams to make a branch that is read/write for more than one user, but the usual model is that another user should branch and then offer the changes for merging, rather than modify trunk directly
[10:50] <Kamping_Kaiser> intellectronica: thanks for that. it all sounds sane enough. :)
[11:01] <bac> Hello Launchpad.  I'm the help contact today.  Please contact me with your questions.
[12:16] <Kmos> hi
[12:16] <Kmos> why 'ubuntu' as project in not valid in Also affects project ?
[12:16] <wgrant> Kmos: It's a distribution, not a project.
[12:19] <Kmos> ah ok.. how could I assign a bug to the team who takes care of ubuntu launchpad page? bug 421078
[12:19] <Kmos> or subscribe
[12:20] <Kmos> I'm not sure if ubuntu drivers are acorrect
[12:23] <lfaraone> Kmos: you'd want to file that against Soyuz.
[12:23] <wgrant> lfaraone: No, Soyuz is not relevant here.
[12:23] <intellectronica> lfaraone, KmosL actually, that has nothing to do with soyu
[12:23] <lfaraone> wgrant: sorry, I mean malone.
[12:24] <Kmos> lfaraone: you can't add apport-collect to every project in launchpad
[12:24] <lfaraone> Kmos: but it'd need to be modified in malone.
[12:24] <wgrant> lfaraone is right.
[12:24] <intellectronica> Kmos: next week, we're going to disable bug filing via the web interface, and point users to a wiki page with clear instructions on how to use these tools. i think that pretty much covers what you're asking for?
[12:24] <Kmos> lfaraone: see my comment in the bug report, that can be avoided
[12:25] <wgrant> intellectronica: This is from within within existing bugs.
[12:25] <Kmos> intellectronica: sure
[12:25] <Kmos> if you add some extra text about existing bugs
[12:25] <lfaraone> Kmos: I think intellectronica is kidding.
[12:25] <intellectronica> lfaraone: i am very serious, actually
[12:25] <lfaraone> intellectronica: Oh? Hm.
[12:26] <intellectronica> wgrant: i don't understand, is the suggestion that we display information on how to add more information using apport-collect on bug pages for existing bugs?
[12:26] <wgrant> intellectronica: Precisely.
[12:26] <lfaraone> intellectronica: Yes.
[12:26] <intellectronica> hmmm ... that's an interesting idea
[12:26] <lfaraone> intellectronica: or better yet, add something akin to "apt:" which calls on apport from a browser.
[12:27] <intellectronica> well, file the bug on malone, we'll have to think if that's really something we want to do, but it's not a bad idea
[12:27] <lfaraone> intellectronica: that'd be harder, but prolly a good project for next year's GSoC
[12:27] <Kmos> ok
[12:27] <lfaraone> Kmos: I added malone to the bug.
[12:27] <intellectronica> we write code all year round. lfaraone, if you want to jump in and contribute a patch i'll be happy to help
[12:28] <intellectronica> but let's wait a bit until we're sure we actually want this feature and how it's going to be designed
[12:28] <lfaraone> intellectronica: if I had 5usd for each time I said "hey, that'd be a cool project to do when I'm free", I wouldn't have to worry about paying for college :)
[12:28] <intellectronica> lfaraone, Kmos: thanks
[12:28] <Kmos> lfaraone: I saw it now =) thanks
[12:28] <Kmos> np
[12:28] <lfaraone> Kmos: glad to help, sorry for the initial misdirection.
[12:29] <Kmos> I think we need it to be enabled only in some distributions. (x)ubuntu
[12:29] <lfaraone> Kmos: that'd be the easy part :)
[12:29] <Kmos> hehe
[12:29] <intellectronica> lfaraone: oh, you don't get five bucks whenever you have a good idea? here in europe we do. it's part of the comprehensive health care system ;)
[12:30] <lfaraone> intellectronica: yeah, but you end up paying 4.99$ of it back due to VAT ;)
[12:30] <intellectronica> :)
[12:31] <Kmos> loll
[12:37] <bigjools> lfaraone: you can edit the target of a bugtask instead of creating a new one, FYI
[12:37] <bigjools> soyuz is going to get bugmail now :(
[12:38] <bigjools> until deryck fixes that ;)
[12:39] <wgrant> This is why we have the null project.
[12:41] <lfaraone> bigjools: well, I marked it as invalid.
[12:41] <bigjools> lfaraone: I saw - but unfortunately it will still get bug mail :(
[12:41] <lfaraone> bigjools: that's silly.
[12:41] <bigjools> yep
[12:53] <sav> um.. is there anything wrong the doubah machine?
[12:54] <sav> (ppa) https://answers.edge.launchpad.net/launchpad/+question/81881
[12:55] <wgrant> sav: That's impressive, but nothing to do with that particular builder.
[12:55] <wgrant> Oh.
[12:55] <sav> erm..
[12:56] <sav> * Builder: https://launchpad.net/builders/doubah  * Source: not available
[12:56] <wgrant> That's probably the buildd-manager race thing again.
[12:56] <wgrant> bigjools: ^^
[12:57] <wgrant> sav: So, everything is OK, except the build status. The binaries are built and published.
[12:58] <sav> thanks for helping! :)
[12:58] <sav> wgrant: I just noticed that https://launchpad.net/builders/doubah says the builder deactivated. Should I just rebuild it?
[12:58] <bigjools> wgrant: remind me what that was again?
[13:00] <wgrant> bigjools: buildd-manager sometimes races with itself and dispatches a successful build a second time.
[13:00] <bigjools> ah the double build
[13:00] <bigjools> yeah
[13:00] <bigjools> thought that was fixed.
[13:00] <wgrant> sav: No need. It's all fine now, but will fail the same way if you retry.
[13:00] <bigjools> hm
[13:00] <wgrant> Maybe get cprov to beat that build over the head when he wakes up.
[13:00] <wgrant> (ie. fix the status up)
[13:01] <wgrant> bigjools: So did I.
[13:02] <sav> wgrant: ok, thanks, I'll just leave it there, I have to get the next package ready. I won't touch it for the next 3-4 days (or even more heh)
[13:03] <wgrant> sav: The only problem you'll see is the red X on your PPA page. Everything else is fine.
[13:03] <sav> ooohh alrighty then :)
[15:06] <cumulus007> Hi, I'm trying to set up my own PPA. I want to have daily builds of Digikam in my PPA. I'm wondering how to upload the source code to my PPA. I can only upload .changes files
[15:06] <bigjools> cumulus007: https://help.launchpad.net/Packaging/PPA/Uploading
[15:06] <cumulus007> I read that, but that doesn't help me. It says I can only upload .changes files
[15:07] <bigjools> no it doesn't :)
[15:07] <bigjools> "Dput uploads the following files: "
[15:07] <cumulus007> yes I see, but can it upload source code in a tar.gz archive?
[15:07] <bigjools> cumulus007: no, source packages don't work like that
[15:08] <cumulus007> hm okay, I'll read https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage then
[15:08] <bigjools> you need to read about debian packaging
[15:08] <bigjools> great
[15:08] <bigjools> cumulus007: let me know how you get on
[15:08] <cumulus007> sure :)
[15:12] <MTeck> I wonder if vcs will ever finish importing this package :(
[15:21] <c0rtis0n> Hey, when I want to upload a patch to launchpad which files are needed?
[15:21] <MTeck> c0rtis0n: #launchpad-dev can help you better
[15:21] <c0rtis0n> thx
[15:23] <cumulus007> bigjools: debian packaging is complicated :|
[15:23] <c0rtis0n> Öhm sry but i thought -dev is for Launchpad-development only? What i ment were that i want to patch a bug wich is reported at launchpad
[15:23] <bigjools> yep :/
[15:23] <lvh> hi!
[15:27] <MTeck> c0rtis0n: bug number?
[15:30] <c0rtis0n> MTeck Bug #158784 (I'am tkranz there...)
[15:32] <MTeck> c0rtis0n: oh - Click "Add an attachment", add a comment, pick your patch file, then click the check box "This attachment is a patch"
[15:34] <c0rtis0n> I just don't know what the patch file is exactly... the diff.gz, the .dsc file, both or ist just the .fix file needed
[15:34] <MTeck> combine them into a tarball
[15:35] <c0rtis0n> ok thank you very mcuh
[15:36] <MTeck> All they probably need is the diff.gz - but you may as well give them the whole thing
[15:38] <c0rtis0n> I've uploaded the tarball now. Thx again.
[15:52] <cumulus007> bigjools: I don't understand how to make a source package. I downloaded the latest revision of the digikam trunk and what should I do next? according to the ubuntu Wiki, I should download a pre-made debian source package but of course that isn't available for digikam trunk
[15:52] <bigjools> cumulus007: have you looked to see if someone has already built a package?
[15:52] <cumulus007> well I don't think so because it's trunk
[15:53] <bigjools> I suggest you start with an existing package
[15:53] <bigjools> and update it
[15:54] <cumulus007> that's a good idea
[15:54] <bigjools> then amend debian/control to change the version to something more appropriate for your PPA
[15:54] <MTeck> Mez: So... how've you been?
[15:54] <cumulus007> where can I find source packages? Do I have to enable the "source code" checkbox in Software Sources?
[15:54] <bigjools> cumulus007: yes
[15:54] <cumulus007> Okay  :)
[15:58] <cumulus007> bigjools: I enabled it, reloaded my package lists but there is still can't find a digikam source package
[16:00] <bigjools> cumulus007: apt-get source digikam
[16:03] <cumulus007> bigjools: lol forgot about that, it's downloading :)
[16:05] <cumulus007> bigjools: done. All I have to do now is to package the trunk into a tar.gz archive and rename it to a orig.tar.gz file?
[16:06] <bigjools> something like that, but check the package.  your best bet now is to ask in #ubuntu-motu for more packaging advice
[16:07] <cumulus007> Okay, thanks for the help :)
[17:19] <MTeck> You guys think this will ever finish? https://code.edge.launchpad.net/~vcs-imports/coreutils/ddhash
[17:30] <emma>  henninge, jtv, Ursinha, danilos hi!
[17:30] <Ursinha> hi emma :)
[17:30] <emma> :)
[17:32] <danilos> heya emma :)
[17:32] <emma> Hehe :)
[17:44] <MTeck> Ursinha: You know anything about vcs-import?
[17:44] <Ursinha> MTeck, what exactly?
[17:44] <Ursinha> (hi, btw :))
[17:44] <MTeck> hi :), how've you been?
[17:44] <MTeck> Ursinha: thsi keeps failing - https://code.edge.launchpad.net/~vcs-imports/coreutils/ddhash
[17:45] <Ursinha> MTeck, let me see the cause
[17:46] <Ursinha> hmm
[17:46] <Ursinha> rockstar, hi :)
[17:46] <rockstar> Ursinha, hello.
[17:47] <Ursinha> rockstar, I'm looking for a bug for this: http://launchpadlibrarian.net/31314543/coreutils-ddhash-log.txt and decided to ask you about it
[17:49] <rockstar> Ursinha, I don't think there's a bug for that, but I'm willing to bet it's actually a bug in bzr-git.  Maybe search there.
[17:49] <Ursinha> rockstar, I just found bug 419478
[17:49] <Ursinha> that mentions bug 402814
[17:50] <MTeck> I think I need to take off pretty soon
[17:50] <Ursinha> MTeck, I'd suggest you to subscribe yourself to bug 419478
[17:51] <MTeck> ok, I will
[17:51] <MTeck> Thanks
[17:57] <rockstar> Ursinha, is jelmer subscribed to those bugs as well?
[17:57] <Ursinha> rockstar, don't know
[17:58] <rockstar> Ursinha, bugs in git importing probably need to be seen by him.
[17:59] <Ursinha> rockstar, in the bzr-git he might be indirectly, he made comments in that bug
[18:00] <Ursinha> in the bug 419478 don't think so
[18:00] <Ursinha> rockstar, hm, it seems he's on both
[18:01] <rockstar> Okay, great.  Just so that he knows.
[18:03] <Ursinha> rockstar, but it seems he marked the bug as incomplete
[18:25] <bac> sinzui: did you intend that OEM call to be 11 hours long?  i may have to decline.
[18:26] <sinzui> bac: there should also be an email sent 30 seconds later that shows it may be 45 minutes long
[19:19] <james_w> how do I get to the source code of a branch from the branch page now?
[19:40] <AlexC_> g'morning
[19:40] <AlexC_> wondering if it would be possible to get someone to review these files: https://translations.launchpad.net/tangocms/trunk/+imports?field.filter_status=all&field.filter_extension=pot
[19:48] <bac> hi AlexC_, unfortunately the translations team is finished for the day.
[19:49] <AlexC_> oh man
[19:50] <AlexC_> well thanks anyway, guess I'll have to wait another few days for automatic translations to import so I can do what I wanted to do days ago :P
[22:00] <ohmy> hello
[22:04] <ohmy> I would like to have your feeding, is the actual version of launchpad suitable to run on production environement ? i mean, i would like to host an application using a local instance of lanchpad. I have just installed it on a fresh jaunty server and have seen some warnings about some features to disable in production
[22:05] <ohmy> one more question please, i'm stuck at this step https://dev.launchpad.net/Running/RemoteAccess
[22:09] <ohmy> In fact my /etc/apache2/ports.conf is very light, it only contains NameVirtualHost *:80  and Listen 80 (it referes to /etc/apache2/sites-enabled/000-default)
[22:09] <wgrant> ohmy: The code you have is the exact code that runs on launchpad.net. So yes, it is production ready. HOWEVER
[22:09] <wgrant> I point you to the third paragraph on https://dev.launchpad.net/Getting
[22:10] <wgrant> And I also wonder why you want to run your own.
[22:11] <ohmy> wgrant, Simply because we have a very large LAN network and no internet access (trust me !)
[22:11] <ohmy> wgrant, thank you for the answers
[22:12] <wgrant> ohmy: So, you can't run your own production Launchpad instance without a lot of work to replace the images and branding.
[22:12] <ohmy> wgrant, i believe this is the easiest part of the work
[22:14] <ohmy> wgrant, for the moment i'm stuck with "seeing is believing", i mean with https://dev.launchpad.net/Running/RemoteAccess step :)
[22:27] <ohmy> i don't know why but i can"t access my server from an LAN machine, it always redirect me to the default apache "It works!", any one have an idea please ?
[22:28] <maxb> You have looked at how many images there are, right? I actually made a list of them all, because I'd like to have a private instance too, but when I did I discovered that the magnitude of a project to replace them all would be HUGE
[22:31] <maxb> Also, I am the author of the RemoteAccess page in its current form, so I can assure you that it does work, though it assumes you're confident with understanding Apache vhosts
[22:34] <ohmy> maxb, of course, i've never doupt it works i'm just trying to figure what did i miss since all the work was done by a proven rocketfuel-setup script
[22:35] <ohmy> maxb, when you mentinned "Change all <VirtualHost 127.0.0.88:80> lines to <VirtualHost *:80>" i have already this ligne podified in the port.config
[22:35] <ohmy> maxb, without any change from myside
[22:39] <ohmy> sorry, i meant i have no occurence of 127.0.0.88:80 everything is already set to *:80 (sorry for the my mistake)
[22:41] <maxb> Have you not seen the /etc/apache2/sites-available/local-launchpad file?
[23:02] <moldy> hi
[23:03] <moldy> a small suggestion: it would be nice to add this: https://answers.launchpad.net/soyuz/+question/59047 to https://help.launchpad.net/Packaging/UploadErrors
[23:07] <maxb> It is a wiki, remember :-)
[23:17] <ohmy> Hello again
[23:17] <ohmy> I have just switched to my old launchpad install witch is ok
[23:18] <ohmy> could you please tell me how to add new admin and to remove the username: admin@canonical.com
[23:19] <moldy> maxb: indeed, i did not quite realize this yet :)
[23:23] <maxb> ohmy: Removing users is impossible without messing with raw SQL
[23:23] <maxb> which is likely to be severely difficult
[23:24] <ohmy> maxb, indeed