[00:18] <Mewcenary> Hey everyone....
[00:18] <Mewcenary> I've got a package update trying to go through on Debian... but finding it hard to get a sponsor.  Is anyone here one who would like to help out... ?
[00:18] <Mewcenary> I'd like to get it done on Debian, so it flows down to Ubuntu naturally...
[00:45] <directhex> Mewcenary, what kind of package?
[00:47] <Mewcenary> I'll link:
[00:48] <Mewcenary> http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=siege
[00:51] <directhex> what a big diff
[00:51] <directhex> oh, autocrap. that explains it
[00:51] <Mewcenary> Yes, sadly so.
[00:51] <Mewcenary> Upstream running automake1.6
[00:52] <directhex> how handy
[00:52] <Mewcenary> Previous Debian release had a mixture of direct source code changes + use of quilt, which lintian did not like.
[00:52] <Mewcenary> So put everything into quilt, which feels a bit cleaner.
[00:52] <directhex> lintian has a point
[00:53] <Mewcenary> I have grown to love quilt.
[00:53] <directhex> IME, mentors can be a bit of a black hole - much easier to find a mentor for team-maintained packages
[00:54] <JontheEchidna> Quilt ftw
[00:54] <JontheEchidna> Once you get used to it it's real easy and convenient
[00:55] <directhex> quilt occasionally involves fighting IME
[00:55] <directhex> sadly
[00:55] <directhex> but computers hate me
[00:55] <directhex> also, anyone from motu-release about?
[00:55] <JontheEchidna> heh, it's just that it has a steep learning curve, and you can screw it up accidentally easily >.>
[00:56] <Mewcenary> Hopefully, a kind sponsor will step forward.  One step towards being a 'real' Debian developer etc!
[00:56] <directhex> iulian or ScottK appear to be connected, though not necessarily awake
[00:57] <directhex> Mewcenary, like i said, life would be easier if it were a team package - or perhaps of interest to a team (even if not technically 'theirs')?
[00:58] <Mewcenary> There's always bribery.
[01:00] <directhex> bribery?
[01:01] <directhex> seems you've worked with the debian cabal before!
[01:01]  * Mewcenary smiles.
[01:01] <Mewcenary> Yes, I did witness some of that.
[01:01] <Mewcenary> Someone trying to get a sponsor for a version already in Ubuntu, but got nigh-on shouted down re: YOUR PACKAGE IS WORTHLESS, UBUNTU HAVE DIFFERENT AIMS etc.
[01:01] <Mewcenary> I wnated to give him a hug.
[01:02] <directhex> it largely comes down to who you know, and who you work with. some teams have excellent cooperation, some have slight cooperation, some aren't on speaking terms
[01:03] <directhex> try the mono, kde, and mozilla teams in order for examples of the above
[01:04] <slangasek> I don't think what you're describing is "the debian cabal"
[01:06] <directhex> indeed
[01:06] <directhex> but like the illuminati, a diluted brand remains enigmatic
[02:07] <amikrop> Hello, how can I fix these lintian warnings/errors?
[02:08] <amikrop> W: webpage source: out-of-date-standards-version 3.7.3 (current is 3.8.0)
[02:08] <amikrop> E: webpage source: missing-python-build-dependency
[02:08] <amikrop> E: webpage source: missing-build-dependency cdbs
[02:08] <amikrop> E: webpage source: missing-build-dependency python-support
[02:08] <amikrop> W: webpage: extended-description-line-too-long
[02:08] <amikrop> W: webpage: new-package-should-close-itp-bug
[02:09] <JontheEchidna> any particular ones you need help with?
[02:09] <amikrop> JontheEchidna: Mainly the errors :-)
[02:10] <JontheEchidna> Could you paste your debian/control file please?
[02:10] <twb> I'd like to find out who is maintaining the Ubuntu midori package, so I can discuss the -fPIC issue with them.
[02:10] <JontheEchidna> in pastebin, of course :)
[02:10] <amikrop> JontheEchidna: http://dpaste.com/19785/
[02:11] <twb> Hmm, I guess I can get it from debian/changelog...
[02:11] <JontheEchidna> amikrop: Ok, the errors are quite simple to fix. Just add the packages specified to the Build-Depends line
[02:11] <JontheEchidna> (cdbs, python, python-support)
[02:11] <directhex> twb, yeah, that's the first place to look
[02:12] <directhex> twb, otherwise known as the "he who touched it last" issue
[02:12] <JontheEchidna> amikrop: Actually you probably would only need python-support rather than both
[02:12] <JontheEchidna> since python-support depends on python
[02:12] <amikrop> JontheEchidna: I manually changed Standards-Version to 3.8.0 after lindian's warning, and I added ${python:Depends} myself (I don't know if it was a right thing to do).
[02:12] <twb> directhex: thanks.
[02:13] <JontheEchidna> amikrop: You would want to add cdbs and python-support to Line 5
[02:13] <JontheEchidna> just put a comment after debhelper (>=7) and then put cdbs, python support
[02:13] <amikrop> JontheEchidna: any (>= x) things after them?
[02:13] <JontheEchidna> nah, just the package names
[02:14] <JontheEchidna> *python-support
[02:14] <amikrop> JontheEchidna: Build-Depends: debhelper (>= 7), cdbs, python-support
[02:14] <amikrop> JontheEchidna: like that?
[02:14] <JontheEchidna> amikrop: yup, that should do it
[02:15] <amikrop> JontheEchidna: Was it right to manually change Standards-Version and add ${python:Depends} myself?
[02:15] <JontheEchidna> Yes
[02:16] <amikrop> JontheEchidna: E: webpage source: missing-python-build-dependency <-- persists
[02:16] <JontheEchidna> hmm, maybe you do need to build-depend on both
[02:17] <amikrop> JontheEchidna: What do you mean?
[02:17] <JontheEchidna> add python to the build-depends is probably required
[02:17] <amikrop> I 've done it.
[02:17] <amikrop> And got this error.
[02:17] <JontheEchidna> python and python-support?
[02:18] <amikrop> JontheEchidna: http://dpaste.com/19789/
[02:19] <JontheEchidna> amikrop: You'd want that line to be like this:
[02:19] <JontheEchidna> Build-Depends: debhelper (>= 7), cdbs, python-support, python
[02:20] <amikrop> JontheEchidna: Worked. Thank you very much, for everything. :-)
[02:20] <JontheEchidna> You're quite welcome. :-)
[02:24] <amikrop> JontheEchidna: OK, now, after running debuild the command ended well but did not prosuce any .deb file.
[02:24] <amikrop> JontheEchidna: http://dpaste.com/19791/
[02:26] <JontheEchidna> amikrop: To get the obvious out of the way, I'm guessing you've looked in the directory above where you debuild'd?
[02:26] <amikrop> JontheEchidna: Yes.
[02:26] <JontheEchidna> strange
[02:26] <JontheEchidna> it even says that it made a deb in the log
[02:28]  * JontheEchidna thinks
[02:28] <amikrop> JontheEchidna: Oh my God, it was a Nautilus problem. Although I changed directories with Nautilus, it didn't refresh. I had to manually refresh to see the .deb file. I am sorry.
[02:28] <JontheEchidna> Hehe :)
[02:28] <amikrop> :-P
[02:28] <JontheEchidna> It had me really going there for a minute, :P
[02:34] <amikrop> Me too ;)
[02:34] <JontheEchidna> I'm stepping out for 15 mins or so, if you have any further questions I'll get back to you then
[02:38] <amikrop> JontheEchidna: alright :-)
[02:38] <amikrop> JontheEchidna: for when you get back (or for anyone else): what is the standard way of distributing our packages? .orig.tar.gz .diff.gz .dsc <-- these 3 files?
[02:44] <dtchen> for non-native (specific to Debian and/or Ubuntu), yes, you'll want an orig, a dsc, and a diff
[02:44] <dtchen> sorry, to clarify: non-native == *not* specific to Debian and/or Ubuntu
[02:44]  * ajmitch is surprised at how few python packages have files in /usr/local after the recent transition
[02:44] <wgrant> ajmitch: They'll FTBFS if they do.
[02:44] <ajmitch> wgrant: sadly not
[02:44] <wgrant> ajmitch: And lots of them do FTBFS because of that.
[02:44] <wgrant> ajmitch: They did two weeks ago...
[02:44] <ajmitch> well they may FTBFS after a recent python upload
[02:45] <wgrant> And they'll only end up in /usr/local after a recent Python upload.
[02:45]  * ajmitch has fixed a package recently which had many files in /usr/local, python was changed that day for --prefix & the layout option to be mutually exclusive
[02:49] <amikrop> dtchen: ok, thank you
[03:06] <amikrop> anyway, thanks guys :)
[03:06] <amikrop> bye
[04:05] <amikrop> I have Architecture: any in debian/control. Why do I get an "i386" .deb and not a "any" one?
[04:07] <wgrant> amikrop: any means it will build a different binary for each architecture.
[04:07] <wgrant> You might be thinking of 'all', which generates one that installs on everything.
[04:08] <amikrop> wgrant: but it built a binary only for i386
[04:08] <amikrop> and not for each architecture
[04:09] <wgrant> amikrop: It can't exactly magically transform your computer into all of the other architectures and build them.
[04:30] <amikrop> wgrant: ok, I 'll use "all", then
[04:46]  * calc thinks amikrop didn't get it
[04:47] <calc> if/when he comes back someone should remind him to read the documentation, you can't just make an any package an all package for fun
[04:47] <calc> and expect it to work anyway
[04:54] <wgrant> calc: I know, but I only saw it after he left :(
[05:00] <calc> wgrant: yea, me too
[05:48] <dholbach> good morning
[05:51] <fabrice_sp> Hey dholbach :-)
[05:51] <dholbach> hiya fabrice_sp
[06:00] <slangasek> fabrice_sp: bug #348160> oh yay, then I don't have to worry about the yucky build failure I got when trying to migrate kmediafactory to libdvdread-dev :)
[06:02] <fabrice_sp> slangasek, yes: I'm fighting to have it build, and I'm just having a link error now (no compilation error), so the patch is close ;-)
[06:02] <slangasek> \o/
[06:03] <fabrice_sp> and guess what: the link error is because libavcodec ;-)
[07:47] <Toadstool> good morning!
[07:47] <Toadstool> yay free LWN subscription, mine is about to expire
[07:52]  * wgrant bought one just a couple of months ago :(
[09:37]  * directhex fills out FFe paperwork for Bug #346884
[09:41] <Laney> \o
[09:42]  * iulian takes a look at it.
[09:46] <iulian> directhex: What testing of the package have you done?
[09:46] <iulian> directhex: What about the rdepends?
[09:47] <directhex> iulian, there are 2 rdepends - banshee and monodevelop-boo
[09:48] <directhex> iulian, i don't know whether any banshee addins actually make use of boo, so i've not found a rational way to test that. and monodevelop-boo needs rebuilding anyway as the 1.9.2 in the archive is incompatible with monodevelop 1.9.3
[09:49] <directhex> and monodevelop-boo 1.9.3 needs boo 0.8.2+, which is how we got here in the first place
[09:49] <directhex> basic machine testing implies ABI compatibility, but not API, iirc. let me check my irc logs
[09:50]  * fransman wanna know what got to be done for solving Bug #330150 ?
[09:52] <Laney> fransman: is it not too late for this?
[09:53] <directhex> hm, no, ABI testing was inconclusive, as machine tools generate false positives for some internal types
[09:53] <directhex> 21-03-2009 13:34:22 > directhex: meebey, how did boo do in your abi testing?
[09:53] <directhex> 21-03-2009 13:34:37 <<EMAIL_ADDRESS>directhex: couldn't test
[09:53] <directhex> 21-03-2009 13:34:47 > directhex: so "sod it" approach?
[09:53] <directhex> 21-03-2009 13:34:51 <<EMAIL_ADDRESS>yeah
[09:53] <fransman> Laney: late because off?
[09:54] <Laney> because of the stage in the release cycle we're at
[09:54] <iulian> fransman: https://wiki.ubuntu.com/JauntyReleaseSchedule
[09:55] <Laney> I mean, it's up to the release managers but I'd say wait until karmic
[09:55] <directhex> "library transition" means "EEK!" btw
[09:55] <fransman> I did post it on 16 Feb 09
[09:55] <directhex> unless only 2 packages are affected. in which case it's fine & dandy. *cough*
[09:55] <Laney> fransman: the sponsors were never subscribed :(
[09:55] <iulian> fransman: Indeed, but you didn't subscribe nobody.
[09:56] <fransman> I am not able to do that Am I ?
[09:57] <iulian> directhex: I've just acknowledged it.  You'll need one more ack.
[09:57] <iulian> fransman: Actually, you can.
[09:57] <fransman> cool
[09:57] <fransman> I did add Tags: sync
[09:57] <directhex> iulian, thanks. depends on one of them materializing though, of course
[09:58] <iulian> fransman: You have some buttons above "Subscribers".
[09:58] <iulian> directhex: OK.
[09:59] <directhex> iulian, note that debian has 0.8.2 rather than 0.9.1 purely because to make a FFe easier to swallow ;)
[10:00] <fransman> iulian: yes I have subscribe someone else, thanks for pointing
[10:02] <iulian> You're welcome.
[10:04]  * iulian -> lunch, school. bbl
[13:01] <e-jat> may i know why this happened ? http://paste.ubuntu.com/138930/ <--
[13:03] <directhex> delete debian/files ?
[13:05] <e-jat> Build needed 00:00:02, 46548k disk space <---
[13:05] <e-jat> im building it at launchpad .
[13:05] <directhex> building what?
[13:05] <e-jat> my PPA
[13:05] <directhex> with your package?
[13:06] <e-jat> yeap ..
[13:06] <e-jat> by seing the log ..
[13:06] <directhex> and does your source package, as uploaded to your ppa, contain a debian/files file?
[13:11] <geser> it does: http://launchpadlibrarian.net/24366527/mymeeting_2.2-ubuntu3.1.diff.gz
[13:12] <directhex> don't do that then
[13:12] <directhex> also, delete debhelper log
[13:12] <geser> e-jat: and why did you change it from arch:all to arch: i386 amd64?
[13:12] <geser> judging from the log your package doesn't support building arch-dependent packages
[13:14] <e-jat> just want to make it available to amd64
[13:14] <e-jat> or should i change it back to all ..
[13:15] <e-jat> that was my 1st package .. so need mo comment from guys in here ..
[13:15] <e-jat> more*
[13:15] <directhex> all means "architecture-independent package"
[13:15] <directhex> things like documentation, where cpu arch is irrelevant
[13:16] <geser> e-jat: arch:all packages are build on i386 but work on all archs (i386, amd64, lpia, etc.)
[13:17] <e-jat> geser: ic ..
[13:18] <e-jat> so i need to delete the package .. reupload changes n rebuild it with arch : all .. ?
[13:24] <directhex> e-jat, other things confuse me. you have a debian/ folder in the orig.tar.gz?
[13:35] <e-jat> owh misplace it .. deleting..
[13:35] <e-jat> directhex: thanks
[14:01] <bddebian> Heya gang
[14:01] <sistpoty|work> hi bddebian
[14:02] <bddebian> Heya sistpoty|work
[14:27] <Laney> Is there any point of a binary package conflicting on itself?
[14:27] <sistpoty|work> Laney: no
[14:27] <Laney> thought as much
[14:28] <sistpoty|work> Laney: otherwise almost every binary package would need to conflict itself, since it obviously would have file clashes ;)
[14:29] <Laney> sistpoty|work: Right, that was my thinking. I just wondered whether there was an edge-case
[14:32] <ScottK> There actually is.
[14:33] <ScottK> I remember seeing one package that did this.  It regenerated a bunch of symlinks and they'd be messed up if the old package was still around.
[14:33] <ScottK> Something like that.
[14:34] <sistpoty|work> that rather sounds like a workaround of buggy maintainer scripts than a proper use of conflicts... ;)
[14:38] <ScottK> I vaguely remember it being less bad than the other options, but it was a while ago.
[14:38] <ScottK> Wasn't my package either.
[16:35] <amikrop> Hello, debuild gives me this error: http://dpaste.com/20020/ Here is my debian/control: http://dpaste.com/20019/
[16:35] <amikrop> Any help would be appreciated much.
[16:36] <directhex> amikrop, you need a " ." as your spacer, not a blank line
[16:37] <amikrop> directhex: ok, thank you :)
[16:42] <amikrop> directhex: Also, I need to put an actual line break in the description (not an empty line).
[16:43] <amikrop> directhex: How can I do this? gDebi seems to ignore my line breaks. It doesn't break the lines, it only leaves empty ones when it sees " .".
[16:44] <directhex> amikrop, look at where "." is appropriate in http://svn.debian.org/wsvn/pkg-mono/monodoc/trunk/debian/control?op=file&rev=0&sc=0
[16:52] <amikrop> directhex: I understood the use of " .". It leaves an empty line (\n\n). I just want to do a single line break (\n). How can I do that?
[16:55] <amikrop> directhex: If I just press Enter, a \n doesn't get in the description.
[16:55] <amikrop> directhex: Wether I press Enter or not, the final result is the same.
[16:55] <amikrop> And I don't want that.
[16:55] <amikrop> What can I do to avoid that? To actually get a \n in the result?
[16:56] <amikrop> Anyone else, too, any help, please?
[17:03] <sistpoty|work> amikrop: I doubt you can do this, at least that's how I interprete 5.6.13 of debian policy
[17:06] <amikrop> sistpoty|work: I can't just leave a line break?
[17:06] <amikrop> sistpoty|work: All I want is to just change a line.
[17:06] <sistpoty|work> amikrop: imho, you can't do this... but take a look at 5.6.13 yourself ;)
[17:06] <amikrop> sistpoty|work: Actually, I have some example code at my description, so I do need to leave a line break.
[17:07] <sistpoty|work> amikrop: ah... then use verbatim formatting (two leading spaces)
[17:07] <amikrop> sistpoty|work: Can I do this to my whole description, too? (not just the code)
[17:08] <sistpoty|work> amikrop: I guess so
[17:08] <sistpoty|work> amikrop: if you think you'll need to have it verbatim *shrug*
[17:10] <amikrop> sistpoty|work: I read about verbatim, but I can't see where it says: "line breaks will actually take effect"
[17:10] <amikrop> sistpoty|work: it only says it will "hradly" wrap them
[17:11] <sistpoty|work> amikrop: if it wouldn't display line breaks, I guess the note about indenting wouldn't make too much sense?
[17:12] <amikrop> sistpoty|work: I hope so
[17:21] <amikrop> sistpoty|work: I made them verbatim, but still, my newlines were ignored.
[17:25] <sistpoty|work> amikrop: then I don't know
[17:25] <amikrop> sistpoty|work: ok, thanks, anyway
[17:38] <Technoviking> hi all, need some packaging help
[17:38] <Technoviking> trying to apply a debdiff to a source package with pbuilder
[17:40] <Technoviking> when I debuild -S -us -uc when source I get the following error
[17:40] <Technoviking> make: *** No rule to make target `/usr/share/gnome-pkg-tools/1/rules/uploaders.mk'.  Stop.
[17:40] <Technoviking> any ideas?
[17:43] <amikrop> My package is GPLed. I am the upstream author. I have a file named LICENSE, which contains the GPL 3. But it isn't placed anywhere by my deb. Should it be placed somewhere? What can I do about it? Here is my debian/rules http://dpaste.com/20049/
[17:44] <amikrop> I also have a file called README, which is places in /usr/share/docs/mypackage/README, but LICENSE is not placed anywhere.
[17:44] <amikrop> * placed
[17:46] <amikrop> So, what can I do, for my LICENSE file to be placed somewhere during my .deb installation?
[17:48] <tgm4883> amikrop, I don't think the LICENSE file needs to be installed, if it's like the COPYING files that I have in my source, they should just need to be in the source tarball
[17:48] <sistpoty|work> amikrop: you could mention it in debian/docs... but OTOH if LICENSE *only* contains the GPL-3, you don't need to have it in the .deb
[17:48]  * tgm4883 notes that I am not a MOTU
[17:49] <fabrice_sp_> slangasek, I've just uploaded the debdiff for kmediafactory. Waiting for a sponsor :-)
[17:49] <fabrice_sp_> Bug #348160
[17:49] <amikrop> tgm4883: So, I should rename it to COPYING and retry?
[17:51] <tgm4883> amikrop, read what sistpoty|work said, you shouldn't need it in the .deb, just in the orig.tar.gz
[17:51] <amikrop> sistpoty|work: why don't I need it in the .deb?
[17:51] <sistpoty|work> amikrop: the rationale is that you can use a .deb only on a debian/ubuntu system, and in the system there's always a copy of the GPL (in each major version) installed, hence this would be duplication
[17:52] <amikrop> sistpoty|work: but 3?
[17:52]  * sebner waves at sistpoty|work :)
[17:52] <amikrop> GPL 3?
[17:52] <sistpoty|work> amikrop: yep, /usr/share/common-licenses/GPL-3
[17:52] <sistpoty|work> hi sebner
[17:52] <amikrop> sistpoty|work: ok, so it will only be in .org.tar.gz
[17:53] <sistpoty|work> amikrop: yep... unlike the deb, the orig.tar.gz can be used w.o. having debian/ubuntu installed ;)
[17:53] <amikrop> sistpoty|work: ok, thanks ;-)
[17:53] <sistpoty|work> np
[17:53] <amikrop> tgm4883: thank you, too
[17:54] <tgm4883> np
[17:57] <slangasek> fabrice_sp_: <yoink>
[17:58] <fabrice_sp_> slangasek, yoink?! :-D
[17:59] <fabrice_sp_> ok. got it :-)
[18:21] <amikrop> sistpoty|work: Is -c gpl3 an option for dh_make?
[18:22] <sistpoty|work> amikrop: no idea... haven't used dh_make in a while myself
[18:22] <amikrop> sistpoty|work: Because, although my upstream program is licensed under GPL 3, I ran dh_make with -c gpl
[18:23] <amikrop> sistpoty|work: and now debian/copyright points to `/usr/share/common-licenses/GPL'.
[18:23] <amikrop> which has gpl 2
[18:24] <sistpoty|work> amikrop: /u/s/c-l/GPL will always point to the latest version (mine points to GPL-3, are you running an old release?)
[18:25] <sistpoty|work> amikrop: however you can (and should) always adjust debian/copyright to your liking (or let's say to your and the archive admins liking *g*)
[18:25] <amikrop> sistpoty|work: there is no gpl3 option
[18:25] <amikrop> sistpoty|work: but ok, it points to 3 for me, too
[18:25] <amikrop> :-)
[18:26] <sistpoty|work> amikrop: some people prefer to have debian/copyright point to the non-symlink, some the other way round... your choice (unless you have v3 only, then I guess pointing to GPL-3 directly seems better to me)
[18:28] <amikrop> sistpoty|work: no, I 'm OK with th symlink ;)
[18:28] <amikrop> * the
[18:28] <sistpoty|work> :)
[18:31]  * sistpoty|work calls it a day and heads home
[18:31] <sistpoty|work> cya
[20:33] <ahasenack> hi, I'm trying to build a source package (debuild -S). The package is for jaunty, and I'm on intrepid. I thought it should work, but it fails when trying to include a file from debian/rules that doesn't exist. Should it be possible? Here is the log: http://pastebin.ubuntu.com/139178/
[20:33] <ahasenack>  /usr/share/python/python.mk doesn't exist on intrepid (or I don't know which package installs it)
[20:34] <sistpoty> ahasenack: that file isn't present in intrepid
[20:35] <ahasenack> sistpoty: correct. So while in general it could work, in this case I can't build a source package?
[20:35] <sistpoty> ahasenack: well, not without fiddling with it. (/me hasn't done a python package since ages, so I haven't too much clue about it)
[20:36] <ahasenack> sistpoty: so I have to install jaunty if I want to build this jaunty source package. I might as well build the binary then too, I was thinking about using ppa
[20:36] <sistpoty> ahasenack: or you could create a jaunty chroot
[20:37] <ahasenack> sistpoty: I tried using mk-sbuild-lv (which I use for other distros), but debootstrap knows nothing about jaunty and it fails
[20:38] <ScottK> ahasenack: That's a new file than only exists with Python 2.6.  You'll need to build the source package in Jaunty.
[20:38] <ScottK> ahasenack: You need the deboostrap from intrepid-backports.
[20:41] <ahasenack> so, get debootstrap which knows about jaunty, create the chroot, then build the source package and upload the source to ppa so I get the binary. I guess I can then skip the ppa part and just build the binary locally
[20:41] <sistpoty> yep
[20:42] <ahasenack> lots of stuff to build a source package, too bad the source build is not distro agnostic
[20:42] <Laney> I can see the whole sponsor queue without scrolling now
[20:44] <ScottK> ahasenack: True.  Generally it is, just sometimes new stuff has to get introduced.
[20:45] <ahasenack> I guess I thought the files would not be "run", just packaged, when a source package is built
[20:45] <ahasenack> like a tarball
[20:45] <ScottK> Generally the clean rule is called when the source package is built.
[20:45] <ScottK> That can sometimes needs lots of stuff.
[20:46] <ahasenack> well, I have time to walk the dog now that the jaunty chroot is being built and packages downloaded :)
[21:27] <_stochastic_> Hi room, I'm having some real troubles getting this package to build, can anyone give me a hand: https://launchpad.net/~stochastic/+archive/ppa/+build/916915
[21:37] <jcfp> _stochastic_: it's looking for avcodec.h and avformat.h in the wrong place?
[21:38] <_stochastic_> yeah, I think so
[21:38] <jcfp> libavformat-dev: /usr/include/ffmpeg/avformat.h   but the compile does this: -I/usr/include/ffmpeg//libavcodec -I/usr/include/ffmpeg//libavformat
[21:38] <_stochastic_> hmm, so I need to patch the source code?
[21:39] <jcfp> dunno, first test this is actually the problem as I'm not some gcc guru :)
[21:46] <ripps> I'm not getting alot of help from #launchpad, it seems somethings wrong with my team ppa, it can't find dependencies that have been the ppa for over a day. It just stopped working around 2 hours ago.
[21:46] <sbasuita> Hi! The last comment on this needs-upgrade bug: https://bugs.launchpad.net/ubuntu/+source/cifer/+bug/342350 says that I need to follow the process documented here: https://wiki.ubuntu.com/FreezeExceptionProcess . However, under the relevant section (Universe->Bug fix only), it says that the bug should just be filed with changelog/justification (done) and a MOTU should just upload. Am I right in thinking I don't need to do anything more t
[21:46] <sbasuita> o push this bug along?
[21:58] <ScottK-desktop> ripps: PPA is a #launchpad thing.
[23:31] <Yasumoto> I'm trying to build a package using pdebuild, and it's telling me that the build dependency of python-cheetah is an uninstallable virtual package, although an apt-cache search seems to show that it isn't
[23:31] <Yasumoto> does anyone happen to know of a way I can check if it's actually a virtual package?
[23:40] <ripps> Yasumoto: I tend to get this when pbuilder is looking for a package in Universe, try adding "COMPONENTS="main restricted universe multiverse"" to your .pbuilderrc.
[23:41] <Yasumoto> ripps: thanks a million, I'll give that a try now
[23:46] <cody-somerville> you'll need to do a pbuilder update --override-config
[23:48] <Yasumoto> cody-somerville: ah, that's what it is
[23:48] <Yasumoto> ripps + cody-somerville: thank you


