=== salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem === JanC_ is now known as JanC === fabo_ is now known as fabo === FJKong_afk is now known as FJKong [05:36] Just wondering, does Ubuntu have support for HEVC yet? Or is that a Win10 only thing for now? [05:36] And specifically version 3... [05:37] Anyone? [05:38] Because Android supports it... [05:38] And maybe I answered my own question, because VLC does... [05:38] !vlc [05:38] Audio (Ogg, MP3...) players: Audacious, Banshee, Listen, Quod Libet, Rhythmbox, Exaile, XMMS2 (GTK/Gnome based) and Amarok, JuK (Qt/KDE based). Video players: Totem, Xine, MPlayer, VLC, Kaffeine - See also !codecs [05:39] Version 2.2.0 I thinl [05:39] *think [05:39] I am just going to go with that :P [05:39] Thanks [07:38] hallyn_: ah, all services run in their own cgroup, you can't entirely "unconfine" them [07:38] hallyn_: as that's how systemd tracks service lifecycle, subprocesses, and reliable stopping [07:45] hi folks, is there a known issue with the 14.04.3 installer, very long filenames in the ISO? [07:45] block-modules-3.19.0-25-generic-di_3.19.0-25.26~14.04.1_amd64.ude [07:45] note the lack of a b :) [07:49] aren't isos limited to 64 characters in the first place? or is that just restriction of some old format? === mardy_ is now known as mardy === greyback_ is now known as greyback|shops [10:23] pitti, deja-dup-caja has been in the Wily new queue for a few weeks now. Who should I talk to to request it is promoted? [10:23] pitti, It is a feature I would like to land for Ubuntu MATE 15.10. === greyback|shops is now known as greyback [11:28] cjwatson: thanks for the details regarding that extra openssh patch, I was definitely wondering why it nobody reported it anywhere else, and I couldn't reproduce the issue myself even on precise. [11:29] mdeslaur: Yeah, my initial reaction was "hang on, why is that needed" [11:29] then git blame / git describe --contains ... [11:31] micahg, Hi I the lead for Ubuntu MATE. I wanted to land Blueman2 in Wily but I've been (and still am) on jury service for the last 3 weeks. [11:31] micahg, I see in mom that you've said you'll tackle the Blueman2 merge. Are you planning to do this for 15.10? [11:38] doko: -intel built on wily breaks 90/270 rotation, vivid binary works. please explain :) [11:40] tjaalton, missing context [11:46] doko: same source built on wily fails [11:46] all I can think of is the toolchain changes [11:47] tjaalton, ENOCONTEXT [11:47] xserver-xorg-video-intel, screen rotation is buggy on wily [11:47] enough? [11:49] filed a bug too 1486920 [11:49] bug 1486920 [11:49] bug 1486920 in xserver-xorg-video-intel (Ubuntu) "[regression] 90/270 degree rotation is broken" [Undecided,New] https://launchpad.net/bugs/1486920 [11:50] tjaalton, does this happen with the version found in -release too? [11:50] yes, the new snapshot doesn't break/fix things [11:51] the current one is basically the same as on vivid, plus some build-fixes [11:53] hmm, libxrandr did change [11:54] perhaps I'll try to comb through the libx* changes first [11:57] tjaalton, if this doesn't help, please try building the package with -O0/-O1 [11:57] ok I will [11:57] still at DebConf this week, so will be on/off [11:58] sure, this isn't super urgent anyway [11:58] just very puzzling.. === _salem is now known as salem_ [12:32] doko: nah, tried both -O0 & -O1, and building against older libxrandr, none worked [12:33] I'll update the bug and leave it for now === Elimin8r is now known as Elimin8er === imcleod is now known as imcleod_back_in_ === imcleod_back_in_ is now known as imcleod [14:38] rsalveti: could you send your upload in https://launchpad.net/ubuntu/+source/cifs-utils/2:6.0-1ubuntu2 upstream please? [14:39] rsalveti: it looks a bit odd to me, since the variable is named is_systemd_running and you're adding a check to see if it's installed. [14:40] rsalveti: (I'm reviewing a merge for kickinz1; the merge won't change behaviour to keep the delta so I will upload as-is, but it should be resolved) [14:48] Hi, As you may know, Onboard is the default on-screen keyboard of Ubuntu. We have just released a new micro update that contains among others a few bug fixes for wily. I have created a debianisation based on the package currently in wily. Could anybody with the appropriate privileges have a look at the sponsorship request before feature freeze kicks in? Thanks in advance. [14:48] https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1487009 [14:48] Launchpad bug 1487009 in onboard (Ubuntu) " New bugfix release of Onboard (debanisation for wily provided) " [Undecided,New] [14:54] frafu: does it include bugfixes only? Then you aren't affected by feature freeze. [14:58] rbasak: It is a new upstream release with bug fixes and also some small improvements for example in the auto-show feature and it also translation updates from rosetta. [15:03] rbasak: It is not the package currently in the repositories with new patches; it is a new release. The changes are listed in the bug description of the sponsorship request linked above. [16:01] rbasak: yeah, that was only needed when we were still using upstart [16:03] rsalveti: ah. It can be dropped now then? [16:03] rbasak: yes, we can just import latest from debian [16:04] kickinz1: ^^ [16:04] kickinz1: as it's feature freeze today maybe easiest to just keep the delta this time to avoid having to retest etc. We can drop it next cycle. It won't cause any harm. [16:34] seb128: Hi, I wanted to let you know that we created a new micro release of onboard, the default on-screen keyboard of Ubuntu. It contains several bug fixes for wily, so it might be good to have it accepted before feature freeze kicks in later today. I debianised the new release basing it on the onboard package currently in the main repo. You can find the debianisation in the following sponsorship request: [16:34] https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1487009 [16:34] Launchpad bug 1487009 in onboard (Ubuntu) " New bugfix release of Onboard (debanisation for wily provided) " [Undecided,New] [16:35] frafu, hey, sorry but I'm about to call it a day, I can have a look tomorrow, bugfixes updates are not subject to feature freeze [16:39] seb128: Thanks for looking at it tomorrow, but it does also contain some small improvements that might not be qualified as real bug fixes. There are however no new features. I hope it will be allright to get picked up also after feature freeze. [16:39] frafu, should be ok, you can still try to find another sponsor today as well [16:40] ok, thanks for your help [16:52] infinity: Hi, Would it be possible for you to have a look at the following sponsorship request before feature freeze kicks in? Thanks in advance. [16:53] https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1487009 [16:53] Launchpad bug 1487009 in onboard (Ubuntu) " New bugfix release of Onboard (debanisation for wily provided) " [Undecided,New] [17:03] coreycb, heyo! re: bug 1477668, why is mysqldb no longer suitable? i.e. why don't our openstack packages just use it instead? [17:03] bug 1477668 in python-pymysql (Ubuntu) "[MIR] python-pymysql" [High,New] https://launchpad.net/bugs/1477668 [17:07] mterry, hey! [17:08] this is an overview of why upstream openstack is moving to pymysql https://wiki.openstack.org/wiki/PyMySQL_evaluation [17:09] Ampelbein: Hi, As a member of the sponsorship team, do you have some time to look at the following request before feature freeze kicks in? [17:10] https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1487009 [17:10] Launchpad bug 1487009 in onboard (Ubuntu) " New bugfix release of Onboard (debanisation for wily provided) " [Undecided,New] [17:17] coreycb, so nova, tornado, and taskflow are in main and depend on python-mysqldb. As you mention in the MIR, ideally those are ported this cycle to use pymsql. Do you think that can happen? [17:17] It's feature freeze today; I don't know know whether that covers porting like that [17:18] mterry, yes, and we can handle that [17:19] pymysql is a drop in replacement for mysqldb so it shouldn't be a big deal [17:19] mterry, but yeah that's a good question re feature freeze. I imagine an exception would be allowed for that but not sure. [17:20] coreycb, excellent. I'm getting a test failure? Looks like it hasn't been rebuilt in the archive for a while... something may have bitrotten. Do you see a build failure? [17:21] mterry, let me look [17:22] coreycb, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796010 [17:23] Debian bug 796010 in src:python-pymysql "python-pymysql: FTBFS: InternalError: (1317, u'Query execution was interrupted')" [Serious,Open] [17:23] coreycb, looks like what I'm seeing [17:23] Hi coreycb, Do you know anybody who could look at the following sponsorship request: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1487009 ? [17:23] Launchpad bug 1487009 in onboard (Ubuntu) " New bugfix release of Onboard (debanisation for wily provided) " [Undecided,New] [17:24] mterry, thanks. I'll look into that and get back to you. [17:24] coreycb, looks good besides [17:25] coreycb, (plus needs a team bug subscriber) [17:25] frafu, has anyone in particular sponsored you in the past? [17:25] mterry, got it, thanks! [17:28] coreycb: Yes, if I remember correct TheMuso, who is greyed at the moment. It is a good idea, I will try to look that up. [17:29] frafu, sounds good, he may be more familiar with your package [17:33] coreycb: Is there a way to look up who sponsored the previous sponsorship requests? [20:09] meh, I changed the HEAD of the upstream APT repository today, and now launchpad imported that to bzr. What will happen when I change it back? === salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem === _salem is now known as salem_