[00:02] * directhex hands slangasek cake [00:02] hmm, not sure how well that goes with the beer that lool was plying me with [00:03] what kind of beer? [00:03] he didn't say [00:03] i mean, a chocolate porter for example, it could go quite well [00:03] * slangasek hehs [00:03] but an american "lager"... less so [00:06] anyway, bedtime pour moi === superm1|away is now known as superm1 [01:33] hi folks [01:36] <__iron> hi [01:36] <__iron> new nvidia non-free driver kills ubuntu [01:36] Heya sistpoty [01:36] hi bddebian [01:37] __iron: which one? also, have you checked launchpad yet for bugs? [01:37] <__iron> a really nice whitescreen [01:37] <__iron> nope [01:37] <__iron> still not [01:38] __iron: which one as in which version? [01:38] <__iron> sec [01:39] <__iron> NVIDIA-Linux-x86_64-173.14.12 [01:41] __iron: can you check with https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bugs if there are any bugs describing your problem are already there? [01:41] __iron: if not, would you mind filing a new bug? [01:42] <__iron> sure [01:42] __iron: thanks. [01:42] <__iron> i take a look [01:42] __iron: just to clarify, you did install it via the ubuntu package, not the thingy that can be downloaded from nvidia, right? [01:43] __iron: And you're not using Xgl, which is pretty finniky about the libGL that you feed it. === xxx__ is now known as _iron [01:44] <_iron> some bugs [01:44] _iron: just to clarify, you did install it via the ubuntu package, not the thingy that can be downloaded from nvidia, right? (^^) [01:45] arg [01:45] <_iron> non-free [01:45] _iron: non-free, as in ubuntu package? [01:45] <_iron> nope [01:45] Then it's not going to work, for a number of reasons. [01:46] _iron: hm... I'm sorry to say that we cannot really support you installing the binary drivers directly from nvidia [01:46] (that's why we package these) [01:46] <_iron> sistpoty i know [01:46] <_iron> therefore nvidia suxx [01:46] And the white screen strongy suggests you're using Xgl, which is now removed from the archive, and which cannot support the nvidia.com installer. [01:47] _iron: however if RAOF doesn't have a clue, you might ask tseliot (probably at ubuntu-devel), but at a better time of day (i.e. when he's not afk ;)) [01:49] RAOF: btw, what's the state of nouveau in experimental? [01:49] <_iron> RAOF: strange [01:49] sistpoty: It's in there. [01:49] RAOF: will it be fun for me to try it? [01:49] *g* [01:49] Probably, yes :) [01:50] sistpoty: What card? [01:50] <_iron> i havent read that installer doenst support X [01:50] RAOF: 8500 GT [01:51] _iron: The installer overwrites libGL and doesn't provide a backup. Xgl _needs_ the mesa libgl to work, and so fails. [01:51] sistpoty: Hm. You may be in luck, but not as much luck as if you had a nv4x card :) [01:51] sistpoty: You might find my PPA more useful; it's substantially more up-to-date. [01:52] <_iron> grml [01:52] _iron: A simple solution for you would be to uninstall the xserver-xgl package; it's useles for you. [01:52] RAOF: oh, cool... I guess I might try this then... thanks! :) [01:52] <_iron> i had buy a ati-card [01:52] A _simpler_ solution would be to use the packaged drivers. [01:52] !nouveau > sistpoty [01:52] sistpoty, please see my private message [01:53] <_iron> RAOF: i thought the new driver supports 3d better [01:54] _iron: The driver you're installing is _exactly_ the driver you'd get from installing the nvidia-glx-173 package. [01:54] <_iron> mhm [01:55] The only time I'd recommend going outside the packaged drivers is when your card isn't supported _at all_. And no cards fit into that category at the moment. [01:56] <_iron> k [01:57] <_iron> i try to install the package [01:58] hm, interesting name for 9.04 [01:59] ajmitch: Ehm, indeed. [01:59] <_iron> other question [02:00] <_iron> it is normal that if i put crtl+alt+F1 [02:00] <_iron> that i cannot change to terminal ? [02:13] <_iron> RAOF: is nvidia-glx-173 package include in stable part of ubuntu ? [02:50] I need someone's assistance on upload packages to hardy-proposed [02:51] NCommander: What do you need? [02:52] * cody-somerville notes we have the UUS queue on launchpad for this. [02:53] ScottK, roughly 20 packages need uploading to hardy-proposed [02:53] Why? [02:54] ScottK-laptop, to correct the GNAT issue on Hardy. I was working with DktrKats (sp?) on it, but he's been busy recently, so I'm just going to put them in the queue for him for easy approval [02:54] Hmmm. [02:54] OK. [02:55] NCommander: You fix my lpia FTBFS yet? [02:55] ScottK-laptop, not yet, but it will float to the top of the TODO queue ;-) [02:56] Unfortunately the Universe process calls for approval before upload. [02:56] Let [02:56] is good to have a FTBFS killer around [02:56] LD [02:56] :D [02:56] * nxvl HUGS NCommander [02:56] Let's see who else is on motu-sru these days ... [02:57] * cody-somerville runs. [02:57] ScottK-laptop, I thought it was upload to hardy-proposed after uploading the bug report [02:57] Did he already approve it? [02:57] nxvl, who held the FTBFS killer title before mine [02:58] ScottK-laptop, yeah, I have all the rebuilt packages with the proper patchs in my PPA [02:58] NCommander: OK. Email me a stack of debdiffs and I'll upload. [02:58] I just need to download each source package, remove the ~ppaX from it, and then reupload if I was an MOTU [02:59] * NCommander looks at motu-sru first to see if someone is around who can tell me if one bug is fine, or I need to file multiple ones [02:59] NCommander: i think no one [02:59] nxvl, ? [02:59] NCommander: no one helt the FTBFS killer title before you [03:00] held* [03:00] * nxvl can cross the hallway and knock on cody's door if he runs to much [03:00] :D [03:01] NCommander: The problem with one bug is then people who are subscribed to bugmail for a particular package get ALL of it. [03:01] nxvl, cody-somerville? [03:02] ScottK-laptop, I think filing 22 bugs is a little overkill though [03:02] So while logically one bug makes sense, due to the carefully thought out state of Launchpad's design, it's not a great idea. [03:02] I agree. I'd have said one bug, but I lost that argument. [03:02] NCommander: yeah, we are in Boston [03:04] ScottK-laptop, the only problem is I can't put (LP: #XXX) in the changelogs because it will close the bug on the first upload [03:04] Only against that package. [03:04] * cody-somerville nods. [03:04] Huh? [03:05] NCommander: You use also affects to open a task for each affected package. The LP closing thing only closes it for the particular package. [03:05] jcastro: around? [03:06] NCommander: As an example, the auto-close on 'needs-packaging' bugs doesn't work because the bug isn't filed against that package. [03:06] ScottK-laptop, I didn't know about that "feature" [03:06] ;-) [03:06] nxvl: yeah, for a minute [03:07] jcastro: http://dev.chromium.org/developers/how-tos/build-instructions-linux [03:07] yeah what about that? [03:07] jcastro: just wanted to show you that link [03:07] oh, seen it [03:08] oh ok [03:08] ScottK, that was kdenet, right? [03:08] just making sure, since you were interested on chrome running in linux and just found that link :D [03:08] nxvl: is that page even right yet? [03:08] last i checked, it was full of build fail [03:08] nxvl: heh, it's not ported [03:08] it's full of fail [03:08] really? [03:09] since a friend of mine posted a copy of that saying it worked for him [03:09] in wine maybe [03:09] NCommander: Yes https://launchpad.net/ubuntu/hardy/+source/kdenetwork/4:3.5.10-0ubuntu1~hardy1 [03:09] oh ok [03:09] oh, they've updated [03:09] jcastro: btw, i;m quite sure i will make it for fosscamp! \o/ [03:10] \o/ [03:11] nxvl: there's not even a skeleton of a GUI of chrome for linux [03:12] chrome is basically a toolkit flamewar waiting to happen [03:12] pwnguin: the FAQ already says GTK+ [03:12] orly [03:12] rly [03:12] i should find a relevant mailing list to subscribe to [03:13] "With all of that said, the plan is to use GTK. It's not due to any dislike of Qt, but just because there's more experience on the team with GTK and it matches the existing Firefox dependency on Linux. Please keep calm. :)" [03:13] http://dev.chromium.org/developers/faq [03:13] well that was very 'collaborative' ;) [03:14] but sometimes, you just gotta recognize the inevitable non-consensus and cut the knot [03:14] if you expected them to try & find consensus, you have to be smoking something powerful :) [03:19] i expect that they want a contributing developer community, but maybe google can just hire one [03:19] do you like my hat? it's made of money! [03:35] ScottK, checking if kppp should be compiled... no [03:35] ScottK, I found your problem [03:36] ScottK, checking linux/if_ppp.h usability... no [03:36] checking linux/if_ppp.h presence... yes [03:36] And there is your reason [03:40] NCommander: OK, so what's the fix? [03:40] ScottK-laptop, I'll tell you as soon as I finish downloading the lpia hardy chroot [03:40] Thanks. [03:40] ScottK-laptop, (I was scrubbing the log for answers) [03:40] ScottK-laptop, it might need a patch to the kernel headers or something [03:41] Ouch. [03:41] ScottK-laptop, which package are the kernel headers on lpia [03:41] NCommander: If that's what needs to be done, it's not worth it. They aren't going to path the Hardy lpia kernel to make KDE work on it. [03:41] path/patch [03:42] ScottK-laptop, if its not a possibility, I can just patch it so it doesn't install kppp [03:42] ScottK-laptop, everything else compiles just fine, so we disable kppp [03:42] ScottK-laptop, it also may be a defective test [03:42] NCommander: One that one arch sounds good. [03:43] ScottK-laptop, huh? [03:43] Disable kppp on lpia. [03:43] yeah, should be easy enough to do [03:43] That sounds good. [03:43] Well, if I can properly fix it, I perfer to do that first [03:46] ScottK-laptop, grabbing the build-deps [03:46] Great. [03:47] Is there any device that ships with lpia yet? [03:50] Dunno. [03:50] I'm just picky about being complete. [03:51] It also then becomes another reason why 3.5.10 in hardy-updates is an improvement over what we have now. [03:51] But I've also got the flu, so I may be completely out of my mind at this point. [03:51] c [03:51] er [03:51] Ew [03:51] The header appears to be partially broken [03:51] It probably needs a dependency [03:52] Be nice or I'll cough on my screen. [03:52] * Hobbsee puts ScottK-laptop in a sealed box. [03:52] problem solved. [03:52] Ah, sweet, sweet silence. [03:56] so, for this intrepid+1, will bzr be *required* for committing to ubuntu? [03:57] i hope so [03:57] Hobbsee: No. [03:58] Hobbsee: Long thread on -devel that it'll all be optional for ages to come. [03:58] ScottK-laptop: oh, good. [03:58] optional on a per package or per upload basis? [03:58] Per upload [03:58] You'll be free to keep working just like you do now if you want. [03:59] i wouldn't mind if it made the process easier, and was fast, but... [03:59] Yeah. That was kind of my point in said thread. [03:59] I was accused of being obstructionist. [03:59] hah [04:00] Bleck [04:00] I don't want bzr packaging mandatory [04:00] In the end we settled that making it not suck before making it mandatory would be a good idea. [04:00] so basically, if you do a normal upload, it'll make a big commit in a bzr repo on your behalf somewhere? [04:01] ScottK, well, I'm making progress, the header appears usable once you define a lot of other crazy headers [04:01] ScottK, I can probably force the test, and then make changes to the includes [04:02] Interesting. [04:03] pwnguin: Something like that. We discussed it to death on -devel. Near the end of the thread there's a link to a spec. [04:03] ScottK, and what seems to be a possible typo in a header [04:03] #define aligned_u64 __u64 __attribute__((aligned(8))) [04:04] Anyone else see the mistake? [04:04] one of the reasons you do bzr/git/svn is to make it more accessible to people not using your code. i think a nice collaborative future might include commit emails on packages hitting upstream mailing lists [04:05] s/using/running [04:06] pwnguin: Personally, I don't have enough time to learn the details of a new VCS just for Ubuntu. [04:06] ScottK, I found the bug it seems, now its a matter of figuring out how to fix it [04:06] NCommander: Great. [04:06] NCommander: What's the bug in? [04:07] ScottK-laptop, appears a -DDEFINE is required to make the right type information be activated [04:07] I need to look at the config log and see what I need to add [04:10] ok so about xournal. the DD developer is basically mia and the last NMU'er has said they dont have time to help out reviewing patches for upstream inclusion [04:12] does MOTU basically adopt it and hope debian recognizes ubuntu as upstream? [04:12] * NCommander sighs [04:12] What a headache [04:13] ScottK-laptop, ok, there appears to be a good way to fix this [04:13] Hold on [04:14] Kewl. [04:14] pwnguin: How interested in the package are you? [04:16] im not sure it matters; vicenczo (sp?) seems to be taking decent care of it [04:17] but theres a request from sponsors on a merge that we get ubuntu nonspecific patches upstream somehow [04:17] its mostly packaging at the moment, so i don't care a whole lot -- i just got my replacement ac cable for the tablet to test again [04:18] ScottK, testing fix [04:23] ScottK-laptop: i'd like to see xournal continue to be up to date in ubuntu, but honestly, the thought of me being the main contact is a bit intimidating [04:24] pwnguin: Then just fix it up here and send patches in bugs to Debian. What happens after that, isn't essentially your problem. If you get ambitious you could NMU the package in Debian. [04:24] currently xournal's up to date with xournal upstream, but debian has some changes to the packaging that people want [04:24] s/people/person [04:25] ScottK, poke? [04:26] (I pinged you on the wrong channel) [04:26] Yeah. Filing it now. [04:26] NCommander: Bug 267991 [04:26] Launchpad bug 267991 in kdenetwork "kdenetwork FTBFS on lpia" [Undecided,New] https://launchpad.net/bugs/267991 [04:27] ScottK-laptop, I changed the code to hook against the glibc PPP interface vs using the Linux one directly (its standardized, its just the glibc interface has proper headers) [04:28] ScottK-laptop: how does one contribute patches via BTS against a debian package without pissing off the developer that might be paying attention? [04:28] ScottK, the changelog has to target hardy-proposed, right? [04:28] i recall having a not good experience with thinkfinger [04:29] NCommander: hardy-backports. [04:29] NCommander: That's where 3.5.10 is right now. [04:29] You are not the bug assignee nor the maintainer of kdenetwork (Ubuntu), and therefore cannot edit this bug's status. [04:29] That's a new error [04:29] are you logged in? [04:30] yeah [04:30] have super powers (i forget the team -- triagers?) [04:30] There it goes [04:31] pwnguin: It depends a lot on the Maintainer. Most are happy to get a good, well explained patch. [04:31] pwnguin: If the maintainer is pretty well MIA, odds of him being annoyed are low in any case. [04:31] ScottK-laptop, I have a patch against the 3.5.9 FTBFS, not backports, but I can spin that one easily if this works [04:32] Should be the same. [04:33] LEts do the SRU one first, that one targets hardy-proposed first, right? [04:34] NCommander: I want to get all of 3.5.10 into -updates, so I'd rather just do it once. [04:35] Does 3.5.10 meet SRU requirements? [04:36] Sort of. [04:36] "Sort of"? [04:37] ok, so i sorta subscribed someone to a bug to get their opinion [04:38] https://bugs.edge.launchpad.net/ubuntu/+source/xournal/+bug/245828 [04:38] Launchpad bug 245828 in xournal "Please merge xournal 0.4.2.1-0.1 (universe) from Debian unstable (main)" [Undecided,New] [04:38] their reply is that they're too busy -- should i unsubscribe them? [04:40] pwnguin: You can't. [04:40] ok [04:41] that makes it both easy and embaressing =/ [06:09] good morning === nellery_ is now known as nellery [06:43] Hi. Even is Intrepid is frozen, does it make sense to follow up on uploading new packages in REVU? [06:56] cody-somerville, you around? === superm1 is now known as superm1|away [07:55] bug #85266 for motu-sru :) [07:55] Launchpad bug 85266 in ngircd "ngircd refuses to start automatically through sysv init" [Medium,In progress] https://launchpad.net/bugs/85266 [08:13] jaunty jackalope [08:13] heh [08:16] morninh everyone [08:16] morning === BugMaN1 is now known as BugMaN === BugMaN is now known as bugman === bugman is now known as BugMaN [09:11] pochu: are you around ? [09:18] aha, i wasn't far off in my predictions! [09:18] 2008-08/#ubuntu-motu.27.log:27-08-2008 14:02:48 > directhex: there are three* places a given package can be available, excluding a PPA. if we say 1. 0 is in the main repository for intrepid, then 1.2 is in the main repository for jilted jackalope, then 1.2 can only end up available in intrepid vi a the backports repo, updates repo, or a ppa (and you won't be in updates without good reason). the version that comes in via backports/upd [09:18] to be older than the version in jilted jackalope, [09:23] i had named it jumping juniper in my head. [09:23] but jackalope sounds cooler [09:23] of course, there's one minor issue with jackalopes [09:24] they have this terrible habit of NOT EXISTING [09:25] directhex: they do.. [09:25] its like a rabbit thingy [09:25] well, in folklore anyways [09:25] a non-existent rabbit with horns [09:26] well... its kinda like santa. lots of people think he exists. or maybe religion [09:26] ooh, don't start THAT flame war [09:26] there are lots of proud santaologists in here [09:26] hehe [09:26] um [09:27] jackalops can exist, it's some kind of disease [09:27] poor rabbits [09:27] by the time you realise, we already have 9.10 [09:27] so ubuntu 9.04 has painful tumours? [09:27] ouch ;) [09:35] well. its on wikipedia. and anything on wikipedia is true and thats good enough for me [09:36] 'The legend of the jackalope has bred the rise of many outlandish (and largely tongue-in-cheek) claims as to the creature's habits. For example, it is said to be a hybrid of the pygmy-deer and a species of "killer-rabbit".' [09:37] that rabbit's a killer! [09:48] huats: I am now (more or less) [09:49] hey pochu :) [09:49] don't worry if you don't have lots of time... [09:54] * james_w hugs directhex [09:54] thanks a lot for sorting out mono-tools [09:57] james_w, of course. debian-mono aims for quality service! === fta_ is now known as fta [10:19] gah [10:19] and i thought the jaunty jackalope thing was a joke [10:21] lol [10:25] dholbach, hi, is the @ubuntu.com redirection automatically created for motus? [10:26] fta: it should be for everybody who's in ubuntumembers [10:26] fta: if it doesn't work, best to talk to the folks in #launchpad [10:26] fta: ubuntumembers in launchpad automatically get it [10:26] dholbach, it doesn't work for me [10:26] i'll ask there [10:26] great, thanks [10:27] Oh dear. A 3500 word reply to something complaining about the 2000 word bug report. [10:27] hello dholbach :-) [10:28] hiya jsgotangco === quadrispro1 is now known as quadrispro [10:59] TheMuso: ping [11:01] sispoty, ping === quadrispro1 is now known as quadrispro [11:16] WHAT is going on with packages.debian.org?? [11:17] it's broken again. i suggest running around screaming, flailing your arms [11:17] ...in #debian-devel. [11:18] i meant in your office. perhaps both! [11:18] directhex: I was doing that, didn't help [11:18] :-) [11:19] It's not like it's down, it's more like a DOS [11:21] Is there a mirror somewhere? [11:21] Of packages.debian.org I mean [11:22] packages.qa.debian? [11:22] I don't think so, but most/all of the functionality is provided elsewhere, though at several different places [11:30] yay! packages.qa.debian.org works [11:31] if you know the source package you want to have information about, packages.qa.d.o is the better choice usually === dholbach_ is now known as dholbach [11:35] azeem: I will use it in the future, for sure [11:47] mok0: What can I do for you? [11:48] sing and dance [12:05] TheMuso: oh, I just want to check with you that it's ok to upload the merge from bug 261089 [12:05] Launchpad bug 261089 in atlas "Please merge atlas 3.6.0-22 (universe) from Debian unstable (main)" [Undecided,In progress] https://launchpad.net/bugs/261089 [12:06] mok0: Sure go ahead. [12:06] TheMuso: great, thx === ara_ is now known as ara === ogra_ is now known as ogra [12:42] hey folks [12:43] i have a problem with ubuntu hardys qt4 package [12:43] it's supposed to include the headers for Phonon, but it doesnt [12:43] what do I have to do to get this fixed? [12:43] Cheetah: headers are normally only in -dev packages [12:44] libphonon-dev [12:45] libphonon-dev does not include the includes for qt4 [12:45] Cheetah: better chance if you ask on #kubuntu-devel [12:47] which includes specifically? it installs to /usr/lib/kde4/include/ [12:47] hmm.. libphonon-dev provides includes in /usr/lib/kde4/include/phonon/ but qt4 expects them in /usr/include/qt4/phonon [12:47] so alter your -I [12:47] meh, that's dirty [12:48] #include is what the qt documentation says [12:48] Also, it doesn't work if the code has include === LucidFox_ is now known as LucidFox [12:48] hmm? [12:49] talk to debian-qt-kde, they're the original maintainers [12:49] 'kay === greeneggsnospam is now known as jsgotangco === ara_ is now known as ara [13:55] hi, how does one incorporate existing docs+examples in a new package? [13:56] karooga: add a package in debian/control and install the docs in that [13:56] karooga: Which package? [14:00] if using debhelper you'll likely need to call dh_installdocs and dh_installexamples in debian/rules [14:01] dh7! [14:08] ScottK: TheMuso: Does anyone of you have some time? I wish to discuss FFE for a package that has not been synced ever from Debian (non-free). [14:09] coo, what? [14:22] bleh, i'm suffering PPA weirdness again. [14:45] hardy-updates problems. why don't PPAs depend on foo-updates? [14:46] directhex: since when is this a ppa support channel? [14:46] directhex: we don't do ppas - #launchpad does [14:46] * Hobbsee expects you'll get some answer about pockets and the phrase "not yet implemented" [14:47] (same answer as why it doesn't build against backports) [15:10] anyone else feeling uncomfortable with having advertisments to a commercial service in /etc/motd? [15:10] siretart: what does it say now? i've not upgraded. [15:10] siretart: what service is that? [15:11] hotmail and msn live search! [15:11] directhex: yddrrk [15:12] ... and it isn't even April 1st [15:16] doko: there's something that explain the build system of gcj package? [15:16] i'd like to understand how build-depends are generated. [15:16] Hobbsee: Graph these measurements at https://landscape.canonical.com [15:16] gaspa: I don't understand the question [15:17] siretart: was it just updated? don't see that here... [15:17] doko: gcj has b-d generated somehow, but there are some weird outputs: as "[]" and "[!none]".... [15:18] i'm guessing how the rules of gcj works, in brief. [15:18] $ apt-cache showsrc gcj-4.3 |grep Build-Depends [15:18] Build-Depends: dpkg-dev (>= 1.14.15), debhelper (>= 5.0.62), gcc-multilib [amd64 i386 mips mipsel powerpc ppc64 s390 sparc kfreebsd-amd64], libc6.1-dev (>= 2.5) [alpha ia64] | libc0.3-dev (>= 2.5) [hurd-i386] | libc0.1-dev (>= 2.5) [kfreebsd-i386 kfreebsd-amd64] | libc6-dev (>= 2.5), libc6-dev-amd64 [i386], libc6-dev-sparc64 [sparc], libc6-dev-s390x [s390], libc6-dev-i386 [amd64], libc6-dev-powerpc [ppc64], libc6-dev-ppc64 [power [15:18] pc], libc0.1-dev-i386 [kfreebsd-amd64], lib32gcc1 [amd64 ppc64 kfreebsd-amd64], lib64gcc1 [i386 powerpc sparc s390], libc6-dev-mips64 [mips mipsel], libc6-dev-mipsn32 [mips mipsel], libunwind7-dev (>= 0.98.5-6) [ia64], libatomic-ops-dev [ia64], m4, autoconf, automake1.9, libtool, gawk, dejagnu [!none !hurd-i386], lzma, binutils (>= 2.18.1~cvs20080103-2) [mips mipsel] | binutils-multiarch (>= 2.18.1~cvs20080103-2) [mips mipsel], b [15:18] inutils (>= 2.17cvs20070426) | binutils-multiarch (>= 2.17cvs20070426), binutils-hppa64 (>= 2.17cvs20070426) [hppa], gperf (>= 3.0.1), bison (>= 1:2.3), flex, gettext, texinfo (>= 4.3), libmpfr-dev (>= 2.3.0), locales [!hurd-i386 !m68k], procps [!hurd-i386], sharutils, libz-dev, fastjar, libmagic-dev, libecj-java (>= 3.3.0-2), zip, libasound2-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], libxtst-dev, libxt-dev, libgtk2.0-dev ( [15:18] >= 2.4.4-2), libart-2.0-dev, libcairo2-dev, libgconf2-dev, xulrunner-1.9-dev [!none !hurd-i386], g++-4.3 [armel], gcc-4.3-source (>= 4.3.2), gcc-4.3-source (<< 4.3.3), realpath (>= 1.9.12), chrpath, lsb-release, make (>= 3.81) [15:19] flood [15:19] Build-Depends-Indep: gjdoc [15:19] hmm, don't see any of these [15:19] dholbach: thx :P [15:19] gaspa: look at debian/rules.conf [15:19] doko: gcj-4.2, i meant [15:19] :) [15:19] siretart: I don't see it either. [15:19] siretart: ah, right [15:19] gaspa: do these hurt? [15:20] doko: actually i don't know. It's not policy compliant, and nobody knows how build-machine behave in this cases. [15:21] does policy even say something about this? [15:21] and apparently it did build [15:22] yes, it builds,though policy says that bracket should specify all not-negated or all negated... so empty bracket are confusing. [15:23] i saw them running edos-debcheck, that's a bit 'fussy'... [15:24] doko: perhaps it's not important nor urgent, but i'd like to understand and make it better, if I'll able to. [15:29] Has anyone here their own buildd system running? [15:37] hi folks, do you have a good example of a well-written freeze exception request bug i can look at? [15:39] dholbach: Btw, I watched to the first of the packaging jam videos yesterday (it's quite similar to what I did, but mine was through creating a single-file package from scratch instea of fixing 'colour') :). What is the second part about? === ember_ is now known as ember [15:41] RainCT: there were three tasks we worked on: generating a debdiff from a very small change, updating a package and then somebody asked me to show how to package something from scratch [15:43] the reason i ask is, a new upstream bugfix release of pybackpack went into debian today and would fix 5 launchpad bugs if ubuntu syncs it, so i guess i'll need to request an exception [15:45] AndyP: if it's only bugfixes, not new features, it doesn't need a FFE [15:46] asomething: oh, great, so what's the process? [15:46] whats the best way to include docs and examples in a package. e.g. I have my_package/docs/some_docs.txt [15:46] sorry, i mean best way to install docs in my package? [15:48] AndyP: as it seems that it would be a simple sync from Debian and not a merge, file a sync request bug. it would probably be good to post the debian and upstream changelogs since the last ubuntu version to show that it's only bugfixs [15:49] i'm guessing just something in debian/rules? [15:50] asomething: ok, thanks for your help [15:51] AndyP: if it will closes specific bugs on lp list those as well, helps get quicker attention [15:52] karooga: dh_installdocs and dh_installexamples [15:58] asomething: shots. [16:02] karooga: if there are things not being picked up automagically you can create a debian/your_package.docs file [16:04] asomething: the files are pretty straight forward, a txt file in the docs dir and some py scripts in an examples dir [16:18] nxvl: hi, any plans for terminator 0.10 in intrepid? :) [16:19] pochu: nope, it doesn't involve any bug fixing, so it's quite difficult to get ACK's from the sru team [16:19] pochu: i already packaged it and i'm seeking for a debian sponsor, but that's it, it will need to wait until jaunty [16:20] nxvl: fair enough, thank you for the info [16:20] which repositories do PPAs use? [16:24] nm, it's in a build log [16:25] Heya gang [16:28] Hi bddebian [16:28] Hi bddebian [16:29] Hi geser, iulian [16:29] iulian: Congrats! :) [16:29]