[12:34] <_MMA_> nothlit: Ja. That's better.
[12:34] <_MMA_> Ill bbl.
[12:35] <lassegul> im going to add a sub pages to the /Hardy page
[12:35] <nothlit> lassegul: :o
[12:35] <nothlit> what
[12:36] <lassegul> theres no link to Alternate from Hardy
[12:36] <lassegul> im sorry there is.
[12:36] <lassegul> ok, theres no need then.
[12:42] <nothlit> lassegul: theres more artists apps to add to the tools page, and we have to finish the etiqueutte page, and we have to clean up get involved
[12:42] <nothlit> as well as all the unfinished stuff commented in the main page
[12:43] <lassegul> nothlit: thats right. You take the Get Involved and i do the Tools page?
[12:44] <lassegul> nothlit: which one do you want to do?
[12:44] <nothlit> i don't much care
[12:44] <nothlit> i'll do what needs to be done
[12:44] <nothlit> and anything else i'm interested in i'll work on anyways
[12:45] <lassegul> ok lets bring em up on gobby then.
[12:46] <nothlit> lassegul: delete the duplicates first =p
[12:46] <lassegul> nothlit: true :)
[12:48] <lassegul> we are set
[01:34] <lassegul_> hmmm. dc. nothlit i gotta sleep. talk to you in the morning
[01:35] <nothlit> lassegul: kk, lemme reconnect and save everything first
[01:36] <nothlit> lassegul: ok
[01:37] <nothlit> lassegul: cya later
[08:16] <troy_s> lassegul_: Sorry went to work...
[08:16] <troy_s> lassegul_: And I call you on the Fedora 8 work - it is complete drivel.  Looks about as 'wow' as Novell's abortion.
[09:01] <lassegul_> troy_s: :)
[09:01] <troy_s> lassegul_: :)
[09:01] <lassegul_> troy_s: isnt that the good kind of 'wow'?
[09:02] <troy_s> lassegul_: It is repetitive, done, and well... dried up like a prune.
[09:03] <troy_s> lassegul_: So no... not good.  lol.
[09:07] <lassegul_> troy_s: I think the colours are well used, with the desaturated blue and purple. Its calm and has and the textures on the drop/splash/swoosh are nice.
[09:08] <troy_s> lassegul_: Feck.  I can't even begin to comment on it.  Blue is done like dinner.  The curves are repetitive of 1995 mentality.    Utter uber tripe.  No balls.
[09:08] <lassegul_> lol
[09:10] <troy_s> lassegul: It is just a sad sad sad reminder as to how far Diana pushed F.
[09:10] <troy_s> lassegul: And I can only imagine that she was probably restrained.  Oh more... No motif.
[09:12] <lassegul> troy_s: I understand what you are saying.
[09:13] <troy_s> lassegul: It is really symptomatic of all the other crap distros are peddling.
[09:13] <troy_s> lassegul: Completely mediocre, completely restrained, completely vague in directionality, and completely lacking in a clearly defined and focused audience / goal.
[09:14] <troy_s> lassegul: The fear of mistake perhaps?  Hard to cite the reasoning.
[09:20] <troy_s> lassegul: The funny thing is that all of this 'we should do it this way' that the distros are showing clearly is helping them get to a colossally underwhelming 2% market share.
[09:35] <lassegul> troy_s: I agree that being conservative when we are in this situation is silly.
[09:35] <lassegul> but artwork alone is hardly the only reason for only %.
[09:35] <lassegul> *2%
[09:41] <troy_s> lassegul: It plays a significant role.  The design of anything used by humans always plays a significant role.
[09:41] <troy_s> lassegul: If you need further proof, look to the many vast areas that have seen significant change in adoption based purely on design -- records for example -- started without album art and the like.  The adoption of that simple trend helped to establish the entire music industry.
[09:42] <troy_s> lassegul: Arguably the art and design of music videos launched another chapter.
[09:42] <troy_s> lassegul: Automobiles, furniture, etc.
[09:42] <troy_s> lassegul: Arguably _everything_ goes through the phase where people 'don't give a care' to the aesthetic presence / design elements.
[09:43] <troy_s> lassegul: And, eventually, after much success through execution, the 'mainstream' adopts the application.
[09:43] <troy_s> lassegul: We must remember that the computing industry is still in a relative 'dark age' -- people only 'see' the Model T Ford -- there are many varieties to come.
[09:46] <troy_s> okie... night all.  take care.
[09:56] <lassegul> good nigt
[02:45] <lassegul> nothlit: check out GetInvolved.
[02:45] <lassegul> nothlit: could you add the announcement on the top about Hardy?
[02:55] <LDS_Trooper> Greetings!
[02:55] <LDS_Trooper> Any luck in getting an advanced look at the new wallpaper?
[03:01] <lassegul> LDS_Trooper: the one in gutsy?
[05:11] <kwwii> lassegul, nothlit: ping?
[05:12] <nothlit> pong
[05:13] <nothlit> kwwii: i hope you don't mind i put this as a third bullet point? Simple wallpapers and themes ubuntu-specific can be submitted to  Ubuntu-Art.org, a sister site of the -look.org and -file.org websites.
[05:14] <kwwii> nothlit: I think we should wait another day or so until we know the outcome of the discussion on the mailing list
[05:14] <nothlit> sure, its commented
[05:15] <_MMA_> I think splitting submissions over 2 spots like that is unwise. Twice the work to me.
[05:15] <nothlit> _MMA_: splitting? its for general simple things
[05:15] <kwwii> _MMA_: right, I think that we should explain the different purposes of the wiki and such a site
[05:15] <nothlit> _MMA_: not for the hardy cycle, just a general collection of ubuntu wallpapers etc
[05:16] <nothlit> unless you think the wiki can handle hundreds or thousands of like submissions
[05:16] <kwwii> the site is for general artistic rambling, the wiki is for definite explicit work on a whole theme
[05:16] <_MMA_> Ahh.... I see now. I read it as Ubuntu-Art.org would also be a plsce to post your submissions.
[05:16] <_MMA_> *place
[05:17] <kwwii> nothlit: once lassegul is around we need to discuss the wiki stuff...I talked to Jono today about our team using the wiki structure they created for every team...most of the information we have already, we just need to tweak things to fit
[05:18] <kwwii> check out for more info on what I mean https://wiki.ubuntu.com/BuildingCommunity/SampleTeam
[05:49] <kwwii> boah, i have spent a day on just conf calls and meetings :-(
[05:50] <kwwii> _MMA_: can you create a package for you murrine theme without the panel background?
[05:52] <_MMA_> Just pull the "panel" folder from the GTK folder and comment out the 2 lines at the top of the gtkrc file.
[05:53] <_MMA_> I can do it in a bit if you dont feel like it.
[05:53] <kwwii> _MMA_: yeah, I can do that, thanks :-)
[05:53] <lassegul> kwwii: im back
[05:53] <lassegul> hello everybody
[05:53] <kwwii> lassegul: howdy
[05:54] <kwwii> lassegul: might want to read the log a bit
[05:54] <lassegul> ive read it
[05:54] <kwwii> so what do you guys think?
[05:54] <lassegul> that sample is really nice
[05:54] <kwwii> we have a lot of that info already
[05:54] <lassegul> and theres not much work we need to do to make it fit either
[05:56] <nothlit> theres not much difference to what we have now, except theres basically a global navigation bar
[05:57] <nothlit> it might be interesting to add, but is it needed @ the top of every submission?
[05:58] <nothlit> my preference is of course the traditional child-parent page relationship but i can see how that may be useful at the "base" pages
[05:58] <kwwii> no, not at the top of the individual projects...that is why I thought we should discuss how and where to use this
[05:59] <lassegul> I think we could just link to /Artwork from the submissions, and keep them like they are
[05:59] <lassegul> something like "home"
[05:59] <nothlit> are you talking about moving the function of the main page into the getinvolved page like they have now?
[05:59] <nothlit> and leaving the page for news and events?
[05:59] <nothlit> i think thats more a loco team style thing
[05:59] <lassegul> nothlit: who are you talking to?
[06:00] <nothlit> lassegul: feel free to respond =p
[06:01] <nothlit> but the navigation system in the main. documentation, incoming, and hardy/gutsy pages might be good\
[06:01] <nothlit> just to allow jumping around even if the page gets a little longer
[06:02] <kwwii> it seems to me that we could use that top bar but that we will still need a bit more than just that
[06:02] <kwwii> teh faq sounds like a wonderfull idea, really
[06:02] <lassegul> nothlit: arent main page and getinvolved organized just like we do?
[06:02] <kwwii> someone asks "who is in charge of this mess" and I say "check this url"
[06:03] <lassegul> the roadmap is also good.
[06:03] <nothlit> lassegul: well, not entirely
[06:03] <kwwii> yes, the home page and the getinvolved seem to fine in the state we have them, basically
[06:03] <nothlit> lassegul: yeah, we can just point that at the general hardy roadmap though, unless we start developing a more detailed one
[06:04] <nothlit> lassegul: our main page is more like a portal, for projects etc, their getinvolved is similar--but the template main page is more of an event based thing
[06:04] <nothlit> lassegul: for teams that hand out cds this week, have a meeting that week, put up posters the next etc
[06:04] <kwwii> I'll create a more precise roadmap...we can explain that major changes are only for every new LTS cycle and then go into specifics for this cycle
[06:06] <nothlit> does the https://wiki.ubuntu.com/Artwork/Processes page do anything the artwork builder page itself doesn't do?
[06:07] <lassegul> lol
[06:07] <nothlit> so basically, we want a faq and roadmap?
[06:07] <nothlit> do we also want a meeting 'ticker' at the top?
[06:08] <kwwii> nothlit: yeah, that seems like the basis of what we need
[06:08] <kwwii> I just thought that there might be issues with certain pages where we still need a table of contents as well as the top bar thingy
[06:09] <lassegul> But where will we put the subpages section then? Under the navigation bar?
[06:10] <lassegul> or should we put it back down to the bottom?
[06:11] <nothlit> kwwii: i'm wondering about the Archives Section and the Processes page, can we move everything in the archives section to the incoming attic? and is the processes page deletable?
[06:12] <nothlit> lassegul: well, if we want to make it fit closer to the template we'd have to leave it at the top
[06:12] <kwwii> nothlit: well, I don't care where the archives end up but I would like them to be viewable somewhere
[06:12] <kwwii> and the proceses page is perhaps poorly named but the info there is somewhat important I guess
[06:12] <nothlit> lassegul: otherwise, my inclination would be to move it to the bottom once we were absolutely sure everything was covered in the text itself
[06:13] <lassegul> nothlit: re:archives  at least they should be collected in one place.
[06:14] <lassegul> nothlit: i disagree with you there, becuase people want to point and click, not to read through the whole page.
[06:14] <kwwii> I think that experience has shown that people do not see the links at the bottom
[06:16] <nothlit> kwwii: i don't see anything in the processes page that isn't duplicated in the builder instructions itself, other than the spec for the builder and that hopefully it will create browsable html pages
[06:16] <lassegul> But it might take up too much screen space when the page has lots and lots of subpages, like Hardy/Alternate, if we have both navigation bar and sub pages on the top, it will probably be 500 pixels tall.
[06:17] <nothlit> lassegul: thats why i prefer the children and "Show Parent" method of navigation generally
[06:17] <lassegul> maybe we should skip the navigation bar on certain pages. Just have a "home" link.
[06:18] <nothlit> and then keeping the relevant information on the pages itself
[06:20] <nothlit> like the hardy page has the technical resources link, and the submission guidelines and meeting link
[06:20] <Samuli^> is there a .deb for murrine engine configurator, by the way?
[06:21] <lassegul> nothlit: now you are talking about skipping the sub pages table?
[06:21] <nothlit> lassegul: i'm talking about not relying on a global navigation as a crutch and making sure we put links where they're needed instead
[06:22] <nothlit> lassegul: the hardy page itself doesn't have a subpages anyways because there is only alternate and (will be) official to navigate to
[06:26] <lassegul> nothlit: i think relevant links collected in one place is better
[06:28] <nothlit> sorry, d/c
[06:28] <nothlit> what was the last thing i said?
[06:29] <nothlit> this is what i got last < lassegul> nothlit: now you are talking about skipping the sub pages table?
[06:29] <lassegul> nothlit: i think relevant links collected in one place is better
[06:31] <nothlit> lassegul: in the navigation bar?
[06:32] <lassegul> nothlit: as a principle
[06:32] <lassegul> nothlit: im not really sure how we implement it in pages that can get messy because of it
[06:33] <nothlit> lassegul: sure, but do you want the one place to be in the main page or at the top of every single one
[06:33] <lassegul> nothlit: every page that isnt necessarily the users destination.
[06:34] <nothlit> lassegul: that would be every page or none
[06:35] <lassegul> hold on some wierd sounds are coming from the other room :S
[06:37] <nothlit`alpha> lol ok
[06:37] <lassegul> nothlit: (a pidgeon got in to my kitchen) yeah you are ok.
[06:38] <lassegul> *you are right
[06:38] <lassegul> kwwii: what do you think?
[06:39] <kwwii> although I like the idea of having all links in one place I am not sure if it would work
[06:40] <kwwii> I wish Jono were here to express his opinion
[06:40] <lassegul> he is away?
[06:42] <kwwii> not sure, checking
[06:42] <nothlit> well, we can try the menubar at the top approach, and if it doesn't work, just make a link back to the main page
[06:42] <lassegul> agreed
[06:42] <kwwii> he is coming
[06:42] <jono> heya
[06:42] <kwwii> the man, the myth, the legend
[06:43] <lassegul> hi
[06:43] <jono> hehe
[06:43] <jono> WHAT DO YOU WANT?!!!
[06:43] <kwwii> lassegul, nothlit: can you explain that again for mister cool?
[06:43] <jono> :)
[06:43] <lassegul> nice template btw.
[06:43] <lassegul> nothlit: will you do the honors?
[06:43] <nothlit> we're wondering whether to adopt your navigation bar include for the artwork wiki section
[06:44] <jono> right
[06:44] <nothlit> we're worried about the clutter, and whether its relevant for every page, such as the individual theme ones
[06:44] <jono> I would recommend
[06:44] <jono>  the purpose for every page is so people can easily navigate around
[06:44] <lassegul> we agreed on having subpages on the top earlier for the same purpose
[06:44] <jono> right
[06:44] <jono> there is no reason why you can't additional items to the menu bar I suggest
[06:45] <jono> but I think you need to have each the things in my menu bar
[06:45] <jono> such as a knowledge base
[06:45] <jono> and a faq
[06:45] <kwwii> I guess the thing is that we have extra pages in addition to what is already included in that bar
[06:45] <jono> and a link back to the main page
[06:45] <jono> sure, so add some additional pages
[06:45] <jono> I would recommend you add a Projects item to the menu bar
[06:45] <jono> and link a lot of things under that
[06:45] <lassegul> so /Incoming goes under projects?
[06:45] <kwwii> right, that would be our current incoming page and subpages from that
[06:45] <kwwii> lassegul: exactly
[06:46] <jono> so as an example:
[06:46] <nothlit> jono: do you think its relevant for this set of pages? https://wiki.ubuntu.com/Artwork/Incoming/Hardy/Alternate/Animals
[06:46] <jono> Processes can go under Knowledge Base
[06:46] <jono> and Specs can go under projects
[06:46] <jono> nothlit: I would link that from Projects
[06:47] <jono> I woudl say pages for ongoing projects would be linked under a Projects option
[06:47] <nothlit> jono: as in, placing the menu bar in that collection of concept pages in the first place
[06:47] <nothlit> jono: its already has the siblings and slideshow navigation to begin with
[06:47] <jono> nothlit: sure, I would suggest the menu bar is on all art pages
[06:47] <nothlit> adding another navigational item, may be a bit much?
[06:47] <lassegul> with the forward back etc. navigation we have there from before it will take up much space.
[06:48] <jono> sorry, I am getting confused
[06:48] <nothlit> perhaps just leave the menu bar to the parent page?
[06:48] <jono> I would recommend having my menu bar as it outlines all core sections
[06:48] <jono> but then you have sub-sections, such as the animals page
[06:48] <jono> but all pages should have the main menu bar, so the navigation feels consistant
[06:49] <jono> and it also makes the pages easier to navigate for new users
[06:49] <kwwii> at some point we could include a secondary navigation under the top bar if necessary I guess
[06:50] <jono> kwwii: exactly
[06:50] <jono> I agree you might want a nav bar for sub-sections
[06:50] <jono> but you want one main menu bar with Home Roadmap Projects Knowledge Base FAQ Contact and the meeting time on it
[06:51] <kwwii> right, that clears things up then, I think
[06:51] <jono> it also helps keep the art team pages consistant with other teams in the ubuntu community
[06:51] <kwwii> lassegul, nothlit: agreed?
[06:51] <jono> right, I best run
[06:51] <jono> later folks, have fun :)
[06:51] <kwwii> thanks man
[06:51] <jono> np :)
[06:51] <lassegul> yep. so long
[06:52] <nothlit> kwwii: i dunno, imo not much point in talking about it, it sounds like something worthwhile to try, doesn't take much work so that would be the best approach
[06:54] <lassegul> I just tested it on Animals, and it looked good.
[06:55] <nothlit> so header should for now have, main page, hardy, get involved, documentation, and meetings?
[06:55] <lassegul> nothlit: we do that first then redo it into Projects etc.?
[06:56] <kwwii> no, the header should at least have everything in the example
[06:56] <nothlit> kwwii: we don't have faq and roadmap atm created
[06:57] <kwwii> the other pages are either in one of those links or it should be in a subnavigation bar
[06:57] <kwwii> nothlit: yes, but I'll create them soon
[06:57] <nothlit> we can place it in when its created and the include will handle it automatically then
[06:57] <kwwii> ok, fair enough
[06:58] <kwwii> I think that instead of just having hardy we should have a Projects page (which is basically Incoming)
[06:58] <kwwii> and Hardy will be one of those projects
[06:59] <nothlit> we don't want a quick link to hardy itself?
[06:59] <nothlit> i find that more important than the main page actually
[06:59] <lassegul> so do I.
[07:00] <kwwii> ok, fair enough
[07:00] <troy_s> seems that you must distill the levels of the tiers
[07:00] <kwwii> troy_s: not sure I understand you
[07:02] <nothlit> !schedule
[07:02] <ubotu> Ubuntu releases a new version every 6 months. Each version is supported for 18 months to 5 years. More info at http://www.ubuntu.com/ubuntu/releases & http://wiki.ubuntu.com/TimeBasedReleases
[07:02] <nothlit> !hardy
[07:02] <ubotu> Hardy Heron is the code name for Ubuntu 8.04-LTS, due April 2008. For more info, see: https://wiki.ubuntu.com/HardyHeron
[07:02] <nothlit> bah
[07:03] <troy_s> kwwii: It appears that where one might 'expect' to find the Hardy elements isn't laid out as one would expect.  (being the more naive form of 'expect'
[07:04] <troy_s> kwwii: And my comment was directed at the 'we should be able to jump to hardy easily)
[07:05] <kwwii> troy_s: so you think that having a direct link in the top bar would be helpful, right?
[07:05] <troy_s> Hrm... I also just noticed that some of the pages don't have ToCs nor a way to navigate quickly to the subpages -- nothlit did you re-save the artwork page template?
[07:06] <troy_s> it would seem logical to use it for all pages.
[07:06] <nothlit> troy_s: i've never edited the artwork page template, the platypus template has it though
[07:06] <nothlit> https://wiki.ubuntu.com/Artwork/PageTemplate/Header
[07:06] <troy_s> kwwii: I know I probably _wouldn't_ put an exception link in the top bar, but maybe make it such that whatever sub-sections one has makes it logical to get to the hardy stuff -- in this case I suppose the most relevant would be 'guidelines'.
[07:06] <nothlit> anyone want any changes?
[07:07] <troy_s> nothlit: You simply put 'template' in a page title and it is shelved there.
[07:07] <troy_s> nothlit: You can also use some macros to make it automagically fill in bits.
[07:08] <kwwii> troy_s: right, now I get it...I think that having a projects page in the main bar and then having that main page point to the hardy project, alternate projects, and a "create new" project might be the best idea
[07:08] <kwwii> naturally, there will also be guidelines for hardy and those should also be interlinked
[07:08] <nothlit> I don't know if the other projects are important
[07:08] <troy_s> kwwii: Yes.  My instincts tell me that 'breaking' any form of developing logic in layouts probably won't help the cause.
[07:08] <nothlit> other than for the contributors themselves
[07:08] <kwwii> right
[07:08] <nothlit> not many people will be interested in modifying oransun or blubuntu, etc
[07:09] <troy_s> also, i always tend to err on the shallow side of the magic number value -- meaning the five or less -- for total elements of information presented.
[07:09] <nothlit> my inclination would just to leave it as it is as a link in the Projects section on the main page
[07:09] <troy_s> one must remember that a short burst of items -- 9 is the MASSIVELY big side of the magic number.
[07:09] <troy_s> 7 is average.
[07:09] <troy_s> and 5 is the lower 'common' end, especially when someone isn't trying to remember elements.
[07:10] <troy_s> http://www.musanim.com/miller1956/
[07:10] <troy_s> for more quick information on that
[07:10] <kwwii> nothlit: right, on the project main page there would be a link to the alternate projects (kinda a main page for those projects
[07:10] <kwwii> )
[07:10] <kwwii> I have to head out for now...see you guys in a few hours
[07:11] <troy_s> (and that is a technical way of basically saying that on average, people process 7 elements of information at peak -- 9 for exception -- and 5 at the low end of the exception.  Miller was one helluva bright guy and his research has direct implications in design.)
[07:11] <troy_s> kwwii: Ciao kww.
[07:11] <kwwii> ciao troy_s
[07:16] <lassegul> nothlit: it looks good.
[07:16] <troy_s> greetings calavera, what brings you around?
[07:18] <nothlit> this is what it looks like with the main page, https://wiki.ubuntu.com/Artwork , and this is what it looks like on a concept page, https://wiki.ubuntu.com/Artwork/Incoming/Hardy/Alternate/Savanna
[07:19] <lassegul> hm. you sure we shouldnt skip the index of the other sub pages of /Alternate in the submission pages, and just keep Next and previous.
[07:22] <nothlit> i would prefer keeping the stuff there and getting rid of the main bar to keep it in the root Alternate and Hardy
[07:22] <nothlit> people in that area, will just want to browse all the concepts
[07:22] <lassegul> true
[07:23] <lassegul> thats what i meant by "pages that might not be their destination".
[07:23] <nothlit> ahh lol
[07:23] <nothlit> when kwwii gets back he can decide =p
[07:23] <lassegul> ja
[08:38] <nothlit`alpha> anyone have an opinion to montage size? https://people.fluxbuntu.org/~nothlit/communitytheme/scripts/test/
[08:40] <coz_> nothlit`alpha, you mean as to its size  ?
[08:40] <coz_> in what manner
[08:43] <joejaxx> nothlit`alpha: small looks like an adequate size for a gallery
[08:43] <nothlit`alpha> as in thumbnails for the wiki stuff
[08:43] <joejaxx> yes
[08:44] <joejaxx> it does
[08:44] <nothlit`alpha> they all fit within 1024x768 afai can tell
[08:44] <joejaxx> yeah
[08:44] <joejaxx> i think small.png is adequate
[08:48] <nothlit`alpha> this is the 320x240 sizing atm /home/justin/montage/large.png
[08:48] <nothlit`alpha> arg
[08:48] <nothlit`alpha> running more than one x
[08:48] <nothlit`alpha> https://wiki.ubuntu.com/Artwork/Incoming/SubmissionTemplate
[09:23] <agoliveira> kwwii: Yes?
[09:24] <kwwii> howdy
[09:24] <agoliveira> kwwii: What's up?
[09:24] <kwwii> agoliveira: nothing I just forgot to type / before join, sorry
[09:25] <agoliveira> kwwii: lol I'm becoming paranoid :)
[09:25] <kwwii> my server died while I was away
[09:25] <kwwii> :p
[09:25] <kwwii> no worries
[09:29] <_MMA_> "died" in what sense?
[09:29] <_MMA_> HW failure?
[09:30] <_MMA_> Smoke and ozone smell? :)
[09:33] <kwwii> one of the fans went out
[09:33] <kwwii> so it overheated
[09:33] <kwwii> I turned the others up (nice webserver/java app on the firmware)
[09:39] <kwwii> nice to find out at 9:39pm that there is a deadline tomorrow
[09:40] <_MMA_> Ouch.
[09:49] <kwwii> well, this server is a few thousand miles away
[09:50] <kwwii> so it is really nice to have a way to interface the hardware without touching it
[09:50] <_MMA_> Oh.......
[09:51] <_MMA_> Neat. :)
[09:51] <kwwii> yeah, and it was for free!
[09:51] <kwwii> :p
[09:52] <_MMA_> Nice. I have about $1000 tied up in my home one with the addition of the TB drive.
[09:53] <kwwii> I just did some work for a large computer manufacturer (3 letter acronym starting with A and ending with D) and they gave me a server to boot
[09:54] <_MMA_> Killer.
[09:54] <_MMA_> Whats it run?
[09:54] <_MMA_> (OS)
[09:57] <kwwii> bsd naturally :p
[09:57] <_MMA_> Nice.
[09:58] <_MMA_> Was gonna do BDS or Debian on my home one. Just said F-it and put Gutsy on it.
[09:58] <_MMA_> CLI install. SSH into it.


