[03:24] <bcurtiswx> maco, do you know if dan's dad's name is Jim ?
[03:24] <maco> bcurtiswx: dunno, never met his folks. for some reason i think he's also a D though.
[03:24] <bcurtiswx> maco, k thx
[03:25] <bcurtiswx> i've been meaning to ask him, never see him here anymore
[03:25] <maco> i know when they both taught at the same uni, they had the same email address but dan with a "2" at the end
[03:25] <maco> (erm i think it was a 2 that was his special marker...)
[03:25] <bcurtiswx> k
[03:25] <maco> er....you know he's deploying in a couple days, right?
[03:25] <maco> thats why he's not around..
[03:25] <bcurtiswx> deploying?
[03:26] <maco> yeah
[03:26] <bcurtiswx> where to?
[03:26] <maco> he works for the military
[03:26] <maco> take a wild guess
[03:26] <bcurtiswx> Afghanistan?
[03:27] <maco> elsewhere in that region too
[03:27] <maco> logged channel, dunno how much more than that should be said
[03:27] <bcurtiswx> maco, not a prob


[00:06]  * bluesabre high fives slickymaster
[00:17] <bluesabre> Unit193: https://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/revision/601 thanks!
[00:35] <pleia2> launchpad is so slooow
[00:35] <knome> not as slow as the wiki!
[00:35] <slickymaster> hey bluesabre
[00:37] <knome> pleia2, did you get to look at the updated slideshow yet?
[00:37] <pleia2> trying :)
[00:38] <knome> no hurries :)
[00:38] <pleia2> where is my cat
[00:39] <knome> i ate it
[00:39] <pleia2> :O
[00:39] <knome> we can add another speech bubble saying "meow"
[00:39] <pleia2> how about a squirrel
[00:39] <knome> not drawn yet
[00:39] <pleia2> the first slide looks a bit plain
[00:39] <knome> it's WIP
[00:40] <pleia2> haha, ok
[00:40] <knome> the whole slideshow, that is
[00:40] <knome> that's why it's not in trunk
[00:40]  * pleia2 nods
[00:41] <pleia2> the internet told me we won't have a media player
[00:41] <knome> yes
[00:41] <knome> the vote where we decided that was on the xubuntu-devel mailing list
[00:41] <knome> i think you voted too :P
[00:42] <pleia2> go me
[00:42] <knome> that's why i was asking you for your media manager preference too
[00:43] <knome> since we're running an article series that presents some of the teams' favorites now that we don't ship any
[00:43] <knome> (news?)
[00:43] <pleia2> I didn't actually
[00:43] <knome> aha :)
[00:43] <knome> might be
[00:43] <pleia2> but I remember it now
[00:43] <knome> yeah
[00:43] <knome> good
[00:43] <pleia2> I had no opinion since I'd never used them really
[00:43] <knome> you might have been under the influence of influence or jetlag
[00:44] <pleia2> that too
[00:44] <knome> the latter one is very likely even..
[00:46]  * pleia2 Strategy Document homework now
[00:46] <knome> <3
[00:46] <knome> if you are referring to the change i proposed, it's fortunately only a small one
[00:46] <pleia2> yeah
[00:49] <pleia2> is good
[00:50] <knome> yeah, i didn't expect much else
[00:50] <knome> it's just describing the current situation
[00:51]  * pleia2 nods
[00:51] <knome> we'll have a fun meeting tomorrow
[00:51] <knome> many things
[00:52] <pleia2> triangles
[00:52] <knome> hmm? :)
[00:53] <pleia2> desktop background
[00:53] <pleia2> is blueman crashing make it failing test?
[00:53] <knome> oh heh, yeah, that's the dev wallpaper we've had forever
[00:53]  * pleia2 nods
[00:53] <knome> pleia2, not a fail, just a regular bug
[00:53] <pleia2> k, that's what I put it as
[00:54] <knome> don't know why i'm highlighting you all the time
[00:54]  * knome facepalms
[00:54] <pleia2> yeah, it's only us here!
[01:04] <bluesabre> oh hey, people appeared
[01:15] <pleia2> I did an iso test so flocculant will still love me for another cycle
[01:16] <bluesabre> oh good
[01:17] <knome> we will all love you eternally
[01:18] <knome> ...for doing the ISO test, of course
[01:18] <pleia2> on real hardware, too!
[01:18] <knome> oh my, that's an upgrade to eternally*2
[01:18] <bluesabre> overachiever
[01:18] <pleia2> I need to look into this kernel bug now
[01:18] <knome> fix it plz
[01:18] <knome> :P
[01:19] <pleia2> I can't fix it!
[01:20] <knome> :((
[01:21]  * knome downgrades pleia2's love level to eternity*1.5
[01:25] <pleia2> hm, so the last kernel upgrade I did was to 4.2.0-27 and that worked, it's -30 that's breaking but I don't know if ones in between broke too
[01:25] <bluesabre> uh oh
[01:25] <pleia2> :\
[01:27] <pleia2> I don't know how we went through so many kernels
[01:28] <pleia2> wait, -27 and -30 are the only ones, there weren't ones in between
[01:38]  * tsimonq2 is loved eternally*100 for all the ISO QA tests I've done...AHEM AHEM.../me moves along
[01:38] <tsimonq2> heheheh :P
[01:40] <Unit193> I have pings..
[01:41] <Unit193> bluesabre: I didn't touch the seed, of course.
[01:46] <bluesabre> Unit193: yeah, pushed the seed so we should be good to go
[02:15] <Guest45173> switched xubuntu-dev looking for licensing answers.  What cannot be used besides logos, icons, etc?  We want to create a custom build based on xubuntu and distribute the .iso commercially to techs, not end users
[02:16] <Guest45173> (already consulted http://xubuntu.org/dev/derivatives/)
[02:16] <pleia2> we tried to include everything on there
[02:16] <knome> basically, the derivatives page covers everything that's essential
[02:17] <knome> if you have specific questions, we'll happily help with them
[02:20] <Guest45173> okay good to know you're here.  thank you for your input
[02:20] <knome> no problem
[02:21] <knome> the guidelines are written to make your work easier, not to land a tight set of rules that you must obey
[02:55] <bluesabre> flocculant: found a bug in gnome-software :)
[02:55] <bluesabre> bug 1552512
[02:57] <bluesabre> too bad I didn't get a screenshot of the screenshots, looked pretty nice
[02:57] <bluesabre> otherwise, it looks good https://imgur.com/a/qh9v0
[02:58] <Unit193> !info app-install-data-partner
[02:58] <Unit193> bluesabre: Do we need that with g-s?
[03:02] <bluesabre> Unit193: dunno :)
[03:03] <bluesabre> Unit193: looks like ubuntu-desktop still rdepends on it
[03:08] <Unit193> Sure, but as a good example, usc deps on app-install-data while g-s doesn't.
[03:08] <bluesabre> I'll check here in a bit
[03:09] <bluesabre> running through the iso now to see if there are any fixes needed in greybird or elementary-xfce
[03:18] <bluesabre> ochosi: bug 1552518
[03:28] <bluesabre> ochosi: Printers > Help > About seems to be missing its icon, will see if I can dig that one up before reporting
[03:33] <bluesabre> everything else seems ok
[03:37] <bluesabre> Unit193: doesn't seem to break anything by removing it
[03:59] <bluesabre> night all
[04:07] <Unit193> G'night..
[07:00] <flocculant> bluesabre: could be too sleepy - but don't understand that bug :)
[09:56] <knome> pleia2, just saying that we don't forget; there's one more issue to solve before moving to https
[09:57] <knome> pleia2, when you load x.org with https, browsers do not apply extras.css correctly, because it's from http
[11:32] <bluesabre> knome: drop the leading http: and just use //
[11:32] <bluesabre> ?
[11:34] <bluesabre>  //static.xubuntu.org/www/extras.css?ver=4.4.2
[11:44] <knome> bluesabre, the problem isn't that we don't get the right protocol
[11:44] <knome> the problem is mixed content; firefox refuses to use the http css file when the site is in https
[11:44] <knome> and we don't have https in static
[11:45] <bluesabre> ah
[11:45] <bluesabre> that's a problem
[11:46] <knome> yep
[11:46] <bluesabre> might just need to serve extras from xubuntu.org or add ssl to static
[11:46] <knome> one option is to load the css from the url via php and then shove it into a <style> tag
[11:47] <bluesabre> yeah, that would work
[11:47] <knome> the problem with serving extras from xubuntu.org is that we don't have file access there..
[11:47] <bluesabre> hacky but functional
[11:47] <knome> the ideal situation would be that we would have file access to the whole theme on x.org
[11:47] <knome> then i could update it on-demand
[11:48] <knome> but since that's not going to happen, i don't think file access to one file (even via an html form) is possible
[11:48] <bluesabre> yeah
[11:49] <bluesabre> what's in extras?
[11:49] <knome> temporary fixes
[11:49] <knome> so if something breaks, i'll put the fix in there first
[11:50] <knome> then move to main
[11:50] <knome> this was originally set up to be able to fix things quickly
[11:50] <bluesabre> gotcha
[11:50] <knome> so not having that work in https (especially if it's the default) is as good as not have the extras included at all
[11:53] <bluesabre> yup
[11:54] <bluesabre> guessing we depend on IS for xubuntu.org updates other than content?
[11:54] <knome> yep
[11:54] <knome> so maybe we should raise this question up in the "switch to HTTPS" thread with them and ask for their opinion on the options
[11:55] <knome> basically they say "it's your site, you do whatever you want with it", but i can't help but think that this loading css from a different domain/server is not the ideal situation for them either
[12:37] <flocculant> bluesabre: awesom
[12:38] <flocculant> e - just thought I'd check that software was there - obviously you knew it would be :)
[12:40] <knome> Unit193, if i create a new branch for meetingology, will you set a new bot up for testing purposes?
[12:40] <flocculant> knome: don't know if slides are in order currently - if they are - suggest swapping the support ones
[12:40] <knome> they are
[12:40] <knome> i'd say we want the mouse to face right
[12:40] <knome> so swapping them would mean the tail would be on some other slide than the other support
[12:41] <knome> so: i'll have to think about that
[12:41] <flocculant> I'd say that's besides the point - someone using the live session is more likely to want real-time than a doc
[12:41] <knome> sure
[12:41] <knome> i'm not disagreeing with that part :)
[12:41] <flocculant> not just a swap of wording ?
[12:42] <knome> well the thing is, the live slide needs those bubbles
[12:42] <knome> and the live one has the bubble for the main content too, kind of said by the mouse..
[12:42] <knome> a tail does not speak
[12:42] <knome> ;)
[12:42] <flocculant> I'm not disagreeing with the head and tail thing - though of course the angular bits only look like a mouse to you ...
[12:42] <knome> maybe
[12:42] <knome> anglish bits
[12:42] <knome> :P
[12:43] <flocculant> knome: so why not have the tail on the desktop then?
[12:43] <flocculant> then the bubbles will be with the head :)
[12:43] <knome> the desktop slide has soooo much stuff already :|
[12:43] <knome> and the point that the mouse is spanning those two slides is that it kind of binds them together better
[12:44] <flocculant> well - sorry but that just seems like the ubuntu way of doing things - form over function
[12:44] <knome> lol
[12:44] <flocculant> as long as it looks ok - sod the content :)
[12:44] <knome> i'm not saying we can't change it... i'm explaining why i'm doing what i am
[12:44] <flocculant> yea :)
[12:45] <flocculant> I understand your points for sure
[12:45] <flocculant> the content is the wrong way round in my opinion
[12:45] <knome> yep
[12:45] <knome> i did think about it
[12:46] <knome> but i'm not sure how to fix it right off the bat
[12:46] <flocculant> I didn't think about them being bubbles tbh - never seen a rectangular bubble before :D
[12:46] <knome> lol
[12:46] <knome> well, speech bubbles
[12:46] <knome> i'm sure you've seen rectangularish speech bubbles in comics
[12:46] <flocculant> I'll think about it as well - given your 'issue'
[12:47] <knome> haha ;)
[12:47] <knome> thanks
[12:48] <flocculant> just quick thought ... if we're going to have a pure contribute slide at the end - why not move the Want to further to the front - set the mood - that could have the tail
[12:48] <flocculant> eg swap Help with Want to
[12:49] <knome> mhm
[12:49] <flocculant> on the other hand - maybe over-thinking the whole slideshow anyway - who sees it for longer than 5 minutes nowadays :p
[12:49] <knome> yep
[12:49] <flocculant> excluding Unit193 :D
[12:50] <knome> one of the things we wanted to change was making the slideshow more graphic
[12:50] <knome> so at least it's that now..
[12:51] <flocculant> yea - I'm not complaining about how it 'looks' at all - good improvements if you ask me
[12:51] <knome> ack
[12:52] <knome> we should also see how the slideshow looks when we've landed the rest of the artwork
[12:53] <flocculant> bluesabre: our buildlog > libreoffice-style-breeze (1:5.1.0-0ubuntu1 ubuntu-minimal changelog  Added libreoffice-style-breeze to desktop-recommends
[12:54] <flocculant> don't know how that impacts on bug 1548647
[12:55] <flocculant> knome: where alberto has marked the importance of medium to our artwork package
[12:55] <knome> ;)
[12:55] <knome> i'll reply to him on the bug
[12:56] <flocculant> better you than me
[12:56] <knome> do we think it's high?
[12:57] <flocculant> well given that we spent a bunch of time in 15.10 getting the damn icons there :p
[12:57] <flocculant> s/the/our
[12:57] <knome> mhm
[12:57] <knome> '
[12:57] <knome> oops
[12:57] <flocculant> '
[12:57] <flocculant> s'ok
[13:01] <flocculant> bbl
[13:01] <knome> hf
[13:05] <bluesabre> knome: while you're in there, maybe mention libreoffice-style-elementary as a package Recommends so we can solve it easily
[13:05] <knome> recommends instead of?
[13:06] <bluesabre> http://packages.ubuntu.com/xenial/libreoffice-gtk
[13:06] <bluesabre> libreoffice-style-breeze | libreoffice-style-tango | libreoffice-style-elementary
[13:07] <knome> sounds sensible to me
[13:07] <bluesabre> gotta run, bbl
[13:11] <ochosi> bluesabre: meh, yeah i knew about that linked buttons bug, and i even tried to fix it before. it's just really a lot of work and code to change...
[13:11] <knome> ooh, a wild ochosi appears!
[13:11] <ochosi> and i'm not even sure there's a straightforward way of fixing it without rebasing on adwaita
[13:11] <ochosi> the two have drifted apart for too long probably
[13:12] <ochosi> and i'd appreciate not having to rebase before gtk3.20
[13:12] <ochosi> but yeah, i see that releasing an LTS version of xubuntu with a buggy theme also isnt an option
[13:12] <knome> let's schedule a hacking session between the two of us to rebase on adwaita then...
[13:13] <knome> gtk3.20 or not
[13:24] <bluesabre> UI freeze a week from today
[13:25] <knome> yep
[13:25] <bluesabre> Being a bug, not that big of a deal for the freeze :)
[13:25] <knome> well rebasing on SASS theme is a big deal
[13:25] <bluesabre> Yes
[13:26] <ochosi> yeah
[13:26] <ochosi> i mean one way to do it would be to do SASS -> css and then take out the relevant portions
[13:26] <ochosi> i sort of tried that
[13:26] <ochosi> but failed, so i'm not sure whether i really know what the relevant portions are
[13:26] <bluesabre> ochosi, knome: gnome software is in today's image, in case you're wanting to do any icon work
[13:26] <ochosi> icon work needed there?
[13:26] <knome> ochosi, hahah
[13:27] <bluesabre> Your call. Gnome icons != elementary icons
[13:27] <bluesabre> :)
[13:28]  * knome attempts to do enough SASS porting work to lure ochosi deep into the porting too
[13:28] <bluesabre> I'll try to do the upstream lo theme work this weekend
[13:30] <bluesabre> Also, won't be able to make the meeting today
[13:32] <bluesabre> Looks like I won't be needed for it though, so that works out
[13:32] <knome> heh
[13:44] <ochosi> yeah, i also won't be here today... :/
[13:44] <ochosi> ok, i
[13:44] <ochosi> 'll look at gnome software and the needed icons
[13:44] <ochosi> knome: well ok, i'll wait and see ;)
[13:44] <ochosi> potentially could take *some* time this weekend
[13:45] <knome> yeah, let's see how this spans out
[13:45] <knome> looks like the dev env wasn't complete anyway, i can't seem to get changes take effect
[13:45] <knome> but i'll work on it...
[13:50] <ochosi> okeydoke
[13:51] <ochosi> monday evening might also work
[13:51] <knome> ok, some progress at least now
[13:51] <knome> but meh :)
[13:51] <ochosi> (i know that's a bit specific, but this is how my free time is structured these days...)
[13:51] <knome> i don't understand why this looks like poop since i've only changed a few colors
[13:51] <ochosi> you can also look at the SASS branch of numix
[13:51] <knome> bah
[13:51] <knome> humbug
[13:51] <ochosi> but tbh i'd rather stay in sync with adwaita directly
[13:51] <knome> yeah
[16:04] <dkessel> slickymaster: nah, there's still gmb in the docs :p
[16:05]  * dkessel uses Unit193 's excellent docs mirror site again to compare stuff on the generated docs pages
[16:12] <pleia2> knome: oh yes, I completely forgot about the external css thing, that'll be hard to solve
[16:13] <knome> pleia2, i pointed out one workaround already (load the file with php and dump into an inline <style>)
[16:14] <pleia2> good grief
[16:14] <knome> yeah
[16:14] <knome> that just leaves me with the thought: why don't we just manage the stuff in x.org in *some* way
[16:14] <pleia2> yeah
[16:16] <knome> i don't know how strict the IS is with file access, but they don't seem to deny us any writes to the database, so we could alternatively just save the css in a wordpress option and dump that into a <style>
[16:17] <knome> ...but then again that leaves me feeling like "why can't they just allow the file write"
[16:17] <knome> but maybe they just won't
[16:22] <pleia2> heh
[16:40] <flocculant> wiki is great today ...
[16:41] <Nairwolf> why ?
[16:42] <flocculant> you missed the sarcasm ...
[16:46] <Nairwolf> yes, sometimes, it's better not to know...
[16:46] <flocculant> :)
[16:56] <dkessel> hah, german is now the second-most complete xubuntu-docs translation :D
[16:58] <flocculant> assuming English is first?
[16:59] <knome> english isn't a translation, it's the source..
[16:59] <flocculant> well
[16:59] <flocculant> whatever :p
[17:00] <pleia2> ok, meeting time
[17:00] <pleia2> #startmeeting
[17:00] <meetingology> Meeting started Thu Mar  3 17:00:03 2016 UTC.  The chair is pleia2. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: action commands idea info link nick
[17:00] <flocculant> I'm apparently available for this :)
[17:00] <pleia2> we have an angeda
[17:00] <pleia2> #link https://wiki.ubuntu.com/Xubuntu/Meetings#Agenda
[17:00] <pleia2> who all is here for our community team meeting? :)
[17:01] <flocculant> I'm apparently available for this :)
[17:01] <knome> slickymasterWork is on and off
[17:01] <flocculant> :)
[17:01] <knome> as always
[17:01] <knome> and i'm here as well
[17:01]  * bluesabre is watching
[17:01] <slickymasterWork> I'll doubt I'll be able to continue logged on
[17:01] <Nairwolf> I'm here
[17:01] <flocculant> hey bluesabre
[17:01] <pleia2> great
[17:01] <pleia2> #topic Open action items
[17:01] <pleia2> looks like we have just the one: knome and branau to collaborate with setting up a wordpress instance for the wallpaper submissions by sunday, feb 21
[17:02] <pleia2> knome: status update?
[17:02] <knome> done
[17:02] <pleia2> \o/
[17:02] <knome> we're running testing at the moment
[17:02] <knome> after that's done, we can announce the contest
[17:02] <knome> so next week
[17:02] <pleia2> #link https://lists.ubuntu.com/archives/xubuntu-devel/2016-March/011059.html
[17:02] <pleia2> ^^ if you want to be a guinea pig
[17:02] <pleia2> I mean help
[17:03] <dkessel> russian is first, surprisingly... never noticed any russian here....
[17:03] <pleia2> alright, moving on
[17:03] <pleia2> #topic Updates and Announcements
[17:04] <flocculant> sorry
[17:04] <flocculant> just quickly
[17:04] <flocculant> knome: if you do need testing - I can
[17:04] <knome> flocculant, ack, i'll send you the testing info after the meeting
[17:06] <pleia2> so, any updates/announcements?
[17:07] <pleia2> #info Beta 1 happened http://xubuntu.org/news/xubuntu-16-04-lts-beta-1/
[17:07] <knome> #info knome has been working on the article series for the website: http://wiki.xubuntu.org/website/series
[17:08] <knome> re: those, the plan is to publish the frist "my media manager" article on week 12
[17:08] <knome> schedule for the other series is still open, it depends a lot on the amount of articles we have
[17:08] <knome> if people have ideas, feel free to add them to the wiki
[17:09] <pleia2> thanks knome
[17:09] <knome> if people want to help with the articles, just poke me or edit the wiki page noting you are working on something
[17:09] <Nairwolf> do you want to translate these articles ?
[17:10] <knome> the website doesn't support translations currently, so to begin with, no
[17:10] <knome> but if somebody works with local teams, they can totally cooperate with us to publish translated articles on their websites
[17:11] <Nairwolf> I will do that, in France xubuntu is really popular
[17:11] <flocculant> \o/
[17:11] <pleia2> alright, drifting off topic from announcements
[17:12] <pleia2> any other updates?
[17:13] <pleia2> #topic Discussion items
[17:13] <pleia2> #subtopic The installer slideshow
[17:14] <pleia2> Full info: The installer slideshow has been kept the same for some time now, other than a few small graphical changes and some rewording of the slides. Should we keep this type of approach or should we choose a completely different approach?
[17:14] <knome> there is a WIP branch at https://code.launchpad.net/~xubuntu-doc/ubiquity-slideshow-ubuntu/xubuntu-1604
[17:14] <pleia2> I looked at it yesterday, pretty sparse so far but shaping up nicely
[17:14] <knome> and commentary/discussion has been ongoing on this channel as well as at http://pad.ubuntu.com/xubuntu-1604-slideshow
[17:14] <knome> so the "WIP" part means we still lack some artwork
[17:14] <knome> and some of the content isn't final
[17:14] <Nairwolf> I can't access to this pad, is it because I'm not in xubuntu team ?
[17:15] <knome> and we might add one more slide that discusses the customizability
[17:15] <flocculant> Nairwolf: go to offtopic
[17:15] <flocculant> might?
[17:15] <flocculant> I think that we should
[17:16] <flocculant> given it'll be live for 3 years
[17:16] <knome> the other option is to include the content in the desktop slide
[17:16] <flocculant> oh
[17:16] <flocculant> sorry :)
[17:16] <knome> ...but so far, since we don't know what kind of content it is, it's impossible to make a judgement on whether it should have its own slide or not
[17:16] <knome> so as always, ideas are welcome
[17:17] <pleia2> knome: oh, explain how to download and run the slideshow?
[17:17] <knome> yes
[17:17] <flocculant> I'd like to see some more on *customise* to be honest
[17:18] <knome> 1) bzr branch lp:~xubuntu-doc/ubiquity-slideshow-ubuntu/xubuntu-1604
[17:18] <knome> 2) cd to the branch root
[17:18] <knome> 3) ./test-slideshow.sh xubuntu
[17:19] <flocculant> should be in http://docs.xubuntu.org/contributors/documentation.html perhaps
[17:19] <flocculant> or somewhere ...
[17:19] <knome> flocculant, yeah, we currently have none really, quite a bit of that can fit in the desktop slide if we lose the two columns at the bottom
[17:19] <flocculant> perhaps
[17:20] <flocculant> except you were saying it had too much anyway
[17:20] <knome> flocculant, this branch is temporary, but yeah, we could mention the usual slideshow branch
[17:20] <flocculant> I wonder if perhaps we could
[17:20] <flocculant> slide > introduces stuff
[17:20] <flocculant> slide > expands a bit
[17:20] <flocculant> but ofc - time constraint(s)
[17:21] <flocculant> I see about 2 slides when I install on ssd
[17:21] <knome> :)
[17:21] <knome> we likely don't want to add more than 1 more slide if even that
[17:21] <flocculant> :)
[17:22] <flocculant> I'll retract then given I want a contribute one :D
[17:22] <knome> flocculant, there is a contribute slide...
[17:22] <knome> basically, the idea behind these changes has been that we should move the content to the website (and other places) and mostly only point to them
[17:22] <flocculant> so we have 1 to play with :)
[17:22] <pleia2> and to remove my cat :'(
[17:22] <knome> because the information is valuable even for those who aren't installing
[17:22] <flocculant> ofc
[17:22] <knome> pleia2, as i said, we can add one more bubble in the local support slide saying "Meow"
[17:23] <flocculant> in blue
[17:23] <pleia2> indeed :)
[17:23] <pleia2> but we don't translate into cat, so maybe that's confusing
[17:23] <pleia2> and my cats are too lazy to do translations
[17:23] <knome> but isn't the vocabulary very small too, just dump in random "meow"s and "mow"s
[17:24] <knome> :P
[17:24] <flocculant> knome: if you've some time later perhaps we could thrash a few bits out - working on from the conversation earlier
[17:25] <knome> yep
[17:25] <pleia2> so, want to continue this outside a meeting?
[17:25] <knome> no, but ok :(
[17:25] <knome> (just kidding)
[17:25] <pleia2> har
[17:25] <flocculant> hah - we can carry on if people want
[17:25] <pleia2> I don't have much to add just yet
[17:26] <pleia2> #subtopic Gnome-software update
[17:26] <flocculant> oh my
[17:26] <pleia2> Full info: Gnome-software update - aiming for decision by 7th March
[17:26] <pleia2> so, who wants to start on this one? :)
[17:27] <flocculant> so then - a few words I can start with then a link
[17:27] <flocculant> we've now got gs in the seed
[17:27] <flocculant> I've spent most of the week playing about with it
[17:27] <flocculant> you can install stuff from repos now
[17:27] <flocculant> now
[17:28] <flocculant> I've picked up on a bunch of bugs ...
[17:28] <flocculant> some are being worked on. some low priority, some high
[17:28] <flocculant> I've spent some time with some in -desktop with Robert Ancell
[17:29] <Nairwolf> If Ubuntu wants to integrate gnome-software in a LTS, I suppose we can trust them and hope the package will be enough stable for a LTS, no ?
[17:29] <Nairwolf> I will test it tonight with the daily
[17:29] <flocculant> I *could* give the meeting a whole list of bug #'s - probably best though to just give us
[17:29] <flocculant> https://bugs.launchpad.net/ubuntu/+source/gnome-software
[17:30] <flocculant> team perhaps can look
[17:30] <flocculant> the couple of issues I've found very very recently are
[17:31] <flocculant> install some app - dependencies need apt-get autoremove > if this isn't changed - then we should at least let our people know
[17:32] <flocculant> currently you can run gs and synaptic at the same time > not been brave enough to kill this install - only found it just before meeting so no time to kill a vm
[17:32] <flocculant> bluesabre has picked up on a couple of points
[17:32] <pleia2> that's a fair number of bugs
[17:33] <flocculant> if people try and find bugs with gs with me as reporter - they'll be from our base
[17:33] <flocculant> I HAVE tried to confirm all in a vm
[17:33] <flocculant> end
[17:33] <flocculant> pleia2: ack - BUT
[17:34] <flocculant> robert and in fact all I've dealt with in -desktop have seemed to appreciate the bugs
[17:34] <flocculant> many are triaged/fix commited
[17:34] <pleia2> that's wonderful to hear :)
[17:34] <flocculant> so while there *are* bugs - I think one of *us* being there helps
[17:35] <flocculant> easy for a dev to not think about the bits elsewhere
[17:35] <flocculant> so then
[17:35] <flocculant> summing up
[17:35] <flocculant> I think that we should just go with it - the nasty stuff will get dealt with I'm sure - they need it a lot more than we do
[17:36] <flocculant> I hope that helps everyone :)
[17:36] <pleia2> wfm
[17:36] <pleia2> flocculant: is there a way xubuntu testers/contributors can pitch in with testing?
[17:36] <flocculant> pleia2: well
[17:36] <pleia2> people love playing with new things
[17:37] <flocculant> basically they should have it now - if they install from the image - they definitely will have after 10:00UTC today
[17:38] <flocculant> oh yea
[17:39] <flocculant> one thing I've noticed locally *today* and I think this is probably to do with x-defaults or something, not pinged bluesabre yet - I no longer see software (as gs) in my menu
[17:39] <flocculant> but it works in live
[17:39] <flocculant> /done
[17:39] <pleia2> I guess I mean, does the desktop team have a workflow/reporting/package test that people can do?
[17:41] <flocculant> not that I know of
[17:42] <flocculant> it wasn't seeing anything but local installed at the beginning of the week
[17:43]  * pleia2 nods
[17:43] <pleia2> if they do come up with something, let me know so I can share it :)
[17:43] <pleia2> and maybe let them know that it could be a useful thing, if they want more testers and bugs reported
[17:44] <flocculant> ofc
[17:45] <pleia2> thanks flocculant, nice to see this moving along
[17:46] <flocculant> :)
[17:46] <pleia2> anyone else have anything to add?
[17:46] <knome> mm
[17:46] <knome> yes
[17:46]  * knome stops ranting on the doc team meeting for a minute
[17:47] <knome> pleia2, wait, was this anything to add to the pkg manager discussion or anything?
[17:47] <pleia2> knome: this topic :)
[17:47] <knome> then nope
[17:47]  * knome goes back to ranting
[17:47] <Nairwolf> I have to leave, I will read logs after.
[17:48] <pleia2> #topic Any other business
[17:48] <pleia2> now anything :)
[17:48] <flocculant> I guess we need to trak the icon down
[17:48] <flocculant> for the slideshow
[17:48] <knome> https://lists.ubuntu.com/archives/xubuntu-devel/2016-February/011045.html
[17:50] <knome> anybody want to say anything, or should we just start the vote?
[17:50] <pleia2> oh! that wasn't on the agenda
[17:50] <pleia2> #info Strategy Document rewrite for "Xubuntu users" (and a bit more)
[17:51] <pleia2> I'm happy to vote
[17:51] <flocculant> :)
[17:51] <flocculant> knome: I'm good if the change I proposed went in
[17:51] <flocculant> wording iirc
[17:51] <knome> it's in revision 531
[17:51] <knome> http://bazaar.launchpad.net/~knome/xubuntu-docs/xsd-community-updates-feb2016/revision/531
[17:52] <flocculant> yep - thought it was
[17:52] <knome> pleia2, start the vote then :)
[17:52] <pleia2> bluesabre: still here?
[17:52] <knome> pleia2, we'll just continue on the mailing list :)
[17:53] <pleia2> okie
[17:53] <flocculant> vote now wfm
[17:54] <pleia2> #vote Approve Strategy Document rewrite for "Xubuntu users" (and a bit more) (+1) or disapprove text (-1)
[17:54] <meetingology> Please vote on: Approve Strategy Document rewrite for "Xubuntu users" (and a bit more) (+1) or disapprove text (-1)
[17:54] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[17:54] <krytarik> +1
[17:54] <flocculant> +1
[17:54] <knome> +1
[17:54] <meetingology> +1 received from krytarik
[17:54] <meetingology> +1 received from flocculant
[17:54] <meetingology> +1 received from knome
[17:54] <knome> :D
[17:54] <pleia2> +1
[17:54] <meetingology> +1 received from pleia2
[17:54] <knome> bang!
[17:55] <pleia2> #endvote
[17:55] <meetingology> Voting ended on: Approve Strategy Document rewrite for "Xubuntu users" (and a bit more) (+1) or disapprove text (-1)
[17:55] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[17:55] <meetingology> Motion carried
[17:55] <pleia2> we'll continue on list :)
[17:55] <pleia2> thanks knome
[17:55] <pleia2> anything else?
[17:55] <knome> i don't think so
[17:56] <pleia2> #topic Schedule next meeting
[17:56] <pleia2> lucky flocculant gets to schedule it next
[17:57] <flocculant> oh woot
[17:57] <pleia2> thanks flocculant!
[17:57] <pleia2> :)
[17:57] <knome> woohoo!
[17:57] <pleia2> thanks everyone, happy thursday
[17:57] <pleia2> #endmeeting
[17:57] <meetingology> Meeting ended Thu Mar  3 17:57:18 2016 UTC.
[17:57] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2016/xubuntu-devel.2016-03-03-17.00.moin.txt
[17:57] <flocculant> 4/4/16 @16:23
[17:57] <knome> so late?
[17:58] <flocculant> pfft
[17:58] <pleia2> lol 16:23
[17:59] <flocculant> :)
[18:02] <pleia2> someday the wiki will stop erroring and I'll get these minutes up
[18:03] <flocculant> I would say that 'the next person up should ensure the minutes are there'
[18:03] <flocculant> maybe I will next meeting :D
[18:03] <pleia2> I think our Minutes magic page just doesn't work anymore
[18:04]  * pleia2 just tries to create page
[18:05] <knome> :D
[18:05] <pleia2> moar 500
[18:05] <knome> yay
[18:05] <flocculant> \o/
[18:07] <pleia2> I'll try this again later
[18:07] <knome> pleia2, i'm doing it
[18:07] <Unit193> knome: Going to dokuwiki meetingology then?
[18:07] <knome> Unit193, yeah
[18:08] <knome> pleia2, minutes are up
[18:08] <pleia2> knome: thank you
[18:09] <knome> np
[18:14] <Unit193> Might want to talk to whoever can merge code to meetingology too.
[18:14] <knome> i can handle AlanBell
[18:15] <Unit193> You sure it's him anymore?
[18:16] <knome> https://launchpad.net/~ubuntu-bots/+members#active
[18:16] <knome> i can also poke jussi
[18:16] <knome> like, poke really hard.
[18:28] <flocculant> ha ha ha
[18:56] <flocculant> pleia2: you want someone not at work to do the minutes ?
[18:57] <flocculant> oh nvm - jolly old Pasi did it :D
[18:58] <flocculant> oh meh
[18:58] <flocculant> knome: vote result looked odd before I got another 500
[19:01] <Unit193> jussi, someone even more inactive. :D
[19:01] <Unit193> Pici runs all the bots now.
[19:09] <flocculant> Pici ftw then
[19:24] <Unit193> flocculant: 1516217 is done right?
[19:25] <flocculant> bug 1516217
[19:25] <flocculant> yea
[19:26] <flocculant> believe so
[21:12] <Nairwolf> knome, I've summited two files, seems okay
[21:13] <Nairwolf> but you can easily upload something else than .jpg .svg or .png
[21:13] <Nairwolf> you rename a file, and it's okay
[21:13] <knome> is the "something else" actually still an image file?
[21:14] <knome> for example, if you rename an image called image.jpg to image.doc, it is still an image file.
[21:17] <Nairwolf> no, I've rennamed a pdf file with .jpg
[21:18] <Nairwolf> if you look, I've called it simply "pdf"
[21:19] <knome> ok, i'll have a look at the security check
[21:20] <Nairwolf> yes, I don't know what's happen if you send a .js file. But I suppose that as soon as you don't execute the file, it's okay
[21:25] <knome> oh. the wordpress function gets the filetype based on the filename. lazy
[21:34] <Nairwolf> yes, a lot of sotfware are cheated by that
[21:34] <Nairwolf> they just verify the name extension
[21:35] <Nairwolf> I suppose it's not really dangerous
[21:51] <knome> Nairwolf, try again; it should fail now for the pdf
[21:51] <Unit193> What about xpm? :D
[21:51] <knome> that too
[21:51] <knome> only jpg, png and svg are allowed
[21:51] <Unit193> :(
[21:51] <knome> and submissions from the user ~unit193 are given automatically a -1 vote
[21:51] <knome> JUUUUST KIDDING!
[21:51] <knome> (but no, no xpm's)
[21:51] <Unit193> Understandably.
[21:52] <Unit193> About the -1 vote, that is.
[21:52] <knome> next i should make sure svg's are shown...
[21:52] <knome> but that's a backed woe
[21:52] <Unit193> I may have missed it, this doesn't require the user in ~xubuntu-users?
[21:52] <knome> backend too...
[21:52] <knome> Unit193, it doesn't.
[21:52] <knome> we can easily make that so if we want though
[22:04] <Nairwolf> ok, knome
[22:07] <Nairwolf> that works
[22:27] <flocculant> knome: if you need testers - feel free :)
[22:29] <knome> oh right
[22:30] <knome> flocculant, info sent
[22:30] <flocculant> looks like it arrived too :)
[22:31] <Nairwolf> I realize it's difficult to know the licence of a specific picture
[22:31] <Unit193> Not if you made it.
[22:32] <Nairwolf> it's not like software, if you find some code source somewhere, you're almost sure to find the licence. With pictures, it's so much easy to copy and share a picture...
[22:32] <flocculant> knome: point #1 - should we not make reading the terms a necessary part of submitting?
[22:32] <Nairwolf> But, I know that without licence, it's by default copyrighted
[22:32] <knome> flocculant, you have to check the checkbox...
[22:32] <Nairwolf> flocculant: it's necessary
[22:33] <flocculant> knome: aah cool - ignore me for a moment then :D
[22:33] <knome> flocculant, even if we made a user scroll through a page, we couldn't know any better if they read them or not
[22:33] <knome> :)
[22:33] <flocculant> no ofc not - but we can say they agreed to them :D
[22:33] <knome> yep
[22:33] <Unit193> Make 'em as short as possible, more likely to read it.
[22:34] <flocculant> Unit193: for sure
[22:34] <Nairwolf> Yes, Unit193 has a good advice
[22:34] <Unit193> Every so often he does, sure. :P
[22:34] <knome> Unit193, http://contest.xubuntu.org/help/terms/
[22:34] <knome> Unit193, they are pretty short compared to some of the terms i've read..
[22:35] <Unit193> knome: I wasn't saying they were long, hadn't seen them.  Nice bullet points, makes skimming for the good stuff easier! :)
[22:35] <knome> Unit193, good good
[22:35] <Nairwolf> Knome, yes it was pretty short, and I've read them
[22:35] <knome> and same terms as we had the last time...
[22:38] <Unit193> (I figured I'd not be of much help testing the contest, even more so since you know I don't create images.)
[22:38] <flocculant> Unit193: do you think I do?
[22:38] <flocculant> I'm just testing the process :)
[22:39] <Nairwolf> I've contacted the author of a really nice wallpaper in order to know the licence
[22:39] <knome> yeah, flocculant is sending images of his dog..
[22:39] <Unit193> flocculant: Yes!  More specifically, you know how to press all the buttons and throw the spaghetti at the wall better. :P
[22:39] <Nairwolf> oh ! Seems to be the perfect wallpaper flocculant !
[22:39] <Nairwolf> I want dog's flocculant as wallpaper !
[22:40] <Unit193> flocculant: FWIW, I actually have been following up and getting a problem with Qt5 and xenial fixed.  Just not said anything here because doesn't matter to Xubuntu.
[22:40] <knome> flocculant, for some reason, i don't see what you sent
[22:41] <knome> are you trolling?
[22:41] <knome> :P
[22:41] <knome> or did i break something...
[22:41] <flocculant> knome: well it lists 3 for me
[22:41] <knome> and do you see the images?
[22:41] <flocculant> no - should I?
[22:41] <knome> yeah...
[22:42] <flocculant> mmm
[22:42] <flocculant> knome: obviously these are just images I have kicking about in backdrops - is that going to make any difference?
[22:43] <knome> nope, this is testing and i'll wipe them all
[22:43] <flocculant> mmm
[22:43] <flocculant> well just jpg's or png's
[22:44] <knome> or svg's
[22:44] <flocculant> but I am doing this from xenial ofc
[22:44] <knome> heh
[22:45] <knome> flocculant, can you send them again?
[22:45] <flocculant> knome: I meant what I'm putting there - not what I could
[22:45] <knome> i think i figured out what broke
[22:45] <flocculant> knome: I just did a new one
[22:45] <knome> oh :)
[22:45] <flocculant> oh ok
[22:45] <knome> hmm.
[22:45] <knome> i don't see it
[22:45] <knome> i deleted 3 of yours
[22:46] <flocculant> well it was before you figured something out :)
[22:46] <knome> hehe
[22:51] <flocculant> knome: yup - that's working now
[22:51] <knome> good
[22:52] <flocculant> delete works
[22:52] <knome> \o/
[22:54] <flocculant> and if it works for me ...
[22:54] <bluesabre> knome, add me, will test whatever needs tested after dinner
[22:54] <knome> bluesabre, instructions in your mail
[23:01] <Nairwolf> everything seems to work with me knome
[23:01] <Nairwolf> goodbye
[23:05] <flocculant> knome: you have time to warble slideshows at all?
[23:05] <flocculant> hi bluesabre :)
[23:06] <knome> flocculant, i'm kind of tired, but i listen well, and can totally throw ideas around
[23:07] <flocculant> knome: no rush at all
[23:08] <bluesabre> Hey flocculant
[23:10] <flocculant> knome: I'm away tomorrow till Saturday - then around for ages again
[23:11] <knome> right
[23:11] <flocculant> knome: how much time do we have?
[23:12] <knome> ui freeze is next thu
[23:13] <flocculant> ok - perhaps over the weekend maybe?
[23:14] <knome> yeah
[23:27] <knome> flocculant, bluesabre: btw, since you are in the -website team, you should be able to vote and see the results on the contest site too - feel free to try that out as well
[23:28] <flocculant> knome: oh right - didn't think of logging in with website rights
[23:28] <knome> :)
[23:29] <bluesabre> knome, will do
[23:29] <knome> cheerio
[23:30] <flocculant> night night
[23:33] <knome> nighty nighty flocculant
[23:49] <flocculant> not gone anywhere yet - thought you were :)
[23:51] <knome> nah
[23:51] <knome> i said i'm kind of tired
[23:51] <knome> means i'll hang out for an hour more at least
[23:51] <knome> :P
[23:54] <flocculant> oh right
[23:55] <flocculant> you said cheerio - implies goodbye to me :D
[23:55] <knome> aha :D


