[02:19] <slangasek> jibel: it doesn't appear that there've been any oneiric->precise (desktop,server) auto-upgrade tests since the job reorg :(
[03:12] <achiang> apt-get dist-upgrade in precise wants to remove python-dbus-common. can that really be correct?
[03:13] <micahg> achiang: yes, doesn't seem to be published any more
[03:13] <achiang> micahg: ok, thanks
[03:52] <stgraber> RAOF: hey there
[03:53] <stgraber> RAOF: thanks for accepting the vlan package
[03:54] <stgraber> RAOF: as for the extra delta in the ifenslave-2.6 SRU (one line change for /run + documentation), the idea was that reverting these just for the sake of having a smaller delta isn't probably worth it as indeed the /run change isn't needed (but won't make any change as /run is a symlink /var/run in Oneiric already) and the documentation would just be inaccurate if reverted
[03:55] <stgraber> RAOF: keeping these two changes gives us the advantage of having an identical package in Oneiric and Precise, making diffing the two quite a bit easier (if we start getting more changes in Precise) and so making debugging easier
[03:55] <RAOF> Fair enough.
[03:57] <RAOF> Accepted
[04:03] <stgraber> RAOF: thanks
[04:04] <stgraber> RAOF: I just posted instructions for the vlan package. I'll do the same for the ifenslave-2.6 package tomorrow, then that should be all that's needed for that bug. I'll test the full stack from -proposed on a server I have around that's affected by the issue and hopefully the bug reporter will do the same (AFAIK he's currently running the Precise version of these packages on Oneiric)
[04:06] <RAOF> Cool.
[04:37] <hyperair> kk
[04:37] <hyperair> oops
[04:40] <YokoZar> What order will dh_install act in?  (This is important for overlapping wildcards)  Is it the order of the packages in the control file?
[04:40] <YokoZar> (for multiple binary packages of course)
[04:41] <ScottK> I don't think you can rely on it to be ordered (think parallel builds).
[05:29] <pitti> Good morning
[07:23] <pitti> jibel: hm, I see "sudo: unable to resolve host ubuntu" in the upgrade-lucid-desktop output
[07:26] <pitti> jibel: uploaded a fix for gdm->lightdm autologin migration
[07:45] <jibel> pitti, good morning
[07:45] <pitti> jibel: bonjour, ca va?
[07:46] <hyperair> YokoZar: i think dh_install installs things multiple times, no?
[07:46] <jibel> pitti, I've got a cold and lost my voice, but ça va :)
[07:46] <jibel> pitti et toi ?
[07:46] <pitti> jibel: je suis bien, merci!
[07:46] <pitti> jibel: get well soon!
[07:47]  * ttx turns his attention to the new #ubuntu-devel-fr channel
[07:47] <YokoZar> hyperair: Yes it does, just learned that ;)
[07:47] <hyperair> =)
[07:47] <hyperair> you might want dh_movefiles instea
[07:47] <hyperair> d
[07:48] <jibel> pitti, I'll run an upgrade test today to validate the fix.
[07:48] <pitti> jibel: merci; NB that it isn't published yet
[07:48] <pitti> jibel: it's built, so should be on the mirrors in 45 mins
[07:49] <pitti> jibel: I guess/hope you did not apply the workaround for this yet?
[07:49] <pitti> jibel: i. e. ideally the user config migration tests should start working as well now?
[07:49] <jibel> pitti, it should, that's what I'd like to verify.
[08:02] <smb> slangasek, I saw your comment about having a reproducer now, but yes mine is on real hw but I can send out the /proc/cmdline. One special thing here is that I have console running on a serial line.
[08:02] <smb> morning, btw
[08:04] <dholbach> good morning
[08:29] <ejat> morning dholbach
[08:29] <ejat> !ping jamespage
[08:29] <dholbach> hi ejat
[08:29] <ejat> :)
[08:30] <ejat> hows ya day ?
[08:35] <dholbach> good good - how about yours?
[09:01] <slangasek> smb: do you happen to have /usr as a separate filesystem?
[09:01] <smb> slangasek, no I think that is in the main vg. but /boot would be differen
[09:02] <slangasek> ok
[09:02] <slangasek> I was specifically looking at the /etc/init/gssd.conf job, which triggers the bug if /usr is a separate filesystem
[09:02] <slangasek> but if that's not it on your system, nevermind; it probably doesn't matter which job it is
[09:03] <smb> Ok, still need to reactivate that machine to get the cmdline. Just refrained as it is a tad loud
[09:04] <slangasek> cmdline probably doesn't matter now
[09:04] <slangasek> don't worry about it - I think we've got a pretty solid reproducer now
[09:04] <slangasek> and on that note, I'm off to bed :)
[09:04] <smb> oh ok. bring it up anyway as its my xen test system. :)
[09:05] <smb> slangasek, good night. rather surprised to see you around anyway. (actually not, you are sometimes up at surprising times)
[09:20] <pitti> mvo: btw, should I binNEW apt now? this requires a full ABI transition, right?
[09:27] <mvo> pitti: slangasek uploaded it, but I assume the answer is yes, binaryNEW please :) the transition should be smooth as its a proper lib package now, once its there I can upload the rdepends
[09:30] <pitti> mvo: just asking because this evening is alpha-2 freeze, so I suppose we shuoldn't release it with an unfinished apt transition
[09:30] <mvo> pitti: if unsure we can wait for slangasek but given that its uploaded I would say lets do it all the way, it should be fine and we prepared it in a ppa and experimental
[09:30] <pitti> mvo: yes, and it is specifically targetted for alpha-2
[09:30] <pitti> for the upgrade fixes
[09:30] <pitti> mvo: binNEWed
[09:30] <mvo> what could possilby go wrong ?
[09:30]  * mvo goes and uploads rdepends
[09:30]  * pitti knocks on wood
[09:30] <pitti> mvo: danke!
[09:39] <seb128> jibel, pitti: bug #922052
[09:39] <seb128> the issue is ubiquity having:
[09:39] <seb128> static const char* indicators[] = {
[09:39] <seb128> 	"/usr/lib/indicators3/6/libsession.so",
[09:39] <seb128> 	// Bluetooth
[09:39] <seb128> 	"/usr/lib/indicators3/6/libapplication.so",
[09:39] <seb128> 	"/usr/lib/indicators3/6/libsoundmenu.so",
[09:39] <seb128> i.e hardcoded version, it needs to be updated,rebuilt with the current version
[09:39] <seb128> seems like ken forgot it when he went through the rdepends
[09:39] <seb128>  
[09:40] <seb128> is there any ubiquity upload planned for other reasons or anybody working on it?
[09:41] <mvo> Riddell: hi, when I do "bzr get lp:update-manager;cd update-manager; python UpdateManager/DistUpgradeFetcherKDE.py" I get a ugly assert failure - is this known? something wrong on my box? is that code still in use ? I'm doing pyflake cleanups and would love to actually test this stuff :)
[09:51] <mvo> Riddell: fwiw the exact error is http://paste.ubuntu.com/822367/
[09:53] <pitti> seb128: I'm creating a MP
[09:54] <seb128> pitti, thanks, I was trying to check if somebody was planning an ubiquity upload and only having a checkout and working on it before checking the source and doing that
[09:54] <seb128> the monday morning downloads are saturating my download ;-)
[09:54] <pitti> seb128: I have a current checkout anyway
[09:55] <seb128> pitti, danke
[09:56] <Riddell> mvo: there was a binary incompatibility last week
[09:56] <Riddell> mvo: I hope it's fixed but it's on my todo list for today to check
[09:56] <pitti> cjwatson, ev: would appreciate if you could pull/upload https://code.launchpad.net/~pitti/ubiquity/indicator-soname/+merge/90666 today
[09:57] <Riddell> mvo: make sure you have already done a dist-upgrade to check (maybe you want to be able to run the upgrade tool to do this :)
[09:58] <mvo> Riddell: ok, if you have time (ahaha, I know how it is :/) it would be awsome if you could simply run " python UpdateManager/DistUpgradeFetcherKDE.py" and "cd DistUpgrade; sudo ./dist-upgrade --frontend DistUpgradeViewKDE" on latest u-m trunk on a system that has a wokring pyqt - just to ensure my pyflake fixes did not mess up stuff on your side
[09:59] <Riddell> mvo: ta, will do
[10:25] <cjwatson> pitti: in progress, thanks
[10:26] <cjwatson> mvo: FWIW I'm working on a release-upgrader-apt update now
[10:27] <cjwatson> mvo: do you think it might be worth SRUing those resolver fixes of mine to lucid and oneiric?  I don't know what you normally do here, but it occurs to me that they might cause trouble for ordinary dist-upgrades too
[10:33] <brendand> Daviey - hi
[10:35] <mvo> cjwatson: we are cautious usually with resolver changes, but those are pretty clear so a SRU would be a good thing
[10:35] <mvo> cjwatson: when debian bzr is back I will merge them into the debian branch too
[10:36] <mvo> cjwatson: oh, and of course thanks a lot! for the fixes
[10:38] <mvo> if someone could binary-new libept1.4.12 that would be great
[10:38] <nigelb> ev: Hapy Birthday!
[10:47] <cjwatson> mvo: right, it wasn't the crazy "re-balance delicate heuristics" exercise that I'd expected
[10:52] <pitti> mvo: looking at libept, but waiting for a few mins for armel to finish
[10:52] <pitti> it's already in the test suite
[10:56] <Daviey> brendand: hello?
[10:57] <brendand> Daviey - just having a problem with the server installer, wondering if it's known about
[10:57] <brendand> Daviey - just after running tasksel, debian-installer fails
[10:58] <geser> cjwatson: as you're a bug contact for vim too: what's your opinion on bug #871907? I plan to merge vim once again in the next days and wonder if I should "fix" this bug too (or not)
[11:00] <cjwatson> geser: well, it's what I use personally, but it sounds like a classic case where we change the default and then the other set of people get upsset
[11:01] <cjwatson> the argument in the bug seems sound though ...
[11:01] <cjwatson> adding termcap entries would be a nightmare when working with other OSes
[11:01] <geser> that's the reason why I rethink about fixing it
[11:01] <Daviey> brendand: Is this on precise?
[11:02] <cjwatson> Daviey,brendand: -> #ubuntu-installer, let's not duplicate this across channels
[11:02] <brendand> Daviey - yes. as cjwatson says, discussing now in #ubuntu-installer
[11:02] <cjwatson> or actually - it's not an installer bug
[11:02] <cjwatson> http://paste.ubuntu.com/822408/ shows unmet dependencies in apache and nova
[11:03] <cjwatson> apparently trying to install multiple conflicting providers of certain virtual packages at once
[11:10] <geser> cjwatson: do you know if a dark terminal is the default for all *buntu variants?
[11:12] <pitti> mvo: libept NEWed
[11:12] <mvo> thanks pitti
[11:13] <dholbach> @pilot in
[11:13] <dholbach> hum
[11:21] <cjwatson> geser: no
[11:21] <cjwatson> I mean I don't know
[11:56] <zyga> barry: hi, quick question, what kind of buig should I file to get a new python trove classifier considered/added
[11:57] <dholbach> @pilot in
[11:59] <geser> dholbach: doesn't ubottu like you as pilot?
[11:59] <cjwatson> the channel was set +t a while back so it can't change the topic any more
[11:59] <dholbach> geser, I'm discussing it with AlanBell in #ubuntu-irc just now
[12:00] <cjwatson> unless it's that it no longer has ops or something
[12:00] <AlanBell> cjwatson: so on friday did you manually set the topic when you did @pilot out?
[12:00] <cjwatson> yes
[12:01] <AlanBell> ok
[12:01] <cjwatson> I didn't have time to track down what was wrong with the bot at the time
[12:01] <AlanBell> thats fine, I was just trying to figure out when it stopped working
[12:01] <AlanBell> ok, so I can op the bot, set the channel to -t or get the bot patched to use chanserv to change the topic
[12:02] <AlanBell> or some combination thereof
[12:06] <AlanBell> lets try that for starters, dholbach want to pilot in? (you may have to pilot out first)
[12:07] <dholbach> @pilot out
[12:07] <dholbach> @pilot int
[12:07] <udevbot> (pilot (in|out)) -- Set yourself an in or out of patch pilot.
[12:07] <dholbach> @pilot in
[12:07] <dholbach> aha!
[12:07] <dholbach> thanks AlanBell and cj
[12:07] <dholbach> thanks AlanBell and cjwatson :)
[12:07] <AlanBell> ok, we can add patching udevbot to use chanserv to change the topic to a todo list somewhere
[12:16] <doko> smoser, pitti, cjwatson: did your glibc-2.15 test system survive?
[12:33] <cjwatson> Can anyone here see a wireless network through NM with a non-ASCII SSID?  I'd like to check something.
[12:35] <pitti> doko: so far it does quite well
[12:35] <cjwatson> Actually, never mind, I think I've found relevant online references ...
[12:36] <pitti> doko: well, it's my normal workstation, so any bigger breakage should be visible quite fast (as the svg loader one)
[12:42] <lynxman> What would be the best way to create a watch file on a package to watch a git repo that's not on github? I've been googling around but can't find a definite answer
[12:48] <alkisg> lynxman: completely unrelated, but I tried your debian/ dir from https://code.launchpad.net/~lynxman/ubuntu/precise/ipxe/newsnapshot along with the current ipxe git and it worked fine. Not sure why your branch is marked "needs fixing" - it'd be nice if you could upload it so that we have a working ipxe for precise (bug #916489)
[12:48] <lynxman> alkisg: I was working on that actually :)
[12:49] <alkisg> Not that much unrelated then :D
[12:49] <lynxman> alkisg: it was just a problem on how I bzr commited the upstream snapshot, also wanted to add a watch file for full updatedness
[12:50] <alkisg> Right I think the last git numbers that you're using aren't very appropriate for version numbers, they got me a "newer version has a lower dpkg number" problem
[12:51] <alkisg> It'd also be nice if we put win32-loader.exe somewhere, either in the CDs or in the web site... That puts grub.mbr + ipxe.lkrn to the *windows* boot manager, but it can't be compiled in ubuntu without workarounds because we're missing a few debian packages like cpio-win32 something
[12:52] <lynxman> alkisg: that was one of the issues, I pumped up the version to 3. to avoid this after talking with the debian packager
[12:52] <alkisg> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607417 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657830 for the ipxe/win32-loader.exe part
[12:57] <lynxman> alkisg: hmm that'd be a nice addition indeed, I'll have a look into it :)
[12:58] <alkisg> lynxman: I have a binary in http://people.ubuntu.com/~alkisg/boot/win32-loader.exe if you want to see how it works first. Select the third option in the installer, "PXE mode".
[13:23] <Daviey> @pilot in
[13:24] <or4n9e> hi. may you please tell me where I can ask a question about packages in main (in my case bluez)? I.e. about the build process of the specific packages and an issue with the default distribution
[13:24] <or4n9e> thanks in advance
[13:25] <pitti> or4n9e: cyphermox recently dealt with bluez, he might be a good person to start discussing with
[13:26] <or4n9e> pitti: ok, thanks
[13:26] <or4n9e> cyphermox: may I chitchat with you quickly please?
[13:29] <pitti> or4n9e: he should get online in an hour or two, he's in Canada
[13:30] <or4n9e> pitti: I see. I'll just stay in here and then try again to ping him
[13:32] <or4n9e> btw, to all attending the chat (I see this as an opportunity) ... THANKS for developing ubuntu, I'm using it (and having fun) since 4.10 and never looked back. my honest respect to all making this happen
[13:42] <Daviey> debfx: Is bug 923343 ready for upload?
[13:44] <debfx> Daviey: yes, but I've filed two other bugs. at least bug #923407 should be easy to fix.
[13:48] <Daviey> debfx: do you want to include the fix for that in the same upload?
[13:48] <scott-work> cjwatson:  can you assist me getting the user (both live and installed default) into the audio group
[13:49] <cjwatson> scott-work: hmm, your preseeding is already supposed to do that
[13:49] <cjwatson> data/precise/preseed/ubuntustudio/ubuntustudio.seed:6:d-i       passwd/user-default-groups      string adm audio cdrom dip lpadmin plugdev sambashare
[13:49] <scott-work> cjwatson:  and also help with getting the jackd package to configure the rt privileges?  it used to but now it doesn't seem to ask, even in during the install
[13:50] <scott-work> cjwatson: re: audio group - i actually have tested an older image since we weren't building them for a while
[13:50] <cjwatson> you won't get questions asked with a ubiquity-based install.
[13:50] <cjwatson> this shouldn't have changed lately.
[13:51] <pitti> Daviey: just commented on the MP and also approved, looks good
[13:51] <pitti> thanks debfx
[13:51] <pitti> Daviey: yes, I think debfx' md5sum fix should also go in, that seemed easy; let me have a quick look
[13:51] <scott-work> cjwatson: my understanding from looking at the jackd code (although i'm not fluent) is that it defaults to audio.conf.disabled unless the defcon is answered yes
[13:51] <Daviey> thanks pitti
[13:52] <scott-work> cjwatson: i suppose the ubuntustudio-default-settings could manually rename that file to audio.conf just as the jackd defcon would
[13:53] <cjwatson> scott-work: better to just preseed that question.  what is its name?
[13:53] <scott-work> cjwatson: the name of the file jackd renames?
[13:53] <cjwatson> scott-work: no, the name of the debconf question
[13:54] <cjwatson> scott-work: also, could I have casper.log from booting an ubuntustudio DVD?
[13:54] <scott-work> cjwatson: re: casper.log, we can have that at the latest by tonight (i will do it if others can't, but i'm at 'work' on a windows machine)
[13:55] <scott-work> cjwatson: i don't know the name of the question but i can ask someone to test today during the day, again the latest would be tonight
[13:55] <cjwatson> jackd/tweak_rt_limits?
[13:55] <cjwatson> is this the jackd2 package?
[13:55] <scott-work> cjwatson: if you have a test install, you can just isntall jack
[13:55] <scott-work> cjwatson: yes, should be jackd2
[13:56] <cjwatson> I'd need to see it in context, and I'm too close to my bandwidth quota to download an ubuntustudio image just now.
[13:57] <scott-work> cjwatson: i have asked in #ubuntustudio-devel, although it's pretty early for musician type people ;)
[13:57] <cjwatson> Is there a bug# for this?
[13:57] <cjwatson> (either)
[13:57] <scott-work> (scott-work is a slight anomoly as he likes to get up early)
[13:57] <scott-work> cjwatson: there is not, but i am more than happy to create one or two
[13:58] <scott-work> cjwatson: would you like me to?
[13:58] <cjwatson> No need
[13:58] <cjwatson> Just wanted to know if there was an existing audit trail to attach commits to.
[13:59] <cjwatson> I believe I've enabled jackd rt priority for you no
[13:59] <cjwatson> w
[13:59] <cjwatson> Of course that assumes that whatever problem is preventing default groups from being set up properly is specific to default groups rather than a general problem with preseeding.
[14:00] <scott-work> cjwatson: thank you very much
[14:00] <pitti> Daviey: committed a fix for the other bug, running tests now
[14:01] <scott-work> cjwatson: i believe len testing the image from last night...although, i don't know if he specifically looked at the user in the audio group
[14:01] <Daviey> pitti: shall i leave test/upload with you?
[14:01] <pitti> Daviey: fine for me
[14:01] <pitti> Daviey: debfx also reported bug 923430, I'll have a quick look, too
[14:01] <scott-work> cjwatson: he might have just reported 'no rt privs', which could (as most likely) is attributable to the jack configure
[14:01] <Daviey> pitti: thanks
[14:02] <cjwatson> scott-work: yep, that's possible.  Worth checking specifically
[14:03] <debfx> pitti: thanks. I'm not quite sure how to fix that one.
[14:03] <pitti> debfx: I actually thougth I fixed that already long ago
[14:03] <pitti> i. e. make it ignore files which are in symlinked dirs
[14:05] <cyphermox> or4n9e: pinging you back, you wanted to know avout something in bluez?
[14:05] <scott-work> cjwatson: astraljava is going to check on these questions after zsyncing the latest image
[14:06] <debfx> pitti: right, so just check if usr/share/doc/$PKGNAME is a symlink?
[14:06] <cjwatson> scott-work: ok, cool
[14:07] <scott-work> is skaet around? or does she usually join later in the day?
[14:07] <pitti> debfx: it currently does
[14:07] <pitti>     # skip if doc dirs are already symlinks
[14:07] <pitti>     if [ ! -d usr/share/doc -o -h usr/share/doc -o -h usr/share/doc/$PKGNAME ];
[14:07] <pitti> ... return
[14:08] <lynxman> roaksoax: about the ipxe review you did, how would you add a watch file for a git repo not in github? Been looking for it to no avail
[14:08] <pitti> debfx: oh, that's not in symlink_doc(), its' in strip_debian_changelogs()
[14:11] <debfx> pitti: I guess clean_upstream_changelogs() should check that before setting $dch
[14:12] <pitti> debfx: yes, indeed; it could do dch=`readlink -f usr/share/doc/$PKGNAME/changelog.Debian.gz` instead
[14:12] <pitti> but this shoudl get a test case
[14:24] <pitti> bzr: ERROR: The delta generated was too large: xdelta: warning: no matches found in from file, patch will apply without it
[14:24] <pitti> error: excessively large binary delta for /home/martin/ubuntu/gvfs_1.11.2.orig.tar.xz
[14:24] <pitti> does anyone know a workaround for this?
[14:24] <pitti> I know that pristine-tar doesn't support .xz, but in the past it just stored the whole orig tarball instead of a delta
[14:24] <pitti> now it's gone from "inefficient" to "impossible"?
[14:25] <stgraber> pitti: thanks for fixing the langpack!
[14:25] <pitti> stgraber: well, my fault in the first place :) de rien
[14:29]  * pitti uses the old-fashioned way for gvfs then and let the package importer sort it out
[14:36] <stgraber> pitti: can you trigger a manual build of Edubuntu? would like to make sure it mostly works before we get into the alpha2 freeze
[14:37] <pitti> stgraber: started
[14:37] <stgraber> pitti: thanks
[14:43] <soren> Kiall: It looks good. My only complaint is the debian/patches/debian-changes-1.11-0mit1~35.gbpd304ad
[14:43] <soren> Er..
[14:43] <soren> Wrong channel.
[14:43] <soren> Heh
[14:45] <zul> can an archive admin review kyestonelight its been sitting in the binary new queue for the past two weeks
[14:45] <soren> zul: Oh, you're packaging it separately?
[14:45] <zul> yeah
[14:45] <soren> You know it's replacing keystone upstream, right?
[14:46] <zul> soren: yep
[14:46] <soren> Ok.
[14:46] <zul> soren: heard 2 weeks ago :)
[14:46] <soren> So.. Why do you..
[14:46] <soren> Meh. You work it out :)
[14:46] <Daviey> I don't think at the time we knew the name would change.
[14:54] <astraljava> cjwatson: US live user is _not_ in the audio group by default. Also, ubiquity crashed when I tried to update it. Called itself, python-apt and python-apt-common obsolete. :) The file in /etc/security/limits.d/ is audio.conf.disabled. Installing now to get the casper.log for ya.
[14:54] <cjwatson> the limits.d bit should be fixed with the next build
[14:54] <Pici> .60
[14:55] <soren> Daviey: Right. I don't think anybody did at that time, but you do now :) That's why I'm wondering.
[14:55] <cjwatson> not interested in that bit for now :)
[14:55] <astraljava> Yep. :)
[14:55] <hallyn> jodh: is upstart supposed to build in sbuild right now?
[14:55] <Daviey> soren: right..
[14:56] <jodh> hallyn: alas no, due to the fact that sbuild does not provide a controlling terminal. build works fine in pbuilder.
[14:57] <jodh> hallyn: I am looking at a change to the upstart test suite to allow it to build in sbuild though.
[14:57] <hallyn> jodh: ok, thx
[14:57] <hallyn> jodh: i expect to send you a merge request (for review) for lxc container support hopefully later today
[14:58] <koolhead11> hi all
[15:02] <jodh> hallyn: ok, thanks. sounds intriguing.
[15:02] <barry> zyga: probably the pypi bug tracker? http://sourceforge.net/tracker/?group_id=66150&atid=513504
[15:06] <zyga> barry: thanks
[15:16] <cjwatson> pitti: http://people.canonical.com/~ubuntu-archive/testing/lucid-updates_probs.html lists some language pack problems
[15:16] <pitti> argh, did that slip in again
[15:16] <pitti> cjwatson: thanks, fixing
[15:21] <stgraber> pitti: is there an easy way I can get apport to submit crashes from another system (in this case from automatic upgrade testing)? apport-bug complains that it's unable to find the package
[15:22] <hallyn> jodh: hm, test_conf still failed in pbuilder.
[15:22] <hallyn> biab.  (will check if it's my own fault)
[15:27] <jodh> hallyn: could you send me some details?
[15:27] <jodh> hallyn: sorry - caught by bug 861268 yet again.
[15:28] <hallyn> jodh: what sort of detail?
[15:29] <hallyn> jhunt, hm, i haven't noticed that since switching from nvidia to nouveau recently
[15:32] <pitti> stgraber: run apport-bug --save foo.appor mypackage  on the affected system, then copy it over, and run apport-bug foo.apport
[15:37] <hallyn> jodh: http://paste.ubuntu.com/822673/ shows the failed bit in 'pbuilder build *.dsc' with the current result of 'pull-lp-source upstart'
[15:38] <stgraber> pitti: right, sadly the affected system doesn't really exist anymore... the only thing I get from the auto dist upgrader is a .crash. I'll try to dig a bit and see if I can get the stacktrace in a readable form so I can look for these crashes on LP.
[15:41] <jodh> hallyn: thanks - do you have the rest of the log though? Need to see atleast a couple of lines of context arond the line showing BAD or FAIL
[15:42] <hallyn> jodh: http://paste.ubuntu.com/822682/ is that what you need?  I can upload the whole log to p.c.c otherwise
[15:43] <Riddell> mvo: hi
[15:44] <jodh> hallyn: thanks. if you could send me the log, that'd be great.
[15:44] <Riddell> mvo: "python UpdateManager/DistUpgradeFetcherKDE.py" complains about not being able to write to ~/.cache/something
[15:44] <Riddell> mvo: when I make ~/.cache it exits successfully without showing a GUI
[15:44] <Riddell> mvo: cd DistUpgrade; sudo ./dist-upgrade --frontend DistUpgradeViewKDE  is working fine
[15:45] <Riddell> mvo: so new bug found in the ~/.cache issue?
[15:47] <astraljava> cjwatson: Sorry, but I can't provide the casper.log. Ubiquity crashes in the middle of the installation.
[15:47] <astraljava> ...repeatedly.
[15:48] <cjwatson> astraljava: casper.log is generated before ubiquity starts.
[15:49] <astraljava> Oh! Lemme try to get to it, then.
[15:50] <nigelb> 20
[15:50] <nigelb> ugh
[15:51] <astraljava> cjwatson: http://astraljava.kapsi.fi/casper.log
[15:53] <cjwatson> the fontconfig-voodoo stuff there isn't pretty, but not immediately relevant
[15:53] <cjwatson> no obvious sign of a preseeding problem
[15:53] <cjwatson> I guess I'll have to download all this and have a look :-(
[15:53] <astraljava> cjwatson: Damn. Well, let me know if you need anything from me.
[15:54] <astraljava> I'll keep it in this state for a while.
[15:54] <cjwatson> I'd been hoping to avoid having to look directly, but sometimes there's no other way
[15:55] <astraljava> Sorry...
[15:56] <hallyn> jodh: http://people.canonical.com/~serge/outout (result of 'sudo pbuilder build *.dsc > outout 2>&1')
[15:56] <astraljava> cjwatson: I can dig into it, too. I know you're very busy, so I don't wanna add more burden on your shoulders because of US.
[15:56] <seb128> mvo, hey, is that some bug or some local corruption?
[15:56] <seb128> rc  libunity-misc0                            0.2.1-0ubuntu2                           Miscellaneous functions for Unity - shared library
[15:56] <seb128> $ LC_ALL=C sudo apt-get remove --purge libunity-misc0
[15:56] <seb128> ...
[15:56] <seb128> dpkg: error: architecture name in specifier 'libunity-misc0:��' is illegal: must start with an alphanumeric
[15:57] <seb128> it does it on other packages in a "rc" state
[15:57] <cjwatson> astraljava: well, feel free certainly, but I expect this is something fairly arcane
[15:57] <seb128> so seems a bug
[15:57] <astraljava> cjwatson: I understand, and am a little afraid of it. :)
[15:58] <cjwatson> astraljava: might be worth getting casper.log when booting with DEBCONF_DEBUG=developer on the kernel command ine
[15:58] <cjwatson> *line
[15:58] <astraljava> cjwatson: Alright, I'll try that.
[15:59] <mvo> seb128: meh, you found a bug
[16:00] <astraljava> cjwatson: There are two dashes at the end, before or after them?
[16:01] <cjwatson> astraljava: doesn't matter, as long as there are spaces in between that argument and the dashes
[16:01] <astraljava> Ok.
[16:06] <MacSlow> mvo, poing
[16:06] <seb128> mvo, where should I open it? ;-)
[16:06] <seb128> open->report
[16:07] <astraljava> cjwatson: Ok, file updated at the same location.
[16:10] <mvo> seb128: apt
[16:10] <mvo> MacSlow: pong
[16:11] <mvo> seb128: and high please
[16:11] <astraljava> Wonder if the burn process went bust. md5sum matches.
[16:12] <cjwatson> astraljava: no, nothing to do with that
[16:13] <cjwatson> despite answers.launchpad.net users' penchant for claiming everything's a burn problem
[16:13] <astraljava> Hehe. :)
[16:13] <seb128> mvo, bug #923807
[16:13] <mvo> ta
[16:13] <cjwatson> astraljava: can you file a bug on casper, please?  The problem is that preseeding is processed after user-setup is run
[16:13] <hyperair> hmmm there's an unpatched sudo vulnerability around.
[16:13] <hyperair> http://seclists.org/fulldisclosure/2012/Jan/att-590/advisory_sudo.txt
[16:13] <smoser> anyone feel like commenting/rejecting/flaming me for https://code.launchpad.net/~smoser/ubuntu/precise/sysvinit/rc.local.d/+merge/88323 (bug 915215)
[16:14] <astraljava> cjwatson: Yes, for sure. And I guess I'll attach the log file, but does it need something else?
[16:14] <cjwatson> astraljava: nope
[16:14] <astraljava> Alright.
[16:18] <astraljava> cjwatson: bug 923810 filed
[16:19] <astraljava> Very vague title, but didn't really know what to put in there.
[16:23] <cjwatson> astraljava: let's keep the ubiquity crash separate
[16:23] <cjwatson> astraljava: it's probably unrelated
[16:24] <jdstrand> hyperair: that only affects 12.04, and our hardening should handle it sufficiently until there is a merge from Debian
[16:24] <hyperair> jdstrand: cool, that's good to know
[16:26] <astraljava> cjwatson: Oh okay, sorry.
[16:27] <cjwatson> astraljava: happy to debug your ubiquity crash separately ...
[16:27] <mvo> seb128: anything special about the pkg ? I can not reproduce the failure currently
[16:27] <seb128> mvo, no, just pick anything in dpkg -l | grep ^rc ?
[16:28] <mvo> seb128: aha! you rock
[16:29] <seb128> mvo, sorry if the description was not clear enough ;-)
[16:29] <mvo> seb128: *cough* or I was not reading carefully enough
[16:42] <astraljava> Sorry about the bug title, didn't refresh in between. Changed it back to what you had.
[16:48] <dholbach> @pilot out
[16:53] <stgraber> cjwatson: hi! ldm is finally somewhat in sync with Debian and it should now be safe for people to merge as any other package. Can you remove it from the MoM blacklist?
[16:54] <cjwatson> stgraber: I believe it's just in the sync blacklist (which MoM uses) - confirm that it's still OK to remove from that?
[16:54] <cjwatson> (*ubuntu* versioning will still be respected, of course)
[16:55] <stgraber> cjwatson: yeah, whenever the Ubuntu delta will be fully gone it'll be fine to sync from Debian, so removing from the sync blacklist sounds good
[16:55] <cjwatson> stgraber: does the same go for ltsp?  it's currently blacklisted for the same reason
[16:56] <stgraber> no, ltsp is still a mess, I'm hoping to resolve the situation this cycle though ;)
[16:56] <cjwatson> stgraber: OK, I've just unblacklisted ldm then
[16:57] <stgraber> cjwatson: thanks
[16:58] <nigelb> 22
[17:02] <jodh> hallyn: I can't recreate your problem using pull-lp-source or building direct from the branch. Is it repeatable?
[17:03] <hallyn> jodh: yeah...  it happens every time here
[17:04] <hallyn> jodh: i'll go ahead and try elsewhere then.
[17:05] <astraljava> cjwatson: The ubiquity crash is on bug 923830
[17:05] <hallyn> jodh: the pbuilder tarball was brand-spanking-new, and the schroot was just updated...
[17:16] <hallyn> jodh: feh, on a canonistack instance it worked.  some breakage on my system apparently!
[17:23] <jdstrand> @pilot in
[17:27] <slangasek> jibel: hey there!  did you catch my comment over the weekend that the oneiric->precise upgrade tests seem to have gone missing from jenkins post-reorg?  Sorry for rocking the boat and screwing this up :/
[17:36] <jibel> slangasek, hey. where are you looking ? from https://jenkins.qa.ubuntu.com/view/Precise%20Upgrade%20Testing%20Dashboard/job/precise-upgrade-oneiric-desktop/ the test ran from Jan 26th to 29th
[17:36] <jibel> same for server
[17:37] <slangasek> jibel: oh, *hah*
[17:37] <slangasek> jibel: I didn't notice that there was a separate listing below for all tests, I only saw the list at the top of https://jenkins.qa.ubuntu.com/view/Precise%20Upgrade%20Testing%20Dashboard/ of the broken ones
[17:37] <slangasek> so the other tests are succeeding and that's why I didn't see them ;)
[17:38] <slangasek> jibel: thanks for the quick fix ;)
[17:38] <jibel> slangasek, oh ok. They didn't failed since post-reorg :)
[17:51] <voidvector> hi, i am running oneiric, how do i force a package and its dependencies to use the precise version? My alternative is compile from source, which i really don't like to do as it is a lib
[18:15] <lamefun2> hello
[18:15] <lamefun2> where does Ubuntu Software Center get list of software from?
[18:16] <jelmer> lamefun2: from the apt repositories listed in /etc/apt/sources.list and /etc/apt/sources.list.d
[18:17] <lamefun2> and how does it know if an package is an "application" or a "technical item" or a "plugin"?
[18:19] <koolhead17> hi all
[18:45] <mdeslaur> tedg: hi! FYI, I cleaned up a lot of screensaver/screen locking cruft out of indicator-session in precise, and I've proposed a merge into trunk
[18:47] <tedg> mdeslaur, Cool!
[19:01] <stgraber> geser: ping (DMB meeting)
[19:51] <or4n9e> cyphermox: ping. pitti told me that I may chitchat with you about bluez distribution in ubuntu
[19:52] <or4n9e> cyphermox: do you have a few?
[19:52] <cyphermox> or4n9e: certainly
[19:53] <or4n9e> cyphermox: great. basically I was going to re-compile bluez in order to --enable-test configure flag just to find out that it's already enabled
[19:53] <cyphermox> ok
[19:53] <cyphermox> oh... maybe those aren't being run though, and if not we should definitely fix that
[19:53] <or4n9e> but ... I need bdaddr tool from bluez test directory and although --test-enable is ON it isn't shipped with ubuntu's default bluez distribution
[19:54] <cyphermox> oh, you mean those tests
[19:54] <doko> smoser, ping
[19:54] <cyphermox> or4n9e: what does bdaddr do?
[19:54] <smoser> doko, here.
[19:54] <or4n9e> there are SOME test utils build, so thee flag isn't useless at all but bdaddr isn't built
[19:54] <smoser> i've not installed your ppa :-( but if you'd like i can do that "right now"
[19:55] <or4n9e> cyphermox: bdaddr changes bdaddr on supported chipsets
[19:55] <cyphermox> or4n9e: ok. I guess you've looked that a fair amount already, were you able to make it get built?
[19:55] <or4n9e> cyphermox: definitely CSR, not sure about the other supported chipsets
[19:55] <mvo> seb128: your crash in libapt is fixed in bzr
[19:56] <mhall119> ev: ping
[19:56] <doko> smoser, did you get my emails about the updated eglibc packages?
[19:56] <or4n9e> cyphermox: nope. I stopped once I've seen that the appropraite flag is set in ubuntu src package
[19:56] <cyphermox> or4n9e:
[19:56] <cyphermox> dah
[19:56] <or4n9e> I then joined here to ask and pitti pointed me to you
[19:56] <smoser> doko, yeah, i just haven't tried.
[19:56] <doko> please do
[19:56] <cyphermox> or4n9e: sure. I can have a look in a few minutes :)
[19:56] <smoser> k
[19:56] <seb128> mvo, oh, it was a segfault? thanks ;-)
[19:57] <cyphermox> or4n9e: you're interested in that being in the Precise package, right? or previous releases as well?
[19:57] <mvo> seb128: for me it was :)
[19:57] <seb128> mvo, great ;-)
[19:57] <mhall119> ev: I need to get a list of the 50 most used applications from software center, so we can target them for tighter Unity integration for 12.04.  Can you get me such a list?
[19:57] <or4n9e> cyphermox: awesome stuff. I mean it would be perfectly appropriate to me if you may provide me a sufficient patch to be able to re-compile the src myself. not sure if bdaddr is actually needed for the masses
[19:58] <or4n9e> cyphermox: I'm running oneiric
[19:58] <or4n9e> bluez 4.96
[19:58] <cyphermox> or4n9e: I don't know, but if it doesn't hurt to have it it's simple enough to make it get built and installed
[19:58] <smoser> doko, ppa link ?
[19:59] <doko> smoser, https://launchpad.net/~ubuntu-toolchain-r/+archive/glibc/+packages
[19:59] <or4n9e> cyphermox: that's true! in the end the typical end-user wouldn't care either way
[19:59] <or4n9e> i.e. doesn't harm
[20:00] <or4n9e> cyphermox: so, you mean, you may even provide an update to the main repos? for oneiric/precise. man, that'd be great
[20:03] <or4n9e> cyphermox: I even read somewhere that bdaddr is actually needed for wiimote (not sure about the details). thus it may even have an advantage to a broader audience if it gets introduced to default ubuntu
[20:04] <or4n9e> cyphermox: lemme know if I can provide further info and thx a million for having a look at it
[20:04] <cyphermox> or4n9e: ok. I'll take a look at that too, fortunately I have wiimotes and I've been itching to try this out
[20:05] <cyphermox> or4n9e: have you filed a bug about all this?
[20:07] <or4n9e> cyphermox: nope, I haven't dealed with the wiimote thingy yet (nor may I provide better info here, I just read on the interwebz that there are some people complaining about the missing bdaddr in debian/ubuntu and compile it themselves)
[20:08] <or4n9e> cyphermox: I myself just need bdaddr with a shell script, so it's more of a personal issue than a "bug" interesting to the general user
[20:08] <or4n9e> I.e. I haven't seen it as a bug yet :)
[20:10] <or4n9e> afaik bluez test utils are anyway provided as unstable test foo and it's basically the distribution's (your) choice to ship it or not, assumed you're responsible for bluez distribution
[20:16] <or4n9e> cyphermox: on a more personal note ... if you're itching to get your hands wet with the wiimote, be sure not to miss Johnny Chung Lee's Wii project page http://johnnylee.net/projects/wii/
[20:19] <burli> any idea if Vala 0.15.1 come to Precise?
[20:20] <burli> or is it to late for new versions?
[20:56] <Atlantic777> Hi! I'm interested in translating some docs about ubuntu development. May somebody recommend me some good official guides to start with?
[21:47] <JuN1x> Atlantic777: https://wiki.ubuntu.com/Translations/QuickStartGuide
[21:48] <Atlantic777> tnx :)
[21:59] <Daviey> @pilot out
[23:19] <jordi> TheMuso: hey
[23:20] <jordi> TheMuso: I've finished packaging alsa-lib 1.0.25, and I'd be very happy if we could use this opportunity to bring the Ubuntu delta down to the bare minimum, if possible.
[23:33] <TheMuso> jordi: Ok, give me an hour to finish what I'm doing, and I'll look over our delta and send stuff your way.
[23:34] <jordi> TheMuso: I'll be going to bed soonish, however I'll leave you some comments in private
[23:34] <TheMuso> jordi: ok
[23:37] <jdstrand> @pilot out
[23:57] <codebrainz> Hi. Is this the best place to ask about the dbus menu thing in Unity?
[23:57] <ScottK> Not really.
[23:58] <ScottK> At the very least #ubuntu-desktop would be better
[23:58] <codebrainz> it's a dev question, if that matters. is there an ayatana (or whatever) channel?
[23:59] <cjwatson> #ubuntu-unity
[23:59] <ScottK> Thanks.
[23:59] <codebrainz> ok, will try there. thanks