[05:36] <cpaelzer> good morning
[05:44] <pitti> Good morning
[08:59] <rayzinnz> 'ello
[09:24] <hikiko> rbasak ping :)
[09:25] <hikiko> new questions on the sru
[09:26] <hikiko> that's what I did so far: https://ufuntu.wordpress.com/2016/04/21/sru-process/ password:trusty used the tools you suggested, quilt and dch and I think (hope) I'm ready to create the new package
[09:27] <hikiko>  and go to step 5 here: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[09:27] <hikiko> the question is
[09:27] <hikiko> which tools I need to create a package?
[09:28] <hikiko> and how should I name it?
[09:28] <rbasak> hikiko: that looks good so far.
[09:28] <seb128> hikiko, did you check with Trevinho? compiz is managed by CI landing
[09:28] <seb128> not normal uploads
[09:29] <rbasak> seb128: including for an SRU?
[09:29] <seb128> rbasak, I was looking at the most recent one, https://launchpad.net/ubuntu/+source/compiz/1:0.9.11.3+14.04.20150313-0ubuntu1
[09:29] <seb128> the CI bot is the uploader
[09:29] <seb128> so I guess so
[09:30] <rbasak> Well that makes life quite a bit harder for hikiko :-(
[09:30] <hikiko> no worries :) I want to learn the full process
[09:30] <hikiko> seb128, I didn't I'm now learning the SRU process
[09:31] <rbasak> I don't know the CI process.
[09:31] <rbasak> seb128: can you help hikiko?
[09:31] <hikiko> also, could you tell me the non-CI process?
[09:31] <seb128> hikiko, can you talk to Trevinho?
[09:31] <seb128> or maybe do that with him next week?
[09:31] <rbasak> Or would it be sufficient for hikiko to put a debdiff in the bug and let a sponsor sort it out?
[09:31] <hikiko> btw seb128 I've seen in the changelog that chris townsend had sru some changes
[09:31] <seb128> rbasak, hikiko, well for things going through CI landing you just need a merge request with the change
[09:32] <rbasak> "just"
[09:32] <hikiko> it's not only the CI bot I think
[09:32] <pitti> we do SRUs via the CI train too?
[09:32] <seb128> pitti, of course
[09:32] <seb128> why not?
[09:32] <hikiko> Trevinho, is in Prague :D
[09:33] <seb128> well, wait monday
[09:33] <seb128> ?
[09:33] <hikiko> alright :)
[09:33] <pitti> I just don't think I've ever seen one
[09:33] <seb128> you are coming next week right?
[09:33] <hikiko> yes
[09:33] <pitti> presumably because most touchy stuff lands in the overlay PPA
[09:33] <seb128> pitti, I just gave an url
[09:33] <seb128> pitti, all unity landings are done this way
[09:33] <seb128> unity7
[09:35] <hikiko> ok but just out of curiosity
[09:35] <Laney> The only difference for the SRU team person is that it's a copy (with binaries) in the queue instead of a source upload
[09:35] <hikiko> if I had to SRU it myself
[09:35] <hikiko> what would be the next step?
[09:36] <hikiko> how would I create a package and how would I name it?
[09:36] <rbasak> hikiko: if not following the CI process, you'd adjust the version number, run "dch -r -D trusty ''" to set the metadata in the debian/changelog file.
[09:36] <rbasak> Then run "dpkg-buildpackage -us -uc -S -nc -d" to create a new .dsc and .diff.gz file for the new version.
[09:37] <rbasak> An uploader would then be able to use the generated .changes file to upload.
[09:37] <rbasak> If you need sponsorship, you run "debdiff <old>.dsc <new>.dsc" to create a debdiff, attach that to the bug, and subscribe ~ubuntu-sponsors to the bug.
[09:37] <rbasak> I've ignored testing here. You can use sbuild to build a test package locally.
[09:38] <rbasak> Or upload to a PPA for testing.
[09:38] <rbasak> So you'd done most of the hard part already for the usual process I think.
[09:39] <hikiko> and then everything else is done on launchpad I guess
[09:39] <hikiko> upload the package etc
[09:41] <hikiko> rbasak, thanks a lot!
[09:41] <hikiko> I'm going to note these steps just in case and wait for monday to ask Trevinho
[09:44] <rbasak> 12:29 <rbasak> "Yakkety Yak"
[09:45] <rbasak> Thursday, April 21st, 2016 "Yakkety yakkety yakkety yakkety yakkety yakkety yakkety yakkety yak. Naturally"
[09:45]  * rbasak isn't sure if that was a coincidence, the obvious choice, or what.
[09:59] <Odd_Bloke> ALL HAIL RBASAK
[09:59] <Odd_Bloke> cjwatson: wgrant: FYI, there are 16.04 powerpc images in http://cloud-images.ubuntu.com/daily/streams/v1/com.ubuntu.cloud:daily:download.json now.
[10:00] <wgrant> Odd_Bloke: <3
[10:00] <Odd_Bloke> cjwatson: wgrant: I don't believe that infinity has had time to test them since we were building from a PPA, but they shouldn't have changed. since he last told me they were booting.
[10:00] <wgrant> Booting is good.
[10:00] <Odd_Bloke> wgrant: Do you pull from daily streams, or release streams?
[10:01] <Odd_Bloke> (Because they aren't currently showing up in release streams, and I'm trying to work out highly to prioritise fixing that :p)
[10:01] <wgrant> Odd_Bloke: Do I look like a stable OS sort of person to you?
[10:01] <wgrant> We've been tracking wily dailies for a while.
[10:01] <wgrant> No reason not to use xenial dailies now :)
[10:01] <Odd_Bloke> OK, cool.
[10:01] <Odd_Bloke> I'll throw fixing that on our backlog then.
[10:02] <wgrant> Thanks!
[10:09] <caribou> Laney: would installing all the reverse deps of a backported package considered adequate testing for a backport request ?
[10:11] <caribou> Laney: I'm testing a script that installs each of the rdepends in a container where the binaries to be backported are installed & checking if it installs correctly
[10:11] <caribou> curious to know if this would be considered sufficient
[10:14] <pitti> rbasak: btw, would you mind having a look at my response in bug 1569434 ? If this is real, it'd drive me nuts :)
[10:25] <Laney> caribou: Just /installing/ doesn't sound enough to make sure that they aren't busted
[10:30] <caribou> Laney: apache2 has more than 100 rdepends, you would test all of them manually ?
[10:30] <rbasak> pitti: I can try to reproduce again.
[10:33] <Laney> caribou: In this case, does installing enable them?
[10:33] <Laney> and restart apache to get them used?
[10:33] <caribou> Laney: I'll check the logs once all of them run but most of them do, yes
[10:35] <caribou> Laney: I think tests must be specific to each backport context though
[10:37] <caribou> Laney: but in that specific case, that's how I ran over a know issue & fixed it : LP: #1286882
[10:38]  * caribou is just trying to get a better understanding of the backport requirements
[11:33] <Laney> pitti: do you need to teach autopkgtest about yakkety?
[11:36] <mgedmin> welp, update-manager (15.10 -> 16.04) froze after unpacking gir1.2-atspi-2.0 and "processing triggers for man-db"
[11:36] <mgedmin> says it's preparing to configure python-cairo, but it's idle
[11:36] <mgedmin> pstree shows it has one zombie child (dpkg)
[11:37] <mgedmin> strace shows it's bloked trying to write "pmstatus:libde265-0:16.8172:Inst..." to a pipe on fd 14
[11:40] <mgedmin> ah, it's an internal pipe used to communicate between threads?  lsof shows that it's the upgrader itself that has the other end open for reading
[11:41] <mgedmin> the GUI window is not responding to events either
[11:42] <mgedmin> ... I might've hit Ctrl+Shift+I to open the GTK+ inspector
[11:42] <mgedmin> while trying to see if it uses GTK2 or GTK3
[12:07] <pitti> Laney: yes, in the sense that I need to update distro-info-data
[12:07] <pitti> Laney: also, retracers etc.
[12:08] <Son_Goku> ah, the joys of using a fresh linux distro release :/
[13:15] <seb128> dpm, pitti,  I've the feeling we have been there before but any idea why evolution-3.18.mo are missing from langpacks? it makes evolution untranslated in xenial :-/ ( (bug #1566750)
[13:17] <seb128> mdeslaur, do you/security team want to be notified about regressions due to the samba trusty security update? and in which way (bug assign? subscribe?) bug #1571854 is another of those
[13:19] <mdeslaur> seb128: you can tell me about them
[13:20] <mdeslaur> seb128: that particular one is problematic though as I don't believe there's an openchange package that actually works with samba 4.3
[13:22] <seb128> indeed not
[13:22] <seb128> we should at least delete -mapi
[13:22] <mdeslaur> seb128: thanks for pointing them out, I'll see if there's any other way to fix it when I get a minute
[13:22] <seb128> or turn it into a "sorry, being removed"
[13:22] <seb128> thanks
[13:27] <TJ-> any ideas why 16.04 "apt-get install --no-install-recommends" breaks Unity desktop, in that there is no 'System' menu-icon, and Dash is unable to find any applications via navigation or via a typed search. Also, All Settings > Universal Access > typing > on-screen keyboard doesn't actually provide the on-screen keyboard, and there's no nm-applet shown
[13:43] <seb128> TJ-, that command shouldn't do anything? or do you mean starting from a base system and installing the desktop without recommends ... that might lead to some component missing yes, don't do that
[13:49] <TJ-> seb128: Yes. I did a debootstrap install for a 4GiB Flash drive, used that to get the basic desktop, and discovered many issues with missing basic functionality
[13:50] <seb128> don't do that
[13:50] <seb128> download the iso and dd it to the stick
[13:51] <TJ-> seb128: can't; I need an installation on the USB
[13:52] <TJ-> my point is "--no-install-recommends" shouldn't leave out vital parts of the interface
[13:53] <dobey> they aren't "vital"
[13:54] <TJ-> dobey: I disagree. there being no system icon, no nm-applet, no access to applications via dash are pretty serious deficiencies
[13:56] <TJ-> I discovered this whilst trying to workaround the broken bluetooth GUI PIN-entry agent which prevents pairing with external keyboard/trackpad... have to do it via CLI with bluetoothctl
[13:57] <seb128> TJ-, you put them as depends and users with no bluetooth complain that they can't remove the bluetooth components
[13:57] <seb128> can't win
[13:57] <TJ-> seb128: I'm not on about BT with regard to recommends - that is a separate issue
[13:58] <rbasak> I think it's reasonable to QA only the default (including recommends case).
[13:58] <TJ-> seb128: even with all the BT GUI components installed on a *full* install from ISO, gui bluetooth PIN agent is broken, never works,
[13:58] <rbasak> If there are specific recommends that should be depends, then...patches welcome?
[13:58] <seb128> +1
[13:59] <TJ-> First time I've used Unity in about 6 years, surprised its not more mature
[13:59] <seb128> ?
[13:59] <rbasak> Otherwise you're basically requiring the doubling of QA effort for what?
[14:00] <seb128> TJ-, you call it not mature because you did some weirdy install, ignored recommends and then are complaining it's incomplete? or is that an orthogonal statement?
[14:00] <rbasak> You're welcome to hack your system but when you break it you get to keep the pieces.
[14:00]  * dobey confused
[14:00] <rbasak> If you want mature, don't do weird things.
[14:00] <TJ-> this isn't hacking this is a regression
[14:01] <dobey> what is a regression?
[14:01] <TJ-> Bluetooth *used* to work fine; was broken several releases ago  bug 1490347
[14:01] <dobey> the bt agent has nothing to do with unity
[14:01] <seb128> TJ-, that has nothing to do with unity
[14:01] <dobey> and i can pair with devices that use PINs just fine
[14:01] <seb128> TJ-, you seem confused?
[14:01] <TJ-> dobey: bet you can't!
[14:02] <TJ-> dobey: bet you *can* pair with devices that use *passphrase* ... because bluez ripped out the *pin* support
[14:02] <dobey> TJ-: except for the many times i've done it in the many years i've been using ubuntu
[14:02] <dobey> you must be confused
[14:02] <seb128> TJ-, I doubt bluez removed pin support
[14:03] <dobey> if bluez removed pin support you wouldn't be able to use bluetoothctl either
[14:04] <TJ-> I was deep in the source-code last year trying to fix it and the related kernel bugs breaking other devices, but had to give up because it was too involved and I had other things to do. the kernel bug is bug 1491988
[14:05] <dobey> well i just paired a headset in xenial with no problem
[14:06] <seb128> TJ-, k, so there is a kernel bug, it's different from being bluez ripping out support
[14:06] <dobey> had no problem pairing my obd-ii scanner in 14.04, so i expect no problem in 16.04 either
[14:11] <TJ-> dobey: yes, headsets and so on seem to work but anything that has to enter the PIN in response to the PC fails. E.g. in the GUI for BT, when you discover a device, there's an option to select the PIN method (0000, 1111, 1234, custom) ... none of those will work with the keyboard even if typing them blind (because there's no GUI prompt for the number as there used to be). Using the bluetoothctl it
[14:11] <TJ-> generates a 6-digit PIN. The thing is, although we call it PIN this is actually using the underlying BT 'passphrase' authentication.
[14:12] <TJ-> I'll dig my notes out on the debugging I did last year on this, I think I also logged some additional bug reports but will have to track them down
[14:12] <seb128> TJ-, anyway on the unity issue, I guess it would be fine to move the files/applications lens from Recommends to Depends, feel free to propose a patch for that or to open a bug
[14:13] <TJ-> seb128: is that why I had no applications listed? so I can manually install that to get over the current impass?
[14:13] <seb128> TJ-, I guess so
[14:13] <seb128> unity-lens-applications
[14:14] <dobey> and indicator-session
[14:15] <dobey> should probably be Depends of ubuntu-desktop
[14:15] <seb128> and onboard and
[14:15] <TJ-> seb128: I shall do.. currrently fighting to get everything working on a 2-in-1 Asus T300chi (touchscreen tablet/laptop hybrid with docking BT keyboard. Not being able to have the BT come up at greeter-time is currently a major issue so using a USB connected keyboard, or ssh in (now I've created a wifi profile in nmtui-edit) :)
[14:15] <seb128> network-manager-gnome
[14:15] <dobey> i don't think onboard should be depends
[14:15] <TJ-> seb128: dobey thanks, I'll install those (already did n-m-g and ubuntu-keyboard - for the on-screen keyboard backup)
[14:16] <dobey> i'm not sure ubuntu-keyboard is the one you want for that
[14:16] <TJ-> Full install has all those
[14:16] <TJ-> dobey: hmmm, really? it looked the most likely candidate!
[14:16] <seb128> TJ-, ubuntu-keyboard is the one used on ubuntu touch, onboard is the desktop one
[14:16] <dobey> TJ-: i think onboard is the one used for ubuntu-desktop
[14:17] <dobey> well, you could just install unity8-desktop-session-mir instead, and use unity8 instead of unity7, then ubuntu-keyboard would make sense perhaps :)
[14:17] <TJ-> dobey: ahhh! OK, I think you're correct since enabling on-screen keyboard still didn't show anything!
[14:18] <TJ-> dobey: oh, is that what it's for?
[14:18] <dobey> i wonder if indicator-network is a usable replacement for nm-gnome now
[14:18] <dobey> TJ-: yeah, ubuntu-keyboard is the phone/tablet (unity8) osk
[14:18] <dobey> also, ubuntu-keyboard is in universe
[14:19] <dobey> no way it would be installed on the ubuntu-desktop iso :)
[14:19] <TJ-> ouch! without --no-install-recommends onboard wants to install tonnes of packages, including a mass of Perl!
[14:19] <dobey> lol
[14:24] <TJ-> right.. I needed 2 of the onboard recommends: gir1.2* ... now the greeter shows the keyboard, athough as a shrunken image in a sub-area of the bottom of the screen
[14:26] <seb128> TJ-, you might want onboard-data
[14:27] <TJ-> yes, got that earlier, thanks
[14:27] <TJ-> this is what the greeter shows: https://iam.tj/projects/misc/ubuntu-1604-greeter-onboard-keyboard.jpg
[14:28] <TJ-> once the user is logged-in the keyboard fills the entire area
[14:31] <seb128> unsure why it does that
[14:32] <TJ-> and this is after log-in, showing the empty dash 'applications' tab, and the lack of system icon top-right, plus onscreen keyboard
[14:32] <TJ-> https://iam.tj/projects/misc/ubuntu-1604-user-onboard-keyboard.jpg
[14:33] <de-facto> Hey guys im fighting to compile http://packages.ubuntu.com/de/xenial/easystroke via "apt-get source easystroke" then "apt build-dep easystroke" then inside the source dir "dpkg-buildpackage" it gives me this error that i also found in https://bugzilla.redhat.com/show_bug.cgi?id=1302917
[14:34] <TJ-> ahh, and noticed that there's no icon to control the onscreen keyboard
[14:34] <de-facto> Does someone have an idea how the ubuntu repo managed to compile this?
[14:34] <cjwatson> It probably built at some point in the past, just not with the current state
[14:35] <cjwatson> It failed in our latest build test
[14:35] <cjwatson> But that doesn't mean we throw away the existing binaries
[14:35] <cjwatson> https://launchpad.net/ubuntu/+source/easystroke indicates that it was built last August
[14:36] <cjwatson> (https://launchpad.net/ubuntu/+source/easystroke/0.6.0-0ubuntu5/+build/7771352)
[14:37] <seb128> TJ-, you probably lack indicator-application as well
[14:37] <seb128> for the onboard indicator
[14:37] <de-facto> cjwatson yeah that is what i suspected, some incompatible changes in the toolchain, im trying to build it because it has some gfx glitches and also a bug which prevents it from storing its settings correctly. First i want to be able to build the original ubuntu package then upgrade the sources from https://github.com/thjaeger/easystroke to fix those issues (he did not raise the version number unfortunately)
[14:37] <TJ-> seb128: thank-you seb128 I'll chase that one down. I was about to do a diff between the (full) SDD install and the USB image to figure it out.
[14:37] <seb128> yw
[14:40] <TJ-> hehehe and with a 'restart lightdm' greeter doesn't show the onboard keyboard, only the lower blacked-out area :)
[14:40] <TJ-> just got to find the system-menu indicator icon now
[14:41] <de-facto> any ideas what i could play around with to fix the error ctions.cc: In constructor 'TreeViewMulti::TreeViewMulti()':   ctions.cc:57:39: error: group' is not a member of 'sigc'   get_selection()->set_select_function(sigc::group(&negate, sigc::ref(pending)));
[14:41] <de-facto> i guess its something from libsigc++
[14:45] <LocutusOfBorg> de-facto, libsigc++ version??
[14:46] <LocutusOfBorg> you might want to test the new upstream release (in debian)
[14:47] <de-facto> LocutusOfBorg libsigc++-2.0-dev Version 2.6.2-1 on Xenial release currently
[14:48] <LocutusOfBorg> maybe 2.8.0 works=
[14:48] <LocutusOfBorg> did it worked before=
[14:49] <de-facto> i used to compile it on previous versions of ubuntu (dont remember the exact versions though)
[14:50] <LocutusOfBorg> seems that the group has been removed between 2.4 and 2.6
[14:50] <LocutusOfBorg> https://anonscm.debian.org/cgit/collab-maint/libsigc++-2.0.git/commit/?id=fa41e72a2a68239a84839e59f763e0f49c0ca098
[14:50] <LocutusOfBorg> - * @deprecated Use C++11 lambda expressions or %std::bind() instead of libsigc++ lambdas and sigc::group().
[14:50] <LocutusOfBorg> I think you did get a lot of warnings with the previous release
[14:52] <de-facto> could very well be the case, i dont remember exactly anymore, but i got a working binary on previous versions of ubuntu
[15:11] <dobey> TJ-: indicator-session is the "system menu" indicator
[15:18] <TJ-> dobey: thanks... I've been walking the rdepends/depends paths to try to figure out why it was missed
[18:35] <Unit193> slangasek: Got time for a quick PM?
[18:54] <slangasek> Unit193: prime ministers are never quick
[18:55] <Unit193> Nope, certainly not.  Thankfully, I'm referring to a private message.
[21:04] <mapreri> pitti: I'm looking at http://autopkgtest.ubuntu.com/packages/p/pbuilder/ and i just noticed the 'i' sign points to tracker.d.o.  I guess this is fine and cool for the debian instance of debci, but probably shouldn't ubuntu link the launchpad page instead? (actually, I'd love to have both links to tracker.d.o and lp)
[23:08] <bdmurray> lamont: Could you have a look at bug 1552801?