[00:14] <Wild_Man> hi Bashing-om fridge and Social Media still need done?
[00:14] <Wild_Man> I think I have access to them on this laptop
[00:15] <Bashing-om> Wild_Man: Yup - None of the Social Media postings have been done.
[00:16] <Wild_Man> Bashing-om, I will see if I have access to the fridge
[00:49] <Wild_Man> http://fridge.ubuntu.com/2020/11/17/ubuntu-weekly-newsletter-issue-657/
[00:51] <Bashing-om> Wild_Man: Fridge: Looks good :D
[01:08] <Wild_Man> Thanks Bashing-om
[01:08] <Bashing-om> Wild_Man: FaceBook - Twitter ?
[01:11] <Wild_Man> kryten will you please pm me the login information for the twitter account I guess I lost it when /my other computer crashed
[01:18] <Wild_Man> Hi guiverc you around? I do not have the info to login into twitter on this computer
[01:22] <guiverc> sorry, didn't realize the day & was more focused in dancing/stamping on towels to dry carpet (hot water heater burst yesterday)...
[01:22] <Wild_Man> Ouch
[01:23] <guiverc> UWN 657 has been tweeted
[01:24] <Bashing-om> \o/ ^
[01:24] <Wild_Man> Thanks guiverc will you please pm me the info to login into twitter
[02:14] <Bashing-om> Wild_Man: guiverc: FaceBook get posted ?
[02:14] <Wild_Man> Bashing-om, yes
[02:14] <guiverc> :)  thanks Wild_Man
[02:15] <Wild_Man> You're welcome guiverc
[02:15] <Bashing-om> Wild_Man: guiverc: Clear now to make back Gdoc history ?
[02:15] <guiverc> yep
[02:16] <Wild_Man> Bashing-om, yes
[02:16] <Bashing-om> Making it so then :P
[02:23] <Bashing-om> UWN: We do issue 658 :D


[05:02] <DalekSec> With regards to https://discourse.ubuntu.com/t/renewal-of-ubuntu-forums-council/14152, I don't suppose there's a way to see if they can renew themselves?  https://launchpad.net/~forum-council/+members shows that none of them are admins at least.
[11:06] <cjwatson> DalekSec: That team's renewal policy is set to "invite them to apply for renewal" (i.e. no self-renewal), so no.  But I've answered on the discourse thread.
[17:29] <DalekSec> cjwatson: Thank you very much.
[18:45] <teward> cjwatson: wgrant: are PPA builds for trusty disabled or still enabled, given Trusty is EOL and in just ESM only now?
[18:50] <DalekSec> Enabled still, as is precise I believe.


