[05:01] <carlos> hi
[05:01] <SteveA> hi
[05:01] <danilos> hi all
[05:01] <SteveA> let's start anyway
[05:01] <danilos> sure
[05:02] <SteveA> first of all, what are you guys currently working on?
[05:02] <danilos> sorry if I confused you today Steve, I guess my connection to #launchpad dropped, while I was stil in #canonical
[05:02] <danilos> (and I lost my phone in Sunnyvale, so  didn't have your number right away)
[05:02] <SteveA> danilos: ok.  I was worried you were ill like many people seem to be right now
[05:02] <danilos> no, I am fine, or at least not counting mental illness :)
[05:03] <carlos> atm, I'm finishing bug-68014
[05:03] <carlos> about the reverting translations
[05:03] <SteveA> what's left to do there, carlos?
[05:03] <carlos> and have pending TranslationReview's review answer
[05:03] <danilos> anyway, I am wrapping up firefox stuff... I managed to break PO import (i.e. some tests are failing for me), so I am fixing that now
[05:04] <carlos> SteveA: improve the 'locking' detection code
[05:04] <carlos> actually, make it work as it should
[05:04] <danilos> I also have a couple simple bugfixes on my plate
[05:04] <carlos> and fix all tests
[05:04] <carlos> I would like to leave it in the review queue today
[05:05] <SteveA> ok
[05:05] <SteveA> we should get it reviewed as a priority
[05:05] <SteveA> danilos: tell me about how the FF stuff is going
[05:05] <danilos> sure
[05:06] <danilos> I have import and export working, but still have to switch to store actual alternate_msgid inside potmsgset table (I started with storing an ID into pomsgid table, but Carlos and I discussed it on UDS, and agreed that there is no point in that)
[05:07] <danilos> since the code involves changes to PO import/export as well, I have that slightly broken right now
[05:08] <danilos> and I haven't yet ported all the other importing mechanisms to ITranslationImport (such as tarballs, KDE langpacks,...)
[05:08] <danilos> I also have OOo import but no export yet
[05:08] <carlos> danilos: could you finish FF without changing tarballs and KDE langpacks?
[05:09] <danilos> carlos: yes, that's the plan, actually
[05:09] <carlos> ok, I would prefer to do that in different branches so we get smaller branches and merges more often...
[05:09] <danilos> carlos: sure, makes sense
[05:09] <carlos> ff is already quite big..
[05:09] <SteveA> there seem to be a lot of unfinished branches on the PendingReviews page
[05:10] <SteveA> and, having code that is not landed on mainline, well, it gets more difficult to maintain as time goes on
[05:10] <carlos> bug-44214 is already answered and should be ready to merge, unless I missed anything
[05:10] <danilos> I have a couple which are partial bug-fixes for some of my in-progress bugs
[05:10] <SteveA> what's a partial bug fix?
[05:11] <carlos> the other branches I have there are not high priority and I had to leave them stopped because are not near finishing. Though, I want to resume them as soon as possible
[05:11] <danilos> which fixes some instances of the problem (eg. the one with legend being shown on pages when no language stats are shown)
[05:12] <danilos> (and there are several templates, and one of them will require some code refactoring to fix it cleanly)
[05:12] <SteveA> danilos: I see.  thanks.  although it seems strange to me that it needs the same kind of fix in many places
[05:13] <danilos> SteveA: well, we have page which list multiple POtemplates, and only a single "legend", and another page which has a single POtemplate and "legend"
[05:13] <carlos> danilos: couldn't we share some code there?
[05:13] <danilos> carlos: sure, but that exactly means some "code refactoring" I mentioned above :)
[05:14] <carlos> I see
[05:14] <carlos> ok
[05:14] <SteveA> so, thinking concretely about the data-loss fix
[05:14] <SteveA> carlos, you said you expect it to be up for review today?
[05:15] <danilos> btw, we also have more of those +rosetta-index oopses for yesterday
[05:15] <carlos> I hope that, yes, unless the tests gave me more problems than they should...
[05:15] <SteveA> how big is the diff?
[05:16] <carlos> it's not working so I don't know how will be the final diff, but it shouldn't be more than 100-200 line changes/additions
[05:17] <carlos> without counting tests
[05:17] <carlos> even less...
[05:17] <SteveA> ok, so a smallish review
[05:17] <carlos> I think so, yes
[05:18] <SteveA> so, we should get it reviewed by someone right away, when it is ready
[05:18] <carlos> I think test changes will be higher than code changes
[05:18] <carlos> ok
[05:18] <SteveA> danilos: about the FF work, how long do you think before you can get something for review?
[05:18] <danilos> SteveA: just a couple of days--tuesday/wednesday most likely
[05:19] <SteveA> and what parts of the spec does that cover?
[05:19] <danilos> SteveA: any chance of getting this cherrypicked before 1.0 if review goes favourably and without too many changes?
[05:19] <danilos> SteveA: well, complete spec: we get Firefox XPI export/import
[05:20] <SteveA> ok, so the expectation we're talking about is the firefox support spec being up for review by wednesday?
[05:20] <danilos> exactly
[05:20] <danilos> with full tests
[05:20] <SteveA> that would be wonderful.  how confident do you feel about that?
[05:21] <danilos> pretty confident
[05:21] <SteveA> ok, thanks
[05:22] <danilos> if I run into problems, I'll ask carlos for some help
[05:22] <SteveA> also, tell me and kikok
[05:22] <carlos> danilos: please, do it
[05:22] <SteveA> we want to hear about your problems
[05:22] <SteveA> and when things go well too
[05:22] <danilos> and he won't mind at all, since he'd like to get to know the code for kde plural forms bug
[05:22] <SteveA> just ping us on irc and tell us things
[05:22] <SteveA> about how it is going
[05:22] <danilos> SteveA: ok, I know I've been pretty bad about communicating with you
[05:22] <danilos> and kiko
[05:23] <SteveA> looks like we're planning to have FF stuff rolled out around 12 December
[05:24] <carlos> SteveA: should we talk also about Rosetta DB optimizations?
[05:24] <danilos> SteveA: how does that fit into 1.0 and time-based releases after that?
[05:25] <carlos> btw, I will be off the week before that (4th-10th)
[05:25] <SteveA> danilos: we still need to work that out
[05:25] <danilos> SteveA: ok, I'll start some discussion on launchpad list
[05:25] <SteveA> about what?
[05:26] <SteveA> kiko and I have been discussing what to do about 1.0->1.1
[05:26] <SteveA> we need to discuss the whole thing with mark today (in about 10 mins)
[05:26] <SteveA> and then write a plan for it
[05:26] <danilos> well, about what is going to be the meaning of 1.1, 2.0 etc.
[05:26] <SteveA> I don't think there's much to discuss on the launchpad list yet, until we've got approval for the basic idea
[05:27] <danilos> iow, I am not entirely sure I understand what you mean by that
[05:27] <danilos> are we simply going to replace our "rollouts" with "releases"?
[05:27] <SteveA> no
[05:27] <SteveA> we'll still do regular rollouts every 1-2 weeks
[05:27] <SteveA> or 2-3 weeks
[05:27] <SteveA> we'll do planning of features on a 13 week cycle
[05:28] <danilos> ok, we're probably getting into marketing area then, if I am not mistaken?
[05:28] <SteveA> I don't want a lot of discussion on the list.  I just want to receive comments and feedback at this point
[05:29] <danilos> SteveA: ok, sure, I'll think about it some more, and post you my comments
[05:29] <SteveA> once we've got the general direction approved, then I'd like discussion with everyone
[05:29] <danilos> yeah, got it
[05:29] <SteveA> let's talk about the db optimizations
[05:29] <danilos> ok, let me check if stub updated the spec with latest "findings" from UDS
[05:29] <carlos> kiko suggested to implement it before improve translation form performance
[05:30] <carlos> I really don't mind to do it before or after that
[05:31] <danilos> I don't think stub updated it; we basically agreed that we want all our 40+M row tables merged into one
[05:31] <carlos> but I guess that will only delay the performance fix
[05:31] <danilos> well, I think the kiko's suggestion is because we probably won't need much translation form optimization work afterwards
[05:32] <danilos> we're currently doing joins across 3 40M row tables, and we'd be doing it over 1 50M row table afterwards instead
[05:33] <carlos> well, I don't think it's a bad thing to change the way suggestions work as we planned to do it
[05:33] <carlos> that will allow us to scale better in the future
[05:34] <SteveA> hey kiko
[05:34] <kiko> ho SteveA
[05:34] <SteveA> I'm waiting on hold, btw
[05:34] <danilos> hey kiko
[05:34] <SteveA> on the subject of the FF spec
[05:35] <SteveA> danilo is pretty confident that it will be up for review, with tests etc. by wednesday
[05:35] <SteveA> if that's so, I expect it to be rolled out right before or after the xmas break
[05:36] <SteveA> carlos expects the data-loss fixes to be up for review tonight
[05:36] <danilos> SteveA: hum, when's the christmas break? (you mentioned 12 December above, but that doesn't sound "christmassy" to me ;)
[05:37] <SteveA> it is a small patch
[05:37] <SteveA> danilos: did I?  for some reason I wrote 24 dec in my notes
[05:37] <SteveA> must have got confused with today's date
[05:37] <carlos> SteveA: yeah, you said 12 December
 looks like we're planning to have FF stuff rolled out around 12 December
