[00:03] <persia> geser: Not quite.  Hammer & tongs backport to python2.4
[00:04] <persia> ScottK: backport to gutsy should work fine.  feisty maybe, but I think it requires too new a version of python-nose.  Might be suitable for a 2.4-forcing gutsy SRU, but that's getting more invasive than I like.
[00:05] <persia> Any backport for Edgy or Dapper should definitely be based on the 0.9 tree, which package I never had working to anyone's satisfaction (including mine).  Given the time, and that it didn't work on release day, I doubt it's worth it.
[01:34] <Solarion> heh.  Anyone else see the Amazon.com sponsored result for searching for 'jono bacon' (no quotes)?
[01:36] <Solarion> on google
[01:36]  * Solarion wants to see the "Low prices on jono bacon"
[01:38] <zul> evening
[02:15] <bddebian> Heya gang
[02:21] <bddebian> Welcome NCommander :)
[02:24]  * NCommander feels people
[02:24]  * LaserJock runs
[02:24] <bddebian> Well this can be a fairly quiet time :-)
[02:24] <bddebian> Heya LaserJock
[02:25]  * NCommander tries to figure out what he can do
[02:27] <LaserJock> hiya bddebian
[02:27] <bddebian> NCommander: Fix bugs! :-)
[02:28] <bddebian> https://wiki.ubuntu.com/MOTU/TODO
[02:35]  * NCommander reads the paperwork first
[02:37]  * NCommander finishs signing things
[03:01]  * Hobbsee reads hte MOTU ML.
[03:01] <Hobbsee> bah.
[03:02] <LaserJock> I read that as "Hobbsee reads the MOTU hate mail"
[03:02] <somerville32> lmao
[03:02] <bddebian> hehe
[03:03] <somerville32> You're not happy with Kmos deciding to leave? :S
[03:03] <minghua> he does?
[03:04] <Hobbsee> So, Kmos is still very impatient, still hasn't learned anything, still says he'll won't do something, then does it.  They recommend more close supervision, as apparently this lot was close enough, and he was shown to violate his sponsorship conditions anyway.
[03:04] <Hobbsee> all because he does sometimes get work right.
[03:04] <somerville32> Hobbsee, You didn't read kmos' response?
[03:04] <somerville32> He has decided to leave
[03:04] <Hobbsee> somerville32: he's decided to leave before.
[03:04] <somerville32> Ah
[03:04] <Hobbsee> somerville32: he said he'd never file another sync request, months ago, too.
[03:05] <Hobbsee> somerville32: he said he wouldn't touch MOTU sync bugs, yet does that as well.
[03:05] <somerville32> "Hobbsee: I WON'T TOUCH AGAIN MOTU BUGS! :-) I'll remember you when I click on the mouse and try to do it."
[03:05] <somerville32> You don't believe him this time Hobbsee? :P
[03:05] <LaserJock> Hobbsee: I don't want to get into it again, but I thought the email was fairly clear, though I think we need an official MC vote
[03:05]  * Hobbsee has little confidence in anything he says actually holding.
[03:05]  * minghua just noticed today that he filed a bunch of Ubuntu-specific FTFBS bugs against Debian.
[03:05] <Hobbsee> LaserJock: what do you read it as saying?
[03:05] <LaserJock> Hobbsee: dholbach's email was fairly clear
[03:05] <Hobbsee> minghua: ...yay.
[03:06] <Hobbsee> LaserJock: it's made recommendations, pretty much the same as were already done.
[03:06] <LaserJock> Hobbsee: no, it said he failed the "exam"
[03:06] <LaserJock> that was my reading
[03:06] <Hobbsee> LaserJock: right, so the recommendations != what they'll do as a result?
[03:07] <LaserJock> there wasn't a recommendation of what to do, it was a summary of the situation
[03:07] <Hobbsee> Recommendation:
[03:07] <Hobbsee> <bullet points>
[03:07] <Hobbsee> that's still a summary?
[03:08]  * Hobbsee thought the summary was the first part, as "recommendation" is at the same position on the screen as "summary"
[03:08] <LaserJock> hmm, I was thinking so, but there's really no recommendation there
[03:08] <Hobbsee> there is a recommendation there - it's just not what most of us wanted.
[03:09] <LaserJock> I wouldn't say that
[03:09] <LaserJock> I don't see a recommendation for or against him leaving
[03:09] <Hobbsee> well, perhaps not.  there seem to be recommendations through it, and the stuff titled "recommendation" really is a summary of hte summary.
[03:10] <Hobbsee> okay, granted.
[03:10] <ScottK> Hobbsee: dholbach clarified on IRC that summary would have been better than recommendation.
[03:10] <ScottK> Good evening all.
[03:10] <Hobbsee> ScottK: right, OK
[03:11] <LaserJock> the original proposal had:"If the evaluation doesn't go well, we must ask him to no longer work on Ubuntu."
[03:11] <ScottK> And I think we should follow through on that.
[03:11] <LaserJock> for sure
[03:11] <LaserJock> so I guess we just need a formal MC vote to confirm
[03:12] <bddebian> Heya ScottK
[03:12] <somerville32> When is the next MC meeting?
[03:12] <Hobbsee> somerville32: they don't do meeting, they do calls.
[03:12] <LaserJock> well, all they need to do is vote via email
[03:12] <joejaxx> is there anywhere i can get a full list of all the FTBFS bugs for a certain arch?
[03:12] <joejaxx> :P
[03:12] <somerville32> lol
[03:12] <joejaxx> sorry to interrupt
[03:13] <joejaxx> :)
[03:13] <LaserJock> joejaxx: thanks
[03:13] <LaserJock> have you tried qa.ubuntuwire.com ?
[03:13] <somerville32> http://qa.ubuntuwire.com/ftbfs/
[03:14] <joejaxx> yeah but that shows all of them
[03:14] <joejaxx> all the arches that is
[03:14] <joejaxx> i guess i can write a script to spider the page
[03:14] <joejaxx> thanks :)
[03:15] <ScottK> Heya bddebian
[03:16] <Solarion> heya laser
[03:20] <LaserJock> hi Solarion
[04:11] <ScottK> Anyone from motu-sru around?  I'd appreciate a look at: Bug 183661
[04:11] <ubotu> Launchpad bug 183661 in libmail-box-perl "FTBFS in Gutsy/Feisty" [Undecided,New] https://launchpad.net/bugs/183661
[04:11] <ScottK> LaserJock: Are you still here?
[04:12] <LaserJock> yep
[04:13] <ScottK> Making a package build that's currently FTBFS is pretty straight forward for an SRU, right?
[04:14] <LaserJock> pretty much, please attach a debdiff
[04:15] <ScottK> For a rebuild?
[04:16] <LaserJock> well, hmm, I'm assuming it'll take a build1
[04:16] <ScottK> Yeah.
[04:16] <ScottK> I was hoping you'd ack it and trust me to write build1 correctly.
[04:17] <ScottK> I just filled out all the required bits on the bug (TEST CASE, etc.)
[04:17] <ScottK> But if you want a debdiff, I'll provide them.
[04:18] <LaserJock> well, I know what you mean
[04:18] <ScottK2> Your call.
[04:19] <LaserJock> ScottK: has a rebuild be done in Hardy?
[04:19] <ScottK> LaserJock: Yes.  It worked.
[04:20] <LaserJock> same version
[04:20] <LaserJock> ?
[04:20] <ScottK> No.
[04:20] <LaserJock> k
[04:20] <ScottK> But FTBFS for the same reason.
[04:21] <ScottK> sbuild attempting to satisfy versioned depends with a virtual package of insufficient version when a non-virtual package would have worked.
[04:23] <LaserJock> ScottK: right, SRU ack'd
[04:23] <ScottK> LaserJock: Thanks.
[04:24] <LaserJock> ScottK: np, thanks for doing the leg work
[04:24] <ScottK2> LaserJock: Thanks for the mail too.
[04:24] <LaserJock> np
[04:45] <slangasek> is there a convention for package numbering on ppas at this point?
[04:46] <Burgundavia> slangasek: try not to make Adam Williamsons prediction come true?
[04:46] <ScottK2> Burgundavia: What was that?
[04:46] <slangasek> who?
[04:48] <LaserJock> slangasek: I think something along the lines of 0ubuntu0ppa1 or similar
[04:48] <Burgundavia> http://www.happyassassin.net/2007/10/24/mistakes/
[04:48] <LaserJock> I got stuck on 0ubuntu0.7.10~ppaX
[04:48] <LaserJock> for gutsy
[04:48] <LaserJock> etc.
[04:49] <jdong> why not 0ubuntu0~7.10~ppaX?
[04:49] <ScottK2> https://help.launchpad.net/PPAQuickStart gives suggestions
[04:49] <jdong> that way you don't potentially interfere with any SRU versions
[04:50] <ScottK2> slangasek: While you're thinking about that, would you mind accepting libmail-box-perl into gutsy-proposed and feisty-proposed?
[04:50] <jdong> slangasek: and looking at mpeg4ip in NEW if it has not been handled yet? :)
[04:50] <LaserJock> jdong: that wouldn't interfere with an SRU would it?
[04:51] <ScottK2> LaserJock: It might have a higher version number than an SRU
[04:51] <jdong> LaserJock: Hmm you're right, 0ubuntu1 is the lowest with ubuntu in it
[04:51] <LaserJock> I guess that's possible
[04:51] <ScottK2> Actually not always for SRU.
[04:51] <LaserJock> jdong: well, security often uses ubuntu0.1
[04:51] <jdong> -1ubuntu0.1 is possible for SRU/security to -1
[04:52] <ScottK2> Yep
[04:52] <jdong> but -0 implies -0ubuntu1
[04:52] <jdong> except maybe the firefox stuff?
[04:52] <jdong> where we introduce a new upstream version as a security fix
[04:52] <jdong> <IP_ADDRESS>+2nobinonly-0ubuntu0.7.10
[04:53] <jdong> yeah, Firefox uses -0ubuntu0.*
[04:53] <jdong> so I guess 0ubuntu0~something is safer
[04:53] <beerfan> Hi all. Is there an abbreviated instruction somewhere for packaging a python script?
[04:55] <slangasek> ScottK2, jdong: <whimper>
[04:55] <pochu> beerfan: does it use distutils?
[04:55] <slangasek> sorry, I'm off-duty right now
[04:55] <LaserJock> slangasek: just make a version scheme up
[04:56] <slangasek> LaserJock: right :)
[04:56] <ScottK2> slangasek: No problem.
[04:56] <jdong> slangasek: fine :)
[04:56] <beerfan> pochu: the script? I don't think so
[04:56] <LaserJock> slangasek: just think *you* can provide the convention
[04:56] <LaserJock> ;-)
[04:56] <jdong> haha
[04:56] <Burgundavia> slangasek: where is the distro sprint?
[04:56] <ScottK2> Speaking of PPAs, how do I make it upload for Gutsy?
[04:57] <jdong> don't you just target gutsy as the distro?
[04:57] <LaserJock> ScottK: changelog
[04:57] <ScottK2> Dunno.  Never uploaded to a PPA before.
[04:57] <pochu> beerfan: take a look at http://wiki.debian.org/DebianPython/NewPolicy. You have examples there.
[04:57] <jdong> ScottK2: yeah the distro field in the changelog
[04:57] <LaserJock> I've only done gutsy PPA uploads
[04:57]  * ScottK2 finally decides to take advantage of it now that the TOS are changed.
[04:58] <LaserJock> I'm still backporting stuff
[04:58] <StevenK> ScottK2: Yeah, target gutsy in the changelog
[04:59] <StevenK> ScottK2: I can give you a .dput.cf snippet if you wish
[04:59] <pochu> ScottK2: either put gutsy in debian/changelog, or in your dput entry put something like "incoming = ~siretart/ubuntu/gutsy"
[05:00] <ScottK> StevenK: I got the dput.cf snippet from the PPA quickstart.  It looked sane enough.
[05:00] <jdong> pochu: why ping siretart for that? :D
[05:00] <pochu> jdong: just to annoy him ;)
[05:00] <ScottK> jdong: Why ping him because pochu did? ;-)
[05:00] <LaserJock> ScottK: it's probably easier to do it in the changelog
[05:01] <jdong> :)
[05:01] <pochu> ScottK: why didn't you ping him too? :)
[05:01]  * Hobbsee pings jdong
[05:01] <LaserJock> you need a unique version / release anyway
[05:01]  * jdong thinks nick completion needs to do globbing!
[05:01] <jdong> ping * :)
[05:01] <pochu> lol
[05:01] <LaserJock> heh
[05:01] <slangasek> Burgundavia: Londinium Anticum
[05:01]  * pochu continues studying
[05:02] <Burgundavia> slangasek: thought as much, in Canonical Tower One
[05:07]  * slangasek wonders if that's supposed to be like One Microsoft Way
[05:10] <StevenK> I've not heard it called Canonical Tower One before
[05:11] <Burgundavia> and now it is and shall be forever
[05:11] <StevenK> I doubt that.
[05:12] <ScottK2> Do PPA uploads get accepted mails sent out?
[05:12] <Burgundavia> StevenK: silence
[05:12] <RAOF> ScottK2: Yes.
[05:13] <ScottK> RAOF: Thanks.
[05:17]  * Hobbsee thought it was called The Evil Canonical Empire Headquarters.
[05:19] <ScottK> Hi there Hobbsee.
[05:19] <Hobbsee> hi ScottK
[05:20]  * minghua renews his membership.
[05:21] <ScottK> JFTR, I pretty much agree with what the Mandriva guy said about PPAs.
[05:21] <Hobbsee> what was that?
[05:21] <minghua> ScottK: What did he say?
[05:21] <Burgundavia> /home/corey/trackpointsDec1007.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec1107.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec2107.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec2107-2.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec2307.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec2607.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec2607-2.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec2907.gpx
[05:21] <Burgundavia> /home/corey/trackpointsDec3107.gpx
[05:21] <Burgundavia> /home/corey/trackpointsJan0108.gpx
[05:21] <Burgundavia> ugh, wrong paste, sorry
[05:21] <Burgundavia> http://www.happyassassin.net/2007/10/24/mistakes/
[05:21] <Burgundavia> that one
[05:21] <ScottK> Yeah. That one.
[05:25] <Hobbsee> ah yes
[05:26] <LaserJock> hehe, "Basically, Ubuntu has institutionalised the third-party repository." gotta love it
[05:26] <StevenK> That isn't amusing, though.
[05:28] <minghua> PPAs won't have a ubuntu.com address, will they?
[05:28] <Hobbsee> no
[05:28] <Hobbsee> they fixed that bug, finally
[05:29] <minghua> I think he is exaggerating the problem.
[05:29] <StevenK> So do I.
[05:29] <Hobbsee> i assume if they use non-official PPA's, it'll just bail out, as it does for third party repos.
[05:29] <minghua> The facts he said are true, but I don't agree with the predictions.
[05:29] <LaserJock> well, I think the idea is right
[05:30] <LaserJock> like what happens when somebody uploads a new gtk or qt that breaks stuff
[05:30] <LaserJock> how do we debug that
[05:30] <minghua> LaserJock: It would have a different version number, and should show in the bug reports.
[05:31] <LaserJock> we don't even know what the version of the "official" packages are in bug reports
[05:31] <minghua> (The good ones anyway)
[05:31] <LaserJock> there's absolutely no way to know a priori
[05:31] <StevenK> Apport reports the version for a crash, for example
[05:31] <crimsun> we do if there is apport info
[05:31] <crimsun> right, what steven said
[05:31] <LaserJock> yes, that's true
[05:32] <LaserJock> but apport isn't used for all that many bugs
[05:34] <LaserJock> I'm guessing upgrade problems will be mitigated to some degree by update-manager
[05:34] <StevenK> Certainly more than they were in Mandriva.
[05:35] <ScottK> What prevents uploads to PPAs with the exact same version number as in the archive?
[05:36] <LaserJock> I don't think anything does
[05:37] <ScottK> So even that's no guarantee.
[05:37] <LaserJock> it's just like a regular repo in that respect
[05:37] <LaserJock> although it does look for .orig.tar.gz's from Ubuntu
[05:38] <ion_> laserjock: If someone uploads a new Gtk or Qt to her PPA, it’s not as if Ubuntu users get that by default. Only the ones who have explicitly decided to trust the repo and use it.
[05:38] <LaserJock> hehe
[05:38] <StevenK> Right.
[05:38] <ScottK> And unlike stuff like automatix, it's downloaded from a Canonical sponsored source.
[05:38] <minghua> You probably can't upgrade to a version the same as your current one, but I know it doesn't matter for newly installed packages.
[05:38] <LaserJock> "my new gtk fixes bugs X, Y, Z and is needed for my new version of Q"
[05:39] <tjaalton> RAOF: exactly, need to test the new stuff for intel (and the rest too if possible)
[05:39] <ScottK> In the same domain as one can get actual Ubuntu .debs from if you want.
[05:39] <LaserJock> and soon enough the repos will be signed
[05:39] <StevenK> I wasn't aware ppa.ubuntu.com resolved ...
[05:39] <StevenK> (It doesn't)
[05:40] <minghua> ScottK: But most users don't know that they can get official packages from LP.
[05:40] <ScottK> StevenK: You can pull .debs off of Launchpad.
[05:40] <ScottK> Agreed.
[05:40] <LaserJock> minghua: no, but LP is official
[05:40] <StevenK> ScottK: Right, but you can't point your sources.list at it
[05:40] <ScottK> True.
[05:40] <RAOF> tjaalton: So, presumably the various non-nouveau DDXs won't care about the new dri modules, but how about mesa?  Is this also going to require a git mesa snapshot to do anything interesting?
[05:41] <minghua> LaserJock: I've also seen people claiming ubuntuforums.org "official".  So as long as the domain names differ, I don't worry too much.
[05:41] <tjaalton> RAOF: I'm working on it :)
[05:41] <LaserJock> minghua: worry about what?
[05:41] <RAOF> tjaalton: Oooh, awesome.  In that case, hell yes!
[05:42] <tjaalton> RAOF: do you have your auto-git scripts somewhere?
[05:42] <minghua> LaserJock: Worry about PPAs breaking systems and upgrades (more then third-party packages already do, anyway).
[05:42] <LaserJock> hmm, I do to some degree
[05:43] <RAOF> tjaalton: Do you mean my "upload new snapshot to PPA" script, or "get new source" script (which is in debian/rules)
[05:43] <LaserJock> we are free-hosting and building 3rd party repos
[05:43] <minghua> Just look at the popularity of getdeb.net, and you'll know that users have enough ways to screw up their system already anyway.
[05:43] <ScottK> It's hard to argue 3rd party repos are a bad idea when the sponsor of Ubuntu hosts them.
[05:43] <LaserJock> and there's not much of a way for users to differentiate good repos from not-so-good
[05:43] <tjaalton> RAOF: oh, right.. it is, I did notice it but didn't look too closely
[05:43] <RAOF> tjaalton: get-orig-source is actually quite nice :)
[05:43] <StevenK> ScottK: Conceptually, they're a great idea.
[05:44] <tjaalton> RAOF: I think I'll upload the merge to git.d.o on debian-experimental branch, and then start working on that
[05:44] <LaserJock> I think PPAs are great, I just think we also need a good way of deal with the "cons" involved
[05:44] <RAOF> tjaalton: You can have my "do everything & upload to PPA" script, but it's unlikely to be very useful for you.
[05:44] <RAOF> tjaalton: Cool.  I suppose I might want to ask for git access, then :)
[05:45] <tjaalton> RAOF: sure, it's easy.. just pop in on #debian-x and ask :)
[05:46] <tjaalton> RAOF: different irc server though
[05:46] <RAOF> Of course, OFTC
[05:46] <tjaalton> and set up an account on alioth.d.o
[05:46] <tjaalton> if not already
[05:46] <RAOF> I've wanted to do that before... not sure if I ended up doing it though.
[05:46] <tjaalton> I guess #d-o is pretty silent right now
[05:47] <tjaalton> uh #d-x
[05:48] <ScottK> StevenK: They're a great idea, but also have risks.
[05:48] <StevenK> ScottK: Right
[05:48] <ScottK> I expect most of the people that'll use them well would have managed without them.
[05:48] <LaserJock> I think they may be good for upstreams
[05:48] <LaserJock> kind of a staging area
[05:49] <StevenK> Exactly. A way to get more testing without people having to build it themselves.
[05:49] <ScottK> For me they're good for backports testing.
[05:49] <ScottK> I can backport a bunch of stuff and build against the backports.
[05:50] <tjaalton> RAOF: the mesa HEAD has autotool support too, so it would be a good time to make it use that
[05:50] <ScottK> So I just uploaded the current clamav package to the ubuntu-clamav PPA for Dapper/Edgy/Feisty/Gutsy.
[05:50] <ScottK> Tomorrow, after they're built, I'll take a whack at uploading the redpends.
[05:53] <RAOF> tjaalton: I'm somewhat ambivalent about that.  Autotools is not my idea of a good time.
[05:59]  * ScottK2 would appreciate suggestions on what to do about checking for gcc bug PR28045... configure: error: your compiler has gcc PR28045 bug, use a different compiler, see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28045
[05:59] <ubotu> gcc bug 28045 in middle-end "[4.0/4.1 Regression] Bitfield, &&, and optimization => bad code generation" [Normal,Resolved: fixed]
[06:01] <minghua> Huh?  What software is that!
[06:01] <ScottK> Current clamav trying to be built on Dapper
[06:02] <doluu> hello all
[06:02] <ScottK2> Immediately followed by make: *** [config.status] Error 1 and the build died.
[06:02] <ScottK2> hello doluu
[06:02] <doluu> I've just build some packages from debian on Ubuntu
[06:03] <doluu> and made change in debian/control to reflect original maintainer
[06:03] <minghua> ScottK: Nothing besides a gcc SRU, as far as I can see.
[06:03] <doluu> how I can get sponsorship?
[06:03] <minghua> ScottK: Or maybe using gcc-3.[34].
[06:03] <ScottK2> doluu: Have you checked to make sure these packages aren't already in Hardy?
[06:03] <doluu> hardy have older version
[06:03] <doluu> it's vzctl
[06:04] <doluu> and vzquota
[06:04] <minghua> !info vzctl hardy
[06:04] <ubotu> vzctl: server virtualization solution - control tools. In component universe, is optional. Version 3.0.18-1 (hardy), package size 184 kB, installed size 1000 kB (Only available for i386 ia64 amd64 powerpc sparc)
[06:04] <ScottK2> doluu: What version does Debian have?
[06:04] <doluu> 3.0.22
[06:04] <minghua> How come we have a version lower than etch?
[06:05] <doluu> openvz's latest version  is also 3.0.22
[06:05] <minghua> Oh sorry, etch has 3.0.11.  I misread as 3.0.21.
[06:05] <tjaalton> RAOF: right, but at least some changes must be done to the old build system since the build failed when it got to i915tex
[06:05] <RAOF> tjaalton: Ok.
[06:07] <ScottK2> doluu: https://wiki.ubuntu.com/SyncRequestProcess is what you want.
[06:08] <minghua> doluu: And come back and ask again once you properly filed a sync request.
[06:11] <ScottK2> !info gcc3.4 dapper
[06:11] <ubotu> Package gcc3.4 does not exist in dapper
[06:12] <minghua> !info gcc-3.4 dapper
[06:12] <ubotu> gcc-3.4: The GNU C compiler. In component main, is optional. Version 3.4.6-1ubuntu2 (dapper), package size 482 kB, installed size 4532 kB
[06:12] <minghua> ScottK: :-)
[06:15] <ScottK> Thanks
[06:27]  * ScottK tries to build clamav again.
[06:32] <ScottK> jdong: Can I backport a C compiler?
[06:34] <StevenK> People might hate you.
[06:35] <ScottK> StevenK: GCC 4.2 doesn't exist at all in Dapper right now, so if it suddenly pops up, nothing should use it?
[06:35] <StevenK> Keep in mind gcc takes over 12 hours to build.
[06:36] <ScottK> I'm gonna do some local testing here first.
[06:36] <ScottK> Backports have the lowest priority anyway, so it's not like it would block much.
[06:44] <ScottK> Nope.  That's not going to work.
[06:45] <ScottK> I guess I need to figure out how to make clamav use gcc 3.4
[06:45] <ScottK> But after I sleep.
[06:45] <ScottK> Good night all.
[06:45] <StevenK> CC=gcc-3.4 in the rules file, and Build-Depend on it?
[06:46] <ScottK> Tried that (or close to that
[06:46]  * ScottK gives it one more try.
[06:48] <StevenK> You'll probably have to feed CC=gcc-3.4 to the configure call
[06:50] <ScottK> That's where I was doing it, but I fed it the path, not just the compiler name.
[06:52] <ScottK> Got through config that time, so that's progress.
[06:52] <ScottK> StevenK: Thanks for the hint.
[06:52] <StevenK> ScottK: No problem
[06:54] <ScottK> And it built in the pbuilder.    He could be stuck on holiday for two weeks with my children.
[07:06] <ScottK> ;-)
[07:06] <ScottK> Actually my kids are great, but we drove over 3,000 miles (4,800 km) over Christmas vacation.
[07:07] <StevenK> Ahh. "Don't make me turn this vacation around!"
[07:07] <somerville32> StevenK, 3 in the morning wouldn't be the same without you
[07:08] <TheMuso> Parents are good (tm)
[07:08] <StevenK> somerville32: I see.
[07:09] <LaserJock> hmm, I wish we had a FTBFS list that didn't include hppa
[07:09] <TheMuso> LaserJock: Why?
[07:09] <StevenK> Because LaserJock doesn't care about it, I'm guessing.
[07:09] <LaserJock> cause hppa is quite a bit of a majority of them
[07:10] <LaserJock> and we're not really going to be fixing them in general
[07:10] <StevenK> lynx -dump <url> | grep -v hppa ?
[07:10] <LaserJock> they should definitely show up, but it'd be nice to have a view without them
[07:10] <LaserJock> StevenK: yes, there's always good workarounds :-)
[07:11] <dholbach> good morning
[07:11] <LaserJock> just thinking for qa.ubuntuwire.com v2
[07:11] <LaserJock> dholbach!
[07:11] <TheMuso> Hey dholbach.
[07:12] <dholbach> hey LaserJock, hey TheMuso
[07:17] <ScottK> Good morning dholbach.
[07:17] <ScottK> Good night everyone.
[07:17] <vemon> do debian maintainers scan ubuntu packages for changes that aren't in debian? meaning: if i make a patch to ubuntu package are there any chanses of it getting to debian without me filing a debian bug about it?
[07:17] <somerville32> vemon, doubt it
[07:17] <dholbach> hey scottK
[07:17] <ScottK> vemon: Depends a lot on the Debian maintainer
[07:19] <vemon> any automagic tricks in launchpad for getting a bug to debian BTS also?
[07:19] <Hobbsee> somerville32: PTS?
[07:19] <somerville32> Hobbsee, Plumbing.... Trade... Supplies?
[07:19] <TheMuso> lol
[07:20] <Hobbsee> somerville32: package tracking system.  debian.
[07:20] <ScottK> vemon: reportbug, but make sure the issue actually applies to Debian.
[07:20] <slangasek> LaserJock: well, feel free to install the grub package from deb http://ppa.launchpad.net/vorlon/ubuntu hardy main and let me know if it eats your system for lunch, instead of just partially implementing a hardy spec like it's supposed to ;)
[07:21] <vemon> scottk, sure. that's the first thing i check anyways since it's always easier to just sync the package from debian
[07:22] <somerville32> Oh cool :)
[07:22] <ScottK> vemon: OK.  Just saying.  Not everyone does that.
[07:22] <ScottK> Good night (really).
[07:22] <vemon> scottk, i don't doubt that :)
[07:22] <somerville32> Me too
[07:22] <somerville32> I need sleep :)
[07:22]  * somerville32 waves.
[07:22]  * slangasek waves to ScottK, somerville32
[07:22] <dholbach> night somerville32, night scottK
[07:31] <vemon> hmm. doesn't reportbug just send a message to the ubuntu<EMAIL_ADDRESS>[07:31] <vemon> referring to: https://bugs.launchpad.net/ubuntu/+source/reportbug/+bug/36186
[07:31] <ubotu> Launchpad bug 36186 in reportbug "Trivial and non-trivial enhancements for bugreport" [Wishlist,Confirmed]
[07:31] <LaserJock> not if you tell it to send to debian
[07:32] <vemon> LaserJock, ok. thanks :) i'm at work now and unable to test it yet so i only have the inter-web to seek info from
[07:33] <vemon> (sound like a bad excuse..)
[07:34] <LaserJock> vemon: if you run reportbug --bts help you get a lits of bug trackers you can use
[07:35] <LaserJock> so reportbug --bts debian should submit to debian I think
[07:38] <LaserJock> ok, anybody know what email address system mail would be sent to if you use a smart host for smtp?
[07:39] <LaserJock> I'd like to be able to use apps that send mail (reportbug for instance) but I don't want my system mail going into some unknown cyberspace
[10:24] <persia> somerville32: Thanks for the continuing review of notecase.  it's very pleasant to see such evidence of collaboration.
[10:25] <slytherin> am I the only one with timeout problems with launchpadlibrarian.net? I am not able to access build logs, bug attachments :-(
[10:26]  * persia tries something
[10:27] <Ng> is there any sane way to build a package from a folder that has a .bzr/ in it, without using bzr-buildpackage?
[10:27] <persia> slytherin: I get things near instantaneously
[10:27] <slytherin> :-(
[10:27] <persia> Ng: debuild -i might be what you seek, but I've heard it's not always perfect.
[10:27] <Ng> hmm, I'll probably just move the thing out of the way then
[10:27] <Ng> thanks
[10:33] <StevenK> Ng: Build the source package yourself using -I.bzr and then point pbuilder build at the .dsc?
[10:38] <soren> StevenK: You mean -i, probably.
[10:53] <rZr> 'morning
[10:59] <StevenK> soren: Probably
[11:06] <rZr> persia: hi, let me poke you on  http://revu.tauware.de/details.py?package=jaaa  because i am about to have no more free time soon
[11:08] <persia> rZr: Nope.  I'm the last three successive reviewers, which I try to maintain as a limit (and only make exceptions when a package hasn't had a review in a really long time).  You need to get someone else's opinion about the package.
[11:09] <rZr> ok I understand .. anyone here , :)
[11:09] <persia> rZr: On the other hand, I advocated the last revision, so I suspect that there is likely only one more at most before it gets in (as that seems to be about normal for packages I advocate)
[11:09] <rZr> ok thanx anyway
[11:11] <emgent> heya
[11:55] <emgent> jdstrand, heya :)
[12:05] <emgent> someone saw Fujitsu?
[12:06] <persia> emgent: On holiday.  Why?
[12:06] <emgent> ok, i will mail him :)
[12:08] <persia> emgent: He has very limited internet connectivity.
[12:08] <emgent> argh! ok, thanks persia for all informations
[12:09] <ion_> What kind of a holiday is one with limited Internet connectivity? :-)
[12:12] <persia> ion_: The sort was might refer to as "Unfortunate"
[12:12] <slytherin> I am just curious whether gcj is built on all arch. can anyone comment?
[12:14] <geser> slytherin: the last gcj-4.2 built on all archs except hppa
[12:15] <slytherin> geser: ok, thanks
[12:16] <geser> slytherin: you can check it when you click through LP to the build status pages for a given source package
[12:19] <mok0> When you call dpkg-buildpackage with the -B flag, why does it visit the build-indep target? It is only in the install-* targets that it seems to differentiate
[12:35] <\sh> moins
[12:36] <mruiz> hi all
[12:36] <emgent> \sh, heya :P
[12:37] <\sh> wow..since two days I'm working now on this freecom fsg-3 nas thing...and finally I managed to get openwrt running on this beast
[12:37] <\sh> moins emgent
[12:37] <emgent> openwrt++
[12:39] <\sh> emgent, well, openwrt is not the problem :) the problem was the fsg3 thing...
[12:40] <\sh> emgent, I needed to play around with this redboot stuff and had to recover the thing for round about 40 times or so
[12:41] <\sh> emgent, and the good thing, I just fixed some packages for the openwrt stuff...need to send the patches upstream ;)
[12:46] <emgent> \sh ++
[12:58] <\sh> persia, reminder bug #164899 what should we do...close it or work on it?
[12:58]  * persia wonders if ubotu plans to provide a URL
[12:59] <ubotu> Launchpad bug 164899 in libao "libao.conf in gutsy is wrong. (alsa09 is set as default)" [Undecided,Confirmed] https://launchpad.net/bugs/164899
[13:00] <persia> \sh: I thought LaserJock had sponsored that, and forgot about it completely.  Probably best to submit a patch and pass to the main SRU team, as it's certainly a regression from feisty.
[13:02] <persia> \sh: With the new SRU policy, it will need a TEST CASE, etc.
[13:02] <\sh> persia, ok..will put it on my todo now...
[13:03] <persia> \sh: Thanks :)  By the way, why are you still not a member of ~motu-swat?
[13:03] <\sh> persia, ah damn....I knew I forgot something :)
[13:03] <persia> heh
[13:04] <\sh> persia, subscription request pending approval :)
[13:04] <\sh> emgent, testing your drupal5 security diffs...:)
[13:04] <persia> \sh: I think it's likely about 10 days until he gets back...
[13:04] <emgent> \sh, cool :P
[13:04] <\sh> persia, you mean fujitsu?
[13:05] <emgent> i asked some hours ago. :P
 someone saw Fujitsu?
 emgent: On holiday.  Why?
 ok, i will mail him :)
 emgent: He has very limited internet connectivity.
