[04:49] <kubotu> ::workspace-bugs:: [1050776] kde4-window-decorator crashes when starting up with oxygen theme @ https://bugs.launchpad.net/bugs/1050776 (by Iven Hsu)
[06:52] <kubotu> ::workspace-bugs:: [1050776] kde4-window-decorator crashes when starting up with oxygen theme @ https://bugs.launchpad.net/bugs/1050776 (by Iven Hsu)
[07:56] <kubotu> ::workspace-bugs:: [1013626] systemsettings crashed with ImportError in /usr/share/kde4/apps/language-selector/language... @ https://bugs.launchpad.net/bugs/1013626 (by Xavier Besnard)
[12:19] <Riddell> schedule the meeting: http://www.doodle.com/2wei2a87kq6sbgxf
[12:19] <Riddell> apachelogger: still planning on doing plymouth SRU and fixing ipod support and have you not found a better todo list then the channel /topic ?
[12:20] <jussi> Riddell: email sent
[12:21] <jussi> bah, these doodles are so annoying...
[12:21] <jussi> I have no idea what tomorrow holds, never mind a week from now...
[12:24] <jussi> Riddell: Hey, I like the urgent todo being in the topic
[12:37] <Riddell> jussi: which urgent todo?
[12:37] <jussi> Riddell: Haralds todo's :P
[12:40] <Riddell> he doesn't seem to be processing them very urgently...
[13:39] <ScottK> Probably just the alchohol related ones.
[13:43] <jussi> lol
[13:48] <BluesKaj> Hi all
[14:27] <apachelogger> ipod is supposed to get fixed by shadeslayer actually
[14:39] <Riddell> shadeslayer: is there a work item in that?
[14:55] <shadeslayer> apachelogger: the media-player thingum?
[14:59] <Riddell> ScottK: you said something about milestones the other day, can you remind me what that was?
[15:02] <apachelogger> shadeslayer: yes, the one you were supposed to talk to sune about
[15:02] <apachelogger> ...
[15:02] <shadeslayer> right, I'm not sure if Sune followed up on that ...
[15:05] <shadeslayer> silly users, report a bug, don't reply to call for testing
[15:05] <apachelogger> last I asked IIRC he had discussed it with the others but did not give me any results and since I am too lazy to go to another server to discuss stuff I do not actually care about...
[15:05] <shadeslayer> lemme ping him
[15:10] <Quintasan_> What kind of retar...
[15:11] <Quintasan_> shadeslayer, apachelogger: is it possible to determine which number out of 4 numbers is the highest one using only two compare operations?
[15:14] <apachelogger> Quintasan: context?
[15:16] <Quintasan> apachelogger: My friend told me he wanted me to help him with his homework, he has print the highest number out of 4 user supplied numbers
[15:16] <Quintasan> using two comapring operations
[15:16] <Quintasan> I told him it's impossible
[15:16] <apachelogger> as in programming or algorithmic homework?
[15:17] <Quintasan> apachelogger: AFAIR he told me they are still doing those flow charts
[15:17] <Quintasan> as in, no code
[15:17] <apachelogger> what's the course about though ^^
[15:17] <Quintasan> stuff like http://upload.wikimedia.org/wikipedia/commons/thumb/9/91/LampFlowchart.svg/220px-LampFlowchart.svg.png
[15:18] <Quintasan> apachelogger: introduction to programming
[15:18] <apachelogger> oh brrrrrrrrr
[15:18] <apachelogger> well, you can technically do it using two comparisions but those would be in a loop
[15:18] <Quintasan> apparently the flowchart part should be done after brief introductuion and a few exercises but they will apparently have one on the test
[15:18] <Quintasan> apachelogger: in a loop?
[15:19] <Quintasan> how exactly would that work?
[15:19] <apachelogger> i.e. while (int a = read()) { if (a>max) max=a; if(a<min) min=a; }
[15:20] <Quintasan> hmm
[15:20] <Quintasan> Did not think of that
[15:20] <apachelogger> oh, the min check can go
[15:20] <apachelogger> then you are definitely at two comparisions in a flow chart
[15:21] <Quintasan> yeah, makes sense
[15:21] <yofel__> what's wrong with flow charts? They're a lot easier to write than the nassi-schneidermann stuff we did in school
[15:22] <Quintasan> I hate it
[15:22] <apachelogger> also algorithmic speaking it probably cannot be done, that is to say I know no algorithm that would find the highest of 4 in n/2 steps
[15:22] <apachelogger> not reliably anyway
[15:23] <apachelogger> i.e. with a useful initial seed ordering you'd get there with some
[15:23] <Quintasan> I could write a function to check is year n is a leap year in two lines
[15:23] <Quintasan> but prof wanted a flow chart that took the whole blackbord
[15:24] <apachelogger> well writing the codez and understanding what it means are two different things :P
[15:25] <shadeslayer> apachelogger: debian upstream says that they'd add it in their kde-*-desktop meta packages
[15:25] <shadeslayer> so we should just go ahead and add it to the seeds I guess
[15:25] <apachelogger> we should fix it properly
[15:25] <shadeslayer> upstream is being ... upstream
[15:26] <Quintasan> apachelogger: implying if ((year%4==0 && year%100!=0) || year%400==0) is hard to understand
[15:26] <apachelogger> I do not see why an ubuntu user installing the amarok package should get shitty experience
[15:26] <apachelogger> Quintasan: that is even hard to read :P
[15:29] <Quintasan> apachelogger: lol
[15:29] <Quintasan> You must have been doing python
[15:31] <shadeslayer> oh oh
[15:32] <shadeslayer> apachelogger: amarok recommends media-player-infoxs
[15:32] <yofel__> xs?
[15:32] <shadeslayer> virtual package, not sure what provides it
[15:33] <yofel__> oh right, someone please fix apt-cache's handling of virtual packages *-.-
[15:33] <shadeslayer> yeah :P
[15:33] <apachelogger> Quintasan: well
[15:33] <apachelogger> Quintasan: try writing that in x86 asm
[15:35] <apachelogger> shadeslayer: so the solution is to have every consumer of libsolid depend on that? Oo
[15:35] <yofel__> shadeslayer: if I remember the syntax of apt-cache depends right, then nothing provides xs, as it's in <>
[15:36] <shadeslayer> yeah, seeing how I can't find anything remotely realted to it, it seems we have a packaging issue :P
[15:36] <shadeslayer> apachelogger: *shrug*
[15:36] <apachelogger> exactly
[15:36] <shadeslayer> that's what upstream feels ....
[15:37] <yofel__> aptitude agrees: --- media-player-infoxs (UNAVAILABLE)
[15:37] <apachelogger> upstream feels that libsolid should be working :P
[15:37] <yofel__> so start by fixing amarok
[15:38] <apachelogger> what is xs?
[15:38] <apachelogger> it's called -info really
[15:38] <apachelogger> ah lol
[15:38] <shadeslayer> yeah
[15:38] <shadeslayer> like I said, some sort of packaging issue I guess
[15:39] <apachelogger> to the history
[15:39] <apachelogger> hm
[15:39] <apachelogger> I don't see it in the branch Oo
[15:39]  * apachelogger blind?
[15:40] <shadeslayer> +Recommends: kdemultimedia-kio-plugins (>= 4:4.2.0), media-player-infoxs
[15:40] <shadeslayer> http://launchpadlibrarian.net/112693094/amarok_2%3A2.6~rc1-0ubuntu2_2%3A2.6.0-0ubuntu1.diff.gz
[15:40] <apachelogger> yah
[15:40] <apachelogger> typos ftw
[15:40] <shadeslayer> possibly Riddell spelled it wrong?
[15:40] <apachelogger> also that is not in bzr
[15:40] <shadeslayer> heh
[15:40] <shadeslayer> what a surprise
[15:41] <apachelogger> last version in bzr is rc1 -.-
[15:41] <apachelogger> so at least two uploads that are not in bzr
[15:41] <apachelogger> so I get one, I do not get the second though
[15:41] <apachelogger> Oo
[15:42] <Riddell> moi?
[15:42] <apachelogger> yes, you again :P
[15:42] <apachelogger> someone please fix it, I need coffees
[15:43] <Riddell> mm, that looks broken indeed
[15:43] <shadeslayer> doing
[15:43] <apachelogger> by fix I mean fix the bzr
[15:43] <Riddell> sorry about that
[15:43] <shadeslayer> well ... doing both :P
[15:43] <apachelogger> the actual fix is to promote that thing from suggests to recommends on libsolid
[15:48] <shadeslayer> also SRU it?
[15:50] <Riddell> shadeslayer: yep
[15:51] <Riddell> shadeslayer: I'm processing e-mail and come across the "please package kdevelop xdebug" one again, did you respond at all?
[15:51] <shadeslayer> I have no idea what that is tbh
[15:52] <shadeslayer> and I forgot about it as well
[15:53] <shadeslayer> http://download.kde.org/unstable/kdevelop/kdev-xdebug/1.3.80/src/
[15:53] <shadeslayer> hmm
[15:53] <yofel__> seems to be http://nikosams.blogspot.de/2012/10/kdevelop-xdebug-php-debugger-beta.html if you want some more details
[15:53] <Riddell> there may well be a reason why it's not packaged
[15:53] <Riddell> I think I'll add a work item to investigate
[15:54] <shadeslayer> could you follow up on that? I have too much on my plate right now :)
[15:54] <Riddell> yep
[15:58] <shadeslayer> Riddell: there's a bunch of stuff to be packaged : http://download.kde.org/unstable/kdevelop/
[15:58] <shadeslayer> at the very end
[15:59] <Riddell> hmm, interesting
[16:02] <shadeslayer> Riddell: bug 1078772 filed
[16:03] <shadeslayer> can I go ahead and upload to quantal-proposed ?
[16:04] <Riddell> shadeslayer: yes but please add diff to the bug and subscribe ~ubuntu-sru
[16:05] <shadeslayer> righto
[16:05] <Riddell> Quintasan: word is there's a homerun release on download.kde.org, you're down for the work item to package it (if you can't do it soon mind and say so to release the lock)
[16:11] <ScottK> Riddell: I think you covered it on #u-release.  We have the milestones in the bug tracker now.
[16:19] <shadeslayer> Riddell: https://launchpadlibrarian.net/123020597/amarok.debdiff
[16:21] <shadeslayer> uploaded to proposed, pending approval
[16:24] <yofel__> btw. now that we do the automated upload stuff, does someone still use the dep-graph? I can generate the 4.10 one from neon, bug I'm wondering if it's worth the trouble (it's more than one or 2 changes)
[16:24] <yofel__> *but
[16:28] <Riddell> yofel__: if it's hassle then I think leave it and see if anyone complains
[16:29] <Riddell> folks skaet is wondering when we want an alpha 1 since we're probably the only flavour using it
[16:29] <Riddell> https://wiki.kubuntu.org/RaringRingtail/ReleaseSchedule current december 6th
[16:29] <yofel__> well, 40 new items for kdegames, kactivities gets used by more things, nepomuk-widgets it new, and so on
[16:30] <Riddell> could be moved to january to pick up any work over the holidays
[16:30] <apachelogger> Riddell: we are the only flavor using alphas?
[16:31] <Riddell> apachelogger: some want 1 alpha
[16:31] <apachelogger> ah
[16:31] <apachelogger> well, IMHO january would be better
[16:31] <apachelogger> seeing as we probably won't have much to test by dec 6
[16:31] <Riddell>
[16:32] <Riddell> January 10th then to catch KDE SC RC?
[16:32] <yofel__> ack, we'll need at least 2 weeks for just KDE judging from our packaging speed lately
[16:32] <yofel__> fine with me
[16:32] <apachelogger> oh sec
[16:32] <apachelogger> .10 b1 is out nov 21
[16:33] <apachelogger> yofel__: should be enough time to get it in?
[16:34] <yofel__> should be, we could just concentrate on the core stuff for beta1, and kdegames for beta2 or so
[16:34] <yofel__> then we won't have thing lying around in a half-done state
[16:34] <yofel__> *things
[16:34] <apachelogger> works for me
[16:34] <apachelogger> Riddell: dec 6 it is
[16:34] <apachelogger> yofel__: we should just make sure the base system works
[16:34] <yofel__> yeah
[16:35] <apachelogger> so we can point people at go download a1 and you'll get over the air upgrades to .10 pre-releases
[16:35] <yofel__> hm, that would be an idea too
[16:36] <Riddell> mm, I'm not sure pointing people at an alpha is a good way to recommend upgrading to KDE SC 4.10
[16:37] <apachelogger> pre-releases
[16:37] <apachelogger> to test .10
[16:37] <yofel__> it's not like we'll backport .10 until we have it fully packaged, which certainly won't happen for b1
[16:38] <apachelogger> actually it may be best to only start backports with rc1
[16:39] <apachelogger> by that time the sources should have settled enough to not cause major packaging changes between rc1 and final
[16:39] <yofel__> right
[16:41] <Riddell> Darkwing: ping?  I need your address
[16:41] <yofel__> so plan would be to package .10 b1 without kdegames, b2 with, and start backports with rc1 - fine?
[16:42] <Riddell> and alpha 1 after 4.10 b1 & alpha 2 after 4.10 final?
[16:43] <yofel__> ack
[16:43] <ScottK> IIRC from the schedule meeting, where things were before seemed to make sense.
[16:43] <yofel__> .10 b1 tagging is officially tomorrow, so we should have the sources by the end of the week
[16:46] <Riddell> skaet: we'll try and stick with alpha 1 where it is, dec 6th then
[16:46] <skaet> Riddell,  ok
[16:58] <shadeslayer> hmmm ... where's the amarok I uploaded to -proposed
[16:58] <shadeslayer> Riddell: do you see it in the queue?
[16:59] <shadeslayer> because I don't : https://launchpad.net/ubuntu/quantal/+queue
[16:59] <shadeslayer> oh wait, it's in unapproved
[16:59] <Riddell> shadeslayer: yes, in https://launchpad.net/ubuntu/quantal/+queue?queue_state=1&queue_text=
[16:59] <shadeslayer> right
[17:01]  * shadeslayer is still waiting to be included in the steam beat
[17:01] <shadeslayer> *beta
[17:02] <Riddell> for all the hype about steam at UDS, nobody actually explained what it is
[17:02] <Riddell> I know it's a game engine but I don't know anything more about it, probably if you play games you already know and if you don't you don't care
[17:02] <shadeslayer> steam is a content distribution engine
[17:03] <shadeslayer> then there's the source engine
[17:03] <shadeslayer> which is the thing that powers games like TF2
[17:03] <shadeslayer> which is all I care about at the moment ;P
[17:07] <Riddell> TF2?  I never even knew there was a TF1, I'm so behind, do they still play sonic the hedgehog?
[17:08] <shadeslayer> lol
[17:08] <shadeslayer> Riddell: http://en.wikipedia.org/wiki/Team_Fortress
[17:09]  * yofel__ never played TF2 so far either, only watched videos of it
[17:10] <shadeslayer> I've played for a couple of hours, but then OS X got annoying
[17:11] <yofel__> heh, here my only win7 system doesn't have 10G free disk space :P
[17:11] <shadeslayer> haha
[17:13] <apachelogger> my win8 has 1.5 gib of free space
[17:13] <shadeslayer> I have 0 GB's of space for win
[17:14] <shadeslayer> -dows that is :P
[17:14] <apachelogger> delete some pleasure movies
[17:14] <shadeslayer> pft, stream all the pleasure movies
[17:15] <apachelogger> bad idea
[17:15] <apachelogger> see, the internet is a series of tubes and if you put too much into it they get blocked and nothing gets thru anymore
[17:33] <ScottK> Digestion works that way too, once you get older.
[17:34] <apachelogger> :S
[17:34] <apachelogger> Oo
[17:34] <apachelogger> :O
[17:34]  * apachelogger leaves now
[17:35] <shadeslayer> haha
[17:36] <ScottK> Riddell: amarok SRU is accepted.
[17:36] <ScottK> shadeslayer: ^^^
[17:36] <shadeslayer> thx
[17:36] <ScottK> np
[18:00] <Riddell> ScottK: ah yes I was forgetting your elite new SRU powers
[18:01] <Riddell> ScottK: you should probably fix up my lack of SRU powers on bug 1067611, sorry about that
[18:03] <Tygart> quick question, no one is on the help forum
[18:03] <Tygart> I am using 13.03 During an sudo apt-get update / dist-upgrade the notification keeps saying Activity in session "Shell"  is something trying to SSH into my computer?
[18:04] <Tygart> 13.04*
[18:05] <Riddell> Tygart: no that means there's some visible activity, ssh wouldn't be visible
[18:05] <Tygart> Ok thank you. I haven't seen that message before.
[18:13] <shadeslayer> ooohh
[18:13] <shadeslayer> skanlite works over wifi just fine
[18:13] <Riddell> shadeslayer: ssh -X ?
[18:13] <Riddell> or networked scanner?
[18:14] <shadeslayer> the latter
[18:14] <shadeslayer> networked scanner + printer
[18:14] <Riddell> cool, good to know since I didn't actually test it
[18:14] <shadeslayer> and I'm on precise ....
[18:17] <shadeslayer> want me to test the new printer thingum as well?
[18:19] <Riddell> shadeslayer: mm, there is no new printer thingum on precise
[18:19] <shadeslayer> I have a quantal ISO, could virtualize and see
[18:20] <Riddell> go for it
[18:23] <shadeslayer> The last time I tried printing in my college ubuntu proceeded to print a 100 test pages
[18:29] <yofel__> never happened for me, and I've been using network printers since gutsy - depends on the driver though. My dad's canon printer refuses to print anything
[18:30] <shadeslayer> can't find the networked printer
[18:31] <shadeslayer> ah well
[18:31] <shadeslayer> the old printer app does find it
[18:31] <Riddell> hum
[18:33] <shadeslayer> as does cups
[18:33] <Riddell> hum
[18:33] <shadeslayer> http://wstaw.org/m/2012/11/14/plasma-desktopsG7451.png
[18:33] <shadeslayer> possibly just due to KVM?
[18:35] <apachelogger> shadeslayer: kdebug is your friend
[18:45]  * yofel__ makes his way home - bbl
[18:46] <Riddell> shadeslayer: well if cups sees it then print-manager should see it
[18:50] <shadeslayer> any ideas what the username/pass is on the live cd?
[18:50] <apachelogger> kubuntu kubuntu most likely
[18:51] <shadeslayer> doesn't work
[18:53] <shadeslayer> apachelogger: kdebug doesn't show any issues
[18:53] <shadeslayer> *kdebug output
[19:13] <Quintasan> Riddell: Will get to it today
[20:32] <Quintasan> yofel_: how do I do bot bugfilling magic?
[20:32] <yofel_> ~help newpackage
[20:32] <kubotu> newpackage <packagename> <version> [description]; Adds needs-packaging bug for entirely new package.
[20:32] <kubotu> newversion <packagename> <version> [description]; Adds update bug for existing package.
[20:32] <Quintasan> kubotu: newpackage homerun 0.1.0 Homerun needs packaging
[20:32] <kubotu> Package homerun already exists!
[20:32] <yofel_> no need to put something like "needs packaging" in the description
[20:33] <yofel_> that's already there
[20:33] <yofel_> it's meant for additional info like url to source etc.
[20:33] <Quintasan> durr
[20:33] <Quintasan> cant find bug for homerun packaging
[20:34] <yofel_> hm... that error should mean that there is already a source called 'homerun' in ubuntu
[20:35] <yofel_> Quintasan: have you ever seen an empty package history o.O? https://launchpad.net/ubuntu/+source/homerun
[20:35] <yofel_> first time for me...
[20:35] <Quintasan> http://packages.ubuntu.com/search?keywords=homerun&searchon=names
[20:35] <Quintasan> nothing
[20:35] <Quintasan> xD
[20:35] <yofel_> yeah, but for some reason it's in the LP Database, that's all the script can check...
[20:36] <yofel_> the publishing history is empty too, wtf
[20:36] <Quintasan> and can't report bug against it
[20:38] <yofel_> kubotu: newversion homerun 0.1.0
[20:38] <kubotu> HTTPError: Package homerun not published in Ubuntu
[20:38] <yofel_> . . .
[20:38] <yofel_> -> #launchpad, this is broken
[20:38] <tsimpson> yofel_: I think that happens when someone uploads something to a PPA but it never existed in ubuntu
[20:39] <yofel_> hm
[20:39] <tsimpson> eg: https://launchpad.net/ubuntu/+source/ferite1.0
[20:39] <tsimpson> I uploaded that to my PPA a long time ago, and it shows under "Other versions of ..."
[20:39] <yofel_> true, seems so
[20:39] <tsimpson> LP is a strange beast
[20:40] <yofel_> guess I'll need to add a publishing check to the script
[20:49] <Quintasan> agateau: THIS LICENSING ON HOMERUN
[20:49] <Quintasan> T_T
[20:49]  * Quintasan sheds tears
[20:49] <yofel_> what's the problem?
[20:50] <Quintasan> three licenses
[20:50] <Quintasan> plus BSD
[20:50] <yofel> sounds normal
[20:53] <Tm_T> 3+1 but only today!
[20:53]  * Tm_T goes salesman mode
[20:53] <ScottK> shadeslayer: I think usename/password on the live CD is ubuntu/none.
[21:07]  * yofel gives up on fixing the script
[21:07] <yofel> the API makes it really hard to catch that case
[21:11] <yofel> hm
[21:12] <yofel> found a way after all
[21:12] <yofel> if number of published sources in the main archive for exact matched package name "homerun" = 0 -> package not yet in archive
[21:13] <Quintasan> OH MY GOD
[21:13] <Quintasan> hahahahahahahahahahahhaaha\
[21:14] <yofel> I'm open for alternatives...
[21:14] <Quintasan> no
[21:14] <Quintasan> You're not
[21:14] <Quintasan> THIS COPYRIGHT
[21:14] <Quintasan> AHAAHAHA
[21:14] <yofel> uh...
[21:14] <Quintasan> THAT'S WHY I HATE PACKAGING
[21:14] <yofel> have you ever read the copyright of calligra?
[21:15] <yofel> (which is invalid btw.)
[21:15] <Quintasan> NOPE
[21:15] <Quintasan> DONT CARE
[21:15] <yofel> :D
[21:15] <Quintasan> I already cringe when I see thing licensed on GPL-2 or GPL-3 (at your choice)
[21:15] <Quintasan> xD
[21:17] <Quintasan> AND WHY THERE IS NO SOUND IN FLASH
[21:17] <yofel> blame your system
[21:18] <Quintasan> kmod:nvidia_current_updates - nvidia_current_updates (Proprietary, Enabled, Not in use)
[21:18] <Quintasan> >Not in use
[21:18] <Quintasan> what the hell
[21:19] <Quintasan> I blame this retarded abstraction layer called Phonon or PulseAudio
[21:19] <Quintasan> depending which one is at fault
[21:20] <yofel> Quintasan: bug 1078908
[21:21] <Quintasan> I fileed that
[21:21] <Quintasan> filled
[21:21] <yofel> so you did, duped
[21:22] <yofel> but now the script works at least
[21:23] <yofel> Quintasan: enjoy :P http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-dev-tools/trunk/revision/161
[21:23] <yofel> line 55 is esp. fun
[21:24] <yofel> worst thing is that this crap actually works right -.-
[21:24] <Quintasan> but still
[21:24] <Quintasan> >Not in use
[21:24] <Quintasan> kmod:nvidia_current_updates - nvidia_current_updates (Proprietary, Enabled, Not in use)
[21:24] <Quintasan> hahahahaha
[21:24] <yofel> apachelogger: can you update the script for kubotu please?
[21:25] <Quintasan> This line makes me wonder why I'm still using linux
[21:25] <yofel> well, what are you running?
[21:25]  * yofel hasn't used jockey in ages btw.
[21:25] <Quintasan> yofel: NO IDEA?
[21:25] <Quintasan> :D
[21:25] <Quintasan> That's the thing
[21:25] <yofel> check your x log, that will tell
[21:26] <Quintasan> nvidia
[21:27] <yofel> ah well, same here
[21:27] <yofel> kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use)
[21:27] <Quintasan> apparently that's the module loaded
[21:27] <Quintasan> and the screen compositing is not smooth T_T
[21:27] <Quintasan> I feel like an idiot running GTX570 and composition is not as smooth as my friends 2 years old laptop with some mobile version
[21:28] <Quintasan> and the damn homerun fails at tests
[21:28] <Quintasan> way to god
[21:28] <Quintasan> go*
[21:29] <yofel> well, in a day or two we'll have 4.10, then you can go back to everyday's insanity
[21:29] <Quintasan> which is?
[21:29] <Quintasan> packaging?
[21:29] <yofel> yep
[21:29]  * yofel wonders if the debian folks fixed qjson yet
[21:29] <Quintasan> I just want my os to use my gfx card normally
[21:31] <Quintasan> agateau: We have to skip tests for homerun for now
[21:31] <Quintasan> they don't work with xvfb or I'm being stupid
[21:31] <Quintasan> The latter is probably true
[21:31]  * yofel reboots
[21:32] <yofel> brb - probably
[21:33] <yofel> re
[21:39] <Quintasan> I'm so not going to do this copyright today
[21:39]  * Quintasan sipts
[21:39] <Quintasan> skips*
[21:39] <apachelogger> yofel: which one?
[21:39] <yofel> newpackage (kubuntu-dev-tools)
[21:40] <apachelogger> what's broken?
[21:40] <yofel> kubotu: newpackage homerun 0.1.0
[21:40] <kubotu> Package homerun already exists!
[21:40] <yofel> kubotu: newversion homerun 0.1.0
[21:40] <kubotu> HTTPError: Package homerun not published in Ubuntu
[21:41] <yofel> homerun exists, but without a published version as it only exists in PPA's
[21:41] <yofel> apachelogger: http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-dev-tools/trunk/revision/161 works, feel free to look over it
[21:48] <Quintasan> ...
[21:48] <Quintasan> how the
[21:49] <Quintasan> apachelogger: usr/lib/libhomerun.so
[21:49] <Quintasan> usr/lib/libhomerun.so.0
[21:49] <Quintasan> usr/lib/libhomerun.so.0.0.0
[21:49] <Quintasan> The first two should go to dev package
[21:49] <Quintasan> shouldn't they?
[21:50] <yofel> the first
[21:50] <Quintasan> oh
[21:50] <yofel> the others go into libhomerun0
[21:50] <Quintasan> explains the rpath magic
[21:51]  * Quintasan has long forgotten the magics of library packaging
[21:52] <Quintasan> yofel: usr/bin/homerunviewer
[21:52] <Quintasan> any idea?
[21:52] <Quintasan> devel pacakge
[21:52] <Quintasan> lib package or the widget one?
[21:52] <yofel> uh, I have no idea what that thing does so don't ask me
[21:53] <Quintasan> agateau: usr/bin/homerunviewer <-- to which package should it belong?
[21:53] <yofel> if it's only useful for devel then put it into -dev, otherwise make a bin package for the executabled
[21:53] <yofel> s
[21:53]  * Quintasan puts it in dev for time being
[21:53] <Quintasan> those are funny
[21:53] <Quintasan> usr/lib/kde4/imports/org/kde/homerun/components/libcomponentsplugin.so
[21:53] <Quintasan> usr/lib/kde4/imports/org/kde/homerun/fixes/libfixesplugin.so
[21:53] <Quintasan> usr/lib/kde4/homerun_source_recentdocuments.so
[21:53]  * Quintasan puts them into widget package
[21:58] <Quintasan> done for today
[21:58] <Quintasan> will do copyright tomorrow and ask someone to review before I upload
[21:58]  * Quintasan feels a little bit rusty
[22:16] <apachelogger> Quintasan, yofel: well, the overly precise library expert would argue that stuff should link against x.x.x rather than x.x ;)
[22:16]  * yofel never said a thing about linking
[22:47] <Riddell> shadeslayer: live cd username is kubuntu and password is empty
[22:47] <shadeslayer> didn't work when I tried it ...
[22:50] <tsimpson> isn't the live cd username "ubuntu"?
[22:52] <Riddell> tsimpson: that got changed recently
[22:53] <tsimpson> finally :)
[22:54] <Riddell> Quintasan: there is daily build packaging for homerun in ~cyberspace which you can base it on
[23:54] <shadeslayer> I don't think the blue-shell packaging had proper copyright, though I might be wrong
[23:55] <shadeslayer> interesting, we do, but .... I don't think that's right .... :P


