=== lukjad007 is now known as ShadowChild [00:59] http://paste.ubuntu.com/205915/ [00:59] I'm new at this, how do I get rid of those errors and warnings? [01:03] ethana2, lintian-info --tags $foo [01:03] e.g. lintian-info --tags dh-clean-k-is-deprecated [01:03] will tell you in detail what to do for each lintian error [01:04] I don't think all my errors are lintian errors though [01:04] at least not the fatal ones.. [01:04] how do I make it ignore gpg signing stuff? [01:06] ethana2: pass "-us -uc" to debuild; that's "don't sign the source" and "don't sign the changes", respectively. [01:06] ahhhh [01:06] I had the -us.. [01:06] That'll get rid of the debsign error, by not calling debsign :) [01:06] RAOF: thanks [01:06] * ethana2 does it [01:10] The following packages are BROKEN: [01:10] pbuilder-satisfydepends-dummy [01:11] The interesting error is after that. Pastebin time! === mcasadevall is now known as NCommander [01:19] hmm [01:19] * ethana2 pastebins all of it [01:20] http://paste.ubuntu.com/205930/ [01:21] pbuilder-satisfydepends-dummy: Depends: xautomation which is a virtual package [01:21] pbuilder-satisfydepends-dummy: Depends: xautomation which is a virtual package. [01:22] what's a virtual package? [01:22] one which doesn't exist [01:23] should I just remove it from the project files? [01:23] Most likely you're missing Universe in your pbuilder? [01:23] I don't know.. [01:23] but it is a universe package I guess [01:24] brb [01:35] back === Snova_ is now known as Snova [04:16] How do you remove a package from REVU? I was typing too fast and uploaded to REVU instead of my PPA... [04:17] packages can be archived there if you tell us which one [04:17] kchmviewer-kde3 [04:20] -kde3 ? [04:20] Eeek [04:20] * ajmitch doesn't see it there yet [04:31] ajmitch: strange...it's showing up here: http://revu.ubuntuwire.com/u/kb9vqf [04:31] StevenK: Yup, it's one of those old KDE3 packages, bound for the KDE3 PPA... ;-) [04:33] kb9vqf_: ah, I thought you meant that you'd just uploaded it, and it is archived there [04:33] nuked now [04:33] sorry for the confusion...and thanks! :-) [04:34] BTW I went ahead and uploaded 389 directory server packages to REVU, just in case I can't get it in upstream in time for Karmic [04:35] I saw that [04:36] I tried to implement your earlier suggestions...we'll see if Debian likes them or not [04:36] which ones were they? :) [04:36] ${shlibs:Depends} [04:36] instead of all the individial lib depends [04:37] Needed -0ubuntu1 [04:37] right, that's fairly standard [04:37] -0ubuntu1 is good, but probably not if you're culling all the previous changelog entries [04:37] I thought I read somewhere that you are supposed to cull them? [04:38] * kb9vqf_ doesn't remember where [04:38] I'm not a big fan of rewriting history especially when building on the work of others [04:38] others will disagree with me, I'm sure [04:39] Yeah, it didn't feel right to me either--that's why I kept Michele in the control file as original uploader [04:39] Michele mentioned that he won't be able to work on anything until September, so I guess it's a good thing that I started work on it [04:39] probably, since I doubt I'd have found time to pick it up again [04:42] now you just need to find some friendly reviewers to bribe [04:43] hint: offer beer [04:43] sounds like Hobbsee is thirsty [04:44] it's great when 30k of a 40k diff is just the license text [04:46] :) [04:47] I'm doing a final rebuild test now, just to make sure it all works [04:48] I can at least review the easy ones, which are the various libraries & don't require any setup [04:49] Sure...try svrcore and all the mozilla libs [04:49] Those, along with JSS, haven't changed for the past five years (!) [04:49] In some cases, they're even older... [04:49] yeah, I've still got copies of them around from my work, I remember having to play around with pkg-config [04:52] if you find anything wrong, poke me at kb9vqf_ (*with* the underscore--my laptop screen died from the lightning EMP so I'm on my server for now) [04:52] it's the java packaging that scares me [04:52] ouch [04:53] I take it you got the servers up & running again? [04:53] Yeah, after $1500 worth of new parts [04:53] * kb9vqf_ hopes his insurance will handle it [04:53] One server mainboard, two CPUs, one hard disk, one video card, and various miscillaneous items [04:54] not fun [04:54] 10 days of downtime...priceless :) [04:54] 10 days is a long time for anyone [04:55] No kidding! Fortunately my laptop still worked (flickering, but working) during most of that time [04:55] Hopefully it didn't kill 389 ds in Karmic [04:55] timewise, that is [04:56] how far down did you do the renaming? [04:57] I still see a few .jar files with fedora-ds in the name, looking at the diffs [04:57] It's still the fedora ds tarball, but the packaging is pretty much completely renamed [04:58] That was, I can just plop in the new 389 tarball when it is released and the users shouldn't notice the difference [04:58] so just package names, not binary names? [04:58] Correct [04:58] * ajmitch will have to build it all & try it out [04:58] It really only affects the ds core and the consoles [04:58] I'm building it all here: [04:58] https://launchpad.net/~ubuntu-389-directory-server/+archive/ppa [04:58] the other libraries should be fine [04:58] Should have it all up by tomorrow (hopefully) [04:59] great [04:59] Yeah, someone put together a team, so things should keep moving :) [04:59] lp team? [04:59] Yeah [04:59] https://launchpad.net/~ubuntu-389-directory-server [04:59] Michele is a member [05:00] * ajmitch should join also [05:00] Kai-Cheung Leung really wants to see it in Karmic...he's the one that set the team up and transfered control to me [05:00] ubuntu-directory team hasn't exactly served its intended purpose [05:00] Heh [05:01] it's mostly been a bug contact for packages [05:01] * kb9vqf_ needs to get to bed...early day tomorrow at work [05:01] ubuntu-directory did nothing, and now ubuntu-server has taken over its domain. [05:15] ping mdeslaur [05:15] micahg: yeah? [05:15] I was wondering if it's worth filing a CVE report bug for something that I know will be fixed and released asap [05:20] mdeslaur: ^^ [05:21] micahg: If it's a new issue that has a CVE number and is in main, we usually follow them in our cve tracker [05:21] what cve? [05:22] cve-2009-2210 [05:22] It's still mostly unpublished [05:22] but there is a bug # in the mozilla bugtracker === ApOgEE__ is now known as ApOgEE- [05:29] micahg: that was fixed in thunderbird 2.0.0.22? [05:30] micahg: we just published it http://www.ubuntu.com/usn/usn-782-1 [05:30] micahg: but the particular cve number is not in the advisory as it probably wasn't public when we released [05:31] ah [05:31] I guess I was panicking for nothing :) [05:31] but in general, should I open an issue if it's not fixed yet, but I know it will be [05:35] micahg: you can open a bug if you'd like, you can also take a look at our cve tracker: https://launchpad.net/ubuntu-cve-tracker [05:36] our plan is to eventually automate the opening of bugs when we get new cves in our tracker [05:36] Would the cves be added automatically? [05:37] yes, eventually [05:37] ok [05:37] is there anything I can do now to help? === santiago-pgsql is now known as santiago-ve [05:38] micahg: what type of help are you willing/able to do? [05:39] add them in the mean time for some packages? [05:39] what's needed? [05:39] you could open bugs for CVEs for packages that are in universe [05:40] that way, people would notice which packages need to be fixed [05:40] ok [05:40] I generally watch for mantis and phpmyadmin [05:40] cool [05:41] I'll be opening ones for phpmyadmin later tonight probably [05:41] mdeslaur: how is universe security going? [05:41] eventually, I'd like to help make the patches as well [05:41] micahg: I'll probably do updates for phpmyadmin in my spare time soon [05:41] micahg: that would be cool [05:41] ajmitch: we don't get much community involvement. [05:42] ajmitch: maybe one or two packages a week get some debdiffs submitted [05:42] that's rather low, how can that be improved? [05:43] mdeslaur: how would I use the Ubuntu CVE tracker? [05:44] ajmitch: we had a session about it last UDS...we (the security team) will try and give some irc sessions about it, and some other stuff [05:44] ajmitch: we may also create a "universe package of the week" type of thing to try and get people interested [05:44] micahg: you need to check out the tree with bzr, have you used bzr before? [05:44] ok, I'm guessing it's something you could target to the existing MOTUs & community [05:44] yes [05:45] micahg: if you check out the tree, there's a readme file in there that explains all the tools and the queries you can perform [05:45] basically, in the active directory, there's one file per CVE number [05:45] the retired directory contains CVEs that we fixed [05:46] and the ignored directory are for CVEs we ignore (they're not for us) [05:46] there are some tools in the scripts directory to print out reports for a particular package [05:46] cool [05:47] so you can do something like ./scripts/pkg_status thunderbird [05:47] check out the readme file, it's full of examples [05:47] I need to go to bed now as I'm falling asleep [05:47] ok [05:47] thanks for your help mdeslaur [05:47] np micahg, let me know how it goes [05:49] ajmitch: yes, existing MOTUs...and also we wanted to mention on the "how to become a motu" wiki page that producing some security updates is a good way to become familiar with a bunch of tools [05:52] hi , i want anaconda instead or beside ubuntu installer ? [06:20] ubottu: tell sdeb about motu [06:20] sdeb, please see my private message [06:33] good morning [06:39] Good morning Daniel! [06:40] heya iulian! [06:41] Good morning dholbach ! [06:41] hey fabrice_sp [06:48] hi dholbach [06:49] hiya ajmitch [06:50] dholbach: how was your weekend? [06:51] very good, I even got some of my tax return done! :) [06:51] yay! [06:51] how was yours? [06:51] I even got some sponsoring done, though I don't think I really got much other ubuntu stuff in [06:51] sponsoring! :) [06:51] fairly boring & quiet, in other words :) [06:52] * dholbach takes the dog for a run - see you in a bit [06:52] I have to catch up to your karma somehow! [06:52] hehe [06:52] close to 4k in the last month or two is a good start [07:00] karmic is the 9.10 ? [07:00] !karmic [07:00] Karmic Koala is the codename for Ubuntu 9.10, due October 2009 - Karmic WILL break - Discussion and support in #ubuntu+1 [07:13] good morning [07:13] hi geser [07:13] Hello geser. === \sh_ is now known as \sh [08:15] <\sh> moins [08:17] hi \sh [08:17] Hi \sh [08:48] is revu working ok? [08:49] submitted a new version of a package and didnt hear anything... [08:54] package name? [08:56] stefanlsd: if you could give me any more info, it'd be appreciated :) [08:57] ajmitch: http://revu.ubuntuwire.com/p/gears [08:58] ok, for some reason it didn't like your signature on the last upload [08:59] ajmitch: oh did update my key a couple weeks ago on LP? maybe revu hasnt pulled the new one? [08:59] it hasn't [08:59] ajmitch: ok. anything i need to do? [09:00] let me check the current procedures for updating keys :) [09:00] Log in, IIRC. [09:01] wgrant: does that pull in updated keys & not merely new ones? [09:01] am logged in, let me try relog [09:01] ajmitch: No idea. [09:01] worth a try anyway [09:01] the keyring is dated may 16, which seems to be too long ago [09:02] ajmitch: ok. re-logged in. anything change? [09:03] nope [09:03] I can try & do a manual update [09:03] ajmitch: Sure that's the right keyring? [09:03] it appeared to be [09:04] no, you're right [09:04] uploaders.gpg vs data/uploaders.gpg [09:04] just to confuse me [09:05] stefanlsd: hopefully gears will get accepted on the next try [09:06] ajmitch: 7A66BA46 should of been the key i signed with and my current key you should have in revu. will try again :) [09:06] stefanlsd: it appeared to have worked now [09:06] ajmitch: aah. yeah. just got a notification :) [09:06] good [09:10] ajmitch: thanks for the help! [09:12] no problem :) === sonicmctails is now known as mcasadvall [10:33] Laney: hi, news on new ghc version? [10:38] gaspa: no, but you can reply to that bug and ask Simon for an update if you like [10:38] of course, which bug? [10:39] bug 382803 [10:39] Launchpad bug 382803 in ghc6 "fix random segfaults when using ForeignPtr" [Medium,Triaged] https://launchpad.net/bugs/382803 [10:39] it would probably be better to email him directly though rather than spamming LP I guess [10:39] yup [10:40] you could CC kaol@debian and ask if he's going to update when it releases too [10:41] if it's more than a couple of weeks longer we should consider staying with .3 and that patch [10:42] Laney: uh, late.... well, i'll do if he will reply. [10:42] thanks, anyway. [10:42] well there's still a long time to go until FF [10:42] no worries [10:43] geser: I wont ask you any more give-back, are you happy ? :D [10:49] gaspa: please cc me if you haven't sent it yet [11:13] Laney: he already replied: "Will discuss with the development team today." [11:13] oh, speedy [11:13] really. :P [11:14] <\sh> thekorn: ping -> #leonov pls :) [11:28] Hello, it seems that the -ubuntu2 release of sl-modem is one of causes of this bug LP 375148 [11:28] Launchpad bug 375148 in sl-modem "no more /dev/ttySL0 device node" [Medium,Confirmed] https://launchpad.net/bugs/375148 [11:28] in that release Ubuntu removed a modprobe conf file that creates a static device (mknod /dev/slamr0) [11:29] I understand that creating static devices is not allowed in Ubuntu [11:29] but the problem is that sl-modem code doesn't dynamically create devices [11:30] and it isn't really maintained upstream (they just accept patches) [11:30] and I understand from them that sl-modem code shouldn't use udev because of license problems [11:30] anyone can suggest a solution for this mess ?! [11:31] who could imagine running a session about "simple packaging from scratch" (maybe dh7?) at UDW? https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep [11:31] I'd really appreciate if somebody stepped up to do it :) [11:31] dholbach: is this dh7 trying to be CDBS like ? [11:32] dholbach: I saw a rules file using dh7 , they just do dh_* something like that [11:32] AnAnt, except overriding dh7 requires 87% fewer chicken sacrifices [11:32] directhex: huh ? what's chicken sacrifices ? [11:32] when is UDW? [11:32] * Laney should just click the link [11:32] AnAnt: you will find that in a lot of cases /usr/share/doc/debhelper/examples/rules.tiny will do what you want and you'll just need something like /usr/share/doc/debhelper/examples/rules.simple [11:33] Laney: https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep Aug 31st to Sep 4th [11:33] AnAnt: but CDBS will cut the deal too :) [11:34] I'll do it [11:34] packaging hello with dh7 [11:34] ;) [11:34] * dholbach hugs Laney [11:34] you're a hero [11:34] man I don't feel comfortable with this ! [11:34] Laney: you get to pick a slot :-) [11:34] it's like you dunno what's going on [11:35] dholbach: is there going to be a session about setting up pbuilder and such like? [11:35] AnAnt, turn on DH_VERBOSE to watch it - and everything it's doing can be trivially overridden [11:36] Laney: I'll do it in GETTING STARTED [11:36] ok [11:37] dholbach: after that then? [11:37] also, I just looked at the rules file for hello. Does this predate debhelper? [11:37] Laney: as you like it - first come, first pick the slot :) [11:37] ok, 1800 on the first day then [11:37] Laney: there#s hello and hello-debhelper [11:37] Laney: shall I add you then? [11:38] please do [11:38] will do :-) [11:38] ah, this is more like it [11:38] hello-dh7 [11:39] dholbach: can any Ubuntu derivative be added to https://wiki.ubuntu.com/Releases ? I see unofficial variants there [11:39] AnAnt: just do it - I see no reason for you not to and don't know if there's anybody "maintaining the page" [11:40] dholbach: well, karmic is mentioned there, so there is someone maintaining it I think [11:41] sure, just do it === menesis1 is now known as menesis [12:32] dholbach: ping [12:32] mok0: pong [12:32] dholbach: hey, you are a launchpad hacker, right? [12:32] errrrrrrrrrrrrrrrrrrrrrrrrr [12:33] The sponsor queue is full of entries from Debian, that really can't be sponsored by us. Is is possible to make a script to automatically unsub from those? [12:34] try https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors and https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors :-) [12:35] dholbach: huh? [12:35] mok0: it just lists Ubuntu bugs [12:36] dholbach: ah now I see... :-) I was looking to unsub to clean up the list [12:37] mok0: the parts of the LP API for unsubscribing teams from bugs is very new so I haven't used those parts yet [12:37] dholbach: OK, I understand. [12:37] dholbach: I also want to consult with you re. bazaar [12:38] dholbach: if you have time [12:38] mok0: sure [12:39] dholbach: OK, so if you look at sahana sources at sf.net it is divided into several CVS "components" [12:39] mok0: did you want to package it from CVS? [12:40] dholbach: no I want to import it to LP, like you have done with the civic thing [12:40] oh, that's something that asomething did [12:40] dholbach: just wondering if it needs 3 different imports [12:40] hm, good question - maybe we need one sahana super project and subprojects for the others? [12:41] dunno if that's too complicated though [12:41] dholbach: how do you manage merging the ubuntu and trunk branches? [12:41] mok0: not at all :-/ [12:41] they don't share history [12:41] dholbach: I see the ubuntu branch only has debian/ [12:41] we just stored the packaging in the branch [12:41] yeah [12:42] bzr bd -- -S -us -uc will use the watch file to build a source package for you [12:42] (bzr-builddeb) [12:42] dholbach: Hm, isn't it supposed to be real smart so you can merge the packaging with an updated upstream clone? [12:43] dholbach: like, the dailydeb thing? [12:43] dholbach: using the watch file kinda defeats the purpose of having upstream sources mirrored in LP [12:44] mok0: I know, I'd love to see us use full-source-from-vcs instead of tarballs :-) [12:44] ask james_w about it :) [12:45] dholbach: ok, I will... I tacitly assumed you were doing it like that [12:45] dholbach: thanks for your time! [12:46] dholbach: I will see what I can find out and let you know [12:46] mok0: asomething started the branch and since he was tracking the stable tarball of civicrm, I thought "ok, let's just do it like that" [12:46] there's funny things like autogen.sh though [12:47] Laney: is that a comment re: this discussion? [12:47] mok0: I'll spruce up the wiki page about it some more, so we can see which parts of the ./packages/ we need to package in the long run [12:47] mok0: yes [12:47] Laney: ah ok :-) [12:47] so it's not as easy as pulling the vcs history [12:47] http://daniel.holba.ch/blog/?p=311 is my thoughts about it :) [12:47] Laney: the autogenerated files ought not to be part of the repo [12:48] Laney: I mean the VCS [12:48] mok0: WORD! [12:48] dholbach: thanx [12:48] mok0: they aren't, but they are part of the tarball [12:48] that's the problem [12:48] Laney: right... [12:49] Laney: when you build from the VCS you should always do autoreconf [12:49] yes [12:49] it makes it an extra step which means that we differ from what upstream releases [12:50] Laney: I go through a great deal of trouble keeping the autogen stuff out of my VCS managed stuff [12:50] as you should [12:50] Laney: I think from a packaging perspective, the correct thing is to ignore it if it's present [12:51] Laney: but there are mountains of stuff like that when you start using VCS'es for packaging [12:52] mok0: Hey. Have you installed cadabra (from revu) to see if it works? I'd like to upload it, if that's OK with you but not before I see it working. Unfortunately, I don't have a Karmic box to test packages. :-( [12:52] iulian: no I haven't... I haven't had the time [12:53] Ouh [12:53] iulian: neither do I... could it be run inside a chroot? [12:54] mok0: Yea, but I don't have one with X installed. [12:54] iulian: I didn't try compiling it for jaunty [12:55] iulian: but I suppose it can be done [12:55] Yup [12:56] * iulian prefers and up-to-date Karmic system. [12:56] s/and/an/ [12:58] Well, I'll see what I can do. I believe it works but I just want to be sure. [12:58] Thanks mok0. [13:00] iulian: for a user-land application like cadabra release shouldn't really matter [13:01] iulian: it requires a library "modglue" but that made it into jaunty :-) [13:01] cadabra didn't cut the FF otherwise it would have been there too [13:02] Heh, cool. I didn't know that. [13:02] OK, so, should I upload? [13:02] iulian: if you think the package is ok, yeah [13:02] Great. [13:03] iulian: If there are bugs in it, we'll find out soon enough :-P === lex79 is now known as lex === lex is now known as lex79 [13:05] mok0: I've reviewed it this morning as well. Having said that, I hope I haven't missed anything, but yeah, like you said, we'll find out soon. [13:06] iulian: Great. I hope to start some revu'ing soon [13:07] iulian: karmic is requiring more work than usual due to the gcc44 toolchain [13:07] iulian: I've been fixing lots of FTBFS'es this time === WelshDragon is now known as YDdraigGoch [13:15] mok0: Cool. I'll have a look at some FTBFS when I have some spare time. I have been a bit busy lately so I have been falling behind a bit on the Ubuntu front. :( [13:16] iulian: you can only do as much as you can [13:17] dholbach: nice read, holy cows! [13:17] mok0: most of my ideas around it haven't changed :) [13:18] dholbach: I'm using git for my packaging, locally, and the workflow is quite effective. [13:19] dholbach: I'd like to try out bzr, but it doesn't seem to give me the same options [13:19] dholbach: the "a branch is a directory" paradigm rubs against me [13:20] really? :) [13:20] dholbach: yes, really :-) [13:20] "bzr branch trunk my-new-feature" became really intuitive for me already [13:20] dholbach: ... and you have parallel directories? [13:21] yes [13:22] dholbach: I don't like it [13:22] dholbach: In git, the directory is just a container of your branch [13:22] dholbach: when you switch to another branch, the content of the directory changes [13:23] dholbach: (except for files not under control) [13:23] dholbach: which means you have all your branches right there in the same directory [13:23] I'm not saying "there's only my way and everybody else is just nuts", but as branching for me is relatively cheap, I do it whenever I feel like it and do all operations only on the branch I'm working on right now... the "bzr pull ../other-branch" afterwards is easy enough too [13:24] dholbach: it's probably just my ignorance, but it seems bzr is always getting in the way of what I want to do [13:26] dholbach: and the extra commit you need to do after pulling trunk's changes drives me crazy :-) [13:26] I don't get that feeling :) [13:26] hu? [13:26] bzr pull doesn't give you uncommitted changes [13:26] dholbach: oh? [13:27] bzr merge does though [13:27] right [13:27] dholbach: afair I always have to do a commit when I update my branch with trunk's changes [13:27] Hm, perhaps that's it [13:28] In git, you can only do a merge when your branch is committed, but then it commits everything for you again [13:29] Anyway, I would like to learn how to be productive using bzr [13:29] mok0: I've been using git for a week or so now, I find it cooler than bzr indeed [13:29] mok0: so I should chase somebody up to give a UDW session about it? :) [13:30] mok0: cadabra has just been uploaded to NEW. [13:30] dholbach: that's a great idea! [13:30] dholbach: btw, I can repeat my session [13:31] mok0: that'd be sweet [13:31] iulian: great! Thanks! [13:31] mok0: you can still just grab a slot https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep :-) [13:31] dholbach: it was fun, there was a good crowd there [13:31] fantastic [13:33] iulian: i've been wanting to ask this - did you forward the message to the ubuntu-motu list, or is that an automated thing? [13:35] Wiki button "Save Changes" should be changed to "I'm felling lucky!" [13:35] OT, is there some easy way to know how much traffic I use on a network interface? [13:36] RainCT, iptraf ? [13:36]