/srv/irclogs.ubuntu.com/2011/09/23/#ubuntu-devel.txt

micahgSweetshark: I'd suggest discussing with tyhicks about ecryptfs and how likely it is to be impacting this bug00:26
tyhicksmicahg: Good suggestion - I've read through it and don't have any good ideas about what eCryptfs could be doing incorrectly00:58
tyhicksDigging in deeper is next on my todo list00:59
micahgtyhicks: sweetshark is in UTC +2 I believe, maybe you could chat with him at some point00:59
LaibschSweetshark: My opinion (which I've already given you in private before) is that you've been trying too aggressively to "close the ticket" and get it off your radar.  When what should really be done is analyze and fix the problem.01:00
LaibschSweetshark: Case in point: Your recent setting to invalid state for the office package when no matter what ecryptfs does or doesn't do, a program should never segfault.  Or your closing as wontfix without any explanation.  You're doing better with the latest comments and explanations.01:00
LaibschSweetshark: thank you for the work you're doing. Much appreciated.01:00
* Laibsch is one of the affected people and in UTC+801:01
tyhicksLaibsch: hello - upstream eCryptfs kernel maintainer here01:02
LaibschI know01:02
LaibschI'm the 50G/140G false positive guy ;-)01:02
tyhicksLaibsch: I tend to agree - since eCryptfs isn't oopsing or falling completely on its face, it sounds like something that could be handled better in userspace01:02
Laibschso we meet again (we can talk privately if you want)01:02
tyhicksLaibsch: ah, that's right :)01:02
Laibschthe problem is 100% reproducible for me.  So, if you can cook up something to collect data, I'm here.01:04
tyhicksLaibsch: I've looked through the report and traces provided and I didn't see much to work off of01:04
tyhicksLaibsch: I think I'm going to need to reproduce it locally (I haven't had a chance to try yet) and then start poking from there01:05
tyhicksLaibsch: I really appreciate the offer and will keep it in mind01:05
Laibschtyhicks: Yes, best is of course if you can reproduce it locally.  But apparently Sweetshark had some trouble doing that.01:06
Laibschtyhicks: I find that Ian guy a bit of a pain in the ... but he says he can reproduce file corruption (comment 53).  Whether that's the root cause of the crashes or even a false claim, I don't know.  But maybe he can give you some valuable data as well on supposedly ecryptfs-induced file corruption.01:12
tyhicksLaibsch: Yeah - just read that comment... I'll definitely have to follow up on that claim01:13
Laibschwould it help if I ran Office through valgrind?01:13
* Laibsch wonders what upstream discussion Sweetshark was referring to01:14
Laibschprobably http://nabble.documentfoundation.org/Multiple-issues-with-cppuhelper-source-exc-thrower-cxx-td2992234.html01:15
smoserslangasek, heres a strange (to me) console log http://paste.ubuntu.com/695394/01:15
=== plars-afk is now known as plars
lamontI wonder, how do I get do-release-upgrade to _NOT_ run screen?02:25
micahgwhy would you want that?02:26
lamontbecause the serial console hates screen02:26
smoserslangasek, ok. i opened bug 856984.  i know whats wrong, and *a* fix is fairly straight forward.02:26
ubottuLaunchpad bug 856984 in isc-dhcp (Ubuntu) "dhclient-script attempts to write /etc/resolv.conf before it is writable" [Undecided,New] https://launchpad.net/bugs/85698402:26
lamontseems that removing screen fixes the issue02:26
smosernice02:26
TheMuso/c/c02:31
=== Amaranthus is now known as Amaranth
ScottKMan, where's barry when you need him.04:30
* ScottK wanted to see him headdesk: https://github.com/whymirror/unholy04:30
infinityScottK: That's vile.  And a thing of beauty.05:28
* ScottK thinks barry will love it.05:28
StevenKOr he will claw his eyes out.05:29
micahgreminded me of this: http://www.linuxjournal.com/article/928205:29
ScottKEntertaining either way.05:29
broderyou guys have seen perl's Inline::C and Inline::Python, right?05:31
broder(well, s/perl/CPAN/)05:31
infinityInlining is a bit different than this python/ruby translation madness.05:31
StevenKI've *used* Inline::Python.05:32
infinityI'm reminded of Facebook's PHP-to-C compiler.05:32
StevenKIt's utter crack.05:32
broderinfinity: but similarly terrifying :)05:32
didrocksgood morning05:35
ScottKGood morning.05:35
ScottKdidrocks: Bad news on the Qt front ...05:35
ScottKIt looks like it's going to fail on armel (already did on powerpc)05:35
ScottKWith that bit of joy, I'm off to bed.05:36
ScottKHave a nice $TIME_OF_DAY.05:36
didrocksScottK: argh, ok, I'll try to have a look05:36
ScottKThanks.05:36
didrocksScottK: have a good night :)05:36
=== Quintasan_ is now known as Quintasan
lucasdoko_: libdb-ruby was entirely superseded by ruby-bdb, it just needs decruft to disappear06:09
=== eyes_ is now known as EyesIsServer
dholbachgood morning07:14
doko_lucas, right seen now. but the source is still in unstable too (and libcairo-ruby)07:57
=== tkamppeter__ is now known as tkamppeter
tkamppeterpitti, hi08:29
doko_mvo, slangasek: I think the break is correct (bug 853688), but I could remove it as well, if it cannot be addressed otherwise08:38
ubottuLaunchpad bug 853688 in gcj-4.4 (Ubuntu Oneiric) "Natty to Oneiric - failed to calculate the upgrade with gcj-4.4-jre installed" [High,Triaged] https://launchpad.net/bugs/85368808:38
mvodoko_: sorry, I haven't had a chance yet to properly look at this08:40
doko_SpamapS, barry: could you have a look at bug 771121? the easiest way would be to disable the python3 package09:20
ubottuLaunchpad bug 771121 in gearman-interface (Ubuntu Oneiric) "gearman-interface version 0.13.2-2build2 failed to build on amd64 with GCC-4.6/oneiric" [High,Confirmed] https://launchpad.net/bugs/77112109:20
TLEpitti: hallo, I was wondering if you have a few minutes for some language packs?09:21
brycehTLE, think he's on vacation currently09:24
tkamppeterI have uploaded a new HPLIP package which fixes bug 560849 with a tiny patch. The package hangs in the "wait for approval" queue. Can someone approve it (is beta2 not unfrozen yet?).09:25
ubottuLaunchpad bug 560849 in hplip (Ubuntu) "hpfax crashed with NameError in bug()" [Undecided,Fix committed] https://launchpad.net/bugs/56084909:25
seb128tkamppeter, we don't unfreeze09:25
TLEbryceh: ok, do you know who might be filling in for him on stuff like copying newly generated language packs to a proposed repository?09:25
seb128tkamppeter, uploads until Oneiric need to get reviewed09:25
tkamppeterseb128, do I need to do anything special for the uploads to get reviewed?09:27
seb128tkamppeter, no09:28
seb128tkamppeter, they will just be regularly reviewed when release team member look at the queue09:28
brycehTLE, seb128.09:28
TLEbryceh: thanks09:29
seb128heh09:29
TLEahh, you got volouteered there09:29
TLE*G*09:29
seb128TLE, better to wait for pitti to be back, he will be back for monday for sure but it's likely he will be around before that so if you need anything important drop him an email I guess09:30
TLEwell, we are trying to release language pack updates according to a schedule, so that translators know what they have to aim for, and that isn't much good if we keep postponing them. In any case, I'll talk to dpm first and see what he thinks and then maybe I'll be back later09:31
TLEseb128: ^"09:32
seb128TLE: ok, if pitti get online during the day I will ping him about it, I've no real clue how the langpacks work and how to do the copy so I would prefer for him to do it09:32
TLEI already pinged him, I can talk to him about it and them we'll bug you if necessary ;)09:34
dpmTLE, let's have a chat later on in the day about langpacks if that works for you09:34
TLEdpm: absolutely, in the office all day09:34
dpmcool, thanks TLE09:34
TLEno worries09:35
doko_pitti: bad pittivi FFe ;-P10:10
sorenpitti: Any idea why the libvirt package in lucid-proposed hasn't propagated to -updates?10:38
cjwatsonbug 823638 hasn't been marked v-done10:41
ubottuLaunchpad bug 823638 in libvirt (Ubuntu Natty) "Please put comment in /etc/default/libvirt-bin or remove it from the .deb" [Undecided,Fix committed] https://launchpad.net/bugs/82363810:41
cjwatsonwhich may be trivial from that bug description; I'm just reading the dashboard10:42
sorenOh, I see.10:43
ScottKjanimo: The glmark2 package you uploaded seems very much like it's not just bug fix only, so I'm going to reject it.  Please coordinate with the person you're sponsoring for (Alexandros Frantzis) and follow the FFe process.10:46
DavieyAny AA's around that can promote an approved MIR please?10:48
janimoScottK, it is sponsoring by alf_ via pm request this morning10:49
ScottKjanimo: Right.  I'm not saying who needs to fill out the FFe, but you're the one that's supposed to know about such things.10:50
janimoScottK, honestly had no idea FFE applies to universe10:50
ScottKOK.10:51
ScottKIt applies to the entire archive.  It always has.10:51
ScottKLesson learned I guess.10:51
janimoalways? Even for GNOME components?10:51
sorenEverything that doesn't have a standing exception.10:51
Davieyjanimo: Are you thinking of feature defintion freeze?10:52
DavieyThat doesn't apply to universe.10:52
janimoDaviey, not sure about the naming. Thinking along the lines, of blanket exception for universe packages where upstream collaborates closely with Ubuntu (e.g linaro in this case) and where they know what they're doing10:52
janimosoren, yes, I assumed there was a standing exception for universe10:53
Davieyhttps://wiki.ubuntu.com/StandingFeatureFreeze10:54
DavieyHardy :)10:54
Davieyjanimo: No, standing applies to packages or groups of, not whole components. :o10:54
janimoDaviey, what does it take to add a new group there? A lot of Linaro stuff - on a different schedule than ours - keeps happening after our freezes. For ARM users and devs it helps to get access to these via the official archives10:55
janimonot talking about landing new kernels/bootloaders which can break stuff, but universe apps10:56
Davieyjanimo: A blanket standing exception to the release team via a bug of nominated packages, and who is responsible for making sure they are kosher.10:57
janimoScottK, https://bugs.launchpad.net/ubuntu/+source/glmark2/+bug/85727910:58
ubottuUbuntu bug 857279 in glmark2 (Ubuntu) "FFE for Oneiric" [Undecided,New]10:58
Davieyjanimo: https://wiki.ubuntu.com/FreezeExceptionProcess should be a good guide10:58
Davieyjanimo: That bug really needs more detail10:59
janimoasac, rsalveti see what Daviey says above. You may want to add this to the discussion at UDS10:59
cjwatsonjanimo: freeze doesn't mean you can't upload stuff, it just means it requires some thought10:59
cjwatsonLinaro does too much core stuff for me to be comfortable with a standing feature freeze exception for everything they do10:59
cjwatsonfor universe applications, I'd have thought that we could easily just work case-by-case?11:00
janimocjwatson, no core stuff, no kernel/bootloader/X is sane to upload with features at this point. I was talking about blanket for the sundry apps/tests/tools they do that affect hardly anyone but ARM users11:01
janimoDaviey, I'll ask alf I merely sponsored him, have no idea what is in the new release11:01
Davieyjanimo: Are you talking features or bugs?11:02
DavieyI mean, if you are fixing FTBFS's on arm for example, that wouldn't need a FFe.11:03
janimoDaviey, features but for fringe apps11:03
janimosure, bugs  I know11:03
htorquesoren: hi! are you currently testing the suggested patch at https://bugs.freedesktop.org/show_bug.cgi?id=41059 ?11:03
ubottuFreedesktop bug 41059 in Driver/intel "XRANDR operations very slow unless (phantom) HDMI1 disabled" [Major,New]11:03
janimoDaviey,  universe apps which do not affect non-ARM images11:03
janimoand mostly developer stuff11:04
Davieyjanimo: Something that adds weight is that those working on it will /use/ it before release to spot regressions, and committing to fixing them.11:05
Davieyfor example, we decided not to update to the latest qemu as we knew that if it did go bang - we'd not have the time/resources to fix it.11:06
Davieyalthough slangasek is thinking about doing that for qemu-linaro :)11:06
janimoDaviey, I sure hope Linaro uses their tools. They use PPA's a lot so they are not much pressured to upload or do not know the hops that need to be jumped through11:06
janimoDaviey, QEMu breaking would mean the whole cloud/server things being affected, very different :)11:07
janimoglmark2 having a regression? pfft11:07
janimoanyway something to discuss with the Linaro guys at UDS11:07
ogra_janimo, well, its our job to care for the archive and get the bits into it11:08
ogra_i dont think there is much to discuss11:08
DavieyYeah, too much policy/hoops can make people choose not to bother :(..  Having done a few FFe's, it becomes a reasonably fast process.. it's a reasonable balance atm, i feel.11:08
janimothey move at a fast pace with their development, monthly releases and PPAs, need to find a good match between their interrests and the fact that we'd also like to ship ARM stuff  that is not too stale11:08
sorenhtorque: Not really :( If someone could toss me a kernel image that I could try, then sure. I'm a bit too busy to sort that out myself right now :(11:08
ogra_janimo, in the past we simply used to have a team member in the universe release team11:08
ogra_we should probably revive that11:08
Davieyogra_: arm or linaro?11:09
ogra_Daviey, ??11:09
janimoogra_, 1) so we could just approve all our FFEs? Nice 2) You are not talking me into becoming that person11:09
ogra_lol11:09
ogra_Daviey, i'm ubuntu-arm11:09
Davieyogra_: "in the past 'we' had a tam member", who is we?11:10
Davieyteam*11:10
* ogra_ doesnt talk for linaro 11:10
cjwatsonI don't think we should have people who are in ubuntu-release just to approve their team's exceptions11:10
cjwatsoncross-fertilisation and cross-checking is extremely valuable11:10
htorquesoren: ok, in that case i'll test it with 3.1-rc7 here. just hope my tailored config is enough to reproduce the bug. don't wanna build a full ubuntu-config kernel.11:10
janimocjwatson, I forgot a smiley there in 1)11:11
ogra_cjwatson, well, but having the people knowing the code also reviewing it makes everything a bit easier11:11
cjwatsonogra_: certainly having people available is helpful, but I will definitely nack any attempt to add people to the release team simply in order to work around exception requirements11:11
ogra_(and not only knowing but being able to verify on HW)11:11
ogra_cjwatson, i didnt intend that with the suggestion11:12
cjwatsonthe release team is the Ubuntu release team, not just the Ubuntu ARM release team - I expect team members to be concerned for the health of the project as a whole11:12
ogra_we used to do it in the past simply because the process was faster11:12
ogra_not because we handled the execptions more losely11:12
Davieyogra_: It should be possible to demostrate a good level of confidence to someone who doesn't understand the issue IMO.11:13
DavieyYeah, i don't think ogra_ is suggesting bypass of process.11:13
ogra_oh, sure, i dont say i mistrust anyone :)11:13
cjwatsonI trust the people involved, but I've found for myself that when you're the person who's acting for the release team for your own team's requests, there is a lot of psychological pressure to say yes despite reservations because you know that your teammates have put a lot of work into this11:14
doko_Laney, janest-core, remove or fix it?11:15
cjwatsona degree of separation helps to avoid that and can actually reduce stress11:15
janimocjwatson, true.11:15
ogra_but it also slows down the process since you need to work yourself into code other know in and out11:15
ogra_*others11:15
cjwatsonI think that's an acceptable price to pay11:16
cjwatsonanyway, reviewing freeze exceptions doesn't mean a complete code review11:16
ogra_indeed11:16
cjwatsonit's more an assessment of its likely impact and sanity11:17
ogra_which an arm person can judge better than a non arm person in this case11:17
cjwatsonI do not in general agree11:17
cjwatsonif the ARM person can't explain it in a way that's clear enough for a non-ARM person to understand, I find that questionable11:18
cjwatsonand non-ARM people are perfectly capable of judging when things essentially only affect ARM and when they may affect other architectures too11:18
cjwatsonand acting accordingly11:18
ogra_well, you save the need for the explanation in that case, indeed one asking for a freeze exception should always be able to explain it to non arm people11:19
ogra_(and thats not arm specific at all)11:19
DavieyInverse, unless the package only builds on arm target - can they measure the impact for other arches with confidence?11:19
cjwatsonI don't agree that saving the need for the explanation is a good thing11:19
asachas we/linaro requested a standing freeze exception? :)11:20
ogra_lol11:20
ogra_no11:20
asacok. got the impression we had from the lines i saw above :)11:20
cjwatsonwhere possible, we should be finding points of commonality across architectures, and it's important that (especially) release team people learn the rough parameters of the differences between ARM and everything else11:20
cjwatsonsaying "don't worry, the ARM people will sort it all out and don't need to explain it to you" just encourages siloing11:21
cjwatsonand I really think it's important to find ways to avoid that11:21
ogra_asac, i was only suggesting to have an arm person back in the universe approval team for FFes as we had it in the past11:21
asacI think we are happy with the process until we complain. however, we are on a monthly release cadance so keeping process lean for stuff that doesnt risk ubuntu release would make sense11:21
asacogra_: ok i see11:22
asacogra_: any cases of slow turnaround of current team? or "stupid" quesitons of release team because they were not familiar enough with ARM topics?11:22
cjwatsontjaalton: can we merge libx11 from unstable (or can I)?  It has a cross-building fix I'd like to have11:24
ogra_asac, neither, just janimo not knowing we need FFes for universe that lead to this discussion11:25
cjwatsontjaalton: I don't know if you manage it in revision control11:25
asacogra_: ah. that feels is a different problem :)11:25
tjaaltoncjwatson: i merged it yesterday already11:25
tjaaltonand uploaded11:26
tjaaltonappears to be in the archive too :)11:26
cjwatsonoh :)11:26
cjwatsonsudo apt-get --reinstall install brain11:27
cjwatsonthanks11:27
janimoasac, exception requests aside, it is not clear what Linaro wants to have in the main archives, if there is such a position at all, or left for each WG/developer to sort it out11:27
asacogra_: I think one thing that could be done better is to what a feature really is ... is it if it changes the the software (current) or rather if it changes the behaviour/featureset availbale in one of the seeds11:27
asacbetter define (or maybe improve) what a feature really is11:27
asacbut thats just a guts feeling11:27
cjwatsonwell, it's already well-defined that simply changing the software does not amount to a feature11:27
cjwatsonbug-fixes are fine11:27
asacsure11:28
cjwatsonTBH I've not had any developer enquire what a feature is before :-)11:28
tjaaltoncjwatson: yeah jcristau mentioned the bug on irc, and later Sarvatt noticed that the fix was uploaded so I merged it right away11:28
cjwatsonit's just the plain English meaning11:28
asaci was meaning: is a package view really what is important or should we rather take a seed/image view to identify if something is a feature worth spending review cycles on11:28
cjwatsonwe certainly do not have anything which ties it to seeds or images, otherwise FFes would be meaningless for universe11:28
cjwatsonand I think the consensus among universe mavens has been that they want to have a degree of review there11:29
asacso xubuntu etc. dont use universe at all?11:29
cjwatsonwell, OK, there are images built out of universe11:30
cjwatsonbut I mean MOTU leaders have historically expressed a preference for having a consistent feature freeze *process* across the board, even if the actual reviews are often pretty rubberstampy for things whose effect is minimal11:30
asacright11:31
Davieydoko_: thanks for the promotion.11:31
cjwatsonand I do think it's clearer to be able to just say "if you're adding features after feature freeze, you need an exception" rather than having to figure out whether something is in an image or not11:31
cjwatson(which is actually kind of non-trivial for many people to work out)11:31
asactrue11:31
doko_pitti, seb128, didrocks: is there a gnome-shell upload pending?11:34
seb128doko_, not sure, I need to check with jbicha when he will be online, the current one is depwaiting on caribou11:35
seb128doko_, which he was trying to get in for some time, so not sure if we should wait on caribou on try to reverse the depends on it11:36
seb128revert11:36
seb128same for pitivi, waiting on jbicha to be online11:36
ogra_ogra@horus:~$ echo "FileVersion:     14.0.4756.1000"| sed "/^FileVersion: */!d; s///;q"11:57
ogra_echo "FileVersion:     14.0.4756.1000"| sed "/^FileVersion: */dmesg; s///;q"11:57
ogra_sed: -e expression #1, char 19: extra characters after command11:57
ogra_wow, wher does that autocompletion come from ?11:58
ogra_*where11:58
cjwatsonogra_: history expansion12:04
sladenogra_: the  '!'12:04
cjwatsonogra_: use single quotes instead; you have no need for double-quote expansion there12:04
ogra_intresting12:04
* ogra_ doesnt actually have a usecase for this, i just verified something from the ubuntu-devel ML ... but found it surprising to see what happens :)12:05
cjwatsonI turn off history expansion on my systems because (a) I find it too annoying (b) I never actually want to use it (c) it conflicts with more useful expansions enabled by extglob12:06
sladenogra_: echo "!emacs"  etc12:06
cjwatsonso I have 'set +H; shopt -s extglob' in .bashrc12:07
Laneydoko: I have no idea what that is12:07
Laneyis there some reason I should?12:07
ogra_sladen, heh, that would require that any of my systems has ever seen emacs :) but yeah, i get it12:08
cjwatsonso for me the command line ogra_ quotes works as presumably intended, but it's not portable12:08
ogra_thaks for the exaplanation !12:08
cjwatsonnp12:08
dokoLaney, I don't know, didn't you fix some other ocaml stuff?12:08
Laneyprobably not intentionally12:08
Laneyi did once write some ocaml12:09
cjwatsondoko: you might be mixing up ocaml and haskell12:09
DavieyEverytime i forget to sudo a command, i follow it with a "sudo !!" on the next line12:09
dokoahh, ok. removing then!12:09
LaneyI recommend you ask sgnb about it12:09
Laneygive peace a chance!12:09
dokook, ok ...12:10
Laneyit looks like something you'd be able to fix if you know what the error means12:11
cjwatsonDaviey: yeah, I know some people use that - I've got used to up-arrow ctrl-a sudo space enter, and !(...) is such an incredibly useful extended glob expansion that it's worth it12:12
sgnbLaney: about what?12:13
cjwatson("any file that does not match these patterns")12:13
Laneyoh, you're here12:13
Laneysgnb: https://bugs.launchpad.net/ubuntu/+source/janest-core/+bug/83110612:13
ubottuUbuntu bug 831106 in janest-core (Ubuntu Oneiric) "janest-core version 0.6.0-3 failed to build in oneiric" [High,Confirmed]12:13
Laneydoko is on an FTBFS busting exercise12:13
cjwatsonDaviey: plus the way that if you mistakenly type ! in something it disappears from your history really bugs me12:13
sgnbLaney: ah, known issue12:13
Laneyknown fix?12:13
sgnbupgrade to latest upstream12:14
sgnbbut ENOTIME these days12:14
sgnb(and there are also dependencies to upgrade)12:14
Davieycjwatson: I can see benefit for using extglob, might start.12:15
dokosgnb, so better remove it for oneiric, or will you have a chance to update it12:15
sgnbremove it12:15
dokook12:15
sgnb(it has been removed from testing, fwiw)12:15
sgnbbut uninstallability of ocamlgraph is unexpected12:16
sgnbI guess a recompilation should fix it12:16
cjwatsonDaviey: oh, hmm, it looks as though nowadays you can use extglob sensibly even with history expansion turned on, so my (c) no longer applies12:17
Davieybah12:18
cjwatsonDaviey: this wasn't true in Feb 2003 when I made this change to my .bashrc :)12:19
Davieycjwatson: you've kept the same .bashrc since 2003? crikey.12:20
Chipzz14:13 < sgnb> Laney: ah, known issue12:20
Chipzzoops12:20
cjwatsonDaviey: no, but I've had it in revision control since 2002 :)12:20
ChipzzI hate it when you select sth and just when you copy the terminal scrolls under you12:20
cjwatsoncertainly a linear descendant; I see no reason to rewrite it ...12:20
Chipzz14:13 < cjwatson> Daviey: plus the way that if you mistakenly type ! in something it disappears from your history really bugs me -> this indeed, I hate that you have to copy/paste the original command and fix it12:21
DavieyMy rule of thumb is that .bashrc should be younger than your current underwear.12:21
* cjwatson spots a cloud person12:21
Laneyah indeed, I'll see about rebuilding ocamlgraph frama-c12:21
cjwatson(please tell me you don't store your underwear in the cloud)12:22
sgnbLaney: ocamlgraph should definitely be recompiled (and has been since lablgtk2 was upgraded)12:22
Chipzzcjwatson: at least it's dry-cleaned that way ^^12:22
dokoDaviey, iiuc ScottK, bug 831121 and bug 831179 are on the server radar?12:22
ubottuLaunchpad bug 831121 in dovecot-antispam (Ubuntu Oneiric) "dovecot-antispam version 1.4~rc3-1 failed to build in oneiric" [High,Confirmed] https://launchpad.net/bugs/83112112:22
ubottuLaunchpad bug 831179 in dovecot-metadata-plugin (Ubuntu Oneiric) "dovecot-metadata-plugin version 0.0.1~hg144-0ubuntu1 failed to build in oneiric" [High,Confirmed] https://launchpad.net/bugs/83117912:22
sgnbLaney: and maybe frama-c as well, but I'd wait for ocamlgraph to be installable again12:23
Laneyaye12:23
* Laney is familiar with the dance12:23
Davieydoko: dovecot-antispam wasn't12:23
Davieythanks12:23
Chipzzcjwatson: IMO a "blog your .bashrc/.vimrc/.screenrc" meme would be interesting and useful :)12:24
Chipzzespecially from debian/ubuntu developers12:24
cjwatsonthere was a point in job[-1] when my .vim directory was simultaneously stored in CVS and Subversion12:25
cjwatsonthat was exciting12:26
Chipzzexciting? sounds confusing instead12:26
Laneyscary12:26
LaneyI just got a prompt which just said "Password: " and kept respawning when dismissed12:26
NafaiChipzz: I keep meaning to blog about my .bashrc and .emacs.d; both are set up to dynamically handle being on multiple machines and custom parts on each12:27
ChipzzNafai: I recently fixed my .vimrc to work with vim-tiny12:28
ChipzzI was getting annoyed at vim-tiny throwing sh*tload of errors upon starting with my .vimrc12:28
Chipzz(first thing I do when I install a new machine is wget my .vimrc, but I sometimes forget to replace vim-tiny with regular vim)12:29
cjwatsonI used to have shell configuration which was capable of setting up a sane terminal configuration on all of Linux, HP-UX, SunOS, UnixWare, and IRIX, and various bits in ~/bin/ to try to smooth over the more annoying differences12:29
cjwatson(the current /usr/bin/which on Debian/Ubuntu actually descends from that)12:29
Chipzzhttp://chipzz.safehex.be/docs/vimrc | http://chipzz.safehex.be/docs/bashrc | http://chipzz.safehex.be/docs/screenrc12:30
Chipzzhrrrrm my .bashrc is missing some useful stuff12:31
Chipzzhttp://chipzz.safehex.be/docs/bashrc | http://chipzz.safehex.be/docs/sshrc12:33
Chipzz[ "$SSH_AUTH_SOCK" ] && export SSH_AUTH_SOCK=$HOME/.ssh/@`hostname -s`.agent12:34
Chipzzthat in conjunction with my .ssh/rc is a nice way of getting screen and ssh agent forwarding to work together12:34
Chipzz(but keep in mind to set proper permissions on ~/.ssh !)12:36
=== kentb-out is now known as kentb
dholbachcan somebody moderate my mail through u-d-a?13:41
hallynkees: hey, regarding the lvm udev rules, you said in email there were specific reasons you had to do it how you did - are those documented, and are there testcases?13:56
hallynsmb: when you say 'pkill of udev was a problem on xen guests and had to be redone' - you mean udev didn't really die?13:58
smbhallyn, On the attempts I did it at least did not immediately. So there I had a loop re-doing pkill untill no udev was to be seen anymore14:00
smbhallyn, Maybe bashing it repeatedly with that hammer was not neede dand it was just waiting for all the numerous helpers to be done14:01
hallynsmb: well you're not doin gpkill -9 right?  I assume it was hanging for the same reason it sometimes hangs with udevadm control --exit14:03
hallynsmb: what kills me is anytime i try to have udevd print out the list of pending events, i can't reproduce it :)14:03
smbhallyn, I think there were two problems there: 1. it not getting done with what it was doing when next steps were tried and 2. it never get done (this seems to still happen sometimes with --exit, I was trying to have some dumps of that but xen pv dumps were broken (maybe because of my pvgrub))14:05
smbhallyn, And yes, a pretty Heissen-bug14:06
hallynmakes me feel like i wasted the afternoon, btw14:06
hallynsmb: are you working that bug today?14:06
smbhallyn, No its sort of on a backlog14:07
hallynk14:07
hallynsmb: with xen, is there a way from the host to slow down (renice) the backign store process separately from the domain itself?14:07
smbhallyn, If there is I don't know of one. It seemed to happen relatively reliable on some boots on my server14:08
smbBut I yet, have to confirm whether the dumps would be usable in crash now with the new pvgrub I got14:09
hallynok, thx smb.  ttyl14:09
ScottKbarry: I ran across something yesterday I thought you'd love: https://github.com/whymirror/unholy14:18
barryScottK: oh wow14:19
dokoScottK, please could you have a look at the patch in bug 770975? still ftbfs for me ...14:21
ubottuLaunchpad bug 770975 in mm3d (Ubuntu Oneiric) "mm3d version 1.3.7-1.2 failed to build on amd64 with GCC-4.6/oneiric" [High,Confirmed] https://launchpad.net/bugs/77097514:21
ScottKdoko: Seems mostly OK, but hard codes multi-arch paths.  I think slangasek should review.  I'm sure he'd know the best way.14:27
cjwatsonmvo: do you have any updated assessment of whether porting update-notifier to libappindicator might be feasible for oneiric (bug 779382)?14:45
ubottuLaunchpad bug 779382 in unity (Ubuntu Natty) "update-notifier not visible under unity" [High,Triaged] https://launchpad.net/bugs/77938214:45
cjwatsonmvo: also I don't suppose you've managed to get anywhere with bug 848659 ...14:47
ubottuLaunchpad bug 848659 in update-manager (Ubuntu Oneiric) "Upgrade from natty fails with 64-bit oneiric beta cd" [High,Confirmed] https://launchpad.net/bugs/84865914:47
keeshallyn: not very well documented, but the reasoning was to bring up a root-on-lvm-on-md system without races. the testcase was that my system boots. :)14:47
mvocjwatson: let me check14:51
Nafallocjwatson: hi there. was just looking at bug 736743. would it be appropiate to hide the error message from 11.10 you reckon? just comment it out sort of thing.14:59
ubottuLaunchpad bug 736743 in grub2 (Ubuntu Oneiric) "environment block not implemented on btrfs" [Wishlist,Triaged] https://launchpad.net/bugs/73674314:59
cjwatsonNafallo: uh, maybe, I'm not in general comfortable with that approach but would need to look15:01
cjwatsonI mean, it does genuinely cause limited functionality15:02
didrockscjwatson: I just tried ubuntu-defaults-image with a local --package option. Like ubuntu-defaults-image --package ~/work/isofr/ubuntu-defaults-french_0.1_all.deb. I'm under the impression that despite the package having been copied to config/chroot_packages/, this one wasn't installed in the chroot (I don't see it), and so, all the localization failed.15:03
slangasekdoko: 853688> well, we also don't know if dropping the breaks on libgcc1 is sufficient... if we have to drop the breaks from both libgcc1 and libc6-dev to get apt to solve it, maybe we want to try a different way15:03
Nafallocjwatson: nope. it's just an obstacle in the experience. people notice it, and I bet the splash would come up faster without the message getting displayed.15:04
cjwatsonNafallo: pretty sure it makes sod-all difference to speed15:04
didrockscjwatson: PACKAGE and PACKAGENAME are correct though, and all the sedding as well, I'm not familiar with lb, does lb config really need to be called before copying those package? (and then lb build should do the right thing?)15:04
Nafallocjwatson: heh, you might be right. I'm happy to clock the difference if you want to give it a go :-)15:05
cjwatsondidrocks: well, lb config *is* called before, isn't it?15:05
cjwatsondidrocks: and yes, pretty sure it needs to be15:05
didrockscjwatson: indeed, ok, so not that, I don't see any log of the package being installed15:05
mvocjwatson: I'm on it, seb128 is a great help15:06
mvocjwatson: on the indicator stuff15:06
cjwatsondidrocks: it ought to work from what I can see - can you file a bug with a log?15:07
didrocksmvo: cjwatson: FYI, update-notifier should be visible in unity since beta2, I whitelisted it15:07
cjwatsonmvo: great, thanks15:07
cjwatsondidrocks: yeah, I noticed that, but not unity-2d right?15:07
didrockscjwatson: sure, doing that15:07
didrockscjwatson: unity-2d as well15:07
didrocksat least, was working when I tested it15:07
didrocks(if you turn the right gsettings options of course to get update-notifier showing its icon)15:07
mvodidrocks: ? awsome15:08
cjwatsonoh, right, I missed that that task had been marked Invalid15:08
mvodidrocks: so the fix is actually not that urgent anymore? that is good news and may safe my friday15:08
didrocksthere is a bug about glitches in the icon rendering, but it's rather it being big that hidden (and only under unity): bug #85612515:09
ubottuLaunchpad bug 856125 in unity (Ubuntu) "update-notifier systray icons showed and the wrong place and size" [Medium,Triaged] https://launchpad.net/bugs/85612515:09
didrocksmvo: yeah, you can enjoy your week-end and it's just a "nice to have" now  :)15:09
didrockscjwatson: if it's considered as a security issue, we should whitelist it in natty as well btw15:09
cjwatsonwe should either whitelist it or port it there, yes15:10
didrocksport it for natty? doesn't it sound risky? (whitelist is just a gsettings key away, not that I found the WMCLASS)15:10
hallynkees: i kinda wish boris was to be found here on irc :)  I don't know how far he's gotten in looking at this15:11
smoserslangasek, would you consider the trivial patch to bug 856984 for oneiric ?15:12
ubottuLaunchpad bug 856984 in isc-dhcp (Ubuntu) "dhclient-script attempts to write /etc/resolv.conf before it is writable" [Undecided,New] https://launchpad.net/bugs/85698415:12
hallynppetraki: do you have a root-on-lvm-on-md system we'd be able to use as  a test for whether oneiric with new udev-lvm rules works?15:12
ppetrakihallyn, readily available, no, but I can spare a blade for you.15:13
cjwatsondidrocks: yeah, agreed15:13
slangaseksmoser: I think your { } are redundant and should be dropped, but otherwise yes, I think that looks sane15:14
smoserthey're not redundant15:14
smoserto avoid the error of failed write going to stderr15:15
smoseryou can test if you'd like15:15
smoser$ sh -c ': >> /etc/passwd 2>/dev/null'15:15
smosersh: /etc/passwd: Permission denied15:15
smoserversus15:15
smosersh -c '{ : >> /etc/passwd; } 2>/dev/null'15:15
hallynppetraki: ok, thanks.  At this point tbh i'm afraid we have to wait for P to open up, and address lvm2, dmsetup, and udev packages alltogether.15:16
ppetrakihallyn, sounds like fun :)15:16
hallynppetraki: which, i suppose, is really a foundations team thing...15:16
hallynbut we can beg to be in the loop :)15:16
ppetrakiheh15:16
smoseri probably *do* uses {} more than other people in shell scripts (especially around variable names), but here they're actually useful15:16
slangaseksmoser: ah, because the redirect is done by the parent shell, not by :, check15:17
slangaseksmoser: yes, go for it then15:17
smoserwell, the {} mean its all one shell15:17
smoserno subshell15:17
smoserjust redirect15:17
smoserbut yeah.15:17
smoserthanks.15:17
smoserslangasek, what do you think about the general behavior of '[ -w file ]' not working during a remount,rw ?15:18
didrockscjwatson: bug #857494 FYI15:18
ubottuLaunchpad bug 857494 in live-build (Ubuntu) "package in config/chroot_packages/ isn't installed in the chroot" [Undecided,New] https://launchpad.net/bugs/85749415:18
slangaseksmoser: sounds like a kernel bug to me15:18
cjwatsonthanks15:18
cjwatsonsmoser: access(3) (which is what that does) has always been a bit wonky15:19
didrocksyw :)15:19
smoseri suspect it is not a kernel bug, slangasek but user space15:19
cjwatsonit basically tests the permission bits on the inode15:19
cjwatsonsorry, access(2)15:19
slangaseksmoser: I defer to cjwatson15:19
smoseryeah, me too15:19
cjwatsonI think I would want to attempt an actual open(O_WRONLY|O_APPEND) or something in order to tell whether writes are really possible15:20
cjwatsonoh, and that's what >> does15:20
jdstranddoko: heh, thanks for the honor of ubuntu-mir membership :)15:21
cjwatsonhm, admittedly the man page says:15:21
cjwatson       EROFS  Write permission was requested for a file on a read-only file system.15:21
jdstranddoko: I guess I need to read up on the MIR docs ;)15:21
dokojdstrand, I thought you wouldn't mind :)15:21
cjwatsonso maybe this is a kernel bug, although I suspect you might find they say the docs are misleading :)15:21
cjwatsonbut you can try asing15:21
cjwatson*asking15:21
dokoslangasek, I'll check with mvo on Monday15:22
tkamppeterTo the release team: I have uploaded ghostscript -0ubuntu9 and -0ubuntu10, it is important to take -0ubuntu10 as it completes an uncomplete fix in -0ubuntu9 (bug 856766).15:25
ubottuLaunchpad bug 856766 in GS-GPL "gs crashed with SIGSEGV in gx_num_components_ICC()" [Medium,Confirmed] https://launchpad.net/bugs/85676615:25
dholbachcan somebody moderate my mail through u-d-a please?15:34
cjwatsondholbach: done15:41
dholbachthanks a lot cjwatson15:41
dokojtaylor, what about the upload for bug 845552?15:50
ubottuLaunchpad bug 845552 in gfire (Ubuntu) "[FFE] Too old Gfire in repo for use, update version or remove from archive" [Undecided,Confirmed] https://launchpad.net/bugs/84555215:51
=== antoniojasr_ is now known as antoniojasr
=== beuno is now known as beuno-lunch
SpamapSdoko: re bug 771121 it actually just needs swig 2.016:18
ubottuLaunchpad bug 771121 in gearman-interface (Ubuntu Oneiric) "gearman-interface version 0.13.2-2build2 failed to build on amd64 with GCC-4.6/oneiric" [High,Confirmed] https://launchpad.net/bugs/77112116:18
dokoSpamapS, could you upload a fix for oneiric?16:20
SpamapSdoko: in progress :)16:20
dokothanks!16:21
bambeepitivi is not installable... (it depends on python-gst0.10 >= 0.10.28, this dependency is not found) -> is it a bug or my mirrors are outdated?16:40
bambeehttp://paste.ubuntu.com/695730/16:41
SpamapSgst0.10-python | 0.10.21-2ubuntu1 |       oneiric | source16:43
SpamapSbambee: archives are up to date16:43
bambee0.10.21 < 0.10.28 :)16:45
SpamapSyep16:45
SpamapSmeaning its a bug16:45
SpamapSbambee: I suggest you report it.. I'll raise it to Critical and target to ubuntu-11.1016:45
bambeeSpamapS: ok16:46
ScottKI think that's fixed already16:46
ScottKbambee: Check for a newer pitivi.16:46
SpamapSoh like, in the last 2 hours? :p16:47
bambeeScottK: already tried, nothing changed16:47
ScottKLike earlier today.16:47
bambeeoh16:47
SpamapSindeed, uploaded but not done building16:48
SpamapS    pitivi | 0.14.91-0ubuntu2 |       oneiric | source16:48
ScottKhttps://launchpad.net/ubuntu/+source/pitivi/0.14.91-0ubuntu216:48
seb128SpamapS, that's the correct version16:48
bambee"Fix python-gst0.10 dependency which made PiTiVi uninstallable" <-- indeed, already fixed16:49
SpamapSuploaded 2 hours ago16:49
seb128it's done building16:49
bambeeok, thanks16:49
SpamapSbambee: so yeah, your mirror just needs to catch up :)16:49
bambeehehe ;)16:49
=== beuno-lunch is now known as beuno
jtaylor17:50 <doko> jtaylor, what about the upload for bug 845552?  <-- still no upload rights :/17:03
ubottuLaunchpad bug 845552 in gfire (Ubuntu) "[FFE] Too old Gfire in repo for use, update version or remove from archive" [Undecided,Confirmed] https://launchpad.net/bugs/84555217:03
ScottKjtaylor: Is it in the sponsor's queue?17:12
jtaylormerge requests are there automatically or?17:12
jtayloryup it is17:13
ScottKK.17:13
tkamppeterMy upload of ghostscript 9.04~dfsg-0ubuntu9 got rejected. Is something wrong with it or is it because I have uploaded the -0ubuntu10?17:56
seb128tkamppeter, 0ubuntu10 got accepted to I guess it's the later17:57
infinitytkamppeter: What Seb said.17:57
seb128tkamppeter, no need to accept a version which is included and deprecated by the next one17:57
infinitytkamppeter: I rejected 9 and accepted 10.17:57
tkamppeterNot -0ubuntu10 appeares. Thanks and sorry for the noise.17:57
slangasekcjwatson: I happened to notice that I have ubuntu-xsplash-artwork installed here, and xsplash seems to be on autopilot since karmic; do you know if this package is still useful or if we should be looking at removing it?18:14
SpamapSsmoser: nice fix on isc-dhcp-4 .. funny how there can be too very different versions of what "writable" means ;)18:18
smoseryeah, i'm wondering if there are other pars of boot that are making similar assumptions/mistakes18:19
smosers/pars/parts/18:19
broderi'm still confused why access() would say yes when open() would say no18:21
SpamapSyou're allowed18:21
SpamapSyou're just not ABLE18:21
SpamapSits like giving a two year old a driver's license. :)18:21
broderSpamapS: no, i don't think it's that. smoser's bug report makes it sound like there's actually a race there18:22
smoserno18:22
smoserits not a race18:22
smoserits consistent18:22
smoser[ -w file ] says yes, attempt says no18:22
smoserand then again18:22
smoserand then both say yes18:23
broderoh, i see. [ -w ] returns yes when it's ro?18:23
smoseri suspect that what is happening is this:18:23
smoser a.) mount is read-only (at which point both say 'not writable')18:23
smoser b.) mountall invokes 'mount()' system call for remount,rw18:24
smoser c.) [ -w file ] says "YES", but attempts to actually write fail18:24
smoser d.) kernel finishes actually making filesystem rw18:24
smoser e.) [ -w file ] says yes, attempts to write succeed18:24
broderright. and my question is why are the paths that access() and open() take sufficiently different that (c) is even possible18:24
smoserwindow between b and d is very small, i'm only seeing it here because i'm using qcow compressed image that is freaking crazy slow read and write18:25
smoserbroder, well, cjwatson's comment was that 'access()' has always been 'a bit wonky'18:25
broderyeah, that just seems unfortunate and error-prone. even if we audit for things that depend on access() actually working, that doesn't solve the problem in the long term18:28
broderand it's just another thing we have to add to the list of "weird unix arcana that will bite you in the rear one day"18:29
smoseri recall having seen issues like this with nfs also18:30
broderi can accept network filesystems as being a special case18:30
brodermaybe the better solution would be to change bash to implement -r, -w, etc. using open directly18:32
brodersince i don't actually think people use access() that often from C18:32
smoserbroder, the issue with open is that actually has side affects18:34
smosereven if file exists, you would be updating ctime.18:35
broderthere's a O_NOATIME at least, but yeah, i guess you can't prevent it from affecting ctime18:36
smoserwell, and you'd actually be creating it18:37
smoserif it did not exist18:37
broderonly if you pass O_CREAT18:37
smoserbut if the file did not exist, how would you know if you could write to it using open unless you passed O_CREATE?18:38
smoseraccess() i think is supposed to say "yeah, you could potentially create that file"18:39
cjwatsonslangasek: I think we should probably kill it though I'm not certain18:43
cjwatsonaccess() from C is pretty common18:43
cjwatsonI think it's probably better to fix access(), I just don't know whether it's sanely possible18:44
SpamapSSomebody remind me.. a Breaks + Replaces will cause dist-upgrade to remove the broken/replaced package and install the new one, right?19:13
micahgSpamapS: it should and generally, breaks/replaces is versioned19:14
SpamapSindeed19:15
slangasekSpamapS: to be sure, it causes the broken/replaced package to be removed when upgrading or installing the breaking package; if the breaking package is not already going to be pulled in, having the breaks/replaces doesn't cause a dist-upgrade to pull it in19:25
SpamapSslangasek: right.. hm19:44
SpamapSslangasek: if I have a Provides does that force dist-upgrade's hand?19:44
slangasekSpamapS: nope19:59
infinitySpamapS: Provides doesn't imply a Conflict.  What are you actually trying to achieve?19:59
slangasekSpamapS: generally for that, you add a transitional package with the name of the old one19:59
slangasekor you make your metapackage depend on the new one or something19:59
slangaseksmoser: how reproducible is bug #833783?  this is going to take some iterating20:00
ubottuLaunchpad bug 833783 in initramfs-tools (Ubuntu Oneiric) "boot failure: can't open /root/dev/console: no such file" [High,Confirmed] https://launchpad.net/bugs/83378320:00
smoserslangasek, hm..20:00
smoserunfortunately, i dont really know.20:00
smoseri would have told you it was on the order of 1/3020:01
smoserbut the last set of tests, i believe that I saw a failure where the kernel rebooted itself.20:01
smoserie, as if i a watchdog kicked in.20:01
smoseri didn't think that i'd seen that behavior before20:01
smoserbut if that is happening, then we may be hitting it more than i thought, and i just didn't know it.20:02
smoseri know. that wasn't very helpful.20:02
slangaseksmoser: ok.  basically, my *suspicion* is that we're racing udev because the initramfs has so little to do that it gets to the bottom faster than udev can blink; but I'd like to be able to verify that20:02
smoserthat makes sense.20:03
slangaseksmoser: you could test this by adding [ -e /dev/console ] || udevadm settle to /usr/share/initramfs-tools/scripts/init-bottom/udev and testing20:04
smoseris /dev/console always the same major minor?20:04
slangasekif that works, it's probably the same as our other udevadm --exit bug20:04
slangasek(*probably*)20:04
smoseror does it depend on platform....20:04
slangasekI think it's always the same major/minor20:04
slangasekso yes, this could be hacked around with hard-coding20:04
smoserif its always 5,1, then just having that in /dev/ would fix this issue20:04
smoserright20:05
smoseri realize htat is a hack20:05
slangasekin fact, you'll see initramfs scripts have code for a mknod fallback already20:05
slangasekright at the top of init20:05
smoserok.20:05
smoserso we're hitting the bottom, calling udevadm --exit, before udev makes /dev/console20:06
slangasekI'm afraid I don't understand this bit of the kernel either, though... can we be sure that /dev/console is always there on the kernel side?20:06
slangaseki.e., would mknod be sufficient, or is it possible the kernel itself would throw errors?20:06
slangasekI'm to the point where I don't trust devices to really be there until udev tells me they are ;)20:06
smoseri'm not certain. but it would surely seem that /dev/console is pretty basic. the kernel has to printk to somewher,e and i always just assumed that was "dev/console"20:07
slangaseksmoser: but definitely a '[ -e /dev/console ] || udevadm settle' is the first thing to try20:07
slangasekoh sure, it's pretty basic20:07
slangasekbut everything's getting so fast now that we're racing every last bit of the kernel's init code, AFAICS20:07
smoserslangasek, https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/68283120:09
ubottuUbuntu bug 682831 in plymouth (Ubuntu Lucid) "lost console output early in boot" [Undecided,Triaged]20:09
smoserthats my prior experience with /dev/console, and it not always being there :)20:09
smoseroh, but wait, that was a plymouth issue20:09
slangaseksee! I'm not just paranoid :)20:09
smosernever mind that.20:10
slangasekah ;)20:10
superm1archive admin, can you please axe the libhdhomerun upload that i just sponsored?  Daviey raised a point that we didn't realize it was in debian and synced from there and we've got a bad delta in the debian/ stuff now for it20:10
infinitysuperm1: Sure.20:10
slangasekinfinity: too slow20:10
slangaseksuperm1: done20:10
superm1thanks slangasek20:10
infinity:P20:10
* ScottK is even more too slow.20:10
slangasek:)20:10
smoserslangasek, tell ya what.20:10
smoserif you can give me a diff of the file to change, then i'll attempt leave a script launching instances on CanoniStack all weekend with and without20:11
smoserand see if we see actual improvements20:11
slangaseksmoser: yeh, diff is in preparation now :)20:11
slangaseksmoser: so in general, would an initramfsless boot do you guys some good?20:13
smoserwe've been there20:13
smoserand came back20:13
slangasekwhyso?20:13
smoserwe dont need an initramfs really. and in lucid, we didn't have it.20:13
slangasekthe kernel package tooling needs help for supporting the initramfsless case20:13
smoserit was a real benefit in it was less things to manage on ec2, where you had to upload a kernel and a ramdisk separately20:13
slangasekbut that's solvable20:14
slangasekand helps with several different problems in parallel20:14
smoserbut when we moved to using pv-grub, which allowed us kenrel upgrades!!!! i never bothered to fight update-initramfs and the kernel hooks and such to stay a different path.20:14
smoserso we got our initramfs back.20:14
slangasekthe other Good fix for the problems you guys've been seeing in the initramfs is to get event-based initramfs... too bad we didn't make it there for this cycle :/20:14
smoserand then, i built a feature or 2 into our cloud initramfs that i'm not likely to want to give up.20:15
slangasekhah20:15
SpamapSensemble has been renamed to juju20:15
SpamapSto answer the question late20:15
=== m4n1sh_ is now known as m4n1sh
SpamapSso we want the bin package to be called juju.. but anybody who has had ensemble up to now we want to get juju to replace it.20:15
slangasekSpamapS: right, ensemble dummy package Depends: juju package Replaces:/Breaks: real version of ensemble package is the canonical solution20:16
SpamapSslangasek: ty :)20:17
smoserslangasek, http://ubuntu-smoser.blogspot.com/2011/07/getting-larger-root-volume-on-cluster.html is a feature that is very useful.20:17
slangasekSpamapS: or, if ensemble would always be installed as a dependency of some other leaf package that would be installed, you can just switch the dependency and dispense with the dummy package... but I suspect 'ensemble' will be in the name of the relevant top-level packages :)20:17
smosermuch less so on ec2, but now on openstack all instances will take that path.20:17
slangaseksmoser: heh, too bad.  I guess we should regroup on the event-based initramfs question for next cycle then20:18
slangasekapw: btw, I think my black screen between grub and plymouth is an initramfs-specific issue... I can reproduce it on my T60, and should have a cryptsetup-less test soon for comparison.  I think either something's missing from the initramfs, or we're again racing udev somehow20:19
smoserslangasek, is there a bug open that we consider *the* bug for "udev --exit does not flush queue" ?20:21
smoserit seems its coming up more and more often, and i think it is the root of many bugs, but i didn't know if there was one bug that those others should actually be duped to20:22
slangaseksmoser: bug #818177 is the one I know about20:22
ubottuLaunchpad bug 818177 in udev (Ubuntu Oneiric) "HP DL380G5 root disk mounted read-only on boot and boot fails" [High,Confirmed] https://launchpad.net/bugs/81817720:22
slangaseksmoser: I wouldn't start duping bugs to it until we actually prove that's what's happening though20:22
smoseri thought it was known fact that it does not flush queue20:23
slangaseknot known to me20:24
slangasekbut I'm not a udev expert, either :/20:24
slangaseksmoser: patch posted: https://bugs.launchpad.net/ubuntu/oneiric/+source/udev/+bug/833783/+attachment/2449493/+files/udev-must-provide-console-833783.patch20:24
ubottuUbuntu bug 833783 in udev (Ubuntu Oneiric) "boot failure: can't open /root/dev/console: no such file" [High,Confirmed]20:24
cjwatsonI think it's true that it doesn't flush the queue, but nobody worried about it before because udev in the real root was meant to catch up all events20:28
cjwatsonbut /dev/console is used between udevadm control --exit and udev starting in the real root ...20:28
slangasekindeed20:28
slangasekand previously, udev happened to always get around to creating /dev/console before being stopped20:28
cjwatsonI don't think it would be desperately hard to fix in udev for somebody who had a spare couple of hours20:29
cjwatsonsmoser: so, speaking of Xen, today I've found and am fixing three separate bugs all of which were independently installation blockers for a friend's colo hosting company that uses Xen guests20:30
cjwatsonsmoser: I'm kind of interested that none of those bugs appeared to be biting us :-)20:30
cjwatsonbug 720558, bug 857548, and bug 85766220:30
ubottuLaunchpad bug 720558 in grub (Ubuntu Natty) "Ubuntu 10.04 currently requires groot= workaround with pvgrub" [High,Triaged] https://launchpad.net/bugs/72055820:30
ubottuLaunchpad bug 857548 in grub-installer (Ubuntu Oneiric) "no longer possible to select GRUB Legacy by preseeding" [High,Triaged] https://launchpad.net/bugs/85754820:30
ubottuLaunchpad bug 857662 in hw-detect (Ubuntu Oneiric) "Should xenbus_probe_frontend be built-in?" [High,Triaged] https://launchpad.net/bugs/85766220:30
cjwatsonsmoser: do you have workarounds for any of those that I don't know about, or is it just that your boot setup is sufficiently different that you dodge them?20:31
cjwatsonI guess you're using preinstalled AMIs ...20:31
cjwatsonkind of surprised that xen-netfront autoloading isn't a problem though20:31
cjwatsonunless you use -virtual I guess20:32
smoser720558 is worked around by grub-legacy-ec220:32
smoser857548 is worked around by the presense of grub-legacy-ec2 (as it does not conflict with grub2)20:32
smoser857662 we dont hit that in our installs because we dont install with installer20:33
smoserthat said, i do know that installation as a guest under xen has been broken20:33
smoseri believe that xen-netfront autoloading is a problem...i think there was a discussion recently on ubuntu-server mailing list to that reguard.20:34
cjwatsonsmoser: conflicts aren't relevant to 857548, but not using d-i would be :-)20:35
smoserright.20:35
cjwatsonsmoser: so I wonder if grub-legacy-ec2 can go away once I've fixed that bug in grub?  or is there more?20:36
cjwatsonI'm going to work around xen-*front autoloading in hw-detect20:36
smoserthe only real reason for grub-legacy-ec2 is to manage /boot/grub/menu.lst and install along side grub220:36
cjwatsonit'll work as long as you're using the -virtual flavour20:36
cjwatson(for the installed system, since then we don't need userspace tweaks too)20:37
cjwatsoncan you remind me why you need grub2 installed?20:37
smoserbecause those images work with "normal bios booting" via grub2 and pv-grub booting via the managed /boot/grub/menu.lst20:38
cjwatsonoh, dual running20:38
cjwatsonok20:38
smoserso as soon as you get me a pv-grub2, *then* we can ditch the grub-legacy-ec220:38
smoserand i'll be happy20:38
smoser:)20:38
cjwatsonyeah, that's a *little* further off20:38
cjwatsonowing to no time this cycle20:38
smoseroh comeon... its not like have anything else to work on20:38
cjwatsonheh20:40
Davieycjwatson: Is it too late to change the d-i background colour slightly?20:45
* Daviey jests.20:46
cjwatsonahahabonk20:47
slangasekblah, why is launchpad marking bugs like 798509 confirmed?21:13
micahg slangasek: they affect multiple people21:14
charlie-tcanewest thing. any comment or duplicate lets launchpad automatically confirm the bug21:14
slangasekmicahg: "like 798509" is the key expression there :)21:14
slangasekit's a duplicate of a fix-released bug21:14
charlie-tcaIt really fails on most, since nothing but a comment by anyone will cause it to go "confirmed"21:15
micahgslangasek: that should be a bug21:15
ScottKsuperm1: Is the hdhomerun-config-gui upload you just sponsored bug fix only?21:16
micahgslangasek: do you want to file the report or should I ?21:16
slangasekmicahg: filing21:16
slangasekmicahg: bug #85777721:17
ubottuLaunchpad bug 857777 in Launchpad itself "launchpad janitor generating noise by 'confirm'ing duplicate bugs" [Undecided,New] https://launchpad.net/bugs/85777721:17
micahgslangasek: thanks21:18
ScottKNice.  Because it didn't send enough bugmail already, I guess.21:18
charlie-tcaIt is kind of frustrating to see a bug report, someone asks a question on it, and leaves it in "New", and launchpad confirms it because of the comment21:20
slangasekpitti: the fix for bug #854329 is staged in bzr for gdm and lightdm; any objections to me uploading it?  (I can't upload the plymouth side until those are uploaded)21:22
ubottuLaunchpad bug 854329 in xdm (Ubuntu Oneiric) "race condition on shutdown with more than one DM installed" [Low,Triaged] https://launchpad.net/bugs/85432921:22
micahgslangasek: FYI, he's on holiday today21:23
slangasekoh, well, that makes it easy then... no one around to tell me no ;)21:24
micahgheh21:24
slangasekScottK: do you know if anyone's interested in working on the kdm part of bug #854329?21:52
ubottuLaunchpad bug 854329 in xdm (Ubuntu Oneiric) "race condition on shutdown with more than one DM installed" [Low,Triaged] https://launchpad.net/bugs/85432921:52
ScottKslangasek: No.  If it's cargo culting something from some other DM, I can probably manage, but maybe debfx.22:02
slangasekScottK: it's pretty cargo-cult, yeah :)22:07
superm1ScottK, yes, silicon dust hasn't added new features in ages22:14
=== kentb is now known as kentb-out
ScottKsuperm1: Accepted.23:08
ScottKOK.  Taking a look.23:16
ScottKAmazing how cleanly gdm.upstart and kdm.upstart diff against each other and yet they have completely different authors listed.23:31
mr_pouitArchive admins: I've synced garcon, and I guess it sits in unapproved. I can't link to the bug report though, so if needed, the FFe is Bug #857718. Thanks.23:32
ubottuLaunchpad bug 857718 in garcon (Ubuntu) "[FFe] garcon 0.1.9" [Undecided,Confirmed] https://launchpad.net/bugs/85771823:32
slangasekScottK: there seems to have been some confusion about the meaning of the field; I'm pretty sure the gdm upstart job wasn't written by GDM upstream...23:34
slangasekmr_pouit: accepted23:34
ScottKslangasek: Seems sufficiently cargo cultable.  I got it.23:34
jbichaooh, dpkg 1.16.1 automatically unapplies patches at the end of building23:35
slangasekScottK: yay :)23:35
mr_pouitslangasek: thanks!23:35
jbichathat should help clean up the .pc mess, right?23:35
ScottKNice.  Found some additional changes to steal.23:44
ScottKjbicha: Only if they weren't applied at the start.23:44
* SpamapS wonders why display managers don't have one upstart job that calls the currently selected default....23:47
slangasekSpamapS: because the way you call the currently selected default varies significantly23:49
SpamapSof course it does, that makes perfect sense, every DM is a special snowflake23:50
slangasekSpamapS: feel free to impose a standard invocation on all the upstreams in your copious free time :)23:50
SpamapSslangasek: indeed, I will have to go in search of more round tuits.23:51
ScottKSpamapS: FYI, just for added fun, kdm upstream is widely viewed as one of the most socially ept KDE developers ....23:54
ScottKslangasek: I pushed it to kde-workspace bzr.  Need to finish looking at patches to cherrypick from upstream before uploading.23:55
slangasekScottK: spiff, thanks23:56
ScottKbarry: Accepted.23:56
barryScottK: awesome, thanks.  i probably won't get to retrying omniorb until tomorrow23:57

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