[02:59] <Kentrel> Hey, I'm getting a little lag with my midi keyboard, rose garden and timidity for playback
[03:01] <holstein> Kentrel: hey
[03:01] <holstein> are you using JACK?
[03:02] <Kentrel> no
[03:02] <holstein> are you using a real time kernel?
[03:03] <Kentrel> no
[03:03] <holstein> theres a couple things that i would suggest
[03:03] <holstein> you can run sudo apt-get install linux-rt
[03:03] <holstein> and if your on karmic or lucid
[03:03] <holstein> check out
[03:03] <Kentrel> Jack isn't suitable for me, since I only work with timidity, but I have wondered if its my kernel
[03:03] <holstein> !grub2
[03:04] <holstein> that might be enough
[03:04] <Kentrel> ok, i'll try that now
[03:04] <holstein> JACK is really awesome though
[03:04] <holstein> i cant imagine what functionality you would miss using it
[03:04] <holstein> BUT
[03:04] <holstein> im not a big MIDI guy
[03:04] <Kentrel> dunno
[03:05] <Kentrel> Rose garden has crashed like 10 times tonight when I've used jack
[03:05] <holstein> interesting
[03:05] <Kentrel> I can never get anything working the way I want it. Midi is simpler for me, since I just want to practice playing
[03:05] <holstein> what are your settings like?
[03:05] <holstein> your latency?
[03:05] <holstein> maybe your pushing it too hard
[03:05] <Kentrel> I've played with all the settings
[03:05] <Kentrel> lol
[03:05] <holstein> hmmm
[03:05] <Kentrel> maybe...
[03:06] <Kentrel> I don't know. I don't care anymore. All I need now is just to be able to play and record midi
[03:06] <holstein> Kentrel: there are some MIDI friendly guys in #opensourcemusicians
[03:06] <holstein> might have better ideas than i have
[03:06] <Kentrel> I'll check it out sometime, thanks
[03:06] <holstein> wont hurt anything to install the RT kernel though
[03:07] <holstein> you can set grub to not-hide
[03:07] <holstein> and select between them at boot if you prefer
[03:07] <holstein> the RT and generic
[03:08]  * holstein just started messing with xsynth-dssi
[03:08] <holstein> and whysynth-dssi
[09:27] <tjingboem> is there a soundfont editor that works with 10.04?
[10:07] <lorenzosu> hi tjingboem the only soundfont editor (for linux) I know of is swami, but never really managed to get it to work
[10:10] <tjingboem> lorenzosu, hello. yes, i tried to build it but it failed. maybe i'll make request for it
[10:11] <lorenzosu> tjingboem, I see. afaik it's the only soundfont editor around, but I'm not sure how much alive it is.. Another way if you're in desperate need is to get some windows one working with wine
[10:12] <tjingboem> if i have a use a windows program i will use windows for it, not wine :)
[10:13] <tjingboem> maybe it is the way to get swami back to life
[10:13] <tjingboem> when there are not too many prorams being "wined"
[10:14] <tjingboem> i got the latest source code from swami and the latest changelog says: 2006-06-01  Josh Green
[10:15] <tjingboem> pretty dead i would say
[10:15] <tjingboem> Swami 0.9.4 release
[15:12] <Whammo> hi I have a question about power, irq bottlenecks, laptops, and latency
[15:13] <Whammo> ACPI and APIC... which one of these do I turn off?
[20:35] <makerprofaze> I'm surprised it always seems so quiet here. Is everyone off making sound?
[20:35] <acerimmer_> ping
[20:36]  * holstein off to get some food
[20:36] <holstein> then off to make sound later :)
[20:38] <makerprofaze> I've got 2 questions. anybody here use/used freecycle?
[23:26] <IngForigua> Hi every one
[23:27] <IngForigua> someone know, how to play midi format


