[08:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:39] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_baloo-widgets build #78: FIXED in 19 min: https://kci.pangea.pub/job/bionic_unstable_baloo-widgets/78/
[08:45] <acheronuk> sitter: seen the email about debconf-kde. test building in a ppa. thanks
[08:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2169: SUCCESS in 44 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2169/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2169: SUCCESS in 1 min 14 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2169/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2169: SUCCESS in 4 min 12 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2169/
[09:44] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_ksmtp build #21: STILL FAILING in 11 min: https://kci.pangea.pub/job/xenial_stable_ksmtp/21/
[09:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ksmtp build #93: STILL FAILING in 14 min: https://kci.pangea.pub/job/xenial_unstable_ksmtp/93/
[12:09] <BluesKaj> Hi folks
[12:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #656: FAILURE in 54 sec: https://kci.pangea.pub/job/xenial_unstable_kstars/656/
[12:15] <Riddell> acheronuk: a request from kpm guy <stikonas[m]> Riddell: also, do you know if patch from https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1752876 can be pushed to either ubuntu or neon
[12:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #272: FAILURE in 5 min 48 sec: https://kci.pangea.pub/job/artful_unstable_kstars/272/
 @Riddell> acheronuk: a request from kpm guy <stikonas[m], I can take this one unless he's already looking at it.
[12:16] <Riddell> go for it tsimonq2
[12:16] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #113: FAILURE in 6 min 48 sec: https://kci.pangea.pub/job/bionic_unstable_kstars/113/
 Thanks for the pointer Riddell
 Please do :)
[12:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #114: NOW UNSTABLE in 40 min: https://kci.pangea.pub/job/bionic_unstable_kstars/114/
[13:13] <ronnoc> morning valorie! I will blog about the banner request - wishing it also included a new Kubuntu wallpaper as well
[13:14] <ronnoc> however looking at Phabricator it would seem a concrete theme needs to be decided on first before that be a discussable option.
[13:25] <acheronuk> it's not changing now
[14:04] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #115: STILL UNSTABLE in 36 min: https://kci.pangea.pub/job/bionic_unstable_kstars/115/
[14:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #657: STILL FAILING in 2 min 21 sec: https://kci.pangea.pub/job/xenial_unstable_kstars/657/
[14:27] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #273: STILL FAILING in 4 min 30 sec: https://kci.pangea.pub/job/artful_unstable_kstars/273/
[14:49] <ronnoc> acheronuk: ofc
[14:54] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #116: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/bionic_unstable_kstars/116/
[14:54] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2170: SUCCESS in 46 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2170/
[14:55] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2170: SUCCESS in 1 min 15 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2170/
[14:58] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2170: SUCCESS in 4 min 11 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2170/
 @DarinMiller are you able to test that nvidia issue with the latest sddm?
[16:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_smb4k build #134: FAILURE in 1 min 2 sec: https://kci.pangea.pub/job/xenial_unstable_smb4k/134/
[16:06] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_smb4k build #44: FAILURE in 1 min 2 sec: https://kci.pangea.pub/job/xenial_stable_smb4k/44/
[16:10] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_smb4k build #175: FAILURE in 4 min 53 sec: https://kci.pangea.pub/job/artful_unstable_smb4k/175/
[16:11] -kubuntu-ci:#kubuntu-devel- Project artful_stable_smb4k build #184: FAILURE in 6 min 11 sec: https://kci.pangea.pub/job/artful_stable_smb4k/184/
[16:30] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_smb4k build #40: UNSTABLE in 25 min: https://kci.pangea.pub/job/bionic_stable_smb4k/40/
 https://www.virtualbox.org/wiki/Linux_Downloads
[16:31] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_smb4k build #72: UNSTABLE in 26 min: https://kci.pangea.pub/job/bionic_unstable_smb4k/72/
 virtualbox is dropping 32bit I think.
[16:32] <wxl> s'ok, there's always kvm
 @acheronuk, I wIll test once I am home from work as I don't have my NVidai laptop with me.
 @DarinMiller, thanks. I have no idea if it will help, but maybe.....
[16:51] <blaze> speaking about sddm
[16:51] <blaze> it suddenly started to ignore "Return" button
[16:52] <blaze> nompad "Enter" works, which my laptop obviously doesn't have
[16:52] <blaze> *numpad
 Yes, I noticed the return button default isse also.  I usually have auto login setup so personally I am not affected by these issues. But, it would good to understand them for others.
[16:55] <acheronuk> weird. since today?
[16:55] <blaze> no
[16:58] <blaze> since previous update more likely
[16:59] <acheronuk> last change was just to bring back a patch that we did have but went awol, so doubt it was that
[16:59] <acheronuk> qtvirtualkeyboard update?
[17:00] <blaze> hmm, maybe
[17:00] <acheronuk> maybe that is stealing the default input?
[17:03] <acheronuk> https://github.com/sddm/sddm/releases/tag/v0.17.0
[17:04] <acheronuk> "Set default input method to qtvirtualkeyboard."
[17:04] <acheronuk> https://github.com/sddm/sddm/commit/ef7e0812dab3d2e56b2ad388e6c45ca5c84391d7
[17:05] <AlexZion> the package manager discover will be the default one ?, it should be considered ready ?
[17:05] <blaze> no, input method should stay
[17:06] <blaze> the problem is somewhere else
[17:07] <acheronuk> AlexZion: we have discover and Muon. Discover a software centre. Muon a more conventional GUI package manger. the user can choose then which to use
[17:08] <acheronuk> blaze: in that case, nothing comes to mind
[17:08] <blaze> Qt update?
[17:09] <AlexZion> ok acheronuk, because about discover I like the idea but doesn't seem to me very "stable", but maybe I'm wrong
[17:12] <acheronuk> blaze: nearly a month since qt 5.9.4 update, and we only just notice?
[17:12] <acheronuk> could be, but seems odd
[17:13] <acheronuk> AlexZion: it's not as good as it could or should be. but not as bad as it was!
[17:14] <blaze> yep, weird
[17:14] <acheronuk> enter works fine in my test vm as well
[17:14] <AlexZion> I saw that improved a lot but I hope it will be much better in the future ;)
 Discover in 5.12 is much more stable than befpre
 5.13 will make people very happy, I think :)
[17:15] <acheronuk> devs are working hard on it to make it so
[17:17] <AlexZion> and we are all grateful for that and forthe great job done on this release
[17:23] <blaze> plasma-desktop update and sddm-theme-breeze are best candidates so far
[17:23] <blaze> but let me check some other theme first
[17:25] <acheronuk> blaze: https://cgit.kde.org/plasma-workspace.git/log/sddm-theme?h=Plasma/5.12
[17:31] <AlexZion> I send a report of a discover crash, and I saw just now that after the crash I was unable to open any application and was even impossible to restart the machine, the only option was to reset the machine
 @DarinMiller maybe you are getting? LP: #1756226
 there is a 'fix' for that in the unnaproved queue
[18:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #292: STILL FAILING in 5 min 44 sec: https://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/292/
[18:22] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kdeplasma-addons build #130: STILL FAILING in 7 min 45 sec: https://kci.pangea.pub/job/xenial_stable_kdeplasma-addons/130/
[18:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:43] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdeplasma-addons build #211: FIXED in 28 min: https://kci.pangea.pub/job/artful_stable_kdeplasma-addons/211/
[18:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:47] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdeplasma-addons build #118: FIXED in 32 min: https://kci.pangea.pub/job/bionic_unstable_kdeplasma-addons/118/
[20:25] -kubuntu-ci:#kubuntu-devel- Project artful_stable_spectacle build #158: STILL FAILING in 5 min 47 sec: https://kci.pangea.pub/job/artful_stable_spectacle/158/
[20:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_smb4k build #176: STILL FAILING in 5 min 49 sec: https://kci.pangea.pub/job/artful_unstable_smb4k/176/
[20:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktp-call-ui build #126: STILL FAILING in 5 min 59 sec: https://kci.pangea.pub/job/artful_unstable_ktp-call-ui/126/
[20:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kproperty build #88: STILL FAILING in 6 min 10 sec: https://kci.pangea.pub/job/artful_unstable_kproperty/88/
[20:26] -kubuntu-ci:#kubuntu-devel- Project artful_stable_smb4k build #185: STILL FAILING in 6 min 49 sec: https://kci.pangea.pub/job/artful_stable_smb4k/185/
[20:28] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_xdg-desktop-portal-kde build #193: STILL FAILING in 9 min 8 sec: https://kci.pangea.pub/job/artful_unstable_xdg-desktop-portal-kde/193/
[20:28] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdb build #104: STILL FAILING in 9 min 19 sec: https://kci.pangea.pub/job/artful_stable_kdb/104/
[20:28] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kproperty build #64: STILL FAILING in 9 min 24 sec: https://kci.pangea.pub/job/artful_stable_kproperty/64/
[20:29] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktp-call-ui build #97: STILL FAILING in 10 min: https://kci.pangea.pub/job/artful_stable_ktp-call-ui/97/
[20:30] -kubuntu-ci:#kubuntu-devel- Project artful_stable_okular build #160: STILL FAILING in 10 min: https://kci.pangea.pub/job/artful_stable_okular/160/
[20:30] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdevelop build #191: STILL FAILING in 10 min: https://kci.pangea.pub/job/artful_stable_kdevelop/191/
[20:30] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akonadi build #226: STILL FAILING in 10 min: https://kci.pangea.pub/job/artful_unstable_akonadi/226/
[20:30] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdb build #190: STILL FAILING in 11 min: https://kci.pangea.pub/job/artful_unstable_kdb/190/
[20:31] -kubuntu-ci:#kubuntu-devel- Project artful_stable_krita build #226: STILL FAILING in 11 min: https://kci.pangea.pub/job/artful_stable_krita/226/
[20:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #274: STILL FAILING in 12 min: https://kci.pangea.pub/job/artful_unstable_kstars/274/
[20:32] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdenlive build #173: STILL FAILING in 12 min: https://kci.pangea.pub/job/artful_unstable_kdenlive/173/
[20:32] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kexi build #157: STILL FAILING in 3 min 45 sec: https://kci.pangea.pub/job/artful_stable_kexi/157/
[20:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ruqola build #166: STILL FAILING in 13 min: https://kci.pangea.pub/job/artful_unstable_ruqola/166/
[20:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #240: STILL FAILING in 13 min: https://kci.pangea.pub/job/artful_unstable_krita/240/
[20:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kreport build #143: STILL FAILING in 7 min 38 sec: https://kci.pangea.pub/job/artful_unstable_kreport/143/
[20:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdepim-addons build #297: STILL FAILING in 4 min 45 sec: https://kci.pangea.pub/job/artful_unstable_kdepim-addons/297/
[20:36] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdenlive build #187: STILL FAILING in 16 min: https://kci.pangea.pub/job/artful_stable_kdenlive/187/
[20:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kexi build #207: STILL FAILING in 4 min 44 sec: https://kci.pangea.pub/job/artful_unstable_kexi/207/
[20:38] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kreport build #102: STILL FAILING in 5 min 36 sec: https://kci.pangea.pub/job/artful_stable_kreport/102/
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kgpg build #88: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_kgpg/88/
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_powerdevil build #161: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_powerdevil/161/
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kblog build #125: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_kblog/125/
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_knotes build #131: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_knotes/131/
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kmenuedit build #145: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_kmenuedit/145/
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akonadi-import-wizard build #117: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_akonadi-import-wizard/117/
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kmail-account-wizard build #87: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_kmail-account-wizard/87/
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akonadi-calendar build #137: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_akonadi-calendar/137/
[20:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kleopatra build #138: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_kleopatra/138/
[20:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_mbox-importer build #109: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_mbox-importer/109/
[20:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akregator build #168: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_akregator/168/
[20:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_grantlee-editor build #113: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_grantlee-editor/113/
[20:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktnef build #107: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_ktnef/107/
[20:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kalarmcal build #115: FIXED in 26 min: https://kci.pangea.pub/job/artful_stable_kalarmcal/115/
[20:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_gcompris build #156: STILL FAILING in 28 min: https://kci.pangea.pub/job/artful_unstable_gcompris/156/
[20:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_telepathy-qt build #31: STILL FAILING in 22 min: https://kci.pangea.pub/job/artful_unstable_telepathy-qt/31/
[20:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:58] -kubuntu-ci:#kubuntu-devel- Project artful_stable_libksieve build #129: FIXED in 38 min: https://kci.pangea.pub/job/artful_stable_libksieve/129/
 (Photo, 1024x264) https://irc-attachments.kde.org/t0Ppy47e/file_5685.jpg
[20:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:59] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-desktop build #241: FIXED in 39 min: https://kci.pangea.pub/job/artful_stable_plasma-desktop/241/
 @nggraham @acheronuk @Sick_Rimmit
 the beaver is very faint anf maybe taking up too much of it? we also have a better gear logo somewhere
 Well that is the gear that I found in SVG.
 I kind thought the beaver hiding.
 mixing with the other lines.
 @ahoneybun, we have a better svg
 Do you have a link?
 how about reversing the text and the beaver?
 the beaver kind of blends in with the other lines
 it looks like noise from a distance
[21:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:05] -kubuntu-ci:#kubuntu-devel- Project artful_stable_khotkeys build #118: FIXED in 19 min: https://kci.pangea.pub/job/artful_stable_khotkeys/118/
[21:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:05] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akonadiconsole build #157: FIXED in 19 min: https://kci.pangea.pub/job/artful_stable_akonadiconsole/157/
[21:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:05] -kubuntu-ci:#kubuntu-devel- Project artful_stable_eventviews build #152: FIXED in 19 min: https://kci.pangea.pub/job/artful_stable_eventviews/152/
 Updated it on the task.
 (Photo, 1024x264) https://irc-attachments.kde.org/gOwtNrsM/file_5687.jpg
[21:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:06] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akonadi-calendar-tools build #156: FIXED in 20 min: https://kci.pangea.pub/job/artful_stable_akonadi-calendar-tools/156/
 (Document) https://irc-attachments.kde.org/BB8Bkjrq/file_5688.svg
 now the background looks pale and sick :)
 it's unfortunate that the beaver color is one of the same colors used by the wallpaper
 @ahoneybun that is the logo that was fixed for us to have nicer edges
 it's the one I used before
 I can change that color.
 (Photo, 1024x264) https://irc-attachments.kde.org/HjwN6ZdH/file_5690.jpg
 (Photo, 1024x264) https://irc-attachments.kde.org/Rld6luOC/file_5692.jpg
 @nggraham
 That's certainly got more contrast, but what about all of those extraneous lines around the poor little guy's head? Are those really part of the official logo?
[21:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:14] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdepim-runtime build #147: FIXED in 28 min: https://kci.pangea.pub/job/artful_stable_kdepim-runtime/147/
 also now it seems unbalanced and too right-heavy
[21:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:14] -kubuntu-ci:#kubuntu-devel- Project artful_stable_mailcommon build #98: FIXED in 28 min: https://kci.pangea.pub/job/artful_stable_mailcommon/98/
 What if we put the text where the beaver is, and the beaver where the text is? The beaver might even fit better there due do its shape
 They are part of the official logo.
 that's uh, not the design decision I would have gone with
 and that's all I'll say on that subject 😊
[21:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:23] -kubuntu-ci:#kubuntu-devel- Project artful_stable_incidenceeditor build #163: FIXED in 17 min: https://kci.pangea.pub/job/artful_stable_incidenceeditor/163/
 (Photo, 1024x264) https://irc-attachments.kde.org/SxDX6J8H/file_5694.jpg
 That seems like a better basic design to me! I'd make the text a bit bigger to balance out the beaver
 also I'm not sure I like how the beaver is gray
 but he's on a brown background
 (Photo, 1024x264) https://irc-attachments.kde.org/D8cxHheN/file_5696.jpg
 larger text.
 @nggraham, camouflage
 I might make the word Kubuntu big enough that the text below it isn't wider. That way the whole text block will fit in a square which should be more visually appealing
 (that goes for whatever side the text winds up being on)
[21:30] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kmail build #161: STILL FAILING in 6 min 51 sec: https://kci.pangea.pub/job/artful_stable_kmail/161/
[21:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:30] -kubuntu-ci:#kubuntu-devel- Project artful_stable_pim-data-exporter build #122: FIXED in 15 min: https://kci.pangea.pub/job/artful_stable_pim-data-exporter/122/
[21:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:30] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kontact build #115: FIXED in 15 min: https://kci.pangea.pub/job/artful_stable_kontact/115/
[21:30] -kubuntu-ci:#kubuntu-devel- Project artful_stable_pim-sieve-editor build #159: FIXED in 15 min: https://kci.pangea.pub/job/artful_stable_pim-sieve-editor/159/
 if the beaver is going to be solid, then maybe whiter but with a hint of transparency?
[21:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:31] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kalarm build #128: FIXED in 16 min: https://kci.pangea.pub/job/artful_stable_kalarm/128/
 i know it's due to space, but chopping the end of his tail off is mean!
 (Photo, 1024x264) https://irc-attachments.kde.org/SwSG9gS6/file_5698.jpg
 @ahoneybun what font is that?
 (Photo, 1024x264) https://irc-attachments.kde.org/9JczF4JS/file_5696.jpg
 Ubuntu font.
 @ahoneybun, too faint?
 hmm, I don't like the pale background
 also the K in Kubuntu and the B in Bionic aren't vertically aligned
 if you make both pieces of text left-justified, that should fix that
 They are not any justified all moved by hand.
 ah
 line up or offset I would say
 I offset the artful one
 (Photo, 567x271) https://irc-attachments.kde.org/WgUyNefi/file_5700.jpg
 not suggesting that here
[21:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:38] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kaddressbook build #143: FIXED in 14 min: https://kci.pangea.pub/job/artful_stable_kaddressbook/143/
 that looks nice 👍🏼
 @nggraham, Yeah, the rest was not so hot
 (Photo, 1024x264) https://irc-attachments.kde.org/a0phgEB0/file_5702.jpg
 it's just tough to make everyone happy lol.
 yeah. well it doesn't have to be done tonight, so getting there
 (Photo, 1024x264) https://irc-attachments.kde.org/kouFdLmq/file_5704.jpg
 bit more of the beaver.
 "Bionic Beaver 18.04 LTS" should not be wider than the "Kubuntu". I agree with @nggraham on that one
[21:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_korganizer build #127: FIXED in 21 min: https://kci.pangea.pub/job/artful_stable_korganizer/127/
 BTW, using that brown bit, if going to upset @MichaelTun
 LOL
 I think it's perfect but anyone else can make something.
 we all probably think we can do better. as we all have different tastes
[21:51] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdepim-addons build #225: NOW UNSTABLE in 27 min: https://kci.pangea.pub/job/artful_stable_kdepim-addons/225/
 but this is a nice start. thanks @ahoneybun
 Yep.
 I try to help when I can.
[21:54] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akonadi build #226: STILL FAILING in 2 min 43 sec: https://kci.pangea.pub/job/artful_stable_akonadi/226/
 @acheronuk, I agree it shouldn't be larger than the Kubuntu thing
 @acheronuk, nah it's ok enough
[22:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:05] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kcalutils build #116: FIXED in 14 min: https://kci.pangea.pub/job/artful_stable_kcalutils/116/
[22:09] <valorie> I like the layout where the beaver faces the logo
[22:09] <valorie> rather than gazing away
[22:09] <valorie> and filling her in makes it less confusing
[22:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:13] -kubuntu-ci:#kubuntu-devel- Project artful_stable_libgravatar build #98: FIXED in 19 min: https://kci.pangea.pub/job/artful_stable_libgravatar/98/
[22:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:14] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdepim-apps-libs build #116: FIXED in 19 min: https://kci.pangea.pub/job/artful_stable_kdepim-apps-libs/116/
[22:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:14] -kubuntu-ci:#kubuntu-devel- Project artful_stable_mailimporter build #122: FIXED in 19 min: https://kci.pangea.pub/job/artful_stable_mailimporter/122/
 @acheronuk, btw I dont like the wallpaper because it doesnt fit the presentation of Kubuntu, that makes it feel off to me
[22:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:24] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kidentitymanagement build #93: FIXED in 18 min: https://kci.pangea.pub/job/artful_stable_kidentitymanagement/93/
 Post another one with that one on twitter and vote! lol
[22:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_calendarsupport build #141: FIXED in 21 min: https://kci.pangea.pub/job/artful_stable_calendarsupport/141/
[22:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_messagelib build #172: FIXED in 21 min: https://kci.pangea.pub/job/artful_stable_messagelib/172/
[23:11] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1075: SUCCESS in 11 min: https://kci.pangea.pub/job/mgmt_merger/1075/
[23:31] <valorie> wow
[23:31] <valorie> just tried to change from folderview to desktop and all of plasma crashed
[23:45] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_gcompris build #117: STILL FAILING in 33 min: https://kci.pangea.pub/job/bionic_unstable_gcompris/117/
[23:48] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdeplasma-addons build #119: FAILURE in 36 min: https://kci.pangea.pub/job/bionic_unstable_kdeplasma-addons/119/
[23:58] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_falkon build #37: STILL UNSTABLE in 45 min: https://kci.pangea.pub/job/bionic_stable_falkon/37/
[23:58] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_smb4k build #41: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/bionic_stable_smb4k/41/
[23:59] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #98: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/bionic_stable_cantor/98/


[02:44] <lotuspsychje> good morning to all
[02:44] <lotuspsychje> hows the artful night been?
[02:47] <Bashing-om> lotuspsychje: \o artful, so far smooth - no real new issues identified :)
[02:48] <lotuspsychje> hey Bashing-om nice2hear
[02:50] <Bashing-om> lotuspsychje: Been on pins, awaiting the hammer to fall . No impact to this time :)
[02:52] <lotuspsychje> great
[02:52] <lotuspsychje> my artful performs best on xorg
[02:55] <Bashing-om> lotuspsychje: Seen a few incidences where xorg reversion was recommended :(
[02:56] <lotuspsychje> ok tnx
[03:18] <lotuspsychje> welcome bordy
[03:18] <lotuspsychje> oerheks: can you paste that link from dax again here
[03:18] <lotuspsychje> from yesterday
[03:18] <bordy> Evenin folks
[03:19] <oerheks> https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes/
[03:19] <oerheks> err https://didrocks.fr/ ?
[03:19] <lotuspsychje> didrocks yeah
[03:19] <lotuspsychje> take a look at that Bashing-om
[03:20] <lotuspsychje> the upgrade to artfull page
[03:21] <Bashing-om> lotuspsychje: look'n .
[03:22] <oerheks> and from the releasenotes, to https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Known_issues.2C_frequent_complaints.2C_fundamental_changes
[03:22] <oerheks> gives valuable information too
[03:22] <oerheks> s Ctrl+Alt+Shift+R keyboard shortcut to start video recording of the whole desktop , and lands in ~/Videos
[03:24] <lotuspsychje> cool
[03:51] <Bashing-om> lotuspsychje: oerheks : I say again ^^ We have a lot to learn :D
[03:52] <lotuspsychje> yeah lil complicated on wayland..
[04:02] <Bashing-om> lotuspsychje: Developers are throwing a lot of changes at us - fast ! systemd, netwworking, wayland ( GUI graphics ), logging ......... ouch !
[04:08] <lotuspsychje> yeah
[04:54] <Guy1524> hey guys, theoretically, would it be possible to upgrade an Ubuntu 4.10 installation to 17.10, and if so, how would it differ from a fresh install
[04:54] <lotuspsychje> !eolupgrade
[04:55] <lotuspsychje> Guy1524: fresh install is very recommended
[04:55] <Guy1524> I don't actually have 4.10 installed, I am just curious, because it would be interesting
[04:56] <lotuspsychje> Guy1524: why is an eol version interesting?
[04:57] <Guy1524> just to see how robust the upgrade system is in Ubuntu
[04:58] <lotuspsychje> Guy1524: check the eolupgrade link
[04:58] <Guy1524> k
[06:01] <lordievader> Good morning
[06:11] <lotuspsychje> hey lordievader
[06:12] <lordievader> Hey lotuspsychje
[06:12] <lordievader> How are you today?
[06:12] <lotuspsychje> great here
[06:13] <lotuspsychje> almost having breakfast
[06:15] <lotuspsychje> http://www.omgubuntu.co.uk/
[06:15] <lotuspsychje> its artful news all over
[06:18] <lordievader> I'm sure it is.
[06:34] <Bashing-om> lotuspsychje: IRT Cosec__  ' sudo find / -name "NVIDIA-Linux-*" ' there is a uninstall script .
[06:35] <lotuspsychje> cool
[06:45] <lotuspsychje> bbl
[12:49] <BluesKaj> Hi folks
[13:12] <oerheks> Happy 13th Birthday, Ubuntu!
[13:13] <oerheks> my lucky number
[13:14] <pauljw> hi BluesKaj, everyone.
[13:15] <oerheks> get 10% off XPS 13 developer edition w/the code "SAVE10XPS" til 7amCT 10/26
[13:16] <pauljw> that's nice, but they're still too expensive for me.
[13:31] <BluesKaj> Hi pauljw
[13:31] <pauljw> :)
[13:34] <BluesKaj> already have a decent laptop, and 13" screen for that kind of money is too expensive, despite the portability factor
[13:34] <BluesKaj> and you're still paying for useless W10 on top
[13:35]  * BluesKaj is in a crirtical mood this morning ...pissed off at a few things
[13:38] <BluesKaj> BBl
[13:43] <pauljw> :(
[15:48] <daftykins> i love my XPS 13 (:
[15:53] <nicomachus> too small for me.
[15:53] <nicomachus> screens should be 15+
[15:53] <nicomachus> no smaller
[15:54] <daftykins> i prefer portability above all else
[15:54] <daftykins> well, battery life is the true priority
[16:16] <nicomachus> 15 inch screen is portable.
[16:17] <daftykins> not to me as a cyclist
[17:19] <oerheks> 4 inch and full hd  .. wait
[17:57] <nicomachus> This guy basalt is having some issues with the ath10k driver if anyone wants to dive into kernel stuff.
[18:10] <daftykins> ;D
[18:10] <daftykins> 'get a new one'
[18:11] <daftykins> (kernel)
[18:15] <TJ-> We've got a major issue for Nvidia users coming up as soon as Ubuntu adopts v4.14 kernel. A key kernel symbol in the memory-manager has been made GPL-only, and it breaks the nvidia (and other out-of-tree non-GPL module) builds entirely
[18:17] <nicomachus> oh great
[18:18] <TJ-> In this current v4.14 development round AMD introduced Secure Memory Encryption facilities and enabled it by default to support their new CPU facilities. Because the memory-management functions are core to almost all drivers it's caused a new GPL-only symbol, sme_me_mask, to be imported into almost all modules. As a result, nvidia drivers fail to modpost when being linked
[18:19] <TJ-> Got a response from the kernel's MM sub-system maintainer today after reporting this last weekend with the RC2 build. They won't change it (I don't blame them). However, unless the SME functions are disabled entirely - which means AMD devices with SME cannot make use of it - the generic Ubuntu kernels will fail with proprietary drivers
[18:20] <nicomachus> So is this just an Ubuntu issue or going to be linux-wide?
[18:21] <TJ-> Linux wide if kernels are built with SME enabled to support AMD devices. For people/distros that build CPU-specific kernels it won't be an issue, but for distros like Debian and Ubuntu RedHat etc., it'll be an issue because we build a single kernel that is capable of supporting all devices
[18:22] <TJ-> The CONFIG enables it by default in mainline too, so anyone trying mainline kernels (as I do and discovered it) will hit this
[20:29] <pauljw> Hi everyone
[20:30] <nicomachus> o/
[20:30] <daftykins> wb o/
[20:31] <Bashing-om> pauljw: \o
[20:33] <pauljw> :)
[20:34] <nicomachus> !recs
[22:38] <nacc> what in the actual f
[22:38] <nacc> sorry for the language
[22:39] <nacc> but serious, connorkmc must be trolling right?
[22:40] <pauljw> seems like it to me, nacc
[22:40]  * nacc should know better, but I get so much madder at people wasting my time on a Friday
[22:41] <nacc> on a happier note, git-ubuntu 0.4 released, and a test snap branch created that has the ability to take an upstream fix, cherry-pick it and make a quilt patch out of it for testing (incl. building a .deb)
[22:41] <pauljw> :)
[22:42] <pauljw> that's pretty nice
[22:43] <nacc> i'm sure it will break for some cases, but it should help a lot of people learn to contribute
[22:43] <nacc> and eventually get us to a git-only workflow
[22:43] <nacc> hopefully we'll start importing all packages in the next month or so


[00:18] -queuebot:#ubuntu-release- New: accepted camv-rnd [arm64] (lunar-proposed) [1.1.0-2]
[00:18] -queuebot:#ubuntu-release- New: accepted camv-rnd [s390x] (lunar-proposed) [1.1.0-2]
[00:18] -queuebot:#ubuntu-release- New: accepted camv-rnd [armhf] (lunar-proposed) [1.1.0-2]
[00:19] -queuebot:#ubuntu-release- New: accepted camv-rnd [ppc64el] (lunar-proposed) [1.1.0-2]
[00:19] -queuebot:#ubuntu-release- New: accepted libfile-kdbx-perl [amd64] (lunar-proposed) [0.906-1]
[00:19] -queuebot:#ubuntu-release- New: accepted libstring-tagged-terminal-perl [amd64] (lunar-proposed) [0.05-1]
[00:19] -queuebot:#ubuntu-release- New: accepted libcommandable-perl [amd64] (lunar-proposed) [0.08-1]
[00:19] -queuebot:#ubuntu-release- New: accepted sch-rnd [amd64] (lunar-proposed) [0.9.3-1]
[00:19] -queuebot:#ubuntu-release- New: accepted libpass-otp-perl [amd64] (lunar-proposed) [1.5-1]
[00:19] -queuebot:#ubuntu-release- New: accepted camv-rnd [amd64] (lunar-proposed) [1.1.0-2]
[00:19] -queuebot:#ubuntu-release- New: accepted golang-github-twpayne-go-shell [amd64] (lunar-proposed) [0.3.1-1]
[00:19] -queuebot:#ubuntu-release- New: accepted python-refurb [amd64] (lunar-proposed) [1.7.0-1]
[00:19] -queuebot:#ubuntu-release- New binary: zycore-c [ppc64el] (lunar-proposed/universe) [1.4.1-1] (no packageset)
[00:19] -queuebot:#ubuntu-release- New: accepted golang-github-twpayne-go-pinentry [amd64] (lunar-proposed) [0.2.0-1]
[00:19] -queuebot:#ubuntu-release- New: accepted zycore-c [amd64] (lunar-proposed) [1.4.1-1]
[00:19] -queuebot:#ubuntu-release- New: accepted golang-github-twpayne-go-vfs [amd64] (lunar-proposed) [4.1.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted golang-github-artyom-mtab [amd64] (lunar-proposed) [1.0.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted rust-fix-getters-rules [amd64] (lunar-proposed) [0.3.2-1]
[00:20] -queuebot:#ubuntu-release- New: accepted rust-trust-dns-resolver [arm64] (lunar-proposed) [0.21.2-1]
[00:20] -queuebot:#ubuntu-release- New binary: rust-fix-getters-rules [ppc64el] (lunar-proposed/universe) [0.3.2-1] (no packageset)
[00:20] -queuebot:#ubuntu-release- New: accepted golang-github-muesli-combinator [amd64] (lunar-proposed) [0.3.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted rust-trust-dns-resolver [armhf] (lunar-proposed) [0.21.2-1]
[00:20] -queuebot:#ubuntu-release- New: accepted rust-shrinkwraprs [amd64] (lunar-proposed) [0.3.0-1]
[00:20] -queuebot:#ubuntu-release- New binary: rust-shrinkwraprs [ppc64el] (lunar-proposed/universe) [0.3.0-1] (no packageset)
[00:21] -queuebot:#ubuntu-release- New: accepted rust-cursive-core [arm64] (lunar-proposed) [0.3.5-1]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-cursive-core [riscv64] (lunar-proposed) [0.3.5-1]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-winit [riscv64] (lunar-proposed) [0.27.5-2]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-cursive-core [armhf] (lunar-proposed) [0.3.5-1]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-winit [arm64] (lunar-proposed) [0.27.5-2]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-cursive-core [amd64] (lunar-proposed) [0.3.5-1]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-cursive-core [s390x] (lunar-proposed) [0.3.5-1]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-winit [amd64] (lunar-proposed) [0.27.5-2]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-winit [ppc64el] (lunar-proposed) [0.27.5-2]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-cursive-core [ppc64el] (lunar-proposed) [0.3.5-1]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-winit [armhf] (lunar-proposed) [0.27.5-2]
[00:21] -queuebot:#ubuntu-release- New: accepted rust-trust-dns-resolver [amd64] (lunar-proposed) [0.21.2-1]
[00:21] -queuebot:#ubuntu-release- New binary: zycore-c [riscv64] (lunar-proposed/universe) [1.4.1-1] (no packageset)
[00:22] -queuebot:#ubuntu-release- New binary: sch-rnd [ppc64el] (lunar-proposed/universe) [0.9.3-1] (no packageset)
[00:23] -queuebot:#ubuntu-release- New binary: camv-rnd [riscv64] (lunar-proposed/universe) [1.1.0-2] (no packageset)
[00:23] -queuebot:#ubuntu-release- New binary: rust-shrinkwraprs [riscv64] (lunar-proposed/universe) [0.3.0-1] (no packageset)
[00:46] -queuebot:#ubuntu-release- New binary: libdevel-mat-perl [s390x] (lunar-proposed/universe) [0.49-1] (no packageset)
[00:48] -queuebot:#ubuntu-release- New: accepted camv-rnd [riscv64] (lunar-proposed) [1.1.0-2]
[00:48] -queuebot:#ubuntu-release- New: accepted rust-shrinkwraprs [riscv64] (lunar-proposed) [0.3.0-1]
[00:48] -queuebot:#ubuntu-release- New: accepted libdevel-mat-perl [s390x] (lunar-proposed) [0.49-1]
[00:48] -queuebot:#ubuntu-release- New: accepted sch-rnd [ppc64el] (lunar-proposed) [0.9.3-1]
[00:48] -queuebot:#ubuntu-release- New: accepted zycore-c [riscv64] (lunar-proposed) [1.4.1-1]
[00:49] -queuebot:#ubuntu-release- New: accepted rust-fix-getters-rules [ppc64el] (lunar-proposed) [0.3.2-1]
[00:49] -queuebot:#ubuntu-release- New: accepted zycore-c [ppc64el] (lunar-proposed) [1.4.1-1]
[00:49] -queuebot:#ubuntu-release- New: accepted rust-shrinkwraprs [ppc64el] (lunar-proposed) [0.3.0-1]
[01:08] -queuebot:#ubuntu-release- Unapproved: elfutils (jammy-backports/main) [0.187-1~bpo22.04.1 => 0.188-1~bpo22.04.1] (core, i386-whitelist)
[01:18] -queuebot:#ubuntu-release- Unapproved: elfutils (jammy-backports/main) [0.187-1~bpo22.04.1 => 0.188-1~bpo22.04.1] (core, i386-whitelist)
[04:24] -queuebot:#ubuntu-release- New binary: golang-github-twpayne-go-xdg [amd64] (lunar-proposed/universe) [6.0.0-1] (no packageset)
[07:45] -queuebot:#ubuntu-release- Unapproved: yt-dlp (jammy-backports/universe) [2022.10.04-1~bpo22.04.1 => 2022.11.11-1~bpo22.04.1] (no packageset)
[08:27] -queuebot:#ubuntu-release- Unapproved: xlnx-firmware (kinetic-proposed/multiverse) [2022.1-1-0ubuntu1 => 2022.1-2-0ubuntu1~22.10.1] (no packageset)
[08:29] -queuebot:#ubuntu-release- Unapproved: xlnx-firmware (jammy-proposed/multiverse) [2022.1-1-0ubuntu1~22.04.1 => 2022.1-2-0ubuntu1~22.04.1] (no packageset)
[08:43] -queuebot:#ubuntu-release- Unapproved: accepted xlnx-firmware [source] (kinetic-proposed) [2022.1-2-0ubuntu1~22.10.1]
[08:44] -queuebot:#ubuntu-release- Unapproved: accepted xlnx-firmware [source] (jammy-proposed) [2022.1-2-0ubuntu1~22.04.1]
[08:44] <LocutusOfBorg> hello Ubuntu-SRU, there is a bug LP: #1986665 almost one month old, not yet released...
[08:44] <LocutusOfBorg> tjaalton, ^^
[08:44] -ubottu:#ubuntu-release- Launchpad bug 1986665 in cmake (Ubuntu Focal) "[SRU] CMake imported targets GTest::gmock and GTest::gmock_main are not available" [Undecided, Fix Committed] https://launchpad.net/bugs/1986665
[08:54] <tjaalton> LocutusOfBorg: ack, released
[09:03] <LocutusOfBorg> ta!
[09:04] -queuebot:#ubuntu-release- New binary: rust-cursive [amd64] (lunar-proposed/universe) [0.20.0-1] (no packageset)
[09:05] -queuebot:#ubuntu-release- New binary: rust-glutin [amd64] (lunar-proposed/universe) [0.29.1-2] (no packageset)
[09:08] -queuebot:#ubuntu-release- New binary: rust-cursive [arm64] (lunar-proposed/universe) [0.20.0-1] (no packageset)
[09:08] -queuebot:#ubuntu-release- New binary: rust-cursive [ppc64el] (lunar-proposed/universe) [0.20.0-1] (no packageset)
[09:08] -queuebot:#ubuntu-release- New binary: rust-glutin [ppc64el] (lunar-proposed/universe) [0.29.1-2] (no packageset)
[09:09] -queuebot:#ubuntu-release- New binary: rust-cursive [armhf] (lunar-proposed/universe) [0.20.0-1] (no packageset)
[09:09] -queuebot:#ubuntu-release- New binary: rust-glutin [armhf] (lunar-proposed/universe) [0.29.1-2] (no packageset)
[09:09] -queuebot:#ubuntu-release- New binary: rust-glutin [arm64] (lunar-proposed/universe) [0.29.1-2] (no packageset)
[09:14] -queuebot:#ubuntu-release- New binary: rust-cursive [s390x] (lunar-proposed/universe) [0.20.0-1] (no packageset)
[09:21] -queuebot:#ubuntu-release- New binary: rust-cursive [riscv64] (lunar-proposed/universe) [0.20.0-1] (no packageset)
[09:26] -queuebot:#ubuntu-release- New binary: rust-glutin [riscv64] (lunar-proposed/universe) [0.29.1-2] (no packageset)
[10:01] -queuebot:#ubuntu-release- Unapproved: xorg-server (jammy-proposed/main) [2:21.1.3-2ubuntu2.2 => 2:21.1.3-2ubuntu2.3] (desktop-core, i386-whitelist, xorg)
[10:01] -queuebot:#ubuntu-release- Unapproved: xorg-server (kinetic-proposed/main) [2:21.1.4-2ubuntu1 => 2:21.1.4-2ubuntu1.1] (desktop-core, i386-whitelist, xorg)
[11:09] <utkarsh2102> sil2100: hellu! \o
[11:09] <utkarsh2102> is there any particular time you do your SRU duty at?
[11:09] <utkarsh2102> I am not sure when to reach out but could you please TAL at google-osconfig-agent, please?
[11:32] <sil2100> utkarsh2102: hey! I can take a look after my next meeting o/
[11:33] <utkarsh2102> sil2100: sounds great, thank you! \o/
[11:33] <utkarsh2102> sil2100: also with your AA hat on, can you take a look at gcp-apt-transport-ar upload to Lunar? It's a NEW package, hehe. :)
[11:34] <utkarsh2102> if you have time^
[11:40] <sil2100> hm hm, I'll try, but I might not have enough cycles for that one today!
[12:28] <sil2100> hmm, LP is very slow, so might take a bit longer
[12:58] <ahasenack> excuses is full of lines like "rust-app-dirs2/arm64 (2.5.2-1 to 2.5.2-1)", showing the same version before and after, is this expected/correct?
[13:09] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (jammy-proposed) [2.765.12]
[13:17] -queuebot:#ubuntu-release- Unapproved: hart-software-services (kinetic-proposed/universe) [2022.03-0ubuntu1 => 2022.10-0ubuntu1~22.10] (no packageset)
[13:20] -queuebot:#ubuntu-release- New source: hart-software-services (jammy-proposed/primary) [2022.10-0ubuntu1~22.04]
[13:33] <sil2100> utkarsh2102: hey! Left a comment on https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1996735 with a question re: the upload
[13:33] -ubottu:#ubuntu-release- Launchpad bug 1996735 in google-osconfig-agent (Ubuntu Kinetic) "Please update to upstream release 20220824.00" [Undecided, Incomplete]
[14:11] <tsimonq2> sil2100: Hey! Any chance I could ask you to kick off a set of ISO rebuilds? Builds won't show up in the tracker unless there's a successful one and the 23.04 Firefox snap branch was just opened :)
[14:11] <tsimonq2> (Feel free to use Lubuntu as a test subject before rebuilding the Lunar universe ;) )
[14:13] <sil2100> Did we also get the snapd-desktop-integration channel created?
[14:14] <tsimonq2> Very good question, let me echo that over :)
[14:15] <tsimonq2> Ah, Graham beat me to it. Cool :)
[14:24] <RikMills> flavours that don't seed snap:snapd-desktop-integration might still be ok to kick off builds right now?
[14:25] <RikMills> not in a huge hurry for kubuntu though. too much stuck in proposed waiting on tests
[14:27] <tsimonq2> Brief ditto for Lubuntu, less stuck but autopkgtests are still the blocker :/
[15:25] <utkarsh2102> sil2100: super, thanks for the comment. I'll reply back now. I also noticed that vorlon also left a comment and I missed it. Sorry and looking now..
[15:40] <seb128> sil2100, hey, any chance you could review webp-pixbuf-loader in J/NEW queue at some point (need a SRU reviewer who also is archive admin, also seems like most SRU reviewer ignore NEW during their shifts?)
[16:07] -queuebot:#ubuntu-release- Unapproved: libfprint (focal-proposed/main) [1:1.90.2+tod1-0ubuntu1~20.04.9 => 1:1.90.2+tod1-0ubuntu1~20.04.10] (desktop-core, ubuntu-desktop)
[16:10] <ahasenack> any idea why the same package is in multiple rows at the top, one for each arch, in the excuses page? And it's the same version in the "from" and "to" fields: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[16:14] <tsimonq2> That makes me really curious... perhaps just Britney being overly verbose?
[16:14]  * tsimonq2 checks the Britney logs - I'll report back if I find anything that may point to this
[16:16] -queuebot:#ubuntu-release- New binary: lerc [armhf] (lunar-proposed/main) [4.0.0+ds-2ubuntu1] (no packageset)
[16:17] <tsimonq2> `I: [2022-11-21T09:03:45+0000] - Checking for new results for rust-app-dirs2/armhf for trigger migration-reference/0`
[16:18] <kanashiro[m]> ubuntu-archive: could we follow Debian and remove src:puppet and its binaries from Lunar and import src:puppet-agent from Debian? src:puppet was removed from testing and unstable. The puppet-master and puppet-master-passenger binaries will not be provided anymore
[16:20] <tsimonq2> tsimonq2: To me, that is indicative of a Britney bug. Britney caches quite a bit of autopkgtest test queries, if I had to put my finger on it, packages that migrate are not being cleared from the cache completely, leaving `migration-reference/0` there. I would have to review the criteria Britney uses to clear such cache on migration.
[16:22] <RikMills> ahasenack: new sources that migrated when only some arches had binaries built. now in the last day or so the remaining arches binaries have built and are 'migrating'
[16:22] <tsimonq2> kanashiro: Not speaking for the Archive Team, but in my past experience it has been helpful to file a bug against the relevant packages with your request, and subscribe ~ubuntu-archive. The bug report then can be mentioned in the removal reason.
[16:23] <RikMills> AFAIK
[16:23]  * tsimonq2 checks the Lunar DONE queue to confirm
[16:23] <kanashiro[m]> Simon Quigley: yeah, I think I'll do that, thanks
[16:28] <tsimonq2> RikMills: I think you're right. Source migrated at 1 AM (local time) on the 16th, DONE queue says amd64 was the only arch available (on rust-app-dirs2) on the 6th, looks like the remaining binaries migrated. Makes sense because Britney only considers "what to migrate" in the context of the release pocket.
[16:34] <RikMills> indeed
[16:37] <ahasenack> it feels like the opening of this devel cycle is causing more test queue buildup than in previous cycles
[16:37] <ahasenack> last update of the excuses page was more than 12h ago
[16:38] <kanashiro[m]> ubuntu-archive: filed this bug regarding the puppet situation: LP #1997260
[16:38] -ubottu:#ubuntu-release- Launchpad bug 1997260 in puppet (Ubuntu) "[RM] puppet was removed from Debian testing and unstable" [Undecided, New] https://launchpad.net/bugs/1997260
[16:38] <ahasenack> it's like this xkcd, but for the excuses page :) https://xkcd.com/303/
[16:38] <RikMills> ahasenack: the last run crashed 8/10 of the way through due some network issue, so it has to start afresh
[16:38] <ahasenack> s/compiling/migrating/
[16:39] -queuebot:#ubuntu-release- New binary: lerc [riscv64] (lunar-proposed/main) [4.0.0+ds-2ubuntu1] (no packageset)
[16:39] <RikMills> runs have been taking about 6 hrs when they don't crash ;)
[16:40] <tsimonq2> ahasenack: To add onto Rik's point, the vast majority of the time is spent querying the autopkgtest SQLite database for results... so many results that this alone takes a few hours. I've been incredibly tempted to get a local stack set up to try some efficiency measures, but EDAYJOB :)
[16:41] <ahasenack> are you saying concurrency on the sqlite db is a big issue?
[16:43] <tsimonq2> What I will say is that there's something afoot that needs looking into ;) my speculation is that it's due to usage of SQLite. Perhaps doing a more general query and storing that in memory instead of querying the SQLite database for every package individually would help.
[16:43] <tsimonq2> It's hard to say for sure, given that I don't have a local copy of this running
[16:45] <tsimonq2> https://people.canonical.com/~ubuntu-archive/proposed-migration/log/lunar/2022-11-20/17:56:13.log is a great example of this - 2022-11-20T18:07:06+0000 is the starting point for test queries, 2022-11-20T22:35:01+0000 is when it ends
[16:50] <RikMills> tsimonq2: I am quite the approach of fetching and caching the results in one go rather than individual network queries has been floated in here before
[16:50] <RikMills> *quite sure
[16:51] <tsimonq2> If anyone is working on it already, please ping me. Otherwise, this has bothered me enough that I'm planning on looking into it myself.
[16:51] <tsimonq2> RikMills: If you have a link to the discussion on that, I would appreciate it. (Maybe there's something I'm missing here.)
[16:52] <RikMills> tsimonq2: possibly sometime last cycle is the best I can say right now
[16:52] <tsimonq2> RikMills: No worries, thanks regardless :)
[16:52] <RikMills> not even quite sure who it was
[16:55] <tsimonq2> Time to get a local copy working >:P
[16:59] <ahasenack> maybe new uploads should be stopped while the queue settles down
[17:13] <tsimonq2> While that is technically possible, I'm unsure that the Release Team would be willing to accept the additional burden introduced by doing so. In my personal opinion, it would be more effective to put engineering work towards resolving the scalability issue, since I doubt this will be the last time something like this occurs
[17:28] -queuebot:#ubuntu-release- New binary: alkimia [amd64] (lunar-proposed/universe) [8.1.1-2] (kubuntu)
[17:32] -queuebot:#ubuntu-release- New binary: alkimia [armhf] (lunar-proposed/universe) [8.1.1-2] (kubuntu)
[17:32] -queuebot:#ubuntu-release- New binary: alkimia [ppc64el] (lunar-proposed/universe) [8.1.1-2] (kubuntu)
[17:34] -queuebot:#ubuntu-release- New binary: alkimia [arm64] (lunar-proposed/universe) [8.1.1-2] (kubuntu)
[17:39] <sil2100> seb128: hey! Looking!
[17:43] -queuebot:#ubuntu-release- New: accepted webp-pixbuf-loader [source] (jammy-proposed) [0.0.5-5~22.04.1]
[17:47] -queuebot:#ubuntu-release- New binary: webp-pixbuf-loader [amd64] (jammy-proposed/none) [0.0.5-5~22.04.1] (no packageset)
[17:54] -queuebot:#ubuntu-release- New binary: webp-pixbuf-loader [ppc64el] (jammy-proposed/none) [0.0.5-5~22.04.1] (no packageset)
[17:57] -queuebot:#ubuntu-release- New binary: webp-pixbuf-loader [arm64] (jammy-proposed/none) [0.0.5-5~22.04.1] (no packageset)
[18:05] -queuebot:#ubuntu-release- New binary: alkimia [s390x] (lunar-proposed/universe) [8.1.1-2] (kubuntu)
[18:08] -queuebot:#ubuntu-release- New binary: webp-pixbuf-loader [armhf] (jammy-proposed/universe) [0.0.5-5~22.04.1] (no packageset)
[18:08] -queuebot:#ubuntu-release- New binary: webp-pixbuf-loader [riscv64] (jammy-proposed/universe) [0.0.5-5~22.04.1] (no packageset)
[18:14] -queuebot:#ubuntu-release- New binary: alkimia [riscv64] (lunar-proposed/universe) [8.1.1-2] (kubuntu)
[18:29] -queuebot:#ubuntu-release- New binary: webp-pixbuf-loader [s390x] (jammy-proposed/universe) [0.0.5-5~22.04.1] (no packageset)
[18:30] -queuebot:#ubuntu-release- New: accepted alkimia [riscv64] (lunar-proposed) [8.1.1-2]
[18:30] -queuebot:#ubuntu-release- New: accepted alkimia [s390x] (lunar-proposed) [8.1.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted alkimia [amd64] (lunar-proposed) [8.1.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted alkimia [armhf] (lunar-proposed) [8.1.1-2]
[18:31] <vorlon> ahasenack: that's how britney represents binary packages that have lagged behind the source. Generally, this is a new source package so the fact that some binaries weren't built yet on some architectures is not a blocker for promotion
[18:31] -queuebot:#ubuntu-release- New: accepted rust-cursive [armhf] (lunar-proposed) [0.20.0-1]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-cursive [riscv64] (lunar-proposed) [0.20.0-1]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-glutin [arm64] (lunar-proposed) [0.29.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-glutin [ppc64el] (lunar-proposed) [0.29.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted alkimia [arm64] (lunar-proposed) [8.1.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-cursive [ppc64el] (lunar-proposed) [0.20.0-1]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-glutin [armhf] (lunar-proposed) [0.29.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted alkimia [ppc64el] (lunar-proposed) [8.1.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-glutin [riscv64] (lunar-proposed) [0.29.1-2]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-cursive [s390x] (lunar-proposed) [0.20.0-1]
[18:31] <vorlon> kanashiro[m]: removing puppet requires removing its reverse-dependencies, which Debian hasn't done yet.  So there's a huge pile of revdeps to work through before we remove it
[18:31] -queuebot:#ubuntu-release- New: accepted golang-github-twpayne-go-xdg [amd64] (lunar-proposed) [6.0.0-1]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-cursive [arm64] (lunar-proposed) [0.20.0-1]
[18:31] -queuebot:#ubuntu-release- New: accepted rust-cursive [amd64] (lunar-proposed) [0.20.0-1]
[18:32] -queuebot:#ubuntu-release- New: accepted rust-glutin [amd64] (lunar-proposed) [0.29.1-2]
[18:32] <vorlon> tsimonq2, RikMills: the whole reason we're querying all these results is because we don't yet have results.  You can't be caching a negative result.
[18:33] <vorlon> britney is going to be slow because it's waiting for 38,000 test results and it needs to check each one whether the results are in.  Use of the sqlite database instead of doing a web api call for each one *is* the optimization.
[18:50] <tsimonq2> vorlon: Thanks for the input :)
[19:03] <kanashiro[m]> vorlon: but those deps rely on the puppet binary which will be now provided by src:puppet-agent. I belive that's the reason they did not do any of that in Debian.
[19:09] <kanashiro[m]> what we cannot replace with src:puppet-agent is what depends on puppet-master{-passenger}. This is a single dep with no revdep which was included in the RM request
[19:44] <Eickmeyer> Is anybody around that might be able to retry today's Ubuntu Studio Lunar daily? The failure should be fixed.
[19:48] <sil2100> Since re-running all images requires a lot of manual runs, I was thinking of just waiting for tomorrow's dailies
[19:49] <Eickmeyer> sil2100: Sure, sounds like a plan if there's a lot of requests and if my request isn't a one-off.
[19:50] <Eickmeyer> In other words, I'm willing to wait. :)
[20:03] -queuebot:#ubuntu-release- Unapproved: libfprint (jammy-proposed/main) [1:1.94.3+tod1-0ubuntu2~22.04.02 => 1:1.94.3+tod1-0ubuntu2~22.04.03] (ubuntu-desktop)
[20:11] <vorlon> kanashiro[m]: ok why is puppet-agent not synced then?
[20:12] <vorlon> kanashiro[m]: you should do that first before asking for removals that will render a huge number of packages uninstallable
[20:15] <kanashiro[m]> vorlon: I am not sure how to proceed with a sync of a package that provides a binary package with the same name of another binary package provided by a different source package (already in the archive), should I just sync it manually? Any advice is welcome
[20:28] <LocutusOfBorg>  libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed
[20:28] <LocutusOfBorg> hello, is anybody working on this?
[20:30] <LocutusOfBorg> kanashiro[m], syncpackage -f?
[20:32] <kanashiro[m]> LocutusOfBorg: -f means "Force sync over the top of Ubuntu changes" but I am not sure if this covers binaries with same names, src:puppet-agent is actually a new package so in theory no delta
[20:32] <LocutusOfBorg> yes it does
[20:33] <LocutusOfBorg> the reason for auto-sync to not doing it, because it will override modified binaries
[20:33] <kanashiro[m]> cool, so I'll do it then, thanks :)
[20:33] <LocutusOfBorg> if you do it manually, thats ok as long as the modifications inside ubuntu delta are droppable
[20:34] <kanashiro[m]> yes, they are, thanks for the explanation
[20:34] <LocutusOfBorg> vorlon, speaking w.r.t. modified binaries... syncpackage -f pkgconf? WDYT?
[20:37] -queuebot:#ubuntu-release- New sync: puppet-agent (lunar-proposed/primary) [7.20.0-1]
[20:52] <jbicha> LocutusOfBorg: what about the diff from pkg-config?
[21:28] <vorlon> kanashiro[m]: yes, manual sync is warranted and needed here
[21:34] <jbicha> LocutusOfBorg: could you open a bug for the at-spi2-core issue with more details?
[21:37] <kanashiro[m]> vorlon: I did that, once it is migrated I'll ping you to revisit the removal request. Thanks for taking a look
[22:33] -queuebot:#ubuntu-release- New binary: openldap [amd64] (lunar-proposed/main) [2.6.3+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[22:33] -queuebot:#ubuntu-release- New binary: openldap [i386] (lunar-proposed/main) [2.6.3+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[22:36] -queuebot:#ubuntu-release- New binary: openldap [arm64] (lunar-proposed/main) [2.6.3+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[22:36] -queuebot:#ubuntu-release- New binary: openldap [s390x] (lunar-proposed/main) [2.6.3+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[22:37] -queuebot:#ubuntu-release- New binary: openldap [ppc64el] (lunar-proposed/main) [2.6.3+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[22:51] -queuebot:#ubuntu-release- New binary: openldap [armhf] (lunar-proposed/main) [2.6.3+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[23:07] -queuebot:#ubuntu-release- New binary: openldap [riscv64] (lunar-proposed/main) [2.6.3+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[23:30] -queuebot:#ubuntu-release- New binary: golang-github-keybase-go-ps [amd64] (lunar-proposed/universe) [0.0~git20190827.91aafc9-1] (no packageset)


[16:27] <Laira-TR> hello, its possible to use "Ubuntu One" from a command line (without graphical user interface)?
[20:09] <mongy> so, I still seem to have this file publishing bug, where is doesnt remember its published later..
[20:10] <mongy> the url works, but thru nautilus its as if its not published...
[20:28] <beuno> mongy, this is 10.10?
[20:28] <mongy> yup
[20:28] <beuno> there's a known bug that does that
[20:28] <mongy> I am using nautilus elementary if that matters
[20:28] <beuno> I think a fix is available on -proposed
[20:28] <beuno> I know it's fixed in nightlies
[20:30] <dobey> it is not fixed in nightlies
[20:30] <mongy> its not a big issue for me, so I can ignore it till natty... just thought I would put it out there.
[20:31] <dobey> the fix in maverick-proposed should fix it on 10.10 though
[20:31] <dobey> i'm not even sure if the bug exists in trunk, but the code is a bit different, so it may or may not, but the fix would be different from what is in maverick-proposed
[22:45] <zombyman> hi... How do I disable synchronization of certain folders on ubuntu one?


[00:14] <axisys> so far these will be removed
[00:14] <axisys> http://dpaste.com/3AMFME6
[00:56] <axisys> wow jump from kernel 2.6 to 3.2
[00:57] <sarnold> the next jump feels even bigger, to 3.13... :)
[00:57] <axisys> wow!
[00:57] <axisys> so put grub on /dev/sda and /dev/sdb.. do I need to put in /dev/md0 (raid1) as well?
[00:58] <axisys> I did not think so.. but just making sure
[01:03] <axisys> hmmm..
[01:03] <axisys> after reboot
[01:03] <axisys> Waiting for network configuration...
[01:03] <axisys> Waiting up to 60 more seconds for network configuration...
[01:03] <axisys> its a server with static IP
[01:03] <axisys> I am on console
[01:04] <sarnold> odd, I can't recall seeing that before
[01:04] <axisys> Booting system without full network configuration...
[01:05] <axisys> pre-up /usr/sbin/ethtool .. they moved it to /sbin/ethtool
[01:09] <sarnold> heh lets hope that was fixed in an SRU ..
[01:11] <axisys> all looks good
[01:11] <axisys> thanks to you and bekks for help
[01:12] <sarnold> done? woo :)
[01:12] <axisys> yep
[01:12] <axisys> took more than an hour
[01:12] <sarnold> cool :)
[01:12] <sarnold> I'm surprised about that
[01:12] <axisys> I will find out tomorrow morning from user complains if anything broke.. heh
[01:12] <sarnold> but at least you got to pick the hour of your choosing :)
[01:12] <sarnold> hehe
[01:13] <axisys> yep. we have 6 jumpstations.. so it was easy to take it down
[02:03] <R0ckET> hi
[06:24] <ash_m> okay, so I switched my vbox over to a bridged connection so I could ssh, but now apt-get can't connect to the internet
[06:24] <ash_m> any ideas?
[06:49] <ash_m> I don't think /etc/init.d/networking restart is doing anything
[06:49] <ash_m> if I do /etc/init.d/networking stop; how do I make sure that it's actually stopped?
[06:51] <ash_m> oh yeah, when I run service networking stop, it says: "stop: Job failed while stopping"
[07:02] <ash_m> okay, so apparently service networking restart isn't _supposed_ to work anymore
[07:02] <ash_m> I think the main recommendation is ifup/down
[07:03] <ash_m> but sudo ifdown eth1 says: ifdown: interface eth1 not configured
[07:03] <ash_m> and sudo ifup eth1 says: ifup: RTNETLINK answers: File exists
[07:03] <ash_m> doing some research on that, I came across the command netstat -rn
[07:04] <ash_m> this prints a table that lists eth1 with ..........
[07:04] <ash_m> wait, nvm; that doesn't really provide useful information
[07:04] <ash_m> (I am just realizing that)
[07:04] <ash_m> but the problem is still there
[09:42] <ash_m> the peeps over in ##networking helped me narrow it down to what I believe is a problem with tcp
[09:42] <ash_m> there is nothing listening on port 80
[09:42] <ash_m> google isn't really helping me out much here
[09:50] <lordievader> Good morning.
[09:51] <lordievader> ash_m: Can you still ping your gateway?
[09:52] <ash_m> lordievader: I think so... lemme check
[09:52] <ash_m> lordievader: being that it's a bridged connection, I assume the gateway for the vm is the same as my computer?
[09:53] <ash_m> lordievader: in any case, that is true
[09:53] <lordievader> Usually yes.
[09:53] <lordievader> You can ping it?
[09:54] <ash_m> yeah
[09:54] <lordievader> Okay, can you ping <IP_ADDRESS>?
[09:55] <ash_m> yes
[09:55] <lordievader> Does your dns work?
[09:55] <ash_m> how do you check?
[09:56] <lordievader> ash_m: dig www.google.com
[09:57] <ash_m> lordievader: https://bpaste.net/show/3e2fc5e9dc04
[09:58] <ash_m> lordievader: does that mean it's working? :}
[10:00] <lordievader> Yes, DNS works. Does apt-get update still not work?
[10:00] <ash_m> lordievader: apt-get update just hangs forever
[10:00] <ash_m> 0% [Connecting to us.archive.ubuntu.com (2001:67c:1562::16)] [Connecting to sec
[10:01] <lordievader> Does ipv4 work?
[10:01] <ogra_> did you try the main mirror instead of us.*
[10:01] <ash_m> lordievader: how would I check that?
[10:02] <lordievader> Disable ipv6 ;)
[10:03] <lordievader> sudo echo 1|tee /proc/sys/net/ipv6/conf/all/disable_ipv6
[10:04] <ash_m> lol
[10:04] <ash_m> I just jumped through a bit longer tut for disabling
[10:04] <lordievader> echo 1|sudo tee /proc/sys/net/ipv6/conf/all/disable_ipv6
[10:04] <ash_m> in any case; should i try pinging now?
[10:05] <lordievader> ash_m: No, apt-get.
[10:05] <ash_m> WORKING!
[10:05] <ash_m> amazing
[10:06] <ash_m> soooo.... why did this work on NAT and not Bridged?
[10:06] <ash_m> NAT converts ipv6 to ipv4?
[10:06] <lordievader> Under NAT it probably never got an ipv6 address.
[10:07] <ash_m> I see.
[10:07] <lordievader> Anyhow your ipv6 network bridge is broken.
[10:07] <ash_m> lordievader: well, that's good to know
[10:07] <ash_m> lordievader: thanks so much
[10:07] <lordievader> No problem.
[10:08] <ash_m> lordievader: I don't want to pester you more, so I'll check to see if this is now a problem google can help me with :)
[10:08] <ash_m> lordievader: that was a really good assessment... what led you to this theory?
[10:08] <lordievader> ash_m: If you did I would have said I couldn't help you. I don't know much about ipv6.
[10:09] <lordievader> ash_m: IPv4 worked, your "Connecting to..." line showed an IPv6 address.
[10:12] <ash_m> lordievader: so you thought, "It's attempting to resolve a v6 address... I wonder what happens if it just attempts to fetch a v4 address"
[10:12] <ash_m> ?
[10:17] <lordievader> The resolving ain't the problem, the connecting to is the problem.
[10:17] <lordievader> ash_m: Linux prefers ipv6 so if you have an ipv6 address it will try that first.
[10:18] <ash_m> is this something I should bother trying to fix or should I just be satisfied with leaving ipv6 disabled?
[10:19] <lordievader> ash_m: That is up to you.
[10:20] <ash_m> lordievader: how do you pronounce your sn? I am saying it "lordy evader" in my head
[10:21] <lordievader> Lord ee vader, it is a play on words.
[10:21] <ash_m> (to which I quickly get tired and contract it to "lordevader")
[10:21] <ash_m> oh, well then
[10:22] <ash_m> :)
[10:22] <ash_m> alright, my compy needs to restart
[10:22] <ash_m> I am really hopeful it doesn't revert all the changes I made to my folder settings... it tends to do that for some reason (win 8.1)
[10:23] <ash_m> c ya! thanks again!
[10:23] <lordievader> Hmm... it will revert the ipv6... but then he was gone.
[10:25] <YamakasY> is ubuntu still friendly ?
[10:32] <ash_m> back :)
[10:34] <YamakasY> wb
[10:34] <lordievader> Hmm... it will revert the ipv6... but then he was gone.
[10:34] <lordievader> ash_m: ^
[10:34] <ash_m> lordievader: I'll check it out
[10:34] <ash_m> lordievader: I actually went through a more elaborate process to edit the conf file directly so I hope that sticks
[10:35] <lordievader> ash_m: /etc/sysctl.conf you mean?
[10:35] <ash_m> lordievader: yeah
[10:35] <ash_m> I wish there was a way to keep MI off on VirtualBox
[10:36] <ash_m> lordievader: it would appear it stuck
[10:36] <ash_m> :)
[10:37] <lordievader> ash_m: Yes, that is persistent.
[10:37] <lordievader> MI?
[10:37] <andol> On that note, instead suggesting "echo 1|sudo tee /proc/sys/net/ipv6/conf/all/disable_ipv6" it might be a slightly better approach to suggest "sudo sysctl net.ipv6.conf.all.disable_ipv6=1", it mapping more directly to what one would put in /etc/sysctl.conf
[10:37] <andol> Not that one really want to have that line in ones sysctl.conf, but still :-)
[10:37] <ash_m> lordievader: mouse integration
[10:37] <lordievader> andol: There are many ways to rome ;)
[10:38] <ash_m> lordievader: it's a server OS anyway, so I will never see it on that console
[10:38] <lordievader> andol: It is in mine, simply because I haven't gotten round to properly setting up ipv6 yet.
[10:39]  * andol makes an effort to keep his inner IPv6 zealot under control...
[10:40] <ash_m> andol: yeah I added net.ipv6.conf.all.disable_ipv6 = 1
[10:40] <ash_m> net.ipv6.conf.default.disable_ipv6 = 1
[10:40] <ash_m> net.ipv6.conf.lo.disable_ipv6 = 1
[10:40] <ash_m> I guess default and lo are meaningless if all is disabled
[10:41] <ash_m> andol: is it worth me attempting to fix my VM so that IPv6 works? right now (as you have noted) it's just disabled.
[10:43] <andol> ash_m: Assuming you have some idea on where to start, it wouldn't hurt to at least spend some time on it.
[10:43] <andol> I mean, sooner or later you will need to familiar yourself with IPv6.
[10:44] <ash_m> that's true, but sooner or later I will need to familiarize myself with networking in general lol
[11:39] <jamespage> coreycb, dosaboy, zul: haproxy included for liberty CA - enables SSL termination support for LBaaS
[11:45] <jamespage> coreycb, something new for you to learn - https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1472586
[11:45] <jamespage> you should be able to follow in my footsteps for previous updates
[11:50] <zetheroo>  memory on a webserver is being gobbled up by something and I need to find out by what ..
[11:57] <coreycb> jamespage, got it, thanks
[12:04] <lordievader> zetheroo: (h)top?
[12:04] <zetheroo> lordievader: that shows percentages ... I would like to see MB or GB ...
[12:05] <lordievader> It shows those things too, and else you can allways calculate them.
[12:07] <zetheroo> all I see is memory percentage
[12:09] <lordievader> zetheroo: Top shows virt, res and share by default, in htop you can enable those.
[12:17] <coreycb> jamespage, 2014.1.5 is Fix Released for trusty and CA testing was successful on precise-icehouse-proposed
[12:19] <zetheroo> I am just wondering ... is it safe to completely turn off swappiness on a server?
[12:20] <lordievader> zetheroo: That depends.
[12:20] <zetheroo> I saw about 10GB of the 16GB memory was marked as "cached" by the monitoring tool we use (munin) - would it make a difference to enable swap?
[12:21] <lordievader> If you have enough ram or don't care about the oom, it can be disabled.
[12:21] <zetheroo> ok - well there was about 1GB free ...
[12:21] <zetheroo> after rebooting the server only 1.5GB is being used out of that 16GB
[12:22] <jamespage> coreycb, awesome
[12:23] <jamespage> coreycb, need to let precise bake for +5 days based on when stuff went into proposed
[12:24] <coreycb> jamespage, ok
[12:24] <jamespage> coreycb, will push out on monday
[12:25] <jamespage> remind me if I have not done it
[12:25] <coreycb> jamespage, will do, sounds good
[13:02] <boukiller> hello, can someone help me with this squid config http://pastebin.com/iLntCWMh ? I have a Access Denied error from squid (ubuntu server 14.04lts)
[14:11] <teward> rbasak: since you know more about it than I, are SRUs accepted for inclusion of apport hooks in order to make diagnosing the ****storm of unusable ambiguous bugs we've seen recently against nginx easier?  or should I be poking -release with that question?
[14:12] <teward> (for vivid+, we need extra info in the bug report that apport just can't give us on its own, for those postinstall bugs)
[14:15] <soahccc> We had a hard drive failure in our raid1. I removed the disk from the array and shut the machine down, replaced disk and when I now try to boot I get this: http://files.sven.bmonkeys.net/images/811730085_12085082117409553779.jpg_2015-07-08_16-11-36.png Any idea what could possible went south? I guess it generally found something to boot from (ie grub is not broken)
[14:32] <rbasak> teward: pretty sure the SRU team would be happy to take apport hook enhancements, as long as they're also present in Wily.
[14:33] <rbasak> teward: I've done that for mysql before.
[14:36] <teward> rbasak: yeah, this is gonna have to land in Wily and Vivid
[14:36] <teward> especially since we have a lot of incomplete, crap-information bugs on the same version with no debugging info
[14:37] <teward> so thanks to pitti in -devel, i've got the info i need to start poking apport hooks into play.  Then I have to beat the source package and test xD
[14:37] <teward> (so if we have a bug or two that accidentally get in and I Invalid them, blame testing >.>)
[14:38] <rbasak> matsubara: please could you test Utopic in bug 1443735? There was a small accident earlier: http://irclogs.ubuntu.com/2015/07/08/%23ubuntu-release.html#t12:09
[14:39] <rbasak> soren: am I right in thinking that you manage the bot in here? I don't think it's worked in a while.
[14:42] <soren> rbasak: Well..
[14:42] <soren> rbasak: No. I stopped managing it at one point.
[14:43] <soren> soren: I just failed to let you guys know :(
[14:43] <soren> Hah.
[14:43] <rbasak> soren: ah :)
[14:43] <soren> And now I'm talking to myself.
[14:43] <teward> rbasak: I *could* drop a clone of one of my bots with Bug Number ANnouncing into here, or we could poke whoever manages ubottu... :P
[14:43] <teward> soren: heh
[14:43] <rbasak> I can always ask to get another bot in here, just don't want to end up with two operational ones.
[14:43] <teward> rbasak: i think the issue is we used to have a ubot, and we have ubottu now...
[14:44] <teward> not sure what the situation is on what does what thoug
[14:44] <soren> I feel pretty confident saying that mine is gone for good.
[14:44] <rbasak> OK. We'll figure out a replacement. Thank you for your bot's previous hard work :-P
[14:44]  * soren tips his hat
[14:45] <teward> rbasak: well, I know Ubottu can do it, just tested in -bots
[14:45] <teward> maybe the managers need to turn that on for here?
[14:46] <rbasak> teward: do you know who manages ubottu?
[14:46] <teward> i could find out
[14:46] <rbasak> Would you mind?
[14:46] <teward> nope, just gotta switch to a channel 5 chans up on the list
[14:49] <teward> rbasak: Pici'll take a look at it
[14:50] <rbasak> Thanks Pici and teward!
[14:58] <OliPicard> hey everyone, I'm trying to setup a cron job every hour to run python3 script.py at the location /var/www however the cron isn't firing. any ideas as to why it isn't? I'll paste the cron syntax in a second :)
[14:58] <teward> rbasak: do you think that there'll be any issue with adding the apport hooks to Wily nginx while we have the pending issue with where to go forward?
[14:58] <lexdvnc> Hi everyone. Quick question. Has anyone here any attempted a kernel upgrade to 4.0 on Ubuntu 14.04 LTS?
[14:59] <lexdvnc> The hot kernel patch is really *something*
[14:59] <rbasak> teward: I don't think so. Seems to me that they're fairly independent.
[14:59] <teward> ack
[14:59] <teward> rbasak: the only thing is it increases the delta between Debian and Ubuntu, but necessarily so
[14:59] <teward> (because apport)
[15:00] <smb> rbasak, ping about hangout
[15:00] <rbasak> Yeah, though it's pretty well separated. I think Debian might even take apport stuff now. We did it for MySQL as it doesn't impact Debian at all. I can't remember Debian status though. Ultimately depends on the maintainers I guess.
[15:00] <rbasak> smb: joining
[15:01] <OliPicard> 0 * * * * python3 /var/www/html/setup.py is on my crontab -e
[15:01] <teward> rbasak: it appears to me people actually RESPOND to requests for information on Debian bugs
[15:01] <teward> whereas people don't here in Ubuntu, my guess is because ubuntu bug reporting is a lot more friendly
[15:06] <OliPicard> I'm guessing I would need to use 0 * * * * python3 setup.py /var/www/html
[15:10] <pmatulis> OliPicard: start with something reall simple. the problem is prolly not with cron but with the binary and/or how it's being called
[15:11] <OliPicard> pmatulis: it's calling fine when in manual mode
[15:12] <OliPicard> if i was to run the app using python3 setup.py it's fine (note it's not called setup.py, It's just an example ;))
[15:12] <teward> stupid question, but does your user when running that script (assuming a userspace crontab) have access to the directory?
[15:12] <teward> and also what are you using to determine whether the script is firing or not
[15:12] <OliPicard> Yup :D
[15:13] <OliPicard> grep
[15:13] <OliPicard> grep CRON /var/log/syslog
[15:14] <OliPicard> Jul  8 07:00:02 host CRON[2156]: (CRON) info (No MTA installed, discarding output)
[15:15] <teward> OliPicard: consider maybe wrapping the command in a bash script, call `logger` and log to syslog that it's going to try and execute the script, then the line after the python3 ... line can be another logger call that spits out what the exit code was?
[15:15] <teward> (ran into a headache like this here at work >.<)
[15:16] <teward> (at least for testing :P)
[15:16] <teward> in case cron says nothing by some weird issue
[15:16] <TJ-> lexdvnc: I use kernels 4.1 and 4.2-rc1 with 14.04
[15:17] <lexdvnc> TJ- are you using it on server or desktop? The concern here is that I want to run 4.0 on KVM VPS
[15:17] <TJ-> lexdvnc: both
[15:17] <lexdvnc> TJ- how was the upgrade process? Smooth? Encountered any major issue?
[15:19] <TJ-> lexdvnc: I just built the kernel ("make ... deb-pkg"), installed the packages and rebooted
[15:19] <lexdvnc> Okay gotcha. I will attempt upgrade
[15:19] <lexdvnc> Thanks TJ-
[15:21] <OliPicard> Teduardo: Ah :D on a server
[15:21] <OliPicard> tedward: sorry my auto correction just failed.
[15:26] <OliPicard> tedward: Just tried this instead: 0 * * * * python3 plutus.py /var/www/html
[15:38] <matsubara> rbasak, sure. I focused on the two lts and the current release. I didn't try the grub-signed packages though
[15:41] <coreycb> jamespage, python-keystonemiddleware is fix released in utopic and successfully tested in the CA for trusty-juno-proposed
[15:41] <jamespage> coreycb, ack
[15:41] <k2gremlin> Quick question, blank iptables allows all or no?
[15:42] <soren> k2gremlin: Depends.
[15:42] <soren> k2gremlin: You also define a default policy.
[15:42] <soren> k2gremlin: So it's up to you.
[15:42] <k2gremlin> Well it's blank and ssh is working locally so...
[15:43] <k2gremlin> but I was trying to define a few ports last night and I could not for thwe life of me get them to work
[15:44] <jamespage> coreycb, promoted to updates - thankyou!
[15:44] <coreycb> jamespage, ty!
[15:46] <soren> k2gremlin: This is the output of my "iptables -L": http://streambin.net/1bd496bb-59ba-4b50-b517-f297f1e9ada5
[15:46] <soren> k2gremlin: See where it says "Chain INPUT (policy DROP)".. That means the default policy is DROP.
[15:46] <soren> k2gremlin: If nothing matches, that's what will happen.
[15:47] <k2gremlin> soren, Ok so my def is accept
[15:47] <k2gremlin> so why is my server not accepting :/
[15:47] <k2gremlin> ports are forwarded on my router
[15:48] <soren> Either another rule is blocking it or you're not actually listening on the given port.
[15:48] <k2gremlin> Chain INPUT (policy ACCEPT)  with nothing under it
[15:48] <k2gremlin> its weird.. when I do a netstat, they show up.. but with a blank state..
[15:48] <k2gremlin> how do I fix that?
[15:48] <soren> k2gremlin: What do you mean "blank state"?
[15:49] <k2gremlin> nothing listed under state for the 2 ports im trying to use
[15:49] <k2gremlin> udp        0      0 <IP_ADDRESS>:7778            <IP_ADDRESS>:*
[15:49] <k2gremlin> thats it lol
[15:49] <soren> UDP is stateless.
[15:50] <k2gremlin> Ok then my port 7777 is not working at all :/
[15:50] <k2gremlin> thats the tcp port
[15:51] <soren> You're not really giving me anything to work with. I have no idea what you're trying to do, what you've done, what you were expecting to happen and what actually happened.
[15:52] <k2gremlin> soren, I am trying to get an Ark server running. It shows up on the LAN but is unreachable from the WAN.
[15:52] <soren> So you say.
[15:56] <k2gremlin> soren, if your interested in taking a peek... https://join.me/887-845-113
[16:42] <matsubara> rbasak, I'm unable to reproduce the bug in Utopic for bug 1443735. It seems the install from scratch already leaves me with grub2 2.02~beta2-15ubuntu01 which after a power off have the 30s grub timeout set.
[16:42] <matsubara> rbasak, is that enough of a verification?
[16:44] <matsubara> rbasak, I left a comment in the bug report stating so.
[16:57] <rbasak> matsubara: I think that's fine. Thank you!
[16:57] <matsubara> rbasak, np
[17:51] <teward> rbasak: fwiw, I fear i'm overcomplicating the apport hooks file xD
[17:51] <teward> but i guess that's just my coding style.
[17:51] <teward> (for nginx)
[19:05] <LinuxJedi> teward: anything I can help with
[19:10] <teward> LinuxJedi: not unless you know how to make systemd actually show stderr during apt
[19:11] <teward> LinuxJedi: it's not an nginx core issue - it's an apport handling issue
[19:12] <teward> LinuxJedi: if you'd like I'll give you a rundown of the issue in PM
[19:12] <teward> AND update you on something else
[19:12] <LinuxJedi> ah! Unfortunately I can only do the basics in systemd. May I suggest beating it with a hammer? :)
[19:13] <teward> :P
[19:13] <teward> LinuxJedi: i'm going the apport-hook method, but i'll give you the rundown of the issue anyways, see the incoming PM
[19:13] <LinuxJedi> cool, thanks :)
[19:13] <sarthor> Hi, I am running ubuntu-server, I am facing this message with apt-get install any-pakagge. E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/postgresql-9.                                  3/libpq5_9.3.9-0ubuntu0.14.04_amd64.deb  Connection failed [IP: <IP_ADDRESS> 80]
[19:24] <jge> weird, anyone know why syslog is writting twice to main log and template even when "&~" is present?
[19:46] <sarnold> sarthor: is it still happening? I get a 200 OK when I connect to it
[19:47] <sarthor> sarnold, Have still happening that.
[19:49] <sarnold> sarthor: I suggest trying mtr <IP_ADDRESS> or traceroute <IP_ADDRESS> to try find out where the connection fails
[19:59] <sarthor> sarnold, mtr says this http://paste.ubuntu.com/11843594/
[20:01] <sarnold> sarthor: that packetloss early on is astonishing.. but the later hops all seem alright..
[20:03] <sarthor> sarnold, that is my modem IP address.
[20:03] <sarthor> and My ISP assign it dynamically.
[20:04] <sarthor> rest I have no issue with internet, where will be the issue? with my ISP or with distination ?
[20:28] <Sprocks> how do i enable AMD-V so that i can have my ubuntu 14.04 server run 64bit virtual machines in virtualboxheadless?
[20:30] <bekks> Sprocks: Enable it in the BIOS.
[20:31] <Sprocks> bekks: i dont see an option for it in the bios but i ran "grep --color svm /proc/cpuinfo" and it says the support is there
[20:39] <bekks> And do you get a specific vbox error message?
[20:42] <jamespage> SpamapS, ironicclient should be in the proposed area of the cloud-archive for kilo in the next hour or so
[20:42] <Sprocks> when i create a vbox machine using the command line it creates a nice 64bit machine but when i try and install a 64bit os i get the wrong kernal message you'd expect
[20:44] <TJ-> Sprocks: if you see the svm flag then virtualization support is enabled, but the hypervisor may require a kernel module to use it. For QEMU there's the KVM module
[20:45] <Sprocks> TJ-: so you think if i install kvm everything should work fine?
[20:46] <TJ-> Sprocks: not for VirtualBox, for that you need the VB module, usually its a DKMS managed module I believe
[20:47] <TJ-> Sprocks:  see "apt-cache show virtualbox-dkms"
[20:51] <sarthor> HI again, if I can not download some packages from here, http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpq5 amd64 9.3.9-0ubuntu0.14.04
[20:51] <sarthor>   Connection failed [IP: <IP_ADDRESS> 80] , then what will be next option please.
[20:51] <Sprocks> TJ-: would you like the paste of that?
[20:52] <TJ-> Sprocks: No, I read it here. I was giving it you for information... that is the moduel VB will require, if it isn't already installed
[20:52] <bekks> The kernel modules are always required, but the error message you get would be interesting.
[20:52] <bekks> sarthor: You could use another mirror.
[20:59] <smygIG> Hallo. Can i use static ip in server when the router is using dhcp? The problem is thet my server dont get ip if it starts before the router.
[20:59] <ogra_> smygIG, you should tell your router to leave that IP out of the DHCP pool so it doesnt get assigned twice
[21:00] <ogra_> (beyond that, yes, sure, that should all work)
[21:02] <smygIG> ORGA_ the ip is lockt to my servers mac.adress
[21:02] <ogra_> right, then it is fine
[21:03] <smygIG> OGRA_ thanx
[21:05] <Sprocks> TJ-: this is what i get when i try to install that http://paste.ubuntu.com/11843935/
[21:07] <TJ-> Sprocks: I thought VirtualBox was installed?
[21:08] <Sprocks> TJ-: it is, i installed it according to https://www.howtoforge.com/vboxheadless-running-virtual-machines-with-virtualbox-4.3-on-a-headless-ubuntu-14.04-lts-server
[21:09] <bekks> Sprocks: Then DONT install virtualbox-dkms.
[21:09] <bekks> Thats a package from the Ubuntu repos, while you install virtualbox from the Oracle repo.
[21:12] <TJ-> Sprocks: Are you aware that the 14.04 archives has virtualbox  4.3.10-dfsg-1ubuntu5 ?
[21:14] <Sprocks> TJ-: no i wasnt aware of that but would that let me run a vbox headless server with 64bit guests?
[21:16] <TJ-> Sprocks: There are a series of packages, see "apt-cache search -n 'virtualbox' ... but virtualbox contains "/usr/bin/VBoxManage"
[23:11] <teward> postfix question: if I want to accept all addresses for a given domain, and forward them (virtual domain aliases basically), is @domain.tld sufficient or is there more config needed (OTHER than putting it in virtual_alias_domains and adding the mapping)
[23:12] <k2gremlin> Is there anyway to tell a process on Ubuntu to use more then 1 core?
[23:13] <sarnold> k2gremlin: that can only be done via writing the application to use threading or multiple processes
[23:14] <sarnold> k2gremlin: by default, every program can use as many processors are on the system
[23:14] <k2gremlin> sarnold, Apparently not the Ark Server program lol
[23:14] <k2gremlin> when it boots up, it slams one core.. and nothing else lol
[23:15] <sarnold> k2gremlin: that's not a big surprise; multi-threading programs are difficult to get right. Multiple processes are a lot easier, but not necessarily a good fit for whatever it needs to do.
[23:15] <k2gremlin> Understand. Thanks
[23:15] <k2gremlin> just being bored while I try to fix a damn port issue.. its killing me lol
[23:16] <k2gremlin> if my iptables says (policy ACCEPT) on input, all is open by default right?
[23:17] <k2gremlin> and any -j Accepts I toss on there don't do crap.. ?
[23:17] <teward> k2gremlin: is this an EC2
[23:17] <teward> or something behind a hardware firewall/router/NAT
[23:17] <k2gremlin> its behind a router/nat
[23:17] <teward> portforward
[23:17] <teward> did you do that?
[23:17] <k2gremlin> and the router is forwarding the ports..
[23:17] <teward> did you verify it?  (packet trace on the server, verify the packets reach?)
[23:17] <k2gremlin> http://imgur.com/QBd9FlG,lOCNNFa#0
[23:19] <teward> sarnold: how hard would it be for me to get a tiny nginx upload into wily right now, given I have upload rights?
[23:19] <teward> (it's the apport hooks)
[23:19] <sarnold> teward: afaik if you have upload rights you can upload whatever you want almost whenever you want, right? featurefreeze times etc..
[23:20] <teward> sarnold: within reason, yeah,I mean I can't upload something that torpedoes the builds, obviously, except where it's a complete accident
[23:21] <k2gremlin> Another general question, is there a way to tcpdump for multiple ports? port 7777 | port 7778?
[23:21] <teward> sarnold: i'm doing some final testbuilding before dropping things into my vivid test vm to see if the apport hooks are built in right to the packages, but eh
[23:21] <k2gremlin> or is it (7777|8888)
[23:21] <sarnold> k2gremlin: something like "port 7777 or 8888"
[23:22] <TJ-> k2gremlin: "port 7777 or port 8888"
[23:22] <sarnold> k2gremlin: there's some examples (more complicated) in the tcpdump manpage
[23:22] <sarnold> teward: nice
[23:22] <teward> sarnold: i love sbuild xD
[23:23] <k2gremlin> sarnold, thanks
[23:24] <teward> sarnold: the only thing I hate is all the flavors of nginx - that's one apport hook per nginx binary
[23:24] <teward> so, nginx-core nginx-light nginx-full nginx-extras
[23:24] <teward> ^ four identical files
[23:25] <sarnold> ooof
[23:25] <teward> because the debug symbols don't need the apport hooks, nor does the -common package
[23:25] <sarthor> Hi. I am back again with same probem if some person can help to guide me toward solution. my apt-get says Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/libc/libcrypt-openssl-rsa-perl/libcrypt-openssl-rsa-perl_0.28-1build1_amd64.deb  Connection failed [IP: <IP_ADDRESS> 80]
[23:26] <teward> sarthor: working here, maybe switch mirrors, or wait a little bit?  (a wget indicates that the download works fine)
[23:27] <sarthor> teward, I am facing this issue since 3 days. How to change mirror. I am not expert.
[23:27] <teward> three days?  and it still happens?
[23:27] <sarnold> sarthor: hmm.. are you perchance using squid-deb-proxy or apt-cacher-ng? I think I had that error message when I switched mirrors but forgot to update the squid ACLs
[23:27] <teward> ^ that perhaps?
[23:29] <sarthor> no squid or any proxy server involved. connected direct to FTTH modem. 25 m/s downllink
[23:31] <sarthor> and this url from the server says in browser  " http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main cpp-4.8 amd64 4.8.4-2ubuntu1~14.04" ..The requested URL /ubuntu/ trusty-updates/main cpp-4.8 amd64 4.8.4-2ubuntu1~14.04 was not found on this server.
[23:31] <sarnold> what URL did you paste into your browser?
[23:32] <sarthor> sarnold, that was wrong sorry.
[23:34] <sarthor> this is what my apt-get says Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/libc/libcrypt-openssl-rsa-perl/libcrypt-openssl-rsa-perl_0.28-1build1_amd64.deb and i think this file is not there.
[23:34] <teward> sarthor: um... what you just posted is not a link?
[23:34] <sarnold> sarthor: I just retrieved that file from all three servers that are using that name
[23:34] <teward> sarnold: http://us.archive.ubuntu.com/ubuntu/pool/main/libc/libcrypt-openssl-rsa-perl/libcrypt-openssl-rsa-perl_0.28-1build1_amd64.deb  <-- try and get that
[23:35] <teward> erm
[23:35] <teward> sarthor: ^
[23:35]  * teward kicks the internet
[23:35] <sarthor> teward, sarnold with me it says The connection was reset
[23:35] <sarthor> The connection to the server was reset while the page was loading.
[23:35] <sarthor> while I have good internet
[23:36] <teward> apparently not
[23:36] <teward> something's killing the connection
[23:36] <sarnold> sarthor: I think you've got a difficult debugging process ahead of you; try doing http to a few dozen websites, see if you can find any commonalities between what works and what fails
[23:36] <sarthor> teward, yea. I can browse internet. can install alot more packages. downoad speed is awsome. do not what is issue.
[23:37] <sarnold> sarthor: at least you're resolving the dns names to the same IPs that I'm getting, so you get a free pass on DNS :)
[23:38] <sarthor> Ahhhhhhhhh... I was crazzy to lean how to configure postfix. I found good tutorial Now I can not install packages due to this issue.
[23:38] <teward> sarnold: in other news: i discovered interacting with my VM over SSH from the host itself on a host-only device makes copy-paste and editing things so much easier and i only discovered this last week is more sane xD
[23:38] <teward> s/is more sane//
[23:40] <sarnold> teward: ssh is the only way to use vms :) hehe
[23:40] <sarthor> BYE for now.
[23:40] <TJ-> sarthor: the issue seems to be a HTTP protocol version issue. HTTP/1.0 fails, HTTP/1.1 succeeds
[23:40] <TJ-> darn!!!!
[23:41]  * TJ- thinks sarthor is behind a transparent proxy that is using HTTP/1.0 for outbound requests
[23:41] <teward> sarnold: yes it is xD
[23:41] <teward> TJ-: i think so too, perhaps
[23:41] <teward> but he said no proxy in there
[23:41] <teward> i doubt it
[23:42] <sarnold> TJ-: hah, I'd never think to try that..
[23:42] <TJ-> If his ISP is operating a proxy he won't know about it.   see http://paste.ubuntu.com/11844647/
[23:46] <TJ-> Interestingly, that mirror is showing different Apache versions for HTTP/1.0 vs HTTP/1.1 - must be behind a load-balancer/proxy itself
[23:47] <teward> TJ-: indeed


[00:06] <Spreadsheet> Happy New Year's Eve everyone
[00:31] <mhall119> happy new year Spreadsheet
[00:31] <Spreadsheet> It's not new years yet, but happy new year too
[00:31] <mhall119> yeah but I won't be around that late, so sayin it now ;)
[04:04] <nightfrog> Merry New Years #ubuntu-us-fl!
[05:01] <jtatum> happy new year
[05:17] <droidfrog> Merry new year


[10:09] <dragonlord> hi there. i've recently managed to get my first package into a PPA working: https://launchpad.net/~rpluess/+archive/ubuntu/dragondreams/+packages
[10:10] <dragonlord> this is amd64 arch on focal
[10:10] <dragonlord> now on my build server I use a docker image with bionic to compile the general release builds
[10:10] <dragonlord> this means in the PPA I should be able to get also the same sources compiled to eoan and bionic
[10:11] <dragonlord> but I can't figure out how I'm supposed to do this. do I need to create new packages with different debian/control files?
[10:11] <dragonlord> or can I somehow tell launchpad to compile the source also for eoan/bionic as wellas also x86 archi?
[10:12] <dragonlord> last but not least since this is my first package i would be really glad if somebody could look over it so I can improve on it on the conformance level


[13:34] <Kow> Does Ubuntu currently use every upstream debian patch [in the official ubuntu kernel builds], or selective? If the latter, is there documentation on explictly which patches are being pulled? Thanks!
[14:25] <TJ-> Kow: as far as I'm aware Ubuntu kernel patches always come from mainline/stable, not Debian


[00:38] <doctormo> Another positive blog post, this time ported packages for natty.
[06:55] <duanedeisgn> 4
[07:26] <nigelb> duanedeisgn: 42
[14:26] <cjohnston> mornin
[14:28] <Pendulum> hiya
[14:28] <cjohnston> o/
[14:29] <czajkowski> fun way to spend a saturday
[14:29] <czajkowski> doing teams re approval
[14:29] <czajkowski> application
[14:29] <cjohnston> heh
[14:30] <czajkowski> I also need to file bugs/mails to the LD dev list
[14:31] <cjohnston> uggh
[14:35] <czajkowski> oh yeah
[14:35] <cjohnston> what
[14:35] <czajkowski> I've some issues that are being a pain this week
[14:36] <czajkowski> some fields are mandatory and need to be made more stringent but not sure how yet
[14:36] <cjohnston> ?
[14:36] <czajkowski> cjohnston: an example is team contact
[14:36] <czajkowski> people leave it blank which means when I need to contact them I've to go to LP
[14:36] <czajkowski> or they put a team as a team contact
[14:36] <czajkowski> which is a mailing list to a group of people
[14:37] <cjohnston> got a team in specific?
[14:38] <cjohnston> czajkowski: look at http://loco.ubuntu.com/teams/ubuntu-eo
[14:39] <cjohnston> team contact on LD is not possible to be a team.. but I don't believe its imported from LD because the team admin may not be the team contact
[14:40] <czajkowski> they are creating teams or admins
[14:40] <czajkowski> so say if I want to mail someone they also hide their address from being public
[14:40] <czajkowski> if you're a team contact
[14:40] <czajkowski> your email address should be public!
[14:41] <cjohnston> there is the contact me on the LP page..
[14:42] <czajkowski> yeah I know
[14:42] <czajkowski> but that's on LP then
[14:42] <czajkowski> tis annoying
[14:42] <cjohnston> if you go to edit details they only have users.. and i believe that it was made to where teams are broken into people
[14:42] <czajkowski> cjohnston: doing one thing today
[14:42] <czajkowski> and that's ireland team
[14:42] <cjohnston> http://loco.ubuntu.com/teams/ubuntu-fr
[14:42] <czajkowski> I'll do LD dev mails later
[14:42] <czajkowski> :)
[14:42] <cjohnston> they are broken out of the team and into people
[14:55] <nigelb> czajkowski: I have a question for you.
[14:55] <czajkowski> sure
[14:56] <nigelb> czajkowski: The loco council deals with the list of loco teams mentioned in your blog post for this cycle.   Is summit slow for you too czajkowski ?
[15:05] <nigelb> hrm, fairly okay for me.
[15:06] <czajkowski> cjohnston: nope tis fine
[15:06] <cjohnston> hmm
[15:55] <czajkowski> jcastro: you about by any sweet love of god chance
[15:55] <czajkowski> oh nm used my brai
[15:55] <czajkowski> *brain
[21:38] <mhall119> czajkowski: cjohnston what's going on?
[21:39] <cjohnston> PM mhall119
[21:47] <cjohnston> pleia2: had another delerium tremins (sp) last night
[22:33] <pleia2> cjohnston: I'm in ur state, soakin up ur sun
[22:41] <nigelb> heh
[22:41] <nigelb> pleia2: on your phone? :)
[22:42] <pleia2> nigelb: nah, wifi here at the condo we're staying at
[22:43] <nigelb> pleia2: Strange, I've never seen you use 'ur' before ;)
[22:43]  * nigelb yawns and heads to bed.
[22:44] <nigelb> Tomorrow is going to be so bad :\
[22:44] <nigelb> pleia2: laters :)
[22:44] <pleia2> night!
[23:01] <cjohnston> pleia2: where in fl
[23:35] <mhall119> cjohnston: miami
[23:35] <cjohnston> ic
[23:50] <topyli> any staff to help with a cloak? we need an ubuntu/member cloak for UndiFineD
[23:51] <Pendulum> topyli: have you checked in #ubuntu-irc?
[23:52] <topyli> Pendulum: wrong channel, sorry :)


[17:06] <ApOgEE--> hi all..
[17:07] <ApOgEE--> i need help about ubuntu trademark. anybody from canonical?
[21:01] <boredandblogging> ApOgEE--: might want to try http://www.ubuntu.com/contact/trademark
[21:47] <johnc4510> The New edition of the UWN #134 is now available:
[21:47] <johnc4510> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue134