[02:15] <e-jat> fta : is there any issue for chromium with flash in <IP_ADDRESS> (23528) build?
[06:23] <micahg> sure
[10:06] <asac> ola
[10:07] <andv> hi asac!
[10:07] <andv> how was your weekend?
[10:15] <asac> all good
[10:15] <andv> went to the sea?
[10:15] <andv> or city?
[10:16] <asac> i am in the middle of the city ;)
[10:16] <andv> oh :D
[10:16] <andv> I've sent you a mail with some details
[10:17] <asac> no time right now ... talk to you later
[10:17] <andv> like 2-3 days ago don't remember
[10:17] <andv> yeah, np :)
[10:17]  * asac fights tb
[10:18] <andv> tb = technical board?
[10:18] <asac> tbird
[10:18] <andv> ooh :)
[10:18] <andv> asac, anyway ffox rocks now
[10:18] <andv> I've installed all upgrades
[10:18] <andv> and everything seems to work great atm
[10:18] <andv> same thing for latest tb
[10:40] <mac_v> asac: hi... could you look at this > Bug #413950
[10:41] <asac> one moment please
[10:41] <mac_v> no problem
[10:43] <asac> mac_v: i dont see any cursor when dragging in a lp comments field
[10:43] <mac_v> the cursor,on grab,is always higher than the pointer :( , this is different from other apps where the cursor is always closer to the pointer , this is only in firefox3.5 not in fireofx3.0 , earlier i thought that the cursor was wrong throughout the system and didnt report it, but works well elsewhere even in firefox 3.0
[10:44] <asac> mac_v: i have some similar report against tbird
[10:44] <asac> s/i/we/
[10:45] <asac> like you drag and drop mails to a folder and it highlights something completely offset (higher)=
[10:45] <asac> mac_v: anyway. i dont even see any cursor atm ;)
[10:45] <asac> thats what i tried to say
[10:45] <mac_v> actually you are supposed to see the cursor , if you type several lines, greater than 3 , you'll notice the problem
[10:46] <mac_v> just copy paste in the comments field
[10:46] <asac> yes ok i see it
[10:46] <asac> mac_v: can you check upstream build and when you see it there, please forward upstream?
[10:46] <asac> ;)
[10:47] <mac_v> asac: but notice the drag while in bookmarks , [not in organize] , just the drop down , the cursor alligns properly
[10:47] <mac_v> upstream build? i'm sorry i have several other bugs as of now , i dont want firefox to be messed up either
[10:47] <asac> mac_v: probably a different beast
[10:48] <mac_v> s/either/also
[10:48] <asac> mac_v: its mostly riskfree to run upstream tarball
[10:48] <mac_v> hm...ok .. which build do you recommend? could you give me a version?
[10:50] <asac> mac_v: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/3.5.2/linux-i686/en-US/firefox-3.5.2.tar.bz2
[10:50] <asac> just unpack it in your home
[10:50] <asac> to be extra safe, backup your $HOME/.mozilla directory
[10:51] <mac_v> already backed up ;)
[10:53] <asac> good
[11:15] <asac> https://answers.edge.launchpad.net/soyuz/+question/80227
[11:17] <fta2> thanks
[11:19] <andv> asac, what's the bindwood status atm?
[11:19] <andv> asac, I can take care of maintaining it if you want
[11:19] <andv> is it ubuntu-specific or can be uploaded in debian as well?
[11:27] <asac> have a call now ... talk to you in ~1h
[11:27] <andv> k perfect
[13:07] <bdrung_> asac: can you have a look at https://code.launchpad.net/~bdrung/firefox-extensions/new-upstream-release-1.1.1/+merge/10049
[13:53] <fta2> asac, wrt https://code.launchpad.net/~jdstrand/firefox/firefox-3.5-apparmor/+merge/10109, a/ it doesn't follow our d/changelog style and b/ there's no profile at all?? so it's not doing anything..
[13:59] <asac> fta2: ok thanks. i asked to resubmit with profile
[14:08] <asac> bdrung_: looks good. what about debian?
[14:09] <asac> bdrung_: hmm. the tagging feels a bit wrong
[14:10] <asac> bdrung_: so maybe oneshouldnt do a release commit on the topic branch
[14:10] <asac>  bzr tags
[14:10] <asac> 1.1-0ubuntu1         47
[14:10] <asac> 1.1.1-0ubuntu1       47.1.4
[14:10] <asac> e.g. it doesnt really refer to the real revision that goes up
[14:10] <asac> i will remove the tag and retagg the committed merge
[14:10] <asac> done
[14:11] <andv> asac, 3 things
[14:12] <andv> when you have a minute
[14:14] <andv> asac, first of all: https://code.edge.launchpad.net/~kvilhaugsvik/firefox-extensions/all-in-one-sidebar.ubuntu/+merge/8652
[14:14] <andv> then bindwood status
[14:14] <andv> then the mail I've sent you
[14:21] <asac> andv: yes i have it on my list. and will get back to you ... if not during day i will send a mail
[14:22] <andv> asac, ok great, I've sent you one more email like 3 minutes ago
[14:22] <andv> with another great news
[14:27] <mac_v> hmm... is there a way to backup fireox history? or to print the history?
[14:27] <mac_v> firefox* not OX! ;p
[14:33] <mac_v> asac: is it possible to backup/print-to-file history?
[14:40] <asac> mac_v: not sure what you mean
[14:42] <mac_v> asac: we can backup bookmarks , similarly web history? how can we same it? i have history for1 yrs and it slows down the browser when i open history , so i was thinking i could split it
[14:43] <mac_v> like how routers note down the history
[14:46] <mac_v> asac: hmm... i'v been able to save the history as bookmarks , can be print bookmarks?
[14:46] <mac_v> s/save/copy
[14:47] <mac_v> sheesh! so many typos! >  i'v been able to copy the history to bookmarks , can we print bookmarks?
[14:48] <asac> mac_v: i dont know why you would want to print bookmarks ;)
[14:48] <asac> so no ... i dont know how to do that. i guess there is an extension for that
[14:49] <asac> for history you can say how many days should be kept
[14:49] <asac> i would suggest to not keep more than 90 days
[14:50] <mac_v> i'v searched didnt find any so thought i'd ask sensei ;p
[15:01] <asac> mac_v: export html ... isnt good enough?
[15:01] <asac> oh you say for history
[15:01] <asac> yeah. i dont know then
[15:04] <mac_v> asac: hmm... ok ,i think i'm getting to find a workaround..  so I'v tried to save the history as bookmark , but its split up in last day/7days/1month... is there a way for the history to show all history? together
[15:06] <mac_v> where is the history file located actually?
[15:07] <asac> mac_v: thats in places.sqlite from what i know
[15:07] <mac_v> oh... :(
[15:18] <asac> jdstrand: hi ;)
[15:23] <jdstrand> o/
[15:28] <asac> jdstrand: did you forget the profile in the merge or was it codebrowse that failed to show "new" files?
[15:29] <jdstrand> asac: heheh
[15:29] <jdstrand> asac: I forgot
[15:31] <asac> jdstrand: ok. please resubmit and if possible use the same changelog format we use ;) ... if not i can shuffle that during merge
[15:31] <asac> i think its just "push" ;)
[15:34] <jdstrand> asac: ok, files added, changelog updated and it's all pushed to lp:~jdstrand/firefox/firefox-3.5-apparmor
[15:35]  * jdstrand hates it when he forgets to 'bzr add'
[15:35] <asac> hehe
[15:35] <asac> no problem
[15:36] <asac> ok will merge that after i get this tbird stuff done
[15:36] <jdstrand> asac: thanks! :)
[15:56] <fta2> asac, fyi, everything rejected for umd
[15:57] <fta2> oops, no, it's not today's batch
[15:59] <asac> fta2: heh?
[15:59] <fta2> nm
[15:59] <asac> you mean it took more than one day?
[15:59] <asac> ah ok
[15:59] <asac> oh you probably ment for space reasons
[15:59] <asac> yeah. lets wait a day and see if they bump our size
[16:15] <fta2> http://paste.ubuntu.com/254562/
[16:17] <fta2> http://paste.ubuntu.com/254563/
[16:48] <fta2> gaps, /tmp/builddeb-get-orig-source-63gvPk/export/chromium-browser-2225/src/webkit/...
[16:48] <fta2> bd now uses /tmp ??? bad
[17:13] <sveinung> hello. I'm still working on getting all-in-one-sidebar ready for Debian. I have some questions that I hope will be answered when you have time.
[17:13] <sveinung> asac: How should I set up the maintainer field? You mentioned team maintainance. Should I put myself in maintainer or uploader? Who else should I put in those fields?
[17:13] <sveinung> In what location should the bzr-tree be hosted? Is firefox-extensions/all-in-one-sidebar.debian OK? That will make it possible to still make separate changes to Ubuntu (like Ubuntu binMMUs). Since I don't have write access there I have temporarily put it in lp:~kvilhaugsvik/firefox-extensions/all-in-one-sidebar.debian
[17:14] <sveinung> ( https://code.launchpad.net/~kvilhaugsvik/firefox-extensions/all-in-one-sidebar.debian )
[18:00] <andv> sveinung, hi!
[18:00] <andv> asac, I've answered to your mail ;)
[18:01] <sveinung> hello
[18:01] <andv> sveinung, you know who i am?
[18:01] <andv> I reviewed/ sponsored all in one sidebar for you like 2 weeks ago
[18:01] <sveinung> I suspected that :)
[18:01] <andv> :)
[18:02] <andv> what's up?
[18:02] <sveinung> I'm trying to get it into Debian now
[18:02] <andv> I can maintain it with you
[18:02] <andv> if you want
[18:02] <sveinung> sure
[18:03] <andv> what did asac tell you?
[18:03] <andv> did he suggest something to you'
[18:03] <andv> sveinung, asac is pretty busy so ping me next time
[18:05] <sveinung> andv: ok
[18:05] <andv> sveinung, did he suggest you something already?
[18:06] <sveinung> I'm looking it up
[18:06] <sveinung> found it: http://irclogs.ubuntu.com/2009/08/13/%23ubuntu-mozillateam.html
[18:06] <sveinung> he said that it was OK to put the branch under firefox-extensions
[18:07] <sveinung> and "we want to jointly maintain it i guess"
[18:08] <andv> sveinung, actually you'll have to drop all changelog entries
[18:08] <andv> from Ubuntu
[18:08] <sveinung> why?
[18:08] <andv> because you are releasing a software in debian
[18:08] <andv> so the package must be clean
[18:08] <sveinung> it's still permitted to keep the changelog entries
[18:08] <andv> yes, but why keeping them?
[18:09] <andv> who cares?
[18:09] <andv> sveinung, you do the package again
[18:09] <andv> for debian
[18:09] <sveinung> andv: for example the script that imports debian packages into bazaar
[18:10] <andv> ?
[18:10] <andv> we gonna sync it
[18:10] <andv> when it's in debian
[18:10] <andv> so you gonna drop all entries anyway
[18:10] <andv> (changelog entries)
[18:10] <andv> I guess you know that a package which gets synced in ubuntu
[18:11] <sveinung> https://wiki.ubuntu.com/DistributedDevelopment/DebianImportSpecification
[18:11] <andv> loses all changelog entries
[18:11] <sveinung> I meant this
[18:11] <andv> I don't get what your problem
[18:11] <andv> you do the package in debian
[18:11] <andv> we will upload it
[18:11] <sveinung> I also think it's nice to keep that sort of data
[18:12] <andv> which data?
[18:12] <sveinung> the changelog entries
[18:12] <andv> if all changes are integrated
[18:12] <andv> you don't have to report those entries again
[18:12] <andv> how the changelog will look like?
[18:13] <andv> changes appears under unstable (by emanuele gentili for istance)
[18:13] <andv> and they never touched unstable ground
[18:13] <andv> before
[18:14] <sveinung> don't know if I will be able to formulate myself good enough in English right now
[18:14] <sveinung> but I'll try
[18:14] <andv> please explain me what's the rationale to keep them
[18:14] <andv> and I'll try to understand you
[18:15] <sveinung> It's just nice to have those entries since you then have a bit more history for the package in a machine readable format
[18:15] <sveinung> so you later can do things to those data
[18:15] <andv> those data?
[18:16] <andv> you can make changes to 'those data' without having those changelog entries
[18:16] <andv> I assume you merged all ubuntu changes into the future debian package
[18:16] <sveinung> for example the Ubuntu Distributed Importer, when creating a branch from a package, will check if there are Ubuntu entries to see what will come first
[18:16] <andv> removing changelog entries does NOT mean you have to remove the changes reported in them
[18:16] <sveinung> I know
[18:17] <andv> so, I don't get why we need to have those entries then
[18:18] <sveinung> It's not for us but for programs reding it. So one for example can see that the package originated in Ubuntu ()but don't get me wrong, I'm not fanatical about this
[18:18] <andv> you won't use the autogenerated branch anyway
[18:18] <sveinung> I know
[18:18] <andv> you gonna keep usinh YOUR branch
[18:18] <sveinung> it was just an example
[18:18] <andv> if you really wanna keep all changes reported in those entries
[18:19] <andv> integrate everything in ONE entry
[18:19] <andv> so together with * Initial release. (Closes: #000000)
[18:19] <andv> you'll add
[18:19] <andv> * modified watch file
[18:19] <andv> * modified debian/foo
[18:19] <andv> or whatever
[18:19] <andv> I hope you've understood a bit
[18:20] <andv> what integrating old entries mean
[18:20] <andv> old entries integrated in a main one which will be the initial release
[18:21] <andv> sveinung, another problem
[18:21] <andv> if you wanna keep those entries
[18:21] <andv> you'll have to license the packaging side
[18:21] <andv> which is useless and time-loss work
[18:21] <andv> you usually license your package under the same license as upstream it is
[18:21] <sveinung> last time they said it was already licensed
[18:22] <sveinung> since it wasn't specified it was assumed it was the same as upstrem
[18:22] <sveinung> *upstrem
[18:22] <sveinung> *upstream
[18:22] <andv> sveinung, look at the changelog
[18:23] <andv> apart from asac changes which seem to be relevant
[18:23] <andv> (and your ones)
[18:23] <andv> do you see any other important change?
[18:23] <sveinung> the initial packaging?
[18:23] <andv>   * debian/control:
[18:23] <andv>    + added Homepage field.
[18:23] <andv>    + Update Standards-Version.
[18:23] <andv> for istance
[18:23] <andv> are not so important to be added on the next debian package you're making
[18:23] <andv> or not?
[18:23] <andv> nono, the current version
[18:23] <andv> we have on karmic
[18:24] <sveinung> andv: I'm sorry. My head don't work right now. I need food, and to eat I have to go home. Could we take this on email?
[18:24] <andv> it will take ages on email I guess
[18:24] <sveinung> (I could try to talk a bit more if email isn't OK for you)
[18:25] <andv> give me branch url
[18:25] <sveinung> thank you wery much!
[18:25] <sveinung> https://code.launchpad.net/~kvilhaugsvik/firefox-extensions/all-in-one-sidebar.debian
[18:25] <sveinung> ooh, sorry
[18:25] <sveinung> misread
[18:26] <andv> can you tell me which debian-specific
[18:26] <andv> changes you did
[18:27] <sveinung> andv: the naming (no ubuntuX at the end)
[18:28] <sveinung> and putting myself as maintainer temporarily
[18:28] <andv> dependencies are now taken from xpi:depends
[18:28] <andv> I see
[18:28] <sveinung> the rest could apply to Ubuntu as well
[18:28] <andv> I gonna have my debian box ready soon
[18:28] <andv> so I can test it
[18:28] <sveinung> except the closes
[18:28] <sveinung> good
[18:28] <andv> I'll have to do some fixes
[18:28] <andv> to the packaging side
[18:29] <andv> then I have to check out lintian
[18:29] <andv> and other stuff
[18:29] <sveinung> one lintian warining will be fixed when mozilla-devscripts v 15 comes out
[18:30] <andv> sveinung, ok
[18:30] <sveinung> MOZ_XPI_DOCUMENTED_LICENSE_FILES is introduced in v 15
[18:30] <sveinung> should I commit and push the code that uses it?
[18:30] <andv> sveinung, so are you OK to cooperate with me maintaining this package?
[18:30] <sveinung> of course
[18:30] <andv> perfect
[18:30] <andv> you'll be the maintainer, I gonna add myself in the uploaders field as co-maintainer
[18:31] <sveinung> great
[18:31] <andv> so I've fixed asac a problem since he's busy doing his stuff
[18:31] <andv> do you own an itp bug already?
[18:31] <sveinung> yes
[18:31] <andv> ok perfect
[18:32] <andv> sveinung, is there a way I can work on your branch?
[18:32] <andv> actually just you is able to upload to that branch
[18:32] <sveinung> I know. It was just ment to be temporary
[18:32] <sveinung> feel free to change it
[18:33] <andv> is there a way to upload to a same branch?
[18:33] <sveinung> (the location)
[18:33] <andv> apart creating a new team
[18:33] <sveinung> I don't know
[18:34] <andv> I guess you can co-maintain a branch on teams only
[18:36] <sveinung> sorry, I don't undersatand
[18:36] <sveinung> *understand
[18:37] <andv> for co-maintaining a branch
[18:37] <andv> e.g both me and you can upload to it
[18:37] <andv> the only way is having a team
[18:37] <andv> I'll ask asac how can we do
[18:37] <sveinung> ok
[18:39] <andv> ok, going to prepare dinner
[18:39] <andv> be back later
[18:39] <sveinung> I'll to be back later
[19:39] <sveinung> andv: Now that I have gotten myself food and some fresh air I think I understand what you meant when we were talking about the changelog. Were you talking about doing the packaging again from scrach?
[19:40] <sveinung> As I said my head wasn't working 100% when I read it. I believed you talked about uploading the Ubuntu one.
[19:40] <sveinung> We can do it from scarch if you want to, and I agree that in that case we should drop the changelog entries.
[19:49] <andv> sveinung, yep
[19:49] <andv> that's what I meant
[19:50] <andv> sveinung, I have to go, be back in 3 hours if you are here
[19:50] <sveinung> sure
[19:50] <andv> see ya later
[19:50] <sveinung> And sorry about the misunderstanding. I had been on campus all day but since I forgot my money I hadn't eaten
[19:51] <sveinung> or taken breaks from the computer
[19:51] <BUGabundo> hi
[19:52] <pace_t_zulu> how's it BUGabundo?
[19:53] <BUGabundo> wit a dyeing PA
[20:03] <andv> sveinung, np
[20:04] <andv> sveinung, after we decide the branch location
[20:04] <andv> sveinung, we gonna start a brand new debian branch
[20:04] <andv> with a clean changelog
[20:04] <sveinung> k
[20:04] <andv> and with a working package for debian
[20:05] <andv> sveinung, do you have a box to test it too?
[20:05] <sveinung> yes
[20:05] <sveinung> I have lenny on my laptop
[20:05] <sveinung> og Squeeze on my stationary
[20:06] <sveinung> *and
[20:06] <andv> perfect
[20:06] <andv> build the package from the branch you linked me before
[20:06] <andv> install the package
[20:06] <andv> and test it on lenny
[20:07] <andv> * squeeze
[20:07] <andv> sorry
[20:07] <andv> not lenny
[20:07] <andv> test it on squeeze which is quite near to si
[20:07] <andv> * sid
[20:07] <andv> as build depends and so on
[20:07] <sveinung> sure
[20:07] <andv> and give me a feedback
[20:08] <andv> asac, do you know where we can host that branch?
[20:08] <andv> asac, do mozilla team have some space to host the all in one branch?
[20:10] <andv> sveinung, ok have to go
[20:10] <sveinung> andv: ok
[20:10] <andv> talk to you later and if asac gets back ask him about the branch thing
[20:11] <andv> asac, I've replied to your mail already
[20:11] <andv> ;)
[20:11] <andv> cya later
[20:11] <andv> and thanks for your work on this sveinung
[20:11] <sveinung> andv: thanks for co maintaining :)
[20:11] <andv> np
[20:11]  * andv off
[20:14] <fta> asac, could you please give me the branch urls, ppa names, etc, for the nm dailies so i can start it?
[21:18] <fta> asac, ... and the nickname you want.. nmd?
[22:08] <micahg> asac: are you around?
[22:09] <BUGabundo> he was , a few minutes agot
[23:11] <asac> fta: nmt?
[23:12] <BUGabundo> asac: still no reply from fta :)
[23:13] <asac> BUGabundo: he asked me something ... i answered ;)
[23:13] <andv> asac, did you read backlog?
[23:13] <andv> I've decided to co-maintain all in one sidebar with sveinung
[23:13] <andv> in debian
[23:13] <asac> andv: we usually use ~ubuntu-dev for extension
[23:13] <andv> problem is finding a place to host the branch
[23:14] <asac> and non -devs drive the branch by requesting merged that you can push or merge
[23:14] <asac> use ubuntu-dev ... thats the right place to put it
[23:14] <andv> are you sure?
[23:14] <fta> * Disconnected (Network is unreachable).
[23:14] <andv> it is meant for debian
[23:15] <asac> andv: it is ment for debian and then to be synched down afaik
[23:15] <andv> yep
[23:15] <asac> why have two branches?
[23:15] <fta> blank between 23:17 and 23:39
[23:15] <andv> you suggest to merge the existing one?
[23:15] <asac> andv: i have no clue about current status
[23:15] <andv> I added you as reviewer
[23:15] <andv> like 2 weeks ago
[23:15] <fta> asac, can you add the debian link please?
[23:15] <asac> andv: i think in a perfect world you have one branch that is for latest debian/ubuntu
[23:15] <asac> and when debian freezes you create a stable debian branch
[23:16] <andv> agreed
[23:16] <andv> I've sent you the review request
[23:16] <asac> andv: and if ubuntu freezes you crate a ubuntu stable branch
[23:16] <asac> etc.
[23:16] <asac> fta: i think that breaks stuff
[23:16] <andv> you have to accept it for the ubuntu-dev branch
[23:16] <andv> e.g sveinung merged it from his branch to ubuntu-dev one
[23:16] <fta> asac, ?
[23:16] <andv> but needs approval
[23:17] <asac> fta: the build bot cannot deal with debian only branches?
[23:17] <asac> hmm
[23:17] <asac> should have been obvious
[23:17] <bdrung_> asac: can you add a comment to https://wiki.ubuntu.com/BenjaminDrung/MOTUApplication ?
[23:17] <asac> bdrung_: i was going to ... when does that need to happen?
[23:18] <fta> asac, some parts of the bot expect debian/changelog, or debian/control
[23:18] <bdrung_> asac: application is on 27th August
[23:19] <bdrung_> so there is enough time
[23:19] <fta> asac, i call dch somewhere
[23:19] <asac> fta: yeah ... dch -c changelog is what we use
[23:19] <asac> but let me check
[23:20] <asac> i think i should give up on debian only then
[23:21] <andv> asac, do you suggest to merge the existing ubuntu branch or to create a new one?
[23:22] <andv> asac, if you wanna keep the old one, just have a look here: https://code.edge.launchpad.net/~kvilhaugsvik/firefox-extensions/all-in-one-sidebar.ubuntu/+merge/8652
[23:26] <asac> fta: ok moved all files to debian/ dir
[23:26] <asac> on applet and nm branch
[23:26] <fta> thanks
[23:26] <fta> asac, do you want/need chained deps?
[23:27] <fta> build-deps
[23:27] <asac> fta: for now i dont think we need it
[23:27] <asac> fta: if we need it ill let you know
[23:27] <asac> api moves slowely
[23:27] <fta> ok
[23:28] <asac> andv: ok checking the all-in-one branch
[23:28] <andv> asac, perfect thanks
[23:28] <andv> asac, if accepted I gonna move tomorrow to fix some stuff
[23:28] <fta> asac, you said "nmt", why t? i used nmd, but i can change
[23:28] <andv> then it will be ready
[23:29] <BUGabundo> fta: "(11:27:04 PM) cabrey: Native !chromium 64 being developed? http://is.gd/2lFfR !linux"
[23:29] <fta> BUGabundo, i don't need that, i already have the package ready
[23:30] <BUGabundo> I know
[23:30] <fta> i just don't want to break too many people so i'm waiting for it to be a little bit more usable
[23:30] <BUGabundo> that's what I told him
[23:30] <BUGabundo> btw, when will it it the PPA?
[23:32] <asac> fta: because we used nmt before for that repo
[23:32] <fta> asac, ok
[23:32] <asac> for me its Network-Manager Trunk -> ~network-manager/+archive/trunk
[23:32] <asac> andv: i am not so sure about the changelog addition of the 1.4.7-0ubuntu2
[23:32] <asac> are we sure we also have the changes done in that release?
[23:33] <BUGabundo> fta: FF3.7 started to stuck on FullScreen today
[23:33] <asac> hmm
[23:33] <andv> asac, the change was about adding a watch file plus adding homepage field on control?
[23:33] <asac> andv: ok seems ok
[23:33] <asac> andv: yes. but where did he merge it from?
[23:33] <andv> from the archive
[23:33] <asac> http://bazaar.launchpad.net/~kvilhaugsvik/firefox-extensions/all-in-one-sidebar.ubuntu/revision/25
[23:33] <asac> was there a contributor?
[23:33] <andv> yes
[23:33] <andv> a contributor added those
[23:33] <andv> without asking here
[23:34] <andv> but as I already said to sveinung
[23:34] <asac> no what i mean ... that commit is a [merge] so he must have merged it from somewhere
[23:34] <andv> the changelog will be cleaned
[23:34] <asac> but i am not sure where it came from
[23:34] <andv> so all those entries will be removed
[23:34] <andv> in debian
[23:34] <asac> andv: why will the changelog be cleaned?
[23:34] <asac> andv: thats not right.
[23:34] <asac> if you share them you keep them
[23:35] <andv> he integrated all changes
[23:35] <andv> so why adding all those entries?
[23:35] <asac> why not
[23:35] <andv> anyway he merged those changes from the package on archive
[23:35] <asac> its the same history
[23:35] <asac> no sense in keeping two branches
[23:35] <andv> a contributor uploaded that revision
[23:35] <andv> sveinung didnt notice it but I did
[23:35] <andv> and he added it
[23:35] <andv> together with the changes
[23:36] <andv> so it's not a real merge
[23:36] <andv> but just adding back lost changes
[23:36] <asac> i am not talking abouta real merge
[23:36] <asac> i am talking about a bzr merge
[23:36] <asac> its a _merge_ and i wonder where it comes from
[23:36] <asac> but doesnt matter. its ok
[23:36] <sveinung> asac: I did a bzr merge to add the missing revision
[23:36] <andv> how do you know it's a merge??
[23:37] <andv> sveinung, where did you take that?
[23:37] <andv> do that contributor have a branch somewhere?
[23:37] <sveinung> I branched from the version before
[23:37] <sveinung> then added the revision
[23:37] <sveinung> then merged it into the current revision
[23:37] <andv> you got it from the autogenerated branch right?
[23:37] <fta> asac, done
[23:38] <andv> I mean when you upload a package it gets synced as a branch
[23:38] <andv> coz I don't think that contributor opened a branch itself
[23:38] <andv> for all in one sidebar
[23:38] <sveinung> no, those are different trees
[23:38] <andv> I still don't get where you branched it
[23:38] <andv> from
[23:38] <andv> but anyway it doesnt matter
[23:39] <asac> sveinung: you did the right thing. really great. thanks
[23:39] <asac> i approved that merge. in future just use distinct topic names for oyur branches and not the same name as the ~uubuntu-dev branc hname
[23:39] <asac> i gave an example in the comment
[23:39] <asac> thanks
[23:40] <andv> asac, I gonna maintain it together with sveinung in debian
[23:40] <andv> if you are satisfied with it
[23:40] <sveinung> asac: sure, I'll remember that
[23:41] <asac> andv: i dont think there are two maintainers needed for an extension ;)
[23:41] <asac> just add yourself as an uploaders: and you can help sponsoring that stuff
[23:41] <andv> asac, yep
[23:41] <andv> that's what i wanted
[23:41] <andv> asac, I've answered to your mail
[23:42] <asac> sveinung: consider to use a .bzr-builddeb/default.conf for the next revision
[23:42] <asac> andv knows what it does
[23:42] <andv> yep gonna take care of it
[23:42] <andv> np
[23:43] <asac> andv: i added it now in the merge
[23:44] <asac> so it will be o n~ubnutu-dev
[23:44] <andv> great
[23:45] <andv> asac, I'll keep all changelog entries then
[23:45] <andv> didnt want to
[23:45] <andv> but I trust the way you wanna do it
[23:46] <asac> ok i pushed it ... you seem to have uploaded to archive without pushing a merge?
[23:46] <asac> thats bad practice
[23:46] <asac> you cannot upload something you didnt push ... or that is waiting another review
[23:46] <asac> anyway. i hope it was now really the same that is now on the branch
[23:46] <andv> ?
[23:46] <asac> andv: the version i just merged is already in karmic
[23:46] <andv> I took the uploaded package from the branch you merged right now
[23:47] <asac> andv: yes. but it might be different
[23:47] <andv> I hadnt access to that branch anyway
[23:47] <asac> never upload anything before it lands on the release branch
[23:47] <asac> andv: you had
[23:47] <asac> thats the whole point of having it in ~ubuntu-dev
[23:47] <fta> asac, http://launchpadlibrarian.net/30433198/buildlog_ubuntu-karmic-i386.modemmanager_0.2.git.20090817t181641.ca767e4-0ubuntu1~nmt1_FAILEDTOBUILD.txt.gz
[23:47] <asac> so that anyone who can upload can also push
[23:47] <andv> asac, you merged it right now
[23:47] <andv> so how could it be on ubuntu-dev two weeks ago?
[23:48] <andv> the updated version
[23:48] <andv> I mean
[23:48] <asac> hmm
[23:48] <asac> andv: either you dont upload or you push it there
[23:48] <asac> fta: thats interesting. wonder if that has something to do with the debian dir movage
[23:49] <asac> andv: anyway ok for now.
[23:49] <andv> asac, I gonna fix some stuff
[23:50] <andv> and then it's ready for debian
[23:50] <fta> asac, no, all karmic are red, jaunty is green (so far)
[23:50] <andv> then I'll test it on my debian box
[23:50] <andv> together with sveinung
[23:52] <andv> sveinung, you there?
[23:52] <andv> sveinung, we gonna keep just one branch
[23:53] <sveinung> andv: yes, I'm here
[23:53] <andv> sveinung, so please re-add all changes you did on the ubuntu-dev branch
[23:53] <andv> sveinung, you made a .debian branch before with some changes
[23:53] <andv> please merge them into the ubuntu-dev
[23:53] <andv> branch
[23:53] <sveinung> it's still on launchpad
[23:54] <andv> asac, but having it on ubuntu-dev will make sveinung unable to push to it
[23:55] <andv> sveinung, do something nice
[23:55] <andv> sveinung, apply the .debian changes
[23:55] <andv> to the .ubuntu branch
[23:55] <andv> then ask a merge again
[23:55] <andv> and add me as reviewer
[23:56] <andv> then remove the .debian branch
[23:56] <andv> it will be useless at that point
[23:56] <andv> asac, but having it on ubuntu-dev will make sveinung unable to push to it
[23:56] <andv> * asac_
[23:56] <sveinung> andv: sure
[23:56] <andv> sveinung, let me know when done
[23:57] <andv> so I review / accept the changes
[23:57] <andv> so the package can be ready for tomorrow
[23:58] <fta> asac, weird https://edge.launchpad.net/~network-manager/+archive/trunk


