[03:26] <virusuy> hi all
[03:53] <maco> interesting to learn that the gnome people even get rid of theming features though!
[03:53] <maco> whoops
[03:54] <maco> that was sposed to be in a PM and was gtk engine murrine dropping scrollbar colour settings
[03:57] <highvoltage> so if you switched gtk theme you can still change scrollbar colours right?
[03:57] <highvoltage> and aren't you supposed to be american? :)
[04:07] <maco> highvoltage: just because i was born here doesn't mean i have to spell like a heathen
[04:07] <maco> except "tire," because "tyre" just looks silly
[04:08] <maco> highvoltage: i said "lorry" when talking to an english guy the other day and the americans standing next to us jumped! it amused me
[04:08] <maco> i told them i codeswitch and if there's an english person, they trump on whether to use english-english or american-english
[04:10] <StevenK> Tyre does not look silly!
[04:11] <StevenK> maco: You fully switch? For example, 'faucet' -> 'tap'; 'diaper' -> 'nappy' ?
[04:11] <maco> StevenK: those words tend not to come up so much, but i did ask about all the prams when we went to dinner during UDS
[04:12] <maco> all the words where i know they say something else, i swap out
[04:13] <maco> StevenK: and btw, we say tap and nappy here too sometimes.  i mean "tap water" is colloquial.  nappy is more used when talking to a child though
[04:13] <maco> its considered baby talk
[04:13] <StevenK> maco: Don't tempt me to feel insulted :-)
[04:22] <virusuy> where can i find an application who needs to be  packaged ?
[04:23] <maco> search for needs-packaging on bugs.launchpad.net/ubuntu/+bugs
[04:25] <virusuy> maco: ok! thanks ! and after create de package what i have to do ?
[04:25] <maco> virusuy: upload all the pieces of the source package (listed in the .dsc file, including the .dsc) to the bug
[04:25] <virusuy> maco: and somewone will check it , right ?
[04:26] <maco> virusuy: oh actually wait no. thats for new releases of old packages. sorry, upload it to revu
[04:26] <maco> !revu
[04:26] <ubottu> REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU
[04:26] <virusuy> maco: cool! thanks
[04:37] <crabbytag> virusuy: if a package needs packaging, send it up to Debian as well
[04:37] <crabbytag> virusuy: you should file an ITP up there, if you plan on doing the work anyway :)
[04:38] <crabbytag> virusuy: after it's in top-notch shape, send to debain-mentors and close out the Ubuntu ITP as well as the Debian ITP
[04:38] <crabbytag> virusuy: since we pull from Debian automatically
[04:38] <virusuy> and ubuntu does just a "sync" from Debian, am i right ?
[04:38] <crabbytag> virusuy: you are
[04:39] <virusuy> crabbytag: cool, actually i cannot find a app to package, can you recommend me one? a easy one :-P
[04:39] <crabbytag> virusuy: check for RFP ( Request for Packaging ) bugs in Debian, I also think pabs ( Paul Wise ) has a list of cool software
[04:40] <crabbytag> virusuy: if I had something nifty I liked, I'd just do it myself ;)
[04:40] <virusuy> crabbytag: ok! i'll look in debian
[04:40] <crabbytag> virusuy: thanks!
[04:43] <virusuy> crabbytag: i found one .... work time!
[04:44] <virusuy> what happend when i found a RFP , and when i go to website, they already have .deb files to download ?
[04:47] <crabbytag> virusuy: you review what they have, and see if it's under a license you may use
[04:47] <crabbytag> virusuy: if it is, you base your work on that, and if it's unfit, please start from scratch
[04:48] <virusuy> crabbytag: ok
[04:48] <crabbytag> virusuy: be sure to turn the RFP into an ITP :)
[04:48] <crabbytag> virusuy: remember to always maintain copyright and clean up everything
=== crabbytag is now known as paultag
[04:49] <virusuy> paultag: oki doki :-D
[04:49] <paultag> virusuy: let me know how it goes :)
[05:46] <c2tarun> can anyone please explain me this error. http://paste.ubuntu.com/563707/
[05:50] <StevenK> You don't have the Build-Depends installed
[05:55] <c2tarun> StevenK: Ok, I dont want to install them in my system. but I can install them on my pbuilder-dist any way i can do that?
[05:56] <StevenK> Then copy the source package directory inside a pbuilder chroot and run dpkg-buildpackage -S -uc -us from there
[05:57] <micahg> c2tarun: BTW, you shouldn't be using build1 for a version unless it's a rebuild of a Debian package that was sync'd
[05:59] <c2tarun> micahg: what should i use here then?
[05:59] <micahg> c2tarun: 2.0.6-0ubuntu1
[06:00] <c2tarun> micahg: but in changelog it was in build format, why so?
[06:00] <micahg> c2tarun: that was just a rebuild of the Debian import, not something with Ubuntu changes
[06:01] <c2tarun> micahg: ok
[06:01] <micahg> c2tarun: did uscan/uupdate not set up the right changelog or did you manually set this up?
[06:01] <chillywilly> W0000T!!!! Packers are the Superbowl Champs!!!!!!!
[06:03] <c2tarun> micahg: no i downloaded the older version by apt-get and there was no watch file so i downloaded newer version from site
[06:04] <micahg> c2tarun: there's a newer version on mentors.debian.net, maybe you want to coordinate with Debian on this update
[06:13] <c2tarun> micahg: which file should I upload as a my public key for gpg key?
[06:14] <micahg> c2tarun: there should be instructions on launchpad
[06:15] <c2tarun> micahg: ya i just saw :) thanks
[06:39] <c2tarun> micahg: there is a version on mentors.debian.net upper than version in our archives. How can I coordinate with them?
[06:44] <micahg> c2tarun: you could try commenting on debian 609789 about the new version on mentors and the new version upstream, if that doesn't get a response by the end of the week, try e-mailing the mentors uploader and the maintainer in the same e-mail and try to coordinate
[06:44] <ubottu> Debian bug 609789 in spyder "spyder: New upstream version" [Wishlist,Open] http://bugs.debian.org/609789
[07:18] <dholbach> good morning
=== 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
=== almaisan-away is now known as al-maisan
=== bilalakhtar_ is now known as cdbs
=== bilalakhtar_ is now known as cdbs
[09:55] <simar> maco, if you don't mind can i ask you some help related to packaging .. i'm stuck at some point
[10:24] <Bachstelze> simar: why not just ask here for everyone to see?
[10:24] <mok0> inquisitive minds want to know
[10:25] <simar> Bachstelze, no problem .. i mean that would be my pleasure..
[10:25] <simar> i'm a bit new to packaging and is trying to resolve this one for dapper https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/209627
[10:25] <ubottu> Ubuntu bug 209627 in lighttpd (Ubuntu Dapper) "lighttpd (security) ssl fix" [Low,In progress]
[10:26] <simar> i know dapper is out now but that would be good practice for me
[10:27] <simar> using hardy sources (where bug is resolved) i found that 92_CVE-2008-1531.dpatch contains the code to fix the patch but the problem is that i do not understand the format of dpatch and there is no manual available on Internet
[10:27] <ubottu> The connection_state_machine function (connections.c) in lighttpd 1.4.19 and earlier, and 1.5.x before 1.5.0, allows remote attackers to cause a denial of service (active SSL connection loss) by triggering an SSL error, such as disconnecting before a download has finished, which causes all active SSL connections to be lost. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1531)
[10:28] <simar> http://paste.ubuntu.com/563767/ contains the patch
[10:29] <Bachstelze> simar: what's the problem ? The patch doesn't apply cleanly to the sources in DApper ?
[10:29] <simar> Bachstelze, i know how to do that. can i use the same patch and use in dapper sources...
[10:31] <Bachstelze> if it applies cleanly, yes
[10:33] <simar> Bachstelze, ok .. i will try to apply.. it
[10:33] <simar> Bachstelze, if you can tell me command that would make my half work done...
=== al-maisan is now known as almaisan-away
[10:34] <simar> i have downloaded the sources of both hardy and dapper and '''dpkg-source -x''' them in separate folders..
[10:36] <Bachstelze> simar: http://matrixhasu.altervista.org/index.php?view=use_dpatch
[10:37] <Bachstelze> simar: basically, copy the patch from the hardy package in debian/patches of the dapper package and try to apply it
[10:37] <Bachstelze> (don't forget to also edit debian/patches/00list to "enable" it)
[10:37] <simar> Bachstelze, I think i got it..
[10:37] <simar> i know that..
[10:38] <simar> but after i do that .. then what to do ..
[10:39] <Bachstelze> after that you update debian/changelog, create a package with debuild and see if it fixes the problem
=== almaisan-away is now known as al-maisan
[10:40] <simar> how can i check whether it fixes the problem .. i mean should i use pbuilder or virtualbox?
[10:41] <simar> Bachstelze,
[10:41] <Bachstelze> simar: you try to reproduce the bug
[10:42] <Bachstelze> pbuilder is just a tool to build the package, you can use it if you want, or just usez debuild
[10:42] <Bachstelze> it's unimportant
[10:42] <simar> Bachstelze, but i have maverick and i think the bug is already fixed here. I must have to have dapper to reproduce the bug.
[10:42] <Bachstelze> you just need to build the package, no matter how
[10:43] <Bachstelze> then yes, you can use virtualbox
[10:43] <simar> Bachstelze, can i build the package in maverick..?? without any of its interference..
[10:44] <simar> i mean it may get some build-depends from maverick .. may be??
[10:44] <Bachstelze> simar: yes, you can createz a Dapper pbuilder
[10:44] <Bachstelze> create*
[10:46] <simar> Bachstelze, ok.. i mean i must build the package in dapper pbuilder and then use VB to test whether the new one removes the bug or not...
[10:46] <Bachstelze> that would be one way to do it, yes
[10:46] <simar> Bachstelze, but from where can i get dapper iso now..
[10:47] <Bachstelze> http://old-releases.ubuntu.com/releases/
[10:47] <simar> Bachstelze, thanks
[10:48] <Bachstelze> actually
[10:48] <Bachstelze> they are still on releases.ubuntu/com
[10:48] <Bachstelze> .*
[10:50] <simar> one last thing .. plz help me to install pbuilder for dapper?? or tell other easy way if you know one..
[10:50] <Bachstelze> I think you can use pbuilder-dist for that
[10:51] <simar> pbuilder-dist dapper
[10:51] <simar> ??
[10:51] <Bachstelze> not sure, I don't use it myself
[10:51] <Bachstelze> I use this .pbuilderrc
[10:51] <Bachstelze> https://wiki.ubuntu.com/PbuilderHowto#Multiple%20pbuilders
[10:52] <Bachstelze> and env variables (DIST and ARCH)
[10:53] <simar> Bachstelze, Thanks you very much. I hope now I can do it..
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
=== yofel_ is now known as yofel
=== warp11 is now known as warp10
[13:31] <drizt> hello!
[13:32] <drizt>  renamed a package. I updating my old (installing before renaming) package with apt-get install but it not removed old config files from /etc. I neen properly updating of my old package. How I should write rules file for it? I need to remove old config files (from old-name package) when installing new version of package
[13:51] <drizt> hey guys! is there anybody here? it's so hardy question? or is my english so bad?
=== dholbach_ is now known as dholbach
=== didrocks1 is now known as didrocks
=== shadeslayer_ is now known as shadeslayer
=== Quintasan_ is now known as Quintasan
[15:55] <c2tarun> how can i copy anthing from my home folder in pbuilder-dist environment?
[16:11] <tumbleweed> c2tarun: copy it from outside the pbuilder (the chroot is in /var/cache/pbuilder/build/something)
[16:12] <c2tarun> actually pbuilder env is in /var/cache/pb.... mine is in ~/pbuilder/
[16:13] <tumbleweed> c2tarun: pbuilder-dist doesn't set the buildplace, so it presumably still happens in /var/cache/pbuilder/build
[16:14] <c2tarun> tumbleweed: thanks :) i'll try
=== al-maisan is now known as almaisan-away
[16:49] <Laney> if I ship a file in a deb with changed permissions (excluded from fixperms), will dpkg maintain local (statoverride) permission changes?
=== hanska is now known as dapal
[18:58] <simar> ari-tczew, hi
[18:58] <simar> ari-tczew, can i pm you
[19:07] <ari-tczew> simar: hello. sure.
=== ximion1 is now known as ximion
=== fosdemlogger is now known as austrialogger
=== austrialogger is now known as apachelogger
[21:55] <drizt> hi. how i can see what command execute in the postinst and preinst sections when i install my package with apt-get install?
[21:57] <geser> drizt: add "set -x" near the top of the scripts
[21:58] <drizt> geser: you mean what i should add "set -x" to my .postinst file?
[21:59] <geser> yes
[21:59] <drizt> thank you. i will try. ... maybe is there is another way to do it?
[22:01] <drizt> what is mean "set -e" ? I have open my .postinst file and seem it on the top.
[22:01] <StevenK> If a command exits with a status that isn't 0, the script exits
[22:01] <drizt> ok thank you
[22:08] <drizt> I want to remove obsoletes conffiles. For it i must use .preinst file. I need to see upgrade parameter and if i got it remove old conffiles. Is it true?
=== tumbleweed_ is now known as tumbleweed
[22:16] <MTecknology> drizt: looking for this? http://man.cx/dpkg-maintscript-helper
[22:17] <drizt> maybe ...
[22:18] <drizt> thank you.
[22:19] <drizt> damn. after rpm it so hardy for me!
[22:20] <MTecknology> what exactly are you trying to do?
[22:22] <drizt> i renamed package.
[22:23] <MTecknology> then ya, you want that page
[22:23] <drizt> after upgrade old package (with old name) i got couple of conffiles (from old and new packages).
[22:30] <drizt> MTecknology: thank you for man.cx now i can use firefox searching to find a manpage!
[22:36] <MTecknology> drizt: I gave you a link to the page you need
[22:36]  * MTecknology has to run off