[08:13] <dholbach> good morning
[08:14] <MooDoo> morning :)
[15:58] <smoser> o/
[15:58] <adam_g> o/
[16:00] <jamespage> o/
[16:00] <hallyn> \o
[16:00] <hallyn> all right let's get going
[16:00] <hallyn> #startmeeting
[16:00] <meetingology> Meeting started Tue Dec  3 16:00:34 2013 UTC.  The chair is hallyn. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:00] <hallyn> [TOPIC] Review ACTION points from previous meeting
[16:00] <hallyn> Previous meeting minutes at: https://wiki.ubuntu.com/MeetingLogs/Server/20131126
[16:01] <hallyn>  ?
[16:01] <hallyn> what as that about?
[16:01] <hallyn> i'll assume it's a mistake and move on,
[16:01] <hallyn> smoser sync with utlemming on building cloud images for alpha 1, targets = seed-review, gpt
[16:01] <smoser> hm... utlemming ^ ?
[16:01] <smoser> lets mark that done, and i'll do it now.
[16:02] <hallyn> ok
[16:02] <hallyn> jamespage do seed-review email
[16:02] <hallyn> saw it on the list i think
[16:02] <hallyn> jamespage, gaughen review blueprints and accept for trusty
[16:02] <utlemming> hallyn: cloud images will have an alpha 1
[16:02] <gaughen> hallyn, we did that yesterday, it's partially done
[16:02] <hallyn> ok, won't renew the action item then, thanks
[16:02] <hallyn> gaughen file bug with status.u.c to get ubuntu server topic tracking in there
[16:03] <gaughen> not done
[16:03] <hallyn> [ACTION] gaughen file bug with status.u.c to get ubuntu server topic tracking in there  (carry over)
[16:03] <meetingology> ACTION: gaughen file bug with status.u.c to get ubuntu server topic tracking in there  (carry over)
[16:03] <hallyn> thanks
[16:03] <hallyn> all: write up blueprints, and have them ready for review by November 28
[16:03] <hallyn> were we all good boys and girls?
[16:04] <gaughen> smoser?
[16:04] <gaughen> were you a good boy?
[16:04] <smoser> never
[16:04] <gaughen> lol
[16:04] <smoser> but i have 1 of 3 done-ish.
[16:04] <smoser> i will work on others.
[16:04] <hallyn> well deadline passed so wwon't renew that :)
[16:04] <hallyn> moving on,
[16:04] <hallyn> [TOPIC] T Development Opening
[16:04] <gaughen> based on our review yesterday, we do have updates for some folks to make to the blueprints
[16:04] <hallyn> who wants to take this?
[16:04] <gaughen> and of course smoser
[16:05] <hallyn> jamespage: arosales: ^
[16:05] <arosales> #link https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[16:05] <jamespage> hallyn, sure
[16:06] <jamespage> so start-ish of cycle still
[16:06] <jamespage> get those blueprints updated as per gaughen's feedback
[16:06] <jamespage> but not looking to bad
[16:06] <arosales> Dec 19 for Alpha 1 which sounds like utlemming is going to cut a cloud image for
[16:06] <jamespage> sensible BP's for an lts
[16:06] <hallyn> ok, thanks - moving on
[16:06] <jamespage> merges and syncs still important focus right now - we need to get version bumps in early as possible
[16:07] <hallyn> ah.  where is the url with theh list of not-done merges/syncs?
[16:07] <jamespage> everyone should know about 'grep-merges' - its easier than going to merges.ubuntu.com
[16:08] <hallyn> hm,  ok
[16:08] <hallyn> [TOPIC] Server & Cloud Bugs (caribou)
[16:08] <jamespage> hallyn, I think rbasak did some work on a server focussed merge report but I don't know where that lives
[16:08] <hallyn> jamespage: do you want an action for ppl to look at merges?
[16:08] <jamespage> yes please
[16:09] <hallyn> [ACTION] everyone look at grep-merges output and merge/sync as much and early as possible
[16:09] <meetingology> ACTION: everyone look at grep-merges output and merge/sync as much and early as possible
[16:09] <hallyn> jamespage: thanks
[16:09] <hallyn> caribou is not here
[16:09] <hallyn> does anyone else want to say anything about server/cloud bugs?
[16:09] <hallyn> going once,
[16:09] <jamespage> hrm
[16:09] <jamespage> I know one that is hitting caribou and his guys right now
[16:10] <jamespage> bug 1241674
[16:10] <hallyn> that is appropriate to discuss here?
[16:10] <jamespage> yeah - it is
[16:10] <hallyn> carry on :)
[16:10] <jamespage> I poked the upstream owner on that one
[16:10] <jamespage> he's promised to update the bug report
[16:10] <jamespage> with details on plans etc...
[16:11] <hallyn> i don't see a link to upstream bug... who is the owner?
[16:11] <hallyn> anyone here?
[16:12]  * arosales is here
[16:12] <hallyn> ok, moving on
[16:12] <hallyn> [TOPIC] Weekly Updates & Questions for the QA Team (psivaa)
[16:12] <hallyn> psivaa is not here
[16:12] <arosales> hallyn, is that re bug 1241674 ?
[16:12] <hallyn> arosales: yes
[16:12] <hallyn> arosales: are you the upstream bug owner? :)
[16:13] <jamespage> hallyn, mgz
[16:13] <jamespage> sorry
[16:13] <arosales> looks like jamespage filed :-)
[16:13] <arosales> and there he is
[16:13] <jamespage> mgz is the upstream owner
[16:14] <hallyn> ...  do you want an action for yourself relating to this?
[16:14] <hallyn> (or anyone else...)
[16:14] <arosales> and 1241674 is the upstream bug
[16:14] <hallyn> arosales: then why isn't mgz marked as owner?
[16:14] <arosales> jamespage, any action for ubunt server here?
[16:14] <jamespage> no its all upstream right now
[16:14] <arosales> hallyn, task is out for juju-core
[16:15] <hallyn> ok, thanks.
[16:15] <hallyn> [TOPIC] Weekly Updates & Questions for the Kernel Team (smb)
[16:15] <smb> I don't have anything to report this week. Are there issues or questions?
[16:15] <hallyn> smb: hi
[16:15] <jamespage> hallyn, no - it was just pertient to carbous section
[16:15] <hallyn> jamespage: ok, thanks
[16:15] <hallyn> anyone have a question for smb?
[16:15] <arosales> jamespage, juju will mostly likely land that in trusty
[16:16] <hallyn> smb: thanks :)
[16:16] <hallyn> [TOPIC] Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:16] <smb> hallyn, welcome :)
[16:16] <hallyn> rbasak is not here,
[16:16] <hallyn> [TOPIC] Ubuntu Server Team Events
[16:17] <hallyn> A big merge+sync irc party perhaps?
[16:17] <hallyn> Woohoo!  Meeerggeeee
[16:17] <hallyn> guess not, moving on
[16:17] <hallyn> [TOPIC] Open Discussion
[16:18]  * hallyn leaves this open for a minute
[16:18]  * smoser applauds hallyn's frat-boy excitement over a merge party.  and quickly puts on his toga.
[16:18] <smoser> i'd say for open discussion...
[16:18] <hallyn> toGA toGA MERGE MERGE SYNC
[16:19] <smoser> please see Jamespage's mail
[16:19] <hallyn> topic?
[16:19] <jamespage> smoser, mail?
[16:19]  * smoser searches for link
[16:19] <smoser> oh wait. i thought you had sent one.
[16:19] <jamespage> I've not sent the one about seed package review yet - sorry being slack on that
[16:19] <smoser> yeah, that one
[16:19] <smoser> :)
[16:19] <jamespage> today
[16:19] <hallyn> ooh...  do we need a new action item?
[16:19] <smoser> so, after jamespage mails it with a timestamp in the past, please read at
[16:20] <smoser> https://lists.ubuntu.com/archives/ubuntu-devel/2013-December/thread.html
[16:20] <hallyn> sorry i thought i'd seen the email on that!
[16:20] <hallyn> but i guess that was irc
[16:20] <smoser> probably you saw http://pad.ubuntu.com/server-seed-review
[16:20] <hallyn> [ACTION] jamespage to send email on server seed [carry over]
[16:20] <meetingology> ACTION: jamespage to send email on server seed [carry over]
[16:20] <hallyn> right
[16:21] <hallyn> ok, then
[16:21] <hallyn> [TOPIC] Announce next meeting date, time and chair
[16:21] <hallyn> Next meeting will be Tuesday Dec 10 at 16:00 UTC
[16:21] <arosales> hallyn, thanks for chairing
[16:21] <hallyn> smoser chairing
[16:21] <hallyn> thanks everyone
[16:21] <hallyn> #endmeeting
[16:21] <meetingology> Meeting ended Tue Dec  3 16:21:47 2013 UTC.
[16:21] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-12-03-16.00.moin.txt
[16:21] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-12-03-16.00.html
[16:22] <jamespage> thanks hallyn
[16:59] <jsalisbury> #startmeeting
[16:59] <jsalisbury> ##
[16:59] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[16:59] <jsalisbury> ##
[16:59] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[16:59] <meetingology> Meeting started Tue Dec  3 16:59:42 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:59] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:59] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Trusty
[16:59] <jsalisbury> # Meeting Etiquette
[16:59] <jsalisbury> #
[16:59] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[16:59] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[16:59] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[16:59] <ppisati> o/
[16:59] <henrix> o/
[16:59] <sforshee> o/
[17:00] <cking> o/
[17:00] <rtg> o/
[17:00] <bjf> o/
[17:00] <smb> \o
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing new to report this week
[17:01] <ppisati> ..
[17:01] <jsalisbury> Incoming
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-t/canonical-kernel-distro-team.html
[17:01] <ogasawara> First, a big thank you to apw for wrestling our kernel related
[17:01] <ogasawara> blueprints and work items into place to make the above links useful
[17:01] <ogasawara> again.  Our work items and owners are as follows:
[17:01] <ogasawara> || apw       || core-1311-kernel                || 5 work items ||
[17:01] <ogasawara> ||           || core-1311-cross-compilation     || 3 work items ||
[17:01] <ogasawara> ||           || core-1311-hwe-plans             || 1 work item  ||
[17:01] <ogasawara> ||           || core-1311-secure-boot           || 1 work item  ||
[17:01] <ogasawara> || bjf       || core-1311-dmraid2mdadm          || 1 work item  ||
[17:01] <ogasawara> || cking     || core-1311-kernel                || 2 work items ||
[17:01] <ogasawara> || ogasawara || core-1311-kernel                || 4 work items ||
[17:01] <ogasawara> ||           || client-1311-xorg-general        || 1 work item  ||
[17:01] <ogasawara> || smb       || core-1311-dmraid2mdadm          || 1 work item  ||
[17:01] <ogasawara> ||           || servercloud-1311-openstack-virt || 5 work items ||
[17:01] <ogasawara> || rtg       || core-1311-hwe-plans             || 1 work item  ||
[17:02] <ogasawara> ||           || core-1311-kernel                || 1 work item  ||
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Trusty Development Kernel (ogasawara)
[17:02] <ogasawara> The master branch for trusty has been rebased to the latest v3.12.2
[17:02] <ogasawara> upstream stable kernel.  We also continue to track the latest v3.13
[17:02] <ogasawara> kernel on our unstable branch and most recently rebased to v3.13-rc2.
[17:02] <ogasawara> Again, we shall switch our master branch from tracking v3.12 to v3.13
[17:02] <ogasawara> once we cycle through the initial -rc's and feel it is stable enough for
[17:02] <ogasawara> wider consumtion, ie uploaded to the archive.
[17:02] <ogasawara> -----
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara> [LINK] https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[17:02] <ogasawara> Thurs Dec 19 - Alpha 1 (~2 weeks away)
[17:02] <ogasawara> Thurs Jan 23 - Alpha 2 (~7 weeks away)
[17:02] <ogasawara> [LINK] https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[17:02] <ogasawara> Thurs Dec 12 - 12.04.4 Kernel Freeze (~1 week away)
[17:02] <ogasawara> Thurs Jan 23 - 12.04.4 Final Release (~7 weeks away)
[17:02] <ogasawara>  * NOTE: Even though the kernel freeze date for 12.04.4 is Dec 12,
[17:02] <ogasawara>          patches needed to have landed in the SRU cadence starting
[17:02] <ogasawara>          this week to make the 12.04.4 point release.  Contact us
[17:02] <ogasawara>          *immediately* if there are patches which need to land.
[17:02] <ogasawara>          https://lists.ubuntu.com/archives/kernel-team/2013-November/034753.html
[17:02] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's
[17:03] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:03] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <jsalisbury> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Saucy/Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:03] <bjf> Status for the main kernels, until today (Nov. 26):
[17:03] <bjf>   *   Lucid - Prep'ing
[17:03] <bjf>   * Precise - Prep'ing
[17:03] <bjf>   * Quantal - Prep'ing
[17:03] <bjf>   *  Raring - Prep'ing
[17:03] <bjf>   *   Saucy - Prep'ing
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:04] <jsalisbury> #endmeeting
[17:04] <meetingology> Meeting ended Tue Dec  3 17:04:20 2013 UTC.
[17:04] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-12-03-16.59.moin.txt
[17:04] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-12-03-16.59.html
[17:04] <kamal> thanks jsalisbury


