=== freeflying_away is now known as freeflying
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== freeflying is now known as freeflying_away
=== jamesh__ is now known as jamesh
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
pittiGood morning04:18
pittiRAOF: thanks for the psql reviews!04:18
RAOFpitti: No problem!04:19
pittiRAOF: could you review the lucid one, too?04:19
RAOFHm, did I not do that one too?04:19
pittiit's still in the queue, and I didn't get a message for it04:20
RAOFAh. That's because sru-review barfed on it last time. Done!04:24
pittiRAOF: cheers! barfed how?04:30
RAOFpitti: I think it was a timeout. My internet is being a bit wonky.04:31
pittiI'll run the test suites with the proposed .debs today04:31
=== freeflying_away is now known as freeflying
=== jamesh__ is now known as jamesh
dholbachgood morning07:00
xnoxpitti: can I quickly poke you about libudev? i'm looking to add nomatch filters to the  udev_monitor. Similar to how filter_subsystem_list and filter_tag_list, expect that i need to add exclude / nomatch (similar to how nomatch works with enumerate functions).08:23
xnoxthis is for bug #123474308:24
ubottubug 1234743 in linux (Ubuntu) "omapfb module floods system with udev events on samsung galaxy nexus" [Undecided,Incomplete] https://launchpad.net/bugs/123474308:24
pittixnox: you can poke me, but as I said last week I never did anything with netlink filters, so I'm afraid I have zero experience there :/08:24
pittixnox: besides, libudev is the wrong place for that08:25
pittixnox: what we want is to apply that filter in udev daemon, on the "kernel" side08:25
pittithey shouldn't even appear on the "udev" netlink side08:25
xnoxpitti: the way I see it, is that udevd will add a filter, but it's using libudev api throughout. So libudev needs "nofilter" functions that one can set excludes, which are applied to the requested monitor.08:25
xnoxand udev netlink side is generated by udevd listening to kernel events?08:26
pittixnox: yes, it has a private libudev API for that08:26
* xnox thought that if I filter kernel netlink in udevd, nothing will appear on the udev netlink.08:26
xnoxor is that not correct?08:26
pittixnox: yes; udevd listens to the "kernel" originated uevents, applies its rules etc., adds the extra properties, tags, etc from them, and re-sends them as "udev" uevent source08:26
pittiand usually clients only listen to the "udev" source08:27
xnoxi was hoping to record and replay the stream of udev events, with/without my filter to make sure that my filter is correct.08:27
pittithat's the difference between udevadm monitor --udev and --kernel08:27
xnoxok. so i understood that correct.08:27
pittixnox: so it seems easiest to filter out that one event in udevd08:27
pittiwithout making any public API changes08:27
pitti(OMG, please let's not change any API/ABI for such a hilarious hack)08:27
xnoxit's just i don't want udev to wake up at all for those, hence the netlink filter.08:28
pittixnox: exactly08:28
pittixnox: hence applying that filter in udevd on the kernel side08:28
pittiinstead of on the udev side, where udevd would wake up all the time08:28
xnoxpitti: ack.08:28
xnoxpitti: looking at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234743/comments/7  i think that's variables as exported by upstart bridge.08:29
ubottuUbuntu bug 1234743 in linux (Ubuntu) "omapfb module floods system with udev events on samsung galaxy nexus" [Undecided,Incomplete]08:29
xnoxpitti: but in uevent/udev terms are those properties?08:30
pittixnox: yes, they are08:30
pittixnox: attributes are in sysfs, like in /sys/devices/platform/omapfb/<fileX>08:30
xnoxi think I just want to ignore any VSYNC.08:30
xnoxchange events.08:30
pittixnox: properties are stuff that udev rules can add, and some come from the kernel or udevd itself (DRIVER, ACTION, USEC_INITALIZED, and so on)08:31
pittixnox: hm, I guess you need to add an accessor to udev_monitor->sock to src/libudev/libudev-private.h08:34
pittixnox: perhaps it's easiest indeed to add the hack to src/libudev/libudev-monitor.c indeed, to udev_monitor_new_from_netlink_fd() if name == "kernel"08:35
xnoxwell there is udev_monitor_filter_update() which applies the filters already08:35
pittixnox: there you have the sock and can can attach the extra filter08:35
xnox(filter by subsystem or tag)08:35
xnoxif i access and modify filter directely any calls to filter_update() will wipe mine. (i think, unless i'm careful to use a different magic #)08:36
pittixnox: ah yes, that's fine; udev_monitor_enable_receiving() calls that, and is called by udevd at the beginning08:36
xnoxso i was thinking, if I am to add api-less hack that would be there.08:36
pittixnox: agreed08:36
xnoxpitti: can udevmock reply kernel src uevents?08:37
pittixnox: it doesn't actually make that distinction between kernel/udev08:38
pittixnox: but I doubt that you currently can run udevd itself against umockdev, as all of its netlink filter operations just won't work on our fake unix socket08:38
xnoxi see.08:40
pittixnox: for testing, I propose you take any existing driver on your system, where you can trigger a kernel-level uevent by writing into /sys/.../udevent08:40
pittixnox: and write your code with some other device name/property08:41
pittixnox: s/udevent/uevent, of course08:41
pittixnox: then, if filtering that out works, it should be a mere string replacement in your hack, and just one verification on maguro (or wherever that happens)08:41
pittixnox: e. g.08:43
pitti$ echo change | sudo tee /sys/class/misc/uinput/uevent08:43
pitti$ udevadm monitor -e --kernel08:43
pittiKERNEL[16115.645262] change   /devices/virtual/misc/uinput (misc)08:43
pitti(you need to start the monitor before, of course)08:43
xnoxpitti: right, can i add attributes to it? or shall i write something in c then to emit proper uevent?08:48
pittixnox: no, you can't change the set of attributes of a kobject, that's defined by the driver (only)08:49
pittixnox: the /uevent attribute shows the kernel-defined properties08:50
pittixnox: but I don't know whether you can "inject" them with that method08:50
pittithe naive approach with "echo -e 'change\nFOO=bar'" doesn't work08:51
pittixnox: so perhaps test with MINOR= or something08:51
mptmvo! Could you please review <https://code.launchpad.net/~brunonova/software-properties/update-apt-on-exit/+merge/190498>? It's a grand total of two lines change.09:10
xnoxpitti: is systemd-udev statically linked againt libudev? cause i don't think i want to change the behaviour of libudev1 et.al.09:19
pittixnox: yes, it is; it builds a libudev-private.la durig package build and links udevd, udevadm etc. against that09:20
pittiso that the private symbols don't appear in the public lib09:20
pittixnox: actually I think with above approach you will09:20
pittixnox: but that's ok; any other program which uses libudev to listen for kernel events will then also have these filtered out09:21
xnoxpitti: i'm now thinking to cheat.09:27
pittixnox: you are considering making the change in udevd.c only? then you'll need an accessor for "int sock" in libudev-private.h09:28
xnoxpitti: i'd like to invert the meaning of lilter tag - from include only this tag, to drop anything tagged. Then add udev rule to tag omapfb device with tag "ignoreme" and then add udevd filter tag "ignoreme"09:29
xnoxoverall that should be quite small and obvious, yet horribly breaking all existing conventions.09:29
xnoxunless that would break udevadm monitor =/09:30
xnoxhmm... or I shall copy & paste.09:30
tvossjodh, ping09:33
jodhtvoss: hi09:34
pittixnox: re (sorry, was OTP)09:42
pittixnox: "invert meaning of filter tag" sounds quite intrusive?09:42
xnoxpitti: well, i think i came up with something even better now.09:42
xnoxpitti: let me hack a bit, and I'll ping you for code review.09:42
=== geser_ is now known as geser
tvossdoko, mind pinging me the link to your fix for the pretty printer python scripts again?09:54
=== MacSlow is now known as MacSlow|lunch
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== MacSlow|lunch is now known as MacSlow
kubuntu83Greetings, everyone. Am I understanding correctly that, in Saucy, the appmenu-gtk* packages were superseded by packages which no longer work outside of Unity (particularly KDE)?12:22
xnoxkubuntu83: define "no longer work" they do work with gtk2 and gtk3 panels (applets), indeed so far there is no appmenu-ng port to qt4/plasma. It does work in qt5/declarative for example.12:23
xnoxno port to qt5/framework5 yet either, I think.12:24
kubuntu83xnox: Gtk2/3 apps are no longer exporting their menus under KDE -- not to KRunner, KWin, or Plasma (all of which are picking up Qt menus just fine).12:28
xnoxkubuntu83: correct.12:31
* xnox ponders if we should disable menuproxy for gtk under kde then.12:32
kubuntu83xnox: Any idea which packages I would need to downgrade/pin to get the old functionality back, or if that's even possible?12:43
xnoxkubuntu83: i don't think it will be possible, as it's abi transition, you'd have to downgrade all the gtk apps to get them linked against older indicators, which in turn will bring a large can of worms and you end up running quantal.12:46
cjwatsonbarry: Er, WTF - running the system-image autopkgtests, they chmodded my /tmp to 270012:47
xnoxkubuntu83: i think it should be possible to export a varible / change gsettings such that the menubar is back within the app and clickable, but it will not export the menus anywhere either.12:47
cjwatsonbarry: I uploaded http://paste.ubuntu.com/6240379/ to make the autopkgtests pass again; Vcs-Bzr points to lp:~ubuntu-system-image/ubuntu-system-image/client, but that doesn't contain the packaging, so I didn't know if there was anywhere I could commit this12:49
kubuntu83xnox: It's already showing up within the app, so I guess it could be worse.12:51
=== _salem is now known as salem_
xnoxkubuntu83: oh, that's ok then.12:56
xnoxkubuntu83: i don't think you can get better than that.12:56
xnox(i guess it checks and finds out there is no dbus service listening to receive the -ng menus, and gives up)12:56
kubuntu83Sorry to bitch and moan. I just spent the weekend porting packages to Saucy, only to run into an issue that will probably keep me from using it.12:57
barrycjwatson: yikes, that's not good.  yeah, i'll fix that12:59
kubuntu83xnox: Sorry to keep bugging you, but do you have any idea who I should be petitioning to get a Qt4/Plasma port of appmenu-ng?13:02
xnoxkubuntu83: can you write code? if not find a volunteer who wants to write it. it should be fairly straight forward from gtk port.13:03
xnoxkubuntu83: it simply needs to find somebody with time to volunteer and contribute the qt4 port. no petitioning is required.13:04
kubuntu83xnox: Right, I was using "petitioning" figuratively. ;)13:04
dokomvo, apt ping13:05
xnoxkubuntu83: ok =) i see.13:06
kubuntu83xnox: By the way, you said I'd end up running Quantal if I tried downgrading the relevant packages, but... Everything (appmenu-wise) was working fine in Raring. Not sure if that's relevant. I assumed appmenu-ng is new to Saucy, right?13:06
xnoxkubuntu83: oh was it. can't remember if it was quantal or raring where the -ng appmenu was introduced, i might be wrong.13:07
mvodoko: apt pong (but in a meeting, so expect some delay in asnwering)13:07
kubuntu83xnox: Alright, well... Thanks for filling me in. Peace.13:11
knoctehow can I know who is in charge of some ubuntu package?13:40
mdeslaurknocte: Ubuntu doesn't have maintainers like Debian does. Looking at the changelog may give you an indication of who usually updates it though.13:42
xnoxpitti: here is my work in progress (sorry for so late, been pinged to do other stuff) http://paste.ubuntu.com/6240591/13:42
mdeslaurknocte: any package in particular?13:42
knoctemdeslaur: libgstreamer packages13:42
xnoxpitti: completely untested at the moment, so the idea is that netlink filter will drop packets from devices tagged "ignore". Reusing existing netfilter logic used to _match only_ tag.13:43
pittixnox: heh, fun; ages ago, udev actually had something like that already, but it was removed because nobody used it and it was considered a bad workaround for a kernel bug :)13:43
pittixnox: right13:43
mdeslaurknocte: doesn't look like anyone in particular takes care of them. Best bet is to file a bug if you have an issue, or want to submit a debdiff to fix something.13:44
knocteI'll file a bug, thanks13:45
pittixnox: so, I don't understand the logic in the first block (how does adding to udev_monitor->filter_tag_list suddenly make it a "no match" tag?)13:45
xnoxpitti: well it still does have "nomatch" type of filters in the enumerate, just not in the monitors.13:45
pittixnox: ah, filter_tag_list is actually that "filter out these tags" already?13:45
xnoxpitti: so the difference is for all tags, compare lower/upper part of tags and if matched.....13:46
xnox... previously jump after drop packet13:46
xnoxnow branch: for "match-only tagged" (old / normal) jump after drop packet; for "nomatch" jump _to_ drop packet;13:46
pitti(no idea how that code/bpf is working)13:46
xnoxpitti: BPF_JMP -> jump instructions, BPF_JEQ if equal to BPF_K constant value. If true instruction location, false instruction location.13:48
pittixnox: so, if that works, it looks fine to me; unintrusive (API-wise) and shoudl avoid all wakeups13:48
xnoxpitti: depending on the value of the tag, i jump one instruction less or not.13:48
xnox(or jump past the drop or not)13:48
pittixnox: what does the "nomatch" string value do?13:49
xnoxi think it will drop everything if no tags matched at the moment. let me think about it.13:49
pittilist_entry in the top corresponds to udev_monitor->filter_tag_list?13:49
xnoxpitti: at the moment it can be any. _add_match_filter results in value NULL, and at the moment i simply use ! NULL to consider that it's nomatch branch.13:49
pittiotherwise it would break the default behaviour13:49
xnoxpitti: so "nomatch" can be any string.13:50
pittiah, ok13:50
xnoxpitti: i guess instead of if (udev_list_entry_get_value(list_entry) == NULL)  I could do explicit string comparison.13:50
pittithe code uses filter_tag_list for positive matches, though13:50
pittiso if you change that list to mean "filter out" tags, how does that not break current behaviour?13:51
xnoxpitti: i'm trying to conditionalise it.13:51
xnoxpitti: by adjusting the actions when tags are matched. I guess i'm wrong now.13:51
pittixnox: ah, that's just a check if it works at all, not yet meant to be fully working13:51
xnoxpitti: since untagged by default would be now dropped, if there is only one nomatch tag.........13:52
* xnox needs to think about it.13:52
xnoxmaybe i need a global flag / option then (not on per tag level) if the filter_tags are to include-only or exclude-only13:53
=== kentb-out is now known as kentb
pittixnox: hm, that sounds a bit dangerous as well14:01
xnoxpitti: well, the api is private and not public, and we only expose / use it in one place in udevd, such that if behaviour for udevd is correct and the libudev behaviour is un-changed we should be ok.14:02
barryjdstrand: ping14:06
jdstrandbarry: hi!14:21
barryjdstrand: hi!  could you sanity check: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1235975/comments/514:22
ubottuUbuntu bug 1235975 in system-image (Ubuntu) "Unsafe file and directory permissions" [High,Fix committed]14:22
jdstrandbarry: I think that is all reasonable, but might mention this-- now that /var/log/system-image and /var/lib/system-image will be created with the correct permissions, why not move the 'correct bad permissions' code into postinst conditional on an upgrade to the release (or past) the one that fixes the issue?14:27
jdstrandbarry: furthermore, shouldn't the debian packaging be creating those directories in the first place? that way they can be cleaned up on uninstall14:28
jdstrand(perhaps the debian packaging is already doing that-- it wasn't clear from the comment)14:29
barryjdstrand: it's not, but i do think it makes sense to have the packaging change any existing directories, and leave the s-i code to *create* files and directories correctly.  that would leave just the logfile itself and the random temp subdir.14:30
barryjdstrand: of course, if someone changes the config file to point to different locations, their on their own14:30
jdstrandbarry: yes. I think that is reasonable in this case14:31
barryjdstrand: i think i will open a new bug for this and try to squeeze in a 1.9.1.  if you want to review the branches (yes, two of them) let me know14:32
cjwatsonbarry: could you look at the current system-image autopkgtest failures?  Linked from http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#system-image (the public link probably isn't up to date yet; the private link requires batuan VPN access)14:37
barrycjwatson: lool is pinging me on #ubuntu-touch, probably about the same thing ;)14:38
=== psivaa is now known as psivaa-afk
barryjdstrand: LP: #124010514:53
ubottuLaunchpad bug 1240105 in Ubuntu system image "An update to LP: #1235975 (permission fixing)" [Critical,In progress] https://launchpad.net/bugs/124010514:54
=== psivaa-afk is now known as psivaa
=== tkamppeter_ is now known as tkamppeter
jdstrandbarry: ack15:42
=== pete-woods is now known as pete-woods-away
infinitysarnold: *pokity poke*15:42
jtaylorstgraber: re bug 1236957, python3-pyparsing is provided by pyparsing, a different source package16:07
ubottubug 1236957 in python3-pyparsing (Ubuntu) "please remove from archive" [Undecided,New] https://launchpad.net/bugs/123695716:07
stgraberjtaylor: oh, indeed, so source only removal then, good16:11
stgraberwell, no, source and one binary16:11
stgraberjtaylor: done16:12
PeterCassettaIs this the right place to ask about getting certain universe packages updated?16:56
sarnoldinfinity: sorry, I've not yet started 1220434 for curtin, but if it's any consolation I took my dog for a good long walk in the wonderful weather on yesterday's day off :)17:05
xnoxPeterCassetta: usually, just ask whatever you want to ask =)))) then people can respond and/or redirect.17:06
infinitysarnold: We're cutting it pretty dangerously close to release.17:06
xnoxPeterCassetta: nobody asks to ask a question on irc ;-)17:06
PeterCassettaxnox, okay, cool.17:07
sarnoldinfinity: indeed :(17:13
PeterCassettaThere's a few applications I use fairly often which are pretty out of date.17:14
=== bfiller is now known as bfiller_afk
PeterCassettaOpenTTD in the software center is 1.2.3, but the latest stable version is
PeterCassettaBlender is also two versions behind (soon to be three), at 2.66a.17:16
PeterCassettaThe latest official stable version is 2.68a.17:16
cjwatsonRealistically, the best way to get that kind of thing updated is to get the Debian maintainer to update their packages, and then we'll sync/merge them into whatever the current Ubuntu development release is at the time17:17
cjwatsonAnd maybe then backport to stable releases17:17
cjwatsonIn saucy, openttd is 1.3.1, blender is still 2.66a17:17
cjwatsonBut we don't update stable releases with new upstream versions, generally - that's what the various -backports repositories are for17:17
cjwatsonblender is 2.68a in saucy-proposed, but unfortunately it fails to build everywhere17:18
cjwatsonSo that needs to be fixed17:19
cjwatsonLooks like it may perhaps be blocked on the libav 9 transition, which will be happening early in the next release cycle17:19
cjwatsonMight need extra work to be backportable then, though17:19
PeterCassettacjwatson, are universe packages generally not updated after an Ubuntu release comes out?17:20
cjwatsonExcept sometimes in -backports17:20
PeterCassettacjwatson, just to be clear: If, say, OpenTTD is backported from saucy, would I then be able to install it on ringtail?17:24
cjwatsonPeterCassetta: I don't recall how it shows up in software-center, but worst case it would be installable on raring with "apt-get -t raring-backports install ..."17:25
PeterCassettacjwatson, okay, one last question: When asking for a backport from, say, saucy, would I report it in the project "saucy-backports"?17:28
cjwatsonNo, report it on the target (e.g. raring-backports)17:29
PeterCassettacjwatson: Okay, cool, thanks for the help. :)17:29
rbasakPeterCassetta: full explanation here: https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport17:29
Bluefoxicybah.  I can't figure out how to get dpkg to stop deleting everything and failing.17:58
Bluefoxicydpkg-source: warning: ignoring deletion of file tests/test_gridfs.py17:58
Bluefoxicyclint byrum... that's who I need to find.18:02
=== bfiller_afk is now known as bfiller
=== salem_ is now known as _salem
alkisgHi, this recent bug fix causes a regression, i.e. it no longer respects the default Xorg resolution but gnome-settings-daemon now forces the highest one: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/106597919:35
ubottuUbuntu bug 1065979 in gnome-settings-daemon (Ubuntu) "external/internal monitors mirrored on boot when laptop lid is closed" [Wishlist,Confirmed]19:35
alkisgShould I file the regression as a separate bug report, or just comment in the same one?19:36
Laneyalkisg: bah19:39
Laneyalkisg: There's already bug #123675219:40
ubottubug 1236752 in gnome-settings-daemon (Ubuntu) "gnome-settings-daemon (3.4.2-0ubuntu0.6.3) breaks nvidia multi-monitor-config" [Undecided,Confirmed] https://launchpad.net/bugs/123675219:40
LaneyWe should probably revert it and then Ritesh can try again if he wants to19:41
alkisgThank you Laney, yeah, please do so :)19:41
alkisgI just commented on the first bug report a minute ago19:41
LaneyFourDollars: ^ you verified this19:41
mercury00hello all. I've built a .deb package with a postinst script that edits a grub config (enables console). However, rather than call update-grub in the postinst, I'd like to 'trigger' grub to update once all packages are updated (the correct way). I believe there's a way to do this but simply cannot find it. any ideas?19:43
mercury00for instance my package might get installed when someone also installs a new kernel. rather than update grub twice, I;m sure there's a built-in way to make grub update after all packages are installed, and I'm sure the kernel packages use it but don't know how they do so. Thanks for any help.19:44
Laneyalkisg: Uploaded19:53
alkisgThank you, I'll give feedback as soon as it builds19:53
Laneybdmurray: ScottK: (picking on two of you at random) could you look at accepting gnome-settings-daemon/precise-proposed? It's a regression-update revert.19:56
smoserbdmurray, ping19:58
smoserdo you have a thought on bug 123989319:58
ubottubug 1239893 in software-properties (Ubuntu) "PPAs added using GUI Software and Updates have an extra space added to repository line" [High,Triaged] https://launchpad.net/bugs/123989319:58
mercury00also, I assume this is the correct channel to ask such questions? Just want to make sure I'm not spamming the wrong place20:00
bdmurraysmoser: I'm looking at your changes now.  Could you elaborate on your question though?20:05
infinitymercury00: That would require update-grub supporting triggers, which I don't believe it currently does.20:06
mercury00ah, ok - what's the general way to trigger update-menus and such though?20:07
infinitymercury00: Generally, packages handle this by triggering in their own update scripts so you don't have to think terribly hard about it.20:09
mercury00I know that when I run updates on several packages, I only see the update menus and all that at the very end of the process, but I don't know how to to that20:09
infinitymercury00: For instance, calling update-initramfs or ldconfig from a postinst will make them trigger, rather than run immediately.20:09
mercury00infinity: ah, ok so it's captured by dpkg or something then, if I call update-initramfs in postinst it triggers it instead?20:10
infinitymercury00: dpkg exports some magic variables when executing a postinst, and then if the called binary understand what that means, it can defer to a trigger instead.20:11
mercury00infinity: good to know: is there a list anywhere of what programs are /triggered/ rather than executed in postinst? I'm mostly only curious at this point, but still couldn't find any documentation on that20:11
infinitymercury00: /sbin/ldconfig is likely the simplest example of that on your system.20:11
smoserbdmurray, just wanted to know if you had a clear idea on what had regressed. i didn't understand how this path would hav regressed.20:12
infinitymercury00: There's no definitive list, as this is up to the packages themselves, not up to the distribution as a whole.20:12
mercury00infinity: aha, that makes sense20:12
infinitymercury00: The idea is that, as the caller, this should all be transparent to you.  You call what you should intruitively call (directly, or via debhepler-inserted things), and if the package does fancy things behind your back, that's its business.20:13
alkisgmercury00: $ cat debian/ltsp-client-core.triggers20:14
alkisgactivate update-initramfs20:14
bdmurraysmoser: did software-properties used to accept ppa: style lines?20:14
alkisgmercury00: With a .triggers file you specify what trigger you want to activate20:15
alkisgYou don't call update-initramfs20:15
smoserbdmurray, i just tested. and this bug existed in 0.92.2620:15
mercury00alksig: I saw some documentation on that, but couldn't find any list of what the triggers actually were,20:15
alkisgmercury00: https://wiki.debian.org/DpkgTriggers20:15
mercury00alksig: just how to call them20:15
mercury00alksig: ah, thanks,20:15
alkisgmercury00: there's a list there. also, tab in irc autocompletes the name so that you get it right :)20:16
mercury00alksig: aha, that's the one I was looking for, I was sure that ubuntu had patched grub to accept the trigger for multiple kernel updates20:17
sarnold(more like, it changes how you get it wrong :)20:17
mercury00or multiple whatever updates20:17
mercury00thanks, didn't know about autocomplete in irc20:17
=== Nisstyre-laptop is now known as nisstyre
argesHi. bug 1065979 seems to be a regression for some users. How can I properly tag it so that patch gets reverted?20:19
ubottubug 1065979 in gnome-settings-daemon (Ubuntu) "external/internal monitors mirrored on boot when laptop lid is closed" [Wishlist,Confirmed] https://launchpad.net/bugs/106597920:19
Laneyarges: I uploaded it and pinged bdmurray but he chose not to reply ;-)20:20
argesLaney: should it be tagged 'regression' or something so it gets on somebody's radar? or bdmurray can handle it since you already pinged him20:23
Laneyarges: I think I did the right thing in the bug referenced from the changelog20:25
Laneyanyway, off now20:25
argesLaney: ok thanks20:25
mercury00alkisg: one last question then: my package source builds several packages, so i have package1.postinst and package2.postinst --- does this mean I also want package1.triggers?20:25
bdmurrayLaney, arges: I'll look at it before my EOD20:26
smoserbdmurray, i take my above comment back . i've never used that before.20:31
mdeslaurbdmurray: can I attack an apport file to an existing bug?20:40
* mdeslaur searches for appropriate magic incantation20:40
bdmurraymdeslaur: what do you mean my apport file? a .crash file or something else?20:41
mdeslaurbdmurray: I ran ubuntu-bug on a machine without a browser, and I selected the "save for later" option. It generated an .apport file20:41
bdmurraymdeslaur: just ubuntu-bug .apport file will work20:42
mdeslaurbdmurray: but that wants to open a new bug, instead of attaching to the bug I already have...20:42
mdeslaurbdmurray: https://help.ubuntu.com/community/ReportingBugs says I should be able to use -u, but it doesn't work20:42
alkisgmercury00: not all packagesXX will need to trigger the trigger. For example, ltsp-client-core does need to trigger update-initramfs, but ltsp-client doesn't. So there's no ltsp-client.triggers file.20:42
bdmurraymdeslaur: ah so no there isn't a way to do that20:44
mdeslaurbdmurray: ok, thanks!20:44
mdeslaurxnox: I've attached requested info to the ubiquity timezone failure bug20:49
mercury00alkisg: right, only one of my packages will need to trigger something, so I'd put the instructions in my package1.triggers file then it seems?21:09
cappytHi everyone, i have a problem doing a live/installable iso based on my current system. I run 13.04 and i tried using remastersys, but it seems not working anymore... anyone has suggestions?21:32
mercury00cappyt: do you have any info about what's not working in particular? error messages? (I have no idea myself, but you'll probably get better help if you have some idea what's wrong)21:35
cappyti can provide a log, if you want21:35
bdmurraysmoser: I think you need to use strip() as DialogAdd adds a '\n'21:41
cappytThis is my remastersys.log https://docs.google.com/file/d/0B1x0krrddxExV0RJbEh1VEpDLXc/edit?usp=drive_web21:59
cappyti can't figure out why is not creating the ISO.21:59
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
sarnoldinfinity: security team ACK on including curtin in main, details to follow in bug report "soon"23:30
=== freeflying_away is now known as freeflying
stgrabersarnold: yay!23:45
stgraberinfinity: was about to promote but just noticed that we only have a security team ack and not an ack from a MIR team member so I'll let you deal with that (since you've got all the hats necessary to deal with it)23:46

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