[00:01] * cheguevara kindly asks for review of http://revu.tauware.de/details.py?package=kcoloredit-kde4 [00:05] cheguevara: have you looked at the lintian and linda warnings ? [00:05] yeah [00:05] all bogus [00:05] newer-standards-version 3.7.3 (current is 3.7.2) <-- isnt exactly bogus [00:06] i havent verified the rest [00:06] ahh wait [00:06] the server is wrong :P [00:06] i read that backwords [00:06] right i thought you had .2 [00:06] :) [00:07] is there a reason you have cdbs makefiles in the debian/tree ? [00:08] its how all kde4 packages are I believe [00:08] Riddell would know better [00:08] no, *some* where in gutsy because it wasent in cdbs in gutsy yet, but hardy includes those [00:09] and you also have some in the debian/cdbs tree that arent even used, looks like you only use kde.ml [00:09] the kde 4 kde.mk file isn't in cdbs [00:09] kde.mk* === ember_ is now known as ember [00:09] imbrandon: hardy doesn't have all of them yet (but it does have kde.mk) [00:09] Riddell: it looks like its the old one /m looks [00:10] imbrandon, cmake.mk should be used as well [00:10] right i see its refrenced in the kde.mk [00:10] hrm [00:12] cmake and kde are both in cdbs, Riddell is that a diffrent kde.mk and cmake.mk ? [00:12] imbrandon: yes [00:13] kde 4 has an entirely different build system to kde 3 [00:13] hrm seems like they should be renamed to debian/cdbs/kde4.mk then to avoid confusion [00:13] Riddell: i know that [00:13] but i thought the mk file was smart enough [00:14] we don't want to rename it, that would be unnecessary diff from debian [00:14] ahh it was -0ubuntu1 i assumed it wasent in debian [00:14] but main ones are [00:14] main kde 4 packages that is [00:15] in experimental [00:15] cheguevara: is this package in debian ? [00:15] no [00:15] no [00:15] umm then ..... /me is confused [00:16] how would it be a diff from debian if its not in debian ? [00:16] kdebase, kdelibs, etc are in debian though [00:16] right [00:16] and its kinda strange to use diff names for .mks across different kde 4 packages [00:16] because the packaging he's using comes from our main kde 4 packages, and that comes from debian [00:16] ahh i see now [00:16] ok [00:18] cool ok other than that looks good to me, let me poke one last thing then i'll advocate [00:18] cheguevara: ^^ [00:18] imbrandon, cool, thanks [00:21] ping nixternal [00:22] yo yo pete [00:22] howz it going [00:22] so just saw your blog about kde4 [00:22] can i try rc2 on gutsy? [00:22] working on a java project that is whooopin' my arse [00:22] is it easy? [00:22] oh [00:22] yes you can use rc2 on gutsy [00:22] easily? [00:22] howto anywhere [00:22] kubuntu.org [00:22] it's 0:22 and I'm a little beat [00:23] thanks [00:23] under the release announcement [00:23] should be one of the top stories if it isn't the top story [00:25] thanks [00:25] got it [00:25] just been writing a howto on maemo and scratchbox [00:25] :) [00:29] does that get dolphin too? [00:46] Im packaging a python program and is pysupport better than pycentral or it doesnt really matter or the other way around [00:50] I prefer pysupport [00:50] I like pycentral [00:51] I think it really doesn't matter so much which you choose [00:51] anybody ever tried to use pbuilder on a mounted drive? [00:51] Hmm, guess its pycentral, as pysupport is not working :) [00:52] txwikinger, You kind of have to :P [00:54] somerville32: :P [00:54] harrisony: The only useful argument I've ever seen between the two is that pycentral allows you to specifically exclude some directories from byte-compilation at install-time (but this was in the past, so pysupport may have caught up) [00:54] I get an error when Iuse it on a sshfs mounted drive [00:54] pysupport is cleaner in my mind [00:56] pysupport works now, so i guess its that :) === DarkMageZ_ is now known as DarkMageZ [01:01] err [01:02] what do you add to debuild -S to make it include the orig.tar.gz [01:03] -sa [01:09] woa. tracker config applet [01:16] can i get someone to look at this and tell me why pbuilder isnt building me a deb i used debuild -S -sa and then pbuilder-dist hardy ../*.dsc [01:16] http://pastebin.ca/819545 [01:17] harrisony: it looks like it worked [01:17] harrisony: where are you looking for the .deb [01:17] ls .. that has the orig.tar.gz and the changes files but no deb [01:17] Oh wait [01:17] stupid me [01:17] hahahahah [01:18] sorry for got to look in ~/pbuilder [01:18] There it is hehe [01:24] * harrisony makes first revu upload [01:31] oops, uploaded the wrong version of the package [01:31] harrisony: parcellite? [01:32] persia: yep [01:32] harrisony: Are you a member of contributors to Ubuntu universe? [01:33] imbrandon, you still around [01:33] persia: yep [01:33] harrisony: Odd. The package got rejected. Usually that's a keyring issue. [01:34] persia: i did change my gpg key 2 days ago [01:34] harrisony: That might be it. Is the new key in LP? [01:34] persia: yea [01:35] * persia syncs the keyring, just in case [01:36] persia: did you go to bed? [01:36] LaserJock: For a bit: I needed to retrieve my Zaurus. [01:40] harrisony: 3A161F13? [01:40] persia: yep [01:51] harrisony: Imported. Unfortunately, I don't seem to be cool enough to delete your packages from the incoming directory, so it might need someone else before you can upload. [01:51] persia: thanks, and ahh, i see [01:52] cheguevara: yea [01:52] cheguevara: i had to reboot [01:52] imbrandon, cool, just wanted to say i uploaded a new revision [01:52] imbrandon: Can you delete from /srv/uploads on revu? [01:52] 'cause Riddell fount some stuff [01:52] persia: yea, why ? [01:53] imbrandon: parcellite needs to die [01:53] k one sec [01:53] DIE!!! I TELL YOU DIE!!!!!!!! [01:53] cheguevara: You'll get the best quality package if you have lots of different reviewers. Best to ask for someone new, rather than checking back with the person who reviewed the package last time. [01:54] persia: just trying to get people that know about kde packaging most of the time, ie Riddel 'cause some kde related things [01:54] persia: done [01:54] cheguevara: Understood, Still, more eyes is better, and there's bunches of things that aren't KDE that are easy to miss :) [01:54] imbrandon: Thanks. [01:55] harrisony: Try uploading now. [01:55] cheguevara: then ScottK hobbsee and others as well as myself are kde people :) [01:55] harrisony: be sure to rm *.upload localy first too [01:55] cheguevara: apachelogger also, and a very active reviewer. [01:55] yep i always get apachelogger to review my uploads [01:55] persia and imbrandon: thanks [01:55] np [01:56] didnt apachelogger have surgery [01:56] or something and was in hospital [01:56] bbiab , videocard issues [01:56] but yeah kcoloredit-kde4 is there for review :) [01:58] cheguevara: You've modified the upstream tarball without a get-orig-source rule. This means it's hard to reconstruct. Please add such a rule. [01:59] hmm, and why is the upstream tarball modified? [01:59] LaserJock: licensing from SVN. Unfortunately necessary. [02:00] eww [02:00] LaserJock: Why? Better than a SVN snapshot, no? [02:01] yeah, but messing around with licensing isn't nice [02:01] persia, do you have an example rule please [02:01] or is it just a @wget [02:03] cheguevara: https://wiki.ubuntu.com/PackagingGuide/Basic#ChangingOrigTarball has a few examples for repacks. Add additional steps as required. In your case, I'd recommend adding a watch file, and starting with a uscan call. [02:03] persia, is it really worth the effort? because RC 2 of all KDE will be out pretty soon and tarball won't have to modified anymore [02:04] i mean RC 3 [02:04] cheguevara: depends on whether you think it will get through revu before RC 3 is out. Not many will advocate without checking your upstream tarball, and if it's known modified, without at least some description of the process to create it. [02:04] Is anyone working on the u-u-s queue? [02:05] somerville32: Several people. Why? [02:06] persia, i already got one package through revu with the same thing (a COPYING file) added + plus Riddell said it was fine to just modify it [02:06] I don't mind doing it though, if you think its a good idea :) [02:06] persia, More specifically, is anyone working on the u-u-s queue at the moment? If there are, I'd stay up a bit incase they get to my items and if not then I'll go to bed. [02:06] cheguevara: You got lucky, and Riddell would be one of the "Not many" mentioned above. [02:06] *than [02:07] somerville32: Go to bed. The queue is currently at around 9 hours since the bug was last touched. [02:07] cheguevara: you should at least document it somewhere, at a minimum [02:07] its in the debian/changelog [02:08] cheguevara, Put a note in readme.debian or smething [02:08] * Upstream tarball modified to include copyright files from svn [02:08] cheguevara, Yes but the changelog will get populated and that note might be harder to spot later on. [02:09] cheguevara: That you modified it is in debian/changelog. Policy says that modified orig.tar.gz must be described in debian/copyright, and that packagers may optionally provide a get-orig-source rule rather than a shell script in debian/copyright. Whether you have get-orig-source or not, you want a watch file. [02:09] and you should say specifically what files where changed [02:11] right [02:11] so add a watch file and put the changed files in copyright? [02:12] cheguevara: That's the quick & dirty way to be policy compliant. [02:12] (which might be fine, given that RC 3 is out soon). [02:13] is there good example of a watch file somehwere as well [02:13] *somewhere [02:14] or is it just version=x and url on the next line [02:15] plus the stuff from ChangingOrigTarball [02:15] cheguevara: https://wiki.ubuntu.com/PackagingGuide/Recipes/DebianWatch is an overview. man uscan for details [02:16] thanks [02:16] also got http://revu.tauware.de/details.py?package=kmldonkey-kde4 [02:33] imbrandon: pong [02:38] persia, re-uploaded kcoloredit [02:46] gouki: heya [02:47] * Hobbsee waves [02:47] * Fujitsu waves. [02:47] Hello Hobbsee :-) [02:48] Hi bddebian, imbrandon, Hobbsee. [02:48] Heya Fujitsu :) [02:48] heya Fujitsu, bddebian, imbrandon [02:48] hey /names [02:49] heya all [02:49] hi Hobbsee [02:49] heya LaserJock! [03:14] hmm, Georgia? [03:14] eh? [03:15] imbrandon said he changed his font to Georgia [03:15] yea all but my mono spaced font is georgia now [03:16] i love that font, and my mono spaced one is Dejvu Sans [03:16] I use Calibri for all but the fixed width, which is Consolas [03:17] Those are Vista core fonts, aren't they? [03:17] not that i'm aware [03:18] they are probably msttfonts because i use them both on windows too though [03:18] Calibri would be the Office 2k7 interface font. [03:18] ahh i thought you ment mine [03:19] yes, they are core Vista fonts AFAICT [03:19] crimsun: I do the exact fonts [03:19] calibri is quite awesome [03:20] If only pbuilder told me how much it needed to download left before i can build this package [03:20] jcastro: But it isn't free to distribute? [03:20] I don't believe it's Free. [03:20] StevenK: I am pretty sure it is not. [03:21] I am actually kicking the tires on the Liberation ones right now [03:21] jcastro: Tut tut. :-P [03:21] Liberation is pretty nice. [03:21] yeah, they're not bad at all [03:22] I've been digging through fonts ever since Kees's post [03:22] * imbrandon dident see kees post [03:22] blog or ML ? [03:22] (http://www.outflux.net/blog/archives/2007/12/12/search-for-a-crisp-monospace-true-type-font/) [03:22] * imbrandon looks [03:22] crimsun: that kinda messed me up [03:23] I must have done something wrong [03:23] LaserJock: The code just doesn't like the lack of ponies, sorry. [03:23] :P [03:23] really i just love the numerals in the MS TT Core font Georgia, if i could have another font for the letters and the numerals Georgia it would rock [03:34] imbrandon, the "W" is a bit funy [03:34] StevenK / jcastro / crimsun : see how it blurs real bad in the blogpost ( but not most anywhere else where georgia or mono is used ) [03:35] like the words "hinting" and "lines" on the last sentance in the blogpost [03:36] cheguevara: heh thats Georgia ( I assume you mean the "W" on the program interfaces ) [03:36] yeah :) [03:46] imbrandon: hmm, but you like the serif font everywhere? [03:46] yea [04:24] interesting, just saw an OLPC commercial on TV [04:25] LaserJock: Ponies! [04:27] LaserJock: http://www.youtube.com/OLPCFoundation [04:28] Hmm, im trying to build a package for this python application but it wont run and i think its a bug in the program [04:28] can i get someone try install the program and tell me if its a bug in the program or me === asac_ is now known as asac [04:46] hmm, I wonder if this laptop harddrive Load_Cycle thing is really an issue [04:47] LaserJock: Yes and no. Depends on the specific hardware. It's a moving part, so can wear out. [04:48] LaserJock: yeah it definitely shortens disk life, but to what extent, I don't know. [04:48] in Ubuntu Daemon's blog it says I shouldn't have more than like 90-160 cycles/day [04:48] LaserJock: I have a mobile terminal (laptop in a high-shock environment) that I put on -B 1 and it has 4.5 million load cycles [04:48] my laptop is getting 3k [04:48] LaserJock: it's "supposed" to last 600,000 load cycles [04:48] LaserJock: yet it still works. Be the judge :-/ [04:49] jdong: what do you mean by -B 1 [04:49] It's a MTBF sort of thing. Due to the number of DOA devices, the tail is fairly long. Backups are good. [04:49] LaserJock: most aggressive power mgmt setting [04:49] LaserJock: basically park the head as soon as activity is done [04:49] ah [04:50] what the blog article complains about [04:50] jdong: Do you also have aggressive caching, or do you restart whenever anything happens? [04:51] persia: just generic laptop-mode, it doesn't feel terribly aggressively cached [04:52] jdong: Ah, so maximum park frequency :) [04:53] yeah, because I'm too lazy to tune it [04:53] my rationale is, the parking makes the data safer when the machine gets bumped, which happens a lot [04:53] Well, my Load_Cycle is at 634,000 mark, and my smartctl tests now fails. :-( [04:53] minghua: I've had 5 maxtors fail on me within 4 months of purchase, none of which were subjected to any power management settings :) [04:53] I don't think there's a strong load_cycle to disk death correlation [04:54] jdong: I know, I know, I've had horror stories with IBM Caviar disks as well. [04:55] I'm not saying my Load_Cycle count is the reason of the test failure, but I suspect they are related. [04:55] Well, I'd suggest that the higher the load_cycle, the higher the chance that the little arm breaks, but the chance may remain completely miniscule. [04:55] it might be a small contributing factor... [04:55] (I have been running Debian on that laptop, by the way.) [04:56] Hmm. I wonder what else is wrong with my harddrive, then. [04:57] random chance.... [04:57] It's an uneasy feeling to know you laptop hard disk can fail anytime. [04:57] I'm up to 467059 [04:58] and a short scan worked fine, but the indepth one seemed to fail [04:58] I suppose compiling a lot will affect it [04:59] Like persia said, backup is always good. :-) [04:59] yeah [05:00] I've been doing that more often lately [05:00] I hope it doesn't die during christmas, I'd be upset [05:00] LaserJock: Add a heap of RAM and compile in cache :) [05:00] although with no sales tax in Montana it might be a good time to pick up a harddrive === harrison1 is now known as harrisony [05:03] A 90% sale would offset the sales tax, so it's never a factor to consider for me. [05:06] is it worth getting a 7200rpm hard drive for laptops? [05:07] well, what's important to you? [05:07] frankly, battery life is to me, so I don't care if it's slower [05:07] well, a pbuilder *not* taking over 1min to unpack would be cool [05:08] LaserJock: Use sbuild, then [05:08] cowbuilder pbuilder with copy on write [05:08] LaserJock: sbuild helps. more RAM helps (bad for battery). Solid-state disk helps. [05:09] I've never managed to get cowbuilder working to my satisfaction. [05:09] sbuild with keescook's lovely script just works [05:10] StevenK: doesn't that take LVM? [05:10] In fact, slangasek, keescook and I were having a talk about improving the script at AllHands [05:10] LaserJock: Right. But you don't have to set your whole machine up as LVM [05:11] LaserJock: Yes, but you can do a fair bit with LVM only for that. I have all my sbuild stuff in a 20GB VG, and can run two simultaneous builds against sid, hardy, or gutsy. [05:11] (mind you, I can't build wxwidgets2.8) [05:12] I have one 250Gb VG, but my machine uses LVM for everything [05:13] would be nice if pbuilder-uml was fixed, has a broken dep. on rootstrap [05:13] because pbuilder-uml sounds neat [05:25] Could anyone suggest why "ftp://ftp.gnome.org/pub/GNOME/sources/gopersist/0.1/gopersist-?_?([\d+\.]+|\d+)\.tar.* debian uupdate" is failing to match in a watch file? [05:33] persia: What does ?_? mean? [05:34] minghua: I believe "-?_?" means zero or one '-' characters followed by zero or one '_' characters. [05:35] persia: I see now. That a rather complicated regex... [05:36] it's appears almost to be a sf.net regex for watch files [05:36] its gopersist with - and/or _ followed by zero or more numbers with decimals, followed by a number, followed by .tar with anything afterwards. [05:36] Where "number" is any number of digits [05:37] persia: Can you enlighten me about [\d+\.]+ as well? I don't understand why + is in the middle. [05:37] Flannel: Right. Somehow it isn't matching anything on ftp://ftp.gnome.org/pub/GNOME/sources/gopersist/0.1 , and I don't understand why. [05:37] persia: thats because / isnt _ or - [05:37] minghua: One or more sets of digits and decimals, followed by one or more digits. [05:37] ftp://ftp.gnome.org/pub/GNOME/sources/gopersist/0.1/gopersist-(.*)\.tar\.gz [05:37] isn't enough? [05:37] ember: .* is not a good idea in perl [05:37] persia: Why are they in the [] brackets then? [05:38] Oh, right, [ ] isn't right [05:38] .* in Perl is greedy by default [05:38] It's better to use a character class [05:38] minghua: [baz] means any of 'b', 'a', or 'z' [05:38] what those brackets should be is [0-9.] [05:39] Flannel: Surely you mean \. [05:39] Heh heh [05:39] Anyway, why is "0-9" better than "\d"? [05:39] I don't think you need to escape . in []. [05:39] persia: It isn't [05:39] persia: \d can't be used inside of [] [05:39] ftp://ftp.gnome.org/pub/GNOME/sources/gopersist/0.1/gopersist-([\d.]+)\.tar\.gz [05:39] Flannel: Works for all my other watch files :) [05:39] But then again, RegExp is not my native language... :-P [05:39] ember: [\d.] isn't right [05:40] (\d|\.) [05:40] would be what that is properly [05:40] or rather (\d+|.) [05:40] [\d\.]+ [05:40] StevenK: Escaping inside of square brackets? [05:40] StevenK: So just drop the final [\d]+ ? [05:41] I'm digging through perlre [05:41] There is no escaping inside of square brackets [05:41] regex is evil [05:41] Flannel: Yes. It needs escaping there too. [05:41] both of those \ are literal \s [05:41] ember: Only because there are so many flavours [05:41] So debian/watch uses the Perl version? [05:41] Flannel: No, they aren't. I have perlre in front of me now [05:42] s/version/flavor/ [05:42] Flannel: I know \d inside square brackets works, so I'm sure I don't agree with that. [05:42] . isnt [05:42] \d works [05:43] minghua: Yes. Debian watch is interpreted by uscan, which is in perl. Amusingly enough, you can execute almost anything in a watch file if you are careful. [05:43] special characters inside of [ are \ ] ^(when at the beginning) and - [05:43] . isnt, nor is *, etc [05:43] steven@liquified:~% echo 0000 | perl -ne 'if (/[\d]+/) { print "Flannel is wrong\n"; }' [05:43] Flannel is wrong [05:43] \d works . doesnt [05:43] you dont escape . inside of square brackets [05:44] * persia does, successfully [05:44] of course [\.] will work, but it'll also match \ [05:44] Flannel: But [.(that other thing) doesn't work. [05:45] \. thats ecaping the ., but its a regular ., so it may still work, but I wouldnt bet on it working everywhere [05:45] Flannel: Sure. I only expect it to work that way in perl. [05:45] Ah [05:45] POSIX has \ not being a special character inside of square brackets [05:46] so it depends on whether youre using POSIX or PCRE [05:46] Flannel: Right. For sed, awk, etc. You'd have been correct, except we should have been using $ and $ for the match string :) [05:46] persia: The "+" in bracket in your original pattern still doesn't make any sense to me. [05:47] minghua: Thats because it shouldnt. He meant one or more of \d, but its inside of brackets, so it doesnt work like that [05:47] minghua: I believe it is a literal '+'. I'm not sure. That regex was generated by watchwiz. [05:47] persia: I read it as a literal +, too. [05:48] Its treated as a literal, whether thats what you want or not... [05:48] Flannel: It oughtn't break anything, right? [05:49] persia: it'll only give you a false positive [05:49] * persia would be happy with any positive match, even false [05:50] What are you trying to match on? [05:50] ftp://ftp.gnome.org/pub/GNOME/sources/gopersist/0.1/gopersist-0.1.1.tar.gz [05:50] (or whichever version they put there tomorrow) [05:51] gopersist[-_](\d+\.?)+tar\.gz [05:51] that's how I'd write it [05:52] If you don't mind false positive, what is wrong with ([\d.]+) [05:52] ? [05:52] Flannel: That doesn't match 0.1.1 [05:52] persia: Why not? [05:52] Flannel: Well, it does, but it matches in three chunks. I need a single chunk (as I'm not writing the perl code that uses it) [05:53] minghua: I might try that (with the missing \ restored [05:54] Oh, you need to match the whole file number as $1? [05:54] "ftp://ftp.gnome.org/pub/GNOME/sources/gopersist/0.1/gopersist-([\d\.]*)\.tar.*" doesn't work either :( [05:54] Flannel: Yep. [05:54] persia: So, well, you could do this: [05:55] * persia tries escaping the / characters [05:55] gopersist[-_]((\d+\.?))+\.tar\.gz [05:55] persia: Curious. [05:55] That'll put the whole thing in $1, then you'll have $2, $3, $4 ... for the pieces [05:56] Flannel: I'm writing for interpretation by uscan. I'm not able to do cool nifty thngs, unfortunately (despite you being mostly correct). Further, I think you meant gopersist[-_]((\d+\.?)+)\.tar\.gz [05:57] Isnt that what I... oh, no its not, but yes, thats what I meant [05:58] persia: and you want watch files for everything? ;-) [05:58] Although this would be useless for the intended purpose, "ftp://ftp.gnome.org/pub/GNOME/sources/gopersist/0.1/gopersist-(.*)" doesn't match either, which I find very odd. [05:59] LaserJock: Yes, so we can keep track. Most just work. This one is annoying for some reason. [06:00] But yeah, I'd just move to character classes. [06:00] persia: Do you need to escape anything? [06:00] As in, escape for the parser [06:00] Flannel: I tried escaping the '/' characters, but then it couldn't figure out the protocol. [06:00] * persia goes off to read uscan source [06:03] persia: Maybe try http:// protocol? [06:04] minghua: Interesting idea. Doesn't match debian/copyright (but that can be fixed). Also means I can separate the URL from the regex, making it easier. Thanks. [07:12] Hi all! === \sh_away is now known as \sh [07:17] <\sh> moins [07:23] woah, crimsun's got a lot of uploads [07:23] 10x as many as I do [07:24] c [07:24] Way cool, I'm still in the top ten [07:24] wrong tab [07:25] shesh, dholbach's got 40 times as many as me [07:25] LaserJock: For big counts, chase NBS, watch files, or source-maintainer-mangling. Usually pretty fast (although I like to make the watch-files also lintian/linda clean) [07:26] LaserJock: Is that ever, or Hardy? [07:26] ever [07:27] For hardy, I think TheMuso has the lead [07:27] LaserJock: Then I suspect I have a lot more than you do as well [07:27] persia: Not for long though. [07:27] I'm doing some -changes greping [07:27] And really, I don't care about upload stats. [07:27] StevenK: umm, yeah ... [07:27] TheMuso: You're high enough you might make top-ten for hardy: seems to be a big gap between around 100 and around 250. [07:28]