[14:27] <wrst> welcome back xTEMPLARx.... not that you are paying attention :)
[21:47] <Omnifrog> well, I'm out of the hospital
[21:47] <Omnifrog> warning: gross pic of my swollen belly http://i.imgur.com/CGyocas.jpg
[21:47] <Unit193> You were in one?
[21:47] <Omnifrog> yeas
[21:48] <Unit193> Doesn't look right... What happened?
[21:49] <Omnifrog> I caught a case of emergency acute appendicitis
[21:49] <Omnifrog> :\
[21:49] <Unit193> Well, good you're out.
[21:50] <Omnifrog> yeah, it was a potentially dangerous situation
[22:15] <average_guy> Glad to hear you're ok Omnifrog.  I have heard that the pain from appendicitis is ridiculous.
[22:18] <Omnifrog> it was !
[23:03] <wrst> Omnifrog: man!!
[23:03] <wrst> glad you are back and healthy
[23:03] <wrst> wow
[23:05] <Omnifrog> that's the first time I ever had anything major, like surgery so it was not just painful but scary!
[23:08] <Omnifrog> before wife took me to ER I made sure there was enough money in checking to giver her time to figure things out.  put the notebook of passwords in plain sight, etc
[23:19] <wrst> oh wow :\
[23:19] <wrst> very thoughtful however
[23:39] <wrst> oh and glad it wasn't needed!!
[23:40] <Omnifrog> yeah. I was a little freaked out on Saturday
[23:40] <Unit193> Of course.
[23:41] <wrst> who wouldn't have been?
[23:41] <wrst> very understandable
[23:41] <wrst> very glad all is ok


