[12:40] <norsetto> _16aR_: do you need to copy the same README, AUTHORS and NEWS in all your binary packages?
[12:42] <_16aR_> norsetto: Is it an obligation ? I thought so
[12:42] <pkern> ScottK: aolserver4-nsopenssl is already rebuilt on all arches except amd64, which is why it showed up for me.
[12:43] <norsetto> _16aR_: no, its not an obligations. But, its a bit silly to have them in two packages which are linked dependency-wise
[12:43] <norsetto> _16aR_: like a lib and a lib-dev
[12:43] <_16aR_> norsetto: I've got a question. When multiplebinary packages have been created from one source. How can we say : this libbalbla.so goes there, ths libbloublou.so goes there ?
[12:43] <_16aR_> norsetto: sure
[12:43] <norsetto> _16aR_: if the upstream makefile doesn't do it?
[12:43] <pkern> ScottK: http://launchpadlibrarian.net/8792926/buildlog_ubuntu-gutsy-amd64.aolserver4-nsopenssl_3.0beta22-3build4_FAILEDTOBUILD.txt.gz -- That looks like an aolserver4 bug.
[12:44] <norsetto> _16aR_: use .install or your install target to move them
[12:44] <_16aR_> norsetto: so my .install has a function, no ?
[12:45] <pkern> DktrKranz: Could you look into that please?
[12:45] <pkern> DktrKranz: You fixed aolserver4 some time ago.
[12:45] <_16aR_> debian/tmp/usr/lib/librvrutils.so.0.0.0  usr/lib/ in librvrutils0.install : if i have let it into debian/tmp/usr/lib/, it couldn't have spearated from librcfg, no ?
[12:45] <DktrKranz> pkern, yes...looking
[12:46] <pkern> DktrKranz: Thanks.
[12:46] <DktrKranz> pkern, is a new version? I don't recall any nsopenssl
[12:47] <_16aR_> norsetto:  and I've another question : is it OK to package every .so into 1 .deb ? I've seen some package like OpenSceneGraph which are all .so into 1 package
[12:47] <norsetto> _16aR_: yes, because the second one is in debian/librvrutils/usr/lib
[12:47] <pkern> DktrKranz: No.
[12:47] <pkern> DktrKranz: Seperate source package.
[12:48] <DktrKranz> ok, thanks
[12:48] <pkern> DktrKranz: But build failed in aolserver4 postinst.
[12:48] <pkern> On amd64 only, though.
[12:48] <DktrKranz> anyway...it seems conflicting with an existing app which runs on port 80
[12:48] <DktrKranz> sounds weird only to amd64, though
[12:48] <_16aR_> norsetto: finally I was not too wrong on this then ^^ Phew
[12:49] <norsetto> _16aR_: you have few lintian E/W to work through too
[12:49] <norsetto> _16aR_: no, it was ok (cdbs magic :-))
[12:49] <pkern> DktrKranz: Buildd app probably
[12:50] <pkern> DktrKranz: And the second line looks strange too.
[12:50] <DktrKranz> pkern, no amd64 boxes here...I'll try on PPA
[12:50] <pkern> DktrKranz: The second line is triggered.
[12:50] <pkern> DktrKranz: Address already in use was on i386 too.
[12:51] <DktrKranz> Fatal: nsmain: prctl(PR_SET_DUMPABLE) failed: Invalid argument
[12:51] <DktrKranz> that's the issue...
[12:52] <pkern> Exactly.
[12:53] <pkern> It fails with "/usr/sbin/aolserver4-nsd: error while loading shared libraries: libnsd.so: cannot open shared object file: No such file or directory" here on install (amd64).
[12:53] <pkern> T
[12:53] <pkern> "Trying on recover" succeeds then afterwards.
[12:53] <pkern> s/on/to/
[12:55] <DktrKranz> pkern, could you please try to run it on your amd64 box to see if it fails to configure?
[12:55] <DktrKranz> no problems here...
[12:55] <DktrKranz> on i386
[12:56] <pkern> DktrKranz: As said, it fails in postinst first, in trying to recover it succeeds.
[12:56] <DktrKranz> whoops...didn't noticed...
[01:01] <DktrKranz> pkern, ldd /usr/sbin/aolserver4-nsd | grep nsd.so
[01:01] <DktrKranz> i get libnsd.so => /usr/lib/aolserver4/lib/libnsd.so (0xb7f51000)
[01:02] <pkern> Me too. May this be a confusing ldconfig trigger issue?
[01:03] <DktrKranz> perhaps, not sure...
[01:10] <DktrKranz> pkern, gotta go right now, let's schedule that for tomorrow. I'll have a deeper look
[01:11] <pkern> ScottK: DktrKranz will look at aolserver4.
[01:11] <pkern> DktrKranz: Thanks.
[01:11] <ScottK> pkern: Cool.  Getting nervous about time ...
[01:12] <ScottK> pkern: He's not yet a MOTU, so he'll need a sponsro
[01:12] <DktrKranz> pkern, could I ping you to make some tests?
[01:12] <ScottK> sponsor...
[01:12] <pkern> DktrKranz: Possibly. ;)
[01:12] <DktrKranz> ScottK, np about that...I can ping bluekuja
[01:12] <pkern> ScottK: Where exactly is a problem with that?
[01:12] <ScottK> zul: pkern got the dependency issue sorted on nspluginwrapper.  Howabout an ack now?
[01:12] <ScottK> pkern: With what?
[01:13] <pkern> ScottK: Getting a sponsor. ;)
[01:13] <bluekuja> pkern: yeah, np
[01:13] <ScottK> Ah.  Just mentioning.
[01:13] <pkern> But that makes me curious. apt-get rdepends is not entirely helpful because it's highly arch-dependent.
[01:14] <DktrKranz> gnight all
[01:14] <pkern> Bye DktrKranz
[01:14] <ScottK> gnight
[01:14] <ScottK> pkern: Yes.  I see that now.
[01:15] <norsetto> g'night evrybody
[01:15] <ScottK> g'night norsetto
[01:23] <_16aR_> is it possible to run pbuilder without root privilege ?
[01:24] <pkern> _16aR_: No.
[01:24] <_16aR_> but with a special account
[01:24] <_16aR_> pkern: ok, that's bad
[01:24] <pkern> Well it needs the chroot capability.
[01:43] <_16aR_> How can I modify a .zip to an .orig.tar.gz without ruining the timestamps etc ?
[02:02] <PhreeStyle-home> hello, I'm interested in learning how to be a motu. I send an application in for a mentor a couple weeks ago and have not gotten any kind of response. I'm sure it's due to lack of manpower, so I'm wondering if someone here wouldn't mind being a mentor
[02:06] <RAOF> PhreeStyle-home: Ok.  I'm sure someone here will, but just hanging around here is also good :)
[02:07] <PhreeStyle-home> thanks :) I was begining to wonder if my message was sent
[02:08] <RAOF> PhreeStyle-home: I'm a freshly minted MOTU, and I learnt primarily by hanging around here :)
[02:08] <PhreeStyle-home> well, I'm like a complete noob in all this...I am a windows developer, so coming into linux is a completely different ball game
[02:09] <PhreeStyle-home> I want to learn to eventually write applications for linux, so I figure a good start would be to learn how handle package management
[02:09] <RAOF> PhreeStyle-home: Ooooh, a bona-fide developer.  What language(s)?  What would you like to do? :{
[02:09] <RAOF> :)
[02:10] <PhreeStyle-home> Well, I come from C#, so it's going to be a rough ride.
[02:10] <RAOF> PhreeStyle-home: No, not at all.  See mono :)
[02:11] <PhreeStyle-home> I'm interested in desktop development...I like making front ends for otherwise tedious tasks
[02:11] <RAOF> Many of the windows apps youv'e coded should run without changes in linux anyway :)
[02:11] <RAOF> PhreeStyle-home: Oh, hurray!  We always need more frontends ;)
[02:11] <PhreeStyle-home> Actually, I have not had good luck with mono
[02:11] <RAOF> Ah.
[02:12] <RAOF> Well, your C# knowledge should be largely portable, at least :).
[02:12] <PhreeStyle-home> most of my applications go a little farther than a notepad clone and if I even touch a listview control, you can bet it won't work right in linux
[02:12] <PhreeStyle-home> I sure hope so :)
[02:12] <RAOF> You'll probably want to learn the gtk# libraries, though.
[02:13] <PhreeStyle-home> the one thing that bothers me though is that mono is not highly looked upon
[02:13] <RAOF> I was under the impression that as long as you didn't p/invoke, mono was very nearly a .net dropin.  But I've never needed to test it.
[02:13] <RAOF> PhreeStyle-home: Only by the uninformed.
[02:14] <PhreeStyle-home> possibly true
[02:14] <RAOF> PhreeStyle-home: Mono is an official Gnome dependency.
[02:14] <RAOF> (For tomboy, and f-spot)
[02:14] <PhreeStyle-home> well i figured I would end up writing gnome applications anyways...there's something about KDE that just rubs me the wrong way...not sure why
[02:15] <RAOF> PhreeStyle-home: I find it's the amazing over-abundance of options, at least last time I checked :)
[02:16] <PhreeStyle-home> Well that's true, but I've always had problems with consistency...with theming, menu arrangements and last time I used it, it was very buggy....applications wouldn't start unless started two or three times
[02:16] <PhreeStyle-home> and that was 3 months ago...that's the scary part
[02:16] <RAOF> So, there's actually nothing much that you need to know about packaging in order to do C# development.
[02:17] <PhreeStyle-home> well, even C# programs need to be packaged at some point, right?
[02:17] <slangasek> RAOF: lack of information is not why I don't look highly upon mono. :)
[02:17] <RAOF> slangasek: :P
[02:17] <RAOF> PhreeStyle-home: True.  But C# programs are generally easy, since your tools tend to put stuff in the right place automatically.
[02:18] <RAOF> slangasek: Why *do* you not look highly on mono?
[02:18] <PhreeStyle-home> i'm curious too...most say because of memory footprint and slowness
[02:18] <RAOF> PhreeStyle-home: Basically, as long as you release a tarball that builds your project from source, it's easy enough to package.
[02:18] <RAOF> (The frikkin' Tao project is an example of the contrary :()
[02:19] <imbrandon> PhreeStyle-home: take a look at monodevelop, 99% of my .net apps i write work without modification , normaly even not even recomilation in linux
[02:19] <imbrandon> just copy to the linux box, mono blah.exe and go, and no they arent notepad closes either
[02:20] <imbrandon> clones*
[02:20] <PhreeStyle-home> imbrandon: I tried monodevelop at version 0.14 and it crashed saving a code file only 5 lines long
[02:20] <slangasek> RAOF: PhreeStyle-home seems to have nailed it; that's very nice and all that some folks find C# makes development faster, but I'd like to run my desktop on real-world hardware thanks
[02:20] <slangasek> also, patents
[02:20] <zul> PhreeStyle-home, I would start at reading some documentation and looking at http://wiki.ubuntu.com/MTOU/TODO
[02:20] <zul> er http://wiki.ubuntu.com/MOTU/TODO
[02:21] <imbrandon> slangasek: real world hardware? heh i do most of my development and packing on a p200 including mono
[02:21] <PhreeStyle-home> I looked at all the suggested reading for motu stuff, but I guess it will take a little hand-holding for me to understand it a bit better
[02:21] <imbrandon> PhreeStyle-home: feel free to ask away, we always try to help out when we can
[02:22] <RAOF> PhreeStyle-home: Unless you're uncomfortable asking on a public channel like this, you don't *need* a mentor :)
[02:22] <RAOF> We're all very friendly here.
[02:22] <PhreeStyle-home> that's good to know....alot of times I go into a channel and get ignored...that is obviously not the case here :)
[02:22] <RAOF> (Except for LongPointyStick, she's sharp and dangerous :P)
[02:22] <PhreeStyle-home> :P
[02:22] <imbrandon> lol
[02:23] <RAOF> So, what's the changelog syntax for closing multiple bugs at once again? (LP: #bug1, #bug2, #bug3)?
[02:24] <PhreeStyle-home> well let me ask a question then, if I were to try and learn gtk# programming in c#, what would be a good sample application to try and build?
[02:24] <RAOF> PhreeStyle-home: As in: something we'd like to see, or something that exists that you can learn from?
[02:24] <PhreeStyle-home> I don't know.. either i guess
[02:24] <crimsun> RAOF: LP: #foo, LP: #foo, IME
[02:25] <PhreeStyle-home> something easy :)
[02:25] <PhreeStyle-home> the first app I thought of making was a front end to mount cifs shares that actually works
[02:25] <PhreeStyle-home> but i figured that would be a bad way to start...especially if I were to hose the fstab file
[02:26] <RAOF> That's probably not a great candidate right now, since gvfs is comming really soon now, and should be awesome.
[02:26] <imbrandon> banshie and f-spot are both gtk# iirc, but also not system.windows.forms also works just fine, i use that personaly for portability of pure .net accross windows/linux/osx
[02:26] <RAOF> tomboy notes is probably good, too.  That's fairly simple.
[02:26] <imbrandon> s/not/note
[02:27] <RAOF> crimsun: Thanks.
[02:27] <PhreeStyle-home> so would it be a good idea to make it in system.windows.forms first, then try to port it to gtk#? Is that a good exercise?
[02:28] <imbrandon> PhreeStyle-home: personaly thats what i would do if you are wanting to learn gtk# , that way you see the relationship of them
[02:29] <imbrandon> but thats just how _i_ learn, do whats best for you
[02:29] <PhreeStyle-home> yea that might be the best thing then...if I have any problems running the system.windows.forms version on the linux side would I be able to get a little help in here? The mono channel is usually pretty empty
[02:30] <imbrandon> depends on the time and whats going on, but most likely a bit, but just rember its not a support chan and not all mono ( or even most ) devs
[02:31] <imbrandon> :)
[02:31] <PhreeStyle-home> i figured :)  what is the most common programming language among devs?
[02:31] <imbrandon> in ubuntu ? python has a good following
[02:33] <RAOF> Python *does* rock :)
[02:34] <PhreeStyle-home> it will be a while before I get comfortable with python...I went through a few tutorials and the whole time I was trying to relate the information with what I know about C# and I think that is a bad way to approach Python...at least for me
[02:34] <RAOF> C is a perenial favourite for people who want their code to fail in mysterious ways on x86-64
[02:34] <RAOF> (Libvisual, I'm looking at you!)
[02:35] <RAOF> C++ for those krazy KDE folk.
[02:35] <imbrandon> pykde ( python ) is the kubuntu choice mostly
[02:35] <PhreeStyle-home> yea, I'm not a big C/C++ fan...I know that's what all operating systems are based on, but it's....different
[02:36] <slangasek> RAOF: I like my C code to work on all architectures just fine :)
[02:36] <RAOF> C (the way Gnome uses it)/C++ are OK.  But as long as you've got unittests, python is so much more understandable I find.
[02:37] <RAOF> slangasek: You obviously don't write uint32_t when you mean intptr_t all the time then :(
[02:37] <slangasek> no, indeed I do not
[02:37] <PhreeStyle-home> ok, I know this is really, really bad...and I will get yelled at for this...but I don't really know how to use unit tests
[02:37] <slangasek> because I actually understand C :)
[02:37] <ajmitch> slangasek: sadly, not enough people do
[02:37] <slangasek> RAOF: (have been an alpha porter for Debian for years; amd64 folks have it *easy*)
[02:37] <RAOF> slangasek: You have the added fun of endianness, right?
[02:38] <slangasek> (i.e., try running a 64-bit platform /before/ 64-bit has achieved critical mass)
[02:38] <PhreeStyle-home> i know it's good coding practice and all, but I could never figure out how to use the testing in my code
[02:38] <slangasek> RAOF: nah, Linux/alpha is little-endian
[02:38] <RAOF> PhreeStyle-home: Not a lot of people do use unittests, at least that I find.  Test-driven-development (a quick google should help here) is wonderful though, especially in python.
[02:39] <RAOF> You don't *have* to have unittests in python, but it's so much easier if you do :)
[03:09] <RAOF> Right.  That upload closes all but one of the libvisual-plugins bugs.
[03:14] <RAOF> I've also updated the bug with the minimal autoreconf patch, for the OP's future reference.  He at one point asked how small the changes could be :)
[03:15] <RAOF> Not me that gets congratulating; good ol' darkmagez!
[03:16] <persia> Well, DarkMageZ fixed all the bugs, but the patch has scared off many a revewer these past few months :)
[03:17] <RAOF> This is true :)
[03:19] <PhreeStyle-home> blah...I loaded one button onto the stetic designer and monodevelop crashed :(
[03:22] <blueyed> StevenK: re bug 151379: do you think it's OK to leave out the ABIVER from the module name?
[03:22] <ubotu> Launchpad bug 151379 in virtualbox-ose-modules "Please provide virtualbox modules for 2.6.22-14" [Undecided,New]  https://launchpad.net/bugs/151379
[03:24] <bddebian> Heya gang
[03:24] <RAOF> Heya bddebian
[03:24] <bddebian> Hi RAOF
[03:24] <blueyed> Hi bddebian
[03:25] <bddebian> Hello blueyed
[03:25] <StevenK> blueyed: Maybe, maybe not. The problem with leaving it out is people get confused when it doesn't load due to an ABI bump.
[03:26] <blueyed> StevenK: but it won't load in any case, as long as there's no new version around, correct?
[03:26] <blueyed> Therefor it should be somehow integrated in linux-meta, shouldn't it?
[03:26] <blueyed> (at least in Hardy then)
[03:28] <blueyed> StevenK: can you confirm that my debdiff did not work on any arch?
[03:29] <StevenK> blueyed: With or without, it still won't build - the code is in virtualbox-source, and it doesn't build.
[03:30] <ScottK> StevenK: pkern (when he wakes up I guess) has Bug #151288 sorted.  If I could get another motu-uvf ack it'd be one less reason for Automatix to exist.
[03:30] <ubotu> Launchpad bug 151288 in nspluginwrapper "UVFe: Please merge nspluginwrapper 0.9.91.5 from Debian Unstable (Contrib)" [Undecided,Confirmed]  https://launchpad.net/bugs/151288
[03:31] <ScottK> StevenK: asac ~blessed the upload.
[03:32] <StevenK> ScottK: But zul commented "nack, please fix the dependency issue"
[03:32] <ScottK> StevenK: Yes and pkern has it fixed.
[03:32] <ScottK> He's tested it and everything.
[03:32] <ScottK> Since he's MOTU, he'll just upload once I get an ack.
[03:33] <StevenK> ScottK: Stamped.
[03:33] <ScottK> StevenK: Thanks.
[03:34] <bddebian> Speak of the Devil :-)
[03:34] <pkern> Hah.
[03:34] <pkern> ;)
[03:34] <StevenK> We were talking about him, not too him. :-P
[03:35] <bddebian> heh
[03:35] <ScottK> pkern: All yours then.
[03:36] <ScottK> jtbl: Any luck on the artwork license?
[03:36] <pkern> ScottK: And that means what? :-P
[03:37] <jtbl> i heard the icon comes from some other gmail app package
[03:37] <ScottK> pkern: It means the UVFe for nspluginwrapper has been stamped approved.
[03:37] <ScottK> jtbl: Any hint which one?
[03:37] <jtbl> i didnt find out the exact package
[03:37] <ScottK> Ah.
[03:37] <pkern> ScottK: Aye.
[03:38] <ScottK> persia: ^^^ Is the enough of a hint (I don't know how many gmail packages there are)?
[03:38] <pkern> ScottK: When should one "nominate bugs for release"?
[03:39] <ScottK> pkern: When one feels that the release ought not happen without them being fixed except the day before the RC milestone it better be pretty big (since they've already spun the RC CDs).
[03:40] <pkern> Hm k.
[03:40] <StevenK> Uh, the RC CDs have been spun three times.
[03:40] <ScottK> pkern: Now that you've had ubuntu-dev stamped on your forehead you're expected to have sufficient judgement to sort it out.
[03:40] <pkern> flashplugin-nonfree/nspluginwrapper uploaded.
[03:40] <persia> ScottK: Maybe.  I'll take a look around.  If nothing else, there are other gmail-ish icons about.
[03:40] <bddebian> Just don't tell your Debian brethren ;-P
[03:40] <pkern> ScottK: And not get spoon-feeded? Well, that's LP stuff ya know.
[03:41] <ScottK> pkern: Yeah, well you probably know enough to figure it out at this point.
[03:41] <persia> jtbl: If you happen to get any further information, please let us know.
[03:41] <ScottK> persia: That'd be great.
[03:41] <pkern> asac: So there it is your use-case ;)
[03:42] <pkern> ScottK: Yeah, crawling the wiki like everytime before. :-P
[03:42] <pkern> ScottK: I more of less accidentally nominated the vmware-player stuff for release. Now that may have been wrong.
[03:42] <ScottK> pkern: Don't worry, whatever you find there is probably wrong anyway.
[03:42] <ScottK> pkern: pitti will "tell" you if it is.
[03:43] <pkern> ScottK: Ok.
[03:43] <pkern> ScottK: Yeah, policy is moving. \:
[03:43] <pkern> ScottK: Or LP, whatever. ;)
[03:43] <StevenK> % lintian *_amd64.deb | wc -l
[03:43] <StevenK> 31
[03:43] <StevenK> Ugh...
[03:43] <ScottK> He likes removals so even if it was overkill, he'll have a good sense of humor about it.
[03:44] <ScottK> pkern: And if it's not wrong, it'll have been moved to where I can't find it.
[03:44] <ScottK> jtbl: The nspluginwrapper upload is done, so you can remove that from what you all are planning on providing.
[03:44] <pkern> ScottK: My point why I ask those things is "what's current policy and what has been agreed on".
[03:44] <ScottK> pkern: Well those two things don't always line up.
[03:45] <StevenK> Whoever wrote qmv, I want to bear your children.
[03:45] <ScottK> pkern: I'll warn you that this is yet another Ubuntu related topic I'm a little bitter about.
[03:45] <bddebian> Uh-oh
[03:45] <ScottK> Yeah, thus the warning.
[03:45] <pkern> bddebian: We're not in Teletubby land here.
[03:46] <bddebian> hah
[03:46] <ScottK> It's almost like he thought I had the LongPointyStick.
[03:46] <pkern> https://gallery.debconf.org/main.php?g2_itemId=24445
[03:47] <pkern> And http://mugshot.org/visit?post=ZJWKs0cvTAz1J2
[03:47] <ScottK> StevenK: Any opinion on Bug 151289
[03:47] <ubotu> Launchpad bug 151289 in esvn "Please merge eSVN 0.6.12 from debian lenny/sid to Gutsy - fixes svn incompatibility." [Undecided,New]  https://launchpad.net/bugs/151289
[03:47] <StevenK> Yeah, well, we all know Joss is a bastard
[03:48] <pkern> ScottK: NACK at that.
[03:48] <pkern> ScottK: http://durotan.0x539.de/~pkern/esvn-screenie.png
[03:48] <pkern> ScottK: At least the version in Gutsy works.
[03:48] <pkern> (We had that topic... this morning? yesterday?)
[03:49] <ScottK> pkern: Thanks.
[03:49] <jtbl> i have no clue where that icon came from
[03:49] <jtbl> i have searched everywhere i can think of
[03:50] <jtbl> i still think someone contributed it to us
[03:50] <ScottK> jtbl: Thanks for looking into it.
[03:50] <jtbl> the only other suggestion is to use an icon from kcheckgmail
[03:51] <ScottK> jtbl: At this point if we get a .desktop with artwork of some sort that's related to gmail, I think it'll be good.
[03:51] <pkern> ScottK: I guess we could bigon who prepared the debdiff if it failed for him.  At least somebody (I'd guess the submitter) was here yesterday, I showed him the screenie and he confirmed that would mean that the bug's away.
[03:51] <pkern> OTOH that was filed only 12h ago.
[03:51] <ScottK> pkern: Now I'm confused.  Are you saying we should and should not update the package?
[03:52] <persia> jtbl: If you think the kcheckgmail icon is nice enough, that's an easy patch.
[03:52] <ScottK> It sounds like a good integration thingy to do, but I'm not sure.  That's why I ask around.
[03:52] <jtbl> yeah it should be fine
[03:53] <persia> jtbl: OK.  Thanks.
[03:53] <ScottK> persia: I think that's plenty good.
[03:53] <ScottK> jtbl: Got any other issues we can try to work in?
[03:54] <pkern> ScottK: I only see that it's broken in Feisty.  But I'm doing further checking.
[03:54] <ScottK> pkern: Thanks.
[03:54] <jtbl> nope
[03:54] <jtbl> thats all i can think of
[03:55] <jtbl> it looks like icedtea made it into universe
[03:55] <ScottK> Great.  Let's work on this earlier in the release cycle next time...
[03:55] <persia> pkern: I don't know if it still works, but one used to be able to use dchroot to a pbuilder or lvm chroot to test gui packages against a target distro in local X.  If that still works, it's a handy way to test if you're on a previous release.
[03:55] <jtbl> that will allow amd64 users to have a decent java plugin
[03:56] <ScottK> To the extent that's possible (decent and java going together) sure.
[03:56] <RAOF> jtbl: Really?  Awesome.  That meants I'll get bothered by stupid java applets in my browsing again.  Woooooo!
[03:56] <jtbl> yeah
[03:57] <jtbl> it was just posted today
[03:57] <pkern> esvn (0.6.11+1-4) unstable; urgency=low
[03:57] <pkern>   * Implement parser for .svn/entries with format > 6 (Damien Caliste).
[03:57] <pkern>    (Closes: #387447)
[03:57] <pkern> ScottK: Fix already present in Gutsy.
[03:57] <pkern> persia: I'm on Gutsy.
[03:57] <pkern> persia: Which I regret, but well.
[03:57] <ScottK> Gah.
[03:57] <jtbl> and with the updated nspluginwrapper 64 bit firefox is ready for the new flash plugin which should be out soon
[03:57] <pkern> ScottK: So a clear NACK from me.
[03:58] <ScottK> Sounds reasonable to me.
[03:59] <PhreeStyle-home> does anyone else here use monodevelop to develop gui applications?
[03:59] <pkern> persia: gcc 4.3 fixes, windows titles
[03:59] <pkern> persia: Nothing special or outstanding.
[04:00] <ScottK> pkern: Thanks.  I marked it wontfix
[04:00] <pkern> ScottK: Fine.
[04:00] <persia> pkern: gcc fixes come from Debian.  I don't know about the titles :)
[04:00] <bddebian> You know it seems like it took eons to get from 3.4 to 4.1 now it seems like there a new gcc every freakin' month :)
[04:00] <ScottK> bddebian: Time just seems to move faster as you get older.
[04:01] <persia> bddebian: Watch: there will be a large delay between 4.6 and 5.1 (and 5.0 will be useless, except for a new taiwanese supercomputing architecture)
[04:01] <bddebian> Well that's probably true :-(
[04:01] <bddebian> persia: Heh
[04:11] <ScottK> I guess talking about gcc version numbers was just too exciting for some people.
[04:11] <bddebian> heh
[04:13] <ScottK> I've got my list of "Stuff I was planning on doing before the RC freeze" done, so let me know if anyone has something.
[04:14] <persia> ScottK: I've two things on my list: getting current sbuild and current schroot not to report "Chroot mode deprecated" when mounting LVM snapshots, and adding an icon and .desktop file to checkgmail.  Either of those appeal to you?
[04:14] <ScottK> persia: No.  I don't know enough to deal with either of those.  Sorry.
[04:15] <persia> pkern: The logs are only 80% reliable.  It's be right tomorrow (usually only one day is bad, for each channel, for each three weeks or so)
[04:15] <ScottK> I wasn't dodging the .desktop thing because I was busy.
[04:15] <bddebian> There has to be some new crack crack to upload somewhere ;-P
[04:15] <persia> ScottK: I'd be happy to walk you through the .desktop thing: the only blocker for me right now is that I'm not on an Ubuntu system.
[04:16] <ScottK> Urgh.  I was afraid you'd say something like that.
[04:16] <RAOF> bddebian: There's always Xgl - you don't have to feel I've got an exclusive lock on that crack!
[04:16] <ScottK> OK.
[04:16] <persia> heh
[04:16] <persia> OK.  First, you'll want to grab the package, the target .desktop file, and the target icon.
[04:16] <ScottK> persia: What package am I doing?
[04:16] <persia> ScottK: I think it's checkgmail.  I'll check LP.
[04:17] <persia> ScottK: Yep.  checkgmail 1.12-1
[04:17] <ScottK> Looks right.  We have one of those
[04:17] <ScottK> I got kcheckgmail too so I'll have the icon
[04:18] <persia> ScottK: OK.  First thing is to find the icon in kcheckgmail.  If you're lucky, it's already uuencoded in debian/
[04:18] <ScottK> OK.
[04:19] <ScottK> persia: I'm doing this on a PIII/700 with 256MB RAM, so be patient.
[04:19] <persia> ScottK: No problem.  Most of what's being done isn't processor-intensive.
[04:19] <persia> ScottK: Do you have an text representation of the icon?  (.uu, .xpm, .svg, etc.)
[04:20] <ScottK> I have a .svg I think
[04:20] <persia> SVG is good.  No silly uuencoding rules.
[04:21] <persia> Check license compatibility.  If you can, copy the svg file to the target debian/ directory.
[04:21] <ScottK> Checking
[04:22] <ScottK> Both GPL v2 or later, so that's good
[04:22] <persia> Makes it easy :)  Next, grab the .desktop file from Automatix
[04:23] <ScottK2> Grabbing
[04:23] <persia> Install desktop-file-utils, and run `desktop-file-validate checkgmail.desktop`.  You'll need to edit the file a bit to match the instructions.
[04:24] <ScottK2> OK
[04:26] <ScottK2> checkgmail.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated
[04:26] <bddebian> Yeah, don't need that anymore
[04:26] <ScottK2> checkgmail.desktop: warning: value "Application;Network;" for key "Categories" in group "Desktop Entry" contains a deprecated value "Application"
[04:26] <persia> ScottK: Just delete the "Encoding" line from the file, and make sure it's UTF-8.
[04:26] <bddebian> Remove Applications
[04:26] <ScottK2> So just remove the first one
[04:26] <persia> ScottK: Also, listen to bddebian :)
[04:26] <ScottK2> So remove them both
[04:27] <bddebian> Remove the whole encoding line.  Remove Applications from the categories line
[04:27] <persia> ScottK: Keep "Network", but drop "Application".  Delete the entire line with "Encoding"
[04:28] <ScottK2> Of course the icon name doesn't match my file name.  I should adjust that too I assume.
[04:29] <StevenK> ScottK2: Bug 151289 rubber stamped
[04:29] <ubotu> Launchpad bug 151289 in esvn "Please merge eSVN 0.6.12 from debian lenny/sid to Gutsy - fixes svn incompatibility." [Undecided,Won't fix]  https://launchpad.net/bugs/151289
[04:29] <persia> ScottK: Ideally the you want "Icon=checkgmail", and to have your icon named "checkgmail.svg".  Don't worry about a path.
[04:30] <ScottK> persia: Double stamped confirmed won't fix
[04:30] <persia> heh
[04:30] <ScottK2> persia: http://pastebin.ubuntu-nl.org/40225/
[04:31] <ScottK> StevenK: You might want to refresh and look at my comment before yours unless I'm misreading "do it"
[04:32] <persia> ScottK2: Drop the extension from checkgmail.svg: that way someone can theme it with a .png (or whatever).  It eyeballs fine: does desktop-file-validate produce anything?
[04:32] <ScottK> No result at all.  I'll drop that
[04:33] <persia> ScottK2: Drop the modified .desktop file also in debian/
[04:33] <ScottK2> It's there
[04:33] <persia> Does the package use dh_install or CDBS?
[04:33] <ScottK2> dh_install
[04:34] <persia> Easy then.  Add 'usr/share/pixmaps' and 'usr/share/applications' to either debian/dirs or debian/checkgmail.dirs (as appropriate)
[04:34] <pkern> Hm. /me is not tired.
[04:34] <pkern> But I guess I should sleep anyway. \:
[04:34] <persia> Install the .svg to usr/share/pixmaps and the .desktop to usr/share/applications in the .install file.
[04:35] <persia> (for those just lurking: if neither dh_install nor CDBS is in use, one must edit the rules file to manually install things)
[04:36] <pkern> Yeehaw MOTU school. :D
[04:36] <ScottK2> pkern: I try real hard to avoid this GUI stuff.
[04:37] <ScottK2> persia: Looking again, dh_install is commented out in debian/rules
[04:37] <ScottK2> There is dh_installmenu enabled.
[04:37] <persia> ScottK2: Your call: I usually uncomment, but you can also do the install -m 644 stuff.
[04:38] <ScottK2> Uncomment and add a .install file I guess
[04:38] <RAOF> Also, in future this logic is planned to be moved to dh_icons at some point, irght?
[04:38] <persia> dh_installmenu is for .menu files, rather than for .desktop files.  While the Debian menu can be enabled in Ubuntu, doing so isn't trivial, and not intended by default.  On the other hand, populating menu files is best practice for feeding Debian.
[04:38] <persia> RAOF: No.  It would be part of dh_desktop.
[04:40] <persia> ScottK2: That's it.  Maintainer mangle, Add changelog, Build, install, and there should be an icon in the menu.
[04:40] <ScottK2> persia: Is it gonna work on KDE?
[04:40] <bddebian> Should
[04:40] <ScottK2> OK
[04:40] <persia> ScottK2: It should.  I've closed lots of "Icon doesn't show in the K-Menu" bugs with variations on that procedure.
[04:41] <ScottK2> Let me fiddle with this then and I'll whine if I can't figure it.
[04:42] <pkern> mailman_2.1.5-8sarge5.fsmi8.etch1 -- Now this is a funny version number. 2.1.5-8, sarge revision 5 (security updates), own revision 8 (patches), forward ported to Etch. :D
[04:47] <tonyyarusso> Erm, I can't figure out where I'm supposed to file bugs against Drivel - https://bugs.edge.launchpad.net/ubuntu/+source/drivel, https://bugs.edge.launchpad.net/drivel, http://bugzilla.gnome.org/browse.cgi?product=drivel, or multiple ones of the above?
[04:48] <pkern> Primary point for users would be https://bugs.edge.launchpad.net/ubuntu/+source/drivel
[04:48] <pkern> Or rather s,.edge,, ;)
[04:48] <RAOF> The first is for bugs against the Ubuntu packages, the second is probably just to have the ability to forward LP bugs to the upstream bugtracker, which would be the third one :)
[04:49] <tonyyarusso> oof
[04:49] <tonyyarusso> My bug is a feature request, not Ubuntu specific.
[04:49] <RAOF> Then the 3rd option is probably most appropriate.
[04:49] <RAOF> that's the upstream bugtracker :)
[04:49] <persia> tonyyarusso: LP/ubuntu/ is the catchall, LP/drivel/ seems experimental, and b.g.o : drivel appears to be the active upstream tracker
[04:50] <tonyyarusso> If I filed it upstream, would there be any handy way to keep tabs on it within LP?
[04:50] <tonyyarusso> (Just so I don't have to log in as many places)
[04:50] <persia> tonyyarusso: You might add the feature request to both: new Ubuntu people looking for something to do might try to implement if there's a pointer.
[04:50] <persia> tonyyarusso: Add a new bug at LP/ubuntu/drivel, and link to upstream.
[04:51] <tonyyarusso> persia: good call
[04:52] <ScottK> The "not real" drivel project in LP is what LP want so creat for ALL upstreams of Ubuntu packages so that linking to the upstream bug tracker will work.
[04:52] <ScottK> They swear it's a scalable solution.
[04:52] <tonyyarusso> Oh hey, it looks to already be filed.  http://bugzilla.gnome.org/show_bug.cgi?id=311023
[04:53] <ubotu> Gnome bug 311023 in general "MovableType/WordPress entries can't have multiple entries" [Enhancement,Unconfirmed] 
[04:53] <persia> ScottK2: Are you sure?  I thought they wanted to link to upstream somehow, but not necessarily in LP.
[04:53] <tonyyarusso> not a very well named bug, but oh well
[04:54] <ScottK> persia: Via a project for each upstream.
[04:55] <persia> ScottK: Does it say that somewhere?  How is it imagined that "upstream" bugs in LP will be communicated with developers?  Actually, don't answer that except perhaps with pointers: this isn' t the right forum...
[04:56] <ScottK> persia: It's in the "No, let us LP developers explain how bug status is supposed to be used, you're doing it wrong" thread on devel-discuss
[04:56] <persia> ScottK: I somehow missed that.  I'll review the thread again.  Thanks.
[04:58] <ScottK2> persia: It's possible it was on IRC too, but I recall kiko saying somewhere that it was no big deal to add the projects and he'd be glad to personally add any we wanted.
[04:59] <ScottK2> persia: It's in the menu, but without the icon.
[04:59] <ScottK2> Help
[04:59] <ScottK2> I looked and checkgmail.svg is in the right spot.
[05:00] <persia> ScottK2: Without the icon?  Does KDE handle .svg icons in the icon cache?  Alternately, I'm an idiot, and forgot to tell you to add dh_icons to refresh the icon cache.
[05:00] <ScottK> persia: Where do I add it?
[05:01] <ScottK2> persia: After dh_install in debian/rules?
[05:01] <tonyyarusso> Okay, added in LP as well as Bug #151475
[05:02] <ubotu> Launchpad bug 151475 in drivel "Drivel can not handle multiple categories" [Undecided,New]  https://launchpad.net/bugs/151475
[05:02] <persia> In install:, but looking at http://diablo.ucsc.edu/cgi-bin/man/man2html?dh_icons+1, it only taks about gtk-update-icon-cache.  Doesn't KDE have an icon cache?  I need to look to figure out how to update.
[05:03] <ScottK2> persia: I told you I stay away from this kind of stuff.
[05:03] <persia> ScottK: Are you using KDE3 or KDE4?  Icon cache is supposed to be in KDE4, but not in KDE3.  If there's no cache, I'm not sure why the icon isn't loading, as svg icon support was added to KDE in 2002.
[05:03] <ScottK2> Trying dh_icons
[05:04] <ScottK2> KDE3
[05:04] <ScottK2> It should be there for Gnome anyway, so I'll leave it regardless
[05:05] <ScottK2> Fortunately the package builds pretty quickly.
[05:05] <persia> ScottK2: My apologies.  Usually it just works (at least for me).
[05:05] <persia> bddebian: Any ideas?
[05:05] <ScottK> imbrandon: You around?
[05:06] <bddebian> Sorry, what'd I miss
[05:06] <ScottK> Well, as expected, that didn't help.
[05:07] <persia> bddebian: The .svg is in usr/share/pixmaps, and properly referenced by the .desktop file, but doesn't display in the K-menu.  KDE3 doesn't use the freedesktop icon cache, so dh_icons doesn't matter.
[05:07] <ScottK2> Let me look at what kcheckgmail does a little closer.
[05:07] <bddebian> You can try dh_iconcache but it shouldn't be necessary
[05:08] <bddebian> Ah, see what do I know? :-)
[05:12] <ScottK> I do have working .svg icons in /usr/share/pixmaps.
[05:13] <ScottK> Looking to see where kcheckgmail hides it's icon
[05:13] <bddebian> Does the menu item show at all and not the icon or does the icon just not appear
[05:14] <persia> ScottK: Just to confirm, you have "Icon=checkgmail" and /usr/share/pixmaps/checkgmail.svg, right?
[05:14] <imbrandon> ScottK: yea, now i am
[05:15] <ScottK> imbrandon: I'm trying to add a .desktop with an icon to checkgmail and it doesn't work (no icon) in KDE.  Any hints?  Scrollback for painful amounts of detail.
[05:15] <ScottK> persia: Double checking
[05:15] <imbrandon> ScottK: whats the icon filetype
[05:15] <ScottK2> .svg
[05:15] <imbrandon> kde3 dosent do svg icons
[05:16] <persia> imbrandon: Really?  There are patches out there for svg icons since 2002.
[05:16] <bddebian> I was thinking that but I wasn't sure
[05:16] <ScottK2> Hmmm.
[05:16] <imbrandon> persia: yea i have no idea why no one has added it but thats the case
[05:16] <ScottK2> Well that would explain it.
[05:16] <imbrandon> we've run into it before
[05:17] <persia> ScottK: You said you had working svg icons.  Which?
[05:17] <ScottK> persia: Well wine drops a .svg into usr/share/pixmaps.  I assume that was the icon I was seing, but maybe not.
[05:17] <persia> ScottK: Is there also a wine.ping or wine.xpm?
[05:18] <persia> s/pin/pn/
[05:18] <ScottK2> All the wine stuff in there is .svg
[05:19] <bddebian> What about the hicolor/whatever/whatever/ dirs?
[05:20] <ScottK2> Looks like kchekgmail uses .pngs (from upstream).
[05:20] <cereal_killer> can someone help me with a quick (well not so) .deb packing problem?
[05:20] <ScottK2> If this is a KDE only issue, we needn't worry.
[05:21] <persia> ScottK: So kcheckgmail generates .pngs from the .svg for installation?  That's an excellent example of providing source for binaries :)
[05:21] <cereal_killer> when i pack build my deb everything goes fine but there should be files under DEBIAN/usr and others so the file heirachy is not being created and therefore i'm basically creating an empty .deb
[05:21] <ScottK2> If I upload this package to REVU, will someone on Gnome pull it down and build/test it?
[05:21] <ScottK2> persia: Upstream tarball has .png too.
[05:21] <cereal_killer> well, DEBIAN/package/usr etc
[05:21] <bddebian> ScottK2: I can
[05:21] <ScottK2> bddebian: Thanks.
[05:22] <persia> ScottK2: That's fine.  I don't mind included PDF files with docbook source.
[05:22] <bddebian> cereal_killer: If you build locally nothing ends up in debian/... ?
[05:23] <bddebian> cereal_killer: It should either be in debian/tmp/... or debian/<package-name>/...
[05:23] <cereal_killer> bddebian: i created in my ~ dir /packages/package/package-number
[05:24] <ScottK2> bddebian: Uploaded.  Waiting for it to appear on REVU.  I'll give you a link when it's there
[05:25] <cereal_killer> bddebian: i'm just creating the deb in my home dir, not installing it
[05:25] <bddebian> cereal_killer: Right.  I'm saying if you are in the package-version dir and run dpkg-buildpackage or debuild use -us -nc and see where the files go under package-version/debian/
[05:28] <cereal_killer> bddebian: so after dh_make, dpkg-buildpackage is built in the /debian dir?
[05:29] <cereal_killer> i'm not quite understanding, sorry
[05:30] <cereal_killer> it's telling me it's making the files in the directories though lol
[05:30] <cereal_killer> well, creating them in the debian dir
[05:30] <bddebian> cereal_killer: Yes, once you have the debian/ dir created from dh_make and make any appropriate changes.  You would typically run dpkg-buildpackage or debuild to build your source and/or binary packages.  If you pass -us (unsigned source) and -uc (don't clean the tree) it will leave whatever files it creates under debian/
[05:31] <cereal_killer> what is debuild? I've never heard of that
[05:32] <bddebian> It's just like dpkg-buildpackage.  I don't personally use it but many do
[05:32] <cereal_killer> discard that question
[05:32] <cereal_killer> man has the answer :)
[05:32] <bddebian> ScottK2: What's the name of the package?
[05:32] <ScottK> bdq
[05:32] <ScottK> Urgh
[05:32] <ScottK> bddebian: checkgmail
[05:33] <bddebian> Well where the hell is it? :-)
[05:33] <ScottK> I don't see it there (I double checked I didn't upload it to the archive by mistake).
[05:33] <ScottK> Any REVU admin around?
[05:33] <bddebian> Ah, there it is
[05:33] <ScottK2> Cool
[05:34] <ScottK2> Yeah.  That one.
[05:34] <ScottK2> I'm going to go clean the oven.  Let me know how it works out....
[05:34] <ScottK2> bddebian: Thanks for testing.
[05:35] <bddebian> Heh, np
[05:36] <StevenK> Ugh.
[05:36] <StevenK> I *hate* the local shopping centre during school holidays
[05:41] <bddebian> Man I've installed soo much BS on this poor laptop
[05:42] <bddebian> ScottK2: Just looks like a big Google G ?
[05:44] <ScottK> bddebian: Yeah.  That's it.
[05:45] <bddebian> Works like a charm :-
[05:45] <bddebian> )
[05:45] <ScottK2> bddebian: Thanks.
[05:45] <bddebian> No, THANK YOu :-)
[05:45] <bddebian> hah
[05:46] <ScottK2> Your taking that back now, aren't you.
[05:47] <bddebian> Nope, you rock d00d
[05:56] <bddebian> Heh
[05:56] <bddebian> Obviously you haven't seen some of mine ;-)
[05:56] <imbrandon> lol
[05:57] <ScottK> To late to worry about it now.
[05:57] <joejaxx> imbrandon: do you have time for a quick pm?
[05:57] <joejaxx> :)
[05:57] <ScottK> Thanks again persia and bddebian.
[05:57] <joejaxx> Hello everyone
[05:57] <joejaxx> hello gnomefreak :D
[05:57] <bddebian> ScottK: NP
[05:57] <gnomefreak> hello joejaxx
[05:57] <joejaxx> :)
[05:57] <ScottK> jtbl: checkgmail with ,desktop is uploaded.  You can get rid of that one too.
[05:57] <bddebian> Heya joejaxx
[05:59] <joejaxx> bddebian: do you know where the autorun directive for the menu package is?
[05:59] <ScottK> StevenK: Any interest in looking at the Automatix source for Gutsy to see if they've met their claim of fixing all the stuf mjg59 complained about?
[05:59] <joejaxx> as it seems it is disabled on ubuntu
[06:00] <joejaxx> either that or we went through and removed a whole bunch of postinst hooks which i do not think happened
[06:00] <bddebian> joejaxx: I don't, sorry
[06:00] <joejaxx> :P
[06:00] <joejaxx> oh ok
[06:00] <StevenK> ScottK: None.
[06:01] <ScottK> StevenK: OK.
[06:01] <ScottK> jtbl: libsigc++-2.0-0c2a is in ia32-libs too.
[06:01] <joejaxx> because menus are not being generated on ubuntu automatically
[06:02] <joejaxx> well when packages are installed
[06:05] <joejaxx> so i am guessing something to do with install-menu?
[06:08] <bddebian> Gnight folks
[06:08] <joejaxx> Goodnight bddebian :D
[06:09] <joejaxx> persia: would you happen to know ? :)
[06:09] <ScottK> That's who I was going to suggest.
[06:11] <joejaxx> ScottK: :)
[06:13] <persia> joejaxx: Debian menu, GNOME menu, K menu?
[06:14] <joejaxx> debian menu
[06:14] <persia> joejaxx: I'm not on a Ubuntu system to check, but I think you want dh_installmenu, which should put a call to update-menu-<something> in the postinst.
[06:15] <joejaxx> yes
[06:15] <_nand_> hi!
[06:15] <_nand_> I'm looking for some pointers on menu items installation on debian file...
[06:15] <joejaxx> but i think there is a systemwide setting for it as i do not think we went through and removed the install hooks in the postinst for packages
[06:16] <_nand_> lol it seems we are in the subject already :)
[06:16] <joejaxx> lol :)
[06:16] <persia> _nand_: man dh_installmenu and the menu package documentation
[06:17] <_nand_> persia: i have read about the file menu e.g. ?package(ike): ....
[06:17] <_nand_> persia: but what if i want to install a .desktop file?
[06:18] <_nand_> it don't have enough information to generate it from the menu file...
[06:18] <persia> _nand_: Ah.  That's not the debian menu at all :).
[06:19] <_nand_> persia: hmm... do i have to make a menu entry for both debian and kde/gnome?
[06:19] <persia> There's a (bad) script to leverage the menu-xdg package to autogenerate the .desktop files available from https://wiki.ubuntu.com/MOTU/Packages/DesktopFiles
[06:19] <persia> _nand_: You'll want two entries: a menu file and a .desktop file.  They are separate, but both usful.
[06:20] <_nand_> ok i have them :) Any pointer on an automatic way to install the .desktop file, or do i just add a line in the rule file?
[06:21] <_nand_> (to do it "properly" )
[06:22] <persia> _nand_: You'll need to install manually.  If the package uses dh_install or CDBS, putting it in the debian/package.install file is preferable to adding a line to debian/rules.  If the package uses debhelper, but not dh_install (and is obviously not a dh_make template), use dh_install lines in debian rules.  Otherwise, use install -m 644
[06:22] <joejaxx> persia: for example for the installation of non-modified debian packages on ubuntu the menu does not generate which is why i am looking for the systemwide change :)
[06:23] <persia> _nand_: Icons go in /usr/share/pixmaps, .desktop files go in /usr/share/applications, and .desktop files should neither specify a path nor an extension for the icon.
[06:23] <_nand_> persia: ok thanks for the info!
[06:23] <persia> joejaxx: Ah.  Do you mean the magic that auto-generates .desktop files from the Debian menu, and inserts the results into the regular system menu?  That's in the menu-xdg package.
[06:25] <joejaxx> persia: no :P i mean whatever hook that was disabled in ubuntu stopping update-menus from running everytime a package was installed
[06:28] <persia> joejaxx: I didn't know such a thing was in place.  I don't see it in the pseudochangelog shown from https://launchpad.net/ubuntu/+source/debhelper, nor do there appear to be any Ubuntu patch to the menu or menu-xdg packages.
[06:28] <joejaxx> persia: yes that is why i am confused to why this is happening
[06:28] <joejaxx> since none of those packages are changed
[06:29] <joejaxx> and we definitely did not go through all the debian packages and rip out any update-menu postinst hooks
[06:29] <persia> joejaxx: The especially odd bit is that I've seen changes to my Debian menu when installing packages on my workstation recently, for which I expect update-menus would need to run, and previous in-channel discussion on .desktop files has shown that the standard menus are updating on instalation.
[06:31] <joejaxx> persia: interesting
[06:31] <persia> Curiouser & Curiouser: usr/bin/update-menus comes to us from Debian directly.  Is the menu package perhaps not installed?
[06:32] <joejaxx> oh no it is definitely installed :)
[06:34] <ScottK> Well it looks like the RC images are done as Universe uploads are being accepted again.
[06:34] <ScottK> Latest WINE crack is in the repos.
[06:34] <StevenK> What version?
[06:34] <ScottK> 0.9.46
[06:34] <persia> OK.  dh_installmenu from debhelper-5.0.51ubuntu3 inserts postinst and postrm hooks to call update-menus, if `which update-menus` succeeds.
[06:35] <joejaxx> persia: yeah
[06:35] <joejaxx> hmm
[06:36] <joejaxx> brb testing a theory
[06:36] <persia> And update-menus is installed (without alternatives) by menu 2.1.34, and does the necessary to call registered menu-methods backends.
[06:39] <jtbl> i have a question about the wine package
[06:39] <jtbl> are there any plans to backport future versions into gutsy
[06:40] <ScottK> jtbl: It can be done into gutsy-backports.
[06:40] <jtbl> ok
[06:40] <ScottK> After the Hardy repos open
[06:40] <ScottK> !backports | jtbl
[06:40] <ubotu> jtbl: If new updated Ubuntu packages are built for an application, then they go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[06:40] <jtbl> i was thinking about using the wine package in the ubuntu repos for automatix instead of the one in the winehq repos
[06:41] <ScottK> jtbl: Why do you need one in the automatix repos?
[06:41] <ajmitch> I think it's mainly using automatix as a package installer, right?
[06:41] <persia> jtbl: That's certinaly easier for use to support.
[06:41] <jtbl> right now we have wine as an installation option but we use the package from the winehq repos not ubuntus
[06:41] <ScottK> I see.
[06:42] <persia> umm.. s/tina/tain/ ; s/use/us/
[06:42] <ScottK> So you'd use gutsy-backports?
[06:42] <ScottK> jtbl: If Scott Ritchie will continue to provide us packages and they test out on Gutsy, backporting is no problem.
[06:42] <jtbl> the only reason we used their packages is that they were updated faster
[06:42] <jtbl> ok
[06:43] <jtbl> i would prefer to use the ubuntu package over the winehq package
[06:43] <jtbl> right
[06:43] <ScottK> jtbl: We'll probabaly lag them ~ 1 week for our processes as long as people are willing to help.
[06:43] <ScottK> persia: sounds like a good Hady feature ...
[06:43] <jtbl> automatix does check and see if backports is enabled
[06:43] <ScottK> Does it enable it if it isn't?
[06:43] <persia> ScottK: It was a warty feature :)
[06:43] <Hobbsee> O.O
[06:43] <ScottK> Ah.
[06:44] <jtbl> yes
[06:44] <ScottK> jtbl: Are you still doing anything with clamav?
[06:44] <jtbl> if backports is disabled automatix will enable it
[06:44] <jtbl> no
[06:44] <jtbl> we removed clamav
[06:44] <ScottK> OK.
[06:44] <jtbl> and firestarter
[06:45] <ScottK> persia: I did not know that.
[06:45] <jtbl> well we were installing the clamtk frontend
[06:45] <ScottK> Well the clamtk in feisty-backports works about as well as clamtk ever does.
[06:45] <jtbl> we didnt see a purpose in having it
[06:45] <ScottK> The released version for Feisty was hopeless.
[06:46] <ScottK> OK.
[06:46] <persia> ScottK: Well, it assumes the relevant repositories are enabled.  aptitude just selects the newest package by default.
[06:46] <ajmitch> Hobbsee!
[06:46] <jtbl> i did remove a lot of options in the gutsy version of automatix
[06:46] <ScottK> persia: Ah.
[06:46] <Hobbsee> ajmitch!
[06:46] <superm1> jtbl, am i to understand that you've addressed a lot of the items that were listed in !automatix then?
[06:46] <ScottK> persia: I was thinking some special grab wine from backports because we are SURE you want the latest crack for that package magic.
[06:47] <jtbl> whats remaining is stuff you cant go into gnome-app-install and check one box and have it get installed
[06:47] <jtbl> yes
[06:47] <ScottK> superm1: That's what he's said.  I haven't had a chance to do a code review.
[06:47] <superm1> jtbl, that's very good to hear.
[06:47] <persia> ScottK: Yep.  That's called enabling the backports repository.
[06:47] <jtbl> i addressed even more than that
[06:47] <jtbl> i figured out a way to stay safe with upgrades
[06:48] <jtbl> stick with ubuntu repo packages, and limit the use of third party repos
[06:49] <jtbl> another is sources.list editing
[06:49] <jtbl> the only repos automatix uses in gutsy are the ubuntu repos and automatix's
[06:50] <persia> jtbl: Is there much coordination between the medibuntu and automatix repositories, or do they meet different needs?
[06:51] <jtbl> well we do use medibuntu's libdvdcss and w32/w64codecs packages
[06:51] <jtbl> but we dont use their repos
[06:51] <ScottK> A quick grep shows that 'killall -9 dpkg' is now commented out (but oddly still present).  So that's progress.
[06:51] <jtbl> i just left that for testing purposes
[06:51] <jtbl> if no one is having trouble it goes
[06:51] <StevenK> And how does killing dpkg help testing?
[06:52] <Hobbsee> ScottK: haha
[06:52] <Hobbsee> persia: i think that's medibuntu
[06:52] <jtbl> alot of the stuff that was mentioned was no longer needed
[06:52] <ScottK> jtbl: If it's still present, Automatix will be viewed as unreasonably dangerous.  Whatever trouble it's absence causes, you need to find another way.
[06:52] <Hobbsee> although, we can do installer scripts and whatnot for the nasty stuff
[06:53] <jtbl> i do think that medibuntu should be the de facto ubuntu repo for illicit packages
[06:53] <ScottK> Hobbsee: The good news is that all the stuff we can legally ship that they were going to ship is now sitting waiting for RM approval.
[06:53] <jtbl> there is one problem with medibuntu
[06:53] <StevenK> "illicit packages" -- makes it sounds like the packages are full of drugs and kiddie porn.
[06:53] <RAOF> They aren't?
[06:53] <persia> Hobbsee: That's what I thought, but I don't know if it's specifically unofficially true, so I don't know if it's bad to copy a subset to the automatix repository, which may have other things not in medibuntu.
[06:53] <Hobbsee> ScottK: in universe, i take it?  it'll get it
[06:53] <StevenK> RAOF: :-)
[06:53] <ScottK> Hobbsee: Yes.
[06:54] <persia> StevenK: hotbabe?
[06:54] <Hobbsee> StevenK: well, hotbabe. does automatix distribute hotbabe yet?
[06:54] <persia> medibuntu does
[06:54] <StevenK> Meh, hotbabe isn't
[06:54] <ScottK> Hobbsee: checkgmail, nspluginwrapper, flash-nonfree, and the ia32-libs one was already released.
[06:54] <jtbl> here is the automatix teams stance on medibuntu
[06:54] <persia> StevenK: If hotbabe isn't kiddie porn for you, you don't have the right skin installed :)
[06:54] <Hobbsee> ScottK: they should get shoved thru, then.
[06:55] <ScottK> Hobbsee: Can you shove?
[06:55] <jtbl> we do test for compatibility with the free component and if users decide to use those packages they wont have any issues
[06:55] <Hobbsee> ScottK: ENOARCHIVEACCESS
[06:55] <ScottK> Hobbsee: OK.
[06:55] <jtbl> however the non-free section is different
[06:56] <persia> jtbl: When you say non-free, do you mean restricted/multiverse, commercial, medibuntu, or all of the above?
[06:56] <jtbl> i have check the amd64 packages in non-free and they install 32bit components into 64 bit directories
[06:56] <jtbl> like placing stuff in /usr/lib instead of /usr/lib32
[06:57] <jtbl> the non-free section in medibuntu
[06:57] <jtbl> medibuntu has two sections free and non free
[06:57] <jtbl> non free contains closed source software like skype, acrobat reader, and google earth
[06:57] <persia> jtbl: Ah.  That's clearly wrong.
[06:58] <Hobbsee> how are tehy managing acrobat reader?
[06:58] <persia> ScottK: When you next feel like chasing really-undistributable, perhaps you'll chase the medibuntu packages?
[06:58] <jtbl> however their packages for amd64 install 32 bit binaries and libraries where only 64 bit versions should be
[06:58] <ScottK> persia: No.
[06:59] <jtbl> the cool thing is that adobe now has a deb of acrobat reader on their site
[06:59] <jtbl> but only for i386
[06:59] <jtbl> however they install acrobat  reader into /opt
[06:59] <StevenK> Ew
[06:59] <jtbl> so it would make building an amd64 package easy
[07:00] <jtbl> as far as google earth automatix just pulls it directly from google
[07:00] <jtbl> and installs it using google's installer
[07:00] <ScottK> May main beef with Automatix was installing stuff from Ubuntu repos that didn't need any extra help, moving files to non-standard locations, various dangerous stuff like sigkilling dpkg, and having the nerve to blame unfixed Ubuntu bugs as why there stuff didn't work when they hadn't tried to help fix the bugs.
[07:00] <ScottK> May/My
[07:00] <ScottK> None of that applies to medibuntu.
[07:01] <ScottK> That's a change.  At least if you're on 64bit.
[07:01] <jtbl> here is what we do on amd64
[07:01] <ScottK> But since I live in the US, I'd never install that stuff anyway.
[07:01] <jtbl> for acrobat reader we take the tar.gz directly from adobe and place it in /opt/automatix/acrobatreader
[07:01] <jtbl> same goes for skype
[07:02] <jtbl> and for google earth we use the official google method of installation
[07:02] <jtbl> now their packages are just fine on 32 bit
[07:03] <jtbl> and the free packages are ok on both platforms
[07:03] <jtbl> its the nonfree packages on 64 bit i would avoid
[07:05] <jtbl> also some people install 32 bit software on amd64 by taking an i386 deb and using --force-architecture
[07:05] <jtbl> automatix doesnt do that
[07:05] <ScottK> It's time for me to get some sleep.  Hobbsee if you see an actual RM around later, I'd appreciate it if you'd ask them to accept checkgmail, nspluginwrapper, and flash-nonfree
[07:05] <ScottK> Good night all.
[07:09] <Hobbsee> ScottK: they should be shunting all universe stuff thru.  and thanks for the inference about me not being a real RM.
[07:09] <ScottK> Hobbsee: Sorry.  SHould have said someone with ARCHIVEACCESS.
[07:12] <ScottK> Hobbsee: I can't even keep all the job titles straight in my house.  Ubuntu is beyond me by a fair margin.
[07:17] <ScottK> ajmitch: Not yet.  There are bugs left.
[07:17] <ajmitch> bah
[07:17] <ajmitch> there'll always be bugs
[07:17] <ajmitch> you seen how many are left on the rcbugs page?
[07:17] <Hobbsee> until you fix them all
[07:17] <ScottK> ajmitch: Not so many as there once were.
[07:18] <ajmitch> still far too many, and I've barely touched any
[07:19] <ajmitch> if we're still allowed to fix anything
[07:19] <persia> ajmitch: Why wouldn't we be?
[07:20] <ajmitch> archive freeze, keeping buildds clear at some point
[07:20] <ScottK> persia: linux-image-2.6.22-14-server
[07:20] <ScottK> ajmitch: The keeping the buildd's open phase appears to be over.
[07:20] <ajmitch> ScottK: it'll come back soon enough
[07:20] <persia> ScottK: What about the server kernel?
[07:20] <ScottK> ia32-libs and WINE got through.
[07:21] <ScottK> persia: Still waiting for the reboot.
[07:23] <ScottK> persia: Came up just fine and appears to be working.
[07:24] <Hobbsee> actually, i wonder why the archive stuff doesnt build thru the EU night
[07:24] <Hobbsee> the universe stuff
[07:24] <ajmitch> the servers are tired?
[07:25] <persia> ScottK: While I appreciate the updates I can't help wondering if you didn't mean to tell someone else about it (although my memory for context is particularly poor today)
[07:25] <Hobbsee> ScottK: there might be.  asking.
[07:25] <ScottK> persia: [01:20]  <persia> ScottK: What about the server kernel?
[07:25] <gnomefreak> what file controls the log in options (gnome, kde, enlightenment)
[07:25] <ScottK> persia: You ask, I answer.  Not sure why you ask.
[07:26] <ScottK> Hobbsee: Cool.  Thanks.
[07:26] <persia> ScottK: That was response to "ScottK: persia: linux-image-2.6.22-14-server"
[07:26] <ScottK> Oh.
[07:26] <ScottK> persia: Ah.
[07:27] <persia> gnomefreak: Do you mean the selection of environments available in foo-dm?
[07:27] <ScottK> persia: Sorry.  That was meant to be persia: http://django.ajmitch.net.nz/rcbugs/
[07:27] <gnomefreak> persia: yeah
[07:27] <persia> ScottK: That makes more sense.  Thanks :)
[07:27] <ScottK> Good night all.
[07:28] <persia> gnomefreak: I believe that each x-session-manager registers itself somewhere in /etc, but that's about the limit of my knowledge.  I do know that you'll want to hunt "session managers" instead of "window-managers".
[07:29] <persia> gnomefreak: For testing: try a xwm session, kill xwm from an open terminal, and launch your preferred wm from within that terminal.
[07:29] <StevenK> Using alternatives
[07:29] <StevenK> sudo update-alternatives --display x-session-manager
[07:29] <gnomefreak> persia: was hoping to not have to do that each time
[07:29] <nixternal> I just did an interview for O'Reilly on "the day in the life of a MOTU", so hopefully my pimpage will draw in some fresh blood for hardy
[07:30] <gnomefreak> StevenK: that wont add it to gdm/kdm
[07:30] <gnomefreak> brb lets try this
[07:30] <persia> gnomefreak: Alternately, hijack one of the existing session options to launch your alternate WM.
[08:01] <_nand_> hey, i have another packaging question :)
[08:01] <Hobbsee> shoot
[08:02] <_nand_> the app i package is providing .so libs that he only will use
[08:02] <_nand_> so it is necessary to provides shlibs files?
[08:02] <Hobbsee> checked what the debian library packaging guide says?
[08:03] <persia> http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
[08:04] <persia> _nand_: The official guide is the URL above, but you will need a shlibs file if you expect any clients to depend on the library, otherwise they won't get automated dependency management.
[08:04] <_nand_> yes they say i should... but in my case no one will ever depend of these libs
[08:04] <_nand_> so ok let's say i will put shlibs file
[08:04] <persia> _nand_: If you have internal libraries (as I think you may), you can omit this file.  In general, best practice is to split the package into separate binaries, and provide shlibs, just in case.
[08:05] <_nand_> persia: ok that was what i was looking for
[08:05] <_nand_> thx
[08:05] <persia> _nand_: There will never be any clients?  In that case, why a shared library?
[08:05] <_nand_> persia: i was meaning they won't be a separate package using these shared libs
[08:05] <_nand_> maybe later, but right now no
[08:06] <persia> _nand_: If "maybe later", better to have multiple binary packages (foo, libfoo, and libfoo-dev), and ship a shlibs file.  If "never", better to link statically.
[08:07] <_nand_> persia: you're right
[08:08] <persia> In the rare case where it's "never", and the upstream build system doesn't support static linking against the private library, you can skip the package split and shlibs file.
[08:09] <_nand_> persia: i should check with upstream :)
[08:09] <_nand_> thx for the info!
[08:10] <LaserJock_> goodness, gutsy's got some issues :/
[08:10] <persia> LaserJock_: Which ones now?
[08:13] <dholbach> good morning
[08:21] <jussi|no2> morning Daniel
[08:22] <pwnguin> arrg
[08:22] <pwnguin> short of ssh, any ideas for figuring out what permissions gnome-screensaver-dialog runs under?
[08:22] <Flannel> pwnguin: cron?
[08:23] <pwnguin> well, i was looking for something less painful than ssh
[08:23] <pwnguin> not more painful
[08:28] <persia> pwnguin: `while true; do ps augx | grep gnome-screensaver-dialog; sleep 5; done > logfile` ?
[08:29] <persia> pwnguin: Alternately: trace the codepath back from the dialog, and see from where the permission is inherited.
[08:37] <LaserJock_> persia: I did a fresh install of the latest RC candidate
[08:38] <LaserJock_> scrollkeeper is messing up most package installations
[08:38] <LaserJock_> compiz is nasty
[08:38] <LaserJock_> my computer is trying to overheat
[08:38] <LaserJock_> firefox is taking *forever* to do anything
[08:40] <persia> LaserJock_: Ah.  I thought there were dpkg-hooks for scrollkeeper and compiz is compiz (and certainly generates more heat).  I don't have a handy excuse for firefox.
[08:40] <LaserJock_> I keep having to killall scrollkeeper-update to install anything
[08:41] <LaserJock_> compiz was just acting weird, I don't know if it was slowing down anything necessarily
[08:41] <persia> Did scrollkeeper not get the postinstall magic (implemented, say, for ldconfig)?
[08:41] <LaserJock_> persia: I don't know
[08:44] <LaserJock_> it just pegs my cpu doing scrollkeeper-update
[08:44] <LaserJock_> so I kill it
[08:44] <LaserJock_> then it finishes installing the package
[08:44] <LaserJock_> then the next one that calls scrollkeeper-update does the same thing
[08:44] <LaserJock_> I had to kill it like 20 times
[08:46] <persia> Makes sense.  Looking at the logs, there's not been much work on scrollkeeper in the past 4 months.  I suspect it needs a poke, as scrollkeeper-update seems like a major target for the postinstall-hooks (e.g. Bug #44535)
[08:46] <ubotu> Launchpad bug 44535 in scrollkeeper "multiple scrollkeeper-update makes apt upgrade very slow" [Medium,Confirmed]  https://launchpad.net/bugs/44535
[08:48] <persia> Ooh!  Bug# 119614 even makes it more exciting :)
[08:49] <LaserJock_> bug #119614
[08:49] <ubotu> Launchpad bug 119614 in scrollkeeper "avoid several instances running simultaneously" [Undecided,New]  https://launchpad.net/bugs/119614
[08:50] <LaserJock_> yeah, I was seeing basically that
[08:51] <dholbach> hey LaserJock_, hey persia
[08:51] <LaserJock_> it was pretty much a showstopper here
[08:51] <persia> I'm guessing there's a good chance of corrupting the scrollkeeper-db by the combination of the two, but I don't really know much about scrollkeeper internals.
[08:54] <persia> Hi dholbach.  Do you know of curret scrollkeeper efforts?  The install experience is sounding suboptimal.
[08:54] <dholbach> it's going to get replaced with rarian next cycle
[08:55] <dholbach> scrollkeeper ist dead for 3-4 years already
[08:55] <persia> dholbach: Do you mean "Hardy" by "next cycle".
[08:55] <dholbach> yes
[08:56] <persia> I was only thinking about a single scrollkeeper-update run at the end of all the application installations.  From what Laserjock said, installation can be painful.
[08:57] <dholbach> that could be done with dpkg triggers
[08:57] <dholbach> if somebody sat down and did it
[08:57] <dholbach> it's not going to happen for gutsy
[08:58] <persia> dholbach: Ah.  I didn't think the trigger would be that hard.  I won't bother with it if it's that definite that it can't happen for gutsy.
[08:59] <dholbach> you can try to talk to the release team, but I guess there's going to be a certain reluctance 7 days away from release
[08:59] <dholbach> there's a lot that can go wrong: fucked up postinst, non-installable packages, etc etc
[09:00] <persia> dholbach: I guess it depends on whether other testers have similar experiences.  Based on Ian's statement, I get the impression that triggers work, but need some real testing, and aren't suitable for gutsy.
[09:01] <dholbach> we use it for some things already
[09:02] <superm1> i've seen triggers work for delaying update-initramfs, and that works out well
[09:02] <persia> Should only be ldconfig and initramfs (unless the decision is out of date)
[09:03] <dholbach> I think it'd have been fine 4 weeks ago, but I'd be surprised if the release managers allow it now
[09:03] <persia> Ah.  Looking at the spec, it appears all the clients need to be rebuilt: it's not something that can be implemented for the annoyingly slow package.  Never mind: that's too hard to get done in time.
[09:28] <huats> morning all
[09:28] <dholbach> hey huats
[09:28] <huats> hello dholbach
[09:28] <huats> how are you ?
[09:28] <dholbach> good good - how are you?
[09:33] <huats> good, good... A bit overwhlemed at work... but it is ok
[10:19] <\sh> hmmm...
[10:19] <\sh> does anyone know a fast solution to wipe a server with a 3pass method (like dban dod)?
[10:19] <\sh> right now I need with dban dod method 110 hours for 7TB
[10:20] <\sh> moins jono
[10:20] <pwnguin> on a scale from 1 to ten, how bad is adding a user to the root group?
[10:22] <pwnguin> slangasek: if you remember our conversation about fingerprinting and pam, it turns out that the uinput module is simply used to feed sudo and friends a <cr>
[10:22] <persia> pwnguin: If 1 is sunrise, and 10 to total protonic reversal, about a 3
[10:23] <pwnguin> hmm
[10:23] <pwnguin> i think your scale lacks granularity
[10:23] <pwnguin> i challenge you to come  up with a patch that ranks a 6 on such a scale
[10:24] <persia> pwnguin: I'm not sure that can be done without specialised peripherals.
[10:24] <pwnguin> well, uinput seems to default to root perms only
[10:24] <pwnguin> this is quasireasonable
[10:25] <persia> pwnguin: Right.  uinput allows the injection of anything to the kernel, so can simulate devices to which the user would not otherwise have access.
[10:25] <persia> If you just want to feed a <cr>, it's easier to use the user's current input device, to which the user can typically write, and inject it into the stream there.
[10:26] <BugMaN> good morning :)
[10:26] <pwnguin> this sounds like it assumes x
[10:28] <persia> pwnguin: Nope.  /dev/input/foo is one injection point.  /dev/ttybar is another.  Determining the user's environment sufficiently to inject the input is a separate issue.
[10:28] <pwnguin> persia: i meant the fix
[10:28] <pwnguin> so removing uinput is possible
[10:29] <pwnguin> and doesnt assume x. this sounds better then
[10:32] <pwnguin> persia: currently, the uinput stuff mostly works. sudo is fine, and so is gdm. gnome-screensaver-dialog, however, runs as a user, not suid
[10:33] <persia> pwnguin: So the remaining issue is to trap & catch the "lock screen" prompt from the screensaver?
[10:33] <pwnguin> persia: this means a) it cannot access the authentication data, and b) it can't grab uinput to write that <CR>
[10:34] <persia> pwnguin: How does gnome-screensaver-dialog currently pass credentials to pam?
[10:34] <pwnguin> persia: well, remaining issue i care about. it doesn't have localization support, and im sure it needs more thought
[10:35] <pwnguin> i dont think g-s-d passes credentials...
[10:35] <pwnguin> g-s-d loads various pam modules
[10:35] <pwnguin> as per pam standards, and they do their business
[10:37] <pwnguin> persia: at the moment, i patched in some ACL support, and people say it works as long as they add themselves to root for uinput support
[10:37] <pwnguin> this sounds bad to me
[10:38] <persia> pwnguin: It's roughly as bad as the user being able to sudo without a password.
[10:39] <pwnguin> so it defeats the purpose of the entire package
[10:39] <persia> pwnguin: Well, the authentication is strong, but the authorisation weak.  Perhaps slightly different issues.
[10:40] <jono> heya \sh
[10:43] <persia> pwnguin: After a bit more of a look in the docs, am I correct that g-s-d is receiving PAM_USER_PROMPT properly, but has no way to know when to call pam_authenticate() without a <cr>?
[10:44] <pwnguin> im not clear on that
[10:44] <pwnguin> which package is that in?
[10:45] <pwnguin> gnome scrensaver?
[10:47] <persia> pwnguin: From what I understand, your package should provide an API that includes pam_get_item() to collect PAM_USER_PROMPT and pam_authenticate, as part of the standard interface for an authentication provider.
[10:47] <persia> g-s-d would be responsible for calling these functions in the pam modules it is configured to support.
[10:56] <pwnguin> i wish source code would document what the hell the file IS
[11:07] <pwnguin> well, i at least got it working. im not happy with the means, but its a start.
[11:08] <pwnguin> are there any stupid pam modules in universe?
[11:10] <persia> pwnguin: libpam-ccreds, libpam-chroot, libpam-ck-connector, etc.  (packages.ubuntu.com is your friend)
[11:10] <pwnguin> none quite as crack-headed as this one though
[11:11] <persia> Ah.  For the especially crackful, you want things that haven't been included yet :)
[11:11] <pwnguin> this is unfortunate
[11:11] <pwnguin> the wiki already includes a "how to build thinkfinger"
[11:11] <pwnguin> and Debian's packaging it
[11:12] <pwnguin> i imagine this means it'll come in automatically come sync time
[11:12] <pwnguin> or does that go into a seperate queue?
[11:13] <pwnguin> it's generally a good package; for the moment it errs on the side of "buggy" than "insecure"
[11:13] <persia> pwnguin: If it's accepted in Debian, it gets included during sync time unless it's blacklisted.
[11:29] <norsetto> morning all
[11:33] <blueyed> Hi.
[11:33] <blueyed> dpkg-trigger allows to defer the usage of ldconfig. Is there something similar for depmod?
[12:01] <huats> morning norsetto
[12:01] <norsetto> huats: morning
[12:04] <asisak> morning bad old norsetto
[12:06] <dholbach> norsetto, asisak: you have a very *special* kind of relationship, haven't you? :)
[12:06] <asisak> Not at all.
[12:07] <asisak> (norsetto, .*) is a kind of relationship :D
[12:08] <asisak> BTW I had to fix tilda from CVS. Is it still possible?
[12:08] <asisak> I mean because of the freeze(s)
[12:09] <dholbach> fixes in universe are still getting considered, if they fix things
[12:09] <norsetto> dholbach, asisak: morning gents
[12:10] <asisak> dholbach: fixes.* are meant to fix things :)
[12:10] <dholbach> upload it and ask the release managers to take a look at it
[12:10] <asisak> bug 144175 renders tilda almost unusable
[12:10] <ubotu> Launchpad bug 144175 in tilda "tilda stays like a gray window" [Medium,Fix committed]  https://launchpad.net/bugs/144175
[12:12] <asisak> I have to prepare a fix first :(
[12:12] <asisak> And CVS has quite many changes
[12:48] <jerry760poip_> hi i got a question not sure if this is were to ask
[12:48] <jerry760poip_> http://paste.ubuntu-nl.org/40245/
[12:48] <norsetto> dholbach: can I ask your advice abou bug 147188 ? I don't think just adding Debian.NEWS will be enough, will it?
[12:48] <ubotu> Launchpad bug 147188 in sensors-applet "Sensors-applet report Core 2 Duo temp as A (Ampere)" [Low,Confirmed]  https://launchpad.net/bugs/147188
[12:51] <persia> jerry760poip_: It's a good idea to provide more context when asking questions.  For your specific question, I doubt Ubuntu can assist.
[01:00] <persia> norsetto: Test an upgrade.  If I remember correctly (and I may not), new NEWS entries are available in display while upgrading (especially if apt-listchanges is installed).
[01:08] <norsetto> persia: ok, thx, will do
[01:12] <DrKranz> pkern, around for aolserver4 FTBFS?
[01:15] <norsetto> persia: do you know if what the guy is saying about CC-BY-SA 2.5 is true?
[01:18] <persia> norsetto: He's requesting that we pull from upstream, rather than pulling from Debian.  The new icons are not DFSG-free, but they appear to be Ubuntu-free at first glance at the license.
[01:19] <norsetto> persia: I think we should then suggest him to open another bug specific on that, so that the desktop people can comment
[01:21] <persia> norsetto: That seems like a lot of extra work.  If you want to do something towards license rationalisation, it makes more sense to me for you to just open the bug.  My experience with upstreams is that they have only limited interest in distribution beauracracy, and tend to retreat rather than participating (although they can certainly be attracted by collaboration).
[01:21] <persia> My personal take on it is that it's too late for gutsy, but as I'm a sensors-applet user, I'll consider pulling from upstream for an early hardy merge, rather than pulling from Debian.
[01:22] <persia> (not even filing a bug)
[01:22] <norsetto> persia: well, that seems to be the best really
[01:24] <norsetto> persia: the only problem is that between me and you, opening the bug would have meant having a record and the concurrence (or not) of seb128's gang
[01:24] <persia> My philosophy is that bugs get filed by people who either don't understand the issue, don't have time to address it, or don't have permission to fix it.  Anything else just seems like handwaving.
[01:25] <norsetto> persia: ok, I'll draw seb128 attention to it
[01:26] <norsetto> persia: it is true that the icons are pretty ugly ....
[01:26] <persia> norsetto: If sensors-applet reported the Desktop Team as the maintainer, I'd completely agree with you.  Because it reports MOTU, I'd say it's only about 50% important.  This is especially the case because there are no Ubuntu variations.
[01:27] <norsetto> persia: ah, I thought it was part of the Desktop team heritage
[01:27] <persia> norsetto: It may be: I haven't actually researched the package history.  If so, then yes, it is appropriate to ping them, and a bug may be the best way to do that.
[01:29] <norsetto> persia: are u on Gnome/amd64?
[01:30] <persia> norsetto: Essentially.  My session isn't quite default, and I've a fair bit of legacy hanging around.
[01:30] <norsetto> persia: would you mind checking it out? I'm on kubuntu
[01:30] <DktrKranz> persia, some hours ago, pkern informed me aolserver4-nsopenssl FTBFS due to an error in aolserver4 (which I merged). I tested -nsopenssl on my PPA and it's working now, a give back should be enough
[01:30] <persia> norsetto: Do you mean testing the patch?
[01:31] <norsetto> persia: or the binary, I just built it
[01:31] <persia> norsetto: What level of testing do you need.
[01:31] <persia> DktrKranz: OK.  Have you requested a give-back before?
[01:32] <norsetto> persia: just if the user is alerted of the need to remove/reinstall the applet
[01:32] <norsetto> persia: all the rest I checked already
[01:32] <DrKranz> persia, a couple of times, but I wanted you to know about it
[01:33] <persia> norsetto: OK.  That shouldn't be environment-specific, but I'll give it a shot.  Where's the package (source preferred)?
[01:33] <persia> DktrKranz: Because I touched it before?  No worries.  I was only chasing the RC list, and really know very little about it.  Thanks for the note.
[01:33] <norsetto> persia: if you prefer the source than perhaps its better if you use apt-get source and apply the patch
[01:39] <norsetto> persia: I just installed it and didn't see anything relevant on screen
[01:40] <persia> norsetto: What did you use to install?
[01:40] <norsetto> persia: dpkg, thats maybe why?
[01:41] <persia> norsetto: That'd do it.  For a proper test, you'll need to fake a repo.  From what I understand, NEWS notification is an apt-level function rather than a dpkg-level function.
[01:42] <ScottK> asisak: We got the checkgmail .desktop thing done while you were sleeping.  Thanks for offering to work on it.
[01:42] <norsetto> persia: ok, let me check if I can override the dependancies with apt-get then
[01:44] <norsetto> persia: actually, I wonder if that is implemented in synaptics/adept too
[01:45] <persia> norsetto: It ought to be.  From what I understand, those are just GUIs for libapt, although I may be mistaken (the newer .desktop-driven easy installer is quite low-level, and that backend may be used in preference).
[01:47] <DktrKranz> persia, given back and succesfully built (FYI)
[01:47] <persia> DktrKranz: Cool.  Not that I think they have that many users, but releasing FTBFS software is unfortunate (and all too common).  Thanks a lot.
[01:48] <DktrKranz> np
[01:53] <ScottK> persia: Even better its one more openssl0.9.7 rdepends gone so maybe we can get that removed before release....
[01:54] <StevenK> blueyed: Thanks for playing with virtualbox-ose-modules, but I'd prefer it built on i386 ... :-)
[01:54] <blueyed> StevenK: it builds here for i386 ?! (are you on amd64?)
[01:54] <persia> ScottK: I seem to remember being discouraged by vmware-player, which needed some internal changes to use 0.9.8.  Did that get fixed?
[01:54] <blueyed> StevenK: I've just uploaded it to my ppa to test the build
[01:55] <ScottK> persia: Someone else pointed out that the version we had if sufficiently anciean (1.x versus 2.x) as to be effectively unuseable and filed a removal bug.
[01:55] <ScottK> I might not have been so bold myself.
[01:56] <blueyed> StevenK: you may want to subscribe to bug 144801, too.
[01:56] <ubotu> Launchpad bug 144801 in virtualbox-ose "VirtualBox kernel driver not installed" [Undecided,Confirmed]  https://launchpad.net/bugs/144801
[01:56] <ScottK> There is a newer package in Debian, but we don't have it and it's way to late to get it now.
[01:57] <StevenK> blueyed: Yes I'm on amd64
[01:57] <StevenK> blueyed: Okay, I'm curious if PPA can build it
[01:57] <persia> Is aolserver4-nsimap in process, or does that need a poke as well?
[01:57] <StevenK> blueyed: If it builds, I'll get a second opinion about your debdiff
[01:58] <zerwas> Is it still possible to get a bugfix release of software in the universe repository?
[01:58] <persia> zerwas: For certain definitions of bugfix, yes.
[01:59] <zerwas> or perhaps anybody can give me a link how this is handled.
[01:59] <persia> zerwas: Which bug?
[01:59] <zerwas> persia, until which point is this possible?
[01:59] <zerwas> persia, we are doing a bugfix release of Gimmie at the moment
[02:00] <persia> zerwas: Until the buildd admins stop building packages for universe, or the archive admins stop letting them be uploaded.  Not much longer.
[02:00] <persia> zerwas: Upstream bugfix release?
[02:00] <zerwas> persia, yes
[02:01] <persia> zerwas: Those are harder to get in:  You can try following https://wiki.ubuntu.com/FreezeExceptionProcess#head-1d28045481b8803d4815989e93edc4206f4848c4, but I doubt it'll be approved once we hit RC (likely in the next couple hours).
[02:02] <zerwas> ok so it won't get into it. But thank you very much for this information
[02:03] <persia> zerwas: No problems.  If there's a critical patch that really needs to make it, the easiest way is to open a LP bug with the patch, and ask someone in this channel to prep an upload.  The threshold for specific patches for demonstrable bugs in the Ubuntu packages is lower than for new upstreams.
[02:06] <zerwas> persia, ah ok that sounds good. and good to know how to handle this. the bad thing is that i am getting many bugs every day in bugzilla, coming from Ubuntu users :)
[02:06] <pkern> Anyone up for SRU verification of firehol? (dapper edgy) Although I don't know what one should check. (List of reserved IPs updated.)
[02:07] <persia> zerwas: Sorry to hear that.  We try to encourage people to post to LP so we can filter packaging bugs from upstream bugs, and have a first crack at patching the easy ones, but we're not as successful as we might be.
[02:07] <ScottK> pkern: I can do it for Dapper if you give an exact procedure, but probably not until tomorrow.
[02:07] <ScottK> pkern: I just filed the openssl097 removal.
[02:08] <zerwas> persia, that's no problem :-). When we will finish the bugfix-release it will hopefull change. thanks again for your help
[02:08] <pkern> ScottK: Ok.
[02:09] <ScottK> zerwas: If you have specific patches that fix serious bugs, it's possible someone here could get them in.
[02:09] <pkern> ScottK: The patch is so trivial that the only thing which could fail IMHO is the installation. (Although there is NO reason for it.) So simple install testing is sufifcient.
[02:09] <pkern> Maybe it should be invoked once to check for syntax errors, but even that could possibly be caught by installation.
[02:10] <zerwas> ScottK, yes i will talk with the other devs about that
[02:10] <persia> zerwas: Just as an estimate, we'll probably have trouble applying them come Monday or so (although my guess isn't official).
[02:11] <ScottK> pkern: Bug #?
[02:11] <zerwas> persia, all right
[02:11] <CyberMatt> question about REVU
[02:12] <persia> CyberMatt: Go!
[02:12] <CyberMatt> what exactly do i upload .dsc, source tarball and changes
[02:13] <CyberMatt> or just source tarball and changes
[02:13] <persia> CyberMatt: You'll pass your _source.changes to dput, and it will upload all the files listed therein
[02:13] <CyberMatt> ah
[02:14] <persia> CyberMatt: This is so that it can verify the signature on the .changes file, and use the md5sums to verify the other files.
[02:14] <CyberMatt> i see
[02:15] <CyberMatt> thanks
[02:16] <pkern> ScottK: #131946
[02:16] <persia> pkern: Ubotu isn't that smart :(
[02:16] <pkern> ScottK: LP: #13946
[02:16] <pkern> ScottK: LP: #131946
[02:17] <pkern> Bah \:
[02:17] <ScottK> Bug #131946
[02:17] <persia> bug # 131946
[02:17] <ubotu> Launchpad bug 131946 in firehol "Firehol in Ubuntu 6.10 can't work properly due change in reserved ips" [Undecided,Fix committed]  https://launchpad.net/bugs/131946
[02:17] <persia> Right.  That's it.
[02:17] <mok0> :-)
[02:17] <pkern> Fun.
[02:18] <CyberMatt> another question i used http://sponsors.debian.net/viewpkg.php?id=381  as the base for my own inspircd package is it still ok to upload
[02:19] <StevenK> blueyed: Any news?
[02:20] <persia> CyberMatt: As long as your version either A) completely replaces the debian/ directory, or B) 1) has a higher version number and 2) preserves the previous changelog.
[02:20] <CyberMatt> or does that Darren Blader have some kind of lock
[02:20] <blueyed> StevenK: does not seem to have been built yet: https://edge.launchpad.net/~blueyed/+archive
[02:20] <persia> CyberMatt: He likely has copyright on the previous debian/.  I'm sure it's licensed broadly, but it's best to keep a record of previous work.
[02:21] <StevenK> blueyed: Fairy nuff
[02:22] <CyberMatt> ii do have a higher version the 1.1.8 was a bit buggy had a security issue as I remember
[02:23] <ScottK> pkern: Doesn't seem to be on my mirror yet.  Ping tomorrow if I don't comment in the bug in the meantime.
[02:23] <CyberMatt> so I spent like 4 hours bringing up to speed
[02:24] <CyberMatt> 1.1.8 was a bad bad dream
[02:24] <persia> CyberMatt: In that case, it's easier to preserve the previous changelog & copyright notices, just treating your packaging as part of collaborative maintenance.  If the packaging is DFSG-free (and it should be), everything would be good.
[02:26] <CyberMatt> ok then I will make sure I have all that and upload
[02:27] <CyberMatt> could someone be good enough to resync the Revu keyring
[02:27] <persia> CyberMatt: For extra points, I'd suggest sending your patches back to Darren once you've gotten reviewed.  It's best when Debian has a similar package.
[02:28] <CyberMatt> I will
[02:28] <ScottK> CyberMatt: Is your package aimed at Hardy or Gutsy
[02:30] <CyberMatt> is it too late to get in to gutsy
[02:30] <pkern> ScottK: When's tomorrow for you? (UTC)
[02:31] <ScottK> CyberMatt: Unless you are adding just security/serious bug fixes yes.
[02:31] <ScottK> pkern: 1300
[02:31] <pkern> ScottK: Uh. So I should ask ya in an hour? ;)
[02:31] <CyberMatt> then Hardy
[02:31] <ScottK> pkern: Tomorrow, yes.
[02:31] <pkern> :-P
[02:32] <ScottK> i.e. 25 hours from now.
[02:32] <pkern> Wouldn't that be the day after tomorrow then? ;)
[02:32] <Ash-Fox> How does one sign packages after they have been built? (Since I build everything on a server, I'd rather not shove my GPG key there for obvious reasons)
[02:32] <ScottK> CyberMatt: Would you consider trying to work with the Debian maintainer to get your update into Debian?
[02:32] <persia> Ash-Fox: debsign
[02:33] <pkern> Ash-Fox: debrsign
[02:33] <Ash-Fox> Thanks
[02:33] <ScottK> Off for a nap.
[02:33] <persia> r?  Does that do nifty remote signing?
[02:33] <CyberMatt> yed i will E-mail him
[02:33] <pkern> persia: Yep. Via SSH.
[02:33] <pkern> persia: Copies dsc and changes over, signs them, fetchs them back.
[02:33] <persia> Extra nifty.  Attached, or detached?
[02:33] <pkern> (And removes them.)
[02:33] <CyberMatt> he saved me two days of work
[02:33] <pkern> persia: Don't know what that means. :-P
[02:34] <pkern> persia: man debrsign
[02:34] <CyberMatt> so definitly
[02:34] <persia> pkern: From your previous line, attached.  Detached is the .asc files that go next to the signed files, as opposed to the inline signatures.
[02:36] <pkern> persia: Thought that, but I did not know what sense attached signatures should make.
[02:36] <persia> pkern: attached is probably not the right word.
[02:36] <CyberMatt> is there a difference in how i upload for Hardy forgive me first package non checkinstall that actually  works
[02:36] <pkern> Hm... object subject verb. That sounds wrong.
[02:37] <persia> CyberMatt: Be sure to use "hardy" instead of "gutsy" as the target distribution in the last changelog entry.
[02:37] <CyberMatt> ok
[02:38] <persia> pkern: Depends on context.  I believe "Him I struck" is correct, although it may be supposed to be "He I struck" (this gets into deep grammar)
[02:39] <pkern> "He I struck" sounds wrong to me. o_O
[02:39] <CyberMatt> man this is exciting my first contribution to an open source project
[02:40] <dholbach> norsetto: what about Debian.NEWS?
[02:40] <dholbach> urg... he's gone
[02:40] <persia> pkern: It's used rarely.  "That's she" is technically correct, whereas "That's him" is wrong.  Something about nominatives and predicate structures (It's been a while since I was actually studying English).
[02:40] <dholbach> congratulations CyberMatt :-)
[02:41] <norsetto> I just saw a message while quitting?
[02:41] <persia> norsetto: My apologies.  I seem to be having difficulties with my local repository.  I'll comment with my experiences to the bug.
[02:41] <pkern> 
[02:42] <Ash-Fox> Grm, this is a problem.. I can't seem to specify a port for ssh in debrsign and the manual doesn't have any information on this.
[02:42] <norsetto> persia: ok, I'm just rebuilding anyhow, since I had to make few changes, and intend to check it with Gnome after lunch (I've got a partition with it).
[02:42] <persia> Ash-Fox: Configure your ports in ~/.ssh/config
[02:43] <persia> norsetto: OK.  I don't think it's a GNOME thing: rather about whether apt-listchanges is installed, but I'm not entirely sure.
[02:44] <norsetto> persia: now, I think it was simply that it was named debian/NEWS instead of debian/NEWS.Debian
[02:45] <persia> norsetto: That would do it.
[02:45] <Ash-Fox> persia, thanks.
[02:45] <norsetto> persia: ok, now I'm going to have that bloody lunch, and will check the new build after. this should be ok .. l8r
[02:46] <TheMuso> c
[02:46] <TheMuso> wrong tab...
[02:46] <persia> Ash-Fox: You probably want to configure all your common hosts there: it saves lots of typing ssh options.
[02:50] <CyberMatt> oops Blader goofed up on the copyright
[02:51] <CyberMatt> ill fix that file
[02:52] <persia> Hah!  Aptitude fails to URL-encode URLs with interesting characters, and breaks compliant webservers when revision numbers include "+"!
[02:55] <zul_> ScottK: if that dependency is fixed for nswrapper then im ok with it
[02:56] <Hobbsee> how's that for good acronym use?
[02:56] <persia> Hobbsee: GTTFO?  GTFO?
[02:57] <Hobbsee> persia: either.  the first actually refers to an awesome livejournal post.
[02:57] <Hobbsee> but essentially has the same meaning
[02:57] <soren> http://www.google.dk/search?ie=UTF-8&oe=UTF-8&q=gttfo+livejournal  -> ENOENT
[02:58] <StevenK> s/ to search//
[02:59] <Hobbsee> soren: http://community.livejournal.com/metaquotes/5833841.html
[02:59] <TheMuso> StevenK: lol
[02:59] <persia> Thee!
[02:59] <Hobbsee> read the entire thing.  it seriously rocks :D
[03:04] <CyberMatt> need help in this copyright file the debian maintainer has this line
[03:04] <CyberMatt> The Debian packaging is (C) 2007, Darren Blader <dmbtech@gmail.com> and
[03:04] <CyberMatt> is licensed under the GPL, see above.
[03:05] <imbrandon> Hobbsee: haha classic
[03:05] <imbrandon> CyberMatt: whats the problem?
[03:05] <persia> CyberMatt: I'd recommend leaving that, and assigning Darren copyright for your packaging (with your name in the changelog indicating you did it).  That's usual practice.
[03:05] <Hobbsee> imbrandon: yup :D
[03:06] <persia> More specifically, by not changing the file, you automatically assign copyright, so it's neither extra thought or extra work.
[03:06] <persia> s/or/nor/
[03:06] <CyberMatt> ok should i add a line saying i assign all copyright to him
[03:07] <imbrandon> wow upgrading a 200mhz box to gutsy is painfull
[03:07] <persia> CyberMatt: You don't need to do that.  By publishing it with that copyright entry, you announce the assignment.
[03:07] <imbrandon> CyberMatt: no, as persia said , do nothing and it automticly is
[03:07] <CyberMatt> ok
[03:07] <persia> (the previous comment is copyright, 2007 Santa Claus)
[03:07] <soren> imbrandon: When I did that, it took me most of a working day. What was with ubuntu-desktop installed and all that, though.
[03:08] <imbrandon> this is with xfce4, still rough though
[03:08] <blueyed> Riddell: kde-hal-device-manager FTBFS for Gutsy. Is it supposed to be in Gutsy? Is 0.3 the most recent version?
[03:08] <imbrandon> i really need to get a better system but $$ sucks right now ;)
[03:10] <Riddell> blueyed: yes, yes
[03:11] <blueyed> Riddell: see http://people.debian.org/~lucas/logs/2007/08/28/kde-hal-device-manager_0.3-0ubuntu2_gutsy32.buildlog
[03:11] <blueyed> pbuilder works..
[03:11] <blueyed> Is there a way to better simulate the ubuntu build system?
[03:12] <persia> blueyed: set up wanna-build, and make it feed sbuild.
[03:12] <Riddell> blueyed: it may need a build-dep on python-qt-dev
[03:14] <blueyed> Riddell: either python-qt3 or python-qt4-dev I think (according to apt-file search pyqtconfig)
[03:16] <blueyed> persia: according to https://help.ubuntu.com/community/SbuildLVMHowto ?
[03:18] <persia> blueyed: That's a good start (use the script), but it only does the sbuild side.  Auto-feeding from wanna-build can help with multiple-architecture builds (if you have the hardware).  You also want to install extra packages in the chroot like pkg-create-dbgsym and pkgbinarymangler (I don't know the complete list).
[03:21] <CyberMatt> iits in revu
[03:21] <CyberMatt> it takes like 5mins to show right
[03:22] <persia> CyberMatt: The incoming processor runs every 5 minutes, so the worst-case should be about 6 minutes (usually it's around 3).
[03:23] <persia> Also, we're not really in a big REVU cycle at this point in the release cycle (next REVU day is to be decided 19th October), so it might be a bit before you get feedback.
[03:24] <Riddell> StevenK: ping
[03:24] <Riddell> you packaged libtinymail?
[03:25] <StevenK> Right
[03:25] <Riddell> StevenK: debian/copyright says GPL, but most of the code and the COPYING files in LGPL
[03:25] <StevenK> Crap.
[03:25] <StevenK> Riddell: REJECT it, and I'll look at tomorrow morning.
[03:25] <Riddell> StevenK: rejected
[03:26] <StevenK> Riddell: Thanks.
[03:26] <Riddell> StevenK: you should tell upstream to include a copy of the GPL
[03:27] <Riddell> and change debian/copyright to say LGPL with some files under tests/ and libtinymail-test/ GPL
[03:30] <StevenK> Riddell: Right. libtinymail is due to -mobile stuff, so I'll fiddle and re-upload tomorrow morning.
[03:41] <joejaxx> persia: you said that the debian menu was updating on your machine (ubuntu)?
[03:42] <persia> joejaxx: I thought it was.  I'll test a package now...
[03:42] <joejaxx> what version of ubuntu {is,was} it?
[03:42] <persia> joejaxx: About an hour ago
[03:43] <CyberMatt> my revu package is not showing up
[03:44] <persia> joejaxx: Interesting.  Do you have python-wxtools installed?
[03:44] <joejaxx> let me see
[03:44] <persia> CyberMatt: Are you in the keyring?  Did you sign the package?
[03:45] <CyberMatt> yes
[03:45] <CyberMatt> oh wait
[03:45] <Hobbsee> did you upload a source.changes or an .i386.changes?
[03:45] <joejaxx> persia: no i do not
[03:45] <CyberMatt> gpg: Signature made Thu 11 Oct 2007 09:16:39 AM EDT using DSA key ID 469C7BCD
[03:45] <CyberMatt> gpg: Good signature from "Matt Arnold <mattarnold5@gmail.com>"
[03:45] <CyberMatt> Good signature on /home/matt/debian/inspircd_1.1.13-1ubuntu6.dsc.
[03:45] <CyberMatt> Package includes an .orig.tar.gz file although the debian revision suggests
[03:45] <CyberMatt> that it might not be required. Multiple uploads of the .orig.tar.gz may be
[03:45] <CyberMatt> rejected by the upload queue management software.
[03:45] <CyberMatt> Uploading to revu (via ftp to revu.tauware.de):
[03:45] <CyberMatt>   inspircd_1.1.13-1ubuntu6.dsc: done.
[03:45] <CyberMatt>   inspircd_1.1.13.orig.tar.gz: done.
[03:45] <CyberMatt>   inspircd_1.1.13-1ubuntu6.diff.gz: done.
[03:45] <CyberMatt>   inspircd_1.1.13-1ubuntu6_source.changes: done.
[03:46] <CyberMatt> Successfully uploaded packages.
[03:46] <joejaxx> CyberMatt: please use pastebin :D
[03:46] <CyberMatt> Not running dinstall.
[03:46] <persia> !pastebin | CyberMatt
[03:46] <ubotu> CyberMatt: pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic)
[03:46] <CyberMatt> oh i'm sorry
[03:46] <persia> joejaxx: OK.  I just noticed a syntax error in the python-wxtools menu file, which might have been the problem.
[03:46] <Hobbsee> is Nicolas Spalinger here?
[03:47] <joejaxx> persia: is that the one you just tried to install?
[03:47] <Hobbsee> it appears not
[03:47] <persia> joejaxx: No.  I'm playing with sgt-puzzles.  It generates heaps of menu items, and doesn't have any .desktop files, which seems a good way to contain the test.
[03:47] <Hobbsee> he wins hte award for the week about not reading the documentation.
[03:47] <Hobbsee> x2.
[03:47] <joejaxx> persia: ah
[03:48] <Hobbsee> er, x3.
[03:48] <CyberMatt> http://paste.ubuntu-nl.org/40259/
[03:48] <persia> CyberMatt: That looks normal.  When did you join ubuntu-universe-contributors?
[03:48] <Hobbsee> anyone know anything about wine breakage?
[03:48] <Hobbsee> like uploading wine to revu or something?
[03:48] <Hobbsee> it's incomplete
[03:49] <CyberMatt> yesterday 10pm
[03:49] <persia> Hobbsee: I think there was list traffic about it, and someone handled it locally.
[03:49] <CyberMatt> EDT
[03:49] <persia> CyberMatt: What time is it now?
[03:49] <Ash-Fox> Hm, interesting - despite signing the .dsc and .changes files - I find my tiny repository still shoots out this message in apt-get "WARNING: The following packages cannot be authenticated!" - I'm guessing the repository Packages.gz file needs to be signed in some way?
[03:49] <Hobbsee> persia: likely hasnt been resynced yet.
[03:49] <CyberMatt> 9:50AM
[03:49] <persia> Ash-Fox: You need to import the keys into the apt-keyring (I think).
[03:50] <Hobbsee> Ash-Fox: probably because apt-get is downloading binaries, not sources.
[03:50] <persia> Hobbsee: Yep.  Could you resync when you have a chance?
[03:50] <persia> CyberMatt: It's not been long enough.  Wait for the next sync.
[03:51] <persia> Hobbsee: Good point.  Ash-Fox: Does your local repository contain the signature files?
[03:51] <Hobbsee> persia: yeah, it's a keyring problem.  resyncing.
[03:51] <imbrandon> Ash-Fox: not packages, your releases file iirc , but yea the repo needs signed not individual packages
[03:52] <persia> Hobbsee: Thanks.  Also, where is it hosted now?  I'd like to help with admin again for Hardy.
[03:52] <Hobbsee> persia: revu?  same address as always
[03:52] <Hobbsee> it's still on sparky at the moment though
[03:52] <CyberMatt> ok
[03:53] <Ash-Fox> imbrandon, right - which applications create a releases file? I'll look up how to use them
[03:53] <CyberMatt> have to call the bank anyway
[03:53] <persia> imbrandon: When you have some time, would you mind syncing my SSH key to sparky, so I might help with REVU admin?
[03:54] <imbrandon> Ash-Fox: something similar to ...
[03:54] <imbrandon> apt-ftparchive release -c dists/feisty/apt.conf dists/feisty/ > dists/feisty/Release
[03:54] <imbrandon> gpg --sign -ba -o dists/feisty/Release.gpg dists/feisty/Release
[03:54] <imbrandon> ( thats from my bash script to regin a personal archive )
[03:54] <imbrandon> persia: sure one sec
[03:54] <persia> imbrandon: Thanks.
[03:55] <imbrandon> persia: err actualy i dont have access to my own ssh keys on this machine atm, is ajmitch arround ?
[03:55] <imbrandon> he should be able to also
[03:55] <StevenK> persia: If you're in -dev, you already do have access
[03:55] <persia> imbrandon: heh.
[03:55] <Hobbsee> persia: what account to you use to be able to login to revu?
[03:55] <persia> StevenK: No.  I'm a special case.  imbrandon and I looked at it about 5 months ago, and didn't understand it, but I didn't actually care then.
[03:55] <imbrandon> Hobbsee: it should have instructions in the MOTD
[03:56] <imbrandon> on login
[03:56] <Hobbsee> imbrandon: that doesnt come up for sparky anymore.
[03:56] <Ash-Fox> imbrandon, slight problem. I use 'dpkg-scanpackages', which doesn't seem to create a 'Release' file.
[03:56] <persia> Hobbsee: I can log in and comment, just not resync or authorise reviewers.
[03:56] <StevenK> Ash-Fox: apt-ftparchive release <path>
[03:56] <Hobbsee> persia: yeah, but to fix that, i need to know what you use to login to revu with
[03:56] <mok0> I need some suggestions on how to set up pbuilders so I can easily build both amd64 and i386 packages...
[03:57] <imbrandon> Ash-Fox: you could always use falcon :)
[03:57] <persia> Hobbsee: emmet.hikory@gmail.com (hurrah for spam filters)
[03:57] <imbrandon> mok0: there should be instructions on how to do just that in the pbuilder howto on the wiki
[03:58] <Hobbsee> persia: Altering emmet.hikory@gmail.com to level admin
[03:58] <mok0> imbrandon: thx, I will have a look...
[03:58] <imbrandon> mok0: np, after you read it if you have any specific questions feel free to ask in here
[03:58] <persia> Hobbsee: What does that do?  Is there a web interface for sync / authorise now?  My issue is with the ssh key sync.
[03:58] <Hobbsee> persia: ssh revu.tauware.de doesnt give you a nice p/w prompt?
[03:59] <Hobbsee> sorry, ssh key prompt?
[03:59] <persia> Hobbsee: Nope.  There's something funny about my key and sparky.  It's not a revu issue.
[03:59] <imbrandon> persia: ahh i fixed that i thought
[03:59] <Hobbsee> right.  i wonder how one fixes a key, etc.
[04:00] <pkern> REVU fun? (:
[04:00] <Hobbsee> oh, i see.
[04:00] <imbrandon> Hobbsee: it was some funky lf issues in the ~/.ssh/authorized_keys for his user so you would need to edit it as root
[04:00] <Hobbsee> imbrandon: yep
[04:00] <imbrandon> but i rember fixing it in the script
[04:01] <imbrandon> that syncs it
[04:01] <imbrandon> or so i thought
[04:01] <StevenK> If you edit it as root, make sure the ownership is correct
[04:01] <bddebian> Heya gang
[04:01] <persia> imbrandon: I think you fixed the script, but we never went back and tested it.  No worries - it wasn't important until this week :)
[04:01] <Hobbsee> imbrandon: next stupid question, where is persia's home account?
[04:01] <imbrandon> in /home/<lp-id>
[04:01] <pkern> bddebian: Mind you, I am German and sleep at night. Well, or later. ;o)
[04:02] <Hobbsee> hobbsee@sparky:/home$ ls persia*
[04:02] <Hobbsee> ls: persia*: No such file or directory
[04:02] <Hobbsee> imbrandon: i'm not *that* dumb :)
[04:02] <dholbach> norsetto: what about NEWS.Debian?
[04:02] <dholbach> norsetto: I didn't get your question
[04:02] <pkern> bddebian: At least I'm not awake at 6AM local time ;)
[04:02] <bddebian> pkern: :-)  Good, I was thinking maybe I offended you too or so? :)
[04:02] <imbrandon> hrm lemme see if i can get to a box with my ssh keys on it and look
[04:02] <CyberMatt> when will the next resybc be or can someone do it now
[04:02] <persia> imbrandon: No rush.
[04:03] <persia> CyberMatt: It's underway now.  It takes a couple hours.
[04:03] <pkern> Cool, can I get an account too? :-P
[04:03] <Hobbsee> imbrandon: of course, whether this machine has been resynced since persia got MOTU is a very interesting question too.
[04:03] <pkern> persia: It doesn't.
[04:03] <Hobbsee> CyberMatt: it's done now
[04:03] <norsetto> dholbach: Do you think is it enough to have it? Because when I install with apt-get or synaptic I'm not getting any feedback from it.
[04:03] <persia> Hobbsee: It was at least once, but I think only once.
[04:03] <imbrandon> Hobbsee: it should sync once every 4 hours iirc
[04:03] <dholbach> norsetto: to have it for what?
[04:03] <persia> norsetto: Install apt-listchanges to see the NEWS files
[04:04] <Hobbsee> imbrandon: right.  i thought all the autosync stuff got turned off.
[04:04] <dholbach> norsetto: I don't think I ever made use of the NEWS.Debian file
[04:04] <norsetto> dholbach: OK, you missed the rprevious question; its about bug 147188
[04:04] <ubotu> Launchpad bug 147188 in sensors-applet "Sensors-applet report Core 2 Duo temp as A (Ampere)" [Low,In progress]  https://launchpad.net/bugs/147188
[04:04] <pkern> Hobbsee: How long does the sync take now on feeled average?
[04:04] <dholbach> norsetto: what do you or Alex want to put into the news file?
[04:04] <CyberMatt> its says its already uploaded
[04:05] <dholbach> norsetto: ok, got it
[04:05] <imbrandon> Hobbsee: do me a favor and cat /etc/crontab and see when it syncs please
[04:05] <dholbach> norsetto: hrm, why do we apply that patch in the first place?
[04:05] <CyberMatt> I must sound like an n00b
[04:05] <norsetto> dholbach: the warning that the applet should be removed and re-installed for the changes to take effect
[04:05] <pkern> Now that sync cron stuff we had quite often now.
[04:05] <pkern> And nobody found it. :-P
[04:06] <Hobbsee> CyberMatt: yeah, give me a bit, i'm fighting with it.
[04:06] <dholbach> norsetto: is there no other way but purge & install?
[04:07] <persia> dholbach: It's not a purge/install, it's a "Remove from panel, Add to panel".
[04:07] <imbrandon> pkern: hehe we actualy have a "team" to admin them but i've been slacking ( pkern its in #ubuntuwire if your interested in the future when things settle )
[04:07] <dholbach> persia: oh ok
[04:07] <norsetto> dholbach: its not purge/install, its just removing from the panel and reinstalling
[04:08] <CyberMatt> sure ill go get Anope irc services and work on that package for a while
[04:08] <dholbach> norsetto: right - it's very hard to hack this into the code
[04:08] <imbrandon> Hobbsee: it might have , but not afaik, i am hoping it dident so it will resync my keys also
[04:08] <imbrandon> thus asking you to check
[04:08] <imbrandon> ;)
[04:08] <norsetto> dholbach: yes, so, is it worth adding it to preinst?
[04:08] <dholbach> norsetto: what firefox does is print "please restart all running firefoxes, ..." during installation
[04:08] <norsetto> dholbach: postinst actually
[04:08] <dholbach> you can't guarantee that people will read it
[04:09] <StevenK> Firefox also does a notify
[04:09] <CyberMatt> I like irc stuff and there's not much in the universe
[04:09] <dholbach> but I guess it's the easiest
[04:09] <dholbach> way
[04:09] <norsetto> dholbach: yes, you can, but I think it is better than a NEWS that nobody even know it exists
[04:09] <dholbach> right
[04:09] <dholbach> debconf notice would work too
[04:09] <dholbach> that's more work
[04:10] <norsetto> dholbach: yeah, ok, I will add a postint with the notice then
[04:10] <CyberMatt> hence inspircd Anope BOPM
[04:10] <dholbach> great, norsetto
[04:10] <persia> joejaxx: I'm now very confused.  If I execute update-menus, the menus get updated.  update-menus is definitely called in the postinst.  The actual menu update seems delayed somehow (by some minutes).  I'm guessing it's that the XDG menu building process for the logged-in user waits for idle time to execute, so that even though the menu files are updated, the user may not see them.
[04:10] <imbrandon> CyberMatt: you dont have to stick strictly to universe, main bugs are alsways welcome fixes too, you just need diffrent sponsors for uploads ( but there are core-devs in here too, including myself )
[04:10] <norsetto> dholbach: danke!
[04:10] <persia> dholbach: Thanks for the debhelper suggestion.  That's much more visible.
[04:10] <joejaxx> persia: interesting
[04:10] <Hobbsee> CyberMatt: right, it should appear.
[04:11] <StevenK> blueyed: I'm guessing it failed
[04:12] <pkern> imbrandon: I thought there were almost no admins besides siretart?
[04:12] <pkern> imbrandon: And only sparky left?
[04:13] <blueyed> StevenK: no, it was missing a dependency (because of the component). I've re-uploaded it as ~ppa1, which is now PendingRemoval. I'll try a re-upload as "3".
[04:13] <StevenK> blueyed: Way cool
[04:13] <imbrandon> pkern: there is like 4 admins ( me ajmitch siretart and seveas ) and yea alot of the boxes are gone now, but not perminately
[04:14] <CyberMatt> http://revu.tauware.de/details.py?upid=375
[04:14] <CyberMatt> cool
[04:14] <CyberMatt> I didn't mess up
[04:14] <CyberMatt> :D
[04:15] <TheMuso> persia: As one who has access to sparky, how can I now help with revu work if its needed?
[04:16] <TheMuso> Or anybody else? ^^
[04:17] <persia> TheMuso: You can get a REVU admin to add you to the REVU admin group.  If you do this, you can then run a few special commands, and get access to special areas on-disk.  This allows you to resync the keyring, authorise people to comment (e.g. non-LP-primary email addresses), clean up after broken uploads, troubleshoot upload issues, check for accout statuses, etc.
[04:17] <TheMuso> Ah ok.
[04:18] <pkern> imbrandon: Not sistpoty or so?
[04:18] <Hobbsee> imbrandon: i'm an admin too now, btw
[04:18] <Hobbsee> at least of this one
[04:19] <imbrandon> Hobbsee: ahh cool, yea its been a while since i have worried about any of this heh
[04:19] <persia> CyberMatt: REVU includes some automated package checking tools: look at the linda and lintian links.  Ideally you'll update the package so that these are nearly empty (there are a couple exceptions).  For extra cleanliness, call lintian and linda with the arguments listed in https://wiki.ubuntu.com/MOTU/Contributing
[04:19] <siretart> yes, we added some more people as admins on sparky
[04:19] <imbrandon> just been back a week or so ;)
[04:19] <Hobbsee> imbrandon: :)
[04:19] <siretart> hi imbrandon hi Hobbsee
[04:19] <Hobbsee> hiya siretart!
[04:19] <imbrandon> heya siretart
[04:19] <siretart> check /etc/sudoers
[04:19] <pkern> siretart: You're on?
[04:19] <imbrandon> siretart: i'm having Hobbsee redo my key from LP ( trying to update them now )
[04:19] <siretart> need to leave again, heading home!
[04:20] <siretart> imbrandon: ok
[04:20] <siretart> I'lll be back on in a few minutes
[04:20] <pkern> Ok (:
[04:20] <imbrandon> cept firefox seems to have died Hobbsee give me a few minutes i seem to be having issues
[04:20] <Hobbsee> ok
[04:21] <pkern> Could somebody set me up a REVU account? I could also just wait for siretart, no problem. Just to know who's in charge.
[04:21] <pkern> Or rather sparky.
[04:21] <siretart> pkern: shell account on sparky? - sure. please write me an email with what  you have in mind doing on sparky.
[04:21] <bddebian> Don't do it, he's secretly a Debian plant ;-P
[04:22] <joejaxx> persia: wait for the short period before it updated was that after package installation or after you did it maually?
[04:22] <joejaxx> persia: if i do it manually it builds it right then
[04:23] <persia> joejaxx: Package installation.  For manual, were you running as the local user, or as root?
[04:23] <joejaxx> root
[04:23] <joejaxx> as i wanted it system wide
[04:23] <persia> joejaxx: Well, that's extra confusing then.
[04:24] <siretart> bddebian: what makes you think I didn't become a Debian plant as well? ;)
[04:25] <imbrandon> hehe
[04:25] <bddebian> siretart: :)
[04:25] <StevenK> Yeah, the implant doesn't hurt at all. *twitch* *twitch*
[04:25] <persia> siretart: One cannot become a plant (although one can be turned...)
[04:25] <siretart> ;)
[04:25] <StevenK> persia: Semantics. :-P
[04:26] <persia> StevenK: The justification for language
[04:29] <joejaxx> persia: yeah it is
[04:29] <joejaxx> persia: too bad there is not a simple explanation about it
[04:30] <persia> joejaxx: Aside from being annoying, what does this break?  I'm not finding an answer, and thinking a workaround might be easier in the time remaining.
[04:30] <joejaxx> well the fluxbox menu depends on it
[04:31] <persia> joejaxx: Ah.  Is this new for fluxbox 1.0.0, or was it also true for 1.0.0rc3?
[04:31] <joejaxx> i believe it was true of rc3 as well
[04:31] <joejaxx> i would have to do a test though
[04:31] <asac> pkern: why did you upload a new upstream version of flashplugin-nonfree?
[04:31] <joejaxx> fluxbox has had a new maintainer since 0.9
[04:32] <joejaxx> well in debian that is
[04:32] <persia> joejaxx: No need.  I was just worried that the recent effort to get a release rather than an RC in had broken that.
[04:32] <Ash-Fox> How do one define the distribution in a apt.conf file? I've been looking in the man file apt.conf(5) and I can't find it.
[04:32] <joejaxx> persia: oh alright
[04:32] <asac> pkern: we talked about aa new package revision ... not a full upstream update
[04:32] <imbrandon> persia: your lp-id is persia correct ?
[04:33] <persia> Ash-Fox: There's slightly more verbose documentation in the apt-doc package
[04:34] <persia> imbrandon: Yep.
[04:34] <joejaxx> persia: i can have update-menus to run through a settings package that i have
[04:35] <Ash-Fox> persia, thanks.
[04:35] <joejaxx> persia: but it is kind of pointless if no applications after that will be on the menu
[04:35] <asac> pkern: please fix flashplugin-nonfree now!
[04:35] <asac> pkern: you dropped all ubuntu specific changes
[04:35] <persia> joejaxx: You could, but without understanding the issue, I'm not sure that helps.
[04:35] <joejaxx> but that does fix the problem of fluxbox coming up without a menu
[04:35] <asac> pkern: Npp- headers in control
[04:35] <joejaxx> persia: ^
[04:35] <persia> joejaxx: Is fluxbox default anywhere?
[04:35] <asac> pkern: i have to update the plugin db and now flashplugin-nonfree isn't found anymore because of this
[04:35] <asac> pkern: so please hurry ;)
[04:35] <joejaxx> persia: default anywhere?
[04:36] <persia> joejaxx: Part of a default session for something planned to be released.
[04:36] <joejaxx> ah yes
[04:38] <asac> pkern: further there is not a single word about the upstream version upgrade in the changelog
[04:38] <persia> joejaxx: If it's default, I'm tempted to fix it somewhere other than in a separate -settings package.  That seems like a last resort due to weak coupling
[04:41] <joejaxx> persia: yeah
[04:41] <joejaxx> it is last resort :P
[04:42] <joejaxx> i rather fix the larger issue
[04:42] <persia> joejaxx: I'm getting unreproducible behaviour.  Sometimes the menu files are still there after `dpkg -P sgt-puzzles`, and sometimes they're not.  The same for installation.  If I do nothing for a bit, things become more sane (although the timing varies).
[04:43] <joejaxx> the reason why there is no menu in fluxbox is because the menu is including a fluxbox men-method generated file which is not generated
[04:43] <joejaxx> menu-*
[04:43] <joejaxx> persia: that is interesting
[04:44] <persia> joejaxx: Is this consistently reproducible?  I'm getting better behaviour the more times I try it, which may be related to file caching (including archive caching).
[04:49] <persia> joejaxx: Also, try enabling debug in /etc/menu-methods/menu.config.  That may help to determine how/where it's blocking.
[04:50] <joejaxx> persia: yeap
[04:50] <joejaxx> it is reproducible
[04:50] <joejaxx> i just installed four packages that i know have debian menus
[04:51] <joejaxx> and it is not going through the metu-methods
[04:51] <joejaxx> menu-methods*
[04:51] <joejaxx> ok i will try that
[04:51] <persia> (verbosity=debug)
[04:56] <pkern> asac: Well do.
[04:56] <pkern> asac: *Will do
[04:56] <joejaxx> persia: just says forking to background :P
[04:57] <joejaxx> i wonder how i can stop it from doing that
[04:57] <persia> joejaxx: Reading the source, it appears that update-menus forks when first called, and the child waits for the dpkg-lock to clear.  Additional calls are nop events, as update-menus doesn't allow itself to be run twice.  When the dpkg lock clears (and all the menu files should be installed), update-menus processes everything currently installed on the system, and completely rebuilds the menus.  Before processing everything, it attempts to get a sp
[04:58] <persia> joejaxx: You really don't want it not to fork.  It reads all the menu files every time, so installing more than one package would be a nightmare.
[05:00] <DktrKranz> pkern, that FTBFS on aolserver4-msopenssl is now solved
[05:00] <pkern> DktrKranz: Thanks.
[05:00] <pkern> asac: pm, urgent.
[05:00] <DktrKranz> np...this time it was just a give back
[05:02] <persia> joejaxx: Are you ny any chance testing on a fast dual-core or dual-proc machine?  It may be a race condition (which is why it works when run manually: dpkg isn't locking)
[05:07] <persia> joejaxx: I must be off.  Best of luck.
[05:08] <persia> Hobbsee: Thanks for all your work.  I'll try a test in ~6/7 hours, and again in ~20 (just in case).
[05:08] <joejaxx> persia: no i mean instantly start after dpkg is done :D
[05:08] <Hobbsee> persia: i dotn think imbrandon's fixed it, has he?
[05:08] <persia> joejaxx: It's supposd to start right off when the lock is freed.
[05:09] <joejaxx> persia: yeah but it is not :\
[05:09] <persia> Hobbsee: Ah.  I thought you were attacking it wildly.  I'll ping him later.
[05:09] <Hobbsee> persia: i odn tknow what will happen if i just add you as a user...
[05:10] <persia> joejaxx: Right.  The fork is never returning.  Perhaps a race condition.  If verbosity=debug doesn't help, perhaps putting more debug statments in wait_dpkg may help.
[05:10] <persia> Hobbsee: No worries.  I certainly don't want to break anything.
[05:17] <pkern> bddebian: What the heck is a Debian plant?
[05:18] <bddebian> pkern: A spy.  Sent here by Debian to bring down Ubuntu ;-P
[05:20] <joejaxx> bddebian: lol
[05:20] <joejaxx> oh a "plant"
[05:20] <joejaxx> as in placed :P
[05:20] <joejaxx> ;)
[05:20] <pkern> As in placed. Now that explains it.
[05:21] <joejaxx> :)
[05:21] <pkern> bddebian: ACK then. Obviously.
[05:22] <geser> Hi bddebian
[05:25] <bddebian> heya geser
[05:54] <hendrixski> If I want to change a dpatch, instead of patching the patch... I try going into dpatch-edit-patch 0#_patchname and then I want to apply what that patch does so that I can change it... what commands should I run?
[05:56] <hendrixski> 'cause I tried dpatch apply 0#_patchname and it says failed, I tried patch ./ < debian/patches/0#_patchanem.dpatch  etc. etc.  none of that seems to make the changes inside the dpatch-edit-patch base that I need it to make :-(
[05:56] <hendrixski> any advice?
[05:59] <norsetto> hendrixski: dpatch-edit-patch should already apply all the changes up to and including the patch you are editing
[06:00] <hendrixski> norsetto, oh?
[06:00] <hendrixski> It looked like it was only applying up to the previous patch :-(
[06:01] <norsetto> hendrixski: it shouldn't, check it out again
[06:01] <blueyed> StevenK: it has been built finally! See https://edge.launchpad.net/~blueyed/+archive/+builds?build_text=virtualbox&build_state=all
[06:02] <hendrixski> hhmm, I say that because the patch is supposed to add a file to a directory, but it doesn't seem to do so :-(
[06:03] <norsetto> hendrixski: are you running the command at the top of the source tree?
[06:03] <norsetto> hendrixski: check the messages it gives, it should report what it applied
[06:04] <hendrixski> norsetto, I think so... it's not the one with the .dsc and .tar.gz  it's the first directory with code
[06:05] <norsetto> hendrixski: what dirs are in the dir with the .dsc etc.?
[06:07] <hendrixski> a few actually... I'm tinkering with mythtv, mythplugins, and mythstream... so all their folders, and .gz and all are in the same one... I'm applying it from the mythtv-trunk####/ folder... is that not the top of the source tree? and should the level up from that be clean except for the package itself?
[06:08] <hendrixski> I'll try it from a level higher :-)
[06:12] <hendrixski> Nope.. it doesn't work from a level higher :-(
[06:12] <norsetto> hendrixski: you can also specify the unpacked source directory with the -s option
[06:12] <norsetto> hendrixski: in any case, can you paste in a pastebin what dpatch reports?
[06:13] <hendrixski> yes
[06:13] <hendrixski> !paste
[06:13] <ubotu> pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic)
[06:14] <hendrixski> http://paste.ubuntu-nl.org/40269/
[06:16] <norsetto> hendrixski: it reports that the patch is applied correctly: applying patch 06_ubuntu_directories to ./ ... ok.
[06:17] <norsetto> hendrixski: so, whatever it is in there is applied. If its a new file, check the right path, or use find, it must be there
[06:18] <hendrixski> hhmmm, Ok,,, I'm re-downloading the source...maybe I hozed soemthing before when I did dpatch-edit-patch wrong the last time...
[06:18] <hendrixski> oh right.  find command :-)
[06:19] <norsetto> hendrixski: maybe you gave a wrong path or you used it in a chroot, so its in /temp somewhere
[06:21] <hendrixski> yikes! it's possible that changes made while in the dpatch-edit-patch mode can get lost in /temp?
[06:35] <dholbach> I'm calling a day! see you guys tomorrow!
[06:37] <norsetto> dholbach: bye!
[06:37] <dholbach> bye norsetto
[06:37] <Hobbsee> bye dholbach!  not going to stay around for the rc?
[06:38] <dholbach> Hobbsee: I need to get something to eat
[06:39] <Hobbsee> heh
[06:39] <dholbach> see you around!
[06:41] <asisak> bye dholbach
[06:41] <asisak> Hey Hobbsee
[06:41] <Hobbsee> hiya
[06:41] <asisak> (with the hope that norsetto does not ruin the rc)
[06:42] <bluekuja> take care asisak ;)
[06:52] <bddebian> Does anyone know why boswars got rejected?
[06:53] <Hobbsee> !info boswars
[06:53] <ubotu> Package boswars does not exist in feisty, feisty-seveas
[06:53] <Hobbsee> !info boswars gutsy
[06:53] <Hobbsee> did you check ubuntu-archive archives?
[06:53] <ubotu> Package boswars does not exist in gutsy
[07:02] <amachu_> bluekuja: hi
[07:02] <bddebian> Hobbsee: Aye it got rejected out of NEW but how do I find out why?
[07:04] <jpatrick> right we in FF? No NEW uploads?
[07:04] <bluekuja> amachu_: heya :)
[07:04] <amachu_> bluekuja: hey :-)
[07:04] <bluekuja> amachu_: happy to have you here
[07:04] <Hobbsee> bddebian: u-a ml
[07:05] <bddebian> jpatrick: it was uploaded on 8/29
[07:05] <bluekuja> amachu_: what are you packaging-side references?
[07:05] <bluekuja> *your
[07:05] <jpatrick> ah right
[07:05] <amachu_> bluekuja: happy to have you too..
[07:05] <amachu_> bluekuja: packaging-side references?
[07:06] <amachu_> i am unable to get the meaning exactly
[07:06] <bluekuja> amachu_: I mean have you ever packaged something?
[07:06] <amachu_> no not yet
[07:06] <bluekuja> amachu_: have you ever read out some guidelines?
[07:06] <amachu_> yes
[07:06] <bluekuja> amachu_: like?
[07:07] <bddebian> Ah, contained binary dlls
[07:07] <bddebian> Grr
[07:08] <amachu_> https://wiki.ubuntu.com/MOTU/TODO
[07:08] <amachu_> https://wiki.ubuntu.com/MOTU/Documentation
[07:08] <amachu_> i began with
[07:08] <amachu_> https://wiki.ubuntu.com/MOTU/Documentation
[07:08] <amachu_> https://help.ubuntu.com/ubuntu/packagingguide/C/index.html
[07:09] <bluekuja> amachu_: did you read my section on the packaging guide?
[07:09] <amachu_> and its in middle...
[07:09] <bluekuja> amachu_: debian/rules area in fact
[07:09] <amachu_> started and halted a bit
[07:09] <amachu_> saw the mail a while back
[07:09] <amachu_> and pinged you
[07:09] <Whoopie> albert23: hi, did you find the time to test uswsusp again?
[07:10] <amachu_> i will catch up with them and get back to you
[07:10] <bluekuja> amachu_: well done, I think we should start doing a package then
[07:10] <amachu_> yes
[07:10] <bluekuja> amachu_: you told me you're ready from a teorical point of view
[07:10] <bluekuja> so let's move to pratic side
[07:11] <amachu_> ok
[07:11] <bluekuja> amachu_: are you interested in a package in particular?
[07:11] <albert23> Whoopie: yes, I did. It couldn't resume again. The splash did show nicely when it went in hibernate though
[07:11] <bluekuja> amachu_: something you use often or would like to have included in the archive?
[07:11] <amachu_> few min..
[07:11] <amachu_> i have come across few
[07:11] <Whoopie> albert23: what happened on resume?
[07:11] <amachu_> let me try recollecting
[07:12] <albert23> Whoopie: it just rebooted, so I lost my swap again
[07:12] <amachu_> yes
[07:12] <amachu_> the scim-tables-additional
[07:12] <amachu_> few new keyboard tables to be added to that
[07:13] <amachu_> for indian languages
[07:13] <albert23> Whoopie: Without uswsusp hibernate and resume work fine
[07:13] <amachu_> bluekuja: you there
[07:13] <bluekuja> amachu_: do you have an upstream website for that?
[07:14] <bluekuja> amachu_: yeah, sorry for the delay
[07:14] <Whoopie> albert23: that's really strange. do you have any idea why it just rebooted? did you check the initramfs size before and after install?
[07:14] <Whoopie> albert23: would be interesting if it's the initramfs update which happens during install.
[07:14] <amachu_> bluekuja: http://www.scim-im.org/
[07:15] <bluekuja> amachu_: I guess scim is already packaged
[07:15] <albert23> Whoopie: no, I only checked if the right uuid was in /etc/initramfs/conf.d/resume
[07:15] <bluekuja> andrea@nightsong:~$ apt-cache madison scim
[07:16] <bluekuja>       scim | 1.4.7-1ubuntu2 | http://it.archive.ubuntu.com gutsy/main Packages
[07:16] <bluekuja>       scim | 1.4.7-1ubuntu2 | http://it.archive.ubuntu.com gutsy/main Sources
[07:16] <Whoopie> albert23: did you edit /etc/acpi/hibernate.sh based on the patch I provided in bug 109151?
[07:16] <ubotu> Launchpad bug 109151 in uswsusp "no hibernate with uswsusp installed" [Undecided,Confirmed]  https://launchpad.net/bugs/109151
[07:16] <bluekuja> amachu_: seems to be already in
[07:16] <amachu_> its scim-tables-additional
[07:16] <Whoopie> albert23: because it looks to me, you didn't. /etc/initramfs/conf.d/resume is uninteresting for uswsusp
[07:16] <amachu_> with few modifications
[07:17] <bluekuja> amachu_: cant find it inside that website
[07:17] <albert23> Whoopie: uswsusp does change that resume file in the config script
[07:17] <bluekuja> amachu_: another link?
[07:17] <bluekuja> maybe direct would be better
[07:17] <amachu_> bluekuja: this is the debian equivalent http://packages.debian.org/scim-tables-additional
[07:18] <bluekuja> amachu_: well a sync would be ok then
[07:18] <Whoopie> albert23: could you pastebin your /etc/uswsusp.conf ?
[07:18] <albert23> Whoopie: I patched the source files with the debdiff
[07:18] <bluekuja> if debian got it already
[07:18] <bluekuja> amachu_: leaving for dinner, bbl (30 mins)
[07:18] <albert23> Whoopie: one minute, I must install it again
[07:18] <amachu_> bluekuja: ok
[07:19] <Whoopie> albert23: and please apply http://launchpadlibrarian.net/9582145/acpi-support_uswsusp.patch
[07:19] <amachu_> bluekuja: dinner?
[07:20] <amachu_> which geography are you from?
[07:22] <gnomefreak> when a package is archived in revu without comments what does that mean?
[07:23] <hendrixski> norsetto, hey..  just wanted to say thanks... turns out that my patch was going into the wrong directory,  if you hadn't recommended find then I wouldn't have found that out.  :-) thanks
[07:23] <norsetto> hendrixski: hey, no problem, glad I could help
[07:24] <norsetto> amachu: bluekuja is from North Italy, they eat at indecent times .....
[07:24] <amachu> norsetto: dinner?
[07:25] <norsetto> amachu: yes
[07:25] <amachu> norsetto: ok
[07:26] <albert23> Whoopie: http://paste.ubuntu-nl.org/40279/
[07:27] <Whoopie> albert23: and you applied the acpi-support patch?
[07:28] <albert23> Whoopie: yes, I just did
[07:29] <albert23> Whoopie: should I now hibernate again?
[07:29] <Whoopie> albert23: wait a sec
[07:30] <gnomefreak> any motus feel  like acking and pushing http://revu.tauware.de/details.py?upid=360 its been done since sept 20th or so i updated changelog for the day i built it for the 2nd time since i had to reinstall. the person that i expected to upload it isnt maybe busy i dont know
[07:31] <Whoopie> albert23: please change the "resume device" to the /dev/sdaXX instead of the UUID. Then "sudo update-initramfs -k 2.6.22-14-generic -c"
[07:31] <Whoopie> albert23: and then try hibernating.
[07:32] <albert23> Whoopie: in uswsusp.conf?
[07:32] <Whoopie> albert23: yes
[07:32] <pkern> gnomefreak: Rationale for deactivation of debian/patches/00list/82_prefs_ubuntu?
[07:35] <hendrixski> ah crap... when I run debuild -S where does it dump the binary again? /var/something or other?
[07:35] <Hobbsee> parent directory?
[07:36] <hendrixski> Hobbsee, hhmm, it's not there...
[07:36] <hendrixski> oh, I haven't set up my GPG on this computer yet :-(
[07:36] <deitarion> I'm a Gentoo-using application developer who wants to make source packages and feed them to my Launchpad PPA for building. Will I need any tools other than the Gentoo packages equivalent to build-essential, dpkg, gnupg, diff, and patch? I asked in #ubuntu and was directed here.
[07:37] <pkern> You should install Debian devscripts and stuff.
[07:38] <albert23> Whoopie: hanging now, with the progress bar at 100%
[07:38] <Whoopie> albert23: one step forward :) same was here, but I thought, it was my laptop. :(
[07:38] <albert23> Whoopie: I think the splash changed to a lower resolution then I normally have?
[07:39] <Whoopie> albert23: it uses /etc/usplash.conf as source for the resolution
[07:40] <albert23> Whoopie: so now just a hard reboot? Network is also still down
[07:40] <Whoopie> albert23: yes, sorry
[07:41] <albert23> Whoopie: no problem, it can't be as bad as what mkswap did yesterday
[07:42] <Whoopie> albert23: great, thanks for your help. We need to find out why your /etc/uswsusp.conf had UUID and why it hangs at 100%
[07:42] <deitarion> pkern: Are there any more specific names I can take to the people in #gentoo as examples? I suspect that I need to write a new ebuild for them, but I'd like to be sure.
[07:43] <albert23> Whoopie: no problem
[07:44] <bluekuja> amachu: back
[07:45] <amachu> bluekuja: hey
[07:45] <amachu> bluekuja: i was asking which geography are you from
[07:45] <amachu> :-)
[07:45] <bluekuja> amachu: I'm italian
[07:45] <amachu> fine
[07:45] <bluekuja> amachu: north italy, near venice
[07:46] <pkern> deitarion: I'm not on Gentoo anymore and I suspect packages.g.o is still down? ;)
[07:46] <amachu> ok..
[07:46] <pkern> deitarion: Is there a replacement available?
[07:46] <amachu> am from chennai
[07:46] <amachu> india
[07:46] <bluekuja> amachu: cool, what timezone?
[07:46] <amachu> bluekuja: its UTC + 5:30
[07:46] <bluekuja> oh :D
[07:46] <deitarion> pkern: I'm using the eix command with the "including overlays not active on this machine" extension, so I wouldn't know. A partial list of the more important tools I need should be enough though.
[07:47] <bluekuja> amachu: anyway, scim-tables-additional is inside ubuntu as well
[07:47] <bluekuja> amachu: use madison to to find out
[07:47] <bluekuja> amachu: usage apt-cache madison packagename
[07:47] <bluekuja> and you'll get it
[07:47] <pkern> devscripts (as found on ftp.d.o), dpkg-dev (which is included with dpkg), debhelper (as found on ftp.d.o) come to mind.
[07:48] <amachu> ok
[07:48] <hendrixski> what's madison?
[07:48] <Whoopie> albert23: <Mithrandir> Whoopie: hanging on 100% is known, alt-sysrq-k fixes it.
[07:49] <Whoopie> albert23: could you try it? I'm also doing it here.
[07:49] <bluekuja> amachu: first step
[07:49] <bluekuja> amachu: find a source to package
[07:49] <amachu> ok
[07:49] <bluekuja> amachu: something you think it's useful to have packaged
[07:49] <bluekuja> amachu: something you love
[07:49] <amachu> and that should not be in ubuntu now
[07:49] <bluekuja> amachu: something that can improve ubuntu
[07:49] <amachu> bluekuja: ok
[07:49] <albert23> Whoopie: ok, will try
[07:50] <bluekuja> amachu: yep
[07:50] <amachu> yes
[07:50] <amachu> i will
[07:50] <deitarion> pkern: OK. One other question: I've been considering just setting up an Ubuntu chroot on my system and I was wondering how much space that would probably take and how to get a nice minimal compilation-oriented setup.
[07:50] <bluekuja> amachu: so check if the package is already in, both using madison or Ubuntu/Debian PTS
[07:50] <Whoopie> albert23: it worked here.
[07:50] <amachu> madison is ok
[07:50] <geser> hendrixski: there is also rmadison (remote madison) in devscripts (gutsy) with which you can also check other releases and also Debian
[07:50] <amachu> Ubuntu/Debian PTS?
[07:51] <bluekuja> amachu: packaging tracking system
[07:51] <bluekuja> amachu: so packages.u.c
[07:51] <bluekuja> or packages.d.o
[07:51] <amachu> ok
[07:51] <geser> pts is pacakges.qa.d.o
[07:52] <geser> http://packages.qa.debian.org
[07:52] <pkern> deitarion: 1G? I expect it to grow as you install dev packages. 256M minimal I guess.
[07:52] <bluekuja> geser: yeah but generally packages.d.o
[07:52] <amachu> bluekuja: then
[07:52] <pkern> deitarion: Install debootstrap, that's in Gentoo.
[07:52] <amachu> i have make a ubuntu package right?
[07:52] <bluekuja> amachu: then you should apply what you've learnt on all the guides you told me before
[07:52] <pkern> deitarion: Or maybe fetch it from archive.ubuntu.com, because gutsy scripts are included.
[07:52] <bluekuja> amachu: and if you find something not clear, you ask me
[07:52] <deitarion> pkern: Sounds like I'll just do that then. My root drive (as opposed to my media drive) has around 340GiB free at the moment.
[07:53] <bluekuja> amachu: we will try to improve the package step by step
[07:53] <amachu> yes
[07:53] <amachu> sure
[07:53] <bluekuja> amachu: but It would be nice to see what you can/cant do atm
[07:53] <albert23> Whoopie: no luck here, still hanging
[07:53] <amachu> i will find a source then
[07:53] <amachu> :-)
[07:53] <amachu> atm?
[07:53] <bluekuja> amachu: at the moment
[07:53] <bluekuja> :)
[07:53] <Whoopie> albert23: really? press the sequence once more.
[07:53] <bluekuja> amachu: sorry for using this abbreviations
[07:53] <amachu> :-)
[07:54] <amachu> no problems
[07:54] <bluekuja> *these
[07:54] <bluekuja> amachu: I'm here for anything, so feel free to ping me
[07:54] <amachu> yes
[07:54] <albert23> Whoopie: I need to use fn to get sysrq, but  that also makes the k into a 2. Could that be the problem?
[07:54] <amachu> thank you
[07:54] <bluekuja> amachu: I'm your mentor now, so I'm glad to help you
[07:55] <Whoopie> albert23: here, it's "shift+print+alt+k"
[07:55] <bluekuja> amachu: and I'll work with until I see your application sent to the MC
[07:55] <bluekuja> amachu: MC = MOTU Council
[07:55] <bluekuja> *you
[07:55] <amachu> ok
[07:55] <amachu> :-)
[07:56] <bluekuja> amachu: good search for now
[07:56] <bluekuja> :)
[07:56] <amachu> doing that
[07:57] <albert23> Whoopie: doesn't work either.
[07:58] <Whoopie> albert23: sh*
[08:01] <Whoopie> albert23: tested again. works here. I think, you should check if the sequence is correctly recognized.
[08:04] <albert23> Whoopie: tried another time, no luck again
[08:09] <amachu> bluekuja: icewesel??
[08:10] <bluekuja> amachu: already in debian
[08:11] <amachu> ok
[08:19] <amachu> bluekuja: there is a this http://www.nsc.res.in/~elab/phoenix/software/index.html
[08:19] <amachu> which we demonstrated recently
[08:20] <amachu> i will check it out with a friend of mine
[08:20] <amachu> that would also help ubuntu pushing into few colleges
[08:20] <amachu> here
[08:20] <bluekuja> amachu: it's just one file?
[08:21] <bluekuja> http://www.nsc.res.in/~elab/phoenix/applications/croplus.py
[08:22] <amachu> i need to check it out
[08:22] <amachu> will get back to you on that
[08:22] <Whoopie> albert23: sorry, I did what I could. But now, someone with more knowledge about usplash has to look into it.
[08:22] <bluekuja> amachu: perfect :)
[08:23] <bluekuja> amachu: I would suggest you to start with an easy package
[08:23] <bluekuja> amachu: python uses a different policy
[08:23] <bluekuja> amachu: and I want you to learn basic packaging before moving to python/library packaging
[08:23] <amachu> oh.. ok
[08:25] <albert23> Whoopie: Just tried in xkeycaps. The FN key indeed turns the K into a 2
[08:26] <Whoopie> albert23: but why do you need Fn for sysrq? never saw such a keyboard layout.
[08:27] <albert23> Whoopie: it's a laptop. So FN+K is keypad 2
[08:27] <albert23> But xkeycap learned me how to do it :-)
[08:42] <sladen> Whoopie: what are you running, xubuntu, edubuntu, kubuntu, gobuntu, ubuntu ?
[08:42] <sladen> Whoopie: do you see the problem
[08:42] <sladen> Whoopie: assuming you're talking about off-centerness
[08:47] <amachu> bluekuja: fontforge is there, but fontutils?
[08:47] <amachu> will that help..
[08:48] <bluekuja> amachu: fontutils for fontforge?
[08:48] <bluekuja> upstream link?
[08:49] <amachu> http://directory.fsf.org/project/fontutils/
[08:53] <amachu> bluekuja: this should be useful, http://directory.fsf.org/project/html2pdf/
[08:54] <amachu> ?
[08:56] <bluekuja> amachu: html2pdf is not in debian or ubuntu? checked already?
[08:56] <bluekuja> amachu: if not, is there an ITP around inside debian BTS?
[08:58] <amachu> i checked once
[08:58] <amachu> let me confirm in few min
[09:03] <amachu> hey.. html2ps is there
[09:03] <amachu> but bot html2pdf
[09:03] <amachu> * not
[09:07] <geser> doko: have you an idea how to solve bug #145561? it looks like gpc-4.1 computes the gcc-4.1 dependency based on the own package version
[09:07] <ubotu> Launchpad bug 145561 in gpc-4.1 "[UNMETDEPS]  gpc-4.1 has unmet dependencies" [Undecided,Confirmed]  https://launchpad.net/bugs/145561
[09:40] <Whoopie> sladen: I was talking about uswsusp + usplash. I re-added usplash support to it. see bug 109151
[09:40] <ubotu> Launchpad bug 109151 in uswsusp "no hibernate with uswsusp installed" [Undecided,Confirmed]  https://launchpad.net/bugs/109151
[09:50] <albert23> Whoopie: alt+sysrq+k works for me to get past 100%, but it starts a new session, not the old one
[10:14] <homanj> when is the MOTU Q and A
[10:14] <homanj> some time tomorrow right?
[10:15] <jpatrick> 17th
[10:21] <mdomsch> #151664
[10:21] <geser> homanj: Friday, October 12th, at 14:30 UTC in #ubuntu-classroom
[10:22] <geser> bug #151664
[10:22] <ubotu> Bug 151664 on http://launchpad.net/bugs/151664 is private
[10:22] <mdomsch> doh
[10:22] <homanj> geser: thanks. that's what i thought.
[10:22] <mdomsch> fixed
[10:22] <mdomsch> bug #151664
[10:22] <ubotu> Launchpad bug 151664 in dell "DKMS 2.0.17.4 uninstalls wrong file" [Medium,Confirmed]  https://launchpad.net/bugs/151664
[11:10] <geser> pochu: there aren't many core-devs in #ubuntu-motu. try #ubuntu-devel
[11:10] <pochu> geser: already tried :(
[11:11] <geser> pochu: I guess they are all busy with the rc
[11:12] <pochu> geser: if you were core... :)
[11:12] <norsetto> pochu: wait few weeks ....
[11:13] <geser> norsetto: what is in a few weeks?
[11:14] <tonyyarusso> Thanksgiving!
[11:14] <tonyyarusso> Or, you know, UDS.
[11:14] <norsetto> geser: oh, you mean you have not yet applied? What you waiting for!?
[11:15] <geser> no, as I don't work much on packages in main
[11:22] <calc> ah pochu needs a core-dev
[11:22] <calc> pochu: whats up?
[11:23] <pochu> calc: I need a sponsor for liferea: http://emilio.pozuelo.org/~deb/liferea_1.4.4-0ubuntu2.dsc :)
[11:23] <pochu> calc: slangasek approved it (in #ubuntu-devel).
[11:24] <Kmos> pochu: why not release 1.4.5 ?
[11:24] <calc> pochu: ok i'll double check with slangasek and then upload it for you
[11:24] <pochu> calc: great, thanks a lot.
[11:25] <pochu> Kmos: because we are *too* close to release, and then we only take bug fixes we care about.
[11:26] <Kmos> pochu: ok
[11:28] <Kmos> pochu:
[11:28] <Kmos> Version 1.4.5b (Stable)
[11:28] <Kmos>         * Fixing wrong deallocation that prevents Liferea
[11:28] <Kmos>           from working with sqlite 3.5.x (SF #1811055).
[11:28] <Kmos> :)
[11:29] <pochu> Kmos: we don't have 3.5.x ;)
[11:30] <Kmos> pochu: so don't need it :)
[11:31] <pkern> Does anyone know by chance how to parse an in-memory string with librdf?
[11:31] <pkern> (Python that is.)
[11:33] <pkern> Ups... the c.perform() got thrashed. Ignore me. ;)
[11:50] <calc> pochu: uploaded
[11:50] <calc>   liferea_1.4.4-0ubuntu2_source.changes: done.
[11:54] <pkern> The LP rdf sucks?
[11:54] <hendrixski> would anyone recommend a better chroot manual than this: http://doc.ubuntu.com/ubuntu/packagingguide/C/appendix-chroot.html  ??
[11:54] <hendrixski> I was hoping to try out schroot, but can't find anything well written about it
[11:55] <hendrixski> and... also multiple chroots, but there's nothing in there about how to do that.  If you know of one, that does I'd be happy to read it. :-)
[11:55] <bddebian> Later folks
[11:55] <pochu> see you bddebian
[11:56] <pkern> siretart: LP RDF sucks. No foaf:nick in team RDF.
[12:04] <norsetto> hendrixski: https://wiki.ubuntu.com/DebootstrapChroot
[12:06] <hendrixski> norsetto, nice.
[12:06] <norsetto> hendrixski: it was pretty helpful for me
[12:07] <hendrixski> hhmm, it has both dchroot and schroot instruction on there
[12:07] <imbrandon> pkern: i asked for that feature and even filed a bug about it long long ago
[12:07] <norsetto> hendrixski: forget dchroot
[12:07] <hendrixski> norsetto, did you do the stuff in  the "Setting up a dchroot (non-root) environment" as well?
[12:07] <norsetto> hendrixski: no, I just setup an lpia chroot
[12:08] <hendrixski> ah,
[12:08] <imbrandon> pkern: when i was working on the ssh key sync script
[12:08] <hendrixski> coolness
[12:08] <pkern> imbrandon: Someone should beat them.
[12:08] <pkern> imbrandon: Same here.
[12:08] <hendrixski> thanks again... that's twice in one day.
[12:08] <imbrandon> pkern: ssh sync script?
[12:08] <imbrandon> *key
[12:08] <pkern> imbrandon: User syncing first, but in the end, yes.
[12:08] <norsetto> hendrixski: he, in my home country we say: there is no two without three .....
[12:09] <imbrandon> pkern: we did this many months ago and released it gpl2 ( we as in me and ajmitch  and fujitsu ) if you want i'll dig up a copy
[12:09] <pkern> norsetto: What's that in your native language?
[12:09] <imbrandon> all you need to do is change the team
[12:09] <hendrixski> norsetto, careful, I may just have a third thing I'll ask you today :-p
[12:09] <norsetto> pkern: music :-)
[12:09] <pkern> imbrandon: Language?
[12:09] <Simon80> can someone please please please fix bug 123185 before gutsy comes out? it's just a merge of bochsbios from debian that is needed
[12:09] <imbrandon> python
[12:09] <ubotu> Launchpad bug 123185 in bochs "bochsbios too old for Windows XP with qemu" [Medium,Confirmed]  https://launchpad.net/bugs/123185
[12:10] <pkern> imbrandon: Well the concept is to use nss bdb.
[12:10] <imbrandon> nss bdb ?
[12:10] <pkern> imbrandon: libnss-db
[12:10] <pkern> imbrandon: For passwd/shadow/groups.
[12:10] <norsetto> hendrixski: not today, I'm off to bed in 5 min
[12:10] <pkern> norsetto: No, the phrase.
[12:11] <pkern> Non c' duo...
[12:11] <norsetto> pker: non c' due senza tre ?
[12:11] <pkern> senze tre?
[12:11] <pkern> Fun.
[12:11] <norsetto> pkern: eh, almost perfect :-)
[12:11] <pkern> *senza of course
[12:11] <imbrandon> pkern: ahh well this may help you with some of the screen scraping anyhow
[12:11] <pkern> norsetto: Got rid of Italian after three years of studying it. ;)
[12:11] <imbrandon> one sec
[12:12] <norsetto> pkern: too bad, you must have been a promising student
[12:12] <pkern> norsetto: Nope. It was the language I was worst in.
[12:12] <pkern> ;)
[12:12] <pkern> Mainly lack of study, though.
[12:12] <pkern> French and English left. :-P
[12:12] <Simon80> anyone hear my nagging?
[12:12] <Simon80> windows XP in qemu is broken on gutsy and all it takes is a simple merge to fix it
[12:13] <Simon80> all I want is for one developer to get that done, because I can't
[12:13] <pkern> "a simple merge"?
[12:13] <imbrandon> pkern: http://www.imbrandon.com/misc/lpusers.py.txt
[12:13] <Simon80> a merge of bochbios from debian with no changes
[12:13] <hendrixski> Simon80, are you sure it's only broken in qemu?  I heard it was broken on its own
[12:14] <pkern> Now merge's aren't "simple". Just applying patches is.
[12:14] <mdomsch> ScottK, re bug 151664, as I'm upstream for the package, I just fixed it in upstream and dropped a new upstream version
[12:14] <ubotu> Launchpad bug 151664 in dell "DKMS 2.0.17.4 uninstalls wrong file" [Medium,Confirmed]  https://launchpad.net/bugs/151664
[12:14] <pkern> imbrandon: Screen scraping is baaaad. Thanks, though.
[12:14] <Simon80> it's not even a merge, actually, it's a sync
[12:14] <Simon80> I didn't think about it :(
[12:14] <broonie> g
[12:15] <imbrandon> pkern: that was the LP devs only sugestion untill they fixed it
[12:15] <mdomsch> I could apply the same patch to the older version with a new 0ubuntu2 release I suppose
[12:15] <sistpoty> hi folks
[12:15] <imbrandon> pkern: that was over 6 months ago
[12:15] <imbrandon> heya sistpoty
[12:15] <sistpoty> hi imbrandon
[12:15] <pkern> Now I slowly get to understand ScottK on how LP could disappoint oneself.
[12:15] <imbrandon> ;)
[12:15] <pkern> It's one point not to provide a XMLRPC/SOAP API, but not to act on such simple requests.
[12:16] <Simon80> and hendrixski: with stock gutsy, qemu hangs on boot of windows XP.  After installing a slightly newer version of bochsbios from debian, things work the way they do in feisty, which is fine
[12:16] <sistpoty> just a stupid question: what do I need to do to get an upload shoved through the queue? There is no "distro manager" team in LP, as the mail that I got states :P *g*
[12:16] <persia> sistpoty: release-manager team?
[12:16] <pkern> sistpoty: Wait.
[12:17] <sistpoty> persia: no, it said "This upload awaits approval by a distro manager" ;)
[12:17] <Simon80> from bochbios 2.3-2 to 2.3+20070705-2, that's all that needs to be synced to fix this bug
[12:17] <pkern> sistpoty: Which are the archive admins in fact.
[12:17] <imbrandon> sistpoty: i would bug the RM
[12:17] <Simon80> hence my nagging and whining in here
[12:17] <hendrixski> Simon80, i was just trying to lighten the mood with a joke
[12:17] <persia> sistpoty: I'm fairly sure that's https://launchpad.net/~ubuntu-release
[12:17] <Simon80> ah :(
[12:18] <sistpoty> ok, maybe I'm lucky (but I don't think though, due to the release being just out *g*)
[12:18] <Simon80> lol
[12:18] <pkern> sistpoty: If it needs fasttracking maybe ask slangasek.
[12:18] <pkern> sistpoty: Otherwise I'd guess that it will be processed if it's universe.
[12:18] <sistpoty> well, it doesn't really need fast tracking, but I wouldn't want to get it lost in a queue until release though ;)
[12:19] <pkern> sistpoty: All my uploads were processed within some hours.
[12:19] <pkern> ScottK: ping (firehol)
[12:19] <sistpoty> persia: not too sure, I thought Hobbsee couldn't shove things through the queue
[12:19] <slangasek> don't worry, that queue will be empty before release, one way or another ;)
[12:19] <sistpoty> slangasek: cool, thanks! then I'll just go to bed and worry no longer :)
[12:20] <slangasek> (which package, OOI?)
[12:20] <sistpoty> slangasek: haskell-haskell-src
[12:21] <slangasek> ok
[12:21] <sistpoty> thx!
[12:21] <slangasek> bit of a wait then, lots of packages ahead in the queue :)
[12:22] <sistpoty> hehe, in a week is still acceptable for me :P
[12:22] <imbrandon> sistpoty: too much debian in your blood ;)
[12:23] <sistpoty> imbrandon: haha, maybe just too much work and too few spare time to actually *do* an upload
[12:23] <imbrandon> :)
[12:23] <imbrandon> i know i've had a new apt-mirror sitting on my hdd for a week and not uploaded it
[12:23] <imbrandon> lol
[12:24] <persia> Simon80: regarding bochs: whining and nagging here won't help.  Currently, there doesn't appear to be a plan to pull the new bochs.  The process is to follow https://wiki.ubuntu.com/FreezeExceptionProcess#head-1d28045481b8803d4815989e93edc4206f4848c4 to request a newer version (basically a lot of administrative work).  This can then be reviewed for inclusion.  Personally, I suspect that it will take a persuasive arguments to demonstrate that an C
[12:24] <sistpoty> well, I guess this was upload #3 or s.th. for the entire gutsy cycle from me *g*
[12:24] <sistpoty> only writing mails asking questions for MC otherwise *g*
[12:25] <sistpoty> ok, gotta go to bed now, otherwise I'll be late at work tomorrow
[12:25] <sistpoty> gn8 everyone
[12:26] <imbrandon> gnight
[12:27] <norsetto> gnight imbrandon, gnight all
[12:29] <hendrixski> hhhmmm, sooo schroot can only create chroots using the scripts it has?  'cause it's not letting me create a gutsy schroot :-(
[12:30] <persia> hendrixski: Can you make a gutsy chroot with debootstrap?
[12:30] <imbrandon> pkern: https://bugs.edge.launchpad.net/launchpad/+bug/100079
[12:30] <slangasek> schroot doesn't normally create the chroots afaik
[12:30] <ubotu> Launchpad bug 100079 in launchpad "more rdf team info" [Undecided,New] 
[12:31] <imbrandon> found the bug i mentioned about the faof
[12:31] <hendrixski> persia, I thought it does
[12:31] <persia> slangasek: There's a schroot setup script from Kees on the wiki page about schroot that is being used for that.
[12:32] <keescook> it's part of the ubuntu-dev-tools (mk-sbuild-lv)
[12:32] <hendrixski> persia,  I'm following this.... https://wiki.ubuntu.com/DebootstrapChroot  I replaced breezy with gutsy, and it's didn't do anything :-(
[12:32] <keescook> it does depend on having LVM set upt.
[12:32] <keescook> *up
[12:32] <persia> hendrixski: Use the distributed script rather than the wiki script.  Perhaps something changed.
[12:32] <pkern> imbrandon: Your report is mainly about ssh public key inlining, which I don't need.
[12:33] <hendrixski> persia, which one is the distributed script?
[12:33] <pkern> Or which is superfluous and (if that's true) non-standard.
[12:33] <imbrandon> pkern: yea that was what come of the faof disscussion though
[12:33] <persia> hendrixski: aptitude install ubuntu-dev-tools
[12:33] <hendrixski> ah
[12:34] <imbrandon> pkern: and also the addition of faof:nick as with the indvidual rdf for each member ( so a LP url can be constructed )
[12:34] <imbrandon> ( from the desc )
[12:35] <hendrixski> persia, sorry to be such a noob, I'm not finding ubuntu-dev-tools
[12:35] <persia> hendrixski: That wiki page seems a little old :)  To test debootstrap alone, I usually just make a directory, and run `debootstrap (release codename)` in that directory.
[12:35] <persia> hendrixski: You're using 6.10 then :)
[12:37] <hendrixski> persia, I'm on feisty... 7.04
[12:37] <persia> hendrixski: Try https://help.ubuntu.com/community/SbuildLVMHowto.  You can use the schroots with `schroot -c $name`, and not bother with the sbuild bit, if you like.
[12:37] <persia> hendrixski: My apologies.  I thought there was an ubuntu-dev-tools for 7.04, but I could well be mistaken.