[00:00] <AdamDH> is my install line correct: cd src && $(MAKE) install prefix=$(CURDIR)/debian/msp430-binutils/usr ?
[00:02] <jmarsden|work> AdamDH: define prefix before the install target :)
[00:03] <jmarsden|work> cd src && make prefix=$(CURDIR)/debian/msp430-binutils/usr install
[00:03] <AdamDH> so some where I have made a mess of my VM and installed it somewhere!
[00:03] <AdamDH> thanks for all the help jmarsden
[00:03] <AdamDH> i will try that
[00:03] <jmarsden|work> Possibly, but only if you were running as root...?
[00:05] <jmarsden|work> You could test it by hand:  mkdir -p /tmp/junk/usr && cd src && make prefix=/tmp/junk/usr install  # and check what ends up under /tmp/junk
[00:07] <AdamDH> i am running as root probally a bad idea
[00:08] <jmarsden|work> Definitely a bad idea.  The whole packaging system is designed so you do not need to do that... hence the fakeroot package, for example...
[00:11] <AdamDH> YES! got a working package, thanks all for the help, need to tidy up my rules but at least I know now how it all works
[00:11] <AdamDH> took some time but I got there
[00:12] <AdamDH> probally going to have more questions later as I have a few more packages to make
[00:14] <jmarsden|work> Have fun :)
[00:15] <AdamDH> one thing, my package has been named as msp430-binutils_msp430-binutils-2.18-msp430-cvs.0.0.20081229_amd64.deb instead of msp430-binutils_msp430-binutils-2.18-msp430-cvs.0.0.20081229_amd64.deb not sure why as the directory structure is correct
[00:15] <AdamDH> i mean the correct name should be msp430-binutils_binutils-2.18-msp430-cvs.0.0.20081229_amd64.de
[00:16] <Laney> AdamDH: the bit between the _s comes from your debian/changelog
[00:17] <AdamDH> thats in my changelog msp430-binutils-2.18-msp430-cvs.0.0.20081229
[00:17] <Laney> well then
[00:18] <Laney> that explains it, no?
[00:18] <AdamDH> slightley confused
[00:18] <Laney> make the version in the changelog the same as what you want to be between the _s in the resulting deb
[00:19] <Laney> ie binutils-2.18-msp430-cvs.0.0.20081229
[00:19] <jmarsden|work> AdamDH: name is PACKAGE_version-from-changelog_ARCH.deb
[00:19] <AdamDH> ah right follow looks like I screwed up the versioning then when I packaged it
[00:24] <AdamDH> for inclusion into the main tree do my packages need man pages?
[00:25] <jmarsden|work> Yes, I'm pretty sure they will.
[00:27] <AdamDH> looks like I have to write some as there are non with the project, in fact documentation is lacking, I wrote a php script to get the sources and make the patches etc and tidying things up before packaging and to mirror the project
[00:31] <jmarsden|work> No man pages for gcc and binutils???  Surely there are some?
[00:35] <AdamDH> its a cross compiler so non that are for the actual msp430 port
[00:36] <AdamDH> are for the general gcc just not for the arch the compiler is working with
[00:36] <AdamDH> i will see what the AVR project did
[04:57] <CarlFK> http://dpaste.com/103619/   dpkg-buildpackage ...   line 164: debian/rules: Permission denied
[05:00] <Pici> chmod +x debian/rules
[05:00] <jmarsden> CarlFK: chmod 775 debian/rules
[05:01] <CarlFK> cool.  thanks
[05:10] <secraberries> kinda quiet
[05:12] <StevenK> 775!? 755
[05:13] <secraberries> sure
[05:21] <NCommander> hey StevenK
[05:33] <CarlFK> http://dpaste.com/103621/  Setting up libpoppler-glib3 (0.8.7-1.1) ....  libpoppler-glib-dev depends on libpoppler-dev (= 0.8.7-1.1); however:   Version of libpoppler-dev on system is 0.8.7-1.
[05:33] <CarlFK> lies!
[05:33] <CarlFK> oh wait..glib3... dev..
[05:34] <CarlFK> never mind.  all is well
[08:29] <hyperair> revu, anyone? http://revu.ubuntuwire.com/details.py?package=codelite
[09:53] <DktrKranz> has anybody ever seen something similar to this?
[09:53] <DktrKranz> /usr/include/bits/stdio2.h: In function 'int sprintf(char*, const char*, ...)':
[09:53] <DktrKranz> /usr/include/bits/stdio2.h:35: error: '__builtin_va_arg_pack' was not declared in this scope
[10:25]  * StevenK kicks ffmpeg-debian until bits fall off.
[10:25] <iulian> DktrKranz: See bug #293807.
[10:25] <RAOF> So, not very hard, then.
[10:25] <StevenK> Who's bright idea was it to move all of the header files around, anyway?
[10:26]  * StevenK grins at RAOF, and kicks ffmpeg-debian until it implodes
[10:26] <DktrKranz> iulian, yep... I've seen it, and it's seems it's already fixed upstream
[10:27] <iulian> DktrKranz: Was that the package you were working on?
[10:27] <RAOF> Mmmm, Mocha Chill.  The drink no-one seems interested in shipping out east.
[10:27] <DktrKranz> iulian, it was insighttoolkit
[10:27] <DktrKranz> it FTBFS that way
[10:27]  * iulian takes a peek at it.
[10:27] <StevenK> RAOF: Hmmm?
[10:28] <StevenK> Hmmm. New wine.
[10:29] <RAOF> StevenK: Wests Mocha Chill, or some such.  It was briefly stocked in NSW supermarkets last year, but isn't any more.
[10:30]  * hyperair wonders if there's anybody free enough to review a package: http://revu.ubuntuwire.com/details.py?package=codelite
[10:31] <StevenK> RAOF: Perhaps it got branded with the same disdain that West Coast gets and was ignored ...
[10:32] <StevenK> -		--with-ffmpeg-includes=/usr/include/ffmpeg
[10:32] <StevenK> +		--with-ffmpeg-includes=/usr/include/libavcodec\ -I/usr/include/libavformat
[10:32]  * StevenK sighs at siretart and ffmpeg-debian
[10:32] <StevenK> That so shouldn't work
[10:33] <StevenK> VideoEffectClip.H:31: error: conflicting declaration 'typedef struct gavl_video_frame_s gavl_video_frame_t'
[10:33] <StevenK> /usr/include/gavl/gavl.h:1869: error: 'gavl_video_frame_t' has a previous declaration as 'typedef struct gavl_video_frame_t gavl_video_frame_t'
[10:34]  * StevenK whimpers pathetically
[11:49] <StevenK> Haha
[12:01] <quentusrex> How is it possible to have a package in my repo, and have  a numbered release such as 1.0.2
[12:01] <quentusrex> Then also have a package 1.0.2-svn2340???
[12:01] <quentusrex> and if someone wants to run trunk, then they can, but otherwise they can only run the standard release???
[12:02] <Laney> package and package-snapshog
[12:02] <Laney> t*
[12:03] <quentusrex> so it'd be handled like two different packages?
[12:03] <quentusrex> that works.
[12:04] <directhex> and your version number should be something like 1.0.2+svn2340-1 if it's based on 1.0.2 with addons, or 1.0.3~svn2340-1 if it's based on an as-yet unreleased 1.0.3
[12:06] <quentusrex> awesome. thanks.
[12:16] <RAOF> Answer: experimental's grub2 appears to be missing the --fs-uuid option to search, thus breaking the config.  Score!
[12:17] <StevenK> Haha
[12:18] <RAOF> At least it's got tab-autocompletion and a bash-like shell.
[12:18] <RAOF> Now, if it only had a dvorak keymap...
[12:19] <laga> well, grub1 also has tab completion and a shell
[12:20] <RAOF> That wasn't meant to be a comparison; just that it's infinitely easier to fix because it *does* have those features than if it didn't.
[12:20] <laga> yeah.
[12:25] <NCommander> RAOF, your a dvoark user?
[12:25] <laga> epic.
[12:26] <StevenK> I'd learn dvorak, but I'm scared my wrists would break since they're use the brain-damage of qwerty
[12:26] <StevenK> s/use/used to/
[12:29] <NCommander> StevenK, I used to use dvorak, but then I found that by being incompable with the rest of the world sucked
[12:29] <NCommander> although I think in the end my WPM went up
[12:29] <StevenK> Neat way to make sure no one touches your computer
[12:30] <StevenK> Hard to ssh into other machines using other peoples keyboards, then
[12:30] <NCommander> StevenK, yeah, thats why I never changed the caps back to QWERTY after the experiment
[12:30]  * NCommander is too paranoid on breaking this laptops caps to try and rearrange them though ...
[12:32] <NCommander> StevenK, so how was your holiday BTW?
[12:32] <StevenK> Still going
[12:37] <quentusrex> I accidentally forgot to include a binary file in the orig, how can I update the orig and upload it to launchpad? or delete the orig that's in launchpad?
[12:38] <james_w> StevenK: did you get anywhere with openmovieeditor?
[12:38] <quentusrex> I'm trying to execute:  debuild -S -sd to rebuild the package with the binary file I forgot. but it's giving me the error:  dpkg-source: error: cannot represent change to freeswitch-1.0.2/libs/libshout-2.2.2.tar.gz: binary file contents changed
[12:39]  * StevenK checks
[12:39] <quentusrex> And I can't change the orig and upload it because launch pad says it already has an orig.
[12:40] <StevenK> james_w: Yeah. Now it wants img_convert from ffmpeg, but that isn't exported, since it's the old API, and disabled when you enable swscaler.
[12:40] <james_w> you need to change the upstream version number
[12:40] <james_w> StevenK: add libswscale-dev to Build-Depends
[12:40] <james_w> StevenK: see the Debian bug report
[12:40] <StevenK> Hmm
[12:41] <quentusrex> james_w: from freeswitch-1.0.2-1ubuntu2 to???
[12:41]  * StevenK tries that
[12:41] <james_w> StevenK: however, it uses another deprecated ffmpeg function which has been removed in the version we have. Upstream has completely rewritten the code.
[12:42]  * StevenK tries to not lose control and scream like a banshee
[12:42] <Hobbsee> just pull it from the archive...
[12:42] <StevenK> I'm seriously tempted to remove ffmpeg-debian and all of it's rdepends
[12:45] <StevenK> AudioFileFfmpeg.cxx:135: error: 'avcodec_decode_audio' was not declared in this scope
[12:45] <StevenK> james_w: I see that.
[12:45] <quentusrex> james_w: from freeswitch-1.0.2-1ubuntu2 to???
[12:46] <james_w> StevenK: that's the one
[12:46] <james_w> quentusrex: freeswitch-<IP_ADDRESS>.repack-1ubuntu2 or something
[12:48] <quentusrex> should I be using debuild -S -sa or debuild -S -sd?
[12:49] <Hobbsee> quentusrex: -sa, as you want to be uploading the orig tarball to launchpad
[12:49] <quentusrex> ok
[12:49] <StevenK> FWIW, tarball in tarball is just sickening
[12:50] <quentusrex> the software either needs the tarball in the libs/ folder or it will use svn to get it during build.
[12:50] <quentusrex> but launchpad doesnt' allow internet access during build.
[12:50]  * StevenK retches
[12:50] <quentusrex> so, I have to manually include them... so that they'll build...
[12:51] <quentusrex> yeah, I hate it. but the software works REALLY well and builds well too
[12:51] <quentusrex> but it's hard to automatically package.
[12:51] <james_w> huats: hey 4k, how are you?
[12:53] <quentusrex> how do I cancel a launchpad build? It's hung....
[12:53] <maxb> It'll time out eventually
[12:53] <quentusrex> maxb: that'll take too long and take up too much resources...
[12:53] <Hobbsee> you can't.
[12:53] <quentusrex> :(
[12:54] <quentusrex> it's been an hour
[12:54] <quentusrex> https://launchpad.net/+builds/hassium
[12:54] <StevenK> It will time out after 150 minutes
[12:54] <quentusrex> :(
[12:54] <quentusrex> but I need to trial and error to figure this out...
[12:55] <StevenK> Wait, it gets tarballs from SVN?
[12:55] <quentusrex> StevenK: yes...
[12:55] <StevenK> Oh man, it gets even more disgusting
[12:55] <StevenK> Right, I'm not sure that will die on it's own
[12:56] <quentusrex> right...
[12:56] <quentusrex> I dont' think it will...
[12:56] <quentusrex> it'll keep trying the svn get.
[12:56] <quentusrex> :(
[12:56] <maxb> The wget will stop after 20 tries
[12:56] <StevenK> quentusrex: If you're worried, join #canonical-sysadmin, and ask for it to be killed. But it is the 30th of December ...
[13:02] <maxb> Hm, why's it downloading libshout instead of using the Ubuntu packaged one? Is the upstream buildsystem hardwired to be unable to use installed deps? (If so, how hideous :-( )
[13:10] <huats> hey james_w !
[13:10] <huats> how are you my friend ?
[13:15] <james_w> huats: I am good thanks, how are you?
[13:16] <huats> great too !
[13:16] <huats> james_w: on holidays ?
[13:17] <james_w> yup. you?
[13:17] <huats> nope
[13:17] <james_w> still not a MOTU I see :-)
[13:17] <huats> but I am working from home today...
[13:17] <huats> not yet...
[13:17] <huats> I am just returning from the US (and the trip I did after the UDS..)
[13:18] <james_w> ah, how was that?
[13:23] <RainCT> Can someone here tell me how to use the touchpad? XDD  Sometimes it rotates the desktop cube, but I don't know how I've done it XD
[13:23] <directhex> BUILD SUCCEEDED
[13:23] <directhex> Total time: 237.3 seconds.
[13:24] <directhex> ikvm, kiddies!
[13:24] <Laney> directhex: all ready?
[13:25] <directhex> Laney, not yet
[13:25] <Laney> Also, helo from the East Coast Mainline!
[13:25] <directhex> Laney, but i've got a build process going where it rebuilds the bootstrap binaries then rebuilds against those
[13:25]  * Laney choo choos
[13:25] <directhex> signed, no less!
[13:26] <sebner> directhex: NBS shows libgnome2.0-cil and such stuff. Do you know if all the applications need a rebuild?
[13:27] <directhex> sebner, no, no app needs rebuilding if it's been transitioned
[13:27] <sebner> directhex: I see, thx :)
[13:28] <directhex> sebner, that was the idea ;)
[13:28] <sebner> directhex: ^^, well, I just checked the NBS page and saw that so I wos confused =)
[13:40] <StevenK> RAOF: More grub2 testing?
[13:41] <RAOF> Ding.
[13:47] <ajmitch> how I detest when proprietary drivers go wrong
[13:48] <Hobbsee> at 3am?
[13:48] <ajmitch> sure, couldn't sleep, decided to upgrade some stuff
[13:48] <ajmitch> big mistake
[13:49] <StevenK> Haha
[13:49] <StevenK> ajmitch: "U looz"
[13:49] <ajmitch> just installing the nvidia 180.11 driver should be painless, right?
[13:49] <StevenK> What Could Possibly Go Wrong
[13:49] <Hobbsee> no
[13:50] <ajmitch> StevenK: "No devices detected", of course
[13:51] <ajmitch> I should probably just try & reboot instead of relying on rmmod/modprobe
[14:09] <pschorf> can anyone help me get started packaging?
[14:12] <Laney> pschorf: See the topic, and ask if you have any specific questions
[14:13] <Laney> (start with a bitesize bug or two)
[14:14] <pschorf> Laney, is there a better way than just scanning bugs to find one?
[14:18] <Laney> pschorf: https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.ha ...
[14:18] <slytherin> any archive admin around who can process a sync bug?
[14:18] <Laney> ... s_cve.used=&field.tag=bitesize&field.tags_combinator=ANY&field.has_no_package.used= is a list of bugs that people have determined to be suitable for new contributors to work on
[14:18] <Laney> ..
[14:19] <Laney> http://is.gd/ebsa try that link
[14:41] <pschorf> after I've written a patch and added it to debian/patches, does it matter which method I use to repackage the binary?
[14:41] <persia> pschorf, Not really, although pbuilder and sbuild are recommended to convert source packages to binary packages.
[14:42] <pschorf> persia, and to apply the patch, i just append it to series, right?
[14:43] <maxb> I'd say it depends on the scenario. Is there any point in using pbuilder/sbuild when developing a package? Their use is mainly checking that it works in a clean environment, no?
[14:44] <huats> pschorf: https://wiki.ubuntu.com/MeetingLogs/openweekedgy/PatchPackaging
[14:44] <persia> pschorf, Yes, add it to series, and then construct the source package with something like `debuild -S -us -uc`
[14:44] <huats> a session where pitti explains the various patches system...
[14:44] <huats> it might help..
[14:44] <pschorf> thanks
[14:53] <pschorf> boy, setting up pbuild takes some time...
[14:58] <StevenK> Linking program ==> 'blender'
[14:58] <StevenK> sh: Syntax error: EOF in backquote substitution
[14:58] <StevenK> ARGH
[14:59] <slytherin> any archive admins around to process a sync bug?
[15:01] <pschorf> which environment variable do you change so debsign knows the proper email address?
[15:01] <StevenK> slytherin: Yes, but I'd rather not break my rule
[15:01] <slytherin> StevenK: what rule?
[15:01] <StevenK> "Thou shalt not do archive admin after midnight"
[15:02] <StevenK> slytherin: If it's from unstable and easy, I'll do it
[15:03] <slytherin> StevenK: it is from unstable, easy, and important because it will unblock jboss sync.
[15:03] <StevenK> slytherin: Link me the bug
[15:03] <StevenK> While I ponder hot, flaming and enjoyable death for the sadistic guy that wrote scons
[15:05] <joaopinto> pschorf, DEBEMAIL
[15:05] <slytherin> StevenK: bug #311564
[15:06] <StevenK> slytherin: Er, surely that will be pulled in via the autosyncer?
[15:07] <slytherin> StevenK: The package was fixed in Debian just after DIF.
[15:07] <StevenK> Tasty.
[15:07] <StevenK> libjboss-web-services-java | 0.0+svn5660+dak1-1 | jaunty/multiverse | source
[15:07] <StevenK> libjboss-web-services-java | 0.0+svn5660+dak1-1 | jaunty/universe | all
[15:08] <slytherin> StevenK: and that is the reason I logged the bug.
[15:08] <slytherin> StevenK: well, there is another bug for moving all jboss related packages to universe.
[15:09] <StevenK> slytherin: Right, then point me at that bug, and I'll fix the source tomorrow
[15:09] <persia> That's dangerous to do after midnight.  Soyuz gets fussy if not tickled just right for component moves.
[15:09] <StevenK> "and I'll fix the source tomorrow"
[15:09] <StevenK> IE, after I sleep
[15:10] <slytherin> StevenK: bug #309435
[15:10] <pschorf> pbuilder would yell at me if there were any errors, correct
[15:10] <persia> RIght.  Just providing justification :)
[15:11] <StevenK> slytherin: Done
[15:11] <StevenK> 4 dupes?
[15:11] <StevenK> Odd
[15:12] <slytherin> StevenK: thanks to broken requestsync in last week.
[15:12] <StevenK> Fun
[15:12] <slytherin> StevenK: thanks for sync. I will evaluate jboss sync tomorrow and log another bug.
[15:13] <StevenK> slytherin: No problem. Prod me with the bug for multiverse -> universe ?
[15:13] <StevenK> Oh, you have
[15:13]  * StevenK goes back to hiding under his rock
[15:14] <StevenK> That one requires a bunch of checking
[15:16] <pschorf> After I add a debdiff to a bug report and subscribe the sponsors, I just wait?
[15:17] <persia> pschorf, Pretty much.
[15:30] <ScottK> pschorf: No.    Don't just wait.
[15:38] <DktrKranz> ScottK, time to review a fix for a main package?
[15:38] <ScottK> DktrKranz: Not really.  Just about to head off and do some stuff.
[15:39] <DktrKranz> no problem, thanks
[15:53] <jpds> nhandler: When you add new stuff to u-d-t, you have to add the script to setup.py otherwise it won't get installed.
[15:54] <nhandler> jpds: Ok, I didn't know that.
[15:54] <nhandler> I'll push a new revision to fix it
[15:55] <jpds> nhandler: I just did and uploaded it to the archives.
[15:55] <nhandler> Ok, thanks a lot jpds !
[15:55] <jpds> nhandler: No problem, thank you for the great script.
[15:59] <jpds> OK; Looks like my 0.50.1 upload of u-d-t has been eaten.
[16:00] <jpds> Oh, wait, there it is.
[16:08] <Adri2000> hmm, and 0.49 was never uploaded
[16:09] <nhandler> Adri2000: I just noticed that too ;)
[16:10] <jpds> Adri2000: Well nevermind.
[16:13] <Adri2000> it was probably confusing that my changelog entry had "jaunty" while it was not uploaded. when using git, tags can help to know if a version was uploaded or not; how are we supposed to do with bzr? use "UNRELEASED" until it's uploaded?
[16:14] <jpds> Yes, when you upload, make a new changelog entry with UNRELEASED and push.
[16:15] <persia> Using "UNRELEASED" is a common practice.
[16:15] <persia> Then, have a special commit when you set a target and publish.
[16:18] <Adri2000> ok
[16:24] <huats> pschorf: have you cancel your mail to the mentoring mailing list ?
[16:25] <huats> (am I asking that since I am taking care of it..)
[16:27] <pschorf> huats, yes
[16:27] <pschorf> i wasn't sure if i needed to join the list first...
[16:27] <pschorf> ijust reposted it
[16:27] <huats> pschorf: you cannot join the list
[16:27] <huats> :)
[16:27] <pschorf> that's what i realized :P
[16:28] <huats> the list is just a way of communication between the mentoring reception team :)
[16:28] <huats> pschorf: so the next step is to found a good mentor for you
[16:29] <huats> it would help if you tell us (by an email) which aspect you want to work on (desktop/server/ubuntu/kubuntu/xubuntu/whatever).
[16:29] <huats> and then we'll contact you soon with a good match :)
[16:30] <pschorf> should I send another email to the main list?
[16:31] <huats> it might be good yes..
[16:32] <huats> with that informations...
[16:35] <pschorf> alright, I've sent another through
[16:37]  * Laney molests huats
[16:37] <Laney> good work on bakery :D!
[16:37] <huats> thanks Laney
[16:37] <Laney> (I don't think I said this already...)
[16:37] <huats> hope that help
[16:37] <Laney> well
[16:37] <huats> thanks pschorf
[16:37] <Laney> glom crashes whenever I make a table
[16:37] <Laney> but that's not your fault :(
[16:37] <huats> oh !
[16:37] <huats> hum
[16:38] <huats> you should contact murray the author...
[16:38] <Laney> yeah I will do
[16:38] <Laney> just trying a test build from source
[16:38] <huats> ok
[16:38] <huats> Laney: if you need any help just let me know..
[16:38] <Laney> thanks muchly
[16:39] <Laney> actually
[16:39] <Laney> fancy filing a bug on the BTS for bakery 2.6?
[16:39] <huats> why not
[16:39] <Laney> :>
[16:39] <Laney> my goal is glom in Debian
[16:40] <huats> but I really think that contacting murray about the pb is a better ay to deal with it
[16:40] <huats> Laney: I know that Np237 is interested on tha
[16:40] <huats> t
[16:40] <huats> you should talk with him...
[16:40] <Laney> huats: Who's that?
[16:41] <huats> one of the main gnome guy for debian
[16:41] <Laney> oh
[16:41] <Laney> do they have a channel?
[16:41] <huats> gnome-debian on gimpnet
[16:41] <Laney> heh
[16:41] <Laney> it's joss
[16:42] <Laney> he's been controversial lately
[16:42] <huats> he is joss indeed
[16:42] <Laney> well pkg-gnome seems to maintain bakery so I guess we want to coordinate with them
[16:42] <Laney> for bakery and glom
[16:44] <huats> indeed that is the aim
[16:46] <Laney> rock
[17:04] <pschorf> huats, do you know how long the mentoring queue is?
[17:13] <ScottK-desktop> pschorf: There's no need to wait for a formal mentor to be assigned.  You can always ask questions in the channel and usually someone will be around to answer.
[17:25] <pschorf> could someone help me take a look at bug #151011?  I'm having trouble finding where in the code the changes need to occur.
[17:26] <jpds> imbrandon: Hey! :)
[17:35] <ScottK-desktop> pschorf: mvo (you can usually find him on #ubuntu-devel) does substantially all the work on that package.  You probably ought to talk to him.
[17:42] <jcastro> might be interesting to folks: http://arstechnica.com/news.ars/post/20081230-why-ubuntu-users-should-care-about-debian.html
[17:55] <ScottK> jcastro: Thanks for pointing that out.  Personally I'm pumped that they linked to the Python wiki page I wrote.
[18:00] <jcastro> heh, neat
[18:06] <imbrandon> jpds: hello
[18:07] <imbrandon> heya jcastro
[18:07] <jcastro> hi brandon, long time no see
[18:07] <imbrandon> heh yea, irc eats alot of time :)
[18:08] <imbrandon> been preparing for the move accross the pond :)
[18:08] <jcastro> oh?
[18:08] <imbrandon> work is opening a new office in london
[18:08] <jpds> jcastro: Very interesting article.
[18:08] <imbrandon> and i get to spend the next 2 years there getting it going :)
[18:08] <jcastro> imbrandon: that sounds like fun
[18:09] <jpds> imbrandon: Which part of London?
[18:09] <imbrandon> jpds: not sure, i can get the addy here in a sec
[18:09] <imbrandon> jcastro: yea, considering the main client we opened that office for ( Turner/Cartoon Network ) it should be a blast
[18:09] <bluefoxicy> 18270 bluefox   20   0 1275m 521m  25m S   37 14.0  11:45.49 rhythmbox
[18:09] <bluefoxicy> 11594 bluefox   20   0  923m 471m  30m R   16 12.7   3173:27 firefox
[18:10] <imbrandon> jpds:     The Griffin Building
[18:10] <imbrandon>     83 Clerkenwell Road
[18:10] <imbrandon>     London
[18:10] <imbrandon>     EC1R 5AR
[18:11] <ScottK-desktop> imbrandon: This year's trip to KC ended up being very short.  We got delayed by freezing rain/ice on the way there, so there was no time to get together.
[18:11] <ScottK-desktop> Sorry I missed it.
[18:11] <jpds> imbrandon: You do know it's on the logs now? :(
[18:11] <imbrandon> ScottK-desktop: np :)
[18:11] <imbrandon> jpds: i am missing your point .... i think
[18:11] <bluefoxicy> rhythmbox uses a lot of RAM o.o
[18:12] <imbrandon> if you mean that irc is logged , yes i know :P
[18:12] <jpds> imbrandon: Oh, in Soho, nice.
[18:13] <imbrandon> :P
[18:13] <bluefoxicy> 13025 bluefox   20   0  659m  65m  23m S    0  1.8   0:05.03 rhythmbox
[18:13] <imbrandon> ScottK-desktop: just leaves more BBQ for me :)
[18:13] <bluefoxicy> this is a just-started rhythmbox
[18:26] <bluefoxicy> what?
[18:26] <bluefoxicy> ribs?
[18:32] <rhpot1991_laptop> anyone available to help with a SRU?
[18:40] <Adri2000> rhpot1991_laptop: ask
[18:44] <rhpot1991_laptop> I am working on this: https://bugs.launchpad.net/bugs/302104
[18:45] <rhpot1991_laptop> was rejected before, I believe cause I didn't provide enough information, I'd like to know if anything else is needed
[18:45] <rhpot1991_laptop> it also needs an ack from a motu I believe
[19:04] <maxb> rhpot1991_laptop: I'm not a MOTU, but the description of how SRUs work is at https://wiki.ubuntu.com/StableReleaseUpdates, which should let you understand whether your bug is adequate.
[19:05] <maxb> I would suggest at the very least giving it a more descriptive summary line
[19:06] <maxb> There is no justification in the bug for *why* this package should be SRUed. You definitely need to add that
[19:09] <rhpot1991_laptop> one of the comments says why, the package is useless as is
[19:18] <hyperair> could someone review my package please? http://revu.ubuntuwire.com/details.py?package=codelite
[19:25] <pschorf> If you forget to change a bug's status until after subscribing sponsors, does it make a difference?
[19:25] <Laney> no
[19:28] <pschorf> also, if we submit a debdiff, does it automatically get pushed to an attached debian bug, or do we have to do it ourselves?
[19:35] <rawler> hey people..
[19:35] <jpds> Hey rawler.
[19:35] <rawler> saw Debian Import Freeze was 25th of december.. is it the same deadline for packages from revu?
[19:39] <pschorf> does anyone have time to look at a debdiff I put up earlier?
[19:39] <Laney> rawler: No, that's feature freeze time
[19:39] <Laney> pschorf: Which bug?
[19:39] <pschorf> Laney bug 245898
[19:42] <rawler> Laney: cool.. I have a package I would like reviewed and sponsored.. also, upstream has just released a new minor-version.. I wonder if it's worth uploading the new version packaged as well.. :S
[19:42] <Laney> pschorf: Looks good, except you need to target to Jaunty and not intrepid
[19:42] <Laney> I trust you tested that it worked?
[19:42] <Laney> i.e. the old package exhibits the bug and the new one doesn't
[19:43] <pschorf> erm, no
[19:43] <pschorf> :(
[19:43] <pschorf> hang on
[19:43] <Laney> heh
[19:43] <Laney> also, was there already a patch system implemented?
[19:43] <pschorf> i didn't think so
[19:44] <pschorf> i just manually made the patch
[19:44] <Adri2000> pschorf: in the changelog it should be LP: instead of Closes:, and modifying something inside debian/ shouldn't be done through a patch system
[19:44] <Laney> oh, I missed the debian/
[19:44] <Laney> yeah, just edit that directly
[19:44] <pschorf> Ok.
[20:02] <jjlee> There are a couple of bugs in tvtime I fixed on my local box.  Seems it's unmaintained upstream.  I've browsed around the MOTU wiki a bit, but didn't find all the answers yet
[20:02] <jjlee> Are bugs fixed in Debian first, then ubuntu?
[20:02] <ScottK> Ideally yes.
[20:03] <jjlee> Is there a Debian / ubuntu VC repository somewhere for tvtime?
[20:03] <ScottK> Sometimes we fix it here and then send the patch to Debian.
[20:03] <jjlee> ok
[20:03] <pschorf> Laney, Adri2000: I think I've fixed your concerns, can you look at the updated one at http://www.pastebucket.net/0cr1gf
[20:03] <jjlee> I'm guessing there's just the tarballs, no VC (CVS, SVN / whatever)?
[20:03] <Laney> pschorf: Don't change s-v
[20:04] <jjlee> other than the original tvtime CVS on SF, that is
[20:04] <Laney> pschorf: Target to jaunty
[20:04] <jjlee> but it's not obvious that I haven't just missed some repo somewhere
[20:04] <pschorf> Laney: do I need to have a jaunty environment set up to do that?
[20:04] <jjlee> pschorf: that was my next question, too :-)
[20:05] <Laney> pschorf: You should at least have a jaunty pbuilder/sbuild environment
[20:05] <Amaranth> Although you can't test what you're building without running jaunty somewhere
[20:05] <pschorf> ok
[20:05] <Laney> Amaranth: You can test a lot of things by logging into a chroot
[20:05] <pschorf> what is sbuild?  I don't think I've used it yet
[20:05] <Amaranth> But even if you're running jaunty you should still use pbuilder to build the package
[20:06] <Laney> pschorf: It does the same job as pbuilder
[20:06] <tectroc> Hello, i'm new at packaging software/contributing, and wondering if there's a way to search for packages in launchpad, that needed to be updated.
[20:06] <Laney> tectroc: There's an "update" tag, and also http://qa.ubuntuwire.com/uehs/no_updated.html
[20:06] <Laney> if "new upstream" is what you mean by update
[20:07] <pschorf> Laney, thanks.  To target jaunty, is it sufficient to set up the pbuilder environment and build inside?
[20:07] <Laney> pschorf: Change it in the changelog, build it on Jaunty, test it on Jaunty
[20:08] <jjlee> I guess it depends on the bug really
[20:08] <jjlee> it'd be cheeky to not test an ALSA-related bug on jaunty proper
[20:08] <tectroc> ok thanks
[20:08] <jjlee> but another bug I was hoping to fix in tvtime is just about config files, seems a chroot would be enough
[20:09] <pschorf> to test, all I need to do is install the package
[20:09] <jjlee> is that a fair description of ubuntu policy?
[20:09] <pschorf> is there a way I can do that in a jaunty environment without a full install?
[20:09] <Laney> pschorf: Install old package, make bug happen, install new package, check bug is gone
[20:09] <Laney> jjlee: There's no policy on this really
[20:09] <pschorf> Laney, is there a way to do that in pbuilder or something?
[20:10] <ScottK> Depending on where we are in the release cycle people are generally more or less strict about testing.
[20:10] <Laney> pschorf: You can log into a pbuilder with pbuilder --login
[20:10] <jjlee> Laney: so it's considered OK to test bugs in chroot or old system where reasonable?
[20:10] <Laney> jjlee: Use your judgement really
[20:10] <jjlee> right, thanks
[20:11] <Laney> pschorf: You probably want --bindmounts to make your built .deb available to the chroot too
[20:11] <jjlee> re my version control question again: is there a way to reliably find all VC repositories for a given package?
[20:11] <jjlee> all "official" ones, that is
[20:11] <Laney> jjlee: Should be in debian/control
[20:11] <Laney> you mean for the packaging, not for upstream?
[20:13] <pschorf> Laney, what would I pass to pbuilder create to get a jaunty environment?
[20:13] <Laney> pschorf: https://wiki.ubuntu.com/PbuilderHowto
[20:13] <Laney> that'll be more helpful for you
[20:16] <jjlee> Laney: mostly packaging, but both, really
[20:17] <Laney> jjlee: Well if the packaging is in VCS then it should be in debian/control
[20:17] <Laney> for upstream you generally have to look at their homepage
[20:17] <jjlee> tvtime has no Vcs-* fields, so I guess it's safe to assume there are none
[20:17] <Laney> right
[20:17] <jjlee> thanks
[20:37] <pschorf> Laney, i'm still not quite clear on how to build the package and then install it...I can build it successfully with pbuilder build, but it disappears by the time i login
[20:38] <Laney> pschorf: You have to login with --bindmounts /path/to/result
[20:38] <Laney> then install it again
[20:38] <pschorf> the result is in /var/cache, correct?
[20:39] <Laney> I think the default is /var/cache/pbuilder/result
[20:42] <jjlee> One of the tvtime bugs I have in mind is the lack of ALSA support.  There's been a patch around for a long time (which does not remove OSS support).
[20:42] <jjlee> Would that be suitable for jaunty?
[20:44] <jjlee> before feature-freeze, so I suppose yes?
[20:44] <jjlee> Presumably it's just a question of whether anybody reviews and applies the patch...?
[20:45] <jjlee> (after I file a bug)
[20:45] <pschorf> Laney, everything tests out properly in pbuilder
[20:45] <pschorf> should I add a new comment with the updated debdiff?
[20:47] <jjlee> Hmm, according to this message, *everything* is going to be in bzr for jaunty: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-September/000481.html
[20:47] <jjlee> has that happened yet?
[20:47] <emet> jjlee: I think so
[20:48] <jjlee> is there a wiki page or something that discusses the current state of these VC etc. developments in jaunty?
[20:48] <emet> no idea :(
[20:48] <jjlee> the ones he discusses in second-to-last paragraph in that message?
[20:48] <emet> there is also a channel #bzr it is possible that they know more
[20:49] <Laney> see https://wiki.ubuntu.com/DistributedDevelopment/
[20:49] <jjlee> the bzr people are heavily involved in ubuntu?
[20:49] <Laney> pschorf: Write that on the bug with the new debdiff
[20:49] <emet> bzr I am pretty sure is sponsored by the same organization which sponsors Ubuntu
[20:51] <jjlee> I see
[20:51] <pschorf> Laney, is this all I need to do for the patch?
[20:52] <emet> jjlee: the wiki page Laney posted looked pretty interesting
[20:52] <Laney> pschorf: Right, the sponsors are already subscribed and they'll get to it in time
[20:52] <jjlee> yeah, thanks Laney, I'm reading through the linked-to stuff now
[20:52] <pschorf> Laney, thanks for all your help.
[20:53] <Laney> pschorf: You can forward it to debian using "submittodebian" from ubuntu-dev-tools
[20:54] <emet> hey Laney are you MOTU?
[20:54] <Laney> emet: no
[20:54] <Laney> not yet, anyway...
[20:54] <emet> okay
[20:55] <emet> this bzr repo for every package thing sounds pretty cool
[20:55] <emet> I guess anyone could branch a package?
[20:56] <jjlee> emet: that's what MS was saying in that post
[20:58] <jmarsden|work> emet: See also https://wiki.ubuntu.com/BzrContributorHowto
[20:59] <emet> this is pretty cool
[21:08] <pschorf> does anyone know how to add a po file to gettext?
[21:14] <jmarsden|work> pschorf: Use xgettext, and its friends?
[21:16] <pschorf> jmarsden|work, i was going to add the german translation for the nautilus image converter from gnome's SVN.  Can I just add the file in dpatch and add it to LINGUAS?
[21:16] <pschorf> add de.po, that is
[21:17] <jmarsden|work> Possibly... that is going to be package specific; it all depends what the makefile(s) do.  You'll have to read and understand the Makefile(s) concerned to be sure.
[21:18] <ScottK> Ubuntu has it's own translation system, so I don't think adding it to the package actually works.
[21:54] <jjlee> I hope this means somebody's working towards committing changes to the source itself rather than to the debian/ directory: https://wiki.ubuntu.com/NoMoreSourcePackages
[22:13] <ScottK> jjlee: Why?  Patches are a lot more understandable than undifferentiated diff in the source.
[22:14] <jjlee> but it's easy to get the diff, right?
[22:14] <jjlee> once it's in VC
[22:14] <jjlee> it's easier to edit plain old source than on patches
[22:15] <jjlee> the idea seems to be to use something similar to stacked-git to represent the patches in the VC repository
[22:15] <jjlee> so the concept of patch is still there
[22:15] <ScottK> Using the common patch systems in Debian/Ubuntu editing patches directly is almost never necessary.
[22:15] <jjlee> (in addition to the concept of a commit / changeset)
[22:15] <ScottK> Only if you have access to the vcs.  It's not present in the source package any more.
[22:16] <jjlee> what source package?  See title of wiki page
[22:16] <ScottK> Well that's a long ways down the road.
[22:16] <jjlee> "Using the common patch systems": I thought the idea was to make maintaining packages easier?
[22:17] <jjlee> If so, obsoleting some of the mountain of Debian odds and ends would be a good thing
[22:17] <ScottK> If your comfortable using bzr, I'm sure it is/will be.
[22:17] <jjlee> sure, a long way down the road is fine
[22:18] <ScottK> In favor of an Ubuntu odd and end doesn't seem like progress, but that's just me.
[22:18] <jjlee> being comfortable with systems like bzr is a transferable skill that solves a more general problem
[22:18] <ScottK> VCS has advantages, but it's not pure win.
[22:18] <ScottK> Right, so using something that's not virtually Ubuntu unique.
[22:19] <jjlee> many people (cough) think that a lot of the Debian / ubuntu packaging stuff fills a much-needed gap <duck>
[22:19] <jjlee> right
[22:20] <jjlee> the community seems more valuable than the tools
[22:23] <ScottK> Getting the packaging in a VCS is a long term win if we do it smart.
[22:23] <jjlee> yes, it looks promising
[22:38] <howa> rate my new site !! http://www.hardstylersunited.dk/
[22:38] <jpds> That works too.
[22:38] <emgent> lol


[01:20] <phillw> Hi folks, https://wiki.ubuntu.com/phillw/GettingStarted is a copy of what is shown to new people. It's a darn mess. :: SIGH :: We will have a play with it on my sandbox area, and then it can be discussed and edited. As Beta 1 is fast approaching, I'm not too sure how much time I can give to it. Please feel free to put your thoughts and ideas forward. Thanks, Phill.
[01:21] <pleia2> phillw: can you be a big more specific than "darn mess"?
[01:21] <pleia2> it's just a bunch of links to the actual docs that we've written
[01:22] <pleia2> s/big/bit
[01:22] <phillw> pleia2: look at https://wiki.ubuntu.com/phillw/GettingStarted
[01:22] <pleia2> I am looking at it
[01:22] <phillw> that is a copy of it
[01:22] <pleia2> it's a copy of our GettingStarted
[01:22] <phillw> indeed...
[01:22] <pleia2> aside from broken image links, what specifically troubles you about it?
[01:23] <phillw> there is no explantion of anything.
[01:23] <pleia2> no, it's just a list of links to things that explain
[01:24] <phillw> pleia2: as mentioned in the email.. try https://wiki.ubuntu.com/Testing/Activities
[01:24] <pleia2> oh sure, it certainly can be improved :) that's why I'm asking for your feedback
[01:24] <phillw> just stating a topic is insufficient
[01:25] <pleia2> this is just a first draft, please give us a break, we've worked hard this cycle to even get this far
[01:25] <phillw> pleia2: hey do you know how many man-hours were put into the https://wiki.ubuntu.com/Testing/Activities ?
[01:25] <pleia2> coming in here and complaining that something is a "darn mess" isn't particularly respective of the work we've put in this cycle
[01:25] <pleia2> respectful too
[01:26] <pleia2> so please, try to calm down a bit, we're doing our best
[01:26] <phillw> pleia2: it's a darn mess, what I came here to ask, was we can do better :D
[01:26] <pleia2> can you please use kinder words?
[01:26] <pleia2> you're really being quite insulting right now
[01:27] <pleia2> it's a very basic listing of resources, we'll work on improving it
[01:28] <phillw> And, I'm quite calm, but for a n00b, they would have no idea of where to go. As you have told be off in the past on my classroom sessions, it does seem rather odd that having taken your advice on board I now get told off?
[01:28] <pleia2> I'll go and pull out the broken images now
[01:28] <pleia2> I am not telling you off, I really wish you'd stop usin that phrase :(
[01:28] <pleia2> I am explaining that we're working very hard here, please try to respect that
[01:29] <phillw> pleia2: please accept my apologies, but I am also getting fed up of people stating that "wiki is where documents go to die".
[01:30] <pleia2> I never said any such thing, we're actively working on this wiki page
[01:30] <pleia2> ok, removed broken links so at least it doesn't *look* like it's been abandoned anymore
[01:31] <phillw> pleia2: you did not, others have. that is why I added the new tab. At least people will now know if the wiki page has gone out to die.
[01:32] <phillw> s/the/any/
[01:35] <pleia2> phillw: do you know where is the GettingStarted page linked? I can only find the direct system documentation pages
[01:35] <phillw> pleia2: we *will* get that page sorted out. Once it has a bit of love and attention, it will be proposed to leave the sandbox area and re-join the main area. My words may seem wrong and attack mode at times, but I'm a wiki guy and *hate* instances when others can state we have got it wrong :)
[01:36] <pleia2> https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation should really be where folks start
[01:36] <pleia2> that's linked directly on https://wiki.ubuntu.com/DocumentationTeam when folks look to contribute to system documentation
[01:38] <phillw> I only held the docs getting started area whilst the team discussed things to make it more n00b friendly. It went live a couple of days ago. although, I am struggling to see the links that were in the final email
[01:38] <pleia2> https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuDesktopGuide is where the one we were working on ended up
[01:39] <phillw> pleia2: it could well be the cache on my broweser...  let me just kill it
[01:39] <pleia2> GettingStarted wasn't appropriate for it, since it's very specific to Desktop guide, completely ignores wiki, server guide and everything else
[01:41] <phillw> pleia2: so, where should be heading?
[01:42] <pleia2> phillw: we can work on improving /GettingStarted if needed, but for now I think we should really focus on the existing docs
[01:42] <pleia2> I just blogged earlier about the basics of how folks can get involved and linked to the appropriate pages: http://princessleia.com/journal/?p=8443
[01:44] <pleia2> we still have a long way to go, but we're getting there
[01:44] <phillw> pleia2: I'm quite happy to drop getting stated. As I mentioned on the ML - We have to do the best we can for 13.10, but really do have to aim for 14,04 LTS.
[01:44]  * pleia2 nods
[01:46] <phillw> Let us concentrate our scant resources to what we can. Where if https://wiki.ubuntu.com/phillw/GettingStarted is not a 'GO', where is?
[01:46] <pleia2> https://wiki.ubuntu.com/DocumentationTeam
[01:46] <pleia2> from there you look at the headings and see what you find interesting
[01:46] <pleia2> if you click on "System Documentation" you get taken to the instructions for getting started with that, same for "Wiki Documentation"
[01:50] <phillw> :: SIGH :: okies, you are the bosses. I'd rather the 'get involved' part have higher notification, just as Nicholas on QA/ Testing wanted me to highlight our classroom sessions on https://wiki.ubuntu.com/Testing/Activities/ His view was that "I want to help" should be top of the list.
[01:52] <pleia2> well the whole thing is "get involved"
[01:54] <pleia2> fixed up the header so the broken Mentoring link is gone and everything is shiny
[01:54] <phillw> pleia2: you do not know how much 'customer' input we held on that re-write :) But, their input, whilst stinging at times, was taken on board. We do forget the input of new commers.
[01:55] <pleia2> the subheading pages linked in https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation need a lot of work since many still mention DocBook, but one thing at a time
[01:55] <pleia2> phillw: I guess I just don't understand what different material would go on a GettingStarted specific page, since all of https://wiki.ubuntu.com/DocumentationTeam is already explaining what it is and how to get started
[01:56] <pleia2> we have that root page, and a "Joining the Team" page and specific quickstarts for various types of documentation
[01:57] <phillw> pleia2: indeed, we can only do so much at once.  But once I ask people to overview work and they get a messed up page that has no descriptions and broken links; the new comers are totally allowed to give me grief :D
[01:58] <phillw> that is why we have testers :)
[01:59] <pleia2> yeah, that broken /GettingStarted page really shouldn't be linked anywhere
[02:01] <phillw> liz, I even have managed to have a broken link for lubuntu release. It happens; we need the testers to check these things out. It is not a failure, it is a mark of us having a testing system in place.
[02:02] <pleia2> did you figure out where it's linked from?
[02:03] <pleia2> (aside from the mailing list :))
[02:04] <pleia2> I have to head out for a bit, will have to pick this up later
[02:38] <phillw> pleia2: I'm off to bed, catch up later.
[20:53] <bkerensa> pleia2: I have reviewed the collect screenshots tool
[20:53] <bkerensa> and basically some programs it used are no longer shipped with Ubuntu
[20:53] <bkerensa> and Unity has changed too so it seems to not know how to manipulate it to take screenshots at the right resolution
[20:53] <bkerensa> its a mess
[20:53] <bkerensa> :)
[21:35] <pleia2> godbyk and I tried it out yesterday, he wrote some patches yesterday for it
[21:36] <godbyk> bkerensa: Yeah, you have to install a few extra packages (see the comments at the top of the script).
[21:36] <godbyk> I've written some code to check for and install the missing programs, but I haven't committed it yet.
[21:36] <godbyk> I'm commenting the script a bit more, too.
[21:36] <godbyk> Then I want to sort out the timing issues.
[21:37] <pleia2> \o/
[21:38] <godbyk> The script itself is quite brittle as it stands. It relies on a lot of assumptions.


