[15:40] <CarstenG> Hi at all.
[15:41] <CarstenG> I just got an update of the Ubuntu Desktop Guide to my raring installation.
[15:42] <CarstenG> And I see, that there are some screenshots on the main page are still not updated to the raring layout.
[15:44] <CarstenG> E.g. if I hoover over the main captions »What's new in Ubuntu 13.04?«, »Use the Launcher to start applications« and »Find apps, files, music, and mor with the Dash«, I see old screenshots.
[15:45] <CarstenG> Is there a possibility to update these images before release?
[15:45] <CarstenG> Or is it now to late?
[16:08] <bkerensa> CarstenG: Its too late plus the screenshoot tool is not working very well
[17:51] <CarstenG> bkerensa: Thanks for your answer. ok, it's to late, but will the screenshots update during normal updates during the life of raring?
[17:52] <bkerensa> CarstenG: I defer to jbicha
[17:52] <bkerensa> :P
[17:52] <bkerensa> I do not know how to use the script but if its not working then idk
[17:52] <jbicha> I defer to bkerensa ;)
[17:52] <CarstenG> And what do you mean with »screenshot tool«? Is there a special program for the docs?
[17:53] <jbicha> it's possible to do an update after raring is released but it requires coordinating the schedule with dpm & the translators
[17:55] <bkerensa> Well I defer to pleia2 since her team owns doc committers now ;)
[17:55] <bkerensa> ;p
[17:55]  * bkerensa runs and hides
[17:55] <pleia2> that's only as a temporary measure to make sure we don't lose control of the team entirely, we're not actually qualified to make major decisions on behalf of the team ;)
[17:56] <pleia2> CarstenG: yes, there is a specific tool that makes taking them easier
[17:56] <pleia2> (I don't remember it offhand)
[17:58] <CarstenG> pleia2: Sounds good. In the manual team we also have to to lots of screenshot, so maybe we can use this for our purposes, too?
[17:58] <pleia2> it may actually be the same one, bkerensa?
[17:58] <jbicha> it's a script called collect-screenshots.sh in the root of lp:ubuntu-docs
[17:58] <pleia2> ah, thanks jbicha
[17:58] <jbicha> it's different that what the manual team used
[18:00] <CarstenG> thanks Jeremy. I will have a look to it.
[18:05] <jbicha> it didn't work quite right for quantal and it's like that the placement of the screenshots is off by a bit as developers tweak the UI
[18:05] <jbicha> *it's likely*
[18:06] <CarstenG> Jeremy, do you mean Quickshot, which the manual team used in the past?
[18:09] <jbicha> quickshot didn't seem to work right for what I needed but I don't remember why
[18:09] <CarstenG> Well, this is not working any more. There is no developer... Now we are doing the screenshots by hand...
[18:10] <jbicha> I guess that's what the problem was
[20:57] <CarstenG> Thanks for your help. See you later, good night.


[00:34] <lee> hello
[07:39] <rex_> drone
[07:40] <rex_> chanserver
[07:40] <rex_> crowbar
[07:40] <rex_> c_89[m]
[07:40] <rex_> download xfreerdp
[07:41] <rex_> join #rex
[08:52] <sk> Hello
[08:52] <sk> good day people
[09:40] <porquilho> i love xubuntu
[09:58] <diogenes_Vx15> porquilho, and you are not alone :)
[09:59]  * diogenes_Vx15 Michael Jackson - i am here with you :)
[09:59] <porquilho> diogenes_Vx15: the only problems it gave me is just because im overused the sudo command
[09:59] <porquilho> not knowing what i was doing
[10:01] <diogenes_Vx15> porquilho, sudo has nothing to do with any particular distro, it's a common command for all the distros. But nowadays i can see a shift towards doas instead of sudo.
[11:06] <porquilho> diogenes_Vx15: i mean that i gave the problems to myself
[11:06] <porquilho> because i didnt know what i was doing
[11:07] <porquilho> and using the sudo command
[11:07] <diogenes_Vx15> porquilho, that's how people aquire experience.
[11:07] <porquilho> yes
[16:09] <chas> hi
[16:19] <gnrp> I am tihnking of making a manual night/day switch for my xubuntu computers. Do you know by chance if there is a possbility to switch the xfce4-term color scheme from a script?
[18:10] <cesar> Hi there
[20:56] <porquilho> https://0x0.st/HbyR.jpg
[22:05] <Guest3979> hi