[06:17] <soee> good morning
[07:54] <Riddell> good morning Kubuntu!
[08:03] <Quintasan> \o
[08:12] <Riddell> cmollekopf: did the packages work?
[08:12] <cmollekopf> Riddell: yes, thanks
[08:19] <yofel> morning folks
[08:21] <Riddell> hi tariq, how's the support website doing? anything I can do to help?
[08:25] <lordievader> Good morning.
[08:36] <Riddell> ScottK: did you get a chance to look at the owncloud sru?
[08:57] <shrini> good morning Riddell
[09:01] <Riddell> hi shrini
[09:01] <Riddell> shrini: did you get your install bug in or do I need to review it?
[09:05] <Riddell> agateau: same question ⇈
[09:10] <agateau> Riddell: I don't understand the question
[09:10] <Riddell> agateau: you had a merge request for ubiquity? is that still needing review?
[09:12] <agateau> Riddell: I haven't received any comment, so I guess it does. Note that I pick you out of habit for reviews, but feel free to point me to someone else if you are too busy :)
[09:12] <Riddell> that's all good, I'll get onto them
[11:12] <smartboyhw> Hello Riddell yofel
[11:36] <BluesKaj> Hey all
[12:05] <Riddell> shadeslayer_: using i-7ae84810 ec2?
[12:08] <smartboyhw> Riddell, how about lang packs?:P
[12:31] <Riddell> smartboyhw: onto them now
[12:32] <Riddell> smartboyhw: uploading
[12:37] <smartboyhw> Riddell, plz review amarok in my main PPA plz
[12:37] <smartboyhw> And don't give me packaging jobs for the coming two days plz, I'm soon off to London.
[12:43] <Riddell> London?  big and smelly place, come up to Edinburgh!
[12:43] <Riddell> smartboyhw: where's amarok?
[12:43] <Riddell> ah found it thanks https://launchpad.net/~smartboyhw/+archive/ppa
[12:52] <Riddell> smartboyhw: uploaded, thanks for packaging, have fun in England (but if you hear anyone say that tennis chap is English, set them straight)
[12:53] <markey> if anyone complains about Amarok crashing on startup with KDE 4.11, please point them to Amarok 2.8-beta
[12:53] <markey> it's no longer crashing
[12:53] <markey> technically it's sort of a Plasma regression, but anyway, we are now compatible with that
[12:53] <Riddell> yay
[12:54] <Riddell> I wonder if we need to backport that to any PPA
[12:54] <Riddell> markey: so amarok 2.7 crashes with plasma 4.11 ?
[12:54] <yofel> it doesn't
[12:54]  * apachelogger goes Oo
[12:54] <markey> on a related note, apparently lots of KDE applications, including Amarok, are crashing on Ubuntu/Unity with latest updates. no idea why. with Kubuntu everything is fine
[12:54] <yofel> we have the patch for that for 2 weeks already
[12:55] <markey> Riddell: yes. if you would like to backport a patch, I can point you to the commit
[12:55] <apachelogger> xnox: pingy
[12:55] <apachelogger> yofel: pingy
[12:55] <apachelogger> shadeslayer_: pingy
[12:55] <yofel> markey: right, what you're seeing is bug 1195007 - I think caused by fixing bug 1180067
[12:56] <yofel> apachelogger: pong (more or less)
[12:56] <apachelogger> yofel: did you confirm that the qt patch is what causes the crashery?
[12:56] <yofel> I confirmed that upgrading *only* qt on raring makes it crash - that's as much as I had time for
[12:57] <xnox> apachelogger: hi.
[12:58] <markey> yofel: that could be it, yes. the backtraces are usually inconclusive. just some X error and then it's crash
[12:58] <apachelogger> ScottK, xnox, Riddell: the SRU for bug 1180067 (in theory) makes all KDE software crash, it should get rolled back asap
[12:58] <Riddell> um, wow
[12:58] <yofel> that patch registers gtk's x error handler for Qt/KDE apps it seems
[12:58] <xnox> !regression-alert
[12:58] <apachelogger> I am seeing some 20 upstream reports already
[12:58] <yofel> and gdk_x_error() is FATAL
[12:58] <apachelogger> spread across all of kde
[12:59] <markey> so it seems that Ubuntu devs don't give a shit about Qt apps working right?
[12:59] <xnox> that list of people needs updating as well.
[12:59] <apachelogger> ^^
[13:00] <xnox> markey: please, use appropriate language. and Qt is cared about a lot, it's pushed as the default development toolkit for ubuntu.
[13:00] <markey> heh
[13:09] <ScottK> xnox: We'll need to revert that unless you have an immediate fix.
[13:09] <ScottK> xnox: To be clear though, Canonical is pushing Qt5, not Qt4, so that's not quite true.
[13:11] <ScottK> xnox: The regression alert ought to be on #ubuntu-devel since most of those people don't hang out here..
[13:11] <xnox> ScottK: sure, but I have no idea how to start and properly record an incident report for SRU regression. And I only sponsored that SRU for mitya. I'm not expecting gdk to error out the way it is reported to be doing.
[13:12] <xnox> ScottK: can you coordinate a revert on #ubuntu-devel? or what needs doing here?
[13:12] <ScottK> xnox: No.  I have $work to do today.
[13:12] <ScottK> Since you sponsored it, please follow up on #ubuntu-devel.
[13:12] <ScottK> Thanks.
[13:20] <xnox> apachelogger: yofel: it seems like https://developer.gnome.org/gdk/unstable/gdk-General.html#gdk-error-trap-push could be used...
[13:21] <smartboyhw> Riddell, I know, it's British rather:P
[13:22] <apachelogger> xnox: I think that has too limited scope... it would need to be ::QApplication -> trap_push; ::~QApplication -> trap_pop
[13:22] <smartboyhw> (Well, you can't deny that Andy Murray is British right????)
[13:24] <xnox> apachelogger: if I understand it right, callking gdk_error_trap_push() right after gtk_init, should be sufficient without ever doing a pop.
[13:25] <xnox> apachelogger: that's the solution that libreoffice went for as well.
[13:27] <apachelogger> xnox: I am all for giving it a try, but first I would really push a revert into -updates anthen have a possible fixed fix go through proposed again
[13:28] <xnox> apachelogger: well Riddell wants to revert as well.
[13:28] <xnox> apachelogger: do that.
[13:29] <apachelogger> it has quite the sizable impact, so the longer we don't have a fix the more grumpy upstream KDE gets
[13:29] <apachelogger> Riddell: are you handling the revert?
[13:31] <smartboyhw> Riddell, hmm
[13:34] <Riddell> apachelogger: yep
[13:34] <apachelogger> ok
[13:34] <smartboyhw> Riddell, ftbfs of amarok in armhf
[13:35] <Riddell> bah
[13:36] <smartboyhw> Obviously, amd64 successfully built
[13:36] <smartboyhw> So um
[13:36] <apachelogger> qreal
[13:36] <apachelogger> build log?
[13:36] <smartboyhw> apachelogger, not qreaal
[13:36] <smartboyhw> Build dep at cmake
[13:36] <Riddell> no, cmake
[13:36] <smartboyhw> apachelogger, https://launchpad.net/ubuntu/+source/amarok/2:2.7.90-0ubuntu1/+build/4778138/+files/buildlog_ubuntu-saucy-armhf.amarok_2%3A2.7.90-0ubuntu1_FAILEDTOBUILD.txt.gz
[13:36] <Riddell> CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message): Could NOT find Qt4 (missing: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_LIBRARY)
[13:37] <smartboyhw> Yeah.......
[13:37] <apachelogger>   Could NOT find Qt4 (missing: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_LIBRARY)
[13:37] <apachelogger> markey: ^
[13:37] <smartboyhw> What the hell
[13:37] <apachelogger> amarok is no longer compatible with ARM
[13:37] <apachelogger> as there is no desktop opengl on ARM
[13:37] <smartboyhw> :O
[13:37] <markey> well, who wants to run Amarok on Arm at this point
[13:38] <apachelogger> I do
[13:38] <Riddell> don't think that's amarok fault
[13:38] <Riddell> oh it needs opengl?
[13:38] <ScottK> To be fair, not compatible with Ubuntu's Arm.
[13:38] <apachelogger> markey: easy fix would probably be to simply make the opengl stuff optional
[13:39] <apachelogger> if you care at all
[13:39] <markey> I'm not sure I care that much, for the tiny amount of people trying to run it on ARM
[13:39] <apachelogger> libqt4-opengl-dev [!armel !armhf]
[13:39] <apachelogger> why is that in there at all
[13:39] <markey> if it were a larger audience, then yes
[13:40] <markey> it felt really good to be able to make OpenGL a hard dependency, in 2013
[13:40] <Riddell> apachelogger: cos it doesn't work on arm and clashes with gles
[13:41] <apachelogger> Riddell: qtopengl doesn't work on arm?
[13:41] <apachelogger> Oo
[13:41] <apachelogger> what?
[13:41] <apachelogger> oO
[13:42] <yofel> it doesn't from what I've seen in build logs
[13:42] <markey> related note: QGLWidget doesn't work right with EGL (it crashes). that's something I'm very interested in
[13:42] <markey> (at least on Gentoo it crashes)
[13:44] <smartboyhw> ...
[13:51] <xnox> bug 707794
[13:51] <xnox> note a few packages are still not fixed / do not support GLES
[13:52] <xnox> (or have dependencies which are GL only, without GLES ports)
[14:03] <apachelogger> yofel: kf5 project-neon5-plasma-framework should be building soonishy....... if you want to give it a shot, something with the neon envrionment files is fishy as they alone do not allow me to run plasma-shell, adding the stuff form the wiki additionally makes it work
[14:03] <apachelogger> didn't work in vbox though, so I suggest native tests
[14:04] <apachelogger> http://wstaw.org/m/2013/07/05/md4.png
[14:04] <yofel> fun
[14:05] <yofel> I'll check the list of env vars again, but I thought I added everything...
[14:12] <markey> apachelogger: regarding ARM, I was just reconsidering. I think I can make OpenGL optional for 2.8-final. I'll look into it tonight
[14:12] <markey> ok, bbl
[14:12] <apachelogger> markey: would be very appreciated :)
[14:28] <Riddell> agateau: on https://code.launchpad.net/~agateau/ubiquity/kde-rework-try-install-buttons/+merge/172988 ...
[14:28] <Riddell> you add try-install.svg is that used anywhere?
[14:28] <Riddell> or is it just the source?
[14:29] <agateau> Riddell: it is the source for the new .png files
[14:29] <agateau> no need to ship them in the deb
[14:29] <Riddell> groovy
[14:30] <Riddell> agateau: how did you test running ubiquity with the buttons?
[14:30]  * xnox started to simply use .svg files directly instead of pngs.
[14:30] <Riddell> I tried export UBIQUITY_GREETER=1 but that doesn't help
[14:30] <agateau> Riddell: UBIQUITY_GREETER=1 ubiquity -d kde_ui
[14:30] <agateau> oh, that works for me
[14:31] <ScottK> shadeslayer_ and yofel: What did you tell afiestas_ we thought about KDE switching to a 3 month release cycle?
[14:31] <Riddell> agateau: hmm it doesn't work, and it runs in oem mode, wonder why that is
[14:31] <agateau> Riddell: haven't tried it with latest saucy, let me try
[14:32] <ScottK> afiestas_: Do you have a sample release schedule?  Perhaps you could take the 4.11 schedule and overlay it with what you'd expect if there had been two three month releases instead of one 6 month one?
[14:32] <afiestas_> ScottK: wiki page_
[14:32] <afiestas_> ?
[14:32] <yofel> ScottK: I don't think I explicitely talked to afiestas_, but my position is mostly "I don't care". The schedule I saw didn't really conflict with our 14.04 plans
[14:32] <ScottK> afiestas_: Link?
[14:32] <yofel> just different kde version number
[14:32] <afiestas_> ScottK: it is in the email
[14:32] <ScottK> yofel: No, I think that's wrong.
[14:32] <afiestas_> dafuq, nobody has read the wiki or what?
[14:32] <agateau> Riddell: indeed, doesn't work
[14:32] <afiestas_> http://community.kde.org/KDE_Core/ReleasesProposal
[14:32] <ScottK> Thanks.  Looking
[14:33] <Riddell> it doesn't conflict but I'd like to look at it for cadance, each SC release takes a long time to package
[14:33] <agateau> xnox: did anything change wrt the UBIQUITY_GREETER env variable?
[14:33] <yofel> if anything the support duration for bugfixes would be an issue
[14:34] <xnox> agateau: not that I know. I usually go to tty1, stop lightdm; stop ubiquity; pkill -9 X; update files in place; start ubiquity: to see the greeter again.
[14:34]  * agateau investigates
[14:34] <xnox> agateau: we now use pkexec, which clears environment better I think, instead of kdesu / gtksu /sudo
[14:35] <yofel> afiestas_: any reason why you went with 2 point releases for .13 and 3 for .14? Because we won't care much about .14 from what I see
[14:35] <agateau> xnox: ah, could be it
[14:36] <ScottK> Looks like 4.13 would release ~a week or two before "T" feature freeze.
[14:36] <ScottK> That's substantially later in the cycle.
[14:37] <agateau> xnox: Riddell: there is a "-g" option for the command line, which works for me
[14:37] <afiestas_> yofel: that image is a sample
[14:37] <afiestas_> it will continue as long as it takes us to release kde5
[14:37] <Riddell> agateau: oh nice
[14:39] <yofel> afiestas_: sure, but as we don't push new features out as updates, if we release with .13 in april, and you then focus all your fixing attention to .14 until frameworks is done that's not really great for us
[14:40] <afiestas_> yofel: right, I want us to develop a script or something you guys can use to keep branches alive, and do further releases
[14:41] <afiestas_> if we had a site for example, listing bug fixes for example, you could easily backport those and we could do more releases
[14:41] <afiestas_> pretty much like we have done with some 0.5 and 0.6 that were not shceduled
[14:42] <ScottK> Which might work, except with more releases, different distros will target different releases and so you end up with double the work.
[14:43] <afiestas_> accorcing to the release team (which I plan to join to help them) it won't be that much work
[14:43] <afiestas_> since point releases are almost automagical
[14:43] <afiestas_> as long as we have people caring about them
[14:43] <afiestas_> we have an issue now, that is impacting you (distros) and it is that nobody testes stable branch
[14:43] <ScottK> Agreed.
[14:44] <afiestas_> so we need people that will take "maintainership" of these branches
[14:44] <ScottK> What's why we put the point releases in a PPA for people to test before we put them into the regular updates cycle.
[14:44] <afiestas_> and ofc we need to make life easy to these maintainers
[14:44] <ScottK> Right.
[14:54] <Riddell> agateau: getting icons back on the buttons would be a nice addition if you happen to be still in ubiquity mood :)
[14:54] <yofel> afiestas_: on the stable branch topic: how can I list all commits done to 4.10 since it was branched? (that means including commits from all repositories that had commits to KDE/4.10 and including the svn branch)
[14:55] <Riddell> agateau: 1 merge merged and 1 merge commented although I think a comment from a ubiquity gtk person on the splitting one would be needed before going ahead
[14:55] <agateau> Riddell: thanks!
[14:55] <agateau> Riddell: will look into the icon issue
[14:55] <agateau> Riddell: it's new to saucy, isn't it?
[14:55] <Riddell> agateau: I think those went away when I switching it to a QApplication a couple of cycles ago
[14:56] <Riddell> had to get rid of KButton
[14:56] <agateau> Riddell: there are icons on button here: http://agateau.com/2013/04/11/hacking-on-ubiquity/ubiquity2.png
[14:57] <Riddell> agateau: hmm, but on when I run it on my installed saucy system, I wonder what's going on
[14:58] <afiestas_> yofel: yes, even though the idea is to make it even nicer
[14:58] <afiestas_> something like
[14:58] <agateau> that's why I think it's a regression in saucy
[14:59] <afiestas_> a website or something
[14:59] <afiestas_> or even with email alerts to kde-packagers
[14:59] <afiestas_> right now that's done manually I think
[14:59] <afiestas_> (with a CCMAIL)
[15:03] <yofel> afiestas_: right. I would be even happy with a seperate ML for all stable commits. I gave up on trying to filter kde-commits.
[15:03] <yofel> But yeah, if we could have some kind of notification that somebody fixed something in a stable release (esp. post-last-point-release) that would be incredibly helpful
[15:04] <afiestas_> yofel: please, send that kind of feedback to kde-core-devel thread
[15:04] <afiestas_> so we can add it to the proposal
[15:06] <yofel> right, will do
[15:08] <Riddell> agateau: just tried 13.04 on a virtual machine and the icons aren't there http://starsky.19inch.net/~jr/tmp/ubiquity.png
[15:09] <agateau> Riddell: I wonder if this could be linked to running ubiquity from the live session versus running it from the dm
[15:10] <agateau> Riddell: that is: do you get icons if you select "try kubuntu", then start ubiquity from the desktop icon?
[15:15] <Riddell> agateau: let me try
[15:17] <Quintasan> greaaaaaaat
[15:18] <Quintasan> any ideas where to debug when pc suddenly shuts down by itself and I get no messages after reboot?
[15:18] <smartboyhw> Quintasan, :I
[15:18] <smartboyhw> No.:P
[15:19] <Quintasan> I'm praying it's the hdd but who the hell knows
[15:22] <Riddell> agateau: yes exactly right
[15:23] <Riddell> agateau: icons show when in live session then ubiquity but not standalone ubiquity
[15:24] <agateau> Riddell: in raring, I changed code to use QIcon.fromTheme() instead of hardcoded full paths, that must be the reason why
[15:24] <agateau> My guess is the theme is not set when ubiquity is running standalone
[15:24] <Riddell> yeah, I wonder how that gets set
[15:24] <Riddell> must be something in QIcon that does it
[15:27] <agateau> mmm, maybe qapplication does not detect the environment it is running on and cannot pick a theme
[15:27] <agateau> which would make sense because there is nothing kde running at this point
[15:30] <agateau> anyway, I don't get icons at all on saucy :/
[15:32] <tsdgeos> ScottK: "Either they do have to change and do releases every three months or elements
[15:32] <tsdgeos> of the SC get skipped on some releases."
[15:32] <tsdgeos> who is they?
[15:32] <yofel> as I understood: e.g. kdepim
[15:32] <ScottK> tsdgeos: In this case it's kdepim.
[15:32] <tsdgeos> kdepim doesn't do any release
[15:32] <tsdgeos> the release team does
[15:33] <tsdgeos> all they do is increase a version number when we send them an email
[15:33] <ScottK> Right, but their repo has to be in a releasable state.
[15:33] <yofel> they release features - aligned to the schedule the release team sets
[15:33] <tsdgeos> ScottK: repos *always* have to be in a releaseable state
[15:33] <ScottK> There are rules about when features can land, string changes, etc.
[15:34] <ScottK> So I don't think it's right to suggest that changing the release cadence won't affect them.
[15:34] <tsdgeos> you sound like a spanish politician :D
[15:34] <tsdgeos> but it's on the constitution!
[15:35] <tsdgeos> ScottK: is people suggesting it won't affect them?
[15:35] <ScottK> That's how I read afiestas_' email.
[15:36] <ScottK> "You don't have to change the way you work because of this."
[15:36] <tsdgeos> and you don't
[15:36] <tsdgeos> noone follows the damn freezes anyway
[15:43]  * ScottK gives up.
[15:43] <tsdgeos> ScottK: see how laurent says "i just commited a feature for 4.11"
[15:44] <tsdgeos> what? why? how?
[15:44] <tsdgeos> feature freeze was months ago
[15:44] <ScottK> I agree.
[15:44] <tsdgeos> he doesn't understand than a shorter release cycle will be better for him
[15:44] <tsdgeos> because he won't need to "do it now or wait 6 months to get it released"
[15:44] <tsdgeos> it'll be "do it now or wait 3 months to get it released"
[15:44] <tsdgeos> so he'll wait and do it proprely
[15:45] <tsdgeos> ScottK: giving up is what happens when someone proposes change, because people just say "it's not what we do" without even thinking about it
[15:45] <ScottK> No.
[15:46] <ScottK> Its' when someone says two things that can't both possibly be true and people continue to claim it is..
[15:46] <ScottK> Either I don't understand or people are just pushing for change no matter the consequence.  I don't know which this is.
[15:47] <tsdgeos> people are pushing?
[15:47] <tsdgeos> i only see afiestas_ :D
[15:48] <tsdgeos> ScottK: you didn't give much info on why kubuntu had problems either
[15:48] <tsdgeos> "Let's not do it again"
[15:48] <ScottK> Like I said, I don't see how it's possible to both not affect developers and release twice as often, but that may be just me.
[15:48] <tsdgeos> seems like a "no because no"
[15:49] <ScottK> I think the problems with kdepim were felt by many distros and we discussed it at the time.
[15:49] <yofel> kdepim in 4.7 was buggy, really buggy, seriously. And looking back I regret uploading it back then
[15:49] <ScottK> IIRC Fedora people like rdieter objected even more than we did.
[15:49] <yofel> we lived through it, but I would very much like to not have something like that happen again
[15:49] <tsdgeos> and that has to do what with this?
[15:49] <tsdgeos> if 4.7 was buggy
[15:50] <tsdgeos> its code should not had been merged
[15:50] <ScottK> yofel: Agreed, but I was talking about 4.5/4.6 where we had no pim.
[15:50] <Quintasan> ARGH
[15:50] <yofel> ah
[15:50] <ScottK> It was always hard to figure out what pimlibs went with what.
[15:50] <yofel> right, it was out-of-schedule back then
[15:51] <yofel> tsdgeos: ^ and that's the thing we fear. If people start making changes thinking "they have until the next cycle", then things can either be better because they're better tested, but they can also get worse because we get an even larger untested code chunk
[15:51] <yofel> no idea what the best way to prevent that is though
[15:52] <tsdgeos> yofel: how there can be a larger untested code chunk if there's half the time?
[15:52] <tsdgeos> people is going to chunk code faster magically?
[15:52] <yofel> tsdgeos: I meant if they skip a release
[15:52] <yofel> i.e. a feature is still developed for half a year, not in 3 months
[15:53] <yofel> like kdepim did with their rewrite from 4.4 -> 4.6
[15:53] <tsdgeos> yofel: you *can't* skip a release
[15:53] <yofel> kdepim did
[15:53] <tsdgeos> *did*
[15:53] <tsdgeos> that's a good keyword
[15:53] <ScottK> All I was saying is we tried skipping and it was painful.
[15:54] <tsdgeos> no
[15:54] <tsdgeos> you said "Let's not do it"
[15:54] <yofel> I have a tendency to expect people to do something again if they do it once. If you plan to prevent it: *great*, but understand that I'm skeptical
[15:54] <ScottK> True.
[15:54] <ScottK> OK, I said we tried skipping and it was painful, let's not do it again.
[15:55] <tsdgeos> i don't unerstand what you mean by skipping
[15:55] <tsdgeos> but if you mean a module not being released
[15:55] <tsdgeos> that's not going to happen
[15:56] <ScottK> That's what I mean.
[15:56] <tsdgeos> if you mean kubuntu not releasing something
[15:56] <tsdgeos> that's your issue
[15:56] <ScottK> Sure.
[15:56] <ScottK> I mean a module not being released.
[15:56] <afiestas_> ScottK: that won't happen
[15:56] <yofel> note that I count "a module not merging any feature branches for a release", skipping a release too in that context
[15:57] <afiestas_> it can happen that some developer decides to work on 6 month cycles, mergin features using that timeline, but the module will be released anyway
[15:57] <afiestas_> using the example in kde-pim, 4.12 will contain my kde-accounts patches, but won't contain some laurent features because they won't be ready
[15:57] <afiestas_> but in anyway 4.12/13/14/15 will be released
[15:57] <tsdgeos> yofel: why?
[15:58] <tsdgeos> you are going to force people to develop stuff?
[15:58] <ScottK> yofel: I disagree with you there.
[15:58] <yofel> tsdgeos: what would have prevented you from calling "kdepim 4.4.11" "kdepim 4.6"?
[15:58] <tsdgeos> 42
[15:58] <tsdgeos> what kind of question is that?
[16:00] <yofel> nvm me, maybe my trauma from kdepim 4.6 was just too large so I'm unable to be properly objective here.
[16:02] <yofel> tsdgeos: I'm just scared about a "feature" getting too large (e.g. kdepim rewrite) so it's not going to be properly stabilized in *one* kde release timeframe (including point releases).
[16:02] <yofel> But I guess there's nothing one can do about that
[16:02] <Quintasan> Are we going to push 4.10.5 to raring?
[16:03] <yofel> Quintasan: yes
[16:03] <ScottK> Quintasan: Are there positive test results from PPA users?
[16:03] <yofel> Riddell: did you apply those kolab patches to the SRU packages too?
[16:04] <Quintasan> ScottK: From me - it works
[16:04] <smartboyhw> ScottK, soee did report that 4.10.5 was good here...
[16:04] <Quintasan> I can get someone else to test
[16:04] <ScottK> Any bugs on ~kubuntu-ppa that need review?
[16:04] <Riddell> yofel: i should have done to all the PPA versions yes
[16:04] <ScottK> If not, then I think it's fine to push it to -proposed.
[16:05] <yofel> yay
[16:05] <yofel> Quintasan: bug 1198754 needs looking at possibly
[16:05] <Riddell> e.g. 4.10.5 has them here https://launchpad.net/~kubuntu-ppa/+archive/ppa/+packages?field.name_filter=kdepim&field.status_filter=published&field.series_filter=
[16:06] <yofel> Riddell: ok, thanks!
[16:10] <ScottK> yofel: We should definitely have that.
[16:13] <yofel> right
[16:14] <yofel> Quintasan: mind cherry-picking that? If you have no time I'll do it later
[16:42] <ScottK> How hard would it be to have a PPA that did a recipe build on change for the stable branch?
[16:42] <ScottK> People interested in the latest stable/testing could run that and it would be reasonably safe.
[16:44] <Riddell> ScottK: on change of anything in stable branch?
[16:44] <ScottK> yes
[16:44] <Quintasan> Hmmm
[16:44] <Riddell> a neon-stable
[16:44] <ScottK> Except I don't think it would need to be separate packages like Neon is.
[16:45] <Quintasan> Riddell, ScottK: Any ideas on why we have firefox-locale-en on the CD?
[16:45] <ScottK> Quintasan: No.
[16:45] <Quintasan> Or it's quite possible the installer pulled it with internet connection
[16:45] <yofel> ScottK: I think I already explained that to d_ed on kde-quality or so a while ago. Essentially: imports of all stable branches + our SRU packaging in branches + recipes for that
[16:46] <ScottK> yofel: Yes.
[16:46] <yofel> not too much work, but still enough that I want to have a confirmed userbase before doing that
[16:46] <ScottK> I'm thinking if we did that, maybe we could send a point release straight to proposed since we'd have tested it already.
[16:46] <yofel> hm, good point
[16:47] <ScottK> So it would ~replace the updates PPA.
[16:48] <Quintasan> Hell, I could run taht
[16:48] <ScottK> Yeah.
[16:48]  * Quintasan was running neon
[16:48] <Quintasan> so why not
[16:48] <yofel> I have a recipe creation script in the neon tools, that would have to be extended to run on the whole KDE SC
[16:49] <yofel> then we need a name pattern for the SRU branches
[16:49] <yofel> import creation and recipe creation script that is
[16:49] <ScottK> apachelogger is our namespace master, right?
[16:49] <yofel> right, at least he's better at that than I am ^^
[16:52] <ScottK> In any case, something like this could help with the "no one tests stable" problem, regardless of if the release schedule changes or not.
[16:57]  * Quintasan whines
[16:57] <Quintasan> This !@#!@%! PC
[16:57] <Quintasan> When I want to debug this bastard - everything works
[16:58] <Quintasan> When I was to do anything - shit hits the fan
[16:58] <Quintasan> want*
[16:58] <yofel> sounds familiar
[16:58] <Quintasan> At least I have an SSD now
[16:59] <Quintasan> I can finally kill the only PATA drive now
[17:00] <yofel> bbl
[17:01] <ScottK> Can someone test the qt4-x11 in raring-proposed?
[17:01] <ScottK> Is I can get a positive test, I'll release it once it's built on all archs.
[17:02] <Riddell> presumably testing with unity is what's needed
[17:02] <ScottK> True.
[17:02] <ScottK> xnox: ^^^
[17:02]  * ScottK will be away for awhile.
[17:09] <xnox> ScottK: Riddell: I don't have access a raring instance. I would have thought the testing that needs to happen is that kile doesn't crash with empty config.
[17:09] <ScottK> xnox: But not in Kubuntu.  In Unity.
[17:09] <xnox> oh... wait, yeah under !kde
[17:09] <ScottK> Can you find someone to test?
[17:10] <xnox> ScottK: there are many "me too" on bug #1195007
[17:10] <ScottK> xnox: I need to leave and I was hoping someone would get it tested so I can release it when I get back.
[17:11] <xnox> ScottK: is there an "SRU accepted template" / call for -proposed testing that you can post there?
[17:40] <apachelogger> ScottK, yofel: namespace for what?
[17:43] <ScottK> SRU branches for KDE SC packages.
[17:44] <Quintasan> LOL
[17:45] <Quintasan> yofel: I copied Win7 partition from my HDD to SSD, now I have two grub entries, doesn't matter which I press it still boots from the hdd xD
[17:45] <ScottK> xnox: https://bugs.launchpad.net/ubuntu/+source/kile/+bug/1195007/comments/10
[17:55] <apachelogger> ScottK, yofel: ~kubuntu-packagers/kubuntu-packaging/phonon-raring in case you mean the packaging
[17:56] <yofel> Quintasan: doesn't seem like you migrated the win7 boot manager entries properly
[17:56] <Quintasan> yofel: This retarded software overwrote my Kubuntu partition on SSD :D
[17:56] <yofel> lol
[17:56] <Quintasan> Even though I specifically asked it to restore it to the second paritition
[17:57] <Quintasan> The biggest problem with win7 is that the installer is so retarded it won't install unless your hdd is master on the first channel and you install it on the first partition
[17:58]  * yofel never touches win7 unless he has to
[17:58] <yofel> actual my notebook's win7 install is still on it's own HDD, I simply switch the disks out when I need it
[17:58] <Quintasan> lol
[17:58] <Quintasan> well, that's a solution
[17:58] <Quintasan> I actually need to do someting about my disks
[17:59] <Quintasan> I have overlapping partitions somehow
[17:59] <yofel> there was a grub2 bug where e.g. photoshop overwrote parts of the boot manager data (well, the win7 boot manager doesn't put data there so it's fine right?)
[17:59] <yofel> since then I never dual boot linux and windows from one disk
[17:59] <Quintasan> wat
[17:59] <Quintasan> links to that
[17:59] <Quintasan> lol@adobe
[17:59] <yofel> sec
[18:00]  * genii ponders this mid-boggling possibility of photoshop boot loaders
[18:00] <Quintasan> genii: wat
[18:00] <Quintasan> WHY WOULD YOU DO THAT
[18:01] <genii> Quintasan: I'm not sure why anyone at Adobe thought it might be a good idea. That's why I'm finding it mind-boggling they would store data in the mbr or so
[18:02] <Quintasan> yeah
[18:02] <Quintasan> yofel: btw, did I tell you about one core missing from my CPU?
[18:03] <yofel> Quintasan: bug 441941 - fun read
[18:03] <yofel> genii, Quintasan: obvious reason: Adobe OS
[18:05]  * genii watches http://www.youtube.com/watch?v=QyR1MLI_6Ig for enlightenment
[18:07] <shadeslayer_> genii: yofel Quintasan it's akin to shipping a SDK IMHO
[18:07] <shadeslayer_> "Here's an env that will work everywhere (TM)"
[18:08] <Quintasan> WOLOLOLOLOLOLOLOLOLLOLOLOLOLOLOL
[18:08] <Quintasan> yofel: anyways, I noticed Linux and Win7 stopped showing 4 cores
[18:08] <yofel> shadeslayer_: please don't say that, otherwise I'll start looking funny at ubuntu-sdk >.>
[18:09] <Quintasan> I was like: well, fcks, okay can live with that but shouldn't the cpu die?
[18:09] <shadeslayer_> yofel: hehe
[18:09] <shadeslayer_> ubuntu-sdk-os
[18:09] <Quintasan> Imagine my face today when I boot the damn machine and it has 4 cores
[18:09] <yofel> Quintasan: wat?
[18:09] <Quintasan> quite close, got an image to accomapny that?
[18:09] <Quintasan> since I have one
[18:10] <yofel> I think we're thinking of the same one ^^
[18:10] <Quintasan> http://pwr.quintasan.pl/wat.jpg
[18:10] <Quintasan> Exactly
[18:11] <Quintasan> I sometimes seriously wonder if it's me having bad luck or emmiting some kind of aura that makes pc parts behave in a completeely retarded manner
[18:11] <genii> yofel: Seems to be some firefox os offshoot
[18:11] <Quintasan> yofel: btw, I can't unlock my screen in KDE now
[18:11] <shadeslayer_> <3 that image
[18:11] <Quintasan> It keeps saying wrong password every damn time :D
[18:12] <yofel> Quintasan: official KDE?
[18:12] <shadeslayer_> you were hax0red
[18:12]  * yofel remembers that in neon with the old locker
[18:12] <Quintasan> yofel: Yeah
[18:12] <yofel> but I think the new one works differently
[18:12] <Quintasan> As in our packages
[18:12] <yofel> not good :S
[18:12] <shadeslayer_> Quintasan: coming to Akademy right?
[18:13] <Quintasan> shadeslayer_: No.
[18:13] <shadeslayer_> :S
[18:13] <Quintasan> I'm going to be bothering you online
[18:14] <Quintasan> yofel: No idea how to debug this, currently I'm logging in via tty and killing it with dbus
[18:14] <Quintasan> :D
[18:14] <yofel> lol
[18:15] <yofel> me neither, maybe ask in #kde-quality if someone's awake there
[18:15] <Quintasan> shit, if my 2x1TB drives die then I'm in a world of suffering
[18:15]  * Quintasan backsup his keys
[18:16] <yofel> fun
[18:16] <yofel>   xserver-xorg-input-all xserver-xorg-input-synaptics xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-cirrus xserver-xorg-video-intel xserver-xorg-video-mach64
[18:16] <yofel>   xserver-xorg-video-r128 xserver-xorg-video-radeon
[18:16] <yofel> er, prepend "The following packages will be REMOVED:"
[18:16] <yofel> thanks saucy for removing the video driver I'm using
[18:17] <Quintasan> DO IT
[18:17] <Quintasan> DO IT
[18:17] <yofel> don't wanna ;P
[18:17] <Quintasan> You have to
[18:21] <shadeslayer_> 0.o
[18:21] <shadeslayer_> yofel: wasn't there a thread about this on ubuntu  devel
[18:22] <yofel> shadeslayer_: yeah, but this isn't that but self caused because I had a bit of an unsupported setup on raring here >.>
[18:22] <shadeslayer_> ah
[18:37] <Quintasan> This is getting worse
[18:37] <Quintasan> It automagically turn off by itself
[18:37] <Quintasan> CPU temp is not reaching high levels (30*C)
[18:38] <Quintasan> 30-40 more likely
[18:38] <Quintasan> GPU is not overheating too
[18:38] <yofel> resetting or actually powering off?
[18:39]  * Quintasan looks for screwdriver
[18:39] <Quintasan> yofel: it powers off then boots after two seconds
[18:39] <yofel> o.O
[18:39] <shadeslayer_> whaaaa
[18:39] <shadeslayer_> cp: cannot stat 'debian/tmp/usr/bin/akonadi_kolabproxy_resource': No such file or directory
[18:39] <Quintasan> yeah, and it won't boot normally since I have to do a little trick to let it boot
[18:40] <Quintasan> as in I turn off the switch on the power supply, press the power button so it tries starting with the remainder of electricity in the circuits and then immediately turn on the switch on the power supply
[18:41] <Quintasan> sounds stupid but it works
[18:41] <Quintasan> don't ask me why
[18:41] <yofel> and what does it do if you start it in a normal way?
[18:42] <Quintasan> everything gets powered on
[18:42] <Quintasan> fans, disks etc
[18:42] <Quintasan> but I get no video output
[18:42] <Quintasan> as in,  I can't even see POST screen
[18:43] <Quintasan> When I do the retarded power supply trick it works
[18:43] <Quintasan> I think it's time I just reassemble it
[18:43] <yofel> o.O
[18:45] <Quintasan> This was the first and the last time I actually let someone else build a PC for me
[18:46] <apachelogger> Quintasan: short circuit? :P
[18:47] <Quintasan> apachelogger: How do I go about determining whether that's the cause?
[18:47] <Quintasan> well
[18:48] <Quintasan> wouldn't that actually damage my hardware?
[18:49] <Riddell> ScottK: xnox: qt update verified on my computer in bug 1195007
[18:50] <shadeslayer_> !find akonadi_googlecalendar_resource saucy
[18:50] <apachelogger> Quintasan:  it would if it didn't shut down ^^
[18:50] <apachelogger> Quintasan: disassamble, reassmble
[18:51] <shadeslayer_> ^^
[18:51] <Quintasan> apachelogger: Well, I'm going to do that with the exception of CPU
[18:51]  * yofel once had a PSU short circuit on him - but you *smelled* that
[18:51] <shadeslayer_> Quintasan: make sure everything is slotted properly
[18:51] <yofel> dunno why the hardware survived actually
[18:51] <shadeslayer_> my RAM didn't go all the way in and the machine didn't even POST and left me puzzled for quite a while
[18:53] <Quintasan> https://dl.dropboxusercontent.com/u/69524/IMG_20130708_205229.jpg
[18:53] <Quintasan> how the flying fcks do you demonunt this?
[18:54] <Quintasan> things on top are not screws
[18:55] <yofel> see the black parts where it's connected to the mainboard. There's usually some trick to unlock the hooks
[18:56] <Quintasan> hmm
[18:56] <Quintasan> I'm not sure if I will be able to assemble it again
[18:56]  * Quintasan doesn't touch that for now
[19:00] <ScottK> Riddell: was that in KDE or Unity?
[19:01] <yofel> ScottK: I can verify that ubunt9.2 makes kile work in unity
[19:02] <yofel> and someone else confirmed that just now
[19:02] <ScottK> K.
[19:04] <ScottK> I'll release it once it's built.
[19:56] <Quintasan> Well
[19:57] <Quintasan> yofel, shadeslayer_: It still doesn't boot normally
[19:57] <Quintasan> I'm probably going to find someone with more powerful PSU to see what happens
[19:58] <Quintasan> Since I have to provide additional power to it
[19:58] <Quintasan> oh
[19:58] <Quintasan> it just restarted when sitting on login screen
[19:58] <Quintasan> seriously
[19:58] <yofel> memtest?
[19:58] <Quintasan> I'll try it
[19:58] <yofel> in case dmesg ever showed random segfaults
[19:58] <Quintasan> It didn't
[19:58] <Quintasan> That's the problem
[19:59] <Quintasan> I can't even get a proper fucking failure message from the system before it goes down
[19:59] <yofel> although I only recently removed a memory DIMM that was causing system crashes but was error-free in memtest
[19:59] <yofel> it also crashed another system so it has to be broken in some way
[20:00] <Quintasan> It's like
[20:00] <Quintasan> "Sup bro nothing wro...fuck"
[20:01] <Quintasan> Power gets cut for a second or two and then it tries to boot
[20:11] <Quintasan> yofel: no errors so far
[20:12] <Quintasan> and it didn't reboot
[20:12] <Quintasan> What the flying fsck
[20:12] <yofel> well, that's how I was feeling too. I left memtest running for a day, 0 errors. Run windows for an hour - BSOD in MEMORY_MANAGEMENT
[20:13] <yofel> I'm still not totally sure whether the PC is fine now or not, but without that memory it hasn't crashed yet
[20:16] <Quintasan> yofel: Thing is - it doesn't even BSOD or panic
[20:17] <Quintasan> the power gets damn cut for some reason
[20:18] <yofel> well, until I told windows to not damn reboot immediately, my BSOD experience was "oh hi, what can I do for you todaREBOOT"
[20:18] <yofel> except that I didn't have a moment where it was off completely
[20:21] <yofel> ScottK: I just remembered why I gave up daily builds of stable kde branches: http://paste.kde.org/791636
[20:21] <yofel> I'm just triggering another build of https://code.launchpad.net/~yofel/+recipe/kubuntu-kdelibs-stable. If it breaks again I'll talk to the launchpad people
[20:21] <Quintasan> lol
[20:22] <yofel> (or I need hardcoded version strings in the recipe text :/ )
[20:55] <Quintasan> herp
[20:56] <Quintasan> 5 passes
[20:56] <Quintasan> no errors
[23:58] <ScottK> yofel: I'm told us recipe format 0.3 instead of format 0.4 may help.
[23:58] <ScottK> s/us/use//