[00:36] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.20 => 2.02~beta2-36ubuntu3.21] (core)
[05:24] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (trusty-proposed/main) [2.208.16 => 2.208.17] (desktop-core)
[06:11] <tjaalton> any archive admin still around? linux-signed-oem is in bionic NEW and blocking testing
[06:12] <tjaalton> still/already
[06:13] <tjaalton> vorlon, infinity: you're probably only ones that might be still awake :)
[06:48] <RAOF> infinity: The thought occurs that we didn't go over accepting from binary-NEW in the archive admin training... 😁
[07:03] <RAOF> The packages tjaalton is talking about look like they're destined for the correct pockets, and lintian is reasonably happy with them. I think they're correct to accept, and I think that pushing the button on LP would do the right thing. (and presumably `queue accept`, too).
[07:03] <RAOF> So, I would accept them; but I won't do that until you tell me that there isn't a necessary check I've missed.
[07:33] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1035.40]
[07:33] <infinity> RAOF: Oh, I caught a ping in another channel and sorted it.
[07:34] <infinity> RAOF: We should talk binary NEW at some point, yeah, but for kernel stuff, "people who do kernel stuff are meant to handle it" is the rule of thumb.
[07:34] <infinity> Looks like Lukasz just missed a step.
[07:35] <tjaalton> right
[08:59] -queuebot:#ubuntu-release- Unapproved: dpdk (bionic-proposed/main) [17.11.3-3~ubuntu0.18.04 => 17.11.5-0~ubuntu18.04.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[08:59] -queuebot:#ubuntu-release- Unapproved: dpdk (cosmic-proposed/main) [17.11.3-3 => 17.11.5-0~ubuntu18.10.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[11:18] <LocutusOfBorg> can anybody please kick them out?
[11:18] <LocutusOfBorg> missing build on arm64: libceres-dev, libceres1 (from 1.13.0+dfsg0-2build1)
[11:18] <LocutusOfBorg> missing build on ppc64el: libceres-dev, libceres1 (from 1.13.0+dfsg0-2build1)
[11:18] <LocutusOfBorg> (probably colmap on ppc64el has to go too)
[11:19] <LocutusOfBorg> debian already removed, not sure why nobody picked them up yet :)
[11:25] <LocutusOfBorg> apw, maybe I can abuse of your time? I'm really trying to let something migrate from the proposed pocket
[11:26] <LocutusOfBorg> I made a script that looks for stuff in proposed that has a new version in debian unstable, and I'm manually syncing what is fixed in Debian
[11:26] -queuebot:#ubuntu-release- New binary: ruby-chromedriver-helper [amd64] (disco-proposed/universe) [2.1.0-6ubuntu2] (no packageset)
[11:35] <LocutusOfBorg> this one should unblock lots of ruby proposed packages ^^
[11:35] <LocutusOfBorg> not sure why it fails testsuite on pbuilder, and not on sbuild, some network restriction, there is an associated debian RC bug
[11:36] <LocutusOfBorg> also, please remove freecad on armhf, already removed by debian
[11:53] <LocutusOfBorg> also please bump debci hint to 2.0
[14:59] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [4.18.0-1014.14~18.04.1] (kernel)
[15:48] -queuebot:#ubuntu-release- Unapproved: geogebra (bionic-proposed/universe) [<IP_ADDRESS>+dfsg1-4 => <IP_ADDRESS>+dfsg1-6~18.04.1] (no packageset) (sync)
[16:00] -queuebot:#ubuntu-release- Unapproved: accepted geogebra [sync] (bionic-proposed) [<IP_ADDRESS>+dfsg1-6~18.04.1]
[16:30] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (trusty-proposed/main) [4.15.0-1041.45~14.04.1] (kernel)
[16:32] -queuebot:#ubuntu-release- New source: linux-restricted-modules (disco-proposed/primary) [5.0.0-8.9]
[16:33] <apw> vorlon, ^ you are likley the most aware of that one
[16:33] <oSoMoN> dear release team: I'm considering adding gstreamer1.0-gtk3 as a recommends of libreoffice-avmedia-backend-gstreamer to fix bug #1820062. libreoffice-avmedia-backend-gstreamer is in main, whereas gstreamer1.0-gtk3 is in universe, but its source package itself is in main (gst-plugins-good1.0). Is that acceptable, and would that require a FFe? (seb_128 suggested it would)
[16:39] <jamespage> bdmurray: hey - I revisited the testing of bug 1813807 - we had a bit of a test misconfiguration in terms of user setup which I've corrected
[16:40] <jamespage> unrelated to the packages actually being SRU's but now resolved more generally
[16:41] <bdmurray> jamespage: cool, I'll have a look
[19:26] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.18.0-1014.14~18.04.1]
[19:26] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (cosmic-proposed) [4.18.0-1008.9]
[19:26] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1041.45]
[19:26] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (cosmic-proposed) [4.18.0-1014.14]
[19:26] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (trusty-proposed) [4.15.0-1041.45~14.04.1]
[19:34] -queuebot:#ubuntu-release- Unapproved: accepted resolvconf [source] (cosmic-proposed) [1.79ubuntu<IP_ADDRESS>]
[19:36] -queuebot:#ubuntu-release- Unapproved: accepted resolvconf [source] (bionic-proposed) [1.79ubuntu<IP_ADDRESS>]
[23:52] -queuebot:#ubuntu-release- New: rejected intel-mediasdk [source] (disco-proposed) [18.4.1-0ubuntu1]


