/srv/irclogs.ubuntu.com/2013/06/07/#ubuntu-devel.txt

xnoxsmoser: yes?!00:05
slangasekinfinity: it hasn't been in the same publisher cycle; if you want to smack it again with change-overrides, go ahead00:15
=== _salem is now known as salem_
=== fginther|afk is now known as fginther
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
pittiGood morning04:37
pittiwgrant: hey William, how are you?04:52
pittiwgrant: who should I ask to enable saucy translations in launchpad?04:53
wgrantHm, we didn't already do that?04:53
wgrantMaybe we didn't.04:54
wgrantLet's see if I can remember how.04:54
* infinity wonders why that doesn't happen as an artifact of opening a new series.04:56
wgrantIt's very early on NRCP04:56
pittiwgrant: https://translations.launchpad.net/ubuntu/saucy/+language-packs is empty04:58
infinitywgrant: Yeah, odd that we missed it.  But that's why checklists are worse than something just doing the right thing.04:58
pittiwgrant: but I got a mail from some contributor who wants to start translating saucy in LP04:58
StevenKWe're not building langpacks, because that happens later, I think04:59
wgrantpitti: It's not done, yeah05:00
wgrantAnd we can't really test it beforehand like we normally do05:00
wgrantSo let's live dangerously :)05:00
pittiwell, with a rolling release thingy, as well as for people who start translating in LP it would actually be nice to have langpacks early as well, but opening saucy translations is indeed a bit more important05:00
wgrantThe plan was to have langpacks from the start, AIUI, but that didn't actually happen05:01
infinitymlankhorst: So... Whoever NEWed all your lts-raring stack did so to universe, and thus you missed out on noticing that xorg-server-lts-raring has a build-dep on libaudit-dev that needs to be dropped (it's in universe in precise, and we're not likely to promote it, since the condition for promoting it in raring was a bunch of code cleanups)05:03
infinitymlankhorst: I suspect they NEWed everything to universe, now I get to go hunt them down and clean up.  Unless you have a quick list of all the source packages involved, so I can mindlessly promote the lot? :P05:04
versableHey, a package won't build for me in lp. Package "webkitgtk-3.0 missing". libgtk-3-dev is in the build-depends though05:15
versablelog: https://launchpadlibrarian.net/141838690/buildlog_ubuntu-precise-i386.etube_0.2-0~2~precise1_FAILEDTOBUILD.txt.gz05:16
versablebzr code: http://bazaar.launchpad.net/~versable/elementary-community/eTube/files05:16
versableIt builds fine lokally05:16
versablelocal*05:17
infinityversable: Missing build-dep on libwebkitgtk-dev, I'd assume.05:17
infinityOh, wait, wrong webkit.05:17
infinitylibwebkitgtk-3.0-dev05:18
versableinfinity: Right, that's probably it. Thanks.05:18
dholbachgood morning06:19
mlankhorstinfinity: feel free to kill the audit dependency for now07:05
mlankhorstif it still builds07:05
mlankhorstinfinity: xorg-pkg-tools has the list07:05
mlankhorstsec let me generate it07:06
infinitymlankhorst: I was thinking that killing the audit dep was something you'd have to do in your fancy scripts, so it doesn't come back.07:06
mlankhorstsure I'll do that too07:07
infinitymlankhorst: But yeah, let me test-build quickly here.07:08
sarnoldwhy kill the audit dep? I thought audit had been promoted to main?07:08
mlankhorstnot in precise yet07:08
sarnoldah07:08
infinitysarnold: And the one in main won't ever be promoted, since it needs a ton of work to be acceptable.07:09
infinitys/main/precise/07:09
infinityBrain.  Hurting.  Long day.07:09
lifelessinfinity: isn't it 0800 for you? Or have you moved. Again.07:09
kirui'm a beginner,like to contribute to ubuntu please help07:09
infinitylifeless: It's 1am.07:10
infinitylifeless: It'll be 8am for me in a month when I'm in the UK, close enough. :P07:10
mlankhorstbut I've added /libaudit-dev/d for xorg-pkg-tools, next version should upload correctly07:10
lifeless:)07:10
infinitymlankhorst: Oh, hrm.  Dropping the build-dep isn't enough.07:10
infinitymlankhorst: Oh, wait, I remember adding this.  It was also adding some selinux thing.07:11
* infinity checks the changelog.07:11
infinityhttp://launchpadlibrarian.net/130794589/xorg-server_2%3A1.13.2-0ubuntu1_2%3A1.13.2-0ubuntu2.diff.gz07:11
infinitymlankhorst: Needs to be the inverse of that.07:11
infinitymlankhorst: Are your scripts smart enough to mangle 'selinux = --disable-xselinux' in debian/rules?07:12
mlankhorstit's sed, i can just do it quickly07:12
* infinity rebuilds again.07:13
mlankhorst-e "s/--enable-xselinux/--disable-xselinux/" \07:13
infinityShould do.  It passed confugre with that, at least.07:14
* infinity waits for it to, like, build.07:14
mlankhorstok I'll bbl, weather is really nice so it's a crime not to bike :)07:19
infinitymlankhorst: Heh.  Enjoy.  I'll just upload this as precise2, and if you ever have to respin, your scripts will DTRT?07:20
infinitymlankhorst: http://paste.ubuntu.com/5741156/ <-- My debdiff, so you can check and see if your script produces the same change.07:22
smbinfinity, Hmmm... is this just broken by my reading? [ubuntu/quantal-proposed] linux_3.5.0-34.55_amd64.tar.gz - (Accepted)08:05
infinitysmb: You don't pay attention to -changes much, if that's the first time you've noticed that. :)08:05
infinitysmb: That's the uefi custom upload.08:05
smbinfinity, I probably do not do that much08:05
smbIt required this to be in a smaller quantity of updates for me to notice. :-P08:06
smbThanks for the explanation08:07
pittixnox: wrt. cryptsetup uninstall/plymouth in initramfs: is it possible that this is related to cryptswap?08:35
pittixnox: I use ecryptfs, so ubiquity set up a cryptswap device and thus kept the full cryptsetup package08:35
pittixnox: but (1) I doubt whether we really need swap that early (in intramfs), and (2) at least in the past we didn't set up cryptswap for non-ecryptfs; perhaps we do now?08:36
pittixnox: (I haven't checked anythign in ubiquity, it just came to my mind)08:36
xnoxpitti: correct. ecryptfs does pull in cryptsetup for encrypted swap. But default unecrypted (neither full, nor homedir) install shouldn't pull in cryptsetup.08:36
xnoxecryptfs does encrypted swap for a few releases now (not sure when it started)08:37
pittiyes, and that makes sense; I just wonder whether we need to set up/mount swap in initramfs already08:38
pittixnox: but that's actually unrelated; I guess (2) is the more interesting question in terms of initramfs size with all defaults08:38
xnoxwe shouldn't, indeed.08:38
xnoxI'd like to still find out why/how we are regressed, instead of simply implementing conditional logic (do not include ecryptfs in initramfs, unless '/' or '/usr' are encrypted)08:39
pittiyes, sure; ecryptfs and cryptswap just came to my mind as possible things which might have changed08:40
=== doko_ is now known as doko
xnox20130521 saucy daily correctly removes cryptsetup & ecryptfs-tools in a default install, whilst 20130523 and later do not.09:34
xnoxpitti: so it seems like cryptsetup via ecryptfs-utils via adduser moved from "d-i-requirements" to "minimal" on 20130521, while on 20130520 it was not.09:45
xnoxand indeed in raring, cryptsetup was not in Task: minimal.09:45
pittieek09:45
pittiindeed, only cryptsetup-bin is supposed to be installed by default09:45
pittithat's why we split it out in the first place09:45
pittixnox: dropping adduser's ecryptfs-utils recommends to suggests?09:46
xnoxpitti: but it was there in raring as well, so how come it _now_ moved up?09:46
pittior ecryptfs-utils ought to recommend cryptsetup-bin only (but I'm not sure whether that's sufficient)09:47
pittiperhaps that changed09:47
xnoxbut versions of adduser, ecryptfs-utils nor crypsetup have not changed since raring yet.09:52
pittihm; I don't see how cryptsetup would not have been in minimal in raring then09:53
xnoxhttp://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu/saucy/daily-live-20130520.log09:54
xnoxvs09:54
xnoxhttp://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu/saucy/daily-live-20130521.log09:54
xnoxResolving minimal dependencies ...! Promoted ecryptfs-utils from d-i-requirements to minimal to satisfy adduser09:54
pittibut indeed it wasn't09:54
om26eri have a local repository, how can I increase its priority ?09:55
om26ernot sure what to put infront of "pin:" in the .pref file09:56
xnoxom26er: https://help.ubuntu.com/community/PinningHowto but please note if the packages have identical version number, the "first" repository wins.09:58
wgrantpitti: saucy's translations are copied and imports are happening now09:59
pittiwgrant: splendid, thank yoU!09:59
om26erxnox, and if its a separate repo in /etc/apt/sources.list.d/ ?09:59
xnoxom26er: check with $ apt-policy package what "won"10:00
pittixnox: we didn't rebuild d-i or anythign like that on that day -- perhaps on that day someone processed priority-mismatches?10:00
om26erxnox, here http://paste.ubuntu.com/5741445/ my repo is indeed getting higher priority, but I want to set it to 600 or 1000 just to be sure, but seems my pref file is broken ?10:03
xnoxpitti: should I upload adduser lowering ecryptfs-utils from recommends -> suggests?10:16
cjwatsonpitti,xnox: https://launchpad.net/ubuntu/saucy/i386/ecryptfs-utils says no10:16
cjwatsonIndeed there's a bunch of priority-mismatches I'd been deliberately not processing until I had a chance to think about it :)10:16
xnoxcjwatson: any idea how ecryptfs-utils got into minimal?10:16
xnoxbut wasn't before...10:17
pittithe more interesting question is how it was not in minimal in raring yet?10:17
cjwatsonA Recommends from adduser would be sufficient10:17
xnoxthat was also present in raring.10:17
cjwatsonone moment10:18
xnoxi see that it moved into minimal on 20130521 http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu/saucy/daily-live-20130521.log10:18
cjwatsonadduser wasn't in minimal in raring for some reason10:18
cjwatsonAh, it was in required, which is really where it belongs IMO10:19
cjwatsonBut required doesn't follow Recommends10:19
cjwatsonSo I guess something in required dropped a Depends: adduser10:19
cjwatsonWell, I dunno, adduser in minimal vs. required is OK actually10:20
pittixnox: my gut feeling is that adduser should only suggest ecryptfs-utils10:20
cjwatsonTBH this is basically that the Recommends was incorrectly not noticed in raring10:20
cjwatsonSo I'd say adduser should be left where it is and drop the Recommends to Suggests10:20
xnoxack. will upload.10:22
cjwatson(required doesn't process Recommends because it corresponds to debootstrap and debootstrap doesn't; but this does mean that there are some corner cases where Recommends kind of get lost)10:22
pitti xnox: спасибо!10:23
KoterpillarWhere do I find documentation (ideally, examples) for implementing a host for Application Indicators? Not an indicator itself, but something that would show them?10:27
xnoxapw: i think you can still blame pitti and systemd for bootspeed regression, as it was udev that dropped adduser dependency when moving from udev->systemd source package thus triggering an unfortunate series of seed changes and promoting cryptsetup into minimal.10:30
xnox=)10:30
pittifun -- making things bigger by *dropping* dependencies..10:31
pittiTGIF!10:31
apwxnox, heh :)  pitti TGFT10:36
apwxnox, fixable without adding spagetti to the seeds ?10:37
xnoxapw: yeah, uploaded adduser that moves ecryptfs-utils from recommends to suggests. But it's kind of hilarious that adduser is now not required =)10:37
apwheh yeah, it is a bit of a scarey thought all told10:39
pittiwell, there's always useradd, for really mini-minimal systems10:39
apwso i shall look at the new boot charts on monday, fingers cross10:39
pittiadduser is perl10:39
pitti(perl-base only, so you can't get rid of that anyway, but still)10:40
rbasakpitti: got time to talk about locales and postgres?10:41
pittirbasak: sure (didn't I talk enough yet on devel@? :-) )10:41
* xnox pretends to speak only ASCII based languages10:41
pittirbasak: that's where apw's spaghetti come in10:41
rbasakpitti: I have a really long reply for you too. I was hoping to shorten it by talking on here :)10:41
rbasakpitti: I think my objection lies in postgres' postinst behaviour10:42
rbasakpitti: that if the *user* locale is bad, then the postinst's behaviour changes10:42
pittirbasak: that it fails in an invalid locale? I can change that (as I said in my mail)10:42
rbasakpitti: I'm trying to verify this. I'd like the postinst to ignore the user's locale (ie. the environment) and use /etc/default/locale instead, if it is there.10:42
pittii.e . go from "fails to install" to "installs, but doesn't create any cluster"10:42
rbasakpitti: I'm not sure that it does actually fail. I think it already has that behaviour. But I'm struggling to fire up a cloud instance to test at this moment.10:43
pittirbasak: you also need to check at least /etc/environment then, and quite possibly /etc/profile, /etc/profile.d/, and whereever else admins might drop locale definitions in10:43
rbasakpitti: I'd like it to install *and* create a cluster by using /etc/default/locale.10:43
pittirbasak: no, the package installation does fail if pg_createcluster fails10:43
rbasakpitti: the user's locale shouldn't matter.10:43
rbasakIt's confusingly inconsistent if the way a package is set up depends on the user's environment at the time of the dpkg run10:44
pittirbasak: well, it's the locale in a root context; the problem is that in that pathological case ssh + sudo carry the remote locale all the way into a root context where it is totally invalid10:44
rbasakEven without ssh, if the user sets a valid locale in ~/.profile or ~/.bashrc or whatever and uses sudo, then it'll work but there's still an inconsistency10:45
pittirbasak: I share the feeling about inconsistency; I just don't know a good answer to it10:45
rbasakWhat's wrong with using /etc/default/locale if it exists, falling back to /etc/environment?10:45
pittirbasak: in the bug report case there is no /etc/default/locale nor /etc/environment10:45
rbasakThen that solves the ssh carry through an invalid locale problem too10:45
pittirbasak: the problem is that nothing specifies that locales must be defined in those two filese only10:46
rbasakpitti: I think the bug would still exist if there is; I'll verify.10:46
rbasakpitti: then in that case only, default to C.UTF-8 but prompt with debconf?10:46
pittirbasak: in my experiments, if /etc/default/locale actually does set a locale, that overwrites the one ssh is passing on10:46
rbasakIn the majority of cases, the installer would have fixed it in /etc/environment (old) or /etc/default/locale (new), and there will be no prompt.10:46
rbasakFor users with unusual systems, they'll be asked.10:47
pittirbasak: I really want to avoid debconf (for various reasons, see mail); using C.UTF-8 would be acceptable then10:47
rbasakI'd be happy with C.UTF-8 with no prompting.10:47
rbasakOK10:47
rbasakDoes that mean you agree with me? No using the environment at all; use /etc/default/locale, fall back to /etc/environment; fall back to C.UTF-8.10:47
pittithen, what do we do about those people who actually want C (I got several reports there)10:48
pittirbasak: no, as I said these are not the only files where you can set the locale10:48
pittias the primary definition of "locale" is in terms of environment variables, there are a gazillion places to define them10:48
rbasakHow about an extra fall back to the environment but iff /etc/default/locale and /etc/environment doesn't set the locale?10:49
rbasakI'm trying to pin down using the "system" locale here, rather than the user locale. Only the user locale is available from the environment.10:49
pittirbasak: ^ I don't know what you mean by this10:49
pittii. e. use /e/d/locale, if that doesn't define anythign, use /e/environment, if that doesn't define anything use the environment?10:50
rbasakOr how about a debconf prompt with low priority for those who really need an override?10:50
pittithat's exactly what leads to the curretn bug10:50
pittithose who really need to change it can just specify it at pg_createcluster10:50
pittia debconf prompt is ridiculously expensive (given translations etc.) for such a small corner case IMHO10:50
rbasakSo fall back to C.UTF-8 then.10:51
pittirbasak: I'd actually fall back to C10:51
rbasakOK, fine.10:51
rbasakI just want /etc/default/locale used in preference to the user's environment.10:51
pittiif a server does not define any system locale, then presumably the admin actually means it; not sure?10:51
rbasakI think that'll fix the bug.10:51
rbasakI understand that you don't think it will.10:51
rbasakI will verify.10:51
pittirbasak: but.. there IS no /e/d/locale for the bug you reported/commented on10:51
pittithe bug precisely happens on those systems which don't define a system locale10:52
dokoRiddell, how stable/good is kde in saucy (wanting to do a test rebuild)10:52
dokoseb128, didrocks , how stable/good is gtk/gnome in saucy (wanting to do a test rebuild)10:52
Riddelldoko: pretty good, I just uploaded all of KDE SC 4.10.4 which is due to start compiling right about now10:53
rbasakpitti: I'm not sure that's the case. I believe the system I reproduced on did have /etc/default/locale set.10:53
pittirbasak: so what this would need is to find a way to tell whether a defined locale from the env that isn't in /e/d/l nor in /e/env comes from someplace else in the system or from sudo10:53
seb128doko, it should be good/stable enough to have a rebuild, we are on the stable serie for both and have no update planned soon10:53
rbasakpitti: I can't seem to reproduce right at this moment, because I can't get an available instance on a private cloud I have access to.10:53
dokoRiddell, well, if it starts compiling, then it's still in proposed?10:53
Riddelldoko: yes10:53
dokoso *not* ready10:53
pittirbasak: FYI, I use "run-adt-test -sl" for those; they are cloud-image based, and perfect for quick throwaway VMs10:54
=== Guest86601 is now known as zumbi
pitti(and all local)10:54
=== zumbi is now known as Guest22269
rbasakPostgres is a very special case here.10:56
rbasakNormally a locale setting doesn't cause any persistent changes to the system10:56
rbasakI don't think it's safe for the environment to specify a locale for this purpose.10:56
rbasakWe should define where a system locale is defined, and use that10:56
rbasakOr use C, and require people to override template1 when they need to.10:57
rbasakOr use the locale of the user who runs createdb when he runs createdb to do it for him.10:57
pitti^ that already happens, I think10:57
rbasakIn that case, why does the postinst need to use anything but C?10:58
=== Guest22269 is now known as zumbi_
pittiso perhaps a middle ground would be for the postinst to clean up its entire locale environment (LANG, LANGUAGE, LC_*), then source /etc/environment, then source /etc/default/locale, and then run pg_createcluster10:58
pittithat'll break use cases where the admin defines a system locale in a different place, but these seem rather small to me (we have to compromise somewhere)10:59
cjwatsonYou can't source /etc/environment safely.  It may look mostly like a shell file, but it has a formally different syntax; it's a pam_env configuration file.10:59
rbasakThat works for me10:59
pitticjwatson: ah, too bad10:59
cjwatsonUnfortunately pam_getenv is broken, or that would be the right answer.11:00
cjwatsonI think the above may be true for /etc/default/locale too, technically, although it's in practice safer since its key set is more restricted11:00
pittiI've seen plenty of places which source /e/d/l, though11:01
cjwatsonMight be worth seeing how hard it is to fix pam_getenv ...11:01
pitti/etc/init/mountall.conf11:01
cjwatsonI wouldn't get too upset about sourcing /etc/default/locale11:01
cjwatsonIt might even be formally permitted, I forget11:01
pittiso mountall will fail if sourcing /etc/default/locale fails11:01
pittiI thought that was one of the reasons why it got moved out of /e/env11:02
cjwatsonBut the locale hasn't been written to /etc/environment for years11:02
rbasakWould it be OK to attempt to source /etc/environment, and ignore failures? Or is that unsafe too?11:02
cjwatsonYeah, could be11:02
cjwatsonYou have to go to considerable lengths to avoid that killing the calling shell11:02
pitticjwatson: right, but I still think it's a legitimate place for defining it11:02
cjwatson. /etc/environment || true  <- not sufficient11:02
pittinot wanting to be too selfish, but even my own server has that, and that was a debian install from a few years back11:02
rbasakI only became aware of /etc/default/locale recently, when something broke. I've been using /etc/environment for a long time. But note that something broke (can't remember what).11:03
cjwatsonpitti: pam_getenv was meant to be the safe answer to this.  I'm not sure how long it's been broken for11:03
pittiprobably something like $(source /etc/environment  && locale |grep LC_CTYPE || true)11:04
cjwatsonFailing that, I guess you could source in a subshell and pass out the answers you care about, or something11:04
cjwatsonYeah11:04
cjwatsonBut . not source11:04
cjwatson(source is a bashism)11:04
pittiand with an actually correct || true'ing (not applying that to grep), etc., but something along that lines11:04
rbasakHave we agreed with this as a solution then?11:05
rbasakI still need to check that /etc/default/locale is actually set on the use case that generated the maas bug.11:06
rbasakBut I think it's reasonable to demand that it is set, even if the ssh session has a broken locale11:06
rbasakThough with pitti's solution, it'd use C without a system locale defined, right?11:07
pittirbasak: well, in the cases where it isn't set, it would use C then11:07
pittirbasak: right11:07
rbasakGreat11:07
pittithat still leaves the broken locale for everything else, of course11:07
rbasakRight. I need to track down why Julian didn't get the cloud-init warning. Perhaps that's not the final solution but it should have worked for him.11:08
rbasakPerhaps he wasn't using a cloud instance, thinking about it.11:08
rbasakSo no cloud-init.11:08
rbasakI'll track that down with him.11:08
rbasakFor other things, the warnings about the locale being broken are fine, I think. At least no other functionality other than displayed messages are broken, AFAIK.11:09
mlankhorstinfinity: yeah it will be fine11:12
mlankhorstthanks11:12
pittirbasak: I updated bug 969462 with a summary11:14
ubottubug 969462 in postgresql-common (Ubuntu) "fails to start after install if invalid locale is set" [Low,In progress] https://launchpad.net/bugs/96946211:14
rbasakpitti: thank you! And for sticking it out with me on this.11:14
pittirbasak: heh, you're welcome; locales are messy :/11:15
pittirbasak: oh, actually, package installation does not fail in that case any more; that got changed a while ago11:16
pittisorry about that (but you wanted that behaviour anyway)11:17
rbasakRight, OK, thanks. But the maas postinst will still fail without this new behaviour, right?11:17
pittithere still wouldn't be a DB cluster to talk to, yes11:17
cjwatsondidrocks: Did you notice that a few bits of today's autolanding are stuck in -proposed because python-ubuntu-platform-api and uoa-integration-tests don't exist?11:20
* xnox tried to set C.UTF-8 locale & purge langpacks from my server. I'm still stuck with en_GB.utf8, en_US and en_US.iso88591 in locale -a output.11:21
didrockscjwatson: ah, I was waiting for still 30 minutes to see if things are wrong (now that all main promotion are done)11:21
didrockscjwatson: uoa-integration-tests is in NEW11:21
didrockspart of my review list11:21
cjwatsonOh, it is?  Ah, I missed it11:21
didrockspython-ubuntu-platform-api? I need to look at it11:21
didrockscjwatson: does the migration tool tells you about Main/Universe as well?11:22
cjwatsonNo11:22
didrocksok, as the migration is quite complex, I hoped I didn't miss anything11:22
didrocksone sec for python-ubuntu-platform-api11:22
didrockshope*11:22
pittioh, I thought we were moving away from python11:23
pittiah, for tests?11:23
didrockspitti: probably for those11:23
=== schmidtm_ is now known as schmidtm
didrockscjwatson: argh ok, autopilot-touch11:24
cjwatsonRight11:25
pittididrocks: btw, this was a nice read! https://launchpad.net/ubuntu/+source/autopilot-gtk/1.3daily13.06.05-0ubuntu111:26
didrockspitti: heh, glad you like it :)11:26
pittididrocks: does uploading the package auto-close the upstream bugs, OOI?11:26
didrocksit's matching any bugs related to the commit if there are, but keep the commit message (there is a list of commit message and a tag to not display some though)11:26
didrockspitti: no, long debate, nobody agrees, even between the different upstreams11:27
pittididrocks: autopilot-gtk doesn't have any ubuntu bugs, but a lot of upstream ones which were addressed by that11:27
didrocksok, for autopilot, let's do a manual upload removing the dep, we don't use autopilot-touch in the distro anyway11:28
didrocks(downgrading to suggests)11:28
* cjwatson clears the broken lplib cache that'd broken component-mismatches11:30
=== MacSlow is now known as MacSlow|lunch
didrockscjwatson: for daily release, I'm using a separate cache per process11:31
didrocksonly way to not have this issue11:32
didrocks(that I found)11:32
cjwatsonI'm using separate caches for a lot of things but not quite everything :-/11:32
wgrantI thought that fix was SRUed recently.11:33
cjwatsonI don't see it in python-launchpadlib/+changelog11:34
cjwatsonI think I asked for it ...11:34
didrockscjwatson: it's in lars.restful IIRC11:34
cjwatsonoh, python-lazr.restfulclient11:35
wgrantlazr.restfulclient probably11:35
cjwatsonApparently not to precise though11:35
wgrantAh11:35
cjwatsonbug 45941811:36
ubottubug 459418 in lazr.restfulclient (Ubuntu Precise) "Cache is not safe for concurrent use (by processes or threads)" [High,In progress] https://launchpad.net/bugs/45941811:36
cjwatsoncyphermox: ^- are you still planning on uploading that to precise?  it's been a few months11:36
cjwatsonand you could help make our archive reports more robust :)11:37
didrocksand less emails because of the script being broken \o/11:37
rbasakAny objections if I fix https://wiki.ubuntu.com/StableReleaseUpdates#Procedure? The "If you can't upload" section looks like it's got lost at the end of a bullet point; I think it needs to be clearer since people who can't upload may just assume that they can't do anything.11:43
cjwatsonrbasak: Go for it11:45
cjwatsonI agree that wants to be out a level11:45
rbasakDone. Sorry, just realised after I hit submit that I left the changelog blank :-/11:48
cjwatson*shrug*11:53
seb128cjwatson, hey, is there a component mismatch report for packages in proposed?11:56
cjwatsonseb128: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.txt11:56
cjwatson(thanks to Ursinha)11:56
seb128cjwatson, ah, nice, thanks11:56
cjwatsonit's an hour or two out of date for reasons discussed above - should update at the next publisher cycle11:57
seb128k11:57
=== cking_ is now known as cking
=== _salem is now known as salem_
Yud_ZrocIs there a compiling guide for ubuntu?12:20
=== MacSlow|lunch is now known as MacSlow
didrockscjwatson: thanks for the pocketsphinx upload :) I asked sil2100 to disable the powerpc tests and he was working on that this morning12:33
didrockssil2100: stop, not needed anymore :)12:33
sil2100Ah, ok ;)12:34
sil2100Well, it was just a quick fix anyway12:34
cjwatsonHeh, yeah, was just trying to clear a bit of component-mismatches12:35
cjwatsonAnd the sight of python-support offends me :)12:35
didrockscjwatson: does the migration to the main release pocket still don't retain the components in main?12:35
didrocksahah :)12:36
cjwatsonI don't understand the question12:36
didrocks(I'm seeing the scopes in universe, I'm sure I NEWed them in main)12:36
didrockslike https://launchpad.net/ubuntu/+source/unity-scope-devhelp12:36
cjwatsonThere may be some LP bugs there12:36
didrocksok12:36
didrocksI'll repromote them then12:36
cjwatsonhttps://launchpad.net/ubuntu/+source/unity-scope-devhelp/+publishinghistory definitely suggests a bug12:37
didrocksno worry, it's a good "end of crazy week" monkey work I can do :p12:37
cjwatsonProbably YA stupid ancestry bug12:38
=== OdyX` is now known as OdyX
wgrantcjwatson, didrocks: Copies don't do binary overrides12:46
wgrantWell, they respect existing ancestry, but you can't specify overrides12:46
wgrantOnly for sources :/12:46
didrockswgrant: ah, ok, makes sense then :)12:47
didrocksthanks for the explanation12:47
cjwatsonwgrant: But even the source was copied from proposed/main to release/universe12:48
wgrantcjwatson: But the copy to -release was a cross-suite ancestry lookup12:49
wgrantI don't think that works in many cases.12:49
wgrantHmm12:49
wgrantBut you're right about the source12:49
wgrantSo it's not binary-specific12:49
wgrantBlargh.12:50
cyphermoxcjwatson: yes, I'll upload in a minute12:50
cjwatsoncyphermox: Great, thanks12:52
cyphermoxdone, it will be in the queue12:52
cyphermoxhas anyone besides me tried the packages?12:53
cyphermoxseems to work properly here, but maybe I'm not testing it right12:53
cjwatsonI think bits of the reports on lillypilly run with a similar local patch12:54
cjwatsonJust not all of them12:54
cjwatsonIt might be worth upgrading lillypilly to a -proposed package by way of verification, once we confirm it basically works at all12:55
=== salem_ is now known as _salem
cyphermoxok12:59
dobeywgrant: thanks for the branch fixing13:00
=== _salem is now known as salem_
cjwatsonarges: Could you merge iptables, or tell somebody else they can do it (you're touched-it-last so it defaults to you)?  There's some stuff in saucy-proposed blocked on that.13:12
argescjwatson: hi. Ok not really sure what you mean by merge, should i just try to reformat my patches to work on top of a fresh debian version?13:13
cjwatsonarges: https://merges.ubuntu.com/main.html13:13
cjwatsonYours is only the most recent patch - there's a large stack of Ubuntu patches that need to be ported forward.  You might want to just ask jdstrand to do it since he did the last big chunk of work :)13:14
cjwatsonBut we default to assuming that the person who uploaded it last will do it13:14
argescjwatson: well i'd love to learn and don't mind doing it13:14
cjwatsonarges: also https://wiki.ubuntu.com/UbuntuDevelopment/Merging, perhaps more helpful13:15
argesthanks, answered my next question13:15
didrockscjwatson: pyruntest build-dep (for gtester2xunit) and julius-voxforge (recommended by hud) are the 2 we missed I guess. We filed the MIRs, but that won't block the iso building if it's not treated today (as being build-dep and recommends only), right?13:16
xnoxarges: there is also a UDD / bzr workflow. When branches are up to date... and when bzr manages to merge sensibly.... http://developer.ubuntu.com/packaging/html/udd-merging.html13:17
argesxnox: ok thanks13:17
cjwatsondidrocks: shouldn't, from that description13:18
didrocksok, thanks :)13:18
cjwatsonplatform-api will be a blocker though13:19
* cjwatson moves unity-scopes-runner and the various hud binaries to main13:19
cjwatsonoh, maybe somebody had done the latter already13:20
=== hggdh_ is now known as hggdh
argesxnox: so i should be merging from debianlp:squeeze/iptables (in this case) which seems to be at an older version, or bzr merge-upstream seems to be at a newer version that whats reported on the merges.u.c page13:24
=== davidcalle_ is now known as davidcalle
xnoxarges: usually one merges from lp:debian/iptables (aka sid) or from lp:debian/experimental/iptables (if that's what needed/wanted)13:25
cjwatsonYou should certainly not be merging from squeeze, which is oldstable :)13:26
cjwatsonEver13:26
argescjwatson: xnox: ok should the wiki be updated then?13:26
argeshttp://developer.ubuntu.com/packaging/html/udd-merging.html13:26
xnoxhmm.... it's a bzr branch somewhere.13:26
cjwatsonI don't think that's a wiki - but yes, that's completely wrong, merge frmo sid13:26
cjwatson*from13:26
argesi'm guessing its meant to be more of a generic guide13:26
argesok13:27
cjwatsonNo point being generic since package merging is basically for one purpose13:27
* xnox found a branch and will update in a sec.13:27
mterrycjwatson, thanks for fixing the pocketsphinx build on powerpc.  I was considering disabling, but hadn't researched the failure yet13:38
mterryWe have a similar problem on sphinxbase, but it also fails on i386 as well as powerpc13:38
argescjwatson: do i need to be filing a merge bug before working on this btw?13:39
cjwatsonI thought it was probably more urgent to get the python-support dep out of main than to worry about the test failure13:39
cjwatsonarges: no13:40
argesack13:40
cjwatsonarges: you're touched-it-last, it's yours by default13:40
cjwatsonmerge bugs are weird things anyway imo :)13:40
argesok next question: so i merged with bzr merge lp:debian/iptables into lp:ubuntu/iptables, and the conflict doesn't match whats here : https://merges.ubuntu.com/i/iptables/REPORT13:41
argesthe versions match what the merge tool did btw13:42
stgraberoh, nice, Debian has iptables 1.4.18 now, that means that once arges is done with the merge I'll be able to stop using my locally packaged 1.4.18!13:43
stgraber(1.4.18 introduces IPv6 NAT which I need to provide easy IPv6 to containers and VMs)13:43
cjwatsonyou shouldn't necessarily expect bzr and MoM to produce the same results; you're meant to use judgement13:43
argesok13:43
cjwatsonthey're differently smart in different ways13:44
cjwatsonfor the most part MoM is likely to be cruder13:44
xnoxmterry: hello, I had a ping from you yesterday but i was gone, and then you were gone. What's up?13:45
mterryxnox, hi~13:45
pittioh, hud now pulling in the voxforge stuff?13:49
pittiare we getting speech recognition into the desktop now?13:49
pitti(just seen the new universe → main mail)13:50
pittididrocks: ^ FYI, this will block propagation, in case you aren't aware13:50
=== wedgwood_away is now known as wedgwood
pittiso we all need to become much more careful what we yell at our #$#@)*# machines during debugging -- it might land right in the amazon online search!13:51
pitti(I'm more scared that it might actually find something)13:51
cjwatsonpitti: component mismatches don't block propagation to release13:52
xnoxcjwatson: but the iso will fail to build?!13:52
pitticjwatson: uh?13:52
pitticjwatson: it should, though, as it will make hud uninstallable?13:52
cjwatsonxnox: didrocks and I established they won't13:52
cjwatsonpitti: it's just a recommends13:52
pittiaah13:52
xnoxpitti: well there is no such concept in debian, hence britney doesn't have such feature... yet.13:53
cjwatsonfurthermore educating britney about components would be hard so I haven't :)13:53
cjwatsonit's a rare-ish problem anyway13:53
pittii. e. we rely on "the daily iso doesn't build" indicator to revert cases which break stuff in a major way13:54
pittixnox: Debian has a policy that main packages mustn't depend on contrib or non-free; isn't that exactly the same thing?13:54
cjwatsonpitti: with the exception of platform-api, I believe it's all sorted13:55
tjaaltonwhat's up with llvm-3.2?13:55
pittinice13:55
cjwatsonpitti: they do, but britney doesn't enforce it13:55
pitticjwatson: ah, good to know; I (dangerously) assumed it would13:55
pittithanks13:55
tjaaltonmesa ftbfs due to " llvm-3.2-dev : Depends: llvm-3.2 (= 1:3.2repack-7) but it is not going to be installed"13:55
cjwatsontjaalton: new llvm-toolchain-3.2 needs clang in main.  I haven't checked what's going on there, whether it's a dropped Ubuntu patch or genuine13:55
cjwatsonthere's been some reorganisation there13:55
tjaaltonah, ok13:56
pittioh, wow! seb128, http://people.canonical.com/~ubuntu-archive/component-mismatches.txt wants to demote gnome-desktop to universe at last \o/13:56
seb128pitti, \o/ (what was still using it?)13:57
cjwatsonhm, maybe it's just trivial component-swapping actually13:57
pittiseb128: not sure, I just saw it; I don't often look at c-m these days13:57
seb128pitti, great in any case ;-)13:57
cjwatsontjaalton: next publisher run might sort it out13:58
tjaaltoncjwatson: ok, thanks!13:58
DktrKranzpitti: is source for c-m published somewhere? I'd like to have something similar for Debian too14:00
cjwatsonDktrKranz: lp:ubuntu-archive-tools.  It's very very very Ubuntu-specific though - it's reliant on germinate output14:00
cjwatsonI'm not TBH sure how it would be useful for Debian14:00
cjwatson(It specifically doesn't handle free vs. non-free moves)14:00
DktrKranzah, pity14:01
cjwatsonIt's just for the supported vs. not distinction14:01
cjwatsonBut feel free to pull something out of it if you find it useful, obv14:01
DktrKranzthanks!14:01
infinitySpeaking of components.  I'm trying to sort out why julius, which is in multiverse, claims to be in the ubuntu-desktop task.14:04
infinityThat doesn't seem right...14:05
infinityOh, hud.14:06
infinityLolz.14:06
cjwatsonRecommends from julius-voxforge14:06
cjwatsonProbably needs to be dropped to Suggests14:06
cjwatsonAssuming julius does actually belong in multiverse14:06
didrocksyeah, we need to discuss with the touch guys14:07
cjwatsonOK, seriously confused about llvm, actually.  Trying to disentangle14:08
didrocksinfinity: cjwatson: no more julius for the next daily release (Monday)14:09
infinitycjwatson: Isn't it just that llvm-toolchain-3.2 replaced llvm-3.2, *and* it now pulls in clang?14:09
didrocksas it doesn't break the iso, I won't rush an upload :)14:09
cjwatsoninfinity: except there's something weird going on with clang vs. llvm-defaults14:09
infinityOh, wait, it now GENERATES clang, rather than pulling it in.14:10
infinityThey've merged the sources upstream, I guess.14:10
cjwatsonDebian has llvm-defaults 0.17 which seems to have vanished from Ubuntu14:10
infinityThat can't be a bad thing, maybe clang won't be such utter crap.14:10
infinitySo, yeah, we definitely need the new llvm-defaults.14:11
* cjwatson tries explicitly syncing it14:11
infinityAnd I think we need to suck up clang in main, cause splitting this back out will probably be more effort than it's worth...14:12
infinityMaybe.14:12
infinityWell, at least libclang.14:12
infinityWe might be able to keep the compiler frontend out.14:12
xnoxsmoser: Hello, you around? =)14:13
cjwatsonAh, auto-sync wouldn't have wanted to sync it because clang was modified in Ubuntu14:14
cjwatsonOf course14:14
cjwatsoninfinity: Did you ever check over the llvm-3.2 / clang Ubuntu deltas to see if anything needs forward-porting?14:14
infinitycjwatson: I haven't yet, I should do today.14:14
cjwatsonIf you could, that would spook me less, yeah14:14
* infinity nods.14:14
infinityThis whole thing took me rather by surprise, I assume llvm-thingee got autosynced and blew up our carefully-crafted house of cards.14:15
infinityIf we still have patches, they're probably one or two tiny ones I can forward-port and forward.14:15
infinityWill check after I've rebooted, filed a kernel bug, and had breakfast.14:15
cjwatsonNo, it didn't get auto-synced.  Sylvestre filed a sponsorship request or similar and dholbach processed it.14:16
cjwatsonauto-sync was rightly holding off until somebody had a chance to manually resolve the whole stack.14:16
cjwatsonSo it's possible we've actually synced a version with the wrong vendor ID, missing support for saucy, and such.14:17
cjwatsonDepending on how clever the latest source is.14:17
pittididrocks: reading your "landed" mail, congratulations! that was a big chunk14:19
didrocksthanks pitti! Happy it's done :)14:19
pittididrocks: and nice timing on a Friday afternoon :)14:19
didrocksisn't it? :)14:19
* pitti resists the temptation to upgrade now, otherwise I'll spend my Saturday fixing my machine14:20
pittij/k14:20
xnoxpitti: you are _not_ running saucy?14:21
infinityClearly, I should never have rebooted.14:21
infinityNow compiz is segfaulting on every run.14:21
infinity\o/14:21
pittixnox: of course I do, but I only upgrade in the mornings usually14:21
xnoxpitti: I see.14:22
pittixnox: I don't have a raring machine :)14:22
pittiin fact, it seems I don't even have a raring schroot yet; must be less than three months, i. e. I didn't yet have to do a postgresql update for stables14:22
infinityMirv: Did anyone every get a chance to look into that compiz-versus-glib segv?14:22
xnoxpitti: my irc-proxy was upgraded to raring this week. Not sure if I should go for saucy or not.14:22
cjwatsonI think gtk+3.0 needs a rebuild against new wayland ...14:22
infinityMirv: It's driving me batty.14:22
cjwatsonmesa too14:23
Laneycjwatson: seb128 is doing it14:23
Laneywell, gtk, don't know about mesa14:23
barryyikes, how dead is the latest compiz?14:24
infinityOh, I thought that was Colin's impression of Jar Jar.14:24
cjwatsonok, long as somebody's on it, it makes p-m output giant14:24
infinitybarry: It hatses me.14:24
cjwatsoninfinity: that's the segfault-for-fun-and-profit thing?14:24
barryinfinity: it is teh crashez14:24
infinitycjwatson: Neither fun nor profit.14:24
cjwatsonI've had 'unity --replace &' running on tty1 for a while ...14:25
infinitycjwatson: Considering high velocity introcution of laptop to wall.14:25
infinityintroduction*14:25
cjwatsonWell, DISPLAY=:0 that, but14:25
infinityWell, I win some sort of prize for this.14:25
infinityI now have a classic X cursor on my tty1.14:25
barryone small silver lining is that the nsa is now being deluged by crash reports14:25
cjwatsoninfinity: ha14:26
infinitykms, you make me giggle.14:26
Laneyso I shouldn't hit go on this dist-upgrade then?14:26
cjwatsonxnox: thanks for merging gdcm14:27
barryLaney: only if you want to take an early weekend14:27
cjwatsonLaney: compiz has been crashy for a while now ...14:27
infinityThis is still the same compiz/unity from raring.14:27
infinityBut every new glib update seems to make it worse. :P14:27
Laneyoh, alright14:27
LaneyDoesn't seem particularly bad here14:27
barryhmm, both my saucy desktops are totally useless now14:28
seb128segfaults should be fixed in today's version14:28
infinityI seriously can't get it to log me in now...14:28
cjwatsonLaney: I think the pattern is glib cleans up memory leaks => things that failed to increment refcounts properly died14:28
infinityMaybe a by-hand run will work for now.14:28
xnoxcjwatson: no problem, retried insighttoolkit4 as well.14:28
cjwatsonxnox: I noticed, thanks14:28
infinityNope.14:29
infinity*sigh*14:29
cjwatsonseb128: I hope so :)14:29
infinityseb128: When can I haz this version?14:29
Laneygdcm actually got fixed?14:29
seb128infinity, it's in saucy ?14:29
infinityseb128: I literally can't log in anymore.14:29
cjwatsonLaney: apparently14:29
seb128infinity, since when ?14:29
Laneywowzers14:29
smoserxnox, here.14:29
infinityseb128: Wait, today's version of what?14:29
barryseb128: nope. i *just* dist-upgraded and compiz is completely useless14:29
smoseri 'never minded' my ping of you yesterday14:29
seb128infinity, unity; sorry I didn't follow the backlog14:30
seb128barry, backtrace?14:30
infinityI got no new unity today.  Has it made it out of proposed?14:30
infinityOh, hah, it must have JUST promoted.14:30
infinitybarry: Try again?14:30
barryseb128: yeah, i'm trying to get a bug report filed, but have to do it remotely14:30
jbichainfinity: I have the new Unity; it just won't run here :(14:31
infinityOh joy, I get a bunch of new scopes forced on me.14:31
barryinfinity: trying...14:31
infinityOh, just recommends.14:31
seb128was any package let on hold of the upgrade or removed?14:32
jbichainfinity: but no unity-lens-shopping; see, Ubuntu does listen to its users ;)14:32
seb128can pastebin your dpkg.log?14:32
infinityjbicha: Heh.14:32
Laneyhah, yeah, compiz segfaulted immediately after the upgrade14:33
Laneyseems to have respawned itself alright though14:33
xnoxsmoser: oh. ok. What was it though? Anyway, I'd wanted to say that I did cherry-pick all relevant fixes, and the delta as part of last upload is what we are planning to SRU into Raring to fix all of issues with forgotten events.14:33
jbichaseb128: the only removals were appmenu-gtk, appmenu-gtk3, and the shopping lens14:33
xnoxsmoser: we hope it's sufficient for cloud-init case. Ideally one would still need to refresh raring images, after sru is published, given the caveats outlined in the bug report.14:33
seb128jbicha, nothing on old?14:33
seb128hold14:33
jbichano14:34
seb128can you get a stacktrace?14:34
* barry has the same experience as jbicha 14:34
xnoxsmoser: do you have any questions about upstart fixes? or you still need to try them first?14:34
smoserxnox, well i haven't tried them.14:34
smoserbut the reproduce case was pretty straigt forward.14:34
smosermy ping was complaining about not restarting14:35
jbichamy ~/.xsession-errors or ~/.cache/gdm/session.log doesn't seem to have any useful info14:35
xnoxsmoser: ack. jodh is on holiday, feel free to ping me if anything comes up.14:35
smoser(on upgrade)14:35
smoseri guess you're only doing that if its the old version though.14:35
smoserwhich is sane.14:35
smoserand wont really be a problem.14:35
smoserthe images will get refresshed and have this new udev in thm and then that will be that.14:35
xnoxsmoser: well, it will restart on upgrade, if the upgrade is done at runlevel 2. If one is in early boot, the upgrade will not restart. (e.g. not yet fully initialised cloud-init instance)14:36
smoserer.. s/udev/upstart/14:36
seb128jbicha, what if you run unity from a vt?14:36
barryinfinity, jbicha, seb128 good news.  another dist-upgrade and my desktop is happy again14:37
smoserxnox, yeah, i had thought you could restart after reaching runlevel 2 in that case.14:37
smoserbut that adds complexity14:37
xnoxsmoser: we could hint that reboot is required instead if the upgrade was done in early boot, but I remember you said you don't want to reboot.14:37
smoserie, youcould add a job that would run on rc 2 and then it would delete itself.14:37
smoserright. you could mark the 'reboot-required'14:37
infinityHuzzah, I'm in a unity session!14:37
smoserit would seem that you probably should mark that, dont you think?14:37
smoseras a reboot *is* required.14:37
seb128barry, cool14:38
xnoxsmoser: reaching runlevel 2 is outside of dpkg control, so I'd rather not have ethermal jobs to do that. pitti was also asking for "ethermal" configuration location e.g. /run/init/14:38
pitti("ephemeral"?)14:38
smoser:)14:38
xnoxsmoser: yeah, we should mark reboot-required. I'm now not sure why in the end we didn't add it in. I'll check my notes from the sprint.14:38
smoserbut ethermal sounds good too14:39
xnoxpitti: smoser: yes =) my big words should usually be filtered through fuzzy match by context.14:39
smoserxnox, all in all, i think its sufficient, and soon enough we'll have fully owrking images.14:39
xnoxtrue.14:40
mlankhorstsoon we'll have eternal configuration locations14:40
smoseri have to remove the work around in cloud-init also. as to avoid breakage, it does not reload-configuration after writing an upstart job14:40
smoser(that is required for the case where /etc is overlayfs or some other non-inotify friendly fs)14:40
smoserand wasn't supposed to hurt anything :)14:40
xnox=)))) true.14:41
infinityAww, crap.  I must have closed firefox twice in a row at some point and lost my several-hundred-tab session.14:42
xnoxsmoser: to be honest, I'm of an opinion reload-configuration should live in upstart-file-bridge or upstart itself. E.g. one puts inotify watch on '/' which will get a create event, as soon as anything is written on to overlayfs top level dir, and if it happens to be a "create /etc folder" we should reload.14:42
seb128jbicha, does another dist-upgrade fix it for you like for barry?14:42
infinityGrr.14:42
infinityI blame compiz.14:42
LaneyAhh, mesa is caught up with llvm14:42
cjwatsoninfinity: might still be in one of the sessionstore.* files in your profile14:42
LaneySo I guess wayland is stuck until then14:42
infinityseb128: I seem to be back in business after another dist-upgrade but, then again, I'd been able to run it in the past too, so I dunno.14:42
infinitycjwatson: Timestamps and sizes on those don't look promising.14:43
infinityYeah, I think it's lost for good.14:43
seb128infinity, if you have an issue please try to get a backtrace, or ping me and I will help to get debug infos14:43
cjwatsoninfinity: backups?14:44
smoserxnox, i'm confused. i what is different currently than what you're saying ?14:44
smoseroh. i see.14:44
* Laney restarts session with some trepidation14:45
xnoxsmoser: upstart should be resiliant against hostile fs, instead of cloud-init lending a helping hand ;-)14:46
infinitycjwatson: I don't backup that frequently.  I'm sure I'll live with a fresh firefox start.14:46
infinitycjwatson: Those tabs just end up being a depressingly long TODO-that-never-gets-TODONE anyway.14:46
infinityseb128: If it explodes again, I'll be sure to yell.14:47
cjwatsonMy backups sucked until I made it a daily cron job.14:47
cjwatsonAlthough I do need to get a secondary backup disk again.14:47
infinitycjwatson: My laptop isn't really all that critical to me, which is why I don't backup often.14:47
infinitycjwatson: Other than PGP and SSH keys, the rest of this data is meaningless to me.14:48
infinityAnd those don't change often. :P14:48
cjwatsonIt's more minimal-hassle-of-recovery than meaningfulness for me, I think.14:49
* xnox wiped openssh-server keys of my machine the other day..... happens. couldn't be bothered to restore from backup. plus got a new shiny ecdsa key.14:50
barrydoko: ping14:50
dokobarry, ?14:52
barrydoko: hi.  i want to work on sru'ing lp: #1058884 today.  just wanted to check with you so i don't step on your toes if you're planning anything else14:53
ubottuLaunchpad bug 1058884 in python3.3 (Ubuntu Raring) "Race condition in py_compile corrupts pyc files" [Undecided,Confirmed] https://launchpad.net/bugs/105888414:53
dokobarry, there are still some packages in proposed, I think. but I would have to recheck14:54
=== mmrazik is now known as mmrazik|afk
barrydoko: i saw that proposed is a bit ahead.  would you rather i wait until they clear or should i just go ahead and backfill them?  (fwiw the bzr branches should be current w/the proposed backlog)14:56
bdmurraycjwatson: could you have a look at bug 1187233?14:56
ubottubug 1187233 in OEM Priority Project "Grub2 fails on ASUS X201E with secure boot is enabled" [Critical,New] https://launchpad.net/bugs/118723314:56
cjwatsonbdmurray: I punted that over to shim since it doesn't seem to be a GRUB problem; if slangasek has a chance to look, he knows rather more about shim than I do14:57
cjwatson(It's reminiscent of the problem stgraber reported just before the last physical UDS, FWIW)14:57
cjwatsonMight just be an our-shim-is-too-old problem14:58
dokobarry, weill, you can add the patch on top, but make sure to correctly generate the changelog14:58
infinityxnox: I don't care about host keys at all, but losing ssh user IDs is a pain, I do keep those in more than one place.14:59
barrydoko: will do, thanks14:59
jbichaUnity is working now here but I'm not sure what changed :|14:59
bdmurraycjwatson: okay, thanks14:59
=== gusch is now known as gusch|away
infinityAww, crap.15:06
infinityseb128: Remember when I lost detached menus in some applications but not others?15:06
infinityseb128: Do you remember why that was?15:06
infinityseb128: Cause it's back. :)15:06
seb128infinity, no15:06
infinityOh.15:06
infinityPoo.15:06
* infinity tries to remember WTF caused that.15:07
infinityseb128: Ahh, the upgrade installed unity-gtk2-module unity-gtk3-module, which removed appmenu-gtk appmenu-gtk315:08
infinityseb128: Was that intentional?15:08
seb128infinity, yes15:08
seb128infinity, did you restart your session?15:08
infinityseb128: Kay, well.  I no longer have global menus in pidgin.15:08
infinityseb128: I rebooted after the upgrade, so yes.15:09
seb128infinity, do you have unity-gtk2-module?15:09
seb128oh yes, you said that15:09
seb128infinity, I'm about to do an upload of gtk2/gtk3, let me know if those fix your issue15:09
infinityseb128: Mmkay.15:09
pittiwow, dist-upgrade will use 48.5 MB additional space15:10
infinitypitti: All the new lenses?15:10
pittiinfinity: yeah, and the voxforge stuff presumably is quite heavy15:11
infinityI admit, I dist-upgraded with --no-install-recommends15:11
pittiyeah, I'm pondering that15:11
infinitypitti: Which would also cull out voxforge stuff.15:11
pittiinfinity: cf. my statement above about yelling crap at my computer during debugging, and then finding amazon search results for that in the dash..15:12
infinitypitti: Hahaha.15:12
pittiunity-scope-guayadeque, urgh15:13
pittido we really need to install and run all these scopes by default?15:13
pittiI mean, how many people are going to use all those?15:13
Laneyhaha, that package's long description is ex-ce-llent15:13
seb128pitti, we don't run them15:13
Laney This package contains the "guayadeque" scope which allows Unity15:13
Laney to search for guayadeque content.15:13
seb128pitti, we activate them on demand when the server says to use them15:13
pittiinfinity: ah, but even without recommends it's still +35 MB, as the sphinx/voxforge stuff is apparently required15:14
seb128it's voice stuff for the hud15:14
pittiright, I know15:14
pittilet's see how well this machine will understand me15:15
pittiseb128: est-ce qu'il peut comprendre français ? :-)15:15
seb128je ne sais pas ;-)15:15
tedgpitti, We need more data, basically for each language we need 100hrs of samples.  Unfortunately English is the only one there.15:15
pittij/k15:16
pittiyeah, I saw, it's just -hmm-en for now15:16
infinitypitti: Curious, I was able to remove the voxforge stuff post-upgrade.15:16
tedgI figure next sprint that is in a non-English country we should sit at Starbucks for a day and get samples from people in line :-)15:16
infinitypitti: Can't be THAT required.15:16
jbichaI don't see guayadeque in the Filter Results list; I think Unity is smart enough to not show it if guayadeque isn't installed15:18
pittiLaney: yeah, seems all scopes have the exact same description with just the name changed15:19
jbichathere's a QueryBinary=guayadeque field in /usr/share/unity/scopes/music/guayadeque.scope15:19
pittitedg: perhaps we shouldn't pull in the -en voxforge bits through direct dependencies, but through our "install language support" magic15:20
pittitedg: (at least in teh future, when we actually do have multiple languages)15:20
tedgpitti, That would make sense to me.  We need to make HUD smarter to handle those languages, but yes.15:21
tedgpitti, I'd really like to set that up as a way that Loco's could help out.15:21
tedgpitti, Submit language data to voxforge15:21
tedgWe might be able to get to 100hrs for major languages then.15:22
Laneyhow do I try that stuff out?15:22
tedgLaney, The voice recognition?15:25
Laneyyeah15:25
tedgLaney, You can get hud tools and use the hud-gtk frontend, or else with Unity 8.15:25
Laneytedg: ** (hud-gtk:11375): ERROR **: hud-gtk.vala:139: Failed to open file 'share/hud-gtk/hud-gtk.ui': No such file or directory15:26
Laney;-)15:26
tedgUhg15:27
tedgcd /usr/share/hud :-)15:27
=== gusch|away is now known as gusch
QuintasanLaney: I believe I sent you a mail asking if you would sign my new GPG key as I did a transition, do you respect those or I have to catch you on some conference?  :P16:33
LaneyProbably not, sorry16:34
Laneycome to debconf :-)16:34
QuintasanLaney: I see. Switzerland it is. Never been there, might attempt to get there :P16:35
ograoh, debconf is in ch ?16:36
Laneysure is16:36
ograhmm16:36
infinitycjwatson: So, looks like this only dropped one of our llvm-3.2 patches, the rest made it back to Debian or upstream, I believe.16:38
infinitycjwatson: Checking clang patches now.16:38
=== plars is now known as plars-afk
cjwatsonCould be worse then16:43
infinitycjwatson: Testbuilding before upload, but it looks like this is our remaining delta: http://paste.ubuntu.com/5742432/16:52
infinitycjwatson: I need to rethink the "list every release ever" madness, and try to simplify that for upstream for all distros, it's borderline insanity.16:52
cjwatsonDistro-specific version comparison would be less bad16:55
cjwatsoninfinity: BTW your changelog is wrong, s/Raring/Saucy/16:56
infinitycjwatson: Picky, picky.16:56
infinitycjwatson: The queue would have told me ALL about that. :)16:56
infinitycjwatson: It would have said "dude, that's in unapproved", and I would have jumped on #launchpad-ops and screamed "WHO FROZE MY ARCHIVE?!" and then felt like a right git when I realized I just can't read.16:57
infinitycjwatson: Oh.  You mean the description of the patch, not the upload target.16:57
infinitycjwatson: La la la.16:57
cjwatsonI did :)16:59
infinitycjwatson: That's okay, it was wrong in the patch header too.17:00
cjwatsonCapitalisation hint and all.17:00
infinitycjwatson: I suspect I cargo-culted it from the last time I'd done the same thing. :P17:00
* infinity wonders what the ratio of cargo-culting programmers to historical cargo-cultists is.17:01
cjwatsonI hardly ever even write new changelog entries when I can copy-and-paste the last similar one I wrote17:02
=== plars-afk is now known as plars
menaceis there any point in removing all read-privileges for /etc/sysctl.conf or /etc/syslog.conf in terms of security in an standard installation? just stumbled over that in a installation procedure...17:40
sarnoldmenace: won't a user still be able to dump all the settings via sysctl -a ?17:41
sarnold.. or read values out of /proc ?17:41
argesjdstrand: hi17:57
sarnoldarges: he's out-of-office this week..17:58
argessarnold: ah... was going to have him review my iptables merge17:58
argesi'll ping him next week then17:58
sarnoldarges: okay :)17:58
slangasekpitti: hey, have you seen bug #1181810 on upower, and do you have any idea what might be causing it?18:01
ubottubug 1181810 in upower (Ubuntu) "After upgrade to saucy, lid close policy is not being respected" [High,Confirmed] https://launchpad.net/bugs/118181018:01
slangasekpitti: I'm not sure if it could be related to the changes made to acpi-support18:01
slangasek(though probably not, I guess, since there's now nothing in acpi-support which handles lid close events)18:02
josephtslangasek: that looks like a dupe of bug 118051318:03
ubottubug 1180513 in gnome-settings-daemon (Ubuntu) "lid close actions are ignored laptop always suspends" [Medium,Triaged] https://launchpad.net/bugs/118051318:03
slangasekjosepht: ah, ok18:03
slangasekjosepht: thanks for the pointer, that does indeed look like the same issue - and I see I was pinging the right person, as pitti assigned the bug to himself ;)18:04
=== sraue_ is now known as sraue
argescjwatson: so i did a iptables merge that installs, runs. whats the best way to post it so that others can review? I could not get the bzr merges working properly, so I used the grab-merge.sh script.18:10
infinitydoko: Can you avoid retrying the armel gcc-4.8 build in toolchain-r after I kill it?  It seems to be taking out pandas left and right.18:16
slangasekarmel?18:21
infinityslangasek: quantal.18:22
slangasekhmph :)18:22
keessarnold: not all of them, actually.18:33
kees$ ls -la /proc/sys/fs/*prot*18:34
kees-rw------- 1 root root 0 Jun  7 11:33 /proc/sys/fs/protected_hardlinks18:34
kees-rw------- 1 root root 0 Jun  7 11:33 /proc/sys/fs/protected_symlinks18:34
keesan attacker has to trip the warning to find out if they're set ...18:34
keesso, it's an interesting point about /etc/sysctl.*18:34
keesthough it's no secret what a distro's settings are.18:34
lifelesskees: zomg people know what we build our binaries with?18:39
Mirvinfinity: I believe you should have gotten the fix around ~now with today's updates18:46
infinityMirv: Indeed, I seem to be more stable now.18:47
infinityMirv: Fingers crossed.18:47
keeslifeless: they do indeed! :)18:58
sarnoldkees: oh, neat :) I've not noticed the tripwarning before :) hehe19:01
keessarnold: yeah, if you trigger the link protections, and audit notice is generated19:02
=== salem_ is now known as _salem
cjwatsonarges: best thing to post is a debdiff from current Debian22:57
=== wedgwood is now known as wedgwood_away
bdmurrayslangasek: could you have a look at bug 1187233?23:11
ubottubug 1187233 in OEM Priority Project "Grub2 fails on ASUS X201E with secure boot is enabled" [Critical,New] https://launchpad.net/bugs/118723323:11
slangasekbdmurray: well, I suppose I'll need to, yes; this isn't going to be a bug we can fix quickly, there's minimal debugging capabilities here23:12
slangasekmore precisely, getting a debug build of shim will require fiddling the secureboot settings in ways that may prevent the problem from being reproducible anyway... but I'll see what I can do - next week23:12
bdmurrayslangasek: okay, sounds good.23:13
cjwatsonpitti: Please stop dropping the devpts mount from the d-i udev startup script; /usr/share/initramfs-tools/init is not used for d-i23:24
cjwatsonpitti: I'm putting it back to unbreak the server images23:24
cjwatson(debian/extra/udev.startup is used nowhere else than d-i)23:26
=== broder_ is now known as broder

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