/srv/irclogs.ubuntu.com/2014/02/12/#ubuntu-devel.txt

=== maclin_ is now known as maclin
=== mwhudson is now known as zz_mwhudson
MirvScottK: my best estimate would be in 2.5 weeks from now, with the new 5.2.1 fixing some remaining issues and QA team coming up to speed in testing with 5.2.1 appearing in PPA soon. there'll be a bit of new extra work also because mkspecs location changed in Debian recently and that wasn't reflected in our packaging before now.05:25
NoskcajCan someone please upload lp:~noskcaj/+junk/gnome-weather to trusty? debian won't upload it in time and ubuntu-gnome needs it05:59
Noskcajoops, lp:~noskcaj/+junk/gnome-photos actually06:00
RAOFpitti: Yo!06:05
=== maclin_ is now known as maclin
pittiGood morning06:39
pittiRAOF: hey06:39
RAOFpitti: Good morning!06:39
RAOFI've got two questions - how soon will those umockdev commits land in trusty, and how would you like the load_ioctl(testbed, NULL, "foo.ioctl") thing implemented?06:40
RAOFHm. But first I apparently need to get some mushrooms, so I'll ping you again later :)06:41
pittiRAOF: if you want those commits, I'll do a microrelease/upload today06:46
pittiRAOF: ioctl_record_open() needs to write $UMOCKDEV_IOCTL_RECORD_DEV (major/minor) as the first line into the .ioctl file; or if that's impractical/ugly, umockdev-record needs to pass the original device name in addition (perhaps UMOCKDEV_IOCTL_RECORD_DEVNAME)06:50
pittiRAOF: then ioctl_tree_new_from_text() needs to be able to load that06:52
pittiRAOF: perhaps "@DEV /dev/...." (@ to make it an invalid ioctl name)06:52
pittiRAOF: hm, actually evaluating it in ioctl_tree_new_from_text() is a bit impractical, as you'd need to pass it upwards and back in time06:55
pittiRAOF: so I guess ioctl_tree_new_from_text() should just ignore it, and load_ioctl() itself needs to open it once, read the first lines, and evaluate the @ commands06:56
pittiRAOF: you need to make "string dev" to "string? dev", check it for null, and if it is, open the file, read the devname, and use that instead of "dev"06:56
RAOFpitti: Ah, good. That was roughly what I was thinking, except using # instead of @.06:57
pittiRAOF: # is an usual comment character, though06:57
pittiRAOF: we support # in .script files; not sure that it already does in .ioctl files, but it should06:57
pitti(particularly when you hand-edit them)06:58
RAOFRight; I was going to have ioctl_record_open write something like "# originally recorded from: /dev/baz"; “@ DEV /dev/...” seems better, though.06:58
RAOFpitti: So, I notice that ioctl_record_open supports appending to existing .ioctl files. How would you want that handled?06:59
pittiRAOF: right, if the file already has non-zero length you shouldn't write it again07:00
pittisyntactically it should be ok (ioctl_tree_* should just ignore @DEV entirely), but it would look confusing07:00
RAOFOr we could support loading for multiple things, with a little bit of extra effort in umockdev.vala07:00
RAOFIf you don't think loading for multiple things is likely to be valuable (it's not something I want at the moment), just suppressing it for non-zero file lengths is fine.07:01
pittihm, I wouldn't want to stuff traces from multiple different devices into one .ioctl file TBH07:01
pittithe format and its traversing is complicated enough as it is07:01
RAOFSweet.07:01
RAOFSo, should umockdev-record error out if it tries to append something from a different device node?07:02
pittithere should be an assertion07:02
pittiit Should Not Happen™, so it doesn't need to be a fancy error message07:02
pittioh wait07:02
pittiif one umockdev-record sessio opens the device multiple times, it can't happen07:03
pittibut you can record into the same file multiple times, indeed07:03
pittiRAOF: so yes, then umockdev-record should error out07:03
RAOFGood.07:03
pittiif we want to support that at some point, we can do that without breaking compatibility07:03
RAOFIndeed. It wouldn't be _super_ hard to do (read in the file in umockdev.vala, split it out into the apropriate ioctl files), but I don't know if it's _useful_ :)07:04
pitti*nod*07:05
pittiRAOF: yeah, I'm more concerned about user confusion than implementation07:05
pittimlankhorst: tested ppa7, I followed up to bug 127873707:21
ubottubug 1278737 in xorg (Ubuntu Trusty) "Upgrade to trusty fails from precise backported enablement stacks" [High,In progress] https://launchpad.net/bugs/127873707:21
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
mlankhorstpitti: well it seems that multi-arch: no is required on newer ubuntu, but precise used multi-arch: none..08:33
mlankhorstI'll just skip that field altogether08:34
pittiif it's not there, it should be similar to M-A: same, right?08:34
mlankhorstno it skips to multi-arch: none I guess08:35
mlankhorstwhich is what's needed08:35
dholbachgood morning08:41
mlankhorstpitti: yeah I fixed m-a none, can you still hit the geode issue?09:15
* pitti boots the precise live system09:16
pittimlankhorst: confirmed, no held back packages any more; great!09:25
mlankhorstgood09:26
pittimlankhorst: want to upload? I can do the NEWing, and then re-run the full upgrade tests09:26
mlankhorstI can't upload, tjaalton? :P09:26
tjaaltonpush it to git09:27
pittimlankhorst: I can sponsor it, if you want09:27
pittimlankhorst: (with dropping the ~ppa suffix)09:27
tjaaltonhm can't use git since it had the merge from debian already staged09:27
pittiit's a new source package09:28
tjaaltonah09:28
tjaaltonok then :)09:28
pittiand it'll get removed in trusty+1 again09:28
mlankhorsthttps://mblankhorst.nl/etc/ xorg-lts-transitional*09:28
pittiso probably not worth the trouble09:28
tjaaltonI thought it was xorg source modified09:28
tjaaltonsure09:28
mlankhorsttjaalton: no way I want to have this hit version control09:28
mlankhorst:P09:28
tjaaltonhehehe09:28
tjaaltonno complaints there09:28
mlankhorstpitti: at one point you need to upgrade and confirm whether /usr/lib/xorg/protocol.txt still exists09:30
pittimlankhorst: *nod*; is its existance enough, or should we assert some contents?09:31
pittimlankhorst: I can add that as a post-upgrade test09:31
mlankhorstno, existence is enough09:31
pittimlankhorst: and protocol-{precise,*}.txt should not exist any more?09:32
mlankhorstI'm also curious about "update-alternatives --config x86_64-linux-gnu_gl_conf" after upgrade09:32
mlankhorstpitti: just protocol-precise.txt that exists09:32
mlankhorstit's overridden by xserver-common09:32
pittimlankhorst: I mean after the upgrade09:32
mlankhorstyeah protocol-precise.txt should be gone09:32
pittiin trusty we certainly don't expect protocol-precise.txt any more, or do you?09:32
mlankhorstit was a diversion added by xserver-common-lts-w/e09:33
pitti*nod*09:33
pittimlankhorst: hm, no copyright file, I'll add a simple one09:37
mlankhorst'not eligible for copyright' really!09:37
mlankhorstthere are no contents either! :-)09:37
seb128slangasek, infinity, cjwatson: does any of you have a strong objection to restrict the list of archs for firefox to amd64/armhf/i386? (same as chromium) It fails to build on arm64/ppc/ppc64 and noboby seems to have available slots to work on those issues, meanwhile that blocks migration to trusty and means we are 3 versions behind (we never had a version built on the trusty toolchain yet)09:39
seb128chrisccoulson, ^09:39
dokoseb128, there are patches for arm64, which were once overwritten by chrisccoulson09:41
seb128doko, those patches were not upstreamed and we don't have the resources to distro maintain them and rebase on new versions by ourself09:41
dokojamespage, 1268915 is still incomplete. could you subscribe?09:41
chrisccoulsonindeed, and they only make it build. without a jit compiler for arm64, it would be even more unusable than the current arm build09:42
chrisccoulsonwhich is already terrible09:42
jamespagedoko: done09:43
chrisccoulsonit looks like ppc actually builds, but then crashes when creating the startup cache. that needs someone with real hardware to debug that really09:44
seb128not having a porting box for ppc doesn't help there09:45
pitti@pilot in09:51
=== udevbot changed the topic of #ubuntu-devel to: Trusty Tahr Alpha 2 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: pitti
seb128ups, pitti went offroad09:58
seb128pitti, easy on the piloting ;-)09:59
* seb128 hugs pitti (just saw the ibus-pinyin sync)09:59
pittiseb128: yeah, sorry about taht; already undid my damage09:59
seb128no worry09:59
seb128happyaron filed the libpyzy MIR and mterry already did a first review, good10:01
Guest3895seb128: hey10:03
=== Guest3895 is now known as happyaron
happyaronseb128: hey10:03
seb128happyaron, hey10:03
seb128lol, I was looking for you, I even looking in the calendar to see if you were off10:04
happyaronseb128: shall I subscribe desktop team for libpyzy?10:04
happyaron:)10:04
seb128happyaron, "desktop-bugs" is our bugs team10:04
seb128so yes10:04
seb128or let me know if you don't the rights to do that10:04
happyaronseb128: I can't subscribe it on LP, :(10:05
darkxstpitti, pilot, can you take a look at the gnome-ey stuff in the queue10:06
seb128darkxst, from #ubuntu-desktop backlog, seems he's already doing10:07
darkxstseb128, boom :( gdm still restarting ;(10:08
seb128darkxst, did you try twice?10:08
seb128darkxst, it's the prerm from the installed version that stops it10:08
pittidarkxst: I'm at gnome-menus ATM10:09
seb128darkxst, so when installing the new fixed deb it's going to restart, because of the prerm of the installed version, then it should work10:09
darkxstseb128, yes, right, it worked second time10:09
Laneyyou should sed the prerm of the old one ;-)10:11
* Laney RUNS10:11
darkxstpitti, there is also lp:~noskcaj/+junk/gnome-photos, I told Noskcaj to file a bug but he didnt ;(10:11
Laneyoh actually I don't think you can10:12
Laneyhttps://wiki.debian.org/MaintainerScripts?action=AttachFile&do=get&target=upgrade.png10:12
pittidarkxst: bug 127920110:15
ubottubug 1279201 in Ubuntu "[needs-packaging] gnome-photos" [Wishlist,Fix committed] https://launchpad.net/bugs/127920110:15
darkxstpitti, ah, ok10:18
pittidarkxst: ah, gnome-photos landed in the NEW queue 23 mins ago10:19
darkxstyes, I see that now10:20
tjaaltonhum, trusty doesn't seem to recognize win 8.1 at all.. the partitioner says the disk is empty10:20
RAOFtjaalton: And yet grub finds it just fine!10:24
tjaaltonRAOF: didn't go that far yet, this is still the installer10:24
tjaaltonand I'd like to keep win8.1 there, if only just for civV which just crashes here on wine :)10:28
RAOFOh, indeed.10:29
RAOFYou should probably also want to keep XCOM:EW :P10:29
tjaaltondon't have that one, yet anyway :)10:32
cjwatsonseb128: there are a *lot* of rdepends on firefox - for instance packagekit's arch-specific build-depends would need to be tweaked if we were removing firefox/powerpc.  I can see your point but it needs actual thought and hard work following the rdepends stack and thinking about it rather than just restricting the arch set10:34
cjwatsonit's probably tractable, but please make sure that that work is done rather than just left to +1 maint or something10:35
seb128cjwatson, thanks for pointing that out. What would be the right place to have that discussion? ubuntu-devel@?10:35
cjwatsonSeems reasonable, yeah10:35
seb128thanks10:39
spineaudoko: hello, could it be possible to move to main the following checkbox dependencies? bug 1277408 and bug 1278822. So that our next upload of checkbox can have all its dep in main10:39
ubottubug 1277408 in checkbox-ng (Ubuntu) "[MIR] checkbox-ng" [Undecided,Fix committed] https://launchpad.net/bugs/127740810:39
ubottubug 1278822 in plainbox-provider-checkbox (Ubuntu) "[MIR] plainbox-provider-checkbox" [Undecided,Fix committed] https://launchpad.net/bugs/127882210:39
pittiRAOF: oh, to clarify: (1) do you want to work on the load_ioctl(NULL) thingy, and (2) do you want a release now or wait on (1)?10:40
RAOFpitti: (1) yes, and (2) yes, please wait.10:41
tseliotcjwatson: QA caught an issue with Jockey in 12.04.3 (hybrid graphics won't work with the new X stack). I've filed bug #1279229 and uploaded a fix in precise-proposed10:41
ubottubug 1279229 in jockey (Ubuntu) "Jockey is unable to check Saucy's xserver ABI" [High,In progress] https://launchpad.net/bugs/127922910:41
pittiRAOF: ack, thanks10:42
RAOFpitti: Also - do we get DEP-8 tests run on syncs from Debian? I added some to fsharp, but they don't seem to have been run.10:42
pittiRAOF: we generally do, yes10:42
LaneyThey get missed on the first upload AFAIK10:42
pittithat was fixed10:42
pittiRAOF: très interessant, I'll have a look at that later10:43
LaneyWell then, :)10:43
RAOFJust to check - they should show up on https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/ if they get run, right?10:43
pitticorrect10:43
pittiTestsuite: autopkgtest10:43
pittithat looks fine to me, too10:43
pitticjwatson: is https://code.launchpad.net/~dannf/ubuntu/trusty/base-installer/arm64/+merge/199972 something you'd rather handle yourself, or should I sponsor this?10:45
cjwatsonI'll take care of it, I did most of the rest of that stuff at the core sprint10:46
pitticjwatson: ack10:46
cjwatsonjust ran out of time there10:46
pittihttps://code.launchpad.net/~dannf/ubuntu/trusty/base-installer/arm64+calxeda-subarches/+merge/199977 as well then, I assume10:47
pitti(which includes the previous MP)10:47
cjwatsonyeah10:48
seb128happyaron, desktop-bugs subscribed to libpyzy now10:49
happyaronseb128: great10:49
tjaaltonmy partman bug was already reported https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=73173610:56
ubottuDebian bug 731736 in debian-installer "partman doesn't detect GPT partitions installed Windows 8.1" [Important,Open]10:56
tjaaltonhuh, why are we still on parted 2.3?11:08
tjaaltonfound debian #64613011:10
ubottuDebian bug 646130 in parted "parted versions lags behind" [Normal,Open] http://bugs.debian.org/64613011:10
tseliotcjwatson: did you get my message?11:33
cjwatsontseliot: probably best not to rely on just me for all things precise since I need a break from it after 12.04.4, but I'll have a look at this SRU I guess11:35
pittimlankhorst: oh, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html11:36
pittimlankhorst: xserver-xorg-video-geode-lts-* mustn't be built on amd6411:36
Laneybdrung: Is there a way to use ubuntu-distro-info to get the full name (-r) of the current release?11:37
cjwatsontseliot: ok, looks reasonable11:37
bdrung_workLaney, current release = the latest stable release?11:38
Laneybdrung_work: the one you're running it on11:38
pittimlankhorst: fixing..11:39
Laneyor maybe going from codename to release would be okay11:39
Laneytrusty → 14.04 LTS for example11:39
cjwatsontseliot: (accepted)11:39
bdrung_workLaney, no. distro-info has no info what release you are running on11:39
bdrung_workcurrently it does not support a codename -> fullname/release mapping11:40
tseliotcjwatson: ok, thanks a lot11:40
seb128bdrung_work, hey, did you get my email about Sweetshark's libroffice's ppu application?11:41
Laneyxnox: ^11:41
LaneyI read that as 'patches welcome'11:41
bdrung_workseb128, probably. i'll hope to find time to process my mail backlog at the weekend11:42
seb128bdrung_work, good ... is that application still blocked on anything?11:42
pittimlankhorst: http://paste.ubuntu.com/6919521/11:42
xnoxbdrung_work: Laney: thanks.11:43
bdrung_workseb128, i have to look into the mail and look at the progress of the last month11:43
bdrung_workxnox, yes, patches are welcome11:44
seb128bdrung_work, do you think you are going to have slots to do that soon? if not can you delegate to other ppu members?11:44
seb128bdrung_work, that application is ongoing for ages and we feel like we addressed all the initial concerns, it would be nice to see things moving or have an update on what more should be done11:45
bdrung_workseb128, i'll try to do it on the weekend. otherwise i have to delegate it.11:45
seb128thanks11:45
bdrung_worksince i have a job, my free time is heavily reduced11:46
=== _salem is now known as salem_
xnoxbdrung_work: may i upload https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1012439 ?11:51
ubottuLaunchpad bug 1012439 in debootstrap (Ubuntu) "carve out distro information to distro-info package" [Undecided,Confirmed]11:51
Laneythat's a long week :P11:52
bdrung_workxnox, you may :)11:52
bdrung_worki think there was an objection against this patch11:53
deniswhi11:53
xnoxLaney: like my accidental 6 month holliday?! =)11:53
Laneyaccidents happen right11:53
Laneyanyway I heard we know one of the debootstrap maintainers ;-)11:54
deniswwas it a deliberate decision to have the desktop web apps integration use the touch-optimized webbrowser-app in trusty? will that app be made more desktop friendly before the trusty relase?11:54
bdrung_workxnox, bonus: get the patch into debian11:55
xnoxLaney: debootstrap maintainers? who is that? =)11:57
bdrung_workhttp://packages.qa.debian.org/d/debootstrap.html11:57
cjwatsonxnox: please don't diverge debootstrap in Ubuntu, it's hassle12:01
xnoxcjwatson: ok.12:02
cjwatsonxnox: that latest version of the debootstrap patch is probably ok, but if we use it it should be in Debian12:03
cjwatson(case in point, I just synced debootstrap)12:03
=== freeflying_away is now known as freeflying
cjwatsonxnox: but hey, you're in the d-i team these days12:04
mardycjwatson: hi! I updated https://code.launchpad.net/~mardy/click/lp1245826/+merge/20467412:10
cjwatsonmardy: ack, will look later today, trying to finish something else off12:18
dokobdmurray, did you find out anything about the php issues?12:20
shadeslayerso if I run : grep-dctrl -P kde4libs -F Build-Depends /var/lib/apt/lists/es.archive.ubuntu.com_ubuntu_dists_trusty_main_source_Sources   : it seems to give me the entire kde4libs source information, but I explicitly told it to give me the Build Depends field, any ideas what I'm doing wrong?12:21
cjwatson-F is "search by this field"; if you want "show this field" you need -s instead12:22
shadeslayerahh12:23
mlankhorstpitti: can you make xserver-common* architecture: all ? and I want to point out that you matched with *geode** :P12:25
apacheloggerpitti: any objections to modifying the apport cleanup cronjob to also clean the drkonqi files we create through kdelibs?12:27
pittiapachelogger: fine for me12:28
=== MacSlow is now known as MacSlow|lunch
dokojamespage, why did you drop the juju gccgo binaries for x86? are these builds still being tested?12:38
jamespagedoko, not any longer12:39
dokojamespage, are any gccgo binaries being tested?12:40
jamespagedoko, on ppc64el and arm64 yes12:40
dokook12:40
jamespagedoko, oh - and upstream will be checking with gccgo still so we don't regress those platforms12:41
dokoupstream?12:41
jamespagedoko, juju team12:41
dokoahh12:41
apacheloggerhm12:49
apacheloggerpitti: apport's cron actually excepts whoopsie's .upload*, do you simply leave them around since they are 0byte anyway?12:50
pittiapachelogger: they are cleaned up after 7 days12:51
pittiapachelogger: I guess ev did it that way to avoid cleaning up crahses which have an .upload but not an .uploaded yet, or so (but I'm not sure, it woudln't work that way)12:51
apacheloggermh12:52
apacheloggerpitti: ok, going hold on to that then since the drkonqi stuff is related ^^12:52
pittimlankhorst: WDYT? http://paste.ubuntu.com/6919792/12:53
mlankhorstpitti: looks good!12:54
pittiuploaded12:54
mlankhorstmaybe that will fix the weird issue12:54
rbasaktjaalton: just looking at bug 1278898. The server team aren't actively looking after cobbler now, since the MAAS team stopped depending on it. I also note that there's no Debian package for this now. Are you happy to continue caring for the package in universe, or should we drop it?13:00
ubottubug 1278898 in cobbler (Ubuntu) "cobbler-web: import error with django 1.6.x (trusty)" [Undecided,New] https://launchpad.net/bugs/127889813:00
tjaaltonrbasak: there's a new upstream bugfix release to address that, I'll push that to trusty soon13:00
tjaaltonpackaging has been in collab-maint git, but guess there's no itp for it yet13:01
rbasakAh, OK. Thanks!13:01
apacheloggerpitti: https://code.launchpad.net/~apachelogger/apport/cleanup-drkonqi-files/+merge/20595513:01
=== MacSlow|lunch is now known as MacSlow
pittiapachelogger: bah, this is rather hard to read :)14:03
pittiapachelogger: i. e. this cron job does *not* remove drkonqui files after 7 days, while current apport does?14:04
apacheloggerpitti: what, for me the find returned the drkonqi files with mtime >7days14:05
apacheloggeralas, the find syntax is nigh unparsable to my puny mind14:06
pittiapachelogger: oh of course, I missed the -o14:07
apacheloggerpitti: ^^14:07
pittiapachelogger: merged, danke; how soon do you want/need this in trusty?14:08
pitti(probably not that urgent, right?)14:08
apacheloggerpitti: not urgent14:09
apacheloggerthanks for merging :)14:09
seb128hum, what's the best way to run checkrdepends nowadays?14:48
* seb128 is reading https://wiki.ubuntu.com/ArchiveAdministration#NBS14:48
pittiseb128: reverse-depends from ubuntu-dev-tools AFAIK14:49
pittiit's fast, and reasonably correct14:49
seb128that needs a local mirror right? do we have an archive admin available box recommended for that?14:49
pittino, it reads from LP or UDD or something like that14:49
rbasakAh, handy. Thanks!14:49
seb128pitti, I was speaking about checkrdepends14:50
pittia local mirror is an incredibly heavy beast, I doubt that many people have one14:50
pittiseb128: so was I14:50
seb128 reverse-depends gnome-control-center-signon-autopilot14:50
seb128No reverse dependencies found14:50
seb128pitti, it errors out out on14:51
seb128IOError: [Errno 2] No such file or directory: '/home/ubuntu-archive/mirror/ubuntu/dists/trusty/main/source/Sources.gz'14:51
seb128for me14:51
seb128  -B ARCHIVE_BASE, --archive-base=ARCHIVE_BASE14:51
seb128                        archive base directory (default: /home/ubuntu-14:51
seb128                        archive/mirror/ubuntu)14:51
seb128or is archive base dir /var/lib/apt/lists?14:51
* seb128 tries14:51
pittireverse-depends src:gnome-control-center-signon14:51
pittiyou might want that?14:51
pittireverse-depends -b src:gnome-control-center-signon14:52
pittiand that for reverse build deps14:52
pitti(account-plugins and empathy in that case)14:52
seb128pitti, seems fine to delete the gnome-control-center-signon and gnome-control-center-signon-autopilot binaries then, right?14:53
seb128or am I overlooking something14:53
pittiseb128: gnome-control-center-signon has reverse depends14:54
seb128pitti, which one?14:54
pittiseb128: http://paste.ubuntu.com/6920308/14:54
pittidoes that look any different for you?14:54
seb128pitti, those all have a "unity-control-center-signon | gnome-control-center-signon"14:54
pittiaah14:54
seb128if I didn't overlook things14:55
pittifine then14:55
seb128pitti, should we change https://wiki.ubuntu.com/ArchiveAdministration#NBS to recommends using reverse-depends over  "checkrdepends -b"?14:59
pittiseb128: yes, sounds good; shell login is generally disabled now15:00
seb128cjwatson, infinity: ^15:00
seb128pitti, danke15:00
geserpitti, seb128: reverse-depends queries a webservice on qa.ubuntuwire.org15:02
cjwatsonok15:02
cjwatsonLet's still keep checkrdepends around though; for those with access to it it has stronger guarantees of being current15:02
seb128on what box can that be run? pepo?15:03
seb128(seems I don't have ssh to that one)15:03
cjwatsonubuntu-archive@snakefruit15:03
seb128cjwatson, thanks15:04
bdmurraydoko: no, not yet15:04
dokopitti, does dbus in trusty diverge that much from unstable? https://launchpadlibrarian.net/164705202/buildlog_ubuntu-trusty-i386.python-notify2_0.3-2_FAILEDTOBUILD.txt.gz15:12
seb128doko, ** (notification-daemon:2593): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files15:12
seb128doko, seems like you are missing a depends on at-spi or something15:12
seb128or at-spi2-core rather to be exact15:13
dokoseb128, it did build before ...15:13
pittidoko: it's not dbus itself, something in gtk/whatever now requires at-spi2-core15:15
mitya57I think rather notification-daemon should depend on that15:15
pittimitya57: agreed15:16
seb128speaking of notification-daemon, if anyone still uses it/cares about it, it needs to be fixed for incorrect g_source_remove use15:16
seb128that's an issue with new glib and is ranked high enough on the trusty reports15:17
seb128on e.u.c15:17
mitya57Hm, no, neither notification-daemon nor python-notify2 reference a11y in the code15:17
pittiI've seen this quite often recently15:18
pittimy suspicion is that it's something in GTK, and that gtk itself should depend on it15:18
seb128pitti, libgail-3-0 depends on at-spi2-core15:19
* seb128 doesn't understand the a11y stack enough to figure what's the right thing to do there15:20
seb128I though libgail was needed for a11y?15:20
pittithat build log doesn't install gail, though15:20
seb128pitti, https://launchpad.net/ubuntu/+source/gtk+3.0/3.5.8-0ubuntu115:20
seb128that's where it got added15:21
seb128I think GTK upstream has been working on dropping gail and moving a11y directly in gtk15:21
seb128so yeah, maybe having libgtk-3-0 depending on it would make sense15:22
seb128would be useful to get a bt of those warnings15:22
seb128to see what is the caller15:22
pittiG_DEBUG=fatal-warnings?15:25
mitya57G_DEBUG=fatal_warnings (with underscore)15:26
mitya57or maybe dbus-monitor15:26
seb128thanks guys, I know how to get one15:27
seb128I'm just dealing with 5 stuff already so I was hinting in case somebody has the setup to trigger the warning15:27
seb128I can try in a bit otherwise15:27
seb128;-)15:27
* seb128 usually do "b g_log" instead15:28
seb128so you can go pass the first warning15:28
* mitya57 is in battle with mathjax packaging, so not now15:28
dobeycjwatson: can we install a hook or something from the click scope, that gets run whenever a click package is installed (like a dpkg trigger but for click)?15:30
cjwatsonclick packages can attach to hooks; there's no way to write a hook that will run for *any* click package installation right now15:31
cjwatsonthat's possible, would need to be specced with some thought15:31
dobeycjwatson: oh ok. i was just thinking that it would be nice for the click scope to be refreshed when i adb shell and install a click package that way (or do it from qtcreator or whatever)15:32
cjwatsonI suppose the simplest way would be to make the Pattern field (https://click.readthedocs.org/en/latest/hooks.html) optional, in which case no symlink would be created and we'd just run whatever Exec says15:32
cjwatsonwould that work for you?15:33
cjwatson(if so, please file a bug, I'm not going to get to it this week)15:34
dobeyi'm not sure, but probably.15:34
dobeyright, we're in a bit of rush on scope development right now as well. so if we can't do it right now, it'll have to wait a bit anyway15:34
dobeybut i'll read the hooks doc and let you know15:35
cjwatsonwell.  I could maybe do it on Thu/Fri if it's a simple enough approach, but it'd be my first proper release under the ci train stuff so I can't guarantee it15:36
dobeycjwatson: yeah, no worries. i don't want to block the scope work on it so we're going to have to do the results invalidation call a different way for now. but i'll see if your suggestion makes sense (or if i think of something better while reading the docs), and file a bug15:45
cariboupitti: I see that you have merged my clamav MP, though I thought it was still waiting for a fix15:51
cariboupitti: I just updated the MP with a potential modification15:51
pitticaribou: I posted the modification I did to the MP and to the bug15:52
cariboupitti: yeah, just seeing the emails15:53
cariboupitti: my suggestion was to replace the [[:space:]] with \b as the reasoning behind that is to be able to discriminate on word boundary15:53
pitticaribou: \b looks fine as well, but [[:space:]] should work equally well15:54
cariboupitti: I do think so. So let keep it as it is then15:54
pittiafter all, you could potentially have a variable Logfile-Destination /dev/null15:54
pittiand \b would match after LogFile15:54
pitti(perhaps)15:54
cariboupitti: I'll fix the debdiffs in the bug15:54
pittiI mean, I don't know whether clamav allows that15:54
pittibut [[:space:]] seems fine15:55
cariboupitti: dunno. I'll open a bug on this on Debian15:55
pitticaribou: thanks, appreciated15:55
cariboupitti: thanks for the merge, I'll get the SRU fixed15:55
=== Sweetsha1k is now known as Sweetshark
pitticaribou: I already fixed the precise SRU15:56
cariboupitti: ah, ok then I won't bother15:56
=== cmagina_ is now known as cmagina
cariboupitti: such a small fix15:56
psusihow can I get an rdepends on udebs?  possibly using the package cache within a d-i build tree?15:56
cariboupitti: btw, I had the same issue with UDD and the time it took to check it out15:57
roadmrHello! My source package stopped building some now-deprecated binaries, so the new upload is in -proposed with a series of "out-of-date" on the deprecated binaries. How can I fix this? do the old binaries need to be removed?15:57
seb128roadmr, you need an archive admin to delete the NBS binaries I think15:58
stgraberroadmr: what source package is that and what binaries did you drop?15:59
psusiahh, figured it out...15:59
roadmrstgraber: source: checkbox, dropped binaries: checkbox-gtk, checkbox-urwid16:01
stgraberroadmr: ok, taking a look now16:01
cjwatsonFWIW this only happens if the binaries were dropped in a subsequent upload when there was already an unmigrated upload in -proposed16:01
cjwatsonit's a corner case due to -proposed being a partial suite16:01
roadmrstgraber: also, my source package was building python3-checkbox-support which exists only in -proposed, but that overlaps the same package (version 0.1 I think) from debian. I fixed this but I guess the stale binary stayed in proposed and is also considered out-of-date16:02
psusiwait... maybe not... those are non udeb rdepends somehow...16:02
stgraberroadmr: you actually have a bigger problem, you regressed architecture support16:02
pitti@pilot out16:02
=== udevbot changed the topic of #ubuntu-devel to: Trusty Tahr Alpha 2 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
stgraberroadmr: checkbox used to build on all architectures, now it fails on arm64, powerpc and ppc64el16:02
=== freeflying is now known as freeflying_away
roadmrstgraber: I saw it failing due to lack of some qt5-sensors dependency, but it's not actually needed, my latest upload should have fixed that. I can double-check that too16:03
stgraberroadmr: I'm looking at https://launchpad.net/ubuntu/+source/checkbox/0.17.4ubuntu316:04
roadmrstgraber: oh, I removed the qtsensors5-dev dep but now it's stuck on qtmultimedia5-dev16:05
stgraberroadmr: so I resolved the pytohn3-checkbox-support bit for now, I'll let you upload something which fixes those 3 arches then we can see what britney thinks about migrating those16:06
stgrabercjwatson: right, python3-checkbox-support was in that case (introduced in ubuntu2, dropped in ubuntu3, never migrated)16:06
roadmrstgraber: cool, thanks so much! I'll fix that asap16:07
alowinfinity: Would like to chat about PPC64el and libv816:15
infinityalow: Perhaps when I'm out of this current meeting/call.16:17
infinityalow: I meant to follow up to your email, but I've been headless chickening the last day or two.16:17
alowinfinity: no problem. I've been hacking away to create minimal diffs between the v8 levels. I've created a unique branch for libv8 https://github.com/andrewlow/v8ppc/tree/libv8-3.1416:18
infinityalow: Awesome.  And, as an added bonus (not a requirement, but a bonus), I understand this works on big-endian as well?16:19
alowinfinity: It should - I haven't tested that specifically. I'd be happy to hit both BE / LE16:19
alowinfinity: I'm off on vacation soon for a bit, so it'd be good to get this working for others soon16:20
infinityalow: Righto.  I will probably end up testing on ppc32be by accident, since that's my primary development workstation in my house. :P16:20
infinityalow: I'll try to find some time to poke at it today, after I throw some time at glibc stuff this morning.16:20
alowso my repo https://github.com/andrewlow/v8ppc/tree/libv8-3.14 doesn't include the debian/ directory in it (yet) - would that be preferred?16:21
infinityalow: No, no.  A simple branch of upstream is much easier to work with, importing debian directories and spec files tends to end in tears when they diverge from the distros anyway.16:21
alowinfinity: oh good. so.. from here http://packages.ubuntu.com/source/trusty/libv8-3.14 I took the repository git://anonscm.debian.org/collab-maint/libv8.git and used that as a comparison base for  https://github.com/andrewlow/v8ppc/tree/libv8-3.1416:22
alowwhen I mix in a slightly hacked debian directory to support ppc64el -- I get .deb files out the other side16:23
infinityA positive result. ;)16:23
infinityDoes it run a testsuite at build time?  I haven't looked at v8 packaging.16:24
alowinfinity: one caveat - I don't understand how the debian/patches directory gets applied. So I run the makefile / gyp patch manually16:24
alowinfinity: yes - testsuite gets run16:24
alowinfinity: >>> Running tests for ppc64.release16:25
alowConverting status file.16:25
alowConverting status file.16:25
alowConverting status file.16:25
alowNo connection to distribution server; running tests locally.16:26
alow[01:28|% 100|+ 6093|-   0]: Done16:26
infinityalow: Kay, cool.  As for patches, that depends on the source format, but if it's 3.0(quilt), the patches are applied at source unpack by dpkg.16:26
infinityalow: Based on the debian/patches/series file.16:26
alowinfinity: Ok - I'm not sure I've setup things correctly in my builds then. I'll poke at that. I start with the source tree in place and use 'fakeroot debian/rules binary' to build16:27
alowinfinity: but I'm fairly confident my code in the repo is suitable for the build at this point16:27
alowinfinity: patches may not all apply clean - I'll try to validate that16:28
infinityalow: Kay.  Will you be around in ~30m, when I'm not multitasking too much here? :)16:29
pittimlankhorst: success!16:29
alowinfinity: yes16:29
pittimlankhorst: I'll add the protocol.txt post-upgrade test tomorrow; we don't keep around the container after upgrade, so I can't check right now16:30
pittimlankhorst: I filed bug 1279411 as a reminder, does that sound right?16:33
ubottubug 1279411 in Auto Upgrade Testing "check for /usr/lib/xorg/protocol.txt after upgrade" [Undecided,New] https://launchpad.net/bugs/127941116:33
mlankhorstpitti: thanks16:33
infinityalow: Alright, grabbing the Debian source and cloning your git repo and having a morning smoke.  I'll be with you shortly. :P16:46
alowinfinity: cool - I'm around16:46
pittimlankhorst: http://bazaar.launchpad.net/~auto-upgrade-testing-dev/auto-upgrade-testing/trunk/revision/90 (tested locally)16:49
infinityGah, only 250KB/s from github?  Internets, why do you hate me this morning?16:50
pittimlankhorst: rolled out, I'll check the results tomorrow16:51
pittimlankhorst: you are right: http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-precise-trusty-desktop-lts-raring-i386/13/artifact/results/bootstrap.log16:59
pitti- ['/usr/lib/xorg/protocol-precise.txt', '/usr/lib/xorg/protocol.txt']16:59
pittimlankhorst: that's what's left after the lts-raring → trusty upgrade16:59
pittimlankhorst: so the diversions should be cleaned up17:00
pittimlankhorst: I filed bug 127942417:02
ubottubug 1279424 in xorg-lts-transitional (Ubuntu) "Needs to clean up /usr/lib/xorg/protocol-precise.txt" [Undecided,New] https://launchpad.net/bugs/127942417:02
pittijibel: ^ FYI (in case you wonder why green tests go back to yellow)17:03
jibelpitti, thanks for adding new tests. I'm pretty sure you can find tests that will make it red :)17:03
pittiat most yellow, I hope17:05
tester56will vlc 2.2 land in trusty?17:08
Logan_tester56: does it even have an ETA?17:10
tester56Logan: oh damn ... I do not know, sorry for that. As I have it running here, I supposed it was released already, my mistake sorry for the inconvenience. It has been in development for quite some time now if I am not mistaken17:13
Logan_haha, no need to apologize17:13
Logan_if it lands before Feature Freeze, we can likely maneuver it into trusty, but I'd rather go with Debian's releases17:13
Logan_and Feature Freeze is in eight days, so it doesn't look like that'll be happening :P17:14
Logan_unless there's a good reason to merge it in17:15
cjwatsonCoo, ci.debian.net exists17:21
cjwatsonJust noticed it from my qa.debian.org/developer.php page17:21
=== Lutin is now known as Guest51635
roadmrstgraber: We introduced a few new build-deps (and dependencies) for checkbox, and some aren't available for those archs (arm64 and ppc). That's where my arch support regression comes from.17:28
stgraberroadmr: does checkbox absolutely need those or could you have ti build on those arches without those build-deps?17:29
stgraberroadmr: (making those arch-specific build-deps and deps and have checkbox do the right thing at build time)17:29
mptbdmurray, I see the new color for 14.04 is on <https://errors.ubuntu.com/>, but the milestone lines aren’t. Does that mean there’s something wrong with the milestone line code, or is it just that the rollout included the former but not the latter?17:30
roadmrstgraber: they're actually for a new checkbox-gui binary, maybe we could do what you say and then checkbox-gui would just be unavailable for those archs17:30
mptbdmurray, or a simpler way of asking the question: What revision is the current rollout? :)17:32
stgraberroadmr: I guess that'd be reasonable, yes, make checkbox-gui arch:any and only building on the arches that have those bits, changed your build depends to also be arch-specific and change your build process so that it only attempts to build the GUI bits if those build-deps are present.17:34
bdmurraympt: rhe rollout included the milestone colors, so it may be something with the graph code17:34
mptok, thanks17:34
roadmrstgraber: ok, sounds good, I'll get working on this. Thanks so much for your help and guidance!17:35
stgrabernp17:36
Logan_does anyone else run trusty in a VirtualBox VM? I'm having screen resize issues with the latest update17:47
Logan_debfx: ^17:49
=== Trevinho_ is now known as Trevinho
seb128do we have arm64 porter boxes?18:01
seb128http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt has18:01
seb128skipped: gnome-control-center-signon (52 <- 1)18:01
seb128    * arm64: unity-control-center-signon18:01
seb128not sure how to debug that18:01
infinityseb128: It means unity-control-center-signon is uninstallable on arm64...18:04
seb128infinity, yeah, which would be easier to figure out why if I had access to an arm64 chroot/porter box ;-)18:04
infinitySo, there isn't a porter box right now due to lack of hardware to go around.18:04
seb128how would you recommend trying to debug that?18:05
infinityseb128: Check your channel invites. :P18:05
seb128infinity, and why is unity-control-center-signon being uninstallable blocks migration when it's a new binary and has never been installable?18:06
alowBenC: infinity pointed me your way in regards to e500 v2 hardware. Today my v8 port doesn't work on e500 https://github.com/andrewlow/v8ppc/issues/100 - I'd like to fix, but need ready access to hardware18:24
BenCalow: I can get you access to e500mc, but I don't have anything for e500v2 (which, you probably shouldn't care about anyway)18:25
BenCalow: I can try a build on e500mc and let you know if that works or not...18:26
alowBenC: I know it won't work - check the data in the github issue I linked18:26
BenCalow: That data shows e500v2, which is not entirely the same as e500mc, so let me check18:27
alowBenC: if the basic floating point hasn't changed between e500mc and e500v2 - then either should work18:27
BenCalow: But it has...e500mc has hardware floating point and e500v2 uses softfloat (or mathemu in the kernel)18:28
alowBenC: the reason the code doesn't work is that we are generating FPU instructions - and the encoding is entirely different on e500 (mc / v2)18:28
BenCalow: I've cloned and started a build. In the meantime can you email me: ben.c@servergy.com and I'll get you ssh access to our RPLE server, which is e500mc/P4080 based.18:32
BenCACTION tools_gyp_v8_gyp_v8_snapshot_target_run_mksnapshot /home/svy/v8ppc/out/ppc.release/obj.target/v8_snapshot/geni/snapshot.cc18:43
BenCIllegal instruction18:43
alowBenC: yes - expected18:44
alowBenC: if you build with "make ppc snapshot=off" it will complete the build.. but crash on startup when it tries to generate FPU instructions into memory and run them (V8 is a JIT)18:45
BenCalow: I can give you access to the hardware if you email me an SSH pub key and username18:45
alowBenC: drat.. just hit send -- will follow up now with key & name18:46
BenCAh, thanks18:46
BenCalow: So the system has chroots. Probably makes no difference which one you use, but we want people to create a schroot env for their builds so we can easily isolate having to install build-deps if needed18:47
BenCalow: Instructions on how to use the setup is in the motd when you login18:47
alowk - will be a good citizen in that regard18:47
=== chuck_ is now known as zul
=== bfiller is now known as bfiller_afk
dobeykenvandine, robru: is there a way to make friends-service update from twitter more often? also, it seems to never actually pop up notifications on my workstation, but every time i boot my laptop, i get a bunch of notifications from it. :-/19:08
kenvandinedobey, you can change the interval in gsettings19:28
kenvandineand there is also a setting for notifications19:28
dobeykenvandine: yes, notifications is set to "mentions-only"19:29
dobeykenvandine: which is what i want, but i don't seem to be getting them.19:29
dobeyi do on my laptop though of course19:29
slangasekseb128: firefox ppc> I have no opinion on this, other than to reiterate that if there are issues with packages on the ports, this needs to be brought to the attention of the porters prior to give them a chance to respond /before/ it becomes a blocking issue for the desktop19:30
seb128slangasek, hey, how do I brought attention to the porters? trusty has a firefox which is outdated by 3 versions (and outdated compared to security pockets from other series by almost as much)19:42
slangasekseb128: for powerpc, I would say the first stop is to ping infinity about it :)19:42
seb128slangasek, it's not like the issue was not visible, it's just that nobody is stepping up to do anything about it, we are past mid-cycle and we got 0 firefox build with the trusty toolchain reaching the release pocket19:43
seb128infinity, ping :p19:43
seb128slangasek, done ;-)19:43
seb128infinity, slangasek: note that firefox "builds", the build fails on a cache generation error after the actual build is done, seeing that the same version works on other series it looks like a toolchain issue (due to the toolchain or to firefox doing wrong thing)19:44
slangasekseb128: it's visible /to you/ because you're paying attention to the package; build failure reports from launchpad go to the uploader, not to the porters19:45
slangasekso no, it's not fair to assume that a package build failure is "visible" to the porters unless someone lets them know it's blocking them19:46
seb128slangasek, right, I'm not especially paying attention, out of the fact that my firefox is outdated by 3 versions19:46
seb128slangasek, I wish we had a better way to flag such issues :/19:47
infinityseb128: Right, the toolchain pointer is an interesting hint.  It might be a workable workaround to build with an older GCC on ppc for now, though the actual problem should be hunted down.19:48
infinityseb128: It might also be an acceptable workaround to drop ffox and its rdeps from PPC for now, but I want to look into the impact of that before I go on a deletion spree.19:49
seb128infinity, I've said that before, and thanks for stepping up to provide us solution when that happened, but not having a porter box available doesn't help there19:49
seb128how the heck can we support an arch without having access to one box to debug issues?19:49
infinityseb128: A porter box is on my Very Soon TODO.  It got pushed back by an externally-imposed ABI break on ppc64el that I have to deal with this week.19:49
seb128infinity, that's good news ;-)19:49
seb128infinity, anyway, help on the firefox issue is welcome, we don't have a firefox maintainer anymore atm19:50
seb128chrisccoulson does what he can on his extra-work-hours time to keep it going19:50
seb128but he said several times that he doesn't have the free slots/motivations to deal with "exotic" archs (that includes ppc)19:51
infinityPretty sure, to most people, "exotic" is everything that their home computer isn't. :P19:51
seb128lol19:51
infinity(It just so happens that my home contains a lot of computers...)19:51
chrisccoulsonmy home computer isn't i386 or arm, but i'm happy to deal with those ;)19:51
seb128infinity, it's rather than we have to be given proof that anyone uses firefox on ppc and it's usable there19:52
infinityseb128: To be fair, I don't use a desktop on PPC either, mine are all servers.  So, yeah, I'm happy to examine the "just drop the binaries" option, but I want to poke the "why is it broken?" bit first.19:53
seb128infinity, thanks19:53
seb128infinity, I got that you are busy this week, do you think you can have a look before the end of the month?19:53
seb128infinity, I would like to see us publishing a firefox update in trusty before beta time19:54
infinityseb128: Yeah, I can commit to having a fix, one way or the other, before beta.19:55
psusicjwatson: quick question... partman-ufs is broken on linux so I got the monolithic image to build once after removing it from pkg-lists/standard-udebs... but this file seems to be auto generated somehow so it keeps getting put back.  how is this?19:56
=== zz_mwhudson is now known as mwhudson
infinityseb128: Although, I'm not seeing the toolchain change argument here, with rmadison output.  Looks like powerpc is missing for precise-updates too.19:57
infinityThe last version that built on ppc on any series was 25.19:57
seb128shrug19:57
infinitySo, 25->26 deltas and looking for stupid would be my first pass.19:57
seb128infinity, sorry, I saw the security/updates going through on other series, I assumed that's because they didn't regresses on archs19:58
infinityseb128: Nah, the security team will happily regress unsupported arches if they can't immediately sort out the breakage.19:58
seb128I didn't think we pushed through updates that don't build on all supported arches19:58
seb128k19:59
seb128I learnt something there19:59
seb128infinity, anyway, if you can help getting that resolved one way or another that would be appreciated ;-)19:59
* infinity nods.19:59
seb128I'm just chrisccoulson would join in buying you drinks at the next event19:59
infinityThis whole work-for-drinks thing needs to stop before my liver falls out.20:00
infinityI'm staring at a bottle of gin from Carlos, and wondering if it's going to kill me.20:00
seb128infinity, can buy you some vegetables if you prefer!20:01
sarnoldchrisccoulson also runs on steak, would that work? hehe20:01
infinityseb128: Steak? :)20:01
seb128oh, you said you want french cheese if I remember20:01
infinitySteak!20:01
seb128that works too ;-)20:01
infinityA few kilos of d'Affinois cheese wouldn't go amiss either.20:01
seb128hehe20:01
infinityIn fact, it's nice melted on top of a filet mignon.  Two for one.20:02
seb128lol, I see where you a going ;-)20:02
* seb128 starts wanting some steak20:02
seb128infinity, ok, gnome-control-center-signon built, I just deleted the arm64 debs from trusty/trusy-proposed since he can't work there (lack of qt5) and is depwaiting in the current upload20:12
seb128infinity, if there is still work needed, after the next run, please do your magic if you can ;-)20:12
infinityseb128: Alrighty.20:12
seb128thanks20:12
infinityseb128: That should have been all the magic required.  Hopefully your deletes didn't misfire and take out anything else this time. :P20:12
* seb128 hides20:13
seb128let's see, I'm confident I'm not going to screw twice in a day ;-)20:13
infinityThat sentence really needs another word to be significantly less embarassing.20:13
seb128screw -> screw up an Ubuntu upload? ;-)20:15
seb128see why french should be default, it would be easier!20:15
stgraberit'd be a lot less fun ;)20:17
infinityseb128: "up" was indeed the missing word. :)20:19
infinityseb128: Entirely different meaning without it. :P20:19
seb128;-)20:21
seb128I was going for fun, stgraber got it :p20:21
seb128anyway, let's see if britney is happy once the arm64 binaries are gone20:21
infinityShould be.20:22
seb128great20:22
infinityUnless something depends on the now-missing binaries.20:22
infinityBut if so, we should sort that anyway, not ignore it.20:22
seb128things depends on those yes20:22
seb128but those have never been installable20:23
infinityI'm going to go pizza hunting.20:23
seb128since they depended on qtdeclarative20:23
seb128infinity, if you have internet, or a phone, you can get pizza delivered ... rather than having to hunt for it. Just saying...20:23
seb128infinity, enjoy ;-)20:24
ogra_seb128, he probably likes the guns ;)20:24
seb128ogra_, did he move to Texas? ;-)20:24
ogra_maple syrup guns ;)20:25
jdstrandseb128: powerpc isn't 'supported' by us in that sense. amd64, i386 and armhf get security support. the other archs are along for the ride (https://wiki.ubuntu.com/SecurityTeam/FAQ#Architectures)20:25
seb128jdstrand, yeah, sorry I use "supported" for "existing"20:26
infinityjdstrand: Time to update the table for a new release and a new arch. :)20:27
jdstrandinfinity: yes, a couple of them :)20:29
jdstrandoh no, arm64 is already there20:29
jdstrandinfinity: and thank you for looking into ff/powerpc20:29
seb128infinity, \o/ that worked, g-c-c-signon migrated to trusty20:32
dobeyis it impossible to disable ctrl+super+left/right keybindings?20:33
seb128dobey, you tried ccsm?20:34
dobeyseb128: no, but tried dconf-editor, and don't see them in there. and setting them to a different action didn't help20:35
=== salem_ is now known as _salem
seb128dobey, I'm not sure, I think that's the grid plugin but you might want to ask Townsend when he's online, I think he cleaned that code previous cycle20:45
=== SpamapS_ is now known as SpamapS
infinityjdstrand: You might want to split that table in two, for historical and current, too.  Then the current one would have fewer arches, and fewer still next year.22:19
jdstrandyeah22:34
jdstrandI was thinking about that22:34
=== psivaa is now known as psivaa-afk
=== bfiller_afk is now known as bfiller
miseria"la verdadera felicidad de un ser humano, se logra cuando deja de ser esclavo, de la avaricia y la codicia" bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival*23:38

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