[06:34] <Athanasius> I am trying to configure my DHCP server, can someone help?
[06:34] <Athanasius> in edubuntu?
[06:35] <Burgundavia> what is your issue?
[06:35] <Athanasius> I have 2 NIC's eth0 goes from the router (static ip) and eth1 is supposed to go to the thin clients
[06:35] <Athanasius> am I supposed to make eth1 static or dhcp?
[06:37] <Athanasius> I have really been struggling to get my edubuntu server going
[06:38] <Burgundavia> static
[06:38] <Burgundavia> set it to the .1 address of the range your dhcp addy is serving out
[06:38] <LaserJock> Athanasius: what version of Edubuntu
[06:38] <Athanasius> feisty
[06:39] <LaserJock> when I installed it, it set up the 2 nics automatically
[06:39] <Athanasius> so if the dhcpd.config file says <IP_ADDRESS>?
[06:39] <Athanasius> it didn't do it for me
[06:41] <Athanasius> eth0 is set static for <IP_ADDRESS>
[06:41] <LaserJock> I think they need to be on different networks, right?
[06:41] <Burgundavia> yes, they do
[06:41] <Burgundavia> otherwise the routing tables will be seriously messed up
[06:43] <Athanasius> this is the standard config that edubuntu has: http://paste.ubuntu-nl.org/28036/
[06:44] <Athanasius> my router is set for <IP_ADDRESS> but that is the same as edubuntu's default dhcp for the clients
[06:45] <Athanasius> do I need to change it to <IP_ADDRESS>?
[06:46] <LaserJock> the two nics need to be on different networks is the bottom line
[06:46] <LaserJock> so you could change the dhcp for the clients
[06:46] <LaserJock> or change the network for eth0
[06:48] <Athanasius> ok, so if I am going to change the ip for the client dhcp to .1.0, what am I to set as the default gateway?
[06:48] <Athanasius> I mean the gateway address for eth1?
[06:50] <LaserJock> I think the gateway would the the Edubuntu server
[06:50] <LaserJock> but I'm not positive
[06:50] <Athanasius> for instance, the subnet would be changed to <IP_ADDRESS> instead of 0.0
[06:52] <LaserJock> so the server would be <IP_ADDRESS>
[06:53] <Athanasius> I will try it, it might kill my internet connection though, it has done it before...
[06:53] <LaserJock> well, wait
[06:53] <Athanasius> ok
[06:53] <LaserJock> eth0 should hook you to the internet
[06:53] <LaserJock> eth1 will be <IP_ADDRESS>
[06:54] <Athanasius> yes, it does, you are right
[06:54] <Athanasius> it won't restart the dhcp server
[06:55] <LaserJock> Athanasius: did you go through the LTSP server setup when you installed Edubuntu?
[06:55] <Athanasius> yes
[06:56] <LaserJock> is should have asked you for which nic you wanted to use for your main one then set up the 2nd for the dhcp/clients
[06:56] <Athanasius> yes it did, I used eth0 for internet and eth1 for the clients
[06:57] <Athanasius> under "option routers <IP_ADDRESS>" do I need to make that the ip for the router (<IP_ADDRESS>)?
[06:59] <LaserJock> I guess I would just substitute 192.168.0 with 192.168.1 everywhere
[06:59] <Athanasius> I am doing that now
[07:00] <Athanasius> I think I have to restart


