/srv/irclogs.ubuntu.com/2012/04/18/#ubuntu-devel.txt

StevenKbarry: Hit the edit icon next to 'duplicate of ...'00:00
barryStevenK: oh, *and* delete the bug number then hit the check box. :)  but thanks!00:01
StevenKbarry: Well, yeah, but I thought once I got you over the hurdle of *finding* the link, you could figure out the rest. :-)00:01
barryStevenK: i put my 10,000 monkey-clone army on it and they shakespeare'd it in 300ms00:02
keesslangasek: is there a bug open for the targoniness of booting 64-bit kernels on a 32-bit CPU?00:10
keesslangasek: afaict, the kernel itself just enters a hlt loop and doesn't display _anything_.00:11
slangasekkees: bug #983825?00:11
ubottuLaunchpad bug 983825 in gfxboot-theme-ubuntu (Ubuntu) "Present helpful message when booting 64-bit medium on 32-bit machine" [Medium,Triaged] https://launchpad.net/bugs/98382500:11
keesperfecto00:11
pittiGood morning05:02
sladenpitti: morgen!05:09
=== Whoopie_ is now known as Whoopie
=== tkamppeter_ is now known as tkamppeter
dholbachgood morning06:49
=== smb` is now known as smb
=== kenws_ is now known as kenws
=== ritz is now known as ritz|nomNomNom
tsdgeosahasenack: having any luck with the patched unity-2d i told you? Too soon to declare victory maybe?09:49
ahasenacktsdgeos: yeah, too soon09:49
tsdgeosoki :-)09:49
=== MacSlow is now known as MacSlow|lunch
=== MacSlow|lunch is now known as MacSlow
seb128ev, hey, just curious but is there somewhere where we can get news about the status of your work on whoopsie, the db, etc?11:52
evseb128: actually, let me forward you an email I sent about it to my team soliciting input11:53
evwould be excellent to hear your thoughts11:53
seb128ev, thanks ;-)11:53
=== _salem is now known as salem_
=== greyback is now known as greyback|lunch
=== doko_ is now known as doko
dokojibel: about 983981, is this pure lucid, or lucid-updates?12:29
jibelbug 98398112:32
ubottuLaunchpad bug 983981 in update-manager (Ubuntu) "Lucid -> Precise main failed to upgrade: ERROR: pycompile:Requested versions are not installed dpkg: error processing python2.7-minimal installed post-installation script returned error exit status 3" [High,New] https://launchpad.net/bugs/98398112:32
jibellucid updates12:32
jibeldoko, ^12:32
dokojibel, but not for any update, correct?12:35
jibeldoko, correct. Only the test referenced in the report fails.12:42
dokojibel, are the tarballs for the chroots available somewhere?12:43
=== greyback|lunch is now known as greyback
mvoMirv: new ddtp stuff uploaded13:00
mterryRAOF, heyo.  Got a moment to talk about X and keyboard layouts?13:29
RAOFI'll say yes.13:30
mterryRAOF, I'm seeing "key types not defined" when trying to have xkbfile X extension use the "fr oss" layout13:30
mterryWhat does it mean for a map to not have it's key types defined?13:30
mterryRAOF, (this is bug 960096)13:30
ubottuLaunchpad bug 960096 in ubiquity (Ubuntu) "Live session started with wrong layout" [High,Triaged] https://launchpad.net/bugs/96009613:30
RAOFHm.  I don't know at the moment.  Let me check13:30
mterrybut if you do look at the bug, look only at the last few comments.  Several flaws have been glommed into the same bug report13:31
mterryI'm working on the most recent one13:31
dobeyshould i not get a "Waiting for Approval" mail for something i uploaded to oneiric-proposed?13:33
stgraberdobey: yes, you should13:33
dobeyhrmm, i haven't gotten one, and i uploaded it last night13:34
dobeyubuntuone-storage-protocol_2.0.1-0ubuntu1_source.changes13:35
stgraberdobey: it's not in unapproved for oneiric so it probably got lost somewhere13:37
stgraberbdmurray: iso tracker updated published, bug search should be working fine now with duplicates13:37
dobeystgraber: should i just rm the .upload file and try again?13:37
stgraberdobey: yep13:39
dobeyok13:39
dobeysays successfully uploaded again. hopefully it worked this time13:40
=== dholbach_ is now known as dholbach
RAOFOh, wow.13:42
RAOFmterry: The XKB protocol is quite impressive13:42
mterryRAOF, in a good way?  :)13:43
RAOFIn a bloodymindedly baroque way.13:43
RAOFAlso, it supports keys in radio groups for some reason.13:44
RAOFOn the off-chance you'd like to map your keyboard such that exactly one of 'a', 'b' or 'c' is considered to be pressed at any one time.13:45
RAOFThe protocol specification is also a light-weight 107 page PDF, plus appendicies.13:46
* RAOF has thus far managed to avoid looking too closely at the direction of XKB in the hope that it'd go away if he didn't make eye contact.13:47
ScottKmvo: I just noticed Bug #984906.  If you end up doing another update-manager upload, I would appreciate it if you could include the fix for it as well.13:47
ubottuLaunchpad bug 984906 in update-manager (Ubuntu) "update-manager-kde short description wrong" [Low,New] https://launchpad.net/bugs/98490613:47
RAOFmterry: I'll take a longer gander at it tomorrow; 10pm beckons.13:50
mterryRAOF, OK.  thanks!13:50
Mirvmvo: ok, great! Debian itself has had apparently problems that the translations haven't been uploaded for some while, but at least now it should be up-to-date what Debian has on its servers13:50
Mirvapparently some unicode problem was just now found13:52
dokoScottK, do you know why pycompile in lucid still has DEFAULT_VERSION = (2, 5) ?14:01
ScottKNo.14:01
ScottKmvo: Very quick (with the commit for the bug fix).  Thanks.14:06
mvoScottK: sure, that was a tiny one, thanks for the report and the irc ping14:07
ScottKShould help the production metrics for the week....14:07
=== carif_ is now known as carif
saidinesh5hi guys..... just made a package for a software of ours14:35
saidinesh5http://paste.kde.org/459398/14:35
saidinesh5so basically are these warnings safe to ignore?14:35
saidinesh5especially the ones regarding cannot find lib needed for <package>14:35
saidinesh5(basically vsxu_artiste, vsxu_player, vsxu_server are all dependant on libvsxu  , and i ve specified that in the control file)14:36
dobeystgraber: ugh. it's telling me the signer doesn't have upload rights now. i guess something got mucked up when we made the packageset for precise for u1 stuff, and now i can't upload to the older ubuntus?14:47
stgraberdobey: that could be, ppu are for all releases but package sets are per release14:48
stgraberdobey: as we created the ubuntuone packaget set in precise, you probably lost your upload rights to older releases in the process14:48
dobeystgraber: ugh. any way to fix it? or will i have to just do merge proposals now for all the packages in older ubuntus?14:49
stgraberdobey: launchpad doesn't let me create a copy of the package set in oneiric apparently ...14:52
dobeyhmm14:53
stgraberdobey: I can do a temporary hack to let that one in though, what's the source package name?14:53
dobeystgraber: well i have a few more packages to do as well, and was expecting to have to do a proposal for at least one. i guess i'll just do it for all. i guess this also explains why my bug nominations weren't automatically approving on a couple packages for the older ubuntus as well14:54
Laneystgraber: hrm, why can't you create it?14:54
stgraberstgraber@castiana:~/data/code/ubuntu-archive-tools$ python edit_acl.py create -P ubuntuone -S oneiric -p developer-membership-board14:55
dobeystgraber: and i'll have to do similar SRUs for natty and probably lucid soon as well, so don't want to keep wasting time with temporary hacks14:55
stgraberPackage set ubuntuone already exists14:55
stgraberstgraber@castiana:~/data/code/ubuntu-archive-tools$ python edit_acl.py add -P ubuntuone -S oneiric -p ubuntu-ubuntuone-dev14:55
stgraberThere was a 404 error:14:55
stgraberNo such package set (in the specified distro series): 'ubuntuone'.14:55
stgraberLaney: ^14:55
Laneysounds buggy14:55
cjwatsonedit_acl.py create IIRC14:55
cjwatsonoh, /me reads again14:55
Laneythat was in his first paste14:55
cjwatsonodd14:55
LaneyI guess you could namespace it as a workaroudn14:55
stgraberI probably could but then we might end up with both in Q as LP seems to do some weird things when creating a new series...14:56
LaneyI recall bugs around initialising packagesets14:56
Laneycheck with #lp?14:57
stgraberwell, I have a couple of "critical" bugs opened for a few months regarding the packageset table being a bit of a mess14:57
LaneyI would guess/hope that it only uses sets in n to initialise n+1, but …14:58
stgraberit doesn't ;)15:00
stgraberthat's what caused most of our existing bugs15:00
ScottKmicahg: Would you or some other mozillateamish person please look at esteid-browser-plugin in the New queue and see if it's now something that's supportable from your POV?15:01
Laneyall I can suggest is that you seek counsel from a Launchpad developer about the best way to proceed15:01
cjwatsonI've been meaning to fix that initialisation bug15:01
cjwatsonit should be easy15:02
cjwatsondid you at least make sure that the data in P is clean?15:02
stgraberfor ubuntuone, it should be, it's a new package set15:02
Laneythere's some duplication15:02
LaneyI can't remember the details15:02
stgraberfor some of the other packagesets, no, we have a ton of duplicates15:02
cjwatsonI meant for all package sets - I knew it was broken but I haven't had a chance to go through and sanitise it15:03
cjwatsonwe should probably try to clean that up before we open Q15:03
stgraberI got a few fixed by the Launchpad guys, then they filed another bug to get that table cleaned up and nothing happened since15:03
stgraberyeah, fixing the init code and cleaning up the current mess before Q would be good15:03
cjwatsoncan't we clean it up by hand?15:03
stgrabernot with edit_acl15:04
cjwatsonhow come?15:04
stgraberthe API does checks that the DB doesn't ;)15:04
cjwatsonbah15:04
cjwatsonbut I suspect that cleaning things up requires manual attention15:04
stgrabercjwatson: bug 88718515:05
ubottuLaunchpad bug 887185 in Launchpad itself "ArchivePermission allows duplicated rows" [Critical,Triaged] https://launchpad.net/bugs/88718515:05
stgrabercjwatson: and the initial question: https://answers.launchpad.net/launchpad/+question/17744915:05
stgraberso when trying to fix from the API, I get "NotOneError" so only someone with direct DB access can fix it15:05
cjwatsonwe could relax that for removal15:06
cjwatsonthat would probably be better than db hackery15:06
stgraberthat'd work, then we can cleanup the current mess with edit_acl15:06
cjwatsonI have to do RC stuff first though15:06
cjwatsonbut I think I can look at this15:07
stgraberah, the packageset creation part is an edit_acl bug, I'll fix that one15:07
stgraberit checks for existing packageset but without giving a distroseries15:07
cjwatsonok15:08
cjwatsonmakes sense given what I was doing when I wrote that15:08
stgraberdobey: fixed for oneiric15:16
dobeystgraber: thanks15:17
Laneynice15:17
dobeystgraber: can we get it fixed for natty and lucid as well?15:18
stgraberdobey: are you uploading to these two today?15:18
stgraberit takes me time to create the new packageset as I need to do it by hand depending on what packages were there (no magic copy function), so I'm happy to do it but won't spend the extra time until it's needed ;)15:19
dobeystgraber: probably not today no15:19
Laneyimplement the copy function :P15:20
stgraberLaney: almost tempted to do it, then ask LP not to do any copying when creating a new series and just use edit_acl for it ;)15:22
Laneyheh15:22
LaneyI was thinking that it would be useful when we create new sets in future15:22
stgrabercjwatson: actually, would that be easier? ^ :)15:22
stgraberI think I can implement a new "copy" function to edit_acl that takes a packageset and two series and just re-create it15:23
cjwatsonhm, not sure, the init stuff was partly for derived distributions and I don't know what they wanted here15:23
cjwatsonI think it would be *quicker* to fix the bug at hand and then consider such a redesign afterwards15:23
dobeyok. well i'll ping again when i need to upload to natty and lucid. thanks again stgraber!15:30
stgraberdobey: np15:32
SpamapS[160199.816023] [Hardware Error]: Machine check events logged15:52
SpamapSruh roh15:52
stgraberdobey: natty and lucid done (I added a copy function quickly ;))15:54
=== zyga is now known as zyga-food
stgrabercjwatson: I just filed a merge proposal for that do_create distroseries fix and to add a basic do_copy16:05
=== Quintasan_ is now known as Quintasan
* slangasek hugs didrocks for his gnome session16:26
* didrocks hugs slangasek back :)16:26
didrocksNot sure you saw the discussion but it was hot ;)16:27
slangasekdidrocks: the one on #ubuntu-release, I saw :)16:27
didrocksyeah ;)16:27
vibhavI missed it again :(16:27
andreas__tsdgeos: no backtraces yet, looking promising16:29
andreas__tsdgeos: but no logging either, so that code wasn't triggered16:29
SpamapSwow.. I went like, a whole week without a dist-upgrade and now I have 600 packages to update.16:29
tsdgeosandreas__: ok, so the code didn't really do anything useful16:30
* SpamapS probably should uninstall some packages :-P16:30
SpamapSahh.. the gnome 3.4.1 bump is the source of most of it :-P16:31
=== andreas__ is now known as ahasenack
SpamapSneed an opinion on bug 981130 ..16:51
ubottuLaunchpad bug 981130 in ceph (Ubuntu Precise) "python-ceph Depends on librgw1, which is no longer built" [Undecided,New] https://launchpad.net/bugs/98113016:51
SpamapSits a small python library.16:51
SpamapSwith three modules..16:51
SpamapSonly one of them needs librgw116:51
SpamapSshould we just not install the module that needs rgw1 .. or just drop the dep on librgw1 and ship a module that won't work?16:52
dobeystgraber: cool. thanks much!16:56
ScottKSpamapS: I vote for only shipping working stuff.17:02
dokoseb128, why did you reassign 960967 to libjpeg8?17:02
seb128doko, I though it was the lib jtransform_execute_transform() and providing do_rot_270()17:03
seb128doko, where the segfault happens17:03
seb128doko, I guess I was wrong, where should it go?17:04
jtaylordoko: sorry I have probably missed your reply to the argparse issue, will it still be fixed?17:04
dokojtaylor, it is fixed17:05
dokoseb128, libjpeg is built from jpeg-turbo17:05
jtaylordoko: oh I don't have -proposed enabled yet, thanks17:05
seb128doko, oh ok, I was unsure, I picked the wrong one17:05
seb128doko, I'm fixing it17:05
seb128too many libjpeg* ;-)17:06
dokoseb128, and it appears to be a duplicate17:07
SpamapSScottK: me too.. discussing w/ upstream what the best course is17:07
ScottKOK.17:07
seb128doko, could well be, I didn't check for duplicates17:08
seb128doko, it has a picture example included though which might be useful17:08
micahgScottK: at this point, chrisccoulson needs to review esteid-browser-plugin17:10
ScottKmicahg: OK.  Thanks.  chrisccoulson?17:10
ScottK(it's in new again in case you missed it)17:10
PaoloRotoloHi all!17:17
=== Nafallo_ is now known as Nafallo
slangasekpitti: what do you think of bug #937249?17:22
ubottuLaunchpad bug 937249 in apport (Ubuntu) "apport-gtk crashed with SIGSEGV in composite_line()" [High,Confirmed] https://launchpad.net/bugs/93724917:22
=== zyga-food is now known as zyga-afk
=== deryck is now known as deryck[lunch]
saidinesh5apachelogger: here?18:13
saidinesh5hmm... any ubuntu packagers here?18:19
kklimondasaidinesh5: well, it's a channel for ubuntu developers so it's a possibility that some ubuntu packages sit here ;)18:20
kklimondasaidinesh5: it's better to ask the actual question18:20
saidinesh5heheh .. well basically ..... i just created a debian/* stuff for a project that i m involved with18:21
saidinesh5so basically it is split up into (libvsxu , libvsxu-dev , vsxu-artiste, vsxu-player,....)18:21
saidinesh5(everything depends on libvsxu)18:22
saidinesh5so 1) should i have to include the lib/*.so in the libvsxu-dev.install also ?18:22
saidinesh5or just making it depend on libvsxu is enough?18:23
saidinesh5?18:30
cjwatsonsaidinesh5: typically *.so.* should go in the runtime packages and *.so should go in the -dev packages18:41
cjwatson*.so being symlinks to *.so.* in any sane upstream package18:41
saidinesh5cjwatson: you mean *.so.* is like *.so.version?18:45
=== deryck[lunch] is now known as deryck
cjwatsonsaidinesh5: that's what I mean, yes19:06
* saidinesh5 should probably edit some CMakeFiles for this now19:07
saidinesh5cjwatson: could you also take a look at the ppa i ve created and the recipie i m trying to make?19:07
saidinesh5cjwatson: CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:91 (MESSAGE):19:12
saidinesh5  Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY)19:12
barryslangasek, cjwatson: re bug 924079.  i've read the bug and cjwatson's post (which seems to have no follow ups?).  what needs to be done here?  are you looking for someone to verify that if the patches were sru'd that it solves the problem?  there still seems to be the issue of abi breakage though, right?19:13
ubottuLaunchpad bug 924079 in apt (Ubuntu Oneiric) "do-release-upgrade fails to upgrade from Oneiric to Precise" [High,Triaged] https://launchpad.net/bugs/92407919:13
saidinesh5what should i include so that that builds?19:13
slangasekbarry: cjwatson's suggestion today was that this might be better done as a release-upgrader-specific backport, like we did for lucid19:13
slangasekbarry: I don't know if that's a better answer than trying to SRU patches to apt; mvo's your expert :)19:14
barryslangasek: yeah, sorry mumble was so problematic today ;)19:14
slangasek:)19:15
barryslangasek: i'll look into it and make sure to follow up with mvo in the morning (he appears to be off-line right now)19:17
slangasekbarry: ack19:17
saidinesh5but libgl and stuff should be installed because of libglfw-dev ...shouldnt they?19:20
cjwatsonsaidinesh5: sorry, I'm not going to have time to look at your package (especially if it's cmake, which I don't speak at all) - just offering general advice19:22
saidinesh5cjwatson: ah its okay.. basically i m just a little confused about the package dependancy...19:22
cjwatsonbarry: I vaguely remember that mvo put together a non-ABI-breaking patch for that, too, but I don't have a record of it, so perhaps chase that up19:23
cjwatsonbarry: it may ultimately need to be an SRU to apt - I'm just worried about timing, mostly19:23
saidinesh5like it says it cant find OpenGL libs. but libglfw-dev should pull libgl and friends ...... isnt it?19:23
cjwatsonsaidinesh5: my first guess would be that the upstream build system is buggy and can't cope with libraries installed in multiarch locations (e.g. /usr/lib/x86_64-linux-gnu/), but it may not be that19:24
cjwatsonyou'll need to look into whatever logs it gives you (if any) in detail19:24
barrycjwatson: ack19:25
* saidinesh5 checks 19:25
saidinesh5libxrandr2 (>= 2:1.3.0-3), libc6 (>= 2.1.3), libgcc1 (>= 1:4.1.1), libglfw2 (>= 2.6), libpng12-0 (>= 1.2.0), libjpeg8 (>= 6b1-1), libglew1.6 (>=1.6.0)19:26
saidinesh5bleh19:26
saidinesh5they should have been -dev libs19:26
cjwatsonare those Depends or Build-Depends?19:27
saidinesh5i put them as Build-Depends19:28
cjwatsonright, that would be wrong19:28
cjwatsonalso micromanaging :) you don't need to build-dep on the C library ...19:28
saidinesh5Ahh ya...19:29
cjwatsonin most cases you probably shouldn't version the build-deps either, unless you know you require API (not ABI) added in that version19:29
cjwatsonnote that runtime depends don't necessarily correspond to sensible minimum versions on build-depends19:29
saidinesh5Ahh cool that answers my next questioN! :D19:31
saidinesh5cjwatson: if i include libglfw-dev will that install the needed headers for libglfw? (like libgl1-mesa-dev etc..) ?19:33
saidinesh5(like libglfw depends on libgl)19:34
jibeldoko, same error on upgrade with DEFAULT_VERSION = (2, 6) I collected a bit more informations with debug enabled. I'll update the report.19:51
=== xnox_ is now known as xnox
cjwatsonsaidinesh5: don't know offhand, look at its dependencies and that should say20:15
saidinesh5hmm.... looking into it cjwatson :)20:15
slangasekbryceh: I don't suppose bug #966868 resembles the X-racing-drm bug of yours?20:37
ubottuError: Launchpad bug 966868 could not be found20:37
slangasekoh hush20:37
brycehslangasek, hmm, looking20:41
brycehsomeone needs a name for when you're investigating one bug and notice three other unrelated bugs along the way...20:44
stgraberbryceh: normal debugging?20:45
slangasekbryceh: yak shaving? :)20:45
brycehthere we go20:46
brycehslangasek, anyway, yeah it seems to be crashing trying to open the intel device driver.  could be same bug20:47
bryceher, same issue20:47
slangasekok20:47
brycehslangasek, i915 got initialized around 6.4-6.5 sec; if you can tell when plymouth was firing you can see if it was before or after that.  that'd be more definitive20:49
slangasekbryceh: yeah, I don't have timestamps for that by default20:52
brycehslangasek, adding plymouth:debug might make some timestamps show up.  (sudo xdiagnose, first option)20:52
slangasekyep20:52
slangasekactually, no, even then we don't get timestamps20:52
brycehslangasek, #4 in that stack looks like libdrm code20:58
brycehdunno if its the same libdrm code as that other intel bug though.20:59
brycehslangasek, posted comment on the bug.  I think escalating to Intel would be the logical next action.21:12
=== salem_ is now known as _salem
slangasekbryceh: if the raciness is due to an Ubuntu sauce patch?  (or is that now upstreamed?)21:12
brycehslangasek, I think so.  They actually do care about ensuring their stuff works with Ubuntu.21:15
=== highvolt1ge is now known as highvoltage
slangasekok21:16
brycehslangasek, if nothing else they may be able to give advice21:16
slangasekwhat's the escalation path?  do we need apw looped in?21:16
brycehI usually escalate and then bring apw in once I get some feedback from upstream21:17
slangasekok21:17
slangasekI'm happy to be part of the conversation if it helps21:17
brycehslangasek, I'd expect so21:18
brycehslangasek, fwiw I do think that we'll get a flame back telling us not to run the kernel i915 this way.  but we'll see.21:24
slangasek:)21:24
brycehslangasek, you'll need to manually sub yourself to https://bugs.freedesktop.org//show_bug.cgi?id=48894 because bugzilla sucks21:26
ubottuFreedesktop bug 48894 in Driver/intel "plymouthd crashed with SIGABRT in __assert_fail_base()" [Major,New: ]21:26
* slangasek searches for the 'subscribe' button because bugzilla sucks21:27
brycehput your email addy in cc21:28
brycehyou might have to register first21:28
slangaseknah, am registered, just couldn't remember the next step :)21:28
slangasekbryceh: how much do you know about the kernel events that we get for drm devices21:29
slangasek?21:29
brycehslangasek, not much, I generally don't play at that level too often21:48
brycehslangasek, past experiences tinkering in libdrm has left me with a general dread of this part of  the stack21:49
SpamapSUgh, I never know where to ask this21:49
SpamapSUDD ...21:49
slangasekbryceh: ;)21:49
SpamapSwhat do I do when merge-upstream decides to rename .. everything21:49
brycehSpamapS, turn to drink?21:49
ScottKSpamapS: dput and let the importer sort it out.21:49
SpamapSScottK: I have staged changes. :-/21:50
SpamapSso my only recourse is to apply those manually w/ patch21:50
SpamapSwhich is what I've done21:50
SpamapSbut.. that *sucks*21:50
slangasekbryceh: so the "Best" fix is still to just have a reliable event that the upstart jobs can key off of... I'm wondering if there actually is a different event already that meets this need, or if not, how we should fix it so there is21:50
ScottKWhat's more important: The history or the brain cells lost figuring out the right UDD way to do it?21:50
slangasekSpamapS: what branch, what command?21:50
SpamapSslangasek: lp:ubuntu/juju21:51
SpamapSslangasek: have tried both from a tarball and from the upstream branch..21:51
SpamapSit decised that the directory 'juju' is in conflict21:51
slangasekheh21:51
SpamapSwhich would be.. the entire program :-P21:51
slangasekthat suggests past branch divergence21:52
SpamapSPossibly21:52
slangasekwhat's the command I should run to try to reproduce this?21:52
SpamapSslangasek: bzr merge-upstream lp:juju21:52
slangasekhmm, revision 1.1.11 doesn't help... imported an upstream tarball without merging the branch21:53
slangasekSpamapS: is there also a tarball to merge at the same time?21:53
slangasekthe "proper" answer is to merge both, not either/or21:53
brycehslangasek, yeah an event seems like a better solution.  the suggestion yesterday to hack a sleep loop into libdrm hasn't been sitting well with me.21:53
SpamapSslangasek: bzr export from the juju trunk to a tarball produces the same result, because thats basically what merge-upstream does anyway21:53
slangasekSpamapS: so there isn't a pre-existing tarball?21:54
slangasekare you *creating* one as part of this upload?21:54
apwbryceh, do i need to take that patch to upstream on the morrow and see waht they make of it?  perhaps they'll have some better ideas21:54
SpamapSslangasek: yes21:54
SpamapSslangasek: 0.5+bzr531 has never been uploaded21:54
slangasekSpamapS: ok, so you should do the bzr export first to get your tarball, then reinject it with the merge-upstream21:54
SpamapSslangasek: thats what I tried. *same* result.21:55
slangasekok21:55
SpamapSbecause thats exactly what merge-upstream does IIRC21:55
brycehapw, I think so, yes.  If you have the link still handy I can post it to them now21:55
slangasekSpamapS: give me a minute for my terminal to catch up with us then :)21:55
SpamapSslangasek: I don't know why I seem to be the only one who runs into all the UDD weirdness. :-P21:58
apwbryceh, http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=commitdiff;h=6d74feca6235b463ade4ecddd1dfdb73d30a2ff7;hp=e29a4668d7441aa88d8015da51674a7e8159312b21:58
slangasekSpamapS: well for starters, I've never seen this message before from bzr merge:21:58
apwbryceh, thats what we are using to prevent the crash21:58
slangasekExporting upstream branch revision kapil.thangavelu@canonical.com-20120415230912-d0itvlx1i2ft0c41 to create the tarball21:58
slangasekso the juju branch seems special :)21:58
SpamapSslangasek: haha ok21:58
apwbryceh, so ... drop me an email with wherever we are at so i can follow up in the am21:59
* SpamapS hates being special21:59
hallynhm, so if someone reports a broken do-release-upgrade, but because they had left processes running (causing deluser to fail), do we call that invalid, or should the pkg upgrade deal with it gracefully?21:59
brycehapw, add yourself to cc on https://bugs.freedesktop.org//show_bug.cgi?id=4889422:00
ubottuFreedesktop bug 48894 in Driver/intel "plymouthd crashed with SIGABRT in __assert_fail_base()" [Major,New: ]22:00
slangasekSpamapS: so what's astonishing to me is not that there was a directory conflict, but that the *contents* of those directories seem to be entirely disjoint22:00
slangasek$ diff -uNr docs* | diffstat22:00
slangasek[...]22:00
slangasek 37 files changed, 4685 insertions(+), 78 deletions(-)22:01
slangasekSpamapS: why does the upstream branch look nothing like the current UDD branch?22:01
SpamapSslangasek: thats about right.. lots of features landed22:02
brycehapw, added you to the cc22:02
SpamapSslangasek: though thats not the same diffstat I see in the branch doing 'bzr diff -c 519..531'22:02
SpamapSslangasek: would it be better to back up to 0.5+bzr504-0ubuntu1  (r10) ?22:03
slangasekwell, let's see22:04
SpamapSslangasek: I have to step AFK for 15 minutes .. will be back ASAP22:04
slangasekbryceh: someone want to tell fd.o they're not in UTC? :P22:09
brycehslangasek, OMG don't you dare22:09
slangasekyou like all incoming bugzilla mail being sorted 7 hours in the past? :)22:10
brycehslangasek, that's a quick path to getting flamed by mithrandir22:10
slangasekheh22:10
brycehseriously, hang out on #freedesktop a while22:10
slangasekI'm happy for them to use UTC for their timezone setting22:10
slangasekas long as they set their friggin' clocks right22:10
brycehslangasek, I recommend raising the issue with him by pinging it (but don't mention what the ping is about).  he loves that.22:12
slangasekhahaha22:13
slangasekbryceh: I have to be careful; if I taunt him too much, he'll make upstart in Debian a metapackage depending on systemd22:13
bdmurrayslangasek: in bug 984693 update-notifier was just finishing up correct?22:17
ubottuLaunchpad bug 984693 in msttcorefonts (Ubuntu) "ttf-mscorefonts-installer also installs Flash" [Undecided,New] https://launchpad.net/bugs/98469322:17
slangasekbdmurray: yes, apparently they had the package installed already but the trigger hadn't done its job yet22:18
brycehslangasek, o_O22:18
brycehslangasek, you're gonna get me banned off freedesktop!22:18
slangasek;)22:20
SpamapSslangasek: back22:23
brycehslangasek, got a little feedback from jbarnes on the bug22:23
SpamapSslangasek: so, is there some version missing from the graph in that branch?22:23
slangasekSpamapS: well, the version you pointed me at failed the same way22:23
slangaseklooking at the history now22:23
slangasekSpamapS: has this merge-upstream *ever* worked for you, when pulling from the branch?22:24
smoserhey...22:24
smoserhow can i make my system not multiarch ?22:25
slangasekbecause sure enough, these main directories were added separately in the two branches22:25
smoseri'm looking for 'apt-get update' to not get i386 lists or show packages.22:25
slangaseksmoser: you can nuke /etc/dpkg/dpkg.cfg.d/multiarch; but this will make some software uninstallable for you22:25
SpamapSslangasek: I think so. But its hard to recall frankly. I have a lot of merge-upstream issues22:25
smoserslangasek, i'm ok with that. thank you.22:26
slangasekSpamapS: 'bzr log -n0 juju' shows a completely different history for the directory on the ubuntu branch vs. the upstream branch22:26
slangasekSpamapS: so you can do one of two things: 1) merge from the tarball only, which shouldn't fail like this; 2) port your local changes over on a one-time basis and nuke all of the .moved directories, which gets you in sync with the upstream branch going forward22:27
SpamapSslangasek: I think at some point I did an upload w/o committing.. so the importer grabbed it instead. Perhaps thats the issue?22:27
slangasekwell, the first commit by you on the UDD branch is revno 722:28
slangasekbefore that they were auto-imported22:28
SpamapSok22:28
SpamapSI like the idea of nuking and getting back on track22:28
slangasekbut *none* of the UDD branch history shows the history of the upstream branch... so what you're seeing now is the inevitable result of trying to merge two branches without shared history22:29
SpamapSbut I'm not sure what that means.. so you're saying back up to the last uploaded version, merge upstream, fix .moved dirs, then manually patch in my changes?22:29
slangasekwith or without the "Back up" part22:29
SpamapSok, and would just bzr rm'ing the .moved dirs suffice?22:30
slangasekor maybe just 'bzr resolve *.moved'22:30
slangasek(which you have to do anyway; I don't remember if the resolve also rm's in this case)22:30
SpamapSit doesn't22:30
SpamapShave to rm first22:31
SpamapSthere are issues with that approach though22:31
SpamapSthe 'examples' dir, for instance, has no README file now.. but the upstream version definitely does have that README file22:31
slangasekah, really?22:32
SpamapSyeah, its like only things that got touched are there22:32
slangasekhmmmm22:32
SpamapSfrankly I'm ready to just build a .dsc as I see fit, and let the importer handle it.22:32
slangasekwell, that's fine too22:33
slangasekand approximately equivalent to doing a merge-upstream *without* referencing the upstream branch22:33
SpamapSI suspect if I --overwrite with all the things after the last upload uncommitted, that would do it, right?22:33
slangasekheh, the importer hates --overwrite22:33
SpamapSslangasek: I get the same problem whether I merge-upstream lp:juju or an exported tarball tho.22:33
slangasekif you leave it as-is, the importer will move your branch aside22:33
SpamapSslangasek: it wouldn't care if I used --overwrite to get it back to a state it knows about though, right?22:34
slangasekI'm not convinced that's true22:34
SpamapSgah!22:34
slangasekthe importer wigs out on nearly any use of --overwrite I've ever done22:34
slangasekmaybe I'm just lucky that way22:34
brycehslangasek, posted jbarnes' comments to the bug.  Seems he's recognizing it as a core drm bug22:34
slangasekbryceh: ack22:34
SpamapSmy understanding is that it keeps track of revids that it has seen22:34
SpamapSso as long as I go back to the revid that it saw last, and no further, it should be ok22:35
slangasekSpamapS: so merge-upstream from a tarball gives me 27 fewer conflicts ;)22:35
SpamapSslangasek: progress22:35
SpamapSslangasek: it still would be missing files that got pushed over to the .moved dirs though22:36
brycehslangasek, guessing we may have tons of dupes scattered about of this basic issue.22:36
slangasekSpamapS: yeah, this is an extra-special merge failure.  I don't have any idea why it's not happy using the existing dirs22:37
slangasekSpamapS: anyway, don't worry about reverting anything out of the UDD branch; just prep your upload however you'd like and upload it, and the importer will happily move your commits aside in favor of the authoritative contents of the upload22:37
SpamapSok that sounds like a plan..22:38
SpamapSI do wish we had a better way to resolve this22:38
slangasekwell, this is very much a corner case22:38
SpamapSlike, at this point, I'm building a package by adding a debian dir to the tarball extracted22:38
slangasekI've never seen merge-upstream wig out like this about directories, when referencing a tarball22:38
SpamapSbasically uupdate22:39
slangasekyep22:39
slangasekSpamapS: can you file a bug against udd about this, though?22:40
SpamapSslangasek: yes happily22:40
slangasekthis is deep into "that shouldn't have happened" territory22:40
SpamapSThis will be my second "that should happen" UDD bug22:40
SpamapSslangasek: bug 985285 FYI22:45
ubottuLaunchpad bug 985285 in Ubuntu Distributed Development "juju packaging branch fails using merge-upstream from tarball and upstream branch" [Undecided,New] https://launchpad.net/bugs/98528522:45
slangasekcheers22:45
roaksoaxcjwatson: around?22:47
cjwatsonroaksoax: yes22:47
roaksoaxhow can I disable multiarch on d-i? apt-setup/multiarch string false? or similar?22:47
cjwatsonroaksoax: d-i apt-setup/multiarch string22:48
cjwatson(i.e. empty)22:48
slangasekdoes that do any good?  /etc/dpkg/dpkg.cfg.d/multiarch is also a conffile22:51
cjwatsonheh22:52
cjwatsonit may not, now you mention it22:52
cjwatsondo I need to fix that?22:52
cjwatsonhttp://paste.ubuntu.com/936150/22:52
slangasekcjwatson: I suppose so, if you care about this working :)22:53
roaksoaxcjwatson: awesome thanks22:54
cjwatsonslangasek: I care about not having to remember that it doesn't for five years22:55
slangasekcjwatson: ack ;)22:55
slangasekyeesh, can someone make sense out of https://launchpadlibrarian.net/66149842/Stacktrace.txt for me?22:55
* cjwatson uploads22:56
slangaseksomewhere between frames 5 and 4, we've lost a pointer on the stack22:56
slangasek(what was passed as arg 3 shows up as arg 2)22:56
roaksoaxcjwatson: and would we be able to use something like d-i apt-setup/universe boolean false ?23:00
cjwatsonroaksoax: yes23:02
roaksoaxw23:02
roaksoaxcjwatson: awesome, thanks23:02
cjwatsonslangasek: I'm stumped.23:04
slangasekcool23:04
cjwatsonI assumed it was a missing prototype, but doesn't seem to be.23:04
slangasekyeah, that was my first guess23:04
cjwatsonAny compiler warnings?23:05
slangaseknone of relevance23:05
slangasek(some asprintf warnings)23:05
slangasekI'm doing a rebuild now with warnings++23:05
cjwatsonIs there any affinity between bug dups and architecture?23:06
cjwatsonI see that one's amd6423:06
slangasekcjwatson: the first 4 and the last 2 are all amd64; I'm going to assume for the moment they all are23:07
cjwatsonAll amd64, checked in lp-shell23:08
cjwatson>>> master = lp.bugs[733453]23:08
cjwatson>>> for bug in [master] + list(master.duplicates):23:08
cjwatson...  for line in bug.description.splitlines():23:08
cjwatson...   if line.startswith('Architecture:'):23:08
cjwatson...    print bug.id, line23:08
cjwatson...    break23:08
cjwatson...23:08
slangasekaha23:09
cjwatsonthat pattern saves a lot of time clicking around :)23:09
slangasekI would say so :)23:09
slangasekcjwatson: -Wall does not enlighten23:11
slangasekI wonder if something went wrong with the retracer on that one... would be good to have a way to double-check against the current version, rather than the retracer discarding any trace23:13
slangasek(why does the retracer not attach a trace when declaring it a dupe?  seems like that'd be simple enough...)23:13
* cjwatson tries building it locally to see if gdb says anything useful23:13
slangasekwell, that's the other thing... I've never seen this bug23:15
slangasekso maybe it's simple memory corruption23:16
* slangasek afks for a bit23:16
cjwatsonbizarre manifestation of it though23:17
=== tlyu_ is now known as tlyu

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!