2008/06/10/#ubuntu-motu.txt

[00:59] <kirkland> can someone point me to the appropriate wiki page describing how to promote a package from universe to main?
[01:02] <ajmitch> kirkland: https://wiki.ubuntu.com/MainInclusionProcess
[01:02] <kirkland> ajmitch: awesome, thanks.  i was looking under MOTU/* ....
[01:04] <leleobhz> someone can help-me to solve this: E: uniconvertor_1.1.2-0ubuntu3_i386.changes: checksum-mismatch-in-changes-file md5 uniconvertor_1.1.2-0ubuntu3.dsc
=== daniel1 is now known as danielm
[01:24] <persia> mouz: If the fix is done upstream, it's good to try to make sure it's in intrepid and close the intrepid task as "Fix Released" to encourage approval of your SRU candidate.
[01:29] <kirkland> kees: hey, i'm starting the MainInclusionReport for ecryptfs-utils
[01:29] <kirkland> kees: it only has one dependency not already in main...  libpkcs11-helper1 (source: pkcs11-helper)
[01:30] <kees> all build-deps will need an MIR too
[01:30] <kirkland> kees: does that mean 2 separate MIR's?  one for ecryptfs-utils and one for  pkcs11-helper?
[01:30] <kirkland> kees: ah, okay
[01:30] <kees> I think so, yeah.  and check all of pkcs11-helper's deps too
[01:52] <kirkland> kees: i guess the other obvious alternative is to try and remove the dependencies
[01:57] <persia> kirkland: Please try to include them instead.  We've enough packages that get bug reports about things being disabled in an attempt to fit them in an MIR.  On the other hand, if it doesn't turn off functionality...
[01:57] <kirkland> persia: interesting, is that a general consensus among MOTU?
[01:58] <persia> kirkland: I'm not sure, although I think it ought be :)
[01:58] <ajmitch> kirkland: people often expect features to be enabled if possible, I don't think it's a consensus, but something that comes through from bugs
[01:58] <persia> There's a bit of balance involved: anything getting MIR restricts upload access from MOTU, so all MIR are annoying to some degree.
[01:59] <persia> On the other hand, turning features off to wedge something into main annoys users, and MOTU often review the bug reports.
[02:00] <kirkland> thanks
[02:00] <ajmitch> it probably won't be too hard to get MIR approval for both packages
[02:43] <danielm> hi all
[02:43] <danielm> why lintian warnings:  native-package-with-dash-version
[02:44] <danielm> i can't use '-'? :|
[02:44] <persia> danielm: Typically that means you forgot to include the orig.tar.gz in the parent directory.
[02:45] <danielm> oh! that is!
[02:45] <danielm> thanks :)
=== asac_ is now known as asac
[03:41] <ScottK> kirkland: In some cases I've split packages into two source packages to get something into Main without losing functionality (see amavisd-new and amavisd-new-milter for an example)
[03:42] <kirkland> ScottK: good pointer, thanks
[03:42] <nxvl> kirkland: but we need to split them?
[03:42] <nxvl> or at least, we can?
[03:44] <kirkland> nxvl: i'd think we should save that as an alternative
[03:44] <kirkland> nxvl: let's first try to get all 3 included
[03:44] <kirkland> nxvl: if we run into problems, we can try ScottK's suggestion
[03:45] <ScottK> JFTR, it was an observation, not a recommendation.  I have no idea what you are actually trying to do right now.  It should be kind of a last resort.
[03:45] <kirkland> ScottK: understood, agreed
[03:46] <nxvl> ScottK: yes, thanks, i was just making sure we can split it
[03:55] <slangasek> right, amavisd-new-milter is a case where splitting is the only real option for main inclusion, since "milter" implies duplication of MTAs in main :)
[03:56] <slangasek> whereas kirkland's packages don't appear to be duplicating functionality
[03:57] <persia> slangasek: Is duplication-in-main bad?  Should those cases where it is present result in demotion requests?
[03:58] <slangasek> persia: it's a consideration for main promotion, since it increases the security support burden; and where MTAs are concerned, I don't see anyone wanting to support both postfix and sendmail... :)
[03:58] <lifeless> slangasek: exim4!
[03:59] <slangasek> maybe the proposed archive reorg will make this less of a consideration
[03:59] <StevenK> slangasek: I've been told by pitti that sendmail has zero chance of hitting mail.
[03:59] <persia> slangasek: In the specific case of MTAs, I suspect I agree (then again, I believe all sendmail competitors were written by people who didn't understand sendmail.cf)
[03:59] <StevenK> Sigh, main
[03:59] <slangasek> Zugschlus: oh hai, I didn't see you hiding there behind lifeless's nick
[03:59] <StevenK> Haha
[03:59] <lifeless> slangasek: ><
[03:59] <slangasek> :-)
[03:59] <StevenK> lifeless: You asked for that. :-P
[04:00] <slangasek> hmm, exim4 is /already/ in main?  how curious :)
[04:01] <persia> In that case, the existence of amavisd-new-milter is even more confusing.
[04:01] <lifeless> StevenK: given exim4 is in main, I don't think I did. Also it is good.
[04:01] <slangasek> persia: augh slippery slope
[04:01]  * persia anxiously awaits archive-reorg AKA nothing-in-main
[04:01] <slangasek> :)
[04:01] <StevenK> I don't really want to enter into an MTA flamewar, but I don't like exim.
[04:02] <lifeless> StevenK: fair enough. Each to their own I say, as long as its not qmail or sendmail.
[04:02] <StevenK> lifeless: We can at least agree on that. :-)
[04:03] <StevenK> I used to like exim. $OLD_WORK beat that out of me.
[04:03] <persia> The problem with MTAs is that none is perfect, so working for a while with any both makes the MTA one works with bad, and all the others confusing.
[04:34] <ScottK> persia: I'm pretty certain Weiste Venema understands Sendmail.cf.  Of course he's probably also the only developer of a Sendmail competitor to get a Sendmail developers' award.
[04:36] <StevenK> Ha. I like that.
[04:37] <StevenK> I'm also amused that Postfix supports milters.
[04:38] <ScottK> That's what he got the award for.
[04:38] <ScottK> A kind sole who knows a little about init scripts might want to have a look at Bug #238744 and see if they can figure out how to help the reporter out.
[04:38] <ubottu> Launchpad bug 238744 in havp "package havp 0.86-1 failed to install/upgrade: El paquete est? en un estado muy malo e inconsistente - debe reinstalarlo" [Undecided,Confirmed] https://launchpad.net/bugs/238744
[04:40] <persia> ScottK: Right.  Does he like sendmail.cf?
[04:40] <ScottK> persia: No.  That's part of why he wrote Postfix.
[04:41] <persia> ScottK: It seems to be the common excuse for not using sendmail.
[04:42] <ScottK> excuse/reason, yes.
[04:43]  * persia puts the "Sendmail is the best MTA ever" placard back in the back of the closet, to again accumulate dust
[04:45] <emgent> hello
[04:48] <LucidFox> Are all KDE4 dependent builds broken now, or am I just missing something?
[04:48] <LucidFox>   kdelibs5-dev: Depends: kdelibs5 (= 4:4.0.80-0ubuntu5) but it is not going to be installed
[04:49] <persia> LucidFox: There was an issue with half-in-main at one point: you might ask in #kubuntu-devel to see if it has been sorted (unless someone else answers here)
[04:49] <LucidFox> thanks
[04:52] <ScottK> It's not totally sorted
[04:52] <ScottK> Progress has been made.
[04:53] <RAOF> Omega[1];
[04:54] <RAOF> Ahem.  #ubuntu-motu != maple
[04:57] <ScottK> persia: You get pitti to agree to MIR Sendmail and then we can unsplit the package.
[04:58] <ScottK> I could see some utility in splitting libmilter out into it's own source and getting that in Main so we can have supported milters for Postfix, but beyond that, I don't think so.
[05:00] <persia> ScottK: I may be insane, but I'm not quite that masochistic.
[05:01] <ScottK> Thus the existence of a separate amavisd-new-milter source package in Universe.
[05:04] <ajmitch> sendmail in main? I think there'd be a few tears over that one
[05:07] <StevenK> A few?
[06:49] <pwnguin> do i need to manually file a sync request at this point or does launchpad or whatever Debian sync stuff keep track of changes in unstable?
[06:50] <RAOF> It's autosync at this point.
[06:51] <pwnguin> so if i saw a new upload in debian today via rss its in some build queue already?
[06:52] <persia> pwnguin: Mind you, you will need to file a sync if there was previously variation in Ubuntu, and such variation is no longer required.
[06:52] <persia> The autosync script is run manually, generally two or three times a week.
[06:56] <dholbach> good morning
=== _ruben__ is now known as _ruben
[08:09] <\sh> moins
=== mneptok_ is now known as mneptok
[08:34] <pwnguin> persia: i dont follow. if there was ever an -ubuntuX version autosync wont work?
[08:34] <pwnguin> or just in the "looks like a merge" case?
[08:35] <pwnguin> probably the latter.
[08:36] <persia> pwnguin: autosync won't automatically overwrite: it becomes a merge candidate.  Once the package is back in sync, all history of *ubuntuX is lost (changelog is in sync), so there was never an *ubuntuX version.
[08:37] <pwnguin> ok
[08:37] <pwnguin> makes sense
[08:37] <pwnguin> the former would be stupid ;)
[08:38] <pwnguin> at any rate, the package I'm after should take care of itself then
[08:39] <persia> Yeah, although I remember one case where Debian sync'd from Ubuntu (including changelog), and it became a merge candidate.  I think that's fixed now.
[08:39] <pwnguin> im sure thats happened
[08:40] <persia> Less often then you'd think.  Most of the Ubuntu people who are also Debian people are good about the changelog, and most Debian maintainers are careful enough with their package to keep the changelog clean.
[08:40] <pwnguin> im just saying it's probably happened once, given the number of new package requests motu sees
[08:40] <persia> I think most of the occurrences were around the introduction of the Ubuntu patch to packages.qa.debian.org
[08:41] <pwnguin> huh
[08:41] <persia> Well, the ftp-masters are good at catching that.  We've had a lot of packages in Ubuntu and then in Debian, but usually they are changelog-clean by the time they arrive.
[08:42] <pwnguin> ah. hurray for oversight
[08:42] <pwnguin> <-- not a DD
[08:42] <persia> That's one of the reasons that those who want long-term credit for packaging something new are encouraged to get it into Debian, so their entry in debian/copyright doesn't get overridden.
[08:42] <pwnguin> wa?
[08:43] <persia> OK.  So Alice packages libfoo for Ubuntu, and puts "This package was debianised by Alice" in debian/copyright.
[08:43] <pwnguin> sure
[08:43] <persia> Later Bob packages libfoo for Debian, and puts "This package was debianised by Bob" in debian/copyright.
[08:43] <persia> After this, Chris reviews the merge candidate, and requests a sync.
[08:43] <pwnguin> and then a dd fulfills a ITP without looking?
[08:44] <pwnguin> yea
[08:44] <persia> So Dana, an archive admin, does the sync, and overwrites Alice's credit.
[08:44] <pwnguin> so basically, duplication of effort, not spurious deletions of debian/copyright filse
[08:44] <pwnguin> files
[08:44] <persia> pwnguin: Well, it's more common when someone puts something into REVU, and doesn't file an ITP (or at least an RFP with a pointer at the Ubuntu package).
[08:45] <persia> pwnguin: Right.  Overwriting debian/copyright due to duplication of effort.
[08:45] <persia> Debian always wins.  Ubuntu follows that policy in large part because it encourages collaboration.
[08:45] <pwnguin> heh
[08:45] <pwnguin> im reminded of a paper i read yesterday
[08:46] <pwnguin> if you want to "win" an stop sign intersection, dont make eye contact with the driver coming from the right
[08:47] <pwnguin> "in fact, he argues the strongest move one can make is to throw the steering wheel out the door!"
[08:47]  * persia suspects that advice doesn't work here, where left-on-red is generally considered OK
[08:47] <StevenK> Only if he is a worse "Chicken" player than you are.
[08:47] <StevenK> Left turn on red here is okay if the intersection is signed for it
[08:47] <pwnguin> left on red?
[08:47] <pwnguin> you're nuts
[08:48] <pwnguin> or drive backwards
[08:48] <StevenK> We drive on the left hand side here
[08:48] <persia> pwnguin: No, we drive normally.  Two to one.
[08:48] <persia> (disclaimer: I no longer drive)
[08:48] <pwnguin> seriously
[08:48] <StevenK> Left is right. :-P
[08:48] <pwnguin> why am i the only guy who stays up late?
[08:49] <pwnguin> anyways, debian never had a steering wheel
[08:50] <pwnguin> also, the allegory is a 4 way stop with two drivers going straight
[08:51] <persia> Right.  Just keep going.  If the other driver also follows this rule, accellerate
[08:51] <pwnguin> basically, by pretending to ignore the other guy, he as to assume you dont see him and so on to "win"
[08:51] <pwnguin> persia: you seem like a natural at this ;)
[08:51] <persia> see previous point about me and driving.
[08:51] <StevenK> Note to self: Never drive with persia
[08:51] <persia> StevenK: Driving with me these days is safe: I generally hire a professional.
[08:52] <StevenK> If you calling a taxi driver a professional, I suggest you inspect the taxi drivers in Sydney and New York
[08:52] <pwnguin> hah
[08:53] <persia> pwnguin: The fault in the analogy is that Debian doesn't turn a blind eye (and never really has to Ubuntu, as opposed to the many other derivatives).  Allowing Debian overwrite is Ubuntu driven, to the frustration of some people in Debian who would prefer Ubuntu overwrite for new packages.
[08:53] <pwnguin> never get in a car with a driver behind the wheel who came to america thinking "what's the worst that could happen"
[08:54] <persia> StevenK: In Sydney, I was unhappy, and generally tried to restrict travel to beween 4:00 and 7:00am, and look to a known safe driver in the evenings.  In New York, I take trains (although some of the limousine companies are acceptable)
[08:55] <persia> pwnguin: From that comment, I will take a stab at the nationstate in which you reside, and reference the intersection of Summer Street and Cutter Avenue in Somerville Massachusetts as proof that it's a rare place that completely prohibits left on red.
[08:56] <pwnguin> i recognise the word massachusetts
[08:56] <pwnguin> but ive never been there
[08:57] <pwnguin> america is bigger than new york, after all ;)
=== devfil_ is now known as devfil
[09:23] <tarzeau> when i try to import my pgp key it says: The key CC798E5CAF5268D858C506C27C8DFA5B0999548B has already been imported.
[09:23] <tarzeau> on launchpad.net
[09:23] <tarzeau> but i don't have the passwords of the other 3 accounts anymore
[09:24] <tarzeau> and launchpad.net can't send it to me either
[09:24] <tarzeau> what can i do about this?
[09:24] <persia> tarzeau: How did this happen?
[09:24] <tarzeau> persia: i don't have gurkan@linuks.mine.nu anymore
[09:24] <persia> Did you change your email address, and lost touch with the old ones?
[09:24] <tarzeau> persia: and i want to take the bugs/package assignments from that email address too, how to?
[09:24] <siretart> hi tarzeau
[09:24] <tarzeau> hey siretart
[09:24] <persia> OK.  Explain your situation to answers.launchpad.net/launchpad.
[09:25] <siretart> tarzeau: did you revoke your old userid on your key? and did you upload that key to 'keyring.ubuntu.com'?
[09:25] <persia> someone will likely ask for some proof of identiy, and help you.
[09:25] <tarzeau> siretart: no, would it then work?
[09:26] <tarzeau> siretart: i'm still speculating to get the name again and reactivate it
[09:26] <tarzeau> siretart: besides once revoked, i can't unrevoke it anymore so i want to keep it like this
[09:26] <siretart> tarzeau: well, if you lost access to that mail account, I'd consider it natural to express this in your public key
[09:26] <tarzeau> persia: what kind of proof of identity?
[09:26] <siretart> tarzeau: by signing that userid you are testifying having control over that email adress. which you don't.
[09:27] <persia> tarzeau: I don't know.  I've never done it myself.  I have heard of others who were able to sort out lost LP access.
[09:27] <persia> Also, you do want to update your GPG key to reflect your current email.  Anything else is incorrect.
[09:27] <tarzeau> persia: it is up to date
[09:27] <tarzeau> siretart: i just don't want to revoke an email address that i might use again
[09:27] <persia> tarzeau: Including the revocations for the addresses you no longer control?
[09:28] <tarzeau> persia: i will be in control again, it's just temporary
[09:28] <tarzeau> persia: would removing the ids work?
[09:28] <tarzeau> and then adding them again later?
[09:29] <persia> You can't remove.  You can only revoke.  I wouldn't revoke if you expect to add again later, unless there's a big gap of time in the middle.
[09:29] <tarzeau> persia: ok, that's what i do. but can i use the key on launchpad meanwhile?
[09:30] <persia> tarzeau: For that, try asking in #launchpad.
[09:30] <tarzeau> persia: i'm asking on the url you gave me
[09:32] <tarzeau> #35788 ...
[09:33] <siretart> tarzeau: think if you paste a clearsigned request to have your primary account address changed to some other adress you actually can read, that should do it
[09:33] <siretart> tarzeau: paste in a support ticket, that is
[09:33] <tarzeau> i can't merge the accounts either since the primaryily registered email doesn't work temporarily
[09:33] <tarzeau> siretart: the ticked i made is not a support ticket?
[09:33] <siretart> you change your primary account later again
[09:34] <siretart> tarzeau: ah, yes it is
[09:35] <siretart> still I think you want to have the primary contact adress changed by some admin. which ticket #35788 doesn't say
[09:35] <siretart> or forcemerge the other accounts
[09:35] <tarzeau> how?
[09:35] <tarzeau> siretart: i'll add that to the ticket
[09:36] <tarzeau> siretart: thanks, added
[09:37] <wgrant> Perhaps include a request to merge all of your accounts with your current one, signed with the OpenPGP key associated with those other accounts?
[09:37] <wgrant> That's probably the easiest way to do it.
[09:37] <tarzeau> wgrant: let me try that as well
[09:38] <freeflying> hi motu's, after the motu ship expired, the upload right also expired?
[09:38] <wgrant> freeflying: They are one and the same.
[09:38] <persia> freeflying: Yes, they are linked.
[09:38] <tarzeau> added
[09:39] <freeflying> persia: haha, I'd keep on re-applying those, like motu, official loco team :)
[09:39] <wgrant> tarzeau: It might have been better to give it an inline sig, but that works too.
[10:36] <Riddell> DktrKranz: ping
[10:36] <DktrKranz> Riddell: hi
[10:37] <Riddell> DktrKranz: oh, I see, never mind
[10:37] <Riddell> was looking at your rpy upload
[10:37] <DktrKranz> troubles?
[10:38] <Riddell> no, just my eyesight :)
[10:38] <DktrKranz> heh :)
[10:39] <DktrKranz> thanks for approving
[10:39] <Riddell> DktrKranz: poke me in a week to have them moved to -updates
[10:40] <DktrKranz> Riddell: sure. I'll do some verifications to see if everything is ok, just for being sure.
[10:41] <Riddell> DktrKranz: you should add the verification-needed tag
[10:41] <Riddell> and a TEST CASE: comment
[10:41] <Riddell> also motu-sru should have been subscribed
[10:46]  * persia notes that DktrKranz is motu-sru
[10:48]  * DktrKranz should have added test case before :/
[10:48] <persia> And likely subscribed the rest of the team so it showed on http://qa.ubuntuwire.com/sru/
[10:51] <DktrKranz> I though I have subscribed motu-sru, probably it was a different bug
[11:21] <Riddell> siretart: ping
[11:22] <siretart> Riddell: I am not available. please leave a message after the beep. *BEEP*
[11:22] <Riddell> openal-soft is LGPL but the debian/copyright file says GPL
[11:25] <siretart> indeed, I need to fix this in debian as well, then.
[11:25] <Riddell> siretart: I'll reject then, poke me when you upload a fix
[11:25] <siretart> is this a reject reason? I thought it was possible to relicense lgpl code as gpl, since gpl is stricter than lgpl, isn't it?
[11:26] <Riddell> I can accept
[11:26] <Riddell> if you don't want to fix it
[11:26] <Riddell> seems untidy though
[11:26] <Riddell> or if you want to fix later
[11:26] <siretart> I will fix it in any case. I need to do additional uploads to start the openal transition anyways
[11:26] <siretart> so accepting it will allow us to start the transition earlier
[11:27] <Riddell> ok, I'll accept
[11:27] <siretart> thanks!
[11:28] <norsetto> Hola
[11:30] <Riddell> ciao norsetto
[11:30] <norsetto> Riddell: ciao there :-)
[11:31] <Riddell> siretart: what's the relationship between openal and openal-soft?
[11:32] <Riddell> siretart: and presumably libopenal1 should go to main?
[11:32] <siretart> Riddell: executive summary: openal is deprecated and we want to replace it with openal-soft. do you want more details?
[11:33] <Riddell> that's fine
[11:33] <siretart> so yes, as long as we don't want to demote dependencies along with openal, it needs to go to main
[11:34] <siretart> however I don't really feel that comfortable having openal in main. I mean, code wise. for openal-soft, I don't have enough experience with it to make that assesment. But my experience with openal is very mixed
[11:36] <Riddell> I'm not sure what's keeping it in main
[11:41] <Riddell> hmm, rss-glx is
[11:46] <sistpoty|work> hi folks
=== cprov is now known as cprov-lunch
=== thekorn_ is now known as thekor
=== thekor is now known as thekorn
[12:27] <simplechat> heyyas
[12:27] <simplechat> how would i find the package before the current released package?
[12:27] <simplechat> there was a new version of fglrx which breaks horribly when actually in use
[12:28] <simplechat> is there an easy way to downgrade?
[12:28] <directhex> simplechat, launchpad.net usually contains things.
[12:28] <simplechat> directhex, as do most sets
[12:29] <simplechat> can i have a more specific direction?
[12:29] <simplechat> and will there be a correction?
[12:32] <simplechat> like, can i expect fglrx to unbreak on the next update?
[12:32] <simplechat> or will it just sit there for a couple of weeks?
[12:33] <directhex> https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+publishinghistory
[12:33] <directhex> and if there's a bug, file a bug
[12:33] <directhex> on a given version, click the version number, then "builds" on the left, click an architecture, "resulting binaries" on the left
[12:33] <directhex> packages!
[12:34] <simplechat> source packages?
[12:34] <directhex> those too, if you want
[12:36] <simplechat> no, as in, where are the .debs? i've found .targz's and diffs
[12:36] <simplechat> but not .debs
[12:36] <directhex> so... did you follow the instructions above?
[12:37] <directhex> the bit relating to "then "builds" on the left, click an architecture, "resulting binaries" on the left" for example
[12:50]  * dholbach hugs nixternal
[12:51] <simplechat> ...
[12:52] <simplechat> was the latest version the version that came out late last month from ati?
[12:53] <simplechat> directhex, https://launchpad.net/ubuntu/hardy/i386/xorg-driver-fglrx/1:7.1.0-8-3+2.6.24.11-12.31 that is what i need?
[12:54] <directhex> well, that and the kernel module to match
[12:54] <simplechat> kernel module?
[12:55] <simplechat> which one?
[12:56] <simplechat> https://launchpad.net/ubuntu/hardy/i386/fglrx-kernel-source/1:8-3+2.6.24.11-12.31 ?
[13:10] <saivann> If a MOTU have some time to review and accept a obvious patch for intrepid and hardy-proposed : bug 232402
[13:10] <ubottu> Launchpad bug 232402 in chmsee "chmsee does not build in Hardy" [Medium,In progress] https://launchpad.net/bugs/232402
[13:51] <askand> Hello, I need some hep writing a maininclusionreport :) The package is libiptcdata and the reason I want it to be in main is to fix bug 213367 . The first thing I wonder is what "Any source code review performed ?" means?
[13:51] <ubottu> Launchpad bug 213367 in gthumb "build gthumb with IPTC data support" [Undecided,Confirmed] https://launchpad.net/bugs/213367
[13:51] <Riddell> hmm, Daniel Hahler disappeared?
[13:54] <StevenK> askand: What that means is, "have you read through the source code, and looked to see if it is written in a security-conscience matter?"
[13:55] <white> StevenK: who cares about security? :)
[13:55] <white> as long as the app is fancy, it is alright ;)
[13:55]  * StevenK kicks white in his insecurity
[13:55] <white> hehe
[13:56] <askand> wow im not sure I am capable of seeing if it is "written in a security-conscience matter" really
[13:56] <StevenK> So the answer is no :-)
[13:59] <askand> Ah ok :) hm "Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ?" Since hte package is a library I guess that would be a no-answer on that too?
[14:00] <StevenK> I'm guessing since it adds metadata to a picture, it would be a yes
[14:01] <askand> Then I go with your guess
=== santiago-php is now known as santiago-ve
[14:14] <askand> How do I know if a package follows FHS and Debian Policy?
[14:14] <StevenK> You check both documents
[14:14] <persia> askand: You read both documents, and compare them against the package.
[14:14] <ogra> an duse lintian
[14:14] <ogra> *and use
[14:15] <ogra> it usually catches the worst parts
[14:16] <persia> Yes.  Lintian can help tell you if the answer is "No".  Being sure the answer is "Yes" requires more digging.
[14:17] <ogra> indeed, but its a good tool for measurement :)
[14:17] <persia> Yes :)
=== Czessi_ is now known as Czessi
=== jcfp` is now known as jcfp
=== broonie_ is now known as broonie
[15:15] <sebner> dholbach: I'll fight linkchecker but no in the next 2 weeks. I just dont have the time for it (final exams ..)
[15:15] <sebner> *not
[15:16] <dholbach> sebner: OK, np
[15:24] <gaspa> persia: i made a 'friendly' list of packages that depend on nbs (not totally, but working)
[15:24] <gaspa> DktrKranz tells me  you could be interested :)
[15:25] <gaspa> the list is here: http://iogaspa.altervista.org/nbs/reversenbs.xml
[15:26] <gaspa> persia: if you have comments, are appreciated. :)
=== ScottK-laptop is now known as ScottK2
[15:59] <neurobuntu> test
[15:59] <geser> failed
[16:00] <neurobuntu> dang, I was hoping it would pass
[16:09] <norsetto> saivann: your chances will be greater if you set the bug status to confirmed and assign it to nobody. For the sru, try also to provide the information required here: https://wiki.ubuntu.com/StableReleaseUpdates
[16:16] <saivann> norsetto : Thanks
[16:18] <norsetto> saivann: np, note as well that the version for -proposed should be something like 1.0.0-1ubuntu1.1 not 1.0.0-1ubuntu2
[16:18] <saivann> norsetto : Oh thanks, I'll fix this too!
=== greeneggsnospam is now known as jsgotangco
[17:13]  * sistpoty|work heads home now... cya
=== AsciiTXT is now known as marnold
=== santiago-php is now known as santiago-ve
=== nhandler_Merging is now known as nhandler
[17:47] <bluefoxicy> damnit
[17:47] <bluefoxicy> audacity crashes, just like it did when stupid backports sent it to 7.10
=== fta_ is now known as fta
[19:11] <Falken> Hi everyone
[19:11] <Falken> I just uploaded my very first package on REVU. It doesn't show up on http://revu.ubuntuwire.com .. what am I doing wrong ?
[19:18] <ScottK> Falken: How long ago did you upload it?
[19:20] <Falken> ScottK: about one hour ago
[19:20] <Falken> there is already a package with the same name which was uploaded 2 months ago by another person
[19:22] <Falken> but I don't know how it's supposed to work. Mine is up to date, should I do something to overwrite the old one ?
[19:23] <ScottK> It should just work.
[19:23] <ScottK> If someone else was working on the package already, have you checked with them to see if they are still interested?
[19:25] <Falken> yep, it's the upstream guy. we talked about it on launchpad
=== tb1 is now known as tbf
[19:26] <Falken> I followed the doc on https://wiki.ubuntu.com/MOTU/Packages/REVU
[19:27] <Falken> and dput told me it was successfully uploaded ...
[19:28] <Falken> this is my dput conf concerning revu :
[19:29] <Falken> fqdn = revu.tauware.de , incoming = /incoming , login = anonymous
[19:29] <Falken> and that's it
[19:32] <Falken> maybe I should ask the old package to be nuked
[19:33] <ScottK> It shouldn't be needed.
[19:49] <emgent> heya people
[19:57] <neurobuntu> persia: rare? almost all intersections in Somerville and Cambridge are no turn on red
[19:57] <neurobuntu> oops ignore that
=== DrKranz is now known as DktrKranz
[19:58] <DktrKranz> broonie, thanks for scons :)
=== radio|work` is now known as brandon|work
[20:20] <Falken> do you know if there is something like a refresh rate on REVU ? my package still doesn't show up. dput tells me it has already been uploaded when I try again
=== Pici` is now known as Pici
[20:22] <ScottK> You needs a REVU admin to look for you.
[20:22] <ScottK> RainCT: ^^^?
[20:27] <broonie> DktrKranz: np. It occurs to me that you might want to consider applying to become a DM.
[20:27] <Falken> thanks ScottK ;)
[20:28] <DktrKranz> broonie, still early, I need to have a DD to sign my GPG key and find advocates :)
[20:29] <broonie> I'll advocate you for SCons.
[20:30] <DktrKranz> cool :)
[20:30] <slangasek> "anything just so I never have to touch scons again"? :-)
[20:31] <DktrKranz> heh, I'll leave risk to you :)
[20:31] <broonie> slangasek: I didn't say that.
[20:32] <slangasek> broonie: sorry, I must be projecting. :)
[20:32] <broonie> slangasek: All I'm saying is that I didn't say it. :)
[20:37] <Cliph> Having a problem with a one of my meta dpkgs, is this a good place to get some help?
[20:37] <Cliph> I have output and pastebins ready
[20:38] <norsetto> !ask | Cliph
[20:38] <ubottu> Cliph: Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-)
[20:39] <Cliph> Hi, I'm building a meta-dpkg and it has a bunch of dependencies that are also available in my repository, when I try installing <my-meta-package> I get a message about some of my dependencies stating "Depends: <other dependency> but it is not going to be installed"  Here is a pastebin of the output and my control file: http://pastebin.com/d1efb6512 And here is a pastebin of apt-cache policy <my-meta-package>: http://pastebin.com/d7e10ae2b
[20:40] <RainCT> Falken: Do you still have a problem with REVU? (I was away).
[20:41] <Cliph> If this isn't the best place to get help with this issue please direct me to the right one. Thanks!
[20:49] <geser> Cliph: what happens when you try to install one the mentioned packages, e.g. jazinga-gui ?
[20:51] <Cliph> oh, I see
[20:51] <Cliph> gui depends on jami, depends on some other packages and so on up the tree
[20:51] <Cliph> lets see what I can do ...
[20:53] <Cliph> I see I see, the dependencies cascade and there's an unmet package deep down the dependency tree
[20:57] <Cliph> that was it, that helped me, thank you geser, there were dependency problems deeper down, now I know what that error message too. Thanks again for you help.
[21:11] <RainCT> Falken: your upload was rejected, probably because you aren't in the revu-contributors group or you joined it recently and you are not yet in the keyring (I can update it if you can confirm this)
[21:11] <RainCT> Falken: by the way, remove the "<nnnn is the bug number of your ITP>" from the changelog
[21:20] <i4x> ppl, I need to know if it's possible to build a package that run's a script while installing!!
[21:23] <i4x> I know a few things on how to build a package!.. but don't know how to build it to execute a script while installing!!
[21:24] <ScottK> There is preinst and postint.
[21:27] <mrjb> hi folks!
[21:28] <jussi01> Hi mrjb
[21:28] <mrjb> i was sent here from
[21:28] <jussi01> :)
[21:28] <mrjb> never mind ;)
[21:28] <jussi01> Lads and Ladies, mrjb is looking fo help packaging his program
[21:28] <mrjb> thanks for the intro :)
[21:29]  * norsetto sighs
[21:29] <mrjb> nors: tough day?
[21:30] <mrjb> the story is, i've made a piece of software that i'd like to share
[21:30] <i4x> ScottK: preinst and postint? if it is what I think... well, then I mean postint !! I want to run some things (like grant permissions) before installing files!!
[21:30] <mrjb> http://ringbreak.dnd.utwente.nl/~mrjb/hd24tools/
[21:31] <mrjb> i'd like to make it available on regular ubuntu/ubuntustudio repository
[21:31] <mrjb> but i've never built a .deb before
[21:32] <mrjb> i'm not at the point of asking for help doing the actual packaging yet, as first i'd like to try following this tutorial: http://ubuntuforums.org/showthread.php?t=51003
[21:32] <brandon|work> mrjb, have you read the wiki on packaging?
[21:32] <brandon|work> https://wiki.ubuntu.com/MOTU/GettingStarted
[21:33] <mrjb> for now I'll assume I can manage to package the software
[21:33] <mrjb> (thanks for the link by the way)
[21:33] <mrjb> after that, how would i go about having it included in the regular repositories?
[21:34] <norsetto> !revu | mrjb
[21:34] <ubottu> mrjb: REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU
[21:34] <Laney> There are a *lot* of packages on REVU atm :O!
[21:35] <mrjb> ok, i'll read up on the matter
[21:40] <mrjb> thanks!
[21:44] <norsetto> sistpoty: do you think it is worth to sync atlas 3.6.0-21.5 ?
[21:45] <sistpoty> norsetto: t.b.h I haven't looked at the changes yet. iirc my changes could be dropped as is, but I'm not too sure about the other changes (iirc from geser?)
[21:46] <sistpoty> norsetto: also, I guess it would make sense to fix blas first (unless that's done already)
[21:46] <sistpoty> bug 202869
[21:46] <ubottu> Launchpad bug 202869 in blas "ICAMAX/IZAMAX tests" [Undecided,New] https://launchpad.net/bugs/202869
[21:52] <norsetto> sistpoty: roger
[21:52] <sistpoty> norsetto: feel free to take over the merge though ;)
[21:53]  * norsetto feels free
[21:53] <sebner> norsetto: free, free like a bird xD
[21:53] <sebner> huhu sistpoty =)
[21:53] <sistpoty> hi sebner
[21:54] <norsetto> sebner: free like beer (whatever that means, I still haven't got that)
[21:54] <sebner> norsetto: free like freebeer? ^^
[21:54] <DktrKranz> "free kevin!"
[21:54] <sebner> rofl
[21:54] <norsetto> DktrKranz for president!
[21:55] <DktrKranz> norsetto, better ask Nokia or AT&T guys before :)
[21:55] <norsetto> nokia: ?
[21:55] <norsetto> at&t: ?
[21:56] <DktrKranz> rtfm :P
[21:56] <DktrKranz> s/manual/book/
[21:56]  * norsetto reads
[22:00] <devfil_> norsetto: I've done the package that you've seen yesterday
[22:03] <norsetto> devfil: good, thanks for all your hard work
=== devfil_ is now known as devfil
[22:04] <DktrKranz> norsetto, tomorrow is devfil's birthday and I guess he wants a gift... ;)
[22:04]  * norsetto hands over a kubuntu cd to devfil
[22:05] <devfil> norsetto: I use GNOME :P
[22:05] <norsetto> devfil: yes, thats why ;-)
[22:05] <sistpoty> leleobhz: you just replied to my mail regarding the binary upload of uniconverter to revu, right?
[22:06] <leleobhz> sistpoty: right!
[22:06] <leleobhz> sistpoty: a little mistake uploading binaries
[22:06] <leleobhz> sistpoty: and after ive seen havea archived package.. (but ive used cdbs)
[22:07] <sistpoty> leleobhz: thing is, that the .changes file (which you upload via e.g. dput) describes what files to put up there
[22:07] <sistpoty> leleobhz: so if the .changes files points to a .deb, then it's a binary upload
[22:07] <sistpoty> leleobhz: which revu however won't accept
[22:07] <leleobhz> sistpoty: yep... ive uploaded the source after this
[22:07] <leleobhz> sistpoty: its a mistake, as i said...
[22:07] <sistpoty> leleobhz: ah, great. then no need to worry ;)
[22:07] <leleobhz> a little problem with tab completion
[22:07] <leleobhz> ;]
[22:07] <sistpoty> heh
[22:07] <nxvl> norsetto: ping
[22:08] <leleobhz> sistpoty: but im worried about the duplicated package
[22:08] <leleobhz> sistpoty: may my package be droped?
[22:08] <norsetto> nxvl: SIGPONG
[22:08] <sistpoty> leleobhz: if you upload s.th. twice, it will just create a new upload entry on the revu page
[22:09] <leleobhz> sistpoty: but my package are very different from original
[22:09] <nxvl> norsetto: i have just fixed A LOT of bashisms on bootcd, but i think they may break the bash compatibility
[22:10] <nxvl> norsetto: is that a good idea to send the patch back to debian or not?
[22:10] <norsetto> nvxl: err, isn't that the purpose?
[22:10] <leleobhz> sistpoty: the original made with debian traditional way and mine ive used cdbs, and its a new version
=== jussi01_ is now known as jussio1
[22:10] <sistpoty> leleobhz: that's not really a problem imho
[22:10] <slangasek> nxvl: breaking bash compatibility isn't a good idea, in Ubuntu or in Debian... :)
[22:11] <leleobhz> sistpoty: but may my package inserted into official repositories?
[22:11] <leleobhz> s/but/so/g
[22:11] <nxvl> slangasek: so it's a good idea to send them the patch back?
[22:11] <nxvl> norsetto: why is that the idea? in debian they use bash for building
[22:11] <slangasek> nxvl: well, it's a better idea to first fix the patch so that it doesn't break bash compatibility...?
[22:11] <sistpoty> leleobhz: hm.. that's a good question, as awen's comment stated that he'll try to get it into debian
[22:11] <nxvl> i'm talking about Bug #238761
[22:11] <slangasek> nxvl: but if you aren't comfortable doing this, then talking with the Debian maintainer about how to fix it is a good idea, yes
[22:11] <sistpoty> leleobhz: personally, I'd prefer that if we have the chance to sync a package from debian, we should do that
[22:11] <ubottu> Launchpad bug 238761 in bootcd "bootcd 3.10 FTBFS due bashism" [Undecided,Confirmed] https://launchpad.net/bugs/238761
[22:12] <leleobhz> sistpoty: even if my version is newer
[22:12] <leleobhz> ?
[22:12] <sistpoty> leleobhz: however I have no clue if awen is still pursuing that goal or what the state is
[22:12] <sistpoty> leleobhz: have you contacted awen yet? maybe you'd like to work together on the package?
[22:12] <a|wen> sistpoty: what package are we talking about?
[22:12] <leleobhz> sistpoty: so awen decides?
[22:12] <nxvl> the problem, most of them, are the \n's
[22:13] <leleobhz> a|wen: uniconvertor
[22:13] <sistpoty> a|wen: uniconverter
[22:13] <nxvl> since it first run a script which in dash it will interprete the \n but in bash don't
[22:13] <a|wen> leleobhz: what's with the package?
[22:13] <nxvl> so for dash i needed to add some more \'s
[22:13] <nxvl> to end with the same result
[22:13] <leleobhz> a|wen: ive created it again because ive dont seen you package before
[22:14] <leleobhz> i forgot to look at archived package
[22:14] <leleobhz> s
[22:14] <leleobhz> so, the version 1.1.2 are uploaded as a new package]
[22:14] <a|wen> leleobhz: ahh ... it's in debian now; and i got it included in intrepid (was to late for hardy at the time)
[22:15] <leleobhz> a|wen: so it ill get syncronized with debian and my package droped?
[22:15] <slangasek> nxvl: erm, dash parses \ inside of single quotes?
[22:15] <slangasek> that seems... unfortunate
[22:15] <a|wen> leleobhz: where is your package atm.? ... link?
[22:15] <leleobhz> a|wen: ive sent it to revu
[22:15] <slangasek> also, this seems vaguely familiar, like an LTSP bug I saw towards the end of the hardy cycle
[22:16] <nxvl> slangasek: inside double quotes
[22:16] <slangasek> nxvl: many of the changes in your patch are to instances where it's in single quotse
[22:16] <leleobhz> but if you want i can put into ppa or my private repository
[22:16] <a|wen> leleobhz: ahh ... the package is already in ubuntu (and i've got inkscape patched to work with it), so it should be good
[22:16] <nxvl> so inside single quotes also
[22:16] <nxvl> i do a lot of tests
[22:16] <a|wen> leleobhz: but if you have some improvements, they are always welcome!
[22:16] <nxvl> and i ended just comparing the outputs in bash and in dash
[22:16] <leleobhz> a|wen: well, only a clean package
[22:17] <leleobhz> a|wen: ive used cdbs
[22:17] <leleobhz> and you manpage ;]
[22:17] <slangasek> nxvl: er, oh; I take that back, it just *looks* like it's in single-quotes, but it's really an insane variable containing a multiline command
[22:17] <slangasek> well
[22:17] <nxvl> yep
[22:17] <leleobhz> a|wen: ill keep the package here, if you think its a good idea use cdbs or another thing...
[22:17] <nxvl> a lot of insane commands
[22:17] <leleobhz> well
[22:17] <slangasek> no, it's "$( ... 'foo' )"
[22:18] <leleobhz> how can i see what applications arent packaged yet?
[22:18] <leleobhz> have some wishlist?
[22:18] <slangasek> which means that it should be treated as a string literal inside the quotes, ohwell
[22:19] <a|wen> leleobhz: you hopefully use python-support right?
=== somebodynotmysel is now known as sodacap
[22:20] <leleobhz> a|wen: sure! ;]
[22:20] <nxvl> slangasek: belive me, it's a nightmare
[22:20] <leleobhz> a|wen: ive eated the cdbs documentation before
[22:20] <nxvl> slangasek: i'm fighting with this thing since yesterday
[22:20] <a|wen> leleobhz: good :) ... if you give me a link for it, i can look at improving the packaging when the new upstrem release is here
[22:21] <leleobhz> a|wen: i ill upload it to my ppa, its ok?
[22:21] <a|wen> leleobhz: a .dsc link from mentors is fine
[22:21] <leleobhz> a|wen: ive only sent it to revu
[22:22] <sistpoty> a|wen: interesting. lp shows a source package page for uniconvertor, but it doesn't show any releases yet (and it also is not in the new queue for intrepid)...
[22:22] <leleobhz> a|wen: if helps
[22:22] <a|wen> leleobhz: then a .dsc link from revu :)
[22:22] <sistpoty> ah. it's python-uniconvertor
[22:22] <a|wen> sistpoty: yes :)
[22:23] <leleobhz> a|wen: how can i see it?
[22:24] <a|wen> leleobhz: found it ... thanks :)
[22:24] <leleobhz> a|wen: oh, nice
[22:24] <leleobhz> a|wen: its the ubuntu3?
[22:24] <a|wen> leleobhz: i'll just wait a bit for it then
[22:24] <leleobhz> a|wen: sending....
[22:25] <a|wen> leleobhz: might be a good idea to put a comment on revu, that it is already in ubuntu as python-uniconvertor
[22:25] <leleobhz> a|wen: how can i do this?
[22:25] <leleobhz> a|wen: done, source sent
[22:25] <a|wen> leleobhz: login at the front page let's you add comments
[22:26] <leleobhz> how can i do my first login?
[22:27] <sistpoty> leleobhz: use your email from the upload as login, don't enter a password. then you get a link to recover your password
[22:27] <leleobhz> sistpoty: yes yes, but show-me only a screen telling me to run a gpg command
[22:27] <leleobhz> and notting on my email
[22:28] <a|wen> leleobhz: if you fancy packaging python modules, there is actually a debian python group ... it's a great way to collaborate about python packages; and they are quick at sponsoring ... and you can get the packages sync'ed from debian to ubuntu afterwards
[22:28] <sistpoty> leleobhz: yes, so run that gpg command, and it will decrypt your password, given that you have the private key ;)
[22:29] <leleobhz> sistpoty: but have notting into
[22:29] <leleobhz> see
[22:29] <leleobhz> http://img512.imageshack.us/img512/5756/revuzo2.png
[22:29]  * sistpoty looks
[22:30] <a|wen> leleobhz: so if you ever feel for some python packaging you could drop by #debian-python
[22:30] <leleobhz> a|wen: i only want to package ;]
[22:31] <leleobhz> a|wen: this channel are into freenode?
[22:31] <sistpoty> leleobhz: oh, your elg-e key has expired. hence revu cannot encrypt with it
[22:31] <leleobhz> sistpoty: ?
[22:31] <a|wen> leleobhz: sorry on irc.debian.org
[22:31] <leleobhz> sistpoty: what i need to do?
[22:34] <sistpoty> leleobhz: iirc you can (re)set the expiry date of the elg-e subkey, or create a new one. but don't ask me how, I haven't done this in a very long time (maybe anyone with better gpg knowledge around=
[22:34] <leleobhz> sistpoty: and how can i resend it to revu?
[22:35] <sistpoty> leleobhz: you'll need to send it to a public keyserver and then revu's keyring needs to be resynced to pick it up
[22:35] <a|wen> leleobhz: got your package now; thanks again ... i'll keep a look at your packaging when a new upstream version arrives
[22:36] <leleobhz> a|wen: nice!
[22:36] <leleobhz> a|wen: last, have some wishlist for packaging?
[22:39] <a|wen> leleobhz: not atm ... but you might be able to find some RFP (request for packaging) in either launchpad or the debian BTS
[22:39] <leleobhz> a|wen: but i can be helpfull in debian without being a DD?
[22:41] <a|wen> leleobhz: they have debian mentors (much like revu) ... and then you request sponsorship on a mailinglist
[22:41] <nxvl> slangasek: the first one is inside double quotes, which are inside single quotes, whichare inside single quotes
[22:41] <a|wen> leleobhz: the good thing is that this way both ubuntu and debian will benefit for it
[22:41] <nxvl> slangasek: the first one is inside double quotes, which are inside single quotes, whichare inside double quotes*
[22:41] <a|wen> leleobhz: i'll go find a few links for you
[22:43] <leleobhz> a|wen: nice!
[22:44] <a|wen> leleobhz: RFP: http://www.debian.org/devel/wnpp/requested ... packages that needs adoption (the former maintainer isn't there anymore) http://www.debian.org/devel/wnpp/orphaned
[22:44] <a|wen> leleobhz: the mentors site http://mentors.debian.net/ ... there are some good links there
[22:45] <a|wen> leleobhz: and you can also drop by #debian-mentors on irc.debian.org
[22:45] <leleobhz> a|wen: nice
[22:45] <leleobhz> a|wen: im fighting with my gpg keys (i dont know how i can manipulate sub-keys)
[22:46] <a|wen> leleobhz: and then keep an eye on the packages in ubuntu :) ... if they don't have any ubuntu specific changes they will be synced; else some manual work is needed ... or an import if it is not in ubuntu yet
[22:47] <a|wen> leleobhz: gpg is not my strong side ... hope you figure it out
[22:47] <leleobhz> :]
[22:47] <leleobhz> a|wen: ill contact you later, after solve the key problem
[22:48] <a|wen> leleobhz: i'll probably pop off shortly (my timezone call this late evening) ... but feel free to ping me when i'm back
[22:49] <leleobhz> :]
[22:49] <leleobhz> sistpoty: ping
[22:49] <leleobhz> a|wen: thanks
[22:49] <sistpoty> leleobhz: pong
[22:49] <leleobhz> sistpoty: i need elgamal key?
[22:50] <leleobhz> because i cant change it expiration data (or i dont know how to do this properly)
[22:50] <sistpoty> leleobhz: yes, otherwise revu cannot encrypt your password (nor anyone else can send you e.g. an encrypted mail)
[22:50] <leleobhz> sistpoty: so how can i change expiration data?
[22:50] <leleobhz> because it appears on my keyring but gpg --edit-key dont do anything
[22:51] <sistpoty> leleobhz: let me take a look
[22:52] <Laney> Can someone help me with these errors when building a package: http://pastebin.ubuntu.com/19153/
[22:53] <leleobhz> heh
[22:58] <a|wen> leleobhz: you need to do "gpg --edit-key [key-id]" ... this should get you in an edit prompt; use "help" to get a list of options
[23:00] <sistpoty> leleobhz: ah, found it. what a|wen wrote. then use key 1 (or key 2) to toggle between primary key and subkey
[23:00] <sistpoty> (or whatever the index of your elg-e key is
[23:00] <sistpoty> +)
[23:01] <sistpoty> leleobhz: then you can change the expiry date with expire
[23:01] <sistpoty> selecting a subkey however is imho very unintuitive *g*
[23:03] <sebner> gn87 folks
[23:04] <sistpoty> gn8 sebner
[23:06] <leleobhz> sistpoty: err
[23:07] <sistpoty> leleobhz: yes?
[23:07] <leleobhz> ah, ok
[23:08] <sistpoty> heh
[23:09] <leleobhz> sistpoty: sent the new key
[23:09] <a|wen> g'night people
[23:09] <sistpoty> gn8 a|wen
[23:09] <leleobhz> gn8
[23:10] <leleobhz> sistpoty: so, how much time i need to wait the key reload?
[23:11] <sistpoty> leleobhz: where did you send it to? as at least the elg-e key on the ubuntu keyserver is still expired
[23:11] <leleobhz> sistpoty: now
[23:11] <leleobhz> on last 5 minutes
[23:12] <leleobhz> sistpoty: and my old elg-e key is expired since 2007 :[
[23:13] <sistpoty> leleobhz: yes. but to which keyserver did you send the changed key? (did gpg's output say s.th. about this?)?
[23:13] <leleobhz> yep
[23:14] <leleobhz> wwwkeys.eu.pgp.net
[23:14] <sistpoty> ah. then it's clear why I can't find the new key :)
[23:15] <Laney> ScottK: Do you mind if I merge spambayes?
[23:15] <Laney> Also, does anyone know what /!\ means on DaD?
[23:15] <leleobhz> sistpoty: send to some another server?
[23:16] <sistpoty> leleobhz: hm... even there it still says that your elg-e key expired in 2007
[23:16] <ScottK> Laney: Go ahead.
[23:16] <Laney> Thanks
[23:16] <ScottK> Laney: It means that the diff is empty (so it's a bogus merge)
[23:16] <sistpoty> leleobhz: can you look again with gpg --edit-key <yourkeyid> at the "sub  2048g/317905E4" line?
[23:16] <ScottK> Laney: It means you have to do it manually or grab the merge from MoM.
[23:17] <Laney> ScottK: Ah, right. I don't use the grab-merge scripts anyway
[23:17] <leleobhz> sistpoty: sub* 2048g/317905E4  created: 2006-11-10  expires: never       usage: E
[23:18] <sistpoty> leleobhz: hm... maybe that keyserver first needs to think about it *g*
[23:19] <leleobhz> sistpoty: so, where i send my key?
[23:19] <sistpoty> leleobhz: you could try to use keyserver.ubuntu.com
[23:21] <leleobhz> sistpoty: sent
[23:25] <sistpoty> leleobhz: ah, there it is... excellent.
[23:26] <leleobhz> :]
[23:27]  * sistpoty refreshes key for revu... may take some time
[23:27] <leleobhz> ;]
[23:32] <leleobhz> sistpoty: stupid ask... handbrake package on revu has been rejected because it has been created using binary direct instead using source
[23:32] <leleobhz> ive started a packaging using source
[23:32] <leleobhz> sistpoty: so is the same way of uniconverter? send and make a comment?
[23:34] <sistpoty> leleobhz: yes, you'll need to build the package from source... however I haven't looked at uniconvertor yet, so I can't say s.th. about it atm.
[23:34] <sistpoty> (and I should also be in bad since quite some time right now *g*)
[23:34] <leleobhz> sistpoty: almost same case
[23:35] <leleobhz> sistpoty: but the original package has been rejected
[23:38] <sistpoty> leleobhz: oh, keys are up to date now
[23:39] <leleobhz> sistpoty: can i ask you a thing in pvt?
[23:39] <sistpoty> sure
[23:44] <Laney> ScottK: Looking at the new Debian version, I think it's a step back from the changes that we currently have in Ubuntu. Is it acceptable to leave a merge for now, possibly also reporting the changes back to the maintainer?
[23:49] <directhex> it's encouraged!
[23:49] <directhex> well, the "changes back to the maintainer" bit is
[23:50] <Laney> Aye
[23:50] <Laney> But I don't want to be like "I don't like the way you've done it, take our stuff instead"