=== L3top is now known as WhiteDynamite
=== WhiteDynamite is now known as L3top
slangasekbroder: blast, follow-up to bug #858122 shows that I missed /etc/rc6.d/S35networking... not sure how important that is02:18
ubottuLaunchpad bug 858122 in insserv (Ubuntu Oneiric) "incomplete migration to /run (shutdown script order has been demolished)" [High,Fix committed] https://launchpad.net/bugs/85812202:18
=== dendro-afk is now known as dendrobates
=== pp7 is now known as malkauns
L3topanyone got an explanation why deb mirror://mirrors.ubuntu.com/mirrors.txt lucid main restricted universe multiverse might throw CD-ROM errors?03:45
L3topno cd references in the sources.list03:46
L3topnm... nothing to do with the mirrors.04:10
broderslangasek: i bet there are unfortunate nfs interactions05:38
pittiGood morning06:07
ajmitchmorning pitti06:17
hrwcan we change one thing related to compatibility with lts? Lucid has libmpfr1ldbl package which is present in all next releases up to oneiric (which lacks it). This way packages built for lucid (aka 'last LTS') work on maverick/natty but fail to install on oneiric ;(07:22
hrwwould be nice to have such compatibility for all <(lts+1) releases07:23
micahghrw: the source was removed07:23
micahgnot in Debian either07:23
hrwmicahg: Debian has longer release time07:24
hrwmicahg: to provide binaries for oneiric I need now bump 8 packages versions, build them in order - with ppa builders queue it will take another 3 days07:25
micahghrw: it's not in squeeze07:25
hrwor will grab older mprf from lucid and recompile under oneiric and check will it work07:25
micahghrw: ah, was migrated to mpfr407:26
hrwmicahg: maverick migrated to mpfr4 but kept old version.07:27
hrwin oneiric it got dropped07:27
micahgright, until the migration was complete07:27
micahghrw: if there are specific LTS -> LTS upgrade issues, we can address those, but we won't add back the old source07:28
hrwmicahg: I am fine with lack of old library in new lts. I complain about lack of in in lts-107:28
micahghrw: we remove libraries basically when Debian does unless we need them for something, it was removed for squeeze, so we removed it for oneiric07:29
micahghrw: is something specific broken in oneiric because of this?07:29
micahgthe only thing we try to guarantee between upgrades is a stable upgrade path, not that a specific version of something is available07:31
infinityhrw: Keeping libraries around just so people only need to build a binary once for 4 releases isn't sane.07:31
infinityhrw: There's a reason the PPAs build for all releases.07:31
infinityhrw: If you want to provide oneiric packages, build them on oneiric.07:31
micahgI'm wondering why the packages are needed in the first place unless something outside the archive was using it07:32
infinitymicahg: That's what he's saying.  He wants to build on lucid and have it work on lucid->oneiric, so yes, not archive packages.07:33
micahgwell, we generally don't advise that anyways AIUI, each release usually brings toolchain improvements and extra security hardening07:34
hrwmicahg, infinity: if package build for lucid works under next releases then why bother with rebuilding?07:36
hrwand toolchain improvements are not something important for cross toolchain backport07:36
infinityhrw: No one's saying you must rebuild it if it works.  We don't rebuild things "just cause" either.07:37
infinity(There are still packages in precise that were built on natty)07:37
micahgalthough in the above case we probably should to pick up --as-needed :)07:37
infinityBut we're not going to guarantee compatibility like you're asking for, that's all.07:37
hrwinfinity: ok07:37
infinitymicahg: It'll all get rebuilt in time.  *shrug*07:38
infinitymicahg: Most of us don't like gratuitous archive/mirror churn for tiny gains.07:38
micahgwell, we still have packages from warty :)07:38
hrwbuilding mpfr under oneiric now - will provide it in ppa07:38
infinityhrw: Why would you do that?07:38
infinityhrw: Why not just build your package against the new library?07:39
micahgsure, not for gratuitous purposes, but some packages can really simplify the dependency change07:39
micahginfinity: you just answered that question when I asked it :)07:39
hrwinfinity: it took me 3 days of building for lucid07:39
hrwinfinity: with 21h queues I prefer to build one instead of 807:40
infinity(The PPA queues are empty right now)07:40
hrwok, worth try07:40
hrwbe back in 1h07:44
=== smb` is now known as smb
dholbach@pilot in08:48
=== udevbot changed the topic of #ubuntu-devel to: Precise Beta-1 Freeze in effect. Archive: open | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/xmGdCW | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach
dholbachcan somebody please reject https://code.launchpad.net/~l3on/ubuntu/precise/rawstudio/fix-ftbfs/+merge/94701 - the bug in question was solved differently already09:03
=== doko_ is now known as doko
=== tkamppeter_ is now known as tkamppeter
dholbachthanks pitti09:35
hrwcan someone push vwstreams to archive to get it built on armel/armhf? This will make wvdial buildable on armhf. I built both on mx53/armel in armhf chroot.09:54
Sweetsharkdholbach: Hey! If I forget to say that to jono when he is back online, please say a big thanks to jono for his kudos to LibreOffice.10:00
dholbachSweetshark, you could comment on his blog post! ;-)10:01
dholbachbut yeah I have a call with him later on and if I don't forget it, I'll let him know :)10:01
pittihrw: what do you mean by "push to archive"?10:01
dholbachSweetshark, how is your upload rights application coming together?10:01
mptmvo, I got "Not all updates can be installed" and "Do you want to start the upgrade?" dialogs opening at the same time. Does that mean I should upgrade, or not? :-)10:02
dholbachpitti, could it be it never built for armel/armhf?10:02
pittiit didn't10:02
pittibut even doko's rebuild didn't10:02
pittiso a mere rebuild won't help; not sure why10:03
micahgpitti: http://bazaar.launchpad.net/~ubuntu-core-dev/packages-arch-specific/ubuntu/view/head:/Packages-arch-specific#L27610:03
dokohrw, pitti: needs porting, and now it's in P-a-S. do you volunteer?10:04
pittiright, was just looking there10:04
pittidoko: hrw says it's working for him?10:04
micahgDebian seems to be building wvdial on armhf at least10:05
Sweetsharkdholbach: I google+ shared his blog with a big thanks already.10:05
pittihrw: it's an architecture blacklist for packages which don't limit the architectures in debian/control10:05
dholbachSweetshark, ah cool10:05
hrwpitti: thx10:05
pittiinfinity: can we just change Packages-arch-specific, or is this still fully in sync with Debian?10:06
mvompt: *urgh* could you make a screenshot please and show it to me?10:06
Sweetsharkdholbach: not much happening with the application. but didrocks did a upload for me, so he might comment on that too, once he finished answering "where is my workspace switcher?" questions ...10:07
micahgif someone's rebuilding wvstreams, can you drop the Qt package, it's unused and built against qt310:07
hrwI never owned normal modem so have no knowledge of wvdial and how to use/test it. Just saw that it is in ftfbs queue for armhf so decided to take a look10:07
dholbachSweetshark, all the best with the application then :)10:07
mptmvo, http://i.imgur.com/oBotI.png10:10
mvompt: this is indeed pretty ugly10:12
mptmvo, anything you want me to capture before I click "Cancel"?10:12
mvompt: no, thanks. but if you could run "apt-get dist-upgrade --simulate -o Debug::pkgProblemResolver=true" and paste/mail me the output, that would be nice10:13
seb128mvo, mpt: hey, while you are around, small question, is the fact the update-manager standard "install upgrades" dialog keep resizing according to the package name length, known/going to be worked this cycle?10:14
mptmvo, nothing informative: http://paste.ubuntu.com/858969/10:15
mptseb128, I doubt it -- mvo is pretty busy, :-) and update-manager doesn't attract volunteers for reasons I haven't figured out yet10:16
seb128mpt, what would be the fix for that? just ellipsize the package names...?10:17
mvompt: that is confusing, its giving a error that it can not install all updates first, but apt-get does not show any trace of this :/10:17
mvoseb128: the download/install dialog? in the release upgrader ? or for regular updates?10:17
seb128mvo, regular updates10:17
seb128mvo, the one which makes "downloading <package>"10:18
mptseb128, I think you're right, just ellipsizing the name10:18
seb128mvo, it's width change with the <package> string length10:18
seb128mvo, which makes lot of bouncing, especially on the "unpackaging" steps10:18
seb128mpt, thanks, that seems trivial enough, I might have a look if mvo doesn't ;-)10:19
mvoseb128: ok, that should be straightforward indeed, aptdaemon is the package10:19
mvoseb128: maybe a gtk3 regression10:19
seb128mvo, ...!!!10:20
mvoseb128: self.set_ellipsize(Pango.EllipsizeMode.END) is in the code10:20
seb128mvo, I will have a look, thanks10:20
seb128mvo, mpt: sorry I didn't mean to hijack your discussion10:20
mvoseb128: thanks, look at lp:aptdaemon and there aptdaemon/gtk3widgets.py in AptProgressBar10:22
pittiev: hm, bug 901675 seems to be from introducing threading into the GTK GUI :/10:22
ubottuLaunchpad bug 901675 in apport (Ubuntu) "apport-gtk assert failure: python: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed." [Medium,Confirmed] https://launchpad.net/bugs/90167510:22
seb128mvo, thanks10:22
pittiev: can we avoid using GTK from more than one thread?10:22
mvoseb128: maybe something missing there10:22
mptmvo, unfortunately it's not reproducible -- second time I tried it I just got the "Do you want to start the upgrade?"10:23
mvompt: there must be a law or something that bugs are 10x harder to reproduce for developers or something :/ but thanks a bunch for letting me know about it10:24
mptmvo, if all three of those windows were a single window, the bug would be fixed one way or another :-)10:25
seb128mvo, I wonder if that's because you don't force any max geometry on the dialog, so rather than ellipsizing it just shows to resize10:29
seb128mvo, i.e you "        self.progress.set_size_request(350, -1)" but I don't think set_size_request block it to upscale10:29
dholbachpitti, regarding bug 940566 it seems like libquvi-scripts will need a MIR :-/10:33
ubottuLaunchpad bug 940566 in libquvi (Ubuntu) "FFe: Sync libquvi 0.4.0-1 (main) from Debian experimental (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/94056610:33
mvoseb128: oh, that could well be it10:34
pittidholbach: was this a splitout like "quvi", or a new build dep?10:34
ansgarpitti: Also splitout.10:35
pittithat's fine then10:35
dholbachthen I'll go ahead with the sync and everything around it10:35
dholbachthanks pitti, thanks ansgar10:35
pittimvo: do you see what apt complains about in https://jenkins.qa.ubuntu.com/view/Precise/job/precise-upgrade-oneiric-universe/lastFailedBuild/ARCH=amd64,LTS=non-lts,PROFILE=universe,label=upgrade-test/artifact/universe-amd64/apt.log ?10:37
pittimvo: libcv-dev was split into several packages, which breaks:/replaces: the older versions; this seems not unusual to me10:37
dholbachseb128, didrocks, did you have a chance to talk to mhall119 about the quicklist additions?10:39
seb128dholbach, yes10:39
seb128dholbach, and to jono10:39
dholbachI'm on duty as patch pilot today and wonder what to do about the merge proposals10:39
seb128dholbach, which ones ?10:40
seb128dholbach, if that's universe we agreed to postpone those to next cycle and discuss at UDS10:40
dholbachhttp://reqorts.qa.ubuntu.com/reports/sponsoring/ ← all the ones saying "add_quicklist"10:40
pittimvo: in general, what do you look out for first in these logs? "Holding back" lines?10:40
seb128dholbach, let me review those10:41
pittiRiddell, mvo: https://jenkins.qa.ubuntu.com/view/Precise/job/precise-upgrade-oneiric-universe/lastFailedBuild/ARCH=amd64,LTS=non-lts,PROFILE=universe,label=upgrade-test/artifact/universe-amd64/apt.log also seems to have trouble with replacing koffice-data (which has zero rdepends left) wit calligra-data; would it help to move "Conflicts: kformula, koffice-data" to "Breaks: kformula, koffice-data"?10:42
pittiI still don't understand why apt is so hesitant to remove a package which doesn't even exist any more and has no rdepends10:43
mvopitti: I usually start by looking at the last few lines and walk my way backwards to figure out what exactly is going on10:43
pittiand holds it back instead of replacing it with the superseding pacakge10:43
Riddellpitti, mvo: or should we just make transitional packages?10:43
pittiRiddell: seems a little exaggerated for -data packages to me; but perhaps Breaks: will help10:43
pittibut still, it seems to me that apt is overly picky here10:44
smbpitti, Hm, apport retracer just marked a crash I had this morning as a duplicate of a bug expired two months ago and then got rid of all the evidence... That seems a bit unhelpful to me... :/10:44
mvotransitional will fix it for sure, the log shows that the "score" of koffice-data is 4 but calligra-data:amd64 only 3 - if its a 1-to-1 exchange of the name the score should be equal and if koffice-data is no longer in the archive it gets a penality10:45
pittismb: can you please file a bug against apport for this and assign to me? I guess it doesn't handle the "Expired" state, it's relatively new10:45
mvopitti: its a tradeoff, its hard for apt to know what is important to the user but yeah, in this case its not doing the right thing10:45
mvo  Installing koffice-data as Depends of koffice-libs10:46
mvolooks odd10:46
pittimvo: oh, where do you see the score?10:46
smbpitti, Ok, will do. thanks10:46
mvopitti: its the integer in the following lines:10:46
mvo  Considering koffice-data:amd64 4 as a solution to calligra-data:amd64 310:46
mvoeh, line10:46
mvosorry, I know that the output is really hard to read10:46
pittimvo: koffice-libs is also gone, hmm10:46
mvo  Installing koffice-libs as Depends of kpresenter10:47
mvowas the transition still in progress when this happend maybe?10:47
pittihm, I think kpresenter and friends should have a transitional package10:47
pittiit went away as well10:47
pittiwhich probably causes the upgrade confusion10:48
pittimvo: no, that test upgrade is very recent10:48
mvopitti: odd, if its just a transitional package, why would it cause the libs to get installed10:48
pittiRiddell: so it should help to add transitional packages for the applications like kpresenter10:48
pittimvo: it's not; kpresenter was also dropped apparently10:48
pittiso the existing kpresenter package keeps koffice-{libs,data}10:49
pittiRiddell: hm, is there a calligra equivalent for kpresenter?10:50
pittiRiddell: so we'll need a transitional package for at least that one10:51
Riddellok, can do10:51
pittifor kspread apparently as well10:51
Riddellpitti: why that one?10:51
pittiand kword10:51
Riddellall the apps?10:51
pittiRiddell: these are top-level application packages that users have installed10:51
pittiwhich need to be transitioned to their equivalent of calligra10:51
pittiotherwise apt woudln't know what to do and just keep them instead of upgrading10:52
pittiRiddell: want a bug report for it?10:52
Riddellpitti: a bug is handy yes10:53
Riddellpitti: but there are other applications in koffice, don't they need transitionals too?10:53
pittiRiddell: yes10:53
pittiah, bug 91543110:53
ubottuLaunchpad bug 915431 in calligra (Ubuntu) "kexi can not be dist-upgraded" [Undecided,New] https://launchpad.net/bugs/91543110:53
pittiI'll generalize this10:53
pittimvo: ok, that covers calligra; I'm still baffled whaht's going on with the opencv stuff10:54
mvo  Considering libopencv-features2d-dev:amd64 8 as a solution to libcv-dev:amd64 110:55
dholbachrickspencer3, hey - how are you doing?10:56
mvothat seems to be the crucial bit10:56
rickspencer3hi dholbach10:56
rickspencer3doing well10:56
dholbachrickspencer3, I noticed the quickly patches in the sponsoring queue (929417, 929572, 929420) - how do you want to go about them?10:56
rickspencer3hi dholbach funny you should mention tat10:57
rickspencer3I'm working on 929417 at this very moment10:57
rickspencer3dholbach_, for the others, could you please ask didrocks/mterry in #quickly?10:57
dholbach_sorry, just had the network kick me out10:58
mvopitti: hm, no, actually "Broken libopencv-features2d-dev:amd64 Depends on libopencv-highgui-dev [ amd64 ] < none -> 2.3.1-7 > ( universe/libdevel ) (= 2.3.1-7)"10:58
dholbach_rickspencer3, I noticed the quickly patches in the sponsoring queue (929417, 929572, 929420) - how do you want to go about them?10:58
dholbach_rickspencer3, merge them upstream, roll a release, then get it in precise?10:58
didrocksrickspencer3: dholbach_: I'm piloting on wednesday, I planned to review them by then10:58
rickspencer3thanks didrocks10:58
rickspencer3didrocks, I'll strive to get the tutorial updated by then10:59
didrocksthanks rickspencer3 ;)10:59
mvopitti: and that leads to "Broken libopencv-highgui-dev:amd64 Depends on libjpeg-dev [ amd64 ] < none > ( none )" and that to "Broken r-base-dev:amd64 Depends on libjpeg-dev [ amd64 ] < none > ( none )" which seems to be the root of it11:00
pittiRiddell: I updated bug 915431, and added a list of all (hopefully) missing transitionals11:00
ubottuLaunchpad bug 915431 in calligra (Ubuntu Precise) "needs transitional packages for old koffice application names" [High,Triaged] https://launchpad.net/bugs/91543111:00
pittijibel: ^ FYI (I think I tagged it as you do)11:00
=== dholbach_ is now known as dholbach
pittimvo: we so much need to graphviz-ize this :)11:01
mvopitti: oh yes!11:01
jibelpitti, excellent. thanks!11:02
pittimvo: oh, thanks! so if we just fix that dependency, it shoudl be better11:02
pittimvo: odd, I thought that libjpeg62-dev and libjpeg8-dev ought to Provide: libjpeg-dev, but seems they don't11:02
mvopitti: there is some fishy stuff here "Broken libjpeg-turbo8-dev:amd64 Conflicts on libjpeg62-dev [ amd64 ] < 6b1-1ubuntu2 -> 6b1-2ubuntu1 > ( libdevel )" too11:02
micahgpitti: no, having both libjpeg*-dev packages provide libjpeg-dev creates depwaits11:03
mvopitti: it maybe enough to have a addition "provides: libjpeg62-dev" in libjpeg-utrbo8-dev" - but I don't know why we have the two different ones and why they conflict etc11:05
smbpitti, bug 94185411:05
sorenUh oh..11:05
ubottuLaunchpad bug 941854 in apport (Ubuntu) "Apport retraces marks bug report a duplicate of an expired bug" [Undecided,New] https://launchpad.net/bugs/94185411:05
pittismb: thanks11:05
sorenhttp://archive.ubuntu.com/ubuntu/dists/oneiric/Release has checksums for Packages and Sources files (uncompressed ones), but they're missing for at least Oneiric.11:06
sorenIt makes my sbuild really unhappy and my tiny brain really confused.11:06
micahgmvo: that would be wrong though as libjpeg-turbo8-dev doesn't provide libjpeg62-dev11:06
pittimvo: oh, indeed -- libjpeg-turbo8-dev provides our libjpeg-dev, so I wonder why it's not just installing that one11:06
sorenCould they have gone missing or were they never there?11:06
mvomicahg: hm, good point - so "    Installing libjpeg-turbo8-dev as Depends of libopencv-highgui-dev" - does that really need this paritcular jpeg lib or could it just pick libjpeg-dev instead?11:08
micahgmvo: it's asking for libjpeg-dev11:08
micahgwhich is provided by libjpeg-turbo8-dev11:09
pittiso we should fix all remaining reverse dependencies of libjpeg62-dev?11:10
pittiwe even have three packages in main which b-dep on libjpeg62-dev,11:11
mvomicahg: aha, that explains it and libjpeg62-dev does not provide libjpeg-dev so it picks the other one.11:11
pittisuch as compiz-plugins-main11:11
pittididrocks: ^ is that an oversight, or does it really fail with libjpeg8?11:11
mvoso the new libjpeg-dev is libjpeg-turbo8-dev is that the summary?11:12
micahgfor precise, yes11:12
didrockspitti: i think this dep comes from 0.8 area11:13
micahgpitti: it's just the dev packages that aren't co-installable, the binaries are fine, maybe we just need to make the upgrader smarter about this11:13
mvoso that is the root of the problem then: "  Considering libjpeg62-dev:amd64 0 as a solution to libjpeg-turbo8-dev:amd64 -111:14
mvo  Holding Back libjpeg-turbo8-dev:amd64 rather than change libjpeg62-dev:amd64" this transition is not working and that causes the other havoc11:14
didrocksso can probably be tried with a newer one, care to open a bug and assign me so that I test? (we will have soon a new compiz upload)11:14
sorenmvo: Any idea why  "apt-get update" would attempt to fetch uncompressed Packages and Sources files?11:14
pittimicahg: hm, the only package which explicitly depends: (not build-deps) on libjpeg62-dev is libspandsp-dev11:14
pittiand that doesn't even appear on https://launchpadlibrarian.net/94128035/apt.log11:14
mvosoren: it might to that as a fallback if it can not find any compressed ones or any compressor (but the later is really odd)11:15
pittimicahg: nevertheless, if people have it installed, then it breaks upgrades11:15
sorenmvo: In the former case, I should see it trying to fetch the compressed ones and failing somehow?11:15
micahgpitti: right, so maybe we should just make the upgrader smarter and remove it or replace it (perhaps even with a warning)11:16
mvoone thing we could do is to play with the priority, e.g. libjpeg62-dev becoming extra will be one less point for it11:16
pittibut there's > 20 universe packages with Depends: libjpeg-dev, and as this isn't actually wrong, moving them all to libjpeg8-dev sounds just wrong to me11:16
mvosoren: yeah, you should see in the apache logs that it tries to hit the compressed ones first11:16
micahgpitti: right, we want the build-depends to be libjpeg-dev to make transitions easier (like Debian)11:17
pittimicahg: no, binary depends I mean11:17
pittimicahg: i. e. foo-dev depends: libjpeg-dev11:17
pittiwhich still looks right to me11:17
micahgyeah, that's right too :)11:17
mvoyeah, we should not change them if possible, it looks like the score code in apt is not taking the fact into account that the provides changes between the two packages11:17
pittiBroken libmng-dev:amd64 Depends on libjpeg-dev [ amd64 ] < none > ( none )11:17
pitti  Considering libjpeg62-dev:amd64 235 as a solution to libmng-dev:amd64 411:18
pitti  Removing libmng-dev:amd64 rather than change libjpeg-dev:amd6411:18
pittimvo: ^ with a score like that (235), one more or less hardly seems to make a difference?11:18
pittioh, hang on11:18
pitti Considering libjpeg62-dev:amd64 0 as a solution to libjpeg-turbo8-dev:amd64 -111:18
mvopitti: yeah, that was the line I was looking at11:19
pittithere the difference is -1, but would "extra" help here?11:19
sorenmvo: Awesome, thanks.11:19
mvoyeah, that might help then but apt will still prefer installed packages over new ones, so it may not be good enough11:19
sorenmvo: Turns out I had a screwed up approx cache.11:19
mvosoren: ok11:20
pittiit seems feasible to drop all remaining explicit libjpeg62-dev dependencies; would that help, if we remove it from the archive? or doesn't the upgrader look at thaht anyway?11:21
tkamppeterpitti, hi11:21
pittihello tkamppeter11:21
tkamppeterpitti, it is about bug 938669.11:22
ubottuLaunchpad bug 938669 in upstart (Ubuntu) "Can not increase MaxClients in cups (Max clients reached, holding new connections...)" [Undecided,New] https://launchpad.net/bugs/93866911:22
pittimvo: would it help if libjpeg-turbo built a real libjpeg-dev package?11:23
pittithese purely virtual dependencies are prone to failure anyway11:23
tkamppeterpitti, should we do as the user suggested, adding the line "limit nofile 4096 4096" to /etc/init/cups.conf or should there be fixed something on upstart, for example supporting /etc/security/limits.conf?11:23
mvopitti: yeah, I think that should work11:24
pittitkamppeter: this doesn't sound like an upstart bug11:24
pittitkamppeter: the default limit is set by pam11:24
apwjodh, i have a report of a machine which is hanging during boot, after upstart has started, now --debug is puking too much so i loose output.  any suggestions on how to debug ?11:25
pittidoko: are you ok with me adding a real libjpeg-dev package to libjpeg-turbo, to unbreak upgrades?11:25
dokopitti: maybe in the libjepg-empty source?11:27
pittidoko: libjpeg-empty doesn't seem to exist?11:27
pittiah, got it11:27
pittidoko: yep, fine for me11:28
pittidoko: it would then get a much higher version number then, though11:29
pittidoko: but I guess that's ok?11:29
jodhapw: What's the last message it displays? You could try '--verbose' for less spew. What version of11:29
jodhUpstart is it? Is the hang repeatable? Any new jobs installed recently?11:29
jodh 11:29
apwi believe this is latest precise, but not confirmed as they are resisting filing a bug as usual11:29
apwyes its repeatable, hard to tell what might have started recent as the console is a mess of mixed messages11:29
tkamppeterpitti, does this mean that the bug needs to get assigned to PAM?11:29
pittitkamppeter: I'm still not sure it is a bug11:30
pittitkamppeter: the default limits are quite sensible11:30
pittitkamppeter: if you have a special case where thousands of connections are made, then the admin can set this locally11:30
jodhapw: can you get a dump/screenshot of the console though?11:30
apwjodh, what was the nolog option, --no-log or --nolog ?11:30
jodhapw: '--no-log'11:30
pittidoko: I see, I agree that -empty makes more sense11:30
micahgpitti: it needs to go in libjpeg8-empty or it won't be a viable upgrade from version 6ubuntu* or libjpeg62 (which I assume is the same conclusion you just came to)11:31
pittimicahg: it doesn't matter for that as the package has always been virtual, and thus lower than any real package11:32
pittimicahg: but conceptually -turbo is just an implementation detail11:32
pittiI think -empty shoudl build a libjpeg-dev that (currently) depends on libjpeg8-dev11:32
pittimvo: thanks muchly for your help! I uploaded a fix now11:34
mvopitti: awsome, thank you11:35
mvopitti: I get some lunch now11:35
apwjodh, ok here is the log they have with --verbose: http://sprunge.us/BiSi11:35
apwjodh, see anyting indicative ?11:35
apwjodh, am i right in thinking that procps is stuck in 'post-start'11:38
jodhapw: actually, probably not - procps doesn't have a post-start by11:41
jodhdefault (although check to see if someone added this to the system in11:41
jodhquestion). I'm wondering if sysctl is hanging here. Try "echo11:41
jodhmanual|sudo tee /etc/init/procps.override" and reboot.11:41
* doko is staring at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661424 ... 11:45
ubottuDebian bug 661424 in icedtea-netx "icedtea-netx: warning on upgrade - binary operator expected" [Normal,Open]11:45
=== _salem is now known as salem_
ansgardoko: Maybe the `...` returns something including whitespace?11:51
ansgardoko: [ -z foo bar ] -> bash: [: foo: binary operator expected11:52
pittidholbach: hm, you didn't sync quvi and libquvi-scripts and cclive, right? or did I look into the wrong queue?11:52
micahgdoko: does the shell11:52
micahgdoko: does the shell's return output need to be quoted11:52
dholbachpitti, I'm happy to do it - I thought I'd wait for libquvi to get in first, no? :)11:53
pittidholbach: sounds fine, as long as it doesn't need the others for building11:54
dholbachpitti, libquvi-scripts is the most recent - cclive I can sync as it will likely DEPWAIT11:55
pittidholbach: ah, then it sounds you could as well sync it now11:55
dholbachpitti, cclive and quvi synced now too - thanks for looking it up and letting me know11:59
* pitti hugs dholbach, danke11:59
* dholbach hugs pitti back11:59
fraviofiihello, Is it possible to have an ubuntu-core for arm-v4? Can I prepare it myself?12:02
tkamppeterpitti, can you comment on bug 938669?12:12
ubottuLaunchpad bug 938669 in upstart (Ubuntu) "Can not increase MaxClients in cups (Max clients reached, holding new connections...)" [Undecided,New] https://launchpad.net/bugs/93866912:12
pittitkamppeter: will do after lunch12:13
=== zimmerle` is now known as zimmerle
=== MacSlow is now known as MacSlow|lunch
mpt"One or more running instances of xscreensaver or xlockmore have been detected on this system. Because of incompatible library changes, the upgrade of the GNU libc library will leave you unable to authenticate to these programs. You should arrange for these programs to be restarted or stopped before continuing this upgrade, to avoid locking your users out of their current sessions."12:44
mptHow do I restart/stop xscreensaver without being logged out and therefore cancelling the upgrade? :-)12:45
tjaaltonmpt: killing the screensaver shouldn't log you out12:51
dholbach@pilot out12:53
=== udevbot changed the topic of #ubuntu-devel to: Precise Beta-1 Freeze in effect. Archive: open | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/xmGdCW | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
tjaaltonuh, ppa build queue 6h?13:03
pittisome of the PPA builders were taken offline to do other things apparently13:25
jelmerhi tjaalton13:35
tjaaltonjelmer: hi13:36
zulmterry: ping13:54
mterryzul, hi13:55
zulmterry:  i have a couple of MIR that i just filed that is blocking nova from buidling s bug #941920, bug #941916, and bug #941913 can we get them taken care of today? they are pretty easy they are just python modules and they should all be ready13:56
ubottuLaunchpad bug 941920 in python-iso8601 (Ubuntu) "[MIR] python-iso8601" [Undecided,New] https://launchpad.net/bugs/94192013:56
ubottuLaunchpad bug 941916 in python-tz (Ubuntu) "[MIR] python-tz" [Undecided,New] https://launchpad.net/bugs/94191613:56
ubottuLaunchpad bug 941913 in python-babel (Ubuntu) "[MIR] python-babel" [Undecided,New] https://launchpad.net/bugs/94191313:56
mterryzul, will look13:58
zulmterry: thanks!13:58
mpttjaalton, you were right, thanks :-)14:05
tjaaltonmpt: np :)14:06
=== MacSlow|lunch is now known as MacSlow
=== bladernr_afk is now known as bladernr_
=== dendrobates is now known as dendro-afk
Davieymterry: for info, these are beta release critical issues. :/  Thanks14:22
geserpitti: is there a (good) reason to keep postgresql-9.0 (universe) in the archive while we have postgresql-9.1 in the archive too?14:23
pittigeser: uh, no; I thought I already removed it ages ago14:23
pittigeser: thanks for pointing out, I'll remove14:23
pittithere are 4 rdepends left in Debian14:24
pittiI'll sync them when/if they update to 9.114:24
mterryDaviey, k, am in the middle of doing them.14:24
=== dendro-afk is now known as dendrobates
mterryzul, FYI, I generally find it easier to have one bug for a chain of dependencies like this (python-babel and below) and adding tasks for the separate packages.  No big deal to have them separate, but you may find it easier too, for keeping track14:25
zulmterry: ill do that in the future14:26
=== yofel_ is now known as yofel
=== zyga is now known as zyga-food
pittiev: you saw the whoopsie FTBFS?14:41
pittigeser: thanks, removed14:44
Sweetsharkpitti: any good idea about Bug #938582 ?14:48
ubottuLaunchpad bug 938582 in libexttextcat (Ubuntu) "[MIR] libexttextcat" [Undecided,Fix released] https://launchpad.net/bugs/93858214:48
Sweetsharkchrisccoulson: ping?14:49
pittiSweetshark: sorry, I don't understand -- which package depends on which?14:49
pittiSweetshark: libexttextcat0's dependencies look fine to me14:50
Sweetsharkpitti: libexttextcat0-dev*ubuntu1 depended on libtextcat0-dev*ubuntu1 (although that one isnt ubuntufied) IIRC from my pbuilder failures.14:52
mterryzul, question for you in bug 94191614:52
ubottuLaunchpad bug 941916 in python-tz (Ubuntu) "[MIR] python-tz" [Undecided,Incomplete] https://launchpad.net/bugs/94191614:52
* Sweetshark rechecks14:52
zulmterry: yep14:52
Sweetsharkpitti: libexttextcat-dev : Depends: libexttextcat0 (= 3.2.0-1ubuntu1) but it is not going to be installed <- from my pbuilder log.14:52
pittiSweetshark: hm, no idea why that would be; the versions are identical14:53
pittilibexttextcat0 | 3.2.0-1ubuntu1 |       precise | amd64, armel, armhf, i386, powerpc14:53
pittilibexttextcat-dev | 3.2.0-1ubuntu1 |       precise | amd64, armel, armhf, i386, powerpc14:53
Sweetsharkpitti: does libexttextcat0  3.2.0-1ubuntu1 depend on libtextcat0  3.2.0-1ubuntu1 by chance?14:55
pittiDepends: libc6 (>= 2.14), libexttextcat-data (= 3.2.0-1ubuntu1)14:55
pittiSweetshark: no, should it?14:55
pittiand libexttextcat-data is built by the libexttextcat source, so all seems fine14:55
Sweetsharkpitti: hmmm, so what is wrong my pbuilder?14:56
* Sweetshark goes hunting there.14:56
zulmterry: i think it might be feasable to look at it after ff14:56
mterryzul, you mean after Beta1?  We're after FF14:57
zulmterry: sorry beta114:57
mterryzul, this (and the tests, see my new comment) are normally MIR blockers.  What's the story with the urgency here?15:01
zulmterry:  pretty urgent15:01
zulits a blocker right now15:01
mterryzul, for the nova stack?15:01
zulmterry: correct15:02
mterryzul, well, as a MIR reviewer, it's not approved until those get fixed.  But I'll subscribe ubuntu-release (who has to sign off anyway post-FF) if they want to promote it anyway/temporarily for the beta15:04
zulthis is babel right?15:05
Davieymterry: sorry, what is the blocker?15:05
mterryzul, -tz15:05
mterryDaviey, bug 94191615:06
ubottuLaunchpad bug 941916 in python-tz (Ubuntu) "[MIR] python-tz" [Undecided,Incomplete] https://launchpad.net/bugs/94191615:06
mterryDaviey, tests and a hardcoded timezone list15:06
zulDaviey: er..http://paste.ubuntu.com/859292/15:07
mterryzul, the tests can be run manually, but not sure how they are intended to be run, because yeah, setup.py doesn't call 'em15:08
Davieymterry: ah, i wrote a patch to enable the test suite at runtime.15:10
Davieyerr build time15:10
Davieyoh, that was for python-iso8601.15:12
Davieymterry: Can i suggest that, if nothing inherently scares you, that they get promoted, with open bug tasks to resolve the niggles?15:12
mterryDaviey, ah yeah, I was going to file a bug for that one with Debian.  It's test suite seemed awkward to run, so wasn't going to block on it.  But that patch would be super welcome too!  :)15:12
dholbachhey mterry - did seb128 ping you about the lightdm sponsoring item? :)15:13
mterrydholbach, no?15:13
dholbachhang out, let me dig it out15:13
dholbachah no, sorry - unity-greeter15:14
dholbachbug 88436615:14
ubottuLaunchpad bug 884366 in unity-greeter (Ubuntu) "Theme is not customizable by downstream (derivative) distros" [Undecided,Confirmed] https://launchpad.net/bugs/88436615:14
zulmterry: k tz is running the tests now15:17
mterryDaviey, it's just a matter of process.  Issues of release schedule timing aside, these would be blockers.  ubuntu-release will probably take your stance too (pitti?), in which case I'm on board15:18
pittiwe could also revert to the previous nova15:18
pittias it was uploaded a bit hastily anyway15:18
* pitti needs to run out for a bit, bbl15:18
zulprevious version of nova had a big nasty memory bug i rather not revert it either15:20
mterrydholbach, ah, we made it easier for derivatives by moving to gsettings instead of an /etc/ config file.  So they can just ship gsettings overrides15:25
mterrydholbach, I'll comment in bug and close out15:25
dholbachmterry, excellent15:25
dholbachthanks a lot15:25
dholbachseb128, ^15:25
sorenzul: Memory bug?15:25
zulsoren: scheduler bug15:25
zulsoren: that just sucks alot of memory from nova-compute15:26
sorenzul: Do you have a bug ref?15:26
zulsoren: yeah gimme a sec15:26
seb128dholbach, mterry: thanks15:26
=== zyga-food is now known as zyga
ogzyi am trying to pack libaudiere-1.9.4 for oneiric, i tried to use te source files from hardy and downloaded the dsc, diff.gz and tar.gz files and run sudo pbuilder build *.dsc here is what i got as error: Dependency is not satisfiable: libdumb1-dev but i have this package installed, any idea?15:45
ogra_inside your pbiulder chroot ?15:45
ogzyogra_: yes15:46
ogra_might it be that there is a versioned dep on the package ?15:46
ogzyi checked the control file after i dpkg-source -x *.dsc, it only says the package name, no version15:47
mterryzul, I'm looking at python-babel now and it includes a bunch of binary info about locales.   So what does nova even use python-babel for?  Is it anything it could just use python-pyicu for instead, since it's already in main and has a boat-load of included locale info?15:48
zulmterry: i nor probably wasnt aware of it...its something that i will definently have to look at15:49
goganchiccan anybody tell me where can I find code of hiding/showing global menu? I want to show it always. There are no settings for this function in unity interface and no code in indicator-appmenu package15:49
mterryzul, I can't even find where nova is importing babel15:50
zulmterry: are you looking at the package in the archive?15:50
mterryzul, yeah15:51
zulmterry: yeah youll have to look at the upstream source15:51
mterryzul, ok.  we are depending on python-babel in anticipation then?15:52
zulmterry: yes15:52
zulmterry: its a dependency of the nova waiting to build in the buildds15:53
chrisccoulsonhi Sweetshark15:54
goganchicis indicator-appmenu the package which display menu in the top panel in unity?15:54
mterryzul, all I see in nova trunk is a babel.cfg16:02
zulmterry: https://github.com/openstack/nova/commit/4a4c274c834728a03bce7e5384c562321821eaf816:02
mterryzul, ah...  babel is a build tool as well as a library16:04
mterryzul, missed that bit16:04
mterrySo not so easy to replace with pyicu16:06
mterrygoganchic, yes16:19
goganchicmerry, and what about code for hiding/showing global menu? Is this code in indicator-appmenu package too? Or this code belongs to main unity package (libunity or smith like this)&16:20
goganchicmterry, and what about code for hiding/showing global menu? Is this code in indicator-appmenu package too? Or this code belongs to main unity package (libunity or smith like this)?16:22
stgrabermvo: any thought on bug 937196?16:22
ubottuLaunchpad bug 937196 in ifupdown (Ubuntu) "10.04 LTS -> 12.04 upgrade failed: ifupdown depends on upstart and initscripts but they are not configured" [High,Confirmed] https://launchpad.net/bugs/93719616:22
mterrygoganchic, well, that gets a bit complicated.  unity hosts the appmenu indicator, sure.  But appmenu-gtk which is a gtk+ module that all client apps load is responsible for sometimes showing it (like when user holds down ALT I believe)16:23
mterrygoganchic, what's your goal?16:24
mterrygoganchic, this might be better fodder for #ubuntu-unity?16:24
goganchicmerry, my goal is to show global menu by default, always, not only when mouse pointer is over it. I'll try #ubuntu-unity channel, thanks16:25
goganchicmterry, my goal is to show global menu by default, always, not only when mouse pointer is over it. I'll try #ubuntu-unity channel, thanks16:25
pittijibel: would it take much effort to re-run precise-upgrade-lucid-universe, now that we have the libjpeg-dev fix?16:32
pittijibel: ah, nevermind16:33
pittijibel: we need calligra fixed first16:33
mptev, hi, can we kill the bubbles that say "An application has crashed on your system (now or in the past). Click on the notification icon to display details."?16:45
jmlmy precise install is being ground to a halt, I think by dconf-settings16:53
=== deryck is now known as deryck[lunch]
jmlcan I just kill it, please?16:55
seb128jml, don't blame the messenger16:58
infinitypitti: Oh, checking scrollback, our P-a-s is forked from Debian's and we can change it, but wvstreams (and thus wvdial) just plain didn't work on ARM last time anyone checked.16:59
seb128jml, it probably means something loop write to gsettings16:59
infinitypitti: Not from a building POV, but from a runtime one.16:59
seb128jml, strace it maybe to figure what key is being written?16:59
infinitypitti: If that's no longer true, I'm happy to build them again.16:59
pittiinfinity: right; I saw that you already PaSed wvdial, but http://qa.ubuntuwire.org/ftbfs/ doesn't take that into account16:59
pittiinfinity: thanks16:59
infinitypitti: (If you're just trying to get wvdial out of the yellow block on the qa report, that's an LP bug, and would be resolved by uploading the source again). :P16:59
pittiinfinity: *nod*17:01
jmlseb128: what am I looking for in the strace output?17:01
infinitypitti: Alternately, fix qa/ftbfs to parse P-a-s, so it can ignore builds that LP shouldn't have. ;)17:02
infinitypitti: (Which seems saner than re-uploading source just to remove a build record)17:02
jmlwrite(12, "GVariant\0\0\0\0\0\0\0\0\30\0\0\0\20\31\0\0\0\0\0(\344\0\0\0"..., 12288) = 1228817:05
jmlwrite(12, "elay\0\0\0\0\350\3\0\0\0imaximized\0\1\0bcache"..., 348) = 34817:05
jmlto .config/dconf/user.DF597V, which then gets renamed to .config/dconf/user17:05
seb128jml, maybe try to gsettings list-recursively > log and diff the logs17:05
seb128i.e 2 calls to those17:05
bluefoxicyI asked Ubuntu to upgrade yesterday17:05
bluefoxicyit hasn't.17:05
bluefoxicyIt got one package in, then asked me about which services to restart for a glibc upgrade and waited.17:06
bluefoxicymight I suggest making apt a bit more intelligent, such that it can look at packages which will pause apt and defer them until later in the process (i.e. when things can't be installed without the offending package first)17:07
bluefoxicyand also, marking such packages where you can install and defer any such questions until later so that it simply doesn't ask until later in the process17:07
jml-org.gnome.settings-daemon.peripherals.keyboard numlock-state 'on'17:08
jml+org.gnome.settings-daemon.peripherals.keyboard numlock-state 'off'17:08
* bluefoxicy hates babysitting things. Would rather come back to a stalled process when it's almost done than when it's just started.17:08
seb128jml, it seems g-s-d is spammed gsettings with numlock status changes17:09
jmlI've seen some people mention issues with apple keyboard & numlock...17:09
seb128jml, do you have any service or anything dealin with numlock status for you?17:09
jmlbut I haven't paid attention to details17:09
seb128jml, when did that start?17:09
jmlseb128: I don't think so.17:09
jmlseb128: within the last hour17:10
seb128jml, you can probably "gsettings set org.gnome.settings-daemon.peripherals.keyboard remember-numlock-state false"17:10
seb128or kill gnome-settings-daemon17:10
seb128it seems stuff fight over your numlock status17:10
jmlseb128: setting remember-numlock-state off seemed to stop the spinning.17:12
jmlseb128: thanks.17:12
seb128jml, yw, still weird that stuff keep changing the status of numlock and a bug somewhere17:12
seb128could be xorg or virtualbox or something17:12
seb128jml, the gsettings stuff was only a side effect, g-s-d only stores the status17:13
seb128it seems something keeps changing the status though17:13
seb128jml, oh, and no, I've no idea how to debug what is the something ;-)17:13
jmlseb128: heh17:15
jmlseb128: well, tbh, I'd rather get on with other things than spend time debugging OS issues :)17:15
jdstrand@pilot in17:15
=== udevbot changed the topic of #ubuntu-devel to: Precise Beta-1 Freeze in effect. Archive: open | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/xmGdCW | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: jdstrand
seb128jdstrand, hey, please ignore merge request about unity_quicklists, those have issue and are being sorted17:18
jdstrandseb128: ok17:19
hrwtkamppeter: thx for activity in bug 93288217:21
ubottuLaunchpad bug 932882 in gutenprint (Ubuntu) "The PPD version (5.2.7) is not compatible with Gutenprint 5.2.8-pre1." [Undecided,Opinion] https://launchpad.net/bugs/93288217:21
hrwhave a nice rest of day17:24
brodercan somebody on ~ubuntu-branches set https://code.launchpad.net/~pali/ubuntu/natty/plymouth/plymouth/+merge/61897 back to work in progress?17:40
=== deryck[lunch] is now known as deryck
broderhmm, is it deliberate or accidental that packages that were removed still have udd branches?18:09
slangasekbroder: I think it's deliberate18:14
slangasekwe don't want to lose the history; so the question is how do you want to represent a package removal18:14
broderbackports just got a bug from a user checking out a package that was removed several releases ago18:14
broderwhich is clearly confused on several levels18:14
broderbut possibly indicates some real potential problems, especially with things like developer.ubuntu.com now pointing at udd18:15
* slangasek suggests filing a bug on udd18:16
* broder nods18:16
broderslangasek: what do you want to do about insserv, by the way? based on my experience with afs, i'm suspicious that stopping networking before umountnfs.sh will cause nfs to hang on shutdown, but i haven't used nfs so i don't know18:23
infinitybroder: Why would you stop networking before umounting network filesystems?18:24
infinity(I mean, why should that be discussed instead of just fixed?)18:25
ogra_more excitement !18:25
micahgmaybe the lp:ubuntu/foo branch "symlink" can be removed for packages that have been removed from the dev release?18:26
mterryzul, do we even need python-babel if all it does is manage gettext files?  Won't those be managed by the langpacks?18:27
=== kentb-out is now known as kentb
zulmterry: im not sure its something we need to look at18:27
brodermicahg: yeah, maybe. i don't feel like i understand the relevant issues well enough to do much more than raise it with the udd team and let them figure it out18:28
broderbut i went ahead and filed bug #94213818:28
ubottuLaunchpad bug 942138 in Ubuntu Distributed Development "Removed packages still have udd branches" [Undecided,New] https://launchpad.net/bugs/94213818:29
* micahg comments on the bug18:29
mterryzul, ok, well added comment to python-babel bug with review there, including that question18:29
bdmurrayzyga: have you put the command-not-found change for bug 938992 on to Launchpad yet?18:34
ubottuLaunchpad bug 938992 in command-not-found (Ubuntu) "crash_guard routine should be changed" [Medium,Confirmed] https://launchpad.net/bugs/93899218:34
=== jjohansen is now known as creckets
=== creckets is now known as crickets
=== crickets is now known as jjohansen
infinityTheMuso: *pokity poke*19:00
infinityTheMuso: When you're around, can you add me (adconrad) to ~ubuntustudio-dev?  Kthx.19:01
smoserslangasek, ping19:05
zygabdmurray: nope19:05
slangaseksmoser: hey there19:05
zygabdmurray: let me find that branch19:05
smoseri'm looking at bug 93735219:06
slangasekSpamapS: say, do you have any packages using wait-for-state in the wild?19:06
ubottuLaunchpad bug 937352 in cloud-initramfs-tools (Ubuntu) "root partition in may not be grown" [Undecided,Fix released] https://launchpad.net/bugs/93735219:06
smoserand wondering if you have some insite19:06
slangaseksmoser: that one's marked fix released, is that the one you mean?19:06
smoserslangasek, yeah, it wasn't fixed. i need to change that.19:07
bluefoxicyBy convention in init scripts, if you have multiple things to turn on19:07
bluefoxicyis it preferred to have settings like "NETWORK0={0,1}", "NETWORK0={on,off}", or "NETWORK0={enabled,disabled}"?19:07
smoserslangasek, so basically what happens:19:07
smoser 1.) normal initramfs mount of /19:07
bluefoxicyor, you know.  y/n19:07
smoser 2.) growpart initramfs plugin (in local-bottom) umounts /19:08
smoser 3.) calls growpart , which runs 'sfdisk' which calls BLKRPART19:08
smoser 4.) sometimes, blkrrpart gets device or resource busy19:09
smoserslangasek, at http://paste.ubuntu.com/859573/, i've modified the initramfs to collect 'ps -w' output before and after the sfdisk command19:10
slangasekbluefoxicy: I wouldn't consider any of these things to be best practice, really19:10
smoseri'mi wondering what could be causing the busy.  smb was fairly certain the only thing he could think of was udev events, so we added a 'udevadm settle' before running growpart (to  make sure any initial events from the normal boot had finished)19:11
slangaseksmoser: what's this 'blkid' call in the ps output?19:11
slangaseksmoser: remember that "udevadm settle" doesn't mean "no more events will happen", it means "the event queue is currently empty".19:12
slangasek(empty, and all events that were in it have been processed)19:12
smoserslangasek, yeah, that is probably the thing that is the issue.19:13
smoseri'm assuming it jsut came from udev seeing the vda1 event.19:14
SpamapSslangasek: I don't believe there are any using it yet no19:14
SpamapSslangasek: I've been meaning to write up how to use it at some point. :p19:14
smoserright, obviously it doesn't mean "no more events will happen". but i had assumed that in that point in the boot, where / had already been mounted (on /dev/vda1), that such events would have already occurred.19:15
SpamapSslangasek: I've recommended its use on askubuntu.com a few times19:15
smoserbut one way or another , I need to block until or somehow assert that nothing will have /dev/vda open in the initramfs.19:15
slangaseksmoser: can I see the udev log from this system?  I want to see what attributes are on /dev/vda119:15
smoserslangasek, can i get that from the booted system ?19:16
slangaseksmoser: /var/log/udev.log19:16
smoseri can give you access to the system just as easily19:16
slangasek(thanks to coldplugging)19:16
slangasekeither way then :)19:16
slangasekSpamapS: do you have a pointer handy to one of those recommendations?  I'm specifically interested at the moment in the context of bug #56975719:16
ubottuLaunchpad bug 569757 in nis (Ubuntu) "NIS upstart dependency broken for lucid" [High,Triaged] https://launchpad.net/bugs/56975719:16
slangasekSpamapS: dunno if you're following the debian-devel upstart thread?19:17
smoserudev log is at http://paste.ubuntu.com/859585/19:17
smoserand, slangasek you can get to ubuntu@ via chinstrap19:17
slangaseksmoser: ok; so it's line 75 of /lib/udev/rules.d/60-persistent-storage.rules19:18
slangasekwhich seems legitimate here19:18
slangaseksmoser: I think the problem is your initramfs script is not event driven, and hasn't waited for the kernel to say the disk is ready19:18
slangaseksorry, for udev to say19:18
SpamapSslangasek: no, I am woefully behind on debian-devel.. ;)19:19
smoserslangasek, i dont know.19:19
smoserit runs at local-bttom19:19
smoserafter rootfs has been mounted once already19:19
smoserand mounted via LABEL also19:20
slangaseksmoser: hmm!19:20
smoserso i would have thought that that would have already occurred19:20
slangasekexcept the main mounting script is also not event driven AFAIK :)19:20
smoserslangasek, well it uses wait-for-root19:20
smoserwhich is linked to udev i think19:20
smoser(verified it is linked to udev)19:21
SpamapSslangasek: probably the best example of how it can be used is bug #643289 .. recommended it in comment 1419:22
ubottuLaunchpad bug 643289 in nfs-utils (Ubuntu Lucid) "idmapd does not starts to work after system reboot" [High,Triaged] https://launchpad.net/bugs/64328919:22
slangasekSpamapS: so the nis case is interesting, because what we need to implement here is the equivalent of an LSB "Should-Start" rule19:22
slangasekSpamapS: wait-for-state doesn't DT"R"T for non-existent jobs19:22
=== fisted_ is now known as fisted
slangasekso I can't just call start wait-for-state WAITER=autofs WAIT_FOR=ypbind in the autofs pre-start19:23
infinitysmoser: Wait, why are you growing root in local-bottom?19:23
slangasekinfinity: clouuuud19:23
infinitysmoser: That would be where your code differs from jasper, we do it in local-premount.19:23
slangasekSpamapS: I *can* create a job in the nis package called start-ypbind that's 'start on starting autofs' and calls 'start wait-for-state', but that's kinda the wrong place for it to live19:24
infinitysmoser: Doing it post-mount just seems to be asking for this sort of trouble.19:24
slangasekinfinity: why?  I'm not seeing why unmounting the partition should generate new udev events19:24
infinityslangasek: No, but why mount/umount/resize/remount?19:25
smoserinfinity, i chose post-mount because i could guarantee that at that point the device was available19:25
smoserothe rthan that , i'd have to do the wait-for-root before the real wait-for-root19:25
smoserbut... same problem would occur i think.19:25
slangaseksmoser: 'premount' is called from /usr/share/initramfs-tools/scripts/local right before it's about to mount the device.19:25
slangaseksmoser: so you don't need to wait-for-root because the script's already done it for you19:26
smoserslangasek, right. i dont at *that* point19:26
smoserbut i do have to afterwards19:26
smoseras the sfdisk generates events that might delete it temporarily19:26
smoserslangasek, well, i forget why i did premount19:27
infinityDo you go straight from resizing into mounting and starting?19:27
smoserer... why i did not do premount19:27
smoserbut really, why would that be any different19:27
infinityWe do premount-resize, then trigger a reboot in bottom.19:27
smosermount and umount should not create events to udev, and the one that runs earlier just seems *more* prone to errors.19:27
smoserinfinity, i dont want to reboot19:27
infinityFair enough.19:27
infinityBut there's a solution for that too.19:28
slangaseksmoser: I don't see any reason for errors in either case, but if you do it in premount, you're doing it at precisely the point that initramfs-tools says the device is ready for use19:28
infinityYour resize script (if it were in premount) could re-scan for partitions/devices before exiting.19:28
slangasekinfinity: does that, that's why we're getting the error ;)19:28
smoserslangasek, i can try the local-premount (or look into why i didn't use that originally)19:29
smoserbut i don tthink its going to change much really.19:29
SpamapSslangasek: roger. I think we can make it react more appropriately for a job that does not exist.19:29
SpamapSslangasek: have to work on some other stuff for a while today.. will return to this later19:30
slangaseksmoser: well, it reduces complexity a little bit, you don't have to umount / remount... you just have to resize, reread, probably call wait-for-root again for the benefit of the local script, and exit19:30
slangaseksmoser: this may fix the bug in which case it's an easy win, and if it doesn't it gives us less to search through19:30
slangasekSpamapS: ok - mostly wanted to check that you agree it should be done by adjusting wait-for-state19:31
slangasekSpamapS: if so, I'll go ahead with uploading nis19:31
infinityslangasek: The error may be coming from the partition scan, but that's only because the device was previously busy anyway (it threw an error on resize too).19:32
infinityslangasek / smoser: My gut feeling is that growing and rescanning in premount will Just Work (and I don't see why you'd need to retrigger wait-for-root after the rescan, we already know the device is there).19:33
=== Ursinha_ is now known as Guest34384
slangasekinfinity: we know the device was there before fiddling with the partitions again; I don't know if we get new events for the partitions when resized19:33
slangasekinfinity: and the resize failed only in that it failed to reread the partition table afterwards19:34
slangasekthe actual resizing succeeded (as it should)19:34
smoserslangasek, i'm reading init from the initramfs19:34
smoserand it seems to me that local-premount is before wait-for-root19:35
slangaseksmoser: no, local-premount isn't called from init at all.  *local*-premount, not *init*-premount19:35
slangaseksmoser: the difference is critical here :)19:35
slangaseklocal-foo are "the set of scripts run when the root filesystem is a local filesystem"19:36
slangasekand are all run from scripts/local19:36
infinitylocal does, basically, wait-for-root && premount && mount19:37
smoseryeah, i see that.19:37
slangasekwell, it does top && wait-for-root && premount && mount19:37
slangasek&& bottom :P19:37
infinityStill, if premount successfully re-rereads the table, I don't see need for a second wait-for-root.19:38
* infinity shrugs.19:38
slangasekbecause the ioctl for the table reread is not going to wait for udev before returning19:38
slangasek(because it a) can't, b) shouldn't)19:38
infinityOh, there's that.19:38
infinityFair enough.19:38
slangasekso if udev goes mucking about in /dev afterwards, it's racy19:38
infinityNot onerous to add a wait-for-root to the premount mucking script anyway.19:39
slangasekyes; there's already one in there as it is19:39
slangasekjust the umount/mount need to be dropped19:39
bdmurrayScottK: Do you think bug 940789 is a duplicate of bug 927855?19:40
ubottuLaunchpad bug 940789 in update-manager (Ubuntu) ""Obsolete packages will be removed" dialogue is too tall for netbook screen with KDE front end" [Undecided,New] https://launchpad.net/bugs/94078919:40
ubottuLaunchpad bug 927855 in update-manager (Ubuntu) "window size too large to see buttons after expanding details" [Undecided,Confirmed] https://launchpad.net/bugs/92785519:40
smoseri really think this is a goose chase19:43
smoserbut i will oblige and try in local-premount, making necessary changes.19:43
infinitysmoser: I'm not sure it's a goose chase at all.  Not mounting the FS certainly leads to one less possible way that the device could be busy, right?19:44
slangaseksmoser: even if it doesn't fix it, infinity is right that this is the better and simpler way to do what you're doing19:44
bluefoxicyI am playing with zram19:44
infinitysmoser: (And umounting doesn't guarantee a device isn't busy)19:44
bluefoxicyis there any interest in this?19:45
infinitybluefoxicy: We use it on the ac100 images.19:45
slangasekso if it doesn't fix it, we have less of an area remaining to search for the bug in :)19:45
bluefoxicyinfinity:  I think it's appropriate roughly "everywhere" to use compressed memory because of the CPU/swap trade-off inequality.19:45
bluefoxicyin other words I think my desktop doesn't give a crap that it's squeezing 4, 8, 16 kilobytes of data into a compressed swap area, but it sure takes a beating thrashing disk19:46
infinitybluefoxicy: Except that most modern desktops really don't swap often at all.19:46
smoserslangasek, infinity ah.19:46
smoseri see at least one reason i used post-mount19:46
bluefoxicyinfinity:  servers?19:46
infinitybluefoxicy: The reason we use it on the ac100 is a combination of limited RAM and slow/fagile storage.19:47
smoseri check some files in the mount that may indicate "do not grow this"19:47
smoser(ie, to be configurable)19:47
bluefoxicyinfinity:  the real problem with all this to me is no hibernate file19:47
infinitybluefoxicy: I'd contend that any server that swaps frequently has admins that need to look at fixing it. :P19:47
bluefoxicyyour desktop has 16 gigs of RAM, you don't have to swap, good for you.  You can't hibernate :P19:47
bluefoxicyinfinity:  I'd contend that a software fix that extends performance without requiring additional money sunk into additional hardware is a fix :)19:48
slangaseksmoser: oh, ok :/19:48
smoserits also something i would like to not lose.19:48
infinitybluefoxicy: But it doesn't extend performance on a system with an appropriate amount of RAM for the workload, it degrades it.19:48
bluefoxicyOnly if it gets used.19:49
infinitysmoser: What's the use-case for that?19:49
smoserbut... if i have to in order to acutally have functional code in the default case i'd drop it.19:49
bluefoxicyThat's the thing:  if you don't extend past the end of memory, you never use any of this19:49
infinitybluefoxicy: But your zram swap is more likely to be hit if you, say, have 1/2 your RAM configured as zram swap.19:49
infinitybluefoxicy: zram doesn't come from thin air.19:49
slangaseksmoser: well, shot in the dark - how about another wait-for-root call after your umount and before your growpart?19:49
smoserinfinity, i'm not really sure, othe rthan to allow this code to be disabled without re-building the image19:49
infinitybluefoxicy: If you use part of RAM for zram, you lose it as RAM.19:49
bluefoxicyinfinity:  not true.  If you have 4GB of RAM and set 2GB as zram swap, you can use 3.5GB of physical RAM without swapping to zram.19:50
infinitysmoser: boot argument?19:50
slangaseksmoser: if you had to lose that config code, I guess you could offer configuration via kernel ^^ infinity fast19:50
smoserinitially, the idea was that we would only run this once per "instance", but then we ended up changing that because on ec2, you can 'start instance', 'stop instance', 'grow volunme', 'start instance'19:50
bluefoxicyinfinity: zram doesn't preallocate memory; it dynamically allocates it in the same way as tmpfs.  So if you're storing nothing on the device, it doesn't use any RAM.19:50
bluefoxicybluefox@icebox:~$ cat /sys/block/zram0/disksize19:51
bluefoxicy1073741824  [In bytes]19:51
bluefoxicybluefox@icebox:~$ cat /sys/block/zram0/mem_used_total19:51
ScottKbdmurray: It could be.  I'm not sure if the code that drives window size is -common or front end unique.19:52
smoseryeah, slangasek infinity kernel command line update is actually significantly more difficult in many ways that adding a file19:52
slangasekyeah, I was afraid of that19:53
infinityIt is?19:53
smoserwell, at very least it means updating grub config rather than touching a file19:53
brodersmoser: how are people supposed to create that flagfile? publishing their own ami?19:53
broderoh wait, right, you still can't customize the initrd. nvm19:54
smoserbroder, yeah, that is really the only way. you're right, thats not terribly easy.19:54
smoseryou can customize the initramfs now, broder, it is read and loaded via pv-grub19:54
smoserbut yeah, that is possibly one reason i did it that way...19:54
smoseri'll try this now and see.19:54
brodersmoser: oh, ok. so then, if people already have to publish their own ami, could they disable the expansion at initrd-build time?19:54
slangasekyou can simply omit the cloud-initramfs-tools package then?19:55
smoserbroder, yeah, its definitely doable. i'm surprised i didn't actually add anything that would allow you to do that.19:56
smoserbut yeah, just removing woudl do it.19:56
exarkunAnyone want to talk about https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/668955 https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/788965 https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/810405 https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/814933 https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/815130 https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/627654 ?19:56
ubottuLaunchpad bug 668955 in twisted (Ubuntu) "package python-twisted-core 10.1.0-2 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 2" [Undecided,New]19:56
ubottuLaunchpad bug 788965 in twisted (Ubuntu) "package python-twisted-core 10.2.0-1 failed to install/upgrade: ErrorMessage: subproces installed post-installation script gaf een foutwaarde 1 terug" [Undecided,New]19:56
ubottuLaunchpad bug 810405 in twisted (Ubuntu) "package python-twisted-core 10.2.0-1 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug" [Undecided,New]19:56
ubottuLaunchpad bug 814933 in twisted (Ubuntu) "package python-twisted-core 10.0.0-2ubuntu2 [modified: usr/share/pyshared/twisted/python/dxprofile.py] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1" [Undecided,New]19:56
ubottuLaunchpad bug 815130 in twisted (Ubuntu) "package python-twisted-core 10.2.0-1 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück" [Undecided,New]19:56
slangasekwould perhaps be nice to have it configurable, since c-i-t ships two scripts (growroot + rescuevol)19:57
smoserslangasek, well they're thir own packages.19:57
smosereach could be deleted19:57
slangasekwell there you go then19:57
slangasekseems sufficient to me19:57
seb128could some buildds admin bump the score for https://launchpad.net/~sil2100/+archive/ppa/+build/3244412 https://launchpad.net/~sil2100/+archive/ppa/+build/324441319:58
smoserbut, same as grub config, removing a package is obviosly more diffiicult than touchign a file.19:58
smoserbut i'll go down this route19:58
smoserhoping that it will allow us to undertsand what is going wrong.19:58
stgraberseb128: done19:58
slangasekexarkun: what specifically would you like to talk about?20:03
exarkunslangasek: whether I should mark them all as duplicates.  which I just did, because I'm not always very patient.20:04
slangasekexarkun: they're not duplicates at all, please undo this20:04
slangasekone of them doesn't even have the same exit code as the others, and aside from two from the same user, they each have different error messages in the log20:04
exarkunslangasek: They're all caused by failing hardware corrupting package data, and then the failure being incorrectly handled by the installation tools.20:05
slangasekexarkun: please don't consider "post-installation script returned error exit status 1" sufficient reason to dupe bugs20:05
exarkunPackages can be corrupted in a lot of different ways, I'm sure20:05
slangasekwhere do you see evidence of hardware corruption in each of these?20:05
exarkunlack of evidence to the contrary, behavior unreproducable by anyone else20:06
exarkun"Illegal Instruction" from an executable20:06
exarkunLooks pretty hardware-faily to me.  Actually I didn't link to that one, sorry: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/94126920:07
ubottuLaunchpad bug 941269 in software-center (Ubuntu) "package software-center 5.1.9 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured" [Undecided,Confirmed]20:07
slangasekexarkun: there has been no analysis at all on bug #788965 that supports this theory that it's hardware corruption.20:09
ubottuLaunchpad bug 941269 in software-center (Ubuntu) "duplicate for #788965 package software-center 5.1.9 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured" [Undecided,Confirmed] https://launchpad.net/bugs/94126920:09
exarkunslangasek: I offered my analysis.20:09
slangasekSorry: TypeError: ('compile() expected string without null bytes',)20:09
slangasekthere's no evidence that anyone even tried to reproduce the bug with the set of packages the user had installed20:10
slangasekjumping to the conclusion that it's filesystem corruption just because there are other bugs reported against this package which are caused by filesystem corruption isn't logical20:10
exarkunOkay, I'm sure you're right.  I'll go back to ignoring these bug reports.20:11
exarkun(so they can sit for years with no comment)20:11
infinitygeser: Did you decide not to resurrect vim's changelog history, or did someone else sponsor your upload before you could? :P20:27
infinitygeser: I was entirely serious about that particular changelog having sentimental value to a lot of developers.  I think I'll just reject that upload and re-sponsor it with the changelog intact. ;)20:30
slangasekSpamapS: I'm having second thoughts about putting the wait-for-state check in autofs, because that means running extra scripts at boot time that are *only* useful when nis is installed20:35
slangasekif you don't have nis installed, they just slow the boot down for no reason20:35
slangasekso blah20:35
SpamapSslangasek: yeah, seems like nis should have that script20:36
SpamapSslangasek: you can always cancel a starting job and take it over with start on starting...20:36
SpamapSslangasek: though I haven't thought this through, and I need caffeine/food so ignore me ;)20:37
slangasekSpamapS: my current thoughts: http://paste.ubuntu.com/859688/20:39
slangasekthe "cron" part should maybe go away though, because cron is smart enough now to detect when names become resolvable20:40
slangasekbroder: can I easily get access to the lintian lab?20:41
broderslangasek: uh, i don't have anything setup for it at the moment. if you'd like to wait 20-30 minutes, i can get off my rear and finally set something up. otherwise, i can run things for you20:44
slangasekbroder: I'm looking for 'grep -l 'Should-Start:.*ypbind' /etc/init.d/*'20:46
slangasekbut I may have another way to run it that's nearly as fast20:46
smoserslangasek, well, in so far 3 tries, i've yet to make the it fail at local-premount20:46
smoseri'm running some more... as 3 isn't very definitive20:47
slangaseksmoser: sure :)20:47
smosercan you come up with any reason why that blkid would have been running though?20:47
broderslangasek: running now20:48
smoseri'm really not interested in changing code without a reason, as20:49
smosera.) i already did that once for this bug :)20:49
slangaseksmoser: sure, something generating a change event on the kernel device20:49
smoserb.) it seems that 11.10, 11.04, 10.10 are also vulnerable to this20:49
slangaseksmoser: as part of the blkrrpart ioctl20:49
smoserbut what would have done that?20:49
slangaseksome aspect of the kernel driver20:50
smoserand why would we think that prior to mount of root anything would be different for *that*20:50
slangasekoh no, sorry20:50
slangasekthis is blkid running *while* we're trying to call blkrrpart20:50
slangasekso what would cause the event, hmm20:51
slangasekyou can probably argue that it's a kernel bug20:51
smoserbecause if we dont know what would have done it, then i have a hard time coming up with a reason it can't happen during premount either.20:51
slangasekwell, the only thing going on here that *could* do it, AFAICS, is the mount/umount20:52
slangasekand if it is, I think that's a kernel bug20:53
slangasekbut of a sort that's probably hard to isolate and fix20:53
smoserslangasek, well, i can't seem to trigger the mount/umount in a loop in user space20:55
smoser(unfortunately i cant reproduce any of this cleanly outside of first boot)20:55
smoserand it only started showing up withen we upgraded to precise kvm and openstack20:55
smoserwhich obviously changed a bunch of timings20:55
smoserslangasek, if it were triggered by mount/umount, you would think that it could be triggeref by somethin glike:20:56
smoser while : ; do mount ext4-dev /mnt && umount ext4-dev /mnt ; done20:57
smoserand watching udev20:57
smoserand i think that nothing happens20:57
smoser(i can test that, but basically ou'r asserting that some udev event would fire based on that)20:57
smoser(i think)20:57
smoserunless you have some reason that that mount/umount early in boot would trigger something that subsequent mount/umount wouldnt20:59
slangaseksmoser: nope21:00
smoserso then at this point, the best justification for a change from local-bottom to local-premount is that "it seems simpler"21:02
smoser(and testing seems to change the race conditions)21:02
slangasekno, it's that the *only possible* thing we've found that could be racing is something triggered off by the mount/umount21:03
slangasekeven if we don't understand it21:03
smoserdo udev events have timestamps on them?21:04
smoserie, when the kenrel fired this event, could i get a timestamp of when it did it ?21:04
smoserbecause then, if i could, and verify that no events came from the kernel *after* mount/umount, then i'd know that it wasn't during that21:04
slangaseksmoser: what you see in /var/log/udev is what you get21:05
slangasekso there's a "time since boot" in the header line21:05
smoserbut is that udev recieved ?21:06
smoseror kernel generated21:06
slangasekudev received21:07
smoserwell, at least its something21:07
slangasekbroder: so on second thought, I think I actually want this scan done against Debian unstable anyway :-)21:07
smoseri'll add some 'cat /proc/uptime' and see if i cant dgrock anything from it.21:07
smoserslangasek, thank you for your help, btw21:07
broderslangasek: ah, can't help you there21:08
slangasekbroder: yep - no worries21:09
TheMusoinfinity: Done.21:13
infinityTheMuso: \o/21:13
smoserslangasek, http://paste.ubuntu.com/859728/21:14
smoserthats pastebin of console output of this instance at21:14
slangaseksmoser: doesn't let me in21:15
smoser(sorry, was slow)21:16
smoserslangasek, ^21:16
smoserbut that one didn't catch the blkid in 'ps'21:17
slangasekpulled the IP from the log :)21:17
slangasekbut it's still not letting me ssh in21:17
smoserslangasek, vorlon@dario.dodds.net as your ssh id ?21:31
smoserslangasek, and i did get a failed resize21:32
smoserafter move to pre-mount21:32
smoser2 out of 2921:32
slangaseksmoser: yes - it lets me in now where it didn't before21:32
slangasekhmm, curiouser and curiouser21:33
smoserunfortunately, that ami doesn't have the 'ps -w' in it21:34
smoserso i dont have ps output21:34
smoserslangasek, one thing.21:36
smoseri did not 'udevadm settle' before sfdisk in pre-mount21:36
ricotzslangasek, hello21:52
ricotzslangasek, do you know why libpst wasnt updated since karmic? https://launchpad.net/ubuntu/+source/libpst21:52
ricotzi am pinging you because you are one who touched it ;)21:53
seb128ricotz, because nobod maintains it in Ubuntu and Debian doesn't have a newer version so most likely nobody noticed it was outdated21:55
slangaseksmoser: just a hunch... can you call sfdisk with --no-reread?21:56
seb128ricotz, there is no bug open asking for an update either21:56
smoserwe had another bug on that.21:56
slangasekricotz: what seb128 said; the only thing I touched on the package was to fix a build failure21:56
infinityslangasek: Oh hey, jasper does that too.21:56
ricotzseb128, i see, i guess this is worth an update21:56
infinityslangasek: I wonder if there may have been a reason. :P21:56
seb128ricotz, you are welcome to work on that, I would be happy to review,sponsor your update ;-)21:57
seb128ricotz, it might require a ffe if the update is not only bug fix though21:57
smoserhttps://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/906722 slangasek <--21:57
ricotzseb128, alright, this version is from karmic ;)21:57
ubottuLaunchpad bug 906722 in cloud-initramfs-tools (Ubuntu) "root partition is not being grown" [High,Fix released]21:57
ricotzseb128, fta updated it for some testbuilds of evolution 3.3 which requires this newer version21:58
slangaseksmoser, infinity: by default, sfdisk calls ioctl(BLKRRPART) before it edits things, and again *after*... and if the ioctl is itself triggering a udev change, then there's nowhere in your script to intercept it because it's happening while a single sfdisk command is running21:59
ricotzseb128, alright, i have a look21:59
seb128ricotz, thanks21:59
smoserslangasek, oh. yuck.21:59
smoseri didn't realize that.21:59
smoserthat sucks.21:59
smoserso that is a general issue with sfdisk then22:00
smoserthat will fail at other times also22:00
smoseras the first will *cause* the second to fail22:00
smoserslangasek, so i'm guessing you're looking at code22:01
slangaseksmoser: again, if there haven't been any geometry changes, and the ioctl causes this problem, I think you're looking at a kernel bug22:01
slangasek(and the first time we call the ioctl, there shouldn't be any geometry changes)22:01
smoserslangasek, actually i'm almost certain that it does cause udev events22:02
smoserhold on. thats easy to check22:02
slangasekit shouldn't, because nothing has changed22:02
slangasekyou only want change events when the geometry has actually changed; the kernel should be smarter about that22:02
slangasekanyway, --no-reread is correct for what you're doing22:03
slangasekthe extra reread is pointless here because you know the state of the system in the initramfs22:03
smoserand it doesn't seem to.22:03
smoserslangasek, so your theory here is that if i add '--no-reread', and that fixes it22:05
smoserthen all we're doing is masking a kernel bug22:05
slangasekwell, we're fixing a minor bug in the invocation of sfdisk, and confirming a bug in the kernel22:05
smoserok. so, i'll poke at this a bit later.22:06
smoseryou think 'growpart' should generically pass that ?22:07
smoseras it is accounting for failure, and replacing it22:07
smoser(ie, growpart wont always only be called from initramfs, or at least that was a goal in writing it)22:07
slangasekI think I would assume that the disks are in a sane state before someone's called growpart on them anyway22:08
slangasekbut if you think that's not a safe assumption, growpart can grow an option itself22:08
smoserright. i think probably sane, or maybe add a '--no-no-reread'22:09
broderjdstrand: ah, sorry bug #884402 got left in the queue - i've been meaning to deal based on russ's feedbac22:11
ubottuLaunchpad bug 884402 in shibboleth-sp2 (Ubuntu) "package libapache2-mod-shib2 2.4.3+dfsg-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1" [Undecided,Triaged] https://launchpad.net/bugs/88440222:11
broder(we managed to convince him that his postinst was wrong, but we can't just sync it because there are significant pending changes on the debian side)22:11
geserinfinity: it got sponsored before I could add a debdiff with a complete changelog, so I didn't replace the debdiff afterwards22:25
geserinfinity: I'll update the debdiff if you reject the current upload22:26
infinitygeser: I already fixed it.22:26
geserwill remember on future merges to keep old changelog entries forever22:39
seb128geser, why so?22:41
geserseb128: I dropped old changelog entries (800 lines of Ubuntu changelog entries from lucid back to warty) in my last vim merge which infinity prefers to keep22:43
seb128ok, we drop those for desktop and I do the same for other stuff I merge usually22:43
seb128so I take a not to not merge stuff infinity's maintains ;-)22:43
infinitygeser: I'm not sure that's necessary (or even desirable) for most packages/mergs, but vim's a special and weird case. ;)22:43
infinityseb128: Surely, you remember the upload wars to all get in in the same 5-minute window and see whose vim would get accepted? :P22:44
infinitygeser: Anyhow, yeah.  Not a big deal, and not a policy, per se, to retain changelogs for ever (unless they actually still reference our delta in some meaningful way), but there's some old skool project nostalgia with vim specifically.22:45
infinitygeser: And possibly base-files. ;)22:45
=== salem_ is now known as _salem
geserinfinity: I would have expected setting background=dark for vim by default would cause more discussion than my trimming of old changelog entries22:48
infinitygeser: Nah, because background=dark is the One True Way.22:49
infinitygeser: People with white terminals are wrong.  Full stop.22:49
infinitygeser: (And as this is clearly a religious argument, not a scientific one, there's no need for me to back up that assertion with evidence, and it's protected by various constitutions!)22:50
infinitygeser: Of course, it could also be that it's still sitting in the unapproved queue.22:51
geserinfinity: so no objections for background=light for gvim either (or do you don't care about gvim)?22:54
infinitygeser: That seems reasonable as a default, but I don't use gvim, which is probably why I don't care. ;)22:56
slangasekinfinity: can you think of a way offhand to get dash to read contents from a file and pass the contents to another command on the commandline, without forking to get the file contents?23:07
slangasek( $(< /path/to/file) is a bashism )23:08
broderslangasek: doesn't $(< /path/to/file) fork?23:11
slangasekbroder: shouldn't23:12
broderoh i see. i didn't realize that was special-cased syntax23:12
slangasekthere's no command23:12
slangasekyou're just asking for the contents of the file23:13
broderi figured it was a shortcut for $(exec </path/to/file) or something23:13
slangasekbroder: I don't suppose you can think of a more posix-y way to do this? :)23:14
broderi assume the lack of forking is important?23:14
slangasekbroder: upstart :/23:16
broderexpect daemon and add another fork somewhere? :)23:18
slangasekit already needs to be expect daemon23:18
jdstrand@pilot out23:18
=== udevbot changed the topic of #ubuntu-devel to: Precise Beta-1 Freeze in effect. Archive: open | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/xmGdCW | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
broderaren't you good, then? i thought upstart was fine with several forks before the actual double-fork happened23:19
slangasekbroder: no, it counts forks23:21
SpamapSbroder: nope, 1 or 2.. or 'tis broken23:21
SpamapSI really wish we could just trust daemons to tell us what their main pid is (i.e., pidfiles)23:22
brodererr, i wasn't clear. i meant rather that you could fork off stuff in the script section as long as none of them forked again23:22
infinityslangasek: Of the top of my head, I can't think of a way to do that without forking. :/23:28
* slangasek nods23:29
infinityslangasek: http://paste.ubuntu.com/859877/ ?23:39
infinityslangasek: Or is FD manipulation out too?23:39
slangasekinfinity: no, that's acceptable as long as it doesn't trigger a fork :)23:40
slangaseklet's see, can I just do while read ... do done < $FILE without generating a subshell?23:41
infinityslangasek: Maybe?23:42
infinitystrace doesn't look forky to me.23:44
slangasekyep, that does the trick23:45
slangasekinfinity: thanks :)23:45

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