[19:22] <simcha> Hi I was testing sth with mainline kernel 4.5-r6 and realised that it is missing aufs driver needed by docker in default configuration. Where shall I file the bug if any?
[20:33] <jtaylor> simcha: mainline kernels don't have aufs
[20:34] <jtaylor> its a ubuntu specific addition
[20:35] <jtaylor> so if you want to file a bug it needs to be against upstream linux


[00:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktp-auth-handler build #4: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/artful_unstable_ktp-auth-handler/4/
[00:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_cantor build #4: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/artful_unstable_cantor/4/
[00:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #4: STILL UNSTABLE in 53 min: https://kci.pangea.pub/job/artful_unstable_kopete/4/
[00:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ark build #5: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_unstable_ark/5/
[00:18] <ahoneybun> mm where did they put the dashboard thinge
[00:18] <ahoneybun> to show all the open windows
[00:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:19] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-sdk build #6: FIXED in 17 min: https://kci.pangea.pub/job/artful_stable_plasma-sdk/6/
[00:20] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #5: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_stable_ark/5/
[00:20] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kalzium build #4: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_stable_kalzium/4/
[00:20] -kubuntu-ci:#kubuntu-devel- Project artful_stable_cantor build #4: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/artful_stable_cantor/4/
[00:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kspaceduel build #98: FAILURE in 4 min 47 sec: https://kci.pangea.pub/job/zesty_unstable_kspaceduel/98/
[00:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ksnakeduel build #154: FAILURE in 5 min 58 sec: https://kci.pangea.pub/job/xenial_unstable_ksnakeduel/154/
[00:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ksnakeduel build #110: FAILURE in 6 min 20 sec: https://kci.pangea.pub/job/zesty_unstable_ksnakeduel/110/
[00:26] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-integration build #7: FAILURE in 6 min 52 sec: https://kci.pangea.pub/job/artful_stable_plasma-integration/7/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kspaceduel build #209: FAILURE in 11 min: https://kci.pangea.pub/job/xenial_unstable_kspaceduel/209/
 (Photo, 1280x720) https://irc-attachments.kde.org/Ye5vWJDR/file_2443.jpg
 \o/
[00:36] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kstars build #4: STILL UNSTABLE in 35 min: https://kci.pangea.pub/job/artful_stable_kstars/4/
[00:36] -kubuntu-ci:#kubuntu-devel- Project artful_stable_umbrello build #4: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/artful_stable_umbrello/4/
[00:43] <acheronUK> ahoneybun: are you sure your kmail upgraded ok? that lib should not be looking for that symbol, as the akonadi new kmail linked against does not have it
[00:49] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kopete build #26: STILL UNSTABLE in 39 min: https://kci.pangea.pub/job/zesty_stable_kopete/26/
[00:50] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ark build #19: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/zesty_stable_ark/19/
[00:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kile build #17: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/zesty_unstable_kile/17/
[00:54] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-integration build #4: FAILURE in 4 min 39 sec: https://kci.pangea.pub/job/xenial_stable_plasma-integration/4/
[00:55] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_plasma-integration build #7: FAILURE in 5 min 59 sec: https://kci.pangea.pub/job/zesty_stable_plasma-integration/7/
[01:01] <valorie> ahoneybun: is that lubuntu, or kubuntu?
[01:01] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kstars build #12: STILL UNSTABLE in 35 min: https://kci.pangea.pub/job/xenial_stable_kstars/12/
[01:01] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_ark build #21: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/xenial_stable_ark/21/
[01:01] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kio-extras build #28: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_stable_kio-extras/28/
[01:02] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_umbrello build #23: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_stable_umbrello/23/
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_cantor build #21: STILL UNSTABLE in 35 min: https://kci.pangea.pub/job/zesty_stable_cantor/21/
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ktp-auth-handler build #27: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_stable_ktp-auth-handler/27/
[01:03] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_plasma-desktop build #24: UNSTABLE in 36 min: https://kci.pangea.pub/job/zesty_stable_plasma-desktop/24/
[01:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kile build #15: STILL UNSTABLE in 38 min: https://kci.pangea.pub/job/xenial_unstable_kile/15/
[01:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_elisa build #15: STILL UNSTABLE in 41 min: https://kci.pangea.pub/job/xenial_unstable_elisa/15/
[01:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgeography build #358: FIXED in 25 min: https://kci.pangea.pub/job/xenial_unstable_kgeography/358/
[01:05] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #4: STILL UNSTABLE in 1 hr 16 min: https://kci.pangea.pub/job/artful_unstable_krita/4/
[01:05] <acheronUK> ahoneybun: I can replicate the error by doing 'apt-get upgrade' rather than 'apt-get dist-upgrade'
[01:06] <acheronUK> dist-upgrade or equiv is required
[01:06] <ahoneybun> acheronUK: right of course
[01:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #300: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/300/
[01:18] <ahoneybun> valorie: what?
[01:19] <valorie> the image you posted, ahoneybun
 ah that was Kubuntu of course
[01:19] <valorie> huh
[01:19] <ahoneybun> what?
[01:20] <valorie> isn't that the lubuntu logo?
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #106: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/xenial_unstable_kproperty/106/
[01:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_elisa build #15: STILL UNSTABLE in 37 min: https://kci.pangea.pub/job/zesty_unstable_elisa/15/
[01:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #110: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/zesty_unstable_kalzium/110/
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #106: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_unstable_kdb/106/
 nope
 that's konqui
[01:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kspaceduel build #5: STILL FAILING in 6 min 7 sec: https://kci.pangea.pub/job/artful_unstable_kspaceduel/5/
[01:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ksnakeduel build #5: STILL FAILING in 6 min 15 sec: https://kci.pangea.pub/job/artful_unstable_ksnakeduel/5/
[01:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #402: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/xenial_unstable_plasma-pa/402/
[01:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #158: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_unstable_ark/158/
[01:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #136: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/136/
[01:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kspaceduel build #99: STILL FAILING in 6 min 2 sec: https://kci.pangea.pub/job/zesty_unstable_kspaceduel/99/
[01:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ksnakeduel build #111: STILL FAILING in 6 min 40 sec: https://kci.pangea.pub/job/zesty_unstable_ksnakeduel/111/
[01:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ksnakeduel build #155: STILL FAILING in 7 min 7 sec: https://kci.pangea.pub/job/xenial_unstable_ksnakeduel/155/
[01:42] <valorie> ha! now I remember that from the Berlin tshirt
[01:42] <valorie> that konqui driving the trabant
[01:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #137: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/zesty_unstable_cantor/137/
[01:44] <ahoneybun> xD
[01:44] <ahoneybun> also that fixed it acheronUK
[01:44] <ahoneybun> dist-upgrade
[01:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #156: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/zesty_unstable_umbrello/156/
[01:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #230: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/230/
[01:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #474: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/xenial_unstable_ark/474/
[01:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kreport build #4: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/artful_unstable_kreport/4/
[01:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kspaceduel build #210: STILL FAILING in 10 min: https://kci.pangea.pub/job/xenial_unstable_kspaceduel/210/
[01:47] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-integration build #5: STILL FAILING in 12 min: https://kci.pangea.pub/job/xenial_stable_plasma-integration/5/
[01:51] <acheronUK> ahoneybun: :)
[01:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-import-wizard build #120: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/zesty_unstable_akonadi-import-wizard/120/
[01:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #129: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/xenial_unstable_kdiagram/129/
[01:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #335: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/335/
[01:55] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_sddm build #5: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/artful_unstable_sddm/5/
[01:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sddm build #5: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_sddm/5/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sddm build #5: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_unstable_sddm/5/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_plasma-integration build #8: STILL FAILING in 21 min: https://kci.pangea.pub/job/zesty_stable_plasma-integration/8/
[01:57] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-integration build #8: STILL FAILING in 22 min: https://kci.pangea.pub/job/artful_stable_plasma-integration/8/
[02:04] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktp-common-internals build #5: STILL UNSTABLE in 35 min: https://kci.pangea.pub/job/artful_stable_ktp-common-internals/5/
[02:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:05] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdeplasma-addons build #5: FIXED in 37 min: https://kci.pangea.pub/job/artful_stable_kdeplasma-addons/5/
[02:17] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktp-auth-handler build #4: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/artful_stable_ktp-auth-handler/4/
[02:17] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-desktop build #5: UNSTABLE in 49 min: https://kci.pangea.pub/job/artful_stable_plasma-desktop/5/
[02:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kile build #4: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/artful_unstable_kile/4/
[02:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kexi build #5: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/artful_unstable_kexi/5/
[02:19] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscreenlocker build #6: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/artful_unstable_kscreenlocker/6/
[02:26] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-desktop build #32: UNSTABLE in 51 min: https://kci.pangea.pub/job/xenial_stable_plasma-desktop/32/
[02:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-import-wizard build #129: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/xenial_unstable_akonadi-import-wizard/129/
[02:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #123: STILL UNSTABLE in 1 hr 25 min: https://kci.pangea.pub/job/xenial_unstable_krita/123/
[02:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscreenlocker build #344: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/xenial_unstable_kscreenlocker/344/
[02:32] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #169: FIXED in 47 min: https://kci.pangea.pub/job/zesty_unstable_kwin/169/
[02:35] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_krita build #26: STILL UNSTABLE in 1 hr 46 min: https://kci.pangea.pub/job/xenial_stable_krita/26/
[02:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akonadi-import-wizard build #6: STILL UNSTABLE in 17 min: https://kci.pangea.pub/job/artful_unstable_akonadi-import-wizard/6/
[02:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #149: STILL UNSTABLE in 1 hr 21 min: https://kci.pangea.pub/job/zesty_unstable_krita/149/
[02:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kscreenlocker build #138: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/zesty_unstable_kscreenlocker/138/
[02:55]  * ahoneybun wonders why iframe irc works on kubuntu.org but not his website
[02:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #108: STILL UNSTABLE in 1 hr 29 min: https://kci.pangea.pub/job/zesty_unstable_calligra/108/
[03:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #241: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_unstable_kdepim-addons/241/
[03:04] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdepim-addons build #6: STILL UNSTABLE in 45 min: https://kci.pangea.pub/job/artful_unstable_kdepim-addons/6/
[03:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #131: STILL UNSTABLE in 1 hr 6 min: https://kci.pangea.pub/job/xenial_unstable_calligra/131/
[03:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:24] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kwin build #6: FIXED in 29 min: https://kci.pangea.pub/job/artful_stable_kwin/6/
[03:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #133: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/zesty_unstable_kdiagram/133/
[03:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_messagelib build #7: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/artful_unstable_messagelib/7/
[04:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #180: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/zesty_unstable_kdepim-addons/180/
[04:25] -kubuntu-ci:#kubuntu-devel- Project artful_stable_breeze build #7: FAILURE in 1 hr 0 min: https://kci.pangea.pub/job/artful_stable_breeze/7/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #448: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/xenial_unstable_ki18n/448/
[04:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_calligra build #4: STILL UNSTABLE in 1 hr 48 min: https://kci.pangea.pub/job/artful_unstable_calligra/4/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #421: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/xenial_unstable_kcoreaddons/421/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #465: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/xenial_unstable_kconfig/465/
[04:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #152: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_kitemviews/152/
[04:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #131: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_kcoreaddons/131/
[04:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #160: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_kdbusaddons/160/
[04:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ki18n build #108: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_ki18n/108/
[04:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfig build #95: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_kconfig/95/
[04:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #162: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/162/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_messagelib build #37: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/xenial_stable_messagelib/37/
[05:31] -kubuntu-ci:#kubuntu-devel- Project artful_stable_breeze build #8: STILL FAILING in 1 hr 0 min: https://kci.pangea.pub/job/artful_stable_breeze/8/
[05:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcompletion build #8: STILL UNSTABLE in 10 min: https://kci.pangea.pub/job/artful_unstable_kcompletion/8/
[05:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcodecs build #8: STILL UNSTABLE in 10 min: https://kci.pangea.pub/job/artful_unstable_kcodecs/8/
[05:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ki18n build #8: STILL UNSTABLE in 10 min: https://kci.pangea.pub/job/artful_unstable_ki18n/8/
[05:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_phonon build #4: STILL UNSTABLE in 11 min: https://kci.pangea.pub/job/artful_unstable_phonon/4/
[05:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #211: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/zesty_unstable_messagelib/211/
[05:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcoreaddons build #7: STILL UNSTABLE in 15 min: https://kci.pangea.pub/job/artful_unstable_kcoreaddons/7/
[05:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kconfig build #7: STILL UNSTABLE in 15 min: https://kci.pangea.pub/job/artful_unstable_kconfig/7/
[06:52] <lordievader> Good morning
[07:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:11] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_plasma-integration build #9: FIXED in 13 min: https://kci.pangea.pub/job/zesty_stable_plasma-integration/9/
[07:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kscreenlocker build #139: STILL UNSTABLE in 17 min: https://kci.pangea.pub/job/zesty_unstable_kscreenlocker/139/
[07:22] <acheronUK> santa_: seems we need to bump breeze build deps on plasma-integration and plasma-desktop to 5.9.5 anyway
[07:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscreenlocker build #345: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/xenial_unstable_kscreenlocker/345/
[07:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #403: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/xenial_unstable_plasma-pa/403/
[07:25] <santa_> acheronUK: ok, I will have a look later this morning I'm  a bit busy right now
[07:29] <acheronUK> santa_: me too. just going out the door. thank you
[07:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscreenlocker build #7: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/artful_unstable_kscreenlocker/7/
[07:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:42] -kubuntu-ci:#kubuntu-devel- Project artful_stable_breeze build #9: FIXED in 21 min: https://kci.pangea.pub/job/artful_stable_breeze/9/
[07:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #211: STILL UNSTABLE in 47 min: https://kci.pangea.pub/job/xenial_unstable_messagelib/211/
[07:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:52] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-integration build #9: FIXED in 9 min 54 sec: https://kci.pangea.pub/job/artful_stable_plasma-integration/9/
[07:59] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_breeze build #18: FAILURE in 1 hr 1 min: https://kci.pangea.pub/job/xenial_stable_breeze/18/
[08:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:17] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_plasma-desktop build #25: FIXED in 1 hr 18 min: https://kci.pangea.pub/job/zesty_stable_plasma-desktop/25/
[08:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:41] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_breeze build #19: FIXED in 36 min: https://kci.pangea.pub/job/xenial_stable_breeze/19/
[08:49] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kwin build #7: UNSTABLE in 1 hr 7 min: https://kci.pangea.pub/job/artful_stable_kwin/7/
[08:55] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:55] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-integration build #6: FIXED in 14 min: https://kci.pangea.pub/job/xenial_stable_plasma-integration/6/
[09:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:27] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-desktop build #33: FIXED in 46 min: https://kci.pangea.pub/job/xenial_stable_plasma-desktop/33/
[09:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:58] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-desktop build #6: FIXED in 1 hr 8 min: https://kci.pangea.pub/job/artful_stable_plasma-desktop/6/
[12:08] <BluesKaj> Hi folks
[12:26] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1480: SUCCESS in 1 min 3 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1480/
[12:26] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1480: SUCCESS in 1 min 17 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1480/
[12:29] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1480: SUCCESS in 3 min 41 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1480/
[12:30] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1480: SUCCESS in 4 min 39 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1480/
[12:32] <acheronUK> santa_: so by default, KA will now look for the metadata clone at ~/ka-metadata ?
[12:34] <santa_> acheronUK: indeed, you can configure the location to be somewhere else if you want
[12:40] <acheronUK> santa_: ok. is 'complete -F _command do-all' still needed in ~/.bashrc ?
[12:41] <santa_> acheronUK: oh, yep. thanks for pointing that out, I forgot completely about bash completions
[12:42] <acheronUK> santa_: might also be worth mentioning on option 1, that the metadata repo still needs cloning https://git.launchpad.net/ka/tree/INSTALL
[12:43] <acheronUK> that's obvious to me/you, but maybe not to a newbie packager getting set up
[13:41] -kubuntu-ci:#kubuntu-devel- Starting build #19 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #13 4 mo 10 days ago)
[14:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:04] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #19: FIXED in 23 min: https://kci.pangea.pub/job/iso_xenial_unstable_amd64/19/
[14:05] <yofel> finally..
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1481: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1481/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1481: SUCCESS in 1 min 14 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1481/
[14:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1481: SUCCESS in 3 min 33 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1481/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1481: SUCCESS in 4 min 6 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1481/
[15:41] <mparillo> This is going to be fun. kdesudo kate /etc/hosts will no longer work. https://blog.martin-graesslin.com/blog/2017/02/editing-files-as-root/ I wonder how many old forum posts need to be updated.
[16:06] <acheronUK> santa_: again, I may be absent for a fair bit of the evening. real life is a pain!
[16:07] <acheronUK> mparillo: lol. did you see the mailing lists on that? OpenSuse were not impressed
[16:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kscreenlocker build #140: FIXED in 16 min: https://kci.pangea.pub/job/zesty_unstable_kscreenlocker/140/
[16:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:08] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscreenlocker build #8: FIXED in 16 min: https://kci.pangea.pub/job/artful_unstable_kscreenlocker/8/
[16:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscreenlocker build #346: FIXED in 17 min: https://kci.pangea.pub/job/xenial_unstable_kscreenlocker/346/
[16:12] <santa_> acheronUK: no prob, I have some experiments to do in the meantime. good luck with whatever you have
[16:18] <mparillo> acheronUK: I did not. I did recall two comics. You broke my workflow: https://xkcd.com/1172/ What do I need root for? https://xkcd.com/1200/
[20:53] <ahoneybun> clivejo: https://www.reddit.com/r/Kubuntu/comments/62k1hm/question_while_feeling_mildly_infuriated_where_to/
[20:56] <ahoneybun> yofel: so how do I get that xenial KCI iso?
[21:00] <clivejo> ahoneybun: https://kci.pangea.pub/images/
[21:00] <clivejo> https://kci.pangea.pub/images/iso_xenial_unstable_amd64/current/
[21:01] <clivejo> BTW our main DNS is kci.pangea.pub
[21:02] <clivejo> and is linked from here - http://qa.kubuntu.co.uk/
[21:03] <clivejo> I would like that Todo list moved to Phab
[21:04] <clivejo> https://phabricator.kde.org/w/kubuntu/kci/
[21:06] <ahoneybun> thanks
[21:06] <ahoneybun> has anyone tried that image yet clivejo?
[21:06] <clivejo> ahoneybun: Im not sure
[21:06] <clivejo> Rik might have
[21:06] <ahoneybun> so what is that?
[21:06] <ahoneybun> newest stuff on xenial base?
[21:07] <clivejo> yes
[21:07] <ahoneybun> soooo Neon?
[21:07] <clivejo> roughly
[21:07] <ahoneybun> how different is it?
[21:08] <clivejo> +/- certain packages
[21:08] <ahoneybun> so it has some apps and not just bare
[21:08] <clivejo> it has all Frameworks/Plasma/Apps
[21:08] <clivejo> but some things like digikam arent on ours
[21:09] <ahoneybun> ah
[21:09] <clivejo> and we have some stuff that neon doesnt
[21:10] <clivejo> we also don't have translations
[21:10]  * clivejo should open a phab task for that
[21:13] <ahoneybun> oh?
[21:13] <ahoneybun> no translations?
[21:13] <clivejo> translations arent stored in KDE git repos
[21:14] <clivejo> but Harald figured out a way to combine them
[21:14] <ahoneybun> but how does Neon have it?
[21:14] <ahoneybun> oh right
[21:14] <clivejo> https://apachelog.wordpress.com/2017/03/16/kde-neon-with-testing-translations/
[21:15] <clivejo> we need to figure out how he does it and add it to our tooling
[21:16] <genii> Did anyone ask yet?
[21:16] <clivejo> ask?
[21:16] <genii> The author
[21:17] <acheronUK> genii: you mean sitter?
[21:17] <clivejo> I don't understand
[21:18] <clivejo> its released under GPL2 I believe
[21:18] <clivejo> but there has been no demand for that yet
[21:19]  * genii makes another pot of coffee
[21:19] <clivejo> but it would be nice to have for sure
[21:21] <acheronUK> at the moment I was intending to see how much 'fallout' we get when trying to stage apps 17.04, then go from there
[21:22] <acheronUK> Neon is a bit different, as they are trying to provide a user targeted iso and repo as well as a dev tool
[21:22] <acheronUK> or translation testing for KDE devs
[21:23] <acheronUK> ahoneybun: replied on reddit
[21:30] <clivejo> how do I see your reply?
[21:31] <acheronUK> https://www.reddit.com/r/Kubuntu/comments/62k1hm/question_while_feeling_mildly_infuriated_where_to/dgsk1pk/
[21:39] <ahoneybun> thanks acheronUK
[21:40] <santa_> I'm going out for a while
[21:41] <acheronUK> santa_: ok. have fun (if that is your intent)
[21:42] <santa_> clivejo, acheronUK: if you are around tomorroe I would like to discuss a thing related to plasma 5.9.5 and how to test in a reliable way which build dependencies should be bumped
[21:42] <santa_> * tomorrow
[21:45] <acheronUK> santa_: yes, we maybe need something a bit more reliable in that respect than just staging and seeing what happens in the arbitrary order LP starts builds
[21:45] <santa_> ↑ THIS
[21:47] <acheronUK> yup. what happened with the builds last night showed up some issues, but really need to identify them in advance. plus I'm not 100% confident there are not more that did not get shown up just because things randomly built in an ok order
[21:48] <santa_> indeed
[21:49] <santa_> I am not surprised you are a science man XD
[21:52] <acheronUK> santa_: not quite sure what that means, but I'll assume that is good!
[21:52] <acheronUK> having a science background maybe helps in problem solving and analysis
[21:52] <santa_> it means you think in a rational way. that's very good in this case
[21:53] <acheronUK> :)
[21:53] <acheronUK> I try!
[22:56] <wxl> isn't wayland going to be default x server this cycle?
[22:56] <wxl> i thought i saw something about that
 for Ubuntu desktop
 not sure about it
 wait
 I think it will be an test session like Unity8 was
[23:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #857: SUCCESS in 6 min 56 sec: https://kci.pangea.pub/job/mgmt_merger/857/
[23:10] <ahoneybun> wxl: this benefits us a lot tbh
[23:10] <ahoneybun> Canoncial would work with NVIDIA and AMD to get drivers for Wayland and help us a ton
[23:22] <valorie> I think we can't switch until Plasma does
[23:22] <valorie> which is getting closer..... some devels run it full-time
[23:23] <valorie> Wayland-by-default has been announced by softpedia/omg/etc.
[23:23] <valorie> but I've not seen anything official
[23:23] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kspaceduel build #6: STILL FAILING in 5 min 38 sec: https://kci.pangea.pub/job/artful_unstable_kspaceduel/6/
[23:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ksnakeduel build #112: STILL FAILING in 5 min 39 sec: https://kci.pangea.pub/job/zesty_unstable_ksnakeduel/112/
[23:27] <ahoneybun> valorie: Neon has it already so really there is nothing stopping us
[23:27] <ahoneybun> I don't think so anyway
[23:28] <valorie> wouldn't work for me, with nvidia
[23:28] <valorie> neon has it as a choice
[23:28] <valorie> and not by default afaik
[23:29] <ahoneybun> you can move to intel if needed
[23:29] <valorie> I do have intel
[23:29] <valorie> also
[23:29] <valorie> yes
[23:30] <ahoneybun> which I think I need to do to get Anbox working
[23:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sddm build #6: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_unstable_sddm/6/
[23:32] <valorie> you gonna make another app?
[23:33] <ahoneybun> what?
[23:33] <valorie> weren't you doing that before?
[23:33] <valorie> for the ubuntu phone
[23:33] <ahoneybun> Anbox runs Android apps on Linux
[23:33] <ahoneybun> plus Ubuntu Phone is dead
[23:33] <valorie> right.....
[23:33] <valorie> yes, I know
[23:34] <ahoneybun> https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwing7expMPTAhXE6iYKHTpkCQYQFggnMAA&url=http%3A%2F%2Fanbox.io%2F&usg=AFQjCNHxzRMt1VrQIw9tEYCyN2si8wtxDA&sig2=0yoKuLsn9ooYeCFRBunkaw
[23:34] <valorie> well, deadish
[23:34] <ahoneybun> mm
[23:34] <ahoneybun> https://anbox.io/
[23:34] <ahoneybun> valorie: if your talking about UBports, it's going to dead by losing supports and workers
[23:34] <valorie> but why would you want android apps on your desktop unless you are going to develop?
[23:35] <ahoneybun> whatsapp and others
[23:35] <ahoneybun> plus I've never made an Android app before anyway
[23:35] <valorie> ok, my mistake
[23:35] <ahoneybun> I don't have high hopes for UBports tbh
[23:35] <valorie> halium should help, perhaps
[23:35] <valorie> spread the work
[23:36] <ahoneybun> I hope it helps AsteroidOS the most
[23:36] <ahoneybun> valorie: also I'm not worried about the underground work
[23:37] <ahoneybun> more community issues
[23:40] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ark build #20: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/zesty_stable_ark/20/
[23:41] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kopete build #5: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/artful_stable_kopete/5/
[23:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #5: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/artful_unstable_kopete/5/
[23:49] <wxl> i have a lot of questions about it
[23:49] <wxl> (wayland)
[23:50] <wxl> will x still be aruond?
[23:50] <wxl> or do we need to change all the seeds?
[23:50] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kopete build #27: STILL UNSTABLE in 42 min: https://kci.pangea.pub/job/zesty_stable_kopete/27/
[23:50] <wxl> when are we going to start seeing it in images and/or how do we begin testing?
[23:50] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kstars build #13: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/xenial_stable_kstars/13/
[23:51] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #6: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_stable_ark/6/
[23:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeconnect-kde build #5: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/artful_unstable_kdeconnect-kde/5/
[23:58] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #6: FAILURE in 8 min 12 sec: https://kci.pangea.pub/job/artful_unstable_babe/6/
[23:59] <valorie> x is going to be fallback for a *long* time


[03:16] <bluesabre> knome, in favor of photos, but not naked ones :D
[07:31] <flocculant> ochosi: ok - all done and installed - adding comment to bug 1652933
[07:35] <flocculant> not sure what to expect to get logged though yet
[08:53] <JackFrost> flocculant: Did the new indicator plugin fix things?
[10:08] <ochosi> flocculant: you need to build and install the branch as explained, then e.g. killall xfce4-notifyd (it'll be restarted with the next notification automatically) and then go to the notification settings and enable the log there
[10:08] <ochosi> from then on, notifications should get logged and displayed in the log tab
[11:50] <bluesabre> woohoo! https://launchpad.net/ubuntu/+source/sgt-launcher
[11:53] <bluesabre> I'll try to get that added to tomorrow's iso
[11:58] <flocculant> JackFrost: as far as I can tell that's workiing
[11:59] <flocculant> ochosi: ok - I've rebooted since so I assume that'll do - I'll see what happens from now on (Ihad enabled it)
[11:59] <flocculant> bluesabre: \o/
[12:00] <flocculant> ochosi: re the bug ^^ looks to me like both app tab and log tab have the same size 'list area'
[12:01] <flocculant> JackFrost: I did have some oddities around the time it updated - there was a bug, but it appears to have gone *shrug*
[12:02] <JackFrost> It was supposed to have been fixed, yeah.
[12:07] <bluesabre> morning flocculant and JackFrost
[12:07] <flocculant> hi there :)
[12:07] <JackFrost> Howdy bluesabre, and yeah saw that land.
[12:08] <flocculant> bluesabre: is the plan to add sgt and lose the other 2 or 3?
[12:10] <flocculant> ochosi: can confirm the log logs things :)
[12:13] <flocculant> confirm I also stopped it logging Clementine - that'll fill up quickly ;)
[12:20] <bluesabre> flocculant, first was going to add sgt, but we can consider whether to keep the others
[12:20] <bluesabre> We aren't currently near an iso target, so doesn't matter if we have a little extra cruft
[13:34] <ochosi> flocculant: the sizing is only fixed in master, not in the logging branch yet
[14:02] <flocculant> bluesabre: yup - realise the size thing - was just a question :)
[14:02] <flocculant> ochosi: okey doke


[02:03] <jcastro> fta: wow, you're right, chromium is actually working
[14:00]  * gnomefreak forgot i had made 1.0 to grab 0.9 tarballs :)
[14:01] <gnomefreak> asac: what were we using to get tarballs for sunbird? nothing worked last night
[14:06] <gnomefreak> gtwitter doesnt have a menu
[15:50] <gnomefreak> gwibber needs to learn how to connect to twitter
[16:51] <asac> gandi: sunbird 0.9?
[16:52] <asac> i think we download them from mozilla
[16:52] <asac> gandi: gwibber _can_ do twitter
[16:52] <gandi> asac: ?
[16:52] <asac> gandi: sorry ... wrong nick ;)
[16:53] <asac> tab-trap
[18:15] <fta> hi
[19:17]  * asac out for easter night


[01:37] <jose> mhall119: maybe chipotle this time? :D
[01:38]  * belkinsa hasn't been to Taco Bell in ages and been there maybe three times in her lifetime
[07:21] <dholbach> good morning
[14:45] <mhall119> jose: chipotle is over-rated, maybe I'll take you to Moe's
[14:59] <willcooke> mhall119, well said sir.  (@ your email re: wallpaper)
[15:01] <mhall119> thanks, I don't know why we get so much negativitiy on that list
[15:02] <mhall119> s/list/thread/
[16:28] <jose> mhall119: as long as it's a good burrito, I have no problem
[16:29] <mhall119> well, it's an Americanized burrito, but I like them
[16:30] <popey> mmmmm burrito
[16:30] <popey> http://drool.popey.com/
[16:32] <jose> my last meal in the US was a burrito
[16:37] <popey> I tend to overdose on wings in the US
[16:37] <popey> On one of our sprints I had wings _every_ day.
[16:37] <popey> sooooo nice
[16:46] <willcooke> \o/
[18:32] <pleia2> yay, community team update \o/
[18:33] <pleia2> mhall119: I don't know what's up lately, I know my filter is skewed, but I keep bumping into negativity everywhere lately
[18:33] <pleia2> the response to nhaines made me really sad
[18:33] <pleia2> mhall119: so thank you for standing up for him <3
[18:51]  * philipballew is currently eating a burrito


[04:25] <Muscovy> Are the Launchpad servers really busy? A few of my packages have a wait of three days.
[04:29] <micahg> Muscovy: the PPA builders get re-appropriated around release time, there are only 3 per arch ATM
[11:34] <alourie|work> hello
[11:35] <alourie|work> I have the question regarding the REFERER header - how do I enable it?
[11:39] <spiv> alourie|work: by undoing of however you disabled it -- it's enabled by default in pretty much every web browser.
[11:40] <spiv> alourie|work: possibly there's an firefox add-on you need to tweak
[11:40] <alourie|work> spiv: I don't even know what that means :-) I didn't disable anything. I just know found out it exists...
[11:40] <alourie|work> oh
[11:40] <alourie|work> so you mean I may have an add-on that blocks it?
[11:40] <spiv> Right
[11:40] <alourie|work> hm
[11:40]  * alourie|work is puzzled
[11:41] <spiv> Probably one designed to guard your privacy
[11:42] <alourie|work> I have no add-ons like that
[11:42] <alourie|work> all are webdev and download tools
[11:44] <alourie|work> unbelieavable
[11:46] <alourie|work> works in chrome though
[13:49] <sjamaan> Is something the matter with the git importer?
[13:49] <sjamaan> http://launchpadlibrarian.net/47254275/peter-bex-chicken-git-mirror.log
[14:08] <jelmer> sjamaan: hi
[14:08] <sjamaan> hi jelmer
[14:08] <jelmer> sjamaan: it looks like it's using an outdated version of dulwich
[14:08] <sjamaan> What's that?
[14:11] <sjamaan> (and more importantly, how can it be fixed?)
[14:53] <ricotz> hello, is someone monitoring builds which are failing over and over again with a "dependency wait" error, for example https://edge.launchpad.net/~inkscape.testers/+archive/ppa - https://edge.launchpad.net/~inkscape.testers/+archive/ppa/+build/1187463
[14:55] <ricotz> kiko, hello ^
[16:53] <vadi2> I just upgraded my main branch using 'bzr upgrade' and tried to push it to LP, but this failed: http://paste.pocoo.org/show/208873/ any idea why? I had to upgrade it as well because it didn't allow me to create any new branches at all due to different branch format versions
[17:01] <MrKanister> Hi there. I've got a question regarding launchpadlib. Let's say I want to find out the version of a package in the latest Ubuntu release. How do I get there by using the launchpadlib?
[17:01] <MrKanister> From the API Doc I have to use a pacakge_publishing_history, but I don't know how to get there starting from a package or distribution object.
[17:06] <vadi2> Got it, had to press upgrade button on launchpad branch
[17:28] <d34df00d> Hi!
[17:28] <d34df00d> I've uploaded a package to my PPA to be built.
[17:29] <d34df00d> Then I realized that it I entered wrong Ubuntu release, and deleted the package before it has been built.
[17:29] <d34df00d> Now the package, despite being deleted and not showing up in the list of packages, appears in the build queue.
[17:29] <d34df00d> That's after it already had been tried to be built and failed (cause I've deleted it).
[17:29] <d34df00d> Is there anything I can/should do about it?
[17:34] <om26er> The message you sent included commands to modify the bug report,
[17:34] <om26er> but you didn't sign the message with your OpenPGP key.
[17:34] <om26er> I get this when I reply a bug with email
[17:44] <geser> om26er: did you include any commands to modify the bug? if yes, then the mail has to gpg signed
[17:45] <om26er> geser, yes
[17:45] <om26er> geser, so that mean I have to use an email client?
[17:45] <geser> om26er: usually you use an webmailer?
[17:46] <om26er> geser, all the time (gmail)
[17:49] <geser> om26er: if you use firefox, try using firegpg (http://getfiregpg.org/) to sign your email when using gmail over the browser
[17:49] <om26er> geser, hm I am die hard chromium user. Thanks for the info :)
[17:51] <geser> om26er: then try copying the mail body into a file, sign that file, copy the signed mail body back into the webmail form
[17:51] <vadi2> Question... does loggerhead check if the branch is private and the user is logged in?
[17:51] <vadi2> I seem to be able to browse private branch contents without being logged in.
[17:52] <om26er> geser, I'll defer ;)
[17:52]  * om26er tries anjal this time
[20:35] <xnox> does launchpad still build superseeded sources packages?
[20:35] <xnox> or does it skip it
[22:03] <ZykoticK9> Why is there no method of reporting offensive posts to launchpad/answers?  I have attempted to ask for offensive posts to be rename/deleted previous in this irc channel and was told to ask a question.  IRC has OPs, Forums have Mods, why is there not an equivalent for Launchpad?  Titles and posts suck as the current https://answers.launchpad.net/ubuntu/+question/109301 should be dealt with in some manner, if only to change the title.
[22:03] <ZykoticK9> s/suck/such
[22:10] <ZykoticK9> I'm shocked, it appears I can change the name of the post myself.  does that showup changed for everyone?  how is that even possible?  and i get karma for it possible as well - hilarious, issue resolved.  sorry for the rant - thanks everyone.
[22:42] <nhandler> ZykoticK9: Anyone can modify a bug title or description. However, only LP admins can edit/delete comments
[22:43] <ZykoticK9> nhandler, changing the title is perfect.  I'm shocked, but it's perfect.


[21:27] <clifter> Is it better to install with using the "Ubuntu Software Center" or from "Terminal" using sudo apt-get install <program> ? ? Advantages or disadvantages to either way ? ?
[21:28] <pleia2> I wouldn't say one is better than another
[21:28] <pleia2> a lot of people find the ubuntu software center easier to search and use (particularly if they don't like the command line)
[21:29] <blitz> one way you learn more about the terminal
[21:29] <pleia2> I've always used apt-get without issue though
[21:29] <blitz> I feel like using apt-get is more transparent as to what's actually going on
[21:29] <blitz> you know what packages you're getting
[21:33] <clifter> pleia2; blitz: Thanks - I favor Terminal because I see right away if package installed ok. Just wondering wasn't sure where to ask? Is this channel ok for occasional general support question?
[21:36] <pleia2> clifter: yep, asking here is fine :)
[21:41] <clifter> pleia2: Cool thanks much
[23:51] <clifter> I have forgotten proper way to add another irc channel to start as well as my default channel. Any ideas?
[23:55] <clifter> Running Ubuntu 13.10 - Icon for log-off & shutdown is missing after a reboot I just did. What would be a good fix? Have used Terminal before.


[15:54] <cmaloney> morning (for another 7 minutes)
[15:56] <greg-g> ...and 3 hours
[15:56] <cmaloney> Not in God's timezone. ;)
[15:58] <jrwren_> what time is it in Jarusalem?
[15:58] <jrwren_> or Jerusalem?
[15:58] <jrwren_> oh, 7pm.
[15:58] <greg-g> Mecca
[15:58]  * jrwren_ poors a drink
[15:58] <cmaloney> God's Timezone is EDT
[15:58] <cmaloney> says so in the bible.
[15:59] <cmaloney> (somewhere, I'm sure)
[19:02] <aleph_one> since I've never been to a MUG event, I've got a question about how it works
[19:03] <aleph_one> I'm looking into getting an Asus C201 and installing the libreboot port for it
[19:03] <aleph_one> if I have questions/run into problems, would the MUG meeting be an okay place to ask around? assuming I've done my own research, etc.
[19:14] <cmaloney> Sure, though we also have a discuss mailing list that may be of service prior to the meeting
[19:14] <cmaloney> usually we have more presentation-type material than Q&A
[19:56] <aleph_one> cool


[03:01] <squisher> rbasak, jamespage: I pushed some more changes to bcache-tools, and I think it's ready for a release. It should be all prepped, but it's not tagged yet (waiting for feedback from you guys first)
[03:15] <DonRichie> Can somebody give me a link to a tutorial how to make an ubuntu guest ready for a virtio network adapter? Googling confuses me at the moment since the tutorials I find refer to the configuration on the kvm host itself
[03:17] <DonRichie> Am I done by installing libvirt-bin and then enabling virtio for the adapter on the KVM Host system?
[08:30] <rbasak> squisher: OK, I'll take a look.
[08:35] <lordievader> Goodmorning.
[10:18] <pvlos> hello guys, I read that a backport for apache may be released for <apache2.4 versions regarding the logjam attack
[10:19] <pvlos> is there any ETA for the packages?
[10:19] <pvlos> I am using 12.04
[10:25] <bekks> pvlos: Which CVE is it?
[10:25] <pvlos> bekks: http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-4000.html
[10:27] <bekks> Well, 2.2 is currently in needs-triage. So no need to backport 2.4
[10:27] <bekks> The link can be found in your link :)
[10:29] <pvlos> bekks: I know but the 'needs-triage' may stay forever
[10:29] <bekks> As for every bug. There is no guarantee that a bug will be fixed.
[10:30] <pvlos> bekks: the bug is critical though
[10:31] <pvlos> is there any way to fix the issue withou the backports?
[10:31] <pvlos> without^
[10:31] <bekks> Which makes it very likely that it will be fixed, but still no guarantee
[10:32] <pvlos> i see
[10:32] <bekks> And since 12.04 (and 2.2 with it) are supported until 2017, it is not likely that a backport isneeded. Instead, 2.2 will be fixed.
[13:57] <lukasa_> Hey all: does the cloud archive repository lag behind the cloud-archive staging PPA?
[13:57] <lukasa_> Because the cloud archive Kilo staging PPA contains a fix for libvirt that does not appear to have made it to the package source that is added by apt-add-repository cloud-archive:kilo
[14:20] <jamespage> lukasa_, it will get there - the staging PPA is a holding area for entry in the stable update process
[14:22] <jamespage> lukasa_, those updates are in proposed - http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/kilo_versions.html
[14:22] <jamespage> just pending some testing
[14:32] <lukasa_> jamespage: ah great, thanks
[14:32] <lukasa_> Out of interest, do you know what the timeline usually is?
[14:49] <jamespage> lukasa_, normally minimum of a week
[14:49] <jamespage> lukasa_, those ones colided with last weeks summit - apologies
[14:50] <lukasa_> jamespage: No worries, it happens. =) Just wanted to make sure I understood what was happening. For testing we can temporarily use the kilo-staging PPA. =)
[14:50] <jamespage> lukasa_, use the proposed pocket
[14:50] <jamespage> add-apt-repository cloud-archive:kilo-proposed
[14:51] <lukasa_> Ah, much better idea, thanks!
[14:51] <jamespage> lukasa_, that way you will use exactly the same binary as we release to updates
[14:58] <jamespage> lukasa_, i've just kicked off the testing - if that succeeds, I'll push through today
[14:58] <jamespage> mean't to be taking two days off :-)
[14:58] <lukasa_> That's extremely kind of you jamespage, thanks so much. =)
[14:58] <jamespage> lukasa_, no problemo
[14:58] <lukasa_> In return, I promise to ask you no further questions for a week or so
[14:58] <lukasa_> (If only because I'm on holiday myself. ;) )
[14:58] <jamespage> lukasa_, well until monday nayway
[15:09] <turambar> hi, any experts on pxeboot here? :)
[15:10] <turambar> i want to know if it is possible to provide a kickstart file on the server that provides the netboot infrastracture via its local filesystem instead of an url
[15:18] <rbasak> How would a booting machine get to the local filesystem on the boot server?
[15:20] <Ameurux> the question is not clear
[15:44] <aryklein> is there any good reason why ubuntu cloud image comes with grub-legacy instead of grub2?
[15:45] <aryklein> is there any good reason why ubuntu cloud image comes with grub-legacy instead of grub2?
[15:46] <genii> aryklein: Ask whoever provided the images, Like Amazon or whoever it is
[15:47] <aryklein> genii: I got it from https://cloud-images.ubuntu.com/
[15:47] <aryklein> genii: so this is the reason why I'm asking it here
[16:02] <genii> aryklein: From what I can find, it's due to an issue between Xen Hypervisor and Grub2
[16:02] <aryklein> genii: ah ok. Thanks for the info
[16:29] <gartral> hey all, I'm working colaboratevly on a server backend with someone and I've been wondering; is it possible to share a proccess, or control there of, to a group of people like you can files?
[17:31] <sarnold> gartral: shared tmux or screen sessions
[17:31] <sarnold> gartral: it's perhaps not as easy/transparent as sharing files, but it works well enough
[19:03] <baggar11> When did linux-generic-lts-vivid drop?
[19:03] <baggar11> Am I seeing it right, that it dropped on the 21st?
[19:04] <baggar11> for 14.04...
[19:04] <sarnold> looks like the 20th to me https://launchpad.net/ubuntu/+source/linux-meta-lts-vivid
[19:05] <baggar11> sarnold: thanks, wasn't sure if it was the proposed date or the updates date on the 21st
[19:05] <sarnold> the "full publishing log" shows 2015-05-20 17:13:35 PDT -- presumably it'll localiz e to your timezone if you visit https://launchpad.net/ubuntu/+source/linux-meta-lts-vivid/+publishinghistory
[19:10] <broder> is it possible to access a copy of the archive in s3? we were hoping to point some of our servers at one of the new in-vpc s3 endpoints
[19:10] <broder> (i see $region.ec2.archive.ubuntu.com, but it looks like that points at ec2 instances)
[19:12] <sarnold> broder: I suggest checking in #ubuntu-mirrors -- I know some of the aws mirrors were on s3, but there were reliability issues, I don't know if they have been addressed or replaced with ec2 instances..
[19:12] <broder> ah, cool. will do - thanks!
[19:12] <sarnold> it seems like it's been a while since I've heard reliability complaints there.. hehe
[19:13] <broder> i've been trying to piece together what happened from email archives. it looks like it was originally s3, but i suspect they moved to ec2 because something something snapshot consistency
[19:33] <tyler_wy1ie> o/ has anyone here who's used fai configured their grub? i'm running into some snags trying to fix it
[19:58] <gartral> sarnold: the issue with shared tmux/screen is that it's a huuuge security hole... I don't want the other members to run programs as the dedicated user..
[19:59] <gartral> sarnold: if I wanted to do what you were suggesting I would have just given them an SSH key for the user
[20:03] <gartral> also I have an edge-case issue that I'm unsure how to reslove.. I have a code base that I need to import from a *VERY* old backup, we're talking 5-1/2 inch floppies, I happen to HAVE a 5-1/2 inch floppy drive so that's not a problem... the problem is there's hundreds of files and they're all upper-case, how can I squash-case them without doing it file by file, by hand?
[20:06]  * gartral makes a mental note that he should have used better punctuation there...
[20:07] <sarnold> gartral: try mount(8) option shortname=lower
[20:08] <gartral> sarnold: already tried, i got no data transfered
[20:08] <sarnold> oh :(
[20:08] <jdstrand> sarnold: that is an interesting idea. I would going to suggest rename(1p)
[20:08] <jdstrand> s/would/was/
[20:08] <sarnold> gartral: you can probably also configure sudo to let your pals run a few specific commands as a specific user..
[20:08] <gartral> sarnold: I have them safely on the HDD, I just want a move command that'll squash-case
[20:09] <sarnold> jdstrand: heh, that was goiong to be my suggestion if the mount option didn't work :)
[20:09] <jdstrand> :)
[20:10] <gartral> oh dear god this is going to be fun compiling later, it's partially written in f***ing LISP
[20:11] <gartral> can GCC even handle in-line lisp? >.<
[20:12] <sarnold> you may have better success getting emacs to do C :)
[20:12]  * sarnold runs
[20:12] <gartral> LOL
[20:14] <gartral> o.o ok, never mind... whoever wrote this was a bloody genius... there's a LISP parser, written in C, in the code to handle the Lisp in-line... I now feel wholy under-qualified to even touch these disks
[20:19] <gartral> an-e-way how would I go abuot squash-casing these?
[20:26] <jrwren> is it gnu common lisp?
[21:11] <tonyyarusso> gartral: What was wrong with the rename suggestion?
[21:24]  * genii ponders rename 'y/a-z/A-Z/'
[21:33] <inno> hello, i maintain an ubuntu vps for my blog, which i command from a mac via ssh
[21:34] <inno> i'd like to backup and move my production site to my local mac, make changes and then upload back to production the changes
[21:34] <inno> i'm trying to setup an rsync deal, but was wondering if that's the way to go, or should i use scp
[21:34] <inno> or... ?
[21:34] <inno> i'm kinda new to all of this
[21:34] <sarnold> rsync is awesome, definitely beats scp individual files or re-copying everything needlessly
[21:35] <sarnold> no need to run an rsync daemon though, just rsync -e ssh ... is sufficient
[21:35] <sarnold> (and probably the -e ssh isn't even needed these days)
[21:35] <sarnold> consider also using git; a local and remote repository, so you can just pull changes when you make them; thishas proven popular on e.g. heroku
[21:36] <inno> yeah, i'm looking at git as well for this and currently have the site dir as a git repo as well
[21:37] <inno> i'm using ghost for the blog and it requires turning off the ghost service before doing anything with the database, so i'm not sure yet how to handle that
[21:37] <inno> with the git solution
[21:37] <inno> with the rsync one, i wrote a script i run on my mac that ssh's into the vps, stops the service, rsyncs everything, and then starts the service again
[21:40] <inno> i modified the sudo config so that a password isn't required over ssh when starting and stopping the service for my user
[21:40] <inno> is this the right approach?
[21:40] <inno> and should I set a delay after the call to stop the service to make sure it stops before running the rsync command (the next line in the script)?
[21:40] <sarnold> it's probably fine if it's a single-purpose system
[21:40] <sarnold> please promise me you're using ssh keys rather than passwords though :)
[21:41] <sarnold> there may be a way to use e.g. status <foo> to find out if the service is still running or not
[21:42] <inno> haha, i am using ssh keys to connect, although it used to ask me for passwords for sudo commands until i made that change
[21:42] <inno> is there something else i need to do?
[21:42] <inno> ah, that would be awesome to check for the service status and then run the rsync
[22:48] <harushimo> Can I install maas on a VM?
[22:48] <harushimo> I've been doing that last couple times
[22:49] <sarnold> hey harushimo :) I thuoght of you when this got pasted around the other day: http://www.ubuntu.com/download/cloud/install-ubuntu-openstack
[22:50] <harushimo> I did
[22:50] <harushimo> I couldn't get passed step 3
[22:51] <harushimo> I needed to redo my VMs again
[22:51] <harushimo> hehe
[22:52] <harushimo> its an experiment
[22:52] <sarnold> d'oh :)
[22:52] <speedy> hi
[22:55] <harushimo> sarnold: any tips?
[22:56] <sarnold> harushimo: you should be able to do maas in a vm, though that does mean your VM needs to be configured properly to allow the vm guest to do all the raw networking it wants to
[22:56] <sarnold> so it can't do NAT and that kind of stuff around the vm
[22:57] <harushimo> sarnold: I've  been following http://marcoceppi.com/2012/05/juju-maas-virtualbox/
[22:58] <marcoceppi> harushimo: that guide is pretty out of date now
[22:58] <harushimo> marcoceppi: any tips
[22:58] <marcoceppi> harushimo: it's much better to use libvirt and qemu since MAAS can actually use that as a power type
[22:58] <harushimo> marcoceppi: do you have some instructions on that
[22:59] <marcoceppi> harushimo: not really, there are some on the MAAS website but they are kind of incomplete. I can do a blog post tonight if you'd like about it
[22:59] <harushimo> marcoceppi: that would be great
[22:59] <harushimo> marcoceppi: I can't get pass step 3 on that documentation
[23:00] <harushimo> marcoceppi: I've been trying to install openstack so I can install cloud foundry
[23:01] <marcoceppi> harushimo: well you're going to want something more than VMs
[23:01] <harushimo> marcoceppi: oh really?
[23:01] <marcoceppi> harushimo: yeah, I mean eventually
[23:02] <harushimo> marcoceppi: I agree..sorry this for my dev purposes
[23:02] <harushimo> marcoceppi: I would need more than VMs
[23:12] <marcoceppi> harushimo: how are you deploying cloud foundry?
[23:15] <harushimo> marcoceppi: It will be done through openstack
[23:16] <harushimo> marcoceppi: I need to install hypervisor which is openstack and I install over that
[23:17] <marcoceppi> Right right, no worries. Okay, I need to fix my MAAS machine but once that's sorted I'll start on the blog post/video
[23:18] <harushimo> marcoceppi: thank you so much
[23:19] <harushimo> marcoceppi: companies are going this route. I want to be learn the technology and sell myself too
[23:19] <harushimo> marcoceppi: I'll continue to experiment


[00:25] <klynch> Hi all
[04:51]  * Takyoji trolls Ubuntu 11.04 moar
[04:51] <Takyoji> I'm certainly fleeing to Lubuntu now on all my systems.
[04:52] <Takyoji> even the GNOME fallback in 11.04 is unstable
[14:05] <klynch> Hi all
[20:29] <fisch246> anyone interested in seeing the midnight showing of Harry Potter?
[20:35] <tonyyarusso> What day is it even?
[21:09] <fisch246> july 15th
[21:09] <fisch246> at 12 a.m
[21:10] <fisch246> i know it's early
[21:10] <fisch246> but i want to know if people are planning to see it, so i know if it's even worth setting it up
[21:10] <fisch246> maybe just go as friends or something
[21:10] <fisch246> it would be easier with just a few people
[22:03] <klynch> we need to update the wiki, there is a note from 2008
[22:03] <klynch> bit out of date.


[10:42] <TJ-> I have a long-running Linux VM that gets its IPv6 via SLAAC, but after the first successful allocation it seems to expire and not be renewed, losing connectivity. I've tracked it down to the kernel's net.ipv6.conf.eth0.autoconf being set to 0 - but cannot find anything configured to change that. Anyone have any ideas on what might be doing it? This is Ubuntu 18.04 using ifupdown (not
[10:42] <TJ-> systemd-networkd)
[11:06] <tomreyn> the "suddenly after the system booted and ran fine for a while, network configuration changed" symptom reminds me of earlier reports on cloud-init, but that'S the only thing i could think of. and i'm not sure this sounds related to what you're seeing.
[11:28] <Skyrider> What's the best way to upgrade sudo from 1.8 to 1.9?
[11:31] <andol> Carefully :-)
[11:32] <andol> Looks like there are sudo 1.9 packages for Ubuntu 20.10.
[11:33] <andol> If you really need sudo 1.9 for your current Ubuntu release I suggest you rebuild those, and try them out in a test environment.
[11:33] <Skyrider> I recall upgrading sudo weeks ago in my lxc container. Forgot how to though :D
[11:34] <andol> Curious, what's the draw of sudo 1.9?
[11:35] <Skyrider> sudo: setrlimit(RLIMIT_CORE): Operation not permitted <- having this bug fixed in containers.
[11:35] <Skyrider> https://github.com/sudo-project/sudo/issues/42
[11:35] <andol> Ah.
[11:35] <Skyrider> Odd ubuntu 20 comes with a legacy release of sudo though.
[11:36] <andol> Nitpick: There is no such thing as Ubuntu 20.
[11:36] <andol> Ubuntu 20.04 is just as close to 19.10 as it is to Ubuntu 20.10.
[11:37] <Skyrider> I tried looking for 1.9 in the cache policy, but only 1.8 pops up.
[11:38] <andol> Also, looks like sudo 1.9 was released after Ubuntu 20.04 came out.
[11:38] <Skyrider> Guess that makes more sense then ^_^
[11:39] <andol> Anyway, if this is only for a container, rather than for a bare metal host, everything ought to be a lot easier and safer.
[11:40] <andol> Might just as well try grabbing the Ubuntu 20.10 sudo 1.9 binary package(s), and see what happens if you try to install them directly.
[11:42] <Skyrider> I attempted to grab the deb packages, but its attempting to remove my existing sudo.
[11:42] <Skyrider> Which leads to errors "Refusing to remove sudo"
[11:48] <andol> Interesting.
[11:48] <andol> Worked fine for me in an Ubuntu 20.04 VM. https://paste.ubuntu.com/p/FgQyQ7JKwd/
[11:52] <Skyrider> Oddly enough running it a second time works. O_o
[11:52] <Skyrider> Though, its complaining about libpython3.6, not installed. for sudo-ldap and sudo-python.
[11:54] <tomreyn> mixing packages from different ubuntu releases is generally not advisable (exceptions may apply, but that's unsupported then)
[11:54] <Skyrider> I merely grabbed the "sudo-python_1.9.0-1_ubu1804_amd64.deb" file as well, which depends on python3.6
[11:54] <tomreyn> i'd certainly not recommend doing this for the purpose of snoozing a warning message
[11:55] <albert23> Skyrider: did you see there is a very simple solution? echo "Set disable_coredump false" >> /etc/sudo.conf
[11:56] <Skyrider> I actually had no idea ^_^, I merely saw it was resolved in  1.9 of sudo
[11:56] <tomreyn> noticing this would have involved reading more than the first two posts of the bug report
[11:57] <Skyrider> Guess it is because I merely expected for upgrades to latest versions in combination of ubuntu 20 being new as well would be simple.
[11:57] <andol> Skyrider: That sudo-python package doesn't look like it's from the official repositories?
[11:58] <Skyrider> Ya, guess that's my fault for relying on a third party site ^^
[12:17] <TJ-> tomreyn: turned out to be my bad - ifupdown config for IPv6 - if you do not specifically add "autoconf 1" to *every* IPv6 static stanza the tooling sets it to 0 (disabling SLAAC) and we have about 15 static assignments to the same interface and only the first set "autoconf 1"
[12:20] <tomreyn> TJ-: hmm, maybe that's a good reason to do away with ifupdown then indeed.
[12:20] <TJ-> yeah... this is a system that has evolved continuosly since 2007
[12:20]  * tomreyn shudders
[12:21] <TJ-> the problem was the uncommanded "autoconf=0" for the interface
[12:21] <TJ-> at least with ifup --no-act --verbose --force I was able to see it issuing the commands - can't do that with systemd-networkd!
[12:23] <tomreyn> i agree that debugging isn't as easy with many parts of systemd as it should be
[12:24] <tomreyn> (or i lack understanding of how to do it properly)
[12:25] <TJ-> no way to manage active state of sd-nd at present that I'm aware of
[12:26] <tomreyn> hmm, i don't think i ever tried
[12:29] <TJ-> you have to edit the text config files and restart the service
[12:30] <tomreyn> hmm, that's a bit unexpected, a deviation from the behaviour of other service units.
[12:31] <tomreyn> but then i guess networking is somewhat ffoundational and you don't want to accidentially disable it, if that's the perspective where this came from.
[12:31] <tds> i quite like ifupdown2 as an ifupdown alternative
[12:32] <tds> being able to properly diff the running state against config, and only apply changes as needed, is very nice
[12:34] <trippeh> the latest sd-nd has up/down per interface, but you may still need to reload (havent tested it extensively)
[12:35] <TJ-> now I'm fighting with the obtuse openwrt method of configuring multiple interfaces to get IPv6 PD working correctly
[12:35] <trippeh> yeah you just define a wan6 pointing to the same interface/bridge
[12:38] <TJ-> trippeh: unfortunately not in this case; the WAN side is fine and I've just got the LAN side (via Luci) to look correct, clients are seeing PDs and using SLAAC too, but the routing is going astray somehow, or firewall isn't being correctly set. Unusual situation in that I've a /48 PD but the upstream router from me has taken an address from within the PD range so I've had to put a /126 on
[12:38] <TJ-> the WAN6
[12:39] <trippeh> I have DHCPv6-PD working with openwrt, and systemd-networkd at home.
[12:41] <trippeh> the PD support in sd-nd has become quite serviceable in 246
[12:42] <trippeh> TJ-: thats a little weird indeed - but can you just not assign the /64 upstream is in on the downstreams?
[12:44] <TJ-> trippeh: well, the upstream router is on PD::1/48
[12:45] <trippeh> as in /48 "on link"??
[12:45] <TJ-> trippeh: yes
[12:46] <trippeh> are you sure. are they drunk
[12:46] <RoyK> Generally you don't segment to lower than /64
[12:47] <RoyK> But that only gives you 65536 networks on a 48-bit prefix, which can possibly be a hassle? ;)
[12:51] <TJ-> RoyK: it definitely is for our use-case !
[12:53] <RoyK> TJ-: erm - what usecase is that?
[12:56] <TJ-> RoyK: addressing every star in the universe :)
[12:57] <RoyK> TJ-: something like this? https://xkcd.com/865/
[13:01] <TJ-> RoyK: not far off :)
[13:02] <RoyK> TJ-: but seriously - what are you trying to do here?
[13:03] <TJ-> ^^^ read above ^^^
[13:06] <trippeh> if the upstream router has /48 on-link, and then needs to install the same /48 route to your openwrt, what does it do?
[13:06] <trippeh> does it become a ECMP route?
[13:07] <trippeh> this setup sounds borked
[13:08] <RoyK> TJ-: if using openwrt, how large will this routing table become if you do it your way? I *really* doubt your router will be able to handle that
[13:08] <TJ-> RoyK: one entry in the table
[13:08] <TJ-> the /48
[13:09] <RoyK> but what's the point of all those networks???
[13:12] <RoyK> btw, I was thinking more of the internal routing tables - one entry for each network - it'll be a rather nasty job for a small cpu
[13:17] <trippeh> I am rather confused. :)
[13:17] <RoyK> aren't we all?
[17:57] <znf> Here's something I've been beating my head around. I need to install a HWE kernel on 18.04; thing is, last time I did this, the server wouldn't come back online -- it booted, but something happened to it's networking.
[17:57] <znf> What that was? I've no idea.
[17:57] <znf> The thing is - I've got no IPMI/IKVM on this. How can I reboot into the new kernel and then reboot back to the old one if something happens? What's a good failsafe?
[18:01] <tds> znf: can you powercycle the machine remotely?
[18:01] <znf> no
[18:01] <znf> I was thinking I could simply make a script reboot automatically in ~5 minutes unless killed
[18:02] <znf> but I'm drawing a blank on how to make it choose the old kernel back
[18:04] <tds> i suppose you could have the script just reconfigure grub, though that's a bit nasty
[18:05] <znf> and my friend is not to keen on driving there and going on top of a 13 story building with a keyboard and monitor to fix it, understandably
[18:06] <tomreyn> there's a single good answer to such scenarios: wait until you can do it safely.
[18:07] <tomreyn> that's unless it's not a production system and you don't mind loosing it for days or weeks until someone passes by.
[18:08] <znf> eh, it's a box with the only purpose of capturing DVB-S (hence why it's on top of the building)
[18:09] <znf> and I just need the newer kernel to enable a newer intel video driver so I can use quicksync
[18:10] <tomreyn> from what i read it was 'just' that last time, too.
[18:11] <tomreyn> 'just' a differently configured reboot ;)
[18:12] <znf> I mean it's not that important :P
[18:14] <tomreyn> there's grub-reboot for this scenario you have, but i haven't used it in a while, so i'm not certain this still works reliably. maybe soemone else can comment.
[18:21] <znf> I see
[18:21] <znf> that's interesting, but it doesn't really say how the hell to get a picture of the actual MENU_ENTRY number
[18:24] <tomreyn> yes, we lack a utility for this. but i *think* this gives it away:   grep -o "menuentry '[^']*.*" /boot/grub/grub.cfg | awk -F "'" '{print $2":\n\t"$4}'
[18:24] <tomreyn> start counting at 0
[18:28] <znf> the confusing part is the submenu stuff
[18:28] <znf> Ubuntu does it in submenus
[18:29] <znf> The titles should be separated using the greater-than character (>) with no extra spaces.  Depending  on  your  shell  some  characters
[18:29] <znf>        including > may need escaping.
[18:29] <znf> granted, I could also do "Ubuntu, with Linux 4.15.0-99-generic"... probably
[18:48] <tomreyn> right, the submenus are a bit tricky and error prone
[18:51] <tomreyn> https://unix.stackexchange.com/questions/62733/how-to-correctly-set-up-the-right-grub-2-default-menu-entry
[18:54] <tomreyn> so, since the "Advanced" menu is usually the second entry on the main menu, you start with "1" (remember, it's an index, start couting at 0), then you add ">" to indicate there's a submenu, and from the submenu you pick the very entry, again starting to count at 0
[19:12] <xae-a12> Any1 here have experience blocking fake harmful bots?
[19:14] <tomreyn> xae-a12: why, do you live in seattle? build thicker walls, i'd say.
[19:14] <xae-a12> no i thankfully do not lol
[19:15] <tomreyn> but maybe you weren't referring to pysical bots after all, and i just jumped to conclusions for lack of detail?
[22:02] <SpaceBass> Hey folks - I'm trying to debug a problem with LDAP authentication. Does anyone know if it is possible to get verbose output or logs in Ubuntu for libnss_ldap ? ... the config file supports a logging option but it's not clear that the ubuntu client supports it


[08:20] <_hc> hello all, I'm a DD and I'm checking in on the status of my packages in Ubuntu/hirsute.  This update seems to be stuck in "proposed" even though it made it into Debian/testing/bullseye a while ago: https://launchpad.net/ubuntu/+source/androguard
[08:20] <_hc> is there something I can do to get it unstuck?
[08:28] <Unit193> First stop would be to https://people.canonical.com/~ubuntu-archive/proposed-migration/hirsute/update_excuses.html#androguard where you can see autopkgtest regressions.
[08:35] <Unit193> (See also: http://autopkgtest.ubuntu.com/running#pkg-androguard - http://autopkgtest.ubuntu.com/packages/a/androguard)
[08:37] <_hc> could someone retrigger those failed runs? it seems like something killed the tests
[08:37] <_hc> I tried but I don't have permissions
[08:38] <_hc> it is passing on all arches in Debian/bullseye https://ci.debian.net/packages/a/androguard/
[08:38] <_hc> all supported arches
[08:41] <Unit193> Yeah, I did so when you first asked.
[08:41] <_hc> thanks
[11:30] <ginggs> _hc: out of memory.  Killed in the log and passing on armhf are reliable indicators of that
[11:31] <seb128> so, I triggered     ['chromium-browser/89.0.4389.82-0ubuntu<IP_ADDRESS>'] for bionic/amd64 earlier
[11:31] <_hc> do ubuntu's runners have less RAM than Debian's?  Is there something I should do?
[11:32] <seb128> but there is no result showing on https://autopkgtest.ubuntu.com/packages/chromium-browser/bionic/amd64 and it's not in the running page
[11:32] <seb128> how can I tell what happened there? is that pending a webpage refresh?
[11:32] <seb128> did it silently fail for some reason and if so how do I tell that's the case?
[11:37] <ginggs> _hc: much less.  androguard needs to be added to the big_packages list so the test will run on a bigger cloud instance.  i've been meaning open a MR for some other packages, i'll add yours to the list
[11:38] <_hc> thanks!
[11:48] <Laney> seb128: it seems to be there, I'm guessing you were just waiting for it to be fetched by the website
[12:13] <seb128> Laney, ah, I should have waited a bit more, thanks :)
[12:13] <seb128> oSoMoN, so yeah, it's also failing, not specific to the ppa
[12:48] <oSoMoN> seb128, ack, thanks for confirming this
[12:49] <seb128> np!
[16:25] <cjwatson> rbalint: Sorry for the long delay!  I'm getting copious coffee and working on a reply now ...
[16:26] <rbalint> rbasak, ^ , guess :-)
[16:26] <cjwatson> Ugh, sorry
[16:26] <cjwatson> Quite right
[16:39] <rbasak> Thanks!
[20:02] <coreycb> Hello release team, I would like to sync python-dogpile.cache from debian experimental as it's needed by a new version of python-oslo.cache for OpenStack.
[23:54] <rbasak> Trevinho: do we need to revert the sssd SRU?
[23:56] <Trevinho> rbasak: It's not clear to me what are the affected cases, as that comment looks more a warning, or what?
[23:58] <rbasak> AFAICT, the reporter is giving us a use case that breaks auth when your SRU is applied?
[23:58] <Trevinho> rbasak: yeah, not sure there's an actual case though?
[23:59] <Trevinho> rbasak: I mean I hope so, so indeed would be better to proceed with safer upgrade if there's such risk