[02:37] <bluefoxicy> didn't get anywhere with the K8 kernel
[02:38] <bluefoxicy> it starts to boot, and then my newcastle cored machine just streaks the machine with green bars and hardlocks.
[03:59] <pdr> anyone around?
[04:09] <ajmitch_> sure
[09:12] <fabbione> BenC: please pull from my archive. I have a couple of redhat cluster suite updates only.
[02:47] <fabbione> hey BenC
[02:47] <BenC> fabbione: Hey, I'll pull from you after the meeting
[02:47] <fabbione> i got a couple of updates in my tree.. it would good if you can pull before upload .22
[02:48] <fabbione> ok perfect
[02:48] <fabbione> i think for dapper+1 we will spare our troubles from manual merging
[02:48] <fabbione> steve did publish gfs2 tree in git on kernel.org
[02:49] <fabbione> but we can't switch to it yet
[02:49] <fabbione> too unstable
[02:49] <BenC> cool
[02:49] <fabbione> it was about time :)
[02:49] <fabbione> after tons of ranting ;)
[02:49] <fabbione> i know for a fact that the GFS redhat team hates me
[02:49] <BenC> lol
[02:51] <fabbione> http://sources.redhat.com/ml/cluster-cvs/2006-q1/msg00178.html
[02:51] <fabbione> https://www.redhat.com/archives/linux-cluster/2006-February/msg00120.html
[02:51] <fabbione> i don't give them time to breath :)
[04:03] <zul> heylo
[04:15] <infinity> (base)adconrad@cthulhu:~$ ls /sys/bus/pci_express/devices/ -l
[04:15] <infinity> total 0
[04:16] <Keybuk> total 0
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie00 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie00
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie00 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie00
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie00 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie00
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie00 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie00
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie03 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie03
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie03 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie03
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie03 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie03
[04:16] <Keybuk> lrwxrwxrwx 1 root root 0 2006-02-16 14:12 pcie03 -> ../../../devices/pci0000:00/0000:00:0e.0/pcie03
[04:16] <Keybuk> --
[04:16] <infinity> Yeah, what he said.
[04:17] <Keybuk> interesting that they're all the "same" device
[04:17] <infinity> Except for the part where I get aimed at a different bus/bridge, but whatever.
[04:17] <infinity> Same shit.
[04:17] <Keybuk> infinity: do any links you have of the same filename point to different destinations?
[04:17] <infinity> Nope, same as yours. 00 to 00, 02 to 02, 03 to 03.
[04:18] <infinity> Three 00, two 02, and three 03. :)
[04:18] <infinity> thpethul.
[04:20] <Keybuk> BenC: so yeah, it'd be nice if it didn't do *that* :)
[04:20] <BenC> ok
[04:21] <BenC> all those symlinks from from the driver core, so pcie must just be doing something stupid with sysfs linking
[04:21] <infinity> Yeah, I think we already concluded on the "something stupid with linking" front.
[04:21] <infinity> :)
[04:24] <BenC> ah, no it's not really that stupid
[04:24] <BenC> each of those links represents a "pcie service" for that device
[04:24] <BenC> the naming is just stupid
[04:25] <Keybuk> except for the "creating symlinks that userspace can't deal with" stupidness? :p
[04:25] <BenC> it should include the service number so it's unique
[04:25] <Keybuk> pcie00:%d ?
[04:25] <Keybuk> (same for the subdirs under /sys/bus/pci/devices/*/pcie%d ?
[04:26] <BenC> can you ls -l /sys/devices/pci0000:00/0000:00:0e.0/ ?
[04:27] <infinity> base)adconrad@cthulhu:~$ ls -l /sys/devices/pci0000\:00/0000\:00\:1c.2/
[04:27] <infinity> total 0
[04:27] <infinity> lrwxrwxrwx 1 root root    0 2006-02-17 06:22 bus -> ../../../bus/pci/
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 class
[04:27] <infinity> -rw-r--r-- 1 root root 4096 2006-02-17 06:22 config
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 device
[04:27] <infinity> lrwxrwxrwx 1 root root    0 2006-02-17 06:22 driver -> ../../../bus/pci/drivers/pcieport-driver/
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 irq
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 local_cpus
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 modalias
[04:27] <infinity> drwxr-xr-x 3 root root    0 2006-02-17 06:22 pcie00/
[04:27] <infinity> drwxr-xr-x 3 root root    0 2006-02-17 06:22 pcie02/
[04:27] <infinity> drwxr-xr-x 3 root root    0 2006-02-17 06:22 pcie03/
[04:27] <infinity> drwxr-xr-x 2 root root    0 2006-02-17 06:22 power/
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 resource
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 subsystem_device
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 subsystem_vendor
[04:27] <infinity> --w------- 1 root root 4096 2006-02-17 06:22 uevent
[04:27] <infinity> -r--r--r-- 1 root root 4096 2006-02-17 06:22 vendor
[04:27] <infinity> (base)adconrad@cthulhu:~$
[04:27] <Keybuk> --
[04:27] <infinity> (That's my PCIe bus)
[04:27] <Keybuk> and for me
[04:28] <Keybuk> drwxr-xr-x 3 root root    0 2006-02-16 14:12 0000:01:00.0
[04:28] <Keybuk> lrwxrwxrwx 1 root root    0 2006-02-16 14:12 bus -> ../../../bus/pci
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 class
[04:28] <Keybuk> -rw-r--r-- 1 root root 4096 2006-02-16 14:12 config
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 device
[04:28] <Keybuk> lrwxrwxrwx 1 root root    0 2006-02-16 14:12 driver -> ../../../bus/pci/drivers/pcieport-driver
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 irq
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 local_cpus
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 modalias
[04:28] <Keybuk> drwxr-xr-x 3 root root    0 2006-02-16 14:12 pcie00
[04:28] <Keybuk> drwxr-xr-x 3 root root    0 2006-02-16 14:12 pcie03
[04:28] <Keybuk> drwxr-xr-x 2 root root    0 2006-02-16 14:12 power
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 resource
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 subsystem_device
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 subsystem_vendor
[04:28] <Keybuk> --w------- 1 root root 4096 2006-02-16 14:12 uevent
[04:28] <Keybuk> -r--r--r-- 1 root root 4096 2006-02-16 14:12 vendor
[04:28] <Keybuk> syndicate co%
[04:28] <Keybuk> --
[04:28] <BenC> well, that pcie%02x is supposed to be an OR of the type and service (4 bits each)
[04:28] <Keybuk> the pcie00 and pci03 directories just contain bus, power and uevent
[04:28] <BenC> why it isn't unique is a little odd
[04:30] <Keybuk> aye
[04:30] <BenC> I'll have to ask about this
[04:30] <Keybuk> that "pci device" does appear to the the pcie bus
[04:31] <Keybuk> the pcie devices themselves (ie. the video card and friends) show up as ordinary pci devices
[04:34] <infinity> Yes, they do.
[04:34] <infinity> If they didn't, my laptop wouldn't work with breezy. :)
[04:35] <infinity> (breezy's radeon driver didn't support PCIe, only PCI)
[04:35] <Keybuk> (and how to tell)
[04:35] <infinity> It does PCIe.
[04:35] <BenC> "because they are a bunch of clueless idiots"
[04:35] <BenC> not really a helpful response
[04:36] <BenC> Time to try Xgl, brb
[04:42] <Keybuk> ah, "(II) NVIDIA(0): Detected PCI Express Link width: 8X"
[04:44] <Keybuk> glxgears -iagreethatdanielsisachild says ~20000 FPS
[04:44] <Keybuk> so I guess that works then
[06:13] <bcollins> xgl totally hosed things up
[06:13] <bcollins> guess it's not ready for ppc and/or radeon
[06:13] <mjg59> Yeah, I've had a couple of people say that
[06:14] <mjg59> Ooh.  Hmm.
[06:18] <Keybuk> who is it?
[06:19] <bcollins> trying to get Tiger running on a P4
[06:21] <mjg59> "Edgar Hucek"
[06:21] <mjg59> Would be interesting to find out
[06:22] <Keybuk> name doesn't ring a bell
[06:22] <mjg59> Nope
[06:22] <mjg59> Was doing some work on Xbox stuff at some point
[06:22] <zul> never heard of him
[06:22] <mjg59> Hmm.
[06:22] <mjg59> We need to get hold of some Mac hardware.
[06:22] <Keybuk> is Mactel stuff out in the shops yet?
[06:23] <zul> supposedly
[06:28] <Keybuk> we've apparently ordered one
[06:31] <mjg59> An iMac?
[06:31] <mjg59> Or a Macbook?
[06:32] <Keybuk> Macbook
[06:33] <mjg59> When? The originals batch should be being delivered nowish, but new orders look like they're pushed back until March...
[06:33] <Keybuk> dunno, I guess it was probably about the time Jane said we'd be trying to do the work ;)
[06:33] <mjg59> Heh
[06:34] <mjg59> Booting a kernel should be fine, but we'll need to find out some way to get a console off it
[06:34] <Keybuk> they don't have usual PC BIOS do they?
[06:34] <Keybuk> I guess Linux's support for EFMI isn't quite there yet?
[06:35] <Keybuk> surprised Intel haven't helped with that
[06:36] <mjg59> EFI is fine
[06:36] <mjg59> People have been using it to boot on IA64 for years
[06:36] <mjg59> And elilo should work fine on x86
[06:36] <Keybuk> why no console then?
[06:36] <mjg59> Does EFI provide a sensible console?
[06:36] <Keybuk> I don't know
[06:36] <mjg59> (Once passed to the kernel)
[06:36] <mjg59> I guess it might do - in which case vgacon probably works
[06:37] <Keybuk> it's one of those things where until I see one, I won't know much about it ;)
[06:37] <mjg59> Ah, yeah, IA64 has VGAcon
[06:37] <mjg59> So it might work
[06:37] <mjg59> That would make life easier
[07:20] <mxpxpod> what would make syslogd spawn 9 new instances of itself when I resume from sleep?
[07:31] <bcollins> sweet...never though I'd see osx installing on this P4
[07:32] <zul> did you pay for your copy of osx?
[07:33] <bcollins> *cough*Of course*cough*
[07:33] <zul> hmm...maybe i should try..
[07:33] <bcollins> the paid-for copy of osx wont install on normal PC hw without all the extra hacks
[07:33] <zul> hehe
[07:33] <bcollins> namely, needing sse3 hw
[07:34] <bcollins> the "copy" I have has an sse2 hack, so I can atleast run it on my P4
[07:34] <zul> oooo...i have sse2 as well...gimme..;)
[07:34] <zul> *cough* gimme please *cough*
[07:36] <bcollins> uh, I deleted it from my public high b/w system...no way I'm uploading at 27k/sec :)
[07:36] <zul> heh...its ok...ill just go hang myself..:)
[07:57] <Keybuk> bcollins: is there any particular advantage to the amd64-k8 kernels over amd64-generic?
[07:58] <BenC> Keybuk: just that the compile-time options are more geared toward k8
[07:59] <Mithrandir> Keybuk: they give you IO-MMU support, for instance.
[08:05] <Keybuk> Mithrandir: btw, anything in particular you'd like me to test on this?  I know you've been doing some amd64 portability work
[08:05] <Mithrandir> Keybuk: actually, yes.  If you run ddcprobe from the console, does it output sane values for you?
[08:05] <Keybuk> yes, quite a bit
[08:06] <Mithrandir> pitti has some problems with his card, but I'm not sure which one that is yet
[08:07] <Keybuk> http://rafb.net/paste/results/I1NxVx81.html
[08:08] <Mithrandir> hmm, so it appears it doesn't do edid for you either.. :-/
[08:08] <Keybuk> interesting
[08:08] <Mithrandir> any chance you could try ddcprobe from a i386 live cd?
[08:08] <Keybuk> Xorg.0.log says the nvidia driver has read stuff from EDID
[08:09] <Keybuk> as in boot the Live CD and try?  or just run the i386 binary on this?
[08:12] <Mithrandir> as in, boot the live cd, pop out to the console and run sudo ddcprobe there
[08:12] <Keybuk> right
[08:12] <Keybuk> will have to do that a bit later ;)
[08:12] <Keybuk> will give you the result tomorrow
[08:12] <Mithrandir> the amd64 kernel doesn't have the vm86 syscall, so the i386 binary is useless on amd64.
[08:12] <Mithrandir> thanks, no hurry.
[09:35] <fishdish> another curiosity: there is this computer called TYAN VX 50. It has 8 slots for AMD Opteron processors. We are trying to fix Ubuntu to work with all the 8 processors. We have a problem though: 4 of the processors are connected to the motherboard with a PCI-E. Therefore there's a PCI-E to cross to 4 processors which are missing from the configuration
[09:36] <cjb> fishdish: "are missing from the configuration"?
[09:48] <doko> * Added support for Intel PRO/Wireless 3945ABG driver; this driver needs 16KB
[09:48] <doko>   stacks in kernel.
[09:48] <doko> BenC: this is from ndiswrapper-1.9. do our kernels have 16kB stacks?
[09:49] <BenC> our stacksize is stock
[09:57] <fishdish> yeah... 4 processors are seen, 4 missing
[09:58] <fishdish> it seems that the PCI-E between the processors hides the add-on board from sight
[09:58] <fishdish> this monitor sux even
[09:59] <fishdish> I have noticed that this is a kernel issue. Some ppl on #debian thoguht NUMA had to be reconfigured.
[10:00] <fishdish> but i think NUMA has nothing to do with it
[10:00] <fishdish> which part of the kernel handles multiprocessing over PCI-E?
[10:01] <fishdish> TYAN sells their product with Linux (suse) but i'd like to use Debian/alternative
[10:02] <fishdish> Therefore in need to build  a custom kernel
[10:03] <fishdish> i think this server is not the only one with such hardware... it would help also with many other hardcore workstations
[10:04] <Keybuk> Mithrandir: didn't have any luck with the breezy live cd
[10:04] <Keybuk> it spat random garbage at my monitor and X crashed
[10:05] <fishdish> Keybuk tune the video mode
[10:05] <Keybuk> fishdish: it's a live cd ... I can't ;)
[10:05] <fishdish> ah, and it's not knoppix
[10:05] <Keybuk> I suspect it's more that the nv driver can't drive this card, but thought it could
[10:06] <fishdish> nvidia drivers sux
[10:07] <fishdish> they are like 10000 hours older than the current winoze drivers
[10:07] <fishdish> windoz
[10:07] <Keybuk> the nvidia-glx one in dapper works just fine for me
[10:08] <fishdish> me i need sth to support processors behind PCI Express
[10:08] <fishdish> it's a lot of guessing
[10:08] <Keybuk> you'll almost certainly have to write it yourself :)  enjoy
[10:08] <Keybuk> Mithrandir: I'll have to wait until I have real bandwidth before I can download and burn a dapper Live
[10:09] <fishdish> i think so - the more i read the docs and ask people, the more i think so. Novell Linux Server can see the whole 8 processors but i don't want Novell Linux Server. I want Debian. The Real Linux.
[10:10] <fishdish> ...so many diffrent kinds of computers to configure fro Linux..
[10:10] <mjg59> Keybuk: Just boot to console mode
[10:10] <Keybuk> mjg59: how do you do that on a live?  "s" as usual?
[10:11] <mjg59> If all else fails, just pass init=/bin/bash
[10:11] <Keybuk> does that not break casper?
[10:11] <Keybuk> I don't know much about the breezy live
[10:11] <mjg59> Dunno
[10:11] <fishdish> bash sux why cant there be a shell script perl-alike?
[10:11] <mjg59> I'm sure if you poke it hard, somethng will happen
[10:11] <Nigelenki> amd64 kernel hard-locked when I opened gtk-gnutella, 2.6.15-15-generic
[10:12] <fishdish> cool
[10:13] <fishdish> what about running Ubuntu on a MIPS processor? the next computer i have is a MIPS -based development board that represents a handheld. If i build a Debian kernal with MIPS support and then build Ubutnu on top of it, will it work?
[10:14] <fishdish> typos...
[10:17] <fishdish> ...the CPU is an ARC 750D
[10:17] <fishdish> the same core with nintendo Came Cube
[10:18] <fishdish> ..i believe
[10:21] <Nigelenki> mmm
[10:21] <Nigelenki> ^3buntu
[10:21] <Mithrandir> Keybuk: just installing xresprobe from dapper?
[10:21] <Keybuk> Mithrandir: hmm?
[10:21] <Mithrandir> Keybuk: you know you can install random stuff to the live cd?
[10:22] <Mithrandir> Keybuk: so just change breezy to dapper and then do apt-get install xresprobe on the live cd.
[10:22] <Keybuk> Mithrandir: only if you can get the live cd to actually *boot* :)
[10:22] <Keybuk> it crashed
[10:22] <Mithrandir> Keybuk: heh, tried with noapic acpi=off?
[10:27] <Keybuk> Mithrandir: nope, too much effort <g>  will just do a dapper one later
[10:27] <Keybuk> breezy live takes too long to boot
[10:28] <Mithrandir> Keybuk: sure


[10:49] <alan_g> alf_: anpok_ with krillin CI problems again I'm strongly inclined to land some "easy stuff" by hand. Starting with lp:~afrantzis/mir/fix-1517990 - any objections?
[10:50] <alf_> alan_g: no
[10:52] <anpok_> sure!
[10:52] <alan_g> In that case, I'm accepting suggestions
[11:28] <ahayzen> Hey guys, I've just reported bug 1518935, but I'm not sure which part of the platform is causing it, I think it is possibly QtMir but wanted to ask you guys before I add the project as affected?
[11:33] <greyback_> ahayzen: hard to know for sure, someone would need to investigate. I suggest unity8 at the very least
[11:33] <ahayzen> greyback_, ok thanks :-)
[12:24] <dandrader> alan_g, any reason why size hints (min and max size, size increment value) are not properties of mir::scene::surface?
[12:25] <alan_g> dandrader: because they are specific to window management
[12:26] <dandrader> alan_g, I'm doing a lot of gymnastics to get that info from mir::shell::WindowManager methods to our MirSurface object in Unity.Application
[12:26] <alan_g> dandrader: that's because the window management work for qtmir hasn't been done yet
[12:26] <alan_g> greyback_ and I are due to start it on Wednesday
[12:27] <dandrader> alan_g, window management is done in unity8. qtmir just proviedes that info to it
[12:27] <alan_g> OK, I'm using "window management" as shorthand for that work
[12:28] <dandrader> alan_g, right now I'm working on making unity8 obey those size hints
[12:28] <dandrader> alan_g, in QML
[12:29] <dandrader> alan_g, and qtmir is the guy that exposes mir stuff into QML to untiy8 can use it
[12:29] <dandrader> alan_g, because it's just so much better to write those kinds of things in QML than in C++
[12:30] <alan_g> dandrader: agreed. And that piece of qtmir work has been postponed over months. So greyback_ and I are getting together to do it this week.
[12:30] <greyback_> dandrader: ordinarily I'd agree, but we've a mandate to implement policy like this in mir
[12:30] <greyback_> dandrader: I do want this info exposed to qml though
[12:31] <dandrader> greyback_, alan_g I have the unity8 part ready here: https://code.launchpad.net/~dandrader/unity8/sizeHints
[12:32] <alan_g> IMO mir::scene::Surface already has a bunch of info on it that doesn't belong there.
[12:33] <greyback_> dandrader: the plan is to move the JS code you added in WindowResizeArea.qml to mir itself


[00:34] <sarnold> is there an easy way to unbust juju's local provider on raring?
[00:34] <sarnold> or would it be easier to just do everything in a precise? quantal? vm?
[00:36] <sarnold> (both the raring and the ppa juju's wind up causing python troubles; archive juju leads to whoopsiedaisy problems, ppa juju leads to funny python traces in the juju debug-log, "SyntaxError: invalid syntax")
[00:41] <_mup_> Bug #1159020 was filed: SyntaxError: invalid syntax <juju:New> < https://launchpad.net/bugs/1159020 >
[17:17] <Carlo> hi all boys
[17:18] <Carlo> is there any Italian here XD?
[21:00] <hazmat> sarnold, i suspect there is an underlying python distro issue


[01:21] <bryce> mlankhorst, happy NY to you as well
[01:43] <GeoffCh> Happy New Era too!  bryce, supposing you got my email:  do you suppose the i915 driver could be mapping my modelines somehow to fit within the (wrong) dimensions of my display?
[01:44] <bryce> GeoffCh, dunno, I'd have to see logs
[01:47] <GeoffCh> OK, I can do that.  Xorg.0.log, syslog, xorg.conf, anything else?
[01:47] <bryce> xrandr --verbose, dmesg
[01:48] <GeoffCh> OK, sure.  No hurry, I'll email them.
[14:43] <ricotz> bjsnider, hi
[14:43] <bjsnider> hi
[14:43] <ricotz> bjsnider, by any chance did you look into building nvidia blob with 3.8rc2 yet?
[14:44] <bjsnider> no
[14:44] <ricotz> ok, thanks
[15:54] <mlankhorst> sforshee: do you know of other ati cards that might also need the d3 delay increase?
[15:56] <sforshee> mlankhorst, I only have one other system with an ATI card and it doesn't have hybrid graphics. I haven't seen any issues with that one.
[15:57] <sforshee> slangasek has a mac mini with radeon, but when I had that one I don't recall seeing any issues either
[15:57] <mlankhorst> ok so it might be just this laptop then having problems during switcheroo?
[15:57] <sforshee> perhaps
[20:31] <ricotz> Sarvatt, hey ;), i see you having fun updating things
[20:35] <Sarvatt> yeah would have helped if i looked before test building/uploading xserver :)
[20:40] <ricotz> oh :)
[20:40] <ricotz> did you dare to think about <IP_ADDRESS>1 ;)
[20:45] <ricotz> i hope someone likes to pick up pixman 0.28.2
[21:06] <Sarvatt> ricotz: have you tried newer pixman? the glyph cache stuff is supposed to make the nvidia blow up last i looked
[21:06] <Sarvatt> from 0.27
[21:06] <Sarvatt> err nvidia blob blow up
[21:06] <ricotz> no, havent tried it
[21:07] <ricotz> xserver 1.14rc1 will need it though
[21:07] <Sarvatt> saw lots of complaints from arch people on the nvidia forums about it
[21:07] <ricotz> hmm, i see
[21:09] <Sarvatt> ahh arch backported the commit from xserver master to 1.13, so our 1.13 will be fine
[21:09] <Sarvatt> but yeah https://bugs.archlinux.org/task/32612
[21:19]  * bryce waves
[21:37] <wrouesnel> is there any word on if the radeon drivers are working in the edgers ppa again?
[21:39] <mlankhorst> was a bit of fallout in linux git lately :P
[21:40] <wrouesnel> ?
[21:53] <mlankhorst> Sarvatt: hm does edgers use kernel drm git version?
[21:54] <agrestringere> Got a quick question for you all: I updated to the Xorg Edgers PPA and the current 3.5 Kernel is having massive problems with my Wifi
[21:54] <agrestringere> the broadcom sta driver won't even start up
[21:55] <agrestringere> any advice on how to get this working?
[21:59] <agrestringere>  Anyone can help with this:  Linux 3.5.0-18-generic #29-Ubuntu , wireless package used is bcmwl-kernel-source_<IP_ADDRESS>+bdcom-0ubuntu3_amd64.deb
[22:02] <agrestringere> handling it in #ubuntu room, ignore, thanks...


[15:35] <ball> For a backup disk, is there a good reason to use ext4 or ext3 rather than ext2?
[15:37] <penguin42> ball: The journals on 3/4 area bit more tolerant of not being properly unmounted
[15:38] <ball> Thanks.
[15:38] <daftykins> weekend \o/
[15:39] <daftykins> i've been configuring NUT the UPS management software today
[15:39] <ball> daftykins: How's it working out?
[15:40] <daftykins> pretty good! just invoked a test, all the VMs on the host were successfully shutdown, followed by the host itself
[15:40] <daftykins> need to work out how to get a Synology NAS to pay attention too, got it as far as being able to query the master
[15:40] <ball> It's good to get those in the right order.
[15:41] <ball> daftykins: Can you set the exhaustion level at which shutdown occurs or are you doing it when AC fails?
[15:42] <daftykins> oh yeah you get to define all the limit levels
[15:42] <penguin42> and do you have Majel Barret's voice telling you about it?
[15:42] <ball> penguin42++
[15:42]  * daftykins powers the server back on via iDRAC
[15:44]  * penguin42 likes the DRACs - I tend to use them transatlantically
[15:44] <daftykins> i'm glad this one has behaved after being factory reset, it was really causing trouble after the system arrived in Exeter
[15:45] <ball> I went kayaking in the sea at Exeter.
[15:45] <ball> Those were the days!
[15:45] <penguin42> probably not with a dell server....
[15:46] <daftykins> maybe with all the parts removed
[15:46] <ball> Of course!  Where do you think Microsoft got the idea for their "underwater datacentres"?
[15:46] <penguin42> using rack kits as paddles?
[15:46] <daftykins> and most of the... no, what am i thinking, even an aluminium chassis wouldn't displace more than it weighed
[15:48]  * ball looks glum
[15:49] <ball> I need a handful of 32 Gbyte microSHDC cards.
[15:49] <daftykins> o0
[15:50] <ball> ...and they've doubled in price due to the "chip shortage".
[15:51] <ball> Mostly unrelated: I need a faster computer.
[15:51] <daftykins> this for an army of Pis or something o0
[15:51] <penguin42> ball: Well, I'd offer you my 16 core Ryzen if the damn thing hadn't died :-(
[15:52] <ball> daftykins: One for a Pi 2B, one for a tablet, one for my daughter's GoPro
[16:00] <daftykins> once my pal notices my messages he'll be able to power the Synology NAS back on, then i can investigate the correct config xD
[16:02] <daftykins> pleased with that, there was a bit of hassle considering which device would make a good master... right now i'm using the Dell host OS (XCP-ng) as it
[16:02] <daftykins> so i don't even bother with shutdown of the pfSense router right now
[16:04] <penguin42> daftykins: can it do wake-on-ether?
[16:07] <daftykins> can't reach it to find out xD
[16:08] <penguin42> can you reach something else on the LAN?
[16:10] <daftykins> i'm in no hurry, i don't know its' MAC though
[16:43] <penguin42> bound to be in a log somewhere :-)
[16:44] <daftykins> hehe
[16:45] <daftykins> ah well, it's why we test, to find out the shortcomings!
[17:26] <ball> What does it mean when the terminal cursor stops flashing?
[17:27] <daftykins> yessss \o/ Synology now reading the UPS status
[17:27] <ball> daftykins: from the physical VM host via upsnut?
[17:29] <daftykins> yep, Synology being the NAS appliance on the LAN - it's a slave reading from the server host
[17:30]  * ball nods
[17:31] <ball> I'm glad that's working.
[17:31] <daftykins> kinda nuts 'cause the GUI web admin doesn't support it, so you have to hand-edit the config
[17:31] <ball> Is the NAS part of the UPS load?
[17:31] <daftykins> yep
[17:31] <ball> I'm glad you got it working.
[17:31] <daftykins> "ups.load: 24" :D
[17:31] <ball> Oh, I just said that. :-)
[17:32] <daftykins> what situation are you seeing the cursor thing in?
[17:32] <ball> daftykins: Most recent case was during a dd job.
[17:32] <daftykins> hrmm
[17:35] <daftykins> only used to seeing a change when the terminal isn't the active window, really
[17:35] <daftykins> assuming the input is correct - i'm quite fond of "sudo dd if=/dev/zero of=/dev/sdx bs=4M status=progress" for example
[17:38] <ball> That's essentially what I did, though if pointed to an image.
[17:38] <ball> ...and bs=16384
[17:48] <daftykins> assume you're prepping microSDs, i'd probably open another term and check "dmesg | tail" output in case the card is unhappy
[17:51] <ball> I did look at dmesg output after the dd job was done.  No major complaints and the card seems to work fine in the target system.
[17:51] <daftykins> little bit weird
[17:56] <daftykins> ah, so pleased with today's progress... been meaning to get around to that for ages, but i kept umm-ing and arr-ing about which device i wanted to be master
[17:57] <daftykins> i got really close but network chat wasn't working, then i spotted iptables blocking the daemon port on the host :)
[17:57] <ball> I think it makes sense the way you've described it.
[17:58] <daftykins> yeah, the server is the priority really, best for it to shutdown safely
[17:59]  * ball nods
[18:01] <daftykins> ooh i spy the domestic LAN doing some light HLS traffic according to his router, i detect kids entertainment time! :D
[18:05] <ball> What's HLS?
[18:05] <ball> Video streaming?
[18:05] <daftykins> HTTP live streaming, mmm
[18:05] <ball> Ah ok.
[18:05] <daftykins> fires off in little bursts of throughput as the player grabs another chunk of a few seconds here and there
[18:05] <daftykins> easy to spot on traffic graphs :D
[18:06]  * ball doesn't get traffic graphs, even at the office.
[18:06] <ball> That reminds me: I'm supposed to be building a router.
[18:06] <daftykins> oh o0
[18:07] <ball> It'll have to wait until I've had time to read up on npf and VLANs.
[18:07] <ball> I wonder how much the telco would charge to install and maintain a router for us.
[18:07] <daftykins> ah dealing with VLANs has totally made me rethink how i design things
[18:08] <daftykins> very cool to offer clients an entirely separately routed guest WiFi network that keeps guests away from the LAN their own office kit is on, say
[18:08] <ball> daftykins: That's a big motivation for me.  At present our WiFi is *just* for guests.
[18:08] <daftykins> hrmm probably too much! only a couple of hundred quid for a 24 port PoE+ switch
[18:08] <ball> We have the switch already.
[18:08] <ball> ...it's the router we need.
[18:09] <daftykins> mmm, derp... not sure how i switched the two, was probably thinking about lovely VLANs on a managed switch
[18:09] <daftykins> a nice pfSense appliance from netgate would be nice \o/
[18:10] <ball> Hmm... ok.
[18:14] <daftykins> depends on the tech in use on the incoming pipe, # users, whether remote access is desired, the usual
[18:17] <ball> Last time I looked it was about six concurrent users on an ADSL circuit.
[18:17] <ball> (not including guests)
[18:17] <daftykins> ah pretty trivial then
[18:18] <ball> Should be.
[18:18] <ball> Still a bit for me to learn though.
[18:18] <ball> brb, pressing a button...
[18:19]  * daftykins braces himself
[18:19] <daftykins> now i have the pfSense tuned into the UPS status :D
[18:23]  * ball grins
[18:26] <daftykins> if the office is in a biz sector that values security, pfSense would be worth it... if not, probably not so much
[18:27] <ball> We're a non-profit.
[18:28] <daftykins> hrmm probably overkill, they tend not to include WiFi so i to that with separate Ubiquiti APs
[18:28] <daftykins> so you end up with a 3 box solution minimum, 4 boxes if you adds an xDSL transceiver
[18:28] <ball> I don't want WiFi in the router anyway.
[18:28] <ball> We already have APs plugged into a PoE switch.
[18:29] <daftykins> funky, hopefully they're decent enough they can have SSIDs configured with VLANs associated to make a nice isolated guest network \o/
[18:30] <ball> They support it, I'd just have to figure out how to configure it.
[18:30] <ball> (to work with the router)
[18:30] <daftykins> the switch would need to be managed as well really
[18:30] <daftykins> that lets you do them all over a single network cable to the AP \o/
[18:30] <ball> the switch supports it too, I think.
[18:31] <ball> I should probably check the WX site for tornado warnings.
[18:33] <ball> Watches for tornado and flash flooding.  "Heavy rain".
[18:33] <daftykins> ooh err
[18:34] <ball> Looks like it's blowing over now but there's more behind it.
[18:44]  * daftykins pops LGR on - https://youtu.be/mpayqVGmKyo
[18:54] <ball> I'm watching Geoff Marshall on a Pendolino.
[20:37] <Myrtti> nice
[21:22] <daftykins> g'night all \o
[23:56] <ball> Goodnight daftykins!


[16:54] <Michal__> Hi
[16:56] <Michal__> When they paid the money?
[17:17] <Michal__> http://www.youtube.com/watch?v=JvxG3zl_WhU


[20:01] <thomi> morning
[20:21] <ibeardslee> morning
[20:27] <ajmitch> morning
[20:27] <ajmitch> I see my work desktop is bitten by leap seconds as well - firefox & chrome & virtualbox all loading the cpu
[20:29] <Atamira> good morning all
[20:35] <ajmitch> sigh, mondays
[20:35] <Atamira> oh i love them. its my day off :D
[20:35] <ajmitch> opened up my laptop to resume it, and it turned off - removed battery & put back in in order to turn it on again
[20:36] <ajmitch> just a little concerning
[21:09] <mwhudson> morning
[21:09] <mwhudson> is there a good explanation of the leap second bug somewhere?
[21:10] <ajmitch> http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second explains the crasher bug
[21:10] <ajmitch> https://lkml.org/lkml/2012/6/30/122 has why anything using threads heavily chews CPU
[21:12] <ajmitch> but we can now happily ignore the problem until next time it happens, right?
[21:46] <thumper> morning
[21:49] <ojwb> morning
[21:50] <ojwb> ajmitch: it'll be ok, there's plenty of time to rewrite everything that uses threads not to...
[21:54] <ajmitch> ojwb: I'm sure there won't be a problem when 2038 rolls around either
[22:01] <kcj_> Morning.


[00:24] <bgilbert> hey all, I'm getting an "Oops!" page when I try to log into launchpad, and the page sent me here
[00:24] <bgilbert> possibly relevant: I had a pre-SSO launchpad account, but there didn't seem to be a way to recover it, so I created a new Ubuntu One account with the same email address
[09:10] <ismail> Hi all, for a long time now I can't login to my Launchpad account via Ubuntu One. It says "Sorry, something just went wrong in Launchpad." Username<EMAIL_ADDRESS>recent Error-ID: OOPS-7b7824cad424d704c0bba68cd6f0b5eb Would anyone be able to look at this and give me a clue what might be happening?
[13:15] <cjwatson> bgilbert: If you can give us the OOPS ID then we can fix your account
[13:17] <cjwatson> ismail: I guess you deleted and recreated your SSO account in 2017?
[13:24] <cjwatson> ismail: Since you have a GPG key attached to your account, I might as well make use of it.  Please decrypt the email I just sent you and follow the instructions there
[14:07] <ismail> cjwatson: Sounds correct, msg decrypted and msg sent to you :)
[16:26] <cjwatson> ismail: OK, you should be able to log in now
[16:57] <ismail> cjwatson: Thank you! It worked.
[21:22] <bgilbert> cjwatson: it is:  OOPS-c7c564b110973c9e32d7dfbc62446771


[13:27] <dourvas> hey!Forgive me if i sound too novice but i am. i installed the last version of edubuntu (fat client). During installation everything were going wanderfull. i even were connected to internet (the 2 arrows were visible). when the installation process completed and the edubuntu started to load for the first time it crashed. I did not record the message. i had to reset the mashine. the edubuntu works fine now but there is no sign of the
[13:30] <dourvas> what do i do to connect to the network?