[05:40] <Noskcaj> Is there any point trying to fix some of quickly's bugs since it's pretty much EOL
[06:09] <pitti> Good morning
[07:19] <jibel> pitti, some packages failed to install in adt VMs during latest provisioning. I reprovisioned them.
[07:19] <jibel> pitti, I'll restart the tests that failed once it is done.
[07:19] <pitti> jibel: thanks; I've not gone through all of them yet (see #u-quality), but started
[07:20] <pitti> jibel: there's a couple of new packages there which geuinnely fail
[07:27] <pitti> jibel: oh, was visp one of those? that doesn't have an obvious failure
[07:28] <jibel> pitti, visp, quagga and gtkada
[07:28] <pitti> good, thanks; deleting those mails then
[07:37] <jibel> pitti, that's also a case where status in britney stays 'running' forever. Because the test fails early (like VM or test session fails to start), no results is generated.
[07:37] <jibel> -s
[08:31] <pitti> jibel: ah, git uninstallability is also on http://people.canonical.com/~ubuntu-archive/testing/trusty-proposed_probs.html
[08:31] <pitti> problem is that https://launchpad.net/ubuntu/+source/git/1:1.8.4.1-1 built only on amd64
[08:32] <pitti> tests fail on the othhers
[08:32] <pitti> debian bug 727226
[08:33] <pitti> seems we should perhaps just remove that version from trusty-proposed, and wait for a fix from Debian?
[08:33] <pitti> cjwatson: ^ would you agree that this is a sensible approach? (unless someone on the Ubuntu side fancies fixing this)
[08:34] <cjwatson> pitti: Could you check whether anything has grown versioned dependencies that would be broken by removing it?
[08:34] <pitti> yes, doing
[08:37] <pitti> cjwatson: checked all components, none
[08:38] <cjwatson> pitti: and AIUI this is causing some autopkgtests to fail?  (for the removal message)
[08:38] <pitti> cjwatson: yes, at least guilt
[08:39] <cjwatson> pitti: ok, removed
[08:39] <pitti> thanks
[08:40] <pitti> cjwatson: I didn't actually mean that you should do it for me, I was more interested in your general opinion whether we should just remove broken stuff from -proposed if it's unlikely that we'll fix it on our side
[08:40] <pitti> but I take this as a "yes" :)
[08:40] <cjwatson> I'm not sure I hold that opinion in general, but in the case where it's having fallout I'd say probably
[08:41] <cjwatson> as a general policy it worries me that it's hard to track
[08:46] <pitti> cjwatson: heh, ironically it broke mercurial's tests, too (as they install git to verify git import)
[08:51] <Fudge> cjwatson  I sit here, I read but still have a hard time catching on :D
[08:58] <debfx> jodh: is it possible to run upstart services as a user with all its supplementary groups (without using wrappers like start-stop-daemon)?
[09:00] <xnox> debfx: http://upstart.ubuntu.com/cookbook/#setuid
[09:00] <xnox> debfx: http://upstart.ubuntu.com/cookbook/#setgid
[09:00] <xnox> ?
[09:02] <debfx> yeah I know about setuid but that just sets the primary group
[09:04] <xnox> i see.
[09:05] <xnox> debfx: i'm not aware of any other standard facility, apart from using sudo / start-stop-daemon / etc.
[09:05] <xnox> doko: with gcc-4.8, how come it's libstdc++-4.8-dev, yet libstdc++6-4.8-dbg
[09:06] <pitti> most packages don't put the soname into the -dev package for simplicity
[09:07] <pitti> (-dev package name, I mean)
[09:10] <jodh> debfx: you mean+need setgid I think.
[09:21] <xnox> pitti: sure, but it used to be libstdc++6 across the board (including all -dev packages) so not sure if the rename is incomplete.
[09:22] <debfx> jodh: setgid sets the primary group and leaves the supplementary group list empty, no?
[09:22] <debfx> basically I want upstart to call initgroups() before execing or let me manually specify the supplementary groups.
[09:22] <jodh> debfx: upstart does call initgroups.
[09:23] <jodh> debfx: maybe you're using an older version that doesn't?
[09:23] <debfx> possibly, tested it with precise
[09:26] <debfx> ok, found it: https://code.launchpad.net/~stgraber/upstart/upstart-initgroups/+merge/136794
[09:50] <darkxst> clutter-gst is completely broken in trusty right now it seems
[09:50] <darkxst> https://launchpadlibrarian.net/155208131/buildlog_ubuntu-trusty-amd64.clutter-gst-2.0_2.0.8-1~trusty1_FAILEDTOBUILD.txt.gz
[09:51] <darkxst> other builds just hang
[09:52] <darkxst> although can't reproduce locally with pbuilder
[10:30] <pitti> slangasek, stgraber, jibel: FYI, I renamed the BP to core-*, as per cjohnston's mail: https://blueprints.launchpad.net/ubuntu/+spec/core-1311-lts-upgrade-testing
[10:33] <brainwash> pitti: http://lpaste.net/94917 http://lpaste.net/94918 http://lpaste.net/94919
[10:33] <brainwash> regarding the suspend/resume issue
[10:34] <brainwash> some random log files, did my best to gather some information when the failure occurs
[10:36] <pitti> brainwash: thanks! would you mind adding these to the bug, so that the information is at one place?
[10:37] <pitti> brainwash: as for the first, I take it you didn't do https://wiki.ubuntu.com/DebuggingDBus to see the method calls as well? The log only has signals
[10:38] <brainwash> oh, right.. forgot about this
[10:39] <brainwash> there is no trace of this signal in the monitor log "SIGNAL EMISSION org.freedesktop.systemd1.Manager.JobRemoved()"
[10:39] <brainwash> send by systemd-shim
[10:39] <pitti> stgraber, slangasek: as discussed, I filed https://blueprints.launchpad.net/ubuntu/+spec/core-1311-ssd-trimming
[10:49] <cjohnston> thanks pitti!
[11:24] <tseliot> pitti: hi. You seem to be part of the lightdm. Does this mean you get to review merge requests?
[11:25] <pitti> tseliot: I can review simple fixes, but I don't know the overall code; robert mainly added me to fix the apparmor profile
[11:25] <tseliot> pitti: oh, ok. I have a two lines patch but it's a feature
[11:53] <tseliot> stgraber: are you around?
[12:08] <mbait> Hi there! I'd like to backport some package for Precise. I am using 'backportpackage' in a couple with PPA. The problem is the build is failed due to outdated dependencies. Is it possible to backport dependencies as well?
[13:32] <melodie> hi
[13:33] <melodie> I am seeking an information related to the txt.cfg in the isolinux directory, in a Desktop Live. This is related to the name for a remix. If someone has knownledge about it? (I browsed lots of docs on the web and I missed the one detail I need, so far)
[13:57] <sladen> melodie: it's a while I had to poke one;  there are a series of label/menu/title lines;
[13:57] <sladen> melodie: it should be possible to spot the text that you'd like to change, and alter it
[13:57] <LLckfan2> I have an android tablet that I have put youtube app on. When I try to sign into youtubr it says an error occurred. Is there anything I can do to fix this? I did not get the app from Google Play as Google Play does not support my brand of tablet.
[13:58] <melodie> hi sladen
[13:58] <sladen> LLckfan2: Android?  This is #ubuntu-devel.  Ubuntu is a different operating system (though both Linux and Android use the Linux kernel for hardware drivers at the very base layer)
[13:59] <melodie> I have changed just the name "Ubuntu" for the name of my remix, and the next three isos had a little issue: after changing the language to my language, the two first boot stanzas where still in English.
[13:59] <melodie> this is what I try to find about. Where should I look ?
[14:02] <sladen> melodie: is there an 'i18n.cfg', or similiarly named file somewhere around?
[14:02] <melodie> sladen probably, I look
[14:03] <sladen> melodie: also  https://help.ubuntu.com/community/InstallCDCustomization#Modify_installer_behaviour_using_a_Preseed_file
[14:03] <melodie> no there isn't
[14:04] <melodie> should there be one?
[14:05] <brainwash> pitti: I've uploaded the log files now, including dbus-monitor with 99-eavesdrop.conf enabled
[14:05] <melodie> well in the latest lubuntu saucy isolinux there isn't one either
[14:06] <brainwash> pitti: it really looks like some dbus connection issue
[14:06] <sladen> melodie: is  http://cdimage.ubuntu.com/lubuntu/releases/13.10/beta-2/lubuntu-13.10-beta2-desktop-i386.iso  what you are starting with?
[14:06] <melodie> sladen I have already read the link you are pointing me to
[14:07] <melodie> I started with a Ubuntu Mini Remix 12.04 months ago and I often look into Lubuntu and Xubuntu isos to search about information, but I don't use them directly
[14:07] <melodie> so after reading the link you pointed me to, it seems you think I want to customize for one language? This is not the case.
[14:08] <melodie> and I can't build seed files, because I don't use a regular method, just Ubuntu Builder and the command line for things it doesn't do
[14:10] <melodie> Only having "Ubuntu" in the txt.cfg file changed to "My_remix_name" would be interesting right now, and later I will start to work on getting into other details, such as a meta package
[14:11] <melodie> I just don't understand why when I change the name there, 2 over the 5 boot stanzas stay in English.
[14:12] <melodie> this is what I have:
[14:12] <melodie> http://pastebin.fr/29250
[14:12] <melodie> these are the txt files in the isolinux directory
[14:15] <melodie> sladen I wonder if the i18n.cfg was not what is now po4a.cfg ?
[14:15] <melodie> it contains the iso codes for the languages?
[14:18] <sladen> melodie: there is normally base string in a configuration string; and then various translation files which contain the base string; and the translated replacement for each language
[14:18] <sladen> melodie: this are normally .po files, yes; but I'm not sure how it works for syslinux/isolinux
[14:19] <sladen> melodie: pitti or cjwatson may be able to remember off the top of their heads exactly how it is setup
[14:20] <pitti> brainwash: hang on, might it be that most of the people who are reporting this are running not Unity or GNOME, but XFCE or KDE?
[14:20] <sladen> melodie: the translations being in the  /isolinux/NN.cfg
[14:20] <sladen> melodie: the translations being in the  /isolinux/NN.tr
[14:21] <pitti> brainwash: I'm asking because gnome-settings-daemon inhibits logind's own handling of the lid
[14:21] <pitti> brainwash: does this also happen if you run suspend from the menu instead of closing the lid?
[14:21] <brainwash> pitti: I'm running xfce, but I don't use the lid to trigger suspend
[14:22] <brainwash> only menu mostly
[14:22] <brainwash> sometimes via direct dbus call
[14:23] <melodie> sladen ok, but still how come 2 first strings stay untranslated and the three after do... this is bizarre
[14:23] <brainwash> the strange thing is that it only happens occasionally, like 20-25% of all suspend/resume cycles
[14:24] <pitti> brainwash: ok, then it's not that; thanks
[14:25] <sladen> melodie: if you change a string;  but not the base string in a particular locale translation, then it will not match.  Without a match, the translation for that language can't be replaced
[14:25] <brainwash> pitti: and it appears to me that different issues got mixed in the bug report, but maybe they are all related
[14:26] <melodie> sladen ok I see. So until I know how to start from the sources the best I can do is leave it as is
[14:27] <melodie> the NN.tr files are binaries so...
[14:27] <melodie> needs sources and a compiling step :)
[14:27] <sladen> melodie: po4a is "PO for All"
[14:28] <melodie> oh ok
[14:29] <brainwash> pitti: however, if systemd's actions don't get inhibited and the system suspends twice within a small time frame, things might fail also I guess
[14:31] <melodie> sladen do you know if this is what I would need to start from? https://launchpad.net/ubuntu/+source/syslinux-themes-ubuntu
[14:32] <melodie> or rather https://launchpad.net/ubuntu/+source/syslinux ?
[14:33] <cjwatson> melodie: The translations are in gfxboot-theme-ubuntu
[14:34] <cjwatson> It's tedious that this has to be done per-flavour, but necessary in general due to the structure of natural language
[14:35] <cjwatson> Not a real example but compare e.g. "an Ubuntu mirror" with "a Lubuntu mirror" in English
[14:35] <melodie> hi cjwatson
[14:37] <melodie> what is  gfxboot-theme-ubuntu ? I am looking into a syslinux-theme-ubuntu archive from https://launchpad.net/ubuntu/precise/+source/syslinux-themes-ubuntu : this is not what you refer to, is that right?
[14:37] <melodie> a package maybe?
[14:37] <cjwatson> It's a source package
[14:37] <melodie> I seek for it, thank you
[14:38] <sladen> melodie: apt-get source gfxboot-theme-ubuntu && cd /gfxboot-theme-ubuntu-*/po
[14:39] <sladen> melodie: in eg. 'fr.po' there is  msgid "^Try Lubuntu without installing" <-> msgstr "^Essayer Lubuntu sans l'installer"
[14:40] <melodie> sladen cjwatson I have the source package for the version I am working on now, I just wonder if there is a howto compile that once the strings changed? :)
[14:41] <melodie> is is just ./configure && make or such?
[14:43] <sladen> melodie: sudo apt-get build-dep gfxboot-theme-ubuntu && debuild  should work
[14:44] <melodie> nice! I'll try that
[14:46] <melodie> in the README it says how to add text, and how to remove text, is that also valid for replacing a string?
[14:47] <slangasek> pitti: ack, thanks
[14:48] <cjwatson> melodie: I usually do those replacements with some sed rune I make up on the spot
[14:49] <melodie> I see :)
[14:54] <melodie> how does the syslinux bootloader know which one of the versions will be booted, as in a NN.po file each flavor is provided?
[14:55] <melodie> should a new block file be added in the po files?
[14:55] <melodie> a new block text*
[14:57] <melodie> that seems to lead to a larger job :)
[14:58] <cjwatson> I generally add one per flavour, yes
[14:58] <cjwatson> The PO files just include all known flavours
[14:58] <cjwatson> And syslinux knows about it because its other configuration files are set up appropriately
[15:00] <melodie> cjwatson ok
[15:00] <melodie> I'll have to learn lots more about all this
[15:00] <melodie> during the coming winter :)
[15:02] <melodie> thank you very much
[15:02] <melodie> and sladen thank you very much also
[15:08] <melodie> I wonder what is still good from that page nowadays and what is not? (ie syslinux.cfg used to contain what txt.cfg does now): https://help.ubuntu.com/community/LiveCDCustomizationFromScratch
[15:21] <sladen> melodie: a really useful thing would be to keep track of your successes, and failures, and write-up some (more up to date) documentation as you go
[15:28] <melodie> sladen unfortunately I don't have (at least so far) the knowledge for that. I didn't start from Scratch because when I started I just tried head into the doc and when arrived at the interesting page in the doc (something about diverting sysctl) I just got lost, not knowing how to understand what was after: was it to be used literally or adapted, I had no idea. Since then, I use ready to go scripts, the one I find working best for now being Ub
[15:28] <melodie> untu Builder (a gambas gui) with Ubuntu Mini Remix as a start.
[15:28] <melodie> else, I do take notes and put the files used and information on a web space
[15:29] <sladen> melodie: you are acquiring the knowledge.  Write notes as you go, and it will be useful for you, and anyone working with you; but *also* useful for everything afterewards
[15:29] <melodie> I might copy them to bitbucket or github later, for now it's here: http://meets.free.fr/Downloads/BentoVillageProject/
[15:30] <melodie> not too messy, but will need to refine again later :)
[15:30] <tseliot> slangasek: are you available to review/approve an upload (with a small diff) which should fix 2 SRUs?
[15:40] <melodie> sladen I might learn more when I will dive into seeds for the preseed directory, I found a doc and some good pointers on the Edubuntu wiki yesterday. I would have questions about preseeds too. Are they used as well for building the isos as for updating at install time when the option is ticked in the installer?
[15:58] <melodie> thanks for all, bye
[16:11] <tseliot> stgraber: re-ping
[16:12] <stgraber> tseliot: hi
[16:25] <brainwash> pitti: the report is getting flooded with comments once again, just to clarify my comment, the entry is missing, because systemd-shim didn't print it https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/comments/58
[16:28] <brainwash> pitti: besides that, is any other log/debug informantion needed to understand the problem and identify the culprit?
[16:45] <tseliot> slangasek: never mind
[18:18] <psusi> slangasek: I'm looking at a bug report by a user saying he has no /dev/.blkid.tab... and I don't see how it *ever* works.  persistent-storage.rules always runs blkid -p, which prevents it from writing out the cache, so how does it ever get created?  Shouldn't that not have a -p there?
[18:35] <dobey> sarnold, jdstrand: hi. do you guys know who would be best to chat with about creating an apparmor profile for tarmac? or more specifically, to prevent external processes spawned by tarmac from doing certain things
[18:37] <sarnold> hi dobey :) I've never heard of 'tarmac' before. What is it? what does it do?
[18:38] <dobey> sarnold: it's a tool for managing branch landing on launchpad
[18:38] <sarnold> dobey: if tarmac uses the usual fork()+exec() method of starting processes, AppArmor's "child" profiles may be suitable: http://wiki.apparmor.net/index.php/QuickProfileLanguage#Child_profiles
[18:39] <dobey> it uses the python subprocess module; so i presume that's standard enough
[18:41] <sarnold> dobey: you -may- need to add something like /bin/bash ix,  to the tarmac profile if the python subprocess winds up shelling out to system(3) to execute programs; if it builds arguments as arrays and uses execve(2) directly, you may not need the /bin/bash ix, and just use the /path/to/helper Cx, rules
[18:43] <dobey> sarnold: hrmm. does "profile * {}" work for that?
[18:44] <sarnold> dobey: I don't think it would work as you'd hope -- if you want to allow tarmac to execute -anything- but just confine what those "anythings" are allowed to do, it might look something like this:
[18:44] <sarnold> /usr/bin/tarmac {
[18:45] <sarnold>   /usr/bin/* cx -> tarmac_child,
[18:45] <sarnold>   profile tarmac_child {
[18:45] <sarnold>     /path/to/launcpad/branches/** rw,
[18:45] <sarnold>   }
[18:45] <sarnold> }
[18:45] <dobey> sarnold: it needs to run pretty much anything, as what it's doing is building a source tree and running the tests for it; and that can vary infinitely wildly across projects
[18:46] <dobey> hmm
[18:46] <dobey> sarnold: but it has to be a full path like /usr/bin? can it be "* cx -> tarmac_child" ?
[18:47] <sarnold> dobey: so you'd want to add something like /**/ r, /** rm, /** ix, /path/to/allowed/writes** w,
[18:47] <sarnold> dobey: it could be /** cx -> tarmac_child
[18:47] <dobey> ok, maybe i can use apparmor to do this then
[18:48] <sarnold> woo :)
[18:49] <dobey> would rather use apparmor than a complex chroot setup
[18:54] <dobey> sarnold: and /**/tarmac will work to match the tarmac script itself, regardless of the install path?
[18:57] <sarnold> dobey: /**/ will only match directories; you'll also need /** for the files
[18:57] <sarnold> (it's a bit confusing the first few times..)
[18:58] <sarnold> dobey: I've got to run, I'll be back in ~two hours.. I hope this is a good enough start for you to get into some trouble :)
[18:58] <dobey> sarnold: yeah, and there are plenty of existing profiles to look at
[18:58] <dobey> sarnold: thanks. i'll probably ask you to review my profile :)
[18:58] <sarnold> dobey: thanks! :) have fun
[19:49] <Noskcaj> roaksoax, kirkland: Can one of you release testdrive? I think we've got enough fixes to warrant it
[19:49] <Noskcaj> And do either of you have time to help with gtk3 and/or python3 porting?
[19:58] <roaksoax> Noskcaj: saucy just openned a few days ago
[19:58] <roaksoax> there's no immediate need to release until at least we have alpha one
[19:58] <roaksoax> however, i'll be releaswing later on the week
[20:02] <stgraber> s/saucy/trusty/
[20:09] <Noskcaj> roaksoax, makes sense, thanks for the info
[20:11] <roaksoax> s/suacy/trusty
[20:23] <dobey> can i get someone to push rhythmbox-ubuntuone from precise-proposed to -updates? it's been in proposed for almost 5 months with no complaints on the bug report about it. and just noticed the verification tag was still -needed, but changed to -done now.
[20:28] <ScottK> dobey: Done
[20:29] <dobey> thanks ScottK
[20:30] <ScottK> yw.
[20:30] <dobey> ScottK: are you sru team btw? i have another favor to ask if so :)
[20:32] <dobey> there's an ubuntu-sso-client in saucy unapproved queue, which is a critical bug fix, that we'd like to get through asap. i uploaded it on friday, but hasn't gotten reviewed yet
[20:33] <ScottK> I'l take a look and if I'm reasonably comfortable with the diff, I'll accept it.  No promises.
[20:34] <dobey> thanks. it's a small and obvious diff, so i'm confident :)
[20:36] <ScottK> dobey: Accepted.
[20:39] <dobey> ScottK: thanks again :)
[20:39] <ScottK> yw again.
[20:45] <cjwatson> jdstrand: your latest click-apparmor upload doesn't seem to be in lp:click-apparmor
[21:02] <mdz> cjwatson, is google calendar telling the truth, that tech board is supposed to meet now?
[21:03] <cjwatson> mdz: Sounds plausible-ish but I hadn't planned to turn up to future TB meetings
[21:03] <cjwatson> mdz: It's 2100 in the UK if that's any help
[21:04] <mdz> who would know for sure? there's no chair on the wiki, etc.
[21:04] <mdz> oh hi pitti
[21:05] <pitti> hey mdz, how are you?
[21:13] <jdstrand> cjwatson: fixed. you keep pointing this out to me. perhaps I will learn some day...
[21:13] <cjwatson> heh, thanks :)
[21:13] <cjwatson> Of course I only notice when I want to propose a change
[21:18] <mdz> pitti, good good
[21:18] <mdz> pitti, going to be in the US anytime soon?
[21:20] <pitti> mdz: not this year any more
[21:20] <cjwatson> mdz: you going to be at the BAD meeting on Wed?
[21:20] <mdz> cjwatson, didn't know about it, and have plans Wednesday evening
[21:20] <cjwatson> ah, shame
[21:20] <cjwatson> in Oakland this week
[21:21] <mdz> I saw jonathan and asheesh last night though
[21:21] <mdz> I didn't know they were having regular get togethers
[21:22] <sergiusens> cjwatson, hey, do you know of any good location to get python3-requests for precise?
[21:22]  * pitti waves good night
[21:22] <cjwatson> mdz: don't know if this is a regular thing, I only know about it from slangasek
[21:23] <cjwatson> sergiusens: nope, I guess it might be possible to backport it
[21:23] <cjwatson> sergiusens: but I'd say that if dependencies are unavailable on precise then that's a good reason to have bilingual code and run it under Python 2 on precise
[21:23] <mdz> cjwatson, slangasek isn't in the bay area now, is he?
[21:24] <mdz> http://bad.debian.net/ lists August 8th 2012 as an 'upcoming event' :-)
[21:24] <mdz> good night pitti
[21:24] <sergiusens> cjwatson, sounds reasonable
[21:24] <cjwatson> mdz: he's with us in Oakland
[21:24] <mdz> oh, just at the moment
[21:24] <cjwatson> yeah
[21:24] <mdz> not relocated
[21:24] <cjwatson> can't imagine prying him loose from Portland
[21:24] <mdz> yeah
[21:25] <mdz> who's there and how long? anyone interested in meeting up?
[21:25] <cjwatson> UE managers and tech leads
[21:25] <mdz> this week is pretty busy for me but we could probably work something out
[21:25] <cjwatson> a few old-timers, I can ask around
[21:49] <hallyn> slangasek: see edk2 thread titled 'OVMF support for QEMU's PC System Flash' - i could be wrong, but i *think* that gives us what we wanted with being able to persist nvvars changes across qemu starts
[22:09] <paulproteus> mdz: Huh, BAD is on Wednesday?
[22:09] <paulproteus> Intriguing.