[02:53] <arraybolt3> Hey, guys, the Kinetic Ubuntu Server amd64 images aren't building - I get a 404 Not Found when I try to download the amd64 image. I think I should file this as a bug, but I have no clue what package to file it against so I can submit a failed report on the QA tracker. Should I file a bug, or should I just leave my "in progress" report?
[05:05] <mwhudson> dbungert: then i'm not aware of such a tool and it sounds like it would be useful
[13:51] <hallyn> hm, network-manager in jammy seems to be flubbing re-connections to my 5g hotspot.  haven't noticed it on other networks.  I *had* thought it was the kernel, but doing systemctl stop Networkmanager; systemctl start NetworkManager seems to reliably fix it.  Without that, 'nmcli con down X; nmcli con up X'
[13:51] <hallyn> just hangs
[22:48] <mwhudson> bah the image looked ok in the preview! https://discourse.ubuntu.com/t/spec-publishing-netboot-artifacts/28256


[12:19] <gary_poster> whee! 1 weekend = 742 emails...
[12:28] <gary_poster> aloha and welcome to Monday
[12:29] <gary_poster> bac benji danilos gmb, call in 2 (yes, gimme an extra minute)
[12:29] <gmb> ok
[12:29] <danilos> aloha :)
[12:31] <bac> ok
[12:44]  * gmb -> late lunch
[12:51] <gary_poster> kids -> school
[14:00] <gary_poster> gmb, I'm just starting reading your LEP.  I think sometimes there are two useful sorts of feedback (along one axis): feedback when someone is reading something for the very first time, and feedback after they have thought about it.  The first can give you ideas on how to make the information more accessible, and the second actually gives thoughtful feedback on the ideas contained.  So, I'm immediately ready to give
[14:00] <gary_poster> Would you like me to enter it here as I go, or in an email, or at the bottom of the LEP, or some other way?
[14:01] <gmb> gary_poster: Email or at the bottom of the LEP is fine; I'm trying to get my head around the upload stuff at the moment and could do without the interruptions for a wee while.
[14:01] <gary_poster> cool, gmb will do
[15:12] <gary_poster> gmb, thank you for the LEP.  my comments/thoughts got long :-P .  I put them on a separate page. No rush for a reply for me--getting back to other things now. :-) https://dev.launchpad.net/LEP/BugRelationships/GaryComments
[15:13] <gmb> gary_poster: Okay, thanks.
[15:13] <gary_poster> welcome
[17:44]  * gary_poster has now done pretty much everything he can do before working on the bug he has no motivation for :-P
[17:44] <gary_poster> procrastination time is over...
[17:48] <bac> hi gary_poster, want a diversion?
[17:49] <gary_poster> ooh, bac!  yes!
[17:49] <bac> skype?
[17:49] <gary_poster> :-) sure, call when ready
[17:50] <bac> gary_poster: skype crashed
[17:50] <bac> trying again
[17:50] <gary_poster> ok
[17:51] <bac> https://pastebin.canonical.com/53395/
[18:33] <bac> benji, gary_poster: either of you updated your tree lately?  the addition of txlongpoll is breaking mine
[18:34] <gary_poster> bac, I did last week, and I think txlongpoll was in it then.  Can try again now...
[18:34] <benji> bac: I haven't.  And now I'm scared to. ;)
[18:34] <bac> yeah, be scared.  :)
[18:34] <gary_poster> bac, what's your symptom?
[18:34] <bac> i only did to get gary's new storm recorder
[18:35] <bac> gary_poster: make build failes on installing txlongpoll
[18:35] <bac> from bin/buildout
[18:35] <bac> Installing txlongpoll.
[18:36] <bac> While:
[18:36] <bac>   Installing txlongpoll.
[18:36] <bac>   Getting distribution for 'oops-twisted'.
[18:36] <bac> Error: Picked: oops-twisted = 0.0.1
[18:36] <gary_poster> bac, hm.  updating now
[18:36]  * bac flashback to friday, writ large
[18:38] <gary_poster> bac, duplicated.  investigating
[18:38] <bac> oops_twisted-0.0.1.tar.gz is in download-cache/dist
[18:38] <gary_poster> bac, the good news is that it should be easy to fix.  versions.cfg is missing.  The bad news is that this should never have happened
[18:39] <gary_poster> our landing machinery should have caught ths
[18:39]  * gary_poster will try to fix
[18:40] <bac> i recall txlongpoll had a versions.cfg last week.  it was testresources that was ugly
[18:40] <gary_poster> bac, yeah, simple fix
[18:40] <gary_poster> it is still building...
[18:40] <gary_poster> other stuff
[18:40] <gary_poster> will get you diff
[18:40] <bac> thanks
[18:41]  * bac brb
[18:44] <gary_poster> trying to land testfix.  Bah
[18:44] <gary_poster> conflicts in work I was in middle of
[18:58] <gary_poster> bac, fwiw, I'm landing testfix via lp-land...
[18:58] <gary_poster> ...succeeded
[18:58] <bac> gary_poster: cool.  to the txlongpoll package or lp?
[18:58] <gary_poster> bac, so just bzr pull and should work
[18:59] <gary_poster> bzr lp
[18:59] <gary_poster> I mean, bac, lp
[18:59] <bac> thanks!
[18:59] <gary_poster> welcome
[20:09] <bac> gary_poster: your statement recorder suggestion is great.  i've discovered this offensive action:
[20:09] <bac> 'UPDATE BugTask SET status=10 WHERE BugTask.id = 38'
[20:09] <gary_poster> bac, cool!  What is triggering that?
[20:09] <bac> sadly, the traceback only points to the line of the flush() so i'm still searching
[20:09] <gary_poster> oh, suck
[20:09] <bac> yeah
[20:09] <gary_poster> hm
[20:09]  * bac wishes for a 'watch' command in pdb
[20:10] <gary_poster> bac, what flush is this?
[20:10] <bac> the one at the bottom of bugtaskset:createTask
[20:42] <benji> bac: I haven't used it, but http://pypi.python.org/pypi/pdbpp has a watch command ("display" is their spelling)
[20:42] <bac> benji: great, i'll have a look
[20:47] <bac> @break_on_setattr('bar')  <-- Nice!
[20:50] <gary_poster> bye
[21:01] <benji> that is nice