[00:16] <tsimonq2> wxl: I assume you didn't ignore queuebot here? :O
[00:16] <wxl> tsimonq2: exactly. you can ignore per channel with irssi, too.
[00:19] <tsimonq2> wxl: cool :D
[00:23] <lynorian> https://gist.github.com/dfcfcb000515c5943c96f5c690e90a1e working on the manual some
[00:23] <tsimonq2> lynorian: pull request and I'll accept it!
[00:23] <tsimonq2> :D
[00:23] <tsimonq2> I check my email fairly often so PRs will get in quick
[00:23] <wxl> yay!
[00:23] <wxl> go manual team!
[00:24] <tsimonq2> got pulled away, finishing CONTRIBUTING.md soon
[00:54] <lynorian> https://help.ubuntu.com/community/Lubuntu/GetLubuntu#PowerPC_systems has dead links for powerbooks and openpower systems
[02:04] <tsimonq2> lynorian: ack PR 1
[02:04] <tsimonq2> \o/
[04:56] <ac2> hey guys, anyone around that has run into any issues connecting wifi through virtualbox?
[04:56] <ac2> or should I be directing this towards #lubuntu
[05:05] <lynorian> ac2 probably in #lubuntu
[05:06] <lynorian> if it was only with say 16.10 the development release then here would be the proper place
[10:51] <datadevil> hi. I was wondering if I can download an iso of the qt based version to try on my chromebook
[12:38] <tsimonq2> datadevil: that's currently in the works, sorry
[12:42] <datadevil> oh ok
[12:43] <datadevil> good to know. So the best option is still to install minimal cd like it says on the site?
[21:42] <ac2> hey, could any help me troubleshoot a vm running lubuntu?
[21:42] <ac2> it appeards the display goes black right after login and have a feeling its issue with the monitor settings


[00:18] <sadmac_tokyo> damn. the company lwn subscription doesn't get picked up from the tokyo office
[00:20] <sadmac_tokyo> or maybe it does. I think it was another subscription where it was free to get in
[00:25] <sadmac_tokyo> s/free/automatic/
[00:26] <sadmac_tokyo> the ephasia thing is really a problem this time of morning
[23:02] <szymon_g> hi