[08:21] <wilee-nilee> holstein, are you on?
[08:26] <fotoport-1> на русском можно задавать вопросы?
[08:26] <smartboyhw> !ru | fotoport-1
[08:30] <fotoport-1> hello
[08:30] <cfhowlett> fotoport-1, greetings
[08:36] <fotoport-1> мне нужна помощь
[08:36] <cfhowlett> !ru
[08:38] <fotoport-1> I have two printers do not print together
[08:38] <cfhowlett> !details|fotoport-1,
[08:46] <fotoport-1> on all versions starting with 11, two and a printer attached to one computer do not print. Printing stops when you send a job to the second printer. Printers epson T50
[08:47] <cfhowlett> fotoport-1, versions?  11.10 and 11.04 are BOTH end-of-life ...
[08:47] <cfhowlett> fotoport-1, lsb_release -a    in a terminal ... what ubuntu are you running?
[08:50] <fotoport-1> I put ubuntu 11.04 11.10  12.04 Ubuntu Saucy Salamander 13.10
[08:51] <cfhowlett> fotoport-1, 13.10 saucy is still in beta ... 12.04 should work.  did you add the printer to the system settings?
[08:57] <fotoport-1>  yesterday tried to run on 12.04  /etc/modprobe.d/modprobe.conf     blacklist usblp
[08:57] <fotoport-1> did not work and divided into groups
[09:00] <cfhowlett> fotoport-1, bring this question to #ubuntu ... more people available to help
[09:30] <fotoport-1>  there is generally no one answers
[10:38] <mlpug> hello, I guess that when I play my midi file with fluidsynth it pans everything by default into middle. What is the simplest way to pan instruments individually?
[10:38] <mlpug> In DAWs this is straightforward to do but I have my own scripted system so I would like to just instruct fluidsynth (or other softsynth) to do the panning based on some extra instructions I give to it (e.g. channel 1: left, channel 2:right, channel 3:mid
[10:39] <cfhowlett> mlpug, ask in #opensourcemusicians if no one here knows
[10:40] <mlpug> cfhowlett, yes. that could be the place to go if needed.


[13:55] <hatch> good morning
[13:55] <frankban> hi hatch
[14:32] <hatch> so how was everyones weekend?
[14:33] <benji> bac: http://pastebin.com/0M4PiXZD
[14:34] <bac> hi hatch.  had a lovely long weekend.  hope yours was good
[14:36] <hatch> yeah it was really sunny here - which is a little odd for this time of year
[14:37] <hatch> today is looking like it's goign to be the same
[14:44] <hatch> the supply of Fire Emblem Awakening for 3DS is so bad people are charging a $25 premium online for it hah!
[14:52] <rick_h_> benji: howdy
[14:52] <benji> hi rick_h_; so, post-merge...
[14:52] <rick_h_> yea, qa'ing fun for all
[14:52] <benji> do you have a card on the kanban board?
[14:53] <rick_h_> hmm, on ours. I didn't add one to yours
[14:53] <benji> after a merge the app is updated on http://uistage.jujucharms.com:8080/ you can go there to QA your change
[14:54] <benji> rick_h_: that prbably makes sense; I ask because there is a UI/UX review slot on ours that tracks if there is something for the UI/UX guys to review
[14:54] <rick_h_> ok, and then once qa'd just mark the bug as fix released?
[14:54] <rick_h_> benji: ok, good to know.
[15:00] <benji> rick_h_: right
[15:07] <hatch> bcsaller_: 'charmstore' is the default namespace correct? if no namespace is defined it's the default?
[15:09] <bcsaller_> hatch: yes, thats passed in at init and set as default
[15:10] <hatch> alright I'm going to change that to be something more generic - I just didn't want to change it if I was understanding incorrectly
[15:12] <gary_poster> hatch, I converted your kanban card to a prototype card as we discussed
[15:13] <hatch> funny story I was watching a c# tutorial yesterday and the guy took a template and moved the opening curly brackets onto the new line....I cringed haha
[15:13] <gary_poster> hatch, and then I put the actual bugs as cards, to be moved through one at a time
[15:13] <hatch> gary_poster: sounds good! I'm fighting with edge cases right now :/
[15:13] <gary_poster> hatch, and they are all at the top of the board now
[15:14] <hatch> gotcha
[15:14] <gary_poster> cool hatch.  don't forget that, if you've proved the basic story in the prototype, you can just move on to the TDD approach.  OTOH, if you think these edge cases might affect the underlying design, go for it.
[15:14] <hatch> yeah unfortunately they do -  I woudln't feel right submitting it as is
[15:15] <hatch> sorry that's not entirely true
[15:15] <hatch> the one I'm finishing now does
[15:15] <hatch> then I can call it
[15:15] <gary_poster> cool
[15:15] <hatch> I have a postit note that says "split it up"
[15:15] <hatch> lol
[15:15] <gary_poster> :-)
[15:16] <gary_poster> Actually doing the full TDD thing would be even more fab
[15:20] <bac> benji: hangout died.  won't come back.  let's chat after call
[15:21] <benji> bac: k
[15:21] <bac> benji: entityName is a string
[15:21] <gary_poster> rick_h_, thanks again for the fix for bug 1111730.  We will be making a release today, hopefully.  we've been experimenting with moving bugs to "fix committed" and then we actually will mark them as "fix released" when we make the tarball.  That may just be too annoying, but fwiw that's where we are
[15:21] <_mup_> Bug #1111730: Unit count widget misplaced <ie10> <juju-gui:Fix Released> < https://launchpad.net/bugs/1111730 >
[15:21] <bac> f(a,b type) means both a and b are of the same type
[15:21] <benji> bac: I figured, I was just wondering why it isn't declared as such
[15:21] <bac> shortcut
[15:22] <rick_h_> gary_poster: ah ok. Yea we battle the same idea of 'released' with things as well.
[15:22] <gary_poster> cool
[15:22] <benji> bac: saving those 7 characters is a big win
[15:26] <hatch> OK fixed now to split this up
[15:27] <gary_poster> cool
[15:30] <gary_poster> jujugui call nowm oops
[15:48] <bac> benji: quick hangout?
[15:57] <benji> bac: I do make a mean BBQ potato
[15:58] <hatch> mmmmmm BBQ
[15:58] <hatch> mine has been covered with about 2ft of snow for too long
[15:58] <gary_poster> move someplace warmer :-P
[16:04] <jovan2> gary_poster et al - prototype is at https://drive.google.com/a/canonical.com/#folders/0B1IM--9A1RkTV3FQLVJtbjZvUGM
[16:04] <gary_poster> thank you jovan2 looking now
[16:11] <bcsaller_> Makyo: rapi is further along than suspected , it should just be an improv thing, and the key is 'env'
[16:17] <Makyo> bcsaller_, ah, awesome.
[16:20] <hatch> gary_poster: haha if anything i'd move somewhere with MORE snow :)
[16:20] <gary_poster> :-)
[16:29] <hatch> yikes lbox just rejected me because my indentation was wrong
[16:29] <hatch> note to self....check indentation
[16:30] <Makyo> hatch, make lint is what's catching that. make prep can help, too, if the beautifier can fix it.
[16:30] <hatch> it's also dumping on me because of an invalid jsdoc tag
[16:31] <hatch> I thought we used yuidoc?
[16:31] <Makyo> hatch, we do.  Wonder what that's about?
[16:31] <gary_poster> hatch, if you can turn off the option probably fine
[16:31] <hatch> will investimagate
[16:31] <gary_poster> (must be jshint)
[16:32] <Makyo> The only jshint tag we're using is bitwise operations, right?
[16:32] <gary_poster> dunno
[16:33] <hatch> *shudder* bitwise in js
[16:34] <Makyo> :/
[16:35] <hatch> you're a bitwise fan?
[16:37] <Makyo> I don't care too strongly either way, and the code that uses it isn't mine, but I do like tools that get the job done :)
[16:39] <hatch> hmm
[16:39] <hatch> virtualenv/bin/gjslint --strict --nojsdoc --jslint_error=all
[16:39] <hatch> but it's still flagging the jsdoc stuff
[16:41] <benji> hatch: do you mean yuidoc?
[16:43] <hatch> nope it's dumping on me because my indentation is off on a couple lines and because my documentation is not 'valid'
[16:44] <benji> hatch: if you pastebin the output I'll be glad to see if I can help
[16:45] <hatch> https://gist.github.com/anonymous/1e9e97bf336735ad288a
[16:46] <hatch> damnit I can't claim that gist
[16:49] <hatch> ohh we have the --strict tag
[16:49] <hatch> that's why it's failing
[16:50] <hatch> anyone have any objections to me removing that?
[16:50] <hatch> https://developers.google.com/closure/utilities/docs/linter_howto?hl=en search for --strict
[16:55] <benji> hatch: I'm pretty sure we actively want --strict; we've had it enabled for quite a while without it killing us, so I'm curious why it is causing problems now
[16:56] <hatch> well I'm using non jsdoc tags
[16:56] <hatch> they are valid yuidoc tags though
[16:56] <benji> if you push this to a branch that I can grab I will be glad to look at it
[16:56] <hatch> yup it's pushed
[16:56] <hatch> 1130787-subapp-app-extension
[16:57] <benji> I can construct one, but a full branch URL would be more helpful.
[16:57] <hatch> https://code.launchpad.net/~hatch/juju-gui/1130787-subapp-app-extension
[16:57] <hatch> :)
[16:59] <hatch> if we want to be able to use all of the yuidoc syntax flag we have to drop --strict
[16:59] <hatch> OR, I could just delete those flags and indent the things as it likes
[17:02] <benji> hatch: re. @public: just remove it; re. indentation: I think you know what to do there ;); re. Type should be immediately after @param tag: reverse the name and type ("{object} config" not "config {object}")
[17:03] <hatch> ♫ To the right, to the right, all of my tasks to the right to the right ♫
[17:03] <benji> re. "descriptions must end with valid punctuation such as a period.": do what it says :)
[17:03] <benji> heh
[17:03] <hatch> I can dooo eeet
[17:04] <benji> I actualy prefer it the way you have it, but it's not worth enguaging with the linter about it.
[17:04]  * hatch punches the linter for fun
[17:04] <hatch> you got it
[17:05]  * hatch grumbles and contemplates writing a blog post on how linters hinder innovation in hopes it gets picked up by Fox's hype machine
[17:12] <hatch> wow github support deleted that gist already...that was like 10m
[17:13] <benji> bac: I have a passing test!
[17:18] <hatch> O K jshint is a little nuts.... it won't let me use ++
[17:18] <hatch> lol
[17:20] <frankban> += 1 for jshint!
[17:21] <hatch> frankban: lol yup
[17:22] <hatch> although it's not allowing me to use fallthrough's on my switch statement
[17:23] <hatch> rofl it says file must use "use strict" then it says strings must use single quotes
[17:24] <bac> benji: yay
[17:26] <hatch> ahah /* falls through */ is a workaround
[17:28] <frankban> gary_poster: re bug 1130793, what do you think about including the new helpers (from the charm) in the same MP?
[17:28] <_mup_> Bug #1130793: For safety, Python charm-helpers juju-log command should insert a "--" before the log message. <Juju Charm Tools:New> < https://launchpad.net/bugs/1130793 >
[17:28] <hatch> *sigh* tests are failing
[17:29] <hatch> has anyone seen this error before?
[17:29] <hatch>   1) Application basics "before all" hook:
[17:29] <hatch>      TypeError: 'undefined' is not an object (evaluating 'c._buildCfg')
[17:32] <hatch> it's on test-prod not test-debug
[17:34] <benji> bac: it isn't my greatest work, but this seems sufficient for the moment: http://paste.ubuntu.com/5565315/
[17:35] <hatch> ohhh I didn't add the module to modules-prod
[17:35] <hatch> *the more you know*
[17:36] <hatch> hmm nope that shoudln't be it
[17:43] <hatch> whenever someone has a second I'd like some input on why this branch won't pass test-prod - I am almost 100% sure it's because it's not loading in the new extension https://code.launchpad.net/~hatch/juju-gui/1130787-subapp-app-extension
[17:43] <hatch> ^ jujugui
[17:44] <benji> hatch: I can look; let me run the tests real quick to be sure I am seeing the same thing
[17:44] <hatch> sure I'm running `make test-prod`
[17:45] <hatch> I swear I'll get all of these procedures down ;)
[17:45] <benji> arg, I have to reinstall mocha-phantomjs; one sec
[17:47] <bac> benji: i think it is fine.  it did find a a real bug.
[17:47] <bac> benji: how to proceed?  want me to merge it in and propose or do you want to?
[17:47] <benji> bac: have at it
[17:47] <bac> benji: ok, thanks
[17:47] <gary_poster> frankban, sorry don't know why I didn't see before.  Probably too late but +1
[17:48] <gary_poster> oh, I was not here that's why. :-P  gradual lunching is the order of the day
[17:49] <benji> it'd be really nice if the HACKING document was actually a literate shell script  or something that would just run all the commands... oh!  if we prefixed the commands with a command prompt, wwe could have a make target that pulled them out and ran them
[17:50] <hatch> I have to say I haven't used a makescript in YEARS until 2 weeks ago
[17:50] <hatch> :)
[17:51] <hatch> well at least directly
[17:51] <benji> you poor, poor deprived person; I'm glad we got to you when we did
[17:51] <frankban> gary_poster: not too late, thanks. We also have a gui branch implementing a log_hook context manager. we did that as a first attempt to workaround the juju-log gojuju problem. it could be worth proposing it anyway
[17:51] <gary_poster> fine by me frankban, yeah
[17:51] <hatch> benji: lol iunnoo.....if I write a node script I can run it on windows too ;)
[17:52] <hatch> well unless it relies on a unix tool
[17:52] <hatch> heh
[17:53] <benji> exactly!  good hygiene requires using tools that will never work on windows, therefore you needn't fear being forced to use it
[17:54] <benji> ok, hatch, I have reproduced the failure, looking quickly
[17:54] <hatch> lol
[17:54] <hatch> ok great
[17:54] <hatch> thanks
[17:55] <benji> hatch: I am seeing lots of merge conflict markers in the code, e.g., app/assets/javascripts/app-subapp-extension.js
[17:55] <bac> benji: just curious, did you deploy and hit with your ws client?
[17:55] <benji> bac: nope
[17:56] <bac> will do
[17:56] <hatch> benji: that's interesting because the files doesn't exist in trunk
[18:01] <benji> hatch: I figured out where the conflicts came from, it is because I had modified my branch of your branch when looking at your lint issues; I've fixed it and am now looking at the test failure
[18:01] <hatch> ahh ok
[18:03] <benji> hatch: if I apply this diff, all the tests pass: http://paste.ubuntu.com/5565397/
[18:04] <benji> I suspect that translates to "you did something wrong" ;P
[18:04] <benji> but at the moment I don't have anything more insiteful to say
[18:04] <hatch> lol - so if I make it so that it doesn't extend the extension then it works
[18:04] <benji> yep
[18:05] <hatch> i am pretty sure it has something to do with the module being loaded because test-debug passes just fine
[18:05] <benji> so... maybe you need to initialize the config earlier, or defer calling some of the subclass code that needs the config until later
[18:05] <hatch> the file is in assets/javascripts does that mean I need to include it manually in modules-prod?
[18:06] <benji> I don't know without looking at how those files are used.  That sounds like something good to investigate though.
[18:06] <benji> I'll check back after lunch and see if there is anything I can do to help.
[18:07] <hatch> yeah I think I'll go grab some lunch now then investigate
[18:08] <hatch> thanks for the help
[18:41] <hatch> and back
[18:50] <hatch> hmm
[18:54] <hatch> benji: I figured it out - I needed to add it to the 'merge-files' file
[18:55] <hatch> I should probably document that somewhere
[19:06] <benji> hatch: hmm, that doesn't sound right; the dependency should be picked up automatically
[19:06] <hatch> all of the modules under the assets dir are in there
[19:06] <hatch> so I'm assuming that's correct
[19:12] <benji> hatch: oh, I thought you were adding code that you had written, not third-party code
[19:13] <benji> wait, I think you are adding code you wrote, in that case, assets is not the best place for it
[19:15] <hatch> oh...darn I just proposed it
[19:15] <hatch> I put it in there because that's where I saw bcsaller_ put the new routing stuff
[19:16] <hatch> I could create another folder for extensions I suppose
[19:17] <benji> hatch: I suspect a location under "app" is most appropriate
[19:18] <hatch> alright I can fix that - can you comment that on the review?
[19:18] <gary_poster> hatch, if it is generic and potentially sharable then I don't think anyone can really complain that you put it in assets
[19:19] <gary_poster> sharable == usable by others
[19:19] <hatch> ok great - because yes it's very generic
[19:20] <hatch> wow that took way to long heh - at least now I know the processes :)
[19:21] <benji> we should consider an index of assets that catalogs things like where we got them from and what version they are, etc.
[19:21] <gary_poster> hatch if you are done with the prototype--you've gotten feedback from Ben and you like it and it works and stuff--then move it to "release: daily" on the board so other people can use your spot on the board please
[19:22] <hatch> ok but the prototype I'm not proposing though...correct?
[19:23] <gary_poster> hatch, right you are done with it
[19:23] <gary_poster> as far as the board is concerned
[19:24] <gary_poster> you won't work on it again--it's done.  yeah?
[19:24] <hatch> yep it's done
[19:24] <gary_poster> then it is as released as it ever will be :-)
[19:26] <hatch> great can you triage bug #1132943
[19:26] <_mup_> Bug #1132943: Create an app scaffold that others can use with Y.SubApp <juju-gui:New for hatch> < https://launchpad.net/bugs/1132943 >
[19:26] <hatch> I already created a task for it
[19:28] <benji> bac: what can I do to push our card forward?
[19:29] <bac> benji: i have it in review.  and i'm now trying to figure out how to get a single diff of the two pieces of work to annotate as a HOWTO.
[19:29] <gary_poster> hatch you have privileges to triage it, right?  If not, I'll change it so you do.  I am not the gate keeper, we (the team) are.  The bug is high importance, as you correctly triaged it.  This is demonstrable, because we have decided to work on it now, and that's what "high" means to us.  Since you triaged it, and you are on the team, it is triaged. :-)
[19:30] <bac> benji: so, i think getting this add-get-2 branch landed and doing the write up is all that needs to be done to finish the card.  you agree?
[19:30] <hatch> gary_poster: OHHH ok, it said that the gatekeeper had reviewed....I assumed that was you :D
[19:30] <gary_poster> hatch I went ahead and triaged it, but (a) does that make sense?  and (b) could you verify that you see the option to change the status
[19:30] <hatch> yes I have the ability to change it
[19:30] <gary_poster> hatch completely understandable.  ok excellent
[19:31] <benji> bac: yep, I agree
[19:32] <bac> benji: so...i'm not sure what there is to do collaboratively, except maybe review the draft of the doc once i get it.
[19:32] <gary_poster> there's room to statr another command card if that makes sense
[19:33] <gary_poster> start
[19:33] <hazmat> bcsaller_, merged re ls annotations, thanks
[19:33] <gary_poster> benji or you could do those design ones
[19:33] <gary_poster> bug 1125424
[19:33] <_mup_> Bug #1125424: Tweaks to loading messages and login visuals <juju-gui:Triaged> < https://launchpad.net/bugs/1125424 >
[19:34] <bcsaller_> hazmat: thanks :)
[19:35] <hatch> jujugui: could I get some reviews on https://codereview.appspot.com/7381055/ please so I can open up my spot on the board
[19:36] <bcsaller_> hatch: I'll take one
[19:36] <hatch> thanks sir
[19:36] <gary_poster> hatch, I'm working on it.  (your tags are supposed to show you if anyone claimed it)
[19:36] <hatch> ahhh I see now
[19:38] <gary_poster> hatch, I'm not sure how much we should care yet, but AFAICT your new js module does not show up in the docs (make view-docs)
[19:38] <bcsaller_> for some reason the diff on app/app.js is broken. wonder how that happened
[19:38] <gary_poster> hatch, if you don't think we should care then argue as such on Friday :-)  we talked about it before and we were/I was wishy washy about it
[19:39] <hatch> bcsaller_: actually all the diffs are broken
[19:39] <hatch> :/
[19:39] <hatch> gary_poster: nope I agree docs are important
[19:39] <bcsaller_> except the new module
[19:40] <gary_poster> hatch, verified that bcsaller_ is correct.  I was hoping that there are not in fact changes in those other files, but they do have changes in fact
[19:40] <gary_poster> in fact in fact
[19:41] <hatch> yeah single line changes
[19:41] <hatch> I can try re-propose?
[19:44] <bcsaller_> hatch: yeah, try that
[19:45] <hatch> ok it's on it's way
[19:45] <bcsaller_> Makyo: the new rapi-rollup should have basic annotations if you didn't see that already
[19:46] <Makyo> bcsaller_, thanks, just saw.
[19:48] <hatch> looks like the same issue wrt the diffs
[19:52] <gary_poster> It's correct in the MP :-/ dunno what's going on with rietveld
[19:53] <gary_poster> hatch, re bug 1132933, you are right that it should be documented.  That is only necessary for the "assets" bits
[19:53] <_mup_> Bug #1132933: document the merge-files file <juju-gui:New> < https://launchpad.net/bugs/1132933 >
[19:53] <gary_poster> I will comment to that effect
[19:56] <hatch> sounds good
[19:58] <hatch> ok the second branch that I did has the same diff bug
[19:58] <hatch> what the heck is going on there
[19:58] <benji> bac: let me know if there is anything I can do to further the cause.  In the meantime I will start a new card
[19:59] <gary_poster> hatch, at least as far as I am concerned, don't worry about it.  The other files have trivial changes I see in the MP
[19:59] <hatch> ok I'm just concerned that they result didn't have the actual changes
[19:59] <gary_poster> hatch, look at https://code.launchpad.net/~hatch/juju-gui/1130787-subapp-app-extension/+merge/150414
[20:00] <hatch> OH i know why
[20:00] <hatch> it's "related" to two branches
[20:00] <hatch> thats gota be it
[20:01] <gary_poster> hatch,it is?
[20:01] <gary_poster> don't see that
[20:01] <hatch> https://bugs.launchpad.net/juju-gui/+bug/1130790
[20:01] <_mup_> Bug #1130790: Create Y.SubApp by extending Y.App <juju-gui:Triaged by hatch> < https://launchpad.net/bugs/1130790 >
[20:01] <hatch> maybe....? :)
[20:01] <gary_poster> hatch, maybe that is confusing to lbox/rietveld.  shouldn't be.  isn't to the MP.
[20:02] <hatch> yeah oh well
[20:02] <gary_poster> hatch, lbox is something we can hack on
[20:03] <hatch> I don't think you want me anywhere near a makefile :P
[20:03] <gary_poster> not that I have
[20:23] <hatch> oh man I have too many active branches heh - I think I need folder color coding in sublime :D
[20:25] <hatch> bcsaller: sorry I forgot to add to my reply - that I agree that the parent app should be a bubble target but I haven't implemented that yet because I don't have a real world example of how that should work
[20:25] <hatch> rebubbling is very 'expensive' so the parent app could simply listen for those events
[20:26] <hatch> but it could also rebubble so its an internal event
[20:26] <hatch> both have advantages/disadvantages
[20:26] <hatch> once we have real code using this it's trivial to add one or the other
[20:27] <hatch> right now its 'listen to the sub event manually' option
[20:27] <hatch> feel free to disagre and tell me I'm stupid ;)
[20:35] <gary_poster> hatch I'm distracted but will be back to review in a sec.  my biggest comment will be "where are the tests" :-)
[20:36] <hatch> oh boy I completely forgot about those in the rush to get the code in
[20:37]  * hatch creates a test that returns true
[20:37] <gary_poster> :-)
[20:40] <hatch> darn I'm getting that 'watch 'error again
[20:43] <hatch> hmm
[20:44] <hatch> does anyone know of a way to see how many watches are being used?
[20:47] <hatch> ahah! Sublime Text also adds watchers in which I have a lot of files open
[21:03] <bac> benji: i've got a first draft of the doc but am now EOD.  would you want to run with it for the rest of your day or are you now in the middle of something else?
[21:05] <benji> bac: I'm in the middle of something, plus the fact that I'll only have an hour to work on it suggests that it would be best for me to not put my fingers in it
[21:05] <bac> benji: a-ok
[21:05] <bac> i forgot that you were faking EST and thought you had two more hours
[21:05] <bac> i'll pick it up tomorrow
[21:05] <bac> bye all
[21:07] <gary_poster> bye
[21:08] <hatch> cya
[21:09] <hatch> gary_poster: ok I spend the next couple hours learning mocha and writing tests for those two tasks that are blocking
[21:09] <hatch> if that's alright
[21:11] <gary_poster> hatch, blocking tasks?
[21:12] <hatch> well they are in the review section
[21:12] <hatch> but there is two of them
[21:12] <hatch> so they are blocking
[21:12] <gary_poster> ah!
[21:12] <hatch> mocha is looking pretty simple so it might not take 2h
[21:12] <gary_poster> I needed to refresh board
[21:12] <hatch> :)
[21:12] <gary_poster> hatch, heh, no yo ucan hack that together quickly :-)
[21:20] <gary_poster> hatch, I made a review finally of the older revision of your first branch
[21:24] <hatch> alright - looks like your comments are still very valid on the latest version - I'll try and get to them soon
[21:27] <gary_poster> cool thanks
[21:27] <gary_poster> hatch to reiterate I like what you are doing there generally
[21:44] <bac> gary_poster: i'm going to be starting a little late tomorrow.  have to take my mom to the airport.
[21:45] <gary_poster> ok bac
[21:45] <gary_poster> bac how was the weekend trip?
[21:45] <bac> gary_poster: good.  had a lot of fun on the east coast and then went south on sunday
[21:46] <gary_poster> cool bac, I'm glad
[21:46] <bac> 100x35 miles means you can do a lot of exploring on a day trip
[21:51] <Makyo> bcsaller, would you be willing to share your "improv landscape" work even if it's not finished?  Would like to make sure I'm heading down the right path.
[21:51] <Makyo> bcsaller, s/share/push
[21:52] <bcsaller> Makyo: the change to support get_annotation('env') is already merged, I'm working to add the env annotations to the delta stream right now
[21:53] <Makyo> bcsaller, thanks
[21:59] <hatch> how do I go about running JUST one test suite?
[21:59] <hatch> do we have that ability?
[22:00] <gary_poster> hatch yes.  See those links for each suite.  open them in a new tab or click on them in the same tab and reload
[22:07] <hatch> sorry I don't think I follow
[22:16]  * Makyo walkinates dogalope.
[22:17] <hatch> haha
[22:20] <hatch> gary_poster: are you saying there is a *.html file somewhere which doesn't automatically run all the tests?
[22:20] <gary_poster> oh, hatch!  I forgot you were not looking at these in the browser
[22:20] <gary_poster> hatch, start the test server, and look at them there
[22:21] <gary_poster> the section headers will be links
[22:21] <gary_poster> I suggest you use those
[22:21] <gary_poster> Maybe there is a way to do it with the phantomjs integration but I don't know it
[22:21] <hatch> ohhh now I see :)
[22:21] <hatch> thanks
[22:35] <bcsaller> Makyo: lp:~bcsaller/juju/delta-annotations has the delta streaming, its up for review now, but you can try it out,  lp:~bcsaller/juju-gui/landscape-links has the initial wiring
[23:33] <gary_poster> hatch, thanks for clarifying the dispatch binding stuff. cool