[01:24] <ChinnoDog> I don't see any links to a map with you on it.
[01:48] <waltman> Nor do I
[01:49] <waltman> In fact, it says you're currently in San Francisco.
[01:55] <pleia2> oh, maybe it's only viewable to me
[01:55]  * pleia2 sees about fixing this
[01:57]  * waltman is grumpy about his laundry tonight
[01:58] <pleia2> there we go
[01:58] <waltman> Where should we be looking for this?
[01:59] <pleia2> https://plus.google.com/+ElizabethKrumbachJoseph/posts
[01:59] <pleia2> under my name
[01:59] <pleia2> if you're logged in
[01:59] <pleia2> won't let me show it to the whole not logged in world, annoying
[02:00] <waltman> Under your name all it says is "Lives in San Francisco"
[02:00] <pleia2> are you logged in to g+?
[02:00] <waltman> Yup
[02:00] <pleia2> maybe it's being laggy
[02:01] <pleia2> works between my accounts (elizabethkjoseph can see elizabethkrumbachjoseph)
[02:01]  * pleia2 shrugs
[02:03] <waltman> What should I be seeing?
[02:04] <pleia2> Currently in Raleigh, NC, USA
[02:04] <waltman> aha, there it is!
[02:04] <pleia2> rather than where I live
[02:04] <pleia2> :)
[02:04] <pleia2> if you're my g+ friend, you get more precise data when you mouse over the city name
[02:04] <waltman> I had to force-reload the page
[02:05] <pleia2> except the location is wrong, so whatever :)
[02:05] <pleia2> social media is ahrd
[02:05] <pleia2> hard
[02:05] <waltman> You know the game starts 3 hours earlier here, right? :)
[02:06] <pleia2> yeah, I was at the speakers dinner when it started :(
[02:06] <waltman> http://www.smbc-comics.com/index.php?db=comics&id=3520
[02:06] <pleia2> made it just in time for the first run of the game last night (my flight was delayed)
[02:07] <pleia2> er, 3 hours *later*!
[02:07] <pleia2> 5pm at home
[02:09] <pleia2> also, HP is killing me, wearing blue at this conference arrgggh
[02:14] <waltman> When you become president of HP, your first act should be to change the corporate color to pink!
[02:15] <pleia2> ++
[02:15] <pleia2> they asked me if I wanted some custom polos and I said "can they be pink?" "no"
[02:15] <ChinnoDog> HP logo in pink. I can't wait to see it.
[02:15]  * pleia2 shut down
[02:16] <pleia2> only blue
[02:16] <waltman> Not many other companies use pink as their official corporate color, so your engineers will be easily picked out in a crowd.
[02:16] <pleia2> there's t-mobile
[02:16] <waltman> Do they make servers?
[02:16] <waltman> Or printer/calculators?
[02:16] <pleia2> no, but HP Enterprise won't either :)
[02:17] <waltman> Oh well, I'm sure HP pink will be a much nicer shade than T-Mobile pink.


[03:40] <lifestream> Could someone recommend a program, besides GIMP and Pinta, that is good for... digital painting?
[03:40] <lifestream> Photoshop is expensive:P
[03:40] <lifestream> (and sadly doesn't work with wacom, on linux, if I use layers :P)
[03:43] <lifestream> Basically use paintbrush and smudge a lot, and need layers, preferably doesn't use Mono *gag*
[03:58] <ScottL> lifestream, krita is good for digital painting i believe
[03:59] <ScottL> http://www.koffice.org/krita/
[03:59] <lifestream> Krita ? :P Hmm...:-) I'll try
[04:00] <lifestream> I also just found Alchemy, MyPaint
[04:02] <ScottL> krita is a KDE application, so it will bring in a lot of KDE libraries, which may mean something to you if you are running gnome, maybe not
[04:02] <lifestream> Using openbox
[04:03] <lifestream> But have VLC installed, so a bunch of libraries might already be installed
[04:05] <lifestream> Also found Artweaver :P Didn't know there were so many choices
[04:07] <lifestream> Oops, no Artweaver is windows.  Gee so many new choices *tries them*
[08:44] <rlameiro> good morning
[08:54] <rlameiro> hello AutoStatic
[08:54] <AutoStatic> good morning rlameiro
[12:07] <MobiusJedi> I love gmusicbrowser!
[13:19] <rlameiro> MobiusJedi: it apears a nice app
[19:18] <Kransac> Hi everyone
[19:18] <_pg_> hello!
[19:18] <Kransac> I've just installed ubuntu studio for the first time yipiii!
[19:18] <_pg_> does anyone know the upgrade path for 9.10 x64 studio to Lucid? will there be problems with the RT kernel? I hear lucid doesnt have rt kernel.
[19:19] <holstein> _pg_: i suggest trying the generic kernel
[19:19] <_pg_> holstein: how do I do that?
[19:19] <holstein> iv e heard the latency is great
[19:20] <holstein> you can always add the RT on later if necessary
[19:20] <_pg_> holstein: let me back up. why do I even want an rt kernel?
[19:20] <holstein> _pg_: low-latency
[19:20] <_pg_> holstein: is that only used in audio?
[19:20] <holstein> if your not doing audio recording
[19:20] <_pg_> holstein: or just quicker all around?
[19:20] <holstein> you probably wont need it
[19:20] <holstein> nah, not quicker
[19:20] <tucemiux> _pg_, youll probably be able to upgrade the usual way or burn the ISO and get a fresh install
[19:21] <_pg_> holstein: where do I choose what kernel? at login?
[19:21] <holstein> different priorities
[19:21] <holstein> _pg_: in lucid, the grub menu is hidden
[19:21] <holstein> check out
[19:21] <holstein> !grub2
[19:21] <holstein> you can probaly just press escape
[19:21] <holstein> and get to the grub menu
[19:21] <Kransac> I have an Edirol FA-66 audio card. Do you know how I can see if it's recognized by the system?
[19:21] <furenku> does anybody now what's gonna happen with the rt kernel in lucid?
[19:22] <furenku> since it's not being supported in ubuntu
[19:22] <holstein> BUT upgrading should be find _pg_ , and you should get the generic kernel AFAIK
[19:22] <_pg_> holstein: thanks! will try
[19:22] <holstein> furenku: the word is RT is not default
[19:22] <holstein> but in the repos
[19:22] <holstein> furenku: you should try the generic one though first
[19:23] <furenku> holstein: thanx, but i already did, and i'm getting quite a lot of xruns
[19:23] <holstein> furenku: OH
[19:23] <furenku> even with a high latency, that's why. but i'm not being able to boot into a newly installed rt kernel
[19:23] <holstein> well, try the RT one
[19:23] <holstein> did you install it?
[19:24] <holstein> linux-rt?
[19:24] <furenku> holstein, i'm trying to try it lol i'm however too blind to understand how to boot into it
[19:24] <holstein> OK
[19:24] <holstein> check out
[19:24] <furenku> holstein, i mean, i understand grub2
[19:24] <holstein> hmm
[19:24] <furenku> but any changes i make in /default/grub seem to no avail
[19:24] <holstein> you dont see the menu when you boot?
[19:24] <furenku> not at all
[19:25] <furenku> do you know how to enable that?
[19:25] <holstein> try pushing escape
[19:25] <furenku> that'd be great help
[19:25] <furenku> ok
[19:25] <holstein> when you think you should see it
[19:25] <holstein> now that i think about it
[19:25] <holstein> i have the same issue on my EEE
[19:25] <furenku> do you know any other way of enabling it other than that?
[19:25] <holstein> in lucid
[19:25] <holstein> i did what i thought would un-hide it
[19:25] <holstein> and it didnt
[19:25] <holstein> and the escape trick works for me
[19:26] <holstein> after that, i forgot it was an issue
[19:26] <holstein> furenku: we should look for a bug on launchpad
[19:26] <furenku> ok i'll retry it now, i'll come back and let you know what happened
[19:26] <furenku> holstein, thats a good idea
[19:27] <holstein> i had a couple of nasty bugs, and i just forgot about that one
[19:28] <holstein> BIAB guys...
[19:28] <furenku> what's biab btw?
[19:30] <furenku> _pg_ so, just gonna try rebooting into rt kernel, i found a tool called startupmanager that seems to help choose which kernel to boot to in grub2, i'll let ya know
[19:30] <_pg_> furenku: please do
[19:30] <_pg_> furenku: preciate it
[19:54] <furenku> _pg_: i'm now running 10.04 lucid with -rt kernel, firewire audio seems to be running ok (i'll let it playing for some minutes and see what happens -- till now no XRuns).
[19:54] <holstein> furenku: W00t
[19:54] <holstein> good news
[19:54] <furenku> holstein, yes.
[19:56] <furenku> holstein, to be able to boot into -rt kernel , you have to modify /etc/default/grub to have the following in the first line: GRUB_DEFAULT="Ubuntu, with Linux 2.6.31-10-rt"
[19:56] <furenku> changing the GRUB_DEFAULT to a number strangely did not work at all
[19:56] <_pg_> furenku: awesome blossom. Im tackling that a different day, but will come back here when I inevitably run into issues! ;-]
[19:56] <furenku> oh! forgot to say. first you have to apt-get install linux-rt
[19:56] <furenku> lol
[19:57] <_pg_> furenku: but if im not using audio production, just upgrading normally I can use the defaiut kernel with no modifying correct?
[19:57] <furenku> oh, if you're not interested in the rt kernel then there's no problems at all
[19:57] <furenku> hahha
[19:57] <holstein> _pg_ is upgrading from karmic
[19:57] <holstein> running the RT kernel right now
[19:58] <holstein> BUT i think you'll get the default lucid set-up
[19:58] <_pg_> furenku: someone led me to believe that RT>not RT like x64>x32 for just raw speed
[19:58] <_pg_> *slams face into computer*
[19:58] <_pg_> that was a nightmare
[19:58] <holstein> _pg_: that upgrade will take quite a while
[19:58] <_pg_> holstein: ok what is the syntax?
[19:59] <_pg_> holstein: sudo apt-get upgrade ubuntu-studio-desktop-x64 or something
[19:59] <helo> can I install ubunstu on a thumb drive from the dvd?
[20:00] <holstein> i use sudo apt-get update && sudo apt-get dist-upgrade
[20:00] <_pg_> helo: yezzir. ubuntu startup disk creator
[20:00] <_pg_> holstein: all one loine?
[20:00] <_pg_> line*
[20:00] <holstein> but i think you can run update-manager -d or something like that
[20:01]  * holstein looks
[20:02] <helo> i have no dvd drive, so i will try to install it through virtualbox...
[20:02] <holstein> helo: ive had issues with that
[20:02] <helo> well, no blank dvd ;)
[20:02] <helo> oh... hmmm
[20:03] <holstein> using unetbootin to create a bootable ubuntustudio install USB stick
[20:03] <holstein> any iso with the alternate text installer
[20:03] <holstein> seems to fail when locating the image
[20:03] <holstein> i have a USB DVD drive, so i havent been motivated to find a work around
[20:04] <holstein> yeh _pg_ , update-manager -d
[20:04] <holstein> that will lauch the normal update manager
[20:05] <holstein> and show a distribution upgrade available
[20:05] <holstein> helo: you can install from a normal lucid live CD
[20:05] <holstein> and add the ubuntustudio meta-packages
[20:05] <helo> ahhhh, perfect... thanks :)
[20:06] <helo> will that set up jackd, qjackctl, and amsynth?
[20:06] <holstein> https://help.ubuntu.com/community/Ubuntu%20Studio%20Upgrade%20from%20Ubuntu
[20:06] <holstein> helo: it will install them
[20:06] <holstein> 'set-up' is a matter of opinion ;)
[20:07] <holstein> depends on your gear really
[20:07] <holstein> helo: you dont need all the ubuntustudio packages really
[20:07] <helo> heh... i've been using jackd without -rt with passable results for practicing (just a usb 88-key midi controller that i'm learning on), but occasionally i get some clicks and pops
[20:08] <holstein> you can just install jack and whatever else you need
[20:08] <helo> on an intel atom
[20:08] <holstein> helo: COOL
[20:08] <helo> the main thing i'd like to try is a -rt kernel
[20:08] <holstein> is that a generic kernel in karmic?
[20:08] <helo> actually it's debian sid, but yes: just the generic kernel
[20:09] <holstein> you can probaly just sudo apt-get install linux-rt
[20:09] <holstein> BIAB
[20:10] <helo> it would be great if i could get my netbook to run well... my midi controller is usb powered, so it is a relatively portable setup
[20:26] <tucemiux> helo, did you install ubuntustudio on your netbook already?
[20:38] <helo> tucemiux: nope, only debian sid
[20:39] <helo> i'm going to try my thumb drive with ubuntu beta2 with linux-rt
[20:39] <helo> that should give similar results
[20:40] <tucemiux> helo, try netbook remix, goo luck!
[21:37] <atok> Hi!
[21:38] <atok> Whats with Ubuntu Studio Karmic login screen ?
[21:38] <atok> why its so ugly ?
[21:38] <atok> how can i install login screen from Hardy ?


