/srv/irclogs.ubuntu.com/2008/12/08/#ubuntu-motu.txt

RAOFRight.  Which means I should upload the new evolution-sharp to Jaunty, too.00:00
* jdong nods00:00
RAOFSadly I can't do that through Experimental; the new upstream fails to build against < e-d-s 2.24.00:00
RAOFEven though it says it should on the box. :(00:01
=== vorian is now known as heHATEme
jdongkees: I must be bored out of my mind; I'm actually rewriting all my rcS and rc2 scripts as upstart jobs, without using lsb-functions at all01:30
TheMusojdong: Yes, you must be bored.01:41
jdongTheMuso: I'd be willing to bet money this would make bootup thrash like hell and not terribly useful until I get a SSD :)01:41
TheMusoimbrandon!!02:01
keesjdong: ah you at uds? it'd be great to see the work. i know both keybuk and kirkland are very interested in doing that kind of thing02:33
jdongkees: no, unfortunately I am not02:44
jdongkees: my first go-through will likely be a hackjob that involves extensive copy-pasting from our init system with my best guesses at the dependency relationships :)02:44
jdongI just want to get an understanding of the challenges with a fully parallelized boot02:45
jdongif it's not a horrible unfinishable mess I'll probably send something out to the mailing list02:45
jdongI've BARELY got to S37 :)02:47
* jdong wonders if he can write a mechanical python hook to generate wrapper upstart event jobs based on installed init.d scripts02:48
keesheh cool.02:48
jdongI oddly recall starting to write such a thing two years ago, in fact!02:49
* jdong greps his ~/src02:49
=== heHATEme is now known as vorian
=== hyperair1 is now known as Guest89158
=== Guest89158 is now known as hyperair
jdonghttps://code.edge.launchpad.net/~uphackers/uphack/uphack-tools02:51
jdongaha!02:51
jdongupconv/uphack.02:51
jdongis it sad that I've done so many of these crazy things I don't know if I conceived it in a dream or actually wrote it?02:51
* jdong tries to think "What plane" mentioned in revno 6....02:52
jdongwas that what I was doing over spring break?02:52
psusiif a package generates conf files after it is installed, is there any way for dpkg to keep track of that so they can be removed if the package is purged?03:04
psusiI'm wondering about /var/lib/gconf/defaults/*... dpkg does not show the files as having come from any package, but gconf2-common created the directory with no files in it... I assume they must have been generated somehow after install?03:05
jdong*HOLY CRAP*03:07
jdongkees: it booted!03:07
jdongI am not convinced it's any faster though03:07
jdongand TODO: figure out how to shut it down :D03:07
jdong25s in vmware....03:10
* jdong is almost curious enough to try this natively03:10
psusijdong: what are you playing with now? ;)03:12
jdongpsusi: upstart03:20
jdongpsusi: a quick and dirty python script that generates dummy upstart jobs for each rcS.d-rc2.d script03:21
psusiyou mean you are making an upstart job for each individual script instead of just having one job that runs /etc/init.d/rc?03:34
jdongright.03:34
psusiwhy?03:34
jdongwith a basic set of heuristics for job dependencies.03:34
jdongparallelized boot03:34
psusidoesn't rc already have an option to do that?03:34
jdongpsusi: it doesn't seem to be as parallel03:35
psusiohh.. I guess it only runs jobs with the same Snn level in parallel...03:35
psusiI see now why you are surprised that it worked ;)03:35
jdongpsusi: lemme generate a quick dot diagram of my dependency graph urrently03:35
jdongpsusi: http://jdong.mit.edu/~jdong/upstart-dep.png03:36
jdongpretty neat looking03:36
ScottKjdong: Now that Debian has dependency base boot sequencing done with sysv init's, how much is this conversion really likely to buy us?03:37
jdongScottK: I was unaware debian has this03:37
jdonghow does that fit into our plan to completely go upstart though?03:37
jdongthis for me is just an experiment in what an upstart-booting parallelized system buys us03:37
ScottKjdong: I'm wondering why we're doing that.03:37
jdongwell upstart represents job relationships in a better way IMO03:38
jdongit fits the model of the modern Linux machine better than a bunch of start-stop scripts.03:38
ScottKjdong: http://lists.debian.org/debian-devel-announce/2008/11/msg00007.html03:39
psusiI have often wondered whether paralellizing the boot scripts might cause more slow down that it makes up for, due to all the tasks competing for resources at once03:39
jdongpsusi: I think it must.03:39
ScottKjdong: Sure, no doubt it's better, but is it enough better to be worth the additional difference between Debian and Ubuntu.03:39
psusijdong: wouldn't each job finish faster if it wasn't fighting the others for access to the cpu, ram, and disk IO?03:41
jdongpsusi: not really when the jobs aren't really bound by the same resource.03:41
psusiI mean theoretically the only way you get benefit from parallel jobs is if each job is only using a subset of the available resources, so each job will use the resources that the other jobs aren't.... if they are competing for the same resources though, it slows things down03:41
jdongthe former is the case according to my bootchart03:42
psusiso you almost need a way of scheduling the jobs that uses information about what resources they use so it only parallelizes jobs that don't conflict for the same resource03:42
psusilike if one job is IO bound and one is CPU bound, then run both at once03:42
jdongwell competing for disk right now is the biggest problem.03:42
jdongI could care less if they compete for CPU or RAM03:42
psusibut you don't want to run two jobs at once that are both IO bound03:42
jdongI think a bit of aio scheduler hackery can work around the IO contention though03:43
psusieh?03:43
jdongpsusi: sysv: http://jdong.mit.edu/~jdong/macbook/bootchart-sysv.png03:43
jdongupstart: http://jdong.mit.edu/~jdong/macbook/bootchart-upstart.png03:43
jdong27s vs 22s03:43
psusiif both jobs are IO bound, wouldn't it be best to just run them sequentially so that they aren't causing the head to keep seeking back and forth?03:44
jdongstill relatively untweaked with mechanically-generated rules.03:44
jdongthe 67 . /lib/lsb/init-function.sh calls are probably representing significant overhead too03:44
jdongpsusi: the AIO scheduler with large timeslices can alleviate a lot of the seeking though.03:44
jdongpsusi: and frankly single tasks during bootup seek crazily enough03:45
jdongwe don't really have any guarantee that each task alone doesn't thrash.03:45
jdonghttp://jdong.mit.edu/~jdong/macbook/hardy-upstart-defragged.png03:45
jdongthat's an optimized run with readahead/boot listed files rewritten to disk03:45
psusitake readahead-list for example.. it looks like right now you block the remaining tasks until readahead is done, because you don't want them trying to read bits before readahead gets them, causing seeking03:46
psusiideally you want to start other jobs that are more cpu bound while readahead runs so you can keep both the disk and cpu busy03:46
psusithe aio scheduler? is that a new io scheduler?03:46
psusiI'm confused as to what aio has to do with the elevator03:47
psusijdong: ideally you want the files readahead is fetching to be all sequential near the start of the disk... or at least modify readahead to be able to keep a cached copy of all of it somewhere like windows' prefetching does03:48
jdongpsusi: (1) that depchart is not up to date; there ARE a few other things that I have moved up to be parallel with readahead03:49
psusijdong: being able to pack the readahead files sequentially at the start of the disk is one of the reasons I'm trying to rescue e2defrag03:49
jdong(2) Yes, I'd like for all the boot files to be near the start of the disk and sequential.03:49
jdongyou don't want to see my symlink farm method for forcing that with a tiny 100MB /prefetch partition :P03:49
psusiwhat would be nice is if you could have the kernel block the other jobs if they request a block that readahead has not already pulled into cache and wait until readahead gets it without seeking... maybe you could do that with IO priorities?03:50
jdongthat was my next tier of hacks.03:51
jdongyou're getting ahead of me!03:51
psusi;)03:51
jdongionicing and nicing was my next set of master ugly hacks :P03:51
jdongI first want to get this set of jbos correct03:51
jdongstill getting a few races I need to sort out03:51
psusihrm... your max disk throughptu was only 12 MB/s?03:51
jdongrofs and dev/pts mounting not at the right time :)03:51
psusithat seems rather low03:51
jdongit's a laptop on ata_piix emulation.03:51
psusieww03:51
jdongthis can be a LOT faster with a proper computer.03:52
jdongin fact I'm curious enough to try it...03:52
* jdong digs out his production system03:52
psusijdong: dual core cpu?  kind of funny how the graph only shows 50% IO wait time during readahead-list03:52
jdongyup03:53
psusiI wonder how much it will help to use e2defrag to pack the files on readahead-list in order at the start of the disk03:55
psusiI need to finish getting that reintroduced to the repository03:55
jdong:)03:55
psusiI finally got around to creating a project for it on lp and checking it into bzr03:56
psusihrm... I wonder why you still have a good deal of disk IO after the readahead is done... looks like it is done by modprobe03:57
jdongpsusi: modprobe blocks hard in the kernel at several points03:57
jdongwhich inflates bootchart03:57
jdongok, so 34s stock boot no tricks....03:57
jdong*unpacks event.d*03:58
jdong27s upstart04:02
* psusi shakes his head at his WD raptors and their WAAAAAY off standby timers04:03
* ScottK-laptop thinks anyone who uses WD hard drives deserves whatever they get.04:07
ScottK-laptopnellery: I just sent you kind of a nasty note about your milter-greylist merge.  I'm not as annoyed as the comment in the bug probably sounds.04:07
lidaobingplease help review iptux 0.4.2-0ubuntu1(new package): http://revu.ubuntuwire.com/details.py?upid=4186, thanks04:08
nelleryScottK-laptop: Hi, just read it04:08
nelleryI'll be sure to ask the last merger next time.  Thanks for the heads up.04:08
ScottK-laptopnellery: Also, since Debian moved to quilt, I think it's better our change is in quilt too.  FYI for next time.04:09
ScottK-laptopnellery: Note that once we get past roughly DIF, merges are pretty much free for all if they haven't been merged at least once in the cycle.04:09
ScottK-laptoplidaobing: Is this the same iptux sitting in Debian New?04:10
nelleryScottK-laptop: I'll definitely look out for that in the future, thanks again04:11
ScottK-laptopNo problem.04:11
lidaobingScottK-laptop, Debian new? let me check, I think I still waiting for RFS04:11
psusiScottK-laptop: why do you say that?  don't like high performance hardware?  I've been messing with lm-sensors and laptop-mode lately and it seems these things have very strange ideas of when they should spin down... one of these days I need to write a kernel patch to have it manage the standby of disks properly instead of leaving it to them04:12
lidaobingScottK-laptop, I can't find it in Debian new queue, http://ftp-master.debian.org/new.html, any more information?04:12
ScottK-laptoppsusi: Excepting one hard drive in a laptop that died right after it was in a car in a severe accident, every single hard drive I've had fail that was less than 5 years old in the last 20 years has been a WD.04:13
ScottK-laptoplidaobing: Maybe I mis-remember.  Let me check.04:13
psusiScottK-laptop: wow, that's hard to believe... in my many years of experience WD drives are usually very reliable... though usually not that fast.. you sure you aren't thinking of IBM?  specifically their deskstar series?  or as I like to call them, deathstar04:15
ScottK-laptoplidaobing: I don't see it there now, but I'm pretty sure it was.  I wonder if it got rejected for something.  A lot of stuff got processed through New yesterda.04:15
ScottK-laptoppsusi: Nope.  That's my experience.  The laptop HD that died in the car accident was an IBM, but I think that's the only one of those I've had.04:16
ScottK-laptopNow it's not many hard drives mind you, but it is all of them ...04:16
lidaobingScottK-laptop, no information in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507451, and did not recieve any email for it.04:18
ubottuDebian bug 507451 in wnpp "ITP: iptux -- IP Messenger client for Linux" [Wishlist,Open]04:18
ScottK-laptoplidaobing: It's also possible I misremember.04:21
jdongpsusi: ok I might be cheating now: http://jdong.mit.edu/~jdong/upstart-dep-lazy.png04:51
jdongmoved 70% of the bootup to sleep 10; after GDM :D04:51
psusijdong: eh?04:51
jdongpsusi: kickstart gdm first and then worry about booting up the rest of the system :)04:52
psusidoesn't gdm depend on the rest of the system already being started? ;)04:54
jdongno, the graph shows the boot order relationship04:54
jdongi.e. it's a dirty topsort of the graph04:54
jdongi.e. B's "start on starting A" shows as A->B04:54
psusijdong: what's readahead_desktop?04:55
jdongthe LTSP version of readahead.04:55
jdongit doesn't matter here04:55
psusiI see... you start gdm before things like laptop_mode and and cron... that seems ok04:56
psusijdong: I'm wondering if it is doing readahead on things that gdm or the things gdm starts reads, in which case it probably isn't a great idea to start gdm before it04:56
jdongpsusi: I'm gonna do a control run with no readahead04:56
jdongand then carefully readahead JUST up to the gdm point.04:57
psusijdong: and you know, there are probably some things, like rsyncd, that could be started up after gdm has had some time to initialize and get to a login04:57
jdongpsusi: everything after gdm is (1) sleep 10 (2) ionice -c3 (3) nice 2004:59
=== fta__ is now known as fta
jdong22s05:01
psusijdong: ohh, so you give gdm 10 seconds to start up then start loading everything else with low priority?  after the user already has a login prompt?  nice05:04
psusijdong: and what was the base time on a stock system?05:05
psusijdong: mountoverflowtmp should probably be done before dbus on down05:07
jdongpsusi: around 37s05:08
jdongand yes I am reworking the dep tree still05:08
jdongwhat uses perl during bootup?05:08
jdongstill about 22s stable.05:10
jdongI think I've hit a fundamental limit :)05:10
psusijdong: also it looks like readahead is executed in parallel to most everything else... probably should wait for readahead to finish or the things that would benefit from it can fight with readahead seeking back and forth05:10
psusior ideally maybe use multiple readahead lists for several different stages... readahead stage 1, then boot the parts that use those files while readahead stage 2 runs in the background, then once stage1 finishes, launch stage2 jobs05:12
psusisee what I'm getting at?  maybe take dbus as a good split point... build one readahead list for everything prior to dbus... read that list in entirely first, then start all jobs prior to dbus05:14
psusithen have a second readahead list for all jobs starting with dbus and after, and read that list at the same time as you run all of the jobs before dbus05:14
psusithen start dbus and all after only once the second readahead list is done05:15
jdonginteresting; 34MiB of readahead necessary05:17
psusialso stop_readahead looks like it is run in parallel with many jobs, so it may or may not record files needed by, policykit, for example05:19
jdongpsusi: oh I'm not profiling with upstart enabled.05:20
jdongI have a simulated sysv setup that activates via bootflag, for profiling05:20
psusiahh05:20
jdongsuch a hack :D05:20
jdongjust "defragged" readahead data.05:20
psusiwhat do you think of having multiple readahead stages?05:20
jdonguntarred it really fast, that is :)05:20
jdongwell I'm considering the idea of multiple readahead stages05:21
jdongjust right now it's terribly annoying to get profiled05:21
psusiyea... difficult, but may yield sweet fruit05:21
jdong20s05:21
jdongsignificant difference from rewriting out readahead/boot's files05:22
psusino sense making mountall_sh and networking wait for readahead to finish fetching data that won't be needed until you start cups05:22
psusihehe, now get them to be stored in the order they are read ;)05:22
=== santiago-ve is now known as Guest13204
jdonglol I think I'm gonna call it a night with stupid bootup tricks :D05:23
psusihehe.... I want to see that boot time down to 10 seconds ;)05:24
jdongpsusi: in case you're bored: https://code.edge.launchpad.net/~uphackers/uphack/uphack-tools05:26
jdongthere's upconv which reads in /etc/rc*.d and spits out /tmp/event.d05:26
jdongand depchart which when executed depchart /tmp/event.d | dot -Tpng > foo.png, creates a .png :)05:26
jdongpsusi: I'd be interested to see a SSD bench05:27
jdongoh to bootstrap you should probably keep your existing tty* and make them start on started mountall_sh05:27
jdongotherwise you may find yourself lacking terminal(s) :)05:28
psusicool... I got one for you: https://launchpad.net/~e2defrag ;)05:28
psusieh?  aren't the getty's already started as their own upstart jobs?05:28
jdongpsusi: yes but my magical event.d generator does not generate the special tty jobs05:29
psusijdong: I'm saying I thought the tty jobs already existed in event.d and don't need generated from rc scripts05:29
jdongpsusi: from what I remember, to bootstrap copy the auto-generated event.d files into /etc/event.d, then rm /etc/event.d/rc*05:29
jdongpsusi: and the pre-generated tty jobs depend on "runlevel"05:29
jdongi.e. the rc jobs05:29
psusiI could have sworn the way it was already the runlevel event started the gettys and /etc/init.d/rc 2 in parallel05:30
jdongpsusi: not in Intrepid, they "fixed" that :D05:31
psusilol... why was it "broken"? ;)05:32
psusiI thought it was like that because the gettys were the first and only startup jobs that had been converted to the upstart system from sysv05:32
jdongthat's why I said "fixed"05:34
jdongthe "problem" was if the system was fscking it would still allow you to log in.05:34
jdongand also it would present the login before the hostname was set05:34
psusiohh, I see.... it now starts on stopped rc2... before it started on runlevel 205:35
jdongright05:35
jdongIMO it should start on started rc205:36
jdongand use the service declearation05:36
jdongwith pre-start exec /etc/ ....05:36
jdongI'd like to see rc2 as "started" when it finishes running.05:36
psusimakes sense... that way it waits until after rcS but not on rc205:36
jdongnot "starting" -> "stopped"05:36
siretartjdong: I think I'm a bit biased with that question ;-)07:53
\shmoins09:23
zerwasmoin09:26
pochuhiya09:37
* directhex votes to declare it the weekend again -_-09:38
pochuit's holiday here in Spain :)09:39
smaftoulHi all09:42
\shit's UDS time ,-)09:43
pochuaren't they all still sleeping?09:45
\shlooks like...-6h from europe, right?09:52
directhex.ca is west coast isn't it?09:52
directhexwait, no . there09:52
directhexbut my clock says -8 for LA09:52
\shah west coast..yeah that's a bit more then -6h09:54
Nafallohehe. why not find out where they are first? ;-)09:54
Koon-9h from CET.09:56
smaftouldoes anyone knows where apache sets it's ulimit from ?09:57
smaftoulI set this export APACHE_ULIMIT_MAX_FILES="8192"09:57
smaftoulin /etc/apache2/envvars09:57
smaftoulI have a php file that contains <? system("ulimit -n"); ?> , and I het 102409:58
smaftouldo I need to modify /etc/security/limits.conf ?09:58
smaftoulshouldn't this be documented ?09:58
* directhex stabs ulimit with a spork09:59
NCommanderhey directhex09:59
directhexmorning NCommander09:59
NCommanderdirecthex, I take it your not at UDS?09:59
NCommander\sh, you here?09:59
slytherinNCommander: Just FYI ... the freezes I was seeing on my ibook are almost completely gone after blacklisting rfkill_input module.10:00
\shNCommander: nope...:) I'm not at UDS :)10:00
KoonThe "not-at-UDS" club gathers :)10:00
slytherinKoon: are you keeping watch on pkg-java checkins? some of the maven packages we were planning to work on have entered Debian NEW queue.10:02
Koonslytherin: I looked at it a while ago... I'll check it again10:03
directhexNCommander, not until someone starts paying for my travel costs, no. california is one of the few places which would cost me more than my mortgage payments to visit10:03
NCommandero_o;10:03
=== awmcclain is now known as ethan0
ethan0I'm so sorry for this easy question, but if I have a *_all.deb, I could extract the source and rebuild for ubuntu, right? _all have source included, right?10:04
directhexethan0, wrong.10:05
\shethan0: nope..._all.deb just means, it's architecture independant10:05
directhexethan0, .deb is (usually) never source10:05
ethan0It's a binary package then. Ungh. Sorry, I've been up for much too long.10:06
directhexethan0, a source package comes in the form of a diff.gz, orig.tar.gz, and .dsc10:06
ethan0Yes, of course. Sorry.10:06
* ethan0 needs to sleep10:06
directhexethan0, an _all might be something like, say, a CLI .dll file10:06
directhexactually, <£400 for last-minute flights. it was definitely >£1k when i looked previously10:07
directhexstill, too rich for my blood10:07
smaftoulanyone here apache expert or packager ?10:13
mgdmis there any chance/likelyhood of a backport of libdmtx to hardy?11:09
pochuhow many reverse dependencies does it have?11:10
mgdmit doesn't appear to have very many, though I could be looking in the wrong place11:11
mgdmas far as I can make out it only wants libpng and libtiff11:12
slytherinmgdm: The package does not exist in hardy. Is that correct?11:12
mgdmslytherin: yeah, it only seems to have appeared in Jaunty11:12
pochuthen you should be fine11:15
pochumgdm: report a bug at https://edge.launchpad.net/hardy-backports/+bugs11:16
mgdmI'm just trying to build it just now11:16
mgdmAh, cool11:16
pochumgdm: of course building, installing and testing it will help the backporters to approve it ;)11:17
mgdmI guessed it might :)11:17
mgdmif the package is asking for debhelper >= 7, but Hardy only has 6, is that a major issue?11:34
directhexyes! it causes baby jesus to cry11:35
sebnermgdm: hardy backports have 7 but do you really need debhelper7?11:35
directhexalso, i thought dh7 was ni hardy-backports11:35
=== RainCT changed the topic of #ubuntu-motu to: Masters of the Universe - https://wiki.ubuntu.com/MOTU | Want to get involved with the MOTUs? https://wiki.ubuntu.com/MOTU/Contributing | Jaunty: OPEN. | Grab a merge: http://dad.dunnewind.net http://merges.ubuntu.com | http://qa.ubuntuwire.com/uehs
mgdmSorry, I'm an utter newbie, just trying to build this Jaunty package on Hardy but I don't really know what I'm doing11:36
pochumgdm: enable hardy-backports to build it11:37
=== pochu changed the topic of #ubuntu-motu to: Masters of the Universe - https://wiki.ubuntu.com/MOTU | Want to get involved with the MOTUs? https://wiki.ubuntu.com/MOTU/Contributing | Grab a merge: http://dad.dunnewind.net http://merges.ubuntu.com | http://qa.ubuntuwire.com/uehs
mgdmpochu: OK, I'm trying it, thanks11:38
mgdmOh, I do have debhelper 7 already installed, but it's not in the pbuilder chroot, I suspect11:45
mgdm(does that sound plausible?)11:45
directhexit sounds plausible. pbuilders don't tend to have backports on by default11:45
pochuin English, when you read something out loud, how do you read "e.g.", as "e g" or "exampli gratia" ?11:49
orly_owli say e g11:49
orly_owlAlso, ##english11:49
lagai say "for example". but i'm not a native speaker11:49
phytopiusi would also say for example11:49
orly_owloh yes, you could say that too11:49
mgdmI'd say "for example", too, and I'm a native speaker11:50
pochuthanks you all :)11:50
directhexi say "egg", but i'm a weirdo!11:50
pochulol11:50
directhexnah, "for example" is correct11:50
orly_owlNot on IRC you're not!11:50
pochuand for i.e. you say "that is"?11:51
directhexpochu, aye11:52
pochucool11:52
* pochu is studying for the toefl11:52
lagai probably wouldn't understand it if someone said "exempla gratia" ;)11:54
lagapochu: cool11:54
* mgdm works out what he's doing wrong11:55
pochumgdm: login into pbuilder and look at /etc/apt/sources.list11:57
pochuif you don't have hardy-backports, that's what is wrong11:57
directhexor, even better, use OTHERMIRROR and --override-config11:57
mgdmyeah, I went for the OTHERMIRROR option in the end11:58
mgdmI figured that was more sustainable in the long run than logging in and hacking manually11:58
mgdmyay, it builds and runs \o/12:02
slytheringeser: ping13:09
pmjdebruijnI uploaded my package to REVU fifteen minutes ago, and it's still not visible on the website? what could be wrong?13:23
slytherinpmjdebruijn: is this your first upload to revu?13:24
pmjdebruijnyes13:24
slytherinpmjdebruijn: did you login to revu prior to upload?13:25
pmjdebruijnslytherin: oh crap... I thought I was still logged in from yesterday13:26
RainCTpmjdebruijn: which package is it?13:27
pmjdebruijnlensfun13:27
pmjdebruijndput says it's already uploaded13:27
slytherinpmjdebruijn: wait, I meant if logged in even once. If you had then there seem to be some other problem13:27
slytherinpmjdebruijn: what is the dput command you used?13:27
pmjdebruijndput revu lensfun_0.2.3-0ubuntu1_i386.changes13:27
slytherinpmjdebruijn: you need to upload source.changes13:28
pmjdebruijnoh silly me13:28
* pmjdebruijn goes back to the drawing board...13:28
geserslytherin: pong13:33
slytheringeser: do you have time to review a mail? Sending it to Debian java mailing list. I don't want my anger to get reflected strongly in the mail.13:34
ScottK-laptopslytherin: What happened?13:36
slytherinScottK-laptop: source of library changed between two revisions (not upstream versions), apis missing/changed and hence jbossas4 won't build.13:37
ScottK-laptopLovely.13:37
slytherinScottK-laptop: and this went unnoticed as I am sure everyone assumed that source of svn5660+dak1 must be same as svn566013:38
pmjdebruijnah, there it is13:38
pmjdebruijnI already see I have some work to do13:38
geserslytherin: sure13:38
pmjdebruijnanybody else, willing to check it out? so I can correct several things at one...13:39
pmjdebruijnhttp://revu.ubuntuwire.com/details.py?package=lensfun13:39
slytheringeser: http://paste.ubuntu.com/82457/13:39
mgdmOo, lensfun, been meaning to check that out13:43
geserslytherin: wow, the .orig.tar.gz changed from over 700 kB to 70 kB with one upload?13:44
slytheringeser: yup13:45
geserslytherin: send the mail, it looks ok to me13:45
pmjdebruijnmgdm: eh?13:45
pmjdebruijnmgdm: lensfun by itself does nothing... it's a library... but it works wonders when ufraw is compiled with lensfun support13:46
pmjdebruijnmgdm: I have my own repo at "deb http://ubuntu.pcode.nl/ubuntu intrepid exiv2 ufraw lensfun"13:46
pmjdebruijnmgdm: use at own risk, these are development snapshots... the newer exiv2 may break digikam, etc...13:46
mgdmpmjdebruijn: Yeah, I was meaning I wanted to try it out with UFRaw :) I shall check out your repo, though13:47
pmjdebruijnmgdm: those aren't released version, just development snapshot... but it works for me13:48
pmjdebruijnmgdm: what camera do you have?13:48
mgdmI usually compile things like hugin, enblend, etc from scratch, I should learn how to package them (or find if someone else has done it already)13:48
mgdmpmjdebruijn: 400D13:48
pmjdebruijnmgdm: me too13:48
mgdmcool13:48
pmjdebruijnmgdm: I usually start by modifying existing packages...13:48
=== LucidFox_ is now known as LucidFox
=== asac_ is now known as asac
=== _stink__ is now known as _stink_
pmjdebruijnI just removed all obvious/lintian errors from lensfun14:37
pmjdebruijnI'd appreciate if somebody would have time to take a look at it sometime this week :)14:37
bddebianHeya gang14:45
geserHi bddebian14:46
sebnerheya bddebian14:46
ScottK-laptopbddebian: Heya.14:46
ScottK-laptopbddebian: I noticed you've got at least one merge pending.  Are you planning on dealing with it or should be find someone else?14:47
bddebianHi geser, sebner ScottK-laptop14:47
bddebianScottK-laptop: Which package?14:47
ScottK-laptopbddebian: pybliographer14:48
bddebianWell I uploaded a better version to mentors long ago but I don't think it ever got picked up.14:50
bddebianDidn't I upload that to Ubuntu?14:50
ScottK-laptopbddebian: Dunno.  Just looking at MoM.  Maybe you could upload that to Debian and then we could sync ....14:52
bddebianAye, let me look at the status of pybliographer14:53
ScottK-laptopGreat.14:53
bddebianScottK-laptop: Hmm, weird, looks like 1.2.11 was uploaded to unstable in July.15:11
ScottK-laptopThen can  we just sync it?15:12
bddebianHmm, he also put a 1.3.2-1 in Experimental.  The merge on the 1.2.11 looks very strange.  So a sync would probably be OK except that it might puke on the tarball. :(15:13
ScottK-laptopbddebian: You going to sort it or should I?15:15
bddebianScottK-laptop: Please do, I don't even have a working Ubuntu install atm, my Ubuntu lappy died :(15:20
ScottK-laptopOK.  Will do.15:20
bddebianThanks15:24
mok0bddebian: Hey, you said gimme a break, here it is: <BR\> :-)16:02
bddebianmok0: :)16:03
bddebianmok0: I honestly am not trying to ridicule you.  I apologize if it came off that way.16:03
mok0bddebian: no offense taken; I just wanted you & others to focus on real arguments16:04
mok0bddebian: anyways, if you've seen my latest mail, I offer to take over maintenance of gtk+ 1.216:05
bddebianmok0: Yeah, nice :)16:05
mok0bddebian: but I can't see that it's been orphaned16:05
StevenKPersonally, I think we should remove GTK 1.216:05
bddebianStevenK: That has been the arguement :)16:06
mok0StevenK: ah, you guys...16:06
bddebianmok0: You are correct, I don't think gtk+1.2 itself is technically orphaned16:07
mok0bddebian: ... but it's unmaintained?16:07
bddebianmok0: Of course it hasn't seen a maintainer upload since 2004 :)16:07
mok0bddebian: okay... so what should I do then?16:08
bddebianLet me check MIA on that DD16:08
mok0bddebian: thx16:08
bddebianHeh, he retired over a year ago16:09
mok0StevenK: We've had the discussion on d-d. I dislike the idea of retiring libraries just because they are not needed by the distribution itself. There are users who need the libraries to compile their own programs16:09
bddebianThen they can get it from upstream..16:10
* bddebian hides16:10
mok0bddebian: if there _is_ an upstream, yes16:10
mok0bddebian: gtkglarea for example, upstream is MIA16:11
mok0all links are dead16:11
mok0those sources live only in the archives of the various distros16:11
mok0But I know for a fact that it's still being used16:12
ScottK-laptopAnd since mok0 has volunteered to do the work, people should let him do it ....16:12
* mok0 hugs ScottK-laptop16:13
bddebianmok0: Exactly my point but I'm checking with the MIA folks to make sure I'm reading that mia-query correctly16:13
mok0bddebian: I am grateful if you would figure it out16:13
bddebianScottK-laptop: Agreed but he is talking about 1 package with a butload of unmmaintained/orphaned rdepends16:13
ScottK-laptopRight.  The rpendends are a different issue.16:15
ScottK-laptopOr however you spell that ...16:15
bddebianmok0: OK, I'm going to file an O: on gtk+1.2 then you can just take over maintainance, closing the O:16:16
bddebianWell techinically you should ITA: first.16:16
mok0bddebian: ok, will do... of course I need to persuade a DD to upload it :-)16:17
bddebianI can do that16:17
mok0bddebian: great, thanks16:17
ScottK-laptopmok0: Oddly enough you're talking to one ...16:18
ScottK-laptopSo start persuading ...16:18
mok0ScottK. I think he already went soft on me :-)16:19
bddebianheh16:21
bddebianmok0: Did you see my question about the soname of gtkglarea also?  I have it ready to upload but wasn't sure if you wanted to leave the soname mismatch?16:21
mok0bddebian: I didn't see you comment, but I can guess... it is the lintian that complains about the name, right?16:22
mok0bddebian: it is a choice of changing the package names or the library names; I'd rather not do either16:23
bddebianmok0: Well the package name really should change but if you are trying to get this in for Lenny, I agree16:23
mok0bddebian: if you think it's ok to change the package names, I will do that16:24
bddebianmok0: It is but it might break any reverse dependencies.16:25
mok0... and make a transitional package too16:25
mok0:)16:25
mok0exactly16:25
bddebianmok0: Are you trying to get it in time for Lenny?  If so, I'd say let's leave it for now.16:26
mok0bddebian: to be honest I thought lenny was frozen already16:27
bddebianmok0: It is but if you are fixing bugs/etc we can ask for an exception16:27
mok0bddebian: The upload closes 4 bugs + the ITA bug16:28
mok0bddebian: but they are all minor/trivial16:28
mok0bddebian: like, putting a .o file in /usr/lib :-)16:29
bddebianAye, I'll upload, then ask for an exception, thanks16:29
mok0bddebian: great16:30
mok0bddebian: then I can ask for an Ubuntu sync; right now there's a dumb merge16:31
* mok0 asserts getting rid of a merge is better than sex16:32
lagaerror: assertion failed16:33
bddebian+116:33
mok0laga: heh16:34
ScottKsiretart: Are you @ UDS this time?16:35
siretartScottK: no, not this time. :(16:38
siretartScottK: are you going to attend?16:38
ScottKsiretart: No.  The timing was poor.  I'm hoping to find someone who is there who can hunt down how to listen in remotely.16:39
rjuneheh16:39
bddebianmok0: OK, gtkglarea uploaded and the orphan bug for gtk+1.2 is 508182 .  I'm probably going to get an ass-kicking for that one by the way there were shitloads of uploaders including the GNOME team :(16:39
rjuneI want to find someone who is there as well.16:39
rjuneI have a URL I need to get to ogra16:39
mok0bddebian: uh-uh16:40
ScottK-laptopbddebian: Then one of them can adopt it now if they want.16:40
mok0bddebian: perhaps I should hold off a while before doing work on the package16:40
ScottKGrumble.  From the relevant wiki page, "Mf you cannot attend in person, you can still listen to the conferences or take part in them remotely. More information will be made available close to the conference date."16:44
* ScottK wonders how close ...16:44
hefe_biaI know you're all busy, but I'd be so happy if someone could take a look at Tomboy-Blogposter in REVU, a small plugin for posting tomboy notes to your blog. It's been advocated multiple times before (by mok0 and sikon) and now the issues that were only fixable by upstream are fixed, too... It's my first package... http://revu.ubuntuwire.com/details.py?package=tomboy-blogposter16:49
* ScottK-laptop tries communication via planet ....16:49
* mok0 volunteers to take a look at tomboy-blogposter later today (although he thinks mono is evil)16:51
hefe_biamok0: thank you!16:53
* hefe_bia still does not understand why mono without WinForms is bad.16:54
* hefe_bia likes python better, though ;)16:54
ScottK-laptophefe_bia: The problem is that there is no knowing what patent claims may exist against it.  The best term I could use is 'risky'.16:55
=== hefe_bia_ is now known as hefe_bia
sharmsScottK-laptop: the question is though, which languages are you fully aware of which patent claims exist against them?16:57
sharmsor can you ever be aware16:57
ScottK-laptopsharms: Fully, none.  But given the origin of c#, it's clearly more risky.16:57
hefe_biaScottK-laptop: ah, I see. I thought that that was cleared somehow now. Too bad - First I was so sceptic about it (coming from C++) but I grew to like C# as a language.16:57
sebnerScottK-laptop: it's in fedora and debian so ubuntu shouldn't be scared :P16:58
ScottK-laptopsebner: In patents, prior use and even prior art don't help much.  There's really no way to know if Microsoft is just biding their time or they've changed their tune.16:58
mok0hefe_bia: Imagine a situation where most of the important apps in Ubuntu are mono apps; and Microsoft decides it's time to make their patent claims...16:59
ScottK-laptopMind you, having been involved in the development of open source technology that later showed up in Microsoft patent claims, I may be more sensititve than most.16:59
* hyperair waits for directhex to start his rant on C# FUD16:59
mok0ScottK, .... once the patent is awarded, there's nothing you can do??16:59
sharmsI would say as vague as patents are though, I would be just as worried about python, ruby etc16:59
sharmstheir patents would not just apply to C#17:00
mok0sharms: they'd be laughed out of court for that17:00
sharmsthats why they are not in court right now? :)17:00
mok0sharms: but Mono is a direct re-implementation of parts of .NET17:00
mok0sharms: even Miguel agrees on that17:01
sharmsI agree there too, I am just saying that if they go full out and decide to shut down mono apps, a lot of other things would be at risk too17:02
mok0sharms: ... and he is now employed by Novell, who have made a deal with Microsoft17:02
sebnerScottK-laptop: sure but since the Open Invention Network protects mono I'm fine17:02
hefe_biamok0: I understand. As I said I thought the patent issues had somehow been solved. (Maybe I was a victim of propaganda...) Though I see the problem if patents apply.17:02
mok0hefe_bia: Nothings ever solved with big corporations17:02
ScottK-laptophefe_bia: The problem isn't that it's solved, but that we just can't know.17:03
mok0hefe_bia: just look at how the SCO trial is going...17:03
hefe_biaAnyways I wouldn't start a new development with mono for Linux.17:03
sharmsThe mono website says 'Jim miller from microsoft': 'Basically a grant is given to anyone who want to implement those components for free and for any purpose. '17:03
sharmshttp://www.mono-project.com/FAQ:_Licensing17:03
mok0sharms: oh, on the mono website? That's completely worthless as documentation in court17:04
ScottK-laptopsharms: So MS fires the guy and claims he was speaking out of turn.17:04
ScottK-laptopMeaningless.17:04
sharmsit's a fun discussion, because there is not a correct answer until the courts decide, so we really get nowhere :)17:05
hefe_biaBut can they claim patents on parts that were standardized? Or is the problem that the implementation may accidently violate patents?17:05
mok0sharms: right17:05
ScottK-laptophefe_bia: Standards have no affect on patents.17:05
mok0One of the problems is that Microsoft have never told what patents they say Linux is violating17:06
broonieOr what they mean by Linux for that matter.17:06
mok0... so they keep everyone in a state of uncertainty17:06
mok0broonie: yes17:06
mok0Like most others, when they say "Linux" they mean the whole working OS17:07
mok0+ apps17:07
mgdmis adding a Build-Depend on pkg-config a good/bad/stupid thing to do?17:07
pochumgdm: good, if your package need it17:08
* hefe_bia thinks he has to read up on the topic... Thanks for the insight.17:08
mgdmit seems to17:08
hyperairif configure.ac contains PKG_CHECK_MODULES then adding pkg-config to build-dep is fine i think17:09
sebnerScottK-laptop: http://www2.apebox.org/wordpress/linux/51/ :)17:11
mgdmI won't say I'm getting the hang of it, but I've nearly got the package I asked for the backport for updated to a new upstream release17:12
mgdm(libdmtx)17:12
pochuhmm17:12
pochumgdm: backports are backported from the package in the development version, so you shouldn't need to update anything...17:12
mgdmthe package in Jaunty isn't the latest upstream, it's the latest in Debian17:13
pochuah, then you are updating the package for jaunty, right?17:13
mgdmI did this for myself as an exercise, to see if I can work out how to package things - if it isn't useful then at least I've learned something17:13
mgdmif I can submit it to Jaunty then that'd be fine by me too :)17:14
pochumgdm: what's the latest upstream release?17:16
mgdm0.6.017:16
mgdmversus 0.5.2 that's in Jaunty17:17
ScottK-laptopsebner: I agree that a lot of the anti-mono crowd is over the top, but as the guy says, the combination of Microsoft's history of bad behaviour, the Novell deal, and the broken US patent system leave some room for reasonable concern.17:20
NCommandermgdm, if you finish the updated package, post it to Launchpad, and then ping me, and I'll review for upload17:20
sebnerScottK-laptop: sure but life is a game and I won't hide myself in the cellar for the rest of my life17:20
mgdmNCommander: great, thanks. I'll need to try it out on my laptop, it has my GPG keys17:20
mgdmNCommander: this is the first one I'll have done though, so expect some WTFery :)17:21
NCommanderWell, I'm at UDS17:21
NCommanderso my time to review time is somewhat high ATM17:21
ScottK-laptopmgdm: You can always just make a new gpg key, add it to your LP profile, and then upload ...17:21
mgdmunderstandable17:21
mgdmScottK-laptop: I could... but I'm leaving for home in < 8 minutes :)17:22
ScottK-laptopAh.  No point then.17:22
pochumgdm: actually you don't need your gpg key to attach the diff.gz to a launchpad bug ;)17:22
mgdmAh...17:22
mgdmthere isn't a bug for a new upstream version, shoudl I file one?17:22
pochuyup17:22
mgdmok17:22
mgdmI need to add something else to the changelog first17:23
NCommandermgdm, remember to subscribe ubuntu-universe-sponsors17:24
mgdmDone17:26
mgdmhttps://bugs.edge.launchpad.net/hardy-backports/+bug/30628017:26
ubottuLaunchpad bug 306280 in hardy-backports "Update libdmtx to 0.6.0" [Undecided,New]17:26
NCommanderOh, this is a backport?17:26
NCommanderBackports are different17:26
NCommanderTHe updated version MUST be in jaunty17:26
mgdmOh, I botched that17:27
NCommanderand as a general rule17:27
NCommanderWe don't backport libraries17:27
NCommanderI'll look at it later17:27
mgdmFeck, I filed it in the wrong place17:27
mgdmif I file it against "ubuntu" rather than hardy-backports will that be more correct?17:29
pochuyes. you can add an Ubuntu task to the same bug report17:29
sharmsScottK: looks like Mike posted a blog entry same time you did17:34
mgdmI need to leave just now, if anyone has any hints for putting that bug in the right project, ping me...17:35
ScottKsharms: Mike's blog entry doesn't have any information that's actually useful for remote participation.  I responded to his.17:36
sharmsgotcha17:36
ScottKBut icecast.ubuntu.com is starting to have some useful information.17:37
pochumgdm: I've added an Ubuntu task for you (click on "Also affects distribution", then Ubuntu and libdmtx)17:40
mgdmpochu: ah, great, thanks - I wasn't sure if that was right17:52
mgdmdoes the .diff.gz look sensible, if you have any time to look?17:52
pochunot really right now17:53
mgdmpochu, and everyone: thanks for all your help :)18:20
=== santiago-pgsql is now known as santiago-ve
=== x-spec-t is now known as Spec
=== mterry_ is now known as mterry
=== smarter_ is now known as smarter
=== _magnetic is now known as foolano
=== fta2 is now known as fta
=== etank is now known as service_desk
=== service_desk is now known as etank
crimsunsomeone poke Hobbsee20:33
Hobbseecrimsun: poke back20:38
=== gouki_ is now known as gouki
=== ivoks is now known as ivoks_
=== pericamali is now known as ivoks
meoblast001hi22:38
meoblast001whats the package name for mozilla-xpcom22:38
Hobbseexulrunner or similar, probably22:41
meoblast001i installed that22:41
jdongxulrunner-1.9-dev?22:47
jdongxulrunner-1.9-dev: /usr/lib/xulrunner-devel-1.9.0.3/xpcom-config.h22:47
meoblast001jdong: how would i tell wxMozilla that it has a different name22:48
jdongI have no idea what you mean?22:48
meoblast001this is what it tells me http://rafb.net/p/PE42Ul79.html22:49
meoblast001and i already have xulrunner-1.9-dev installed22:49
jdonga search and replace from mozilla-xpcom to xulrunner-xpcom should do it.22:50
jdonglibxul-dev: /usr/lib/pkgconfig/xulrunner-xpcom.pc22:50
jdongthat's the pkg-config file you want to address that error22:50
jdongnote libxul-dev22:50
meoblast001ok im not familiar with pkg-config22:51
meoblast001so what am i doing?22:51
jdonginstalling libxul-dev22:51
meoblast001rephase please22:51
meoblast001ok22:51
meoblast001then...22:51
jdongthen in your project find-and-replace everything that says "mozilla-xpcom" to "xulrunner-xpcom"22:52
meoblast001thats the configure script that has the error22:52
meoblast001i got this working before22:52
meoblast001well... it worked before22:52
meoblast001dont know why it wont work now22:52
jdongUbuntu hasn't shipped mozilla-xpcom for several releases?22:52
meoblast001then where do i get it?22:53
jdongyou don't get it.22:53
jdongas I said, you reconfigure your *project* to buidl against XULRUNNER-xpcom22:53
meoblast001what is it included in?22:53
jdongI don't know how I can make this any clearer....22:53
meoblast001this isnt my project.... this is wxMozilla22:54
meoblast001i dont know what would need to be changed in it cuz i didnt write it22:54
meoblast001i think i need to tell the configure script its real name22:54
meoblast001is that what its sayingi n that pastebin i gave you22:54
jdongyou need to patch wxmozilla's buildsystem everywhere you see MOZILLA-xpcom change it to XULRUNNER-xpcom22:55
jdongthis is the 4th time I've said the exact same thing.22:55
meoblast001ok22:55
jdongyou should NOT be trying to find mozilla-xpcom.22:55
meoblast001now its clear to me22:55
meoblast001somehow i got it to work in the past22:56
meoblast001jdong, what about mozilla-nspr?23:01
=== Skiessi is now known as DreadController2
=== DreadController2 is now known as Skiessi
meoblast001ok23:04
meoblast001found it23:04
meoblast001i've about had it with this stupid package naming scheme23:07
meoblast001jdong, changing the configure script made errors in them makefile23:18
=== mterry_ is now known as mterry

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!