[00:04] <brousch> wow, crazy stuff http://www.myfoxdetroit.com/dpp/news/local/tornado-destroys-homes-in-dexter-michigan-other-areas-hit-by-severe-weather-20120315-DK
[00:17] <jrwren> brousch: it was very close
[00:18] <jrwren> snap-l: the N = None; del N # confused me coming from a java/.net background
[00:18] <jrwren> i just wait for patent expiration... just a few more years for the mp3 patents.
[00:19] <brousch> i'm sure they will be extended like copyrights
[00:28] <jrwren> no
[00:28] <jrwren> patents don't have that history.
[00:28] <jrwren> i had a celebration when teh RSA patent expired.
[00:33] <jcastro> JAY WREN
[00:33] <jcastro> hi
[00:48] <jrwren> hi jcastro
[00:48] <jrwren> how are you?
[00:48] <jrwren> i miss you, when are you moving back to MI?
[00:48] <jrwren> hey, #ubuntu-us-mi am I the only one who doesn't care at all about ubuntu achievements?
[00:58] <greg-g> shhhhh!
[00:59] <jcastro> jrwren, I'm visiting on memorial day
[01:02] <jrwren> YAY!
[01:43] <snap-l> jrwren: I think achievements are pretty stupid
[01:43] <snap-l> which is why I'm not on 4square
[01:44] <snap-l> but, I acknowledge that some people need that pavlovian dog acknowledgement in order to excel
[01:46] <snap-l> and yes, I'm happy that Patents expire, unlike copyrights which retire like Bret Farve or Ozzy Osbourne.
[01:47] <snap-l> Frankly, I don't mind initial publish date + X years (where X < 50)
[01:48] <snap-l> with additional (c) extension for 10 years if you publish a new edition of the work
[01:48] <snap-l> at least it would keep the things that still have legs (like the Beatles and Steam Boat Willie) going, and give added incentive to keep shit in print
[01:48] <jrwren> where X < 7
[01:49] <jrwren> fuk beatles and steam boat willy, they should be public
[01:49] <snap-l> and let things that may not have monetary value go PD gracefully.
[01:49] <jrwren> its not about monetary value, its about freedom
[01:50] <snap-l> jrwren: I know
[01:50] <jrwren> or rather, the problem is that it IS about monetary value instead of freedom
[01:50] <snap-l> which is why I get extremely irritated when the Edgar Rice Burroughs estate starts sabre-ratling whenever someone publishes something against John Carter of Mars
[01:50] <snap-l> It's PD. Get over it.
[01:51] <snap-l> or the Howard estate re: Conan
[02:47] <rick_h> snap-l: no calling 6am
[02:48] <rick_h> going to be a rough night of transition me thinks
[02:53] <rick_h> woot, new keyboard...let the awkward adjustment phase begin
[11:06] <rick_h> morning
[11:06] <rick_h> ugh
[11:08] <mydogsnameisrudy> rick_h:  wrong side of the bed , go back to bed and getup on the other side
[11:16] <snap-l> rick_h: Good morning
[11:16] <snap-l> and good morning, everyone else.
[12:25] <rick_h> man, it's going to be a long day
[12:25] <snap-l> rick_h: I can imagine
[12:29] <brousch> rick_h: you back in the M I?
[12:29] <rick_h> yep
[12:29] <rick_h> got in last night so starting to catch u\
[12:29] <rick_h> losing three hours coming back sucks
[12:32] <brousch> maybe 4 hours
[12:32] <brousch> do they do daylight savings in CA?
[12:32] <snap-l> Only AZ and Hawaii neglect to celebrate DST
[12:35] <brousch> some parts of IN
[12:35] <brousch> they go county-by-county there
[12:35] <snap-l> It's all restupid
[12:36] <rick_h> brousch: yea, lost my hour there as well
[12:37] <brousch> hey apple-lovers http://aroberge.blogspot.com/2012/03/python-for-ios-first-look.html
[12:38] <rick_h> I've seen  enough apple to last me a while
[12:38] <rick_h> forgive my typing as I get keyboard adjusted
[12:39] <snap-l> rick_h: but for $3 you can play with a limited Python on an iOS device?
[12:39] <snap-l> isn't that worth it for you? :)
[12:39] <brousch> well it's better than having no python ;)
[12:42] <snap-l> Tendulkar reaches cricket milestone
[12:42] <snap-l> Indian cricketer Sachin Tendulkar becomes first man to score 100 international centuries.
[12:42] <snap-l> I will never, ever understand Cricket.
[12:50] <brousch> hm, time to dive into throwing exceptions. i don't know if i've ever done that before
[12:50] <rick_h> from python?
[12:50] <brousch> yeah
[12:50] <rick_h> raise Exception('message')
[12:50] <snap-l> ^^
[12:50] <rick_h> or subclass Exception
[12:50] <brousch> shouldn't there be a different exception for different errors?
[12:50] <rick_h> or the another Exception like ValueError, etc
[12:51] <rick_h> right, so you can create subclasses to throw for the 'type' of error
[12:51] <brousch> ok
[12:51] <rick_h> with a message specific to the exception
[12:51] <brousch> last time i did this was in java
[12:52] <brousch> i am kind of excited because i think if i change this program to use exceptions i can also make it testable
[12:52] <rick_h> yay!
[12:52] <brousch> or more easily testable
[12:53] <brousch> right now it prints errors and exits, but those should really be logs and exceptions
[12:54] <rick_h> right
[12:55] <brousch> so i've got that going and read python on android. fun days ahead
[12:55] <brousch> s/read/real/
[12:56] <rick_h> wheeeee
[12:56] <rick_h> python to rule them all
[12:56] <brousch> you're not all pyed out yet?
[12:57] <rick_h> no, I'm invigorated to start a python group out here
[12:57] <rick_h> I need to find some place to host meetings
[13:02] <snap-l> ho boy.
[13:03] <brousch> snap-l's house!
[13:06] <rick_h> my goal is to get a PSF sponsored sprint before the year is out
[13:11] <brousch> bookie sprint?
[13:11] <rick_h> no, needs to be more base python. Thinking a sprint to practice porting some lib to py3
[13:11] <rick_h> maybe something bookie uses :)
[13:12] <brousch> that would be cool
[13:45] <jrwren> brousch: IN no longer goes county by county. the state as a whole joined EST/EDT like the rest of us, a few yrs ago.
[13:47] <jrwren> oh shit... i'm wrong on that.
[13:47] <jrwren> my family in IN lied to me!
[13:47] <jrwren> ah, 2006, entire state began observing DST
[13:47] <jrwren> but zone is still county by county.
[13:47] <jrwren> *sigh*
[13:48] <brousch> heh
[15:08] <greg-g> give me more movies like: Independence Day, Transformers, Battleship
[15:09] <greg-g> ie: aliens coming to destroy humans but thank the effing lord we spend more money on the US Military than we should because it actually came in use for once
[15:09] <rick_h> oh interesting
[15:13] <greg-g> :)
[15:14] <rick_h> I'm coming up empty, but I'm not good at these kinds of problems
[15:15] <greg-g> yeah, me neither :)
[15:16] <greg-g> I just saw the trailer for Battleship and... wow
[15:16] <rick_h> heh, haven't seen it yet
[17:18] <rick_h> brousch: opencv love http://pyvideo.org/video/674/militarizing-your-backyard-with-python-computer
[17:21] <brousch> ahahah
[17:21] <brousch> i will set it up to squirt those damn kids on my lawn
[17:21] <brousch> make george wear a red hat so he is exempt
[17:24] <snap-l> greg-g: Alien military movies?
[17:24] <snap-l> What about Starship Troopers?
[17:24] <snap-l> (note: have not seen Starship Troopers)
[17:27] <snap-l> MOst of the recent alien movies have been more of the "our military is useless against these things"
[17:27] <brousch> the only good thing in starship troopers is denise richards
[17:29] <snap-l> greg-g: Work in a Mars Attacks reference. :)
[17:31] <snap-l> Fuck, they're planning a Cloverfield 2 and District 10
[17:31] <rick_h> I actually liked district 9
[17:31] <rick_h> and yea, it was setup for a follow up
[17:31] <snap-l> I want to seeit but haven't convinced JoDee
[17:31] <rick_h> cloverfield I can do without
[17:32] <snap-l> rick_h: Seriously? Hmm.
[17:32] <snap-l> Thought once the hook was known it didn't need a follow-up
[17:32] <rick_h> snap-l: yea, it's very different. I went and saw it by myself
[17:33] <snap-l> Like Blair Witch Project.
[17:33] <snap-l> Should never have been given a sequel.  This was done kind of cool like discovery channel like
[17:34] <snap-l> rick_h: Didn't see the first one, but seriously, it's like a haunted house
[17:34] <rick_h> yea, not interested
[17:34] <snap-l> once you know the hook of the haunted house, it's not scary anymore.
[17:35] <snap-l> really wish Hollywood would leave well enough alone.
[17:35] <rick_h> hah, this squirrel cannon is arduino powered
[17:35] <snap-l> LIke Tron Legacy
[17:35] <rick_h> I got the soundtrack out of it, so happy me
[17:36] <snap-l> Yeah, the soundtrack was the best part.
[17:37] <brousch> i must be the only person who doesn't care for it
[17:37] <rick_h> the tron soundtrack?!
[17:37] <brousch> yeah
[17:37] <snap-l> WHich I was surprised since Wendy Carlos' Tron Soundtrack is one of my favorites.
[17:37] <brousch> boring and kind of annoying
[17:37] <snap-l> brousch: What's your general feeling on electronic music?
[17:38] <brousch> i like some of it
[17:38] <snap-l> Also, the CD sounds a LOT better than the MP3s
[17:39] <brousch> it looks i kept 2 tracks in my playlist: adiago for tron and end of line
[17:39] <rick_h> soundtracks are meant to be listened to in whole
[17:39]  * rick_h has a ton of those in his queue...best coding music
[17:40] <snap-l> brousch: Yeah, I initially thought it was pretty boring as well
[17:40] <brousch> i did listen to it in whole, and picked out those 2 as not annoying :P
[17:40] <snap-l> but near the end is when it won me over.
[17:40] <rick_h> ugh, brousch is broken. Send him in for repair
[17:40] <snap-l> Meh, different strokes.
[17:40] <brousch> Tools still sucks
[17:40] <rick_h> Tool!
[17:41] <rick_h> *sigh* /me thinks he's hopelessly broken
[17:41] <snap-l> brousch: Redeem yourself: http://magnatune.com/artists/albums/saros-labyrinth/
[17:42] <brousch> if i remember right, the tron soundtrack had too much high pitch sound for me
[17:43] <snap-l> Are you referring to Daft Punk's, or Wendy Carlos' soundtrack?
[17:43] <brousch> daft punk
[17:43] <rick_h> yea, we're talking tron 2 right?
[17:43] <snap-l> I didn't get high pitched at all
[17:43] <brousch> i don't think i've heard the tron 1
[17:44] <rick_h> yea, I mean I'd not classify it as high pitched
[17:44] <snap-l> http://www.youtube.com/watch?v=NzRWXn5KNFI
[17:45] <brousch> i may be remembering wrong
[17:46] <brousch> maybe it was just boring
[17:47] <snap-l> Yeah, which makes it pretty good background music.
[17:47] <snap-l> ;)
[17:47] <rick_h> that, star trek, and inception are my big rotation these days
[17:47] <snap-l> That Saros album is pretty awesome, IMHO
[17:48] <snap-l> If anyone wants a copy, LMK
[20:31] <rick_h> http://blog.mitechie.com/2012/03/16/pycon-2012-what-a-ride/ pycon retro
[20:33] <snap-l> "Last year I hardly new anyone." <- knew. :)
[20:33] <snap-l> rick_h: ^^
[20:33] <rick_h> bah
[20:34] <rick_h> ty much
[20:39] <snap-l> np
[21:03] <rick_h> and bookie stuff http://blog.mitechie.com/2012/03/16/bookie-pycon-2012-sprint-report/
[21:03] <rick_h> oops, guess that should be in #bookie