[12:12] <lophyte> superm1: you around?
[01:01] <superm1> lophyte, i'm here
[01:01] <superm1> lophyte, just got back from new years celebrations
[01:04] <lophyte> superm1: hehe, nice.. how was your holidays/
[01:04] <superm1> very good
[01:04] <superm1> and you?
[01:04] <lophyte> pretty good
[01:05] <superm1> so whats up?
[01:05] <lophyte> trying to set up a myth box, finally
[01:05] <superm1> okay come in #ubuntu-mythtv
[01:05] <superm1> we'll chat there
[01:05] <lophyte> oh, didn't know there *was* a channel for that..
[04:15] <lukaswayne9> Hello all!  I've just uploaded a new version of my application, GFCEU, to the revu.  It sports some new features and critical bug fixes, and I really hope to see it get into fiesty!  If you have the chance, please review it!  http://revu.tauware.de/details.py?upid=3930
[04:16] <crimsun> you'll have better luck later in the week, I suspect
[04:18] <crimsun> lukaswayne9, err, is there no use of the new Python policy?
[04:18] <lukaswayne9> Alright
[04:18] <lukaswayne9> new?  Newer since edgy?
[04:18] <crimsun> lukaswayne9, are you using python-support or python-central?
[04:19] <lukaswayne9> Oh damn, I built this on edgy :-\  I've been out of the building scene for a while...
[04:19] <crimsun> it should only be a very quick change
[04:19] <lukaswayne9> What change?
[04:21] <crimsun> http://wiki.debian.org/DebianPythonFAQ
[04:25] <lukaswayne9> After reading the FAQ, I'm still not clear on what needs to be changed
[04:26] <crimsun> well, are you going to use pysupport or pycentral?
[04:26] <crimsun> (note you're not build-depending on one)
[04:27] <lukaswayne9> pysupport i suppose
[04:27] <crimsun> well, you have to do it explicitly (i.e., add it), because neither is implicit
[04:27] <lukaswayne9> Alright.  WIll I still need to include python-dev?
[04:29] <crimsun> you'll want to change that to python-all-dev
[04:30] <lukaswayne9> And with the depends... I should change ${python:Depends} to python, python-support   ?
[04:33] <crimsun> no, that remains
[04:33] <lukaswayne9> So where does python-support come into play? Just add it to the depends list?
[04:35] <crimsun> you'd b-d on it
[04:35] <lukaswayne9> okay
[04:35] <lukaswayne9> alright, uploaded again
[04:35] <lukaswayne9> thanks a lot
[04:36] <crimsun> make sure you added the dh_pysupport invocation prior to dh_python in debian/rules
[04:36] <crimsun> http://www.debian.org/doc/packaging-manuals/python-policy/ap-packaging_tools.html#s-pysupport
[04:37] <StevenK> Adri2000: Just so you can stop bothering me, please look at Debian Mentors which do this sort of thing.
[04:39] <lukaswayne9> crimsun: okay, reuploaded
[04:53] <crimsun> lukaswayne9, in the future, please be careful with debian/changelog
[04:53] <crimsun> the two latest entries don't have update timestamps
[04:53] <crimsun> updated, even
[04:55] <crimsun> lukaswayne9, uploaded.
[04:56] <crimsun> rexbron, some misspellings in debian/changelog
[04:56] <rexbron> uug
[04:56] <rexbron> im owned
[04:56] <rexbron> let me re-read it, then kick myself
[04:58] <lukaswayne9> crimsun: alright! thank you
[05:00] <rexbron> crimsun: fixed to and relevent, any others?
[05:02] <crimsun> rexbron, the very first bit is awkward: "Removed rule to related to config.guess"
[05:02] <rexbron> crimsun: question, should I just remove all references to that rule, or rephrase
[05:03] <lifeless> rexbron: more detail will make it less awkward
[05:03] <rexbron> ok
[05:03] <lifeless> rexbron: i.e. 'stop deleting config.guess inappropriately'
[05:03] <lifeless> or whatever
[05:04] <rexbron> ok
[05:05] <rexbron> crimsun, lifeless: anything else before I upload?
[05:05] <crimsun> now's as good as any
[05:09] <rexbron> umm, I am uploading it but forgot to add in the changelog, that I fixed typos (I did not think it warrented it, was I wrong?)
[05:09] <crimsun> err, well, that was the point of the upload ;)
[05:10] <rexbron> so it is going to show up as ubuntu4
[05:10] <crimsun> that's fine
[05:10] <rexbron> ok
[05:10] <crimsun> when it's finally uploaded to Ubuntu it'll be -0ubuntu1
[05:10] <rexbron> i see
[05:12] <crimsun> what specifically about the naming scheme?
[05:12] <rexbron> Kamping_Kaiser: <program>_<upstream version>-<debian version>ubuntu<ubuntu version>
[05:13] <Kamping_Kaiser> the bit where ubuntu version gets attached
[05:14] <rexbron> baisically, if a ubuntu person makes a change to make it work with ubuntu (or any change for that matter) we up our own version nimber
[05:14] <rexbron> *number
[05:14] <Kamping_Kaiser>  -0ubuntu1 <is that debian version 0, ubuntu version 1? or are both numbers ubuntu version?
[05:14] <rexbron> right on the first case
[05:14] <Kamping_Kaiser> its suddenly much clearer :\
[05:15] <crimsun> it means that packaging version is not in Debian, but yes, the Ubuntu packaging version is 1
[05:15] <Kamping_Kaiser> what if debian now package it, does ubuntu have the option to keep its version (0ubuntux), or to sync in debians? (1ubuntux)
[05:16] <rexbron> a sync is when debian changes match ubuntu chagnes
[05:16] <rexbron> otherwise it is a merge
[05:16] <crimsun> Kamping_Kaiser, in that case we have a skew, and a decision has to be made whether to "fakesync" (use Debian's packaging infrastructure) or to continue with Ubuntu's
[05:17] <lifeless> rexbron: sometimes we talk all the changes, but still cannot sync
[05:17] <lifeless> because having changed the version number, dependencies in other packages also changed.
[05:17] <lifeless> s/talk/take/
[05:17] <rexbron> ok
[05:18] <Kamping_Kaiser> crimsun, i think i see :)
[06:22] <acacs> opa
[06:24] <Kamping_Kaiser> o_0
[07:26] <poningru> zomg
[07:26] <poningru> can someone bring in alpine and alpine-pico from debian??
[07:26] <Lathiat> alpine eh
[07:29] <Lathiat> vala?
[07:29] <Amaranth> it's a new programming language
[07:30] <Amaranth> well, sort of
[07:30] <Amaranth> it's like pyrex
[07:30] <Amaranth> http://vala.paldo.org/
[09:01] <crimsun> we need a "verify these $release-proposed SRU" day
[10:41] <jenda> Hello.
[10:45] <highvoltage> hello jenda
[10:45] <fowlduck> hello
[10:47] <jenda> The/a dev of KDEnlive and MLT has created deb packages, and the question got to me, but I am clueless, as usual...
[10:48] <jenda> http://paste.ubuntu-nl.org/216/
[10:48] <jenda> there
[10:50] <crimsun> it's unclear what the question(s) is(are).
[10:50] <crimsun> is he looking for Web hosting? Source package review? Both?
[10:52] <jenda> I'm not sure really...
[10:52] <fowlduck> I don't think he knows the process to get them included
[10:52] <jenda> crimsun: more like - what do you do if you want to make your deb package available to Ubuntu users.
[10:53] <crimsun> https://wiki.ubuntu.com/MOTU/Packages/New and the link(s) in the topic.
[10:53] <crimsun> the last link in the topic is most immediately relevant
[11:05] <jenda> crimsun, fowlduck: ok, thanks.
[11:05] <crimsun> np
[11:07] <fowlduck> yeah, glad to help (although crimsun did all the heavy lifting, as usual)
[11:31] <slytherin> Can anyone tell me who review packages uploaded to REVU?
[11:33] <crimsun> slytherin, anyone can
[11:33] <crimsun> however, only members of ubuntu-dev have advocate votes that matter
[11:33] <crimsun> currently two advocate (positive) votes are required to upload a new source package to the current development version
[11:34] <slytherin> crimsun: Thanks.
[12:10] <crimsun> Amaranth, let me know if your alsa issue is still relevant in 2.6.20-3.4 (now available)
[12:13] <gnomefreak> not yet here crimsun we just got the libc6-dev for 2.6.20-3
[12:13] <gnomefreak> linux-libc-dev i mean
[12:13] <crimsun> it's definitely available from archive.uc
[12:13] <crimsun> I just rebooted into 2.6.20-3-lowlatency
[12:14] <gnomefreak> i guess im waiting for the meta than -generic hasnt hit archive.ubuntu.com
[12:14] <gnomefreak> in updates atleast
[12:18] <gnomefreak> ah i see it in repos just no restricted-modules for it yet (assuming thats one reason it hasnt been sent to updates yet
[12:29] <finalbeta> I clicked the first link in the topic expecting to find how to actually make a .deb. I'm 6 links further and still not the wiser.
[12:30] <battlesquid> i'd like to recommend gruler be added to a ubuntu repository, because kruler doesn't work well (with borders!) in gnome
[12:30] <crimsun> you missed the Ubuntu Packaging Guide completely.
[12:30] <crimsun> ^ finalbeta
[12:31] <finalbeta> I see, the wiki has some issues. Now that I press back, I did see the kubuntu packaging guide.
[12:32] <finalbeta> Ok, cewl, thnx. Will try this.
[12:33] <crimsun> UPG is available from help.ubuntu.com, or if you're using GNOME, System> Help> System Documentation> Contributing to Ubuntu> Maintaining Ubuntu
[12:55] <Kamping_Kaiser> libavahi-common3 0.6.10-0ubuntu3.3 <- how can you have .3 of an upload? does that just mean "made a slight change"?
[12:57] <geser> it's the 3rd update to a "stable" package
[12:58] <crimsun> Kamping_Kaiser, the versioning scheme is different for updates, as geser mentioned
[12:58] <Kamping_Kaiser> so you will get x.x in -updates and -security?
[12:58] <crimsun> generally, yes
[12:58] <Kamping_Kaiser> thanks both
[12:58] <crimsun> and x.x~proposed1 to $release-proposed
[12:59] <crimsun> and possibly x.x~$release# for backports
[12:59] <crimsun> there is method to the madness
[12:59] <Kamping_Kaiser> this gets complex fairly fast. at least its organised madness
[01:21] <Kamping_Kaiser> does anyone here use firefox? can you look at the man page in OPTIONS? i think its missing an F... i just want to know its not just my setup.
[01:23] <Fujitsu> Where in the OPTIONS section?
[01:24] <Kamping_Kaiser> A summary of the options supported by irefox is included below.
[01:24] <Fujitsu> Nope, your setup.
[01:24] <Fujitsu> I get a nice bolded lowercase `firefox'
[01:24] <Kamping_Kaiser> might be a fixed-after-dapper bug
[01:30] <Lathiat> Kamping_Kaiser: security releases
[01:31] <Kamping_Kaiser> Lathiat, cheers. wonder why i havent picked it up :/
[02:00] <Kamping_Kaiser> in a debian/rules file, if i want to echo <some text "somemoretext ;"> into another file, do i need to escape all the special charactesr? <>;"
[02:00] <Adri2000> slomo: two things about liferea on feisty: I don't know what liferea-bin is supposed to do, do you? anyway it segfaults here. also, since I'm on feisty, my liferea is in english instead of french, I tried whith other locales and it doesn't seem to work either
[02:03] <geser> slomo: hello, can I merge prj2make-sharp?
[02:04] <MehdiHassanpour> Hi Motu developers
[02:05] <MehdiHassanpour> I've asked for ttf-freefarsi package to be add in Feisty universe
[02:06] <MehdiHassanpour> It's been added to Debian's unstable
[02:08] <Hobbsee> hey PriceChild
[02:08] <PriceChild> Hobbsee: !!!!!! :D
[02:09] <PriceChild> how're you?
[02:09] <Hobbsee> good
[02:09] <Hobbsee> MehdiHassanpour: doing it
[02:09] <MehdiHassanpour> Hobbsee: Thanks :-)
[02:11] <PriceChild> gd gd
[02:14] <Kamping_Kaiser> i dont see this covered in ubuntus packaging guide (but perhaps i just didnt read the right bit). i'm trying to make a derived package from firefox (just changing a few settings), and i get this error. i renamed the source dir, if thats useful info:
[02:14] <Kamping_Kaiser> dpkg-source: warning: source directory `./firefox-1.5.dfsg+<IP_ADDRESS>karl0' is not <sourcepackage>-<upstreamversion> `firefox-1.5.dfsg+<IP_ADDRESS>'
[02:14] <Kamping_Kaiser> dpkg-source: warning: .orig directory name firefox-1.5.dfsg+<IP_ADDRESS>karl0.orig is not <package>-<upstreamversion> (wanted firefox-1.5.dfsg+<IP_ADDRESS>.orig)
[02:16] <geser> the .orig.tar.gz has still the old directory name hence the warning
[02:16] <Kamping_Kaiser> so i should rename the diff, dsc, orig.tar.gz and the source dir, not just source dir?
[02:16] <Hobbsee> Kamping_Kaiser: but you can ignore it, if it's a warning
[02:17] <Kamping_Kaiser> Hobbsee, i prefer not to ignore warnings, they always come back to haunt me :)
[02:17] <geser> the diff and dsc get the new names automatically once you build a new source package
[02:17] <Kamping_Kaiser> thanks.
[02:18] <geser> the old dir name is inside the orig.tar.gz (use tar tzf to see it)
[02:18] <Hobbsee> Kamping_Kaiser: heh.  you can ignore that one though
[02:19] <geser> Kamping_Kaiser: if you really want to get rid of the warning, you have to unpack the orig.tar.gz, rename the dir and tar it up again
[02:19] <Kamping_Kaiser> Hobbsee, :)
[02:19] <Kamping_Kaiser> is that ok, with the 'dont mess with orig.tar.gz' rule?
[02:20] <Jozo-> Kamping_Kaiser: Don't change upstream version, if there is no need to change it.
[02:21] <Kamping_Kaiser> hm
[02:21] <Kamping_Kaiser> thanks for explaining this btw geser and folk
[02:44] <xerxas> Hi !
[02:45] <xerxas> Happy new year to all of you
[02:48] <slomo> geser: sure
[02:48] <slomo> Adri2000: well... it should work ;)
[02:52] <Adri2000> slomo: liferea-bin or locales? or both?
[02:53] <bddebian> Heya gang
[02:54] <Kamping_Kaiser> hey mate :)
[02:54] <bddebian> Heya Kamping_Kaiser
[02:54] <Kamping_Kaiser> :)
[02:55] <Lutin> hello bddebian
[02:55] <bddebian> Hello Lutin
[02:57] <Adri2000> slomo: there is no .mo files in the .deb
[02:57] <Lutin> bddebian: do you have 5 min to help me with the allegrogl pkg, on revu ?
[02:57] <slomo> Adri2000: it's in the language packs
[02:57] <slomo> Adri2000: once they're updated again...
[02:57] <Adri2000> ahhhh yes it's in main now
[02:57] <Adri2000> okay :)
[02:58] <slomo> ademan: and liferea-bin should work normally... well, does "liferea" work for you? ;)
[02:58] <Adri2000> Adri2000* :p liferea works yes but liferea-bin segfaults
[02:58] <slomo> Adri2000: probably mozilla-madness *shrug* ;)
[03:06] <Lutin> bddebian: actually I don't konw what to do whith the lib .... lintian says it's a sharedlib, but i provides no .so.x.x, has no soversion ... would be great if you had a clue :)
[03:07] <bddebian> Yeah, it would be :)
[03:09] <Lutin> lol
[03:10] <giskard> ciao
[03:13] <bddebian> Heya giskard
[03:14] <bddebian> Lutin: Actually, I believe the -dev package should have .so.X.X
[03:15] <Lutin> bddebian: that means I'd have to patch the makefile to actually generate it ?
[03:17] <bddebian> Give me a sec
[03:17] <bddebian> What the heck is the objdump parameter to get the SONAME?
[03:21] <geser> -p or -x
[03:21] <bddebian> Hmm, I didn't know -x did SONAME.  Thx geser
[03:22] <geser> -x includes -p
[03:22] <bddebian> Ahh
[03:23] <bddebian> Lutin: I wonder if that lib has issues.  I believe libs should have an SONAME
[03:24] <Lutin> bddebian: what should I do then ?
[03:27] <geser> Lutin: what gives "objdump -p libagl.so | grep SONAME"?
[03:28] <Lutin> geser: give me 5 min, I have to build it on this pc :)
[03:31] <bddebian> geser: Nothing
[03:32] <Lutin> the point is, as it's intended to be a plugin to allegro, it's not build like a sharedlib i guess
[03:33] <bddebian> Well it's building libagl.so
[03:39] <Lutin> so, I should ask upstream to modify the autofoo stuff to provide soname and lib.so.x.x, (or do it myself) ?
[03:40] <bddebian> Upstream would probably be preferred.  But I may be wrong about this.  I'm certainly no library expert..
[03:41] <azeem> Lutin: if it's a plugin, does it get installed into /usr/lib/allegro or something?
[03:42] <bddebian> Yes, /usr/lib/libagl.so
[03:42] <azeem> so, no :)
[03:43] <bddebian> So no, what?
[03:43] <azeem> if it's a plugin, it has no business getting put into /usr/lib
[03:43] <bddebian> Oh. heh sorry
[03:43] <azeem> it should get put into a subdirectory where allegro can find it
[03:43] <azeem> and plugins don't count as libraries, so no soname issues
[03:43] <bddebian> Ah, OK, thx
[03:47] <Lutin> azeem: ok
[03:47] <Lutin> azeem: and still should be updated to have a soname and such ?
[03:47] <bddebian> Lutin: So, just stick it in /usr/lib/allegro/libagl.so or so and make sure allegro can find it :-)
[03:48] <Lutin> bddebian: ok
[03:48] <bddebian> Lutin: No, not for a plug-in apparently
[03:48] <Lutin> bddebian: some software rely on that plugin, such as the ta3d game, so I wonder if it's only a plugin
[03:48] <azeem> Lutin: no, check out other allegro plugins for package naming conventions, if any
[03:49] <azeem> something like allegro-plugin-ag or whatever would be more suiteable in this case I guess
[03:49] <azeem> Lutin: how does ta3d rely on it?
[03:49] <azeem> check whether objdump -x ta3d |grep NEEDED lists it
[03:50] <Lutin> azeem: ok
[03:50] <Lutin> azeem: if it does, what does that means ?
[03:51] <azeem> Lutin: then it would mean libag1 is a true library and not a plugin
[03:52] <stgraber> Is there any problem with REVU ?
[03:52] <stgraber> my upload appears to be stuck in the FTP
[03:53] <bddebian> Here is where the allegro arts plugin puts it:
[03:53] <bddebian> usr/lib/allegro/4.2/alleg-artsdigi.so
[03:55] <Lutin> bddebian: ok, thanks
[04:02] <Lutin> azeem: currently building ta3d, I'll check the objdump thing asap
[04:07] <Lutin> azeem:  NEEDED      libagl.so
[04:08] <Lutin> seems that it's a true librairy
[04:10] <bddebian> Ack
[04:17] <Lutin> so I have to ask to upstream to provide the lib.so.x.x and a soname/soversion
[04:19] <jorgp> is there a mplayer 1.0rc1+ planned for multiverse?
[04:58] <Lutin> bddebian: did you see the liballegro4.2 source package ? all fixed by the debian maintainer. seems the upstream is not wanting to use libtool ^^
[04:59] <bddebian> joy
[05:07] <stgraber> Can anyone check why uploads got stuck on the FTP and doesn't appear on REVU ?
[05:17] <bddebian> How do I best do docbook2man in a CDBS package?
[05:23] <Lutin> bddebian: I don't understand what exactly means those linda warnings on kayali :/
[05:24] <bddebian> Lutin: Me either
[05:26] <Lutin> bddebian: lol
[05:26] <Lutin> I can't get what's wrong with having a 775 chmod on a script
[05:27] <Lutin> err. 755
[05:29] <geser> it's missing a she-bang
[05:32] <Toadstoo1> heya everybody
[05:32] <Toadstoo1> happy new year
[05:34] <bddebian> Heya Toadstoo1, to you also
[05:35] <bddebian> geser: Hey, do you know how I can get a docbook to a manpage in a CDBS package?
[05:36] <geser> bddebian: no
[05:36] <geser> have you tried to use one of the several cdbs hooks?
[05:37] <Toadstool> why the heck was my nick Toadstoo1? :p
[05:37] <Toadstool> I hate nickserv ^^
[05:38] <Adri2000> bddebian: can I "merge" msttcorefonts? ("" because it's really an easy merge :p, updated merge)
[05:41] <bddebian> geser: Yeah, I found it, thanks
[05:42] <bddebian> Adri2000: Go for it, thanks
[05:42] <Adri2000> ok, I will need someone for uploading, and that's the bigger part of the job for this merge :P
[05:43] <Adri2000> but first, pbuilding...
[05:56] <Adri2000> -> http://adrishost.homeip.net/~adri2000/ubuntu/toupload/msttcorefonts_1.6ubuntu1.debdiff (from 1.6), I hope my changelog is ok...
[06:18] <Lutin> does anyone know what that linda warning acutally means ?
[06:18] <Lutin> W: kayali; Executable /usr/share/kayali/MaximaParserTokenTypes.txt with perms 0755 is not an ELF file or script.
[06:19] <Lutin> err. .py, not.txt
[06:22] <bddebian> Lutin: It's telling you that you have executable "rights" on a non-script or ELF file
[06:23] <Lutin> bddebian: ok
[06:27] <Toadstool> Lutin: which in this particular case means that you should either change the rights on this file or add a shebang if it is supposed to be executed
[06:27] <Lutin> Toadstool: hay !
[06:28] <Toadstool> hi Lutin
[06:28] <Lutin> (thanks a lot) how are you ?
[06:28] <Toadstool> good, how are you?
[06:29] <Lutin> fine, thanks :)
[06:30] <Sp4rKy> hi there
[06:30] <Sp4rKy> Toadstool: hi !
[06:31] <Toadstool> heya Sp4rKy
[06:35] <Amaranth> alright, time to show my newbiness
[06:35] <Amaranth> how do i do this revu thing? :)
[06:45] <bddebian> Amaranth: Upload or reviewing?
[06:45] <Amaranth> upload
[06:46] <bddebian>  dput revu foo*.changes :-)
[06:46] <Amaranth> starting from scratch, i've never used it in any form
[06:46] <somerville32> kAmaranth: Watcha doin'?
[06:46] <bddebian> Ahh
[06:46] <Amaranth> somerville32: vala
[06:46] <Amaranth> http://vala.pardo.org
[06:46] <somerville32> Is it a programming language, kAmaranth?
[06:46] <Amaranth> yeah
[06:46] <Amaranth> and stop that :P
[06:47] <somerville32> What do you mean kAmaranth? :)
[06:47] <geser> is it a kde programm?
[06:47] <Amaranth> geser: nope
[06:48] <somerville32> Should be
[06:48] <Amaranth> more GNOME related, it's a programming language that leans on glib (specifically gobject) to convert a C#-like syntax into C then compile it
[06:49] <somerville32> Interesting
[06:49] <Amaranth> very
[06:51] <Amaranth> ugh, pbuilder is so slow
[06:51] <Amaranth> just realized i never updated it for feisty
[06:52] <somerville32> Amaranth: I have a 333mhz
[06:53] <Amaranth> oh, it's http://vala.paldo.org btw
[06:53] <Amaranth> typos ftw
[07:00] <bddebian> Do I have to do something special when I have an xml docbook file to create the manpage?
[07:05] <Adri2000> bddebian: could you upload the msttcorefonts merge please? http://adrishost.homeip.net/~adri2000/ubuntu/toupload/msttcorefonts_1.6ubuntu1.debdiff
[07:05] <Q-FUNK> has anybody heard anything about ubuntu abandoning the powerpc port?
[07:07] <Adri2000> bddebian: docbook2man?
[07:08] <bddebian> Aye, I'm using that.  Well docbook-to-man.  I'm not sure of the difference between docbook2man and docbook-to-man
[07:08] <bddebian> But I get:
[07:08] <bddebian> W: pegsolitaire; Manual page /usr/share/man/man1/pegsolitaire.1.gz failed to run through lexgrog.
[07:14] <bddebian> How do I keep cdbs from installing files I don't want it to install?  Do I have add an install/package:: target and rm the files manually?
[07:21] <Q-FUNK> bddebian: .la files?
[07:22] <bddebian> Q-FUNK: ?/
[07:37] <bddebian> Adri2000: Uploaded
[07:39] <Adri2000> thanks
[07:57] <bddebian> No, THANK YOU :)
[08:57] <LaserJock> hi MOTU Land
[09:00] <zul_> hey LaserJock
[09:00] <LaserJock> hi zul_
[09:01] <bddebian> Heya LaserJock
[09:02] <LaserJock> bddebian!
[09:11] <siretart> bddebian: didn't you apply for ubuntu-core-dev?
[09:11] <siretart> bddebian: TB Meeting going on right now
[09:12] <LaserJock> oh, it is?
[09:13] <siretart> right now, yes
[09:13] <hub> am I the only one unable to upgrade feisty pbuilder because of vim?
[09:14] <hub> Setting up vim-tiny (7.0-164+1ubuntu1) ...
[09:14] <hub> update-alternatives: unable to make /usr/share/man/ru.KOI8-R/man1/vi.1.gz.dpkg-tmp a symlink to /etc/alternatives/vi.ru.KOI8-R.1.gz: No such file or directory
[09:14] <hub> dpkg: error processing vim-tiny (--configure):
[09:14] <hub>  subprocess post-installation script returned error exit status 2
[09:14] <hub> pbuilder update fails with that
[09:16] <bddebian> siretart: A long time ago.  I gave up.  They don't want me :-)
[09:19] <siretart> bddebian: eh!
[09:41] <TheGods> howdy
[09:41] <LaserJock> hi
[09:42] <TheGods> hi
[09:42] <TheGods> does anyone here know anything about cinelerra?
[09:43] <Lutin> when I use this line in debian/rules, the build fails. does anyone see what's wrong ?
[09:43] <LaserJock> TheGods: not much. it's currently being worked on by the Ubuntu Studio folks
[09:43] <Lutin> for file in `find -name "*.py"`; do [ -n "`head -n 1 $file | grep #!`" ]  && chmod 755 $file; done
[09:44] <TheGods> LaserJock, i am one of those folks ;)
[09:44] <LaserJock> ah Toby
[09:44] <TheGods> there's a problem with ffmpeg licencing that the cinelerra people include in their sources
[09:44] <TheGods> indeed
[09:44] <TheGods> i just wanted to find out the details such that i could post to their mailing list
[09:44] <LaserJock> what's wrong with it?
[09:45] <geser> Lutin: have you tested this line with dash or bash only?
[09:45] <TheGods> LaserJock, i'm not sure - that's why i'm asking ;)
[09:46] <LaserJock> TheGods: well, I'm not really sure what the question is though
[09:46] <TheGods> oh of course!
[09:46] <LaserJock> TheGods: siretart can tell you a lot about ffmpeg right now ;-)
[09:46] <TheGods> ok
[09:46] <TheGods> thanks
[09:48] <TheGods> this is some of what i posted in #cinelerra: "Cinelerra uses a version of ffmpeg where free distribution is limited (perhaps only in the US, perhaps not). However, as a result, we cannot have the software in the Ubuntu repositories, which means we cannot include it in our release. This isn't what we'd like to be the case, and I would love to see this change."
[09:48] <TheGods> that's what i've been told, at least
[09:48] <siretart> TheGods: see https://wiki.ubuntu.com/MainInclusionFFmpeg
[09:48] <Lutin> geser: yes, seems to work with bash
[09:48] <TheGods> siretart, thanks muchly
[09:49] <geser> Lutin: test also with dash as dash is /bin/sh
[09:49] <LaserJock> TheGods: so cinelerra ships it's own copy of ffmpeg?
[09:49] <TheGods> yes
[09:49] <LaserJock> and it's different then our ffmpeg?
[09:49] <siretart> *sigh* - another one :/
[09:50] <TheGods> that's what i hear. and although it's (l)gpl, i've heard it's not freely distributable in the usa
[09:50] <siretart> the license is indeed not the problem
[09:50] <TheGods> yes, indeed
[09:51] <siretart> TheGods: does cinerella modify ffmpeg in any way?
[09:52] <LaserJock> TheGods: I sure don't envy you guys. Multimedia is awful to work with
[09:52] <TheGods> thanks :P
[09:53] <TheGods> siretart, i'll have to ask
[09:53] <Lutin> geser: ok with dash as well
[09:54] <Lutin> oh no, weird
[09:54] <Lutin> exit code is 1
[09:54] <siretart> TheGods: if they don't please make the package build against the ubuntu ffmpeg package. this way, we share bugs and security issues
[09:54] <TheGods> that's what i'm asking
[09:54] <TheGods> apparently their build system is horrendous :(
[09:57] <Lutin> geser: ok, I know why it fails
[09:57] <Lutin> geser: because if the last file does not math the test condition, the last exit code is 1 and make the thing fail
[09:57] <Lutin> I guess
[10:00] <TheGods> siretart, fortunately: (from the svn log): "r949 | pmdumuid | 2006-10-29 00:54:57 +0200 (Sun, 29 Oct 2006) | 9 lines
[10:00] <TheGods> Add configure option to allow for external ffmpeg linking."
[10:02] <bddebian> Anyone know why this is happening on a CDBS package?
[10:02] <bddebian> E: pegsolitaire: changelog-file-not-compressed ChangeLog
[10:02] <bddebian> W: pegsolitaire: wrong-name-for-upstream-changelog usr/share/doc/pegsolitaire/ChangeLog
[10:05] <_MMA_> LaserJock: The Cinelerra ffmpeg apparently is old, tweaked and stable. They dont want to mess with it (understandable) but it causes a problem for us to get into Universe.
[10:06] <LaserJock> _MMA_: I see
[10:06] <siretart> _MMA_: what definition of 'stable' do you use?
[10:06] <LaserJock> _MMA_: happy New Year, by the way
[10:06] <TheGods> siretart, it's their word
[10:06] <_MMA_> To you as well Jordan.
[10:07] <_MMA_> Yes. Having never used it myself I cant attest to its stability. Im going on their word.
[10:07] <TheGods> as i said, they've added a configure option to allow building with the normal ffmpeg
[10:08] <TheGods> i have been advised to ask on the mailing list, and will do so
[10:09] <_MMA_> TheGods: We need to also talk with muzzol. He might have handled some of these things and we dont want to be redundant.
[10:09] <TheGods> yes
[10:09] <TheGods> no
[10:09] <TheGods> i don't want to diverge too much from upstream if possible

[10:12] <LaserJock> ah, why not? ;-)
[10:13] <TheGods> cos then we'll have the burden of support
[10:16] <siretart> TheGods: if that works, please at least try to use the external xine
[10:16] <TheGods> you mean ffmpeg, but of source
[10:16] <LaserJock> heh
[10:16] <siretart> TheGods: I'm having the same problem with xine, upstream strongly recommends using the internal one, but we use an external one
[10:16] <TheGods> *course
[10:16] <siretart> of course, ffmpeg. my bad
[10:16] <TheGods> siretart, i know you're grief :(
[10:16] <TheGods> *your
[10:17] <TheGods> *are
[10:20] <siretart> TheGods: yes, the situation is pretty unfortunate. espc if you try to work on it for months if not for years
[10:20] <bddebian> WTF is this crap?  W: pegsolitaire: description-synopsis-might-not-be-phrased-properly
[10:21] <TheGods> siretart, that sounds like hell :(
[10:23] <siretart> TheGods: well, one very annoying fact is that the ffmpeg refuse to make 'proper' releases. this way, other projects using ffmpeg are forced to use some random svn snapshot
[10:23] <siretart> TheMuso: the problem with that is that random snapshots tend to break the build without notice
[10:24] <siretart> tsmithe: this means that they tend to include copies of ffmpeg, which makes them a support (both security and bug wise) nightmare
[10:30] <stgraber> siretart: you are the REVU's ftp admin right ?
[10:31] <siretart> stgraber: what's up?
[10:32] <stgraber> siretart: things got stuck in it and not shown on revu
[10:32] <siretart> compiz or pastebinit?
[10:32] <stgraber> pastebinit
[10:32] <stgraber> if you can remove everything I'll reupload
[10:33] <siretart> stgraber: did you join the lp group?
[10:33] <stgraber> yes, that's just a fix because it was rejected for inclusion in universe (missing COPYING file)
[10:34] <LaserJock> stgraber: no need to put that on REVU I don't think
[10:34] <LaserJock> stgraber: just send the fix the the loser MOTU that uploaded it ;-)
[10:35] <LaserJock> *to the
[10:35] <stgraber> LaserJock: well I did a little bit more changes than that single file (paste.ubuntu-nl.org now has some kind of javascript protection and I remove it for instance) + fixing two typos :)
[10:36] <LaserJock> stgraber: well, whatever you want :p
[10:36] <bddebian> siretart: Do you have a second to help my dumb arse?
[10:37] <stgraber> LaserJock: what kind of fix do you need ?
[10:37] <LaserJock> stgraber: a debdiff to the version I uploaded
[10:38] <Lutin> bddebian: fixed kayali, if you want to have a look
[10:38] <siretart> bddebian: what's up?
[10:39] <somerville32> Is there anyone here that is subscribed to feisty-changes AND can mass fwd them to an address for me (for legit reasons, of course)?
[10:40] <Toadstool> somerville32: https://lists.ubuntu.com/archives/feisty-changes.mbox/feisty-changes.mbox <-- the full raw archive in mbox format
[10:41] <somerville32> Toadstool: Is there any way I can import it to gmail?
[10:41] <somerville32> Or know of a program that could mass fwd for me?
[10:41] <Toadstool> er... no idea
[10:41] <tsmithe> somerville32, you looking to parse them for yo app?
[10:41] <Toadstool> I don't use gmail
[10:41] <somerville32> tsmithe: Yes.
[10:42] <tsmithe> surely python has mbox support?
[10:42] <Toadstool> sure
[10:42] <tsmithe> there's this kind of thing (very quick google): http://mail.python.org/pipermail/python-list/2004-October/289414.html
[10:42] <somerville32> I want to test normal operation though
[10:42] <bddebian> Lutin: OK
[10:42] <bddebian> siretart: Can I PM you?
[10:42] <tsmithe> or somerville32 http://www.marklyon.org/gmail/
[10:43] <siretart> bddebian: mmh, fair enough
[10:54] <harrisony> hi there i am following the guide here https://wiki.ubuntu.com/MeetingLogs/OpenWeek-Packaging101 and am doing sudo pbuilder create but i just wanted to know why is it download I: Validating apt-utils
[10:54] <harrisony> I: Retrieving aptitude
[10:54] <harrisony> I: Validating aptitude
[10:54] <harrisony> I: Retrieving base-files
[10:54] <harrisony> I: Validating base-files
[10:54] <harrisony> I: Retrieving base-passwd
[10:55] <harrisony> I: Validating base-passwd
[10:55] <harrisony> I: Retrieving bash
[10:55] <harrisony> opps didnt mean to do that sorry
[10:55] <lasindi> Hi all, I'm trying to create an Ubuntu package for a Python application I've recently written; I have no experience in packaging. I've been reading through this tutorial (http://women.debian.org/wiki/English/PackagingTutorial) I was directed to from the Ubuntu website, and when I ran dh_make, I chose CDBS as I have no binaries (because of Python). Is this the right choice (I get an error saying it can't find a .orig.tar.gz file)?
[10:55] <Fujitsu> It needs to download the base system before it can install it!
[10:56] <harrisony> Fujitsu oh..do you know how many packags it needs to download
[10:56] <Fujitsu> Not exactly.
[10:56] <LaserJock> lasindi: CDBS is ok, it is expecting to find the programs source in a tarball like <packagename>-<version>.orig.tar.gz
[10:57] <LaserJock> harrisony: a fair amount, it's creating a minimal Ubuntu install
[10:58] <harrisony> LaserJock, ahhh hmm i guess ill have to wait a while thanks!
[10:58] <LaserJock> harrisony: what kind of connection do you have?
[10:58] <enyc> hrrm
[10:59] <harrisony> LaserJock 64kb/s
[11:00] <LaserJock> harrisony: yeah, it'll take a few minutes. It's alphabetical so you can get an idea of where you are anyway
[11:00] <enyc> I wonder if I need to wait really patiently for a response in bug https://launchpad.net/bugs/77485 .... or if I need to mumble about this here and see if somebody here take notice  ;-)
[11:00] <Ubugtu> Malone bug 77485 in qpsmtpd "SRU request: edgy:qpsmtpd fix for bug #72602" [Undecided,Unconfirmed]
[11:02] <bddebian> LaserJock: That was just my stomach ;-)
[11:02] <LaserJock> oh
[11:05] <lasindi> LaserJock: so should I be in the source directory when I do dh_make and also have the tarball in the parent directory?
[11:05] <LaserJock> yep
[11:06] <LaserJock> lasindi: what I do is take the tarball and unpack it. then I move it to <packagename>-<version> if it isn't already. then tar it up to a .orig.tar.gz
[11:07] <LaserJock> lasindi: just make sure that the .orig.tar.gz and the downloaded tarball are the same (md5sum)
[11:07] <lasindi> LaserJock: okay, it's now complaining that I don't have a toplevel Makefile - this is because I'm using Python. What I was thinking is having the program's source install to /usr/share/programname and then writing a bashscript to go in /usr/bin that cds to /usr/share/programname and then runs the python program. Is that reasonable?
[11:08] <LaserJock> is it a single .py file?
[11:08] <enyc> LaserJock: ;-)
[11:09] <lasindi> LaserJock: well, I have several source files, but I only need to call one .py file.
[11:09] <lasindi> *well, "run" is a better word than "call" ;-)
[11:11] <LaserJock> enyc: the debdiff certainly seems small and reasonable but I'm not exactly sure what it's fixing?
[11:11] <LaserJock> lasindi: then put that one in /usr/bin/ and the rest in /usr/share/<packagename>/
[11:13] <lasindi> LaserJock: wouldn't that mean I need to have sys.path.append('/usr/share/packagename') in the source code? (I've been trying to avoid path names in my source code to keep it platform-independent.)
[11:14] <LaserJock> lasindi: well, you could use distutils
[11:14] <lasindi> The reason I'm wondering about the bash script method is that Jokosher, another Python app, does this.
[11:14] <LaserJock> although it might be a tad overkill
[11:14] <enyc> LaserJock: fixes 72602 as per bug title ;-)
[11:14] <enyc> LaserJock: "the impact of this bug"... described in 77485 anywaf
[11:15] <LaserJock> lasindi: that way is certainly acceptable, but I think distutils is a bit better for general portability, IMO
[11:17] <LaserJock> enyc: ah, yeah, I was looking at the "Closes: " bug, you should probably also put the SRU bug number in there too
[11:20] <bddebian> Later gang
[11:20] <enyc> LaserJock: well it is described in 72602
[11:20] <lasindi> LaserJock: I'm looking through the website at the moment, but distutils looks like something that wouldn't handle dependency resolution, which is why I was looking at Debian packaging. Is this correct?
[11:23] <LaserJock> lasindi: what I mean is distutils is a common way of handing installation for python apps
[11:42] <stgraber> LaserJock: thx


 oh that reminds me
 tsimonq2: the git repos need moved off phab - i'm finishing the gittea setup today so we will need to clone all the repos over proper
 and then theres our git.  simpler than the phab diffusion stuff and easier to learn heh
 kc2bez: ^^ for awareness