[15:22] <dipankar_> dfarning, I am here
[15:24] <dfarning> dipankar_, Can you describe the problem so that when lfaraone comes online he can help us?
[15:25] <dipankar_> hi lfaraone,
[15:26] <dipankar_> lfaraone, there is a sugar start-up problem
[15:27] <dipankar_> lfaraone: we narrowed down to the presence-service package
[15:28] <dipankar_> when I am trying to run the command 'sugar-presence-service'
[15:28] <dipankar_> I get the following:
[15:28] <dipankar_> The program 'sugar-presence-service' is currently not installed.  You can install it by typing:
[15:28] <dipankar_> sudo apt-get install sugar-presence-service-0.88
[15:28] <dipankar_> But when I try to install it:
[15:28] <dipankar_> I get:
[15:29] <dipankar_> Reading package lists... Done
[15:29] <dipankar_> Building dependency tree
[15:29] <dipankar_> Reading state information... Done
[15:29] <dipankar_> sugar-presence-service-0.88 is already the newest version.
[15:29] <dipankar_> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[15:29] <dfarning> dipankar_, hmmm it looks like the package is empty.
[15:30] <dfarning> dipankar_, try going into synaptic and looking at the files in sugar-presence-service
[15:32] <dfarning> I sure there is a command line way of determining this information.... but I can never remember the incantation.
[15:33] <dipankar_> dfarning, I checked the status in the synaptic package manager
[15:33] <dipankar_> I found the following in the installed files:
[15:33] <dipankar_> /usr/share
[15:33] <dipankar_> /usr/share/doc
[15:33] <dipankar_> /usr/share/doc/sugar-presence-service-0.88
[15:34] <dipankar_> /usr/share/doc/sugar-presence-service-0.88/NEWS.gz
[15:34] <dipankar_> /usr/share/doc/sugar-presence-service-0.88/buildinfo.gz
[15:34] <dipankar_> /usr/share/doc/sugar-presence-service-0.88/changelog.Debian.gz
[15:34] <dipankar_> /usr/share/doc/sugar-presence-service-0.88/copyright
[15:34] <dfarning> dipankar_, yes that is the documetation stuff.  all the python seems to be missing.
[15:35] <dfarning> dipankar_, let's try taking a closer look at the build logs on launchpad
[15:35] <dipankar_> dfarning,
[15:35] <dipankar_> dfarning, ok
[15:37] <dipankar_> dfarning, I am at the build page of sugar-ppa
[15:37] <dfarning> can you cut and past a link
[15:39] <dipankar> dfarning, here is the link : https://launchpad.net/~sugarteam/+archive/ppa/+builds?build_text=&build_state=all
[15:40] <dfarning> ok I have to log off and log back in.   just a minute
[15:40] <dipankar_> dfarning, sure
[15:44] <dfarning> dipankar let's take a look at the build log at https://launchpad.net/~sugarteam/+archive/ppa/+build/1786826
[15:46] <dfarning> dipankar_ I am not exactly sure what the following means:
[15:46] <dfarning> dpkg-deb: building package `sugar-presence-service-0.88' in `../sugar-presence-service-0.88_0.88.1-1_all.deb'.
[15:46] <dfarning>  dpkg-genchanges -b -mUbuntu/i386 Build Daemon<EMAIL_ADDRESS>>../sugar-presence-service-0.88_0.88.1-1_i386.changes
[15:46] <dfarning> dpkg-genchanges: binary-only upload - not including any source code
[15:46] <dfarning> dpkg-buildpackage: binary only upload (no source included)
[15:47] <dfarning> dipankar but it looks like the source code was not included in the upload.
[15:47] <dipankar_> ok dfarning
[15:47] <dipankar_> I got it
[15:47] <dipankar_> Remember the problem that I was facing
[15:47] <dipankar_> dfarning, you told me to remove the original tarball file
[15:47] <dipankar_> while making the package
[15:48] <dipankar_> may be that caused the error
[15:51] <dfarning> dipankar I think I might have gotten the build flags wrong.
[15:51] <dfarning> take a look at https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage
[15:52] <dfarning> dipankar maybe the flags should have been 'debuild -S -sd'
[15:52] <dipankar_> dfarning, I used debuild -S -sa
[15:53] <dfarning> dipankar_ I don't understand the flags very well.
[15:54] <dipankar_> dfarning, me too. But I think you are correct in pointing that
[15:54] <dipankar_> dfarning, I think I should have used the -S -sd flag
[15:56] <dfarning> dipankar_  At thing point, I would just try to rebuild the package and reupload it and see what happens:)
[15:56] <dipankar_> dfarning, I will do that is just a minute
[15:56] <dipankar_> * is  -> in
[16:10] <dipankar> dfarning
[16:10] <dipankar> dfarning, I have made new package of sugar-presence-service
[16:10] <dipankar> dfarning, shall I push it into ppa
[16:10] <dipankar> ?
[16:12] <dfarning> dipankar yes lets see what happens
[16:14] <dipankar> dfarning, done
[16:14] <dipankar> dfarning, pushed the package into ppa
[16:17] <dfarning> dipankar ok lets wait for it to build and check the logs.
[16:17] <dipankar> dfarning, btw Manu Sir told me to consult with you and check the working in launchpad (bug-reporting, bug-removing, etc)
[16:17] <dipankar> I didn't clearly get it though
[16:18] <dipankar> dfarning, can you explain it a bit?
[16:18] <dfarning> dipankar yes, sugar on launchpad is a mess right now:(
[16:19] <dfarning> in general, all bugs againt sugar should be reported to launch pad.
[16:20] <dfarning> that way we will have a record, and the intial bug notice will be sent to the sugarteam mailing list so everyone can scan it and see if it relates to them.
[16:20] <dfarning> hmmmm.
[16:21] <dfarning> dipankar how about if I think this though and sent it to the mailing list so everyone can read it?
[16:24] <dipankar> sure dfarning
[16:33] <dfarning> dipankar looks like the build will start in about 30 minutes.
[16:33] <dipankar> how come such late?
[16:35] <dfarning> dipankar I think the ubuntu build farm is run on an elastic cloud so resource are allocated and deallocated as necessay.  PPA builds are really low in the priority list.
[16:35] <dipankar> dfarning, got it. Lets wait then.
[17:11] <lfaraone> dfarning: sorry, I had a Physics final.
[17:47] <dfarning> lfaraone, how did it go?
[17:51] <dfarning> lfaraone,   when you get a chance can you look at the sugar-presence-service package.  Its only contents are the share/docs/ dir :)
[17:52] <dfarning> lfaraone, I can barly build a package much less debug one:(


[21:10] <MikeRL> Anyone know of any commands to disable power saving on Intel Wireless cards?
[21:11] <MikeRL> I ran some but forgot all of them on 20.04 and issues went away, but after an early upgrade via terminal, the WiFi issues have returned.
[21:11] <MikeRL> Previously, it was narrowed down to power saving.
[21:12] <MikeRL> I ran some but forgot all of them on 20.04 and issues went away, but after an early upgrade via terminal, the WiFi issues have returned.
[21:12] <MikeRL> Oops. Duplicate. What I get for using arrow keys with the terminal. Must've changed focus inadvertently.
[21:13] <oerheks> https://unix.stackexchange.com/a/315400
[21:13] <oerheks> 2): disable powersave
[21:15] <MikeRL> oerheks, Thanks. I will check that file.
[21:15] <MikeRL> Hmm. It's still set to 2.
[21:16] <MikeRL> Dang. It disconnected again. Not good. Might try IRC on my phone if that happens again. Or the Pi.
[21:16] <MikeRL> I ran some other commands as well.
[21:16] <MikeRL> https://ubuntuforums.org/showthread.php?t=2447113
[21:17] <MikeRL> This does the same exact thing you mentioned, I believe.
[21:17] <MikeRL> But I had issues restarting the service via sudo sysctl. Think it's renamed in groovy.
[21:17] <MikeRL> "sudo nmcli networking off" worked though.
[21:18] <MikeRL> Also refollowed this: https://askubuntu.com/questions/1258738/ubuntu-20-04-upgraded-some-network-manager-packages-now-problems-are-ensuing
[21:18] <MikeRL> Country code is US. I can double check the router.
[21:27] <MikeRL> After digging, the channel is 44. Not the default. Worked fine until upgrade.
[21:29] <MikeRL> I'm curious, has anyone else reported WiFi networking issues after upgrading?


