=== juliank_ is now known as juliank [02:48] is there a list of packagesets and packages that belong to those packagesets somewhere? [02:49] I also wonder if I can use the Launchpad API to look at that... === StevenK_ is now known as StevenK === Serge is now known as Guest84149 === Lutin_ is now known as Guest93281 === semiosis_ is now known as semiosis === ]reed[ is now known as [reed] === stokachu_ is now known as stokachu === lynxman_ is now known as lynxman === beisner- is now known as beisner === dasjoe_ is now known as dasjoe === dcmorton_ is now known as dcmorton === FlannelKing is now known as Flannel === daltenty_ is now known as daltenty === mariogrip_ is now known as mariogrip === Tribaal_ is now known as Tribaal === ulkesh_ is now known as ulkesh [05:52] Good morning [05:52] Howdy. [05:53] apw: FYI, I reopened bug 1626436, -17 still boots a lot slower than 4.4 and with high loads; although a lot less severe than the previous -14 [05:53] bug 1626436 in linux (Ubuntu) "[4.8 regression] boot has become very slow" [Medium,Triaged] https://launchpad.net/bugs/1626436 [06:07] good morning pitti! [06:10] bonjour didrocks, ça va ? [06:12] pitti: ça va bien, et toi ? :) [06:13] didrocks: je vais bien aussi; salutations de Berlin, je reste chez larsu :) [06:13] pitti: oh, c'est vrai ! Dis-lui bonjour de ma part :) [06:14] didrocks: je vais le faire, merci ! (il encore dort) === geser__ is now known as geser [07:52] happyaro1, cyphermox: I didn't get around to creating a NetworkManager DNS plugin for resolved this cycle, got diverted by too many other things; at this point I'd just revert NM back to using dnsmasq, like we had before; is that ok for you? === davmor2_ is now known as davmor2 === popey_ is now known as popey === infinity1 is now known as infinity === sunweave1 is now known as sunweaver === Riddelll is now known as Riddell [10:51] pitti: morning, could you please take another look at https://lists.ubuntu.com/archives/lubuntu-devel/2016-September/000824.html ? [10:51] (afair you said you would take a look today) [11:06] cjwatson_: hey! I was wondering - there's such a strange situation we have right now in -proposed, ubuntu-keyboard 0.100+16.10.20160921-0ubuntu1 is there but the binary for ubuntu-keyboard-data for this version is not, even though it was not removed or anything [11:06] cjwatson_: tested in an yakkety-proposed amd64 chroot with apt-cache policy and even launchpad acts strangely here [11:07] https://launchpad.net/ubuntu/yakkety/+package/ubuntu-keyboard-data <- this only shows the old version [11:07] https://launchpad.net/ubuntu/yakkety/+package/ubuntu-keyboard <- while here's the main ubuntu-keyboard binary from -proposed [11:07] cjwatson_: do you know what could be the cause of it? [11:07] cjwatson_: does it mean someone removed the binaries from -proposed? [11:10] https://launchpad.net/ubuntu/yakkety/amd64/ubuntu-keyboard-data is more useful [11:11] that says it was superseded by ubuntu-keyboard 0.100+16.10.20160921-0ubuntu1 [11:11] er, wait, what [11:11] this may have been a race of some kind, let me dig through logs a bit [11:11] Strangeness I see, 0.100+16.10.20160921-0ubuntu1 should have ubuntu-keyboard-data but it doesn't, even though on the LP build page I see it being generated === cjwatson_ is now known as cjwatson [11:12] This also basically blocks ubuntu-keyboard and unity8 in -proposed [11:12] Since, yeah, the autopkgtests can't run since it can't install ubuntu-keyboard-data for the -proposed ubuntu-keyboard, since the binaries are not there! ;) [11:13] there are two copy records here which suggests something like a double-override accident [11:14] uh, sounds scary [11:15] Thanks for looking into that! [11:16] @pilot in === udevbot_ changed the topic of #ubuntu-devel to: Xenial (16.04.1) Released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | reverse-depends/seeded-in-ubuntu broken? http://ubuntuqa.tblwd.org/ | Patch Pilots: Mirv [11:17] certainly seems to have been copied rather a lot [11:17] celeryd-production_launchpad_job.log-20160923.gz:[2016-09-22 15:37:07,396: INFO/Worker-1] Running (ID 33200448) in status Waiting [11:17] celeryd-production_launchpad_job.log-20160923.gz:[2016-09-22 22:45:27,787: INFO/Worker-2] Running (ID 33204726) in status Waiting [11:17] celeryd-production_launchpad_job.log-20160924.gz:[2016-09-23 23:46:15,121: INFO/Worker-1] Running (ID 33200448) in status Waiting [11:17] celeryd-production_launchpad_job.log-20160924.gz:[2016-09-23 23:46:16,081: INFO/Worker-3] Running (ID 33204726) in status Waiting [11:18] Oh! [11:18] I think I was doing the copy, and I remember that it hanged on the last package [11:18] Like, the copy-package script [11:18] I think I aborted and re-run again, but that should cause 2 copies at max I guess? [11:19] Since the bileto publish job was busted I had to publish some packages manually through copy-package [11:19] the first two of those copies were suspended, i.e. held in UNAPPROVED [11:19] (I feel so bad since it might have been me that busted things) [11:19] so I think you did a double copy, both ended up in the queue [11:20] then when they were accepted, two copies of the same package were accepted simultaneously (literally - two celery workers were processing those two copies in parallel) [11:20] and our locking isn't always what it could be [11:20] so, easy to fix, I'll just copy it over itself [11:22] done, should hopefully sort itself out in a bit [11:23] cjwatson: thanks! [11:24] Sorry for the commotion, I didn't know if the first run copied everything since it seemed hanged so I preferred to just do a second copy, as I didn't expect it to cause two entries in UNAPPROVED [11:24] Now I know it's not so low-risk as I thought it is === kitterma is now known as ScottK [11:54] oh man ... [11:55] * ogra_ has a failed 14.04 -> 16.04.1 server upgrade and in the middle of sending the error report lp goes down ... [11:55] must be my lucky day [11:58] sigh [11:58] no bug here, move along [12:01] oh man [12:01] ogra@aleph:~$ sudo reboot [12:01] sudo: reboot: command not found [12:01] that ugrade went *really* wrong [12:02] (it tried to do a lot of insserv stuff, re-ordering sysv scripts and so on ... ) === sforshee` is now known as sforshee [12:07] hmm, not even remotely a trace of systemd on that machine ... [12:07] thats rather unexpected ... specifically since i used do-release-upgrade [12:12] Anyone know of a dpkg gotcha when replacing directories with symlinks? https://paste.debian.net/841984/ [12:12] It becomes an empty directory instead of a symlink [12:13] Do I have to do it in postinst? [12:14] Laney, I think there is a helper todo that [12:14] Laney: Yep, that's standard. dpkg-maintscript-helper can help [12:14] (via dh_installdeb, probably) [12:14] dir_to_symlink [12:14] aha [12:14] Not sure I've come across this particular one before === cpaelzer_ is now known as cpaelzer === Pici` is now known as Pici === Snow-Man_ is now known as Snow-Man === freyes__ is now known as freyes === mhall119_ is now known as mhall119 [13:09] sil2100: are you landing the ubuntu-touch-meta part of bug #1625023 ? (asking with my patch pilot hat on) [13:10] bug 1625023 in Canonical System Image "switch to systemd on ubuntu phone xenial" [Critical,Confirmed] https://launchpad.net/bugs/1625023 === ddstreet_away is now known as ddstreet [13:14] pitti: no objections [13:19] @pilot out === udevbot_ changed the topic of #ubuntu-devel to: Xenial (16.04.1) Released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | reverse-depends/seeded-in-ubuntu broken? http://ubuntuqa.tblwd.org/ | Patch Pilots: [13:23] Mirv: yeah, I'm on it [13:24] Mirv: for now no action required there, we'll do the switch in the nearest days === _salem is now known as salem_ === alai` is now known as alai [13:28] sil2100: ok === BrAsS_mOnKeY is now known as g2` [13:41] oh sigh [13:42] * dholbach hugs Mirv [13:42] pitti, so i just had my server eat itself completely doing a 14.04->16.04.1 do-release-upgrade ... i now have a ton of insserv complaints every time i use apt ... systemd wasnt installled at all ... grub ended up with only memtest in it ... [13:42] pitti, can i just purge insserv ? iirc we dont need it === josepht` is now known as josepht [13:42] (i just manually installed grub and systemd so i got at least back to ssh support) [13:43] * ogra_ thinks that was the worst ubuntu expirience he had yet ... just using official tools :( [13:50] ogra_: hm, you can purge insserv in 16.10, but not yet in 16.04; what did it say? some broken sysv script somewhere without LSB headers? [13:50] pitti, about 200 lines every few seconds ... [13:50] yeah, LSB header noise [13:51] now that i got back to a working system (after installing grub by hand from an old 11.04 CD i had around since mini.iso from USB was to new for the BIOS on that old iron) i just noticed that dist-upgrade wants to still upgrade ~600 packages [13:52] so i guess the insserv thing was caused by a half upgraded system ... i'll see that i get to normal first [13:52] still pretty bad that do-release-upgrade can get you into such a state === henrix_ is now known as henrix [14:07] Launchpad, where are thou === Guest84149 is now known as hallyn [14:20] This may sound as a silly question, but what is the normal procedure to generate a _sources.changes file for a debian native package ? dpkg-genchanges -S ? [14:22] caribou, yes, I do that usually [14:22] actually -S -d [14:22] :) [14:22] and -sa when needed [14:23] LocutusOfBorg: good, thanks! [14:23] yw! [14:24] sitter: note that this is coming from snappy newbie who is mostly having fun and learning the tool, but I started with https://github.com/tjyrinki/qt-ubuntu and it's available in edge channel (just not sure if any useful at the moment for anything). my main wish is to have a snap that contains the Qt as known in Ubuntu world (hence, "qt-ubuntu"), with all the patches we've wanted to cherry-pick or [14:24] backport for our products. === lutostag_ is now known as lutostag [14:24] pitti: network failure [14:25] stuck in the cable ? [14:28] Mirv: seems reasonable. for KDE the current plan (really just vision) is to have an own Qt though to tighter control patches etc. [14:30] sitter: right, mine can also be called mostly a vision at the moment. it's really up to how will the eventual needs seem to be - snap does allow a lot of flexibility in all directions, meaning not everyone needs to use the common one, but still eg snapcraft work can be shared [14:31] Mirv: agreed === tarpman_ is now known as tarpman [14:46] * ogra_ glares at his sever removing config files for usplash [14:47] hmm, i knew this install was old ... i wasnt aware *how* old actually === JanC is now known as Guest94585 === JanC_ is now known as JanC === elmo_ is now known as elmo [15:00] flexiondotorg: Is there a reason you mark bugs like bug 1601874 as Incomplete? [15:00] Error: Could not gather data from Launchpad for bug #1601874 (https://launchpad.net/bugs/1601874). The error has been logged [15:01] !dmb-ping [15:01] bdmurray, BenC, cyphermox, infinity, micahg, rbasak, sil2100: DMB ping. === Eleventh_Doctor is now known as Pharaoh_Atem === Pharaoh_Atem is now known as King_InuYasha === King_InuYasha is now known as Pharaoh_Atem [15:12] bdmurray, When LP comes back I'll take a look. === roaksoax_ is now known as roaksoax === daniel3 is now known as Odd_Bloke [16:05] oooh ... LP is back (at least for the bug i just reloaded) [16:06] -ish (slow, but stuff is coming through) [16:18] smoser: [16:18] +Before=NetworkManager.service [16:18] Before=network-pre.target [16:18] smb: that's a no-op and looks like some red herring [16:19] smb: ifupdown, NM, networkd, and similar things all run after network-pre.target (that's its purpose) [16:19] smoser, ^ [16:19] sorry, smoser ^ [16:20] pitti, added for redhat [16:20] as you say, shoudl be a noop [16:20] right? [16:21] smoser: oh, is their NM not doing After=network-pre.target? [16:22] i think that network-pre.target is an ubuntu-ism, no? [16:22] no [16:22] both the target and NM.service are the upstream units [16:22] we don't have ubuntu specific targets [16:23] (well, in the systemd package -- obviously there are some from packages like cloud-init) [16:24] hm.. [16:24] pitti, how'd you see this ? [16:24] smoser: doing yakkety unapproved queue review [16:25] * pitti felt like some punishment in the evening before dinner :) [16:25] also, the DC is coming back, so catching up with stuff [16:25] yea [16:27] smoser: so, as this shuldn't be different in RH I was just curious what it should do, and if there maybe is some "real" bug somewhere [16:28] pitti, want to join #cloud-init and see if harlowja will respond ? [16:28] he is who did this, and uses cent. [16:29] smoser: done; I'll be AFK for dinner RSN, but I'll get backscroll === AdmWiggin is now known as tianon [17:07] coreycb: fyi, ftfbs from doko's last e-mail for cinder, I think it's because you need a build-dep on python-pep8 or python3-pep8 for the tests? [17:07] coreycb: https://launchpadlibrarian.net/285536781/buildlog_ubuntu-yakkety-amd64.cinder_2%3A9.0.0~b2-0ubuntu1_BUILDING.txt.gz [17:24] nacc, I think that is fixed by rc1 which is in proposed [17:25] coreycb: ack, thanks! [17:29] nacc, yw, it is great when things are already fixed :) btw that is stuck in proposed based on a few dependencies we're fixing up. [17:31] coreycb: np, i'm just trying to keep an eye on the ubuntu-server ftbfs list === alan_g is now known as alan_g|EOD [17:53] pitti, i would like your opinion on https://bugs.launchpad.net/ubuntu/+source/gce-utils/+bug/1627789 [17:53] Launchpad bug 1627789 in gce-utils (Ubuntu) " ordering cycle prevents google-startup-scripts from running" [High,Triaged] [18:09] doko: for the ftbfs for libecap, i think the 3 symbols mentioned in https://launchpadlibrarian.net/285536159/buildlog_ubuntu-yakkety-i386.libecap_1.0.1-3ubuntu3_BUILDING.txt.gz (same for all the arch's build logs) are no longer present. `pkgkde-symbolshelper` parsing the build-log as input does seem to want to just elide those 3 -- but I'm inexperienced in this area? [18:10] flexiondotorg: so about bug 1601911 - why is it incomplete? [18:10] bug 1601911 in mate-menu (Ubuntu) "/usr/lib/mate-menu/mate-menu-config.py:11:g_type_check_instance_is_fundamentally_a:g_object_unref:model_free_row_data:model_update_current_folder:update_combo_box" [Undecided,Incomplete] https://launchpad.net/bugs/1601911 [18:12] bdmurray, Reagarding 1601874 you mentioned ealier, it is from an old package from a PPA. [18:14] As for 1601911, I've never encountered it and can't reproduce it. [18:16] flexiondotorg: bug 1601874 also occurered with version 16.04.9.1 which is the Xenial version of the package... [18:16] bug 1601874 in ubuntu-mate-welcome (Ubuntu) "/usr/bin/ubuntu-mate-welcome:11:_gtk_style_provider_private_get_settings:gtk_css_value_initial_compute:gtk_css_static_style_compute_value:_gtk_css_lookup_resolve:gtk_css_static_style_new_compute" [Undecided,Incomplete] https://launchpad.net/bugs/1601874 [18:18] flexiondotorg: I'm trying to understand why you marked a whole bunch of crash reports from the Error Tracker as Incomplete. Its hard to tell just based off the bug. [18:19] bdmurray, The rationale for marking those bugs incomplete is we've spent about 5 days testing Ubuntu MATE Welcome. [18:19] The version in Xenial and the version we've been preparing for Yakkety. [18:20] None of the team were able to excercise Ubuntu MATE Welcome is such a way to cause those errors :-( [18:21] flexiondotorg: and what about engrampa or atril? e.g. this crash with 340 instances https://errors.ubuntu.com/problem/bf4ee7bcedb2e9da402d6486d69fe3cf5fc783f7 [18:26] bdmurray, I just requested access errors.ubuntu.com [18:26] flexiondotorg: Maybe we should mark the bugs as New then, rather than causing them to expire in 60 days? [18:27] bdmurray, Can you help me understand the correct way to interact with bugs I can't reproduce please? [18:27] OK, I can mark them New. [18:28] flexiondotorg: I think the first step would be to look at the crashes, let me give you access to errors. [18:29] flexiondotorg: Can you access this now? https://errors.ubuntu.com/problem/bf4ee7bcedb2e9da402d6486d69fe3cf5fc783f7 [18:30] Yes. Excellent! [18:31] flexiondotorg: So we can see a Stacktrace there which has details. Those don't get put in the bug report since it might contain sensitive information. [18:31] flexiondotorg: If you look at the Occurences table there are links to the individual crash reports e.g. https://errors.ubuntu.com/oops/2da4c81a-8358-11e6-8a94-fa163e30221b [18:32] flexiondotorg: That contains the apport crash report information like ProcCmdline which might be useful in recreating the crash [18:32] bdmurray, Thanks, this is great. [18:33] flexiondotorg: the version table can also be useful in determining which releases are affected, however just because you don't see it affecting Yakkety doesn't mean it won't. There aren't a lot of yakkety users yet. [18:33] I thought I'd registered for errors before but that just let me manipulate the graphs. [18:34] That doesn't require any special permissions. [18:39] flexiondotorg: if you have any questions about the error tracker or feedback please let me know [18:39] bdmurray, Will do. [18:46] doko: looking at libpam-radius-auth ftbfs, but i'm not able to reproduce it. [19:12] doko: nm, PEBKAC for libpam-radius-auth, would still appreciate your input on libecap [19:17] doko: http://paste.ubuntu.com/23234756/ for libpam-radius-auth, does it look sane? [19:27] nacc: I'll NMU that to Debian too, fabbione package ... [19:27] doko: ok [19:28] doko: so you'll handle both libpam-radius-auth and libecap? [19:29] nacc: libecap, yes these destructor symbols are not part of the ABI [19:29] doko: ack [19:31] nacc: are you able to upload libecap yourself? Not sure why we don't see that in Debian [19:32] doko: yeah, i can [19:32] doko: i just wanted to check with you first [19:37] doko: http://paste.ubuntu.com/23234825/ ? also, do you normally file a bug for every ftbfs so it's clear what the failure was? [19:39] nacc: for Ubuntu? no, I gave up on this, because these bugs are then not rracked. maybe we should do that again for main for every package [19:40] doko: i have been filing them for myself so i have a place to link the logs [19:40] just wasn't sure if there as a 'best practice' already [19:46] nacc, ahh, libecap in debian doesn't have symbols file ... [19:46] doko: yeah, i just realized it's a delta [19:46] doko: did the above debdiff seem reasonable? [19:47] i can upload now, if so [19:53] doko: i noticed that with libpam-radius-auth, it's orphaned in debian and we're on a different upstrema there too [19:53] nacc: if you use the LP tag 'ftbfs', the bug will show up on http://qa.ubuntuwire.org/ftbfs/ [19:54] jbicha: yep, i realized that last night, so i've been modifying them :) [20:00] doko: presuming you ack, i can upload both libecap and libpam-radius-auth for yakkety [20:18] doko: ok, llvm-toolchain-3.6 now :) -- seems like gcc 6.1/6.2 isn't provide gcc-6.1/gcc-6.2, but gcc-6? so do we need to adjust that regex to be 5|6? [20:18] http://paste.ubuntu.com/23234972/ [20:51] smoser: LP is oopsing on me again -- I guess I'll have a look tmw morning then [20:51] pitti, fair enough [20:51] thanks [20:52] smoser: hmm, https://launchpad.net/ works, but https://launchpad.net/bugs/1627789 oopses [20:52] Launchpad bug 1627789 in gce-utils (Ubuntu) " ordering cycle prevents google-startup-scripts from running" [High,Triaged] [20:52] smoser: can you open it? [20:53] no. it had worked earlier today [20:53] interestingly, the private one works :) [20:54] smoser: https://bugs.launchpad.net/ubuntu/+source/gce-utils/+bug/1627789/+text also works -- I just cannot comment on that [20:54] Launchpad bug 1627789 in gce-utils (Ubuntu) " ordering cycle prevents google-startup-scripts from running" [High,Triaged] [20:56] smoser: looks ok to me; probably all the cloud-init-ish stuff should perhaps rather be installed into cloud-init.target than multi-user, but surely fine for an SRU [20:58] pitti, right, but i think they want to run even if cloud-init is not present. [20:59] smoser: oh, ok; then that looks right === kees_ is now known as kees [22:14] nacc: isn't 3.6 already fixed in Debian, and can be merged? but yes, this should be fixed the same way as in newer llvm's [22:44] doko: i'll check [22:45] doko: we're already merged to current llvm-toolchain-3.6 in debian [22:45] afaict [23:29] doko: it's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835582 [23:29] Debian bug 835582 in src:llvm-toolchain-3.6 "llvm-toolchain-3.6: FTBFS with gcc-6" [Serious,Open] [23:36] doko: fyi, +1 on the idea of auto-opening ftbfs bugs for packages in main [23:45] is there anything I can do to help LP #1571456 (xenial SRU for glibc) get looked at? (waves at infinity :)) [23:45] Launchpad bug 1571456 in glibc (Ubuntu Xenial) "id crashed with SIGSEGV in sock_eq()" [Medium,Triaged] https://launchpad.net/bugs/1571456 [23:52] barry: doko: Any idea what the status of bug 1443704 is? [23:52] bug 1443704 in python2.7 (Ubuntu) "Support for TLS 1.2 not present (added in 2.7.9)" [Undecided,Confirmed] https://launchpad.net/bugs/1443704 [23:55] nacc: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838945 [23:55] Debian bug 838945 in src:libecap "please incorporate some patches" [Normal,Open] [23:55] so once applied, this is syncable [23:55] doko: ack, i'll watch for it [23:56] doko: i went ahead and submitted the small patch for now, i hope that's ok -- and we can presumably sync once debian is updated [23:56] barry: dropped, because I never had the time to finish it. feel free to pick it up again, but then maybe with the package/version from xenial [23:57] Odd_Bloke: ^^^ [23:58] doko: mako is a debian bug as well (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830178) [23:58] Debian bug 830178 in src:mako "mako: FTBFS: ValueError: too many values to unpack" [Serious,Open] [23:59] doko: I'm asking for someone else at a sprint; what approach were you taking to make it work?