[00:18] <teward> rbasak: uhm, who looks after the perl autopkgtests
[00:18] <teward> because there's some nasties in there holding up Perl, and we need that to get out of proposed, or forcibly bypass that, before we can actually test the merge, etc.
[00:18] <teward> because i need to rebuild if we've bumped Perl at all
[07:27] <b3h3m0th> How do I: Lock user for X seconds after Y consecutive failed login attempts within a time windows of Z seconds.
[07:27] <b3h3m0th> Using PAM ?
[07:30] <sarnold> b3h3m0th: I think pam_tally2 is probably the way to get there
[07:30] <b3h3m0th> I tried tally but could not figure out a way to specify the Z param
[07:30] <b3h3m0th> *tally2
[07:31] <b3h3m0th> pam_faillock,  a redhat patch does support this using a fail_interval param. But  unfortunately for me ubuntu does not ship it :(
[07:41] <b3h3m0th> fail_interval=n: The length of the interval during which the consecutive authentication failures must happen for the user account lock out is n seconds. The default is 900 (15 minutes).
[07:41] <b3h3m0th> ^ This is what I'm actually looking for. [source: https://linux.die.net/man/8/pam_faillock]
[07:42] <b3h3m0th> I want a user to be able to try to login (Y-1) times every Z seconds indefinitely without lockout.
[08:56] <zioproto> hello all. Just starting a trusty to xenial do-release-upgrade on a server running glance-api and glance-registry. Openstack version MItaka. Any specific Openstack advice ? It is a staging system so relax :)
[09:47] <aaran> Hi, what is the name of the service that lets you book out time slots on a server for computation? I thought it was time sharing but thats from the olden days of mainframes
[09:49] <aaran> any ideas?
[09:54] <aaran> hmm think I found it job scheduling
[09:54] <rbasak> aaran: are you thinking about stuff like https://en.wikipedia.org/wiki/TORQUE_Resource_Manager ?
[09:55] <rbasak> It's more of an HPC thing.
[09:56] <rbasak> Also Slurm
[09:57] <aaran> basically we have a gpu server that a bunch of staff would like to run jobs on and its a system to book time to use the machine
[09:59] <aaran> its a single server so I dont think that slrum would be needed as that seems to be for clusters?
[10:07] <rbasak> For a single server, why not just use a shared calendar and trust?
[10:08] <aaran> because of students and their inability to stick to a schedule
[10:08] <aaran> But its an idea, thanks I will pitch the idea and wait to see what comes of it
[10:10] <caribou_> rbasak: jgrimm: FYI I have just synced clamav. The only remaining part will be to get the MIRed tomsfastmath in
[10:10] <cpaelzer> aaran: from my experience with similar - unfortunately not FOSS - solutions after the initial setup of getting hard schedules everybody complains about wasting so much time
[10:11] <cpaelzer> aaran: if you go for calendar+trust doe it as calendar+trust+communication; nothing is as bad as killing a 8 hour job 5 minutes before it completes :-)
[10:11] <cpaelzer> aaran: if you go for any sort of automation, make it a prio or credit based system with seme tolerance before killing runnign jobs
[10:12] <rbasak> For hard (no trust needed) schedules, I wonder if MAAS could help. It has an API, so you could automatically redeploy and give access to a scheduled user every time the scheduled user changes.
[10:12] <rbasak> Not too much scripting.
[10:12] <rbasak> Perhaps way overkill though (over using trust).
[10:12] <aaran> hhmm
[10:12] <cpaelzer> also chargeback (no matter how small) helps tremendously to get the people to keep their work fast and efficient
[10:14] <aaran> not sure if chargeback would be feasible
[10:14] <cpaelzer> doesn't have to be money
[10:15] <cpaelzer> if you implement something time credit based just lower that in case one overruns
[10:15] <cpaelzer> makes things much more self regulating
[10:15] <cpaelzer> but well over-engineering s at stake - start with calendar+trust and see where you get
[11:10] <joelio> any idea how https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-8743.html is getting on, appreciate it's medium risk
[11:15] <rbasak> joelio: try asking in #ubuntu-hardened.
[11:16] <rbasak> (it's also quite early for the Americas so you might not get an answer straight away)
[11:17] <joelio> rbasak: no worries, it's just on my list of things to keep an eye on, no biggie :)
[11:48] <cpaelzer> nacc: I think I debugged and understood the pg-repack issue, if you could trigger to re-run the postgres dep8s that would be nice
[11:48] <cpaelzer> nacc: from https://bileto.ubuntu.com/excuses/2470/yakkety.html that would be
[11:49] <cpaelzer> nacc: and actually the postfix tests and not the postgres ones
[11:49] <cpaelzer> pitti confirmed in the bug that these might just be flaky and worth a re-trigger
[12:57] <zioproto> regarding openstack packaging for glance the trusty to xenial upgrade was painless
[12:57] <zioproto> I am using the standard xenial mitaka packages
[13:16] <zioproto> Finally some interesting problem. I guess all puppet+openstack people will run soon into this https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472
[13:24] <zioproto> jamespag`, coreycb this bug is not assigned on Xenial, there is PPA that fixes the problem. Before we have a bunch of Openstack people having this problem, how can we make sure this gets assigned for review and merge in Xenial ??? thanks https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472
[14:39] <cpaelzer> coreycb: FYI the machine type fixes just passed the unapproved queue
[14:40] <cpaelzer> coreycb: I'll ping again when they built, tested and I'mabout to mark as verification done
[14:41] <coreycb> cpaelzer, ok thanks
[14:59] <lucidguy> Looks like if you want Nagios4 on Ubuntu 16.04 you have to build from source.. not on any reputable repo?
[15:16] <rbasak> lucidguy: yeah I don't think Nagios 4 is packaged in Debian or Ubuntu.
[15:19] <lucidguy> rbasak: I'm trying to decide if I should stick with v3 from repo or go and build v4
[15:21] <rbasak> I don't know enough to answer that question, sorry.
[15:56] <teward> cpaelzer: thanks for your testing, I appreciate the rapidity of your getting those tests done :)
[15:56] <teward> cpaelzer: thanks for your testing, I appreciate the rapidity of your getting those tests done :)
[15:56] <teward> cpaelzer: did you see anything that would otherwise be considered "bad" in the package?  (My brain isn't fully awake, I need another 3 coffees lol)
[16:00] <cpaelzer> teward: I did not do packaging review yet
[16:00] <cpaelzer> teward: didn't realize I should
[16:00] <teward> cpaelzer: nah, it's all good, i meant as "Anything odd introduced in the logs"
[16:00] <teward> packaging review I'm confident is fine, base Debian + our delta
[16:00] <cpaelzer> teward: from the "package user side" it appeared good to me
[16:00] <teward> and we were able to drop a few things.
[16:00] <teward> cpaelzer: yeah that's the primary tests I was after
[16:01] <teward> package review, I'm confident it's fine, because it's pretty much base Debian package + nginx-core specific things + build compat. fix for fPIE/fPIC that seems to be ubuntu specific + apport hooks
[16:02] <teward> nginx in Debian just uploaded 1.10.3-1 recently so it's not able to be pulled yet for merging, but it shouldn't be more than packaging changes.
[16:02] <teward> i'll check that tomorrow, until then I'm going to push this up because I'd *love* to get this in before FeatureFreeze
[16:02] <teward> we can FFe request for any packaging-specific changes that aren't 'new features'
[16:03] <teward> first, food, 'cause I haven't eaten all morning
[16:10] <joelio> lucidguy: considered Icinga2 ?
[16:25] <cpaelzer> rbasak: can you hit the importer on exim4 and logwatch for me - I'd like to consider feasibility of a re-merge before FF
[16:27] <jgrimm> cpaelzer, thanks!  cpaelzer btw, i suggested that you be added to the importer team
[16:28] <cpaelzer> jgrimm: I had hoped to annoy rbasak often enough that he does so on his own at some point :-)
[16:28] <jgrimm> heheh
[16:28] <rbasak> Running
[16:28] <cpaelzer> thanks
[16:29] <cpaelzer> jgrimm: btw I escaped the libvirt abstraction hell, libvirt-python binding to the rescue
[16:29] <jgrimm> rbasak, since you are at it.  autofs and libqb would be handy to import too.
[16:29] <lucidguy> joelio: no, boss asked for Nagios
[16:29] <jgrimm> cpaelzer, \o/
[16:30] <rbasak> cpaelzer: done. I think they were no-ops. The automatic importer is working maybe?
[16:40] <rbasak> nacc: OK to push obviously-correct minor usd bugfixes straight to master?
[16:41] <teward> rbasak, cpaelzer, jgrimm, powersj: NGINX merge uploaded to proposed.  Faster than my initial timeline was yesterday.  :)
[16:41] <rbasak> teward: \o/
[16:41] <rbasak> Thank you!
[16:41] <jgrimm> teward, \o/
[16:41] <teward> might need another one as an FFe for 1.10.3-1 from Debian (additional packaging changes)
[16:41] <teward> but hey *that* merge we get to drop a delta xD
[16:42] <rbasak> nacc: never mind. It's a bug in my pending branch. Not even in master!
[16:43] <teward> rbasak: those local branch/tree bugs are pesky and annoying, aren't they :P
[16:43] <rbasak> :-)
[16:43] <rbasak> Nice to get the bugs ironed out before I propose a merge :)
[16:45] <nacc> rbasak: ack on bugs
[16:45] <nacc> cpaelzer: i think pitti got those retriggered?
[16:46] <rbasak> jgrimm: autofs done (no-op?)
[16:46] <rbasak> jgrimm: libqb running (looks like an import from the beginning)
[16:49] <teward> rbasak: eheh, look at all the "NEW" in the queue xD  https://launchpad.net/ubuntu/zesty/+queue
[16:49] <teward> (for nginx)
[16:50] <teward> (translations)
[16:56] <jgrimm> rbasak, thanks! and thanks!
[16:56] <nacc> jgrimm: fyi, new dogtag-pki is being synced over and built now, then various tests should rekick or i will manually as neccessary
[16:56] <jgrimm> nacc, thanks
[16:57] <nacc> jgrimm: re: openvpn, can i reject the old merge request?
[16:58] <nacc> jgrimm: MP: #316337
[16:58] <jgrimm> nacc, yep i only left it around for you to refer back to
[16:58] <nacc> jgrimm: ack, will close once i merge the new one
[16:58] <jgrimm> since i'd uploaded a new branch. thanks sir
[16:58] <nacc> jgrimm: 317004 is current?
[16:59] <jgrimm> nacc, yes
[17:02] <coreycb> zul, i'm working on testing a cherry-pick of this to nova: https://review.openstack.org/#/c/431582/
[17:04] <GPenguin> hello, i am interested in the wordpress package on ubuntu 16.04. server edition
[17:05] <GPenguin> the readme in /usr/share/doc/wordpress is ... uhm... well, a bit rusty?
[17:05] <GPenguin> i see the mysql server itself is not installed. and the doc speaks about a password which i never set
[17:06] <GPenguin> is there a more detailed and more up to date version of the documentation out there?
[17:07] <nacc> GPenguin: yes, wordpress only depends on a client
[17:07] <nacc> GPenguin: you need to setup a server potentially
[17:07] <GPenguin> ah, hmmm
[17:08] <nacc> GPenguin: if you insatll suggests, it will pick up mysql-server as well
[17:08] <rbasak> jgrimm: libqb done
[17:11] <GPenguin> nacc: i am also missing the wp-config.php
[17:12] <jgrimm> rbasak, thanks
[17:13] <GPenguin> uhh, that is in /usr/share/wordpress
[17:17] <nacc> GPenguin: looking to see if i can reproduce; iirc, when i did the update, i got it installed and setup fine
[17:26] <nacc> GPenguin: and the apache config uses /usr/share/wordpress
[17:26] <nacc> GPenguin: the example one
[17:37] <nacc> GPenguin: yeah, so that basically works, your choice of apache configuration, enable it, run setup-mysql and then navigate in a browser to finsih the wordpress install like normal
[17:38] <GPenguin> hmmm
[18:04] <zul> coreycb: okie dokie
[18:27] <BrianBlaze420> oh man going from 8 to 16 is fun lol
[18:37] <compdoc> 16 girlfriends?
[18:42] <OerHeks> 16 bit?
[18:44] <nacc> 8.04 to 16.04 based upon yesterday's context
[18:44] <nacc> BrianBlaze420: honestly, it's probably easiest to backup data and install from scratcch
[18:44] <BrianBlaze420> yeah that's what is happening
[18:44] <BrianBlaze420> so sad lol
[18:45] <BrianBlaze420> i am more sad that the guy who set this up walked away from it for so long
[18:45] <BrianBlaze420> anyways I am just venting :)
[18:55] <teward> BrianBlaze420: sounds like an evil system I had to work with in the past, at my one workplace.  8.04 running evil Python
[18:55] <teward> 16.04 wasn't out yet so we had to -> 14.04
[18:55] <teward> 14.04 -> 16.04 will be easy heh
[18:55] <teward> python, dovecot, etc. all configured on 14.04 works pretty well on 16.04 too :P
[18:55] <BrianBlaze420> lol yeah I am looking forward to getting there
[18:55] <BrianBlaze420> where I am not horrified of updating lol
[18:56] <teward> took a year to migrate everything off 8.04
[18:56] <teward> because of python lol
[18:56] <teward> dovecot and postfix were easy
[18:56] <teward> python, not so much
[18:56] <teward> (3rd party library updates, etc. caused problems0
[18:56] <teward> s/library/module/
[18:56] <teward> anyways i digress :)
[18:57] <BrianBlaze420> :)
[18:57] <BrianBlaze420> at least I feel less alone, so I appreciate lol
[18:57] <teward> sarnold: ohai, you!  nginx merge uploaded to -proposed.  Lotsa new binaries lol
[18:58] <sarnold> teward: \o/ nice, how'd it go?
[18:58] <teward> sarnold: painfully.  'cause it's a ***horrible*** evil process.
[18:58] <sarnold> teward: aye :/
[18:58] <teward> baseDebian + PackagingDeltaChanges + (fixMistake x 4)
[18:59] <teward> finally got it to a PPA last night, and cpaelzer was kind enough to run install/upgrade tests
[18:59] <teward> i'm just waiting for the mismatched components report :P
[18:59] <teward> 'cause there'll be some
[19:00] <teward> (some of the dynamic module packages)
[19:13] <JoseLuis_> Good afternoon all.
[19:14] <teward> greetings
[19:16] <JoseLuis_> I have a lot of mail in my server about Cron <root@localhost> /etc/cron.hourly/kill.sh  and Cron <root@localhost> /etc/cron.hourly/cron.sh
[19:18] <JoseLuis_> SIOCSIFFLAGS: Cannot assign requested address     SIOCSIFFLAGS: Protocol driver not attached
[19:20] <sarnold> what do those scripts do?
[19:22] <JoseLuis_> cat /etc/cron.hourly/kill.sh  http://termbin.com/vgz8
[19:22] <JoseLuis_> cat /etc/cron.hourly/cron.sh http://termbin.com/cfb4
[19:23] <sarnold> oh crap
[19:23] <sarnold> now I remember why your name is familiar
[19:23] <sarnold> JoseLuis_: https://www.linode.com/docs/security/recovering-from-a-system-compromise
[19:25] <JoseLuis_> sarnold: I am going to read
[19:34] <JoseLuis_> sarnold: Definitely, we will to create a new server in linode, but we should need to install security first before to install program and database.
[19:36] <sarnold> JoseLuis_: it'd be worth trying to figure out how this instance was compromised while you're at it -- full forensics are extremely difficult, but it'd be best to know if the machine was hacked via ssh password brute-force searches, or a web-based management console, or something else..
[19:40] <JoseLuis_> yeah, but I do not know how to do this.
[19:41] <teward> sarnold: compromised systems are compromised!
[19:41] <teward> JoseLuis_: you'd either hire someone
[19:41] <teward> or just not bother finding how to ID the compromise.  Either case, nuke with fire
[19:46] <JoseLuis_> I was hired in august for manage mongodb and to make some scripts in linux to monitoring some server in linode and windows.
[19:48] <sarnold> I wonder if this was involved http://thehackernews.com/2017/01/secure-mongodb-database.html
[19:49] <JoseLuis_> the security in linux servers and windows server is almost null, (pass with 12345678, qwerty, etc..)
[19:50] <teward> JoseLuis_: well, "the security in linux servers" is a matter of configuration
[19:50] <teward> 99% of the time, people who set up the servers
[19:50] <teward> don't follow common sense practices
[19:50] <JoseLuis_> sarnold: thanks for the information.
[19:51] <sarnold> teward: I'm afraid that's what he was reporting on :)
[19:51] <sarnold> JoseLuis_: good luck
[19:51] <teward> heh
[19:51] <teward> sarnold: CrapSecurity is about equal to ZeroSecurity
[19:52] <teward> and then there's my network, locked up tight, every system has a firewall, different passwords for each, service and priv. separation across multiple systems...
[19:52] <teward> VLANed out the wazoo to protect other subnets...
[19:52] <teward> IDS/IPS on the border...
[19:52] <teward> redundant firewalls...
[19:52] <teward> ... is my network overkill yet?  :P
[19:53] <sarnold> ayup. :)
[21:09] <pmatulis> a rift in the fabric of time
[21:39] <Dmitrii-Sh> cpaelzer: hi, is there a reason why libvirt is missing from https://code.launchpad.net/~usd-import-team/+git ? I'm not too familiar with usd-importer yet but 'git grep -i libvirt' in its repo shows that it is commented out in the usd-cron-packages.txt:#libvirt
[21:42] <Dmitrii-Sh> cpaelzer: in general, I am looking for a good way to do quick git merge-base --is-ancestor <hash1> <hash2> type of checks for upstream patches and it is much easier to have an up-to-date git repo at hand to do it
[21:43] <nacc> Dmitrii-Sh: there is a distinct git repository being used
[21:44] <nacc> Dmitrii-Sh: for libvirt they use the debian repo, iirc
[21:44] <nacc> Dmitrii-Sh: there is an ubuntu branch (or branches)
[21:44] <nacc> Dmitrii-Sh: i might be wrong, smb may also know
[21:46] <Dmitrii-Sh> nacc: hmm, I saw the Debian repo https://anonscm.debian.org/cgit/pkg-libvirt/libvirt.git/refs/ but there is only a single ubuntu branch there (from 2007)
[21:47] <nacc> Dmitrii-Sh: oh sorry, there is a lp repo, i guess (found it from the ubuntu package search SCM link)
[21:47] <nacc> https://git.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt
[21:48] <nacc> Dmitrii-Sh: that looks current, i think
[21:48] <nacc> Dmitrii-Sh: also, should be the Vcs-Git value in the control file in the source pacakge, iirc
[21:51] <Dmitrii-Sh> nacc: this one seems right
[21:51] <Dmitrii-Sh> nacc: http://packages.ubuntu.com/source/xenial-updates/libvirt the repo mentioned here too
[21:51] <nacc> Dmitrii-Sh: cool :)
[21:52] <Dmitrii-Sh> nacc: wasn't the case with qemu AFAIR but this one is good )
[21:52] <Dmitrii-Sh> nacc: thx
[22:35] <powersj> rbasak: thanks for the review of etckeeper, updates made!


[03:55] -queuebot:#edubuntu- Unapproved: edubuntu-artwork (noble-proposed/universe) [24.04.25 => 24.04.26] (no packageset)
[04:14] -queuebot:#edubuntu- Unapproved: accepted edubuntu-artwork [source] (noble-proposed) [24.04.26]


[15:13] <boredandblogging> anyone else getting a blank fridge.ubuntu.com/event
[15:13] <boredandblogging> ?
[15:13]  * Rinchen looks
[15:14] <Rinchen> yeah, busted again...
[15:14] <boredandblogging> its happened last weekend and it magically fixed itself
[15:17] <Rinchen> I've poked newz to see if we can't get a high php memory value
 ok, then it probably means we're close to the right ram setting but not quite on the mark. Apparently some pages need a little more.
[15:18] <Rinchen> he's going to have IS update it again
[15:19] <boredandblogging> excellent
[15:34] <cody-somerville> :/
[18:32] <x9x> brr
[19:30] <Rinchen> heh
[19:31] <Rinchen> Jag känner en bott, x9x  :-)
[21:49] <x9x> hehe
[23:59] <LaserJock> Rinchen: how is implementation of the UbuntuNews spec blocking you?
[23:59] <Rinchen> LaserJock, I can't shut down fridge-devel
[23:59] <LaserJock> hmm
[23:59] <Rinchen> it's a spam fest with subscribers I don't recognize and private conversations
[23:59] <LaserJock> well


[08:18] <Nothing_Much> oh my goodness
[20:04] <balloons> ahoneybun, glad everything arrived safely
[20:04] <ahoneybun> yea me too balloons
[20:04] <ahoneybun> I'm keeping it in the box safe and sound for the moment


[00:52] <OvenWerks> teward: yes that works. I like that it is much easier to read and easy to make sure there are spaces where they need to be without adding +" "+ kinds of junk.
[00:53] <OvenWerks> I have found another bug though :(  I will look at fixing that.
[01:05] <teward> yep.  this is why I like format strings :P
[01:05] <teward> OvenWerks: and what bug, if I may ask?
[01:29] <OvenWerks> the visible check box was not working right (just pushed fix) I could make something not visible, but could not make it visible again. And I had to do an edit to do even that.
[01:31] <OvenWerks> teward: ^^ So I have fixed that. (running glade to add one small change sure makes for a big diff)
[01:34] <teward> OvenWerks: I take it that was not my fault then :p
[01:34] <OvenWerks> no not your falt
[01:37] <Eickmeyer> OvenWerks: I just triggered a rebuild.
[01:47] <teward> Eickmeyer: might be a while :Po
[01:47] <teward> I can fast build if you want
[01:48] <Eickmeyer> teward: I'm in no rush.
[01:48] <Eickmeyer> Dunno about OvenWerks
[01:49] <teward> well this also lets me notice any odd new lintian warns :p
[01:49] <Eickmeyer> teward: Also, looks like it's already built and just needs to be publish.
[01:49] <Eickmeyer> teward: True. Go ahead.
[01:50] <teward> yep looks good.
[01:50] <teward> not sure if hte publisher will be fast enough :P
[01:50] <teward> but i'm impatient :)
[01:51] <teward> https://people.ubuntu.com/~teward/ubuntustudio-menu-add_0.1_all_v4.deb if you are as impatient as I :)
[01:51] <teward> glad to hear though my little change there didn't blow it up :)
[01:51] <teward> i thought for a second I had introduced another bug xD
[01:53] <Eickmeyer> Nah, looks like you're good. Any problems that came from that have been circumvented, I take it?
[01:54] <teward> Eickmeyer: AIUI yes
[01:54] <teward> OW said there was a bug in the visible checkbox not working right
[01:54] <teward> but not related to my code
[01:54] <teward> and I think OW is now in love with format strings xD
[01:54] <Eickmeyer> I see that. Looks like he fixed it.
[01:54] <Eickmeyer> hehehehe
[01:54] <teward> both f-strings
[01:54] <teward> and "".format :P
[01:55] <Eickmeyer> Maybe someday I'll learn Python and know what that means.
[01:56] <teward> heh
[02:10] <teward> Eickmeyer: basically?
[02:10] <Eickmeyer> Huh?
[02:10] <teward> instead of doing "some string "+variable+" was here" it's easier to know where things are in the string
[02:11] <teward> f"some string {variable} was here"  <-- easier to make sure things are exactly where they need to be
[02:11] <teward> AND to quote out entire args
[02:11] <Eickmeyer> Okay, that makes sense.
[02:11] <Eickmeyer> I had to turn that into a bash script in my head.
[02:12] <teward> it's not actaully that far off ;)
[14:51] <OvenWerks> Eickmeyer: f-strings are like super bash instring variables as the "variables" can be equasions or the return of functions
[16:17] <teward> OvenWerks: can we confirm the bugs you ID'd are fixed and documented in the changelog and 'ready for upload'?
[16:17] <teward> and that 'this works'?
[16:17] <teward> once that's ready I can responsor it
[16:57] <OvenWerks> teward: they bugs are fixed... running my local file before uploading. I will DL the package and check this afternoon to check that way too.
[16:58] <OvenWerks> teward: in many ways I would like other people to try it as that exposes my blind spots...
[16:59] <OvenWerks> but we seems to have very few people willing to do that.
[17:00] <OvenWerks> When I build something, everything inside is "intuitive" to me... but I tend to be the odd one out in many of these things
[17:12] <teward> OvenWerks: well I don't run Studio
[17:13] <teward> so make Eickmeyer test it :p
[17:13]  * teward is just here as a 'helper' today
[17:25]  * Eickmeyer tested it already
[17:26] <Eickmeyer> teward: I'd go ahead. If we can get it into Eoan, I should have upload rights for bugfixes, or at least can get them from the DMB.
[17:27] <Eickmeyer> If we can get people testing the dailies, that would be the best route at this point.
[17:27]  * Eickmeyer is going crazy applying for jobs.
[17:44] <teward> ack
[17:44] <teward> i will pull latest, debuild, and upload again.  If it rejects I'll let you know.
[17:44] <Eickmeyer> teward: ack
[17:47] <teward> this is missing the subprocess patches...
[17:47] <teward> the one that switches the subprocess call to array based
[17:47] <teward> OvenWerks: did that get pushed?
[17:47] <teward> or did we expect me to apply that?
[17:48] <teward> or did that still not work?
[17:50] <teward> the change which does subprocess.run(["/usr/bin/exo-desktop-item-edit", str(self.tempfile)], shell=False) instead of the string based exec
[17:50] <teward> Eickmeyer: ^ this was the last bit that sarnold wanted done
[17:50] <teward> but it was untested
[17:50] <teward> 'cause i'm not on eoan
[17:50] <teward> nor STudio
[17:51] <teward> so if this still doesn't work i'll be happy to leave it as is with the strings
[17:51] <teward> but sarnold wanted it array-based preferably
[17:51] <teward> rather than string-driven
[17:51] <Eickmeyer> OvenWerks needs to address that then.
[18:11] <teward> ack
[18:16] <OvenWerks> I thought that had been changed. sorry, I will look at it.
[18:17] <OvenWerks>  I thought that was what I tested.
[18:19] <OvenWerks> https://git.launchpad.net/ubuntustudio-menu-add/tree/usr/bin/ubuntustudio-menu-add?id=bd332ecd04cf778bd60208dbd187dd9658eaf7b4
[18:20] <Eickmeyer> teward: ^
[18:20] <OvenWerks> line 418
[18:20] <teward> OvenWerks: that's the format-string driven one
[18:20] <teward> i had another patch hang on
[18:20] <teward> that applied it as an *array* with the full path
[18:20] <teward> guess it never pushed
[18:20] <teward> 'cause i didn't hit push
[18:21] <OvenWerks> I notice the terminal =true too :(
[18:21] <teward> yeah that's why it's not got my code in it.  Mine uses shell=False
[18:21] <teward> and sarnold doesn't like shell=True if it can be avoided
[18:21] <teward> for security reasons
[18:22] <teward> okay...
[18:22] <teward> https://git.launchpad.net/ubuntustudio-menu-add/commit/?id=50791c079560173736ec8eaaa2dc4362b297c0e0
[18:22] <teward> which uses the array
[18:22] <teward> lets see if *this* works.  if not we'll revert
[18:22] <teward> this pulls the full path in so
[18:22] <teward> if this works as-is then all is good
[18:24] <teward> it SHOULD but it'll need a test ;)
[18:27] <OvenWerks> teward: that works here.... so what is different? When we tried it before it failed. Maybe shell == yes needs string?
[18:27] <teward> OvenWerks: no
[18:27] <teward> it's shell=False
[18:27] <teward> taht's what we needed
[18:27] <teward> which i discovered during some tests
[18:27] <OvenWerks> Yes, I agree
[18:28] <OvenWerks> I was wondering why it failed before (yesterday)
[18:28] <teward> yeah i was headscratching
[18:28] <teward> then i did some local Python subprocess call tests
[18:28] <teward> and found it
[18:33] <OvenWerks> The only differences I see are " rather than ', full path and Shell=false
[18:34] <OvenWerks> I think the shell=False could be omitted as being default but leaving it in is self documenting.
[18:34] <OvenWerks> teward: ^^
[18:35] <teward> yeah I left it in there for explicitly making sure.  I used double quotes by accident, but from Python's perspective 'foobar' == "foobar"  as they're both strings
[18:35] <teward> if you prefer single quotes that's a minor change
[18:35] <OvenWerks> Not worth it
[18:35] <teward> mmkay.  I need to add some changelog entries since I contributed now :|
[18:36] <OvenWerks> I tend toward double quotes... not sure why (K&R c maybe?)
[18:36] <teward> *SHRUGS*
[18:36] <teward> oops caps
[18:38] <teward> OK so I also added to the changelog since it has my two revisions per sarnold
[18:38] <teward> sarnold: want to do one last review before this gets reeval'd for sponsoring?
[18:39] <sarnold> sure
[18:40] <teward> https://git.launchpad.net/ubuntustudio-menu-add/tree/usr/bin/ubuntustudio-menu-add should be less offensive wrt subprocess and lib calls :)
[18:43] <sarnold> btw is there a reason why this line uses concatenation?
[18:43] <sarnold> self.tempfile = str(os.path.expanduser("~/"))+".config/ubuntustudio_menu_temp.desktop"
[18:43] <teward> sarnold: because OvenWerks hasn't gotten to using an f-string for it yet
[18:43] <sarnold> hmm I guess I could just try ..
[18:43] <teward> since they only learned about format strings yesterday-ish(?)
[18:44] <sarnold> os.path.expanduser("~/.does/not/exist")
[18:44] <sarnold> '/home/sarnold/.does/not/exist'
[18:44] <sarnold> no need for foramt strings
[18:44] <teward> sarnold: the concat is to add the rest.
[18:44] <teward> that's why the concat as is works
[18:45] <teward> and yes i'm annoying asking sarnold to spotcheck
[18:45] <teward> but since sarnold caught the first batch of errors
[18:45] <teward> i'm being cautious :)
[18:46] <teward> oh OvenWerks just a question
[18:46] <teward> self.menufolder in menu_cb
[18:46] <teward> that's not init'd in __init__
[18:46] <teward> should it be?
[18:46] <teward> even if it's init'd to None?
[18:46] <teward> (code inspection shows it as a low-level consideration)
[18:46] <teward> (not blocking but still a question)
[18:48] <sarnold> teward: well, it looks like os.path.expanduser() doesn't need the file to exist, it should work fine without the concatenation or format string or hwatever
[18:48] <teward> indeed, it doesn't.
[18:48] <teward> sarnold: so you're saying straight os.path.expanduser("~/.config/ubuntustudio_menu_temp.desktop")  ?
[18:48] <teward> (as an example)
[18:49] <sarnold> yeah that should work, right?
[18:50] <teward> yep even without the str-casting since it returns a str
[18:50] <sarnold> yay
[18:51] <teward> anything else glaring?
[18:51] <teward> Eickmeyer: OvenWerks: and forgive our bootprints over this :)
[18:52] <sarnold> nope, thanks for fixing up the executions to use arrays :)
[18:52] <teward> yeah that was a PITA to trace
[18:53] <teward> OvenWerks: at your convenience, `git pull` and test please :)
[18:53] <teward> if all still works
[18:53] <teward> i'll sponsor it up :)
[18:57] <Eickmeyer> teward, sarnold: I think I speak for both of us when I say any improvements are welcoe.
[18:57] <Eickmeyer> *welcome
[18:57] <teward> indeed.
[18:57] <teward> Eickmeyer: of course, sarnold does A LOT of code review so spots things I sometimes don't :)
[18:57] <Eickmeyer> Makes sense.
[18:58] <sarnold> everyone spots different things :)
[18:58] <sarnold> I'm good at noticing things along syscall boundaries
[18:58] <sarnold> and sometimes algorithmic mistakes
[18:58] <sarnold> other people know specific idioms in languages better
[18:59] <OvenWerks> teward: self.menufolder is actually initialized in the glade file.
[18:59] <sarnold> but now time to watch some women's world cup :) have fun
 OvenWerks: ah.  ack, OK.
 just thought I'd ask :)
 OvenWerks: if everything works fine here though as-is then this is Good 2 Go and I'll be happy to upload (unless you want a test build too)
[18:59] <OvenWerks> the data is static unlike submenu
[19:00] <OvenWerks> I am still testing, I looked at the init first
[19:03] <OvenWerks> I din't know I could give the whole string for expanduser. Thank you. Yes that still works.
[19:04] <OvenWerks> teward: thinking about logically, it does make sense I could do it that way.
[19:05]  * OvenWerks wonders how ubuntustudio-controls got through...
[19:05] <Eickmeyer> OvenWerks: Probably because it was an already-existing binary.
[19:07] <OvenWerks> I will go through -controls sometime fixing some of these things there as well.
[19:08] <OvenWerks> The lines of code count should go down.
[19:08] <teward> OvenWerks: probably because it didn't have me or sarnold digging into the code :P
[19:08] <teward> (my coredev is new as of this week and Eickmeyer asked me to poke so :P)
[19:09] <OvenWerks> teward: I will at least go through the code first before we sak for a look.
 👍
[19:10] <OvenWerks> I should be able to get rid of things like shell=True
[19:10] <teward> OvenWerks: yeah, since shell=True is already insecure
[19:10] <teward> they even say it in the docs xD
[19:10] <teward> thanks for the effort though, just make sure it works with the array execution and those strings being expanded
[19:10] <teward> if all looks good I'll kick it into NEW queue
[19:11] <OvenWerks> yup, but it is obvious to me my main problem there is using the shell to find the executable, just give the path and that can go away
[19:11] <OvenWerks> teward: ubuntustudio-menu-add looks good to me. anything those changes affect has been tested.
 ack
 are you and Eickmeyer comfortable with this being 0.1 in the repos then?
[19:12] <OvenWerks> yes
[19:13] <OvenWerks> when I work on -controls, I will commit each kind of change. (maybe tab to space frst)
 good idea :)
[19:14]  * OvenWerks is off to lunch
[20:49] <teward> OvenWerks: Eickmeyer: just as an FYI: the package was accepted to the NEW queue as is now
[20:49] <teward> it's waiting AA review
[20:49] <teward> at their convenience.
[20:50]  * teward goes to pack up before heading home from work