[12:03] <foampeace> yes not sure exactly how to sign it right...so many options
[12:03] <foampeace> in thunderbird enigmail
[12:03] <raphink> never used it
[12:03] <raphink> did you look on google?
[12:05] <foampeace> what about keyservers?
[12:06] <foampeace> should i put anything in the email?
[12:06] <foampeace> just leave the default keyservers?
[12:06] <foampeace> random.sks.keyserver.penguin.de, pgp.dtype.org, keyserver.kjsl.com, ldap://certserver.pgp.com
[12:06] <foampeace> those are the defaults
[12:06] <raphink> keep this
[12:07] <raphink> you don't have to worry about keyservers in the email client I think
[12:08] <raphink> http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto.php
[12:09] <raphink> don't use generate key though ;) obviously ..;
[12:10] <foampeace> thanks
[12:10] <foampeace> o i could have generated with this program itself
[12:15] <foampeace> shoudl the messages be encrypted?
[12:17] <raphink> nope
[12:17] <raphink> just signed
[12:17] <raphink> to encrypt the message, you need to have the key of the person you're sending it to
[12:18] <raphink> so the message can only be read with this key
[12:20] <foampeace> i see encryption
[12:20] <foampeace> it does it whether i like it or not
[12:21] <foampeace> -----BEGIN PGP SIGNATURE-----
[12:21] <foampeace> Version: GnuPG v1.4.1 (GNU/Linux)
[12:21] <foampeace> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
[12:21] <foampeace> iD8DBQFDf7ZQeS1hPlkp6OoRAtSoAKCb3K/ZJsOL5c27KK4F/CMg/NjcVQCgiv9Y
[12:21] <foampeace> qwG/rZNmbd9G80IEWAewYpA=
[12:21] <foampeace> =67IT
[12:21] <foampeace> -----END PGP SIGNATURE-----
[12:21] <foampeace> see?
[12:21] <foampeace> thats not right?
[12:23] <raphink> that's not encrypted
[12:23] <raphink> that's just your signature
[12:23] <foampeace> phew
[12:23] <foampeace> so now i send to the guy
[12:23] <raphink> BEGIN PGP SIGNATURE  <-------
[12:23] <raphink> it's writing in capital letters : SIGNATURE ;)
[12:23] <raphink> if it was encrypted
[12:24] <raphink> you couldn't read your the message you wrote anymore
[12:24] <raphink> unless you encrypted it for you too
[12:25] <foampeace> register as uploader?
[12:25] <raphink> foampeace: ?
[12:26] <foampeace> so he can add me to the upload keyring?
[12:26] <raphink> yep
[12:26] <raphink> if you signed your message
[12:26] <raphink> then he can be sure that you own this key
[12:27] <raphink> and he can get the public key and add it to the keyring
[12:27] <LaserJock> how do you sign somebody's key --sign-key?
[12:27] <raphink> yes
[12:28] <raphink> or rahter
[12:28] <raphink> first of all
[12:28] <raphink> you edit the key
[12:28] <raphink> with --edit-key
[12:28] <raphink> and you sign each uid you trust
[12:28] <raphink> and set the trust level
[12:30] <foampeace> dput.cf?
[12:31] <raphink> foampeace: yes you need to have dput installed and to set it
[12:32] <foampeace> sudo apt-get install dput
[12:32] <LaserJock> raphink: after you do --edit-key and sign it you can then export it?
[12:32] <raphink> sure
[12:33] <raphink> when you quit gpg after signing the key
[12:33] <raphink> you can export the newly signed key to the servers
[12:33] <raphink> yes foampeace
[12:33] <raphink> how well do you know debian systems foampeace ?
[12:34] <foampeace> raphink: how well? thats hard to answer
[12:34] <raphink> how long have you been using a debian system?
[12:34] <foampeace> severa years on and off
[12:35] <raphink> ok
[12:35] <foampeace> dput is for uploading?
[12:35] <crimsun> yes.
[12:36] <Kyral> I need to finish EasyChem
[12:36] <raphink> ;)
[12:37] <Kyral> But first comes fixing the PBuilder
[12:37] <raphink> Kyral: did you try with the link I gave ?
[12:37] <Kyral> Its already made
[12:37] <raphink> ok
[12:37] <raphink> that should work
[12:37] <Kyral> the problem is with /etc/shadow
[12:37] <Kyral> I have to jump into the pbuilder and touch the file
[12:37] <foampeace> ill be replied to with user and pass etc?
[12:37] <raphink> well this should fix the /etc/shadow issue
[12:38] <crimsun> Kyral: no.
[12:38] <crimsun> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338976
[12:38] <crimsun> use Markus Kolb's 2-line patch.
[12:38] <raphink> taht's what I gave him crimsun
[12:38] <foampeace> raphink: will i be replied to?
[12:38] <raphink> Kyral: you need to patch the script as told in the bug report
[12:38] <raphink> no foampeace
[12:38] <raphink> you will be added to the keyring
[12:38] <raphink> then you can begin to upload
[12:39] <foampeace> just automatically added?
[12:39] <Kyral> how do I patch again?
[12:39] <raphink> not automatically foampeace
[12:39] <raphink> someone will get your email and answer to it
[12:39] <raphink> afer adding your key
[12:39] <crimsun> patch -p# < foo.patch
[12:39] <crimsun> man patch
[12:40] <Kyral> wait a sec, they patched it in Debian
[12:40] <raphink> Kyral: you can just do it manually it's just one line
[12:40] <raphink> ;)
[12:40] <crimsun> and we haven't merged it yet
[12:40] <Kyral> ah
[12:40] <raphink> Kyral: just edit this file and change this line
[12:40] <crimsun> this you need to by-hand
[12:40] <raphink> you know how to read a diff ?
[12:40] <Kyral> do I have to hit every PBuilder?
[12:40] <crimsun> it's only that script
[12:40] <crimsun> it doesn't affect your base.tgzs
[12:40] <Kyral> okay
[12:43] <Kyral> Gah, I need to patch xterm
[12:43] <Kyral> Forum user pointed out that it doesn't provide x-terminal-emulator
[12:43] <foampeace> can you contribute other stuff besides packages?
[12:43] <foampeace> like what
[12:44] <foampeace> docs?
[12:44] <foampeace> graphics?
[12:44] <Kyral> but can I submit a patch to something from Main....
[12:44] <foampeace> themes?
[12:45] <foampeace> i apologize im in a fog about all this until tommorrow
[12:46] <raphink> sure foampeace you can make themes, graphics, docs and whatever :) these are nice ways to contribute too
[12:46] <foampeace> always takes a nights rest :)
[12:46] <foampeace> its real good that people get to contribute to it like this
[12:47] <raphink> if you don't feel at ease technically with packaging, there are many other ways of contributing
[12:48] <raphink> :)
[12:48] <foampeace> its seemed to do most of the packaging on its own
[12:49] <raphink> what do you mean foampeace ?
[12:49] <foampeace> but maybe you laughing at me for saying that
[12:49] <raphink> no, not at all
[12:49] <foampeace> i mean autoapt
[12:49] <raphink> o_O
[12:49] <raphink> do you know about lintian foampeace ?
[12:49] <foampeace> lintian?
[12:49] <Kyral> https://launchpad.net/distros/ubuntu/+source/xterm/+bug/4614 <--If I patch this and make a debdiff can someone upload it?
[12:49] <Ubugtu> Malone bug #4614: Doesn't provide x-terminal-emulator Fix req. for: xterm (Ubuntu), Severity: Minor, Assigned to: Nobody, Status: New http://launchpad.net/malone/bugs/4614
[12:49] <minghua> damn, snapshot.debian.net doesn't have the version I need
[12:50] <Kyral> Where the heck did the bot come from
[12:50] <raphink> lol
[12:50] <raphink> Ubugtu: what'd you say?
[12:50] <Kyral> 4614
[12:50] <raphink> stupid bot...
[12:51] <Kyral> !malone 4614
[12:51] <raphink> foampeace: lintian is a tool to check your packages
[12:51] <Kyral> ....how do you work this thing
[12:51] <raphink> install it and run it on your packages
[12:51] <foampeace> lintian the deb package checker?
[12:51] <raphink> yep foampeace
[12:51] <raphink> one of the goals for a clean package is to have no lintian output when you run it on your package
[12:51] <raphink> i doubt you get no lintian output when using autodeb
[12:52] <raphink> (although i've never used it myself so I can't be sure)
[12:52] <Kyral> If you are serious about packaging follow the New Maintainers Guide
[12:52] <raphink> :)
[12:52] <raphink> BEGIN PGP SIGNATURE
[12:52] <raphink> oop
[12:52] <raphink> http://www.debian.org/doc/manuals/maint-guide/index.en.html
[12:52] <foampeace> ok
[12:52] <raphink> here
[12:52] <raphink> read this
[12:52] <Kyral> anyway that bug is an easy fix, but the package is in main
[12:52] <raphink> that is the basis to know
[12:53] <raphink> foampeace: I know there are way of doing packages easily
[12:53] <raphink> but I prefer to not install these packages on my system...
[12:53] <Kyral> bug 4614
[12:53] <Ubugtu> Malone bug #4614: Doesn't provide x-terminal-emulator Fix req. for: xterm (Ubuntu), Severity: Minor, Assigned to: Nobody, Status: New http://launchpad.net/malone/bugs/4614
[12:53] <Kyral> good bot
[12:54] <raphink> official packages must be clean in order to assure a good system to users
[12:54] <raphink> hehe
[12:54] <Kyral> I can fix it fast, but I don't have upload rights to Main
[12:56] <raphink> ;)
[12:57] <Kyral> I'll fix it, attach the debdiff to the bug, mark it as Accepted, and ping whoever can upload it
[12:57] <foampeace> raphink: ok mine has lots of problems..not that i would know why
[12:58] <raphink> foampeace: there you see how good autodeb is ;)
[12:58] <raphink> foampeace: paste the lintian output there : http://paste.ubuntulinux.nl/
[12:58] <raphink> so I can see ;)
[12:59] <raphink> (and tell me the url of your pastebin entry...)
[12:59] <Kyral> Dangit this is gonna be a NMU for sure
[12:59] <raphink> foampeace: you can get more details by running `lintian -i'
[12:59] <raphink> instead of just lintian
[12:59] <raphink> Kyral: :(
[01:00] <foampeace> k
[01:00] <Kyral> I'm not the maintainer, I'm just a bugfixer :D
[01:00] <raphink> hehe
[01:00] <Kyral> still...what do I do
[01:02] <foampeace> raphink: lintian tells you what to do mostly?
[01:02] <foampeace> http://paste.ubuntulinux.nl/4773
[01:02] <raphink> foampeace: if you understand what it says, then yes mostly
[01:02] <raphink> lintian doesn't tell you about _all_ pbs with your package though
[01:02] <raphink> so if you ahve many output, that means you migth have even more issues
[01:03] <foampeace> does mine look easy?
[01:03] <raphink> foampeace: yours look like you would gain time in forgetting about autodeb
[01:03] <raphink> reading the maintainer's guide
[01:04] <raphink> and use dehelper scripts rather
[01:04] <raphink> I think most of these errors are due to the use of autodeb
[01:04] <Kyral> hey \sh
[01:04] <foampeace> raphink: ok
[01:05] <raphink> foampeace: really the first thing you have to do is read. Read the whole maintainer's guide and read about Debian Policy aswell
[01:05] <foampeace> ok
[01:05] <raphink> at least throw an eye on Debian policy when you're done with the maintainer's guide
[01:05] <raphink> :)
[01:05] <raphink> that's not a very nice reading but it's useful
[01:05] <\sh> re
[01:05] <raphink> hi \sh
[01:06] <Kyral> that was fast and easy
[01:06] <Kyral> anyone wanna upload this thing?
[01:06] <raphink> you can't upload Kyral ?
[01:06] <Kyral> nope
[01:06] <raphink> why?
[01:06] <Kyral> I'm a MOTU-Wannabe :D
[01:07] <raphink> you don't need to be a motu in order to upload
[01:07] <raphink> just have your key in the keyring
[01:07] <Kyral> To main
[01:07] <raphink> oooh ic ;)
[01:07] <Kyral> XTerm is in main
[01:07] <raphink> sorry for misunderstanding you ;)
[01:07] <raphink> yep
[01:07] <\sh> raphink: aehm..u need to be a motu to have upload rights to universe
[01:07] <\sh> Kyral: what about xterm?
[01:07] <raphink> \sh I thought uploading to revu ;)
[01:07] <raphink> huhu
[01:07] <Kyral> Forum user pointed out that it doesn't provide x-terminal-emulator
[01:07] <\sh> raphink: no...send patches to me
[01:08] <\sh> raphink: I will upload it for u then
[01:08] <raphink> what exactly is required to be a MOTU \sh ?
[01:08] <raphink> oh it's not for me \sh, it's for Kyral :)
[01:08] <\sh> raphink: first of all u need to be an ubuntu member...means, document your work on your wiki.ubuntu.com/ page
[01:09] <Kyral> !bug 4614
[01:09] <Ubugtu> (bug <abbreviation> <number>) -- Look up bug <number> in the bugzilla associated with <abbreviation>.
[01:09] <\sh> raphink: then apply for ubuntu membership in front of the CC
[01:09] <Kyral> bug 4614
[01:09] <Ubugtu> Malone bug #4614: Doesn't provide x-terminal-emulator Fix req. for: xterm (Ubuntu), Severity: Minor, Assigned to: Nobody, Status: New http://launchpad.net/malone/bugs/4614
[01:10] <foampeace> no one is working on my package
[01:10] <raphink> that's possible foampeace
[01:10] <\sh> raphink: while u are doing your contribution towards the universe or to other parts of ubuntu...work together with the motu team...after membership and after a couple of weeks..you apply for universe upload rights in front of the TB.
[01:10] <raphink> there are many orphan packages foampeace
[01:10] <raphink> \sh: TB ?
[01:11] <Kyral> until then I have to ping MOTUs whenever I fix something
[01:11] <\sh> raphink: technical board
[01:11] <raphink> ok
[01:12] <raphink> so I need to be contributing to ubuntu (for example through universe), then apply for membership to CC, then apply for universe upload
[01:12] <raphink> right?
[01:13] <Kyral> I love easy bugfixes
[01:14] <\sh> raphink: yepp
[01:14] <raphink> say
[01:14] <raphink> I have already an account on launchpad
[01:14] <raphink> and 4 packages waiting in REVU
[01:14] <raphink> and my key is in the strong set
[01:14] <raphink> what is still required?
[01:14] <Kyral> Patience
[01:14] <raphink> haha
[01:14] <\sh> Kyral: i assgned the bug to me...i'm doing the xterm uploads normally for main :)
[01:14] <Kyral> \sh I saw
[01:15] <Kyral> Thanks for taking care of the upload
[01:15] <\sh> raphink: well...the CC will decide if your contributions are worth for ubuntu...u need to talk to some people from the CC board eventually to sabdfl himself
[01:16] <raphink> how do I know that people are members from the CC board?
[01:16] <raphink> apart from Mark ...
[01:16] <Kyral> Jeff Waugh...Matt Zimmerman....
[01:17] <raphink> ok
[01:17] <Kyral> Isn't Mako as well?
[01:17] <minghua> Aha, I think I've found a bug in ubuntu's X packages
[01:17] <Kyral> anyway. Bug killed. Another changelog entry. And last but not least, another decoration for my WikiPage
[01:17] <\sh> mako, elmo, and kamion i think
[01:21] <minghua> no, not X packages, but rather lesstif packages
[01:24] <minghua> anybody know the story about package libxp-dev?
[01:26] <\sh> grmpf..fixing gabber2
[01:26] <\sh> what is with libxp?
[01:27] <minghua> lesstif changelog has an entry about dropping libxp and libxp-dev dependency, saying they are out of ubuntu
[01:28] <minghua> however lesstif2-dev headers still include libxp-dev headers
[01:28] <minghua> in current dapper, libxp-dev and libxp6 seems to exist, altough labelled as obselete
[01:29] <minghua> BTW this is (one of) the real reason grace and grace6 FTBFS in dapper
[01:30] <\sh> minghua: Depends: lesstif2, libice-dev, libsm-dev, libx11-dev, libxext-dev, libxt-dev, libxrender-dev, libxft-dev, libfontconfig1-dev, libfreetype6-dev
[01:30] <\sh> which is the install dependency of lestiff2-dev
[01:30] <\sh> aeh lesstif2-dev
[01:31] <crimsun> I don't think libxp-dev is going away anytime soon
[01:31] <minghua> \sh: exactly.  and if you look at the debian package, libxp-dev is there
[01:32] <\sh> minghua: libxp was xprint right?
[01:32] <minghua> Argh, and lesstif has a SONAME bump from 0.93.94-11.4 to 0.94.4.-1?  Fun.
[01:32] <minghua> \sh: yes
[01:32] <minghua> It seems I'd better merge lesstif first
[01:33] <\sh> and I think daniels don't want to use xprint anymore
[01:33] <\sh> in his xorg stuff
[01:34] <minghua> \sh, that's okay, it seems libxp is separately maintained by siretart now
[01:34] <slomo> xprint is evil
[01:34] <minghua> well, evil is better than FTBFS :-)
[01:34] <crimsun> oh crap, ssl transition strikes.
[01:34] <slomo> he said to me, that if someone wants to maintain it he is fine with it... but he thinks that it should be dropped
[01:35] <siretart> hi
[01:35] <crimsun> (python2.4 is uninstallable)
[01:35] <minghua> hi siretart
[01:35] <\sh> slomo: wasn't libxp demoted to universe?
[01:35] <slomo> \sh: yes
[01:35] <siretart> minghua: libxp is deprecated, it should not be used as dependency where possible
[01:35] <Lathiat> unfortunately lots of 3rd party things are compiled against it, hence it needs to stick around yeh?
[01:35] <crimsun> it was? Still shows in main for me.
[01:36] <minghua> siretart: I am just merging packages, I don't really have enough expertise to judge that
[01:36] <siretart> minghua: the thing is that the j2re1.4 packages which we have in multiverse (you know, binary only shit) are linked against libxp, as well as a few other legacy apps
[01:36] <crimsun> (or perhaps just hasn't been anastacia-ised yet?)
[01:36] <Lathiat> for example if you download firefox, its compailed against libxp
[01:36] <siretart> minghua: so, if you can drop the dependency, do it. If not, well, we have libxp around
[01:36] <Lathiat> i think acroread is too
[01:36] <Lathiat> and yeh java
[01:36] <minghua> someone need to get rid of the libxp dependency from lesstif then
[01:36] <\sh> ChatViewManager.cc: In member function 'void Gabber::ChatViewManager::on_menu_item_activate()':
[01:36] <\sh> ChatViewManager.cc:107: error: 'manage' was not declared in this scope
[01:36] <minghua> I just want to merge grace :-(
[01:36] <\sh> but there is no "manage" at all this line
[01:37] <minghua> I don't really want to touch lesstif
[01:37] <minghua> siretart: it's not even the package I'm trying to merge
[01:37] <\sh> minghua: i don't see libxp even in lesstif1 or lesstif-dev
[01:38] <minghua> \sh: I need lesstif2-dev
[01:38] <\sh> minghua: lesstif2-dev there is no libxp
[01:39] <\sh> LOL what's up with seveas?
[01:39] <slomo> drunken? ;)
[01:40] <\sh> heheh
[01:40] <\sh> Seveas: alcohol or weed? or just the cat jumping on your keyboard? ,)
[01:41] <Seveas> alcohol :)
[01:41] <minghua> \sh: yes, but /usr/include/Xm/Print.h (from lesstif2-dev) #include's <X11/extensions/Print.h>, which only comes from libxp-dev as far as I can see
[01:41] <Seveas> Ubuntu NL has gathered
[01:41] <Seveas> and is drinking too much
[01:41] <minghua> \sh: no matter what, lesstif2-dev should depend on packages it includes headers from
[01:41] <wdh> join us all for this drinking bash :)
[01:42] <\sh> minghua: then include the build dep and recompile :) if it's necessary and needed and can't be patched out
[01:42] <minghua> \sh: I am arguing lesstif2-dev should depends on libxp-dev, and in Debian they do
[01:42] <\sh> minghua: but if it's compiled like this without complaining about Print.h then leave it
[01:43] <minghua> \sh: actually I'm not sure if it really uses libxp-dev or not, it just bail out at ./configure
[01:43] <\sh> minghua: we're not debian and we have different X server packages and an X maintainer, and when he says: no libxp anymore we try to follow :)
[01:43] <Kyral> sonuva
[01:44] <Kyral> EasyChem is borked more than I thought
[01:44] <minghua> \sh: no problem with that
[01:44] <minghua> \sh: but still a bug in lesstif2-dev, won't you agree?
[01:45] <\sh> minghua: again...where do u see libxp? it would be a bug if it pulls in libxp...but looking at the dev package and the deps of it..it doesn't
 \sh: yes, but /usr/include/Xm/Print.h (from lesstif2-dev) #include's <X11/extensions/Print.h>, which only comes from libxp-dev as far as I can see
[01:46] <\sh> oh ok...i misunderstood
[01:46] <minghua> \sh: the bug is it DOES NOT pull it in
[01:46] <siretart> minghua: does it ftbfs because of that?
[01:46] <\sh> siretart: na...
[01:46] <\sh> siretart: it installs an interface file which uses another interface file of a package which is not installed
[01:47] <minghua> siretart: it causes FTFBS for other packages that build-depends on lesstif2-dev
[01:47] <\sh> minghua: can't u patch out the printing stuff/
[01:47] <\sh> ?
[01:47] <siretart> neat :/
[01:47] <\sh> or rewrite it using other printing things?
[01:48] <\sh> siretart: bringing libxp in won't hurt for lesstif2
[01:48] <minghua> \sh: as I've said, it's an error in ./configure
[01:48] <\sh> it's universe...
[01:48] <Kyral> what is the i18n devpack?
[01:48] <minghua> \sh: and I am just not competent to fix this at all
[01:48] <\sh> minghua: hmmm
[01:49] <minghua> \sh, siretart: I'll just pull in libxp-dev myself and have it built, and note this is a workaround in changelog
[01:49] <\sh> minghua: wait
[01:49] <\sh> minghua: which packages are u working on?
[01:49] <\sh> minghua: grace?
[01:49] <minghua> \sh: grace
[01:50] <\sh> bug number?
[01:50] <minghua> \sh: yes, actually grace6 has the same problem, it was patched to pull in libxp-dev by previous universe merger
[01:50] <minghua> \sh: bug 4403
[01:50] <Ubugtu> Malone bug #4403: grace: merge new debian version Fix req. for: grace (Ubuntu), Severity: Normal, Assigned to: MOTU Merge Team, Status: Accepted http://launchpad.net/malone/bugs/4403
[01:51] <minghua> I scratched my head for quite a while yesterday when merging grace6 and saw this libxp-dev dependency patch that I don't understand
[01:52] <siretart> hm
[01:52] <siretart> this motif shit is really annoying :/
[01:53] <minghua> I think it doesn't really matter though, as most likely grace will have ubuntu-specific patches, due to hardcoded /usr/X11R6 silliness
[01:53] <minghua> bug 2387 for example
[01:53] <Ubugtu> Malone bug #2387: X11 binary file in wrong directory Fix req. for: grace (Ubuntu), Severity: Normal, Assigned to: MOTU, Status: New http://launchpad.net/malone/bugs/2387
[01:53] <minghua> grace6 had these patches, so even if lesstif2-dev is fixed, we can't just sync debian version anyway
[01:54] <\sh> minghua: so pull in libxp-dev into grace...
[01:54] <minghua> a dpkg-buildpackage testing run never hurts, which is what I'm doing :-)
[01:54] <\sh> or
[01:54] <\sh> no
[01:55] <\sh> the correct way is to pull libxp into lesstif1/2
[01:55] <minghua> \sh: yes, I agree the correct way is to pull libxp into lesstif
[01:55] <minghua> it's just that I don't want to touch lesstif (yet) :-P
[01:56] <\sh> i'll touch it
[01:57] <siretart> err,
[01:58] <siretart> \sh: what do you mean with 'pulling libxp-dev into grace'?
[01:58] <\sh> siretart: forget it...I'll add libxp-dev again to lesstif2 because it's using libxp-dev
[01:58] <siretart> \sh: I agree.
[01:59] <\sh> siretart: but waut
[01:59] <\sh> aeh wait
[01:59] <minghua> that's the way I want it too :-)
[01:59] <\sh> why it's including something from libxp and is not FTBFSing itself?
[02:00] <\sh> which can mean, that it includes something from another package but will never use it
[02:00] <minghua> \sh: It may well FTBFS as well
[02:00] <siretart> \sh: motif is evil [tm] 
[02:00] <\sh> minghua: it didn't FTBFS during breezy dev :)
[02:01] <\sh> minghua: lesstif2
[02:01] <minghua> \sh: yeah, just saw breezy has a new version, looks similar to the hoary version though
[02:02] <minghua> \sh: by the way it's lesstif1-1 in breezy
[02:02] <\sh> minghua: lesstif1 and lesstif2 are build out of one source package :)
[02:02] <\sh> which is lesstif1-1
[02:03] <minghua> \sh: yes, figured that out already
[02:03] <\sh> so...something is really wrong here
[02:03] <raphink> anyone to review my packages ? :)
[02:03] <Kyral> The merge is the priority I believe
[02:03] <minghua> \sh: the new lesstif2 in sid doesn't build lesstif1 anymore, though
[02:04] <\sh> minghua: because lesstif1 is somehow very very very old :)
[02:05] <minghua> older than me, perhaps? :-)
[02:06] <\sh> I think 1.2 I bought from delix in 1995/1996?
[02:06] <\sh> ok..I do an experiment
[02:06] <minghua> \sh: from debian changelog: * Upstream dropped support for lesstif1. Changing source package to
[02:06] <minghua>  lesstif2 and continuing the lesstif1 package separately.
[02:06] <\sh> *g*
[02:07] <Kyral> EasyChem is ready to go
[02:07] <minghua> so do we want to split lesstif1/2 as well?
[02:07] <\sh> ok..I commented in the include statement of libxp include
[02:07] <\sh> in Xm/Print.h of Motif2.1
[02:07] <Kyral> should I add a Debian Menu entry before I upload it to REVU first...
[02:09] <\sh> minghua: could u try something?
[02:10] <minghua> \sh: sorry, try what?
[02:10] <\sh> minghua: you are using pbuilder right
[02:10] <\sh> ?
[02:10] <minghua> yes
[02:11] <minghua> \sh: if you want me to just remove the include of libxp header in Xm/Print.h, I can do that
[02:11] <\sh> ok..pbuilder login --save-after-login ... then apt-get install lesstiff2-dev then edit this Print.h file from lesstiff2 and comment in the include statement of the libxp interface pls
[02:11] <minghua> I know how to handle pbuilder stuff
[02:12] <minghua> \sh: I am actually manually building in a pbuidler chroot now :-)  so making changes are easy
[02:12] <\sh> minghua: that would be nice to try this
[02:13] <minghua> \sh: by "comment" you mean "make the include statement a comment, and not effective anymore", right?
[02:14] <\sh> yes...comment in == make the include statement a comment :)
[02:14] <minghua> okay, I usually say "comment out" though :-(
[02:14] <minghua> I'd better look up in dict later...
[02:15] <Kyral> Jeez, how do I stop these manpage errors
[02:15] <Kyral> its an X11 app, it has help built in
[02:16] <\sh> minghua: well...add a // in front of the #
[02:16] <\sh> hehe
[02:17] <Kyral> what does this mean..
[02:17] <Kyral> W: easychem source: source-contains-CVS-dir po/CVS
[02:18] <lfittl> siretart: Could you do a quick review of the debdiff for http://revu.tauware.de/details.py?upid=975 and advocate it again?
[02:18] <Kyral> Oh well, package going up :D
[02:19] <\sh> Kyral: that the source wasn't CVS clean
[02:19] <\sh> or isn't actually
[02:19] <Kyral> which means..?
[02:20] <\sh> Kyral: if u do a cvs checkout from a cvs repos. there are CVS directories created
[02:20] <\sh> Kyral: those directories shouldn
[02:20] <Kyral> oh
[02:20] <\sh> 't be in the source for an release
[02:20] <\sh> to prevent this, there is cvs export
[02:20] <Kyral> It came like that....how do I fix it...
[02:20] <\sh> Kyral: new package or are you fixing something?
[02:20] <Kyral> new package
[02:21] <\sh> Kyral: so something for universe via revu?
[02:21] <Kyral> it should hit REVU in a couple secs
[02:21] <Kyral> yah
[02:21] <\sh> Kyral: oh..ok...then check the source orig.tar.gy
[02:21] <\sh> z
[02:21] <Kyral> I have the source on my HD :D
[02:23] <minghua> \sh: no, that won't work.  now I have:
[02:23] <minghua> /usr/include/Xm/Print.h:42: error: syntax error before 'XPContext'
[02:23] <minghua> /usr/include/Xm/Print.h:45: error: syntax error before '}' token
[02:23] <minghua> /usr/include/Xm/Print.h:63: error: syntax error before 'XPFinishProc'
[02:23] <minghua> \sh: it seems Xm/Print.h indeed uses the data structure in libxp
[02:24] <minghua> \sh: this is still just ./configure test though, not the real source
[02:24] <Kyral> wait a sec
[02:24] <minghua> \sh: but as I've said, I'm not competent to mess with ./configure script
[02:24] <Kyral> what is lintian talking about, I don't see a CVS dir anywhere
[02:25] <beezly> is anyone else working on packaging dogtail? I see it is in https://wiki.ubuntu.com/UniverseCandidates
[02:26] <minghua> Kyral: lintian told you it's po/CVS
[02:26] <Kyral> and I'm telling you there isn't a CVS dir there
[02:27] <Kyral> its in the orig.tar.gz
[02:27] <Kyral> but not in the unpacked tree
[02:27] <\sh> Kyral: i told u to check the orig.tar.gz
[02:27] <Kyral> yah yah, me an idiot
[02:28] <\sh> Kyral: actually those things are removed...and that's why u have a diff.gz it's the diff between the working debianized dir and the orig tar
[02:29] <Kyral> then how do I knock out the warning from lintain?
[02:29] <\sh> Kyral: but if it's in the orig.tar.gz leave it...don't change it...better to kick upstreams bum
[02:29] <\sh> forget them
[02:29] <Kyral> k
[02:29] <Kyral> other than that lintian has no beef with the package
[02:29] <\sh> minghua: what about grace now? is it complaining?
[02:30] <\sh> oh sorry backlog
[02:30] <\sh> minghua:ok then...I'll add libxp-dev back to the build deps
[02:31] <minghua> \sh: pity.  it seems grace don't need any other patch though
[02:31] <minghua> \sh: so if this is solved we can actually sync from debian
[02:31] <minghua> but whatever
[02:32] <\sh> minghua: just a minute :)
[02:33] <\sh> ok..uploaded
[02:33] <\sh> lesstif1-1 that is
[02:33] <\sh> now u can check the buildds when the package build, wait for the archives and sync it or mark it to be synced
[02:35] <Kyral> Actually I need a new package pulled in from Debian
[02:35] <minghua> one more thing about grace, though:  the previous ubuntu patch has a tightened build dependency defoma (>= 0.11.8ubuntu2), I believe this can be safely dropped now, right?
[02:36] <\sh> minghua: defoma has to be merged anyways
[02:36] <minghua> \sh: oh really?  but previous merger of grace6 dropped them
[02:37] <minghua> hoary, breezy and dapper all have 0.11.8ubuntu2 after all
[02:37] <minghua> I don't mind doing a merge, of course
[02:38] <minghua> I just want to reduce unnecssary ubuntu specific versions
[02:38] <Kyral> who do I ask to sync a new package from Debian?
[02:38] <tseng> he wont listen to you, if you arent on the motu list
[02:38] <\sh> minghua: sorry I was mistaken with defoma
[02:39] <tseng> youll need to convince a sponsor
[02:39] <Kyral> oh
[02:39] <minghua> \sh: cool, then.  I'll wait for your new lesstif1-1 built, test the debian version in pbuilder, and ask for a sync
[02:40] <minghua> Is asking for sync still slow these days, BTW?
[02:40] <ajmitch> yes
[02:40] <Kyral> yah imview-doc should be painless...
[02:41] <minghua> this encourages spurious ubuntu changes :-(
[02:42] <foampeace> exit
[02:42] <\sh> minghua: because having a small delta is that what we want....so having a sync is a goal..so a sync is more worth then a normal upload
[02:44] <minghua> \sh: I agree completely.  I am arguing things worth more should be easier to do ;-)
[02:45] <minghua> \sh: just my personal rant though, never mind
[02:45] <\sh> minghua: well..we only have one ftpmaster today...and we will have a better solution when soyuz landed in the next couple of weeks
[02:45] <Kyral> what is soyuz in this context?
[02:46] <\sh> https://wiki.launchpad.canonical.com/SoyuzSpecification
[02:46] <slomo> \sh: but kamion and mdz already can do some of elmo's tasks
[02:48] <slomo> \sh: btw, please read the heise article about windows... somewhat funny ;)
[02:49] <\sh> slomo: yes...but only in very important times..but having a list of syncs handy  and sending a mail to elmo once a week is much better then bothering every 5 mins kamion, mdz or elmo via irc
[02:50] <slomo> \sh: elmo never read my mails when i sent them to him once... so i changed my strategie and told him to sync some stuff on irc at the time i found it and every day the stuff he forgot
[02:52] <ajmitch> elmo has a large list of things to do
[02:53] <\sh> slomo: hahahahah....funny article
[02:53] <slomo> yes, that's exactly the problem :/ one poor man with a todo list growing to infinity...
[02:54] <slomo> \sh: i like this passage: "Um Windows ranken sich heute viele Mythen. Am bekanntesten ist der von der "intuitiven Benutzeroberflche", die die Arbeit am PC erleichtert." :)
[02:54] <\sh> slomo: and i like "bis die Arbeit vereinfacht wurde und gleichzeitig die Nutzer so geschult waren, dass sie die Arbeit mit Windows als Vereinfachung begriffen."
[02:56] <slomo> \sh: that's in the same passage... :P never show a somewhat non-interested windows user linux without preparing him... he will tell you that everything is not logical because he is accustomed to other things ;)
[03:02] <\sh> yeah
[03:02] <\sh> so now to bed...
[03:02] <\sh> cu later
[03:02] <slomo> gn9 :)
[03:02] <slomo> gn8 ;)
[03:30] <zakame> hello
[04:26] <bmonty_laptop> ok, if I have a packege that builds in my pbuilder but fails on the buildd, what's the best way to go about fixing the issue?
[04:28] <minghua> bmonty_laptop: first find out why it fails on buildd, perhaps? :-P
[04:30] <bmonty_laptop> yeah, except where it fails on the buildd makes no sense to me...it is calling automake1.8, but the build depend is for 1.9 and it doesn't happen in my pbuilder
[04:30] <bmonty_laptop> it would make sense to me if I could reproduce the error during my own build
[04:32] <minghua> bmonty_laptop: a pointer to the buildd log, please?
[04:33] <bmonty_laptop> http://people.ubuntu.com/~lamont/buildLogs/f/fnfx/0.3-7ubuntu1/fnfx_0.3-7ubuntu1_20051118-1846-i386-failed.gz
[04:36] <crimsun> actually what you need to do is build-depend on libtool as well
[04:36] <minghua> bmonty_laptop: weird indeed
[04:36] <crimsun> then before you actually call ./configure, make sure you autoreconf -f -i
[04:36] <crimsun> what's happening is that there's a timestamp skew
[04:37] <crimsun> (welcome to the glorious world of autotoolage)
[04:38] <crimsun> hmm, any main uploaders still awake?
[04:39] <crimsun> there are packages that need to be transitioned to libssl0.9.8
[04:39] <bmonty_laptop> crimsun: odd, let me see if I can get this correct, then would you mind taking a look?
[04:39] <crimsun> bmonty_laptop: sure
[04:39] <crimsun> (though the coffee shop closes in 20 minutes)
[04:43] <bmonty_laptop> its building in my pbuilder now
[04:46] <bmonty_laptop> crimsun: http://www.montynet.org/ubuntu/fnfx_0.3-7ubuntu2.debdiff
[04:47] <bmonty_laptop> it builds OK in the pbuilder
[04:48] <crimsun> that should do it.
[04:49] <bmonty_laptop> ok, do you want to upload it, or should I stick it back on the merge bug?
[04:51] <crimsun> uploaded.
[04:52] <bmonty_laptop> thanks
[04:52] <bmonty_laptop> how did you know that timestap skew was the problem?
[04:53] <crimsun> that plagued half the packages I touched for Hoary.
[04:54] <crimsun> anytime auto* are being called when they're not supposed to be, you can guess that a timestamp's amiss somewhere
[04:54] <crimsun> some packages prevent this by touching them all before running ./configure
[04:55] <bmonty_laptop> ok, is it an issue with ubuntu's buildd, or should I push that to debian?
[04:55] <zakame> you could also do a full rebuild of the autotools and set AM_MAINTAINER_MODE
[04:55] <crimsun> you probably want to talk with the Debian maintainer about incorporating that change (autoreconf)
[04:56] <crimsun> yeah, AM_MAINTAINER_MODE is good
[04:56] <bmonty_laptop> hmmm, guess I need to learn more about autotools
[04:56] <zakame> also, some packages also automatically rebuild the autotools in the debian/rules
[04:58] <bmonty_laptop> so basically it remakes the configure script and then runs it?
[04:58] <crimsun> yep
[04:58] <zakame> exactly
[04:58] <crimsun> gah, time to find another wireless AP
[04:59] <zakame> laterz ppl :D
[04:59] <bmonty_laptop> bye zakame
[05:00] <bmonty_laptop> crimsun: that could be hard or easy depending on where you are
[05:09] <ajmitch> hello chillywilly
[05:11] <bmonty_laptop> goodnight everyone
[05:11] <bmonty_laptop> crimsun: thanks for your help
[06:15] <Kyral> hoy LJ
[06:16] <LaserJock> hi Kyral
[06:17] <minghu1> hi LaserJock
[06:21] <LaserJock> how's it going for you guys?
[06:24] <minghu1> quite good.  how about you LaserJock?
[06:26] <LaserJock> I'm at my grandparents for the weekend and I need to go to bed but I did get my package on REVU reviewed today so that's cool
[06:28] <minghu1> that's good news :-)
[06:31] <LaserJock> minghu1: well it was especially good because I got a + vote
[07:24] <Kyral> Any MOTUs that have a sec could you look over my EasyChem package in REVU?
[08:42] <zakame> hi robitaille
[08:42] <robitaille> Hello zakame
[10:34] <zakame> heya
[10:35] <crimsun> hi
[10:36] <zakame> hi pef
[10:37] <pef> heya zakame  :)
[12:21] <raphink> hi
[12:22] <raphink> I'm packaging an app that runs on ruby files
[12:22] <raphink> there's no installer yet, so i'm doing a .install
[12:22] <raphink> where should the .rb files go?
[12:22] <raphink> in /usr/share/apps/$myapp/ ?
[12:23] <StrikeForce> what package has aclocal in it?
[12:24] <StrikeForce> also I get this error when compiling with the standard cf flags " C compiler cannot create executables"
[12:24] <StrikeForce> has anyone come across it?
[12:27] <crimsun> StrikeForce: aclocal-foo is in automakefoo
[12:27] <crimsun> StrikeForce: you need build-essential installed, of course, unless you're getting that message in a pbuilder
[12:28] <StrikeForce> kk
[12:28] <StrikeForce> thanks
[12:28] <StrikeForce> yep
[12:28] <StrikeForce> crimsun, have you seen the the C compiler error before?
[12:29] <crimsun> not in a pbuilder, no.
[12:29] <StrikeForce> crimsun: its the cflags however I'm not sure which one is getting the issue
[12:29] <crimsun> what CFLAGS are you using?
[12:29] <StrikeForce> the standard ones from dh_make
[12:29] <StrikeForce> CFLAGS="Wall -g -O2 -Wl,-z,defs" ./configure --host=i486-linux-gnu --build=i486-linux-gnu --prefix=/usr
[12:29] <StrikeForce> thats obviously with the information added
[12:29] <crimsun> Wall is invalid
[12:30] <StrikeForce> ?
[12:30] <StrikeForce> I thought it was ok?
[12:30] <crimsun> it's -Wall
[12:30] <crimsun> the leading hyphen is extremely important
[12:30] <StrikeForce> ahh ok
[12:30] <StrikeForce> thats why let me check now
[12:30] <StrikeForce> god I'm dumb
[12:31] <StrikeForce> still a cflags issue though overall :(
[12:31] <crimsun> why are you tacking on all that?
[12:32] <StrikeForce> It compiles without it but I want to put 'as much' as I can into it
[12:32] <StrikeForce> should I just leave it without the flags?
[12:32] <StrikeForce> if it works?
[12:32] <crimsun> "as much" being...?
[12:32] <StrikeForce> trying to make it as efficient as possible
[12:32] <StrikeForce> apart from that nothing
[12:32] <crimsun> oh god, don't do that
[12:32] <StrikeForce> no reason for doing it
[12:32] <StrikeForce> just apart that its there
[12:33] <crimsun> remember our common denominator is i386
[12:33] <crimsun> it has to run on i386
[12:33] <StrikeForce> ok well using the standard ./configure make make install works
[12:33] <StrikeForce> so just leave it at that then?
[12:33] <crimsun> so don't tack anything extra onto your CFLAGS
[12:33] <crimsun> CFLAGS=$(CFLAGS) ./configure [...] 
[12:34] <crimsun> ideally you don't even touch that
[12:34] <StrikeForce> yep
[12:34] <StrikeForce> well it works fine now
[12:34] <slomo_> but never hardcode any i386 CFLAGS...
[12:35] <crimsun> right. We also support ppc
[12:35] <slomo_> and amd64 and ia64.... ;)
[12:35] <crimsun> the sbuilders are intelligent enough to do their magic.
[12:36] <StrikeForce> ok
[12:36] <StrikeForce> well I'll remember that for the future
[12:36] <StrikeForce> thanks heaps for the help :)
[12:36] <StrikeForce> now on to the man pages
[12:36] <StrikeForce> on a side note
[12:37] <StrikeForce> I've got as build deps autoconf, automake1.7
[12:37] <StrikeForce> it compiles without them but they are checked for in the config? should I leave them in there?
[12:38] <crimsun> what do you mean they're "checked for in the config"?
[12:38] <StrikeForce> in the configure script
[12:39] <StrikeForce> it generates a message to say you /might/ need it
[12:39] <StrikeForce> but it isn't essential
[12:39] <crimsun> then remove them.
[12:39] <StrikeForce> ok
[12:42] <jpatrick> StrikeForce: I think that its better to use automake1.9
[12:42] <StrikeForce> as I said though its not required build dep although I'm double checking now
[12:43] <crimsun> jpatrick: only if that's the -minimum- version that works across all arches
[12:45] <raphink> question : in the app I'm packing is no .desktop. I created one at the root of the source as a patch and added it to the debian/$myapp.install so it's installed by the package. Now when build the package it says it can't find the .desktop file although it has applied the patches. Any idea ?
[12:45] <raphink> s/packing/packaging/
[12:54] <raphink> it seems it doesn't create the .deskop in the right place... Should I put it in debian/ instead ?
[12:55] <pef> Riddell: can you have a look ? http://revu.tauware.de/details.py?upid=977
[12:56] <Riddell> pef_aw: will do (later today, off to see Harry Potter just now)
[01:17] <\sh> moins
[01:22] <crimsun> moin \sh
[01:22] <crimsun> \sh: would you kick vorbis-tools please? It needs a rebuild for the openssl 0.9.8 transition
[01:23] <freeflying> why can't I upload to revu now
[01:24] <\sh> crimsun: sure
[01:24] <crimsun> \sh: thanks!
[01:24] <\sh> hmmm
[01:24] <\sh> it's more libcurl?
[01:25] <freeflying> It give me message like this :Note: This problem might be caused by files already existent on the server.
[01:25] <\sh> there is no build dep on libssl
[01:25] <freeflying> but I use the force option
[01:27] <\sh> so I'll rebuild it
[01:28] <crimsun> \sh: right, it just needs to be rebuilt against the new libcurl3-dev
[01:29] <crimsun> (since the older one depends on libssl0.9.7, which no longer is in pool)
[01:30] <\sh> yepp
[01:33] <\sh> crimsun: done
[01:33] <crimsun> \sh: thanks :)
[01:34] <\sh> freeflying: u increased the version number?
[01:35] <freeflying> \sh: haven't
[01:35] <freeflying> \sh: I rewrite rules,and the version number is the same
[01:36] <\sh> freeflying: that is your problem
[01:36] <\sh> u have to increase the version number, so that revu can throw away the old version
[01:37] <freeflying> \sh: then , what shall i do
[01:37] <\sh> freeflying: what is your version numbering scheme anyways?
[01:37] <\sh> we discussed it and it should be 0ubuntu0.1 (for the very first upload to revu)
[01:38] <freeflying> \sh: I'll do it
[01:54] <StrikeForce> \sh, has it changed to that number sequence?
[01:55] <StrikeForce> \sh, should I change all my numbers and re-upload?
[02:03] <freeflying> \sh: how can i delete what I've uploaded to revu before
[02:03] <\sh> StrikeForce: no...but for new packages we should use this numberscheme..because the first real upload to universe will be 0ubuntu1
[02:03] <StrikeForce> \sh, thats how I've done it
[02:03] <StrikeForce> 0ubuntu1
[02:04] <\sh> freeflying: u can't but I can..what's the package name?
[02:04] <\sh> StrikeForce: yes...but this will be for the first real universe upload...for revu we should use the 0ubuntu0.n scheme..it's easier then to update to 0ubuntu1 and upload it to universe
[02:05] <StrikeForce> \sh, ok no worries
[02:05] <StrikeForce> \sh, do you mind revu'ing the packages I have uploaded
[02:05] <StrikeForce> \sh, theres been 3 of em so far
[02:06] <StrikeForce> \sh, when you get time though
[02:07] <freeflying> \sh: skim
[02:08] <freeflying> \sh: plz  delete them
[02:09] <\sh> freeflying: please increase the version number now to 2
[02:09] <\sh> 0ubuntu2 please and reupload
[02:10] <freeflying> \sh: thanx
[02:14] <siretart> hi
[02:14] <siretart> \sh: revu does not care about version numbers
[02:15] <siretart> \sh: I think just preparing 'upload candidates' with the version number aimed to be in the archive is just fine
[02:15] <siretart> \sh: Or did I misunderstand you?
[02:15] <StrikeForce> hi siretart
[02:15] <minghua> \sh: hi, your lesstif1-1 upload didn't fix my problem
[02:16] <minghua> \sh: I need a dependency on libxp-dev for lesstif2-dev, not a build-dependency for (source package) lesstif1-1
[02:19] <\sh> minghua: u'll get it
[02:20] <\sh> in at least 1h :)
[02:26] <minghua> \sh: thanks
[02:41] <freeflying> siretart: when can access the package i upload to revu after i upload it
[02:42] <siretart> freeflying: should work instantly
[02:42] <freeflying> why can't i access to what I've uploaded
[02:43] <freeflying> siretart: the package is skim
[02:46] <siretart> freeflying: you uploaded a binary package
[02:46] <freeflying> I built it with source package
[02:46] <siretart> freeflying: we cannot review binary packages, so revu is ignoring them. please upload SOURCE packages, as instructed on wiki.ubuntu.com/REVU
[02:47] <siretart> freeflying: you uploaded a skim_1.4.3-0ubuntu2_i386.changes instead of a skim_1.4.3-0ubuntu2_source.changes
[02:47] <jpatrick> \sh: can you check http://revu.tauware.de/details.py?upid=968 ?
[02:47] <freeflying> siretart: thanks ,got it
[02:48] <siretart> freeflying: please check before you upload if the *_source.changes references the orig.tar.gz
[02:49] <StrikeForce> that pbuilder bug
[02:49] <StrikeForce> how do I fix it?
[02:49] <herve> hello
[02:49] <StrikeForce> hi
[02:49] <jpatrick> herve: hi
[02:50] <freeflying> siretart: may you delete them all
[02:50] <StrikeForce> reading the responses confused me
[02:50] <siretart> freeflying: done
[02:50] <freeflying> siretart: thanks
[02:50] <StrikeForce> grep: /var/cache/pbuilder/build//7902/etc/shadow: No such file or directory that bug?
[02:52] <\sh> jpatrick: check the comments
[02:52] <\sh> StrikeForce: pbuilder login --save-after-login
[02:53] <\sh> StrikeForce: touch /etc/shadow
[02:53] <\sh> StrikeForce: exit
[02:53] <\sh> StrikeForce: it's a known issue and distro team will fix it
[02:53] <StrikeForce> \sh, I know I read that I was trying to work around it in the mean time
[02:55] <jpatrick> \sh: working on it
[02:57] <jpatrick> \sh: $(MAKE) -f admin/Makefile.common ;\ <- that line?
[02:57] <\sh> yepp
[03:02] <jpatrick> \sh: reuploaded http://revu.tauware.de/details.py?upid=969
[03:08] <\sh> jpatrick: u have still a \ left :)
[03:08] <jpatrick> ah
[03:11] <ptlo> hi all. there's a package in UniverseCandidates (sysprof) that I'd like to have on my ubuntu (breezy), and I've searched the net and found someone preparing .debs for Ubuntu (Breezy&Dapper). I'm not MOTU, but can I edit the UniversePackage to provide the deb locations in the 'status' field, or should I bug someone about that?
[03:12] <ptlo> (i've installed those debs on my system, no problem, but i believe that the above action would benefit more than me, so that's why i ask)
[03:12] <siretart> ptlo: so you have prepared a source package for your application?
[03:12] <siretart> ptlo: what software are you talking about?
[03:13] <ptlo> siretart, it's not my app. i'm talking about sysprof (system profiler for gnome). there are source packages available for it, the guy that did it says he'll happily give them over to some MOTU or debian packager..
[03:14] <\sh> provide us with the url on the wiki page then
[03:14] <ptlo> ok
[03:14] <jpatrick> \sh: done
[03:15] <\sh> jpatrick: u uploaded it?
[03:15] <jpatrick> \sh: http://revu.tauware.de/details.py?upid=981
[03:18] <\sh> building now
[03:23] <\sh> jpatrick: now ask riddell :)
[03:23] <ptlo> I've updated the UniverseCandidates page. if there's anything more i could do, please let me know
[03:40] <\sh> bbl
[03:49] <Kyral> mornin'
[03:49] <raphink> hi Kyral
[03:50] <Kyral> hey
[03:52] <Kyral> About the ability to login as root to the GUI. "Its not a bug, its a feature". Normally I don't like that response, but here I love it :D
[03:54] <Gloubiboulga> hello
[03:54] <Kyral> yo
[04:04] <Gloubiboulga> I have a little question about merges
[04:05] <Gloubiboulga> the debdiff provided will be run against the ~scott sources, am I right?
[04:06] <raphink>  $ lintian /var/cache/pbuilder/result/kalcul_0.1-0ubuntu1_i386.deb
[04:06] <raphink> W: kalcul: non-dev-pkg-with-shlib-symlink usr/lib/libkdeeduwidgets.so.0.0.0 usr/lib/libkdeeduwidgets.so
[04:06] <raphink> W: kalcul: package-name-doesnt-match-sonames libkdeeduwidgets0
[04:06] <raphink> how do I fix that,
[04:06] <raphink> ?
[04:08] <raphink> I guess usr/lib/libkdeeduwidgets.so.0.0.0 should be in libkdeedu-dev
[04:09] <raphink> should I mail the libkdeedu-dev maintainer about this ?
[04:10] <raphink> Riddell:
[04:23] <bmonty_laptop> good morning everyone
[04:23] <Kyral> morning
[04:23] <raphink> hi bmonty_laptop
[04:23] <Kyral> hows things?
[04:24] <raphink> Kyral: do you know about my issue with the kdeedu library?
[04:24] <raphink> :s
[04:24] <Kyral> nope, nor do I know what kdeedu is
[04:24] <raphink> kdeedu is the KDE Edutainment project
[04:24] <poningru> !info kdeedu
[04:24] <Kyral> I should really install KDE just so I can be more knowledgeable about it so I can help support it
[04:25] <raphink> my problem is that I'm packaging a program that is installing a kdeedu library
[04:25] <poningru> hi guys I wasn wondering I would get started with helping etc.
[04:25] <raphink> so lintian tells me a binary package shouldn't install a libary
[04:25] <Kyral> I kinda feel bad that I cannot help with KDE
[04:25] <poningru> is it just pick a package and work on it?
[04:26] <Kyral> I know only GNOME and XFCE (and my GNOME knowledge is somewhat slipping)
[04:26] <raphink> so i'm wondering if I should email the kdeedu library manager about it so he can add this lib
[04:26] <bmonty_laptop> poningru: have you looked at the MOTU pages in the wiki?
[04:26] <poningru> hmm
[04:27] <Kyral> I need a more powerful subwoofer
[04:28] <bmonty_laptop> poningru: you should look through the MOTU pages (CategoryMOTU), the main effort right now is https://wiki.ubuntu.com/MOTUToSync
[04:28] <Kyral> or kill bugs :D
[04:28] <Kyral> gotcha
[04:29] <poningru> looking
[04:31] <bmonty_laptop> hey Nafallo
[04:31] <Kyral> anyway breakfast
[04:32] <Kyral> cya guys
[04:32] <Nafallo> morning.
[04:32] <Nafallo> and out again, later.
[04:34] <Gloubiboulga> bmonty_laptop, maybe you can answer me about merges
[04:35] <bmonty_laptop> Gloubiboulga: I'll try
[04:35] <Gloubiboulga> The debdiff I have to provide shoul be applied against the ~scott sources, ri gth ?
[04:35] <Gloubiboulga> should
[04:36] <bmonty_laptop> I do the debdiff against the latest from unstable
[04:36] <Gloubiboulga> ok, so the sources to be used are the debian ones
[04:36] <bmonty_laptop> you can't debdiff against the merged package, because that already has the changes we are trying to bring into ubuntu
[04:36] <Gloubiboulga> ok thanks
[04:38] <bmonty_laptop> Gloubiboulga: when I start working on a package, the first thing I do is grab the source package from debian
[04:41] <siretart> is there a list of package affected by openssl 0.9.8?
[04:43] <bmonty_laptop> I don't think so
[04:44] <bmonty_laptop> hmm...I just did an rdepends on libssl0.9.7...its a long list :(
[04:45] <bmonty_laptop> 463 packages
[04:53] <Kyral> Thats gonna be a NASTY transition
[05:28] <rbelem> ls
[05:28] <rbelem> ops... wrong terminal
[05:31] <\sh> re
[05:33] <siretart> hi \sh!
[05:33] <siretart> \sh: how are you?
[05:33] <\sh> well...I think I don't have any jetlag problems anymore
[05:34] <\sh> but i'm missing armagetron from yesterdays upload...not the failed one, I uploaded a new one
[06:06] <\sh> siretart: how is revu2 going?
[06:11] <siretart> \sh: nothing visible atm. I'm still playing with madison-lite, because I need it for some stuff 'under the hood'
[06:12] <siretart> \sh: I want 'fetchpackage sid libfoo' to download the latest version of libfoo from unstable, but this must not be too expensive implemented. madison-lite seems to be a promising base for that
[06:13] <\sh> well..can't we fix apt-get?
[06:14] <siretart> hm.
[06:14] <siretart> you can try, if you want
[06:15] <\sh> well..apt-get source foo=sid or something should work
[06:15] <\sh> but it doesn't
[06:15] <siretart> I'd be happy if 'apt-get -t <dist> source <sourcepackagename>' would download me the latest sourcepackage of that distribution
[06:15] <\sh> yeah..thats what i meant
[06:15] <siretart> and btw, I still need a cheep way of determining the version in a given distribution
[06:16] <\sh> siretart: grep-dctrl?
[06:16] <siretart> I need to determine cheap if an version number of an upload is bigger or lower than in a given distribution
[06:17] <siretart> \sh: jepp. I inteded to run grep-dctrl on the partial mirror used by madison lite. or by extending madison-lite itself
[06:17] <siretart> so you get my current status :)
[06:17] <\sh> well..I'm working still on glpbugs...
[06:18] <\sh> finding (source) packages works and now I'm doing the configuration..after that I want to implement update and close bug features...
[06:18] <siretart> cool :)
[06:18] <\sh> the UI looks fine...and if i'm doing it the right way...i can easily add a kde ui as well
[06:19] <Kyral> whats up
[06:20] <Kyral> I didn't realize the first Flight was released
[06:21] <\sh> it was announced
[06:21] <Kyral> I must not have paid attention to the Devel list
[06:22] <Kyral> most of the time during the week I skim it fast
[06:22] <\sh> subscribe to ubuntu-devel-announce :)
[06:22] <Kyral> or that could be why I didn't get it....lol
[06:23] <Kyral> hey ogra
[06:24] <\sh> moins ogra darling
[06:36] <Kyral> Oh well, I guess this is what 2 GB+ GMail Accounts are for
[06:36] <\sh> Kyral: idon
[06:36] <\sh> grmpf
[06:36] <Kyral> ?
[06:36] <\sh> i don't use my gmail account :)
[06:37] <\sh> only for porn ,-)
[06:37] <Kyral> lol
[06:37] <Kyral> I wouldn't but when I was subscribed with my college email, the flood of emails triggered them to block @ubuntu.com :P
[06:37] <Kyral> or at least the MLs
[06:44] <siretart> \sh: you have some mailinglists distributing porn?! ;)
[06:44] <\sh> siretart: u need some?
[06:44] <\sh> hehehe
[06:44] <siretart> hrhr
[06:45] <\sh> well...i think working on ubuntu will give anyone a changed sexual life
[06:46] <\sh> one wants to wear women clothes, the other one wants to have porn in his gmail mailbox
[06:50] <siretart> could be just by chance ;)
[06:51] <\sh> siretart: better sex? the people are looking at you with fear?
[06:52] <\sh> phew...food was nice
[06:52] <siretart> :)
[06:54] <bmonty_laptop> siretart: I have a quick off-topic python question for you...
[06:54] <bmonty_laptop> mind if I /msg it?
[06:54] <siretart> go on
[06:56] <bmonty_laptop> \sh: over to you, if I want to do a GUI with python, what is the prefered binding, pygtk or gtk?
[06:56] <siretart> I'm inclined to suggest pygtk
[06:56] <slomo_> i thought there only is pygtk...
[06:57] <bmonty_laptop> all the examples show an "import pygtk" and if that fails they "import gtk"
[06:58] <bmonty_laptop> I want to make an app that is ubuntu specific, so I want to make sure I use the correct binding
[06:58] <\sh> bmonty_laptop: pygtk to set the version u need
[06:58] <slomo_>         import pygtk; pygtk.require("2.0")
[06:58] <slomo_>         import gtk
[06:58] <slomo_> that's what i often see
[06:58] <\sh> import pygtk
[06:58] <\sh> pygtk.require('2.0')
[06:58] <\sh> import gtk
[06:58] <\sh> import gnome
[06:58] <\sh> import gnome.ui
[06:58] <\sh> from gtk import glade
[06:59] <bmonty_laptop> ok, thanks
[06:59] <\sh> the module name of gtk is for gtk 1 and gtk2 the same...pygtk let u decide which version u need...and decides where to look
[07:00] <bmonty_laptop> and using gnome would be the prefered method for the GUI?
[07:17] <Gloubiboulga> bye
[07:44] <sivang> rehi all
[07:52] <ajmitch> morning
[07:58] <bmonty_laptop> hey ajmitch
[08:03] <\sh> does anybody know from where gnome-themes-extras is synced from? i don't find it on unstable
[08:03] <\sh> argl forget it..
[08:03] <\sh> its named gnome-themes-extras and not gnome-theme-extras
[08:40] <sivang> \sh: Stephan, what mood are you in? Would you mind giving me a small walkthrough of packaging from scratch of a python software as an example? Don't hesistate to tell me to "bugger off" if you don't feel like
[08:41] <\sh> sivang: depends on the piece of python code...is it using the python setup.py?
[08:42] <\sh> sivang: actually did u read the debian new maintainers guide?
[08:43] <sivang> \sh: if you tell me it has something about python code, I will go and re read it. yes, I have read it, either it's me who's dumb, but I didn't really get anything useful from there. At least not to a different package then the one the NM guide was demonstrating :)
[08:44] <\sh> sivang: well it gives u most of the stuff u need
[08:44] <\sh> sivang: u need debhelper and dh_make
[08:44] <sivang> \sh: ok, noted. I already know dh_make creates the Makefile skeleton, how to I work with the stuff it spitts into my rule file?
[08:45] <\sh> sivang: remove everything from the debian/ dir, which dh_make creates, what u don't need...and then we can start to talk about python specials
[08:45] <sivang> \sh: ok, cool. I have a small python script which I like to get packaged cleanly, I'll go make some preperations and come back
[08:45] <\sh> sivang: pay attention to configure target and build target..this u have to change to fulfill the needs of your package
[08:45] <\sh> sivang: upload it to revu so i can check :)
[08:46] <sivang> \sh: well, first I'd have to get the package ready :)
[08:51] <herve> hello
[08:53] <sivang> hey herve , 'sup?
[08:53] <herve> had a nice week-end!
[08:59] <Kyral> This should be an interesting experiment
[09:00] <Kyral> ubuntu-desktop, xubuntu-desktop, and kubuntu-desktop, all on the same thing
[09:03] <\sh> it works it has to...i'm running ubuntu/kubuntu-desktop
[09:03] <Kyral> well, xubuntu-desktop is broken
[09:03] <Kyral> because of hplip
[09:03] <Kyral> I just want to learn more about KDE so I can help more people
[09:04] <Kyral> and its also broken
[09:04] <Kyral> due to the openoffice.org2 package
[09:06] <Kyral> well, xubuntu-desktop is fixed
[09:06] <Kyral> hehe *fires up The GIMP*
[09:34] <azeem> anybody know how/whether Ubuntu handles the g++ allocator change library renames?
[09:35] <herve> yes we do
[09:36] <sivang> azeem: IIRC, dholbach is assigned to do that or so I've seen in discussions from the previous week
[09:38] <siretart> azeem: doko said he will send a follow up when we are ready
[09:38] <azeem> ok, so you're doing it right now, same way as Debian does?
[09:38] <Kyral> I stink at GFX
[09:38] <siretart> azeem: he has uploaded updated gcc-3.4 and gcc-4.0 packages today
[09:38] <siretart> azeem: I think he waits for the buildd masters to update the chroots, same as in debian, I think
[09:38] <siretart> azeem: why do you ask?
[09:42] <azeem> I was going to transition some packages in Debian now, and wondered what Ubuntu does
[09:44] <siretart> azeem: we have been instructed to do the same as in debian, but to wait for the 'go' signal (i.e. post on ubuntu-devel)
[09:44] <azeem> packages only get synced on request right now anyway, right?
[09:45] <siretart> packages get synced automatically
[09:45] <siretart> iff there are no ubuntu specific changes on it (i.e. 'ubuntu' in version string)
[09:45] <slomo_> siretart: i think doko waits only for lsb_release to be installable again... gcc FTBFS because of that
[09:45] <azeem> I see
[09:47] <\sh> azeem: are u coming to the "Linuxtage Essen" on the 3./4. december?
[09:48] <slomo_> \sh: do you know this already? you're famous now =) http://foodfight.org/movies/Ubuntu%20Fanpeople/
[09:48] <\sh> slomo_: yeah
[09:48] <Treenaks> \sh: World-famous :)
[09:48] <\sh> hehe
[09:49] <\sh> it is so lame :)
[09:49] <Treenaks> some german was wgetting my whole site though.. out-of-control wget
[09:49] <azeem> \sh: didn't know about that event until now :)
[09:49] <Treenaks> azeem: UBZ?
[09:49] <\sh> azeem: http://essen.linux-tage.linec.de/
[09:50] <azeem> \sh: incidently, I might be in Cologne that weekend, so Essen wouldn't be so far away
[09:50] <azeem> but I haven't decided yet
[09:50] <sivang> Treenaks: where is mine? :)
[09:51] <\sh> azeem: no...I'm from cologne :)
[09:51] <azeem> well, I am from Munich, so it'd be a longer way otherwise :)
[09:51] <\sh> azeem: actually kerpen which is 20 mins from cologne with the train
[09:52] <Treenaks> sivang: I don't know, I'll search around a bit more.. I might have accidentally deleted you :(
[09:52] <Riddell> \sh: did you upload moodin?
[09:52] <slomo_> \sh: funny... i'm in essen on the 5.12.... one day too late :(
[09:52] <slomo_> ajmitch: works fine here on both machines ;)
[09:53] <sivang> Treenaks: /me cries..
[09:53] <sivang> slomo_: I wonder how it would go for a machine that still has a couple of breezy bugs that went unfixed :) (gdm permisson problem on login, etc)
[09:54] <slomo_> sivang: test it... maybe they're fixed... dapper has a new gdm ;)
[09:56] <sivang> slomo_: well, and how is X working? >:-}
[09:56] <slomo_> sivang: well... it works ;)
[09:56] <sivang> slomo_: ok, let's do it :)
[09:57] <ajmitch> maybe if I actualy update to dapper I can start doing some work on it ;)
[09:59] <sivang> 483 upgraded, 11 newly installed, 2 to remove and 3 not upgraded.
[09:59] <sivang> Need to get 205MB of archives.
[09:59] <sivang> ok, here goes nothing
[10:04] <Kyral> hehe
[10:05] <Kyral> Its stable
[10:05] <Kyral> OO.org2 doesn't work though
[10:05] <crimsun> on what arch?
[10:05] <crimsun> it works fine on i386
[10:05] <Kyral> x86
[10:05] <Kyral> Tell that to my machine
[10:06] <Kyral> it isn't installable
[10:06] <crimsun> err, !installable is different from doesn't work
[10:06] <Kyral> I had to remove it because it would segfault
[10:07] <Kyral> oh well, I prefer Abiword anyway
[10:17] <herve> bye
[10:18] <siretart> gn8 folks!
[10:19] <slomo_> gn8 siretart
[10:19] <Kyral> cya
[10:25] <\sh> Riddell: no...did u advocate the latest package?
[10:26] <\sh> slomo: well..so come on the 3rd :)
[10:27] <Riddell> \sh: nope, just checking, I'll take a look at it now
[10:27] <slomo> \sh: but i have to be the driver for to other people from detmold... would be a waste to drive the same route 2 times in 3 days :/
[10:27] <\sh> slomo: bad timing
[10:28] <\sh> Riddell: take your time...it will fail
[10:28] <slomo> \sh: yes... definitly :( especially after reading your latest blog entry...
[10:30] <\sh> slomo: yeah..that was quite a good idea..good that i'm member of the friends of gentoo :)