[00:33] <CarlFK> elements: I did that for a few weeks because the intrepid kernel had support for my wifi - worked fine
[00:33] <CarlFK> finally I just installed intrepid
[16:45] <Syco54645_AAO> hello, i am having trouble compiling the intrepid git of the kernel.  it is giving me an error that i have pasted here: http://pastebin.ca/1196487  does anyone have any ideas?
[16:49] <CarlFK> Syco54645_AAO: did you see  https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[16:49] <Syco54645_AAO> CarlFK: i believe so, let me look at it.
[16:51] <Syco54645_AAO> on step 8 i did not use CONCURRENCY_LEVEL=N, but the rest of it i used
[16:51] <Syco54645_AAO> and it did not work
[16:51] <Syco54645_AAO> the .config file that i am using is from <IP_ADDRESS>
[16:52] <CarlFK> you did #5 make oldconfig ?
[16:54] <Syco54645_AAO> yes i did all of the steps up till 8
[16:54] <CarlFK> well, try 8 with the CON thing
[16:54] <Syco54645_AAO> ok
[16:55] <Syco54645_AAO> isnt that just to help with compiling though, to speed it up.  that line would say not to use any
[16:55] <Syco54645_AAO> i believe
[16:56] <CarlFK> good point
[16:56] <CarlFK> iv compiled kernals, but no expert
[16:57] <Syco54645_AAO> well we shall see wat happens
[16:57] <Syco54645_AAO> it is odd that it would fail like that though
[16:58] <Syco54645_AAO> well that didnt even start to compile
[16:58] <Syco54645_AAO> lol
[16:58] <CarlFK> you might want to try the .27-3 kernel source deb - which might be different
[16:58] <CarlFK> that's oss
[16:58] <CarlFK> odd
[16:59] <Syco54645_AAO> i may grab the src deb
[16:59] <Syco54645_AAO> see waht that will do
[17:03] <Syco54645_AAO> well thanks for trying to help
[17:03] <Syco54645_AAO> talking to another one of the kernel team for the aspire one to see what they got
[17:04] <CarlFK> good luck - sorry i wasn't much help :)
[17:05] <Syco54645_AAO> np
[17:05] <Syco54645_AAO> thanks
[17:05] <Syco54645_AAO> looks like we will need the luck, he is having an issue as well
[17:40] <oussema-harbi> hi everyone
[17:41] <oussema-harbi> i ve compiled the linux kernel from 2.6 sources ,but i cant get it to work
[17:41] <oussema-harbi> it loads everything ,but when mounting the rootfs ,it doesnt recognize the partition
[17:42] <oussema-harbi> does anyone have any idea about what am i doing wrong ?
[17:46] <CarlFK> recognize ?
[17:47] <CarlFK> can you post your kernel/initrd files somewhere I can try them?
[17:47] <oussema-harbi> ok
[17:51] <oussema-harbi> infact i didnt make an intrd
[17:51] <oussema-harbi> could that be the fault ?
[17:52] <oussema-harbi> because i think mouting the rootfs is done before loading initrd in ram ,no ?
[17:55] <oussema-harbi> they are on http://radestn.homelinux.org/files/
[17:56] <oussema-harbi> soory they are on http://radestn.homelinux.org/drupal/files/
[17:57] <oussema-harbi> so Carl ?
[18:01] <CarlFK> getting...
[18:02] <oussema-harbi> ok
[18:03] <CarlFK> um... shouldn't i see vmlunux and initrd.gz ?
[18:04] <oussema-harbi> isnt lfskernel. ... the equivalent for vmlinux
[18:04] <oussema-harbi> and for the intrd.gz ,i said i didnt update the initramfs
[18:04] <oussema-harbi> may be that's the error
[18:05] <CarlFK> put up what you are using
[18:07] <oussema-harbi> well now am using windows -the new grub couldn't load the old ubuntu either ,but i can see the files from windows
[18:07] <oussema-harbi> i ll uppload the old ones -the workling ones
[18:07] <CarlFK> where working = doesnt recognize the partition, right?
[18:09] <oussema-harbi> here is the situation :
[18:09] <oussema-harbi> i have a ubuntu hardy that works fine
[18:09] <oussema-harbi> i tried to compile the kernel on a different partition ,and i updated the grub
[18:10] <oussema-harbi> when rebboted ,the kernel cant mount the partition of the new rootfs -where i put the new kernel
[18:10] <oussema-harbi> and even when i make grub >find /boot/grub/stage1
[18:11] <oussema-harbi> i get (hd0,1) ==> the working ubuntu
[18:11] <oussema-harbi> and (hd0,2) ==> here i put the new kernel ,with a new filesystem
[18:11] <oussema-harbi> so i make root(hd0,1) ,i wanted to recover the old one
[18:12] <oussema-harbi> and i did : grub>kernel /boot/vmlinuz-2.26.24-generic root=/dev/sda2 ro single
[18:12] <oussema-harbi> but it says /dev/sda2 unrecognized
[18:13] <oussema-harbi> NB: i did grub> setup  after doing (<grub>root(hd0,1) )
[18:13] <oussema-harbi> do you get the situation ?
[18:14] <CarlFK> not exactly - what happened to initrd.gz ?
[18:14] <CarlFK> something like initrd.img-2.6.24-19-generic
[18:15] <oussema-harbi> i have initrd.img on / -on the working system root
[18:15] <oussema-harbi> ohh
[18:15] <oussema-harbi> yes i have initrd.img-2.6.24
[18:15] <oussema-harbi> yes i have initrd.img-2.6.24-generic
[18:16] <CarlFK> are you using it?
[18:16] <oussema-harbi> am checking
[18:16] <oussema-harbi> here is my menu.lst
[18:16] <oussema-harbi> #Begin /boot/grub/menu.lst
[18:16] <oussema-harbi> #By default boot the first menu entry
[18:16] <oussema-harbi> default 0
[18:16] <oussema-harbi> #Allow 30 seconds before booting the default
[18:16] <oussema-harbi> timeout 30
[18:16] <oussema-harbi> Use prettier colors
[18:16] <oussema-harbi> color green/black light-green/black
[18:17] <oussema-harbi> #The first entry is for LFS
[18:17] <oussema-harbi> title LFS 6.3
[18:17] <oussema-harbi> root (hd0,2)
[18:17] <CarlFK> make
[18:17] <CarlFK> it
[18:17] <oussema-harbi> kernel /boot/lfskernel-<IP_ADDRESS> root=/dev/sda3
[18:17] <CarlFK> stop
[18:17] <oussema-harbi> #The original Working system for backup
[18:17] <oussema-harbi> title Ubuntu Hardy
[18:17] <oussema-harbi> root (hd0,1)
[18:17] <oussema-harbi> kernel /boot/vmlinuz-2.6.24-19-generic
[18:17] <oussema-harbi> root=UUID=dd3c2ea0-b194-4e4e-b4c1-3f4a1dec9a33 ro quiet splash
[18:17] <oussema-harbi> initrd /boot/initrd.img-2.6.24-19-generic
[18:17] <oussema-harbi> # This entry automatically added by the Debian installer for a non-linux
[18:17] <CarlFK> clsoe the chat window
[18:17] <oussema-harbi> OS
[18:17] <oussema-harbi> # on /dev/sda1
[18:17] <oussema-harbi> title           Windows Vista/Longhorn (loader)
[18:17] <oussema-harbi> root            (hd0,0)
[18:17] <oussema-harbi> savedefault
[18:17] <oussema-harbi> makeactive
[18:17] <oussema-harbi> chainloader     +1
[18:17] <oussema-harbi> stop what ?
[18:17] <oussema-harbi> why ?
[18:17] <oussema-harbi> am i flooding ?
[18:17] <CarlFK> yes
[18:17] <oussema-harbi> ok
[18:18] <CarlFK> oh boy.
[18:18] <oussema-harbi> is it ok ,now ?
[18:18] <CarlFK> yeah - use a paste bin
[18:18] <oussema-harbi> i dont know how to do it
[18:18] <oussema-harbi> i ll put it on the address i gave you
[18:19] <CarlFK> http://dpaste.com/
[18:19] <CarlFK> hit that, paste, hit "Paste it", cut/paste the resuling url here
[18:19] <oussema-harbi> http://dpaste.com/76491/
[18:20] <oussema-harbi> i tried replacing root=UUID=dd3c2ea0-b194-4e4e-b4c1-3f4a1dec9a3 with root=/dev/sda2 ,but didnt work
[18:20] <CarlFK> you probably need a initrd, unless you complied in the fs drivers
[18:21] <oussema-harbi> in that case why i sdint work with ubuntu too ?
[18:21] <CarlFK> huh?
[18:22] <oussema-harbi> i tried loading the second option (working ubuntu ..) but the kernel says unable to find device /dev/sda2
[18:26] <oussema-harbi> i upload the old working kernel and initrd
[18:26] <CarlFK> put those 2 files on your site
[18:26] <CarlFK> good :)
[18:26] <oussema-harbi> do you want the old device map?
[18:27] <oussema-harbi> it's there too
[18:28] <CarlFK> nope
[18:29] <oussema-harbi> ok now
[18:33] <oussema-harbi> are you trying to boot from those files ?
[18:33] <CarlFK> http://dev.personnelware.com/carl/a/qemu1.png
[18:33] <CarlFK> thats what I get with lfskernel-<IP_ADDRESS>
[18:34] <oussema-harbi> yes except the block is(0,0)
[18:35] <CarlFK> oh right - i forgot  root=/dev/sda3 - jsut to be sure ill try that
[18:35] <oussema-harbi> ok
[18:35] <CarlFK> although it is pretty clear you need the fs drivers
[18:35] <oussema-harbi> do you know what 's that EDD error ?
[18:35] <oussema-harbi> wait ill google on it
[18:37] <CarlFK> you get nothing after "available partitions: " right?
[18:37] <oussema-harbi> yes
[18:37] <oussema-harbi> i got nothing
[18:38] <CarlFK> yeah - thats cuz you don't have any drivers - which are typically in initrd
[18:40] <oussema-harbi> ok i ll update initramfs and try again
[18:40] <CarlFK> initrd is a ram disk that the kernel knows how to read - the drivers could also be included in the kernel, but that makes it bigger and stuff (exactly why initrd is used gets complicated.)
[18:40] <CarlFK> also, you can use qemu to test
[18:40] <oussema-harbi> i guess intirrd is a minimal ramfs ,that the kernel uses to load and mount the original one
[18:40] <oussema-harbi> am i right ?
[18:41] <CarlFK> right
[18:41] <oussema-harbi> am on windows right now*i just have virtualbox
[18:41] <oussema-harbi> i ll boot on grub
[18:41] <oussema-harbi> and try to recover the old one
[18:41] <CarlFK> juser@dhcp85:~/a/radestn$ qemu -kernel vmlinuz-2.6.24-19-generic -initrd initrd.img-2.6.24-19-generic hda.qcow2
[18:41] <oussema-harbi> and then chroot and update initramfs
[18:42] <CarlFK> little easier than having to get the files in/out of the VM disk
[18:42] <oussema-harbi> yeah
[18:42] <CarlFK> i think virtualbox might be based on qemu, so you may already have qemu
[18:43] <oussema-harbi> virtualbox is not done with qt
[18:43] <oussema-harbi> so they are not really the same
[18:43] <oussema-harbi> anyway ,i ll reboot
[18:43] <oussema-harbi> and try to recover
[18:43] <oussema-harbi> Thank you very much for your help :-)
[18:43] <oussema-harbi> have a good day / nice dreams :-)
[18:44] <CarlFK> good luck
[18:44] <oussema-harbi> Thank you :-)
[18:49] <_ruben> hmm .. cant seem to find any more indepth info on how to build source package for use with module-assistant, other than /usr/share/doc/module-assistant/HOWTO-DEVEL.gz


