[00:00] <imbrandon> 6 more hours untill i'm officialy 29 :P woot
[00:00] <TheMuso> lol
[00:00] <imbrandon> ( localtime )
[00:01] <imbrandon> been sitting here playing with my new bday toys ( a 5.1mp digital camera via my mom and a usb card reader from my kido's )
[00:01] <imbrandon> :)
[00:01] <cyberix> 127.0.0.1:123
[00:02] <jas01> can't use woot anymore... it's mainstream :(
[00:02] <jas01> whoot! happy bday!
[00:03] <imbrandon> heh
[00:03] <zul> imbrandon: young'un
[00:04] <Flare183> !nvida
[00:04] <Flare183> sorry wrong channel
[00:06] <ubotu> Sorry, I don't know anything about nvida - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[00:07] <slangasek> cyberix: February 14 is too late, yes. :)
[00:41] <mtaylor> anybody happen to know the difference between ${Source-Version} ${source:Version} and ${binary:Version}? cause lintian tells me to use binary:Version, but I can't find docs about the different var ANYWHERE
[00:42] <slangasek> mtaylor: ${Source-Version} is deprecated because the name is misleading. ${binary:Version} is what it says; in Ubuntu it's always the same as ${source:Version}, but for Debian compatibility the difference is that ${binary:Version} changes when there's a binNMU and ${source:Version} always refers to the original source version
[00:42] <slangasek> the distinction is relevant for dependencies between arch: all and arch: any packages, since arch: all packages aren't rebuilt in a binNMU
[00:42] <mtaylor> slangasek: AWESOME
[00:44] <mtaylor> slangasek: you don't happen to know where that's doc'd do you... I looked through the policy and tried googling...
[00:45] <slangasek> good question, I have the unfortunate habit of usually being there when the policies are being drafted so never have occasion to look for documentation :/
[00:45] <slangasek> (well, or non-policies in this case, since it's not really in policy)
[00:45] <mtaylor> hm. sounds like it should be in policy...
[00:45] <mtaylor> since it is a lintian rule, after all
[00:46] <Fujitsu> Bah, slangasek beat me to it my almost a minute :(
[00:46] <Fujitsu> s/my/by/
[00:46] <slangasek> the current Debian policy czars seem to think very little should be written into policy. :)
[00:46] <mtaylor> I wasn't going to tell you
[00:46] <mtaylor> gr
[00:47]  * mtaylor thinks the detailed policy is one of debian's strong points
[00:47] <slangasek> at minimum, it ought to be in the developer's reference, and it's not there either
[00:47] <Fujitsu> One would think it should be.
[00:48] <mtaylor> I would think there shouldn't be a lintian rule warning me about anything if there isn't a policy to back it up
[00:48] <mtaylor> else what the hell is lintian anyway ?
[00:48] <mtaylor> but then, I suppose I'm odd perhaps
[00:48] <Fujitsu> It is policy, it's just not in the policy document.
[00:48] <mtaylor> hehehe
[00:48] <mtaylor> NICE
[00:49]  * mtaylor feels like he'll possibly be tried in a secret court for violating a secret law now...
[00:52] <slangasek> oh, well, lintian is a tool that mechanically checks for bugs, and it correctly identifies some uses of ${foo:Version} as buggy; unfortunately, there's a stream of thought that if it's self-evidently a cause of bugs, it doesn't need to be written in Policy :-P
[00:52] <slangasek> (but then it should be in the devref, where it also isn't, and the devref isn't maintained via debian-policy, so....)
[00:52] <mtaylor> ah... I follow
[00:52] <slangasek> long story short, you have a valid complaint, and you've touched a nerve with me :-)
[00:53] <mtaylor> YAY!
[00:54]  * mtaylor has done his job for the night then
[01:20]  * persia wonders if there is any sane way to handle bug #177360 (say, something like Debian bug #415287)
[01:20] <ubotu> Launchpad bug 177360 in ion3 "ion3 in Gutsy doesn't follow author's License" [High,New] https://launchpad.net/bugs/177360
[01:20] <ubotu> Debian bug 415287 in ion3 "dummy bug; should not be in testing" [Serious,Open] http://bugs.debian.org/415287
[01:22] <StevenK> Nnnnnnggg
[01:23] <StevenK> I don't think we can remove packages from Gutsy.
[01:23] <persia> Well, we can, but we won't.  I was more interested in not including it in hardy unless there was an actual stable release.
[01:23] <slangasek> in the interest of preserving sanity, cyanide pills are available in the pouch in front of you
[01:24] <StevenK> Muaha
[01:24] <StevenK> Preserving nothing still leaves nothing
[01:24] <persia> slangasek: I'm not interested in sanity, but only archive integrity (and understand these are incompatible).  Any other suggestions?
[01:24] <StevenK> Hah
[01:25] <slangasek> so are you asking for a way to mark a package in hardy as "not for release"?
[01:25] <StevenK> Can we even do that?
[01:25] <slangasek> no
[01:25] <slangasek> but I'm asking if that's what he's asking for :)
[01:25] <persia> slangasek: That would be one way to do it.  An alternate would be to pull from hardy in such a way as to resync for hardy+1.
[01:25] <slangasek> right, kicking the package out of the dist is the only method that's consistent with the current model
[01:26] <persia> slangasek: There's actually a bug outstanding for each of those requests.  I'm just not sure which of the many workarounds is currently preferred.
[01:28] <slangasek> persia: I think it's reasonable to kick the package out under those circumstances; while Debian unstable is something that users run long-term for its own sake, Ubuntu's "development" dist is pretty explicitly a staging ground for the next release
[01:29] <slangasek> so not a place to carry stuff that shouldn't be in a release at all due to licensing reasons
[01:30]  * Hobbsee waves
[01:30]  * slangasek waves
[01:39] <persia> slangasek: Thanks.  I'll retitle & subscribe the archive admins.
[02:15] <bddebian> Heya gang
[02:15] <persia> Good evening :)
[02:15] <bddebian> Hi persia
[02:18]  * imbrandon waves to all
[02:19] <bddebian> Heya imbrandon
[02:19] <imbrandon> heya bddebian
[02:36] <joejaxx> lol
[02:36] <joejaxx> my firefox is taking up 375mb of ram :D
[02:36]  * joejaxx is an internet power user :D
[02:37] <StevenK> I had Transmission taking up 1.4Gb before I closed it
[02:37]  * Fujitsu 's Epiphany is eating 120, but X is rather suspiciously eating 250.
[02:37] <joejaxx> joejaxx    834 53.9 36.3 633152 375944 ?       Rl   Dec17 718:08 /usr/lib/firefox/firefox-bin
[02:37] <joejaxx> lol
[02:38] <StevenK> Fujitsu: That 250 is probably mostly textures
[02:38] <Fujitsu> StevenK: Gecko textures, yes.
[02:38] <joejaxx> StevenK: 1.4gb lol :P
[02:38] <Fujitsu> And if Gecko crashes, they don't get freed until X is restarted.
[02:39]  * persia cheers gecko, and points at midori for those who don't agree
[03:08] <Hobbsee> slangasek: that LP bug got fixed.  i could still delete before, as deletions don't generate mail anyway, FYI
[03:10]  * Fujitsu thinks <release>-changes should probably be renamed to <release>-selected-manual-uploads-if-LP-feels-up-to-it
[03:10] <persia> heh
[03:10] <Hobbsee> hehe
[03:10] <bddebian> heh
[03:10] <Fujitsu> It doesn't track -updates migrations, deletions, autosyncs...
[03:10] <Fujitsu> Security notifications are meant to return in 20 minutes, but somebody stuffed up the announcement...
[03:11] <Fujitsu> s/20 minutes/40 minutes ago/
[03:17] <slangasek> Hobbsee: ah, ok
[03:19] <Hobbsee> slangasek: i can accept and reject packages.  that's about it
[03:20]  * slangasek nods
[03:22] <Hobbsee> and i have to poke one of you to work around YALPB whenever i accept a package, too
[03:22] <Hobbsee> which triggers YALPB#2 if done in a particular timeframe.
[03:24] <Fujitsu> The main default?
[03:25] <Fujitsu> And associated upload failure?
[03:27] <Hobbsee> yes
[03:47] <TheMuso> Interesting. http://www.linuxtoday.com/infrastructure/2007121901026NWDTRL
[03:51] <LucidFox> Bah.
[03:51] <LucidFox> If they use proprietary software to do that, this will be exactly what Stallman feared.
[03:53] <dadehoog> yeah, that's really a compromise which ends any hope of open formats for DVDs/media
[03:58] <superm1> hey folks, if anyone is feeling up for a revu: http://revu.tauware.de/details.py?package=ical2sqlite
[03:58] <bluefoxicy> awesome
[03:58] <bluefoxicy> I got random e-mail
[03:59] <bluefoxicy> through extensive googling, some guy writing a paper has determined I am the person most familiar with Ubuntu Linux's security posture
[03:59] <bluefoxicy> What the hell gave him that impression?
[03:59] <bluefoxicy> Oh well, everything he lists is stuff I'm familiar with so okay.
[03:59] <Fujitsu> You've written all the security specs.
[03:59] <bluefoxicy> rofl
[03:59] <bluefoxicy> PITTI is probably most familiar with Ubuntu's security posture
[04:00] <bluefoxicy> or Kees Cook
[04:09] <verb3k> LucidFox,  Hi, See this:    http://psxim.googlecode.com/    :)
[04:10] <verb3k> LucidFox, what do you think? is there anything missing?
[04:11] <bderrly_> so i want to update the libtorrent/rtorrent packages in gutsy, i see they are maintained by MOTU but they haven't been updated in a long time. is there someone that could go through the process with me so i can get the hang of packaging?
[04:11] <bderrly_> i've read through several of the packaging docs on the wiki, etc but there are so many different ways of doing that i'm a bit confused about the best way to tackle a package
[04:12] <persia> bderrly_: The best way to update a package is to keep the same packaging style.
[04:13] <bderrly_> makes sense
[04:15]  * Fujitsu saw something on Planet Debian recently about those new versions.
[04:16] <bderrly_> Fujitsu, yah, i talked with the guy that packages them for debian, but i want to get them in ubuntu
[04:16] <bderrly_> no one has updated those packages for ubuntu since april i htink
[04:16] <bderrly_> even though debian has updated several times since then
[04:16] <Fujitsu> Those actions are largely the same.
[04:16] <Fujitsu> !info rtorrent hardy
[04:16] <ubotu> rtorrent: ncurses BitTorrent client based on LibTorrent. In component universe, is extra. Version 0.7.8-1 (hardy), package size 351 kB, installed size 948 kB
[04:17] <Fujitsu> We take almost all of our package from Debian.
[04:18] <bderrly_> but who does that and when?
[04:18] <verb3k> Fujitsu, are you a motu?
[04:18] <Fujitsu> I am.
[04:18] <persia> bderrly_: The set of all package contributors for packages with ubuntu versions, and the automated script run by the archive-admins at the beginning of each development cycle.
[04:19] <Fujitsu> bderrly_: It is largely automatic until last week.
[04:19] <verb3k> Fujitsu, I need a favor, I have written a python and it now needs packaging and you know that's not easy, could you make the deb for me? the program's home is here:  http://psxim.googlecode.com/
[04:20] <verb3k> Fujitsu,  a python program*
[04:20] <verb3k> Fujitsu, it's only one file
[04:20]  * Fujitsu notes that there are more capable MOTU around, that he doesn't like writing new packages, and that he is a little busy at the moment.
[04:20] <persia> verb3k: As I told you before, if you want someone else to package it, you should file a needs-packaging bug.  If you don't want it in universe, this isn't the right place to ask.
[04:21] <verb3k> persia, didn't know that packaging is so hard like that :)
[04:21] <nxvl> hi folks
[04:22] <bderrly_> Fujitsu, so how do i get these packages updated in gutsy?
[04:22] <Fujitsu> bderrly_: We're not Gentoo. YOu could try backports, though.
[04:22] <Fujitsu> !backports | bderrly_
[04:22] <ubotu> bderrly_: If new updated Ubuntu packages are built for an application, then they go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[04:23] <cheguevara> bderrly_, you may wanna work on getting them updated for hardy
[04:23]  * Fujitsu wonders if s/they go/they can go/ might be a good idea.
[04:23]  * persia seconds Fujitsu
[04:23] <persia> Err.  Or maybe "may"?
[04:24] <Fujitsu> I think either should be acceptable.
[04:24] <Fujitsu> You have bot powers now, don't you?
[04:26] <persia> Fujitsu: I may be an editor, but that's like saying I'm licensed to fly intergalactic craft: it doesn't help me actually do anything.
[04:26] <persia> (the distinction being I could probably read something in the former case, but don't know what)
[04:27]  * Fujitsu isn't sure of the command to run regexps over a factoid, but does know how to set them.
[04:27] <pwnguin> verb3k: i think 23 minutes after release is a bit early to be asking for a package
[04:28] <persia> Fujitsu: My problem is that ubotu doesn't believe I'm me.  Trying to convince it I'm real again now.  If this works, maybe I can do something.  If not, we can submit to the moderation queue.
[04:28] <persia> pwnguin: The release was only to support packaging.
[04:28] <pwnguin> interesting
[04:28] <Fujitsu> Ah.
[04:28] <Hobbsee> what's the bot problem?
[04:29] <persia> Hobbsee: I don't know how to wrangle, and !backports needs an extra "can" or "may".
[04:29]  * persia is trying to learn now...
[04:29] <Hobbsee> ubotu: backports is ~s/they go/they can go/
[04:29] <ubotu> But backports already means something else!
[04:29] <Hobbsee> !no backports is <reply> If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[04:29] <ubotu> I'll remember that Hobbsee
[04:30] <Fujitsu> Danke.
[04:30] <Hobbsee> i dont' remember the regexpisms.
[04:30] <verb3k> pwnguin, It was released long ago and tested , I just made a hoepage for the project becasue a MOTU said do that before you buidl your package
[04:30] <Hobbsee> i think there's documentation on it somewhere, though
[04:30] <persia> What is "!no"?
[04:30] <verb3k> build*
[04:31] <Fujitsu> persia: Overwriting an existing factoid.
[04:31] <persia> Ah.
[04:31] <Fujitsu> One would normally do `!newfactoid is whatever', but that will fail if it exists, as Hobbsee adeptly demonstrated.
[04:31] <verb3k> pwnguin, besides, I am not asking for universe inclusion, I am just trying to get help from packagers
[04:32] <Fujitsu> I don't think you're likely to find packages here if it's not for universe.
[04:32] <persia> heh.  I learned enough to discover that I'm not a licensed bot wrangler.  Now I can stop worrying and go back to pestering others :)  Thanks Hobbsee (as always)
[04:32] <Hobbsee> hehe
[04:33] <pwnguin> verb3k: why not?
[04:34] <pwnguin> if it has a package, and is tested etc
[04:34] <pwnguin> verb3k: it might as well be in universe
[04:35]  * persia notes it would likely be multiverse anyway
[04:35] <verb3k> pwnguin, Does the universe follow some rules for inclusion regarding quality? (like the debian stable)
[04:35] <bderrly_> wow, the upgrade to hardy is pretty large
[04:35] <bderrly_> 651MB
[04:35] <bderrly_> 920 packages upgraded
[04:35] <Fujitsu> That's quite small.
[04:35] <persia> bderrly_: It's just getting started...
[04:36] <pwnguin> verb3k: different rules
[04:36] <TheMuso> 000/c
[04:36] <TheMuso> ugh
[04:36] <bderrly_> guess i had better get it now then ;)
[04:36] <pwnguin> verb3k: if you, as the upstream author, are not prepared to accept bug reports from users, its probably not a good idea
[04:37] <verb3k> pwnguin, I would like to solve bugs in my program, that's good practice
[04:37] <verb3k> pwnguin, google code has a decent tracker
[04:37] <pwnguin> persia: i dont see why it'd go in multiverse if the code's free and doesnt depend on nonfree
[04:37] <pwnguin> verb3k: as does launchpad ;)
[04:37] <pwnguin> does lp track google code yet?
[04:38] <Fujitsu> That would be a no. Bug #78395.
[04:38] <ubotu> Launchpad bug 78395 in malone "Support Google Code's issue tracker" [Undecided,In progress] https://launchpad.net/bugs/78395
[04:38] <pwnguin> anyways, its fine if you use google
[04:39] <pwnguin> not upstreams problem if it doesnt
[04:39] <verb3k> pwnguin, I may switch to launchpad, I make up my mind later
[04:39] <pwnguin> verb3k: ideally, you'd get it into ubuntu and debian unstable at least
[04:40] <verb3k> pwnguin, good, have you seen the code? do you think it can stand on its feet?
[04:40] <pwnguin> im looking at the google code svn
[04:40] <pwnguin> its empty
[04:40] <verb3k> pwnguin, yes XD , I just put the tarball
[04:40] <verb3k> pwnguin, downloads
[04:41] <pwnguin> check it into cvs/svn/bzr at least, so distros can track commits for patches
[04:41] <verb3k> pwnguin, will do
[04:41] <persia> pwnguin: I thought it was a firmware manager for a non-free emulator.  Shouldn't that depend on the emulator, making it multiverse?
[04:42] <pwnguin> from what i can tell
[04:42] <pwnguin> it rips cds
[04:43] <pwnguin> we have tools to rip music to disk
[04:43] <verb3k> persia, that's true, you do NOT need to play it in an emulator, you can just back it up for later burning
[04:43] <persia> My misunderstanding.  I thought it packed into the right format for a PSX emulator.  It's certainly free for real hardware.
[04:44] <pwnguin> again, oggenc isnt in multiverse, nor is sound juicer
[04:45] <pwnguin> verb3k: unfortunately, im not in MOTU, and not at all familiar with psx emulation or python
[04:45] <persia> pwnguin: Right.  I misunderstood.  If I were packaging a ROM manager for MAME, I'd rather be multiverse and depend on a MAME than be universe.  On the other hand, PS X hardware is more common than arcade cabinets.
[04:46] <pwnguin> im not sure why rarity matters
[04:46] <pwnguin> psx hardware is commonly modded to play backups
[04:46] <verb3k> the original psx didn't need modchips to play backups
[04:46] <pwnguin> shennanigans
[04:47] <verb3k> maybe later versions yes
[04:47] <persia> pwnguin: One sets Recommends & Suggests based on the common case.  Universe Recommending Multiverse is frowned upon.  If the common case is real hardware, than Suggests: is correct.  If the common case is emulators, Recommends: is correct.
[04:47] <pwnguin> unless you're referring to the console port in the back
[04:47]  * Fujitsu wonders what this PS X is. Is it some generation of the Sony PlayStation that I've never heard of?
[04:47] <persia> Fujitsu: Yes.
[04:48] <pwnguin> its the old term for the playstation one
[04:48] <Fujitsu> Ah.
[04:48] <pwnguin> apparently there was some playstation hardware running simply as a drive to the snes
[04:48] <pwnguin> that got scrapped and they called the new project psx internally, i guess
[04:49] <verb3k> Initially, sony wasn't planning to enter gaming business  http://en.wikipedia.org/wiki/PlayStation
[04:49] <persia> verb3k: You should really put your code repo up...
[04:50] <pwnguin> assuming one ever existed
[04:50] <pwnguin> it would be nice to import that into the public repo on google code
[04:50] <verb3k> it's a fresh account
[04:50] <pwnguin> indeed
[04:50] <pwnguin> but it should be able to import histories
[04:52] <pwnguin> verb3k: about how many users do you think you have currently?
[04:53] <verb3k> pwnguin, I don't know , didn't release it for the gaming community yet
[04:53] <verb3k> many developers saw it
[04:53] <verb3k> but not many gamers
[04:55] <verb3k> one thing I find very daunting in programming, is the amount of knowledge you should have to complete a single task.....that's very good but requires a lot of time, dedication, and lots of reading
[04:55] <pwnguin> depends on the task
[04:55] <verb3k> and lots of research
[04:56] <pwnguin> but basically, yea, preparing is better than diving in head first
[04:58] <verb3k> I am trying to find problems that interest me to solve them with python, this psxim tool initially was a bash script I did for myself only, then thought about sharing it, and then making a GUI etc.....chains of ideas :)
[05:00] <pwnguin> is it possible to detect which drives have a psx disc in them?
[05:00] <verb3k> pwnguin, I thought about that but didn't really search or ask
[05:01] <verb3k> I think it's achievable
[05:03] <pwnguin> not a requirement, but it might make it slightly more substantial
[05:03] <verb3k> true
[05:03] <pwnguin> alternatively, it might mean you could write a nautilus script
[05:04] <pwnguin> well, i just broke another chair
[05:04] <pwnguin> guess i need to go to walmart
[05:04] <Fujitsu> ...
[05:05] <pwnguin> verb3k: later; if nobody wants to put it directly into universe or debian unstable, you might see if a "packaging jam" is being held locally
[05:06] <verb3k> what's that?
[05:07] <pwnguin> verb3k: a LoCo training session
[05:07] <pwnguin> for packaging
[05:07] <verb3k> my loco is shattered
[05:07] <pwnguin> but jono cant possibly use normal words, being a british
[05:07] <verb3k> 5 or so people and then can't find them anymore
[05:09] <verb3k> In fact, LUGs are more common than LoCos
[05:10] <pwnguin> yea
[05:11] <pwnguin> locos in the US feel a bit silly
[05:13] <verb3k> the local community needs join forces instead of splitting in smaller groups( you know gentoo guys, ubuntu guys and suse guys)
[05:13] <verb3k> to*
[05:23] <pwnguin> well, its nice to have resources available to ask "how do i do x" in cases where it varies between gentoo, ububntu etc
[05:30] <tritium> verb3k: I don't find LoCos in the U.S. silly
[05:31] <verb3k> I didn't say that LOL :)
[05:31] <tritium> Ah, that was pwnguin, sorry ;)
[05:32] <TheMuso> Yay for a package having an MD5/size mismatch causing debmirror to fail. :)
[05:32] <verb3k> pwnguin, that's true but nor for all countries, there are countries where you barely find a Linux user
[05:33] <verb3k> pwnguin, not*
[05:33] <Fujitsu> TheMuso: Broken mirror?
[05:33] <TheMuso> Fujitsu: No, the problem is on auc as well.
[05:33] <Fujitsu> Ah, that bug.
[05:34] <TheMuso> Fujitsu: Oh its known?
[05:34]  * TheMuso shouldn't be surprised.
[05:34] <TheMuso> But is
[05:34] <Fujitsu> Yes. I'll find it.
[05:34] <TheMuso> np
[05:34] <Fujitsu> Bug #174038
[05:35] <ubotu> Launchpad bug 174038 in soyuz "bad md5sum in Packages file" [Undecided,Triaged] https://launchpad.net/bugs/174038
[05:35] <TheMuso> Fujitsu: You really seem to be quite up on soyuz shortcomings.
[05:36]  * Fujitsu ends up reading most Soyuz/Malone bugs.
[05:36] <Hobbsee> TheMuso: he does a lot of soyuz support.  crazy guy
[05:36] <Fujitsu> Hah.
[05:36] <TheMuso> heh
[05:37]  * persia wonders if the 1.12 rollout was successful, and if it fixed the bug that annoyed me.
[05:37] <Fujitsu> The announcement was wrong.
[05:38] <ScottK> Fujitsu: Incorrect, evil, or both?
[05:38] <persia> Ah.  Then no, and no, and more so, not good questions anyway.  Thanks.
[05:38] <Fujitsu> It apparently wasn't attempted. The date was probably listed incorrectly.
[05:39] <persia> Maybe they are using the 49-hour international day, and it's still pending RSN.
[05:40] <Fujitsu> It says UTC, and I haven't seen any other announcements about it happening, whereas there are usually emails.
[05:41] <persia> Right.  Looking again, I was doing bug triage during the upgrade window, so would have noticed.  Isn't it usually Thursdays anyway?  Maybe the 20th?
[06:11]  * Fujitsu wonders why that md5sum bug isn't Critical and long-fixed...
[06:11] <warp10> Hi all!
[06:12] <Fujitsu> Hi warp10.
[06:12] <warp10> Fujitsu: hi!
[06:14] <blueyed> Is is "a EVMS object" or "an EVMS object"? What's the rule again?
[06:15] <Fujitsu> That's debateable.
[06:15] <Fujitsu> I would say the latter, as it's very rarely expanded, but others would disagree.
[06:16] <Fujitsu> Wait, in both cases it is the latter.
[06:17] <persia> The rule is that the 'n' is included if the following word begins with a vowel (sometimes including 'h' and excluding 'y')
[06:18] <Fujitsu> Right. But acronyms can get interesting to pronounce with that policy, but that particular one isn't afflicted.
[06:18] <blueyed> yes, I remember that it's not only the letter, but the sound.
[06:18] <persia> blueyed: Right, which is why it is often "an hour" and "a yellow dog"
[06:24] <blueyed> Does a patch like the following make sense really? Or does it only put work on the translators? http://launchpadlibrarian.net/4704937/evms-strings.patch
[06:25] <persia> blueyed: It makes a lot of sense, and is a good patch, and should be applied upstream (not even Debian would be very interested).
[06:26] <blueyed> persia: yes, I'd forward it in anyway. So you think I should prepare a debdiff?
[06:26] <blueyed> There are two other similar bugs for the same package.
[06:26] <blueyed> (with smaller patches)
[06:27] <persia> blueyed: I don't see anything there that might be confusing, just typos & the like.  I'd not sponsor that, and don't expect others would: the problem is that it makes all the strings fuzzy for small benefit.
[06:28] <blueyed> Ok. So then it should only get forwarded upstream?
[06:29] <persia> blueyed: Right, and watched, and closed when upstream accepts it.  Was there a change that would reduce confusion, or changed something that was wrong, it would make more sense to apply an Ubuntu-specific patch.
[06:29]  * persia notes that the guidelines are a little different for packages in main due to Rosetta, and that the answer may be different (but not likely very different).
[06:39] <blueyed> persia: submitted the patch to upstream (luckily on SF.net) and added bug watches. Sometime launchpad is really nice.. ;)
[06:47] <persia> blueyed: Sometimes :)  Please stay subscribed, as LP can't yet tell when it's fixed by tracking the upstream bug into the repos.
[06:50]  * Fujitsu notes that LP should actually grab the status of SF bugs from 1.1.12.
[06:51] <blueyed> Fujitsu: yes, but it does not close the Ubuntu task.
[06:52] <persia> Fujitsu: As in actually report them as "closed elsewhere" for easy tracking?
[06:52] <Fujitsu> persia: Yes.
[06:52] <Fujitsu> SourceForge is the only type of bugtracker import that doesn't do that at the moment.
[06:54]  * persia anticipates significant growth of https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=resolved_upstream
[06:54] <Fujitsu> Hopefully.
[06:54] <Fujitsu> And we even get importance syncing soon.
[06:55] <TheMuso> c
[06:55] <TheMuso> damn wrong ta
[06:55] <TheMuso> tab
[06:58] <persia> Fujitsu: What's the MOTU-swat workflow?  Does it involve subscriptions for things like bug #176931?
[06:58] <ubotu> Launchpad bug 176931 in lookup-el "[lookup-el] [CVE-2007-0237] possible local symlink attack" [Unknown,Fix released] https://launchpad.net/bugs/176931
[06:58] <Fujitsu> persia: Yes please. I wish hk47 would subscribe us, as he files a lot.
[06:59] <persia> Fujitsu: This should probably be documented somewhere :)
[06:59] <Fujitsu> Quite possibly.
[07:28] <dholbach> good morning
[07:52] <geser> morning
[07:55] <dholbach> hey geser
[07:55] <geser> Hi dholbach
[08:20] <slytherin> what is format for specifying LP bug number in changelog?
[08:26] <geser> LP: #nnn
[08:34] <slytherin> geser: thanks
[08:36] <slytherin> One more question.  a package doesn't exist in debian yet, I am packaging it for Ubuntu. Is the XSBC-Original-Maintainer field necessary?
[08:37] <minghua> No if the maintainer address you use is an @ubuntu.com one, I believe.
[08:38] <persia> If you plan to have the package be team maintained, it's good to add your name as the Original-Maintainer to note that you are a good contact if people have questions.
[08:42] <slytherin> persia: No plans like that as of now.
[09:05] <slytherin> I have just added libxml-commons-external-java to revu. This is one step forward in getting latest batik in Ubuntu. It is my first attempt at java library packaging from scratch. So please hammer slowly. :-D
[09:09] <Fujitsu> Mightn't it be an idea to get batik to build on the buildds in the first place, before upgrading it?
[09:10] <slytherin> Fujitsu: Tried that already. Too many errors. 1.7 beta will build if this library is in and a small problem in build.xml is fixed via a patch. :-)
[09:11] <Fujitsu> Ah, good.
[09:11] <Fujitsu> Using icedtea or gcj?
[09:11] <slytherin> Fujitsu: gcj
[09:12] <huats> MOTUs and hopeful : Hello :)
[09:13]  * persia complains about discrimination against core-devs and happy contributors :)
[09:17] <huats> ;)
[09:17]  * dholbach hugs y'all :)
[09:17] <huats> persia: if you want I can leave and come back to make it ok :)
[09:20] <persia> huats: No worries.  I just like complaining about that :)
[09:22]  * huats always knew that you like to complain..
[09:22] <huats> :)
[09:46] <persia> Does anyone in the SRU team intend to attend the MOTU meeting on Friday?
[09:49] <TheMuso> Don't think I can make it.
[09:49] <TheMuso> Actually, I could make that
[09:50] <TheMuso> persia: I don't think its hard to use. I've almost got the steps memorised, both for making one, and checking one.
[09:53] <persia> TheMuso: I'd agree with that, it's just that there was an SRU team meeting last week, and I'd like to see a report of the updated process.  If someone is attending, and wouldn't mind preparing a short note as an agenda item, it might be nice (but is definitely wishlist).
[09:53] <TheMuso> Right.
[09:54]  * persia cheers, and travels
[10:12] <proppy> hi
[10:19] <dsop> must an upstream makefile support the DESTDIR variable ?
[10:27] <stdin> dsop: if it doesn't use autoconf then yes
[10:31] <elmargol> It think I'm not allowed to change files outside the debian folder?
[10:31] <elmargol> Somehow the f-spot package does this
[10:32] <pochu> elmargol: if you need to do it use a patch system
[10:33]  * StevenK tries to figure out why a CDBS using package fails with dh_install
[10:40] <StevenK> ... Interesting. The terminal that build is in is orange ...
[10:40] <StevenK> I think the Ubuntu theme is re-asserting itself
[11:05] <Kmos> norsetto: morning
[11:05] <norsetto> morning
[11:08] <dholbach> hey norsetto - how's your network?
[11:08] <Kmos> dholbach: hi :)
[11:08] <dholbach> hi Kmos
[11:08] <norsetto> dholbach: hey! finally solved my problems with my IP
[11:09] <dholbach> norsetto: how did you solve it?
[11:09] <dholbach> everybody cheer! we have norsetto back!
[11:09] <norsetto> dholbach: by calling them and giving them a hard time ....
[11:10] <dholbach> and how did they fix it?
[11:11] <norsetto> dholbach: no idea, what they told me is that there was a problem in the "central", I guess just a server went boing last thunderstorm
[11:11] <imbrandon> moins all
[11:11]  * imbrandon yawns
[11:11] <dholbach> norsetto: I'm really glad you're back
[11:11] <norsetto> yes, his colon is still ok
[11:11]  * txwikinger2 sympathy-yawns
[11:12] <imbrandon> imbrandon == imbrandon++; today is the last birhtday of my 20's :(
[11:12] <imbrandon> hehe
[11:12] <dholbach>   ____ ___  _   _  ____ ____      _  _____ ____  _
[11:12] <dholbach>  / ___/ _ \| \ | |/ ___|  _ \    / \|_   _/ ___|| |
[11:12] <dholbach> | |  | | | |  \| | |  _| |_) |  / _ \ | | \___ \| |
[11:12] <dholbach> | |__| |_| | |\  | |_| |  _ <  / ___ \| |  ___) |_|
[11:12] <dholbach>  \____\___/|_| \_|\____|_| \_\/_/   \_\_| |____/(_)
[11:12] <dholbach>                                                    
[11:12] <dholbach> ! :-)
[11:12] <imbrandon> hehe thanks dholbach
[11:13] <txwikinger2> long live monospace
[11:13] <Kmos> imbrandon: happy birthday!
[11:13] <pochu> happy birthday imbrandon :)
[11:13] <txwikinger2> happy bday imbrandon
[11:13] <norsetto> imbrandon: happy (!?) birthday
[11:13]  * imbrandon feels loved
[11:13]  * txwikinger2 feels really old
[11:13] <Kmos> we need to get an irc admin to kill him with "HAPPY BIRTHDAY"
[11:13] <Kmos> :)
[11:14] <imbrandon> Kmos: i'm a freenode staff, guess i could do it myself LOL
[11:14] <Kmos> imbrandon: lolll
[11:14]  * norsetto thinks txwikinger is a reckless youngster
[11:14] <Kmos> imbrandon: isn't a bad idea.. onself kill
[11:15]  * txwikinger2 is probably double the age of norsetto :)
[11:15] <txwikinger2> what does that make norsetto then? :D
[11:16] <norsetto> since we are talking about age, I think somebody just turned to the top position again (well, at least he joined me)
[11:16] <imbrandon> heh age is all relitive, i turn 29 today and it dont bug me a bit, i love birthdays , but my wife is a few months older than me ( turned 29 in sept ) and it kills her
[11:16] <imbrandon> lol
[11:17] <norsetto> txwikinger2: I doubt you are 90 years old, but then I could be wrong
[11:17] <txwikinger2> what is the top position? the oldest person?
[11:17] <txwikinger2> Nah.. not 90 :D
[11:18] <imbrandon> the only bad part is its still 5am here, so no one else is awake yet :)
[11:18] <txwikinger2> a lot of people never really wake up anyway
[11:19] <imbrandon> heh
[11:19]  * txwikinger2 thinks otherwise they wouldn't prefer Windows over Ubuntu ;)
[11:22] <Kmos> bug 173529
[11:22] <ubotu> Launchpad bug 173529 in python-coverage "Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)" [Wishlist,Invalid] https://launchpad.net/bugs/173529
[11:22] <effie_jayx> DaD is down?
[11:22] <Kmos> what can I do about this one?
[11:22] <Kmos> effie_jayx: yes
[11:22] <effie_jayx> Kmos,  thanks
[11:23]  * txwikinger2 wonders if he can convert to Islam for one day in order to take advantage of the religious holiday tomorrow
[11:25] <norsetto> kmos: you should check why there is this difference
[11:27] <dsop> okay, 10th try or somewhat to get my p[ackage included :)
[11:27] <Kmos> norsetto: i'll check.. but the comparison is about debian and ubutu .orig.tar.gz ?
[11:29] <Kmos> debian: 10525
[11:29] <Kmos> ubuntulog: 10514
[11:29] <Kmos> at ubuntu: 10514
[11:30] <norsetto> kmos: yes, so, why is there such a difference? Has the upstream tarball been changed by  Ubuntu or Debian, and why? If the Debian one is correct than we can sync.
[11:31] <Kmos> the ubuntu .orig.tar.gz unpacks to python-coverage-2.6.orig and debian to python-coverage-2.6
[11:31] <Kmos> i think this won't change it's size
[11:32] <Kmos> i've done a diff agains the only file inside the .tar.gz
[11:32] <Kmos> coverage.py
[11:32] <Kmos> and it doesn't have any differences from debian to ubuntu
[11:33] <Kmos> let's check upstream - http://www.nedbatchelder.com/code/modules/coverage.htm
[11:35] <Kmos> the upstream is now 2.77 and not 2.6
[11:35] <Kmos> already reported to debian bts
[11:35] <Kmos> and it doesn't have the old .tar.gz to download
[11:39] <Kmos> i'll comment the bug report
[11:39] <norsetto> kmos: can you wait until I check too?
[11:40] <Kmos> norsetto: ups.. already done
[11:40] <Kmos> :)
[11:40] <Kmos> i've commented what I found
[11:54] <zul> morning
[11:55] <Kmos> norsetto: https://code.edge.launchpad.net/python-coverage
[12:26] <mruiz> hi all
[12:26]  * Hobbsee waves
[12:27] <MenZa> hey Hobbsee
[12:27] <pochu> hi Hobbsee
[12:27] <RainCT> hi
[12:27] <Hobbsee> :)
[12:27] <mruiz> hi pochu , Hobbsee , MenZa , RainCT
[12:28] <pochu> hey mruiz
[12:28] <totopalma> hi all :)
[12:28] <zul> hey Hobbsee
[12:59] <ScottK> StevenK: Thank you for touching python-numpy.
[13:00] <StevenK> Oh, damn.
[13:01] <StevenK> Now I've touched it last.
[13:01] <geser> Hi Hobbsee
[13:01] <Hobbsee> heya geser
[13:01] <StevenK> ScottK: It and 45 other packages
[13:04] <ScottK> StevenK: I think Fujitsu was looking into the new numpy in any case.
[13:06] <StevenK> Ah. I'm only trying to get at NBS packages
[13:35]  * persia praises norsetto for his excellent packaging skills
[13:53] <mruiz> hi all... DaD is offline?
[13:55] <persia> mruiz: 404 from here
[13:55] <mruiz> thanks for the confirmation persia... I got the magic number too
[13:56] <persia> mruiz: Try MoM or http://qa.ubuntuwire.com/multidistrotools/ if you need, but at this point it's better to close bugs than to chase merges.
[14:04] <mruiz> ftbfs bugs are a goal?
[14:05] <persia> mruiz: Very much so.  Are you looking for something to do?
[14:05] <mruiz> persia, yes... :D
[14:07] <Adri2000> mruiz: well, I don't know what's going on with DaD... and I don't seem to be able to ssh in the server from here
[14:07] <persia> mruiz: I'd suggest picking packages and doing general improvement runs.  FTBFS fixes are great if you can, but some are tricky.  Easier would be package updates & watch files from http://qa.ubuntuwire.com/uehs/,  Even easier would be dependency fixes from http://qa.ubuntuwire.com/debcheck/
[14:08] <persia> mruiz: Start from one of FTBFS, UEHS, or debcheck, pick a package, check the LP bugs for easy ones, and prep a candidate.
[14:08] <mruiz> thanks Adri2000 for the explanation about that
[14:11] <verb3k> LucidFox, Hi .....I don't like to be annoying but I did you you told me to do
[14:13]  * persia encourages verb3k to file a bug rather than poking on IRC
[14:13] <verb3k> persia, argh ... you caught me :)
[14:14] <mruiz> persia, I'll start with dependency fixes
[14:14] <verb3k> persia, I guess I;ll have to take the hard way and learn packaging
[14:14] <verb3k> I'll*
[14:15] <persia> mruiz: That's probably a good place.  I strongly recommend you take a look at all of UEHS, FTBFS, LP, MDT, and the BTS when you pick a package.  Often there are good fixes in other places that you can combine to make a more useful upload.
[14:27] <slytherin> I have quickly fixed an FTBFS for libglazedists-java by adding java-gcj-compat-dev to Build-Depends. How and where to upload the fix?
[14:28] <persia> slytherin: Add a debdiff to a bug.  See https://wiki.ubuntu.com/MOTU/Contributing
[14:28] <slytherin> persia: Does that mean first log a bug?
[14:29] <persia> slytherin: Check to see if there is one first, but likely.
[14:30] <slytherin> persia: I picked up the package from the ftbfs list on qa.ubuntuwire.com. So I doubt there is a bug already
[14:31] <persia> slytherin: Yes, there likely isn't, but it's always best to check.
[14:32] <slytherin> persia: Ok. One more thing. is it possible to send mails to debian packagers to have java-gcj-compat-dev as first build dependency in all the java related packages? I think it will reduce lot of ftbfs. Currently most of them have sun jdk as build dependency which can not be installed non-interactively.
[14:33] <persia> slytherin: My understanding is that it is polite to discuss possible mass-bug filing in mailing lists first in Debian.  Best to track down the mailing list for the debian-java team, and send a note there.
[14:34] <slytherin> persia: Ok. I will finish this package first and then send mail on list if there is one.
[14:35] <persia> slytherin: Thank you.  Getting java in better shape is a tough job, and I'm really glad to see someone tackling it.
[14:36] <slytherin> persia: I am a java developer so I can put more brain in these issues. :-)
[14:36] <persia> :)
[14:43] <mruiz> UEHS: Ubuntu External Health Status... in this case, what does mean external ?
[14:44] <imbrandon> upstream
[14:45] <bddebian> Heya gang
[14:46] <persia> mruiz: That list contains all the packages unique to Ubuntu or orphaned in Debian, for which we can't verify they are in sync with upstream.  These typically benefit from a look.
[14:49] <slytherin> persia: Done. bug 177477
[14:49] <ubotu> Launchpad bug 177477 in libglazedlists-java "Fix FTBFS by adding java-gcj-compat-dev as build dependency" [Undecided,New] https://launchpad.net/bugs/177477
[14:50] <geser> Hi bddebian
[14:50] <persia> slytherin: Great.  You'll want to set the status to "Confirmed" (subscribing the sponsors queue is the special exception to the general rule of not confirming your own bugs), but otherwise it looks good.
[14:51] <slytherin> persia: I will leave that to sponsors. :-)
[14:52] <slytherin> I am actually enjoying this. :-D
[14:53] <persia> slytherin: Please confirm it.  When processing the sponsors queue, we look at confirmed unassigned bugs first, and when tired or lazy, sometimes just push the others out of the queue for not being properly formed (we try not to do this, but sometimes after 10 rejections, one gets trigger-happy)
[14:53] <slytherin> Ok. :-)
[14:53] <slytherin> done
[14:54] <bddebian> Heya geser
[14:54] <persia> slytherin: Thank you.
[15:04] <promag> is this the place to ask questions about packaging?
[15:05] <promag> well
[15:05] <promag> I have an autoconf/automake project (c++)
[15:06] <promag> the makefile's create multiple binaries and libraries
[15:06] <persia> promag: For packaging of applications for Ubuntu, yes.
[15:06] <promag> I want to create several debian packages
[15:07] <promag> from this autoconf/automake project
[15:07] <promag> for each library I want to create a package
[15:07] <persia> promag: The general rule of thumb is to split a source package into two packages per library (lib + dev), a separate package for any daemon, and separate userspace packages for qt, gtk, tk, console, etc.
[15:08] <promag> two packages per library?
[15:08] <promag> dev is the source?
[15:08] <persia> The library packaging guide (http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html) and the package splitting guide (http://wiki.debian.org/PkgSplit) will be useful adjuncts to the packaging guide (https://wiki.ubuntu.com/PackagingGuide/).
[15:09] <promag> ok
[15:09] <promag> so there's no relation between packaging and makefile.am's?
[15:09] <persia> promag: libfoo0.0.1 is the actual library.  libfoo-dev is the development headers, etc.  foo-tools is the small utilities that use the library.
[15:10] <persia> promag: If you have a good makefile.am, you can make a very small debian/rules file if you don't mind a bit of make magic: see https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml
[15:10] <promag> well, I have several makefile.am
[15:12] <persia> promag: Does the entire thing build with automake; ./configure; make; make install --DESTDIR=./debian/tmp/ ?
[15:12] <promag> yes
[15:13] <promag> You use CDBS?
[15:14] <persia> promag: I am only a secondary maintainer, so I use whichever packaging system the original maintainer used.  I personally like CDBS when it works, and find it annoying when it doesn't.  Usually it can be made to work.
[15:18] <promag> persia: thanks for your time
[15:18] <promag> I think I'll try cdbs
[15:18] <promag> ohh
[15:18] <persia> promag: No problem.  Good luck with your packaging, and feel free to ask questions here if you get stuck.
[15:18] <promag> one more question
[15:19] <promag> it works for any language?
[15:19] <promag> lets say I want to build a package with some php code and flex apps in the middle
[15:21] <imbrandon> mmm nice
[15:21] <persia> As long as your build system manages that, it should be fine.  Basically, debian/rules is a makefile, which has some defined targets that get called during the build process.  These in turn tend to call hooks into the original source build system.
[15:21] <\sh> django is a cool framework...
[15:21] <imbrandon> i just got my old unused palm VIIx ( ancient thing ) to work as an external lcd display when in the cradle
[15:21] <imbrandon> :)
[15:21] <persia> When you use CDBS, you're including a bunch of makefile snippets already written by other people which do most of the work for you, and there is good support for hooking into autotools.
[15:22] <persia> imbrandon: VNC?
[15:22] <promag> persia: ok thanks I'll try it
[15:22] <imbrandon> no, just like a 20x4 text display
[15:22] <mruiz> persia, finally I decided to update a package: adtools ... also I'm looking for doc about debian/rules
[15:22] <imbrandon> persia: via serial, matrixorbital lcd driver
[15:22] <persia> imbrandon: I had VNC working on my III.  You ought to be able to get some graphics :)
[15:23] <imbrandon> ahh
[15:23] <imbrandon> never thought about vnc on a palm
[15:23] <imbrandon> well older palm
[15:23] <persia> imbrandon: Just run a special X server to feed the VNC, and then send your clients to the appropriate display (assuming you set the appropriate permissions).
[15:25] <persia> mruiz: Debian policy defines the required rules.  Beyond that, it's just a makefile, and all the tricks from http://www.gnu.org/software/make/manual/make.html are acceptable.  The more you can make it not look like a shell script, the better (but don't adjust packaging too much for an update)
[15:28] <Adri2000> has anyone visited DaD today before around 11:00 UTC (that was 4:30 hours ago) ?
[15:28] <Adri2000> and was it working? or was it already 404ing?
[15:35] <promag> persia: how does cdbs knows the control files for the packages I want to create?
[15:35] <persia> promag: You need to manually generate control, rules, and copyright.  For a package split, you will also need a bunch of debian/package.dirs and debian/package.install files.
[15:35] <persia> Also, you'll need a changelog: I suggest creating this with dch
[15:36] <promag> persia: any change of dhc fetch comments from svn?
[15:36] <promag> *chance
[15:37] <persia> promag: You don't want that.  The application changelog (./changelog) contains the upstream changes.  The debian changelog (debian/changelog) contains packaging changes.
[15:38] <promag> persia: Any online reference about multiple debian/packages.dirs and debian/package.install ?
[15:39] <persia> promag: Should be in the library packaging guide and package split guide I pasted before.  The dh_install manpage is also informative.
[16:26] <promag> persia: I'm a bit lost with cdbs
[16:26] <promag> can I call dh_make to create necessary files?
[16:28] <pochu> Yes, but the debian/rules file created won't be cdbs, but debhelper style
[16:29] <pochu> You can remove and create a cdbs rules file then, as cdbs is simple
[16:29] <pochu> dunno if there's a better way...
[16:30] <promag> but dh_make asks this:
[16:30] <promag> Type of package: single binary, multiple binary, library, kernel module or cdbs?
[16:30] <promag> I choose cdbs
[16:30] <promag> right?
[16:31] <pochu> Heh, didn't know that :-)
[16:31] <promag> well me too :P
[16:31] <promag> :-p
[16:32] <promag> my project creates a program (binary) and several plugins (libraries)
[16:32] <promag> cdbs is fine?
[16:32] <txwikinger> when I do an interdiff, how does it considers the fact that the orig.tars are different?
[16:32] <pochu> Yes, although debhelper is fine too.
[16:33] <promag> pochu: well but I'm noob
[16:33] <promag> supa noob
[16:34] <promag> :-p
[16:34] <promag> after doing dh_make I do "debuild -S"
[16:34] <promag> it says "make[1]: *** No rule to make target `distclean'."
[16:35] <promag> ohh ok
[16:35] <promag> -S creates a source package
[16:36] <promag> gpg: skipped "promag <promag@localhost>": secret key not available
[16:36] <promag> what can I  do?
[16:36] <pochu> promag: also dh_make will create a template. You need to edit it :)
[16:37] <pochu> s/it/the files in debian\//g
[16:37] <promag> pochu: leet :-p
[16:37] <promag> ok
[16:37] <pochu> promag: either pass "-us -uc" (unsign source, unsign changes) to debuild, or set "DEBMAIL"
[16:37] <pochu> (or was it DEBEMAIL?)
[16:38] <pochu> That's for the secret key issue
[16:38] <promag> pochu: well I'm toying with hello.tar.gz just to see what happens
[16:38] <promag> so do I need to edit templates?
[16:39] <pochu> After dh_make, yes
[16:39] <pochu> for example look at debian/copyright
[16:39] <pochu> There's no copyright information, just a template :)
[16:40] <promag> pochu: and what about generating packages from svn tags ?
[16:41] <pochu> promag: sorry, I'm not sure what you mean
[16:42] <verb3k> The flash plugin is broken and I finally got the recently released flash player but it is really really slow, is there a way to get the previous version?
[16:42] <promag> supose I tag a source revision as version 0.2
[16:43] <pochu> Then the package should be called foo_0.2.orig.tar.gz
[16:43] <pochu> (the debian one, upstream's should be foo-0.2.tar.gz)
[16:43] <promag> then, to build a package, I need to checkout /svn/foo/tags/0.2 foo
[16:43] <pochu> svn export rather
[16:44] <pochu> as export will remove the .svn/ directories :)
[16:44] <promag> right
[16:44] <pochu> promag: and svn/foo/tags/0.2 foo-0.2
[16:44] <pochu> better :)
[16:44] <promag> ok... what about the tar.gz?
[16:45] <pochu> promag: if you copy the foo-0.2 to foo-0.2.orig, before creating the debian/ subdir, it will be generated when you create the source tarball
[16:45] <pochu> e.g. dpkg-source -b foo-0.2
[16:46] <pochu> (foo-0.2.orig/ shouldn't have a debian/ subdir)
[16:59] <promag> pochu: much appreciate
[17:25] <warp10> Hi all!
[18:04]  * txwikinger is confused about Bug #73612
[18:04] <ubotu> Launchpad bug 73612 in ubuntu "please sync python-ldap-doc from Debian Sid" [Undecided,Fix released] https://launchpad.net/bugs/73612
[18:05] <txwikinger> Wenn was this package ever uploaded?
[18:06] <txwikinger> When
[18:08] <geser> txwikinger: https://edge.launchpad.net/ubuntu/feisty/+queue?queue_state=4&queue_text=python-ldap
[18:08] <amitprakash> hi... i set a ubuntu repo using http://nerdica.com/?p=43
[18:08] <geser> txwikinger: it was rejected but don't ask me why
[18:08] <amitprakash> however .. when other clients update.. they give preference to the official repositories
[18:09] <norsetto> txwikinger: apparently it was in dapper: python-ldap-doc | 2.0.4-1ubuntu4 |        dapper | all
[18:09] <amitprakash> does anyone know why is this so or how to fix this
[18:09] <RainCT> wow, it's easy to setup a repo :)
[18:10] <txwikinger> ah thanks geser, norsetto
[18:10] <RainCT> amitprakash: what do you mean exactly with "it gives preference"?
[18:10] <geser> norsetto: as the bug said, it got split from python-doc
[18:10]  * geser notices that the PTS has a new layout
[18:11] <geser> txwikinger: you might want to ask why it didn't got included in Ubuntu
[18:11]  * RainCT notices it too
[18:16] <amitprakash> RainCT, i mean if its available on my repo.. it shouldnt download from official repos
[18:16] <pochu> Do they have the same version?
[18:18] <amitprakash> pochu, yes
[18:19] <pochu> amitprakash: then why should it use your package? I trust more the archive than your repo :)
[18:20] <pochu> amitprakash: just bump your package's version
[18:20] <pochu> What are you packaging by the way? :)
[18:27] <txwikinger> geser: Who should I ask? Who might know?
[18:39] <geser> txwikinger: I don't know who might remember but try Mithrandir or pitti in #ubuntu-devel
[18:42] <jeromeg> is it possible to remove a package from a ppa ?
[18:43] <geser> jeromeg: yes, but afaik and irrc currently only through opening an answer ticket
[18:44] <jeromeg> geser: ok, where should I open it ?
[18:44] <amitprakash> pochu, no other way ?? i wanted it so that i could get people to use the already downloaded repos
[18:44]  * txwikinger thinks debian is cheating
[18:44] <jeromeg> geser: in the launchpad answer tracker ?
[18:49] <awen_> hi... i'm trying to set up pbuilder to be able to package for multiple distributions as describet in the howto: https://wiki.ubuntu.com/PbuilderHowto ... it works fine when using pbuilder, but pdebuild still looks for the base.tgz (it seems that either the DIST variable doesn't get passed), anyone know how to make it work?
[18:49] <geser> jeromeg: iirc yes, but ask in #launchpad first, I can't find right now, where I read it
[18:50] <jeromeg> geser: I just asked and got a reply, thank you
[19:06] <awen-> seems i lost the connection. did anyone have a hint for me? =)
[19:10] <pochu> awen-: no
[19:11] <amitprakash> pochu, no other way ?? i wanted it so that i could get people to use the already downloaded repos
[19:13] <pochu> What do you mean with already downloaded repos?
[19:17] <awen-> ahh PBUILDERROOTCMD="sudo -E"
[19:22] <Ubulette> asac, vv
[19:22] <Ubulette> fta@ix:~ $ epiphany
[19:22] <Ubulette> epiphany-browser: error while loading shared libraries: libplds4.so: cannot open shared object file: No such file or directory
[19:22] <Ubulette> oops, wrong channel
[19:30] <jdong> dear world, hold me..... math exam scores are being posted......
[19:30] <effie_jayx> jdong,  good luck
[19:31] <cbx33> good luck jdong
[19:32]  * somerville32 would changes his nick to world and then hug jdon and then change back but he is into too many channels to do that :P
[19:32] <jdong> well so far average is 43/80 stddev=19
[19:32] <jdong> that might just barely save me
[19:32] <amitprakash> pochu, hi.. wat i meant is that i download debs from official repo.. and add em to mine
[19:32] <jdong> though this term will be tight. My current expectation is a failing D.
[19:32] <amitprakash> pochu, now people who use my repo get it off lan instead of net
[19:33] <geser> amitprakash: like a archive mirror?
[19:33] <amitprakash> geser, yes
[19:33] <amitprakash> geser, however i wont it to work with apt-get
[19:34] <pochu> amitprakash: do you mirror the entire archive?
[19:34] <amitprakash> pochu, no.. only the part i need
[19:35] <pochu> I dont know whether it's possible, sorry. And also I can't understand why you would need to copy some packages to your repo :)
[19:35] <somerville32> pbuilder mirrors only the parts you need
[19:35] <somerville32> so does sbuild I think
[19:42] <cbx33> hey guys
[19:42] <cbx33> who knows about mesa here?
[19:42] <cbx33> blender crashes on ati cards
[19:42] <cbx33> and I'm trying to figure out why
[19:42] <cbx33> or more accurately what I can do to fix it
[19:43] <cbx33> https://bugs.freedesktop.org/attachment.cgi?id=11723
[20:27] <totopalma> umh
[20:39] <TheMuso> Hey folks.
[20:42] <geser> Hi TheMuso
[20:48] <bddebian> Heya TheMuso
[21:05] <ScottK> keescook or jdstrand: Would you please have a look at Bug #177537.
[21:05] <ubotu> Launchpad bug 177537 in clamav "Remote Code Execution" [Undecided,In progress] https://launchpad.net/bugs/177537
[21:05] <ScottK> Looking at the debdiff it looks reasonable to me (I think this is based on the new Etch package that just got published).
[21:06] <keescook> ScottK: sure thing, gimme a few minutes -- just finished rebooting into 2.6.24.  :)
[21:06] <ScottK> keescook: Thanks.
[21:06] <ScottK> leonel: ^^^
[21:07] <leonel> ScottK: reading
[21:07] <leonel> great !
[21:07] <leonel> checking  feisty's  clamav  ..
[21:12] <keescook> leonel: in the patch for CLI_UNPSIZELIMITS(NAME,CHK), there is a "free(section_hdr);" that isn't in the original version of the code.  Is that okay/expected?
[21:13] <keescook> leonel: also, can you adjust the version to be ubuntu2.1 instead of ubuntu3 ?
[21:14] <ScottK> keescook: Once you get the gutsy-security version published, I'll ask to have that backported to feisty-backports to cover that pocket.
[21:15] <keescook> leonel: do you happen to have reproducers for the CVEs?
[21:15] <leonel> keescook: not yet
[21:15] <keescook> leonel: okay, cool. oh, and pocket needs to be "gutsy-security" too :)
[21:15] <ScottK> \sh or keescook: Are we doing Universe security announcements yet?
[21:16] <keescook> ScottK: I don't know what the plans are for that.  I think Fujitsu was driving it?
[21:16] <ScottK> Ah.  OK. I think Fujitsu and
[21:16] <ScottK> \sh are both involved.
[21:16] <jdstrand> keescook: I thought there was talk of UUSN in LP
[21:16] <ScottK> Thanks.
[21:17] <keescook> jdstrand: cool.
[21:17] <jdstrand> a cherrypick or something...
[21:17] <jdstrand> I haven't seen it though
[21:17] <keescook> jdstrand: oh, I think you mean the -changes announcements.
[21:18] <jdstrand> probably
[21:18] <jdstrand> can you tell I am fuzzy on the details?
[21:18] <keescook> jdstrand: that's already happened.  I'm assuming ScottK is talking about a separate mailing list like, like for ubuntu-security-announce
[21:18] <keescook> hehe
[21:18] <jdstrand> oh I see
[21:18] <ScottK> Or maybe I was confused.
[21:19] <\sh> ScottK, hrm? I thought kees and/or jd are doing the USN announcement for any package security fix...
[21:19]  * \sh is lost in django jungle
[21:19] <ScottK> \sh: Dunno.  I guess it's sounding that way.
[21:19] <jdstrand> \sh: currently only for main
[21:19] <keescook> \sh: only the stuff in main/restricted goes out on u-security-announce
[21:19]  * ScottK is lost (as usual) in Ubuntu process churn.
[21:20] <jdstrand> \sh: LP now has UUSN support (at least started)
[21:20] <jdstrand> keescook: I am assuming we could use the existing framework for the website
[21:20]  * \sh talks with Fujitsu about all the new stuff :) from next week on I'll back on the ubuntu path  
[21:20] <ScottK> slangasek: Noting the discussion about flash-plugin-nonfree on debian-release: At least in the Kubuntu packages the new Flash breaks Konqueror do to some new function they want that Konqueror doesn't have.  FYI.
[21:21] <\sh> jdstrand, sounds promising :)
[21:21] <keescook> jdstrand: yeah, I'd love to.  with security-in-soyuz, it'll likely be trivial.
[21:21]  * ScottK also anxiously awaits the chance to endorse \sh's re-application to MOTU.
[21:22] <slangasek> ScottK: can you follow up to the discussion on debian-release?  I'm not really involved with Debian stable updates
[21:22] <\sh> ScottK, well, when I'm starting with my new job...there will be some new Ubuntu Projects coming from me...one idea will be to present Ubuntu People live on Interactive Flash TV :)
[21:22] <leonel> keescook: that  free(section_hdr)   It's in the debian patch  so I guess  it must  be there
[21:22] <keescook> leonel: okay, cool
[21:23] <ScottK> slangasek: OK.  Will do.  I'm somewhat relucant to be "the Ubuntu guy" on Debian lists, but since it's you asking ...
[21:23] <leonel> keescook: do you want me to redo the diff with the changes  you mention ?
[21:23] <\sh> ScottK, go kill yourself on debian lists ,-)
[21:23] <ScottK> Wouldn't be the first time.
[21:23] <\sh> ScottK, and always tell them "launchpad is the way it works" ;)
[21:24] <ScottK> \sh: I don't even say that here.
[21:24] <slangasek> ScottK: you, er, are in the NM queue, so. :)
[21:24] <ScottK> Yeah.  OK.
[21:25] <\sh> ScottK, oh you are going the NM way...didn't know...good luck
[21:26] <ScottK> \sh: A little bit at a time as I have time.
[21:37] <keescook> leonel: no need, I've got it fixed up
[21:38] <Fujitsu> \sh: Morning.
[21:39] <\sh> hey Fujitsu
[21:42] <\sh> Fujitsu, quoting jd: "<jdstrand> \sh: LP now has UUSN support (at least started)" could you elaborate a bit, pls? :)
[21:42] <Flare183> bug: #175404
[21:43] <TheMuso> bug 175404
[21:43] <ubotu> Launchpad bug 175404 in ubuntu "[needs-packaging] Nemo" [Wishlist,In progress] https://launchpad.net/bugs/175404
[21:43] <Flare183> oh thanks
[21:43] <TheMuso> np
[21:43] <Fujitsu> \sh: I haven't heard any mention of it. I know the dak hack is going away within a couple of months, though.
[21:45] <Fujitsu> cprov: jdstrand mentioned that there is some kind of USN support in development in LP. Can you confirm/clarify/whatever?
[21:48] <ScottK> leonel: How does Feisty look.
[21:53] <leonel> ScottK: just starting making  feisty's pbuilder ..
[21:54] <ScottK> leonel: OK.  Thanks.
[21:55] <Lutin> for those who asked: DaD is now back online. however, all the comments have been lost :
[21:58] <ScottK> Lutin: What happened?
[21:59] <leonel> ScottK: need to go out be back in 1 hour approx
[22:01] <totopalma> RainCT, hi :)
[22:01] <Sp4rKy> ScottK: the dad repository has disappeared from the server
[22:01] <RainCT> hi totopalma :)
[22:01] <Adri2000> ScottK: the whole DaD directory disappeared from the server, we don't know yet why and what caused that
[22:01] <ScottK> OK.
[22:05] <verb3k> if I want to make a .desktop file for  a game CD ripping tool, in which category should I put it?
[22:05] <verb3k> AudioVideo?
[22:06] <\sh> Adri2000, vserver based?
[22:07] <RainCT> Adri2000: o_O
[22:07] <RainCT> Adri2000: btw, anything new?
[22:08] <Sp4rKy> RainCT: we put DaD back online
[22:08] <Sp4rKy> but we had to rebuild the whole DaD base
[22:08] <Sp4rKy> and all comments are lost
[22:08] <Sp4rKy> \sh: no, dedicated server, so very strange
[22:09] <Fujitsu> Sp4rKy: I find it to be a bad idea to restore it without knowledge of how it happened. If the server was compromised, merges could have been modified, and I know some people don't thoroughly review diffs.
[22:09] <Lutin> Fujitsu: it's a full 'rebuild', not a backup copy
[22:10] <Sp4rKy> Fujitsu: the server was checked and seems clean, moreover, it's a rebuild (so all merges have been rebuilt)
[22:10] <Fujitsu> Lutin: Right, but before it was removed there could have been other changes.
[22:10] <\sh> Sp4rKy, you don't have any tools like webmin, confixx or plex on it?
[22:10] <Lutin> Fujitsu: agreed
[22:10] <Sp4rKy> \sh no
[22:11] <Sp4rKy> no suspicious auth, nothing in history log
[22:11] <Fujitsu> Is that surprising?
[22:12] <Sp4rKy> a bit ^^
[22:12] <\sh> thinking about the comments, you are using mysql? hopefully not remotely accessible
[22:12] <Sp4rKy> \sh: dad doesn't use mysql :(
[22:12] <\sh> Sp4rKy, how do you save your comments?
[22:13] <Sp4rKy> plain text
[22:13] <Lutin> you don't want to know :}
[22:13] <Sp4rKy> oups :p
[22:13] <Sp4rKy> Lutin: stop sleeping and add mysql feature to dad :p
[22:14] <Lutin> better wait for the comments to be merged in MoM, if it ever happens
[22:14] <\sh> if it's not a database, but plain text like sqlite or xml based...and the data is destroyed...hmmm....
[22:15] <\sh> destroyed like in "rm -f comments.txt"? or more like cp /dev/null comments.txt... or something like "the server is dieing...not fast but"
[22:16] <Sp4rKy> like rm -f dad.dunnewind.net ...
[22:16] <\sh> oh...
[22:16] <Lutin> (and -r , otherwise it wouldn't be fun)
[22:16] <blueyed> StevenK: Do you remember why the >= 1080 version for kbuild has been added to the B-D in virtualbox-ose? I want to forward that to debian, it's the only diff currently.
[22:16] <\sh> dedicated server you say? with a rescue or remote console from the provider?
[22:17] <Sp4rKy> \sh yep
[22:19] <\sh> Sp4rKy, 1. ask your provider if his system is safe...most probably an attack to the remote console (e.g. peppercon (today it's raritan) eRIC cards have an embedded linux on it, very unstable and not secure) ... I don't think you rent good hardware from the good HP people with IlO
[22:19] <\sh> 2. change your provider ,-)
[22:19] <Sp4rKy> ^^
[22:20] <Sp4rKy> i'll ask the provider tomorrow
[22:20] <Sp4rKy> anyway, i guess one of the people with rights have done some mistake yesterday / this morning
[22:20]  * RainCT is about to throw his printer through the window XD
[22:20] <Sp4rKy> ^^
[22:21] <\sh> Sp4rKy, "people with rights"? I'm not sure, if I want to use sources from this server anymore
[22:21] <Sp4rKy> \sh 2 person, me and Adri2000 :)
[22:21] <Lutin> \sh: this meaning, the sysadmins
[22:22] <\sh> Lutin, sysadmins don't do mistake, they destroy with purpose or because the fingers were faster then brain ;)
[22:22] <Sp4rKy> what i called mistake :p
[22:24] <RainCT> arghhhh. the damn printer configuration had switched by itself to "network printer", and I've been 20 minutes trying to figure out why it doesn't print ^o(
[22:24] <Lutin> \sh: haha :) hope it'd be true
[22:28] <\sh> Lutin, hopefully...if not, there is a third admin...and then it's exciting ,-)
[22:28] <Sp4rKy> \sh error found
[22:29] <Sp4rKy> \sh not a security whole
[22:29] <Sp4rKy> just a whole in my brain :)
[22:29] <\sh> Sp4rKy, phew...layer 9 problem then...just in front of the keyboard ,-)
[22:29] <Sp4rKy> yep
[22:29] <Sp4rKy> during upgrade of the rsync processes
[22:30] <Sp4rKy> i forgot to add an exclusion over the dad directory
[22:30] <Sp4rKy> so it has been deleted during the sync
[22:30] <Sp4rKy> %s/whole/hole/g
[22:36]  * Sp4rKy goes to sleep
[22:36] <Sp4rKy> good night guys
[22:36] <Sp4rKy> (and sorry for my stupidity)
[22:37]  * somerville32 waves.
[22:37] <Lutin> Sp4rKy: 'night :)
[22:37] <Sp4rKy> 'night
[22:40] <FisherGirl> hi bersace
[22:42] <bersace> hi
[22:43] <FisherGirl> how are you?