[05:37] <SteveA> ok, that's more like it
[05:38] <SteveA> there remains a question about when to do the DB optimisations discussed at UDS
[05:39] <kiko> I think that is really important
[05:40] <kiko> it will make performance much better
[05:40] <SteveA> it would have the most effect across most users
[05:40] <danilos> if we want to use that to fix timeouts as well, it should be of relatively high priotity
[05:40] <danilos> s/priotity/priority/
[05:40] <kiko> and it will allow improvements later to be made much more easily
[05:40] <danilos> and I'd also need somewhat for proper search support
[05:40] <carlos> kiko: I'm fine, as long as we don't forget the suggestions improvements we had planned before that DB change
[05:41] <SteveA> we didn't yet talk about: search, translation review, OO work
[05:41] <kiko> carlos, I think the suggestions improvements may be rendered unnecessary by the DB work.
[05:41] <danilos> ok, we've had john berkus (I think) from postgres to join us on db optimisations session on UDS as well
[05:41] <kiko> SteveA, this new age is very soothing
[05:41] <carlos> kiko: well, I think that we should do it, better code, more clean, and will allow us to scale much more in the future...
[05:41] <SteveA> I think I'll dial back in and cowboy the leader code in there
[05:42] <kiko> carlos, what are you referring to there?
[05:42] <danilos> he mentioned a really cool thing about something called "partial indexes" (well, I thought it was cool anyway), where you can have indexes for only some values of certain column in a table
[05:42] <kiko> yeah
[05:42] <kiko> not in pg8.1 I think
[05:42] <carlos> kiko: well, instead of doing 3-4 queries for each entry to get all suggestions, making just one query
[05:43] <danilos> i.e. we'd also need to add "language" column to our potranslations table, so we can have per-language indexes
[05:43] <carlos> with the change danilos just said, we could split our DB per language in different databases
[05:44] <danilos> (and just to explain the context, we were very much concerned about performance of substring searches in 12M row table)
[05:44] <carlos> reducing the amount of rows too
[05:44] <danilos> carlos: I think there is actually no need to split database if we can have partial indexes
[05:44] <carlos> danilos: I said that we could, not that we should do it right now
[05:44] <danilos> but as kiko said, yes, this requires 8.2, and stub didn't seem too fond of the idea
[05:44] <carlos> it's just one idea from Mark
[05:45] <carlos> so I was pointing that we would be able to implement it
[05:45] <kiko> danilos, yeah. we can do that later, anyway. a partial index on approved strings would be cool, I can see.
[05:46] <danilos> well, maybe "not too fond" is a bit too strong; he just mentioned something about it not being too simple to do (=time, care)
[05:46] <danilos> but that it's planned anyway
[05:46] <kiko> carlos, so what about TR? I saw the UI at allhands and had some comments.. do you have time for it in the short term?
[05:47] <carlos> time to finish it?
[05:47] <carlos> or to implement your comments?
[05:47] <carlos> both answers are 'yes'
[05:48] <kiko> both yes
[05:48] <carlos> I got an initial review from Bjorn
[05:48] <carlos> I will address all his comments and once that's approved, I will implement the UI changes you suggested
[05:49] <carlos> so I don't complicate bjorn's life too much
[05:49] <kiko> ok.
[05:49] <carlos> hmm, not sure whether that expression is valid too in English... ;-)
[05:50] <kiko> it is!
[05:51] <carlos> ok ;-)
[05:52] <carlos> next point?
[05:52] <carlos> or do you have a phone call now?
[05:52] <kiko> we're mid-phone call, yes
[05:52] <danilos> according to SteveA's summary of points above, OO work
[05:52] <carlos> ok
[05:52] <kiko> yes, please dive in
[05:53] <danilos> ok, I'll put out current state anyway, so you can comment when you get back
[05:53] <kiko> and tell us all about this OO work
[05:54] <danilos> it's the same as pre-UDS/AllHands: OOo import is working (importing single GSI file into multiple translation domains), export not started yet
[05:55] <danilos> on UDS/AllHands, had a couple discussions with doko (OOo package maintainer) about how to best provide GSI files for him, and what domains to use, so need to incorporate his feedback as well (i.e. some bits different for help translation--actually have to check with him for more details on that one)
[05:56] <danilos> (which reminds me: carlos and I also had a discussion with pitti on documentation language packs, and one of the suggestions was to actually support direct import/export of DocBook XML files in Rosetta, just like we're going to support other formats such as FF/OOo)
[06:18] <carlos> danilos: anyway, that's another spec that we should write and plan to implement, if we have time
[06:20] <danilos> carlos: right, but that's another thing distro team wants of launchpad, so I thought I should also bring it up ;)


[10:08] <asdaf> hi all, anyone ever tried to compile upstart with uclibc?
[10:17] <asdaf> I get some errors, such as WEXITED ans WNOWAIT undefined
[13:31] <keesj> asdaf: what version? it somewhere rings a bel
[13:32] <asdaf> uclibc 0.9.28, upstart 0.3.9
[13:33] <asdaf> keesj, I have a clue, it seems uclibc doesn't define them in bits/waitflags.h
[13:34] <asdaf> and glibc does
[13:36] <keesj> not a simlink issue?
[13:37] <keesj> it's defined in the include/linux/wait.h  in het kernel
[13:47] <asdaf> i don't think so, I checked the differences between glibc and ucilbc and it simply seems not to be defined in uclibc
[14:28] <ion_> http://heh.fi/lhc-status (offtopic)
[20:57] <sadmac2> ion_: lol


[08:21] <lassegul> hi folks.
[09:15] <troy_s> lassegul: Any work of late?
[09:31] <lassegul> troy_s: yeah im trying to make some pictures of aurora polaris, I saw it while visiting family and i was amazed by the beauty of it.
[09:32] <lassegul> troy_s: and how the colours light up the ground as well. its truly amazing.
[09:33] <lassegul> troy_s: but i havent gotten anything ready to show yet, but i hope I can get there over the weekend. how about you?
[14:57] <abcde__> Where can I find a CD Label for Gutsy?
[15:20] <nothlit`alpha> abcde_: http://sinecera.de/GUTSY_ARTWORK.tar.bz2
[15:23] <abcde_> nothlit`alpha, thanks, I found some artwork I think looks better, and I found the xcf file, but I have to figure out how to change the text box on it that says feisty. http://ubuntuforums.org/showthread.php?t=422357&highlight=xcf
[15:25] <lassegul> nothlit`alpha: hi. im sorry i havent been online the last couple of days, we have changed the CMTS in our area so ive been offline for the last 3 days.
[15:25] <nothlit`alpha> lassegul: CMTS? thats fine, theres no gigantic rush
[15:26] <nothlit`alpha> i fixed up the getinvolved page
[15:28] <lassegul> cmts is a kind of hub for ISPs that use hybrid coax/fiber lines. GetInvolved is clean and nice.
[16:45] <SlimG3> Is there any (plans for) logos representing the ubuntu release codename? like a drake for dapper drake, this would be doable since all the codenames represents animals in different "moods"
[17:08] <lapo> hi
[17:15] <jarrod__> hi
[17:16] <jarrod__> i think u guys should stop using brown for your backgrounds as it looks very bad
[17:18] <SlimG3> *and they suddenly decided to go for another color*
[17:18] <SlimG3> :)
[17:25] <jarrod__> i think they should use blue or something
[17:26] <troy_s> jarrod__: And what is your 'knowledge' based one?
[17:26] <troy_s> on even
[17:26] <SlimG3> but I (and the people I've come across) agree with jarrod__ , I don't understand what made someone, somewhere, think that the color on his dodo actually looks nice, and even convinced mark to use it
[17:27] <troy_s> SlimG3: The actual colour has NOTHING to do with it.
[17:27] <troy_s> SlimG3: Brown can be very effective tonal base, the execution of the designs is far from useful.
[17:30] <SlimG3> but there still seems to me like there's a shared opinion amongst ubuntoids that the color _looks_ bad (Ps. I dunno what "tonal base" is)
[17:30] <troy_s> SlimG3: You would be making complete random speculation based on uneducated guessing.
[17:31] <troy_s> SlimG3: There are many that think that brown can work, and many that hate it.
[17:31] <jarrod__> i dont know what tonal base is either
[17:32] <troy_s> In the end, people who would suggest a blue are at least as out to lunch as suggesting a monochrome brown.
[17:33] <SlimG3> troy_s: That might be true and it might be false, I for myself haven't encountered anyone in my social network that has a positive or neutral attitude towards the default color of Ubuntu, but then again, I'm not hanging out woth the entire Ubuntu society (and I guess neither are you :))
[17:34] <SlimG3> Would be interesting to see the result of a major vote on the subject
[17:34] <jarrod__> ya
[17:34] <troy_s> SlimG3: It is garbage execution.  Nothing more or nothing less.
[17:34] <troy_s> SlimG3: Any poorly executed attempt can make just about anything look like dribble.
[17:35] <troy_s> SlimG3: And that would be exactly my point -- without a focus group and a proper poll, everyone is just talking from completely guessed vantages.
[17:36] <troy_s> SlimG3: In the end, I would be one of the people who would firmly agree that Brown with a rounded out palette could be at least as successful as say "Starbucks" design presentation or a high end interior design.
[17:36] <troy_s> SlimG3: It is a far far cry from that, however.
[17:36] <SlimG3> troy_s:  you mean the color is ok but the design ruins the total impression?
[17:37] <troy_s> SlimG3: The colour alone is _not_ "ok", but alas, this has been rehashed a thousand times.
[17:38] <SlimG3> mkay, I see your point
[17:39] <troy_s> SlimG3: Poor execution will inevitably lead to complaints about colour.
[17:39] <troy_s> SlimG3: We can change colours a thousand times and if it is poorly executed, it will still be rather useless and underwhelming.
[17:40] <troy_s> Again though, suggesting that 'brown' is the 'problem' is at least as ineffective and completely inaccurate as the implementation of it in Ubuntu.
[17:44] <SlimG3> troy_s: Thanks for taking the time to explain. What you're saying makes sense to me so I'm ditching my color-complaint
[17:44] <jarrod__> but i guess brown has always been the color so i guess changing it would be like a whole new os
[17:45] <troy_s> jarrod__: Indeed.  Worse -- at the very least the poorly underwhelming brown is distinct compared to the landscape of curley curvey blue garbage.
[17:45] <jarrod__> ya
[17:45] <troy_s> (Not that I am a fan of a 1995 trend to put curvey curley swoopy in)
[17:45] <troy_s> Just take a look at the equally bland and banal Fedora and Novell work.
[17:46] <troy_s> It is _extremely_ unfortunate that Diana Fong left the Red Hat team -- her work was at least moving in a far superior pattern to where the rubbish was going.
[17:48] <jarrod__> im gonna go now
[18:11] <nothlit> troy_s: can you throw me a popular example of a work or image using brown? i want to see if i can get in a factoid
[18:13] <troy_s> nothlit: Look at Starbucks 'burr' grinder from a few years ago -- it was a wonderful presentation.  It was stretched across all of their espresso machines too -- with different base tones for each.
[18:14] <troy_s> nothlit: I had a list somewhere... let me go look in a few...
[18:14] <nothlit`alpha> anything other than starbucks?
[18:17] <troy_s> nothlit: Yes.
[18:17] <troy_s> nothlit: (of course)
[18:18] <troy_s> nothlit: You could do a very quick reference to the victorian grunge trend in a good percentage of 18-20 somethings wardrobe
[18:18] <nothlit`alpha> lol, just asking if you have an example i can include
[18:18] <troy_s> yeah ... but i need to find actual links to products
[18:18] <troy_s> the brown in the victorian is almost always the palette blue that goes with it...
[18:19] <nothlit`alpha> np, if you can that would be great
[18:20] <nothlit`alpha> maybe we should whip up a whole treatise on brown for the wiki
[18:20] <troy_s> nothlit: This guy is brilliant
[18:20] <troy_s> http://www.rgbstudio.co.uk/
[18:21] <troy_s> and he is very very very contemporary -- 2nd example shows you brown
[18:21] <troy_s> nothlit: "highscore with moulton" shoe campaign is another one with the brown
[18:21] <troy_s> although more teal base
[18:22] <nothlit> , !brown is <reply> Any colour can be effectively used as a base, it is merely execution. Brown is the colour of the earth, coffee, caramel, and chocolate. It is a characteristic of conte drawings and found very commonly in (raw umber) underpaintings. An example of brown being used very succesfully is Starbucks.
[18:22] <nothlit> this is what i have atm
[18:23] <nothlit> raw umber is such a yummy pigment
[18:24] <troy_s> nothlit: Link?
[18:24] <troy_s> oh the pigment
[18:24] <troy_s> great title for a project too... lol... raw umber.
[18:25] <nothlit> oh, should we just use workforfood? he has some brown stuff
[18:26] <troy_s> well there are a good number out there now -- that victorian grunge look on clothes is rather massive right now
[18:26] <troy_s> brown pullovers with various palette elements such as the light sky blue with embroidered stitching and or faux gold leaf
[18:31] <troy_s> actually, nothlit i forgot to mention that it is quite huge right now in snowboarding circles.  a friend of mine is a world class snowboarder who is sponsored by helly hansen to evaluate the designs -- it is quite all over that scene right now as well.


[09:51] <Jip> hi
[09:51] <Jip> I have asked already, but does someone have an idea how to fix this? https://bugs.launchpad.net/armagetronad/+bug/1190375
[09:52] <Jip> I tried to bzr reconcile already
[09:52] <Jip> it seems that something went wrong with removing a file when another branch was merged ~800 revisions ago
[10:04] <lifeless> have you tried the bugfix jam proposed for it?
[11:05] <Jip> lifeless: how can I do that?
[23:56] <mwhudson> why can i not control-c a bzr serve process?
[23:56]  * bob2 vaugely blames threads
[23:56] <mwhudson> seems likely, doesn't it
[23:58] <lifeless> you should be able to
[23:58] <lifeless> if you can't, thats a bug


[09:17] <vish> and471: hey , could you upload your patches to lp and subscribe the sponsors..
[09:17] <vish> ?
[09:18] <and471> vish, hey, which patches?
[09:18] <vish> and471: the patches you forwarded to debian..
[09:18] <vish> or for those bugs..
[09:19] <vish> and471: debdiffs rather, sponsors prefer debdiffs..
[09:20] <and471> vish, sure, I shall try to complete them today, I have just got back form holiday and I am working through a backlog :)
[09:20] <and471> *from
[09:20] <vish> and471: doh! no wonder i couldnt find you on irc :)
[09:21] <vish> and471: was wondering how you kept changing the bug status but i always seemed to never catch you here. :)
[09:22] <vish> and471: sure not immediately , but we are nearing UIF, and translations need to be in by then.. :)
[09:22] <and471> vish, hehe, yeah I did some bug stuff while I had some free time :)
[09:22] <and471> vish, yup I am aware :) the shotwell guys are also bugging me as they watn to do a new release :)
[09:22] <and471> *want
[09:23] <vish> and471: heh, that was gonna be my follow up, "what happened to shotwell icons" ;)
[09:25] <and471> vish, I won't be able to finish the whole bug I think, but I have say 1/2 of it :)
[09:32] <vish> and471: redoing the icons? or not hardcoding them is 1/2?
[09:33] <and471> vish, 1/2 redoing, 1/4 hardcoding
[09:33] <vish> and471: oh right , re-doing them is not easy.. do you have a list that need to be redone?  make i can do a few as well?
[09:34] <vish> s/make/maybe
[09:34] <and471> vish, sure, I shall publish them on the launchpad bug report when I get round to it :)
[09:34] <vish> and471: cool! thanks..
[10:22] <and471> vish, which icon is the spinner in Humanity?
[10:23] <vish> and471: which spinner?
[10:23] <and471> vish, for example the one you get in nautilus when you open /usr/bin
[10:25] <vish> and471: are you using n-e?
[10:25] <and471> vish, yup
[10:25] <vish> and471: yeah, that doesnt appear in nautilus, it was removed iirc :)
[10:26] <and471> vish, ah, let me think of another example..
[10:26] <vish> and471: there is a spinner in gnome icons, which might be from where the spinner is being pulled
[10:26] <and471> vish, I'll show you a screenshot
[10:27] <and471> vish, the image in the right tab in http://imgur.com/On2Uv.png
[10:28] <vish> and471: oh that!
[10:32] <vish> and471: i cant seem to find it.. not sure where that one if from :s
[10:42] <and471> vish, hehe me neither :(
[10:43] <and471> vish, don't worry it isn't vital
[12:20] <black_tears> hello
[16:37] <kiwinote> devildante: hi!
[16:37] <devildante> hi kiwinote :)
[16:38] <kiwinote> devildante: I adapted the appdetailsview to use package info lines rather than package info tables
[16:38] <kiwinote> devildante: you can use this for the total size info
[16:38] <devildante> kiwinote: thanks :)
[16:38] <kiwinote> devildante: code is in the getting-the-small-things-right branch
[16:39] <devildante> kiwinote: okay :) can I merge it?
[16:39] <kiwinote> devildante: sure
[16:40] <devildante> kiwinote: thanks :)
[17:01] <devildante> kiwinote: it worked, thanks again :)
[17:01] <kiwinote> devildante: great to hear!
[17:01] <kiwinote> devildante: I'll look at the navigation stuff tomorrow
[17:01] <devildante> kiwinote: thanks :)
[17:05] <devildante> kiwinote: I'm here all day, so if you want to talk, I'm available ;)
[17:05] <kiwinote> devildante: are you free-ish this week?
[17:06] <devildante> kiwinote: I'm a 16-year-old student who doesn't have school in summer, of course I'm free :p
[17:06] <kiwinote> devildante: ah, ok, fun :p
[17:07] <kiwinote> devildante: there are still a few things that need doing about that addons branch
[17:07] <devildante> kiwinote: order and I shall code :P
[17:07] <kiwinote> devildante: mostly just tidying up things and so
[17:07] <devildante> kiwinote: is there something interface-wise?
[17:07] <kiwinote> devildante: I think if you work on that say monday and tuesday, then by wednesday thursday it should be truly rocking ;)
[17:08] <devildante> kiwinote: yeah :)
[17:08] <kiwinote> devildante: yeah, a few things like the padding around the install bar
[17:08] <devildante> kiwinote: you mean the "apply changes" bar?
[17:08] <kiwinote> devildante: but also things that installing a normal package fails..
[17:08] <kiwinote> devildante: yep
[17:09] <devildante> kiwinote: that one I done it right now :)
[17:09] <kiwinote> devildante: it's great work, it just needs a bit more polish and testing before it is ready for trunk
[17:09] <kiwinote> devildante: more so because feature freeze has passed
[17:09] <devildante> kiwinote: and about the pkg not installing, it's been a while I didn't test that, so I'll investigate :)
[17:10] <devildante> kiwinote: okay :)
[17:10] <kiwinote> devildante: don't worry too much about it all though, at the beginning of the summer I was just getting stuck into s-c code myself and facing these issues as well
[17:10] <devildante> kiwinote: okay :)
[17:11] <kiwinote> devildante: you already have the advantage that you are a few years younger when you start ;)
[17:11] <devildante> kiwinote: yeah :)
[17:18] <devildante> kiwinote: do you think there will be a problem with the ffe?
[17:21] <kiwinote> devildante: I think if we get it into really good shape this week, then there is a fair chance that we may get it
[17:22] <devildante> kiwinote: thank you for helping me :)
[17:22] <kiwinote> devildante: having said that, I aren't really too experienced with ffe's. I have seen more significant changes come later in the cycle though
[17:23] <kiwinote> devildante: no probs, it's great to see people actively working on s-c
[17:26] <devildante> kiwinote: argh, spotted a bug, and I don't know how to fix it
[17:26] <kiwinote> devildante: you can paste the error in the pastebin and post a link here
[17:26] <kiwinote> devildante: or if it isn't a crash, you can describe the bug here ;)
[17:27] <devildante> kiwinote: when removing an add-on, it is removed, but the "in progress" view doesn't show
[17:27] <kiwinote> devildante: yeah, i think that has to do with how you call the transaction
[17:28] <devildante> output: http://paste.ubuntu.com/478434/
[17:29] <kiwinote> devildante: when i looked at the code I wondered why you wouldn't call install_multiple or remove_multiple rather than feeding the addons as a side thing of a real pkg
[17:29] <and471> nessita, hey, how is the login dialog going?
[17:29] <devildante> kiwinote: it's just because remove_multiple wasn't there when I began to implement
[17:30] <kiwinote> devildante: but i haven't decided what the best way is, so don't change that behaviour until I've had time to think ;)
[17:30] <devildante> kiwinote: okay :)
[17:30] <nessita> and471: hey, you can try it on on latest maverick
[17:30] <kiwinote> devildante: ah, yes, that output looks familar. It's an aptdaemon bug most likely though
[17:30] <nessita> and471: you'd have to use the dbus service "by hand", but is already in main
[17:31] <kiwinote> devildante: don't think I'm comfortable enough with that code to fix it though
[17:31] <devildante> kiwinote: this is the exact line causing this:             trans = aptdaemon.client.get_transaction(tid,
[17:31] <devildante>                                          error_handler=lambda x: True)
[17:31] <devildante> kiwinote: pendingview.py in _on_transaction_changed
[17:32] <devildante> kiwinote: install_multiple and remove_multiple could fix this, you think?
[17:33] <kiwinote> devildante: i think the pending view stuff is a consequence of aptdaemon stuff though
[17:33] <kiwinote> devildante: it should bypass it, but the bug will need to be fixed at some stage anyway
[17:34] <devildante> so I just replace it with install_multiple/remove_multiple (in aptd.py)
[17:34] <devildante> ?
[17:34] <kiwinote> devildante: using install/remove multiple will mean that it sends each addon as a separate transaction, hence showing each in a separate tile in the pending view
[17:34] <devildante> kiwinote: I got some idea, lemme test
[17:35] <kiwinote> devildante: from memory it would need slightly more changes than that
[17:35] <kiwinote> devildante: the biggest question is when we select a pkg to install and select some addons to install, do we want say 5 entries in the pending view, or do we want one entry?
[17:35] <devildante> kiwinote: well my idea won't work :p
[17:36] <kiwinote> hm ;)
[17:36] <and471> nessita, cool, might try it later :)
[17:36] <devildante> from the spec, it seems we want each add-on as a separate task!
[17:37] <devildante> but only when the app is installed
[17:37] <kiwinote> devildante: let me have a quick look
[17:37] <kiwinote> devildante: hm, and when the main app isn't installed we want it one transaction??
[17:37] <devildante> kiwinote: yes
[17:38] <devildante> kiwinote: now it should be easy :p
[17:39] <kiwinote> hm, that makes it a bit messy in the code though, as we need to call install multiple if the pkg is not installed and we need to do what you're doing now for non installed apps
[17:40] <kiwinote> devildante: the nicest and cleanest solution would be to change your current code to use install/remove multiple in all cases
[17:40] <devildante> the "Apply changes" button won't show if the app isn't installed, though
[17:40] <devildante> kiwinote: it seems so
[17:41] <kiwinote> devildante: i think i need to think about it a bit, and we need to check with mpt before you should start changing the behaviour
[17:41] <kiwinote> devildante: so that's something for tomorrow ;)
[17:42] <devildante> kiwinote: okay, I'll do some tests though :p
[17:42] <kiwinote> devildante: nice
[17:42] <nessita> and471: let me know! :-)
[17:42] <kiwinote> devildante: mvo has recently added quite a few automated tests that check for regressions
[17:43] <devildante> kiwinote: oh yeah!
[17:43] <kiwinote> devildante: it may be interesting to look at what he has done and add some tests related to addons
[17:43] <devildante> kiwinote: though I don't know anything about tests :p
[17:43] <kiwinote> devildante: there are both backend tests and gui tests
[17:44] <kiwinote> devildante: heh, nor did I, but looking at what mvo has done you should be able to copy and modify some stuff ;)
[17:44] <devildante> kiwinote: okay :)
[17:45] <kiwinote> devildante: having tests may give bonus points for the ffe, so if you have heaps of spare time, then it may be a good thing to spend some time looking at ;)
[17:45] <devildante> kiwinote: all right :)
[17:46] <kiwinote> devildante: the most important part is making sure you cover all cases
[17:46] <kiwinote> devildante: anywayz, I'm going to have some dinner now
[17:46] <devildante> kiwinote: bye for now :)
[17:47] <kiwinote> devildante: not sure if I'll be back online this evening, we'll see ;)
[17:47] <devildante> kiwinote: np, take your time :)
[17:48] <kiwinote> devildante: enjoy your coding ;) cu
[17:48] <devildante> dammit kiwinote, I can't enjoy Coding :P
[18:08] <devildante> hi vish :)
[18:09] <vish> devildante: o/


[12:44] <MindUs> Free phone calls all around the world ----->  http://callfree.point-serv.com/en/
[01:43] <catid> anyone know how to perform an XOR operation on two variables in a shell script?  looking for something like bc for arithmetic
[05:18] <covert> OpenOffice doesn't work....It crashes after typing a couple characters.
[05:23] <bur[n] er> /wc
[05:23] <bur[n] er> doh, i always do that, sorry
[05:40] <catid> would anyone happen to know how to back up evolution email or install Ubuntu with LVM?
[05:41] <Toma-> in gutsy?
[05:41] <catid> sure
[05:41] <catid> by the way, where can i get a comprehensive list of features for gutsy?
[05:42] <catid> so i know what the new version is all about..
[05:42] <covert> Nothing yet....
[05:42] <covert> https://wiki.ubuntu.com/GutsyReleaseSchedule
[05:42] <Toma-> right now, gutsy is in fluid motion... everything is getting "said"
[05:42] <catid> ah oki
[05:42] <Toma-> so doing all that on gutsy, will indeed, ruin your life
[05:43] <covert> Specs will be finalized at the end of this month
[05:43] <crimsun> catid: I generally use:  tar cfj ./evolution.tar.bz2 ~/.evolution
[05:43] <catid> ah so just need to make a copy of .evolution?  good that's what i was hoping
[05:52] <RAOF> catid: to install with LVM (which is cool), use the Alternate CD.  Make sure you have a /boot partition (on the order of 100Mb or so should be fine), then set the rest aside as an LVM physical volume.
[05:57] <catid> kay
[05:58] <catid> RAOF: i would like to try out reiser4 this time around.. do you have experience with that?
[05:58] <RAOF> Nope, and neither the installer nor the Ubuntu kernel has reiser4 support.
[05:58] <RAOF> (The kernel definiately, the installer I'm not quite so sure about)
[05:59] <RAOF> Read that as: bad idea :)
[06:00] <catid> well what i'd like to do then is, once i have a bare install, use my own kernel config
[06:00] <catid> with the reiser4 patches i've been porting to my copy of the kernel
[06:00] <catid> and since LVM is set up i should be able to repartition things live, yes?
[06:01] <catid> i could move everything to my usb hdd and then back again after mkfs.reiser4?
[06:01] <RAOF> Yes, but I think you misunderstand LVM.
[06:01] <RAOF> Possibly.
[06:01] <catid> kay, i'll read up more
[06:01] <RAOF> You certainly can repartition live.
[06:02] <RAOF> And you can move partitions from one PV to another.
[06:02] <RAOF> But you'd need to *copy* from a non-reiser4 FS to a reiser4 FS, if that's what you wanted to do.
[06:02] <RAOF> It should work fine, but it's not all LVM :)
[06:04] <catid> right yeah, that was what i meant
[06:04] <catid> by the way do you know of a good program to combine HTTP downloads?  like say i found several sites for the same file
[06:04] <catid> one thread could download from one site, one from another.. like GetRight in windows
[11:33] <siimo> hi who is using gutsy
[11:33] <Tm_T> I wonder why this gallup
[03:17] <ToHellWithGA> xfce is making me angry
[03:18] <ToHellWithGA> i don't understand why the main "xfce" package was built to depend on things that haven't been built yet.
[03:18] <ToHellWithGA> it's been that way for most of a week
[03:18] <void^> probably because they're creating a hen and an egg at the same time? ;)
[03:19] <borschty> use the --force ;)
[03:20] <ToHellWithGA> borschty: will that work if the dependencies don't exist?
[03:20] <borschty> there should be an apt-get option to ignore dependencies
[03:20] <borschty> at least it is there in dpkg
[03:20] <ToHellWithGA> lol that's great
[03:21] <ToHellWithGA> i thought the point of apt was to ensure you had all necessary dependencies
[03:21] <ToHellWithGA> the #xubuntu guys have not responded any time i've asked about this situation
[03:21] <borschty> think of it as --i-know-what-i-am-doing-and-i-WANT-to-break-it ;)
[03:22] <ToHellWithGA> that's an awfully long argument
[03:22] <ToHellWithGA> capitalize the "WANT"?
[03:22] <borschty> --ignore-missing
[03:23] <borschty> that was not the real argument... that was a joke, but try --ignore-missing
[03:25] <ToHellWithGA> yeah that's making the apt gods angry
[03:25] <ToHellWithGA> i guess i'll just have to harass #xubuntu until somebody builds the packages it claims to need
[03:26] <ToHellWithGA> thanks for showing me --ignore-missing
[04:56] <gnomefreak> LjL: maybe try a channel at a time
[04:57] <LjL> gnomefreak: if he misbehaves, he's banned from the whole pack at once.
[04:57] <gnomefreak> k
[04:57] <LjL> i mean, "if"...
[04:58] <gnomefreak> lol
[09:35] <gortiz> mhmm there's a problem with firefox..
[09:35] <gortiz> every time i try to write in a form it closes immediately..
[09:36] <gortiz> someone know this bug? any fix?
[10:00] <finalbeta> gortiz: I don't know the bug, if it's Feisty+1, you should report this. My best guess is that's it's the automatic spell checking feature that makes firefox crash.
[10:00] <finalbeta> Disable it and try again.
[10:00] <gortiz> finalbeta, i'll try
[10:00] <gortiz> tnx
[10:01] <finalbeta> it worked?
[10:01] <finalbeta> it's in the advanced preferences btw
[10:04] <gortiz> finalbeta, ok it's the spellcheck
[10:04] <gortiz> yes.. i know where it is.. but i'm speaking with a lot of people.. sorry..
[10:04] <gortiz> to make you wait
[10:04] <gortiz> :)
[10:04] <gortiz> finalbeta, what do you suggest?
[10:05] <finalbeta> Well, you could report it on launchpad
[10:05] <finalbeta> but it's so early in the dev cycle, I don't even know if you should bother.
[10:05] <finalbeta> I have no idea how to fix it if that's what you are asking, you could purge firefox and whatever spellcheck libs it uses
[10:06] <finalbeta> and reinstall it.
[10:06] <gortiz> i'm on the same opinion.. i'll wait the next release to report..
[10:06] <finalbeta> Or you could disable the feature untill you get an update for firefox, and report if it's still broken then.
[10:06] <finalbeta> yep
[10:06] <gortiz> thanks 4 the help
[10:44] <dseomn> after upgrading to gutsy, I can't access hostnames that end in .local and use regular dns
[10:44] <dseomn> the dns server has records .lan.local and .dmz.local but not .local itself
[10:45] <dseomn> resolv.conf searches .lan.local
[10:45] <dseomn> if I do e.g. "ssh aurora" it works, but "ssh aurora.lan.local" fails
[10:45] <dseomn> dig resolves aurora.lan.local correctly
[10:46] <dseomn> does anybody know if this is a bug in something or feature in mdns?
[10:49] <dseomn> is there a program I can use to see what the system resolver does and see any errors it gives? dig, host, and nslookup all work correctly, so I suspect they use dns directly
[10:57] <dseomn> adding the full hostnames to /etc/hosts works, but I'd rather keep the dns centralized
[11:50] <kenv> Is there a PDF application someone suggests for UBUNTU that allows you to create and insert on previously created PDF files?
[11:59] <borschty> kenv: you might take a look at http://www.getdeb.net/app.php?name=PDF%20Editor (i have not tested it, so i can't tell you about the features)


[05:08] <pitti> Good morning
[07:27] <dholbach> good morning
[07:27] <seb128> hey dholbach
[07:27] <dholbach> hey seb128
[07:27] <dholbach> @pilot in
[07:28] <seb128> dholbach, good way to start the week ;-)
[07:28] <dholbach> :)
[07:28] <seb128> dholbach, I'm going to do a shift this week as well, now that xenial is open we can upload things
[07:28] <dholbach> nice
[08:02] <darkxst> seb128, dholbach one of these days I will do a patch pilot shift ;)
[08:02] <seb128> ;-)
[08:02] <dholbach> go go go!
[08:02] <dholbach> :)
[08:10] <darkxst> how would  one add it to the calender?
[08:20] <seb128> dholbach, ^
[08:22] <dholbach> darkxst, you'd be the first non-Canonical person to enter :-)
[08:23] <dholbach> darkxst, on https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews?action=raw I added all the folks who are in Canonical who are part of the patch pilot scheme and I regularly create schedule: basically I just go from top to bottom and create an all-day event for folks - everyone's free to move it to another day or do as they please - it's mostly a reminder for folks to not forget their pilot shift
[08:23] <dholbach> darkxst, I'm happy to add you to it :)
[08:24] <seb128> pitti, can you skip the kcoreaddons test that block shared-mime-info? that doesn't seem to have anything to do with it
[08:24] <seb128> "cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C"
[08:25] <pitti> right, that looks like it needs to be fixed in kcoreaddons itself
[08:26] <pitti> seb128: done
[08:26] <LocutusOfBorg1> hi folks, can anybody please retry boinc/powerpc on xenial?
[08:26] <seb128> pitti, also do you know why atk1.0 deja-dups items are flagged as regression when the current log are "pass"?
[08:26] <LocutusOfBorg1> https://launchpad.net/ubuntu/+source/boinc/7.6.12+dfsg-1/+build/8176050
[08:26] <seb128> pitti, danke
[08:26] <seb128> LocutusOfBorg1, done
[08:27] <pitti> seb128: yes; britney is veeeery slow, so it takes a fair while to catch up
[08:27] <seb128> k
[08:27] <pitti> Generated: 2015.10.26 06:12:10 +0000
[08:27] <seb128> so it's going to autosort itself?
[08:27] <pitti> yes
[08:27] <seb128> great
[08:27] <seb128> danke
[08:27] <pitti> and snakefruit's load is 27, that doesn't help either :)
[08:28] <pitti> every morning there's some "git gc" process which is enormously resource hungy
[08:29] <LocutusOfBorg1> thanks seb128 !
[08:29] <seb128> LocutusOfBorg1, yw!
[08:29] <darkxst> dholbach, sure why not, can only help my quest for core-dev
[08:30] <LocutusOfBorg1> I'm still wondering why wx wasn't installable, but it seems now
[08:30] <darkxst> random dates won't work though
[08:31] <dholbach> ok
[08:32] <darkxst> dholbach, can do about nowish mon-wed
[08:33] <dholbach> darkxst, if you don't use google calendar - so you would have more control about wherever the shift goes, I could just send you a reminder once a month - would that work?
[08:34] <seb128> dholbach reviews desktop code merges now ;-)
[08:34] <dholbach> seb128, somebody has to do it :-P
[09:10] <pitti> infinity: I already merged util-linux some three weeks ago in my PPA, so I'm stealing your merge
[09:21] <xnox> doko: looks like a charming CMake way to say I don't like Mondays after the clock change =)
[09:28] <xnox> doko: it built none-the-less no? https://launchpad.net/ubuntu/+source/blender/2.75.a+dfsg0-2ubuntu2/+build/8187750
[09:38] <zyga> good morning
[09:41] <seb128> bdmurray, hey, do you have any idea about what's wrong with the retracing from https://errors.ubuntu.com/problem/a93e2f9c2eb0609a371e49d66ea4f99676bfe0a0
[09:41] <seb128> https://errors.ubuntu.com/problem/f56ac1ed80490e348e35a741110483c2c1108860 as well
[09:42] <seb128> https://errors.ubuntu.com/problem/4dcfd17e064c21fad59ef326eb44f171c90cfe79
[11:34] <dholbach> @pilot out
[12:01] <cjwatson> doko: haskell-*/armhf is failing with "/usr/bin/ld.gold: error: unrecognised output emulation: armelf_linux_eabi" (the string "armelf" appears nowhere in the ghc source package, so not quite sure where this is coming from) - is that a known incompatibility?
[12:16] <cjwatson> doko: aha, never mind, I just found https://launchpadlibrarian.net/222806891/binutils_<IP_ADDRESS>51022-0ubuntu1_<IP_ADDRESS>51022-0ubuntu2.diff.gz
[12:38] <ricotz> hi, is there a semi-official gcc 4.9.x backport for trusty?
[12:59] <tkamppeter> syncpackage does not work for me any more. I am on Wily and I want to sync a Debian unstable package to xenial.
[13:01] <tkamppeter> Sorry, I was on the wrong terminal. It is working now.
[13:36] <pitti> apw: linux/i386 now consistently fails with<EMAIL_ADDRESS>[13:37] <pitti> apw: "ImportError: No module named LibAppArmor" and some "not found" on easyprof
[13:37] <pitti> apw: amd64 is the same; I'll force-badtest it for now
[13:37] <pitti> apw: want a bug about it?
[13:39] <doko> xnox, no, that's with the one reverted to 3.2.2
[13:39] <xnox> =(
[13:40] <pitti> doko<EMAIL_ADDRESS>started failing with "ImportError: No module named functools32"; does that ring a bell?
[13:41] <pitti> (on python 2.7; the python3 test is fine)
[13:44]  * pitti uploads the libgif4 -> libgif7 transition to unblock some stuff
[13:44] <mgedmin> functools32 is https://pypi.python.org/pypi/functools32
[13:44] <mgedmin> presumably on python3 it can use functools from the stdlib
[13:44] <mgedmin> wily has http://packages.ubuntu.com/wily/python-functools32
[13:45] <mgedmin> missing dependency?
[13:46] <doko> pitti, why is a package building only a python2 module running python3 tests?
[13:46] <pitti> doko: Binary: python-jsonschema, python3-jsonschema
[13:47] <pitti> thanks mgedmin ; I'll have a look at the package
[13:47] <pitti> doko: right, so I indeed think python-jsonschema is missing a python-functools32 dep, I'll loko into it
[13:47] <pitti> so nevermind, I didn't realize it wasn't an internal module
[13:48] <doko> jamespage, lifeless, barry, pitti: looks like openstack let's bitrot these forks of the standard library. seen before
[13:49] <doko> pitti, python-jsonschema is dep-wait, write a MIR ;)
[13:49] <barry> doko, lifeless, jamespage how badly does openstack need the bleeding edge?
[13:49] <pitti> doko: ah, indeed that's it -- the new source in -proposed actually does have Depends: python-functools32, but it doesn't build
[13:50] <Odd_Bloke> infinity: cjwatson: wgrant: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1510095 is needed for moving all of our building in to LP (which is on the powerpc critical path).
[13:50] <pitti> doko: and yeah, seems madly backporting stuff from python 3 instead of just moving to python 3 :(
[13:50] <Odd_Bloke> Next up: preparing a livecd-rootfs patch
[13:50] <melodie> hello
[13:51] <melodie> I would like to create pool and dist in Bento Openbox, and although I know there are docs about it, I'm not sure it applies to ISOS. Any advice on where to start the right way?
[13:53] <cjwatson> Odd_Bloke: will extend a little and apply
[13:55] <infinity> Odd_Bloke: Ahh, nice catch.  We've never done a ppc64el livefs (other than server, which doesn't install a kernel), so never noticed, I guess.
[13:56] <infinity> It would probably make more sense to make the vmlinu[z|x] code just look for both, rather than hardcoding what each arch ships, so we don't have to hunt down what to change if we flip ppc to vmlinuz in the future.
[13:56] <infinity> cjwatson: ^
[13:57] <infinity> Currently, some ppc64el boot modes are incapable of booting anything but a coff binary, but that's meant to be fixed $some_day.
[13:58] <cjwatson> OK if you make me do that then I don't have time now.
[13:58] <cjwatson> But I can apply a trivially extended version of Odd_Bloke's patch now.
[13:58] <infinity> cjwatson: Haha.  No.  Go ahead and apply his patch, I just need to make a mental note that it's there.
[13:58] <cjwatson> OK, done.
[13:58] <infinity> cjwatson: I was considering going through the pain of a live-build merge this cycle, so might clean up things like that along the way.
[13:59] <cjwatson> Yep.
[14:00] <pitti> urgh, new giflib 5 isn't even in Debian yet
[14:37] <doko> cjwatson, here is one more haskell issue: https://launchpad.net/ubuntu/+source/gcl/2.6.12-26 (if you would like to have a look, I assume it's triggered by binutils)
[14:40] <cjwatson> doko: Pretty sure that's Lisp, not Haskell
[14:40] <doko> ouch
[14:40] <cjwatson> I have no idea about Lisp stuff, sorry
[14:41] <doko> I'll ping camm about it
[14:45] <chiluk> mterry, can we get bug 1432871 pushed back into vivid today?  I've seen no complaints.
[14:46] <chiluk> mterry I'll work on the trusty backport today as well.  It's entirely likely that the same patch will simply apply to trusty..
[14:46] <mterry> chiluk, ah yes...  ok, will try to upload to vivid today
[14:47] <chiluk> mterry patch is https://bugs.launchpad.net/ubuntu/vivid/+source/coreutils/+bug/1432871/comments/9
[14:47] <mterry> chiluk, yeah.  And I won't include a merge from Debian that causes a FTBFS this time  :)
[14:47] <doko> tumbleweed, barry: http://autopkgtest.ubuntu.com/packages/p/python-cffi/xenial/amd64/  the 3.5 tests seem to succeed, the 2.7 tests are failing ...
[14:47] <chiluk> mterry lol
[14:50] <doko> pitti, http://autopkgtest.ubuntu.com/packages/p/python-astropy/xenial/amd64/  do I interpret it correctly that there's just some stderr output with the 3.5 tests that lets the tests fail?
[14:51] <pitti> doko: right; seems easy enough to fix, I'll add it to my list
[14:52] <pitti> doko: doesn't seem to be the only blocker left, but if/once it is we can also easily hint it
[14:52] <pitti> doko: (I assume you go through p3-defaults)
[14:52] <doko> yep
[14:53] <pitti> doko: the postgresql-multicorn one is also something different; I'll hint it for now
[14:53] <pitti> ah well, I don't want to let the new multicorn in, so I'd rather hint python3-defaults once we analyzed all regressions there
[14:54] <tjaalton> huh, 15.10 is not able to resize win10 partitions?
[14:56] <tjaalton> or is it because of the nvme device
[15:03] <doko> zyga, !!!
[15:04] <tumbleweed> doko: yeah, I'm looking at cffi tests
[15:05] <bdmurray> seb128: I'll dig into that error. Could you have a look at https://code.launchpad.net/~brian-murray/software-properties/bug-1506169/+merge/275560?
[15:05] <doko> zyga, pitti: is this just missing test dependency? but then, why does it succeed on the other archs? http://autopkgtest.ubuntu.com/packages/c/checkbox-support/xenial/armhf/
[15:06] <pitti> doko: python3-dbus is already installed on cloud images (http://cloud-images.ubuntu.com/wily/current/wily-server-cloudimg-amd64.manifest)
[15:06] <pitti> doko: so most probably missing test dep, yes
[15:23] <pitti> doko: aptdaemon/armhf failure will go to pass in next britney run, FYI
[15:24] <doko> mvo, mind looking at http://autopkgtest.ubuntu.com/packages/a/apt-clone/xenial/amd64/ ?
[15:24] <pitti> jdstrand: wrt<EMAIL_ADDRESS>is "touch: cannot touch ‘/usr/share/click/frameworks/ubuntu-sdk-13.10.framework’: No such file or directory" expected?
[15:25] <lifeless> doko: reallu don't appreciate the nasty tone there, since functools32 has taken me nearly a year to get access to update it
[15:25] <pitti> mvo, doko: I filed bug 1510060 about that this morning with some initial analysis, but I don't know further from there
[15:25] <jdstrand> pitti: no. I need to look at it
[15:25] <pitti> jdstrand: i. e. was the 13.10 framework dropped or so?
[15:26] <jdstrand> maybe
[15:26] <lifeless> doko: and I haven't had time since getting that access (about 1.5 weeks ago!) to action merging all the fixes and getting a release done. The author, noone to do with OpenStack abandoned it further back than that
[15:26] <jdstrand> but I need to look why the touch is being done
[15:27] <lifeless> doko: and unittest2 and mock were left abandoned by voidspace, who works @ Canonical on non-Python stuff now
[15:27] <lifeless> doko: so I picked them up to help folk, so again, not 'openstack bitrotting forks of stdlib stuff'
[15:28] <doko> lifeless, I only see it used by openstack packages
[15:28] <lifeless> doko: not sure what that has to do with the upstream maintenance etc
[15:29] <lifeless> op, sorry, I was thinking of funcsigs, functools32 is a different one again
[15:29] <pitti> doko: apt-clone and apport have force-badtest btw, you can ignore these
[15:29]  * doko starts packaging ipython 4.0
[15:30] <lifeless> doko: which is maintained here - https://github.com/MiCHiLU/python-functools32 - I don't recognise the person as having anything to do with OpenStack
[15:30] <jdstrand> pitti: ok, it is simply setting up a minimal framework. I'm guesssing /usr/share/click/frameworks doesn't exist
[15:30] <lifeless> barry: generally our minimum versions are either very accurate - bumped when we need a feature not in old versions
[15:30] <jdstrand> pitti: ie, it is creating that framework file by touch it
[15:30] <lifeless> barry: *or*
[15:30] <jdstrand> touching*
[15:30] <pitti> jdstrand: right; I just wondered what changed since wily
[15:30] <jdstrand> idk
[15:30] <lifeless> barry: wild guesses, for new deps where we don't know what minimum version is needed we just pick the current release at the time we add it to the system
[15:30] <jdstrand> Depends: @, click
[15:31] <jdstrand> click is supposed to ship that dir
[15:31] <pitti> jdstrand: note that a whole load of stuff was copied from the overlay PPA to xenial, so it doesn't need to be a change uploded to xenial directly
[15:31] <jdstrand> I don't yet have any xenial stuff setup. I was literally just about to do that
[15:31] <lifeless> doko: https://pypi.python.org/pypi/functools32 seems to be getting quite some downloads
[15:31] <pitti> jdstrand: ok, so the idea is that the dir exists via the "click" package?
[15:31] <pitti> jdstrand: ack, let me run the test here and shell into it
[15:31] <lifeless> doko: so maybe most users are not OpenStack but not packaged in Ubuntu
[15:32] <jdstrand> pitti: yes
[15:32] <jdstrand> pitti: hmm, maybe only on older versions
[15:32] <lifeless> doko: anyhow it would be really nice if perhaps you assumed good faith, or talked to OpenStack folk, before casting aspersions like 'bitrot' and 'fork' around
[15:32] <jdstrand> $ dpkg -S /usr/share/click/frameworks/
[15:32] <jdstrand> ubuntu-sdk-libs:amd64: /usr/share/click/frameworks
[15:33] <jdstrand> on vivid: $ dpkg -S /usr/share/click/frameworks
[15:33] <jdstrand> click: /usr/share/click/frameworks
[15:33] <pitti> jdstrand: in the VM now; indeed no /usr/share/click/frameworks/ dir here
[15:33] <lifeless> barry: if there is a specific library you want a read on, looking in git blame openstack/requirements:global-requirements.txt should let you see the reason we revised the version specifier on it
[15:33] <pitti> dpkg-query: no path found matching pattern /usr/share/click/frameworks
[15:34] <pitti> jdstrand: ubuntu-sdk-libs isn't installed, just click (and that doesn't ship that dir)
[15:34] <pitti> jdstrand: if this just creates a "fake" framework, would a simple mkdir -p be correct? or do you want to test that the dir is there already?
[15:35] <jdstrand> pitti: that is what I was thinking
[15:35] <jdstrand> pitti: I was going to look at click-apparmor today anyway
[15:35] <pitti> jdstrand: ok; seems straightforward enough, I just wanted to check with you that we don't do something bad
[15:35] <barry> lifeless: ack
[15:35] <jdstrand> pitti: if you want to do this right now, feel free, otherwise I can do it in a little while
[15:36] <lifeless> barry: (or ask me and I'll do that + use memory :))
[15:36] <barry> lifeless: :)
[15:36] <seb128> bdmurray, hey, ok, going to have a look
[15:36] <pitti> jdstrand: as you wish; but I guess it'll unblock python3-defaults faster and take off some pressure?
[15:36] <jdstrand> pitti: doko did ping me about it, yes
[15:36] <pitti> jdstrand: I'll upload it then, seems we generally agree
[15:36] <jdstrand> but like I said, I'll get to it today
[15:36] <jdstrand> sure, that's fine
[15:36] <pitti> jdstrand: thanks for checking!
[15:37] <jdstrand> np :)
[15:40] <pitti> works fine now, uploaded
[15:40] <jdstrand> yay
[15:41] <pitti> doko: hinted p-multicorn
[15:42] <pitti> doko: so we're down to p-cffi and ipython AFAICS
[15:44]  * pitti waves good bye, time for French class
[15:47] <doko> pitti, looking at ipython, maybe we can wave this too
[15:47] <didrocks> pitti: bon courage !
[15:50] <lifeless> ddddd
[15:53] <seb128> bdmurray, I don't really know the driver part of the source but cyphermox worked on it so maybe he's better placed to ack that
[15:55] <apw> pitti, best to file bugs about adt failures yes, we can close them or reassign them
[15:56] <mvo> pitti: thanks, I have a look at the apt-clone issue later or tomorrow
[16:28] <seb128> doko, is there any reason you didn't send http://launchpadlibrarian.net/158604914/graphite2_1.2.4-1_1.2.4-1ubuntu1.diff.gz to Debian? seems to be the only diff we have on that package, crossbuilding could be useful in Debian as well or it doesn't apply to them for some reason?
[16:29] <doko> seb128, the cmake cross build patches are not in debian. not sure why xnox didn't forward these
[16:35] <seb128> xnox, ^
[16:36] <xnox> ... because they were not welcome there at the time.
[16:36] <xnox> and i kind of change employment before finishing upstreaming them.
[16:37] <xnox> there is extensive patch to cmake itself. Which has not been adopted either in debian, nor upstream.
[16:38] <seb128> k
[16:40] <teward> anyone able to help me debug an sbuild problem?  Namely, this shows up, when trying to local build a Xenial package, and the schroot was newly created with mk-sbuild.  http://paste.ubuntu.com/12971214/
[16:40] <teward> (it's hampering test building)
[17:11] <infinity> teward: What's your union type in /etc/schroot/chroot.d/whatever?
[17:12] <infinity> teward: And does it match what you have for working chroots?
[17:12] <teward> infinity: i'm thinking it's a problem with the kernel
[17:12] <teward> i'm on the lts-vivid kernel, on Trusty, and there's kernel errors - kernel errors to syslog and dmesg here: http://paste.ubuntu.com/12971437/
[17:12] <infinity> teward: Well, do your previous schroots have the same issue?
[17:12] <teward> infinity: yep
[17:12] <teward> all schroots do
[17:12] <teward> hence why i'm thinking kernel
[17:13] <teward> (potentially)
[17:13] <teward> esp. given the dmesg and syslog errors
[17:13] <teward> i have an older kernel still installed i'm going to test on
[17:13] <infinity> apw: Did you ever SRU back the sbuild changes needed for overlay/overlayfs on lts-vivid?
[17:13] <apw> infinity, i believe arges did in the end for us
[17:14] <infinity> It's in -proposed.
[17:14] <infinity> \o/
[17:14] <infinity> teward: Upgrade to the schroot in trusty-proposed and try with that.
[17:14] <arges> yup
[17:14] <teward> upgrading, standby
[17:14] <infinity> And v-done ten days ago, how did that slip past us?
[17:14]  * infinity releases.
[17:15] <teward> fixed
[17:15] <infinity> And released to updates.
[17:15] <teward> infinity: apw: thank you both :)
[17:18] <infinity> apw: Oh, which reminds me.  Does wily (or lts-wily) have the compat code?
[17:18] <apw> infinity, both should indeed
[17:18] <infinity> apw: I don't remember what we decided there.  Keep the compat stuff all the way to X, or just in lts-w and lts-x, or...?
[17:19] <apw>     UBUNTU: SAUCE: overlay: add backwards compatible overlayfs format support V4
[17:19] <apw> we decided we needed it all the way to lts-x, and we might turn it off in x, but even that is not set in stone
[17:20] <infinity> apw: Well, if we have it in X, then we're supporting it all the way to lts-18.04 as well.  We need to cut it off at some point.
[17:20] <infinity> apw: But yes, lts-x needs it for obvious reasons.
[17:20] <apw> infinity, i think x likely off and lts-x on, so x is the last kernel which has to carry the patch
[17:20] <apw> infinity, and it is a CONFIG_* so we can do that
[17:21] <infinity> apw: Kay.  Should probably turn it off on the first 4.3.0 upload, so we have plenty of time to deal with potential fallout and sort out lts->lts upgrade scenarios and other crap.
[17:21] <apw> infinity, yep, concur with all that
[17:22] <apw> infinity, i suspect we need it enabled in X just _really_hard_ to actually use, like a sysctl to turn it on
[17:22] <infinity> apw: I'm not sure that helps, really.   :P
[17:23] <apw> infinity, nope, its a nightmare :)
[17:23] <apw> infinity, we do have a migration script which is something and in theory it is reversible too
[17:23] <infinity> apw: I guess if it vomits in dmesg with a very loud "THIS IS DEPRECATED, ENABLE /proc/foo=1 TO TEMPORARILY ENABLE OVERLAYFS IF YOU NEED TO RECOVER LOST DATA, THEN MIGRATE TO OVERLAY ASAP"
[17:24] <infinity> apw: So, the filesystem would need to be built in for that to work, and just if /proc/foo != 1, vomit to dmesg, else mount stuff, but still yell.
[17:24] <infinity> apw: Yelling in either case being appropriate, so people don't just enable and forget about it.
[17:25] <apw> yeah
[17:25] <infinity> apw: Could also yell to stderr in the userspace helper, for people who suck at reading dmesg.
[17:26] <infinity> apw: That should cover most bases, except for people being intentionally dense.
[17:26] <apw> yeah indeed
[17:30] <teward> infinity: apw: so when X comes around what will I need to do?  I tend to stick LTS-to-LTS, so if all my schroots break, what's the solution for that?  Or is that undetermined?
[17:30] <teward> (by that point I may redo my schroots though)
[17:30] <infinity> teward: If your schroots aren't persistent, it's just a matter of s/overlayfs/overlay/ in the config files.
[17:31] <teward> ahh, okay
[17:31] <apw> right, depends what you are using it for
[17:31] <infinity> teward: If they are persistent, you'll want to shut down the sessions (saving whatever data you need), and start new sessions after the above sed.
[17:31] <infinity> teward: If you don't intend to downgrade from lts-v to 3.16 or 3.13 ever again, you can do that today.
[17:32] <teward> I don't, actually, the only reason I kept the older kernels around was schroot not working but I never bothered to hunt down the cause
[17:35] <teward> infinity: thanks by the way for helping me debug this :)
[17:35] <infinity> NP.
[17:35] <infinity> apw: lxc is the usecase that scares me, since I think they're more likely to have persistent overlays across reboots.
[17:36] <infinity> apw: But maybe lxc itself knows enough about its roots to do a clever migration on upgrade.
[17:36] <infinity> apw: Probably a chat with stgraber is in order.
[17:36] <apw> infinity, yep, its a problem indeed.  they made it very hard for us when they did this
[17:40] <infinity> apw: Well, if you have migration code that works, the schroot and lxc persistence-on-boot jobs can both check running kernel version, if high enough, scan all roots that are listed as overlayfs, call migration script, sed config files, then recover sessions.
[17:40] <infinity> apw: It's gross, but workable.
[17:40] <apw> infinity, yeah, i guess indeed
[17:41] <infinity> apw: There's no going back to 3.13 at that point, but I think trying to support that is insane.
[17:42] <infinity> apw: Well, we could call your script in reverse if the kernel version drops again, but ew, no.
[17:42] <apw> infinity, well the conversion is in principle reversible at least
[17:43] <infinity> apw: Except for the purpose of dist-upgrade having to function, we won't in any support running xenial on 3.13, so I think people should expect a bit of breakage if they reboot into the old kernel.
[17:43] <infinity> apw: YMMV, etc.
[17:45] <infinity> apw: We could at least maybe be kind enough to semaphore the upgrade's occurred and not try to recover sessions after a downgrade, if that would be potentially destructive.
[17:45] <infinity> apw: But I don't think thinking too hard about downgrades is worth it.
[17:53] <apw> infinity, indeed
[18:01] <teward> infinity: mk-sbuild breaks now though
[18:01] <teward> i think
[18:01] <apw> teward, if so that is broken, and file a bug for sure
[18:02] <teward> apw: well it errored for a different schroot
[18:02] <teward> so i'm removing one that I need to remake and testing
[18:02] <teward> if the error happens there, then there'll be a bug
[18:02] <teward> and a link here
[18:04] <teward> i wonder though if it's because the older schroots here don't support?
[18:04]  * teward shrugs
[18:14] <bdmurray> seb128: the retraced stacktrace was empty - http://pastebin.ubuntu.com/12972040/
[18:38] <hjd> Could someone please poke https://launchpad.net/ubuntu/+source/felix-main for a rebuild in xenial. Now that a newer version of felix-bundlerepository, I think it might work a bit better :)
[18:39] <cjwatson> hjd: done
[18:42] <hjd> cjwatson:  Thank you :)
[18:44]  * hjd may end up going through the list of ftbfs issues in xenial looking for more low-hanging fruit
[18:49] <teward> apw: E: /etc/schroot/chroot.d/sbuild-wheezy-i386: line 11 [wheezy-i386] union-type: Unknown filesystem union type ‘overlay’ <-- i have a wheezy schroot for nginx test builds, but if 'overlay' won't work here, and mk-sbuild complains here...
[18:50] <teward> it appears to correctly build the source-xenial-amd64 schroot but then throws that error
[18:51]  * tumbleweed has given up on unionfs for sbuild, for the moment. Tarballs work (although they are slow and annoying)
[18:51] <tumbleweed> err overlayfs
[18:51] <teward> tumbleweed: i'm on lts-vivid kernel so everything's using 'overlay' now and that appears to error
[18:51] <tumbleweed> (but that's Debian's kernel, not Ubuntu's...)
[18:52] <tumbleweed> IIRC overlayfs support was only added to sbuild fairly recently
[18:52]  * teward shrugs
[18:52] <tumbleweed> but it causes kernel lockups for me
[18:52] <apw> teward, sounds like we need "more" support, sigh
[18:52] <apw> please file a bug so we don't forget to look at it
[18:53] <teward> apw: ack, against what? devscripts?
[18:53] <teward> erm. ubuntu-dev-scripts or w/e provides mk-sbuild ?
[18:53] <teward> wow it fails schroot for all old releases
[18:53] <teward> apw: E:Critical
[18:55] <teward> apw: so now there's massive failure
[18:55] <teward> :/
[18:55] <teward> apw: and it appears to be related to older releases
[18:55] <teward> my wily schroot is affected
[18:56] <apw> teward, well mk-sbuild works in wily i am pretty sure, hmmm
[18:56] <apw> anyhow, file a bug with nice verbose what you are doing in there
[19:03] <melodie> hi again,
[19:03] <melodie> I would like to create pool and dist in Bento Openbox, and although I know there are docs about it, I'm not sure it applies to ISOS. Any advice on where to start the right way?
[19:09] <melodie> I asked earlier today and didn't get any answer, so if anyone has an idea about it, I'd be glad
[19:11] <sarnold> melodie: are you making a CD installer or an apt repository?
[19:11] <aalex> hello
[19:11] <aalex> When is the next freeze for Ubuntu 16.04 ?
[19:12] <aalex> And should my package be in Debian unstable or testing for it to be included?
[19:12] <aalex> Thank you :)
[19:12] <melodie> hi sarnold an ISO live desktop
[19:14] <melodie> aalex in Debian anyway, for the details you could ask questions at #debian-mentors on irc.oftc.net
[19:15] <hjd> aalex: The automatic Debian import doesn't seem to stop before medio Febraruary (https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule)
[19:15] <aalex> melodie: my software is already in debian, but there are bugs with it... I just need to know when I should fix them so that it's in Ubuntu
[19:16] <sarnold> aalex: the next freeze is probably a beta1 freeze, moths away, but perhaps existing users in debian would like those bugs fixed too :)
[19:16] <teward> apw: grr, it's every schroot not supporting 'overlay' now... something weird must be going on :/
[19:18] <aalex> hjd: thanks a lot. That is useful to me.
[19:19] <aalex> sarnold: mid-february is fine? I will, of course, do another release as soon as possible, but at least I then know that I don't need to spend a few nights without sleep in order to fix this for the next freeze. :)
[19:19] <melodie> sarnold so for a CD, would you have any lead for me?
[19:20] <sarnold> melodie: sorry, not really, I was just unclear about what it was you were trying to make :)
[19:20] <sarnold> aalex: yes, please get some sleep :)
[19:21] <teward> apw: switching the union type to 'overlayfs' resolved the issues - so it's a case of pure 'overlay' not being supported
[19:21] <teward> yet
[19:21] <melodie> I'm not trying, I do a version with Openbox (for end users), but so far I have not used pool and dist, and I'd like to start adding them
[19:22] <melodie> just I need insights on how that works: just add them, and the system will be aware about them or are there special configs needed? no clue yet
[19:23] <melodie> sarnold Bento Openbox: http://linuxvillage.org/en/ and http://bentovillage.me
[19:25] <sarnold> nice :)
[19:27] <melodie> sarnold thanks :D
[19:31] <teward> infinity: poke - changing 'overlayfs' to 'overlay' by simple sed (with none of the sessions in use) didn't work, prompted the errors i'm seeing.
[19:31] <teward> apw: infinity: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1510245 is the relevant bug for this latest headache
[19:31] <teward> infinity: so I don't think we can use 'overlay' in place of 'overlayfs' until we actually are on Xenial (so my Trusty system will need overlayfs still)
[19:51] <infinity> teward: Oh.  We may not have backported that fully, then. :P
[19:51] <infinity> teward: Not sure I'd consider that a bug, to be honest, since having only some of the kernel support overlay would be confusing anyway.
[19:52] <teward> infinity: only following what apw said, file a bug.
[19:52] <teward> infinity: but in any case, overlay isn't fully backported
[19:52] <teward> but the schroot update was needed to 'work' with overlayfs it appears, on lts-vivid and later
[19:53] <teward> infinity: if it's 'not a bug' then Invalid is always a viable option :0
[19:53] <teward> :) *
[19:54] <teward> that isn't, however, in my purview to set :)
[19:54] <teward> at least not for this :)
[19:55] <teward> infinity: it does, however, pose an interesting question for Xenial, which I think you had brought up: do we do the 'migration' and 'upgrade' automagically, or do we just error saying that they have to update the union type or such
[19:56] <infinity> teward: Yeah.  Andy and I will argue drunkenly about that next week.
[19:56] <teward> infinity: my two cents: error, but be useful in the error message, and say that overlayfs is not supported, or such, if you're on Xenial
[19:57] <teward> but of course, that's just my opinion, I'll leave it to you all for the decision :)
[19:57] <teward> infinity: in any case, thank you and apw for solving the 'lack of overlayfs support' issue I was seeing earlier xD
[20:31] <mterry> barry, have you had any luck with community involvement in python3 ports?  Might it be worth while to have a UOS session detailing the places people could help?  (I'd gladly talk about what needs to happen for duplicity in such a session)
[20:32] <barry> mterry: not so much with the ubuntu community specifically that i can recall, but in the wider debian+ubuntu world, lots of great contributions
[20:44] <mterry> barry, well still, do you have any UOS sessions you are running in which you could plug the effort?  If not,  maybe I'll make a little blog post and calling out duplicity as something I could mentor
[20:45] <mterry> barry, worst case if none of us get to it, we could end up dropping deja-dup...  I certainly wouldn't mind.  Though I don't know how invested seb128 is in having a backup UI
[20:52] <barry> mterry: we have a session on python3 plans for xenial.  should we piggyback on that? http://summit.ubuntu.com/uos-1511/meeting/22568/python3-only-on-the-images/
[20:54] <mterry> barry, ah that session is exactly what I was hoping we had.  Just a shout out in there for help might be good.  I assume we still have that spreadsheet of work-needing-to-be-done that we could point people at
[20:54] <barry> mterry: we do but it's probably horribly out of date
[20:54] <mterry> barry, I'll make sure to attend, but don't need to speak
[20:55] <mterry> barry, fair
[20:55] <barry> mterry: awesome.  plugs are always helpful :)
[21:22] <mterry> barry, so where does /sbin/system-image-upgrader live / come from?  (it's the command used when upgrading the system image)
[21:22] <mterry> It doesn't seem to be on my device normally
[21:24] <barry> mterry: do you mean the magical blob that runs in recovery?
[21:24] <mterry> barry, yeah
[21:24] <barry> mterry: fwiw, i have never touched that, and only looked at the code once or twice
[21:25] <barry> mterry: the best i can point you at is: https://wiki.ubuntu.com/ImageBasedUpgrades/Upgrader
[21:25] <mterry> OK.  thanks
[21:25] <barry> but warning that that wiki page could e way out of date


[00:06] <JoseeAntonioR> ok, but still have the line breaks prob
[00:06] <pleia2> yeah, I don't know what that's about :\
[00:06] <pleia2> do you have a server or somewhere to test it?
[00:07] <pleia2> I tried it a few places and can't seem to replicate
[00:10] <JoseeAntonioR> sure, let me try
[00:12] <pleia2> even works ok on my debian server
[00:12] <pleia2> JoseeAntonioR: are you using the libtext-unidecode-perl package, or something from cpan?
[00:13] <JoseeAntonioR> I think cpan
[00:13] <JoseeAntonioR> but haven't got any problems before, when we published weeks ago
[00:13] <pleia2> well I'm wondering if an update came in via cpan in that time that might have been buggy
[00:23] <JoseeAntonioR> hmm, seems like I need to update the cpan thingy
[00:23] <JoseeAntonioR> it's fine in my VPS too
[00:23] <pleia2> weird :)
[08:05] <Myrtti> oh good grief at the the Ubuntu Style song :-C
[08:53] <not_found> It was kind of painful
[09:29] <Myrtti> painful? infuriating, insulting and sexist were what I was thinking
[15:11] <pleia2> thanks for the feedback :)


[08:35] <JamesTait> Good morning all, happy Video Games Day! :-D
[14:27] <TonaM> Some one in español ???
[14:30] <TonaM> Well english !! , why i can upload a folder , i want to upload an entire folder, instead a single file
[14:31] <TonaM> Auto upload is fine ,....
[14:32] <TonaM> But some times i want to upload an entire folder !! Thanks
[14:32] <davmor2> TonaM: are you using Ubuntu?
[14:32] <TonaM> Yes ubuntuone on android !! :)
[14:34] <davmor2> karni: can you upload a folder on Android?
[14:35] <karni> davmor2: No, you cannot.
[14:35] <karni> You'd need to upload files one by one, sadly.
[14:36] <davmor2> TonaM: ^ Sorry
[14:36] <TonaM> Yes , with auto upload , but i want to upload a folder like if i add a single file !!!!
[14:36] <karni> TonaM: If you're uploading pictures, you could try auto upload instead, and choose that single gallery.
[14:36] <karni> TonaM: "like if I add a single file"?
[14:36] <karni> TonaM: Are you trying to upload pictures?
[14:37] <TonaM> davmor , :) yeah ... I will upload single files ....any way , hope they add that option !!!
[14:38] <TonaM> Soon :) ....
[14:38] <karni> TonaM: Sadly, we won't add any new features for the time being.
[14:39] <TonaM> karni ok .... The service and app are awesome !!!!!
[14:39] <TonaM> karni one more question !!!!
[14:39] <karni> TonaM: Glad you like it :)
[14:39] <karni> Sure
[14:41] <TonaM> karni , i invite a friend , and i get 500 mib ?? Right ?????    How many friend can i invite ?????
[14:41] <karni> davmor2: Do you know how referrals work?
[14:41] <karni> Don't remember the details
[14:42] <TonaM> karni , :(   ....... well i read the referal detaila on web site ....    Thanks !!!!!!
[14:43] <karni> TonaM: wait a moment
[14:43] <davmor2> TonaM, karni: Spread the word and get rewarded by inviting all your friends and family to Ubuntu One. For each person you refer both of you will get 500 MB extra storage if they sign up via this link:  So you share the link if your friend sign up with your code then you get the additional space
[14:44] <karni> TonaM: https://one.ubuntu.com/help/faq/how-much-free-storage-can-i-get/
[14:44] <karni> TonaM: 40 people, total of 20GB
[14:44] <karni> TonaM: Share with your friends!
[14:45] <TonaM> davmor2 karni  , :) thank you two .... 40 people thats great !!!!
[14:45] <karni> :) spread the love
[14:45] <TonaM> Ok ok ..... I willl :)
[14:49] <TonaM> Hey ... anyone in here want to try ubuntuone files ????? Hahahahahahahaha :) :) good day people and thanks !!!


[10:53] <atdprhs> Hello everyone, have anyone deployed k8s on maas cloud?
[10:55] <atdprhs> If anyone did, have you experienced any issues with DNS and HTTPs websites certificate resolving?