[06:18] <hyperair> hmm my universe contributor membership is about to expire. i wonder if i should renew it..
[06:35] <persia> hyperair: Do you currently have membership another way?  If so, it's not so important.
[06:35] <hyperair> persia: well i'm a MOTU.
[06:36] <persia> That's kinda what I was thinking.  Since you have indirect membership, do you care if you also have direct membership?
[06:39] <hyperair> eh? direct membership to universe-contributors, you mean?
[06:40] <persia> Yes.
[06:40] <hyperair> hmm i guess it doesn't matter then
[06:40]  * hyperair didn't realize motu was a member of universe-contributors
[06:40] <persia> Unless I made a mistake, MOTU is a member of universe-contributors, which means that as long as you are maintaining MOTU, you're a Universe Contributor regardless of whether you renew.
[06:41] <hyperair> i see
[06:41] <hyperair> alright, i'll let it expire then
[07:10] <ricotz> hyperair, hello :)
[07:11] <hyperair> ricotz: hi :)
[07:11] <ricotz> hyperair, do you want to upload/sponsor two packages?
[07:13] <ricotz> hyperair, http://people.ubuntu.com/~ricotz/mutter+g-s/
[07:14] <hyperair> ricotz: maybe later.
[07:14]  * hyperair is at work
[07:15] <ricotz> hyperair, ok, no problem
[07:16] <hyperair> ricotz: (i.e. remind me after 10:00 UTC)
[07:17] <ricotz> hyperair, ok, i will try in 4 hours
[11:39] <Laney> bdrung_: looks like packaging-dev is being well received :-)
[11:39] <Laney> do you imagine including a setup-packaging-environment style script in there?
[12:25] <chrisccoulson> who looks after the moonlight package?
[12:26] <persia> chrisccoulson: Check the changelog for the unfortunate who touched it last, but it's mostly handled by the Debian Mono team.
[12:27] <chrisccoulson> i touched it last ;)
[12:27] <persia> The you look after it :)
[12:27] <chrisccoulson> lol
[12:27] <chrisccoulson> that's not the answer i was hoping for ;)
[12:29] <persia> Honestly, if you don't want to own it as TIL, coordinate with the Debian Mono team.
[12:29] <persia> A large number of the members are also Ubuntu Developers: you ought be received well.
[12:41] <ricotz> bigon, ping
[12:42] <Laney> chrisccoulson: directhex
[12:43] <Laney> but he is away for a week or so more
[12:45] <bigon> ricotz: yes
[12:45] <ricotz> bigon, hi
[12:45] <bigon> hi
[12:46] <ricotz> bigon, i wanted to ask if you could upload mutter + gnome-shell, but hyperair just arrived ;)
[12:46] <hyperair> hahah
[12:46] <ricotz> could you upload mutter - gnome-shell
[12:46] <ricotz> oops
[12:46] <ricotz> http://people.ubuntu.com/~ricotz/mutter+g-s/
[12:47] <ricotz> hyperair, so you are going to? :P , bigon might have more insights here
[12:52] <hyperair> ricotz: then let bigon do it. =)
[12:53] <bigon> ricotz: why did you modify libxfixes-dev B_D version?
[12:54] <ricotz> bigon, because it isnt available in oneiric yet
[12:54] <bigon> well
[12:55] <ricotz> bigon, thanks for taking care of :)
[12:55] <bigon> that will probably tonight or during the weekend :)
[12:56] <bigon> ricotz: but for libxfixes I would wait til the package is updated
[12:56] <bigon> in oneiric
[12:56] <ricotz> bigon, hmm
[12:56] <ricotz> bigon, it isnt needed
[12:56] <bigon> let's me ask to fredp
[12:56] <ricotz> the xserver isnt even patched
[12:57] <ricotz> bigon, it is only needed for pointer barriers which is only in xserver master
[12:57] <bigon> oh ok
[12:57] <ricotz> bigon, the mutter package is just a uupdate and gnome-shell quite a sync
[13:00] <ricotz> bigon, could you upload them, please?
[13:01] <bigon> did you tests the packages?
[13:01] <Laney> are you talking about debian uploads?
[13:02] <ricotz> bigon, yes
[13:02] <bigon> Laney: ubuntu universe
[13:02] <ricotz> Laney, hi, no, about oneiric uploads
[13:03] <Laney> ah ok
[13:03] <bigon> I guess we should also ask archive admin to remove blacklist for gnome-shell
[13:03] <bigon> didrocks: ^
[13:04] <cjwatson> if a blacklist entry should be removed, somebody should file a bug with the details
[13:04] <cjwatson> (blacklisted in response to bug 690045)
[13:05] <bigon> cjwatson: ok I'm doing that
[13:05] <bigon> blacklist doesn't prevent manual upload in the archive right?
[13:06] <Laney> correct
[13:06] <ricotz> bigon, thank you
[13:06] <bigon> ricotz: I'm thinking about updating the packages in debian before
[13:06] <cjwatson> bigon: no, but don't work around blacklists with manual uploads (especially not ones that would be identical to Debian)
[13:07] <cjwatson> even if the upload isn't identical to Debian, sync-blacklist entries inhibit merge-o-matic from processing the package
[13:07] <bigon> cjwatson: ok so 1st removal of blacklist and then upload
[13:07] <cjwatson> yes
[13:07] <ricotz> bigon, ok
[13:13] <bigon> ricotz: in debian/changelog of gnome-shell you are talking about a merge, this is not strictly correct </pedantic>
[13:16] <ricotz> bigon, hmm, how would you call it?
[13:17] <ricotz> in this case probably just strip this line?
[13:20] <bigon> yep
[13:22] <bigon> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/789106
[13:34] <Laney> ScottK: Did I remember to sign your key?
[14:22] <artfwo> the versioned copyright format url no longer seems to work: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=REVISION
[14:22] <artfwo> where can i look for the latest dep-5 and how to link to it?
[14:30] <artfwo> ah, it's http://www.debian.org/doc/copyright-format/1.0 now
[14:32] <jtaylor> mdeslaur: concerning SRU bug 774265, maybe it should be postponed
[14:32] <jtaylor> mdeslaur: bug 786134 also affects meld git HEAD and may be related to the fix
[14:34] <mdeslaur> jtaylor: hmm...ok, I'll get it removed from -proposed. Thanks!
[14:35] <jtaylor> mdeslaur: thx, sry I didn't see that earlier
[14:36] <jtaylor> unfortunate that a development release landed in natty ..
[14:36] <jtaylor> I wonder what the rational was
[14:37] <mdeslaur> :(
[14:45] <jtaylor> urg it also affects the stable release 1.4
[15:06] <jtaylor> mdeslaur: the bug is unrelated to the other fix, but as it affects git HEAD it may take a while until it is fixed as it needs to get released first
[15:06] <jtaylor> mdeslaur: don't know if it should hold up the other fix
[15:07] <mdeslaur> jtaylor: so they're unrelated?
[15:07] <mdeslaur> jtaylor: ok, I'll push it through
[15:07] <jtaylor> as far as I can tell, but maybe we should wait for an upstream reply
[15:08] <jtaylor> but bisecting shows it was introduced in a completely other place much much earlier
[15:09] <jtaylor> I can also fix it with a hack without reintroducing the other hang bug
[15:10] <mdeslaur> jtaylor: I've already asked the SRU team to cancel my upload, so let's wait until a complete fix is available for both issues before sending it back to -proposed
[15:10] <jtaylor> k
[15:29] <nigelb> mdeslaur: hey
[15:29] <mdeslaur> nigelb: hi
[15:29] <nigelb> mdeslaur: Did redis build for you? Daviey and I noticed an interesting problem last night.
[15:29] <nigelb> mdeslaur: It built for me, but not for him.
[15:29] <mdeslaur> yeah, it did
[15:30] <nigelb> w00t
[15:30] <mdeslaur> let's see if the builders like it :)
[15:30] <nigelb> :)
[15:32] <achiang> fta: i see you uploaded a new version of chromium to Lucid... but there's no armel build? https://launchpad.net/ubuntu/lucid/+source/chromium-browser/11.0.696.71~r86024-0ubuntu0.10.04.1
[15:34] <Daviey> mdeslaur, Interesting... i was getting a rouge $ARCH thrown into some of the build lines, causing it to fail.
[15:34] <bdrung_> Laney: the responses were either positive or neutral. I think it's better to have setup-packaging-environment in one of the dependencies
[15:35] <nigelb> Daviey: just checked LP build logs. That doesn't seem to happen on LP.
[15:36] <nigelb> https://launchpadlibrarian.net/72523812/buildlog_ubuntu-oneiric-i386.redis_2%3A2.2.5-1ubuntu1_BUILDING.txt.gz
[15:36] <mdeslaur> Daviey: huh...were you trying in schroot or pbuilder?
[15:36] <Daviey> mdeslaur, i did that in pbuilder.
[15:36] <Daviey> i'll try again in schroot just for giggles.
[15:36]  * mdeslaur likes giggling
[15:36] <nigelb> heh
[15:37] <nigelb> Daviey: I used pbuilder-dist. Now I'm really curious why your build failed :)
[15:37] <mdeslaur> oh, I also applied the patches before building
[15:37] <fta> achiang, you should ask micahg
[15:37] <mdeslaur> nigelb: your merge request didn't have patches applied
[15:38] <Daviey> mdeslaur, well i imagine your source package was patches unapplied.
[15:38]  * mdeslaur shakes fist at UDD patch confusion mess
[15:38] <nigelb> mdeslaur: oh?
[15:38] <achiang> micahg: oh you are right. sorry, i misread the debdiff
[15:38] <nigelb> mdeslaur: I thought patches were applied during the build
[15:38] <achiang> fta: ^^
[15:38] <mdeslaur> not with source format 3.0...they get applied when the package is unpacked
[15:39] <nigelb> oh, so I have to do a "quilt push -a" before I request merge?
[15:39] <mdeslaur> nigelb: well, it depends...there seems to be a lot of differing opinions on that
[15:40] <mdeslaur> some repos have patches applied, some have patches unapplied, and some have patches applied but the .pc directory deleted
[15:40] <mdeslaur> (which is completely insane, IMHO)
[15:40] <nigelb> So this is not Right Way (tm)?
[15:40] <mdeslaur> nigelb: I think the Right Way(tm) is still up for debate
[15:41] <mdeslaur> unless it's been solved and nobody's told me
[15:41] <nigelb> heh, I'm a bit rusty. I did what I used to do in Lucid cycle when source format 3.0 was really new :)
[15:41] <Daviey> nigelb, as mdeslaur is saying, it's not a well polished machine :)
[15:41] <mdeslaur> nigelb: essentially, when I check out source, I check to see if patches are applied or not, and then make sure I check it back in in the same state
[15:41] <Daviey> UDD mimics the output of dpkg-source -x *.dsc.
[15:42] <fta> achiang, sorry but i'm tired of armel, where i have no h/w to build and test on, and no one is helping either
[15:42] <Daviey> nigelb,  with 3.0 (quilt) packages the patches get applied with that command.  Other source formats don't do this.
[15:42] <nigelb> mdeslaur: so check if its applied and follow that pattern seems to be what to now? :)
[15:43] <nigelb> Daviey: I remember it being horribly confusing to the 'Right Way' back then :)
[15:43] <achiang> fta: sorry, i wasn't trying to ask you to do armel. i was apologizing for asking you incorrectly
[15:44] <mdeslaur> nigelb: I think so, yes
[15:44] <mdeslaur> nigelb: I'm about as far as can be from a reliable source on that matter though :P
[15:45] <fta> achiang, i still maintain chromium in +1 (oneiric) and in the 4 channels (ppas), but i gave up on the SRUs, hence micahg replaying my branches
[15:45] <fta> achiang, but dropping armel was not my choice
[15:45] <nigelb> mdeslaur: heh :)
[15:46] <achiang> fta: understood, thank you
[15:48] <fta> achiang, i meant to blog about this, but every time i tried, the conclusion was me retiring from ubuntu
[15:49] <achiang> fta: not trying to cause you any angst this morning
[15:50] <fta> achiang, no harm done (and it's 5pm here)
[15:54] <nigelb> mdeslaur: phew, sucessfully built on i386 and amd64. I'm happy :)
[15:54] <nigelb> Daviey: that string you were getting doesn't seem to happening on builders. Something's b0rked on your builder :P
[15:55] <Daviey> bah
[15:55] <mdeslaur> nigelb: ah, cool :)
[16:33] <nigelb> Any suggestions on where to start looking for fixing the --as-need change in packages using automake?
[16:43] <ScottK> Laney: I don't think so.  I don't think I did yours either.
[17:04] <Laney> ScottK: there, done
[17:04] <ScottK> Thanks.
[17:04] <Laney> np
[17:19] <geser> nigelb: mostly likely Makefile.am (which is used to build the Makefile.in which is used to build the Makefile)
[17:19] <nigelb> geser: hrm. This is not easy :)
[17:20] <nigelb> I'm reading autotools manual to get a hang of how it works.
[17:20] <geser> nigelb: have you a specific FTBFS you are looking at?
[17:21] <nigelb> geser: yeah, timblserver. it seemed similar to what I'd done the other day with redis
[17:21] <nigelb> the autotools was a surprise :)
[17:21] <micahg> achiang: arm will come back for chromium, but it was holding up the i386 and amd64 builds, once we're pretty sure the build will succeed, I'll upload them in a new source.  ATM, no one has had a chance to look at the build failures, if you have time that would be great
[17:22] <jtaylor> nigelb: with autotools as-needed errors are often just libs in LDFLAGS instead of LDADD
[17:23] <nigelb> jtaylor: oh.
[17:24] <achiang> micahg: where are the FTBFS logs?
[17:28] <geser> nigelb: in the case of timblserver the bug seems to be in libtimbl which is missing a link to a library
[17:29] <micahg> achiang: well, oneiric has one, but I think that might be toolchain related, no proof though, the last one for arm is here: https://launchpad.net/ubuntu/+source/chromium-browser/11.0.696.57~r82915-0ubuntu0.10.04.1/+build/2463470, you'd probably be better off building the current source, just s/i386 amd64/armel/g in debian/control
[17:29] <nigelb> geser: libtimbl3-dev packages?
[17:29] <nigelb> *package
[17:30] <geser> yes, because of "/usr/lib/libtimbl.so: undefined reference to `GOMP_critical_end'" in the log for timblserver
[17:31] <nigelb> geser: ah. I've been staring at the wrong failure :)
[17:32] <geser> in this case I'm not sure myself in which package the linking error is: timbl or timblserver
[18:23] <pindonga> hi everyone, I'm one of the developers of configglue, which is already packaged on ubuntu (since lucid/maverick). I wanted to ask what's the best way to become the ubuntu maintainer for that package?
[18:36] <Ganseki> I've got a question about packaging. I just checked git and the debian/changelog doesn't have the distribution set, it's set for Debian standards. How does the build process know for what distro to build for?
[18:38] <jtaylor> pindonga: I'd say ask the current maintainers if you can help
[18:42] <jtaylor> Ganseki: locally it builds for whatever you (or your chroot) is running
[19:39] <achiang> micahg: trying a lucid build now