[00:03] <arraybolt3[m]> Hey, that sounds exciting! Is there already a link? teward001
 "[telegram] <teward001> kc2bez: ^..." <- Nice, thank you.
[00:34] <kc2bez[m]> Yeah arc and phabricator are not pleasant to learn. It does make reviews super nice though.
[00:36] <Rober[m]> i'm curious to see how it works now instead of phab
[02:15] <tsimonq2> -100 on gbp
[02:15] <tsimonq2> No. We aren't using it. Hard line. :P
[02:15] <tsimonq2> Also took you long enough ;]
[02:16] <tsimonq2> s/]/)/
[02:16] <tsimonq2> I have been through gbp hell already
[02:16] <tsimonq2> We don't need to store all upstream changes in Git. Just our packaging
[02:17] <tsimonq2> Makes it 10x less intuitive to update to new upstream releases. I want to update the changelog, run uscan, and be done
[02:17] <tsimonq2> And only push those lines, not the 500 million commits that happened in the meantime
[02:18] <tsimonq2> Anyway I'm cranky, I just wanna be back in Green Bay already, talk to y'all later or tomorrow or so :P
 simon: hey you know what fun fact
 you aren't dev lead anymore :P
[02:35]  * arraybolt3[m] horks teward001's hard drive
 plain git will be better than phab and diffusion and ark though
 *revokes arraybolt3's access to Lubuntu resources* oops did I do that
 *yawns*