[00:15] <sarthor_> here is invoice software, Can i get any free like this software in Linux? http://www.hillstone-software.com/invoice_software.htm
[00:23] <genii-around> sarthor: http://frontaccounting.com/wb3/pages/products/features.php is not bad. There is also a package for it already in Ubuntu
[02:26] <Hoyt> hi , how should I start the VM after ubuntu-vm-builder completed ?
[02:26] <Hoyt> the kernel in the config was specified as 'None'
[02:30] <koolhead17> jamespage, ping
[05:25] <carwatt> any idea mkdir: cannot create directory `test': Read-only file system
[05:25] <carwatt> ?
[05:25] <carwatt> input/output error
[06:15] <aarcane> I heard ubuntu ditched iet for iscsi target mode for 12.04, but I don't remember what the new system is called.  What's the new system called, and/or where is a quick start guide ?
[06:16] <Mischinka> Anyone know where i can get ioncube?
[08:31] <brainysmurf> I want to make a 2,1 xserve an ubuntu box, but I dont' know how curren the information is here https://help.ubuntu.com/community/Xserve2-1
[10:34] <RoyK> perhaps offtopic, but has anyone seen a mobo being unable to see a pci-ex card when it's in the 16x slot? I know the card works, but maybe the mobo only allows vga cards there?
[11:41] <brainysmurf> Does anybody know anything about mounting an afp server so that I can have www-data write to it? Specifically, I think I need to do something with the acl on the mac side, but I'm not sure what.
[11:44] <RoyK> brainysmurf: didn't you say you had root on this server? if so, why would you use afp?
[11:45] <brainysmurf> Hi RoyK, thanks for helping. I'm actually a bit confused, because my colleague is telling me that afp is a raid.
[11:45] <RoyK> is a what?
[11:45] <brainysmurf> RAID
[11:45] <RoyK> as in redundant array etc?
[11:46] <RoyK> afp is a protocol, not related to how you store data on disks
[11:46] <brainysmurf> right, there is a stack of hd below the xserve and they connect to the mac through afp
[11:46] <RoyK> yes, but the xserve doesn't store data in afp
[11:47] <brainysmurf> It has a hd, but it's not big enough to hold what I need it for
[11:47] <RoyK> it probably uses a raid controller and HFS+
[11:48] <RoyK> AFP is an access protocol, like NFS or CIFS or even NCP
[11:49] <brainysmurf> So xserve sees those hd as hfs just like anything else, but then serves it up as afp.
[11:49] <RoyK> yes
[11:49] <brainysmurf> If that's the case, then why does it show it looks like a network drive on the desktop??
[11:49] <RoyK> and it can probably serve them with CIFS or NFS as well
[11:50] <RoyK> brainysmurf: what desktop?
[11:50] <brainysmurf> the mac desktop, it's not a hd but connected as a network share
[11:50] <RoyK> yes, that's because you use nfs or afs or something across the network to access it
[11:51] <RoyK> but on the drives, there's no such thing as afp
[11:51] <brainysmurf> I think I need to spend some time with this xserve without my colleauge around.
[11:52] <brainysmurf> She's confusing me.
[11:52] <brainysmurf> If I have troot on both, what's best to share files if I need to have www-data write to it. sshfs?
[11:54] <RoyK> nfs
[11:54] <RoyK> sshfs is generally a good idea when all else fail ;)
[11:55] <brainysmurf> RoyK: xie xie (thank you in Chinese)
[11:55] <RoyK> ;)
[12:11] <alex_____> hi can somebody tell me how i can run the asuse35m-1 deluxe with ubuntu server?
[12:12] <RoyK> alex_____: what is that?
[12:12] <alex_____> a mainboard from asus there is the soundchip acl892 on it
[12:12] <alex_____> i want to hear webradio but there comes no sound out of the speakers
[12:13] <alex_____> alsamixer works an show me the soundchip aplay also
[12:37] <samba35> i am facing strange problem ,my internet on my ubuntu dmz server ,today only i am facing this problem how do i diagnose this
[12:37] <samba35> even apt-get update is taking 15-20 mints where it was 3-4 mints usally
[12:43] <samba35> but when  i ping download some software on my gateway it was fast
[15:41] <randomDude> i'm having some issues installing cobbler on ubuntu server 12.04 : http://dpaste.com/750253/
[15:45] <ikonia> looks like the ip command has the wrong syntax
[15:45] <randomDude> ikonia: i am unable to control that, all i did was ask apt-get install cobbler
[15:45] <ikonia> I understand that
[15:46] <randomDude> perhaps it's a bug with the package then
[15:46] <ikonia> possible, or your config (eg: it reads your config and the current setup is incompatible with what it's trying to do )
[15:47] <randomDude> first time i tried to install cobbler on this system
[15:58] <randomDude> ikonia: nothing i do seems to make apt-get install cobbler... and google only returns results that talk about the deb package info, or things like maas not importing isos (not relelvant to me )
[15:59] <ikonia> unpack the deb and see what the setup is trying to do and how it fails against your systems setup
[15:59] <randomDude> not sure how to do that
[16:00] <ikonia> get the debian source package and have look through the setup
[16:00] <ikonia> see if the setup script is either a.) got a bug in b.) got something that conflicts with your system
[16:02] <randomDude> where does dpkg --unpack send its stuff ?
[16:02] <randomDude> it's not in the folder i'm in nor is it in the folder cobbler deb was in
[16:02] <ikonia> I'd just grab the source package
[16:02] <randomDude> can i do that with dpkg?
[16:03] <ikonia> apt-get source
[16:04] <randomDude> i'm not even sure what i'm supposed to be looking at, what files does apt-get use to install stuff in a package?
[16:04] <randomDude> PKG-INFO ?
[16:05] <randomDude> yeah i have no hope of fixing this which should work by now on a LTS release
[16:05] <ikonia> the control file should show the layout (I've not got an debian based system here to go through it)
[16:06] <ikonia> randomDude: it may work fine on an LTS system, it may be something as simple as your machine isn't setup in line with the pre-requisits
[16:06] <randomDude> so i guess i can't use orchestra thus i shouldn't buy a support contract from canonical if this is whats to be expected
[16:06] <randomDude> ikonia: what makes my system a "non lts system" ?
[16:06] <ikonia> randomDude: I didn't say it wasn't an non-lts system
[16:07] <randomDude> oh i thought you did
[16:07] <randomDude> as in implied
[16:07] <ikonia> no, I said your system may not be setup in line with the pre-requisits for cobbler, which is why it's failing
[16:07] <ikonia> eg: it may not be a problem with the package, more a a problem with how your system is setup
[16:07] <ikonia> I don't know without looking
[16:08] <randomDude> i doubt it
[16:08] <ikonia> why do you doubt it ?
[16:08] <randomDude> i'm pretty sure the package is broken
[16:08] <ikonia> !info cobbler
[16:08] <ikonia> randomDude: why are you pretty sure ?
[16:08] <ikonia> what research have you done to make yourself "pretty sure"
[16:08] <randomDude> because my server is standard?
[16:08] <ikonia> randomDude: standard does mean you've configured it to meet the pre-requists
[16:09] <ikonia> hang on, I'll get a 12.04 machine running in a vm and test it
[16:09] <randomDude> why should i have to configure it? thats what i use apt-get
[16:09] <randomDude> apt-get is suppposed to configure this stuff for me
[16:09] <ikonia> randomDude: apt-get is a package installer not a "make my machine a certain setup"
[16:09] <ikonia> randomDude: it will configure cobbler, sure
[16:09] <randomDude> i mean if apt-get can't configure it to the point where it at least isntalls without failing then...
[16:09] <ikonia> then what ?
[16:09] <randomDude> well apparently apt-get can't get it right
[16:10] <ikonia> please stop talking
[16:10] <ikonia> your basing this on nothing
[16:10] <ikonia> the package maybe broken, it may not be
[16:10] <ikonia> but you've done no research and you're just sat there complaining
[16:10] <ikonia> I was going to test it for you now, but I can't be bothered as you've already made your mind up so you can have a moan
[16:10] <ikonia> package is broken, you won't by a support contract, fair enough, move along
[16:10] <randomDude> :)
[16:12] <randomDude> it's actually quite a shame, because cobbler installs fine on the same system when it has ubuntu server 10.10 on it.
[16:12] <ikonia> ok, it's shame, great
[16:13] <randomDude> shouldn't it stand to reason that if it installs fine on the same system with a previous version of ubuntu and cobbler that there's now something wrong with the version of cobbler that ubunut provide for their latest lts server?
[16:13] <ikonia> no
[16:13] <randomDude> oh ok
[16:13] <ikonia> you've made your mind up it's broken, so find a distro that it's not broken in
[22:35] <danchou> I just bought a server and want to set it up first can someone tell me how to create a usb install disk of ubuntu server my server does not have a cd drive. Second it comes already installed with vmware is it better to install ubuntu-server first and then install vmware if i want virtuilization which i believe i do not need now
[22:51] <LordOfTime> danchou:  you can write the image to USB
[22:51] <LordOfTime> !liveusb
[22:52] <Mischinka> how do i clear cache on my server?
[22:53] <danchou> LordOfTime: thanks
[22:53] <LordOfTime> Mischinka:  which cache?
[22:54] <Mischinka> in my server block of nginx i have: location ~* \.(js|css|png|jpg|jpeg|gif|swf|xml|txt)$ { expires 14d; }
[23:19] <awutz> can't find the package to install sphinx php client in ubuntu 12.04...
[23:21] <awutz> i used to do: 'yum install sphinx-php' on centos...
[23:38] <awutz> bump
[23:40] <patdk-lap> bump?
[23:40] <patdk-lap> it doesn't exist
[23:40] <patdk-lap> use pear to install it?
[23:44] <awutz> patdk-lap: i'll give that a shot.
[23:46] <rfrittmann> hi all
[23:47] <rfrittmann> I just did the HowToForge Perfect Ubuntu 12.04 server, but have some problems with it, mostly networking and DNS related.
[23:50] <rfrittmann> Some background: the laptop I'm on now is connected to a Linksys WRT54G, then out to an iiNet BOB Lite ADSL/VoIP device to the Internet. IP range from laptop to router is 192.168.2.x, while from router to ADSL is 192.168.1.x
[23:51] <rfrittmann> From the server (static IP <IP_ADDRESS>) I can ping the router (<IP_ADDRESS>), but not the other side of it (<IP_ADDRESS>) and cannot connect to the Internet. The laptop I'm on now has a DHCP assigned IP from the router, and as you see, it connects fine.
[23:53] <rfrittmann> I have pointed the default gateway on the server to the router (<IP_ADDRESS>) and the router's own default gateway is the BOB Lite (<IP_ADDRESS>), and this works fine for my laptop, but not for the server.
[23:54] <rfrittmann> Any ideas why this might be?


[19:05] <nealph___> have done a fair amount of googling, but haven't yet figured out how to add a dependency tree to an existing launchpad blueprint...any helpful docs out there?
[19:06] <nealph___> derp. disregard...I had been looking at other bp's, not noting that my own had an "add dependency" option.
[19:15] <nealph___> but perhaps that's worth noting in the help? ^^^


[10:50] <jarnos> Strange. If I run "i3lock --dpms" as an autostarted script, it will not unlock with the correct password. If I start e.g. xtrlock same way, it works.
[16:02] <jarnos> http://pastebin.com/Eg53qWXv Why does it still require authentication in media player?
[16:03] <jarnos> !help mythweb
[16:03] <jarnos> !help
[17:14] <noaXess> hey ho.. where to post about xmltv,specially tv_grab_ch_search? cause tv.classic.search.ch isn't available and they switched to new layout, so grabber doesn't work anymore since 5.1.2016
[22:14] <jsubl2> Just finished my first installed.  recording a show now.  Used your document.  very very easy


[00:39] <kc2bez> @teward001 I ran a build of Cala in stable and that went fine too.
 https://www.omgubuntu.co.uk/2019/06/is-ubuntu-not-dropping-32-bit-app-support-after-all
 Rumors..
[01:03] <kc2bez> The situation is pretty fluid obviously.
 @kc2bez [<kc2bez> @teward001 I ran a build of Cala in stable and that went fine too.], so it didn't error on a phab HTTPS issue?
[01:52] <kc2bez> correct. It had previously.
 right, then I took a welder and welded in an internal CA cert local to ONLY the Lubuntu infrastructure into the trusted CA certs.
 INTERNALLY the HTTPS certs are all from the internal CA that is being used here
 but ONLY internally.
 and they're trusted.
 we'll have to do something similar for Lugito but
 it should then 'just work' internally
[01:54] <kc2bez> Nice.
 yep.
 it's nice that i know my way around OpenSSL and the x509 command lol
[01:56] <kc2bez> Indeed. Thanks for your work on that.
[02:00] <teward> not that hard
[02:00] <teward> esp. when you start rolling a GUI client (XCA has its uses lol)
[09:03] <guiverc2> screenfetch:  on a 'live' daily screenfetch reports DE as LXDE, but on my installed (primary) system it's reporting as LXQt - why would it be different?  (1798364 bug)  ; unimportant but if anyone knows they can put me out of my misery
[09:13] <guiverc2> fyi:  i'm not asking for anyone to look, just if you know off the top of your head
[10:51] <guiverc2> qa-test: opening all menu items in ACCESSORIES - when I got to QtPass it reported error, "GnuPG not found \n Install gpg using your favorite package manager or download it from GnuPG.org"   (I'm ignoring, noting only in comments, let me know if lp.bug.report is needed)
 There is a bug for that already. I don't have it handy here on my phone though.
[10:53] <guiverc2> not a problem, I'll find it, THANKS kc2bez
[10:54] <guiverc2> https://bugs.launchpad.net/ubuntu/+source/qtpass/+bug/1829693
 There it is^. Thanks guiverc
 Congratulations to @N0um3n0 for becoming an official member of the Lubuntu project!
[17:27] <teward> @tsimonq2 fix invitations on the irc channel for members
[17:27] <teward> ERR:NeedInvite
 Congratulations @N0um3n0
 @teward [<teward> @tsimonq2 fix invitations on the irc channel for members], You mean that channel that totally doesn't exist 😉
[17:28] <teward> :P
 @kc2bez [Congratulations @N0um3n0], Thanks !!!
 @tsimonq2 [Congratulations to @N0um3n0 for becoming an official member of the Lubuntu proje …], 👍👍👍👍
[17:34] <wxl> aw man! https://blog.ubuntu.com/2019/06/24/statement-on-32-bit-i386-packages-for-ubuntu-19-10-and-20-04-lts
 I was just reading that.
[17:40] <wxl> https://discourse.lubuntu.me/t/g-o-o-d-b-y-e-f-o-r-e-v-e-r-i386/108
 I kind of wish stuff would all be ported to 64 bit so that apt update would run faster not having to hit the server for 32 bit
[17:50] <wxl> tl;dr we're being held back by the fact that gamers are lazy sods
 Game developers
[17:51] <wxl> i'm considering game developers as gamers themselves (fairly safe bet), but also those gamers that are not developers that insist on playing super old games
[17:52] <wxl> with that logic we should bring back VAX!
 I am partial to baldur's gate myself
 @lynorian [I kind of wish stuff would all be ported to 64 bit so that apt update would run …], Silly question, maybe i386 support could be added on the demand? I agree most people won't use it, but some will, even for playing old games (civilization 4 in my case).
[17:54] <wxl> if it's offered at all, it requires testing, so blah
[17:54] <wxl> it's an all or nothing sort of thing
 It already is as far as I know. Ubuntu proper usually has multilib turned off by default.
 Are we somehow affected by this? Do we have 32-bit libs in our packages?
 so does lubuntu by default
 Then you're not hitting it and it isn't slowing you down
 unless you have to install stuff for it that uses 32 bit
[18:26] <wxl> oooh kde confirmed my bug that ark can't DND to pcmanfm-qt https://bugs.kde.org/show_bug.cgi?id=408233
 wxl, an offtopic question, since you hate php, what do you suggest for webpages? run on server side.
[20:11] <wxl> @HMollerCl static ones :)
 Django driven pages.
 *shot*
 I will take a look at django, problem is that most web hosting (still) doesn't have python.
 "web hosting"
 ugh shared hosting sucks
 BUT
 if you're doing that, static pages
 no dynamic content, etc.
 static.  pages.
[20:14] <wxl> @tsimonq2: `do we have the original for the release cycle image (svg or something?) https://lubuntu.me/downloads/
 @teward001 [static.  pages.], afaik, but php is kind of static
 no
 not PHP
 PHP is evil
 burn PHP
 static HTML.  no dynamic content.  no nothing.
 why?
 static.  HTML.  pages.
 you don't see the security data feeds I do :P
 aa, but if I need to query database, whoch othe roption I have?
 why does your site need to query a db lol
 @teward001 [why does your site need to query a db lol], ur a database
 @tsimonq2 no, you are.  you know nothing though 'cause I injected a worm into the code that truncated all tables
 :P
 I need to query databases to get the info I want to show.
 @HMollerCl  … 1. You have to configure the db securely … 2. You have to configure the webserver securely … 3. You have to program the web app securely
 Have a look at the owasp top 10 to have  an idea, what can and will happen
 thanks @aptghetto why php is worse than other in this?
 Basically, PHP makes it very easy to fail
 If you are not used to program with php (professionally), there are easier frameworks/languages. But the problems remain the same.
 like symfony
 I know php only from school and it is enough for me not to use it. Take the language you know best, follow design patterns and best practices and let review your code
 and which language is better for web development then¡
 ?
 I did once a project from scratch with Django 2.0
 It has a lot of features, but it was only in an internal network.
 ok, thanks for the info