[13:08] <rulus> If someone has time for a little review of http://revu.tauware.de/details.py?package=gtkvd that would be nice, I think I solved all the issues.
[13:09] <\sh> does anyone know why motioneye is just build for i386?
[13:10] <ScottK2> Good morning zul.
[13:10] <\sh> ah sony vaio stuff
[13:10] <\sh> guys, for rebuilding uploads we don't need to change the maintainer field, right?
[13:12] <geser> \sh: motioneye> because debian/control says so: Architecture: i386
[13:12] <\sh> geser, yeah it's just for the sony vaio cam so I think it's really only i386 related
[13:13] <ScottK2> \sh: I haven't been.  I'm not 100% certain that's right.
[13:13] <zul> hey ScottK2
[13:14] <geser> it's also listed in P-a-s as i386 only
[13:15]  * persia suspects Sony has probably released an x86_64 capable motion-eye compatible device, but doesn't know that anyone cares.
[13:15] <\sh> where was this document to the ubuntu maintainer field policy?
[13:16] <persia> \sh: https://wiki.ubuntu.com/DebianMaintainerField
[13:17] <emgent> \sh, tested? :)
[13:18] <\sh> emgent, I'm updating my gutsy pbuilders :)
[13:18] <emgent> hehehe ok :P
[13:18] <jdstrand> emgent: hi!
[13:18] <emgent> jdstrand, hi! :P
[13:21] <\sh> Seveas, ping...would you like to add a freenode cloak for me? :)
[13:26] <PriceChild> \sh, he doesn't do them anymore
[13:26] <persia> PriceChild: Who does now?  Any IRC Council member?
[13:26] <PriceChild> \sh, could you give me your launchpad addy, and check you have a linked nick and email set.
[13:26] <\sh> PriceChild, shermann :)
[13:26] <PriceChild> persia, yes. Me, elkbunt.u, nal.ioth or lj.l
[13:27] <\sh> PriceChild, the /msg nickserv info \sh is wrong...about the linked nicknames...\sh should be master...
[13:28] <PriceChild> \sh, /msg nickserv help set master
[13:28] <\sh> PriceChild, thx done
[13:28] <LucidFox> Hmm. For some reason, an upload failed to close (LP: #) bugs
[13:29] <TheMuso> LucidFox: Incorrect syntax perhaps?
[13:29] <PriceChild> \sh, the cloak has been requested and should be turned on soon. A staffer will probably contact you to confirm you want ubuntu/member.
[13:30]  * persia never got contacted for confirmation, so this may not occur
[13:30] <persia> LucidFox: Did "Launchpad-Bugs-Closed:" appear in source.changes?
[13:30] <PriceChild> persia, probably because the staffer was watching the channel you requested it in at the time.
[13:31] <persia> PriceChild: I'm fairly certain that was true, but am less certain that isn't also true for \sh.
[13:31] <PriceChild> uuu persia you remind me I should get the new version of gizmod uploaded...
[13:32] <\sh> well...if we have ubuntu/motu that would be cool ;)
[13:32] <persia> PriceChild: Oh.  Right.  I kept meaning to poke you about that and forgetting when you were actually about.  Only a couple weeks left.
[13:32] <emgent> ^^
[13:32] <PriceChild> \sh, nope, always ubuntu/member, nevermind if you were approved by edubuntu,kubuntu or motu
[13:33] <\sh> PriceChild, I know...
[13:33] <PriceChild> persia, its all "ready" in my ppa. Just the udev part.
[13:35] <PriceChild> oh and licensing.... gah completely forgot about that
[13:35] <persia> heh
[13:35] <PriceChild> 3 day weekend... its going to be done
[13:41] <LucidFox> No, Launchpad-Bugs-Closed doesn't appear. However, it was a merge so there are multiple entries, including Debian ones, and there's a Closes header
[13:41] <LucidFox> http://launchpadlibrarian.net/11406974/f-spot_0.4.1-4ubuntu1_source.changes
[13:46] <\sh> emgent, the patch for SA-2007-031 is again not correct :)
[13:46] <emgent> uh?
[13:46] <emgent> are u sure?
[13:47] <emgent> http://drupal.org/node/198162
[13:47] <\sh> emgent, if you apply the upstream patch for SA-2007-031 there is a bug inside...the fix is on http://drupal.org/files/issues/db_query_range.patch
[13:47] <\sh> emgent, yeah..the patch is wrong :) that's why 5.5 came out with the fix for the fix of SA-2007-031 :)
[13:48] <emgent> ok i understand
[13:48] <\sh> emgent, in the patch of SA-2007-031 they wrote:
[13:48] <\sh> +-      $result = db_query_range($sql, 0, variable_get('feed_default_items', 10));
[13:48] <\sh> ++      $result = db_query_range($sql, 0, variable_get('feed_default_items', 10), $args);
[13:48] <\sh> but the $args is wrong as you can see from the discussion on http://drupal.org/node/198321 :)
[13:49] <emgent> ok \sh ++
[13:51] <siretart> did we already settle in ubuntu on dh_iconcache vs dh_icons? which of those do we use?
[13:52] <geser> siretart: dh_icons, I don't have dh_iconcache anymore in my hardy installation
[13:52] <siretart> excellent. this means that http://patches.ubuntu.com/s/scorched3d/scorched3d_40.1d.dfsg-1ubuntu1.patch can be dropped now
[13:53] <siretart> (the upload I'm currently preparing for debian is introducing a dh_icons call)
[13:53] <ion_> Is scorched3d 41 coming to hardy?
[13:54] <ScottK2> Good morning all.
[13:54] <ion_> Good evening.
[13:54] <ScottK2> My the coffee isn't helping yet.  What's the canonical method for finding the reverse depends of a package for a particular release?
[13:55] <siretart> ion_: I'm currently building & uploading it for debian, will request a sync for that afterwards
[13:55] <ion_> siretart: Great
[13:55] <siretart> hey ScottK2. how are you doing?
[13:55] <ScottK2> Heya siretart.  Not bad.
[13:55] <geser> ScottK2: if apt-cache rdepends doesn't help, what about using grep-dctrl?
[13:56]  * siretart uses revbuilddep() { grep-dctrl -FBuild-Depends,Build-Depends-Indep -s Package $1 -n /var/lib/apt/lists/*_Sources }
[13:56] <ScottK2> siretart: Currently a little nervous waiting to see how my core-dev application works out.
[13:56]  * ScottK2 writes that down.
[13:56] <siretart> ScottK2: I'll keep my fingers crossed for you!
[13:56] <ScottK2> thanks.
[13:57] <leonel> ei ScottK2  2 good news  today ( clamav  and your applicarion )   me hopes for the best !
[13:58] <\sh> ScottK2, gogogo for core :)
[13:59] <zul> ScottK2: good luck
[14:01] <ScottK2> Thanks all.
[14:06] <PriceChild> Could someone help me get started (again) on REVU? The wiki makes me think that I should be able to recover my password already seen as I've been in the contributers group more than 24 hours. However revu tells me No REVU account for<EMAIL_ADDRESS>exists yet.
[14:06]  * effie_jayx wants something to do :D
[14:07] <ScottK2> PriceChild: You need to do an upload to REVU first
[14:07] <PriceChild> ScottK, aha thanks.
[14:11] <leonel> effie_jayx: where will be your   spanish motu talk ?
[14:11] <effie_jayx> leonel,  it's now.. ;)
[14:12] <effie_jayx> #cupie
[14:12] <leonel> plop where ?
[14:14]  * \sh goes shopping...bbl
[14:17] <persia> PriceChild: just FYI, no point pushing gizmod to REVU: it wants an interdiff in the sponsors queue.
[14:18] <PriceChild> persia, Something new to learn about :)
[14:19] <persia> PriceChild: https://wiki.ubuntu.com/UbuntuDevelopment/Interdiff
[14:19] <PriceChild> persia, thanks
[14:52] <emgent> hello there
[14:54] <LucidFox> Welcome, emgent
[14:57] <philn> hi
[14:58] <philn> where can i talk to PPA admins?
[14:58] <Ng> philn: #launchpad
[14:58] <geser> philn: #launchpad
[14:58] <philn> thx
[15:14] <ScottK> OK.  Here's one I've never seen before (this is GCC 3.4 in dapper) configure: error: C compiler cannot create executables
[15:14] <ScottK> Any suggestions on how to troubleshoot that?
[15:14] <ion_> Look at the configure log. Perhaps just some package missing.
[15:15] <ScottK> ion_: So how do I get the configure log off of a buildd?
[15:15] <geser> ScottK: url to the build log?
[15:16] <ScottK> geser: http://launchpadlibrarian.net/11410627/buildlog_ubuntu-dapper-i386.klamav_0.41.1-0ubuntu2~dapper~ppa1_FAILEDTOBUILD.txt.gz
[15:16] <ScottK> I didn't have that problem in my local pbuilder.
[15:23] <geser> ScottK: CC=gcc-3.4 but no gcc-3.4 installed (Toolchain package versions: [...] gcc-4.0_4.0.3-1ubuntu5)
[15:24] <ScottK> So I need to add it as a build-dep then.  Thanks.
[15:24] <ScottK> Odd it would pick that then.
[15:25] <mok0> I am somewhat confused as to what dpkg-buildpackage does to build packages, and the buildd systems. Does the buildd system distinguish between build-arch and build-indep (i.e. does not use the build target)?
[15:27] <mok0> I don't see the point of having two build targets for indep and arch otherwise
[15:28]  * ScottK head-desk.
[15:28] <mok0> ... if all systems always used "debian/rules build"
[15:28] <ScottK> That's what I get for starting something, sleeping, and then starting again without having fully documented what I did before the break.
[15:29] <geser> mok0: iirc no, as there is no safe way if the package supports build-arch and build-indep or not (if I remember the discussion on the debian-devel-ml correctly)
[15:30] <mok0> geser: Hm. I was trying to avoid my package doing a doxygen run when not building the -doc package.
[15:31] <geser> mok0: but I don't know if this also applies to the ubuntu buildds
[15:32] <mok0> geser: Maybe it's for a future/smarter implementation
[15:32] <geser> or all packages transition to build-arch/build-indep
[15:33] <soulrider> hello, im creating a deb file for sheepshaver. Im doing the checkinstall step now, but im not sure about what i should put in the group field, is it emulation?
[15:33] <mok0> geser: yeah thats what I meant
[15:33] <geser> !checkinstall
[15:33] <ubotu> checkinstall is a wrapper to "make install", useful for installing programs you compiled. It will create a .deb package, which will be listed in the APT database and can be uninstalled like other packages. See https://help.ubuntu.com/community/CheckInstall - Read the warnings at the top and bottom of that web page, and DO NOT interrupt CheckInstall while it's running!
[15:34] <geser> soulrider: checkinstall isn't liked here, so I don't know if somebody can help you
[15:34] <soulrider> geser, thatw iki page doesnt really answer my question. I need to know what the groups field is used for
[15:36] <geser> soulrider: I didn't used checkinstall yet, so I can't help you. sorry.
[15:37] <soulrider> but isnt the group field generic for all deb packages?
[15:37] <Hobbsee> soulrider: checkinstall isn't supported in here.
[15:37] <soulrider> i mean, all packages should have one
[15:37]  * Hobbsee would suggest trying the forums or something
[15:38] <soulrider> what other ways do i ahve to create a deb package?
[15:44] <LucidFox> soulrider> You can use dh_make on the source tree to "debianize" it
[15:45] <LucidFox> the result, however, will most probably involve manual tweaking
[15:45] <LucidFox> You can refer to the Ubuntu packaging guide: https://wiki.ubuntu.com/PackagingGuide
[16:00] <ScottK> \sh: The claws-mail sync was not a good idea it turns out.  "Removed sylpheed-claws-gtk2 dummy packages" - We need those for Dapper -> Hardy upgrades.
[16:00]  * ScottK just read about it on hardy-changes
[16:00] <\sh> ScottK, oh shit..
[16:00] <\sh> ScottK, hmmm..it conflicts/replaces now...
[16:01] <\sh> lemme check...
[16:01] <ScottK> But you need the transitional package.
[16:01] <ScottK> package/packages
[16:02] <\sh> ScottK, grmpf
[16:02] <\sh> I'll get it fixed...
[16:02] <\sh> damn...
[16:04] <ScottK> \sh: Thanks for taking care of it.  It's good to work with people who will clean up after themselves.
[16:04] <\sh> ScottK, well, this is one which can happen all the time, when you don't think about dapper -> hardy directly
[16:05] <ScottK> Sure.  We all miss stuff.  The goal isn't being perfect, but fixing up after.
[16:05] <\sh> at least I can blame myself...
[16:22] <\sh> ScottK, readding the trans packages from gutsy to new claws-mail
[16:23] <ScottK> Great.
[16:24] <ScottK> \sh: Once that's uploaded, I want to backport that to Gutsy and build it against the new libclamav3.  Would you be up for doing some testing?
[16:24] <\sh> ScottK, sure :)
[16:24] <\sh> ScottK, I'll have still my t43 on gutsy...
[16:25] <ScottK> Great.
[16:25] <\sh> ok 3.2.0-2ubuntu1 should hit the buildd soon
[16:27] <\sh> ScottK, do you know if vmware 1.0.4 is running on hardy?
[16:28] <ScottK> No.  I'd ask zul.
[16:29] <mok0> dholbach: ping
[16:29] <\sh> ScottK, I'll try it just now...
[16:29] <dholbach> mok0: pong
[16:29] <mok0> dholbach: looking at your mmdb review now.
[16:29] <mok0> dholbach: I can't reproduce the lintian warning
[16:30] <mok0> dholbach: Even installed hardy version
[16:30] <vemon> hi! i have a small problem with creating a patch. the autoconf version is different from what it was when the configure file was orignally written. now patch i created basically rewrites the whole configure file
[16:31] <dholbach> hm, weird - is the changelog a symlink in one of the resulting packages?
[16:31] <mok0> Yes I think there is some weirdness like that
[16:31] <mok0> It's a cdbs build
[16:31] <vemon> and i've only touched some source files and configure.in by hand
[16:31] <dholbach> ah, hmmm
[16:31] <vemon> so is there a "best practise" for a situation like this? :)
[16:32] <mok0> dholbach: The other point: our ftp server was down for a couple of days without my knowing it
[16:32] <dholbach> hehe :)
[16:32] <mok0> grrrrr
[16:33] <pochu> mok0: is that warning the 'changelog is a symlink' one? If so, ignore it. That's a hack in our cdbs so packages in the CD take less space
[16:33] <mok0> dholbach: we're in a process of moving all servers to virtual machines and it's a mess
[16:33] <dholbach> alright, nevermind then :)
[16:33] <norsetto> mok0: le baladin? You certainly know more about italian beers than I do
[16:34]  * dholbach hugs norsetto
[16:34] <mok0> pochu: No, it's " To refer to the changelog, copyright, and other documentation files of another package that this one depends on, please symlink the entire  /usr/share/doc/<pkg> directory rather than individual files."
[16:34] <mok0> ... and I don't know what it's thinking
[16:34] <emgent> jdstrand i'd like talk with you about a project that i like build for motu-swat and ubuntu-security
[16:35] <jdstrand> emgent: ok-- give me a sec...
[16:35] <emgent> sure
[16:35] <mok0> norsetto: did you google it?
[16:35] <norsetto> mok0: no
[16:35] <emgent> heya norsetto
[16:35] <norsetto> mok0: why, its a joke? ... oh well ....
[16:35] <pochu> mok0: sounds pretty similar, but I've never seen it.
[16:36] <norsetto> emgent: heya emgent
[16:36] <mok0> norsetto: nono, it's a real beer, but it's impossible to find
[16:37] <ScottK> leonel: Are you able to do some python-clamav testing in Dapper?
[16:37] <mok0> norsetto: I think I figured out the Build-Depends-Indep question
[16:37] <mok0> Fish?
[16:37] <norsetto> mok0: you mean is hand made in some small valley in the Alps by an handfull of desperate monks ?
[16:37] <mok0> norsetto: yep :-)
[16:37] <leonel> scottK Of course
[16:38] <mok0> norsetto: "if we can't have women, we can have BEER"
[16:38] <norsetto> mok0: I always have been ware of desperate monks
[16:38] <ScottK> leonel: It's up and built in the ubuntu-clamav ppa.  Please let me know how it works.
[16:38] <mok0> hehe
[16:38] <leonel> scottK just let me clear some todos
[16:38] <leonel> scottK ok  I'll do
[16:38] <ScottK> leonel: Making a later python-clamav work in Dapper is gonna be painful.
[16:38] <ScottK> leonel: No rush and please comment on the wiki after you test.
[16:38] <leonel> scottK OK
[16:39] <ScottK> Thanks
[16:40] <emgent> dholbach, there are some security tracker for ubuntu security people now ?
[16:40] <dholbach> emgent: I'm the wrong person for that question. keescook, jdstrand and \sh might know much better
[16:40] <emgent> ok, forward to \sh && jdstrand
[16:40] <emgent> :)
[16:41] <jdstrand> emgent: ok I'm back
[16:41] <jdstrand> dholbach: thanks
[16:41] <emgent> well jdstrand
[16:41] <jdstrand> emgent: yes we do have a tracker
[16:41] <dholbach> ROCK ON Security Team! :)
[16:41] <jdstrand> https://code.launchpad.net/ubuntu-cve-tracker
[16:41] <jdstrand> emgent: ^^
[16:42] <\sh> emgent, one of the things you should do is to join #debian-security on oftc, so you can see what debian unstable security maintainer are working on
[16:42] <emgent> uhm.. only for CVE
[16:42] <jdstrand> emgent: we are also working on an html report
[16:42] <\sh> emgent, the second is -> jdstrand
[16:42] <jdstrand> that pulls from ubuntu-cve-tracker
[16:42] <\sh> emgent, most likely CVEs are issues also for drupal security announcements
[16:42] <jdstrand> emgent: the branch to look at is 'master'
[16:43] <emgent> i'm thinking to develope a system to grep RSS title with ${ARRAY} (in array all packages name maintained in ubuntu)
[16:43] <emgent> RSS && mail object.
[16:43] <emgent> we can know all rumors and test/fix it first
[16:44] <jdstrand> emgent: you may want to look at what we have going in ubuntu-cve-tracker
[16:44] <jdstrand> there is a README that describes what scripts we have and the process, etc, etc
[16:45] <emgent> ok
[16:45] <jdstrand> emgent: it may or may not overlap with what you want to do
[16:45] <mok0> dholbach: I'll upload my latest version of mmdb, it may not have that lintian warning
[16:45] <dholbach> mok0: OK
[16:45] <emgent> thanks jdstrand && \sh
[16:46] <jdstrand> np
[16:46] <jdstrand> :)
[16:49] <norsetto> mok0: Ok, I'm glad you got that; in case you didn't do it I can suggest you also check the debian policy, its a godsend for this kind of things
[16:50] <mok0> norsetto: I find the information scattered all over that document...
[16:50] <mok0> norsetto: guess I need to memorize it...
[16:52] <norsetto> mok0: if you can memorise the debian policy I will buy you a le baladin
[16:52] <mok0> norsetto: now you're tightening your promises
[16:53] <norsetto> mok0: I'm, but you also need to memorise all the footnotes and appendices ...
[16:53] <\sh> do we have a 32bit libselinux somehow?
[16:53] <mok0> norsetto: hehe. Fortunately there is some logic to it
[16:53] <norsetto> mok0: and addendums, and the python policy, the new python policy and the new new python policy too ;-)
[16:54] <ScottK> Plus all the stuff that's no policy yet, but everyone knows you have to do.
[16:54] <mok0> norsetto: ... and the old because you have to recognize when people are using an out-of-date standard...
[16:54] <ScottK> no/not
[16:54] <mok0> norsetto: anyway, I omitted the .la files from my other libraries in REVU
[16:54] <mok0> ... and added that -D_REENTRANT flag
[16:55]  * norsetto hugs mok0
[16:55] <mok0> norsetto: ... I assume it needs to go in CXXFLAGS as well
[16:55] <mok0> (if there is c++ code)
[16:55]  * norsetto also hopes that mok0 will one day stop fiddling with his own packages and start working on some of the universe ones .....
[16:56] <mok0> norsetto: I will
[16:56] <mok0> norsetto: but there are a few to go
[16:57] <norsetto> mok0: well, just stop writing code, a chemist writing code its ... a perversion ;-)
[16:57] <mok0> norsetto: Unfortunately, most of the software we use in crystallography is closed source. My aim is to package as much as possible of the free stuff, so people can start doing development in a  more reasonable setting
[16:58] <mok0> norsetto: It gets worse: I'm in a molecular biology department
[17:01] <mok0> norsetto: these libraries are all needed by a very popular program "coot" (bug 176211)
[17:01] <ubotu> Launchpad bug 176211 in ubuntu "[needs-packaging] coot" [Wishlist,Incomplete] https://launchpad.net/bugs/176211
[17:03] <norsetto> mok0: popular amongst the 3 or 4 mad molecular biologists in the known world you mean ....
[17:03] <mok0> norsetto: :-)
[17:04] <norsetto> mok0: which apparently have all gathered in your bug report :-)
[17:05] <mok0> norsetto: yeah, it's a conspiracy!
[17:07] <norsetto> mok0: considering what coot means in english I would rather call it something else ;-)
[17:07] <Amaranth> apachelogger: So how is Windows Live Writer?
[17:07] <apachelogger> Amaranth: ?
[17:07] <Amaranth> apachelogger: "Temporary-Post-Used-For-Style-Detection-Content-1776813585"
[17:07] <Amaranth> apachelogger: that was on your blog, it's a Windows Live Writer thing
[17:07] <apachelogger> Amaranth: kblogger-kde4 thingy ;-)
[17:08] <Amaranth> Wow, they picked a stupid thing to copy :P
[17:08] <Amaranth> People complain all the time about the crap polluting blogs
[17:08] <mok0> norsetto: Fortunately, I'm not the developer of that, only the packager
[17:09] <apachelogger> Amaranth: well, usually it is supposed to be a draft post
[17:09] <apachelogger> but there is an issue in the current api implimentation for blogger.com
[17:09] <apachelogger> so it got published
[17:09] <Amaranth> blogger doesn't have draft posts?
[17:09] <apachelogger> of course it does
[17:09] <apachelogger> blogger is just alphaware ;-)
[17:09] <apachelogger> *kblogger
[17:11] <LucidFox> dholbach> Sure, my application isn't a pressing issue to me, I can reapply later. Do I need to withdraw my current application?
[17:12] <dholbach> LucidFox: no... just follow up on it in a few weeks and that'll be fine
[17:12]  * dholbach hugs LucidFox
[17:12] <dholbach> thanks for asking
[17:12] <LucidFox> Ack.
[17:13] <dholbach> see you around
[17:13]  * dholbach calls it a day
[17:16] <RainCT> Hi
[17:18] <pochu> If I'm about to upload a package from REVU to the archive, how does the NEW mail sent to -motu works?
[17:18] <ScottK> \sh: I like reading hardy-changes much better now.
[17:18] <\sh> ScottK, hehe :)
[17:19] <\sh> ScottK, if something goes wrong, blame me ;)
[17:19] <ScottK> Of course.  You touched it last now.
[17:19] <\sh> and vmware is installed nicely and configure correctly...(with an fix for the vmware-any-any update) but starting vmware fails
[17:20] <mok0> norsetto: any further comments re: gpp4?
[17:20] <norsetto> mok0: as long as it builds and installs after the last change I'm still advocating you
[17:21] <mok0> norsetto: cool, thx.
[17:21] <\sh> RainCT, ping did you see my comment to your debdiff for motioneye?
[17:23] <pochu> Should I just forward the NEW message, appending REVU in the subject?
[17:23] <RainCT> \sh: yes, I'll upload a new debdiff right now :).
[17:24] <\sh> RainCT, cool...ping me and I'm happy to sponsor it :)
[17:24] <RainCT> \sh: I only develop with interpreted languages so I wasn't sure what was needed to be done there..
[17:25] <\sh> RainCT, well, I just rebuild the package without the tightend build-dep on imlib11-dev...to be sure that it works :)
[17:26] <RainCT> \sh: should the maintainer field be modified for the rebuild or just the changelog?
[17:26] <bddebian> Heya gang
[17:26] <geser> RainCT: as you are listed as a bug contact for ubuntu-dev-tools (and also worked on that package), what's your opinion to my requestsync-lp script from bug #147994?
[17:26] <geser> Hi bddebian
[17:26] <ubotu> Launchpad bug 147994 in ubuntu-dev-tools "requestsync should have a command line switch to use python-launchpad-bugs (instead of mailing)" [Wishlist,In progress] https://launchpad.net/bugs/147994
[17:26] <bddebian> Hi geser
[17:27] <\sh> RainCT, nope
[17:27] <geser> RainCT: should I include it in the package as an addtional script or try to merge it with requestsync?
[17:27] <RainCT> geser: I think it's a great idea :)
[17:28] <RainCT> geser: ah. I would prefer if they were merged, and had a command line switch and a global variable to choose what method you want
[17:28] <ScottK> But please don't change the default.
[17:29] <geser> RainCT: I'll see if I manage to merge it before FF
[17:31] <RainCT> btw, I have a script to check for reverse build dependencies ready (just the manpage is missing), but before I wanted to ask if I missed some existing solution to look for them
[17:31] <geser> RainCT: I know only of an wrapper around grep-dctrl for it
[17:32] <RainCT> geser: it's based upon that :)
[17:32] <RainCT> but with --help and some other option
[17:33] <geser> RainCT, ScottK: what's your opinion on making 'hardy' the default 'target release' for requestsync when none is specified. I got lazy to type everytime 'hardy' when using requestsync. Is it a good idea?
[17:35] <ScottK> geser: I like the current way.
[17:36] <ScottK> Once hardy is released, it'll be wrong again.
[17:36] <RainCT> geser: perhaps add a global variable for this, too
[17:36]  * RainCT likes global vars :P
[17:36] <geser> ScottK: it still can be overridden on the commandline and one could backport a fixed ubuntu-dev-tools from hardy+1
[17:37] <ScottK> Could, but that's more maintenance work.
[17:37] <RainCT> then you will be able to just export what you want to be the default in .bashrc
[17:38] <geser> ScottK: ok, I'll will leave it as it is currently
[17:39] <\sh> hmm...Shared Folders from System/Administration/ doesn' work for me, can somebody confirm this?
[17:40] <RainCT> \sh: debdiff uploaded
[17:40] <\sh> RainCT, cool thx
[17:43] <\sh> RainCT, uploaded thx :)
[17:43] <RainCT> \sh: thanks :)
[18:03] <DarkSun88> Hi all
[18:05] <norsetto> Hola darksun88
[18:06] <DarkSun88>   Hola norsetto :)
[18:09] <frafu> persia: ping
[18:14] <frafu> persia: In the following review on revu http://revu.tauware.de/details.py?package=mousetweaks you told me to differentiate minus and hyphen.Do you know where I can find any documentation about where to put a minus and where to put a hyphen?
[18:18] <\sh> how correct are the informations on http://people.ubuntu.com/~ubuntu-archive/NBS/
[18:24] <RainCT> frafu: in most cases you will just want to use \-
[18:26] <RainCT> are there specifications (or whatever) for Nautilus' .hidden file somewhere?
[18:27] <\sh> if anyone has time..and knows about mozart language...mozart-gtk is not really FTBFS but gives me a parse error and doesn't stop my pbuilder ;)
[18:33] <afflux> hi
[18:35] <afflux> the zd1211 package is very old and doesn't work since gutsy. It was last updated in March 2006 and has been removed from debian last month. I think we should remove that too. Where should I bring this up?
[18:35] <ScottK> afflux: File a removal bug.  Details on what's needed are somewhere in the wiki.
[18:36] <afflux> I'll try, thanks
[18:37] <zul> besides zd1211 is supported by our kernel
[18:38] <afflux> the zd1211-source package doesn't compile with m-a
[18:38] <nxvl_work> scottK: how is that i see the karma scores of a team?
[18:39] <ScottK> Dunno.
[18:39] <nxvl_work> scottK: i mean a list with all the team members karmas
[18:39] <RainCT> Debian is removing ttf-bitstream-vera (switching to ttf-dejavu instead), but it doesn't make much sense to do the same in Hardy now, or?
[18:39]  * ScottK doesn't worry about karma.
[18:39] <ScottK> Oh.  Still dunno.
[18:41] <zul> afflux: it shouldnt
[18:59] <pitti> hello folks
[18:59] <pitti> according to https://wiki.ubuntu.com/MOTU/Packages/REVU I can ask here to get a reviewing account on REVU?
[19:00] <pitti> so far I managed to do reviews via mail, but I get more and more sponsorees and mentees, so it would be good if I could add comments directly there
[19:01] <ScottK> imbrandon: ping ^^^
[19:01] <mok0> pitti: I seem to remember I emailed someone to get an account
[19:02] <mok0> pitti: try emailing<EMAIL_ADDRESS>[19:04] <pitti> mok0: ok, will do
[19:08] <pitti> mailed
[19:08] <\sh> Lutin, ping why is dcc not on the dad merge list? but on m.u.c.?
[19:09] <afflux> zul: why shouldn't it? It is listed there.
[19:09] <zul> because it was probably synced from debian
[19:10] <Lutin> \sh: no clue
[19:10] <\sh> Lutin, it was a XbuildY revision...could you check for it? :)
[19:12] <Lutin> possible answer is that it moved to non-free, and I'm unsure whether dad checks it or not
[19:12] <sistpoty> hi folks
[19:13] <ScottK> sistpoty: Can you help pitti with getting a REVU account set up?
[19:13] <james_w> hi sistpoty
[19:13] <sistpoty> ScottK: sure
[19:13] <sistpoty> hi james_w
[19:13] <afflux> zul: i think so, but as I said, zd1211 was removed there and the zd1211 package in hardy, gutsy, feisty and edgy contains only the m-a package
[19:13] <ScottK> Great
[19:13] <pitti> ScottK, sistpoty: I just mailed siretart about it
[19:14] <sistpoty> pitti: ok, great :)
[19:14] <pitti> sistpoty: if you can do it right now and it's not much work, so much the better, of course
[19:14] <zul> afflux: great then follow the necessary steps to get it removed
[19:14] <sistpoty> pitti: sure, no problem
[19:14]  * pitti doesn't know the procedure, sorry
[19:16] <sistpoty> pitti: which email do you want (serves as your login then)
[19:17] <pitti> sistpoty<EMAIL_ADDRESS>is fine
[19:17] <sistpoty> pitti: heh, you already have an account (maybe siretart was faster *g*)
[19:18] <sistpoty> pitti: you can find out your password by logging in and entering no password
[19:18] <pitti> sistpoty: ah, great; thank you!
[19:18] <sistpoty> pitti: np... (and don't thank me, I did nothing *g+)
[19:19] <pitti> sistpoty: ah, that worked; hm, that account must be ancient, and I never actually used it :)
[19:19] <sistpoty> :)
[19:21] <afflux> the MOTU/Removal wikipage states that "Packages removed from Debian will eventually be automatically removed". So does that mean I don't need to take action?
[19:21] <afflux> (to get zd1211 removed)
[19:26] <leonel> ubuntu dapper   6.06.2 now ??
[19:27] <ScottK2> leonel: Yes
[19:27] <\sh> a call to dh_icons is already in place in latest cdbs right?
[19:27] <ScottK2> \sh: Yes
[19:27] <leonel> scottK  great ..
[19:27] <leonel> be back  got to go to pay  taxes ..
[19:39] <Adri2000> \sh: why would it appear on DaD? DaD only shows packages with ubuntu changes, and buildX version are supposed to contain no change except a changelog entry
[19:40] <\sh> Adri2000, but they are not synced automatically ... so they should be visible..
[19:41] <Adri2000> unless that changed, before DIF, buildX packages as synced just like the other packages which contain no changes
[19:41] <Adri2000> it's not really done "automatically", but at least they don't require a sync request
[19:41] <Adri2000> s/as synced/are synced/
[19:43] <\sh> Adri2000, they require a sync request now :)
[19:43] <Adri2000> yes, just like the thousands of packages we haven't modified, and which do not appear on MoM or DaD
[19:44] <\sh> Adri2000, when you check mom page...you see dcc was never touched before..the new version came from debian on 20071210 and DIF was 20071213 so there is a diff now between dad and mom
[19:48] <Adri2000> yes, DaD never takes buildX package, being before or after DIF
[19:50] <\sh> Adri2000, this will be fun :)
[19:52] <Adri2000> \sh: anyway DaD will be shut down soon, to concentrate work on MoM. so unless I manage to convince Keybuk to not take buildX in MoM, you'll still have them in the list :)
[19:53] <\sh> Adri2000, problem is after DIF we need those buildX stuff anyways...
[19:54] <ScottK> \sh: After DIF from that perspective you need everything
[19:54] <Adri2000> I don't agree. then why not also list the not modified at all packages?
[19:54]  * norsetto -> dinner
[19:56] <\sh> ScottK, what means everything? we need the never touched merges (with -XubuntuY) and during DIF hopefully all -XbuildY stuff will be automagically synced but after DIF you need the not catched -XbuildY packages to file sync reqs.
[19:57] <\sh> ScottK, like the one I mentioned...
[19:57] <ScottK> \sh: But that's equally of concern when any package gets update in Debian from -1 to -2
[19:58] <\sh> ScottK, then I don't understand MoMs logic...could be, that this package just is a corner case, because it was released 3 days before DIF...
[19:59] <james_w> sistpoty: ready to go?
[19:59] <sistpoty> james_w: one second...
[19:59] <ScottK> Sounds likely.
[20:03] <james_w> The MOTU school session is starting now in #ubuntu-classroom if anyone is interested.
[20:04] <geser> thanks for the reminder
[20:04] <slangasek> everything you wanted to know about making perfect library packages, that-a-way --->
[20:17] <bddebian> Doh
[20:20] <vemon> where is it defined how a debian source package is built?
[20:21] <vemon> i mean where does it say if ./configure or make should be run and when?
[20:26] <bddebian> I missed the start, what are we nm'ing?
[20:26] <slangasek> bddebian: http://www.potyra.de/library_packaging/example.c
[20:27] <bddebian> thx
[20:28] <RainCT> TheMuso: Hey. Can you merge my ubuntu-dev-tools branch into trunk please?
[20:30] <\sh> StevenK, why did you drop the build-dep on libfaad-dev from libquicktime?
[20:31] <StevenK> \sh: That's a hard question.
[20:31] <RainCT> Kmos: are you around? I've a problem with ddclient
[20:31] <\sh> StevenK, yeah...but I know gutsy is just too old to remember? ;)
[20:32] <StevenK> \sh: Right. :-)
[20:32] <\sh> StevenK, hmm...if I knew this answer I could try to build the debian version and sync it, instead of merging it ;)
[20:33] <StevenK> \sh: Could it be main versus multiverse, or so?
[20:33] <\sh> StevenK, well...now it's universe vs. universe ,-)
[20:33] <\sh> but I remember libquicktime was in main during some releases
[20:34] <geser> faad2 was in multiverse till the sync
[20:34] <\sh> geser, ah ok :) now it's in universe and hopefully we can sync the lib
[20:58] <leonel> scottK  removing  libclamav1  from dapper  automagically  installs libclamav2  from ppa     Nice
[21:20] <ScottK> leonel: Are you getting libclamav2 or 3?
[21:21] <leonel> scottK  clamav-base libclamav3 clamav-freshclam clamav-daemon
[21:22] <ScottK> OK.  3 is good.  2 would have been bad.
[21:32] <leonel> scottK libclamav3 installs fine  but  clamav-base  has that error
[21:33] <ScottK> leonel: OK.  I'll look into that.
[21:33] <ScottK> Thanks.
[21:37] <gu_> hi
[21:47] <somerville32> ScottK, Those security uploads haven't been sponsored yet. Should I bug someone about that?
[21:47] <ScottK> leonel: Try to purge clamav-base and install again.  Looking at the clamav-0.92 source package, that template is correct.
[21:47] <ScottK> somerville32: You might ping keescook or jdstrand
[21:47] <ScottK> Of course I just did that...
[21:47] <somerville32> :)
[21:48] <jdstrand> somerville32: which updates?
[21:48] <somerville32> syslog-ng
[21:48] <jdstrand> somerville32: what is the bug #?
[21:49] <jdstrand> or is there not one yet?
[21:49]  * somerville32 is looking.
[21:49] <somerville32> bug #183389
[21:49] <ubotu> Launchpad bug 183389 in syslog-ng "[SECURITY] CVE-2007-6437 prone to denial of service attack" [High,Confirmed] https://launchpad.net/bugs/183389
[21:50] <jdstrand> somerville32: cool and thanks for the debdiffs
[21:50] <somerville32> no problem
[21:50] <jdstrand> somerville32: these all build and have been tested on each release (and fix the problem)?
[21:51] <somerville32> jdstrand, They all build :)
[21:52] <TheMuso> RainCT: Has anybody merged your changes yet
[21:52] <leonel> scottK  purged  cleared  downladed debs  tried to reinstall
[21:52] <leonel> clamav-base template parse error: Template #1 in /tmp/clamav-base.template.53230 does not contain a 'Template:' line
[21:53] <jdstrand> somerville32: ok, I have a few sponsored items in my queue, but should be able to get to it tomorrow
[21:53] <ScottK> leonel: Thanks.
[21:55] <somerville32> jdstrand, Okay.
[21:55] <ScottK> leonel: I think it's a PPA bug as my locally built copy appears to have the template and the PPA version does not.
[21:56] <leonel> ok  so .. just wait  for ppa ?
[21:56] <ScottK> Let me look into it.
[22:04] <ScottK2> leonel: I take it back.  The problem also exists in my locally built copy.
[22:06] <mtp_> Is there any particular reason that my GPG has not been added to the REVU keychain yet? It's been part of the Launchpad group for a few days now.
[22:07] <ScottK2> Anyone: I've got a problem where building clamav against the Dapper toolchain results in an extra line at the start of the clamav-base.templates file.  Any suggestions on where to look to find the problem?  Same package built against Gutsy/Hardy doesn't have the problem.
[22:07] <joejaxx> is there anyway to get pbuilder-dist to accept regular pbuilder options? :)
[22:10] <joejaxx> i want to stop pbuilder-dist from deleting the build directory
[22:10] <joejaxx> :P
[22:11] <ScottK2> leonel: Thanks for finding that.  Now that I've reproduced it locally, I'm working on it.  I'll let you know when it's fixed.
[22:12] <ScottK2> joejaxx: I think you want the login option then.
[22:12] <geser> joejaxx: pbuilder-${release} build --preserve-buildplace the.dsc doesn't work?
[22:12] <joejaxx> ScottK2: it seems pbuilder-dist does recognize the pbuilder options
[22:12] <joejaxx> unless i am incorrectly placing the options in the wrong order
[22:13] <joejaxx> geser: i will try that hold on
[22:14]  * ScottK2 has used login.
[22:16] <joejaxx> hmm
[22:16] <joejaxx> login does not seem like the option i want
[22:18] <ScottK2> Then try what geser said.
[22:18] <ScottK2> leonel: Fix uploading now.
[22:21] <ScottK2> leonel: Please keep an eye on https://launchpad.net/~ubuntu-clamav/+archive and when you see clamav_0.92~dfsg-2~dapper1~ppa3 is built, try again.
[22:23] <joejaxx> geser: that does not work for me
[22:23] <geser> hmm
[22:24] <joejaxx> well i am using pbuilder-dist hardy build [...]
[22:24] <sistpoty> gn8 everyone
[22:24] <joejaxx> Goodnight sistpoty
[22:25] <joejaxx> cp: cannot create regular file `/var/cache/pbuilder/build//etc/hosts': No such file or directory
[22:25] <joejaxx> works fine when i do not add the pbuilder opion
[22:25] <joejaxx> option
[22:25] <joejaxx> maybe i am adding it in the wrong place
[22:25] <matttp> Is there a particular reason that REVU claims ``No REVU account for<EMAIL_ADDRESS>exists yet.?''
[22:26] <matttp> I've had a LP account for a while with the correct groups with GPG key registered for a while now.
[22:26] <matttp> Have I missed something?
[22:26] <ScottK> matttp: Have you tried to upload yet?
[22:26] <geser> joejaxx: symlink pbuilder-dist to pbuilder-hardy and use it than like "pbuilder-hardy build ..."
[22:26] <matttp> ScottK: Yep. :-)
[22:26] <joejaxx> geser: yeap i was just about to see if that worked :P
[22:26] <ScottK> OK.
[22:26] <matttp> I see the file in ftp/incoming, but then it appears to be purged.
[22:26] <matttp> Purged after about ten minutes or so.
[22:26] <ScottK> We need a REVU admin then.
[22:27] <joejaxx> geser: actually i do not think this will work as i will still have to specify that i want to build for hardy
[22:27] <RainCT> TheMuso: no
[22:28] <ScottK> imbrandon: Are you around?
[22:28] <joejaxx> unless it looks at $0 after the dash for it
[22:29] <geser> joejaxx: I use a simpler version of pbuilder-dist and call it "pbuilder-hardy build the_package.dsc" for building or "pbuilder-hardy update --autocleanaptcache" for upgrading
[22:29] <joejaxx> and it does :D
[22:29] <joejaxx> as i suspected
[22:30] <joejaxx> pbuilder looks at echo $0 | cut -f 2 -d '-' :P
[22:30] <joejaxx> ok
[22:30] <joejaxx> bah
[22:30] <joejaxx> that does the same thing
[22:30]  * ScottK2 waits for the ppa buildd to catch up.
[22:51] <Frimost> hi, I have uploaded my first package to REVU put it doesn't appear in the webpage for review and my account it's created either.
[22:51] <Frimost> can someone help me?
[22:55] <TheMuso> RainCT: Ok, will do it later. Got to go out now
[22:55] <RainCT> TheMuso: okay, thanks
[22:55] <ScottK> Frimost: How long did you wait to see it show up?
[22:56] <Frimost> scottK: I uploaded it a couple days ago and today reuploaded it
[22:56] <RainCT> good night
[22:57] <ScottK> Frimost: You need a REVU admin then.  I don't think any are around at the moment.
[22:57] <Frimost> today dput say me that the package was already there and I have force the upload
[22:57] <Frimost> ok,  thanks
[22:58] <ScottK> Frimost: That's because you have a .upload file in the local directory.  Remove that and try again.
[23:00] <emgent> hello people
[23:01] <Frimost> it's seem that my second upload worked! :)
[23:02] <emgent> lol
[23:20] <matttp> Is there a proper IRC channel for me to use if I want to modify packages in main as opposed to universe/multiverse?
[23:21] <ScottK> #ubuntu=devel probably
[23:23] <soren> #ubuntu-devel, even.
[23:23] <ScottK> Right
[23:23] <persia> nxvl_work: Re: bug #178046.  While I still don't like the solution from Debian, please edit this bug description to reflect the sync request.
[23:23] <ubotu> Launchpad bug 178046 in dillo "dillo failed to unpatch" [Undecided,Confirmed] https://launchpad.net/bugs/178046
[23:25] <nxvl_work> persia: the sync request is already reported
[23:26] <persia> nxvl_work: In a different bug?  Please reuse bugs when you can to maintain the subscriber list and reduce bug churn.
[23:26] <nxvl_work> Bug #183606
[23:26] <ubotu> Launchpad bug 183606 in dillo "Please sync dillo 0.8.6-1 (universe) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/183606
[23:26] <nxvl_work> persia: i wan't the reporter
[23:27] <persia> nxvl_work: Ah.  That makes more sense.  I guess 178046 is just a dup now then.  Thanks for the clarification.
[23:28]  * persia is again unhappy with requestsync for generating useless new bugs when there are already work-in-progress developer bugs for the same issue
[23:38] <nxvl_work> persia: have you look at the NEW debian solution?
[23:39] <nxvl_work> persia: i haven't say anything, wrong bug and package :P
[23:39] <nxvl_work> persia: for dillo is the same :P
[23:48] <yamal> what causes error msgs like "dpkg-source: warning: ignoring deletion of file <filename>"?
[23:48] <yamal> happens when doing «dpkg-buildpackage -S -sa -rfakeroot»
[23:48] <mok0> It means you have deleted a file in the local copy of the sources
[23:49]  * yamal needs more sleep
[23:49] <yamal> thanks mok0
[23:49] <mok0> np
[23:58] <imbrandon> ScottK: yup
[23:58] <imbrandon> wasup?
[23:59] <ScottK> imbrandon: matttp is having REVU troubles.
[23:59] <imbrandon> yup, fixing him up now
[23:59] <ScottK> Great
[23:59] <imbrandon> looks like it needs a keysync and him to reupload
[23:59]  * imbrandon is doing so


[18:43] <robru> xnox, what's the deal with libpinyin4? i can't install it (even with -proposed enabled)
[18:44] <infinity> robru: Looks installible here.  Unless you mean in conjunction with what you already have installed?
[18:45] <infinity> robru: It breaks libpinyin2, so you'd need to wait for the transition to be complete there.
[18:45] <robru> infinity, well I have a freshly flashed mako with image 28. libpinyin4 is literally the first thing i'm trying to install. just says 'E: Package 'libpinyin4' has no installation candidate'
[18:46] <infinity> Oh, no installation candidate means it's not in your sources...
[18:47] <infinity> apt-get update? :P
[18:47] <robru> $ grep proposed /etc/apt/sources.list
[18:47] <robru> deb http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed main restricted
[18:47] <robru> deb-src http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed main restricted
[18:47] <robru> I updated 5 times trying to fix this!
[18:47] <infinity> It's probably in universe.
[18:47] <robru> ah
[18:47] <infinity> Which it likely shouldn't be.  I'll check and fix.
[18:48] <infinity> But for now, sed -i -e 's/main/main universe/' /etc/apt/sources.list && apt-get update
[18:48] <infinity> Err, no, it really should be in universe.
[18:48] <infinity> (And is)
[18:58] <robru> infinity, ok, got it, thanks.
[19:02] <xnox> infinity: ubuntu-keyboard is the last one that didn't transition to libpinyin4, i've ported it to libpinyin4 and it's been merged into lp:ubuntu-keyboard. this the 3rd time i'm being pinged about "libpinyin4" is not installable.
[19:02] <infinity> xnox: I guess archive components are a hard concept? :)
[19:03] <xnox> infinity: who knew?! =) i was asked about them at the interview.... granted i was interviewed by cjwatson  / slangasek.
[19:06] <slangasek> hmm
[19:07] <slangasek> robru: why are you installing from -proposed?  hopefully only for test builds, and not on your actual system
[19:34] <robru> slangasek, yeah, i'm testing the next version of ubuntu-keyboard and it has a hard dep on a version of libpinyin that is only in -proposed.
[19:35] <robru> slangasek, testing on my mako i mean, not on my laptop.
[19:35] <slangasek> robru: ok :)
[19:41] <robru> xnox, the error message is not exactly helpful.
[19:59] <xnox> robru: what can i say =) i didn't write apt =)
[19:59] <robru> xnox, WELL MAYBE YOU SHOULD HAVE THOUGHT OF THAT 20 YEARS AGO, HUH!?!?!?!
[19:59] <robru> ;-)
[20:00] <robru> xnox, yeah, dunno. i just woke this morning with instructions to test the new ubuntu-keyboard, which was tricky to install. had no idea you'd been pinged previously
[20:14] <infinity> robru: I'm not sure how the error message could be more helpful.
[20:14] <infinity> robru: It can't tell you about packaged it doesn't know about.
[20:14] <infinity> s/packaged/packages/
[20:15] <robru> infinity, it might say 'Perhaps this package is from universe?' or it might say 'check your archive components' or something. 'not installable' when i can see the package is in -proposed and i can see -proposed is in my sources.list is unhelpful and infuriating
[20:15] <infinity> robru: And if you ask for a package that just doesn't exist, that error becomes more unhelpful than the current one.
[20:16] <infinity> (Which is probably the usual cause of it appearing for normal people)
[20:16] <robru> infinity, when a website is down and you try to load it in firefox, it lists possible reasons. 'this site might be down, your connection might be broken / etc'. apt could easily do something similar.
[20:17] <infinity> (There are also things that, for better or worse, parse that output and act on it)
[20:18] <infinity> I'm dubious that the set of "people who know what an archive component is" and "people who don't know that apt can't see packages it can't see" has much overlap.
[20:19] <infinity> And spelling it out for users who don't know what a component is doesn't seem like a sane thing to put in a terse terminal error message.
[21:26] <ScottK> infinity: "There's a problem, and if you haven't figured it out, you're too stupid to understand the explanation.  Have a nice day."


[02:23] <Hilikus> after updating ubuntu, when i start mythfrontend it askis for the first-time configuration. how can i make it recognize the old config? the mysql table mythconverge is still there AFAICS