[20:43] <bipul> Hi
[20:43] <bipul> Hello, I was trying to install pbuilder , and i am stuck at "I: Retrieving Packages "


[00:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #219: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_marble/219/
[00:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #176: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/176/
[00:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #181: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/181/
[00:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #178: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/178/
[00:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #183: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_marble/183/
[00:29] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #601: FAILURE in 40 sec: http://kci.pangea.pub/job/merger_kdiamond/601/
[00:35] -kubuntu-ci:#kubuntu-devel- Project merger_kio build #799: STILL FAILING in 58 sec: http://kci.pangea.pub/job/merger_kio/799/
[00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #91: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/91/
[00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #100: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/100/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #251: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/xenial_unstable_kstars/251/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #184: STILL FAILING in 41 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/184/
[00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #190: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/190/
[00:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #261: STILL FAILING in 47 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/261/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #245: STILL UNSTABLE in 48 min: http://kci.pangea.pub/job/xenial_unstable_kwin/245/
[00:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #118: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/118/
[00:52] -kubuntu-ci:#kubuntu-devel- Project merger_marble build #469: STILL FAILING in 40 sec: http://kci.pangea.pub/job/merger_marble/469/
[00:56] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #685: STILL UNSTABLE in 56 min: http://kci.pangea.pub/job/mgmt_merger/685/
[00:57] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #665: STILL UNSTABLE in 57 min: http://kci.pangea.pub/job/mgmt_progenitor/665/
[01:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #58: STILL FAILING in 6 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_discover/58/
[01:04] <santa_> clivejo: if you are up for uploading there is a fixed marble here: http://gpul.grupos.udc.es/sponsor/
[01:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #188: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/188/
[01:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #132: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/132/
[01:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #184: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_marble/184/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #54: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_libkleo/54/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #33: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/33/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #61: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/61/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #39: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/39/
[01:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #12: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/12/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #29: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/29/
[01:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #54: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_discover/54/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #46: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/46/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #40: STILL FAILING in 25 min: http://kci.pangea.pub/job/xenial_unstable_libkleo/40/
[01:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #87: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/87/
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #220: STILL FAILING in 29 min: http://kci.pangea.pub/job/xenial_unstable_marble/220/
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #185: STILL FAILING in 29 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/185/
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #75: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/75/
[01:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #191: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/191/
[01:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #78: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/78/
[01:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #55: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/55/
[01:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #89: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_okular/89/
[01:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #78: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_kopete/78/
[01:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #145: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/145/
[01:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #147: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/147/
[01:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #186: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/186/
[01:59] <tsimonq2> early bed for me o/
[02:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #192: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/192/
[02:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kidletime build #270: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kidletime/270/
[03:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpty build #273: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kpty/273/
[03:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #269: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/269/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #252: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_kstars/252/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #87: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/87/
[04:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #203: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/203/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #193: STILL FAILING in 1 min 15 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/193/
[04:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #133: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/133/
[04:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #194: STILL FAILING in 1 min 14 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/194/
[05:03] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #105: FAILURE in 14 sec: http://kci.pangea.pub/job/merger_audiocd-kio/105/
[05:03] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #106: STILL FAILING in 15 sec: http://kci.pangea.pub/job/merger_audiocd-kio/106/
[05:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #177: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/177/
[05:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #41: STILL FAILING in 27 min: http://kci.pangea.pub/job/xenial_unstable_libkleo/41/
[05:28] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #107: STILL FAILING in 17 sec: http://kci.pangea.pub/job/merger_audiocd-kio/107/
[05:29] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #108: STILL FAILING in 14 sec: http://kci.pangea.pub/job/merger_audiocd-kio/108/
[05:29] <Mirv> clivejo: sitter: there's a Qt PPU too one can apply for http://people.canonical.com/~ubuntu-archive/packagesets/yakkety/qt5
[05:33] <Mirv> oh that was just part of developer application talks. congrats clivejo! :)
[05:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #189: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/189/
[05:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #129: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/129/
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #47: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/47/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #62: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/62/
[05:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #130: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/130/
[06:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libgravatar build #22: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_libgravatar/22/
[06:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #25: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/25/
[06:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #246: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_kwin/246/
[06:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #145: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/145/
[06:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libgravatar build #23: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_libgravatar/23/
[06:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #26: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/26/
[06:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #251: STILL FAILING in 29 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/251/
[06:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #105: STILL FAILING in 27 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/105/
[06:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #109: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/109/
[07:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #146: STILL FAILING in 34 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/146/
[07:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #252: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/252/
[07:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #106: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/106/
[07:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #110: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/110/
[07:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #64: STILL FAILING in 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/64/
[07:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #81: STILL FAILING in 1 min 15 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/81/
[07:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #65: STILL FAILING in 40 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/65/
[07:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #82: STILL FAILING in 44 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/82/
[09:14] <ahoneybun> tsimonq2: did you install Kirigami into your 5.8 test ppa?
[09:15] <ahoneybun> seems it is a dep for 5.8 since Discover uses it as it's UI
[10:11] <soee_> clivejo: o/
[11:01] <tibi> hi! I'd like to test the Plasma 5.7 on my Kubuntu machine (I get a crash from my plasma shell at least once every 5 minutes)
[11:01] <tibi> Is there a PPA or repository with debs that I can use>
[11:01] <tibi> ?
[11:02] <clivejo> what version of Kubuntu are you running?
[11:02] <tibi> (unfortunately) 16.06
[11:02] <tibi> 14.04 was rock solid :)
[11:02] <clivejo> you sure?
[11:02] <clivejo> no such thing as 16.06
[11:03] <clivejo> 16.04 maybe?
[11:03] <clivejo> Xenial?
[11:03] <tibi> yeah, sorry
[11:03] <tibi> Description:    Ubuntu 16.04.1 LTS
[11:03] <clivejo> ok
[11:03] <tibi> plasmashell -v
[11:03] <tibi> plasmashell 5.6.5
[11:03] <clivejo> oh
[11:03] <clivejo> where did you get that#
[11:03] <tibi> (from backports)
[11:03] <clivejo> which backports PPA did you add?
[11:03] <tibi> the stock plasma was just as bad
[11:03] <tibi> let me check
[11:04] <tibi> http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu
[11:05] <clivejo> are you getting any crash info?
[11:05] <tibi> clivejo: I can look inside .xsession-errors. I didn't see anything relevant there last time I checked
[11:06] <clivejo> usually when it crashes you get a report pop up asking you what you want to do
[11:06] <tsimonq2> clivejo: we really do need to update the staging PPA with 5.7.5 :/
[11:06] <tsimonq2> s/staging/backports/
[11:06] <tibi> (at least not to my eyes)
[11:06] <clivejo> tibi: is it a production machine?
[11:06] <tibi> clivejo: oh, that. Yeah, I even submited several times the report
[11:07] <tibi> clivejo: yes, it's my main machine. I use it for web development
[11:07] <clivejo> any chance of copying that report and putting it on paste.ubuntu.com ?
[11:07] <tibi> is there a way to get it once it dissapeared from th systray?
[11:08] <clivejo> was the backports PPA the only one you added?
[11:08] <clivejo> could you have added another whilst trying?
[11:08] <tibi> no, no other
[11:08] <tibi> well, plasma just crashed, but no report coming
[11:08]  * clivejo knows that some online articles are telling people to add other PPA's
[11:09] <acheronuk> 5.6.5 from backports was pretty stable during the period I was using it
[11:09] <acheronuk> clivejo: ummm.... which ones?
[11:09] <clivejo> staging *face palms*
[11:09] <acheronuk> holy ***!
[11:09] <clivejo> yeah!
[11:10] <tibi> the only other "odd" thing I have is the Intel Graphics repository
[11:10] <tibi> I've installed the intel drivers, per #kubuntu suggestion
[11:10] <clivejo> oh
[11:10] <clivejo> that could be your problem
[11:11] <tibi> I've added the intel repo to try to fix the crashing problem, it was there before
[11:11] <tibi> even with stock KDE
[11:11] <acheronuk> is that the 01.org ones?
[11:11] <tibi> "stock Kubuntu 16.04"
[11:11] <tibi> acheronuk: yes, the https://download.01.org/gfx/ubuntu/16.04/main
[11:13] <acheronuk> without a log or error give a clue to a reason, it's hard to diagnose
[11:14] <tibi> acheronuk: I'll provide a section from from my .xsession-errors
[11:14] <acheronuk> I've had intel be rock stable sometimes, and a bit error prone at others
[11:15] <acheronuk> one reason why debian etc are wanting to fall back to modesetting and drop the driver
[11:15]  * acheronuk goes in hunt of articles saying to add the staging ppas !!!!
[11:16] <tsimonq2> acheronuk: what's blocking us from getting 5.7.5 in backports?
[11:16] <acheronuk> tsimonq2: I explained only a day or 2 ago
[11:16] <tsimonq2> oh? /me greps logs
[11:16] <tibi> http://paste.ubuntu.com/23274614/
[11:18] <acheronuk> tsimonq2: --> http://paste.ubuntu.com/23274620/
[11:19] <tsimonq2> acheronuk: in your honest opinion, what should migrate to backports-landing first?
[11:21] <tsimonq2> acheronuk: imho we should land Frameworks, then Plasma, then Apps
[11:21] <tsimonq2> acheronuk: I could have our little mini dep tree messed up though ;)
[11:21] <tibi> http://paste.ubuntu.com/23274626/ this is better, it has the crash inside
[11:21] <acheronuk> the staged plasma for xenial was built with FW 5.24 I think, so needs a rebuild on staged 5,26 I think
[11:22] <tsimonq2> acheronuk: which is why I say that we should get that good to go first
[11:23] <acheronuk> tsimonq2: we should get YY good to go FIRST
[11:23] <tsimonq2> ah yes
[11:23] <tsimonq2> that
[11:24] <tsimonq2> acheronuk, santa_, clivejo: what's left for all the mess in yakkety-proposed?
[11:24] <acheronuk> tsimonq2: even plasma and FW on YY is still help up a bit on autopackagetests
 Specifically?
[11:25] <acheronuk> tsimonq2: and to quote the release team.......
 santa_: right; my point is, if these packages don't clear proposed-migration on their own merits, chances are they will not make it for release
 Which is why I'm asking the *specifics* of what we're dealing with.
 I don't want that to happen
[11:26] <acheronuk> any with failing tests on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
 God forbid we release a half migrated anything
[11:28] <acheronuk> I'm going to go through that later to try to work out what can be done, but many of the tests fail without really giving a good reason in the logs
[11:29] <acheronuk> or at least not one that makes sense to me
 You know how to reproduce locally?
[11:29] <acheronuk> never tried
 Launchpad likes to mangle some things sometimes
 It's on the ProposedMigration page
[11:33] <acheronuk> tsimonq2: that page. which no matter how many times you read parts of it, makes little sense
 YOU
 To ME it makes perfect sense
[11:34] <acheronuk> tsimonq2: each to their own. I could give you a page of QM that makes sense to me, but would look like gibberish to you
[11:35] <tsimonq2> yeah
[11:35] <clivejo> but you are Super Simon
[11:35] <tsimonq2> lol
[11:35] <tsimonq2> cosas buenas
[11:36] <tsimonq2> autopkgtests
[11:36] <tsimonq2> autopkgtest tests are run in ephemeral cloud instances as described on /AutopkgtestInfrastructure. The update excuses link to relevant test results, and all results can be browsed on http://autopkgtest.ubuntu.com.
[11:36] <tsimonq2> In most cases test results should be reproducible in a local QEMU VM.
[11:36] <tsimonq2> Reproducing tests in the cloud
[11:36] <tsimonq2> Reproducing tests as they are run in production requires access to an OpenStack-based cloud (e.g. Canonistack). Source the relevant nova.rc file with the cloud credentials. Ensure that you have autopkgtest 3.16 or newer installed (the deb installs on all supported Ubuntu releases without further dependencies).
[11:36] <tsimonq2> First make sure that your cloud knows your public SSH key, in nova keypair-list. If you don't have one yet, add it with nova keypair-add. Let's call this testkey here.
[11:36] <tsimonq2> You can now run your tests with the ssh runner and the nova setup script, e. g. for the libpng package:
[11:36] <tsimonq2>     autopkgtest libpng --apt-pocket proposed --apt-upgrade --setup-commands cloud-vm-setup \
[11:36] <tsimonq2>       -- ssh -s nova -- --flavor m1.small --image ubuntu-trusty-i386-server.img --keyname testkey
[11:36] <tsimonq2> The complete command as used in production (including all proxy settings) can also be seen at the top of test logs.
[11:36] <acheronuk> ^^^^ gibberish
[11:36] <tsimonq2> acheronuk: is that confusing to you?
[11:36] <acheronuk> lol
[11:36] <tsimonq2> you must have a hard life... :P
[11:36]  * tsimonq2 runs
[11:37] <tsimonq2> do you know what QEMU is?
[11:37] <acheronuk> tsimonq2: it's perspective. each person has a different background
[11:41] <acheronuk> soee_: :P https://www.kde.org/announcements/plasma-5.8.0.php
[11:43] <santa_> tsimonq2: various uploads and autopkgtests
[11:43] <soee_> :D
 Y'all get Harald's email?
 I say get rid of Apport :P
[11:57] <acheronuk> I normally disable the damn thing anyway, unless I really need it for a report
 Me too
[12:12] <mamarley> Same here.
[12:13] <mamarley> clivejo: Congratulations on making Developer!!
[12:14] <clivejo> thanks, not as happy an occasion as I thought it would be
 What's wrong, Clive?
[12:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #109: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_okteta/109/
[12:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #103: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/103/
[12:48] <acheronuk> Mirv: do you know why tests like this would timer out<EMAIL_ADDRESS>[13:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #104: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/104/
[13:26] <soee_> clivejo: you have now power to upload to archive ? :)
[13:32] <acheronuk> soee_: in 'theory'. I think clive wants to gain more experience before doing so though?
[13:39] <BluesKaj> Hey folks
[13:40] <soee_> hiho BluesKaj
[13:47] -kubuntu-ci:#kubuntu-devel- Project merger_okteta build #641: FAILURE in 16 sec: http://kci.pangea.pub/job/merger_okteta/641/
[13:52] <BluesKaj> hey soee_
[14:12] <marco-parillo> Hi all; I welcome our new Kubuntu Developer Overlord.
[14:13] <BluesKaj> oh? and who can that be mparillo ? :-)
[14:13] <BluesKaj> marco-parillo,^
[14:17] <marco-parillo> mparillo is my KDE identity (used on my bouncer). marco-parillo is my Launchpad ID, used at work via IRC webchat (IRC ports are blocked here).
[14:18] <marco-parillo> Oh, the question was clivejo is now a Kubuntu Developer.
[14:18] <marco-parillo> The joke came from a Simpsons meme.
[14:50] <Mirv> acheronuk: possibly some stale test process that isn't ended correctly
[14:52] <acheronuk> Mirv: and it would do that on all architectures? as it has done?
[14:53] <acheronuk> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kwin
 Eek!
[15:23] <acheronuk> tsimonq2: eek what?
[15:25] <acheronuk> if you mean that test failure, there is plenty more where that came from :/
[15:26] <acheronuk> tempting to just sign off and come back once ZZ 17.04 has got under way
[15:28] <BluesKaj> I've had 2 yakkety iso images fail after the download, think the source files are corrupt ...yakkety is becoming even messier by the day
[15:32] <acheronuk> BluesKaj: you are a jinxed tester. everything you touch seems to break
[15:32]  * clivejo does even know what that means
[15:32] <clivejo> fail after download?
[15:34] <BluesKaj> md5sums
[15:37] <BluesKaj> nope acheronuk, it's just yakkety ...xenial is running perfectly here even after upgrading with staging ppas last week.
[15:50] <santa_> acheronuk: do you still have the frameworks clones you used for the 5.26 uploading?
[15:51] <acheronuk> santa_: maybe on my other machine
[15:52] <santa_> acheronuk: ok, it's not urgent, but whenever you get there check the e-c-m tag
[15:52] <santa_> it seems it wasn't pushed
[15:53] <acheronuk> odd. will do in a little bit
 Hey clivejo, you should upload calligra :P
[16:03] <clivejo> no I shouldnt
 Lol
 Why not? :P
[16:04] <clivejo> does it have a FFE?
 Afair Kubuntu doesn't follow Feature Freeze
 Plus it's ftbfs
[16:34] <Mirv> acheronuk: sorry on my (Ubuntu) phone and on the run, but yes we have seen cases where a thread by the software was loose at the end of the test run so the autopkgtests waited for it and only killed after 300 minutes or so when the infra kills the test. I can't check the logs right now easily.
[16:36] <acheronuk> Mirv: no problem
[17:38] -kubuntu-ci:#kubuntu-devel- Project merger_okteta build #642: STILL FAILING in 18 sec: http://kci.pangea.pub/job/merger_okteta/642/
[17:53] -kubuntu-ci:#kubuntu-devel- Project merger_extra-cmake-modules build #782: FAILURE in 17 sec: http://kci.pangea.pub/job/merger_extra-cmake-modules/782/
[18:03] -kubuntu-ci:#kubuntu-devel- Project merger_marble build #470: STILL FAILING in 23 sec: http://kci.pangea.pub/job/merger_marble/470/
[18:34] <acheronuk> santa_: did you say something was being done with drumstick?
[18:34] <santa_> acheronuk: we have to upload it
[18:34] <santa_> we have it in the ppa but not in the archive
[18:35] <acheronuk> yep. who? how?
[18:35] <santa_> acheronuk: let me check later, I feel ark is going to be ready soon
[19:00] <ahoneybun> is it just me or does the guy in the 5.8 video sound like Chris from the Linux Action Show?
[19:15] <soee> "Linux Action Show's Chris Fisher takes us through the existing and new features"
[19:43] <santa_> clivejo: remember to push the ark commit + tag
[19:46] <clivejo> santa_: I did push after the upload
[19:46] <clivejo> but I dont see it in the web UI
[19:48] <clivejo> http://paste.ubuntu.com/23276515/
[19:48] <santa_> hmm I don't get it here with git pull
[19:49] <santa_> push again?
[19:49] <santa_> also what does 'tig' say about kubuntu_yakkety_archive and origin/kubuntu_yakkety_archive ?
[19:49] <clivejo> $ git push --tags origin
[19:49] <clivejo> Everything up-to-date
[19:49] <santa_> do they point to the same commit?
[19:50] <santa_> hmm
[19:50] <santa_> try git push origin kubuntu_yakkety_archive
[19:50] <santa_> and then git push --tags
[19:52] <clivejo> ok that worked
[19:52] <clivejo> that was weird
 (Photo, 720x1280) https://irc-attachments.kde.org/43DZENaH/file_665.jpg Screenshot (Oct 4, 2016 3:54:58 PM)
 :( :(
[19:57] <santa_> clivejo: I think it tries to push master if you don't say the branch
[19:58] <acheronuk> I'm fairly sure I didn't have to do that pushing tags the other day
[20:54] <santa_> clivejo: are you still around?
[21:16] <clivejo> santa_: I am now
[21:18] <santa_> clivejo: libkeduvocdocument is ready to upload in git
[21:18] -kubuntu-ci:#kubuntu-devel- Project merger_libkeduvocdocument build #709: FAILURE in 14 sec: http://kci.pangea.pub/job/merger_libkeduvocdocument/709/
[21:19] <santa_> while there is so much diff, it's just an soname bump requested by the release team to accept the package for yakkety
[21:20] <tsimonq2> they're talking about Plasma 5.8 now on Linux Unplugged
[21:20] <tsimonq2> I'm in the queue to say hai
[21:21] <valorie> oh nice
[21:21] <tsimonq2> and he moved on from it /o\
[21:22]  * valorie is preparing to leave for the cabin
[21:22] <valorie> it is really dark and dreary here!
[21:22] <tsimonq2> valorie: have a fun time :)
[21:22] <clivejo> santa_: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/libkeduvocdocument/commit/?id=2e670f6bbf0796f49511dabb1a666c15298045b5
[21:22] <clivejo> seems to be missing a changelog entry?
[21:22] <valorie> no internet, beyond enough phone bandwidth for an occasion Telegram update
[21:23] <clivejo> is that on purpose?
[21:23] <valorie> no indeed
[21:23] <valorie> when we can get something up there, we will
[21:23] <santa_> clivejo: ugh, nope, adding it now...
[21:24]  * clivejo is amazed at how socially as ease Simon is
[21:25] <clivejo> at his age I wouldnt have said boo to a ghost
[21:25] <wxl> well we've had to work on him a bit since he entered the community XD
[21:25] <wxl> still, he is certainly well ahead in many areas
[21:25] <santa_> clivejo: added now
[21:26] -kubuntu-ci:#kubuntu-devel- Project merger_libkeduvocdocument build #710: STILL FAILING in 14 sec: http://kci.pangea.pub/job/merger_libkeduvocdocument/710/
[21:27] <valorie> https://goo.gl/maps/2jL8NkMGGqw -- small clearing across the river from the end of the runway is where our cabin is
[21:27] <tsimonq2> clivejo: oh?
[21:27] <valorie> not a lot of reasons for a company to provide service up there
[21:28] -kubuntu-ci:#kubuntu-devel- Project merger_libkeduvocdocument build #711: STILL FAILING in 15 sec: http://kci.pangea.pub/job/merger_libkeduvocdocument/711/
[21:29] <clivejo> tsimonq2: yeah, I was a shy wee thing
[21:29] <clivejo> still am
[21:31] <clivejo> santa_: done
[21:36] <santa_> clivejo: ok, I will have dinner and talk to steve later, thanks!
[21:37] <clivejo> any idea why none of our uploads have been processed yet other packages in the queue before and after us have?
[21:40] <clivejo> and why every question I ask gets ignored! :/
[21:50] <tsimonq2> clivejo: ping someone
[21:50] <tsimonq2> clivejo: slangasek infinity etc.
[21:50] <tsimonq2> clivejo: if it's urgent make it urgent
[21:50] <clivejo> I have
[21:50] <tsimonq2> ok
[21:50] <tsimonq2> well
[21:50] <tsimonq2> what have you said?
[21:51] <tsimonq2> 14:28 < clivejo> slangasek: would you have time to help with something?
[21:51] <tsimonq2> NEVER EVER EVER ask them something like that :P
[21:52] <tsimonq2> clivejo: what did you need? I'll throw a ping his way
[21:52] <clivejo> I have a few questions
[21:52] <tsimonq2> !ask
[21:52] <tsimonq2> clivejo: follow that advice by heart ^^^^^^
[21:52] <acheronuk> ha!
[21:53] <clivejo> I wanted to know how we deal with the kdeconnect renaming
[21:53] <acheronuk> ubottu knows best
[21:53] <acheronuk> except on that ^^^
[21:53] <tsimonq2> clivejo: the release team won't bat an eye if you don't ask then questions they can answer
[21:53] <clivejo> and how we add new packages
[21:53] <tsimonq2> clivejo: you upload and it goes into a NEW queue
[21:54] <tsimonq2> clivejo: for package renames, it's just a metter of renaming the appropriate files, it might go in the NEW queue
[21:54] <clivejo> can you stuff be added at this time?
[21:54] <tsimonq2> *matter
[21:54] <clivejo> can new
[21:54] <tsimonq2> clivejo: well ask them, tell them why :)
[21:54] <clivejo> I have asked lots of question and never got an answer
[21:55] <clivejo> the only answer I ever got was to make a donation
[21:55] <tsimonq2> clivejo: give me a specific one line question, and I'll show you how to ask it :P
[21:55] <tsimonq2> OH SH*T XD
[21:55] <tsimonq2> "make a donation" lol
[21:55] <acheronuk> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[21:56] <acheronuk> for kirigami ??
[21:56] <tsimonq2> clivejo: plus the release team knows me because I act as Lubuntu release manager from time to time :)
[21:56] <tsimonq2> clivejo: come on, ask me!
[21:56] <tsimonq2> don't be shy! :P
[21:56] <clivejo> oh I see, favouritism
[21:57] <tsimonq2> well they'll (most likely) pay more attention to pings from people they know
[21:57] <acheronuk> more likely they know that if they don't answer, he won't go away ;)
[21:58] <acheronuk> tsimonq2: or what you said
[21:58] <tsimonq2> !ignore
[21:58] <tsimonq2> acheronuk: ubottu knows best ;)
[22:01] <acheronuk> I know
[22:10] <clivejo> tsimonq2: how do I get this package sync'ed with debian and into yakkety - https://bugs.launchpad.net/ubuntu/+source/libdrumstick/+bug/1584310
[22:12] <tsimonq2> ok I'll ask them that
[22:16] <tsimonq2> !info drumstick-alsa unstable
[22:16] <tsimonq2> :/
[22:16] <clivejo> libdrumstick
[22:17] <tsimonq2> !info libdrumstick unstable
[22:17] <tsimonq2> :/
[22:17] <tsimonq2> aha nvm
[22:18] <tsimonq2> 0.5.0-4 is in unstable
[22:18] <tsimonq2> !info libdrumstick testing
[22:18] <clivejo> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824771
[22:18] <tsimonq2> whatever
[22:18] <tsimonq2> clivejo: oh so you want it updated to the latest version?
[22:19] <tsimonq2> I wish the bug report could have mentioned that...
[22:19] <clivejo> libdrumstick (1.0.2-1) unstable; urgency=medium
[22:19] <clivejo> it does
[22:19] <clivejo> Changed in libdrumstick (Debian):
[22:19] <clivejo> status:	New → Fix Committed
[22:19] <tsimonq2> oh nvm
[22:19] <clivejo> Committed → Fix Released
[22:20] <acheronuk> they did it?
[22:20] <clivejo> debian did it
[22:20] <clivejo> Ubuntu havent
[22:20] <tsimonq2> clivejo: not in unstable, can't sync
[22:21] <tsimonq2> clivejo: harumph, https://launchpad.net/debian/+source/libdrumstick
[22:21] <acheronuk> experimental
[22:22] <clivejo> https://launchpad.net/debian/+source/libdrumstick/1.0.2-1
[22:22] <tsimonq2> libdrumstick (1.0.2-1) experimental; urgency=medium
[22:22] <tsimonq2> but you don't understand
[22:22] <tsimonq2> no SANE Ubuntu Release team member would even TRY to sync from Experiemental
[22:23] <tsimonq2> clivejo: you have to poke someone to migrate it
[22:23] <clivejo> Im fed up poking
[22:23] <clivejo> my finger is sore
[22:23] <tsimonq2> clivejo: even then, it has to migrate from Sid to Stretch, which takes a minimum of five days
[22:24] <clivejo> well minuet isnt going anywhere then
[22:24] <tsimonq2> clivejo: slangasek will poke it later so it gets out of the NEW queue
[22:24] <tsimonq2> OH that's something
[22:25] <tsimonq2> the uploader is Ross Gammon!
[22:25] <clivejo> its needs libdrumstick to build
[22:25] <clivejo> thats why I opened that bug back in May
[22:26] <tsimonq2> clivejo: then why do you wait a week and a half before release to bump it!
[22:26] <clivejo> because minuet is stuck in the queue
[22:27] <clivejo> and it needs libdrumstick!
[22:27] <clivejo> as I said in the report requires 'drumstick-alsa>=1.0.1'
[22:29] <tsimonq2> clivejo: check your facts, dude. I asked the release team to do that, and you kept facts.
[22:30] <clivejo> Im too tired and fed up to argue
[22:59] <ScottK> tsimonq2: re syncing from experimental, it depends on why it's there.
[23:10] <tsimonq2> ScottK: oh?
[23:10] <tsimonq2> ScottK: please explain
 Marble just been accepted
[23:15] <acheronuk> :)
[23:16] <tsimonq2> :D
[23:19] <acheronuk> accepted okteta
[23:26] <acheronuk> our uploads are now buried under a pile of 'mate'
 I don't like the idea of any of our packages mating
 We have enough as it is
[23:27] <wxl> you mean mah-tay-ing
[23:28] <ScottK> tsimonq2: as an example, sometimes a package is in experimental only because the Debian release team hasn't given the OK to start a transition due to other transitions in progress.
[23:38]  * acheronuk yawns
[23:38] <acheronuk> zzzzzzzzzzzz
 ScottK is there a way to remove a package that has been uploaded?
 But is stuck in the queue
 I believe its stuck in NEW
 Good night all :)
[23:44] <acheronuk> oooh. Unapproved: accepted extra-cmake-modules [source] (yakkety-proposed) [5.26.0-0ubuntu2]
 Good night Rik, thanks for all your help today bringing me up to speed
[23:50] <ScottK> If it's in source New, removal is easy.  If it's binary New it's more complicated since the source has already been accepted
 It is minuet which needs an updated libdrumstick to build
 Might be better to drop it and start afresh in zz
[23:56] <tsimonq2> .or
[23:56] <tsimonq2> whoops
 Backport it to our PPA


[08:02] <froud> Hi, anyone know if egroupware install on edgy server works
[08:03] <froud> I tried an install on dapper but came up against https://launchpad.net/distros/ubuntu/+source/egroupware/+bugs
[08:04] <froud> Wondering if anyone tried edgy before I dist-upgrade
[08:15] <ivoks> server people :)
[10:13] <Amon_Re> hey guys
[10:14] <Amon_Re> anyone awake?
[10:15] <Amon_Re> hey samit
[10:17] <ivoks> hi
[10:17] <samit> hey
[10:19] <Amon_Re> samit: you don't happen to use lvm do you?
[10:19] <ivoks> wii samit
[10:19] <ivoks> lol :)
[10:19] <ivoks> i use lvm
[10:20] <Amon_Re> wii?!
[10:20] <ivoks> Amon_Re: /wii samit
[10:20] <ivoks>  like whois
[10:20] <Amon_Re> ivoks: i know, was joking about the Nintendo Wii ;)
[10:21] <samit> no, I'm not using lvm.. why? :)
[10:21] <Amon_Re> ivoks: do you use lvm on your desktop or just on your server?
[10:21] <ivoks> Amon_Re: both
[10:22] <Amon_Re> samit: i have 2 computers, both using lvm, neighter of them can log into ubuntuforums.com , password gets accepted, cookey gets written, but it keeps saying i'm not logged in, these are both fresh installs
[10:22] <ivoks> that has nothing to do with lvm
[10:22] <Amon_Re> only thing they have in common is the version of ubuntu (edgy) and lvm
[10:23] <Amon_Re> ivoks: i have no clue what else it could be, ephythingy (what's it called, the gnome browser) has the exact same issue
[10:23] <ajmitch> absolutely nothing to do with lvm, in fact :)
[10:23] <ivoks> well, lvm can't be
[10:24] <Amon_Re> i'm willing to believe it's not lvm, heck, i'd love to believe it, but if it's not lvm, then what could it be? ;)
[10:24] <ivoks> browser, and only browser
[10:25] <ivoks> or proxy, if you use it
[10:25] <Amon_Re> ivoks: i checked my settings, couldn't find anything wrong with them
[10:25] <Amon_Re> no proxy
[10:25] <Amon_Re> no extensions
[10:25] <Amon_Re> nothing at all, i'm on a clean installed laptop, the only extra's on this laptop are xchat & mc, it has the same problem
[10:26] <samit> do any cookies get saved? you can check them in Firefox from: Edit - Preferences - Privacy - Show cookies
[10:26] <Amon_Re> file permissions seems fine
[10:26] <Amon_Re> samit: yep, i see them
[10:27] <ivoks> well, whatever it is, it's not related to ubuntu-server development or use of ubuntu-server :)
[10:27] <Amon_Re> ivoks: i know, but i figured it'd be more likely to find lvm users here ;)
[10:27] <Amon_Re> because that's what i was suspecting
[10:28] <Amon_Re> ivoks: know any other browsers that are available in the repos?
[10:28] <ivoks> Amon_Re: konqueror, epiphany, mozilla, lynx, links, w3m...
[10:28] <mralphabet> here's vote three for nothing to do with lvm
[10:29] <Amon_Re> ivoks: i'll try konqueror, links & lynx are slightly to arcane for me ;)
[10:30] <ivoks> now... what do you think ubuntu-server is missing, if anything?
[10:30] <Amon_Re> it's annoying tho, can't post at the forums because of the problem....
[10:30] <ivoks> (this is unrelated to lvm and Amon_Re's problem)
[10:30] <Amon_Re> ivoks: exchange replacement
[10:31] <ivoks> other than that :)
[10:32] <Amon_Re> ivoks: dunno anything else really, the rest i need is there (web, mail, ftp, file & print, scanning)
[10:32] <mralphabet> I need a way to monitor hardware raid . . . (lsi megaraid specifically) and I haven't found a utility to do it
[10:32] <ivoks> mralphabet: there's a tool
[10:32] <ivoks> mralphabet: i use it, daily
[10:33] <mralphabet> ivoks: I figured there was, I just haven't crossed paths with it yet
[10:33] <ivoks> mralphabet: it's not good as 3ware's, but...
[10:33] <mralphabet> is anything?
[10:34] <ivoks> it's ok for rebuild, monitor, etc..
[10:34] <ivoks> it's called megamgr
[10:34] <ivoks> non-free
[10:35] <ivoks> mralphabet: what card you have?
[10:35] <mralphabet> ivoks: thanks, I'll take a look
[10:35] <mralphabet> an i4
[10:35] <ivoks> mralphabet: i'll give you a link
[10:37] <ivoks> mralphabet: http://www.grad.hr/~ivoks/ut_linux_mgr_5.20.zip
[10:37] <ivoks> i have problems with LSI
[10:37] <ivoks> and dapper :/
[10:37] <mralphabet> ivoks: heh, I haven't had any problems yet . . . it's an older card, I figured any support issues should be nailed down by now for it
[10:37] <mralphabet> ivoks: thanks for the zip, afk a few
[10:38] <ivoks> i get high iowait and low write speed
[10:38] <ivoks> where low is ~ 6MB/s
[10:38] <ivoks> that's and Intel(R) RAID Controller SRCS16
[10:39] <Amon_Re> Hah!
[10:41] <Amon_Re> incase anyone wonders, the problem was the url, www.ubuntuforums.org works, .com doesn't (logging in that is)
[10:43] <Amon_Re> ivoks: 6MB? That's a sata raid ain't it?!
[10:43] <ivoks> yes
[10:43] <Amon_Re> should be faster
[10:44] <ivoks> a lot faster
[10:44] <ivoks> redhat had the same problem
[10:44] <ivoks> but then they fixed it in kernel
[10:44] <Amon_Re> what kernel do you use?
[10:44] <ivoks> i should grab their source and see what they did
[10:44] <ivoks> dapper's 2.6.15
[10:45] <Amon_Re> wasn't there a more recent one backported?
[10:47] <Amon_Re> btw, ever played with evms?
[10:47] <ivoks> i don't use backports on production machines
[10:47] <Amon_Re> i see
[10:47] <ivoks> i tried edgy's kernel, but same thing
[10:48] <ivoks> i'll check out redhat's kernel
[10:49] <Amon_Re> good luck :)
[10:49] <ivoks> thanks
[10:50] <Amon_Re> don't happen to know a decent way to share evolution calendars between multiple computers do you?
[10:51] <ivoks> webdav?
[10:51] <Amon_Re> ivoks: i've been looking into it, and i can publish a calendar onto my webserver, but the other machines can only use it as a read-only calendar, seems rather messy really
[10:52] <Amon_Re> syncml would be cool, had it not been buggy & in java
[10:52] <Amon_Re> caldav is something i never even heard of untill i saw the plugin in evo :P
[10:53] <Amon_Re> there just isn't anything out there that even comes close to be an exchange replacement :(
[10:55] <mralphabet> ivoks: have you seen anything that will report health of the array?  or is it in megamgr and I'm just not seeing it?
[10:57] <ivoks> Amon_Re: openexchange
[10:57] <ivoks> mralphabet: Configure -> Add/View
[10:58] <mralphabet> ivoks: ahh, thanks
[10:58] <Amon_Re> ivoks: never gotten that to work (although that was quite awhile ago.... ) maybe i should give it another shot
[10:58] <ivoks> mralphabet: or Objects, Logical Drive, View/Update
[10:58] <ivoks> Amon_Re: well, i got it working on breezy a year ago
[10:58] <mralphabet> ivoks: perfect, thanks again
[10:59] <ivoks> i think i found rh's patch
[11:01] <Amon_Re> ivoks: how well did/does it run?
[11:01] <ivoks> Amon_Re: it worked; it was proof of concept; i had to re-install it on redhat (which was supported platform, but produced worse results :)
[11:02] <Amon_Re> lol :)
[11:03] <Amon_Re> well, i guess i could go the openxchange route (although getting that beast to run on a gentoo server might be painfull), but it's overkill for my needs atm, simple calendar syncing/sharing should be easy!


[01:57] <SonikkuAmerica> I see the great Phanes has returned
[01:58] <SonikkuAmerica> (to #u)
[01:58] <k1l> yes
[01:58] <SonikkuAmerica> he seems a bit more amenable now
[02:06]  * hggdh reserves opinion at the moment
[09:40] <bazhang> I'd doubt its tatertots doing the trolling here
[09:41] <k1l> no, he is known for it
[09:41] <bazhang> really
[09:41] <bazhang> thought I saw him doing some support earlier
[09:42] <k1l> yes, there were some users in last months reporting tatertots pmed them and even tried to get access to their machines
[09:43] <bazhang> heh missed that
[09:43] <bazhang> riqj seems to be cycling the same question in search of a 'better' answer
 turbo negro
[10:00] <bazhang> that sounds wrong


[07:17] <dholbach> good morning
[08:09] <czajkowski> aloha
[08:34] <popey> dholbach: need to move our meeting because I need to relocate shortly
[08:34] <dholbach> popey, ok, WFM... where do you want to move it to?
[08:34] <popey> already moved
[08:38] <dholbach> popey, ok, I'll have lunch a bit earlier then, no worries
[08:38] <popey> move it to any time later, its no bother, not critical
[08:38] <popey> ☻
[09:11]  * popey relocates, back in ~30 or so
[10:53] <popey> dholbach: want me to move that meeting or do you want to it now (in 5 mins)?
[10:56] <dholbach> popey, should be fine to do it now
[10:56] <popey> ok
[11:22] <dholbach> popey, about the xda:devcon talk summary!
[11:24] <popey> will mail you after lunch
[11:24] <dholbach> thanks
[13:59] <dholbach> popey, about the xda:devcon talk summary! :)
[14:13] <popey> oof
[14:18] <dholbach> popey, brilliant - thanks
[14:18] <popey> that okay?
[14:19] <dholbach> it is :)
[14:38] <dpm> I keep getting notifications from the new phone notifications daemon
[14:38] <popey> welcome to my world
[14:38] <dpm> for the same e-mails I received months ago
[14:38] <dpm> either that or dholbach keeps sending me the same message over and over
[14:40] <dholbach> dpm, what?
[14:40] <dholbach> dpm, what?
[14:40] <dholbach> dpm, what?
[14:40] <dholbach> dpm, what?
[14:40] <dholbach> dpm, what?
[14:40] <dholbach> dpm, what?
[14:40] <dholbach> dpm, what?
[14:40] <dpm> any channel ops here? we might need to ban someone
[14:41] <dholbach> finally :)
[14:42] <dholbach> I thought ASCII art would get me kicked out of here
[14:42] <dholbach> I guess I didn't try hard enough :)
[14:42]  * Pici lurks
[14:52] <popey> dpm: dholbach https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1352604
[14:52] <popey> https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1352602
[14:52] <popey> https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1352599
[14:52] <popey> feel free to confirm and lobby ☻
[14:52] <popey> filed those last night after getting pissed off at the notification bing telling me about 6 month old mail ☻
[14:56]  * dpm joins the mute all the notifications lobby
[14:57]  * dpm hugs dholbach
[14:57]  * dholbach hugs dpm back :)
[15:02] <popey> heh
[15:07]  * czajkowski passes the jaffa cakes around
[15:07] <belkinsa> Yum!
[15:09] <popey> \o/
[15:13] <dpm> popey, when testing file manager I've noticed this: could you confirm https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1352941 ?
[15:15]  * popey looks
[15:15] <dpm> argh
[15:15] <dpm> I can no longer reproduce
[15:15] <dpm> I think notifications brought back the screen lock to life
[15:18] <popey> yeah, works here
[16:08] <dholbach> have a great rest of your day everyone - see you tomorrow!
[18:55] <cjohnston> ~/13


[06:33] <lordievader> Good morning
[06:41] <alkisg> o/
[10:35] <mrcarist> Test
[12:50] <BluesKaj> Hi all
 guys in kubuntu my bluetooth not exist
 he existed in this computer with windows
 but now not detect my bluetooth in blueman
 what i can do
 Greetings Huge thanks for the Creation of Kubuntu and Linux in general! I need some help pls how can I stop Skype in my startup applications cuz when I go into my Autostart I cant find Skype there thx ..🤙🏾
[17:55] <mparillo> Perhaps you need to start with a blank session (at least one time)?
[17:57] <mparillo> System Settings > Startup and Shutdown > Desktop Session > Check Start with an empty session.
 Sorry for that thank you peace n love!
[19:35] <Guest59> Hi there
[19:37] <Guest59> I use Kubuntu 20.10 groovy under my amd64 desktop. I have bought an HP Neverstop 1000w laser printer and am struggling to make it work
[19:40] <Guest59> I apt installed the latest deb packages hplip, which is version 3.20.5 (whereas the latest one on HPLIP site is 3.21.4), but I am only able to print a test page from the CUPS web interface and nothing else
[19:40] <Guest59> Any help?
[19:41] <alkisg_web> Guest59, for an HP 1100something laser printer, I had to `apt purge ippusbxd` because it was trying to put the printer in driverless printing mode
[19:41] <alkisg_web> After purging that, and installing normally via the ppd file, it worked fine
[19:42] <alkisg_web> Your mileage may vary, but maybe that'll also help in your case
[19:42] <alkisg_web> (reboot needed after purging the package)
[19:42] <Guest59> When I run hp-check, i get, as the summary, that there are 3 errors and 4 warnings
[19:46] <Guest59> The errors are: Missing Requiredd Dependencies: 'libcups2' package is missing/incompatible. libcups2 version 2.3.3 IS installed but allegedly incompatible...
[19:48] <Guest59> the other errors are (2) missing python3-pyqt4-dbus and (3) missing python3-pyqt4,
[19:52] <enyc> Guest59: for what its' worth 20.10 about out of support (maybe end of month)
[19:52] <enyc> Guest59: in short as a non-LTS release and with package fun you might be best just to update to 21.04 and then try again / fix/ whatever ....
[19:53] <enyc> or reinstall 21.04 kubuntu and have printing working theer, etc.
[19:55] <Guest59> @alkisg_web and @enyc: thank you both. alkisg_web suggestion seems to have worked (without any need for rebooting)...
[20:26] <Mekaneck> 20.10 goes EOL on the 22nd of July
 Guys how can you change DE from kde to gnome on kubuntu?
[21:35] <tomreyn> alessandro_forleo: you can do this, but it can take a lot of time to identify the packages to remove, and you may not actually identify all the packages you could remove.
[21:35] <tomreyn> so a better approach can be a fresh install.
[21:36] <tomreyn> if you still want to replace, then installing    ubuntu-desktop    should get you the default gnome based ubuntu desktop
[21:37] <tomreyn> there's a good chance that things won't work well until you've removed several of the kubuntu specific packages, though, or changed some defaults.
[21:51] <RikMills> tomreyn: they decided to ignore the telegram captcha, so got booted
[21:52] <tomreyn> thanks. that's where those bridges are severely lacking
[21:55] <RikMills> point taken, though it it is not often that someone genuine ignores it like that