[02:36] <arraybolt3[m]> LOL I don't have write access to anything official though, so what's there to take?
[02:36] <arraybolt3[m]> ok here's your hard drive back
 *yawns* I should be going to bed too but i'm too energized :\
[02:38] <arraybolt3[m]> teward001: OK, actual tip, not a joke, chamomile tea is supposed to help you wind down for sleep.
[02:39] <arraybolt3[m]> teward001: Also, quick question for you, will Phab accounts be migrated to Gitea automatically, or is there anything I need to do in order to get setup with Lubuntu Gitea?
 melatonin helps with winding down too.  can't stand tea.
 the gitea isn't even set up fully yet :P
 so not really
 i think we'll need to rereg users and stuff
 but we're not at migration point yet
 tsimonq2: your gbp issues are because you don't know gbp.  I've had to unfubar gbp several times, and most of the Salsa repos I use use gbp so.
 *salts Simon for being stubborn*
[02:42]  * arraybolt3[m] challenges teward001 to launch rvim in a terminal and then quit without using :q or forcing the terminal emulator shut
 also simon: there's ways to do the overlay without using a full source copy.  the only bits that need that are the upstream tarball branch, which is what the orig.tars are from anyways.
[02:47] <arraybolt3[m]> teward001: I hope we don't start using gbp just because I just spent all this time learning quilt and the million things that go with it...
[02:48] <arraybolt3[m]> Though, I'll just ride with whatever tools the core devs say to use. If Simon ends up switching to gbp, I'll learn it. But I don't think he wants to do that.
[02:48] <arraybolt3[m]> (And please please please don't tell me to start using Windows...)
 tbh
 quilt and gbp work fine together
 evidence: NGINX on Salsa, debian/xca on Salsa, Debian/pv on Salsa (this one uses the overlay i mentioned)
 but i digress
 *yawns*
 unrelated: I love how docker now included docker-compose as an inbuilt function - docker compose ... is easier than docker-compose to install xD
[02:55] <arraybolt3[m]> Isn't Docker closed-source?
 I'd gladly use something else but for some applications the only way to deploy them is via Docker
 (discourse for example)
 also just because something is closed source doesn't mean we can't use it :P
[02:56] <arraybolt3[m]> Yeah, but... hmm... part of me really doubts that Docker is the only way to run Discourse, I bet it could be hacked into LXD.
 it could be, if you really want to fuss with all the Rails chaos
[02:57] <arraybolt3[m]> I guess you know what you're doing, though. I just don't like Docker's closed-sourced-ness. Which is funny because I'm happy to use GitHub...
 but you know what, if we do that we lose support from upstream :P
 arraybolt: see here's the thing
 "closed source" isn't *bad*
 sure we can prefer other things to it
 but in some cases it's easier to bite the bullet than invest the time in trying to hack something into place
[02:57] <arraybolt3[m]> I know that.
 and besides, Docker isn't running everything, and even if it were each service is compartmentalized within LXD containers on the host
[02:58] <arraybolt3[m]> I guess Docker gives away their stuff to open-source projects, right?
 yay for high insanity security compartmentalization
 docker is also "free" you know
 also containerd that docker uses is, it seems, open source
 so technically this is containerd + some management frameworks for docker :P
[02:59] <arraybolt3[m]> I just hate software that's like, "Well, this is free, but if you want the *fancy* stuff, pay $X.YZ a month."
 keeping in mind that docker's core functionality is all we need and not behind a paywall, I don't know why this argument applies to Docker
 i agree with things like redis cloud, etc. those subscription models are annoying
 but usually that's for SAAS
 not self-hosted ;)
