/srv/irclogs.ubuntu.com/2015/03/03/#ubuntu-devel.txt

=== _salem is now known as salem_
=== salem_ is now known as _salem
=== beisner- is now known as beisner
aeorildarkxst something came up and I will be unable to fix bug 1315442.  I wanted to let you know because I said I would get it in today.  Sorry.  Thanks for all the help.04:26
ubottubug 1315442 in gdm (Ubuntu) "Extra "fi" in /etc/init.d/gdm" [Undecided,Confirmed] https://launchpad.net/bugs/131544204:26
pittiGood morning04:28
pittibdmurray: oh sorry, must have missed that mail then04:28
Noskcajinfinity, ok. For some reason i was under the impression it wasn't a package for all arches. I just keep seeing it on the ftbfs list, but it's not a real issue06:02
Mirvdoko_: seen in qtwebkit, not tested in qttools.. but you may try to add to debian/rules echo "CONFIG -= precompile_header" >> .qmake.conf06:17
Mirvdoko_: I'm seeing hints it'd be globally available, so it could just work06:18
jpdsNoskcaj: Feel free to do it if you want.06:57
=== marcusto_ is now known as marcustomlinson
dholbachgood morning07:31
=== marcusto_ is now known as marcustomlinson_
=== marcustomlinson_ is now known as marcustomlinson
=== rcj is now known as Guest41677
pittididrocks: FYI, bug 1312976 updated with pointer to PPA and TODO list08:10
ubottubug 1312976 in nfs-utils (Ubuntu) "Make NFS client/server work under systemd" [High,In progress] https://launchpad.net/bugs/131297608:10
didrockspitti: great! setting up :)08:14
pittididrocks: note that you need at least rpcbind from -proposed08:14
pittididrocks: https://launchpad.net/ubuntu/+source/rpcbind/0.2.1-6ubuntu2/+build/702747208:14
pittididrocks: apparmor and console-setup will not be started with current vivid packages (see bug), but you can ignore those for a first test08:15
didrockspitti: I can grab them from -proposed anyway, clean vm install in progress :)08:17
pittididrocks: oh, you do a new install for that?08:30
didrockspitti: yeah, an independant vm with another disk08:31
pittididrocks: I usually just start (with -snapshot) adt-vivid-amd64-cloud.img08:31
didrockswell, if I can get vivid to start… :/08:31
didrocksseems no unity in the daily08:31
pittididrocks: err?08:31
pittididrocks: oh, you mean the desktop image08:31
didrocksyeah08:31
pittididrocks: the above is the standard autopkgtest VM, i. e. just minimal stuff08:32
=== marcusto_ is now known as marcustomlinson
didrockswell, screw this for now, manual qemu with the autopkgtest vm then and snaphotting08:32
pittiand redirecting port 22 to not go crazy :)08:32
didrocksyeah ;)08:32
pittimaybe my crappy little "vm" script is worth a G+ post, /me does08:33
didrockspitti: I'm sure it worthes it :)08:34
* didrocks wonders with -snapshot where to specify the file to write to08:35
didrocksyeah, so only temporary, I guess until we stop the vm08:36
pittididrocks: ok, done08:41
pittididrocks: you don't, qemu creates a temp overlay in /var/tmp/08:41
didrockspitti: yeah, so if you want an overlay which can survive host reboot…08:41
pittididrocks: if you want to keep the changes, rather make an explicit snapshot (qemu-img snapshot -c clean-install foo.vm)08:41
pittididrocks: right, or create a new image with your original VM as a base08:41
pittididrocks: most often I don't care, so I don't know that one by heart08:42
pittididrocks: I just record the shell commands to do what I want in the VM, and paste them into ssh08:42
didrocksoh, I wasn't using the -net nic08:42
* didrocks looks08:42
didrockspitti: ok, making sense :)08:43
pittididrocks: qemu-img create -f qcow2 -o backing_file=youroriginalvm.img overlay.img08:43
* didrocks logs this08:44
didrocksthanks pitti, upgrading my adt machine and installing from the ppa08:44
didrockspitti: ok, updated, working here, with the hang you noted on shutdown of course (and so using system_reset to restart it)09:05
pittididrocks: this could just be because nfs-server shuts down before the unmounts09:06
mitya57Mirv: I added sip4 to your FFe (as new PyQt5 needs new sip4, and old PyQt5 doesn't support Qt 5.4.1), and also added changelog links for sip/PyQt509:07
pitticyphermox, slangasek: FYI: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#console-setup09:09
didrockspitti: even if shutdown.target will conflicts against it, maybe we can use some dep on umount.target09:10
pitticyphermox, slangasek: two missing dependencies09:10
Mirvmitya57: oh, thanks, I didn't realize pyqt5 5.4.1 would have such a change09:14
Mirvsip4 release mentions being required for new pyqt5, but the pyqt5 release notes I read do not mention that.09:15
pittididrocks: fixed09:19
didrockspitti: waow, already, how did you deal with this?09:19
pittididrocks: I added Before=remote-fs-pre.target to /lib/systemd/system/nfs-server.service09:20
pittididrocks: i. e. if you have server and client on the same machine, start the server first, then the NFS mounts (client)09:20
pittididrocks: and conversely on shutdown, stop the NFS mounts first, then the server09:20
pittiit's certainly a corner case, but as that's merely ordering without adding deps, it should be okay09:20
didrockspitti: hum, but it means we starts the nfs server before having any network? I guess nfs copes with it09:21
pittididrocks: is that bad?09:22
pittididrocks: nfs-server still Requires: network.target09:22
pittididrocks: (not network-online.target)09:22
didrockssystemd.special(7) doesn't seem to note anything wrong about it09:24
didrocksso yeah, nice trick for that corner case!09:24
pittididrocks: hm, for testing server and client separately, we would now need two QEMUs which talk to each other09:29
pittididrocks: do you happen to know the magic -net invocation for that? I naïvely tried -net bridge,br=lxcbr0 (wanting to piggy-back on LXC's) but that doesn't work09:29
pittididrocks: I'd like to verify whether 24-systemd-modprobes.patch is still actually required (upstream/fedora doesn't have it)09:30
infinitypitti: Here's an example of tun/tap bridged networking from a buildd: http://paste.ubuntu.com/10513248/09:35
pittiinfinity: oh cool, thanks09:36
infinitypitti: notably, the -net nic -net tap,script stuff, and then the script itself.  Which might exist on Ubuntu in a cleaner form in /etc/qemu but doesn't on this awful Fedora base system I'm using. :P09:36
didrockspitti: I would have used the bridge option as well, just tried but without any success either09:36
infinityBonus points to the first person who recognizes the MAC address space our buildds are using. :P09:38
pittiinfinity: haha, Atari!?09:40
pittiinfinity: so Atari:leet:40, no idea about the 4009:41
infinitypitti: The odds of clashing on the same physical segment with a real computer seem slim. ;)09:41
infinitypitti: The last byte is assigned by the order I spun the VMs up in and assigned IP addresses, I think.09:42
infinitypitti: But the real question is, did you have to look up 000036, or was that strange nugget of knowlegde stored away in that part of your memory that really shouldn't know such things?09:43
pittiinfinity: nah, I looked it up09:43
pittiinfinity: I remember a few from maintaining udev's 75-persistent-net-generator.rules, but for some strange reason I never ran into the Atari prefix :)09:44
infinitypitti: Sadly, unlike PCI IDs, MACs seem to be less gimmicky, and thus harder to remember.09:46
infinity(Though, there is 8086:F2, and 3C0000)09:47
infinity3C0000 being particularly cute, since that's 3C0M09:47
pittioh, nice! I would have missed the Roman numeral hint09:48
cjwatsonpitti: So ... we're probably at most weeks away from being able to flip the real-ddebs switch in Launchpad10:00
=== doko_ is now known as doko
cjwatsonpitti: But we don't want to inject the existing ddebs back into Launchpad, since we're not certain enough of their provenance in all cases, so the plan per William is to make ddebs.ubuntu.com slurp from Launchpad proper rather than the buildds after we flip the switch, until such time as we've rebuilt everything (say, after 16.04) and can publish a proper full archive from LP10:02
cjwatsonpitti: Are you likely to have a bit of time to make the necessary ddeb-retriever changes?10:02
=== Malsasa_ is now known as Malsasa
pitticjwatson: good to hear!10:02
pitticjwatson: I'm on VAC from March 16 to 25, but I don't expect this to be more work than a day or so; so as soon as we have some ddebs in LP (or staging) to test against, I can carve out some time10:03
cjwatsonpitti: I could probably do some in dogfood for you10:04
infinityCould test against a PPA with ddebs.10:05
cjwatsonOr that10:05
infinityBut the primary archive is a better final test, yes.10:05
cjwatsonpitti: The main trick is how to do the catch-up thing; I was thinking that you could use Archive.getPublishedBinaries(created_since_date=), and remember the latest ddeb you've successfully fetched10:05
cjwatsonPerhaps10:05
cjwatsonpitti: But if you need extra stuff on the webservice, that can be arranged - we just need to know what sort of shape of thing you need10:06
infinitycjwatson: I was thinking one would walk Packages.gz and map back, and keep a note of ones you've already fetched, so future runs are only getting deltas.10:06
cjwatsoncreated_since_date would achieve deltas too ...10:06
pitticjwatson: yes, that's what I was going to do; wgrant and I discussed that before, I think10:06
cjwatsonThe problem with walking Packages is that you don't know which ones *need* ddebs.  You could certainly keep a note of the ones that fail, but the first run would be exceedingly slow10:07
pittiddeb-retriever already walks Packages.gz and creates an archive map (it has to right now), but I think created_since is fine10:07
wgrantNot *fatally* slow.10:07
cjwatsonI don't have enough of a feel for ddeb-retriever to know which approach is best/easiest, though.10:08
pittiiterating over a hundred builds a day is certainly faster than iterating over 30.000 packages10:08
wgrantcreated_since with a bit of a fudge factor probably makes sense, but it would need care around eg. series initialisation to avoid making $lots of requests.10:08
wgrantSo it would probably want to keep a record locally of what it already had.10:08
cjwatsonYeah10:08
pittithe current approach is queue based, too -- i. e. "Fetch all ddebs from $given_day", then sort them in10:08
cjwatsonDamnit why is *_debug_symbols on archives a state secret10:08
cjwatsonAha, ppa-self-admins to the rescue10:09
cjwatsonwgrant: So ubuntu.main_archive will get build_debug_symbols=True but publish_debug_symbols=False (until we have enough of the archive to do a real publisher), is that right?10:10
infinitycjwatson: Unless we do a "screw old binaries, let's rebuild the world" flag day, that real publisher thing may never come.10:11
wgrantcjwatson: Well, enough of the archive and archive views, really.10:12
infinityI guess a gina-like import of old ddebs to glue them to the build records where they belong was just deemed too hard/dangerous?10:12
wgrantUnless we want a few terabytes on $new_pepo10:12
wgrantinfinity: Yes, I do not want to do that unless we have no option.10:12
wgrantBecause we know that ddeb-retriever is fallible.10:12
wgrantAnd the Launchpad database is a rough approximation of infallibility.10:12
infinityYeah, there may be cases where ddeb-retriever accidentally published a PPA version instead of a PRIMARY version, etc.10:13
wgrantUploading ddebs to random builds is not hugely helpful.10:13
wgrantYep, exactly.10:13
wgrantSo the plan is that we have a clean break and pretend that we'll rebuild everything before 16.04.10:13
infinityWhich we won't.10:14
infinityBut maybe we'll rebuild everything that matters.10:14
wgrantYep.10:14
infinityOnce we have an archive implementation that finally doesn't suck, I might try to find motivation to make the actual generation less hackish and contribute it back to Debian.10:15
infinitySince every conversation there has just spun in circles and given them exactly nothing to show for it.10:15
wgrantIn the immediate term the archive generation will continue to be ddebs.ubuntu.com, as today.10:15
mgedminany thoughts about replacing ddebs with symbol servers indexed by build-id (as described in https://randomascii.wordpress.com/2013/02/20/symbols-on-linux-part-three-linux-versus-windows/)?10:15
wgrantOnce we have diskless archives, we can publish post-LP-enablement ddebs for very little disk space indeed.10:16
wgrant(we could work out some solution to publish them physically on pepo, but that really doesn't seem worth it)10:16
cjwatsonpitti: So, examples: https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/ppa has build_debug_symbols=True and publish_debug_symbols=True; https://code.launchpad.net/~unity-team/+archive/ubuntu/phone-right-edge/+packages has build_debug_symbols=True and publish_debug_symbols=False.  Either should do for your purpose.10:16
wgrantbuild_debug_symbols does what it says on the tin.10:17
wgrantpublish_debug_symbols is a bit more complicated: they get binary_package_publishing_history records, and they get set to Published as normal, but they never actually hit the archive pool or indices.10:17
pittimgedmin: it's a really nice way of distributing them, but I guess needs design and thinking around authentication and mirroring10:17
pittiinfinity: thanks for the -net tap hint, works great!10:18
wgrantinfinity: I was pleasantly surprised this morning to find that we don't have to SRU anything, because I made the relevant changes to pkg-create-dbgsym back in 2009...10:18
pittididrocks: FYI, http://piware.de/tools/vmbr is similar to vm, just with that -tap thing, so that VMs can talk to each other and with LXC containers10:18
infinitypitti: At the end of the blog post, he suggests just enhancing Packages to list the buildids that each ddeb maps to.10:19
infinitypitti: That wouldn't be an unreasonable approach, and then both "install by package" and "search by buildid" work.10:19
pittiinfinity: eww -- that's a *lot* of bloat10:19
didrockspitti: oh, excellent!10:19
pittiI'd say that can easily double the Packages size10:19
cjwatsonIt'd be much nicer to have something that serves the individual debug object rather than the whole ddeb, too.10:19
mgedminit also wouldn't help with getting symbols for ppa packages10:19
pittiright10:20
infinitypitti: It is, yes, and having the index server side instead of client side might be more pleasant, but doesn't really fit in an aptish world.10:20
pittiyou want http://debug.ubuntu.com/d/de/deadbeef133710:20
cjwatsonPutting it in LP would let us security-proxy it so that it works for private archives etc.  But it'd be a lot of data and a fairly large new service.10:20
didrockspitti: hum, the second is saying that the device is busy though10:22
pittididrocks: hold that, it's broken10:22
cjwatson(And with some kind of diskless view you could still mirror the public parts)10:22
infinityIt's certainly worth some thought, but without external contribution, I don't see it  happening.10:23
infinityNot in a timely fashion anyway.10:23
sil2100@pilot in10:24
=== udevbot changed the topic of #ubuntu-devel to: Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: sil2100
xnoxthere is a fuse filesystem for debug symbols.... when attempted to be accessed they are fetched from http server...10:50
pittislangasek: I now have working NFS under systemd, under various scenarios; bug 1312976 updated; would you like to review the debdiff and comment, or shoudl I just upload?11:26
ubottubug 1312976 in nfs-utils (Ubuntu) "Make NFS client/server work under systemd" [High,In progress] https://launchpad.net/bugs/131297611:26
xnoxpitti: i have another thing to ponder with you. In ubuntu dbus-daemon is shipped in /bin, rather than /usr/bin.11:27
xnoxpitti: however i do not believe this to be necessory, if not wrong.11:28
pittixnox: yeah, ancient modification; probably because upstart needs it early on?11:28
pitti(I never knew/understood why we need it)11:28
pittiit's certainly not wrong, but a moderately annoying delta when merging11:28
xnoxpitti: the comment from keybuk was "start it earlier" -> but in practice all dbus daemons are in /usr/11:28
xnoxpitti: upstart doesn't need it, as it opens it's own private bus socket and uses that. And it does operate fully without dbus-daemon ever getting started.11:29
xnox(unlike systemd/logind)11:29
pittiand under sytsemd dbus starts After=basic.target, i. e. after local-fs.target11:30
xnoxpitti: upstream we are pondering to move /etc/dbus-1 -> /usr/share/dbus-1, and a question came up whether this will or will not "break ubuntu's /bin"11:30
xnoxpitti: yeap.11:30
xnoxpitti: i want to move dbus back to /usr, may i test & prepare a patch to do so?11:30
pittiso from my POV I'm happy to drop that delta -- it has caused some pain in various places11:30
xnoxpitti: /server work under systemd" [High,In progress] https://launchpad.net/bugs/131297611:30
xnox* darkbasic_ (~quassel@niko.linuxsystems.it) has joi11:30
ubottuLaunchpad bug 1312976 in nfs-utils (Ubuntu) "Make NFS client/server work under systemd" [High,In progress]11:30
xnoxbah, bad url11:30
xnoxpitti: https://bugs.freedesktop.org/show_bug.cgi?id=8928011:30
pittixnox: go ahead11:30
ubottuFreedesktop bug 89280 in core "support ignore_missing attribute in the includedir element, and use that to support all default configuration in datadir" [Normal,New]11:30
pittixnox: the previous was a copy&paste error? or does that apply to NFS?11:31
xnoxpitti: copy&paste error.11:31
pittixnox: and yay for throwing out /etc/dbus-1/system.d!11:31
pitti(or all such policies, really)11:32
xnoxpitti: =)11:32
pittia user can put an updated one into /etc, but we shouldn't put the defualt ones there11:32
xnoxpitti: that's what my patches there achieve.11:32
pitti\o/11:32
xnoxpitti: ditto patches to systemd -> to make policies generate .want symlinks in /run, rather than /etc.11:33
xnoxpitti: and a bunch of similar patches for other projects as well.11:33
LocutusOfBorg1hi sil2100 did you already upload vbox?11:33
xnoxnot everything is forwarded to upstreams yet.11:33
LocutusOfBorg1feel free to rename the patch if you didn't already upload the package11:34
LocutusOfBorg1yes, a number might be better for future uploads11:34
xnoxpitti: i see upstartisms in dbus.postinst =/11:39
xnoxpitti: is there a way to do archive-wide scan for these?11:39
* xnox guesses lintian.11:39
pittixnox: where?11:40
pittilooks fine to me at first sight11:40
xnoxpitti: http://paste.ubuntu.com/10514296/11:40
pittixnox: ah, so s/status/service/?11:41
xnoxpitti: well, and then check for return code, rather than 'upstart formatting of pid #' and need to check that service status under both upstart & systemd outputs the same exit codes.11:42
xnoxpitti: do you have lintian lab or some such way to scan all .deb's maintainer scripts to make sure they don't call initctl / upstart naked commands?11:43
xnoxq11:43
xnoxZZ11:43
xnox:wq!11:43
pittiI don't, no; do we still have the codesearch setup for ubuntu?11:45
xnoxpitti: well i only provide dns for it http://ubuntu-codesearch.surgut.co.uk/ and it points into 502 inside canonistack.11:47
xnoxLaney: are you running codesearch still?11:47
=== MacSlow is now known as MacSlow|lunch
Laneynein11:47
xnoxLaney: warum nicht? =)11:48
LocutusOfBorg1hi all :)11:48
Laneykeine zeit11:48
Laneybasically it kept breaking11:49
Laneythe easiest way I know of atm is to ask j_dstrand to do a grep for you11:49
xnoxLaney: well, i want to grep for "upstartisms" in the .deb maintainer scripts.11:50
xnoxLaney: e.g. dbus postinst calls "status dbus | ...." for a non-upstart specific code-path.11:50
LaneyI believe you have a good usecase11:50
Laneybut I'm afraid that codesearch isn't deployed atm :(11:50
pittiflexiondotorg: did you ever happen to run MATE under systemd? any problesm there which would block switching to it by default?11:52
Laneymaybe we could at some point look at doing it again11:52
xnoxpitti: i still have bits that are not ported on the phone for pid1 systemd.11:52
xnoxpitti: so at least touch, should be kept on upstart for the time being.11:53
pittixnox: yeah, phone won't switch for sure11:53
pittixnox: just added a work item and discussed with ogra in #u-touch11:53
pittixnox: most touch devices have too old kernels (3.4), that'll block the switch until touch moves to a newer android11:53
xnoxpitti: really? why? what's needed / missing?11:54
ogra_pitti, i doubt we will ever get a newer android for the released phones11:54
ogra_and even then it is doubtful that they will have any newer kernels11:54
xnoxpitti: can't we just patch xattr support back in? http://cgit.freedesktop.org/systemd/systemd/commit/?id=d2edfae0f9bdbecf6a8518e2a5bcf06f470e0d9e&ss=111:54
flexiondotorgpitti, I'm also an Arch TU so I've been running MATE on systemd for a couple of years now 😃11:54
pittiyeah, I wasn't saying "next week", this will still be a few years in the worst case11:55
ogra_i think the only way would be to backport missing bits11:55
flexiondotorgpitti, We did the systemd support for MATE a good while back.11:55
xnoxpitti: or like backport xattr support for cgroups.11:55
pittiflexiondotorg: right, but I meant on Ubuntu? I don't expect problems, but I'd like to get a confirmation from each flavor that it doesn't break stuff11:55
flexiondotorgpitti, The transition from Ubuntu 14.10 to 15.04 was seamless. No systemd issues that I've encountered.11:55
ogra_xnox, our prob here is that porters will have to do the same ... we dont want that porting turns into a kernel patching orgy11:55
flexiondotorg*from Ubuntu MATE 14.10 to 15.0411:55
xnoxogra_: it already is, e.g. we mandate apparmor.11:56
pittiflexiondotorg: the default is still upstart, you need to opt-in (boot systemd in the grub menu or isntall systemd-sysv)11:56
xnoxflexiondotorg: 15.01 doesn't use systemd-sysv yet.11:56
flexiondotorgpitti, Confirm systemd looks good on Ubunut MATE 15.04 currently :)11:56
pittiflexiondotorg: ok, thanks!11:56
ogra_xnox, right, patching our apparmor in means essentially "delete the upstream apparmor folder in your tree and copy ours in place"11:56
tjaaltonpitti: I'd say upload nfs-utils now, it doesn't affect current upstart users anyway11:56
flexiondotorgxnox, pitti You say systemd is not default?11:56
flexiondotorgHow do I fully opt it exactly?11:57
ogra_xnox, if we can make the systemd patching as easy, then yes, not an issue ... but i fear it will take a bit more there11:57
xnoxflexiondotorg: correct, you need to install systemd-sysv packge to test that ubuntumate works with systeemd as pid 1.11:57
pittiflexiondotorg: https://wiki.ubuntu.com/SystemdForUpstartUsers#Switching_init_systems11:57
cjwatsonwell no you don't11:57
cjwatsonyou can just as well use the grub menu entry11:57
flexiondotorgpitti, So I can modify my seeds and rebuild then?11:57
pittithe wiki page shows both methods11:57
flexiondotorgpitti, Will gladly test that.11:57
pittiflexiondotorg: nah, not necessary11:57
pittiflexiondotorg: also, you can't -- ubuntu-minimal is shared between flavours11:58
xnoxcjwatson: true, but that wouldn't catch things that calls "/sbin/init" expecting to start upstart user session and things like that. Although, I believe i fixed all of those by now.11:58
flexiondotorgpitti, OK, understood.11:58
xnox(e.g. lightdm greeters spawning "init --user" to run indicators.....)11:58
pittialso, these ^ shoudln't be desktop specific, but better safe than sorry :)11:58
flexiondotorgpitt, I'll do an inplace test now.11:58
flexiondotorgpitti, xnox Is the switch to systemd planned for 15.04?11:59
mardypitti: hi! I'm a bit rusty with dbus python: I want to return a DBus error from a mocked method, how do I do that?11:59
pittiflexiondotorg: yes, still; I'm currently writing an FFE11:59
sil2100LocutusOfBorg1: ouch, already uploaded it as it was...12:04
pittislangasek: FYI, filed bug 142765412:05
ubottubug 1427654 in ubuntu-meta (Ubuntu Vivid) "FFE: switch system init to systemd [not touch] in 15.04" [Undecided,New] https://launchpad.net/bugs/142765412:05
sil2100LocutusOfBorg1: might consider re-uploading or something, but I suppose it shouldn't be a big problem12:05
sil2100@pilot out12:05
=== udevbot changed the topic of #ubuntu-devel to: Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
xnoxpitti: i'm not sure if $ service dbus status -> is useful under systemd.12:05
pittixnox: why not?12:07
xnoxpitti: well, i guess i will use systemctl -q is-active dbus12:08
xnoxpitti: service dbus status -> outputs a bunch of colored output and exits zero.12:08
pittiright, and it exits with 3 for non-running jobs12:09
ogra_just write an AI that can judge the colors12:09
pitti>/dev/null obviously required :)12:09
pittitjaalton: yeah, it's tempting, but I guess I'll give slangasek at least a chance to review before I upload12:11
xnoxpitti: ok that should work. let me check this under upstart as well and switch to service command then.12:11
pittimardy: look into e. g. the bluez4.py template: raise dbus.exceptions.DBusException('org.foo.bar', 'not foobarized')12:12
pittixnox: so what Debian does should actually work fine?12:13
=== _salem is now known as salem_
pittixnox: calling /etc/init.d/dbus is not the most efficient as it needs to go through the lsb script, but it should work12:13
pittibut *shrug*, it's not like it matters12:14
xnoxpitti: well, "$ service dbus status" under upstart gives: "dbus stop/waining" and exits 012:15
xnox=(12:15
pittibah12:15
xnox(in a single user mode, as otherwise stopping dbus under upstart brings the systemd down)12:15
pittiyeah, try that with anacron or somethign harmless :)12:16
xnoxpitti: i'm not proud http://paste.ubuntu.com/10514602/12:20
flexiondotorgpitti, pitti install systemd testing is going well on Ubuntu MATE. Actually resolves a shutdown issue I've been having :)12:21
pittixnox: hm, that still doesn't work for Debian under sysvinit? can we do a "if <runnign under upstart> status else /etc/init.d/dbus status"?12:22
pittixnox: also, why doesn't /etc/init.d/dbus status work? /lib/lsb/init-functions.d/01-upstart-lsb shoudl divert it to status already?12:23
xnoxlet me check exit codes.12:23
pittiflexiondotorg: nice, thanks! once you are sufficiently convinced that it doesn't break stuff, woudl you mind sending something like "confirming that MATE works with systemd" to bug 1427654?12:24
ubottubug 1427654 in ubuntu-meta (Ubuntu Vivid) "FFE: switch system init to systemd [not touch] in 15.04" [Undecided,New] https://launchpad.net/bugs/142765412:24
xnoxpitti: (a) 01-upstart-lsb is in ubuntu only (b) /etc/init.d/dbus status exists zero here under upstart and dbus not running.12:24
pittiok, so 01-upstart-lsb is broken12:24
pittixnox: I guess Debian doesn't care much about this, and we can drop that delta next cycle (hopefully), so then just go with your's12:25
flexiondotorgpitti Will do.12:25
flexiondotorgpitti I noticed that plymouth didn't appear. Is this by design?12:25
flexiondotorgpitti, I only ask because I remember the back lash when Arch switched to systemd.12:25
xnoxflexiondotorg: depends if plymouth is integrated correctly on mate.....12:26
xnoxflexiondotorg: it works under systemd on ubuntu-unity12:26
flexiondotorgpitti, Just need to know if I need to find my flame proof trousers again.12:26
flexiondotorgxnox, Prior the adding systemd I have a slow boot and Plymouth. After adding systemd VM boot waaaaay faster.12:27
flexiondotorgThinking I might not be seeing plymouth because X was hammered up that much quicker.12:27
pittiflexiondotorg: no, should work12:27
xnoxthere is plymouth in VMs.12:27
flexiondotorgpitti, Thanks.12:27
pittiplymouth in VM is a bit fiddly, though12:27
mardypitti: excellent, thanks!12:27
flexiondotorgxnox, VirtualBox VM with Ubuntu MATE in it.12:27
pittiflexiondotorg: often the VM is too fast, and you don't actually see it; or the graphics driver (like qemu's default one) causes some corruption12:28
pittiit usually shows better on real iron, or with e. g. qemu's -vga std12:28
flexiondotorgpitti, xnox - Anyway to test Ubiquity install with systemd installed?12:28
pittiflexiondotorg: yes; append "init=/bin/systemd" to the kernel command line in gfxboot12:29
flexiondotorgOf course. Thanks.12:29
pittiflexiondotorg: i. e. press a key to get the menu, press F6 to get the expert menu, press Esc twice to close it again12:29
pittiflexiondotorg: then you can edit the kernel command line12:29
pittiflexiondotorg: (I tested that on ubuntu a few months ago)12:29
flexiondotorgpitti Yep, done it.12:30
mdeslaur@pilot in12:39
=== udevbot changed the topic of #ubuntu-devel to: Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mdeslaur
flexiondotorgpitti, One issue with systemd enable during install.12:42
LocutusOfBorg1sil2100, maybe I can rename in the next upload :)12:43
flexiondotorgpitti, When I click restart it does just that. No prompt to remove the media.12:43
LocutusOfBorg1or I can ask -release to reject but I guess it should be fine12:43
LocutusOfBorg1I do not really care about them12:43
* dholbach hugs mdeslaur12:53
* mdeslaur hugs dholbach back12:53
=== MacSlow|lunch is now known as MacSlow
pittiflexiondotorg: ah, bug report appreciated; thanks for testing!13:27
dokojamespage, which packages build-depend on gccgo-go? just juju-core?13:27
dokohttps://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/142767613:30
ubottuLaunchpad bug 1427676 in juju-core (Ubuntu) "juju-core should drop the b-d on gccgo-go and libgo5, using gccgo instead" [Undecided,New]13:30
flexiondotorgpitti, Will test some more befre I raise bugs.13:30
dokopitti, jibel: looks like a lot of the i386 perl related autopkg tests need a give back13:39
cjwatsonThis is why I always sync perl by copying it into a devirt archive and then copying with binaries to the main archive ...13:40
dokonoticed for the future ...13:41
cjwatsonAfter one too many situations where I wound up with perl being uninstallable and unbuildable in -proposed13:41
pittidoko: yep, I got the bunch of errors, I'll lean on the retry button13:41
=== kickinz1 is now known as kickinz1|afk
=== kickinz1|afk is now known as kickinz1
=== Guest41677 is now known as rcj
=== rcj is now known as Guest72440
jdstrandpitti: hey, fyi re bug #1312976, apparmor may load files from /var14:17
ubottubug 1312976 in console-setup (Ubuntu) "Make NFS client/server work under systemd" [Undecided,In progress] https://launchpad.net/bugs/131297614:17
pittijdstrand: hey14:18
jdstrandpitti: is /var expected to be nfs-mountable?14:18
pittijdstrand: ah, and we want to support NFS on /var?14:18
jdstrandthat's the question14:18
pittijdstrand: ok, we could flip that around, if we don't care about protecting all the NFS stuff by apparmor?14:18
jdstrandI don't think I can answer that-- I'm not up on the issue14:18
jdstrandpitti: so, when cache loading hits and we have proper systemd support for apparmor, the initscript would become a second stage loader to update the cache. I thihnk it could have remote_fs then14:19
jdstrandbut we don't have that right now, so not sure what the best course of action is in this transition period14:20
jdstrandsbeattie: fyi (systemd/apparmor backscroll) ^14:21
pittijdstrand: ah, ok; so I'll see to breaking the dep cycle in some other way14:21
jdstrandok, it seems like it might be easier for now14:22
=== kickinz1 is now known as kickinz1|afk
jdstrandwell and in the future :)14:22
pittijdstrand: ok; I was a bit concerned about your "start apparmor as early as possible" request, but if you are happy with starting NFS before, I'm ok with that14:23
pittifun, that's the third time when the need for a /cache/ pops up14:24
pittii. e. early-boot cache which is guaranted to be available without NFS, separate partitions, and stuff14:24
jdstrandpitti: happy is strong. we will have apparmor start as early as possible with the cache loading work14:24
pittijdstrand: well, then the cache can't go on /var14:25
jdstrandit is a bit unfortunate for the initscript since there are profiles available for portmap iirc14:25
jdstrandthere are two caches> system cache in /etc and snap/click cache in /var14:27
pittijdstrand: ah, so once we split the startup scripts into system/click that'd work?14:27
jdstrandmaybe14:27
pittijdstrand: cache in /etc/ is really ugly too, though14:28
pittijdstrand: perhaps /lib/apparmor/ ?14:28
pittijdstrand: hwdb.bin is a similar case, I ended up putting it into /lib/udev/14:28
jdstrand /etc is a historical artifact14:28
jdstrandwe've discussed moving /etc/apparmor.d/cache in the past. looks like we'll need to discuss it again14:29
jdstrandthe thing is-- currently snaps with systemd jobs have their cache in /var/cache/apparmor. I think those units all have Requires=apparmor.service14:31
jdstrandso they should be ok14:31
pittijdstrand: on snappy and touch that shouldn't matter at all; we ship a single root fs, no /var on NFS14:32
jdstrandbut I feel like we need to revisit the cache locations and timing of things for when libapparmor supports cache loading (and therefore systemd can use it)14:33
jdstrandtyhicks: fyi (please see backscroll for last 15 minutes or so)14:33
pittijdstrand: ok, so for now you want me to revert that, and have NFS start before apparmor?14:33
jdstrandpitti: I think for today, that is the best option14:34
pittiand we revisit after the cache work/job split?14:34
pittijdstrand: ack; thanks for the heads-up! sorry for the misunderstanding14:34
jdstrandpitti: I noticed on snappy the other day dhclient was running unconfined. if we don't land the cache work, we'll need to deal with that in some way. perhaps some of that thinking might be put towards portmap profile14:35
jdstrandpitti: thanks for the discussion-- now we'll think about it and discuss it as upstream14:36
dokoxnox, boost ping14:37
xnoxdoko: yo, what about it?14:37
* xnox doesn't recall a boost ping - you mean gcc5 fixing?14:38
doko=)14:38
dokoxnox, afaiu 1.57 is ready for GCC 514:38
xnoxdoko: *sigh*14:39
xnoxdoko: i could transition, but in W not in V14:39
dokoyeah, v is a bit late ...14:40
xnoxdoko: well, and debian experimental i guess14:40
pittijdstrand: hm, that's tricky; this means that network.target, pollinate, and more all need to sort themselves before apparmor, on really early boot14:52
dokotjaalton, you're the X guy, aren't you? xauth gained new b-d's. could you file MIR's?14:58
dokodidrocks, https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731   this still has the recommends. is this intended?15:00
ubottuLaunchpad bug 1394731 in grilo-plugins (Ubuntu) "[MIR] grilo-plugins" [Undecided,Fix committed]15:00
didrocksdoko: I guess the deal was to not promote that binary15:02
didrocksdarkxst: that's right, isn't it? ^15:02
smoserhey..15:03
smoseri have a problem seems like might ave been solved before.15:04
smosercurtin runs in python2[.7] or python3.15:04
smosercloud-images in vivid no longer have python-yaml (python2)15:04
smosercloud-images in precise do not have python3-yaml (or python3 at all).15:05
tjaaltondoko: ok15:05
smoserwhat i'd like is a /usr/bin/python3or2 that ran 3 if possible, otherwise ran 215:05
smoseri'm guessing that is a problem that someone else has seen  and solved.15:06
smoserbarry, ^ maybe ?15:06
pittijdstrand: just for the rationale: currently /var/cache/apparmor/ is empty for me -- why is it needed to have /var for apparmor?15:07
pittijdstrand: (other than on touch/snappy where /var on NFS isn't an option)15:07
dokosmoser, I don't think this can work, because you can't ensure that every module is provided for one interpreter15:08
barrysmoser: the windows launcher has that iirc.  it's been discussed several times in various python forums, but so far nothing exists for *nix afaik15:08
pittijdstrand: i. e. right now the cache actually is in /etc/? or am I missing anything?15:09
smoserdoko, well, with the help of a 'python -m some_checker_module' you could.15:09
slangasekpitti, cyphermox: ok, looks like we should just drop the console-setup-freebsd binary package, thanks for the pointer15:09
tjaaltoncjwatson: do you remember why our xauth is marked M-A: foreign? to fulfil some cross-arch dependency?15:09
smoserand in this simplistic case , it'd be good enough to 'python3 -c "sys.exit(0)"' as a test.15:10
barrymake be should call it /usr/bin/python2.8 :)15:10
barry*maybe we* -- jeebus15:10
cyphermoxslangasek: agreed, I was working on that just now15:12
slangasekcyphermox: great, I'll leave you to it15:13
pittijdstrand: also, /etc/init/apparmor.conf runs before NFS and mounting /var too?15:13
jdstrandpitti: /etc/apparmor.d/cache is for any profiles in /etc/apparmor.d. profiles shipped in debs are put in /etc/apparmor.d/15:15
dokosmoser, but how do you express this using package dependencies?15:16
jdstrandpitti: /var/cache/apparmor is for any profiles in /var/lib/apparmor/profiles. profiles for clicks and snaps are generated and put in /var/lib/apparmor/profiles15:16
pittijdstrand: right; my question was (1) what is in /var/cache/apparmor (I don't have that here), and (2) if that's important, how does /var on NFS work under upstart?15:16
ogra_pitti, click app profiles15:16
ogra_(which we plan to support on desktop iirc)15:17
pittiogra_: right; but I still fail to see how you can have /var/lib/apparmor on NFS under upstart15:17
pittiit's a pretty drastic cyclic dependency15:17
pitti(and we don't currently have it)15:17
ogra_no idea, i havent use NFS in 8 years or so :)15:18
pitti/etc/init/apparmor.conf is "start on starting rc-sysinit", it makes no effort to wait for NFS or /var etc.15:18
ogra_(on the phone it has ano override ... that set "start on lightdm")15:19
ogra_err15:19
ogra_start on startin15:19
ogra_g15:19
jdstrandpitti: I don't recall if NFS /var and apparmor worked with apparmor. perhaps mdeslaur recalls? istr we may have discussed it15:19
cjwatsontjaalton: It can be depended on to provide an interface (i.e. /usr/bin/xauth), isn't coinstallable with other versions of itself, and that interface isn't architecture-dependent; that's reason enough15:20
cjwatsontjaalton: I expect there was probably a dependency or build-dependency somewhere that made this useful, yes, though I don't remember what15:20
cjwatsontjaalton: Oh, I filed a Debian bug and gave some reasoning.  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=69508715:21
ubottuDebian bug 695087 in xauth "xauth: Please mark Multi-Arch: foreign" [Wishlist,Open]15:21
jdstrandpitti: apparmor aside, I think we are getting back to the previous question-- is NFS mounted /var even expected to work on Ubuntu at all?15:22
jdstrandand I don't have an answer to that15:22
pittijdstrand: I don't know :/15:22
jdstrandseems logging would break pretty hard15:22
mdeslaurpitti: yes, but rc.sysinit is start on filesystem15:22
pittiwell, people might expect it :) but I have no idea whether it actually works15:22
jdstrandslangasek: hey-- is /var mounted on NFS supposed to work?15:22
mdeslaurpitti: filesystem includes local-filesystems and remote15:23
smoserdoko, yeah, from a package perspective not easily solved.15:23
pittimdeslaur: ah, ok; so under upstart we also let rpcbind, the nfs daemons, pollinate, and whatnot run before, so that we can't apparmor-protect them?15:23
pittiwe can do that, it just seems the wrong way around to me15:24
mdeslaurpitti: right, but we do need to protect the dhclient that gets run as part of the network interface coming up15:24
jdstrandwith upstart we had a bunch of patches for updating upstart jobs15:24
slangasekjdstrand: I'd say it's known to not work, because of /var/lib/nfs15:24
jdstrandslangasek: oh, heh15:24
mdeslaurpitti: which is why apparmor cache is in /etc, and not in /var15:24
pittimdeslaur: but then /etc/init/apparmor.conf would run too late?15:25
jdstrandmdeslaur: so, there is /var/cache/apparmor for clicks/snaps. we may need to rethink that15:25
ogra_pitti, bug 525154 claims it worked once (after this was fixed)15:25
ubottubug 525154 in nfs-utils (Ubuntu Natty) "mountall for /var or other nfs mount races with rpc.statd" [High,Fix released] https://launchpad.net/bugs/52515415:25
pittimdeslaur: right; I think it's correct to have apparmor caches on the root fs (just perhaps not in /etc/, but that's a different question)15:25
slangasekjdstrand: there are some things that can be moved to /run (and have been), but /var/lib/nfs is used for the lock state across reboots... not sure what we do with that, except for perhaps breaking lockd15:25
mdeslaurpitti: yes, which is why we have apparmor hooks in a whole slew of other upstart jobs and the ifup scripts15:25
tjaaltoncjwatson: oh good, I'll check that and commit it there if pkg-xorg doesn't oppose15:26
jdstrandour goal with proper apparmor cache loading and systemd is to clean all this up15:26
mdeslaurjdstrand: yes, but at that point, /var is guaranteed to be mounted15:27
jdstrandmdeslaur: yes, but when we have the libapparmor patches, it may not be15:27
mdeslaurjdstrand: oh, wait, you're using that for snaps now, yeah, that's no good15:27
mdeslaurjdstrand: it was ok with click packages, but not for snaps15:28
jdstrandmdeslaur: snaps are actually covered cause they depend on apparmor15:28
jdstrandin their job file15:28
jdstrandRequires=apparmor.service15:28
pitti(After=, I hope)15:28
jdstrandAfter=apparmor.service15:28
jdstrandyes, both15:28
mdeslaurjdstrand: and apparmor depends on all the local filesystems?15:28
mdeslaurincluding /var?15:28
jdstrandmdeslaur: well, that is what pitti is looking at15:29
pittimdeslaur: local-fs, yes15:29
mdeslaurright15:29
pittimdeslaur: the question was about $remote_fs -- i. e. if /var is on NFS15:29
pittiIMO we should not have caches which we require on early boot on a potential NFS dir, it's just crying for trouble15:29
pitti(and as you said yourself, it's a pain to get to work)15:30
mdeslaurright15:30
jdstrandmdeslaur: I think we need to discuss this with tyhicks and sbeattie. we should be collecting the requirements here and add them to what we know, then come up with a plan15:30
* jdstrand has to go to a meeing15:31
mdeslaurjdstrand: the plan is to move apparmor to the right place in systemd15:31
pittiwell, we could split it15:31
jdstrandmdeslaur: yes. and that may mean we move dirs around15:31
pitti/etc/init.d/appamor for loading /etc/apparmor for early boot, and another one for /var for clicks etc.15:31
pitti(or keeping /etc/init.d/apparmor for the late one, and an apparmor-early for the early boot)15:31
jdstrandwe already know we need 2 stages: first to load caches, and the next to regenerate the caches in case they are out of date15:31
pittior declare that you can't have click/snap packages with /var on NFS15:32
jdstrand(since libapparmor will only load caches, not compile them)15:32
mdeslauryeah, we could split it out15:32
mdeslaurbut if /var on nfs is known not to work at the moment, perhaps we don't care15:32
pittiit's not known to work; it hasn't been shown to not work15:33
pittimdeslaur: the trouble would only be with /var on NFS on a system which uses click, right?15:33
cjwatsontjaalton: Probably shouldn't, I expect it's just an oversight - I think pkg-xorg has accepted other similar stuff from me15:33
pittibut on the pro side we'd have all the networking/NFS/portmap/DHCP parts covered15:33
jdstrandwe really want all those parts covered15:34
flexiondotorgI've just fixed the following bug - https://bugs.launchpad.net/ubuntu-mate/+bug/142240215:34
ubottuLaunchpad bug 1422402 in ubuntu-mate "Shell Command Injection in places.py plugin of mate-menu package" [High,Fix committed]15:34
tjaaltoncjwatson: indeed15:34
mdeslaurpitti: what about /usr on nfs?15:34
flexiondotorgI would like to raise a bug to package a new version of mate-menu.15:34
pittimdeslaur: that's just sheer madness :)15:34
mdeslaurdoes that work and so people do that?15:34
jdstrandwhat we have with upstart now is a confusing mess. I mean it works, but it is hard to keep straight. not something you really want when dealing with loading security policy15:35
flexiondotorgShould it be flagged as security related given the bug it addresses?15:35
mdeslaurok, good, didn't know what is typically done15:35
pittimdeslaur: more seriously, I haven't seen it, and I don't believe that it works until I see it15:35
pittimdeslaur: AFAIR in the last meeting we said that /usr/ on a separate partition must work, but /usr on NFS can't15:35
mdeslaurpitti: ok, cool15:35
pittimdeslaur: for once all the nfs/rpc daemons are in /usr/sbin :)15:36
mdeslaurdo we know what is causing the dhclient race?15:36
pittiah no, not all of them15:36
pittisome are in /sbin/15:36
=== kickinz1|afk is now known as kickinz1
dokoneutron-lbaas: python-neutron-lbaas15:44
doko[Reverse-Depends: neutron-lbaas-agent (MAIN)]15:44
dokozul, jamespage: ^^^ did the source change?15:44
zuldoko: yeah it got split out into its own tree upstream15:45
dokook, thanks15:45
dokoMirv, qtbase-opensource-src recommends qttranslations-opensource-src (universe). MIR or suggests?15:48
tyhicksmdeslaur: no - we don't know what is causing the race yet15:48
dokobarry, there's a lot of python* component mismatches. could you have a look? http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:49
tyhicksmdeslaur: steve is supposed to be looking at it more this week15:49
barrydoko: i'll look.  i don't know when i'll have time to do anything about it :(15:51
dokoLaney, you uploaded remmina, needing two MIR's15:54
LaneyI think not15:54
Laneythat nx thing shouldn't be in main15:55
dokoLaney, at least your name is on the changelog ;-P15:55
Laneydemote it (with remmina-dbg)?15:55
dokoLaney, so demote the binary?15:56
Laneygo for it15:56
Laneythanks15:56
pittikees, slangasek, stgraber, infinity: TB meeting in 2 mins (reminder)15:58
pittimdeslaur: ^16:00
=== kickinz1 is now known as kickinz1|afk
=== kickinz1|afk is now known as kickinz1
=== beisner- is now known as beisner
=== anthonyf is now known as Guest62520
mdeslaur@pilot out16:47
=== udevbot changed the topic of #ubuntu-devel to: Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
pittikees, slangasek, stgraber, infinity, mdeslaur: TB meeting in 3 mins, this time for real :) (sorry for confusion)16:58
slangasek:)16:58
mdeslaurhehe16:58
slangasekstgraber: I think you're on for chairing today?17:00
pittislangasek: would you like to review the nfs patches, BTW?17:01
pittior should I just upload them?17:01
slangasekpitti: in principle yes, but I don't think I'd be able to get to it today17:02
pittislangasek: in the next days would be enough; I started the FFE, and we have some other thigns to be done for that17:02
=== Guest72440 is now known as rcj
pittiUnit193: did you test current xubuntu under systemd? (Given how much we talked about it, I suppose yes, but just to avoid doubts..)17:04
=== kickinz1 is now known as kickinz1|afk
ericsnowquick question: is vivid going to switch to using systemd for PID 1 at some point?17:35
Odd_Blokeericsnow: I've heard that it's expected to happen some time in the next week.17:41
ericsnowOdd_Bloke: ah, thanks17:41
Odd_Blokeericsnow: *waves hands*17:41
ericsnow:)17:42
dokoLogan, infinity: the librdkafka sync broke powerpc. this probably needs to be restored17:48
LoganI'll take a look17:48
Logandoko: yeah, looks like Adam's patch needs to be restored17:51
Logandoko: shall I do an MP? I don't have upload access to main17:52
dokoLogan, please check with infinity, eod for me17:57
Logansure :)17:57
Unit193pitti: And still running under it, yep.  There seems to have been a couple glitches, but nothing consistent.18:49
NoskcajIs anyone planning to merge meta-gnome3? It would be nice to have it updated for our current gnome packages19:55
jtaylormh someone know how one subscribes to the glibc list?20:01
jtaylorah found it, hidden away on the website not the list archive ..20:02
smoseris this bug known? https://bugs.launchpad.net/ubuntu/+bug/142782120:02
ubottuLaunchpad bug 1427821 in Ubuntu "server iso install fails during grub install" [Critical,Confirmed]20:02
smoseri dont know if it applies to server iso or not.20:03
smoserer... if it applies to desktop or not.20:03
smoseri  kind of suspect not.20:03
infinitysmoser: Not a bug I'm aware of, will have to give it a try later.20:16
cyphermoxsmoser: that looks like a fun bug20:19
dokotumbleweed, online?20:26
dokotumbleweed, what is the rationale for a separate /usr/lib/pypy hierarchy?20:30
tumbleweeddoko: hi20:46
tumbleweedyou mean dist-packages-wise?20:46
dokotumbleweed, yes20:48
tumbleweedincompatible .pyc files. One would be using __pyshared__ and the other wouldn't20:48
tumbleweedunless we'd symlink-farmed20:49
tumbleweedand there's no reasonable way to do transitive dependencies20:49
dokowell, cpython looks up __pycache__, why not pypy?20:49
tumbleweedin 3.x, yes20:49
tumbleweedI plan to share dist-packages for 3.x20:49
dokoyeah, that would be really useful20:50
dokoare you at PyCon?20:50
tumbleweedbeen meaning to talk to you about that20:50
tumbleweedyes, I will be20:50
dokolet's meet before PyCon, or at the sprints20:50
tumbleweedonly arriving on the thursday, but I'll be at the sprints20:51
=== salem_ is now known as _salem
staylorI'm curious about a good way to handle an issue I'm having, I have an amd64 host and have used multilib to install arm cross compilers and libraries but since -dev libraries install the .so library links yet can only be installed for a single arch I'm wondering how to handle this (short of manually creating the symlinks).21:09
dobeymulti-arch packages are installed in the proper places21:19
dobeybut if you want to cross-compile .deb packages, you should probably look at just using sbuild to do it21:19
infinitystaylor: Chroots are the way to go, one for native, one for each cross arch.21:23
infinitystaylor: Having one messy base system that attempts to build for everything will end in misery.21:23
staylorI don't see what's messy about software installing itself logically but I guess chroot is the only way right now.21:23
dobeyeverything in the archive doesn't support multi-arch yet21:26
dobeyso it gets messy quickly21:26
stayloris moving .so from -dev to the base lib package something that's on the roadmap though?21:26
dobeywhy would one move .so from -dev to the base lib package?21:27
dobeyit's possible to install -dev and -dev:armhf for packages that support multi-arch21:28
staylorI see okay I didn't realize nothing supports multiarch yet21:29
dobeylots of things do21:29
dobeyi don't know what you're specifically dealing with though. and building packages in clean chroots is always best anyway21:29
staylorwell glib for one, but I concede chroot seems the way to go21:30
dobeythe number of times people have built debs locally "just fine" and then had the builds fail in a PPA because they forgot to add things to build-depends, is innumerable21:32
dobeyah, the problem with libglib2.0-dev is that it has some things in /usr/bin21:33
dobeyso that creates conflicts when you try to install the dev package for another arch21:33
stayloryeah for packaging I see what you mean and that makes perfect sense, here I am setting up a cross compile environment for developers needing to target arm boards from their workstations so different needs and expecations.21:34
dobeystill, chroots are better and make management easier21:35
Bluefoxicyinfinity: if I gave you a reliable way to install multiple conflicting versions of a .so on a system so you could have different applications use different versions, how useful would that be?23:21
tmpRAOFBluefoxicy: Are you describing SOVER?23:30
* tmpRAOF is not sure if serious.23:30
BluefoxicytmpRAOF:  https://github.com/bluefoxicy/dpkg-ng/blob/master/README.md23:31
BluefoxicytmpRAOF:  I never got anywhere because I have nfc what i'm doing :323:31
BluefoxicyI mean, rewriting dpkg is kind of a big task23:32
BluefoxicytmpRAOF: the way Nix does it is silly.  If your binary uses 40 libraries, it puts in 40 runpaths pointing to very specific versions of the packages.23:33
tmpRAOFSo, the Debian library packaging policy makes ‘installing different versions of the library and link different applications against them’ work.23:34
BluefoxicyI figured you would just make the runpath point at /usr/package/$PACKAGE/$VERSION/lib/ first23:34
BluefoxicytmpRAOF: you can install conflicting libs?23:34
tmpRAOFAbsolutely.23:34
tmpRAOFOr, rather, you can install libfoo3 and libfoo2 at the same time, and dependencies will be resolved appropriately.23:34
Bluefoxicyno23:35
Bluefoxicylibfoo3 installs /usr/lib/libfoo.so.323:35
Bluefoxicylibfoo2 installs /usr/lib/libfoo.so.223:35
sarnoldsee e.g. libssl0.9.8 and libssl1.0.0 ..23:35
Bluefoxicybut how do you install libfoo3.1 and libfoo3.1.1?23:35
tmpRAOFBluefoxicy: The immediate question is ‘why do you want to?’ :)23:35
Bluefoxicyhow do you install libmysql.so.5 from Percona and libmysql.so.5 from Mariadb?23:35
tmpRAOFAh.23:36
BluefoxicytmpRAOF:  sometimes you have non-backwards-compat libraries23:36
tmpRAOFBluefoxicy: Right, and in that case it's up to the *library* package to change from libfoo2 to libfoo3.23:36
BluefoxicytmpRAOF:  This would happen basically constantly if you had a rolling release, too23:36
tmpRAOFIt absolutely doesn't; Debian Sid manages just fine.23:37
tmpRAOFSo, as I see it, Nix satisfies the “I want my program to link against _exactly_ the code that I've tested it against” desire.23:37
tmpRAOFWhich is a perfectly reasonable one.23:37
Bluefoxicyyeah, though I think the NixOS guys are insane23:38
tmpRAOFRegular distros satisfy the “I want my program to work, and benefit from bug fixes in my dependencies without me rebuilding every time one of my dependencies change” desire, which is also perfectly reasonable.23:38
Bluefoxicyit'd make more sense to have e.g. percona-5.2 look in /usr/packages/percona-5.2/lib for libraries first, and put anything specifically selected for percona as a symlink there23:38
Bluefoxicyi.e. normally, that directory would be empty or non-existent23:39
jtaylorkind of like limba?23:39
jtaylorinstall everything at once but each app only sees the set it wants23:39
jtaylorhttp://people.freedesktop.org/~mak/limba/23:39
Bluefoxicyif your package manager goes, "You can't upgrade $LIBX because Percona will break, and you can't install $FOO because it requires a newer $LIBX", it shuffles current $LIBX into /usr/packages/libx-1.0.0/lib/libx.so.1 and symlinks to it from percona's lib; upgrades libx; and installs foo23:40
Bluefoxicybecause screw that; conflicts shouldn't prevent me from having two pieces of software installed at the same time23:40
Bluefoxicyjtaylor: interesting.23:41
jtaylorconda also has a similar approach23:41
tmpRAOFBluefoxicy: How does the package manager know that you can't upgrade libX?23:41
BluefoxicytmpRAOF:  Conflict:23:42
tmpRAOFBluefoxicy: So libx version 1.1 needs to Conflict with all the packages it might potentially break?23:43
tmpRAOFWhy isn't it bumping SONAME?23:43
BluefoxicytmpRAOF:  dpkg notes that you need some lib = some version, > some version, < some version, etc; and that some libs can't be installed at the same time; etc.  It has a pretty complex dependency resolution system that sometimes tells you you need to remove some packages to install others, or that you can't install two things at the same time because they depend on things that can't be installed at the same time.23:44
tmpRAOFAh, so *percona* has a Depends: libx = 1.0?23:45
Bluefoxicyeh, percona, maria, and mysql are special cases23:45
Bluefoxicytehy all install libmysql23:45
Bluefoxicythey all REPLACE each other23:45
Bluefoxicyof course, you get the oddness where libx from some package replaces libx from another, and adds extensions.  Different extensions from another replacement.  Then you get dependencies on one or the other by specific applications, which can't be simultaneously installed.23:46
Bluefoxicyit's been a while since I've actually cared23:46
BluefoxicyI was more trying to gauge if it seemed relevant to anyone at this point.23:47
BluefoxicyThe last time I remember it being relevant to everyone in the world, all at once, was when gtk+ was dealing with 1.2 vs 2.0, because gtk+ breaks backwards binary compatibility a lot.23:47
infinityBluefoxicy: The solution to people not bumping their SOVER is to bump their SOVER, not reinvent the wheel.23:47
infinityBluefoxicy: And the github-style "use this exact version, or else" mentality is a security vulnerability nightmare.  No sane person should try to replicate it, but instead educate them.23:48
Bluefoxicyinfinity: thats' why I think the nix approach is insane, versus a "this specifically doesn't work unless you use this version" approach23:49
infinityBluefoxicy: percona/maria/mysql is a non-problem, FWIW, the servers don't need libmysqlclient, and the clients can all use the one from mysql.23:49
infinityBluefoxicy: And, again, if that changes, the SONAME should too.23:49
Bluefoxicyrtue23:49
Bluefoxicytrue23:49
Bluefoxicyso the current solution is to eliminate all situations where packages have any conflicts, so that all packages in the repository can be installed simultaneously on one system23:50
infinityWe define stable ABIs for a reason, if upstreams break that, we educate them.23:50
infinityEliminating all conflicts is a bit harder, and pretty pointless.23:50
infinityWhy do you need 7 things that all provide /usr/sbin/sendmail?23:50
Bluefoxicyheh23:51
Bluefoxicygood point23:51
infinityAnyhow, the forking library case (like percona/maria) is a pretty uncommon one, and the answer is for them to change the SONAME if they stop being compatible with libmysqlclient.23:53
infinityBut the GTK example you pointed out is a non-issue, 1.2 and 2.0 could always be installed together.23:53
infinityThey couldn't be linked together in the same memory space, but that's a problem no matter how clever you make your filesystem layout, you just need to make sure you don't accidentally do that. :P23:53
Bluefoxicypizza delivery special instructions23:54
Bluefoxicy"Leave the pizza in front of the door; then turn around and walk away slowly.  Don't look back."23:54
Bluefoxicyinfinity: there was an issue for a while where you had to recompile for gtk+ in the 1.2 days.  Some commercial applications (AIM, Yahoo Messenger) broke because they were compiled against a prior minor point release.23:55
Bluefoxicythey enjoyed keeping the same function calls and such so your code would work, but changing structures used internally.23:56
Bluefoxicyas a result, malloc(sizeof(opaque_struct)) would allocate the wrong size23:56
Bluefoxicyor whatever else23:56
Bluefoxicyit was incredibly bad programming practice23:57
Bluefoxicymaybe people have been beaten enough to learn not to do that in the past 10 years23:57
jtaylorno, even glibc devs still do that ;)23:57
jtaylor(see s390x abi break in 2.18 or 19)23:57
Bluefoxicyyes but that's drepper23:57
sarnoldjtaylor: surely they called all six users to give them a heads up? :)23:58
Bluefoxicyjtaylor: tell Drepper next time he breaks s390x, he has to publish a Youtube documentary of his p90x23:59
infinityIt hasn't been drepper for a long time.23:59
jtaylordrepper is not involved since a while23:59
Bluefoxicylooks like I'm very out of date23:59

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