=== ripps_ is now known as ripps === jalcine is now known as JackyAlcine === JackyAlcine is now known as jalcine === jalcine is now known as JackyAlcine === Whoopie_ is now known as Whoopie [10:46] i'm currently packaging screenwriting app trelby, and i was wondering if there's any chance to still get it into precise at this stage; mostly because i'm pretty sure there isn't any screenwriting app packaged for ubuntu yet. [10:51] ockham: Precise is releasing in 5 days, not a chance, sorry. [10:52] StevenK: ok, just making sure. more time for packaging, then. [10:58] Backports is your option, likely. [11:01] and what about ocropus 0.4, whose dependency iulib will likely be fixed this weekend (both in debian experimental)? 0.3 was removed from precise due to conflicts with tesseract 3.x... [11:02] Any changes to Precise at this point are incredibly unlikely unless it fixes a tracked Critical bug. [11:03] StevenK: ok. [13:39] mh python-envisagecore does not install and I have no idea why :/ [13:39] debian is not affected === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === jsjgruber is now known as Guest18144 [15:48] jtaylor: urgh, .pth files [15:52] jtaylor: it doesn't actually fail for me, just produces an ugly error [16:12] StevenK: For Universe stuff it's less unlikely than that. [16:12] (if it's a sync from Debian and as in this case fixes a regression) [16:12] ockham: ^^^ [16:13] ScottK: cool! (you mean the ocropus/iulib case, right? not the trelby one...) [16:14] yes. [16:14] so maybe i should go ping jwilk then... [16:14] Possible. No promises. [16:15] is it a problem that this stuff lives in experimental currently? (unstable still has 0.3 AFAIK) [16:15] No. === Guest94473 is now known as JackyAlcine [21:50] I thought this bug was fixed on oneric? https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/821100 [21:50] Launchpad bug 821100 in ia32-libs (Ubuntu Natty) "ia32-libs does not install /usr/lib32/libGL.so.1" [Undecided,Confirmed] [21:51] apparently not because I still have it :P [22:21] nvm fixed with lglu :D [22:21] libglu* [22:55] Hello everybody hope you are all having a great weekend. I am trying to rap my head around the rules file under /debian and was wondering what %: dh $@ || is $@ like the #? inbash where it is calling the last call ? or is it like a wildcard where it attaches itself to dh ? thanks [22:57] bobweaver: its a makefile macro, in this case the name of the target [22:58] and the target is a wildcard (%) so its basically whatever you give the file as an argument [22:59] http://www.cs.duke.edu/~ola/courses/programming/Makefiles/node7.html [22:59] Thanks ! [23:00] I get it so it is going to each file ? [23:00] one by one $@ aka like a while loop ? [23:00] debian/rules is called with certain defined targets [23:00] e.g. build, build-arch, build-indep, binary etc [23:01] the dh program reads those and acts appropriatly [23:02] so the dh aka debhelper is running at the /debian directory ? because dh knows too do this ? if this is correct how does it know ? [23:03] the dh program is just a scheduler for other commands [23:04] it calls other (debhelper) scripts in a certain order [23:04] you could also write it all out explicitly in debian/rules [23:04] thats how it was done before dh-7 [23:05] yes that is how I have made all my simple packages by altering rules [23:05] rules file * [23:06] Just tying to wrap my head around the bigger picture so to say and understanding why all these things are going on when they are. [23:06] if you open /usr/bin/dh around line 350 the standard sequences are defined [23:06] Thanks ! [23:06] line 420 it defines the targets that must be exposed [23:07] the sequences can be altered by scripts in /usr/share/perl5/Debian/Debhelper/Sequence/ [23:07] e.g. for special handling of python packages [23:07] which would add e.g. dh_python2 to the install sequence [23:08] debhelper is all quite readable for perl [23:08] jtaylor, you are awesome ! [23:09] I see where the compat files are getting called also now. [23:09] here are the makefile targets that must or can be defined: http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules [23:12] I have read that manual so many times :D could not understand it for the life of me for the 1 week. It is starting to come together Just going to take me some time. I have had great Help :) === jalcine is now known as Guest58583