[01:01] <axw> burton-aus: standup?
[02:37]  * babbageclunk goes for a run
[04:33] <blahdeblah> Anyone want a look at my live controller hitting https://bugs.launchpad.net/juju/+bug/1695894 before I hulk smash it?
[04:33] <mup> Bug #1695894: [2.2.b4] model deletion hung, unable to completely destroy the model or create a new one with the same name, errors in logsink.log <canonical-is> <juju:New> <https://launchpad.net/bugs/1695894>
[04:36] <blahdeblah> I guess you're all still recovering from travel
[05:00] <babbageclunk> blahdeblah: sorry, just saw this - is the controller still in the same state? Can you get machine-0.log from a controller machine?
[05:01] <blahdeblah> babbageclunk: I restarted all the jujuds
[05:01] <blahdeblah> but I can get you a controller log
[05:01] <babbageclunk> blahdeblah: ok thanks
[05:02] <babbageclunk> blahdeblah: and restarting the jujuds resolved it, presumably?
[05:02] <blahdeblah> babbageclunk: at least from the perspective of juju status not hanging for 10 minutes, yes
[05:02] <blahdeblah> Still seems an awful lot of log spew
[05:36] <blahdeblah> babbageclunk: https://private-fileshare.canonical.com/~paulgear/lp1695894/ has log
[05:37] <babbageclunk> blahdeblah: thanks - taking a look now
[05:41] <babbageclunk> blahdeblah: I was hoping that might have something useful/interesting at the time the problem started, but it looks like it was happening for long enough that the spam from the i/o timeout is all that's in the log.
[05:42] <blahdeblah> babbageclunk: I've got two previous logs; let me see if I can find something
[05:42] <babbageclunk> ok thanks
[05:43] <blahdeblah> when was it I was talking to you about my 2.2.2 upgrades?
[05:43]  * blahdeblah checks scrollback
[05:43] <babbageclunk> blahdeblah: you mean in Mooloolaba?
[05:44] <blahdeblah> nah - looks like last Monday
[05:44] <babbageclunk> oh, I'd forgotten, sorry!
[05:44] <blahdeblah> so I'll have 2 more logs for you - 1 sec
[05:54] <blahdeblah> babbageclunk: two more logs there now
[05:57] <babbageclunk> blahdeblah: and they both had the same thing happen?
[05:57] <blahdeblah> babbageclunk: same controller; just earlier logs
[05:58] <blahdeblah> hopefully you'll find what you're looking for sometime between last Monday (when I left it in a working state), and this afternoon, when I came back and juju status didn't give me anything for 10 minutes before I gave up waiting.
[06:22] <blahdeblah> babbageclunk: Are you the only one around?  Who's the best person to ask about the details of rick_h's post?  http://mitechie.com/blog/2017/7/7/call-for-testing-shared-services-with-juju
[07:48] <blahdeblah> rick_h: FWIW, went through your blog post step by step, worked out my problem, and got a successful cross-model relation.  Seems to work.  Where and what sort of further testing feedback are you looking for?
[11:17] <rick_h> blahdeblah: awesome
[11:18] <rick_h> blahdeblah: testing is basically making sure it works for the charms, use cases, network setups, how's it work with permissions, stability, error reporting/logging information usefulness. Basically everything lol
[12:42] <blahdeblah> rick_h: I sent you a reply on the mailing list; hopefully that will prompt a few others to try it out.  Once Ian gets the reverse direction cross-controller relations going, I'll be able to do a lot more of the testing you'd like to see.
[12:44] <rick_h> blahdeblah: cool, thanks for testing it out and the email. Good stuff
[22:37] <bdx> heya
[22:38] <bdx> I just had a user set a model config that didn't previously exist, now it exists in my model config and I can't seem to remove it
[22:38] <bdx> http://paste.ubuntu.com/25165776/
[22:38] <bdx> notice the 'env' key
[22:41] <bdx> I'm getting this is my log
[22:41] <bdx> machine-0: 18:27:16 ERROR juju.provisioner cannot start instance for machine "7": cannot run instances: The requested configuration is currently not supported. Please check the documentation for supported configurations. (Unsupported)
[22:41] <bdx> but I cant remove the model-config
[22:41] <bdx> but its squashing any other functionality in the model
[23:00] <mup> Bug #1672306 changed: unit stuck executing update-status <canonical-is> <juju-core:Confirmed> <https://launchpad.net/bugs/1672306>


[01:18] <BenC> unhappy: wireless-dev git tree
[10:39] <unhappy> BenC, U mean this: linux/kernel/git/linville/wireless-dev.git @ git.kernel.org?
[10:53] <unhappy> oh, i got it.
[10:53] <unhappy> Its John Linville's git tree
[10:53] <unhappy> thnx
[11:00] <MidMark> guys there is some delays in linux kernel to appears in update manager? I got only updates for restricted modules, nvidia driver and linux-libc-dev
[11:31] <MidMark> I repeat: linux-image-generic point still to .15 and not .16, restricted modules are updated aswell nvidia drivers, if someone updates then breaks things because X will not start anymore apart back to nv instead of nvidia driver
[12:17] <Lure> MidMark: linux-restricted-modules-common does not include much (no kernel code), so it is safe
[12:17] <Lure> MidMark: I am sure the remaining packages will follow soon (they need archive admin to get them trough binary NEW)
[12:18] <MidMark> Lure: ok but for people who has nvidia this is not so safe
[12:18] <MidMark> I think that if I will updates and will break my feisty
[12:18] <Lure> MidMark: why? no nvidia stuff is in the packages that were updated. Is there any report of brekaing on nvidia?
[12:18] <MidMark> or I'm wrong?
[12:19] <MidMark> Lure: I mean nvidia-glx abi bump
[12:19] <MidMark> from .15 to .16
[12:20] <Lure> MidMark: also modules go in separate dir - see /lib/modules/2.6.20*
[12:20] <MidMark> https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/116768
[12:21] <Amaranth> MidMark: having nvidia-glx get upgraded does not hurt, it's just the X driver
[12:21] <Amaranth> as long as your linux-restricted-modules and linux-image don't get out of sync (and those are parallel installable so no worries) you should be fine
[12:24] <MidMark> Amaranth: if I install nvidia-glx .16 with kernel .15 will X starts??
[12:24] <Amaranth> it should, yes
[12:26] <MidMark> sure? strange
[12:26] <Amaranth> the version is because it comes from the linux-restricted-modules package
[12:27] <Amaranth> but it's _just_ the X driver, it'll work with any kernel module of the same version
[12:27] <Amaranth> version being 9631
[12:27] <MidMark> then ok, but I don't want to try
[12:27] <MidMark> wait for kernel image that seems quite late
[01:47] <goncalo> hello
[07:45] <bdmurray> what package did ipw3945 run off to for the gibbon?
[07:59] <zul> ubuntu-modules i think
[08:00] <Nafallo> indeed
[08:00] <Nafallo> but rt2x00 seems to have gone AWOL?
[08:12] <bdmurray> thanks
[08:16] <johanbr> There's an rt2x00-source package in Gutsy. Maybe it's not meant to be built in-tree anymore?
[08:17] <Nafallo> that's because we import it from Debian :-)
[08:59] <xhaker> crimsun, regression on 2.6.20-16 SB450 Acer, ping me back please


[10:50] <Ziroday> !schedule @singapore
[10:51] <Ziroday> @schedule Singapore
[10:51] <ubotu> Schedule for Asia/Singapore: 29 Nov 22:00: Desktop Team Development | 02 Dec 03:00: Art Team
[15:18] <kraut> moin
[15:37] <zul> @schedule montreal
[15:37] <ubotu> Schedule for America/Montreal: 29 Nov 09:00: Desktop Team Development | 01 Dec 14:00: Art Team


[09:36] <luna> Updated from Ubuntu MATE 20.04.2 to 20.04.4 yesterday, and it went fine, to remove 6 packages and add 256 other ones :)


