=== pw2 is now known as PaulW2U
dodeluserI create a remastered ubuntu iso with this genisoimage syntax:  http://pastebin.com/WR8kJxbN             but the iso is not "hybrid" as I cannot write it to usb with "dd" and boot (does not boot) . what am I doing wrong?05:43
pittiarges: hey! would you mind looking at systemd in unapproved? https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1437375/comments/19 has the explanations05:55
ubottuLaunchpad bug 1437375 in systemd (Ubuntu Vivid) "[udev] Adding "Austin" adapter to Ubuntu partition take over system network interface" [High,Fix committed]05:55
pittiarges: what was uploaded yesterday was not meant to go into -proposed, I uploaded a newer version now05:56
pittiinfinity, RAOF ^ or someone else in ~ubuntu-sru05:57
RAOFpitti: Certainly, sir!06:00
infinitypitti: Nope, but RAOF will!06:00
pittiRAOF: cool, thanks!06:02
RAOFpitti: Want to add the various SRU headers to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259 ?06:07
ubottuLaunchpad bug 1448259 in systemd (Ubuntu Vivid) "Systemd does not send SIGTERM first on shutdown" [High,Triaged]06:07
RAOFpitti: Particularly test-case (although I expect that you'll be aggressively following up anyway)06:07
pittiRAOF: ah, can do; there are several reporters who will test this anyway (and already did so in the PPA)06:09
pittiRAOF: I'll add it06:09
pittiI thought the description was already sufficiently clear06:09
RAOFpitti: It is pretty clear, but it's nice to have a simpleminded test case to run through :).06:10
pittiRAOF: added06:10
RAOFpitti: Also - what's the regression potential for it? The comment in the revert is all ‘waiting for this is unreliable and breaks stuff’.06:10
pittiRAOF: typing06:11
* RAOF holds his finger over the ‘accept’ button...06:12
RAOF...oh! Tea's ready!06:12
pittiRAOF: added06:13
RAOFAh, ok. So the worst failure mode is “shutdown is delayed by some number of 90s timeouts”? Rad.06:14
pittiRAOF: reportedly in nspawn06:15
pittiRAOF: so it could also be in LXC06:15
pittiRAOF: but I've never seen that, so I can't really tell how often it happens06:15
pittiRAOF: it's ceratinly not a real fix, just a compromise to let stuff actually shut down cleanly (bash, mosh, probably other programs too)06:16
pittinow: session gets immediately SIGKILLed06:17
pittiwith patch: session gets SIGTERMed, cgroup for the session is being watched for becoming empty, then it gets removed06:17
RAOFYeah, seems reasonable.06:17
pittiand it will eventually get SIGKILLed if something is hanging06:17
pittiRAOF: cheers06:18
cjwatsonwgrant: "reverse-depends: Error: Unknown release" is that something you can fix?06:48
cjwatsonajmitch: ^- or you?06:48
wgranttumbleweed: ^^06:50
pittiwho has the power to modify the description on http://summit.ubuntu.com/uos-1505/meeting/22514/systemd-and-ubuntu-to-1604/ ?06:58
seb128pitti, I can06:59
pittislangasek and balloons are probably already asleep -- dholbach?06:59
seb128what do you need changed?06:59
pittiseb128: ah -- let me think06:59
pittiseb128: how about this: http://paste.ubuntu.com/11005549/07:01
seb128pitti, done07:01
pittiseb128: merci beaucoup !07:01
seb128de rien !07:01
* mgedmin is amazed that his laptop takes more than 20 minutes to reboot (gave up waiting for shutdown staring at a black screen, used alt-sysrq-s,u,b)07:13
pittimgedmin: something is clearly hanging; can you have a look at /usr/share/doc/systemd/README.Debian for debugging shutdown hangs?07:18
mgedminthanks for that hint!07:19
=== faust is now known as Guest14235
tjaaltonwhy would installing xserver-xorg-lts-utopic on trusty cause this http://pastebin.com/S3Zy0FQB ?08:10
tjaaltonthe x bits haven't changed08:10
tjaaltonproposed is enabled, though it didn't change without08:10
tjaaltonok libegl1-mesa-drivers-lts-utopic needs to be installed manually08:30
tjaaltonwhich is weird08:30
pittimvo_: mind if I steal your util-linux merge?10:02
mvo_pitti: go for it10:16
=== doko_ is now known as doko
Laneytumbleweed: is it on your stack again or should someone else take over?10:31
=== MacSlow is now known as MacSlow|lunch
dokopitti, bzr ftbfs12:07
zygamdeslaur: ping12:29
zygamdeslaur: I watched the gsettings vieo12:29
zygamdeslaur: I have one observation that you may find interestinog12:29
zygamdeslaur: windows went through a similar approach12:30
zygamdeslaur: windows has a layer where some writes are translated12:30
zygamdeslaur: and writes to legacy paths are redirected to per-user location12:30
zygamdeslaur: this works for filesystem and the registry12:31
zygamdeslaur: I can give you pointers after a meeting I'm in12:31
=== _salem is now known as salem_
pittidoko: ah, just saw the mail, yes12:48
=== MacSlow|lunch is now known as MacSlow
Laneyev: can we maybe delete https://launchpad.net/libtimezonemap ?14:13
Laneyafaik https://launchpad.net/timezonemap is the real thing14:13
evLaney, wgrant: any idea how I'd do that?14:28
wgrantLaney, ev: YOu can't, since it's linked to the libtimezonemap source. You need to unlink it first.14:30
evcan the UI say that?14:31
wgrantWell, a mortal also can't delete a project themselves anyway, mostly for historical reasons.14:31
wgrantBut even I can't until it's unlinked.14:31
evits unlinked now14:32
LaneyCheers chaps14:32
wgrantIt's also gone now.14:32
slangasekbarry: your dmesg output has some strange delays in it.  But it also shows the drm module loading 15s after boot, and completing initialization within 2s... so I don't think that explains the gpu-manager delays you're seeing.  It also looks like this all happens in the initramfs and your rootfs is only mounted 17s after boot, which is odd16:14
slangasekbarry: anyway, your 8s delay in the initramfs can't be blamed on systemd ;)16:14
barryslangasek: ok.  i reboot this machine so infrequently i just haven't been annoyed enough to dig into it.  it's basically been upgraded since lucid at least, so it could be fairly crufty16:15
bdmurraympt: Do you have a color suggest for wily for errors.u.c?16:27
smoserhey... anyone have an idea on how to determine if a drive is bootable ?16:30
smoseri'm guessing that mr watson has an idea, or that grub can somehow figure it out.16:30
smosercjwatson, ^ didnt want to bother you, but if you're there .16:31
tumbleweedLaney: on it16:33
Laneynoticed that reverse-depends is broken for wily because of it16:34
tumbleweedyeah, that's a thing16:35
cjwatsonsmoser: grub won't be able to; if I were you I would look up the spec for whatever firmware is in use and implement the algorithm prescribed there16:35
cjwatson(in the case of BIOS, look up the congealed wisdom of the internet rather than the spec, but there's still an algorithm that the firmware implements)16:36
strikovsmoser: I know nothing about gpt but in case of mbr arbitrary code can be stored inside the mbr boot recoder. It means that the only thing you can check is 0x55AA signature at the end of this code.16:51
strikovanything else (partition to boot for example) depends on the code which makes decision i.e. you can't understand what's on its mind without running it16:52
smoserstrikov, wellk i need to figure out which device the bios would look at for that data.16:52
smoserie, i need the bios search order. or even more simplistically, "would the bios boot from this drive".16:53
cjwatsonthere's no way to discover the real bios search order from the os.16:53
smoserthats what i thought..16:53
smoserbut that sucks.16:53
strikovsmoser: iirc, in case of mbr disks bios chooses first with correct 0x55AA (or AA55 don't remember) signature at the end of boot record16:53
cjwatsonsome bioses also implement a bit more than just 55aa too - they check things about the partition type16:53
cjwatson*partition table16:53
cjwatsonI expect it's possible to find a sample algorithm somewhere16:54
smoserwell, my google foo fails me.16:54
smoserjust now, i have 2 systems... one of them is ocnfiugred in the bios to boot from cciss/c0d0, one is not.16:54
smoseri have no way to know, and thus fail to boot on one and work on the other.16:55
smoserreally dont want the user to have to tell me.16:55
cjwatsonthis is why my advice for a long time was to install the boot loader to the master boot record of all installed non-removable disks.16:55
cjwatsonfeel free to try to come up with something better, but I tried for years and failed.16:56
smosercjwatson, the othe rthought was to do so, and somehow fingerprint which it came from16:56
strikovsmoser: hm, bios settings are stored inside a separate chip which is powered via the battery on the motherboard16:56
cjwatsonpretty sure I've been down all these paths before you :)16:56
smosercjwatson, yes.. .that is why i bother you.16:57
cjwatson... and found that it was impossible.16:57
cjwatsonanyway, have to go for dinner, sorry16:57
pittielmo, apw: in case you are interested in the "move from ifupdown to networkd" session: https://plus.google.com/hangouts/_/hoaevent/AP36tYdEA6lEvNPGjxR0J_YbKeXK6hLl5joZb9ERTmNXMVN3Fd8Pqg17:55
bdmurraypitti: If want to create the wily branch of apport I'd just take ~/ubuntu-core-dev/ubuntu/vivid/apport/ubuntu and then push to s/vivid/wily/ right?17:59
leszekhi does anybody have a clue on what might be wrong when add-apt-repository is adding ppas but with wrong codename (wily instead of vivid) even though /etc/lsb-release is set up correctly and in python aptsources.distro.get_distro().codename shows vivid correctly ? Where does the add-apt-repository script grab the codename from ?18:40
leszekeven SoftwareProperties.distro.codename() shows the correct one vivid18:43
leszekbut in the end it adds wily to the sources18:43
leszekwhen I try to add a ppa18:43
Unit193codename = get_current_series_from_lp(self._info["distribution"])  is what I'm seeing.18:44
leszekUnit193: thats means ? It only gets the current version of the ppa or what exactly ?18:48
leszekanyhow it should always add the ppa for the distro I am currently using and not for the one that is default set on ppa (or whatever)18:52
leszekand best of all the ppa (kubuntu backports) that I want to add does not even have a wily repo xD18:53
leszekah ok now I found a clue. Distro Name changing to somethign else then Ubuntu causes the issue. WTF19:04
leszekin /etc/lsb-release19:04
leszekI am still not getting why that is though or even should be19:06
pittibdmurray: sorry, was in UOS sessions; yes, we need to do that anyway, before we change apport in wily19:10
pittibdmurray: thanks for setting up the wily branch! (please update Vcs-* in debian/control too)19:10
=== imcleod is now known as imcleod_errand
hallynslangasek: if you have time, would you mind sponsoring http://mentors.debian.net/debian/pool/main/c/cgmanager/cgmanager_0.37-1.dsc into sid?  Also, would you be willing to sponsr me for Debian DM?19:17
=== anthonyf is now known as Guest80518
=== imcleod_errand is now known as imcleod
argesinfinity: added bug 1452877, going to patch it. any objections ?19:46
ubottubug 1452877 in debootstrap (Ubuntu) "Add wily support to debootstrap" [Undecided,New] https://launchpad.net/bugs/145287719:46
infinityarges: Already fixed in vivid (task updated), but go nuts on the SRUs, sure.19:49
argesinfinity: cool19:49
infinityErr, s/vivid/wily/19:49
* infinity updates properly.19:49
infinityMy poor brain won't shift codenames for another week or two.19:49
infinityDespite how many times I've typed "wily" this week.19:50
argesi keep typing willy19:50
dobeywascwy wabbit19:53
=== anthonyf is now known as Guest51489
=== salem_ is now known as _salem
Unit193robert_ancell: Now that it is wily time, care to look at lp 1295207?  Been using the patch for a couple months now.21:15
ubottuLaunchpad bug 1295207 in pidgin (Ubuntu) "Migrate to farsight 0.2* / gstreamer 1.0" [Undecided,Confirmed] https://launchpad.net/bugs/129520721:15
robert_ancellUnit193, yeah, I guess that makes sense21:16
Unit193Looks like it may be fixed once .12 is released as well.21:17
=== _salem is now known as salem_
=== athairus_oops is now known as athairus
=== salem_ is now known as _salem

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