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