[03:00] <arraybolt3[m]> Because it makes me grumpy. LOL
 it makes me grumpy too but i don't get annoyed about it here.
 :P
 at least we aren't using RHEL which you need to pay out the wazoo for for standard update repos
 :P
[03:01] <arraybolt3[m]> Yeah but for that you install Rocky GNU/Hurd and away you go.
[03:04] <arraybolt3[m]> One concern - Ubuntu is a commercial open source project, and Canonical has 505 employees according to Google, Docker only allows free use for businesses with less than 250 employees. Since Lubuntu is a flavour, does it not count as part of Ubuntu from a Docker standpoint, or is this sorta in violation of their terms?
 IANAL, but technically speaking Lubuntu Project and Lubuntu Association behind the funding is less than 100 people officially
 and the likelihood Docker tries to take us to court over this is zero, they don't gain anything and stand to lose a lot
[03:06] <arraybolt3[m]> Oh my gosh I'm throwing a fit for no reason. Docker Desktop is the pricy thing, the CLI is free and Desktop isn't even available for Linux. Alright, use Docker, enjoy Docker, don't listen to me.
 correct.
 docker daemon is basically just a containerd wrapper
 but Docker Desktop is the GUI tool *they* develop for GUI management of docker daemon
 even so we qualify here:  > Non-commercial open source projects
 Ubuntu isn't a commercial product itself
 Ubuntu Pro and Canonical's enterprise offerings are
 also
 from the documentation of Docker:
 "Docker Personal is the new name of the Docker Free subscription. With its focus on open source communities, individual developers, education, and small businesses, Docker Personal continues to allow free use of Docker– including Docker CLI, Docker Compose, Docker Engine, Docker Desktop, Docker Hub, Kubernetes, Docker Build/BuildKit, Docker Official Images, Docker Scan, and more."
 we're still an open source community
 so for the purposes of Lubuntu we're only using it to leverage fast deployment of app containers, but not much of the rest
 so :P