[15:03] <maeud> Hi, can anyone help me with a preseed issue, it fails when trying to install the grub bootloader. Here is the partman section of my preseed file: https://pastebin.com/raw/F265bZgw  - The error is: "Volume group sda not found" then next line "Cannot process volume group sda" - I also have in my preseed: "d-i grub-installer/bootdev string /dev/sda1" but that's ignored if I chroot into /target and run parted, I can see /boot is on /d
[15:04] <maeud> ran out of bug reports to read, nothing to go on
[15:12] <TJ-> maeud: looks wrong to me; you're mixing LVM and raw partitioning
[15:13] <maeud> I thought I needed /boot like that as everything else is encrypted TJ-
[15:14] <TJ-> maeud: that's not what I mean; you've done d-i partman-auto-lvm/... so it assumes an LVM layout but then d-i partman-auto/disk string /dev/sda so it expects an LVM VG 'sda'
[15:15] <TJ-> maeud: if you want LVM it needs to be in one or more of the partitions
[15:16] <maeud> from the docs that's meant to be used in conjunction TJ- ?
[15:17] <maeud> that option sets the disk to use (if more than one) then you set the method to use
[15:22] <TJ-> maeud: but for the /boot/ file-system don't you need $lvmignore{ }  ?
[15:22] <maeud> I'll try it TJ- see if that helps
[15:24] <maeud> ok running through now, see in 5 min or so
[15:24] <TJ-> maeud: also, is this creating MBR or GPT? IF GPT there needs to be a BIOS-boot partition for GRUB's core image
[15:25] <maeud> How would I see that TJ- ?
[15:25] <maeud> it should be MBR, how can I confirm?
[15:25] <maeud> 150GB disk
[15:25] <TJ-> maeud: examine the result when it works/fails :)
[15:26] <cryptodan> go into bios and see if efi is enabled and if it is then likely it will be gpt
[15:26] <TJ-> maeud: as in "sudo blkid /dev/sda" should show PTTYPE=
[15:26] <maeud> yeah it's MBR
[15:26] <maeud> I saw msdos disk before
[15:26] <maeud> in parted
[15:27] <maeud> it's a VM cryptodan, but it's MBR
[15:27] <maeud> gen 1 VM in hyper-v
[15:27] <TJ-> maeud: OK, so grub-install will write the core.image to the spare sectors from #1 to just before the start of partition #1
[15:28] <maeud> OK, it's working through the install, see in a min
[15:33] <maeud> no luck TJ-, it's still giving me the same error: "Volume group "sda" not found"
[15:41] <TJ-> maeud: so you need to capture debug logging, plus examine what has been created on disk, to figure out how it differs from your intention.
[15:44] <TJ-> I presume you're expecting sda1{ext4} sda2{LUKS->LVM}
[15:45] <maeud> pretty much, sda1 /boot, sda5 crypt
[15:45] <TJ-> sda5 implies an extended partition
[15:46] <TJ-> presumably partman creates that by default no matter how many partitions you configure
[15:48] <maeud> TJ-: https://imgur.com/a/yNmeHZl
[15:48] <maeud> does that look right?
[15:54] <TJ-> maeud: not really much use; use "lsblk /dev/sda"
[16:06] <maeud> lsblk doesn't exist in target TJ-
[16:06] <maeud> sorry, it does exist but can't read
[16:06] <maeud> it doesn't exist outside of target but if I copy it from target it doesn't have access to libs, sec
[16:09] <maeud> TJ-:  here's lsblk of /dev/sda: https://i.imgur.com/gvrklAB.png
[16:10] <TJ-> maeud: so the disk layout is correct; therefore there must be something affecting the LVM VG name for it to decide on 'sda'! does "sda" exist anywhere else in the preseed file?
[16:12] <maeud> just "d-i partman-auto/disk string /dev/sda
[16:12] <maeud> "
[16:16] <maeud> If I comment that line out TJ- it prompts for me to select partitioning method, then if I select manual, it says no root file system defined
[16:17] <TJ-> maeud: then there's something else going on your preseed file. If I were you I'd test it in a virtual machine to make investigation/examination easier
[16:18] <maeud> I am testing in a VM
[16:18] <maeud> sec let me post it
[16:21] <maeud> TJ-: https://pastebin.com/raw/6f3Anx4f
[16:21] <maeud> nothing else referencing it
[16:25] <TJ-> maeud: if it's a VM then you chroot mount the install and look at the debian-installer/partman  log files
[16:25] <maeud> I can't complete the install, do you mean in the vt?
[16:27] <maeud>  /var/log/partman
[16:27] <maeud> I'll look there
[16:27] <TJ-> You're using a VM to test, so you can shut down the VM, and chroot-mount the disk-images
[16:31] <TJ-> I've never liked d-i preseeding, especially partman; I prefer scripts I can control
[16:32] <maeud> I'm using preseeding to do the minimal amount as possible as it's a bit of a nightmare
[16:32] <maeud> playbook doing the rest
[16:32] <maeud> just need to get an install up and running
[16:36] <TJ-> I wrote scripts to test a RAID+LUKS+LVM install this week
[16:38] <maeud> so how do I see what's going on here TJ-, I can see the debug logs for partman and syslog, hw
[16:38] <maeud> it's specifically grub install where it fails
[16:38] <maeud> I've pointed it to sda1 which we've confirmed is /boot
[16:39] <TJ-> how do you mean, you've pointed it to sda1 ?
[16:39] <maeud> remember with the bootdev option which seems to be ignored
[16:40] <TJ-> I'd check the d-i log see what command line it is using for grub-install, because it /should/ be "grub-install /dev/sda"
[16:41] <maeud> where about is that one, I chose the menu item for debug logs, it gives me hardware-summary, partman and syslog
[16:43] <Ussat> anyone here run a gitlab server that uses LDAP ?
[16:43] <TJ-> maeud: I'd suspect syslog
[16:44] <maeud> nothing in syslog, that's what I posted before, it literally just gives me those 2 errors about sda vg
[16:45] <TJ-> The joys of d-i !
[16:46] <maeud> that's it
[16:50] <maeud> ok it's in debug mode now
[17:06] <lotuspsychje> place your details here qwebirc16206
[17:06] <qwebirc16206> Hi! I can't install Ubuntu Server 18.04 on my machine.
[17:06] <qwebirc16206> I have 2 HDDs and want t setup RAID1.
[17:07] <qwebirc16206> Here is the error image: https://drive.google.com/file/d/1dfw_TpcUDGbepl4sO5arQ97Tc-SNUrHn/view
[17:08] <qwebirc16206> It says curtin command block-meta
[17:08] <qwebirc16206> and the step is 9/11
[17:10] <Ussat> did you try to install ON the raid or make raid after ?
[17:11] <qwebirc16206> I tried to create RAID during the installation. Manual partitioning, like this:
[17:11] <bipul> qwebirc16206, Just share the steps of installation. And where are you installing it?
[17:14] <qwebirc16206> bipul: nothing special
[17:14] <qwebirc16206> https://drive.google.com/open?id=1kroSfFCI5Su1ODcdzkCncXo_Hj2lD7sV
[17:14] <Ussat> Peronsally, I would raid after...
[17:14] <maeud> TJ-: the install process is using "grub-installer", it takes /target as an argument then throws that error about sda vg unknown
[17:14] <maeud> it's a udeb pkg
[17:15] <qwebirc16206> bipul: standard configuration up to partitioning
[17:15] <qwebirc16206> I have attached an image of what the partitions looked like
[17:16] <TJ-> maeud: so something in the configuration is confusing it into thinking the VG name is the raw disk name - no idea!
[17:17] <qwebirc16206> tomreyn: here is the info: Ubuntu-Server <IP_ADDRESS> LTS "Bionic Beaver" - Release amd64 (20180725.1+apt)
[17:17] <qwebirc16206> Ussat: what? how?
[17:17] <tomreyn> qwebirc16206: ok. based on your screenshot, the installer seems to be trying to create a RAID-0 array, not RAID-1. are you sure you configured RAID-1?
[17:19] <maeud> and grub-installer is a 1.3k line bash script
[17:19] <maeud> awesome
[17:19] <qwebirc16206> tomreyn: yes, I have configured RAID1
[17:19] <qwebirc16206> see this: https://drive.google.com/file/d/1kroSfFCI5Su1ODcdzkCncXo_Hj2lD7sV/view
[17:19] <qwebirc16206> where did you find RAID0?
[17:20] <qwebirc16206> Oh, indeed, I see it...
[17:20] <Ussat> qwebirc16206, https://www.digitalocean.com/community/tutorials/how-to-create-raid-arrays-with-mdadm-on-ubuntu-18-04
[17:21] <tomreyn> qwebirc16206: this mentioned "raid-0", but maybe that's just the name of the curtin module: https://lh6.googleusercontent.com/6xRkZPJHz1IUEV4TZ8KLyK43BHrTFGSxRgkVdlkfrXUAxSV8bHKLXTHjgJRn0E90b4GPpyLYad5Qbw=w1720-h1242
[17:21] <Ussat> To be fair, I dont raid much most of my servers are SAN connected to an isilon
[17:21] <tomreyn> or maybe it's yet another curtion / subiquity bug.
[17:22] <tomreyn> qwebirc16206: use the alternative (classic, debian) installer
[17:22] <qwebirc16206> I haven't seen that option...
[17:22] <qwebirc16206> There is this installation, OEM installation and check disk.
[17:23] <qwebirc16206> Is it this OEM installation that you meant?
[17:23] <tomreyn> qwebirc16206: no, i'm referring to a different ISO download
[17:23] <tomreyn> qwebirc16206: see "alterantive downloads" at https://www.ubuntu.com/download/server
[17:25] <tomreyn> qwebirc16206: can you confirm that this system boots in UEFI mode?
[17:26] <TJ-> So much easier with scripts and deboostrap! :)
[17:27] <tomreyn> i'm actually considering to write a new installer in bash
[17:27] <tomreyn> maybe someone did this already.
[17:29] <qwebirc16206> yes, it boots in UEFI
[17:29] <qwebirc16206> there is also a /boot/efi partition
[17:31] <tomreyn> i noticed. i'm just thinking about reproducing it. i was hoping the latest build of the default server installer would fix most issues, but i guess many remain unfixed.
[17:33] <kinghat> is this odd that it shows i have 1 security update when i log in and when i search for updates it says up2date? https://paste.debian.net/hidden/d99e2318/
[17:34] <TJ-> kinghat: no, the motd may not have been updated yet
[17:35] <tomreyn> right, there's some 'caching' involved
[17:35] <kinghat> oh. its been a few days iirc.
[17:36] <TJ-> update-motd I think
[17:37] <kinghat> as an extra package? will it work itself out?
[17:37] <TJ-> kinghat: there's a tool you can execute "update-motd" that runs all the scripts that add their bits to the MOTD
[17:38] <TJ-> kinghat: scripts are dropped in /etc/update-motd.d/ and those are run and their output gathered by update-motd
[17:38] <kinghat> hmm this is odd: https://paste.debian.net/hidden/e994c8c2/
[17:39] <TJ-> kinghat: it could be due to the specific script, from update-notifier-common,  /usr/lib/update-notifier/update-motd-updates-available
[17:39] <kinghat> i had messed with grub when i had to take over the machine to get my user back into the sudo group/sudoers file.
[17:41] <TJ-> kinghat: oh, that looks like something caused by curtin/containers stuff, check if there's files in /etc/default/grub.d/
[17:42] <kinghat> kinghat@kinghat-server:/etc/default/grub.d$ ls -ln
[17:42] <kinghat> total 4
[17:42] <kinghat> -rw-r--r-- 1 0 0 140 Aug 21 20:42 50-curtin-settings.cfg
[17:42] <tomreyn> menu.lst? sounds like grub1 (AKA 0.98) when it should be grub2
[17:44] <kinghat> i cant remember what i did to grub because it wasnt formatting correctly on the screen or something like that when i was trying to get into recovery. then i just used a live cd to get sudo to change the sudoers file.
[17:45] <kinghat> maybe i did that grub-boot-repair thing. its been a month or more.
[17:45] <tomreyn> pastebinit <( cat /etc/os-release; echo; dpkg -l | grep grub)
[17:46] <tomreyn> i see. maybe the above output is irrelevant then
[17:46] <kinghat> https://paste.ubuntu.com/p/9mmJ5S5JSs/
[17:46] <tomreyn> just install grub2 to the boot disk
[17:47] <tomreyn> is this an AWS system?
[17:47] <kinghat> nah just ubuntu server on a thumb drive in the house.
[17:48] <tomreyn> i'm not sure what grub-legacy-ec2 actually does but i guess i would just remove it then
[17:48] <tomreyn> also purge the bios variant of grub2 if you use efi
[17:49] <TJ-> There's a postinst script that runs and generates that /etc/default/grub.d/50-curtin-settings.cfg which causes some GRUB v1 crud to be done; I seem to recall it is due to some weirdness on AWS or some other 'cloud'
[17:49] <tomreyn> i.e. sudo apt purge grub-pc grub-legacy-ec2
[17:49] <TJ-> I can't find the bug now but I was dealing with that issue some time ago
[17:49] <tomreyn> and then sudo grub-install /dev/whereever
[17:49] <tomreyn> ok TJ-
[17:50] <kinghat> i dont know for sure if its efi or not. its an old HP workstation board that has a bunch of stuff turned off to be able to run outside of an HP chassis and a PSU converter etc.
[17:50] <tomreyn> i remember that Xen PV systems always had trouble booting with grub2
[17:52] <tomreyn> IIRC there's some environment variable which can tell you how the system booted (UEFI vs BIOS), but i forgot the details and cant find it now
[17:52] <TJ-> hmmm, maybe it was something else, maybe to do with /etc/cloud/cloud.cfg.d/
[17:53] <kinghat> ill look tomreyn
[17:53] <tomreyn> if you have a /sys/firmware/efi directory then you have uefi
[17:53] <TJ-> tomreyn: I generally check sysfs /sys/firmware/efi/
[17:53] <tomreyn> :) thanks
[17:54] <TJ-> tomreyn: right, but it may not have booted with legacy mode, I seem to recall, there's a subtlety to it - checking the efivars I think
[17:54] <tomreyn> actually i made this up about the environment variable.
[17:54] <TJ-> oops, lose the "not" from that last line
[17:54] <kinghat> kinghat@kinghat-server:/sys/firmware/efi$ ls
[17:54] <kinghat> config_table  efivars  fw_platform_size  fw_vendor  runtime  runtime-map  systab  vars
[17:55] <tomreyn> kinghat: so thats a system which booted in uefi mode
[17:55] <kinghat> got ya. so do i need to check `efivars` or just that i have `efivars`?
[17:56] <tomreyn> unless TJ-'s subtlety applies, which i'm not aware of
[17:57] <tomreyn> kinghat: given that sysfs is present / mounted, if you have a directory /sys/firmware/efi then you booted in uefi mode.
[17:58] <tomreyn> i assume this is what you were asking?
[18:00] <kinghat> tomreyn: yes basically.
[18:01] <kinghat> so still run the purges and sudo grub-install?
[18:03] <tomreyn> kinghat: personally, in a situation where "i cant remember what i did to grub [..] maybe i did that grub-boot-repair thing", i would, yes.
[18:04] <TJ-> tomreyn: it would be really useful to have a /proc/sys/kernel/bootloader_method
[18:04] <kinghat> is there a default dir grub installs to or i should put it in dev/?
[18:05] <kinghat> https://paste.debian.net/hidden/10785d0e/
[18:06] <tomreyn> TJ-: yes, indeed.
[18:06]  * TJ- considers a patch and what Linus' reaction would be :)
[18:06] <tomreyn> ROOOOAR!
[18:07] <kinghat> lel
[18:08] <tomreyn> kinghat: looks fine to me, if it does to you?
[18:08] <tomreyn> kinghat: you run grub.install against a storage, not a directory.
[18:08] <kinghat> what does the 2 not fully installed or removed means?
[18:09] <TJ-> have you ever tried to grep for 'efi' or 'EFI' in kernel where #define and  #DEFINE are everywhere!?
[18:09] <tomreyn> kinghat: that you have 2 packages which are neither in state 'ii' not in state 'un'
[18:10] <tomreyn> dpkg -l | grep -Ev '^(un|ii)'
[18:11] <kinghat> https://paste.debian.net/hidden/d7ec8494/
[18:12] <kinghat> here is the dpkg grep: https://paste.debian.net/hidden/2ad5d621/
[18:12] <tomreyn> just "touch /boot/grub/menu.lst" and run it again, looks like the post removal script is buggy
[18:13] <kinghat> touch needs permission?
[18:14] <tomreyn> depends on what it wants to touch
[18:14] <tomreyn> for touching /boot/grub/menu.lst it'll need sudo
[18:14] <tomreyn> also make sure /boot is actaully mounted
[18:15] <kinghat> https://usercontent.irccloud-cdn.com/file/1SP5V3OX/image.png
[18:15] <tomreyn> why grub2? thats new
[18:16] <tomreyn> but i guess you can just agree and then reinstall anything thats missing
[18:17] <kinghat> ummmm lol
[18:18] <kinghat> so this is effectively starting fresh with grub?
[18:18] <kinghat> i havent clicked yes yet.
[18:22] <TJ-> tomreyn: looks like we can rely on the sysfs node: https://paste.ubuntu.com/p/5qYCCWm2C5/
[18:24] <kinghat> should everything grub related on my system be removed and then added back?
[18:38] <kinghat> tomreyn: https://paste.debian.net/hidden/08e4e972/
[18:42] <tomreyn> TJ-: thanks for looking this up
[18:46] <tomreyn> kinghat: such a nicely broken package. maybe just purge "dpkg --purge" grub-pc and grub-legacy-ec2. or purge all of grub , then reinstall grub-efi-amd64 grub-common
[18:47] <tomreyn> * grub2-common
[18:48] <kinghat> tomreyn: `dpkg --purge grub*` ?
[18:54] <tomreyn> kinghat: i think dpkg only handles one package at a time, but not sure
[18:54] <tomreyn> other than that, yes
[18:54] <kinghat> youre correct. try with apt purge?
[18:57] <teward> anyone know if it's possible to boot an ISO stored within an LVM partition into RAM at grub launch time?
[18:57] <tomreyn> kinghat: apt purge didnt seem to work, so i suggested dpkg --purge
[18:57] <teward> asking because I need to weekly Clonezilla this system to a backup disk and i need some GRUB guidance :|
[18:57] <teward> (they give me an ISO)
[19:01] <tomreyn> teward: there's "grub-imageboot" ("boot iso, harddisk and floppy images with grub2 and syslinux memdisk") and "grml-rescueboot" ("Integrates Grml ISO booting into GRUB"). i had mixes results with those on an uefi booting system (have not tried legacy bios). i think the grml ones worked with some iso's but not others.
[19:01] <tomreyn> generally grub can boot from an iso
[19:02] <tomreyn> (but maybe not all of them, not sure)
[19:02] <teward> tomreyn: right, but the tricky part is, the documentation I found doesn't anticipate the ISO being inside an LVM LV
[19:02] <teward> it anticipates it being on a physical partition somewhere
[19:02] <teward> ... which... I don't actually have at the moment.
[19:02] <teward> since this system is full-disk LVM.
[19:02] <teward> since this system is full-disk LVM except for 512MB at the start for a boot partition.
[19:02] <tomreyn> oh, yes, you said LVM, sorry, no idea then
[19:02] <teward> yeah that's where I'm getting stuck :|
[19:02] <teward> I mean TO BE FAIR
[19:02] <teward> I could probably replicate this in an LV
[19:02] <tomreyn> shrink the PV, i guess
[19:03] <teward> tomreyn: last time I did that I torched the partition table LOL
[19:03] <teward> I'll do that after I take a Full Disk Image later :P
[19:03] <teward> and i'll just USB boot for that ;P
[19:03] <teward> ... remind me how to shrink a PV again xD
[19:03] <teward> shrink a PV safely*
[19:03] <tomreyn> i wouldnt dare doing it live either
[19:04] <tomreyn> and i'd need to look up how to do it, too
[19:04] <tomreyn> i did it before, and it worked, that's all i rmeember
[19:05] <teward> i only need like 300MB so eh
[19:05] <teward> i'mma backup my system with a full disk image first though
[19:05] <teward> that way if I fubar it i can restore it
[19:05] <teward> again
[19:05] <teward> it shouldn't be hard to shrink the LVs.  I'll have to recreate the swap LV though
[19:05] <teward> but that won't be a problem.
[19:06] <tomreyn> IIRC when you shrink the PV (after shrinking the LVs) you have to provide the target size explicitly, which is silly, it doesn'T have anything like ext4's "minimal size" option where it shrinks to the smallest possible size automatically
[19:08] <tomreyn> so it's a bit of try and error: you guess the new size, then have lvm resize the PV, then it either prints a warning saying the ewuivalent of "this looks to small but it did it anyways" or the equivalent of "all fine".
[19:08] <kinghat> tomreyn: i ran it again anyways and got this: https://paste.debian.net/hidden/e6779eea/
[19:08] <tomreyn> in the former case you re-reun it with a slightly larger size
[19:08] <tomreyn> ...until oyu get rid f the warning
[19:09] <tomreyn> kinghat: yeay, this actually worked
[19:09] <kinghat> it didnt remove `grub.d` though.
[19:09] <tomreyn> whats left in /etc/grub.d ?
[19:10] <kinghat> kinghat@kinghat-server:/etc/grub.d$ ls -ln
[19:10] <kinghat> total 4
[19:10] <kinghat> -rwxr-xr-x 1 0 0 424 Dec 10 02:00 25_custom
[19:11] <tomreyn> kinghat: and that contains?
[19:12] <tomreyn> i have 40_custom and 41_custom on this bionic
[19:13] <kinghat> tomreyn: https://paste.debian.net/hidden/73c80033/
[19:13] <tomreyn> kinghat: did you or some other admin of this system create this file?
[19:14] <kinghat> im the only one. not that i remember.
[19:14] <tomreyn> kinghat: and do those files actually exist on /boot/efi/EFI/ubuntu/ ?
[19:16] <tomreyn> ...or in /boot/efi/EFI/BOOT
[19:16] <kinghat> yes. among others
[19:17] <tomreyn> and blkid reports that your ESP'S UUID is 84C3-4FDF ?
[19:17] <kinghat> https://paste.debian.net/hidden/adb4e53c/
[19:18] <tomreyn> blkid | grep 'PARTLABEL="efi"'
[19:18] <tomreyn> sdc1 is UUID 84C3-4FDF
[19:18] <tomreyn> and is potentially your ESP
[19:19] <tomreyn> so i guess you can keep it, or remove it, whatever you like
[19:19] <tomreyn> it shouldnt do any harm
[19:19] <tomreyn> just adds 3 extra entries on your grub menu
[19:20] <kinghat> wont grub install just make a new one?
[19:20] <tomreyn> a new what?
[19:21] <kinghat> `grub.d`
[19:21] <tomreyn> not if it's already there, otherwise it'll add to what's already there
[19:21] <tomreyn> i mean: not if it's already there, it'll add to what's already there
[19:22] <kinghat> but if its not there it will just start fresh?
[19:22] <teward> tomreyn: the alternative is I shrink the LV's down considerably to make sure there's enough space and leftover extents to not deal with anything
[19:22] <teward> but then shrink the PV from there, but that's... tricky.
[19:23] <tomreyn> teward: i don't think i'm getting the alternatives you're dioscussing. one is to shrink LVs, then the PV, the other is...?
[19:24] <teward> tomreyn: > you guess the new size, then have lvm resize the PV, then it either prints a warning saying the ewuivalent of "this looks to small but it did it anyways" or the equivalent of "all fine".
[19:24] <teward> ^ avoid this by ultrashrinking :P
[19:25] <kinghat> there is actually a bunch of stuff still in `/boot`: https://paste.debian.net/hidden/f3ab06d3/
[19:25] <teward> shrink the LV way smaller than it needs to be but meh
[19:25] <teward> tomreyn: i'mma do a Full Disk Backup now then attempt to NOT explode the system heh
[19:32] <tomreyn> teward: if you have unpartitioned space on the VG which is backed by exactly one PV then you can just pvresize with the trial-and-error approach. if you have a VG backed by multiple PVs youmay have to pvmove (to move VG data (extents) off one of the PVs) first, so you can remove this PV.
[19:32] <tomreyn> and i dont think you need to do it 'way smaller', no
[19:33] <kinghat> im not sure if its ready to be 'regrubbed' or not but shouldnt `grub-pc` add everything back like the efi stuffs or does that have to be installed manually as well?
[19:34] <tomreyn> kinghat: if those /boot/grub* are there while all the grub* packages are purged, then you should proibably purge those untracked files.
[19:34] <tomreyn> "dpkg -S /path/to/directoryorfile" to check whether its part of a package
[19:34] <teward> tomreyn: i ALMOST deleted the wrong thing lol
[19:34] <teward> switched the lvremove options xD
[19:34] <tomreyn> teward: whoops
[19:34] <teward> that could've been bad xD
[19:35] <tomreyn> i think you real yjust want to test whether you bare metal recovery procedure works
[19:36] <teward> considering i've already restored this twice before... :P
[19:36] <kinghat> kinghat@kinghat-server:/etc/grub.d$ dpkg -S /boot/grub
[19:36] <kinghat> dpkg-query: no path found matching pattern /boot/grub
[19:36] <tomreyn> kinghat: congratulations for testing it.
[19:36] <kinghat> remove those as well?
[19:38] <tomreyn> kinghat: i run an ubuntu 18.04 desktop which does uefi booting and don't have /boot/grub
[19:38] <tomreyn> so i guess you dont need it. after all its not part of any package you have installed. so, yes, i guess it can go.
[19:39] <kinghat> ill get rid of the `grub.bak` dir as well
[19:39] <tomreyn> it would help if you knew what you did to your system :)
[19:39] <tomreyn> i assuem this is a result of running "boot repair"
[19:40] <kinghat> ya. then i manually went in via livecd sudo and fixed the sudoers file
[19:40] <kinghat> should have just done that from the start
[19:40] <kinghat> but i thought there was a problem with grub.
[19:40] <kinghat> there wasnt.
[19:40] <kinghat> i made a problem though. :P
[19:41] <teward> tomreyn: another stupid quesiton, but is there a way to map known partitions to what their GRUB root= equivalents are :|
[19:41] <teward> or do I have to drop to the grub cli to do that
[19:42] <tomreyn> teward: the UUIDs? those are printed by blkid
[19:43] <tomreyn> teward: is this what you meant?
[19:44] <teward> tomreyn: close enough
[19:44] <teward> i'll read the grub manpage
[19:44] <teward> i have to full disk image this first
[19:44] <kinghat> tomreyn: https://paste.debian.net/hidden/f250554c/
[19:44] <teward> back in a bit.
[19:46] <kinghat> not sure about the `/efi/ubuntu/` `grub.cfg` and `grubx64.efi` files
[19:48] <tomreyn> kinghat: grub-install should replace them when you run it.
[19:48] <kinghat> ok. can i remove the `grub.d` dir or just the `25_custom` file in it?
[19:49] <tomreyn>  /boot/efi/ubuntu/grubx64.efi is stage1 of grub, grub.cfg points it to where stage2 is located
[19:50] <tomreyn> kinghat: if you still dont have any grub packages installed, you can just remove all of /etc/grub.d/
[19:51] <kinghat> ok its gone.
[19:51] <kinghat> so `grub-install` or `grub-pc`?
[19:51] <tomreyn> be sure to install grub2 and grub2-common and to run update-grub and grub-install soon, though, or you wont be able to boot.
[19:52] <tomreyn> those are apples and oranges: grub-install is a command, grub-pc is a package name.
[19:53] <tomreyn> sorry, it's not "grub2 and grub2-common" but "grub-efi-amd64 and grub2-common"
[19:53] <kinghat> i mean do i need to have grub before i can `grub-install`?
[19:53] <tomreyn> although this may actually both work
[19:54] <tomreyn> kinghat: yes, you wont have the grub-install command before you installed the package which provides it.
[19:54] <tomreyn> so install it
[19:56] <kinghat> doesnt one of the grub packages already bring in `grub-efi-amd64`?
[19:58] <tomreyn> if you install "grub2" or "grub" this may depend on / install grub-efi-amd64, i have not checked
[19:58] <kinghat> regardless: https://paste.debian.net/hidden/a5456c62/
[19:58] <tomreyn> what matters is that you'll have grub-efi-amd64 and grub-efi-amd64-bin and grub2-common in the end
[19:59] <tomreyn> i dont see any errors on the output, do you have any questions?
[19:59] <kinghat> so now `update-grub` and then `grub-install`?
[20:00] <tomreyn> corret
[20:00] <tomreyn> correct
[20:00] <tomreyn> "grub-install" takes one argument, the destination device.
[20:00] <kinghat> ok i dont want to mess that one up.
[20:01] <tomreyn> i usually install to multiple devices, just in case one breaks.
[20:01] <kinghat> so `grub-install /dev/sdc` via the blkid output here: https://paste.debian.net/hidden/adb4e53c/
[20:02] <tomreyn> ignore what i just said, this doesn'T apply to uefi (unless you have multiple ESPs)
[20:03] <tomreyn> yes, "grub-install /dev/sdc" is probably correct.
[20:03] <tomreyn> i'm a bit puzzled why this is not sda, though
[20:03] <kinghat> i did `grub-probe -t device /boot/grub` and it says /dev/sdc2 but i only need the sdc?
[20:04] <kinghat> me too lol
[20:04] <tomreyn> you seem to have zfs on sda and sdb, i'm not into this
[20:04] <kinghat> i dont know how that happened tbh.
[20:04] <tomreyn> there's a lot of rather relevant things you should try to be more in the know of. ;-)
[20:05] <tomreyn> kinghat: it's good to know or be able to tell, by yourself, how the boot process works, in case it breaks
[20:06] <kinghat> https://paste.debian.net/hidden/d27c8455/
[20:07] <kinghat> do i need to `grub-update` again?
[20:09] <kinghat> i havent restarted but i logged out of the session and back in and im not seeing any updates like before. so
[20:09] <tomreyn> kinghat: no. check the files and modification dates in /boot/efi/EFI/ubuntu/
[20:10] <tomreyn> i'd expect that at least grubx64.efi has a current file modification time
[20:10] <tomreyn> maybe grub.cfg also
[20:10] <kinghat> https://paste.debian.net/hidden/d972f2cb/
[20:10] <kinghat> just `grubx64.efi`
[20:13] <tomreyn> ok. that's fine. we already looked at grub.cfg and it pointed at the correct ESP
[20:13] <kinghat> scared to reboot
[20:13] <tomreyn> you shouild be able to reboot fine.
[20:14] <kinghat> here goes
[20:14] <tomreyn> if it doesn't work immediately, see if you can pick this grubx64.efi on your uefi configuration interface
[20:14] <kinghat> you mean from the bios?
[20:14] <tomreyn> yes
[20:14] <kinghat> im remote atm.
[20:15] <tomreyn> oh, good luck then
[20:15] <tomreyn> i'd rather wait unil i'd be back on site
[20:15] <tomreyn> unless i had out of band management
[20:15] <tomreyn> or remote hands
[20:15] <kinghat> physical access is... all the way downstairs..
[20:16] <tomreyn> that sounds acceptable, if you're not in a 64 floor skyscraper without a lift.
[20:16] <kinghat> lol
[20:16] <kinghat> `reboot` initiated!
[20:20] <kinghat> im in!
[20:20] <kinghat> yay!
[20:20] <kinghat> tyvm tomreyn!
[20:20] <tomreyn> :)
[20:20] <maeud> just can't get past this stupid grub issue at all
[21:48] <teward> tomreyn: well... that didn't go well.  Managed to restore, but I had to do some... not cool tactics.
[21:48] <teward> Ultimately just GUI booted to a Live Desktop USB with a patched gparted and did the LVM resize
[21:48] <teward> which apparently WORKS when the right patch is applied
[21:49] <teward> i'll have to bug the Desktop team at some point to fix this.
[22:12] <maeud> re-did the whole process and it starts the grub install, screen goes black and it loops trying to restart the screen
[22:12] <maeud> can't win
[22:12] <maeud> lol
[22:45] <Checkmate> is there any tools to block bots ?
[22:45] <Checkmate> on website
[23:19] <CodeMouse92> Checkmate: fail2ban works pretty well, as far as blocking malicious bots and other attacks
[23:20] <CodeMouse92> In terms of valid search engine bots, robots.txt is how you control what they crawl.
[23:29] <Intelo> is it possible to buy ip from somewere and use that ip in your vps provider (and not the ip of vps host it self)? You own the ip and can attach it to anywhere?
[23:31] <mybalzitch> you'd need an ASN, and for your VPS provider to allow you to announce your ASN within their network. Not impossible but usually costly
[23:32] <mybalzitch> and I'm not sure they (ARIN) would sell you a /24 (255 IP's) let alone a single ip
[23:34] <Intelo> where to get ip ?
[23:35] <maeud> type "buy ip space" into Google
[23:36] <Intelo> k


