[12:03] and..? [12:03] we know that the package builds, seeing as it's in main [12:03] and I see the output I pasted in the bug report [12:03] dooglus: why not building the package normally? [12:03] instead of running ./configure? [12:05] ajmitch: what's the normal way to build a package? [12:05] dpkg-buildpackage, or using debuild, or pbuilder build.. [12:05] all of which are equivalent [12:05] ok. [12:05] I'll try that. [12:05] how should I have found those commands without you telling me? [12:06] debian NM guide, or asking how you build packages [12:06] or various wiki pages like PackagingTips [12:06] slomo: i can package it from here on. thanks for your help. the plan is to put it into backports and into universe in dapper. can you send me the package sources? ankur.kotwal@gmail.com thanks again. [12:06] or IntroDeveloperDocs, of course [12:08] "of course"? [12:08] Unfrgiven is the author :) [12:08] I could hardly forget his contribution [12:09] ok, shadow built perfectly fine in pbuilder as expected :) [12:10] I was using the traditional configure;make incantation. I wasn't aware of dpkg-buildpackage [12:11] they're packaged for a reason [12:11] debian/rules controls how configure, make, etc are called [12:11] ok. [12:11] for shadow, debian/patches/324_configure.in-no-debian-dir.dpatch removed that line from configure [12:12] oh yes! [12:13] there are 134 patches for shadow there :) [12:14] sometimes when I "apt-get source", patches get applied automatically, and other times (like this time) they don't get applied (presumably until I use dpkg-buildpackage) [12:15] when you apt-get source, it applies the diff.gz [12:15] which contains the debian/ dir [12:15] and often other things [12:15] these are build-time patches [12:15] makes it a lot easier to keep them separate [12:16] ok [12:16] thanks for your help. [12:16] no problem [12:17] did you notice I asked about this in #ubuntu-devel before posting the bug? === marcin_ant [n=user@www.e-dev.tele2.pl] has joined #ubuntu-motu [12:20] no I didn't [12:20] how long did you wait before posting? [12:21] the only thing I see you asking is if bugs go to malone now === herzi [n=herzi@d002024.adsl.hansenet.de] has joined #ubuntu-motu [12:26] yay, Breezy is released [12:27] Time to rebuild VLC... [12:27] yep [12:27] were you guys able to accomplish everyting you wanted to for universe? [12:28] erm, for the release [12:28] of course not [12:28] nope, for me at least. I didn't gain MOTU Powah [12:28] you didn't help us out :P [12:28] Kyral: there was hardly time for you to get up to speed on it [12:28] bah [12:28] Yah I know [12:28] Twas a pun :P [12:29] the archive server is slow [12:29] probably gettin hammered [12:29] no surprise there [12:29] :) [12:30] I am doing a sudo apt-get -d dist-upgrade on 2 boxes :) === lakin [n=lakin@dsl-hill-66-18-228-60-cgy.nucleus.com] has joined #ubuntu-motu [12:30] I'm pbuildering libdvbpsi [12:31] time to go home [12:32] why does Sid VLC depend on libdvbpsi and Breezy VLC doesn't? === Kyral wonders what would happen if he dist-upgraded while Sid repos were active... === tvelocity [n=tony@ipa217.4.tellas.gr] has joined #ubuntu-motu [12:51] I mean I know I would wind up in SID land....but how major would breakage be... === seth_k|lappy [n=seth@asmallorange.com] has joined #ubuntu-motu === Tifa [n=alucard@cpc3-cove3-5-1-cust39.brhm.cable.ntl.com] has joined #ubuntu-motu === Fuddl [n=fuddl@2001:6f8:9cf:0:20f:eaff:fe4d:d7b7] has joined #ubuntu-motu === LaserJock [n=LaserJoc@lambda.chem.unr.edu] has joined #ubuntu-motu === bigcx2 [n=bigcx2@jpi-stillwatr-233-242.dmisinetworks.net] has joined #ubuntu-motu === Tifa [n=alucard@cpc3-cove3-5-1-cust39.brhm.cable.ntl.com] has joined #ubuntu-motu === marcin_ant [n=user@www.e-dev.tele2.pl] has joined #ubuntu-motu === zul [n=chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-motu === doko_ [n=doko@dslb-084-059-067-196.pools.arcor-ip.net] has joined #ubuntu-motu [02:37] evening [02:40] hi === wickedpuppy [n=wickedpu@cm25.epsilon165.maxonline.com.sg] has joined #ubuntu-motu === Amaranth [i=travis@unaffiliated/amaranth] has joined #ubuntu-motu === slomo_ [n=slomo@p5487F27F.dip.t-dialin.net] has joined #ubuntu-motu === b3nw [n=m@unaffiliated/b3nw] has joined #ubuntu-motu === marcin_ant [n=user@www.e-dev.tele2.pl] has joined #ubuntu-motu === Hirion [n=Hirion@p5487F27F.dip.t-dialin.net] has joined #ubuntu-motu === robitaille [n=robitail@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-motu === LaserJock [n=icechat5@ppp-69-227-157-114.dsl.renocs.pacbell.net] has joined #ubuntu-motu [03:39] hi everyone [03:39] hello bmonty [03:39] enjoying the break? [03:40] I'm actually bored ;P [03:42] ajmitch: so what happens now, does automatic syncing with debian get turned on again? [03:42] when dapper reopens [03:42] the flood starts [03:42] does that cause lots of breakage? [03:42] oh yes [03:42] we could have *lots* of breakage :) [03:43] it's fun [03:43] I'm sure === bmonty rolls his eyes === Nafallo preps galago ;-) [03:43] Yanno what would cause more breakage? [03:43] Breezy -> Sid [03:43] Kyral: packages out of sync [03:44] ajmitch: btw, what to do when I don't have a dapper-pbuilder to build at? :-) [03:44] we have to rush to get our ubuntu changes merged in to minimise the breakage [03:44] ajmitch, no kiddin' I saw what would happen if I did it ;P [03:44] Nafallo: dist-upgrade :P [03:44] ajmitch: it's not opened ;-) [03:44] Nafallo: then use breezy for now [03:44] man.. [03:44] ;) [03:45] you have to figure breezy and badger will be very similar for at least a couple weeks :) [03:45] hi bmonty, I got my IRC port blocking problem fixed [03:45] Hot ***! [03:45] the Servers are back! [03:45] bmonty: *cough* [03:45] bmonty: breezy & dapper? ;) [03:45] uhh [03:45] so... build the debian packages that will ftbfs because of dbus/libdbus against breezy, dist-upgrade to dapper, rebuild them and then dput :-) [03:45] ajmitch: yeah...whoops [03:45] bmonty: there might be a few thousand packages synced in the first couple of weeks [03:45] anyone getting a GPG Key error on the Breezy Update server [03:46] Nafallo: eh? [03:46] LaserJock: did the "I need IRC to do my studies" story work? :) [03:46] ajmitch: no? :-) [03:46] Nafallo: you're only going to upload source anyway, so just do the merges like usual [03:46] LaserJock: excellent [03:46] dapper - badger....sounds the same to me :P [03:47] bmonty, no I found out that freenode also has port 8001 which wasn't blocked by my university [03:47] LaserJock: hah, nice evasion [03:47] ahh...hopefully they are complacent and don't notice the traffic :) [03:47] LaserJock: they're probably mainly trying to stop botnets & illegal filesharing anyway :) [03:48] ajmitch: well, I have to merge and build those libs (that's in debian) so that I can use them for building the other parts that's not in debian :-) [03:48] ajmitch: yeah that's why I knew that they wouldn't open the port for me [03:48] Nafallo: or you could just wait a few days & have a break :) [03:48] ajmitch: and then merge those when they arrive in dapper so that I can send the rest of them to NEW ;-) [03:49] Nafallo: just let them sync, FTBFS, and then fix the source [03:49] grrr, I'm getting tired of the script kiddies probing my ssh server [03:49] Nafallo: plenty of other stuff to work on still until dapper opens [03:49] ajmitch: oh? :-) [03:50] bmonty: :-) [03:50] you can help me get OpenLDAP and Kerberos working :) [03:50] Nafallo: clean up malone, get fixed packages queued for upload [03:50] why? [03:50] Nafallo: because the packages are still broken & will be broken after dapper opens :P [03:50] new versions will probably be merged or synced for most of it anyway? [03:51] most, but not all [03:51] we've generally merged in a lot of new upstream versions to fix the more serious bugs [03:51] baah, we need an *ubuntu* search for Malone then? :-) [03:51] what? [03:51] to see what's not going to be synced automatically. [03:52] oh right [03:52] http://ajmitch.meta.net.nz/debuild/ubuntu/merge-tool/current/merges [03:52] ajmitch: do you think the freeze on syncs with debian helps or ends up causing more problems....seems like keeping the syncs on longer would cause less problems [03:52] :-) [03:52] I assume that synced packages don't override packages that have a *ubuntu version number. Is that right? [03:52] bmonty: I think it helps, and we'll enforce it more strictly for dapper [03:52] LaserJock: correct [03:53] LaserJock: which is why we have > 1200 source packages in breezy with an ubuntu* version [03:53] bmonty: keeping the syncs on longer, means, 'get more changes' [03:53] a lot of them will need manually merged [03:53] bmonty: which means, if debian do, say, a gcc4 transition in the middle of our freeze, 'break everything later' [03:53] that will be pain [03:53] sure [03:53] lifeless: maybe, but it also seems like the way to fix a lot of FTBFS packages was a sync === tseng hates on MOM [03:53] and you can have a merge that applies cleanly but is still dead wrong [03:54] i always have that [03:54] bmonty: yes, but its an explicit choice. [03:54] it does stupid stuff with build-deps [03:54] bmonty: getting random crack from unstable later into the release just means less chance to fix the bugs that are introduced [03:54] lifeless: true, maybe we need a different process for getting the syncs done [03:54] bmonty: there will be [03:54] but it'll stay essentially the same [03:54] lol [03:54] we freeze for a reason [03:55] I think sync requests will be done via launchpad at some point [03:55] yeah, I'm not saying that the freeze is a bad idea, just that based on what I worked on it seemed the freeze cause a good portion of the issues [03:56] bmonty: just think of how many more issues you might have seen without the freeze [03:56] we're grabbing from debian *unstable*, it's called that for a reason :) [03:56] (and not just because of the developers) [03:56] ajmitch: for packages in main, I would definately agree...universe, I'm not so sure [03:56] ajmitch: yeah, when sarge was release I stopped running unstable [03:57] bmonty: UVF is essential for universe [03:57] I know ogra agrees with me on that === Amaranth [i=travis@unaffiliated/amaranth] has joined #ubuntu-motu [03:57] the FTBFS packages I was working on where older than testing, how does that happen? Is it just overlooked? [03:57] lifeless: btw, python can't import files with a - in the filename? [03:57] ajmitch: correct [03:57] well you guys have more experience with this than me, so I'm sure it is the best choice [03:58] ajmitch: bzr-man is a script :0 [03:58] ajmitch: I agree with you to fwiw :-) [03:58] lifeless: a script, but most of it is a function :) [03:58] bmonty: don't feel bad, I thought the same thing ;-) [03:58] patches accepted gratefully :) [03:59] lifeless: yeah, trying to get the manpage to be generated properly by setup.py :) [03:59] anyway, ubuntuIM needs galago :-) [03:59] LaserJock: I'm not really arguing the point...just trying to figure out more about why the freeze was done === Nafallo starts dputting breezy packages to his server ;-) [03:59] Nafallo: mini-dinstall? :) [04:00] ajmitch: nope, main only :-) === Arrogance [n=aks@ottawa-hs-209-217-124-29.d-ip.magma.ca] has joined #ubuntu-motu [04:00] I got mini-dinstall working on my web server...it is very nice :) [04:00] post_upload_command = ssh ogre "cd public_html/packages && rm *.changes; apt-ftparchive packages . | gzip > Packages.gz && apt-ftparchive sources . | gzip > Sources.gz" [04:00] :-) [04:00] Nafallo: you can do the same thing with mini-dinstall [04:01] bmonty: that's not in main :-) [04:01] I ONLY use main on my server :-) [04:01] ah [04:01] you just need to get back to doing universe-security [04:01] slacker [04:01] yes [04:01] I run debian on my servers, so I didn't notice [04:02] hehe :-) [04:02] we now unofficially support breezy only for universe security [04:02] I started learning packaging with pbuilder and mini-dinstall. I think it has really helped me learn. [04:02] but but but... MOTU(IM) is more fun ;-) [04:02] unless people still want to do hoary fixes :) [04:02] Nafallo: too bad, get fixing [04:02] LaserJock: less opportunity to mess up your system :) [04:02] yeah [04:02] MOTU work isn't about fun [04:02] it's about getting whipped into doing stuff ;) [04:03] I know. I was just tired about feeling like the only one. and I'm still rather new to programming so... :-P [04:03] Nafallo: recruit more [04:03] yes [04:03] Nafallo: I was wanting to help out, but it wasn't fun enough === tseng too [04:03] you need to find some real suckers === bmonty looks for bddebian. [04:04] bmonty: I was not going to say that ;) [04:04] oh darn, he isn't on [04:04] I know it's not fun... that's why I ended up with half-finished stuff all over the place... [04:04] I need to get my code for the ubuntu-spy working [04:04] and packaged [04:04] 6 months is a lot shorter than you think :) [04:04] so get it done ASAP [04:05] putting it off won't work [04:05] well the feature demands are rolling in on the forum for dapper [04:06] anyway, if everyone does there share on universe security, then it will be easier to do stuff there. [04:06] yep [04:06] Nafallo: how does universe security work? [04:06] bmonty: you fix stuff [04:06] based on what? [04:06] pretty much the same as MOTU work really [04:07] basically grabbing patches [04:07] https://wiki.ubuntu.com/SecurityUpdateProcedures [04:07] and applying them to the current source :) [04:07] basically like that [04:07] I think I can do that :) [04:08] patch the stuff minimally to let it not be insecure, send it do the mailing-list, get pitti to like it (hard ;-)) and then do the upload/have someone do the upload :-). [04:08] security-review list has been very quiet lately [04:08] well, there have been LOTS of stuff todo in breezy [04:09] so I'm not surprised... [04:09] yes [04:09] bbiab [04:10] Nafallo: count me in [04:11] bmonty: :-) [04:11] I'm hoping to count everyone in :-) [04:11] are you going to post vulnerabilities that require a fix, and then assign people to work the package, or do people just work on things they find? [04:12] security is just like regular release-cycle. you can't be an expert on everything :-). [04:12] we have a tool for that :-) [04:12] I just have to find it... :-P [04:13] http://people.ubuntu.com/~pitti/ubuntu-cve/ [04:14] hmm...lots for mozilla [04:14] if upstream (!debian) made a hoary-package-1, which I'm merging, should I use 1ubuntu1 or 0ubuntu1? [04:15] 1ubuntu0.1? [04:15] I think that is what the wiki page says [04:15] it's not security :-) [04:15] oh, my bad [04:15] it's dapper :-) === nsomniac [n=nsomniac@ppp-70-242-120-221.dsl.rcsntx.swbell.net] has joined #ubuntu-motu [04:20] Nafallo: it has to be greater than any existing package, but they should be beaten for versioning it like that [04:20] ajmitch: oki, thanx [04:20] Nafallo: is it in debian yet, and if not, why not? :) [04:20] since the simple way might be to get it into sid quickly [04:21] ajmitch: I don't know :-). Christian Hammond packaged it for hoary. [04:21] it's not in any dist, I found it on the homepage... [04:21] packaged as native :-P [04:22] ah right [04:22] what is it? [04:22] http://www.galago-project.org/ [04:23] what package, I mean === ajmitch thinks he probably has that installed at the moment, too [04:23] some packages are in debian [04:23] all of them :-P [04:23] libgalago (0.3.3-1) unstable; urgency=low [04:24] * Packaged for Debian, based on upstream work. (closes: #330023 ) [04:24] -- Riccardo Setti Sun, 25 Sep 2005 12:51:22 +0200 [04:24] yea, I merged that lib from debian :-) [04:24] ok [04:24] so that's hardly 'all of them' then [04:25] well, I'm taking what's not in debian from upstream's repo ;-) [04:25] (found under download) [04:25] right [04:25] which is what I was asking about - what's not in debian? :P [04:26] gnome-preferences-applet, eds-feed for instance [04:27] missing the gtk libs to. [04:27] galago-sharp and libgalago IS in debian :-) [04:31] Nafallo: you could work with the libgalago debian maintainer to get them in [04:31] ajmitch: yea, I'll just build them first :-) [04:31] hmm, maybe he's doing that to... [04:32] I'll mail him tomorrow after a good nights sleep ;-) [04:32] it's 4:32 here :-) [04:32] ok [04:32] sleep well :) [04:32] ouch! eds-feed hates me :-P === ajmitch fetches some slomo_ packages for debian reviewing [04:33] slomo_: will try & check these in the weekend, for general packaging, and then test them next week.. [04:33] hmm, gcc-errors here we come! :-) === _maydayj_ [n=maydayja@ip101109.101.nas.net] has joined #ubuntu-motu === _maydayj_ [n=maydayja@ip101109.101.nas.net] has joined #ubuntu-motu [04:47] night all [04:50] gnight bmonty [04:56] My Goal for the Dapper Release Cycle: Gain my "MOTU License" ;P [04:57] but not tonight [04:57] My Goal for the Dapper Release Cycle: smeg-gnome, smeg-kde [04:57] but not for a month or so ;) [05:01] well my ultimate Goal for Dapper is to become an Ubuntu Member [05:01] My Goal for the Dapper Release Cycle: being the cynical bastard I usually am [05:01] becoming a MOTU is just a step on the path :D [05:01] wow [05:01] the damn package actually build-deps cvs [05:02] Anywya, Family Guy calls === bddebian [n=bddebian@pcp08717033pcs.phnixv01.pa.comcast.net] has joined #ubuntu-motu [05:09] Damn, everyone wore out from Breezy?? :-) [05:09] bddebian: yeah, its like some sort of climax [05:13] well, I am still trying to fix my bug >;-( [05:13] Your bug? [05:14] # 3112 [05:14] bddebian: I'm still building packages for it ;- [05:14] ;-) [05:15] Nafallo: Heh [05:15] LaserJock: Oh the one you submitted? :-) [05:15] yeah, you know to get my 0 karma back ;-) [05:16] heh [05:18] apparently I suck at bugfixing >:-( [05:19] Heh, me too and look at my karma ;-P === ajmitch holds that record [05:19] Heya ajmitch === Yagisan [n=jamie@60-240-8-226-nsw-pppoe.tpgi.com.au] has joined #ubuntu-motu [05:20] hello sir [05:20] G'day ajmitch [05:21] bddebian: so you've got universe in shape for dapper release? [05:22] Should be done by tomorrow ;-P [05:22] great [05:22] what, man you are slacking ;-P [05:22] man the MOTU are going to have an easy time of it in dapper [05:22] this round of MoM is going to suck [05:22] Amaranth: aye [05:22] Amaranth: it's going to be fun though [05:22] we should have it done in a couple of weeks :) [05:23] and then the constant re-merging until UVF [05:24] so - that means I should start launching all my security stuff at revu then ajmitch ? [05:24] Ugh, I'm having an argument with someone [05:24] does ubuntu's default kernel have pre-empt and low latency? [05:25] Yagisan: such as? [05:25] Diablo-D3: No [05:25] Suck. [05:25] And I loose the argument. [05:26] ajmitch - sec tools, modified kernels [05:26] Yagisan: sure, might as well start [05:26] best to get as much time in the archive as we can get [05:26] more exposure == more testing [05:27] ajmitch: sure - I asked in #u-k yesterday - they will go with .14 so I base the kernel stuff off that when it's out [05:28] that's what I'd have expected [05:28] ajmitch: so it should be "easier" to keep in sync (I just steal their patches) [05:29] ajmitch - pax has experimental patches for .14 which is nice , and with rsbac you can control which flags are applied [05:29] to different apps - without things like chpax [05:29] how close is .14? [05:30] hm, rc4 [05:30] looks like it'll be there soon [05:30] and ehm, will it build with gcc-4? :-) [05:30] ajmitch - who knows - It'll be done when it's done [05:30] Nafallo: no idea [05:31] anyway, I've got to head away for the weekend [05:31] I might be online, if not I'll see you in a couple of days ;) [05:31] i thought 2.6.12 built with gcc4, it just sucked [05:31] ajmitch: lucky you - I have to do boring admin work this weekend [05:32] Amaranth: last time I checked - not everything in the kernel would build on gcc4 [05:32] that's why it's built with 3.4, actually [05:33] yea, but I was kind of hoping we didn't need the patch every kernel-module-source :-P [05:34] s/the/to/ [05:35] as long as any patches we do apply to mains kernel - they won't get too pissed with different kernels in universe will they ? [05:35] as I recall - they didn't like a .11 kernel in universe [05:35] that wasn't 2.6.11 [05:35] it was a bitkeeper snapshot [05:35] Amaranth: a broken bitkeeper snapshot at that [05:36] but it couldn't be removed and people were using it, that's why they didn't like it [05:37] well, wasn't it fabbione that brought it in? :-) === _maydayjay_ [n=maydayja@ip101109.101.nas.net] has joined #ubuntu-motu [05:37] so, when do we see ubuntu/kfreebsd :) (I see it in universe) [05:38] kfreebsd bah. Hurd baby ;-P [05:38] not before someone will put energy on it atleast... [05:38] Yagisan: there should only be one kernel in the repo at all. [05:39] the kernel in main is and will remain the one kernel to rule them all. [05:39] crimsun: one size does not fit all [05:39] crimsun: ehm, XEN? :-) [05:39] Nafallo: we have separate Xen linux-images in main in Breezy? [05:40] crimsun: it was not done for breezy, so no :-) [05:40] well then. [05:40] or rather, that bounty was deferred. [05:41] not completed in time. [05:41] should be completed for dapper I think though... [05:41] Xen's more of a hypervisor than a kernel. [05:41] I'd say xen is more of it's own OS, then can run linux [05:42] s/then/that [05:42] ehm, still need special kernels, right? [05:42] yes it does - it needs to be the Dom) kernel [05:42] Dom0 [05:42] and you need to build the guest kernels as DomU [05:42] Nafallo: fabbione has that code merged into the source. Whether it's in Breezy is another story. [05:43] you can grep ubuntu-kernel logs for his remarks getting Xen working with linux-source [05:43] a couple months ago? [05:44] (and yes, that bounty is quite sweet) [05:44] well, the bounty owner seems to have made stuff a diffrent way then... [05:44] http://lists.xensource.com/archives/html/xen-users/2005-08/msg00765.html [05:44] doh, I just found my bug wasn't really a bug. Dang it. How do you close a bug on launchpad? [05:45] Nafallo: yes, I know about that. [05:46] it will still be ridiculous to have more than one linux-image [05:47] not sure how you would do anything with Xen if you didn't have a linux-image anyhow [05:48] anyway [05:48] crimsun: why is it ridiculous to have more then one linux-image ? [05:49] local time is 05:48. time to hit bed :-P [05:49] gnight all [05:49] Goodnight Nafallo [05:49] Yagisan: ok, correction. More than one linux-source. [05:50] who can close a bug on launchpad? [05:50] crimsun: I think that for some cases - it is needed [05:50] Yagisan: um...why? [05:50] Yagisan: there're already kernel-patch-foo... [05:51] crimsun: well for starters - my servers would need a linux-source-(a_security_technology_here) [05:51] keep in mind the kernel team would have to support all these different incarnations of linux-source-foo :( [05:51] crimsun [05:51] not for universe [05:52] crimsun: eg I know ajmitch is doing some selinux stuff, I'm looking at pax+rsbac [05:52] Yagisan: why wouldn't {kernel,linux}-a_security_technology_here-patch package be more appropriate? [05:53] crimsun: show me how to integrate that into the automated build system - and I'll give it a try [05:53] do you intend to install using the base linux-image-386, enable universe, install linux-image-a_security_technology_here-$arch, and reboot? [05:54] crimsun: for now yes [05:54]