[03:08] <arraybolt3[m]> Well, whatever. I was totally wrong. I might try using Docker if the Linux version is totally free, and it looks like it's even open-source. I... am ridiculous. Hey, makes me like Linux more!
 the linux version of Docker Engine, etc. is free, and for your own personal use it's also free to use Desktop
 otherwise the Docker engine wouldn't be installable from public repositories like Docker provides, you'd need a license URL for it
 i'mma go sleep now, i need to get up early for FT job.  *sips the warm milk and then logs off*
[03:11] <arraybolt3[m]> OK, c ya!
[03:26] <tsimonq2> I'm telling y'all right now that if we switch to GBP I'm force writing over it every time we touch it lol
[04:11] <tsimonq2> Sorry, /me cranky, -> bed
[04:12] <arraybolt3[m]> Hey, I got cranky earlier, did you see my whole debate with Thomas over Docker???
[04:12] <arraybolt3[m]> Anyway, see you tomorrow!
[04:14] <tsimonq2> It's not my first rodeo unfortunately, I've received several warnings in my 7 years of this :P it's never been brought up in any other context though so I think I'm fine :)
[04:14] <tsimonq2> But no I'll read it once I'm awake enough to accurately comprehend ;)
[04:15] <arraybolt3[m]> I was being silly. It's not even worth reading, I was confused and almost entirely wrong.
[04:15] <arraybolt3[m]> With the Docker debate I mean. You can read it for comic value later, but there's nothing important there that I know of.
[04:18] <arraybolt3[m]> Anyway, thanks for all your help with helping me learn Quilt and all that stuff, and I look forward to finishing up the patching and whatnot in the morning!
[15:25] <tsimonq2> Good morning,
[15:25] <tsimonq2> Today I'm spending the day recovering from SELF. You guys and Altispeed won't see much of me today
[15:26] <kc2bez[m]> > <@tsimonq2:linuxdelta.com> Good morning,
[15:26] <kc2bez[m]> >
[15:26] <kc2bez[m]> > Today I'm spending the day recovering from SELF.