[00:59] <ethana2> http://paste.ubuntu.com/205915/
[00:59] <ethana2> I'm new at this, how do I get rid of those errors and warnings?
[01:03] <directhex> ethana2, lintian-info --tags $foo
[01:03] <directhex> e.g. lintian-info --tags dh-clean-k-is-deprecated
[01:03] <directhex> will tell you in detail what to do for each lintian error
[01:04] <ethana2> I don't think all my errors are lintian errors though
[01:04] <ethana2> at least not the fatal ones..
[01:04] <ethana2> how do I make it ignore gpg signing stuff?
[01:06] <RAOF> ethana2: pass "-us -uc" to debuild; that's "don't sign the source" and "don't sign the changes", respectively.
[01:06] <ethana2> ahhhh
[01:06] <ethana2> I had the -us..
[01:06] <RAOF> That'll get rid of the debsign error, by not calling debsign :)
[01:06] <ethana2> RAOF: thanks
[01:06]  * ethana2 does it
[01:10] <ethana2> The following packages are BROKEN:
[01:10] <ethana2>   pbuilder-satisfydepends-dummy
[01:11] <RAOF> The interesting error is after that.  Pastebin time!
[01:19] <ethana2> hmm
[01:19]  * ethana2 pastebins all of it
[01:20] <ethana2> http://paste.ubuntu.com/205930/
[01:21] <RAOF> pbuilder-satisfydepends-dummy: Depends: xautomation which is a virtual package
[01:21] <directhex>   pbuilder-satisfydepends-dummy: Depends: xautomation which is a virtual package.
[01:22] <ethana2> what's a virtual package?
[01:22] <directhex> one which doesn't exist
[01:23] <ethana2> should I just remove it from the project files?
[01:23] <RAOF> Most likely you're missing Universe in your pbuilder?
[01:23] <ethana2> I don't know..
[01:23] <ethana2> but it is a universe package I guess
[01:24] <ethana2> brb
[01:35] <ethana2> back
[04:16] <kb9vqf_> How do you remove a package from REVU?  I was typing too fast and uploaded to REVU instead of my PPA...
[04:17] <ajmitch> packages can be archived there if you tell us which one
[04:17] <kb9vqf_>  	 kchmviewer-kde3
[04:20] <StevenK> -kde3 ?
[04:20] <StevenK> Eeek
[04:20]  * ajmitch doesn't see it there yet
[04:31] <kb9vqf_> ajmitch: strange...it's showing up here: http://revu.ubuntuwire.com/u/kb9vqf
[04:31] <kb9vqf_> StevenK: Yup, it's one of those old KDE3 packages, bound for the KDE3 PPA... ;-)
[04:33] <ajmitch> kb9vqf_: ah, I thought you meant that you'd just uploaded it, and it is archived there
[04:33] <ajmitch> nuked now
[04:33] <kb9vqf_> sorry for the confusion...and thanks! :-)
[04:34] <kb9vqf_> BTW I went ahead and uploaded 389 directory server packages to REVU, just in case I can't get it in upstream in time for Karmic
[04:35] <ajmitch> I saw that
[04:36] <kb9vqf_> I tried to implement your earlier suggestions...we'll see if Debian likes them or not
[04:36] <ajmitch> which ones were they? :)
[04:36] <kb9vqf_> ${shlibs:Depends}
[04:36] <kb9vqf_> instead of all the individial lib depends
[04:37] <kb9vqf_> Needed -0ubuntu1
[04:37] <ajmitch> right, that's fairly standard
[04:37] <ajmitch> -0ubuntu1 is good, but probably not if you're culling all the previous changelog entries
[04:37] <kb9vqf_> I thought I read somewhere that you are supposed to cull them?
[04:38]  * kb9vqf_ doesn't remember where
[04:38] <ajmitch> I'm not a big fan of rewriting history especially when building on the work of others
[04:38] <ajmitch> others will disagree with me, I'm sure
[04:39] <kb9vqf_> Yeah, it didn't feel right to me either--that's why I kept Michele in the control file as original uploader
[04:39] <kb9vqf_> Michele mentioned that he won't be able to work on anything until September, so I guess it's a good thing that I started work on it
[04:39] <ajmitch> probably, since I doubt I'd have found time to pick it up again
[04:42] <ajmitch> now you just need to find some friendly reviewers to bribe
[04:43] <Hobbsee> hint: offer beer
[04:43] <ajmitch> sounds like Hobbsee is thirsty
[04:44] <ajmitch> it's great when 30k of a 40k diff is just the license text
[04:46] <kb9vqf_> :)
[04:47] <kb9vqf_> I'm doing a final rebuild test now, just to make sure it all works
[04:48] <ajmitch> I can at least review the easy ones, which are the various libraries & don't require any setup
[04:49] <kb9vqf_> Sure...try svrcore and all the mozilla libs
[04:49] <kb9vqf_> Those, along with JSS, haven't changed for the past five years (!)
[04:49] <kb9vqf_> In some cases, they're even older...
[04:49] <ajmitch> yeah, I've still got copies of them around from my work, I remember having to play around with pkg-config
[04:52] <kb9vqf_> if you find anything wrong, poke me at kb9vqf_ (*with* the underscore--my laptop screen died from the lightning EMP so I'm on my server for now)
[04:52] <ajmitch> it's the java packaging that scares me
[04:52] <ajmitch> ouch
[04:53] <ajmitch> I take it you got the servers up & running again?
[04:53] <kb9vqf_> Yeah, after $1500 worth of new parts
[04:53]  * kb9vqf_ hopes his insurance will handle it
[04:53] <kb9vqf_> One server mainboard, two CPUs, one hard disk, one video card, and various miscillaneous items
[04:54] <ajmitch> not fun
[04:54] <kb9vqf_> 10 days of downtime...priceless :)
[04:54] <ajmitch> 10 days is a long time for anyone
[04:55] <kb9vqf_> No kidding!  Fortunately my laptop still worked (flickering, but working) during most of that time
[04:55] <kb9vqf_> Hopefully it didn't kill 389 ds in Karmic
[04:55] <kb9vqf_> timewise, that is
[04:56] <ajmitch> how far down did you do the renaming?
[04:57] <ajmitch> I still see a few .jar files with fedora-ds in the name, looking at the diffs
[04:57] <kb9vqf_> It's still the fedora ds tarball, but the packaging is pretty much completely renamed
[04:58] <kb9vqf_> That was, I can just plop in the new 389 tarball when it is released and the users shouldn't notice the difference
[04:58] <ajmitch> so just package names, not binary names?
[04:58] <kb9vqf_> Correct
[04:58]  * ajmitch will have to build it all & try it out
[04:58] <kb9vqf_> It really only affects the ds core and the consoles
[04:58] <kb9vqf_> I'm building it all here:
[04:58] <kb9vqf_> https://launchpad.net/~ubuntu-389-directory-server/+archive/ppa
[04:58] <ajmitch> the other libraries should be fine
[04:58] <kb9vqf_> Should have it all up by tomorrow (hopefully)
[04:59] <ajmitch> great
[04:59] <kb9vqf_> Yeah, someone put together a team, so things should keep moving :)
[04:59] <ajmitch> lp team?
[04:59] <kb9vqf_> Yeah
[04:59] <kb9vqf_> https://launchpad.net/~ubuntu-389-directory-server
[04:59] <kb9vqf_> Michele is a member
[05:00]  * ajmitch should join also
[05:00] <kb9vqf_> Kai-Cheung Leung really wants to see it in Karmic...he's the one that set the team up and transfered control to me
[05:00] <ajmitch> ubuntu-directory team hasn't exactly served its intended purpose
[05:00] <kb9vqf_> Heh
[05:01] <ajmitch> it's mostly been a bug contact for packages
[05:01]  * kb9vqf_ needs to get to bed...early day tomorrow at work
[05:01] <wgrant> ubuntu-directory did nothing, and now ubuntu-server has taken over its domain.
[05:15] <micahg> ping mdeslaur
[05:15] <mdeslaur> micahg: yeah?
[05:15] <micahg> I was wondering if it's worth filing a CVE report bug for something that I know will be fixed and released asap
[05:20] <micahg> mdeslaur: ^^
[05:21] <mdeslaur> micahg: If it's a new issue that has a CVE number and is in main, we usually follow them in our cve tracker
[05:21] <mdeslaur> what cve?
[05:22] <micahg> cve-2009-2210
[05:22] <micahg> It's still mostly unpublished
[05:22] <micahg> but there is a bug # in the mozilla bugtracker
[05:29] <mdeslaur> micahg: that was fixed in thunderbird <IP_ADDRESS>?
[05:30] <mdeslaur> micahg: we just published it http://www.ubuntu.com/usn/usn-782-1
[05:30] <mdeslaur> micahg: but the particular cve number is not in the advisory as it probably wasn't public when we released
[05:31] <micahg> ah
[05:31] <micahg> I guess I was panicking for nothing :)
[05:31] <micahg> but in general, should I open an issue if it's not fixed yet, but I know it will be
[05:35] <mdeslaur> micahg: you can open a bug if you'd like, you can also take a look at our cve tracker: https://launchpad.net/ubuntu-cve-tracker
[05:36] <mdeslaur> our plan is to eventually automate the opening of bugs when we get new cves in our tracker
[05:36] <micahg> Would the cves be added automatically?
[05:37] <mdeslaur> yes, eventually
[05:37] <micahg> ok
[05:37] <micahg> is there anything I can do now to help?
[05:38] <mdeslaur> micahg: what type of help are you willing/able to do?
[05:39] <micahg> add them in the mean time for some packages?
[05:39] <micahg> what's needed?
[05:39] <mdeslaur> you could open bugs for CVEs for packages that are in universe
[05:40] <mdeslaur> that way, people would notice which packages need to be fixed
[05:40] <micahg> ok
[05:40] <micahg> I generally watch for mantis and phpmyadmin
[05:40] <mdeslaur> cool
[05:41] <micahg> I'll be opening ones for phpmyadmin later tonight probably
[05:41] <ajmitch> mdeslaur: how is universe security going?
[05:41] <micahg> eventually, I'd like to help make the patches as well
[05:41] <mdeslaur> micahg: I'll probably do updates for phpmyadmin in my spare time soon
[05:41] <mdeslaur> micahg: that would be cool
[05:41] <mdeslaur> ajmitch: we don't get much community involvement.
[05:42] <mdeslaur> ajmitch: maybe one or two packages a week get some debdiffs submitted
[05:42] <ajmitch> that's rather low, how can that be improved?
[05:43] <micahg> mdeslaur: how would I use the Ubuntu CVE tracker?
[05:44] <mdeslaur> ajmitch: we had a session about it last UDS...we (the security team) will try and give some irc sessions about it, and some other stuff
[05:44] <mdeslaur> ajmitch: we may also create a "universe package of the week" type of thing to try and get people interested
[05:44] <mdeslaur> micahg: you need to check out the tree with bzr, have you used bzr before?
[05:44] <ajmitch> ok, I'm guessing it's something you could target to the existing MOTUs & community
[05:44] <micahg> yes
[05:45] <mdeslaur> micahg: if you check out the tree, there's a readme file in there that explains all the tools and the queries you can perform
[05:45] <mdeslaur> basically, in the active directory, there's one file per CVE number
[05:45] <mdeslaur> the retired directory contains CVEs that we fixed
[05:46] <mdeslaur> and the ignored directory are for CVEs we ignore (they're not for us)
[05:46] <mdeslaur> there are some tools in the scripts directory to print out reports for a particular package
[05:46] <micahg> cool
[05:47] <mdeslaur> so you can do something like ./scripts/pkg_status thunderbird
[05:47] <mdeslaur> check out the readme file, it's full of examples
[05:47] <mdeslaur> I need to go to bed now as I'm falling asleep
[05:47] <micahg> ok
[05:47] <micahg> thanks for your help mdeslaur
[05:47] <mdeslaur> np micahg, let me know how it goes
[05:49] <mdeslaur> ajmitch: yes, existing MOTUs...and also we wanted to mention on the "how to become a motu" wiki page that producing some security updates is a good way to become familiar with a bunch of tools
[05:52] <sdeb> hi , i want anaconda instead or beside ubuntu installer ?
[06:20] <sdeb> ubottu: tell sdeb about motu
[06:33] <dholbach> good morning
[06:39] <iulian> Good morning Daniel!
[06:40] <dholbach> heya iulian!
[06:41] <fabrice_sp> Good morning dholbach !
[06:41] <dholbach> hey fabrice_sp
[06:48] <ajmitch> hi dholbach
[06:49] <dholbach> hiya ajmitch
[06:50] <ajmitch> dholbach: how was your weekend?
[06:51] <dholbach> very good, I even got some of my tax return done! :)
[06:51] <ajmitch> yay!
[06:51] <dholbach> how was yours?
[06:51] <ajmitch> I even got some sponsoring done, though I don't think I really got much other ubuntu stuff in
[06:51] <dholbach> sponsoring! :)
[06:51] <ajmitch> fairly boring & quiet, in other words :)
[06:52]  * dholbach takes the dog for a run - see you in a bit
[06:52] <ajmitch> I have to catch up to your karma somehow!
[06:52] <dholbach> hehe
[06:52] <ajmitch> close to 4k in the last month or two is a good start
[07:00] <qiyong> karmic is the 9.10 ?
[07:00] <qiyong> !karmic
[07:13] <geser> good morning
[07:13] <ajmitch> hi geser
[07:13] <iulian> Hello geser.
[08:15] <\sh> moins
[08:17] <ajmitch> hi \sh
[08:17] <geser> Hi \sh
[08:48] <stefanlsd> is revu working ok?
[08:49] <stefanlsd> submitted a new version of a package and didnt hear anything...
[08:54] <ajmitch> package name?
[08:56] <ajmitch> stefanlsd: if you could give me any more info, it'd be appreciated :)
[08:57] <stefanlsd> ajmitch: http://revu.ubuntuwire.com/p/gears
[08:58] <ajmitch> ok, for some reason it didn't like your signature on the last upload
[08:59] <stefanlsd> ajmitch: oh did update my key a couple weeks ago on LP?  maybe revu hasnt pulled the new one?
[08:59] <ajmitch> it hasn't
[08:59] <stefanlsd> ajmitch: ok. anything i need to do?
[09:00] <ajmitch> let me check the current procedures for updating keys :)
[09:00] <wgrant> Log in, IIRC.
[09:01] <ajmitch> wgrant: does that pull in updated keys & not merely new ones?
[09:01] <stefanlsd> am logged in, let me try relog
[09:01] <wgrant> ajmitch: No idea.
[09:01] <ajmitch> worth a try anyway
[09:01] <ajmitch> the keyring is dated may 16, which seems to be too long ago
[09:02] <stefanlsd> ajmitch: ok. re-logged in. anything change?
[09:03] <ajmitch> nope
[09:03] <ajmitch> I can try & do a manual update
[09:03] <wgrant> ajmitch: Sure that's the right keyring?
[09:03] <ajmitch> it appeared to be
[09:04] <ajmitch> no, you're right
[09:04] <ajmitch> uploaders.gpg vs data/uploaders.gpg
[09:04] <ajmitch> just to confuse me
[09:05] <ajmitch> stefanlsd: hopefully gears will get accepted on the next try
[09:06] <stefanlsd> ajmitch: 7A66BA46 should of been the key i signed with and my current key you should have in revu.   will try again :)
[09:06] <ajmitch> stefanlsd: it appeared to have worked now
[09:06] <stefanlsd> ajmitch: aah. yeah. just got a notification :)
[09:06] <ajmitch> good
[09:10] <stefanlsd> ajmitch: thanks for the help!
[09:12] <ajmitch> no problem :)
[10:33] <gaspa> Laney: hi, news on new ghc version?
[10:38] <Laney> gaspa: no, but you can reply to that bug and ask Simon for an update if you like
[10:38] <gaspa> of course, which bug?
[10:39] <Laney> bug 382803
[10:39] <Laney> it would probably be better to email him directly though rather than spamming LP I guess
[10:39] <gaspa> yup
[10:40] <Laney> you could CC kaol@debian and ask if he's going to update when it releases too
[10:41] <Laney> if it's more than a couple of weeks longer we should consider staying with .3 and that patch
[10:42] <gaspa> Laney: uh, late.... well, i'll do if he will reply.
[10:42] <gaspa> thanks, anyway.
[10:42] <Laney> well there's still a long time to go until FF
[10:42] <Laney> no worries
[10:43] <gaspa> geser: I wont ask you any more give-back, are you happy ? :D
[10:49] <Laney> gaspa: please cc me if you haven't sent it yet
[11:13] <gaspa> Laney: he already replied: "Will discuss with the development team today."
[11:13] <Laney> oh, speedy
[11:13] <gaspa> really. :P
[11:14] <\sh> thekorn: ping -> #leonov pls :)
[11:28] <AnAnt> Hello, it seems that the -ubuntu2 release of sl-modem is one of causes of this bug LP 375148
[11:28] <AnAnt> in that release Ubuntu removed a modprobe conf file that creates a static device (mknod /dev/slamr0)
[11:29] <AnAnt> I understand that creating static devices is not allowed in Ubuntu
[11:29] <AnAnt> but the problem is that sl-modem code doesn't dynamically create devices
[11:30] <AnAnt> and it isn't really maintained upstream (they just accept patches)
[11:30] <AnAnt> and I understand from them that sl-modem code shouldn't use udev because of license problems
[11:30] <AnAnt> anyone can suggest a solution for this mess ?!
[11:31] <dholbach> who could imagine running a session about "simple packaging from scratch" (maybe dh7?) at UDW? https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep
[11:31] <dholbach> I'd really appreciate if somebody stepped up to do it :)
[11:31] <AnAnt> dholbach: is this dh7 trying to be CDBS like ?
[11:32] <AnAnt> dholbach: I saw a rules file using dh7 , they just do dh_* something like that
[11:32] <directhex> AnAnt, except overriding dh7 requires 87% fewer chicken sacrifices
[11:32] <AnAnt> directhex: huh ? what's chicken sacrifices ?
[11:32] <Laney> when is UDW?
[11:32]  * Laney should just click the link
[11:32] <dholbach> AnAnt: you will find that in a lot of cases /usr/share/doc/debhelper/examples/rules.tiny will do what you want and you'll just need something like /usr/share/doc/debhelper/examples/rules.simple
[11:33] <dholbach> Laney: https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep Aug 31st to Sep 4th
[11:33] <dholbach> AnAnt: but CDBS will cut the deal too :)
[11:34] <Laney> I'll do it
[11:34] <Laney> packaging hello with dh7
[11:34] <Laney> ;)
[11:34]  * dholbach hugs Laney
[11:34] <dholbach> you're a hero
[11:34] <AnAnt> man I don't feel comfortable with this !
[11:34] <dholbach> Laney: you get to pick a slot :-)
[11:34] <AnAnt> it's like you dunno what's going on
[11:35] <Laney> dholbach: is there going to be a session about setting up pbuilder and such like?
[11:35] <directhex> AnAnt, turn on DH_VERBOSE to watch it - and everything it's doing can be trivially overridden
[11:36] <dholbach> Laney: I'll do it in GETTING STARTED
[11:36] <AnAnt> ok
[11:37] <Laney> dholbach: after that then?
[11:37] <Laney> also, I just looked at the rules file for hello. Does this predate debhelper?
[11:37] <dholbach> Laney: as you like it - first come, first pick the slot :)
[11:37] <Laney> ok, 1800 on the first day then
[11:37] <dholbach> Laney: there#s hello and hello-debhelper
[11:37] <dholbach> Laney: shall I add you then?
[11:38] <Laney> please do
[11:38] <dholbach> will do :-)
[11:38] <Laney> ah, this is more like it
[11:38] <Laney> hello-dh7
[11:39] <AnAnt> dholbach: can any Ubuntu derivative be added to https://wiki.ubuntu.com/Releases ? I see unofficial variants there
[11:39] <dholbach> AnAnt: just do it - I see no reason for you not to and don't know if there's anybody "maintaining the page"
[11:40] <AnAnt> dholbach: well, karmic is mentioned there, so there is someone maintaining it I think
[11:41] <dholbach> sure, just do it
[12:32] <mok0> dholbach: ping
[12:32] <dholbach> mok0: pong
[12:32] <mok0> dholbach: hey, you are a launchpad hacker, right?
[12:32] <dholbach> errrrrrrrrrrrrrrrrrrrrrrrrr
[12:33] <mok0> The sponsor queue is full of entries from Debian, that really can't be sponsored by us. Is is possible to make a script to automatically unsub from those?
[12:34] <dholbach> try https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors and https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors :-)
[12:35] <mok0> dholbach: huh?
[12:35] <dholbach> mok0: it just lists Ubuntu bugs
[12:36] <mok0> dholbach: ah now I see... :-) I was looking to unsub to clean up the list
[12:37] <dholbach> mok0: the parts of the LP API for unsubscribing teams from bugs is very new so I haven't used those parts yet
[12:37] <mok0> dholbach: OK, I understand.
[12:37] <mok0> dholbach: I also want to consult with you re. bazaar
[12:38] <mok0> dholbach: if you have time
[12:38] <dholbach> mok0: sure
[12:39] <mok0> dholbach: OK, so if you look at sahana sources at sf.net it is divided into several CVS "components"
[12:39] <dholbach> mok0: did you want to package it from CVS?
[12:40] <mok0> dholbach: no I want to import it to LP, like you have done with the civic thing
[12:40] <dholbach> oh, that's something that asomething did
[12:40] <mok0> dholbach: just wondering if it needs 3 different imports
[12:40] <dholbach> hm, good question - maybe we need one sahana super project and subprojects for the others?
[12:41] <dholbach> dunno if that's too complicated though
[12:41] <mok0> dholbach: how do you manage merging the ubuntu and trunk branches?
[12:41] <dholbach> mok0: not at all :-/
[12:41] <dholbach> they don't share history
[12:41] <mok0> dholbach: I see the ubuntu branch only has debian/
[12:41] <dholbach> we just stored the packaging in the branch
[12:41] <dholbach> yeah
[12:42] <dholbach> bzr bd -- -S -us -uc will use the watch file to build a source package for you
[12:42] <dholbach> (bzr-builddeb)
[12:42] <mok0> dholbach: Hm, isn't it supposed to be real smart so you can merge the packaging with an updated upstream clone?
[12:43] <mok0> dholbach: like, the dailydeb thing?
[12:43] <mok0> dholbach: using the watch file kinda defeats the purpose of having upstream sources mirrored in LP
[12:44] <dholbach> mok0: I know, I'd love to see us use full-source-from-vcs instead of tarballs :-)
[12:44] <dholbach> ask james_w about it :)
[12:45] <mok0> dholbach: ok, I will... I tacitly assumed you were doing it like that
[12:45] <mok0> dholbach: thanks for your time!
[12:46] <mok0> dholbach: I will see what I can find out and let you know
[12:46] <dholbach> mok0: asomething started the branch and since he was tracking the stable tarball of civicrm, I thought "ok, let's just do it like that"
[12:46] <Laney> there's funny things like autogen.sh though
[12:47] <mok0> Laney: is that a comment re: this discussion?
[12:47] <dholbach> mok0: I'll spruce up the wiki page about it some more, so we can see which parts of the ./packages/ we need to package in the long run
[12:47] <Laney> mok0: yes
[12:47] <mok0> Laney: ah ok :-)
[12:47] <Laney> so it's not as easy as pulling the vcs history
[12:47] <dholbach> http://daniel.holba.ch/blog/?p=311 is my thoughts about it :)
[12:47] <mok0> Laney: the autogenerated files ought not to be part of the repo
[12:48] <mok0> Laney: I mean the VCS
[12:48] <dholbach> mok0: WORD!
[12:48] <mok0> dholbach: thanx
[12:48] <Laney> mok0: they aren't, but they are part of the tarball
[12:48] <Laney> that's the problem
[12:48] <mok0> Laney: right...
[12:49] <mok0> Laney: when you build from the VCS you should always do autoreconf
[12:49] <Laney> yes
[12:49] <Laney> it makes it an extra step which means that we differ from what upstream releases
[12:50] <mok0> Laney: I go through a great deal of trouble keeping the autogen stuff out of my VCS managed stuff
[12:50] <Laney> as you should
[12:50] <mok0> Laney: I think from a packaging perspective, the correct thing is to ignore it if it's present
[12:51] <mok0> Laney: but there are mountains of stuff like that when you start using VCS'es for packaging
[12:52] <iulian> mok0: Hey.  Have you installed cadabra (from revu) to see if it works?  I'd like to upload it, if that's OK with you but not before I see it working.  Unfortunately, I don't have a Karmic box to test packages. :-(
[12:52] <mok0> iulian: no I haven't... I haven't had the time
[12:53] <iulian> Ouh
[12:53] <mok0> iulian: neither do I... could it be run inside a chroot?
[12:54] <iulian> mok0: Yea, but I don't have one with X installed.
[12:54] <mok0> iulian: I didn't try compiling it for jaunty
[12:55] <mok0> iulian: but I suppose it can be done
[12:55] <iulian> Yup
[12:56]  * iulian prefers and up-to-date Karmic system.
[12:56] <iulian> s/and/an/
[12:58] <iulian> Well, I'll see what I can do.  I believe it works but I just want to be sure.
[12:58] <iulian> Thanks mok0.
[13:00] <mok0> iulian: for a user-land application like cadabra release shouldn't really matter
[13:01] <mok0> iulian: it requires a library "modglue" but that made it into jaunty :-)
[13:01] <mok0> cadabra didn't cut the FF otherwise it would have been there too
[13:02] <iulian> Heh, cool.  I didn't know that.
[13:02] <iulian> OK, so, should I upload?
[13:02] <mok0> iulian: if you think the package is ok, yeah
[13:02] <iulian> Great.
[13:03] <mok0> iulian: If there are bugs in it, we'll find out soon enough :-P
[13:05] <iulian> mok0: I've reviewed it this morning as well.  Having said that, I hope I haven't missed anything, but yeah, like you said, we'll find out soon.
[13:06] <mok0> iulian: Great. I hope to start some revu'ing soon
[13:07] <mok0> iulian: karmic is requiring more work than usual due to the gcc44 toolchain
[13:07] <mok0> iulian: I've been fixing lots of FTBFS'es this time
[13:15] <iulian> mok0: Cool.  I'll have a look at some FTBFS when I have some spare time.  I have been a bit busy lately so I have been falling behind a bit on the Ubuntu front. :(
[13:16] <mok0> iulian: you can only do as much as you can
[13:17] <mok0> dholbach: nice read, holy cows!
[13:17] <dholbach> mok0: most of my ideas around it haven't changed :)
[13:18] <mok0> dholbach: I'm using git for my packaging, locally, and the workflow is quite effective.
[13:19] <mok0> dholbach: I'd like to try out bzr, but it doesn't seem to give me the same options
[13:19] <mok0> dholbach: the "a branch is a directory" paradigm rubs against me
[13:20] <dholbach> really? :)
[13:20] <mok0> dholbach: yes, really :-)
[13:20] <dholbach> "bzr branch trunk my-new-feature" became really intuitive for me already
[13:20] <mok0> dholbach: ... and you have parallel directories?
[13:21] <dholbach> yes
[13:22] <mok0> dholbach: I don't like it
[13:22] <mok0> dholbach: In git, the directory is just a container of your branch
[13:22] <mok0> dholbach: when you switch to another branch, the content of the directory changes
[13:23] <mok0> dholbach: (except for files not under control)
[13:23] <mok0> dholbach: which means you have all your branches right there in the same directory
[13:23] <dholbach> I'm not saying "there's only my way and everybody else is just nuts", but as branching for me is relatively cheap, I do it whenever I feel like it and do all operations only on the branch I'm working on right now... the "bzr pull ../other-branch" afterwards is easy enough too
[13:24] <mok0> dholbach: it's probably just my ignorance, but it seems bzr is always getting in the way of what I want to do
[13:26] <mok0> dholbach: and the extra commit you need to do after pulling trunk's changes drives me crazy :-)
[13:26] <dholbach> I don't get that feeling :)
[13:26] <dholbach> hu?
[13:26] <dholbach> bzr pull   doesn't give you uncommitted changes
[13:26] <mok0> dholbach: oh?
[13:27] <Laney> bzr merge does though
[13:27] <dholbach> right
[13:27] <mok0> dholbach: afair I always have to do a commit when I update my branch with trunk's changes
[13:27] <mok0> Hm, perhaps that's it
[13:28] <mok0> In git, you can only do a merge when your branch is committed, but then it commits everything for you again
[13:29] <mok0> Anyway, I would like to learn how to be productive using bzr
[13:29] <AnAnt> mok0: I've been using git for a week or so now, I find it cooler than bzr indeed
[13:29] <dholbach> mok0: so I should chase somebody up to give a UDW session about it? :)
[13:30] <iulian> mok0: cadabra has just been uploaded to NEW.
[13:30] <mok0> dholbach: that's a great idea!
[13:30] <mok0> dholbach: btw, I can repeat my session
[13:31] <dholbach> mok0: that'd be sweet
[13:31] <mok0> iulian: great! Thanks!
[13:31] <dholbach> mok0: you can still just grab a slot https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep :-)
[13:31] <mok0> dholbach: it was fun, there was a good crowd there
[13:31] <dholbach> fantastic
[13:33] <stefanlsd> iulian: i've been wanting to ask this - did you forward the message to the ubuntu-motu list, or is that an automated thing?
[13:35] <mok0> Wiki button "Save Changes" should be changed to "I'm felling lucky!"
[13:35] <RainCT> OT, is there some easy way to know how much traffic I use on a network interface?
[13:36] <joaopinto> RainCT, iptraf ?
[13:36] <dholbach> mok0: thanks muchly!
[13:36] <mok0> RainCT: netstat?
[13:36] <iulian> stefanlsd: Forwarded.
[13:37] <jpds> RainCT: vnstat
[13:38] <mok0> bbl
[13:39] <RainCT> joaopinto, mok0, jpds: thanks
[13:40] <stefanlsd> iulian: oh ok. thought so. is it required. or just something everyone does...?
[13:43] <iulian> stefanlsd: It's good to forward the message to the list so that everybody knows what you've uploaded from revu.
[13:44] <stefanlsd> iulian: ok. cool. was just wondering if it was a rule, or just something we do. thx
[14:39] <masterkernel> RainCT: got time for a review? :)
[14:40] <masterkernel> http://revu.ubuntuwire.com/p/kernelcheck
[14:42] <RainCT> masterkernel: Not really, I'm busy with something else. By the way, I'd be interested to an answer to the Debian thread
[14:42] <RainCT> Ubuntu is pretty much the same as Debian
[14:42] <masterkernel> which Debian thread?
[14:42] <masterkernel> the wnpp one?
[14:51] <gaspa> dholbach: there will be Loco sessions this time? (about UDW)
[14:54] <slytherin> ttx: was that you who gave back eclipse?
[14:55] <dholbach> gaspa: you mean sessions in more than one language?
[14:55] <gaspa> dholbach: yes.
[14:55] <ttx> slytherin: I've nothing to do with Eclipse, I don't even get your question :)
[14:56] <dholbach> gaspa: I'll do a call for participation once the schedule is a bit fuller, but yes, I'd love to get as much translated as possible
[14:56] <dholbach> :-)
[14:56] <gaspa> cool
[14:56] <gaspa> :)
[15:58] <alkisg> Hi, I'd like to have something like a PPA but on my own server. My main concern is that the server will be remote, and each package will be >100Mb, so I want to be able to only send the changes every time I change something. What should I use for that, reprepro?
[16:03] <mok0> alkisg: as long as the upstream source packages stays the same, you only upload diffs
[16:04] <alkisg> mok0: that's for launchpad, right? I'd like to have my *own* server to host the apt repository...
[16:04] <mok0> alkisg: same thing
[16:04] <alkisg> mok0: ok, but what software will need to be runinng on the server ?
[16:04] <mok0> alkisg: that is, if your server has a buildd
[16:05] <mok0> alkisg: afaik, reprepro should be able to work like you want
[16:05] <mok0> alkisg: the server will already have a copy of orig.tar.gz so there is no reason to upload it again
[16:06] <directhex> i always used apt-ftparchive personally
[16:06] <mok0> directhex: does that build the package?
[16:06] <alkisg> Yes, that's what I'm talking about, a simple "I recomment this tool over the other one". E.g. reprepro or apt-ftparchive?
[16:06] <directhex> mok0, no, it builds the Packages file
[16:06] <mok0> directhex: ah, you have to upload binary debs
[16:07] <mok0> directhex: that wont help him
[16:07] <alkisg> I won't be able to upload binary debs of >100Mb with my dsl :(
[16:07] <alkisg> So, mok0, you think reprepro is a good choice? /me is inexperienced...
[16:07] <mok0> alkisg: yes I do
[16:08] <alkisg> I'll dive into that then. Thanks a lot to both of you.
[16:09] <mok0> alkisg: there is also something called falcon, but I don't know how maintained it is:  https://edge.launchpad.net/falcon
[16:10] <alkisg> Heh I like his milestones map :)
[16:11] <mok0> alkisg: this is for the big thing: http://www.debian.org/devel/buildd/setting-up
[16:12] <alkisg> That's what debian uses for its archives?
[16:12] <mok0> alkisg: yes
[16:12] <mok0> alkisg: a bit overkill if you only need a few dozens of packages
[16:13] <alkisg> I think I'll need about 50 packages, but the bad this is that all over them will contain multimedia so they'll be quite large
[16:13] <alkisg> *thing
[16:13] <alkisg> mok0: I think I'll take your advice for reprepro. Much appreciated :)
[16:13] <mok0> alkisg: https://edge.launchpad.net/debomatic
[16:14] <mok0> alkisg: that's written by DktrKranz, who is always on this channel
[16:14] <alkisg> Hm, and it looks well maintained - packages for karmic and everything
[16:15] <mok0> alkisg: It does
[16:15] <alkisg> DktrKranz: what would you suggest for hosting/maintaining about 50 really big packages? (>100Mb)? debomatic, reprepro or buildd ?
[16:16] <alkisg> They contain multimedia files, but I'd like to be able to only send the differences and have the building process happen on the server
[16:17] <DktrKranz> alkisg: debomatic is something to automate build from debian source packages, is not something for repository management, so you can skip it if you need that
[16:17] <alkisg> Ah, thanks  :)
[16:18] <DktrKranz> mok0: you forgot dak :)
[16:18] <mok0> DktrKranz: Oh yes
[16:18] <DktrKranz> mok0: and a "dak for dummies" book to help configuring it ;)
[16:19] <mok0> heh. There's also "mini-dinstall"
[16:19] <mok0> DktrKranz: In fact, you can combine debomatic with mini-dinstall
[16:19] <ScottK> mcasadevall can tell you how much fun DAK setups are.
[16:20] <mcasadevall> ow dak
[16:20] <mok0> mcasadevall: alkisg is looking to set up a repo
[16:20] <mok0> mcasadevall: going over the various options
[16:20]  * alkisg is reading a little about dak...
[16:21] <ScottK> geser: Do you intend to push your debhelper change to auto add --install-layout=deb to Debian?
[16:21] <alkisg> So far, I'm between reprepro, buildd and dak. A quick "select this" would be the best for me; adding more options the worst :)
[16:23] <DktrKranz> mcasadevall: did you write a full guide on how to setup dak? it would be useful...
[16:23] <DktrKranz> ScottK: already asked myself
[16:24] <mcasadevall> nope
[16:24] <ScottK> DktrKranz: Did you get an answer?  Thanks to that change it'll be tough to make packages work in Debian and Ubuntu without change that need --install-layout=deb .
[16:24] <DktrKranz> ScottK: geser: debian #534620, pending
[16:24] <ScottK> DktrKranz: OK.  We need to go back and look at all the packages where we added it directly since the one of those I've checked no longer builds.
[16:26] <alkisg> Sorry, my xorg decided that it needed a break. /me looks at the logs...
[16:26] <DktrKranz> ScottK: really? so invoking it twice makes packages FTBFS?
[16:27] <ScottK> DktrKranz: I'm not sure exactly what the issue is, but pymilter built on Jaunty, but FTBFS on Karmic.  If I remove --install-layout=deb  from debian/rules it works.
[16:27] <geser> ScottK: I should probably do it, thanks for reminding me
[16:27] <ScottK> So something has changed.
[16:28] <geser> ScottK: any build log at hand?
[16:29] <ScottK> geser: Let me get you one.
[16:29] <DktrKranz> ScottK: I'd try another approach, building a package in jaunty chroot with --install-layout=deb specified twice, to see if that's the issue
[16:30] <mok0> DktrKranz: what do you use to manage the repo of the debomatic built packages?
[16:30] <ScottK> DktrKranz: I'll show geser the log and see if he has ideas.  I've got limited time today to worry about it.
[16:31] <ScottK> Actually I think it's likely some other change as the package still builds on Jaunty and that change was in the Jaunty debhelper.
[16:33] <ScottK> geser: http://pastebin.com/f35992d0e - identical package builds on Jaunty.
[16:34] <DktrKranz> mok0: I scan them with dpkg-scanpackages, but I don't have the need to have a local repository, right now
[16:35] <mok0> DktrKranz: ok thnx
[16:35] <DktrKranz> mok0: but I think every repo helper would be good
[16:36] <geser> ScottK: from a quick look it seems to be the "nice" feature of cdbs to rename dist-packages back to site-packages which hits here again
[16:36] <stefanlsd> is there a requirement for a Copyright line to be in each source code file? i.e. Package contains a COPYING with general license information, do individual source files need to have a copyright?
[16:36] <ScottK> stefanlsd: They should.  It won't get rejected from the archive if COPYING is present and the intent is clear.
[16:36] <ScottK> geser: OK.  Can we fix that?
[16:37] <mok0> DktrKranz: I had some problems with reprepro -- the database got screwed up, so I switched to mini-dinstall which has worked well
[16:37]  * alkisg is reading http://wiki.debian.org/HowToSetupADebianRepository ...
[16:37] <geser> ScottK: I don't know as I did look up the idea behind this yet
[16:38] <ScottK> geser: OK.  Thanks for looking into it.
[16:40] <c_korn> trying to build a package there is this error in configure: http://pastebin.com/d59325ed5 the binary used to be in the libarts1-dev package. but where is it in jaunty now?
[16:42] <geser> c_korn: AFAIR arts went away in jaunty, try building with --without-arts
[16:42] <stefanlsd> ScottK: ok. thanks. so my understanding is its recommended. Not required. With gears for example, there are two main directories.  gears and third_party.  gears/COPYING has a bsd style license. third_party has some thirdpary code and some written by google with the following - // Copyright 2006 Google Inc. All Rights Reserved. But no actual license. I guess what im asking is, does the COPYING apply to that, or is it a bit of a stretch sin
[16:42] <stefanlsd> ce its not inside the gears directory. Although im fairly sure the intended license is the google bsd type license.
[16:42] <ScottK> Since COPYING is in a different dir, I'm not sure it's clear.
[16:42] <c_korn> geser: but the error also says that it removes functionality.
[16:43] <ScottK> Is all the 3rd party stuff the same license?
[16:44] <stefanlsd> ScottK: yeah. not sure its clear either. although i believe that is their intention (although i cant speak on behalf of upstream, but upstream is uselessly unresponsive). No, other thirdparty stuff has explicit licenses.
[16:44] <Laney> all rights reserved is non-free
[16:44] <ScottK> stefanlsd: I probably wouldn't accept it, but other archive admins might.
[16:44] <Laney> isn't it?
[16:44] <ScottK> Laney: Not always.  It can mean all OTHER rights.
[16:45] <ScottK> It's a bit odd.
[16:45] <Laney> well, without any explicit information to the contrary I don't see how you can assume that it is free
[16:45] <DktrKranz> Laney: it's something which hasn't many sense on free licenses, but that won't put it as non-free
[16:45] <stefanlsd> Laney: no. the bsd license has all rights reserved also.
[16:46] <stefanlsd> http://www.opensource.org/licenses/bsd-license.php
[16:46] <geser> ScottK: re pymilter: remove the build/python-milter and install/python-milter (and perhaps also clean) as the default cdbs seem to do it for you already (and some more) and your additional rules just repeat it (when you look at the karmic build log you will see that it gets build and installed twice for every python version)
[16:46] <ScottK> geser: Thanks.  I'll have a look at that.
[16:47] <stefanlsd> ScottK: ok. thanks for the insight. i have an upstream bug opened re the issue and attached diffs for adding the intended license for them, but totally unresponsive.
[16:48] <geser> ScottK: the problem is that cdbs installs it for you to dist-packages (but renames it afterwards to site-packages), your rules install it a second time to dist-packages (so both site- and dist-packages exists now) and pycentral bails out that both exist (it would rename site-packages back to dist-packages if there wouldn't be that conflict)
[16:49] <ScottK> Ah.  I see.
[16:49] <ScottK> So the odd thing is I drop install-layout=deb it works.
[16:49] <ScottK> geser: Thanks for looking into it.
[16:49] <evanrmurphy> I'm going through documentation for beginners in development. Starting to get a decent handle on pbuilder, and it's my understanding that among other things it uses a chroot environment. Now in the PackagingGuide there's a recommendation to make a chroot environment using debootstrap. Why might I like to have two separate chroot envs? Is pbuilder a very specialized one, perhaps? Thanks in advance.
[16:52] <ScottK> evanrmurphy: You can, but you can also use the pbuilder login option to get an open chroot to work in if you need it.
[16:52] <ScottK> Personally, I just do that.
[16:52] <geser> ScottK: it will FTBFS without --install-layout=deb because of "debian/python-milter/usr/local/lib/python2.6/dist-packages"
[16:53]  * ScottK test builds again.
[16:54] <geser> ScottK: have you the sanitychecks from pkgbinarymangler enabled in your karmic pbuilder?
[16:54] <ScottK> geser: Good point.  Probaby not.
[16:54] <stefanlsd> evanrmurphy: i think you just need the pbuilder one.  its essentiallly a debootstrap with added features. like scottk mentioned, --login and you can login to it.
[16:55] <evanrmurphy> Is there any somewhat standard or recommended dev setup in terms of the chroots, virtual machines, etc. to use while working? I'm looking for a good set of tools to start out with, there just seem to be so many!
[16:56] <evanrmurphy> ScottK, stefanlsd: Thank you.
[16:57] <geser> evanrmurphy: a seperate chroot environment has the advantage that you keep work-in-progress there till is ready (so you can use the tools from karmic while the rest of your system is still jaunty)
[16:58] <stefanlsd> evanrmurphy: have you checked out the MOTU videos that dholbach made. They are excellent and should help show you the basics...https://wiki.ubuntu.com/MOTU/Videos
[16:59] <geser> evanrmurphy: I use a seperate chroot for my MOTU work. this has the advantage that I can upgrade it independent from my normal system and I also don't pollute my main system with all those packages needed during package prepareing (debhelper, cdbs, -dev packages, etc.)
[16:59] <stefanlsd> geser: nice idea actually. /me thinks about doing that...
[17:02] <evanrmurphy> geser: That makes a lot of sense, thanks for explaining. Do you use pbuilder's chroot for that (with the --save-after-login option) or another one? It occurs to me that installing too many packages in the pbuilder chroot might thwart it's purpose as the minimal environment for build testing.
[17:03] <evanrmurphy> stefanlsd: I've watched one or two of those videos, but it's been awhile. I'll take another look at them and spend some more time with the tutorials/docs. :)
[17:04] <stefanlsd> evanrmurphy: yeah, right. i wouldnt --save-after-login for that exact reason.
[17:04] <geser> evanrmurphy: I've a minimal pbuilder for test-building and a second chroot (managed through schroot) for the actual work
[17:05] <stefanlsd> evanrmurphy: http://www.debian-administration.org/articles/566 describes that schroot method
[17:06] <evanrmurphy> great, thanks :)
[17:07] <stefanlsd> evanrmurphy: i think many people have different workflows.  personally i just have my pbuilder to test building and sometimes non-gui program functions. for gui stuff testing i use virtualbox. (although i plan on using kvm)
[17:10] <stefanlsd> heading home. cya guys later!  :)
[17:12] <evanrmurphy> I suppose that debootstrap and schroot are just different ways of getting a chroot.
[17:21] <geser> evanrmurphy: debootstrap is used to create a chroot (with the basic packages installed), schroot is used to "use" it
[17:37] <kb9vqf_> Anyone here willing to rescore a PPA build?
[17:40] <c_korn> trying to build the pidgin 2.5.8 version with the diff.gz of 2.5.7 (from karmic) these errors occur: http://pastebin.com/d64f79db1
[17:41] <MTecknology> dholbach: you around?
[17:42] <dholbach> MTecknology: a bit
[17:43] <MTecknology> dholbach: I was trying ot follow the packaging 101 vid and it's kinda broken..
[17:43] <dholbach> really?
[17:44] <MTecknology> dholbach: ya, just minor things, but I only got about 2min into it
[17:45] <dholbach> can you drop me an email about it?
[17:45] <MTecknology> ed version is out of date, it's available in a tar.gz now and dh has an error about no directory existing, I forgot which
[17:45] <MTecknology> sure thing
[17:45] <dholbach> or add something to https://wiki.ubuntu.com/MOTU/Videos ?
[17:46] <MTecknology> which would you prefer?
[17:46] <dholbach> the wiki
[17:46] <MTecknology> alrighty
[17:46] <dholbach> in the next 6-7 weeks I won't have time to work on it
[17:46] <dholbach> so maybe somebody else wants to pick it up
[17:47] <dholbach> alright, I need to leave for dinner now
[17:47] <dholbach> so see you guys around
[17:47] <dholbach> and thanks again
[17:51] <kb9vqf_> Anyone here willing to rescore a PPA build?
[17:51] <kb9vqf_> 382323
[17:52] <kb9vqf_> This one https://launchpad.net/~ubuntu-389-directory-server/+archive/ppa/+build/1097734 and related were affected by a certificates bug that has since been fixed, but it'll be many hourse before it rebuilds
[17:52]  * kb9vqf_ needs to check his clipboard contents before pasting :)
[18:24] <fabrice_sp> Hi. I'm using update-maintainer to update the control file, but it seems it's not correct in karmic as gaspa told me 2 times it should be "Ubuntu Developer<EMAIL_ADDRESS>instead of the one generated by update-maintainer ("Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>"). Is it a know bug of update-maintainer?
[18:28] <geser> for a package in universe is MOTU correct (unless I missed a memo)
[18:28] <fabrice_sp> geser, that's exactly what I thought, but as I have been 'notified' 2 times, I don't know
[18:29] <geser> it might be related to ArchiveReorg
[18:31] <ScottK> It should still be MOTU.  Perhaps gaspa can explain.
[18:31] <fabrice_sp> ScottK, he is not online. I'll send him an email
[18:32] <fabrice_sp> but I wanted to check before. Thanks!
[18:35] <Ampelbein> fabrice_sp: according to https://lists.ubuntu.com/archives/ubuntu-devel/2009-May/028213.html it should be set to<EMAIL_ADDRESS>[18:36] <Ampelbein> the (unreleased) update-maintainer from ubuntu-dev-tools' bzr does the right thing.
[18:37] <Ampelbein> geser: ^^
[18:37] <RoAkSoAx> here is the explanation for it: https://wiki.ubuntu.com/DebianMaintainerField
[18:37] <ScottK> OK.  Then I guess it's changed.
[18:38] <kb9vqf_> I am trying to get a fix into the official archives for bug 357556 , and have attached a debdiff/followed all the steps on https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue -- is there any way to speed the process along or do I just wait?
[18:40] <fabrice_sp> Ampelbein, thanks for that. How can I get the 'unrelease' version of update-maintainer? Or I have to patch it by myself (which is not complicated :-) )
[18:43] <Ampelbein> fabrice_sp: you can check out the newest ubuntu-dev-tools from: lp:ubuntu-dev-tools
[18:43] <fabrice_sp> Ampelbein, thanks!
[18:43] <Ampelbein> fabrice_sp: or you can download a deb from my ppa: https://edge.launchpad.net/~amoog/+archive/ppa/+files/ubuntu-dev-tools_0.75~amoogppa1_all.deb
[18:44] <fabrice_sp> even easier ;-)
[18:44] <fabrice_sp> thanks Ampelbein
[19:24] <Zhenech> could someone (late) sync pokerth for me (#392983)
[19:27] <fabrice_sp> bug #392983
[19:27] <Riddell> ** Kubuntu Tutorials Day starting in half an hour over in #kubuntu-devel  https://wiki.kubuntu.org/KubuntuTutorialsDay
[19:28] <fabrice_sp> Zhenech, do not assign to motu. Subscribe Ubuntu Sponsor for Universe instead
[19:28] <Zhenech> fabrice_sp, ah, ok
[19:29] <fabrice_sp> you can use requestsync for that: it does all the 'dirty' job :-)
[19:29] <Zhenech> and assign to nobody in the meantime?
[19:29] <Zhenech> does it exist on debian? I have no ubuntu machines here
[19:34] <Zhenech> my apt-file says no :(
[19:36] <Laney> Zhenech: packages.ubuntu.com
[19:36] <stefanlsd> is there any motu-sru that could look at bug #364745 for us please
[19:38] <fabrice_sp> Zhenech, yes: assign to nobody, and let is as New
[19:38] <Zhenech> Laney, that would pull some more ubuntu packages, I somewho dislike this :)
[19:38] <Laney> Zhenech: hmm? it has a search box
[19:39] <Zhenech> Laney, installing "ubuntu-dev-tools" from ubuntu on a debian box I mean
[19:39] <Laney> oh that wasn't my suggestion
[19:39] <fabrice_sp> ohh: that was me (with requestsync :-) )
[19:39] <Laney> you could grab the code from launchpad
[19:39] <Laney> should only require launchpadlib for requestsync
[19:41] <Laney> and debian-python apparently
[20:03] <julien__> hi ! is it ok to ask here for REVU reviews ?
[20:04] <julien__> ok just in case : my package is waiting for approval there : http://revu.ubuntuwire.com/p/flabber
[20:04] <julien__> thanks in advance !
[20:12] <fabrice_sp> julien__, did you check/fix the watch file?
[20:14] <julien__> fabrice_sp: yes at that time I didn't put any watch file at all ... there is one now
[20:14] <julien__> and the upstream version was uploaded in launchpad .. so I guess I'm all set
[20:21] <fabrice_sp> julien__, ok. I'll check ;-)
[20:26] <fabrice_sp> julien__, I'm getting no matching hrefs for watch line
[20:26] <fabrice_sp> so your watch file is not ok
[20:27] <fabrice_sp> I think mok0 said that it's http and not https
[20:27] <stefanlsd> RainCT: good news! got that license issue sorted out with gears. pushing new version to revu now. if you're still keen to advocate, that would be great!  :)
[20:27] <julien__> oh and it's still https, right
[20:28] <julien__> sorry it was a long time ago :/ I'm fixing it right now
[20:29] <RainCT> stefanlsd: great, good work! :)
[20:30] <RainCT> stefanlsd: I'll look at it tomorrow. Remember me if I don't do so.
[20:30] <stefanlsd> RainCT: kk. thanks!
[21:05] <gaspa> ls
[21:07] <stefanlsd> bin boot cdrom dev etc home lib lib32 lost+found mnt opt proc root selinux srv sys usr var
[21:07] <gaspa> geser, fabrice_sp: have you solved the Maintainer puzzle? :P
[21:07] <gaspa> I referred to this: https://lists.ubuntu.com/archives/ubuntu-devel/2009-May/028213.html and I saw that also it was update on  https://wiki.ubuntu.com/DebianMaintainerField
[21:09] <fabrice_sp> gaspa, yes :-D
[21:11] <fabrice_sp> as the update-maintainer script in Karmic is not yet updated, I had to use the version that Ampelbein has in his ppa ;-)
[21:11] <gaspa> fabrice_sp: I saw you already know about update-maintainer...
[21:11] <gaspa> right :P
[21:12] <gaspa> and about filing a debian bug, I know it's difficult, but on the other side they will use python2.6 sooner or later,
[21:18] <fabrice_sp> gaspa, I already filled some about python2.6, but they have been discarded
[21:18] <fabrice_sp> I used submittodebian for that
[21:18] <gaspa> discarded?
[21:19] <gaspa> fabrice_sp: do you mean the DD says "won't fix"?
[21:20] <fabrice_sp> gaspa, Hmmm, I have to check but even if the bug report stay open, the comments were close to a 'won't fix'
[21:20] <fabrice_sp> But i'll submit this one also
[21:20] <gaspa> fabrice_sp: yep, i think it's always worth trying.
[21:21] <fabrice_sp> Some other bug reports I made has been fixed in Debian, but none of python2.6
[21:21] <fabrice_sp> yep: I try to report all the ones that make sense
[21:23] <gaspa> fabrice_sp: keep me in CC, or attach the upstream bug in LP, please.
[21:23] <fabrice_sp> just sent the bug report. I'll attach the Debian bug report to LP
[21:24] <gaspa> fabrice_sp: thanks a lot ;)
[21:24] <fabrice_sp> thank you ;-)
[21:26] <fabrice_sp> Have to go now. Bye!
[21:28] <gaspa> fabrice_sp: bye! :)
[21:34] <POX> fabrice_sp: please point me to these python2.6 related bugs in Debian
[21:44] <asac> something is odd ... i cannot advocate on revu ... i could do that in the past
[21:47] <ajmitch> asac: what's your LP id?
[21:47] <asac> ajmitch: asac
[21:47] <asac> maybe i left the REVU team accidentially?
[21:48] <ajmitch> asac: I've set you as reviewer again
[21:48] <asac> indeed i was just uploader
[21:48] <asac> ajmitch: thanks.
[21:48]  * ajmitch doesn't know why :)
[21:48] <ajmitch> when could you last advocate?
[21:49] <asac> cant remember ;)
[21:49] <asac> wasnt really active in recent past
[21:49] <ajmitch> ah, so if it was awhile ago, things have changed a little :)
[21:49] <asac> okok
[21:49] <ajmitch> you probably had an old revu account which you could have merged
[21:49] <asac> ajmitch: i am now reviewer, however, in launchpad still member of uploaders team only
[21:50] <geser> gaspa: I see that update-maintainer in trunk is already fixed
[21:50] <ajmitch> yes, because I set you to reviewer manually, I'm not sure if team membership sets anything at the moment
[21:50] <ajmitch> if it did, it should probably get it from ~ubuntu-dev
[21:50] <asac> hmm ... okay
[21:51] <asac> yeah thats what i thought
[22:47] <kb9vqf_> ajmitch: A bunch of the 389 libraries passed build test...see https://launchpad.net/~ubuntu-389-directory-server/+archive/ppa
[22:48] <kb9vqf_> We're still working on the main 389 server itself
[22:48] <kb9vqf_> In case you wanted to review them ;-)
[22:48] <ajmitch> probably this evening
[22:48] <ajmitch> and yeah, I'm lucky enough to get info about the PPA build failures now :)
[22:49] <kb9vqf_> :)
[22:49] <kb9vqf_> Can I set the maintainer field to the 389 team?
[22:49] <kb9vqf_> Or does it have to be an individual?
[22:50] <ajmitch> You'll probably need to set XSBC-Original-Maintainer to that, and Maintainer: to Ubuntu Developers
[22:50] <ajmitch> for Debian, a team is best if it's to be team-maintained
[22:51] <ajmitch> now if only you can get everyone to agree on where the packaging should go, whether it be svn.debian.org, or bzr on launchpad or elsewhere
[23:03] <ajmitch> james_w: what changes were made with regards to cutting down on bug spam & linking to LP branches?
[23:19] <julien__> hey, I just updated my package on REVU, if anyone feels like reviewing :D
[23:19] <julien__> it's there : http://revu.ubuntuwire.com/details.py?upid=6205
[23:36] <ryanprior> If I'm building a package and it fails in the end stages, is there a way I can run debuild again without having to recompile everything? I'm getting a bunch of messages like "dpkg-source: error: cannot represent change to ecere-sdk-0.44d2.1/ec/release/pass15.o: binary file contents changed" How can I start the process again without having to clean everything and compile over again?
[23:37] <RAOF> ryanprior: You can pass -nc to dpkg-buildpackage (& probably debuild, but I haven't tried that) to tell it to not run the "clean" target.
[23:38] <julien__> ahm quick question : how do I tell pbuilder to act like dpkg-buildpackage -S does ? if I want to upload the result to revu
[23:40] <julien__> curently with "pbuilder build --debbuildopts -S"  it says "dpkg-buildpackage: cannot combine -b and -S"
[23:40] <Ampelbein> julien__: why would you want pbuilder for that?
[23:40] <Ampelbein> julien__: debuild -S -sa from the source-dir will create the sourcepackage.
[23:42] <julien__> I see .. no point entering a specific distribution/arch chroot for just this action ?
[23:44] <ryanprior> RAOF: thanks
[23:44] <ryanprior> where is a good place to install sample code?
[23:45] <RAOF>  /usr/share/doc/$PACKAGENAME ?
[23:45] <Ampelbein> julien__: right.
[23:45] <ryanprior> RAOF: thanks again
[23:53] <julien__> ok thank you Ampelbein :) good night everybody
[23:54] <Ampelbein> julien__: you're welcome, good night.