[00:00] <knosys> do you know how to use the pastebin or paste.ubun?
[00:00] <knosys> ubuntu?
[00:01] <knosys> http://paste.ubuntu.com/
[00:02] <knosys> put there your fstab so everyone that may help can see it
[00:02] <knosys> also maybe fdisk -l command is usefull
[00:04] <knosys> Oh i see its a known bug of a removable device
[00:04] <knosys> in the link you provided, the comment 14 did not help?
[00:05] <knosys> https://bugzilla.xfce.org/show_bug.cgi?id=9193#c14
[00:06] <knosys> so looks there is no fix on that bug since 2012 i see
[00:06] <knosys> sorry man i though it was something more basic :)
[00:07] <chatr> tnx
[00:07] <chatr> for your help
[00:07] <chatr> I can use mount
[00:07] <knosys> haha
[00:07] <chatr> but I want to make it more simple
[00:08] <chatr> because it is better to click on the icon that it appears automatically
[00:08] <knosys> there may be some fixes around , like the comments in that same posts
[00:08] <chatr> to do fdisk -l as root
[00:08] <chatr> it seems that I should update to 4.12
[00:10] <chatr> thanks for your help
[00:10] <chatr> I'll be back
[00:11] <knosys> he was talking about thunar? Oo
[14:51] <zequence> Did you request this last respin, or did it happen automatically?
[14:52] <elfy> hi zequence - it was automatic, I didn't request it and I can't imagine either bluesabre nor ochosi doing so without letting me know
[14:54] <zequence> elfy: Alright. Seems like it's been going slowly though
[14:54] <zequence> I had a look this morning, and not many flavors have been respun since
[15:03] <elfy> not been watching tbh - I'm not that worried about them tbh, I'll probably do some hardware tests over the weekend and early next week if there are more respins
[15:04] <Pwnna> did blueman-applet get deprecated?
[16:18] <zequence> elfy: Ah, right. The rc is not really released until the official stable release date, as it's supposed to be the FINAL release. I seem to remember it used to be released like the Betas before, no?
[16:18] <zequence> Anyway, no sweat then.
[16:19] <zequence> After all, we won't be promoting it much, as we intend to put the most effort on the LTS from now on.
[16:19] <zequence> I'll try making some backports this time around.
[21:27] <pleia2> so, what's up with the weather applet? :)
[21:28] <Noskcaj> pleia2, The plugin? I sorta forgot about a patch i needed to add for 3 months
[21:29] <Unit193> pleia2: In -proposed for trusty.
[21:30] <pleia2> thanks <3