[02:34] <darkxst> jbicha, I think disable bug reporting on xenial, no point allowing people to report bugs if we are just going to auto-close them
[02:37] <jbicha> ok
[06:11] <Seekerj> Hello. I recently switched from Ubuntu Unity to Ubuntu Gnome. Now I cannot connect to my bluetooth speaker anymore. It used to work on Unity. When I open the bluetooth settings, cellphones are recognized but the speaker is not found.
[22:22] <dsynapse> hello
[22:22] <dsynapse> how can I troubleshoot gnome-shell logout issues?  When I select logout it seems it waits about a minute before showing the logout dialog box


[03:07] <zul> heylo
[03:19] <zul> hey BenC
[03:22] <BenC> hey
[03:23] <zul> how is the sprint going?
[03:39] <BenC> not there
[03:39] <BenC> I had to cancel
[03:39] <fabbione> hey benC
[03:43] <BenC> hey fabio
[03:44] <fabbione> BenC: sup?
[03:44] <BenC> not much
[03:44] <BenC> trying to get a kernel out today
[03:44] <fabbione> ok
[03:45] <fabbione> i am waiting for bubba to test the megaraid fix on .12
[03:45] <fabbione> also.. i have prepared the images for that possible binutils regression
[03:45] <fabbione> i need to write info in the bug
[03:46] <BenC> cool
[03:46] <fabbione> i can't find the bugnumber agian
[03:46] <fabbione> bah
[03:46] <BenC> I had to go to bugzilla and follow the malone link
[03:47] <BenC> 20771 or 20711 on bugzilla
[03:47] <fabbione> found it
[03:50] <fabbione> there
[04:11] <mjg59> BenC: ajmitch mentioned that acpi updates seemed to have broken his machine, but I don't know if he's filed a bug yet
[04:12] <BenC> the ones I just pulled in?
[04:12] <mjg59> Yeah
[04:12] <BenC> he did his own build?
[04:12] <mjg59> Didn't get a very detailed report, though
[04:12] <mjg59> Not sure
[04:13] <mjg59> Have you done a daily?
[04:13] <BenC> well a bug report would be premature considering there aren't any images with those updates yet :)
[04:13] <mjg59> Heh
[04:13] <BenC> damn, gotta hold off his build until I find out for sure now
[05:07] <BenC> lots of stuff isn't working with -15 kernel on my P4 box
[05:07] <BenC> keyboard being one of them, so I can't even login
[05:46] <doko> BenC, fabbione: I did make a mISDN patch, http://people.ubuntu.com/~doko/misdn-2006-01-25.diff.bz2, taken from ftp://ftp.isdn4linux.de/, I didn't test it yet, don't have any hardware here. config options should be
[05:46] <doko> #
[05:46] <doko> # Modular ISDN driver
[05:46] <doko> #
[05:46] <doko> CONFIG_MISDN_DRV=m
[05:46] <doko> CONFIG_MISDN_AVM_FRITZ=n
[05:46] <doko> CONFIG_MISDN_HFCPCI=y
[05:46] <doko> CONFIG_MISDN_SPEEDFAX=y
[05:46] <doko> CONFIG_MISDN_W6692=y
[05:46] <doko> CONFIG_MISDN_DSP=y
[05:47] <doko> CONFIG_MISDN_MEMDEBUG=y
[05:47] <doko> so just disable the CONFIG_MISDN_AVM_FRITZ option
[05:47] <BenC> doko: what's that patch do?
[06:46] <doko> BenC: add the mISDN driver
[06:47] <BenC> doko: I already did that
[06:47] <mxpxpod> BenC: have you gotten anywhere with sound in the past few days?
[06:53] <BenC> mxpxpod: nah, been trying to get some other things fixed
[06:53] <mxpxpod> BenC: that's cool... as long as we get this figured out before april
[06:53] <BenC> oh yeah, It'll get done way before then :)
[06:53] <BenC> the fact that it's working is good, just need to tweak some things once I get time to look into it
[06:54] <mxpxpod> cool
[06:54] <mxpxpod> BenC: here's something strange that I've noticed... sometimes when I sleep my ibook, I'll resume and there will be a >10 syslogd's running
[06:55] <BenC> that's odd
[06:55] <mxpxpod> BenC: and it's usually when programs that use network interfaces are left running (at least that's what I've come to the conclusion)
[06:56] <mxpxpod> BenC: and if I kill any of them, sudo doesn't work
[06:57] <BenC> I can't even guess what would cause that
[06:57] <mxpxpod> BenC: yeah, me either
[06:57] <mxpxpod> I think I'm going to do a fresh install next week (mine is upgraded from breezy) and see how that works
[07:00] <mxpxpod> BenC: another thing, when my ibook boots, it puts the airport extreme at eth2, but when I remove the module and modprobe it again, it puts it at eth1
[07:01] <BenC> yeah, I'm not sure what the deal is with that
[07:01] <mxpxpod> ok, so that's not just me
[07:01] <BenC> same with mine, but if I blacklist the sungem module, it goes to eth0 without problem
[07:01] <mxpxpod> haha
[07:01] <mxpxpod> BenC: do you use spamassassin?
[07:01] <doko> BenC: which version?
[07:02] <BenC> mxpxpod: not on this machine
[07:02] <BenC> doko: whatever was the latest CVS when I pulled it in
[07:02] <mxpxpod> BenC: ok
[07:04] <mxpxpod> BenC: brb.. I'm gonna go log on with my laptop
[07:07] <bryanf> BenC: back