[17:07] <qwebirc7333> Question: How do you change the dpi settings in X when using the intel driver.  I'm able to do it with the UseEdidDpi and DPI options but they get ignored by the intel driver.  I'm on Mythbuntu 11.10.
[18:09] <patdk-lap> I normally just set it in xorg.conf
[18:11] <qwebirc7333> I do too for nvidia but for intel Xorg.0.log shows that those options are ignored
[18:12] <patdk-lap> hmm thought they worked for my index
[18:12] <patdk-lap> intel
[18:12] <patdk-lap> but haven't bothered
[18:14] <qwebirc7333> The warning line looks like this....(WW) intel(0): Option "DPI" is not used


[08:50] <cjwatson> wgrant: Did https://code.launchpad.net/~cjwatson/launchpad/db-builder-version/+merge/190633 look OK?
[08:50] <cjwatson> Aside from insane sampledata diff
[09:03] <wgrant> cjwatson: Oh, sorry, missed that. The patch looks fine.
[09:07] <StevenK> That was me using a raring machine to generate the current sampledata
[09:07] <cjwatson> Oh, and re the JS failures on precise, did anyone happen to spot https://bugs.launchpad.net/launchpad/+bug/1090395 ?
[09:07] <_mup_> Bug #1090395: YUITest failures because quantal's webkit disagrees with lucids <javascript> <python-upgrade> <spurious-test-failure> <Launchpad itself:Triaged> <https://launchpad.net/bugs/1090395>
[09:13] <wgrant> Yeah
[09:29] <cjwatson> StevenK: immutable> I guess that was a regression due to my change some time back.  Sorry and thanks.
[10:06] <cjwatson> Err, whoops
[10:07] <cjwatson> wgrant: I seem to have accidentally landed db-builder-version on devel
[10:07] <wgrant> Yeah, just noticed that
[10:07] <cjwatson> wgrant: Is the best recovery path to re-propose to db-devel and land there as well?
[10:07] <wgrant> cjwatson: Nah, we have nothing urgent landing atm, will deploy it on Monday
[10:07] <cjwatson> Or just wait for the auto-merge to db-devel
[10:07] <cjwatson> ?
[10:07] <wgrant> It'll land on db-devel in about 20 minutes :)
[10:07] <wgrant> yeah
[10:08] <cjwatson> OK.  Sorry about that
[10:08] <wgrant> np
[13:27] <wgrant> cjwatson: Doing that without adjusting some nagios checks might upset some sysadmins.
[13:28] <wgrant> Also potentially ppa_reset
[13:30] <cjwatson> ppa_reset should be OK - it greps for BuilderStatus.IDLE anywhere in the output, which is still there
[13:31] <wgrant> Ah, good
[13:31] <cjwatson> Are the nagios checks in bzr anywhere?
[13:31] <wgrant> check_builder_status or something might be in puppet
[13:31]  * wgrant looks
[13:31] <wgrant> The ABORTED check will break
[13:32] <cjwatson> Where's that?
[13:32] <wgrant> In fact I guess the whole thing will crash because it uses status[0]
[13:32] <wgrant> files/nagios/plugins/check_builder_status in memento
[13:32] <cjwatson> ok, should be able to fix that
[13:32] <cjwatson> thanks


