[01:56] <codepython777> has anyone recently bought a laptop here? I'm looking to buy a good ubuntu laptop. Had my eye on dell xps 13 - but that has been discontinued for now.
[04:26] <pitti> Good morning
[07:04] <dholbach> good morning
[07:16] <dholbach> @pilot in
[07:17] <seb128> hey dholbach, enjoy ;-)
[07:17] <dholbach> thanks
[07:29] <Noskcaj> dholbach, 3.8.3 is the newest non-bluez5 version
[07:29] <dholbach> ah ok
[07:29] <Noskcaj> It just brings in a few bug fixes, but it would be nice to have
[07:29] <dholbach> right
[07:29] <Noskcaj> We're discussing bluez5 in -desktop now, it will happen later this cycle if we can get the manpower finally
[09:04] <dholbach> Noskcaj, do you have a link to the source package of 3.8.0-2?
[09:05] <Noskcaj> I thought i got the merge up to 3.8.3-1
[09:05] <Noskcaj> https://download.gnome.org/sources/gnome-user-share/3.8/gnome-user-share-3.8.3.tar.xz
[09:05] <Noskcaj> https://download.gnome.org/sources/gnome-user-share/3.8/gnome-user-share-3.8.0.tar.xz if not
[09:05] <dholbach> the source package
[09:05] <dholbach> like the .dsc file and everything
[09:06] <Noskcaj> oh, no. I just got it from the pkg-gnome tags
[09:06] <dholbach> mh
[09:07] <dholbach> nevermind... http://snapshot.debian.org/package/gnome-user-share/3.8.0-2/
[09:35] <doko> seb128, I saw you didn't forward libproxy to debian. are there other uploads which are not yet forwarded?
[09:37] <seb128> doko, yes, I didn't manage to go through all the diffs on thursday and I was on friday, I'm going to do the remaining ones after lunch
[09:45] <doko> thanks
[09:55] <hron85> Hi, anyone can help me with working with quilt? I made an upgrade for a package and now I have a non-applying patch. However, I cannot refresh it, since it does not apply and quilt do not want to move to this patch until it does not apply
[09:55] <hron85> quilt refresh <patchname> does not work
[09:57] <pitti> Laney: in case you had some config or other files: I just redeployed the entire autopkgtest cloud stuff from scratch
[09:58] <Laney> pitti: nope, maybe stuff in shell history that'll be gone though. :P
[09:58] <pitti> Laney: I did some work this morning to add basenode/ksplice/landscape/two nova configs, and wanted to re-test the whole thing before we switch to production
[09:59] <Laney> what is basenode?
[09:59]  * Laney can't quite google it up
[10:02] <cjwatson> hron85: quilt push -f, resolve conflicts (it should tell you about where they are, and IIRC there'll be the usual patch-conflict <<< [10:03] <cjwatson> hron85: assuming that your starting point is a consistent tree whose quilt state is at the patch immediately below the non-applying one
[10:14] <hron85> cjwatson: yep, it solved my problem, thanks
[10:15] <hron85> cjwatson: yes, I knew the not-applying patch will be the next, but i did not found any way to move to it, since quilt refresh <patchname> rejects to work if the mentioned patch is not applied yet.
[10:34] <jhenke> does anybody know if someone is working on the proposed gnupg 2.1.x as default? I did not see anything since the original message and I wondering if I missed some message
[10:38] <ricotz> StevenK, hi, a gcc5 rebuild of aptitude please :)
[10:39] <ricotz> ah sorry, slangasek ^
[10:41] <cjwatson> hron85: right, in general I think it's best to avoid quilt refresh's mode where it takes a patch name - it's conceptually very confusing
[10:50] <Laney> seb128: doko: do you want help with rebuilds/uploads? if so, where?
[10:51] <doko> ricotz, current ftbfs
[10:51] <doko> Laney, see slangasek's message on -release
[10:52] <Laney> hmm, I don't have one
[10:52] <Laney> nor on the archive
[10:52] <Laney> link?
[10:58] <doko> Laney, #ubuntu-release
[11:00] <Laney> still unclear
[11:00] <Laney> I see the individual transitions - should I take one and work on it?
[11:00] <Laney> + checking your build logs for ABI changes
[11:09] <ricotz> doko, oh, I see
[13:01] <alkisg> mitya57: hi, I'm trying to look into the gnome-flashback keyboard layout applet issue, is the problem there that the existing applet doesn't respond to layout changes reported by xorg?
[13:39] <dholbach> @pilot out
[13:50] <doko> seb128, Laney: just updated to wily. the handles for the terminals don't exist. is this expected?
[13:50] <doko> also when trying to update to wily-proposed:
[13:50] <doko> The following packages will be REMOVED:
[13:50] <doko>   aptitude compiz compiz-gnome compizconfig-settings-manager libasprintf0c2 libcompizconfig0 libdouble-conversion1 libllvm3.6 libmirclient8 libprotobuf9 libproxy1 libtag1-vanilla libxapian22
[13:50] <doko>   mumble python-compizconfig python-xapian signon-ui signon-ui-x11 software-center tasksel tasksel-data ubuntu-desktop unity unity-control-center-signon unity-tweak-tool
[13:50] <doko>   webaccounts-extension-common xul-ext-webaccounts
[13:53] <seb128> doko, the scrollbar issue is known I think, Laney has the details
[13:54] <seb128> doko, compiz/unity rebuild/fixes for gcc5 are in silo43 it seems, check with bregma when he plans to land it I guess
[13:55] <seb128> dunno about aptitude mumble etc
[13:55] <doko> bregma, ^^^ ???
[13:56] <bregma> doko, there's an issue with one of the branches landing that still needs to be retested, then I'm landing that silo as soon as I can
[13:57] <doko> ta
[13:57] <bregma> it's been a game of whack-a-mole getting everything to build
[14:00] <doko> bregma, are there any other silos needed?
[14:01] <bregma> doko, that silo installs OK as long as -proposed is enabled, so not for the Unity stack as far as I know
[14:09] <pitti> Laney: FYI: https://code.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud (moved from ~pitti)
[14:12] <doko> jamespage, zul, roaksoax, smoser: there doesn't seem to be any progress on the ruby dep-waits ...
[14:13] <pitti> apw: not sure if you actually still need this, but http://autopkgtest.ubuntu.com/data/packages/wily/amd64/l/linux/latest.json (and all other JSONs) have URLs to the swift artifacts nwo
[14:14] <apw> that looks useful, even if i don't use it, though i suspect i will
[14:15] <cjwatson> doko: which ruby dep-waits are those, the ones on gem2deb?
[14:16] <cjwatson> doko: because if so (and they quite probably involve gem2deb somewhere), don't hassle the server team about it, needs the next launchpad-buildd rollout because gem2deb started making use of build profiles
[14:16] <doko> cjwatson, ruby-hashie, ruby-rspec, ruby-safe-yaml, ruby-test-unit
[14:16] <doko> ahh, ok
[14:17] <cjwatson> doko: there might be some MIRs buried in there too
[14:17] <doko> dpkg-gencontrol: warning: can't parse dependency libxapian22 (>= 1.2.21)v5
[14:17] <doko> hrm,
[14:17] <cjwatson> ah, no, just misleadingly wrong dep-waits I think
[14:18] <cjwatson> doko: certainly at least ruby-hashie and ruby-rspec will be ultimately fixed by new buildd, haven't checked them all
[14:18] <cjwatson> hopefully I'll get a review of https://code.launchpad.net/~cjwatson/launchpad-buildd/snapcraft/+merge/266541 soon and then I can start the release process
[14:18] <doko> ok, good to know ... still we should address the dep-waits too
[14:19] <cjwatson> doko: what kind of addressing are you talking about?
[14:20] <doko> writing MIR's, dropping b-d's etc
[14:20] <cjwatson> doko: well, some of the dep-waits you see are bogus
[14:20] <cjwatson> so it's probably not worth chasing any of that down until the buildds are fixed
[14:21] <doko> sure, but I doubt that the perl team uses these too
[14:21] <cjwatson> doko: ruby-test-unit -> ruby-power-assert looks like a real MIR case
[14:21] <cjwatson> doko: perl example?
[14:22] <doko> see http://qa.ubuntuwire.com/ftbfs/
[14:25] <cjwatson> ok, sure, there's probably a bunch of MIR handling to be done there
[14:59] <Laney> doko: handles? we changed the scrollbars and there's a problem with the terminal's widget but the thumb is gone if that's what you mean
[15:00] <Laney> you can still scroll it but it's annoying to make it go big
[15:00] <Laney> pitti: ah, cool
[15:01] <Laney> pitti: do you plan to document the architecture? :)
[15:01] <pitti> Laney: yes, of course
[15:04] <doko> Laney, indeed very ugly
[15:05] <Laney> pitti: great - I'm currently still a bit sketchy and would be scared if I had to (e.g.) redeploy it :P
[15:05] <Laney> doko: we will try to tweak more before release
[15:06] <pitti> Laney: heh, sure; indeed there is one remaining bug for complete re-deployment
[15:08] <pitti> (bug 1480962)
[15:08] <pitti> Laney: once that's fixed, it will become really simple; I'll write documentation of all of that once it's all in place
[15:08] <Laney> yay
[15:43] <pitti> tseliot: hmm, seems something broke the fglrx driver? http://autopkgtest.ubuntu.com/packages/u/ubuntu-drivers-common/wily/amd64/
[15:46] <tseliot> pitti: having an actual build log would help. I'll try it here, thanks
[15:46] <pitti> tseliot: yeah, we should fix those tests to cat the build log on failure
[15:46] <tseliot> pitti: that would be nice
[15:50] <smoser> bdmurray, i gues you're not awake...
[15:50] <smoser> https://code.launchpad.net/~smoser/ubuntu-reports/trunk.fix-server-merges/+merge/266745
[15:51] <bdmurray> smoser: I am actually and in a meeting. I'll have a look shortly.
[15:52]  * pitti waves good night
[15:52] <smoser> bdmurray, ok. thanks. and then kick the report generation if you could.
[15:53] <tseliot> pitti: the module built but I see two architectures in my chroot: dkms status
[15:53] <tseliot> fglrx-core, 15.200.1, 4.1.0-3-generic, amd64: installed
[15:53] <tseliot> fglrx-core, 15.200.1, 4.1.0-3-generic, x86_64: installed
[15:59] <pitti> tseliot: did you enable -proposed?
[15:59] <tseliot> pitti: not really
[16:00] <tseliot> pitti: this is all I have http://paste.ubuntu.com/11993942/
[16:00] <pitti> tseliot: i. e. it's plausible that it fails due to gcc 5; /me tries in a chroot with -proposed
[16:01] <tseliot> pitti: gcc -v reports "gcc version 4.9.2 (Ubuntu 4.9.2-17ubuntu1)"
[16:01] <pitti> tseliot: right, and in -proposed we switched to 5.
[16:02] <tseliot> pitti: right, but I don't have -proposed enabled
[16:02] <tseliot> so it must be something else
[16:03] <tseliot> or maybe the failure is a separate issue and/or a false positive
[16:05] <pitti> (wily-amd64)root@donald:/home/martin# modprobe fglrx
[16:05] <pitti> modprobe: ERROR: could not insert 'fglrx': Unknown symbol in module, or unknown parameter (see dmesg)
[16:05] <pitti> [  404.772855] fglrx: Unknown symbol amd_iommu_bind_pasid (err 0)
[16:05] <pitti> [  404.772925] fglrx: Unknown symbol amd_iommu_set_invalid_ppr_cb (err 0)
[16:05] <pitti> [  404.773082] fglrx: Unknown symbol amd_iommu_set_invalidate_ctx_cb (err 0)
[16:05] <pitti> [  404.773170] fglrx: Unknown symbol amd_iommu_unbind_pasid (err 0)
[16:05] <pitti> [  404.773265] fglrx: Unknown symbol amd_iommu_init_device (err 0)
[16:05] <pitti> [  404.773372] fglrx: Unknown symbol amd_iommu_free_device (err 0)
[16:05] <pitti> tseliot: ^ I get that with -proposed
[16:06] <tseliot> pitti: ok, so it's not a build error. It looks like fun. I'll fix it, thanks
[16:06] <pitti> tseliot: hm, I get the same without -proposed
[16:07] <pitti> it started failing on Aug 1
[16:08] <tseliot> maybe the ABI broke somehow?
[16:08] <pitti> tseliot: hm, maybe this is normal in a chroot; that's not what the test fails on
[16:08] <pitti> so this needs a closer look
[16:08] <mitya57> slangasek, ScottK is right — only the plugin(s?) are built against default python3, everything else is built against all supported versions
[16:08] <mitya57> (sorry for the delay btw)
[16:08] <tseliot> pitti: yes, I'll test it on a real system
[16:08] <pitti> tseliot: cheers
[16:12] <mitya57> alkisg, hi, if by "existing applet" you mean indicator-keyboard, then it doesn't support xkb switching. It listens to gsettings changes on org.gnome.input-sources (that are done by g-s-d or u-s-d).
[16:13] <mitya57> And that should work fine in Ubuntu (unlike Debian or upstream).
[16:13] <alkisg> mitya57: it works here in 14.04, but not in 15.10
[16:14] <alkisg> I can use indicator-keyboard with the mouse to change the language, but I can't use any keyboard shortcut to change it
[16:14] <alkisg> Even though gsettings are the same as in 14.04 when it worked
[16:16] <alkisg> mitya57: so the plan is for someone to write such an applet, and then use it in all variants, upstream, debian and ubuntu?
[16:16] <alkisg> Or ubuntu will keep using indicator-keyboard?
[16:18] <mitya57> alkisg, it's in our "patches welcome" list upstream :)
[16:18] <mitya57> let me look at the code a bit
[16:19] <alkisg> If you accept one that listens for *xkb* changes as well, instead of only for gsettings changes, it would be interesting... :)
[16:25] <mitya57> alkisg, why do you still need xkb changes? GNOME upstream deprecated that and gsettings is much easier to use.
[16:25] <mitya57> alkisg, also, do you have gnome-settings-daemon or unity-settings-daemon running?
[16:25] <alkisg> mitya57: unity-settings
[16:26] <mitya57> that should work fine…
[16:26] <alkisg> It doesn't... clean 15.10 installation
[16:26] <alkisg> That was basically what I was worried about, I thought that it would be broken in ubuntu 15.10+, 16.04 etc like it is upstream...
[16:26] <mitya57> Are you using modifiers-only keybinding or not?
[16:27] <alkisg> The defaults, win+space
[16:27] <alkisg> I also tried alt+shift which worked in 14.04, it doesn't work either
[16:27] <mitya57> Does it list in gsettings get org.gnome.desktop.wm.keybindings switch-input-source?
space
[16:28] <mitya57> Looks fine.
[16:28] <mitya57> Is there a bug open in LP for it, and if no, can you please file one?
[16:29] <alkisg> I'll check + file a bug, thanks,
[16:29] <alkisg> about xkb changes, unfortunately gnome upstream breaks sdl apps, and we're trying to make things work as they were with xorg without gnome breaking them...
[16:30] <mitya57> Can you also attach "gsettings list-recursively org.gnome.desktop.input-sources" to the bug, please?
[16:30] <alkisg> E.g. in tuxpaint, tuxtype, we cannot type greek at all now with recent gnome versions, the last one to work fine for us was 12.04
[16:30] <alkisg> mitya57: another issue that might need resolving,
[16:31] <alkisg> I install ubuntu with greek layout in ubiquity etc. Then I create a user, and /home/user is empty
[16:31] <andol> There is something off with the http://releases.ubuntu.com/vivid/ FOOSUMS files, and their corresponding FOOSUMS.gpg - http://paste.ubuntu.com/11994117/. In addition to gpg reporting BAD signatures there is also the oddness that the FOOSUMS files appear to have newer mtimes than their corresponding FOOFUMS.gpg.
[16:31] <alkisg> If that user logs in, he has nothing in the layouts list, while it should be "us,gr"
[16:31] <andol> (No idea where the proper place to report such an issue is)
[16:31] <alkisg> So all users need to go to keyboard settings and add the layouts manually
[16:32] <alkisg> I think this happens in all ubuntu gnome variants, while it doesn't happen in e.g. fedora... or of course in ubuntu <= 12.04
[16:32] <mitya57> alkisg, please report that against the installer (i.e. if you use the graphic one, then it's ubiquity)
[16:33] <alkisg> mitya57: I think the problem is that gnome doesn't respect the global xorg settings anymore
[16:33] <alkisg> It's not about ubiquity... e.g. when one run `adduser x` after the installation, that "x" user doesn't get the xorg system default layout
[16:33] <alkisg> *runs
[16:33] <mitya57> alkisg, are you installing Ubuntu GNOME?
[16:33] <alkisg> No, plain ubuntu and then gnome-flashback
[16:34] <alkisg> It's been that way since 14.04. It was working in 12.04
[16:34] <alkisg> I've been filling a lot of bug reports about these issues, but they didn't draw much attention...
[16:35] <mitya57> This is first time I hear about this issue.
[16:35] <mitya57> :)
[16:35] <alkisg> :)
[16:35] <mitya57> It looks like it's not specific to GNOME Flashback, so try sending a mail to ubuntu-desktop@lists.ubuntu.com
[16:35] <mitya57> There are people who should know what component to blame
[16:36] <alkisg> The long story is that ubiquity, lightdm, accountsservice, gnome-settings-daemon, unity-settings-daemon, and a couple of other applications don't work with multiple keyboard layouts since 13.04 or so
[16:37] <alkisg> Let me try the indicator with unity...
[16:38] <alkisg> mitya57: I think that the "indicator doesn't change on layout changes by keyboard shortcuts" is specific to flashback, in unity it's working fine
[16:38] <alkisg> And it broke after 14.04
[16:39] <alkisg> The 10+ rest issues about layouts are not specific to flashback, but they are specific to ubuntu though... :-/
[16:40]  * alkisg checks + files a bug for that one...
[16:40] <mitya57> alkisg, does the gsettings key (i.e. org.gnome.desktop.input-sources current) change when you toggle the keybinding?
[16:41] <alkisg> unity => yes, moment for flashback...
[16:41] <alkisg> metacity => no, moment for compiz...
[16:42] <infinity> pitti: Did I ever get those trusty langpacks?
[16:44] <alkisg> mitya57: gnome-flashback (compiz) gives me unity without the top panel... go figure :)
[16:44] <mitya57> alkisg, metacity is enough, that indicates that the problem is not in the indicator, but in unity-settings-daemon
[16:44] <mitya57> the fix for compiz will be in next compiz upload :)
[16:45] <alkisg> mitya57: hope you don't mind me asking, are you using the flashback+metacity session yourself in production?
[16:46] <alkisg> We're using gnome-flashback in 1000+ schools here, but I was wondering if mate would be more appropriate, considering the old hardware...
[16:46] <alkisg> gnome-flashback feels like the best choice, considering it's closer to upstream gnome, but it also feels understaffed... :)
[16:50] <mitya57> Yes, we are quite lacking resources
[16:50] <mitya57> Actually I do just packaging (don't have time for anything else), all upstream work is done by 1.5 people :)
[16:52] <alkisg> Yes fortunately Alberts is doing the bulk of the work... but mitya57, are you using it in production somewhere? Or is it just your preferred DE?
[16:53] <mitya57> Many my friends use it :)
[16:53] <alkisg> Nice :)
[16:53] <mitya57> Also I set it up in a school some time ago, not sure if they are still using it
[16:53]  * mitya57 keeps accidentally pressing Ctrl+Q
[16:54]  * alkisg wonders where "ibus" fits in all this... it's preinstalled, and previously it was not running by default, and now it is...
[16:55]  * mitya57 doesn't know anything about ibus
[17:00] <alkisg> mitya57: should I file the bug against indicator-keyboard (Ubuntu), or against unity-settings-daemon?
[17:00] <alkisg> I.e. that it works in unity but not in flashback
[17:05] <mitya57> alkisg, unity-settings-daemon, and also add https://launchpad.net/ubuntu-gnome-flashback as a subtask
[17:05] <alkisg> Thanks, trying...
[17:08] <doko> why is xapian-bindings ftbfs on the buildds ...
[17:14] <doko> bregma, so even with your landing PPA enabled, I can't upgrade
[17:20] <alkisg> mitya57: I've filed LP #1481025
[17:27] <Mirv> cyphermox: thanks for the new wpa! fwiw it does not seem there is stated delta anymore to Debian's debian/config/wpasupplicant/linux, other than the fact that Ubuntu has the settings specified twice + there is unmentioned Android config delta
[17:35] <cyphermox> Mirv: are you saying I forgot to re-add the android crap in changelog?
[17:36] <cyphermox> looks to me like it's there
[17:36] <mitya57> alkisg: thanks
[17:38] <alkisg> Tthank _you_ :)
[17:46] <doko> Noskcaj, qqwing accepted in -proposed
[17:47] <hjd> cyphermox: Thanks for packaging. :) I suppose it's too late to mention it in the changelog, but would you mind leaving a comment on bug 1370245?
[18:01] <Mirv> cyphermox: the section stating remaining changes in debian/config/wpasupplicant/linux from Debian mentions the two options that are double stated in that file but does not mention the CONFIG_ANDROID_HAL=y which is the only actual delta in that config
[18:02] <cyphermox>   - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL.
[18:03] <Mirv> cyphermox: I mean, oh, right, it's up there. then the later mention is just unneeded + the config file should be cleaned since the delta is actually now this http://paste.ubuntu.com/11994721/
[18:03] <cyphermox> nah
[18:03] <cyphermox> *bah
[18:04] <Mirv> so CONFIG_P2P and CONFIG_AP are repeated in Ubuntu's version
[18:06] <cyphermox> Mirv: how about that. Feel free to clean it up if you want to
[19:05] <hjd> jjohansen: Hi :)
[19:06] <jjohansen> hjd: hello
[19:06] <hjd> jjohansen: Sorry for the random ping, but I saw bug 1481039 and wondered whether the linux-lts-backport-maverick and -natty tasks are included for completeness, since they don't seem to be part of any current Ubuntu release.
[19:07] <jjohansen> hjd: its actually because I need to do some updates to the tooling we use so we can drop those
[19:11] <hjd> ok :)
[19:44] <doko_> desktop updated to wily-proposed + landing-043. seems to work again \o/
[19:46] <infinity> doko_: Impressive.
[19:47] <Laney> oh, they fixed the arm64 FTBFS of $package
[19:47] <Laney> SHIP IT.
[19:48] <doko_> apt-get dist-upgrade removes gnome-control-center, but you can install it again. only thing missing is aptitude
[19:51] <Noskcaj> Logan, Would you mind checking the sponsors queue for stuff before you merge? I had a finished merge for light-locker waiting, so there was a bit of an overlap of work. That said, i should have asked you if i could merge it
[19:52] <Laney> doko_: If you can get an easily understandable list of work to be done then I can help out tomorrow
[19:52] <Laney> like 'rename these packages' or 'rebuild/fix for these transitions'
[19:54] <doko_> I'm trying, need to prepare for travel tomorrow as well
[19:54] <doko_> I mean, you could starting to rebuild stuff for icu and boost in main
[19:55] <Laney> I also don't want to clash/duplicate
[19:55] <Laney> so some pad/wiki would be nice
[19:55] <doko_> Laney, coordinate with slangasek; I think I won't do much tomorrow
[20:28] <ari-tczew> cjwatson: shouldn't the fakesyncs be synced automatically?
[20:33] <ari-tczew> cjwatson: nvm, due to mismatch tarballs isn't possible, but I think fakesyncs should be on MoM visible...
[20:33] <ari-tczew> correct me if I'm wrong
[21:45] <doko_> cyphermox, you still involved with libcolumbus?  could you have a look at the ftbfs?
[21:55] <doko> Noskcaj, pyicu 1.8 ftbfs with ICU 55. updated to 1.9.2
[22:09] <Noskcaj> doko, I'll update it in debian python svn today
[22:10] <doko> ta
[22:25] <infinity> robert_ancell: Hey, do you know of anyone (perhaps you?) who could verify the SRU for https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1410801 ?
[22:29] <robert_ancell> infinity, I don't have any AMD hardware, sorry
[23:39] <mwhudson> go 1.5 prep feels like http://media.giphy.com/media/MRUj8R8SMWlIk/giphy.gif today
[23:57] <infinity> mwhudson: You keep getting attacked by a vicious cat?
[23:57] <mwhudson> not entirely what i was trying to convey, no