[04:24] <andrew> bts3685|vps: Thanks. I lost the game.
[04:24] <andrew> darn screen sessions with backlog
[05:06] <MutantTurkey> there is a war going on for your mind, if you are thinking you are winning.
[05:07] <andrew> looks like I'm losing that as well
[05:07] <ssweeny> unless you're thinking of the game like bts3685|vps
[05:08] <MutantTurkey> I was not thinking of that game, I was reminded of a song by Flobots called "we are winning" from the album "fight with tools". An excellent record if i do say so myself.
[05:36] <InHisName> I have a mind, thank you very much.
[05:36] <InHisName> I am NOT loosing that!
[05:36] <InHisName> However every birth day I seem to loose a bit of something . .   .    .     .     .
[05:37] <InHisName> a piece of my    .   .   .   .   youth
[05:38] <jackson> o/
[05:39] <InHisName> I'd easily agree to a million losses of 'the game' to exchange for one single win of a piece of lost youth.
[07:38] <bts3685|vps> effing hell you guys. it's true. screen + irssi is like a timebomb for the Game. which i just lost.
[18:31] <ssweeny> ChinnoDog, you never said if you actually wanted a diaspora invite
[19:27] <ChinnoDog> I wouldn't know what to do with it
[19:27] <ChinnoDog> Is it FB without the proprietaryness?
[19:44] <ssweeny> more or less
[19:44] <ssweeny> it's reminiscent of fb before it got so annoying
[19:47] <pleia2> it's facebook but without all the people you signed up to facebook to communicate with ;)
[19:49] <ssweeny> exactly
[19:50] <ssweeny> those people are what made it annoying
[19:50] <pleia2> everyone on diaspora knows how to communicate with you properly so you don't even need to log into it ever
[19:51] <ssweeny> the perfect social network :)
[20:39] <ChinnoDog> pleia2: I never have to log into it?
[20:40] <ChinnoDog> So I sign up and then forget it ever existed in the first place?
[20:41] <ssweeny> yep
[20:41] <ssweeny> tbh that's probably what i'll end up doing
[20:42] <ChinnoDog> What is the point of that?
[20:42] <ChinnoDog> I already don't use identi.ca
[20:45] <rmg51> I'm way ahead of all of you.....
[20:45] <rmg51> I don't use any of those things :-D
[20:49] <ChinnoDog> It isn't even out of alpha
[20:49] <ChinnoDog> It only exists because a few people were dissapointed in Facebook's privacy policy, and they hardly represent the majority
[20:53]  * ChinnoDog thinks it is destined for mediocrity
[22:09] <ChinnoDog> Anyone need any 2gb hard drives?
[22:10] <anduril> ...
[22:10] <anduril> do you mean thumb drives?
[22:10] <anduril> cause otherwise 0_o
[22:21] <ChinnoDog> hehe
[22:21] <ChinnoDog> You could put an adapter on it, but it wouldn't fit in your pocket very well
[22:21] <ChinnoDog> At least if it was on your keychain you wouldn't be able to lose it very easily.
[22:22] <ChinnoDog> Hardware goes into my closet to die.. this is so sad
[22:22] <anduril> doubt it'd work for very long those old drives werent very shock proof
[22:22] <ChinnoDog> They are Quantum drives too. Not very reliable.
[22:24] <ChinnoDog> I have 4 2gb, 2 20gb, and a 18gb 68-pin SCSI drive
[22:25] <ChinnoDog> I should probably zero them out before I chuck them.
[22:25] <ChinnoDog> I've taken on a burden instead of making use of old parts
[22:25] <anduril> or smash em
[22:25] <ChinnoDog> too much wokr
[22:25] <ChinnoDog> work
[22:26] <ChinnoDog> I have an external USB to IDE adapter
[22:30] <ChinnoDog> no external SCSI adapter though
[22:30] <ChinnoDog> I might have to harvest its magnets for my refridgerator
[22:34]  * ChinnoDog writes some zeros
[22:52] <ChinnoDog> This must be the slowest 20gb hard disk on earth
[22:52] <ChinnoDog> No worries here. No one will have the patience to ever look for data on it.
[22:55] <InHisName> So izzat where you'll stuff your pr0n ?
[22:56] <ChinnoDog> It isn't fast enough for pr0n
[22:56] <anduril> mm cold pizza
[22:59] <waltman> http://www.flickr.com/photos/caseywest/5581885011
[22:59] <PennBot> Title: It's Happy Hour, Damnit. | Flickr - Photo Sharing! (at www.flickr.com)
[23:20] <bts3685|vps> ChinnoDog: zeroing out doesn't prevent recovery from things like foremost or testdisk. might want to get yourself some thermite insteaad
[23:24] <ChinnoDog> bts3685|vps: Reference one verified report of data recovered from a modern hard drive that has been wiped
[23:25] <bts3685|vps> that's like saying "reference one verified report of mysql serving requests"; it's status quo. http://www.linux.com/news/enterprise/storage/8257-how-to-recover-lost-files-after-you-accidentally-wipe-your-hard-drive
[23:25] <PennBot> Title: How to recover lost files after you accidentally wipe your hard drive | Linux.com (at www.linux.com)
[23:26] <ChinnoDog> That is about how to reconstruct data that is already there
[23:26] <anduril> there's a difference between recovering deleted files and recovering information thats been wiped with multiple passes of zeros
[23:26] <bts3685|vps> nope
[23:26] <ChinnoDog> That is not recovery of data after the disk has been erased
[23:27] <ChinnoDog> You only need one pass of zeros on a modern disk
[23:27] <ChinnoDog> No one has ever recovered data from a modern disk below the level of what was written
[23:27] <anduril> three passes doesnt take that long :)
[23:27] <ChinnoDog> That is like the argument for taking vitamin suppliments. It doesn't cost much, no one knows if you need it, might as well do it
[23:31] <anduril> http://en.wikipedia.org/wiki/Data_remanence like always wikipedia has some decent links about this stuff
[23:31] <PennBot> Title: Data remanence - Wikipedia, the free encyclopedia (at en.wikipedia.org)
[23:32] <anduril> I thought 3 passes was the DoD level but apparently it was 7 but now they require physical destruction or degaussing instead
[23:33] <ChinnoDog> That is theoretical
[23:33] <ChinnoDog> It was much easier to do on old hard disks with low density platters
[23:33] <ChinnoDog> Even then it isn't that easy
[23:33] <bts3685|vps> huh. lookit that, as long as the drive is over 15GB and modern ATA, one pass suffices
[23:34] <bts3685|vps> http://en.wikipedia.org/wiki/Data_remanence#Feasibility_of_recovering_overwritten_data
[23:34] <PennBot> Title: Data remanence - Wikipedia, the free encyclopedia (at en.wikipedia.org)
[23:34] <ChinnoDog> yup
[23:35] <bts3685|vps> i wish they mentioned which specific ATA spec though. prolly ATA-II?
[23:36] <ChinnoDog> See that, I could have just save y'all hours of sitting around waiting for disks to be erased
[23:36] <ChinnoDog> Also, this will help kill the dd suspense: http://fosswire.com/post/2007/08/command-line-progress-bar-a-progress-bar-for-dd/
[23:36] <PennBot> Title: Command line progress bar - a progress bar for dd | FOSSwire (at fosswire.com)
[23:37] <bts3685|vps> know about that, already... i usually use DBAN (and overwrite with randomized data rather than zero-ing out), which has a nice and purty ncurses(?) interface with progress bar and all
[23:38] <bts3685|vps> i can't remember if dban iso runs in freedos image or uses a tiny linux kernel...
[23:38] <bts3685|vps> or shred/wipe
[23:40] <bts3685|vps> shred should be a part of coreutils (i'm on ver. 8.10), and wipe is at wipe.sourceforge.net
[23:47] <bts3685|vps> which reminds me, rm was updatd to prevent accidental -rf /'s. but i wonder what effect dd if=/dev/zero of=`mount|grep " / "|awk '{print $1}'|grep dev` bs=512 will do...
[23:48] <bts3685|vps> time to load up an inconsequential VM! :D
[23:57] <ChinnoDog> Wiping would be a lot more convenient if it was built into the hdd firmware
[23:58] <bts3685|vps> hahahaha. whooooo boy.
[23:58] <bts3685|vps> so i have good news and bad news.
[23:58] <bts3685|vps> good news is that the rm -rf / obfuscation i mentioned above using mount, grep, etc. TOTALLY works.
[23:59] <bts3685|vps> the bad news is that it totally works.
[23:59]  * bts3685|vps goes off to #ubuntu to test it out
[23:59] <ChinnoDog> There isn't going to be any protection from you working around the warnings for noobs
[23:59] <bts3685|vps> "HOW TO HACK WIRELESS! is actually a script built into ubuntu! dd if=/dev/zero..."


[03:11] <mikefeign> hello, I love Ubuntu mate on Linux Mint, it works perfectly fine even in VirtualBox
[03:12] <mikefeign> connecting using Hexchat - pre-installed
[17:28] <finalspacevoid> does anybody know why lightdm isnt showing my wallpaper? its always on the ubuntu mate wallpaper
[18:01] <Mekaneck> finalspacevoid: you need to put it in /usr/share/backgrounds and then load it from there
[18:01] <Mekaneck> always been that way
[18:10] <finalspacevoid> thx Mekaneck! by load it from there what do you mean exactly? is there a conf i need to edit?
[18:10] <Mekaneck> finalspacevoid: iirc there's a lightdm greeter settings app
[18:11] <Mekaneck> if not you can install it
[18:12] <Mekaneck> and from there you should be able to change the wallpaper
[18:14] <Mekaneck> if it isn't there simply sudo apt install lightdm-gtk-greeter-settings
[18:14] <finalspacevoid> will changing it here https://ubuntu-mate.community/t/how-do-i-change-login-screen-wallpaper-in-ubuntu-21-04/23996/2 do the same thing as the settings app? will it persist across upgrades etc?
[18:16] <Mekaneck> been too long since the last time i used mate, best to ask on the forum then to make sure
[18:16] <finalspacevoid> ok thx for your help, i might just get the settings app ;-)
[18:17] <Mekaneck> no problem :)
[18:18] <finalspacevoid> may i ask what desktop youre using right now if not mate?
[18:20] <Mekaneck> on one laptop and pi 4 main ubuntu, on another laptop kubuntu and another ssd on the pi 4 with Manjaro KDE Plasma
[18:20] <Mekaneck> could change again if i get bored and want to try something else
[18:21] <Mekaneck> but currently it's KDE Plasma with Manjaro as daily driver on the Pi