[04:13] <pfifo> I noticed that the livecd is using aufs, and that i cannot mount anything with unionfs. Has ubuntu stopped supporting unionfs? Should I start using aufs in my own projects?
[08:14] <dholbach> good morning
[09:09] <bilalakhtar> good morning dholbach !
[09:10] <dholbach> hi bilalakhtar
[09:23] <ogra> TheMuso, i would like to see the fix mentioned in bug 631362 merged in pulse, any objections from your side ?
[09:24] <ogra> (we need to be able to do arch specific configs on some arm platforms)
[09:28] <tkamppeter> Anyone around who could do an update on the seeds for Maverick?
[09:40] <cjwatson> tkamppeter: what sort of change?
[09:42] <micahg> kdevelop's i386 packages have been pending publication for 3 days now
[09:43] <cjwatson> they're in NEW, I'll process that in a moment
[09:43] <micahg> cjwatson: ok, thanks :)
[09:44] <tkamppeter> cjwatson, I have introduced putting PPDs in compressed archives in foomatic-db. The ready-made PostScript PPDs are already in such archives as there seed changes where not needed. This saves several MB on the desktop CDs. To save another 18 MB in the installed system I have also a replacement of the Foomatic XML data by a compressed PPD archive, but this needs replacing the requirement of foomatic-db-engine and foomatic-db by the requir
[09:44] <tkamppeter> ement of foomatic-db-compressed-ppds in the seeds. This makes also the listing of all printer drivers ("lpinfo -m", adding printer with s-c-p) significantly faster. I have discussed this change with pitti last week.
[09:44] <micahg> doh, it says that on the main build page for the version :-/
[09:44] <cjwatson> tkamppeter: changing the seeds is premature by a couple of hours, since I'm only just processing foomatic-db-compressed-ppds through the NEW queue ;-)
[09:45] <tkamppeter> cjwatson, and pitti found it a good idea, and he has helped me to put the correct dependencies into the packages.
[09:45] <tkamppeter> cjwatson, OK.
[09:45] <cjwatson> sure - it needs to wait until foomatic-db-compressed-ppds is published, but I can make the change then
[09:45] <cjwatson> is there any remaining case where foomatic-db-engine and foomatic-db should be listed?
[09:46] <tkamppeter> cjwatson, no, end users do not need these two packages any more. Now these packages appear only in build dependencies of other packages.
[09:46] <cjwatson> ok
[09:47] <cjwatson> micahg: processed
[09:47] <tkamppeter> I have taken care of that by modifiying also the gutenprint and ptouch-driver packages where I have also replaced Foomatic XML data by compressed PPD archives.
[09:47] <micahg> cjwatson: thanks, sorry, I shouldn't have bothered you for that
[09:48] <tkamppeter> cjwatson, thanks already now.
[10:13] <cjwatson> ivoks_away: is anything happening with bug 527195?  I've promoted a couple of its dependencies, following approved MIRs
[11:00] <cjwatson> tkamppeter: done your seed changes
[11:14] <tkamppeter> cjwatson, thank you very much.
[11:32] <cjwatson> hm, I seem to have accidentally made this my archive admin morning
[11:39] <G> ttx: can I assume that bug 619302 got SRU approval?
[12:03] <happyaron> cjwatson: hi, could you have a look at this FTBFS, it seems due to cannot find libopencc-dev. https://edge.launchpad.net/ubuntu/+source/ibus-pinyin/1.3.10-1/+build/1948578
[12:05] <cjwatson> happyaron: I don't need to look at it :)
[12:05] <cjwatson> happyaron: I promoted opencc to main, but ibus-pinyin will have tried to build before that was committed to the archive - it just needs to be retried in an hour or two
[12:06] <happyaron> cjwatson: oh, thanks
[12:06] <happyaron> cjwatson: will the builder retry it automatically?
[12:07] <cjwatson> happyaron: no, I'll retry it when it's appropriate
[12:07] <cjwatson> well actually it might
[12:07] <happyaron> thanks
[12:13] <tkamppeter> cjwatson, I have a question to the seed changes. Will they also affect Kubuntu, Xubuntu, Edubuntu, and especially the netbook editions? Especially on netbooks saving 18 MB on the installed system would be nice.
[12:14] <Riddell> tkamppeter: only if you're changing the platform.maverick seed
[12:15] <cjwatson> tkamppeter: yes.
[12:15] <cjwatson> (the change was in platform.maverick/desktop-common)
[12:16] <cjwatson> Ubuntu Studio needed to have the change copied over manually; I've done that
[12:16] <cjwatson> but the others will pick it up naturally
[12:24] <ttx> G: no.
[12:34] <G> ttx: it's okay, I was thinking about the wrong bug anyway :)
[12:35] <cjwatson> ScottK: why can't all the stuff in kubuntu-meta/README.Kubuntu.update be done by the update script?
[12:35] <Riddell> cjwatson: it should be, neither of us have spent the five minutes it would take to do it yet
[12:37] <cjwatson> maybe we should just take the opportunity to make it a new seed collection.  the current implementation is fundamentally wrong because it causes LP to want to put all the kubuntu-mobile packages in main
[12:39] <Riddell> that would also seem sensible
[12:39] <ogra> doko, !
[12:42] <persia> cjwatson, Riddell: so, last week we talked about having kubuntu-mobile be a separate seed collection (I filed some of the relevant bugs), and it does require a LP change that would have had to be rolled out today.  The feedback I received all seemed to indicate it would be better to just do MIRs for the kubuntu-mobile stuff (and I think most of them are filed).
[12:42] <cjwatson> what LP change?
[12:42] <persia> cron.germinate
[12:43] <cjwatson> I suppose
[12:43] <cjwatson> yes, if you wanted Task fields
[12:44] <persia> bug #626543 was the bug to make kubuntu-mobile go in universe.  MIRs were bugs #627138 and 626583
[12:52] <ogra> doko, do you have any idea about OO.o on armel ?
[12:53] <doko> ogra: yes, somehow. working on this
[12:53] <ogra> awesome :)
[13:46] <bilalakhtar> mvo: around?
[13:46] <mvo> hey bilalakhtar, yes
[13:47] <bilalakhtar> mvo: Whenever you have time, could you please endorse https://wiki.ubuntu.com/BilalAkhtar/MOTUApplication ?
[13:47] <bilalakhtar> There is a week before the meeting, so you can endorse on any day
[13:47] <bilalakhtar> I just informed you beforehand
[13:47] <mvo> thanks, will do
[13:47] <bilalakhtar> mvo: I should thank you!
[14:15] <ivoks_away> cjwatson: i'm waiting for aproval of cluster-glue (bug 527142)
[14:23] <cjwatson> ivoks: I realise that, but it would be worth responding to the concerns about pacemaker in the meantime, would it not?
[14:24] <ivoks> cjwatson: of course
[15:27] <alexvalavanis> Hi there (new to IRC, so please forgive mistakes!)
[15:27] <ttx> ScottK: sorted out the cobertura-maven-plugin FTBFS situation.
[15:27] <alexvalavanis> Can anyone advise how to perform a merge from Debian experimental?
[15:27] <alexvalavanis> MoM doesn't seem to cover it
[15:28] <alexvalavanis> and there's no lp:debian/experimental/* branch on Launchpad bzr access
[15:29] <ttx> alexvalavanis: yes there is...
[15:29] <cjwatson> you can always do it by hand - save diff from common-base version to current Ubuntu to a file, unpack current Debian, selectively apply patches from file
[15:29] <ttx> lp:debian/experimental/tomcat6
[15:29] <ttx> https://code.launchpad.net/debian/experimental/+source/tomcat6
[15:31] <alexvalavanis> @ttx I can't seem to find the branch I wanted: https://code.launchpad.net/debian/experimental/+source/inkscape
[15:32] <alexvalavanis> Is there a delay between a debian upload making it into bzr on Launchpad?
[15:32] <ttx> alexvalavanis: hmm, indeed
[15:33] <alexvalavanis> Thanks, cjwatson.  I thought about a manual merge, but I figured there was too much scope for me messing it up!
[15:33] <ttx> alexvalavanis: should be in, there must be some import issue
[15:35] <alexvalavanis> weird.  So do the Bazaar branches normally sync immediately?
[15:36] <alexvalavanis> The debian/experimental/inkscape upload was made 3 weeks ago
[16:04] <tjaalton> tkamppeter: re bug 612578, no change after backporting cups 1.4.4 from maverick
[16:24] <Riddell> mvo: is there a GUI in Ubuntu Desktop to change /etc/update-manager/release-upgrades from lts to normal ?
[16:30] <mvo> Riddell: yes, its in software-properties-gtk
[16:30] <mvo> Riddell: under "updates/Release upgrades"
[16:35] <Riddell> mvo: fooey, that's something I need to add to the kde UI then
[16:35] <shadeslayer> Riddell: IIRC theres also a option in synaptic
[16:36] <mvo> shadeslayer: its the same dialog they both use
[16:36] <mvo> Riddell: ok, should be trivial :)
[16:36] <shadeslayer> mvo: right.. didnt know that :)
[16:55] <ScottK> ttx: Cool.
[16:56] <ScottK> cjwatson: I'm glad to adjust the kubuntu-mobile stuff as needed.  How it is now is just the best I knew to do in the time I had.
[16:56] <cjwatson> if it's all going into main, then it can stay as it is pending that, I think
[16:57] <cjwatson> if kubuntu-mobile is going to stay in universe, then it needs to be a separate seed collection which as persia says would require a Launchpad change
[17:12] <Riddell> mvo: any idea what the mysql-server-core error is here? http://muse.19inch.net/~jr/tmp/upgrade/main.log
[17:13] <mvo> Riddell: what is the md5sum of that file /var/cache/apt/archives/mysql-server-core-5.1_5.1.49-1ubuntu7_i386.deb ?
[17:16] <Riddell> mvo: cad2c149aa7c9521d7794c4589f4cd2c  /var/cache/apt/archives/mysql-server-core-5.1_5.1.49-1ubuntu7_i386.deb
[17:16] <Riddell> mvo: hmm, which does seem to be incorrect
[17:17] <mvo> Riddell: hm, so fs corruption :/ ?
[17:17] <Riddell> mvo: maybe, I'll try the upgrade again
[17:17] <mvo> Riddell: iI doner if you can copy it to some other place and do a binary diff on it (compared to a downloadied one)
[17:18] <mvo> Riddell: it might be a bit-flip error
[17:52] <cjwatson> Keybuk: bug 603760 et al: I can easily add /var/run/sendsigs.omit.d/ support to sendsigs, but I don't really feel like playing whack-a-mole to move everything over to that directory, and having /var/run/sendsigs.omit and /lib/init/rw/sendsigs.omit.d/ seems wilfully confusing.  Would you object to a new mounted-libinitrw.conf job in mountall that just does 'exec mkdir -p /lib/init/rw/sendsigs.omit.d'?
[17:52] <cjwatson> that seems like the easiest fix
[17:59] <Riddell> mvo: bug 631708 FYI
[18:02] <Keybuk> cjwatson: such things are boot critical path
[18:02] <Keybuk> (anything run in a mounted-* is)
[18:05] <cjwatson> Keybuk: do you have an alternative suggestion?
[18:06] <mvo> thanks Riddell
[18:08] <dupondje> https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/631548 => bluetooth seems completely broken ...
[18:09] <seb128> dupondje, do you have empathy installed?
[18:09] <seb128> dupondje, it's likely a known issue for users who remove empathy
[18:09] <dupondje> GLib-GIO-ERROR **: Settings schema 'org.gnome.Bluetooth' is not installed
[18:10] <seb128> right
[18:10] <dupondje> ii  empathy                                           <IP_ADDRESS>-0ubuntu2                              GNOME multi-protocol chat and call client
[18:10] <seb128> ls /usr/share/glib-2.0/schemas?
[18:10] <dupondje> $ ls /usr/share/glib-2.0/schemas
[18:10] <dupondje> gschemas.compiled                                            org.freedesktop.Telepathy.Logger.gschema.xml  org.gnome.Empathy.gschema.xml  org.gnome.gcalctool.gschema.xml        ubuntu-artwork.gschema.override
[18:10] <dupondje> org.freedesktop.gstreamer-0.10.default-elements.gschema.xml  org.gnome.brasero.gschema.xml                 org.gnome.Evince.gschema.xml   org.gnome.Nautilus.Sendto.gschema.xml
[18:11] <seb128> oh, I didn't get that update yet
[18:11] <seb128> sorry I was confusing with another bug
[18:11] <seb128> dupondje, we will fix it
[18:12] <dupondje> lets hope :) cause I see bluetooth crashes quite some time :)
[18:45] <Chipaca> apachelogger: ping
[19:04] <dupondje> thanks for the fast fix seb128  :)
[19:04] <dupondje> it works, but another thing in the properties view: 'Cannot start 'File sharing'-preferences ... any idea ?
[19:04] <dupondje> also https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/630543 :) but thats not a big issue
[19:05] <seb128> dupondje, you're welcome
[19:05] <dupondje> always cool to see such good response :)
[19:06] <seb128> dupondje, not sure about this one
[19:06] <seb128> I've seen logs with permissions errors
[19:06] <seb128> it could be something else in the stack or a linux issue
[19:06] <seb128> I will check that later
[19:06] <seb128> gtg for dinner
[19:06] <seb128> see you ;-)
[19:08] <dupondje> njoy :)
[19:49] <goruka> hi guys, i tried out the beta because 10.04 worked poorly for me, and it seems i can't use the nvidia driver with the xorg version that comes with 10.10 beta.. any hints?
[19:49] <goruka> (nvidia driver says xorg is too new)
[19:51] <beuno> goruka, try a support channel, #ubuntu+1
[19:51] <goruka> ah cool, thanks!
[20:22] <apachelogger> Chipaca: pong
[20:23] <Chipaca> apachelogger: hi
[20:24] <Chipaca> apachelogger: well... I said it as a comment on #375145, dunno if you've read it yet
[20:24] <Chipaca> apachelogger: but: sorry to read your comment there. Sad that it probably means we're not getting u1 in kde in m or even close. Sad that we couldn't work together. What went wrong?
[20:44] <apachelogger> Chipaca: in theory it should be working (except that the ubuntu-sso-client misses a kwallet backend), wasnt able to test because of brokenness in maverick
[20:44] <apachelogger> what's most importantly missing is a maintainer though
[20:45] <apachelogger> as for what went wrong: general communication problem && moving target && brokenness now and then
[20:46]  * apachelogger would be happy to chat about that at UDS, if he gets sponsored that is ^^
[21:40] <ricotz> slangasek, hello, could you have a look at https://bugs.edge.launchpad.net/ubuntu/+source/lxc/+bug/630030
[22:32] <flixil> Hello. I'm trying to mix branches of software like I used to do in debian. I'm using lucid and I'm trying to mix with the newest in maverik but I cannot access them change lucid for maverik in /etc/apt/sources.list   What is the name I should use?
[22:32] <flixil> Thanks
[22:34] <flixil> Oh shit sorry I mispelled maverik and it's maverick. Now it works :)
[22:44] <YokoZar> Blast, dput via sftp is throwing an exception and I can't upload a new ia32-libs
[22:50] <cjwatson> try ftp
[22:54] <YokoZar> cjwatson: doesn't work for ia32-libs on my internet connection
[22:54] <YokoZar> I think I figured it out it was a bad dput.cf  because the launchpad blog instructions were missing a step ;)
[22:55] <YokoZar> need to change "incoming = /" to "incoming = ubuntu"
[22:55] <YokoZar> which I believe doesn't break ftp, so it would be a nice default
[22:56] <Laney> YokoZar: is it "Exception AttributeError: "'NoneType' object has no attribute 'close'" in <function terminate at 0x2695938> ignored"?
[22:56] <YokoZar> Laney: Yup
[22:57] <Laney> I get that with every upload
[22:57] <YokoZar> Laney: just after "open failed"
[22:57] <Laney> but they still work
[22:57] <YokoZar> Laney: I think the "open failed" part is more important
[22:57] <Laney> yes, likely
[22:57] <Laney> I see no other errors
[22:58] <YokoZar> Laney: hmm good to know the exception is unrelated to the open failure I suppose
[23:37] <TheMuso> ogra: I have other pulse changes to make, so sure I'll get it in.
[23:38] <mwhudson> hi, i've found a packaging bug that's been inherited from debian
[23:38] <mwhudson> should i report it to bugs.debian.org as well as launchpad?
[23:38] <lifeless> yes
[23:44] <mwhudson> does the package importer import uploads from sid?
[23:45] <mwhudson> or just squeese?
[23:46] <cjwatson> both
[23:47]  * mwhudson urlhacks
[23:48] <cjwatson> code.launchpad.net/debian/+source/PKG should link to them
[23:49] <mwhudson> cjwatson: actually no, https://code.edge.launchpad.net/debian/+source/python-defaults hides the sid branch a bit
[23:50] <cjwatson> well, link to something that links to it
[23:50] <mwhudson> yeah
[23:50] <cjwatson> that presentation is a bit of a bug anyway
[23:51] <mwhudson> it probably works ok for ubuntu
[23:51] <cjwatson> given that sid is the principal upload target for Debian developers, and the principal source for Ubuntu merges
[23:51] <cjwatson> it's wrong both ways
[23:51] <cjwatson> it was OK briefly in lucid when we were doing most of our merging from testing
[23:51] <cjwatson> but the rest of the time we merge from unstable, and certainly want to know what's going on in unstable
[23:52] <cjwatson> the problem is that LP really doesn't model testing/unstable particularly well, I suppose
[23:52] <mwhudson> cjwatson: i meant code.launchpad.net/ubuntu/+source/PKG is probably ok
[23:53] <cjwatson> right
[23:53] <mwhudson> but yeah, launchpad models ubuntu ok and debian poorly
[23:53] <cjwatson> I realised that partway through but reckoned what I said still made sense more or less :)
[23:54] <mwhudson> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595826 fwiw


