[06:48] <dholbach> good morning
[06:49] <geser> good morning dholbach
[06:49] <dholbach> hi geser
[06:51] <philipballew> evening all!
[07:38] <hrw> morning
[08:11] <hrw> question I have
[08:11] <hrw> W: armel-cross-toolchain-base source: debian-rules-missing-recommended-target build-arch
[08:11] <hrw> W: armel-cross-toolchain-base source: debian-rules-missing-recommended-target build-indep
[08:12] <hrw> armel-cross-toolchain-base builds both arch and indep packages in build: step and tehre is no way to build only indep ones (the order depends on arch ones). should I add build-arch: (same as build now) and build-indep: (same as build now) + build: build-arch build-indep?
[08:34] <tumbleweed> hrw: you could probably make build-arch and build-indep depend on build (as described in the long lintian info)
[08:35] <hrw> thx
[09:49] <jtaylor> when is the next sync going to be done? there is quite a large number of outstanding syncs
[09:49] <nigelb> I'm sure we're past Import Freeze
[09:49] <jtaylor> for confirmed sync requests
[09:49] <nigelb> ah
[09:50] <nigelb> You could probably poke someone on (https://wiki.ubuntu.com/ArchiveAdministration#Archive_days)
[09:54] <Laney> i suspect some of them are at debconf
[09:55] <nigelb> Ah, right, I forgot about that.
[09:55] <nigelb> Almost all of them are DDs too.
[09:55] <tumbleweed> certainly seen cjwatson around
[09:55] <Laney> you're in bl?
[09:55] <tumbleweed> yeah
[09:56] <Laney> jealous
[09:56] <nigelb> Me too.
[09:56] <Laney> yeah, but I turned down sponsorship :P
[09:56] <nigelb> er, I mean. I'm jealous too :D
[09:56] <nigelb> Laney: hah, then you can't say anything :P
[09:57] <Laney> I can weep at my foolish decision
[09:57] <tumbleweed> :)
[09:57]  * Rhonda peeks at Laney. Whom do you expect here?
[09:58] <Rhonda> Ah yes, vorlon and colin are here.
[09:58] <Laney> mmm
[09:58] <nigelb> vorlon?
[09:58] <Laney> steve
[09:58] <Rhonda> Steve
[09:58] <nigelb> ahhh
[09:59] <Rhonda> Langasek
[09:59] <Rhonda> No clue about the other Steve. :)
[10:00]  * Laney pinged kirkland and jdstrand
[10:00] <nigelb> and again here too...
[10:00] <Rhonda> I could ping vorlon and colin IRL if needed?
[10:06] <slangasek> what then?
[10:07] <slangasek> yeah, not going to have time for any batch processing of archive requests today, sorry
[10:07] <slangasek> if you have an urgent one point me at it and I *might* be able to take a look... but no promises
[10:08] <cjwatson> I can probably manage to do a bulk run
[10:09] <cjwatson> modulo networking
[10:09] <cjwatson> sigh, queue length 85
[10:09] <cjwatson> I'll do as many as I can
[10:09] <jtaylor> nothing urgent to my knowledge, I was just wondering when it would be done
[10:10] <jtaylor> only a question no request
[10:14] <cjwatson> hard to distinguish the two since people put both in the same form
[10:26] <bdrung> ScottK: i gave the maintenance to cdbs
[10:29] <Laney> cjwatson: maybe wait and see if the others volunteer?
[10:30] <Laney> I don't like overloading one person too much ...
[10:53] <ricotz> stgraber, hello :), i noticed some new version tags in ltsp, but there are no new releases, would you say the daily build ppa is usable for stable needs?
[11:08] <ScottK> cdbs: I was wondering if you might look into getting audacious-plugins to build. We need to rebuild it for the libmtp8 transition, but ld and it don't get along:
[11:08] <ScottK> /usr/bin/ld: /lib/i386-linux-gnu/libc.so.6: unexpected redefinition of indirect versioned symbol `nanosleep@GLIBC_2.0'
[11:08] <ScottK> /usr/bin/ld: vtx.o(.text+0x294): unresolvable R_386_PLT32 relocation against symbol `g_hook_insert_sorted'
[11:09] <ScottK> bdrung: OK.
[11:22] <jtaylor> gaa stupid xdotool testsuite failed on armel while it worked on debians builders
[11:26] <jtaylor> anyone have a working armel pbuilder? I can't get mine to work
[11:27] <geser> jtaylor: perhaps persia as he was working on the pbuilder support for armel in the past
[11:40] <ricotz> YokoZar, hi, could you upload the new wine in ppa for lucid too
[11:41] <YokoZar> ricotz: yeah in progress atm
[11:41] <ricotz> YokoZar, thanks
[12:08] <tumbleweed> jtaylor: always worked fine for me (but I've migrated to sbuild these days)
[12:09] <jtaylor> I can create and update it fine but I can't install or build any packages in it
[12:09] <tumbleweed> if you can update it, you should be able to build in it
[12:09] <tumbleweed> what's the error?
[12:10] <jtaylor> package does not exist, or is purely virtual
[12:11] <tumbleweed> during dependency installation? Does it have the correct apt sources?
[12:12] <jtaylor> hm sources should be http://ports.ubuntu.com?
[12:12] <tumbleweed> yes
[12:12] <jtaylor> thatrs probably the problem
[12:12] <jtaylor> I have archive in the source
[12:12] <jtaylor> but why does it update then :/
[12:15] <jtaylor> my pbuilderrc was screwing up
[12:15] <jtaylor> thx for the hint
[12:44] <persia> geser: THat's really all in qemu-deboostrap: the only pbuilder bit I did was to u-d-t's pbuilder-dist
[12:44] <persia> Someone (who uses pbuilder) ought look at getting that into pbuilder properly.
[12:45] <tumbleweed> jtaylor: was just looking at bug 801945 and got caught up in ubuntutools/builder.py. Two questions? Surely s/cowbuilderdist/cowbuilder-dist/. Any reason to separate name from command? (I'm adding detection for builders that aren't installed, rather than bailing out on an OSError
[12:49] <jtaylor> tumbleweed: yes its cowbuilder-dist
[12:50] <jtaylor> weird that got overlooked, a couple of people looked at that merge ^^
[12:51] <jtaylor> I don't recall a reason for seperating it, I think I just wanted to keep the changes minimal
[12:57] <tumbleweed> jtaylor: ok, I'll use name instead of command then
[13:00] <stgraber> ricotz: the reason I didn't upload anything to oneiric yet is that it won't boot anyway :) I need to fix nbd-server first to make LTSP bootable on oneiric again.
[13:23] <Raffa50> hello
[13:23] <Raffa50> i have registred my pgp key
[13:23] <Raffa50> but i can't uload
[13:24] <Raffa50> it say that a file .sig is missing
[13:26] <Raffa50> can anyone help me in submitting my software?
[13:33] <Raffa55> hello
[13:34] <Raffa55> i'm trying to upload my app to the ubuntu software center
[13:34] <Raffa55> i runned
[13:34] <Raffa55> dput revu sly3.changes
[13:34] <Raffa55> but it says that i need a .sig file
[13:34] <Raffa55> how can i do
[13:34] <Raffa55> ??
[13:35] <jtaylor> did you sign the changes it with debsign?
[13:35] <jtaylor> debuild should do that for you
[13:50] <paultag> if it can't find you key because you have a comment on the key, or if the email (for some reason) is not your DEBEMAIL, you can give it -kKEYID (where KEYID is the short-fingerprint of the key)
[13:50] <paultag> Raffa55: ^
[13:52] <ricotz> stgraber, alright, actually i was hoping for an updated lucid version -- maybe a stable ppa is useful if the dailies are too risky
[13:59] <slangasek> dupondje: why did you request gawk to be synced?  You've now caused a component-mismatch as the new version has a build-dependency on a library that the old version did not, and AFAICS you haven't in the process fixed any bugs that were troubling anyone using Ubuntu
[14:02] <jtaylor> where are coredumps placed which apt/dpkg create?
[14:02] <jtaylor> libgvc5 segfaults on installation on armel
[14:07] <Daviey> slangasek: I can't see that dupondje did the sync?
[14:07] <stgraber> ricotz: AFAIK the dailies won't boot on lucid either (although they do build) because of a udhcp bug affecting lucid in the current trunk branch.
[14:08] <Laney> Daviey: https://bugs.launchpad.net/ubuntu/+source/gawk/+bug/588828/comments/3
[14:09] <Laney> yes, it did have to be acked by a sponsor too
[14:10] <slangasek> Daviey: dupondje requested it
[14:14] <Daviey> slangasek: Looks like dupondje essentially just commented on that bug, it was a sponsored sync. bug #588828
[14:15] <slangasek> Daviey: it was dupondje that requested the sync of the sponsors
[14:17] <Daviey> slangasek: ah
[14:17] <dupondje> slangasek: The initial bug was a request to upgrade to 3.1.8. As that version got into debian, it looked safe to sync. Didn't notice the new bd was in universe.
[14:18] <ricotz> stgraber, ok, i will wait then ;)
[14:18]  * Daviey thinks ack-sync could warn of this.
[14:18] <slangasek> dupondje: "looked safe to sync" is not a good reason to make exceptions to the Debian Import Freeze; please focus on syncs that actually address bugs in Ubuntu
[14:19] <slangasek> dupondje: I've assigned bug #815918 to you now, please complete the MIR :)
[14:20] <Daviey> slangasek: Can i assign get the defintion of Debian Import Freeze made cleaer? :)
[14:21]  * slangasek sighs
[14:21] <dupondje> slangasek: https://bugs.launchpad.net/ubuntu/+source/gawk/+bug/588828/comments/2 was for example also a reason to get the new version.
[14:21] <dupondje> But i'll fix the MIR
[14:21] <Daviey> https://wiki.ubuntu.com/DebianImportFreeze <-- It does *not* suggest syncs that resolve issues only.
[14:22] <slangasek> dupondje: ah, that's true; regardless, we need to sort out the build-deps now, so thank you for following up there :)
[14:48] <Laney> dholbach: can you follow up on -devel about the genesis of UCD? You were involved in its creation IIRC.
[14:49] <dholbach> you mean the name?
[14:49] <Laney> like why is it a separate thing
[14:49] <Laney> separate from ~ubuntumembers
[14:50] <dholbach> it's what other governance boards do as well: there's ~{kubuntu,edubuntu,ubuntu-irc,ubuntu-forums}members
[14:50] <dholbach> (the actual team names are a bit different though, I think)
[14:51] <dholbach> while all of these teams are part of ubuntumembers, they are separate because some governance boards might grant additional rights at some stage (ie: commit rights, voting rights, etc.)
[14:51] <dholbach> I still think that's a good idea, but I agree that the name is misleading :/
[14:53] <Laney> I wouldn't mind if we renamed it to Ubuntu Development Members
[14:53] <Laney> but yeah, please clarify this on the list :-)
[14:54] <Daviey> ~ubuntu-dev is essentially Ubuntu Development Members, anyway?
[14:54] <Laney> no
[14:54] <Daviey> oh?
[14:54] <Laney> that grants a load of extra team memberships
[14:54] <Laney> and voting rights
[15:01] <Laney> I'm adding that rename to the agenda
[15:01] <dholbach> Laney, done
[15:01] <Laney> thanks
[15:11]  * Laney tried to make UbuntuDevelopers a bit clearer around prospective/contributing
[15:34] <persia> Laney: I'm a bit attached to the idea that the contrinbyting developers are collectively responsible for the archive, rather than some narrower team.
[15:35] <persia> THat said, I am *very* attached to the idea that "Ubuntu Developers" are all the developers, and cover the entire archive.  That we insist that all packageset teams include core-dev as a member is an artifact of our current strategy, and may not continue to be true if anyone ever decides to implement a restricted packageset.
[15:35] <persia> So "
[15:36] <persia> So "Are collectively responsible for some subset of packages in Ubuntu" is disturbing to me.
[15:37] <persia> I'm also uncomfortable with "are collectively responsible for the maintenance of packages in the universe and multiverse components".  That's a filed bug in Soyuz, and not intended to remain true in any way.
[15:40] <Laney> reponsibility> It's unclear to me what that responsibility entails in practice, and I'm not sure what a similar analog would be for other forms of membership. I also don't know why becoming UCD would place any more burden on anyones shoulders that they did not have before.
[15:41] <Laney> So I guess that's your second remark — I'd be in favour of saying that /all/ developers are responsible for /all/ packages, not just the ones they can upload.
[15:41] <Laney> components> yes, the document already mentioned them and that section should be reworded (perhaps once the permissions model is fixed)
[15:42] <jtaylor> can someone rebuild matplotlib on armel? the buildlog does not indicate any problem with the package
[15:42] <jtaylor> maybe the archive was in a bad state at that time?
[15:42] <jtaylor> my chroot does not work as it crashes n graphviz installation, would be good to see if the same happens in the buildd
[15:44] <Laney> developers (even those who consider themselves prospective developers)
[15:44] <Daviey> jtaylor: given back.
[15:44] <jtaylor> thx
[16:00] <oier> hi, could some motu-dev please review my package 'indicator-bug' at http://revu.ubuntuwire.com/details.py?upid=9151 ? I already have one advocate and I am looking for a second one
[16:02] <oier> it's a fairly simple python indicator which displays a list of bugs for launchpad projects depending on the bug preferences
[16:03] <oier> updates the list and notifies if there are new bugs which match the given search preferences (for example bugs that are tagged as bitesize)
[16:04] <persia> Laney: I'm happy with all developers being responsible for everything, regardless of upload rights.  My concern is mostly about not wanting to block people from a sense of caring for a package just because they don't (yet) have upload rights.
[16:04] <oier> so if somebody could help reviewing and uploading it I would be very grateful
[16:05] <persia> My desire when drafting the UCD text was that people applying for UCD would be willing to assert that they explicitly intended to accept responsibility for the packages.  In practice, I'm not sure that really worked the way I'd hoped.
[16:07] <persia> On components, I'm happy to leave some text there until we fix Soyuz: my main fear is that folk are likely to be confused when they lose upload rights (unless they join appropriate teams), but I suspect that we need to take care to communicate that clearly *anyway* and the text on that wiki page doesn't matter as much.
[17:19] <hakermania> My application compiles at 11.10 fine but not in 11.04 (in purpose). So, does this mean that I have to package my application to 11.10 and send it to revu, right?
[17:56] <hakermania> thanks for the helpful answers after 25 mins :D
[18:26] <maddagaska> Hi. If creating a package containing a web site, what would be the correct path to place its files in? Judging by FHS, it should go in one of /opt or /usr/local, but lintian produces errors for both those directories.
[18:32] <Daviey> maddagaska: normally, /usr/share/ .. but i assume the website is static?
[18:32] <Daviey> or rather, doesn't need editing.
[18:32] <maddagaska> Daviey: That's correct.
[18:33] <maddagaska> So in that case, /usr/share is best?
[18:34] <maddagaska> Much better output on Lintian with that- thanks!
[18:34] <Daviey> maddagaska: groovy.
[18:38] <maddagaska> And with that done, I'll fix permissions tomorrow- thanks again, Daviey.
[22:57] <jtaylor> why is transmission in dependency wait status? it builds fine in my chroot
[22:57] <jtaylor> does it need manual intervention?
[22:57] <micahg> jtaylor: needs MIRs
[22:58] <jtaylor> mir?
[22:58] <micahg> !mir | jtaylor
[22:59] <jtaylor> k
[23:05] <jariq> my package ipwatchd is already in universe and I've updated package in debian sid today.. is there anything I need to do to sync new version from sid into universe or will this happen automaticaly?
[23:05] <jtaylor> no you have to request a sync manually
[23:05] <lifeless> only during freezes
[23:05] <jtaylor> the requestsync tool in ubuntu-dev-tools is helpful
[23:05] <lifeless> depends how urgently you need it.
[23:05] <jtaylor> if its already in ubuntu you always need to do it manually
[23:06] <lifeless> jtaylor: thats incorrect.
[23:06] <jtaylor> ? it will automatically overwritte ubuntu changes? thats new to me
[23:06] <lifeless> no
[23:06] <lifeless> if its diverged, you need to merge or sync.
[23:06] <lifeless> just being present does not make it diverged.
[23:07] <jtaylor> ah yes I somehow assumed it was first in ubuntu ._.
[23:07] <lifeless> https://launchpad.net/ubuntu/oneiric/+source/ipwatchd
[23:07] <Laney> we are in a freeze anyway
[23:07] <ajmitch> debian import freeze was last month, wasn't it?
[23:07] <lifeless> current version in Ubuntu is 1.2-2 unaltered; so it will sync after we release, or you can request a sync to update it now.
[23:08] <jariq> lifeless, by "after we release" you mean when ubuntu 11.10 is out?
[23:08] <micahg> Laney: we aren't in a freeze
[23:08] <Laney> excuse me?
[23:08] <micahg> oh, that freeze :0
[23:08] <micahg> :)
[23:09] <lifeless> jariq: yes.
[23:09] <micahg> that's not really a freeze
[23:09] <ajmitch> micahg: if I look outside the window, it's freezing :P
[23:09] <jariq> to sum it up.. i need to request a sync :)
[23:09] <lifeless> jariq: or wait; depends if you want it in 11.10
[23:09] <jariq> sure i want
[23:10] <lifeless> in which case yes, request a sync :)
[23:10] <micahg> Laney: I forget DIF is called a freeze, but, please correct me if I'm wrong, it just stops the auto-import of new stuff
[23:10] <lifeless> do you have an LP account ?
[23:10] <jariq> yes i do.. sync can be requested via LP ?
[23:11] <lifeless> the script uses LP apis
[23:11] <jtaylor> not yet, but requestsync --lp packagename is equaly fast
[23:11] <Laney> micahg: right. I'd call that a freeze. Maybe not a very cold one, but you do have to explicitly request action.
[23:11] <Laney> however, I am going to bed. night
[23:11] <micahg> night Laney