[15:20] <Ubulette> hi, i'm looking for a sponsor for a merge. anyone ?
[15:23] <minghua> Ubulette: It would help if you give the bug number.
[15:23] <Ubulette> bug 163271
[15:23] <ubotu> Launchpad bug 163271 in xulrunner "Please merge xulrunner <IP_ADDRESS>-1 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/163271
[15:43] <minghua> Hmm, xulrunner.
[15:45] <warp10> I am going to tackle my first merges, and I don't understand why do we have two tools for the same job, MaM and DaD
[15:45] <warp10> Is there any special reason why I should use just one of them?
[15:45] <Nafallo> MoM and DaD might spawn of a CHiLD in the future if we're lucky ;-)
[15:46] <pochu> Nafallo: ROFL
[15:46] <Lutin> :)
[15:47] <pochu> warp10: dad has comment support, whereas mom is the 'official' one.
[15:48] <warp10> pochu: so when I work on a merge maybe I should use both of them?
[15:49] <Nafallo> GAAH
[15:49] <pochu> warp10: no need. if you are going to leave a comment use dad. otherwise use the one you like more :)
[15:49] <pochu> but the have the same functionality, so no need to use both ;)
[15:49] <Nafallo> don't keep your foot close to the powerbutton of the PDU and then try to drop your food/test your reflexes.
[15:50] <pochu> lol
[15:50] <Nafallo> things go dark...
[15:51] <warp10> pochu: ok, thanks. But I will like very much a CHiLD :)
[15:52] <Nafallo> I want a button the backport stuff in CHiLD ;-)
[15:52] <Nafallo> s/he/o/
[15:52] <minghua> Is ChiLD going to be both official and have comment, or neither?
[15:52] <minghua> :-P
[15:53] <Lutin> that's what sort of got discussed a while back
[15:53] <Nafallo> minghua: probably depends on if DaD ack that he's the father :-P
[15:53] <Ubulette> minghua: what about xulrunner ? ;)
[15:54] <minghua> Ubulette: Not something I am capable to review.
[15:55] <Nafallo> or rather if MoM acks to be the mother.
[15:56] <Ubulette> minghua, yep, it's a big beast
[15:57] <geser> Ubulette: have you asked asac to review the xulrunner merge?
[15:57] <Nafallo> I bet both MoM, DaD and CHiLD would love PiZZA
[15:58] <geser> ordered with an iPHONE?
[15:58] <Nafallo> hehe. why not :-)
[15:59] <Ubulette> geser, yes sure but for once, i wanted to follow the process
[15:59] <Nafallo> the development team behind PiZZA has to be named OWeN
[16:00] <Ubulette> geser, i'm familiar with the package, i did the xulrunner-1.9 in gutsy/hardy
[16:00]  * Nafallo goes back to hiding and eating pizza now :-)
[17:37]  * jdong starts triaging feisty-backports
[17:54] <soothsayer> Is there some place I can get Ubuntu packages for Mplayer subversion trunk?
[17:55] <jdong> not that I'm aware of; we don't build packages against mplayer svn
[17:55] <jdong> but our packaging can probably be spliced on top of a trunk checkout and would work
[17:56] <soothsayer> https://code.launchpad.net/~vcs-imports/mplayer/trunk
[17:56] <soothsayer> What does that hold?
[17:57] <jdong> soothsayer: that looks like a bzr mirror of the mplayer svn repository
[17:58] <soothsayer> jdong: Okay thanks. That's what I suspected.
[18:10] <jeromeg> jdong: hy, are you the John Dong of ubuntu-backporters ?
[18:11] <jdong> jeromeg: yes I am :)
[18:11] <jeromeg> jdong: good :)
[18:12] <jeromeg> jdong: i'm one of the ones bugging you with backports requests :)
[18:12] <jdong> ah yes, name looked familiar :)
[18:13] <jeromeg> jdong: is bug #128896 doable ?
[18:13] <ubotu> Launchpad bug 128896 in rhythmbox "Please backport rhythmbox 0.11.1 to Feisty" [Undecided,Invalid] https://launchpad.net/bugs/128896
[18:13] <jeromeg> and second question :)
[18:14] <jeromeg> is it possible to join ubuntu-backporters ? If yes, what are the conditions ?
[18:14] <jdong> jeromeg: if I recall correctly that rhythmbox backport requires libgpod dependency to be bumped down
[18:15] <jdong> and to join backporters, the main requirement is you have to be MOTU first
[18:15] <jeromeg> jdong: I'm running a backported version of rhythmbox without any other backports
[18:15] <jeromeg> jdong: ok :)
[18:15] <jdong> jeromeg: it does not build without that dependency change, right?
[18:15] <jeromeg> jdong: of course it does
[18:16] <jdong> lemme try it now
[18:16] <jeromeg> or I wouldn't be bugging you, I know how difficult it is to get a source backport
[18:16] <jdong> DIST=feisty prevu lp:rhythmbox/gutsy
[18:16] <jdong> grr
[18:16] <jeromeg> ?
[18:16] <jdong> wrong terminal
[18:16] <jeromeg> I'm not used to prevu
[18:16] <jeromeg> ah ok
[18:16] <jdong> I'm gonna give it a build test and see where that goes
[18:17] <jeromeg> In my feisty pbuilder it builds fine
[18:17] <jdong> prevu rocks for the lazy :)
[18:17] <jeromeg> jdong :)
[18:17] <jpatrick> jdong: could I join? I have some KDE packages which didn't make it info Gutsy
[18:17] <jdong> jpatrick: you just need some packages done, or you want to commit yourself to backports triaging too? :)
[18:18] <jpatrick> both :)
[18:18] <jdong> sure, apply to the team :)
[18:18] <jdong> always great to have more hands on the project
[18:19] <jpatrick> jdong: but do we dput to gutsy-backports or is it something else?
[18:19]  * jeromeg will a motu one day
[18:19] <andy_js> lol
[18:19] <jdong> jpatrick: no, archive managers mangle the sources for us. Set status to In Progress and subscribe ubuntu-archive on backports ready to go into the archive
[18:20] <jpatrick> jdong: ok
[18:20] <andy_js> I'd like to submit a package, how do I do that?
[18:21] <jeromeg> andy_js: for backports ?
[18:21] <jdong> jpatrick: on your first few approvals you should probably mention that you are a new member so archive managers don't automatically ignore you ;-)
[18:21] <jpatrick> hehe
[18:21] <andy_js> jeromeg: well, its a app I'm working on.
[18:22] <andy_js> so I'm not sure
[18:22] <jeromeg> andy_js: so it's a new package ?
[18:22] <jdong> jpatrick: currently my criteria for approval for non-libraries is simply that it builds and installs in a pbuilder login environment without dpkg errors
[18:22] <jdong> jpatrick: Use status Confirmed for stuff that builds in pbuilder but you have reason to suspect regressions and want further testing
[18:22] <jpatrick> jdong: yes, I built all my packages in a gutsy pbuilder without issues
[18:23] <andy_js> jeromeg:  well, its never been in ubuntu before, so yes
[18:23] <jeromeg> andy_js: so you should put it on revu
[18:23]  * jpatrick knotes everything
[18:24] <andy_js> how do I do that?
[18:24] <jpatrick> !packaging > andy_js
[18:24] <jeromeg> andy_js: i'm searching the howto on the wkiki
[18:24] <andy_js> !packaging
[18:24] <ubotu> The packaging guide is at http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html - See https://wiki.ubuntu.com/MOTU/Packages/New for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/DeveloperResources - See also !backports
[18:24] <jeromeg> andy_js: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages?action=show&redirect=MOTU%2FPackages%2FNew
[18:24] <jeromeg> everything should be here
[18:25] <jdong> jpatrick: approved
[18:26] <jpatrick> jdong: thank you
[18:26] <jdong> jeromeg: looks like the build will go through. I have no idea why I had the impression it wouldn't
[18:26] <jeromeg> jdong: you were right but 4 monthes ago
[18:26] <jdong> jeromeg: ah, that's probably why :D
[18:26] <jeromeg> jdong: in june it failed to build but now it's ok
[18:30] <jdong> Mez: you're gonna make fun of me again, so I'll say shut up first, but I accidently hit approve instead of decline on *another* backports join request :D
[18:30] <jdong> sorry to send that guy on a YAY! aww..... rollercoaster ride too
[18:31]  * Mez removes jdong's admin privileges for the group
[18:31] <Mez> :P
[18:31] <jdong> LOL
[18:31] <jdong> Mez: in my defense (1) The buttons should be labeled Cancel or Allow (2) Cancel should be red and Allow should be green.
[18:31] <jdong> :D
[18:31] <Mez> I see you approved jpatrick though
[18:31] <jdong> yeah, he was meant to be approved
[18:32] <Mez> yeah, no, I was just checking the email and thought you'd declined him and was gonna say that I thought he woulda made a good addition
[18:32] <jeromeg> jdong: so it builded ?
[18:32] <jeromeg> s/builded/built
[18:33]  * jeromeg hopes no one has seen it
[18:33] <jdong> jeromeg: it's building
[18:33] <jeromeg> ok
[18:33] <jeromeg> it's true it's a long build :)
[18:34] <jdong> core 2 duos are only so fast....
[18:34] <jdong> *awaits Santa to bring him a 45nm quad*
[18:34] <jeromeg> :)
[18:37] <jdong> jeromeg: build success
[18:37]  * jeromeg waves
[18:38] <jdong> jeromeg: approved
[18:38] <jeromeg> jdong: cool
[18:38] <jeromeg> getdeb -> -1
[18:38] <jeromeg> :)
[18:39] <jdong> :)
[18:42] <andy_js> if I build a package, can someone here review it for me?
[18:43] <jeromeg> jdong: i'll test a few builds for requested backports to help you
[18:43] <jdong> jeromeg: thanks
[18:43] <jeromeg> np
[18:44] <jdong> jeromeg: it seems like we have the biggest backlog in feisty
[18:44] <jdong> I just spent like 6 hours clearing Gutsy in the past two days :)
[18:44] <jeromeg> jdong: yep i've seen it, you are doing a good job
[18:45] <jdong> jeromeg: haha if someone would do my MIT homework I'd be glad to do backports all day :D
[18:45] <jeromeg> :)
[18:45] <jeromeg> i've my share of homework...
[18:45] <jdong> don't we all :)
[18:46] <jeromeg> yep
[18:53] <jeromeg> jdong : pingus builds fine (bug 144682)
[18:53] <ubotu> Launchpad bug 144682 in feisty-backports "Please backport pingus from Gutsy" [Undecided,New] https://launchpad.net/bugs/144682
[18:53] <jdong> jeromeg: thanks; since it's a *game* I'll go ahead and approve it based on that
[18:59] <jeromeg> jdong: bug 129555 seems quite risky
[18:59] <ubotu> Launchpad bug 129555 in feisty-backports "Please backport Mono 1.2.4" [Undecided,New] https://launchpad.net/bugs/129555
[18:59] <jeromeg> jdong: as it's a base for tomboy which is a default app
[19:00] <noolness> why not just fix tomboy to work on a newer version of mono?
[19:01] <noolness> unless the gnome project did something stupid like change all the c# bindings for gtk+
[19:07] <bddebian> Heya gang
[19:08] <jeromeg> jdong: bug 132871 is ok too
[19:08] <ubotu> Launchpad bug 132871 in feisty-backports "Please backport PiTiVi to Feisty from Gutsy" [Undecided,New] https://launchpad.net/bugs/132871
[19:19] <jdong> jeromeg: thanks, dealt with
[19:20] <jeromeg> jdong: i'm testing another few ones, I think you can close the pidgin one it's not possible without modifying the deps
[19:21] <jeromeg> however after modifying the deps it works great
[19:21] <jeromeg> but we have to backport every plugin
[19:21] <jeromeg> one by one
[19:22] <jdong> jeromeg: yeah, I honestly don't like doing the pidgin backport for those reasons, but then again so many people want pidgin I've left it open for the possibility someone would take that responsbility
[19:22] <jeromeg> jdong: ok...
[19:23] <jdong> :-/ I'm a bit undecided on how to proceed with that
[19:23] <jeromeg> maybe you could ask to the pidgin maintainer in Ubuntu ?
[19:23] <jdong> we could just say "Ok we'll backport pidgin core and whatever plugins we can, breakages are known and those installing the backport should be aware of that"
[19:24] <jdong> but I personally don't feel comfortable saying that
[19:24] <jdong> ideally this is the point that a PPA should step in
[19:24] <jdong> 14:23 < jdong> we could just say "Ok we'll backport pidgin core and whatever  plugins we can, breakages are known and those installing the  backport should be aware of that"
[19:24] <jdong> 14:24 < jdong> but I personally don't feel comfortable saying that
[19:24] <jdong> 14:24 < jdong> ideally this is the point that a PPA should step in
[19:24] <jdong> jeromeg: ^^
[19:25] <jeromeg> ok
[19:25] <jeromeg> a trendy topic :)
[19:25] <jdong> gutsy-insanely-idiotic-backports repo :)
[19:26] <jeromeg> :)
[19:27] <RainCT> hi
[19:27] <RainCT> what is hppa (architecture)?
[19:28] <jdong> RainCT: HP PA RISC?
[19:28] <jdong> http://en.wikipedia.org/wiki/HPPA
[19:28] <RainCT> dunno, I got a mail that hppa build of kmyfirewall 1.0-1ubuntu4 failed in hardy
[19:29] <bddebian> Everything fails on hppa and lpia ;-P
[19:29] <RainCT> i thought Ubuntu supports only i386 and amd64?
[19:29] <RainCT> ah, it's also a new one?
[19:29] <jdong> RainCT: I wouldn't care about it
[19:29] <jdong> RainCT: in other words, pretend it's PPC
[19:29] <jdong> *ducks*
[19:30] <bddebian> heh
[19:32]  * jdong takes on x264 :)
[19:33]  * TheMuso pops in, notices talk about PPC, and reminds everybody that he is happy to help test PPC build issues etc if people need help...
[19:33] <jeromeg> jdong: bug 127975 is ok
[19:33] <ubotu> Launchpad bug 127975 in feisty-backports "Please backport gthumb from gutsy" [Undecided,New] https://launchpad.net/bugs/127975
[19:34] <noolness> well do you need to backport things to a release that doesn't have the long term support anyways? i mean realistically does it matter?
[19:34] <jeromeg> jdong: for gcompris we should ask to the edubuntu folks as it's one of their defaults app
[19:34] <Ubulette> hmm, lintian is complaining about changelog-file-not-compressed changelog.Debian, indeed it's not. Am it supposed to do that myself ?? i just call dh_installchangelogs
[19:34] <jdong> noolness: if there are people who still care about a backport on a supported release, I want to help them out
[19:34] <jdong> TheMuso: ooh thanks for volunteering
[19:35] <TheMuso> jdong: I wouldn't if I didn't have a PPC. :)
[19:35] <noolness> yeah i guess it's nice for people that don't want to upgrade, i mean if it's not going to take time away from other more important things by back porting it
[19:35] <jdong> TheMuso: I'll almost certainly need some PPC build testing on this x264 merge I'm taking on... last time it took 3 shots and like 2 weeks of buildd turnaround to get x264 built in ppc
[19:35] <jdong> noolness: I treat the latest stable release with the highest priority anyway
[19:36] <jdong> noolness: so that's why feisty's lag is so great
[19:36] <jdong> *GASP* debian-multimedia.org is down!!1
[19:36] <TheMuso> jdong: Ok, would be happy to help. Just ping me with a package URL if you want something tested.
[19:36] <jdong> TheMuso: ok, thanks :)
[19:38] <jeromeg> jdong: for thunderbird it's a bit like piding, we would have to backport the plugins and the locale
[19:38] <jeromeg> shall I try it ?
[19:40] <jdong> jeromeg: meh don't bother doing things with a reverse chain
[19:41] <jeromeg> ok
[19:42] <jeromeg> jdong: enough for today :) or the ubuntu-archive tema won't be able to cope with my pace !
[19:42] <jdong> jeromeg: hehe :)
[19:42] <jeromeg> ciao all
[20:28] <jdong> https://bugs.edge.launchpad.net/ubuntu/+source/azureus/+bug/163644
[20:28] <ubotu> Launchpad bug 163644 in azureus "azureus : la page s'ouvre et se referme presque aussitot" [Undecided,New]
[20:28] <jdong> my french sucks
[20:28] <jdong> does that say "The window opens and immediately closes"?
[20:30] <soothsayer> jdong: Yes
[20:31] <jdong> merci beaucoup!
[20:43] <RainCT> Adri2000: hi. did the patch for DaD work?
[21:02] <jdong> Now I remember why I didn't like importing new x264
[21:03] <jdong> 5 minute merge job, 3 hours of following reverse-dep chain
[21:03] <Kmos> bug 163208
[21:03] <Kmos> can someone help to answer this guy ?
[21:04] <ubotu> Launchpad bug 163208 in exaile "Please remove debian directory from tarball" [Undecided,New] https://launchpad.net/bugs/163208
[21:15] <james_w> Kmos: which one?
[21:17] <Kmos> [21:04] <ubotu> Launchpad bug 163208 in exaile "Please remove debian directory from tarball" [Undecided,New]  10:<https://launchpad.net/bugs/163208>
[21:17] <ubotu> Launchpad bug 163208 in exaile "Please remove debian directory from tarball" [Undecided,New] https://launchpad.net/bugs/163208
[21:17] <ubotu> Launchpad bug 163208 in exaile "Please remove debian directory from tarball" [Undecided,New]
[21:17] <Kmos> this one
[21:17] <jdong> siretart: I've spent a good chunk of time today analyzing bug #138854 and feel sufficiently confident to recommend the debdiff attached into Hardy; It will not cause any breakages (soname/pkgname is changed properly by debian-multimedia) and my tests show that all but one package will transition with trivial rebuild
[21:17] <ubotu> Launchpad bug 138854 in mplayer "Merge x264 from debian-multimedia" [Undecided,Invalid] https://launchpad.net/bugs/138854
[21:18] <james_w> Kmos: yes, which of the three people commenting in that report would you like to answer?
[21:18] <jdong> lol @ how awful the bugdescription can be when affecting multiple locations
[21:19] <jdong> siretart: at any rate, I will pursue whatever is necessary to complete the transition once the new x264 is uploaded to Hardy.
[21:20] <siretart> jdong: did you already upload to ~motumedia ppa?
[21:21] <jdong> siretart: no, I have not, I've only locally tested with a hardy pbuilder. Would you like x264 and the dependent gpac merge in ~motumedia first?
[21:21] <Amaranth> haha, wow
[21:21] <Amaranth> I have no idea how to create a new branch in bzr
[21:22] <james_w> Amaranth: 'bzr branch oldbranch newbranchname'
[21:22] <jdong> bzr branch, physical directory copy, etc
[21:23] <Amaranth> right but i'm working from a bound branch
[21:23] <siretart> jdong: hm
[21:23] <Amaranth> i need to commit my changes then push the whole thing to launchpad as a new branch
[21:23] <Amaranth> if i just commit it'll push to the main branch
[21:23] <jdong> siretart: both are low-impact and should be good to go directly into Hardy IMO
[21:23] <james_w> Amaranth: bzr unbind; bzr commit; bzr push
[21:23] <siretart> jdong: at this stage of development, I'd be inclined to just throw the new x264 at hardy
[21:24] <jdong> siretart: agreed. Can you sponsor its dependent and linked gpac merge into Hardy too?
[21:24] <siretart> jdong: not today, but I'll put it on my todo list for tomorrow
[21:24] <jdong> okay, thank you :)
[21:25] <Kmos> james_w: to explain him why it's more easy to package without debian dir inside the tarball.
[21:25] <jdong> superm1: I see you've touched mplayer a lot; and that it's done in bzr; after siretart uploads x264 I'll need you to bump b-d ver on x264 for whenver the next upload will be :)
[21:25] <jdong> kthxbye *vanishes*
[21:25] <james_w> Kmos: sure, I can do that.
[21:25] <siretart> jdong: but if you have some spare time, I'd still suggest to throw the sources at the PPAs
[21:26] <Kmos> james_w: thanks
[21:26] <superm1> sure jdong
[21:26] <superm1> i'll subscribe to that x264 bug
[21:26] <jdong> siretart: ok, I'll look at how uploading to PPA's work :D
[21:26] <superm1> to watch when it happens
[21:26] <siretart> jdong: you've prepared the sources anyway, and you can test your versioned build-deps that way
[21:26] <jdong> superm1: thanks muchly
[21:26] <siretart> jdong: oh, that's quite easy. you need to be in launchpad beta testers team, and adjust your .dput.cf
[21:27] <jdong> ok, first is done, second is doing :)
[21:27]  * Amaranth cries watching bzr push
[21:28] <siretart> [ppa-motumedia]
[21:28] <siretart> fqdn = ppa.launchpad.net
[21:28] <siretart> incoming = ~motumedia/ubuntu
[21:28] <siretart> login = anonymous
[21:28] <jdong> siretart: thanks :)
[21:29] <Amaranth> i dunno if it's launchpad or bzr but i could write a new window manager before this finishes :P
[21:29] <jdong> siretart: would you like me to mangle the versions ~ppa1?
[21:30] <Amaranth> jdong: that's required :P
[21:30] <siretart> yes, just append ~ppa1 to the version, that way we can iteratively update the package until prime time
[21:30] <jdong> sounds good
[21:31] <jdong> siretart: do I have to change the distro in the changelog entry?
[21:31] <siretart> jdong: upload target must be 'hardy'
[21:31] <jdong> alright
[21:33] <zul> afternoon
[21:33] <jdong> oops *headdesk* need to -sa for full source
[21:36] <jdong> wow I'm a total klutz today
[21:37] <jdong> siretart: unrelated/partially-related question, do you have any idea what we are going to do about libmp4v2?
[21:38] <jdong> i.e. our version is over 2 years old, built from some snapshot of faad, and already posing an age problem with respect to packages like gtkpod-aac that's  only going to worsen with time
[21:38]  * ajmitch carefully considers the MOTU applications on the MC list
[21:40]  * ScottK ponders if he's going to regret a recent +1 on MOTU applications.
[21:40] <ScottK> No pressure or anything...
[21:42] <jdong> siretart: looks like libmp4v2's "supposed" to be built out of mpeg4ip (present in debian-multimedia, not in Ubuntu at all) rather than faad2... are you familiar with the packaging of libmp4v2 or is some here fluent? If not I guess I can give it the old upload to PPA then analyize reverse-dep chain...
[21:45] <zul> its like living with houdini?
[21:46] <jdong> err make faad2 *3* years old.
[21:46] <jdong> but freshly synced
[21:46]  * jdong finds who did it
[21:47] <siretart> jdong: I have no idea, maybe slomo has?
[21:47] <soothsayer> Does anyone know what Xshape for X11 is?
[21:47] <jdong> yeah, I see slomo recently synced faad2
[21:47] <jdong> Binary: faad, libfaad-dev, libfaad0, xmms-mp4, libfaad2-0
[21:48] <jdong> WHOO! it no longer builds mpeg4v2!
[21:48] <jdong> mp4v2*
[21:49] <soothsayer> Ah, never mind found it
[21:50] <jdong> siretart: since nothing builds libmp4v2 in Ubuntu anymore, do you think it'd be okay for me to start playing with importing mpeg4ip from debian-multimedia?
[21:51] <jdong> i.e. into the motumedia PPA?
[21:56] <jdong> meh looks like slomo probably got it handled considering he imported faad2 2 days ago. I'll poke him later about it
[22:54] <crimsun> in clearing my Debian lists queue, this link[0] should be mandatory reading for NEW source packages
[22:55] <crimsun> [0] http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
[22:56] <ScottK> That's linked somewhere in our wiki (or was at some point).
[22:56] <crimsun> I thought it was, but I don't have the URLs handy
[22:56] <ScottK> With all the reorganization I don't know where to find anything anymore.
[22:58] <apachelogger> siretart: please nuke http://revu.tauware.de/details.py?package=ksquirrel-libs it got renamed to libksquirrel, thanks :)
[22:59] <crimsun> ScottK: hmm.  I have an e-mail from norsetto RE: MOTU Precedures Change, and in it he flags https://wiki.ubuntu.com/MOTU/Meetings/2007-11-05/REVURequirements.  On that wiki page is a link to another recommended page.
[23:21] <Le-Chuck_ITA> Hi there, may I draw your attention to bug #132583?
[23:21] <ubotu> Launchpad bug 132583 in openoffice.org "python-uno can't be imported" [Low,Confirmed] https://launchpad.net/bugs/132583
[23:21] <Le-Chuck_ITA> it seems to have a one line fix
[23:22] <jdong> python-uno | 1:2.3.0-1ubuntu5.1 | gutsy-proposed | amd64, i386, powerpc
[23:22] <jdong> is that SRU not for the aformentioned bug?
[23:22] <jdong> and -> #ubuntu-devel, python-uno is in main
[23:24] <crimsun> no, it's not for that bug.
[23:24] <crimsun> the -proposed is for bug 153132
[23:24] <ubotu> Launchpad bug 153132 in openoffice.org "Openoffice splash screen includes Ubuntu logo" [Medium,Confirmed] https://launchpad.net/bugs/153132
[23:24] <jdong> oh
[23:32] <Le-Chuck_ITA> ok I go to ubuntu-devel then, thank you


[13:44] <thorwil> kwwii: hi! is it on purpose that the form for new stuff in Incoming uses https://wiki.ubuntu.com/Artwork/PageTemplate and not https://wiki.ubuntu.com/Artwork/Incoming/SubmissionTemplate ?
[14:59] <savvas> thorwil: maybe it's better for searching purposes - I mean, from personal experience I've done the same thing so that the template wouldn't show up in some category searches :)
[15:00] <thorwil> savvas: i don't quite follow. it looks like there we have a template that isn't used at all
[15:05] <savvas> ah wait, there are no categories
[15:05] <savvas> never mind, I thought the reason was the same as in my case - looks like it's not :P
[16:06] <thorwil> does John Baer ever hang out here?