[01:56] <krytarik> guiverc: Looks like there are some bits in the post that are monospace-formatted, also if you used header tags like <h3> for the headers then it'd be properly formatted in feed readers too.
[01:59] <guiverc> I couldn't remember the header code; nor find my notes - thus the medium font used for headers etc, sorry
[02:00] <krytarik> http://fridge.ubuntu.com/2019/10/18/ubuntu-19-10-eoan-ermine-released/ - most recent prior art from yourself. >_>
[02:01] <guiverc> yeah I see it in liferea without the 'font' change... :(
[02:11] <guiverc> h3 added
[03:53] <krytarik> Yay! \o/
[06:00] -BottyMcBotFace:#ubuntu-news- ::Softpedia:: Ubuntu, Kubuntu, Xubuntu 18.04.4 LTS Now Available for Download @ https://news.softpedia.com/news/ubuntu-kubuntu-xubuntu-18-04-4-lts-now-available-for-download-529182.shtml (by Bogdan Popa, Microsoft News Editor)
[08:06] -BottyMcBotFace:#ubuntu-news- ::Fridge:: Ubuntu 18.04.4 LTS released @ http://fridge.ubuntu.com/2020/02/12/ubuntu-18-04-4-lts-released/ (by guiverc)
[11:37] -BottyMcBotFace:#ubuntu-news- ::Security:: Episode 62 @ https://ubuntusecuritypodcast.org/episode-62/
[20:09] -BottyMcBotFace:#ubuntu-news- ::OMG!Ubuntu:: Rhythmbox 3.4.4 Adds ListenBrainz Plugin, New App Icon @ https://www.omgubuntu.co.uk/?p=163513 (by Joey Sneddon)
[20:50] -BottyMcBotFace:#ubuntu-news- ::Planet:: Jonathan Carter: Initial experiments with the Loongson Pi 2K @ https://jonathancarter.org/2020/02/13/initial-experiments-with-the-loongson-pi-2k/
[23:13] -BottyMcBotFace:#ubuntu-news- ::Portugal:: Ep 77 – Passwords, pela trigésima oitava vez! @ https://podcastubuntuportugal.org/e77/
[23:15] -BottyMcBotFace:#ubuntu-news- ::Planet:: Podcast Ubuntu Portugal: Ep 77 – Passwords, pela trigésima oitava vez! @ https://podcastubuntuportugal.org/e77/


[10:16] <Jordan_U> The situation with erry in #ubuntu right now is a train wreck, he's not coherent and too many people are trying to help him at once.
[10:20] <bazhang> he/she refuses to listen or read
[10:21] <bazhang> he/she wants a single command to fix everything, which is not the way grub2 works
[10:27] <jussi> makes it hard. tried PM?
[10:29] <Jordan_U> Yes, I couldn't get her to answer questions and she was still getting input from the channel. ikonia seems to have dealt with the problem well though.
[10:32] <bazhang> she has done that over the years now