[10:26] <fairuz> Hi, Can I use request_irq in user space?
[11:36] <apw> fairuz, don't believe there is an interface for that no
[11:59] <fairuz> apw: so the irq number, how can I know it exactly? i assume that it's different for each arch?
[12:04] <mjg59> fairuz: the irq number for what?
[12:04] <fairuz> for PL310, a L2 cache controller
[12:05] <fairuz> it says in the TRM, the irq for this device is on MA_IRQ_0
[12:05] <fairuz> just wondering does it mean irq number = 0 in linux?
[12:23] <fairuz> apw: is there a way to know the irq number for each irq source?
[12:35] <mjg59> fairuz: Depends on your architecture
[12:36] <mjg59> fairuz: There's no real mechanism for delivering IRQs to userspace - you'll need something in kernel anyway
[12:36] <fairuz> mjg59: yes, i'm writing in kernel space right now
[12:36] <fairuz> just dont really understand the irq number that I should put
[12:38] <mjg59> fairuz: You'll need to work out how your architecture wires stuff up
[12:38] <fairuz> mjg59: just need a confirmation, does irq number 0 in linux means the hard wired 0 in interrupt controller?
[12:39] <mjg59> No, there can be offsets due to the architecture
[12:39] <fairuz> mjg59: o
[12:39] <fairuz> mjg59: ok
[12:40] <mjg59> fairuz: There's already some amount of PL310-related code in the omap and tegra trees
[12:41] <fairuz> mjg59: I dont found any that touches the interrupt part (or maybe it's me who's not look hard enough)
[12:41] <mjg59> fairuz: What hardware are you using?
[12:41] <fairuz> omap4430
[12:41] <mjg59> #define OMAP44XX_IRQ_PL310                      (0 + OMAP44XX_IRQ_GIC_START)
[12:41] <mjg59> Where OMAP44XX_IRQ_GIC_START is 32
[12:42] <mjg59> So that's probably the IRQ you want!
[12:42] <fairuz> yes!!!!
[12:42] <mjg59> Look at arch/arm/plat-omap/include/plat/irqs-44xx.h
[12:42] <fairuz> i doubt it, I found SPIs start at ID32 and PL310 hard wired to IRQ 0
[12:42] <fairuz> mjg59: Thanks
[12:43] <fairuz> mjg59: I'm still familiarise myself with all those searching in the kernel tree -.-
[12:45] <fairuz> mjg59: one stupid question, in the kernel tree, any file in any include folders can be included right? e.g #include <plat/irqs-44xx.h> ?
[12:45] <fairuz> regardless where the include folder is
[12:45] <fairuz> :D
[12:52] <mjg59> fairuz: Yes, the paths get set appropriately
[13:18]  * ogasawara waves
[13:21] <JFo> o/
[13:22] <tgardner> ogasawara, hey there. kinda early for you, isn't it :)
[13:22] <ogasawara> tgardner: according to the lil guy it's not :)
[13:23] <ogasawara> tgardner: so I figure I'll start my days about now from now on
[13:23] <tgardner> ogasawara, hence the smiley.
[13:23] <tgardner> ogasawara, does your mumble client still work?
[13:23] <ogasawara> tgardner: yep, just gotta dig for my headphones
[13:47] <cooloney> ogasawara: long time no see, welcome
[13:47] <ogasawara> cooloney: thanks
[13:49] <cooloney> ogasawara: how's going? don't work too hard, -:)
[14:04] <JFo> apw, care to have a look at bug 715330 ?
[14:04] <ubot2> Launchpad bug 715330 in xserver-xorg-driver-ati "Freeze after login with KMS enabled on Radeon HD6310" [Medium,Confirmed] https://launchpad.net/bugs/715330
[14:04] <JFo> you may already have a patch req for it.
[14:24] <apw> JFo, looks like we already have that coming, will handle
[14:41] <apw> JFo, abou ?
[14:41] <apw> about ?
[14:41]  * apw slaps his '' key
[14:41] <apw> grrrr
[14:49] <JFo> heh
[15:13]  * ogasawara back in 20min
[16:02] <JFo> <-grabbing lunch
[16:34] <tseliot> mjg59: are you around?
[16:35] <mjg59> tseliot: Hi
[16:36] <tseliot> mjg59: hi. Do you know how to debug the lack of a backlight device after backlight_device_register() succeeds? This is with 2.6.32
[16:37] <mjg59> No
[16:37] <mjg59> If that's succeeded then you should have a device
[16:38] <mjg59> When you say it's succeeded, you know it returns ERR_PTR and not NULL on error, right?
[16:38] <tseliot> mjg59: that's what I was about to ask
[16:39] <mjg59> So if you're just checking against NULL then you'll think you've succeeded when in fact you've failed
[16:39] <tseliot> mjg59: so, shall I test it with "if (IS_ERR(backlight_device))" ?
[16:39] <mjg59> Yes
[16:40] <tseliot> mjg59: well, that's the way the poulsbo driver checks it if(backlight_device), that is
[16:40] <tseliot> I guess it's ok, as it's psb...
[16:40] <tseliot> ;)
[16:41] <tseliot> mjg59: so my next question would be, how would you debug a failure there?
[16:44] <tseliot> mjg59: is there any documentation I can have a look at?
[16:44] <mjg59> tseliot: drivers/video/backlight/backlight.c
[16:45] <mjg59> You should be able to work it out from the failure cases there
[16:45] <tseliot> mjg59: right. Thanks a lot
[16:47] <apw> tgardner, indeed ... finger trouble
[16:57] <tgardner> apw, do you remember if we decided mpt's macbook had a drive hardware issue?
[16:57] <apw> i think we decided it was possible, but we had no evidence
[16:57] <apw> we asked him to collect something when it happened again
[16:58] <tgardner> apw, k
[16:58] <apw> tgardner, though waht i now forget
[16:58] <tgardner> maybe he'll remember
[16:59] <Kano> hi, why is CONFIG_HZ_250 for 32 bit and CONFIG_HZ_100 for 64 bit?
[16:59] <mjg59> I think a better question is arguably why they're not both HZ_1000
[17:00] <apw> mjg59, cause that costs you 10% of performance
[17:00] <Kano> sure,best would be 1000 hz for both
[17:00] <apw> actaully 10-17% depending on load
[17:00] <mjg59> apw: It's very dependent on what your definition of performance is :)
[17:00] <apw> mjg59, indeed, overall throughput in this context
[17:01] <Kano> but at least it should be the same for 32+64 bit or not?
[17:01] <apw> Kano, no it was a deliberate split
[17:02] <Kano> how to change the config to update the files in debian.master?
[17:03] <apw> Kano, in normally use vi to change the option i want, then use updateconfigs target to propogate
[17:04] <Kano> ah
[17:04] <apw> Kano, the source is all included in the tree
[17:05] <Kano> will check it out
[17:09] <davek> hello kernel folk
[17:10] <davek> does anyone know the estimated release of ubuntu using 2.6.38 stable?
[17:11] <apw> davek, we are waiting on final from linus, w
[17:11] <Kano> there is no .38 stable kernel yet
[17:11] <apw> though i would expect it would be in the next day or two
[17:11] <davek> okay
[17:11] <davek> how long would it take after release?
[17:11] <apw> thoguh we are struggling with compiler issues
[17:11] <davek> for ubuntu to add it?  (im kindof a noob here)
[17:12] <davek> i recently purchased a very new motherboard and am looking forward to support for drivers within 2.6.38
[17:13] <apw> davek, if they arn't in the current kernels based on the 38-rcN releases you are likely not goting to get it in any furhter kernel we upload
[17:13] <davek> from what i read there should be Zacate support in there
[17:14] <davek> so would one run Natty to get this kernel, or could i do a trick with Maverick to install it?
[17:14] <davek> (in the future)
[17:14] <apw> davek, well they arn't adding any new features to .38 everything is bug fixes
[17:14] <apw> so if a ntty kernel doesn't have what you want now, its not likely to later
[17:14] <davek> okay
[17:15] <davek> im running Maverick 10.10 presently
[17:15] <davek> will that pick up 2.6.38 too?
[17:16] <apw> we do backports for lucid, but you can hand install them on maverick.  they won't update on maverick tho.
[17:16] <tgardner> davek, you can test also natty by adding this PPA: https://launchpad.net/~kernel-ppa/+archive/pre-proposed?field.series_filter=natty
[17:16] <davek> okay..  wow thanks for the response guys
[17:16] <davek> you rock
[17:16] <davek> thanks apw and tgardner
[18:10]  * tgardner --> lunch
[18:13] <Kano> bye
[19:16]  * jjohansen -> lunch
[20:47] <rupert_millard> Hi. It's my first time ever on IRC! On my new laptop, I am getting an intermittent kernel panic within about a minute of powering up. I installed "linux-crashdump" so I can give you a proper bug report, but although it seems to dump a load of data on the panic, I can't find it anywhere when I boot up. So I've got two problems - what (is/am I doing) wrong with linux-crashdump, and how do I give you the best bug report I can? I do have
[20:47] <rupert_millard> a photograph of the screen showing the panic.
[20:55] <charlie-tca> rupert_millard: You can file a bug by opening a terminal and typing "ubuntu-bug linux" without the quotes
[20:55] <rupert_millard> yes but is that very useful to you?
[20:55] <rupert_millard> i really wanted to include a dump, but linux-crashdump doesn't seem to work for me
[20:57] <charlie-tca> ubuntu-bug provides most of the needed logs, and is a very useful method of filing bugs
[20:57] <rupert_millard> ok
[20:58] <rupert_millard> charlie-tca: what's the point of linux-crashdump then?
[20:58] <charlie-tca> You can look in /var/log for the linux-crashdump, but I don't know if it will be there
[20:58] <rupert_millard> charlie-tca: should I file a bug against it too?
[20:58] <charlie-tca> rupert_millard: no idea, I don't know what it is, myself
[20:58] <charlie-tca> Is there anything in /usr/share/docs that explain it?
[20:59] <rupert_millard> charlie-tca: https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
[21:00] <charlie-tca> The LKCD utility is not designed to gather helpful information in the case of a hardware caused panic or a segment violation
[21:01] <rupert_millard> what constitutes a hardware caused panic?
[21:01] <charlie-tca> ubuntu-bug should pick it up
[21:01] <rupert_millard> well my computer completely locked up - i had to power cycle it
[21:01] <charlie-tca> hm, maybe there is a crash log in /var/crash ?
[21:02] <rupert_millard> there's no /var/crash directory
[21:04] <charlie-tca> then there is no crash report available.
[21:04] <Zelozelos> anyone wanna help out w gwinwrap, im trying to get the videos to play again. the -wid option is causing an error
[21:04] <charlie-tca> Perhaps it is panicing before it can save it
[21:06] <rupert_millard> well since installing linux-crash, there is a load of activity - the second kernel seems to be doing something
[21:07] <rupert_millard> i think init might be starting swap up before kdump has a chance to inspect that partition for a dump
[23:31]  * jjohansen heads out for a bit, back on later