[01:57] <trinikrono> hey all
[01:58] <trinikrono> if someone reports a bug that says it freezes on resuming what package to file too?
[01:59] <lajjr> trinikrono, what is it freezing on?
[01:59] <trinikrono> apon waking bug 366852
[01:59] <ubot2> Launchpad bug 366852 in ubuntu (and 1 other project) "Keyboard and Mouse Frozen after computer wakes (heat: 7)" [Undecided,New] https://launchpad.net/bugs/366852
[02:00] <trinikrono> the wiki page says kernel is the safest, but i wanted to ask first
[02:05] <lajjr> are you getting a crash repost at all?
[02:05] <trinikrono> i am trying to assign packages here
[02:06] <lajjr> yes then kernel.
[02:09] <lajjr> can you tag it please??
[02:09] <trinikrono> well i am not sure what to do here,
[02:09] <lajjr> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Tags
[02:09] <trinikrono> lol okie
[02:09] <trinikrono> you do work on the kernel?
[02:22] <trinikrono> okie
[02:22] <trinikrono> so i go on select a source package
[02:22] <trinikrono> and type in linux
[02:22] <trinikrono> an it says  too many searches, what is the name of the kernel package in ubuntu?
[02:34] <dlbike76> Hello, how long does apport-retrace usually take to process the coredump file
[02:57] <lajjr> trinikrono, if you can use https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies to add the files from you system to the bug report?
[02:58] <trinikrono> lajjr: well its up to the reporter now, i was doing assign bug to package and i put the tags 'suspend resume' also
[03:00] <lajjr> OK great...thanks..
[03:24] <trinikrono> i want to assign the package plymouth to this bug 596182, is this correct?
[03:24] <ubot2> Launchpad bug 596182 in ubuntu "Ugly Text Screens while booting, sometimes does not shut down (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/596182
[03:52] <lajjr> trinikrono, are you sure that bug go with startupmanager ???
[03:53] <trinikrono> well that is why i asking, it said so on the wiki page, find the right package
[03:56] <lajjr> yes you are right just that the description gives you an answer..??
[05:06] <trinikrono> can someone look at bug 371195 i believe that it should be wishlist at least
[05:06] <ubot2> Launchpad bug 371195 in gnome-power-manager (Ubuntu) "Blacklight stays lit (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/371195
[09:55] <meho_r> Hi, all. A question: if I use apport to report a bug, and after a 2-3 days there was an update of some packages, and my bug was declared invalid by apport bot and ask that I report a new bug if it occurs again. What's the catch?  I should patch this :)
[13:05] <vish> pedro_: hi , Bug #596022 is an Ubuntu bug? or needs to be sent to upstream?
[13:05] <ubot2> Launchpad bug 596022 in xchat-gnome (Ubuntu) (and 1 other project) "Package description is unhelpful (affects: 1) (heat: 6)" [Low,Triaged] https://launchpad.net/bugs/596022
[13:09] <pedro_> vish, that's a packaging bug (Ubuntu), probably the debian package is having the same description
[13:09] <pedro_> but that's not an upstream bug
[13:09] <vish> ah ok.
[14:24] <nigelb> vish: debian bug, you can open a task and perhaps provide a patch
[16:47] <xteejx> #ubuntu-meeting
[16:47] <xteejx> oops
[16:48] <xteejx> Anyway, Hi guys good afternoon :)
[16:49] <xteejx> Is anyone around that can take a look at my wiki page, tell me if it's up to scratch, I'm applying for Ubuntu membership and would be great if some of the higher up guys, i.e. pedro, brian etc would sponsor me or add a nice comment on my contributions wo my wiki page
[16:49] <xteejx> I'd really appreciate it, 7000+ karma so far bug triaging lol
[16:51] <xteejx> Or anyone really that's seen my work in and around the bug control/bugsquad stuff, I'm always here :)
[16:52] <drew212> hello xteejx
[16:52] <xteejx> Hi drew212 :)
[16:52] <xteejx> pedro_: Would you add a comment to my wiki page re above Mr pedro? :)
[16:53] <pedro_> hi xteejx
[16:53] <xteejx> hey :)
[16:53] <drew212> xteejx: i want to apply for bugcontrol, but idk when someone is competent enough to apply =P
[16:53] <pedro_> xteejx, only if you give me/us the url ;-)
[16:53] <xteejx> oops of course hehe
[16:53] <xteejx> https://wiki.ubuntu.com/xteejx
[16:54] <xteejx> drew212: Well you need to know about the bug triaging process, the workflow, how things work and why they work like that, our procedures, etc. All this information is on the wiki
[16:55] <drew212> xteejx: i'm currently a member of bugsquad, and i do my 5-a-days or more, and i'm being mentored under ddecator.
[16:56] <xteejx> drew212: Oh cool! Well if you have 5 decent bug reports that you have helped triage, you can apply for BugControl
[16:56] <drew212> xteejx: i do understand how to set importance, although i'm not going to be 100% correct in setting them because i cant get any experience...
[16:56] <drew212> xteejx: i usualy have to ask ddecator or micahg to set the importance of my FF bugs =P
[16:57] <xteejx> Of course, but it's on the Importance wiki page on what should be set as what, simple workaround = low, then medium, high, critical are real showstoppers
[16:57] <xteejx> drew212: That's no problem
[16:57] <drew212> xteejx: yeah, i always double check the wiki page before asking them to add an importance...
[16:57] <xteejx> tbh I haven't seen any BC applications for a couple of months
[16:58] <xteejx> drew212: Sometimes even us BC have to refer back from time to time
[16:58] <xteejx> ;)
[16:59] <xteejx> drew212: When you feel you are ready, just go for it anyway  https://wiki.ubuntu.com/UbuntuBugControl - it's voted on by the curent BC members and of course bugmaster Brian or Pedro have the final say
[17:00] <xteejx> pedro_: https://wiki.ubuntu.com/xteejx
[17:00] <pedro_> drew212, you can also ask your mentor to vouch for you, that helps a lot
[17:00] <xteejx> oh yeah
[17:00] <pedro_> and makes the review process far more easier for the BC members
[17:17] <drew212> pedro_: i'll ask ddecator if he think's im ready =)
[17:31] <zz_grille> hey everybody
[17:32] <zz_grille> i have installed lucid, after this i setup my server system completly but get one problem
[17:34] <zz_grille> tomcat6 creates a new user/group with the path /usr/share/tomcat6, but this directory belongs to the user and group root. a commercial/opensource webapp called opproject uses this directory to create a new folder in it. there the license file will be stored
[17:34] <zz_grille> but because of the wrong owner this was not possible until i changed the ownership to tomcat6:tomcat6
[17:35] <zz_grille> please update the installscript
[17:35] <micahg> zz_grille: please file a bug :)
[17:35] <zz_grille> where ?
[17:36] <micahg> zz_grille: do you have an Ubuntu desktop?
[17:36] <zz_grille> no
[17:36] <zz_grille> thats why i post this hewre
[17:36] <zz_grille> here
[17:36] <zz_grille> :-)
[17:36] <baptistemm> the bug is the application you trying to install
[17:36] <baptistemm> so see with them I'd say
[17:36] <zz_grille> wtf
[17:36] <micahg> zz_grille: https://bugs.edge.launchpad.net/ubuntu/+source/tomcat6/+filebug?no-redirect
[17:37] <baptistemm> I hardly why the owner of /usr/share would be different than root
[17:38] <zz_grille> baptistemm: why? the root webapp has there a directory, too
[17:39] <zus> would one bug begion to affect a bunch of other little things?  this  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574886 affe4cts me as well but im having other issues with in the last 24 hours  im on a fresh install  with ubuntu studio over ubuntu for 3 days now....
[17:39] <ubot2> Launchpad bug 574886 in apt (Ubuntu) "Apt has strange network errors when updating indexes. (affects: 24) (heat: 185)" [Undecided,Confirmed]
[17:45] <DrKenobi> Hi! A few days ago I read about some tool that make easy to triage bugs. Where can i find then?
[17:46] <micahg> DrKenobi: bughugger?
[17:47] <DrKenobi> I don't remember any name, maybe its bughugger. I'll take a look.
[18:07] <MrKanister> DrKenobi: You might want to take look at the packages "ubuntu-dev-tools" and "ubuntu-qa-tools". The present a large selection of useful small tools for the work with lp and bugs
[18:14] <DrKenobi> MrKanister: thanks, i'll take a look!
[18:53] <drew212> micahg: are you avail?
[18:54] <micahg> drew212: maybe for a quick question, about to run to $WORK
[18:54] <drew212> well for bug 571035 should i change the package to adobe flash and add the linux package as it could be a problem in either?
[18:54] <ubot2> Launchpad bug 571035 in firefox-3.5 (Ubuntu) "No sound in Flash videos after hibernate (affects: 2) (heat: 16)" [Undecided,Incomplete] https://launchpad.net/bugs/571035
[18:54] <drew212> its definetly either a flash issue or a kernel issue
[18:57] <micahg> drew212: try kernel
[18:57] <drew212> alrite
[18:58] <drew212> don't assign both packages?
[18:58] <micahg> drew212: nah
[18:58] <drew212> alrite
[18:58] <micahg> drew212: you should only do that if you're at least sure about 1
[18:58] <micahg> drew212: if it's not kernel, they'll reassign
[18:58] <drew212> is there a possibly needs-reassignment tag?
[18:58] <micahg> drew212: what did audio team say?
[18:59] <drew212> no hits in 2 days
[18:59] <micahg> drew212: yes, but you use that if you're not sure where it goes
[18:59] <drew212> should i add the tag?
[19:00] <BUGabundo_IsBack> HIIIIIIIIIIIIIIII
[19:00] <drew212> should i mark as new?
[19:01] <micahg> drew212: move to kernel and mark as New
[19:01] <micahg> drew212: no tag
[19:01] <drew212> sounds good
[19:24] <ddecator> drew212: i'll let you know what i think after i get a chance to review your work more in-depth later this week :)
[20:22] <vish> !development
[20:22] <ubot2> Interested in becoming an Ubuntu Developer? Get started here: https://wiki.ubuntu.com/UbuntuDevelopment
[20:23] <micahg> !msgthebot | vish :)
[20:23] <ubot2> vish :): Please investigate with me only with "/msg ubottu Bot" or in #ubuntu-bots.  Search for factoids with "/msg ubottu !search factoid".
[20:23] <vish> ;)
[20:26] <vish> micahg: i was actually wondering why bugsquad is listed there^
[20:27] <micahg> vish: bugsquad is a good contact for bug info
[20:27] <vish> also not sure what mailing list communication have to do with actual development [as in does it require to be mentioned there]
[20:27] <micahg> which is needed to help fix bugs
[20:27] <vish> micahg: we do , but in context with the wiki.. seems out of place
[20:28] <vish> or maybe i havent got the point of the wiki
[20:28] <micahg> vish: documentation :)
[20:29] <vish> micahg: why i ask is , we often give that link for members asking how they can help develop , while the bugsquad, mailing list is probably not the info they want.. maybe its just me then :)
[20:31] <micahg> vish: it's encouraging upstream devs to talk to us AFAICT
[20:31] <vish> hmm..
[20:32] <micahg> vish: so their apps can be triaged better
[20:34]  * vish ponders about adding a sub-section for papercuts , we need help getting bugs fixed too ;)
[20:35] <micahg> vish: maybe send an e-mail to ubuntu-devel
[20:35] <vish> micahg: for papercuts?
[20:35] <Pa_trick17> Hi, just joined the BugSquad-Team in Launchpad. The Ubuntu-Wiki-Page says that one requirement is to send an e-mail to the BugSquad-Mailing-List, but as I joined this List a few weeks ago i recognized ppl that didn't like all the "Want-to-join"-Mails - Shall I write one or not?
[20:36] <micahg> vish: about adding it to the wiki for development
[20:36] <vish> micahg: ah , right. sure
[20:36] <vish> pedro_: Pa_trick17 is here to join bug squad
[20:37] <vish> Pa_trick17: do mention you launchpad profile link
[20:37] <vish> your*
[20:37] <Pa_trick17> here?
[20:37] <vish> yup , will be easier for pedro_ to add it
[20:38] <Pa_trick17> https://launchpad.net/~trick17
[20:38] <pedro_> though you were a member already Pa_trick17 ;-)
[20:38] <pedro_> let me have a look
[20:38] <Pa_trick17> hi pedro_ ;-)
[20:39] <Pa_trick17> i'm the "proposed member" in the launchpad-team
[20:39] <micahg> drew212: about that crash report bug, the user submitted a crash report, just not one that can be retraced
[20:39] <pedro_> Pa_trick17, approved, keep up the good work!
[20:40] <micahg> drew212: and asking someone for a coredump.gz is not a good idea either
[20:40] <Pa_trick17> pedro_: thx - and greetings to Chile ;-)
[20:40] <pedro_> thanks ;-)
[21:10] <drew212> micahg: we need the stacktrace.txt no? He cant seem to find the file or get anything uploaded, how should we proceed?
[21:17] <micahg> drew212: well, the upload of the coredump should be seamless to the reporter, if the user doesn't have enough memory, then a gdb backtrace might be a better option, but I can search upstream for that bug a little later to see if it's a know issue (you're welcome to search as well)
[21:18] <drew212> micahg: i'm still confused as to what a propper crash report contains... is there a wiki page i can read? the how to triage and apport pages don't really say what you should look for
[21:20] <micahg> drew212: will you be on later tonight
[21:20] <drew212> micahg: probably around 12:30ish
[21:21] <micahg> drew212: don't know if I'll be on that late, but if I am, I'll be happy to explain
[21:32] <trinikrono> i would like to know as well lol
[21:33] <xteejx> ogasawara: Hi Leann sorry to bother you, is there any chance we can get the patch for bug 461419 into Maverick before final?
[21:33] <ubot2> Launchpad bug 461419 in linux (Ubuntu) (and 1 other project) "[Karmic Lucid] Atheros AR5211 - ath5k driver connection and performance issues (affects: 53) (dups: 6) (heat: 302)" [High,Triaged] https://launchpad.net/bugs/461419
[21:33] <xteejx> Or if anyone can answer that, I'd like to know (I'm affected)
[21:42] <xteejx> bug 461419 anyone?
[21:42] <ubot2> Launchpad bug 461419 in linux (Ubuntu) (and 1 other project) "[Karmic Lucid Maverick] Atheros AR5211 - ath5k driver connection and performance issues (affects: 53) (dups: 6) (heat: 307)" [High,Triaged] https://launchpad.net/bugs/461419
[22:06] <xteejx> Anyone available?
[22:10] <xteejx> Does everyone go to sleep at 22:10 BST?
[22:16] <arand> xteejx: I could see If I can get the patch to a PPA, would that be useful?
[22:17] <xteejx> arand: Yeah that would definitely help, a PPA or bzr branch
[22:17] <xteejx> I had problems compiling it took an hour to recompile linux-headers and it messed up I done something wrong
[22:17] <arand> xteejx: And this seems to be a generally quiet hour indeed.
[22:18] <xteejx> arand: I'm not usually around this late, it's 22:18 here lol
[22:19] <arand> The thing is, I would guess the best thing is to try to get the patch included upstream, in the kernel proper. Dunno, since it seems it's not really finished (even though it works the upstream report sound as though some tweaking might be going on..)
[22:20] <micahg> arand: IIRC, upstream patch window for 2.6.35 is closed
[22:20] <xteejx> arand: Yeah, the patch came from upstream, but as micahg says there won't be any further patches for the 6.35 version
[22:20] <xteejx> Well, not unless we include them
[22:20] <arand> Ah, right, (have no check on kernel cycle)
[22:20] <ogasawara> xteejx: sorry, was away.  I'm trying to view the bug in lp but it keeps timing out (I'm assuming to the large # of comments)
[22:20] <micahg> xteejx: yeah, that doesn't mean we can't include it, but that's the kernel team's call
[22:21] <xteejx> talk of the devil :)
[22:21] <ogasawara> xteejx: you said the patch is upstream?
[22:21] <arand> #ubuntu-kernel might be of interest, iff they are alive..
[22:21] <xteejx> ogasawara: Yeah it is, it's attached to the LP report too
[22:21] <ogasawara> xteejx: can you point me to the upstream sha1 id?
[22:21] <xteejx> ermmmm...... no?
[22:21] <xteejx> I have no idea what that is
[22:22] <ogasawara> xteejx: it's the unique identifier for the upstream patch
[22:22] <arand> I don't know if it's in any git tree yet, apart from the one who made it.
[22:22] <ogasawara> xteejx: I'll keep trying to reload the bug here
[22:22] <arand> ogasawara: Patch from upstream bugzilla report https://bugzilla.kernel.org/attachment.cgi?id=26566
[22:23] <arand> and report is https://bugzilla.kernel.org/show_bug.cgi?id=13892
[22:23] <ubot2> bugzilla.kernel.org bug 13892 in network-wireless "ath5k with 168c:001c in Aspire ONE causes other nearby wireless clients to disassociate" [Normal,Needinfo]
[22:23] <xteejx> ogasawara: Ohhh I understand, it's in the upstream report as a patch file, it's not official yet, I'll link the report https://bugzilla.kernel.org/attachment.cgi?id=26566 and https://bugzilla.kernel.org/show_bug.cgi?id=13892
[22:23] <ogasawara> xteejx: hrm, so not officially upstream then (as in included in Linus' tree)
[22:24] <xteejx> Not yet, no, but it seems confirmed by those that have recompiled, and also I believe I've seen the idea of setting L0/L1 before with these cards back with Intrepid...I do think it *may* be a regression
[22:24] <xteejx> the dreaded word
[22:24] <arand> Is a PPA able to handle a kernel rebuild what with size constraints etc.?
[22:25] <micahg> arand: you get 2GB now :)
[22:25] <xteejx> arand: Well the actual .deb wouldn't even make 50mb I don't think, so you should be safe
[22:26] <arand> Yea, but I heard someone before who had troubles since the actual size during build was a fair amount of gigabytes...
[22:26] <xteejx> Is there no way to build locally and add the resulting .deb from pbuilder to a PPA, or something like that?
[22:27] <arand> I don't think so..
[22:27] <xteejx> :( oh
[22:28] <xteejx> ogasawara: ^^ up a few sorry I didn't put the IRC nick on there
[22:28] <micahg> arand: I don't think there's a problem with during build size, only upload size
[22:28] <ogasawara> xteejx: not sure on that, I've never tried
[22:29] <ogasawara> xteejx: I usually just build the .deb and point people to it
[22:29] <xteejx> ogasawara: I meant my answer to your "is it is linus' tree)
[22:29]  * ogasawara is lost
[22:29] <arand> micahg: Like I said, I was talking to someone who ran into a build size limit when (s)he was trying to stick a kernel in a PPA, but I don't know if there were other particulars involved...
[22:29] <xteejx> ogasawara: "Not yet, no, but it seems confirmed by those that have recompiled, and also I believe I've seen the idea of setting L0/L1 before with these cards back with Intrepid...I do think it *may* be a regression"
[22:29] <ogasawara> xteejx: do you know if the author of the patch has submitted this upstream?
[22:30] <xteejx> It is upstream, it's on the kernel bug report
[22:31] <ogasawara> xteejx: I should clarify, when I say "upstream" I mean more in the sense of it's been sent to the appropriate mailing lists when it'll get reviewed by the upstream maintainers
[22:31] <xteejx> ogasawara: Ohhh I don't think so
[22:31] <ogasawara> xteejx: the reason I ask is that's the preferred method to get this into Maverick
[22:32] <xteejx> Oh I see, I don't actually know how to do that, I don't usually deal with kernel patches, I only report upstream bugs
[22:32] <xteejx> :(
[22:33]  * xteejx thinks the LP mailer has just had a spaz attack and sent 20 emails to his inbox at once!!!
[22:35] <ogasawara> xteejx: I just looked up the author of the patch and it looks they've authored a few patches already that have landed upstream.
[22:35] <ogasawara> xteejx: so I'd assume they're comfortable with submitting this to the appropriate people
[22:35] <xteejx> ogasawara: Cool :)
[22:36] <ogasawara> xteejx: I'll dig around the mailing lists and see if it's already been posted or not
[22:36] <ogasawara> xteejx: in the best case scenario, this will get upstream before 2.6.35 final and we'll get the patch for free when we rebase
[22:36] <xteejx> I really hope this makes it to Maverick it's been semi-showstopping for over a year and half (at least for me)
[22:36] <xteejx> When we resync it?
[22:37] <xteejx> That'll be good :)
[22:37] <ogasawara> xteejx: right, we rebase with each 2.6.35-rc# candidate as they come out
[22:37]  * xteejx is happy :)
[22:39] <xteejx> ogasawara: Anyway thanks for looking into this but I gotta run, got an early morning
[22:40] <xteejx> Thanks all for the help, must dash, goodnight :)
[22:41]  * micahg thinks since dash is bash in ubuntu, he's having a party :D
[22:41] <yofel> arand: btw, I already did kernel rebuilds in a PPA, work fine, only if you upload several revisions in succession you get to the space limit very fast... (IE, with 1GB I ran out of space after 3 rebuilds I think)
[22:42] <arand> yofel: Ah, right.
[23:34] <stenten> How do I sign an email to Launchpad with my OpenPGP key?
[23:44] <jmarsden|work> stenten: Maybe https://help.ubuntu.com/community/GnuPrivacyGuardHowto  will help?
[23:49] <stenten> jmarsden|work: thanks, I already had a read of that and it confused me even more, heh.
[23:52] <jmarsden|work> https://help.launchpad.net/YourAccount/ImportingYourPGPKey any better for you?
[23:57] <stenten> Heh, I've already read through all those pages, thanks. I really just want to know if I have to actually add something to my email message or if I'm supposed to do something with it on Launchpad instead.
[23:58] <stenten> I'm trying to use the email interface to modify a bug report.