[00:16] <cjwatson> wgrant: Fancy some pip fun?  https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/379684 arranges to build wheels as part of our deployment artifact, which is something on the order of four or five times as fast on my laptop as building them from scratch (as happens when we rsync out from one path on carob to a different path on target machines).
[00:17] <cjwatson> Should get deployment times back to in the area of what they were before the conversion to pip.
[00:20] <wgrant> cjwatson: what's the [0-9]* in the LP wheel name?
[00:20] <wgrant> But sounds like a good idea
[00:20] <cjwatson> Version
[00:21] <cjwatson> $ grep ^__version__ setup.py
[00:21] <cjwatson> __version__ = '2.2.3'
[00:21] <cjwatson> I just wanted to avoid future amusement with some dependency's name happening to start with "lp-" or something
[00:21] <wgrant> Ah, fair enough, indeed
[00:21] <wgrant> No underscores for us
[00:22] <wgrant> r=me
[00:24] <cjwatson> Excellent, thanks
[01:38] <cjwatson> atemoya:
[01:38] <cjwatson> Thu 27 Feb 12:44:33 UTC 2020 Building code
[01:38] <cjwatson> Thu 27 Feb 13:09:14 UTC 2020 Updating code
[01:38] <cjwatson> Thu 27 Feb 18:13:05 UTC 2020 Building code
[01:38] <cjwatson> Thu 27 Feb 18:32:48 UTC 2020 Updating code
[01:38] <cjwatson> (both builds before the change above)
[01:38] <cjwatson> Fri 28 Feb 01:32:28 UTC 2020 Building code
[01:38] <cjwatson> Fri 28 Feb 01:36:38 UTC 2020 Updating code
[01:39] <cjwatson> So that phase is indeed about five times as fast there.
[01:47] <wgrant> Very nice.
[03:32] <lifeless> noice
[12:42] <tomwardill> ooh, a bug fix from 2017, that's exciting :)
[12:43] <pappacena> Well, I think we still have some bugs from 2011 open... 😅
[12:43] <tomwardill> little steps, little steps ;)
[12:44] <pappacena> One at a time. We will get there. :-)
[12:44] <SpecialK|Canon> We have some bugs from before that ;)
[12:44] <SpecialK|Canon> I put a card on the list for Frankfurt to do a little triage of our Critical bugs
[12:44] <cjwatson> We have bugs from 2005 open ...
[12:44] <tomwardill> huh, you can't sort bugs by age
[12:44] <SpecialK|Canon> I can believe they're still bugs, but we should maybe talk about the definition of "Critical"
[12:45] <tomwardill> oh, I guess Number is basically the same
[12:45] <cjwatson> tomwardill: You can, use the cog at the left of the list of sort columns
[12:45] <tomwardill> https://bugs.launchpad.net/launchpad/+bug/25
[12:45] <mup> Bug #25: Allow discussion/commenting on translations <feature> <lp-translations> <ui> <Launchpad itself:Triaged> <https://launchpad.net/bugs/25>
[12:46] <pappacena> wow... #25!
[12:49] <cjwatson> Launchpad was of course the first project to use Launchpad for bug tracking (leaving aside the special case of bug 1)
[12:49] <mup> Bug #1: Microsoft has a majority market share <canonical> <eoan> <iso-testing> <microsoft> <package-qa-testing> <Clubdistro:Fix Committed> <Computer Science Ubuntu:Fix Committed by compscibuntu-bugs> <LibreOffice:Fix Committed> <dylan.NET.Reflection:Fix Committed> <dylan.NET:Fix Committed>
[12:49] <mup> <EasyPeasy Overview:Fix Committed by ramvi> <Ichthux:Fix Committed by raphink> <JAK LINUX:Fix Committed by jp-charras> <LibreOffice:In Progress by bjoern-michaelsen> <Linux:New> <Linux Mint:Fix Released> <The Linux OS Project:In Progress> <Neobot:New> <Novabot:New> <OpenOffice:In Progress by
[12:49] <mup> lh-maviya> <ReactOS Core Operating System:Incomplete> <Tabuntu:Invalid by tinarussell> <Tivion:Invalid by shakaran> <Tv-Player:Invalid> <Ubuntu Malaysia LoCo Team:In Progress by apogee> <Wine:Confirmed> <Ubuntu:Fix Released> <Arch Linux:New> <Baltix:Confirmed> <Debian:In Progress>
 <Fluxbuntu:Confirmed> <openSUSE:In Progress> <Tilix:New> <https://launchpad.net/bugs/1>
[12:50] <cjwatson> I'm not sure what happened to bug 2; it's not just that it's private or something, it literally doesn't exist
[12:50] <SpecialK|Canon> thanks mup
[12:53] <cjwatson> OK, I think the wheelhouse work has shaved about 40 minutes off our deploy-to-production time.  Not bad
[12:54] <pappacena> Great!
[12:54] <SpecialK|Canon> "not bad" he says
[12:54] <SpecialK|Canon> sounds pretty excellent to me, nicely done
[12:54] <ilasc> :)
[12:54] <cjwatson> (Comparing timestamp differences from the first couple of sections of https://deploy-logs.admin.canonical.com/index/legacy-lp/ndt/2020-02-25-ndt.log and https://deploy-logs.admin.canonical.com/index/legacy-lp/ndt/2020-02-28-ndt.log)
[12:54] <ilasc> I second that!
[12:55] <SpecialK|Canon> Am I right in my reading of that first one being 2h end-to-end?
[12:56] <cjwatson> SpecialK|Canon: Sort of, but bear in mind that it's four steps run in sequence so if the operator isn't paying much attention then that will extend the time
[12:57] <cjwatson> SpecialK|Canon: A fairer comparison is to add the four timedeltas between "Starting <foo> step" and "Ended <foo> step"
[12:57] <SpecialK|Canon> cjwatson: ah thank you
[12:58] <cjwatson> The work I just did takes about 20 minutes off each of the build step (within nodowntime-security-update.sh) and the deploy step (within ./parallel.py --config=lp --options='--push-new-code' --targets='nodowntime')
[12:58] <SpecialK|Canon> I make that about ~45m of gaps, so around 1h15 in the first instance
[12:59] <SpecialK|Canon> Heck even of 2h, 40m is quite a chunk!
[12:59] <SpecialK|Canon> It's only getting more impressive ;)
[15:52] <tomwardill> cjwatson: looks like we'll need to drop the NOT NULL constraint on OCIRecipe.git_path, as well
[15:52] <tomwardill> Snap does the same
[15:56] <cjwatson> tomwardill: Hm, yes, that makes sense
[15:57] <tomwardill> I'll do a DB patch for it
[15:57] <cjwatson> You could get away with a hack to avoid it but it would be gross
[15:58] <cjwatson> tomwardill: Maybe add something like the consistent_git_ref constraint that Snap has while you're there
[15:58] <cjwatson> tomwardill: While it was NOT NULL it wasn't needed, but now it is
[15:58] <tomwardill> ah yeah, makes sense
[16:19] <tomwardill> cjwatson: should/can I reuse the DB patch number from the reverted one? Or best to assign a new one.
[16:19] <tomwardill> Not sure what happens if there's a gap in the run
[16:38] <cjwatson> tomwardill: Reusing is fine in this case since it never went anywhere interesting
[16:38] <tomwardill> cool :)
[16:38] <cjwatson> Just update the description in dbpatches/allocated.txt
[17:22] <tomwardill> cjwatson: https://code.launchpad.net/~twom/launchpad/+git/launchpad/+merge/380038
[17:23] <tomwardill> DB patch, code patch incoming soonish
[17:26] <cjwatson> tomwardill: db=me
[17:27] <tomwardill> gah, pushed code to wrong branch
[17:27]  * tomwardill undoes
[17:38] <tomwardill> matching code, lifting the detachFromGitRepository code into OCIRecipe from Snap https://code.launchpad.net/~twom/launchpad/+git/launchpad/+merge/380039
[17:38] <tomwardill> what I have mostly learnt is that I cannot spell detach reliably.
[17:59] <cjwatson> tomwardill: LGTM, but blocked on the DB patch being rolled out
[18:00] <tomwardill> aye, it's not blocking any of the other OCI work though, so no worries :)
[18:00]  * tomwardill unticks 'git_repository should not be null' on todo list, then ticks it again.
[18:04] <cjwatson> tomwardill: Do you have time for a quick review of https://code.launchpad.net/~cjwatson/lpjsmin/py3/+merge/379696 and/or https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/379996 before you finish up?
[18:04] <tomwardill> sure
[18:07] <tomwardill> cjwatson: +1 to both
[18:10] <cjwatson> Great, thanks
[18:21] <tomwardill> huh, test failures on my DB patch. I definitely ran them, and I definitely had the change applied this time!
[18:22] <cjwatson> Hm, you swapped those two lines in the git_ref setter in your latest code patch
[18:22] <cjwatson> Which of course isn't on db-devel yet
[18:23]  * tomwardill arghs
[18:23]  * tomwardill headdesks
[18:23] <cjwatson> My guess is that you need to land a patch on master that just swaps those lines and nothing else
[18:24] <tomwardill> yeah
[18:24] <cjwatson> Then we'll need to make sure to deploy that to production before rolling out the DB patch
[18:24] <cjwatson> (If we were a larger team this would require backing out the DB patch; as it is I think we can probably cope)
[18:25] <tomwardill> patch incoming
[18:26] <cjwatson> Cool.  I need to finish up soon but I can at least cope with occasionally thwacking buildbot
[18:27] <tomwardill> https://code.launchpad.net/~twom/launchpad/+git/launchpad/+merge/380046
[18:27] <tomwardill> just running tests
[18:28] <cjwatson> r=me
[18:28] <cjwatson> But yeah, will be quickest to confirm that this does fix the db-devel failures before landing
[18:28] <tomwardill> hmm, I should check the tests against the old DB too
[18:29] <cjwatson> I'm not worried about that in this case
[18:29] <cjwatson> But well, maybe worth a try in fact
[18:31] <tomwardill> running now
[18:31] <tomwardill> oh boo, that fails
[18:32] <tomwardill> storm.database.IntegrityError: null value in column "git_path" violates not-null constraint
[18:32] <cjwatson> Ugh
[18:33] <tomwardill> I think backout out the DB patch and doing a two-stage deploy might be safest?
[18:33] <cjwatson> What does the first stage look like, though?
[18:33] <tomwardill> drop the NOT NULL on the git_path
[18:33] <tomwardill> then deploy the code change
[18:34] <tomwardill> then add the constraint
[18:34] <cjwatson> Ah, I see.  A bit elaborate, but at 6:30pm on a Friday I don't have a better plan.
[18:34] <cjwatson> So not really back out - you can just land a change that edits that DB patch in place.
[18:34] <cjwatson> Given that there's nothing on production there's probably some alternative strategy, but let's go with this
[18:34] <tomwardill> how about a revert for the DB patch, given 18:30 friday, etc. Then fix it up next week?
[18:35] <cjwatson> I think it would be fine to back out just the new constraint
[18:35] <tomwardill> so just delete that line from the patch?
[18:35] <cjwatson> DROP NOT NULL on its own is pretty safe.
[18:35] <cjwatson> Yeah
[18:36] <tomwardill> running tests
[18:39] <tomwardill> okay, they passed with both old and new code: https://code.launchpad.net/~twom/launchpad/+git/launchpad/+merge/380048
[18:41] <cjwatson> tomwardill: db=me, thanks
[18:42] <tomwardill> cjwatson: landing, apologies for the late evening mess!
[18:42] <cjwatson> tomwardill: np.  you'll need to force buildbot
[18:43] <cjwatson> wait until you see the change at the left of http://lpbuildbot.canonical.com/waterfall first
[18:43] <tomwardill> on it
[18:45] <cjwatson> Right, mostly gone.  See you in FRA
[18:46] <tomwardill> o/


[00:23] <MarkDude> Hello :)
[13:00] <MarkDude> Hello - anyone active? Should I email the list for a response? :)


[09:40] <sarnl> How to show an exported GMenu in unity?
[17:53] <sgringwe> How do I add menu items to unity hud?
[17:54] <sgringwe> it looks like gtk.application and something with dbusmenu?
[17:55] <sgringwe> i tried using set_menubar on my gtk.application instance with no luck
[18:09] <sgringwe> How do I add menu items to unity hud?
[18:26] <Daekdroom> sgringwe, Just add menus to your application. They'll be available to HUD as long as they're compatible with appmenu.
[18:27] <sgringwe> Daekdroom, and if i don't want a menu bar in my app?
[18:33] <sgringwe> Daekdroom, i guess, what kind of menu are you talking about? a gui menu, dbusmenu?
[18:44] <Daekdroom> sgringwe, A common GUI menu. Whenever appmenu exports it to the top bar (as opposed to the app window), it'll go to the HUD too. I have no idea how to do that without a menu bar in the app, though.


[16:33] <manadart> stickupkid: https://github.com/juju/juju/pull/12309
[16:39] <stickupkid> manadart, looking