[02:36] <jakewrong> anyone know where to find info about ubuntu patches for mitigating todays kernel vulns?
[02:36] <jakewrong> or is there a ppa to install a kernel with the patches already there?
[02:54] <PilotBob42> howdy howdy
[02:55] <noahwheeler> Hey pilot bob
[02:55] <PilotBob42> any progress?
[02:55] <noahwheeler> I was wondering about you
[02:55] <noahwheeler> Yes
[02:56] <noahwheeler> I was able to setup the hotspot after talking with Tmobile
[02:56] <noahwheeler> Onto the Mate OS
[02:56] <noahwheeler> But I still have a million problems
[02:57] <PilotBob42> the laptop and pi are talking though on the hotspot?
[02:57] <noahwheeler> #1 I switched the ttySo - to serial 1 , and the ttyAMA0 to serial 0
[02:58] <noahwheeler> No
[02:59] <noahwheeler> I can switch the wi-fi from home to hotspot
[02:59] <noahwheeler> but only communicate with the pi on the home wi-fi?
[02:59] <PilotBob42> well. yeah.
[03:00] <noahwheeler> the hotspot changes the ip adress on the pi and is so far inaccesable
[03:00] <noahwheeler> ???
[03:01] <PilotBob42> well yeah.
[03:01] <noahwheeler> I can remote desktop to pi with home wi-fi only .
[03:01] <noahwheeler> no ssh
[03:01] <PilotBob42> each SSID you connect to will give the pi a different address.
[03:01] <PilotBob42> You need to be able to know the IP at the time it's connected to the hotspot.
[03:02] <noahwheeler> okay that is what happened here ! yes the ip is <IP_ADDRESS>
[03:03] <noahwheeler> but I can't remote to the desktop with the ip ???
[03:03] <noahwheeler> or ssh ?
[03:03] <noahwheeler> or ssh with the phone
[03:05] <noahwheeler> when connected to the home wi-fi the ip is <IP_ADDRESS> can connect everytime remote desktop , and acces my samba files but no ssh ?
[03:05] <PilotBob42> Well, like I said yesterday, the hotspot might not even allow that sort of collateral traffic from two devices attached to it.
[03:06] <noahwheeler> But there is only ever one device attached
[03:06] <noahwheeler> either the phone , or the pc
[03:06] <noahwheeler> never two at one time
[03:07] <noahwheeler> oh I see what you are saying now !!!
[03:07] <PilotBob42> and the Pi.
[03:08] <noahwheeler> so if I hotspot ! I can't ssh with the pc
[03:08] <noahwheeler> I get it unless I root the phone
[03:08] <PilotBob42> well... maybe...
[03:09] <PilotBob42> if the phone is the hotspot then it has to route the ssh traffic from the PC/laptop to the Pi
[03:09] <PilotBob42> And I'm doubting the phones firmware is allowing that traffic to past
[03:09] <noahwheeler> I thought if the pi used the hotspot for the connection it would act as it does with the pc connection  , but the hotspot connection is not the same ?
[03:11] <noahwheeler> Well I talked to Tmobile and they said I should have no problem with this there is no encryption
[03:11] <PilotBob42> ok good, then you just need to figure out what IP the Pi gets when it connects to the hotspot.
[03:12] <noahwheeler> it has to be a networking thing ???
[03:12] <PilotBob42> and that is the one you use from your laptop when away from home
[03:12] <noahwheeler> or at home right ?
[03:13] <noahwheeler> the wlan0 address is <IP_ADDRESS> but I can't connect to it with the desktop ? I don't know why ?
[03:13] <PilotBob42> No, the Pi will get a different IP for each wireless network it attached too.
[03:14] <PilotBob42> Have you checked that while it's connected to the hotspot?
[03:15] <PilotBob42> Ok, you know how when you set up a new wifi connection in Windows it asks you if it's home, work or public right?
[03:16] <PilotBob42> If you say public (and probably work) then then the devices connected laterally to the same wifi won't be able to talk to each other. It's a security thing to keep you safe
[03:17] <PilotBob42> Either the Pi or the laptop (or both) are doing something like that when you are on your phone's hotspot.
[03:23] <PilotBob42> hmm...
[03:25] <PilotBob42> Anybody here have experience getting EDID to work with the NouVeau or Nvidia drivers?
[03:26] <PilotBob42> hey there, where did I lose you?
[03:26] <noahwheeler> I bet I lost you and have been typing to noone for a long time because I switched to the hotspot
[03:26] <PilotBob42> lol
[03:26] <noahwheeler> so I could get you the adress
[03:26] <PilotBob42> I was saying (and I really think this is your issue):
[03:27] <PilotBob42> you know how when you set up a new wifi connection in Windows it asks you if it's home, work or public right?
[03:27] <noahwheeler> so back to it
[03:27] <PilotBob42> If you say public (and probably work) then then the devices connected laterally to the same wifi won't be able to talk to each other. It's a security thing to keep you safe
[03:27] <PilotBob42> Either the Pi or the laptop (or both) are doing something like that when you are on your phone's hotspot.
[03:27] <noahwheeler>  the hotspot adress is the <IP_ADDRESS> , or .43.1
[03:28] <noahwheeler> okay
[03:29] <noahwheeler> How do I fix it so all are the same ?
[03:29] <PilotBob42> Well, I'm gonna trust that Tmobile told you the truth and they aren't blocking the traffic, so that would leave either the Pi or the laptop thinking it's connected to a public wifi and fire-walling your attempts to talk laterally.
[03:29] <noahwheeler> I can switch it in windows
[03:29] <PilotBob42> The laptop is windows right?
[03:30] <noahwheeler> yes
[03:30] <noahwheeler> win 10
[03:30] <PilotBob42> that's the easier one to check first
[03:30] <noahwheeler> It's actually a gaming desktop I built
[03:31] <noahwheeler> with a 4770 intel core i7
[03:31] <PilotBob42> If you right click the wifi in the system tray and choose "Open Network and Internet setting"...
[03:31] <noahwheeler> It's perfect for this project
[03:32] <noahwheeler> okay
[03:32] <noahwheeler> is set to private
[03:32] <PilotBob42> You'll see "network status" and three icons below it representing the laptop the wifi and the internet...
[03:33] <PilotBob42> ah, good...
[03:33] <noahwheeler> set as metered connection is off
[03:34] <PilotBob42> can you ping the pi from the command line while both are on the hotspot?
[03:35] <noahwheeler> I'm not a computer programmer ! I can try but if I switch to hotspot I will lose the connection here again
[03:36] <PilotBob42> didn't you say you had a laptop too? you can't take your desktop into the field...
[03:36] <noahwheeler> okay so pc , and pi are on the hotspot at the same time ? correct ?
[03:36] <PilotBob42> How are you getting here? on the Pi or the PC?
[03:37] <noahwheeler> I have an Ubuntu 17.10 laptop but I havn't got it involved yet just the phone , and the pi , and the desktop
[03:37] <noahwheeler> I'm here on the Pi
[03:38] <noahwheeler> this is the pi
[03:38] <noahwheeler> actually with monitor , keyboard, and mouse
[03:38] <PilotBob42> So the Pi and the PC can talk to each other when on your home wifi, right?
[03:38] <noahwheeler> connected to the drone on battery power
[03:38] <PilotBob42> which is what you are on right now, right?
[03:39] <noahwheeler> yes
[03:39] <noahwheeler> only the pi right now !!!! I can remote desktop to the pi on this wi-fi though
[03:40] <PilotBob42> I need to know if it says "private" when you have the Pi and PC on the phone hotspot... If it says "public" or "work" while you have everything connected to the hotspot then that's probably your problem.
[03:41] <noahwheeler> okay I will be back shortly
[03:47] <noahwheeler> It's set to private on the pc and personal on the pi
[03:48] <PilotBob42> hmm... did you make note of the IPs of each while on the hotspot?
[03:50] <noahwheeler> the IPV4 adress for the desktop while on the hotspot is !!!
[03:50] <noahwheeler>  ready ?<IP_ADDRESS>
[03:51] <PilotBob42> cool and the Pi?
[03:51] <noahwheeler> the ip for the pi is <IP_ADDRESS>
[03:52] <PilotBob42> Ok, so while both are connected to the hotspot, from the PC try "ping <IP_ADDRESS>"
[03:52] <PilotBob42> And from the Pi try "ping <IP_ADDRESS>"
[03:52] <PilotBob42> do these from the command line on each.
[03:53] <PilotBob42> And not the results...
[03:53] <PilotBob42> *note the results
[03:53] <noahwheeler> Okay I'm gonna lose you again I'll be back ! So I go to command promp and i ???
[03:53] <PilotBob42> yup, command prompt on each
[03:54] <PilotBob42> type the command as I put them in quotes (for each machine respectively)
[03:54] <noahwheeler> just type ping 192 ?
[03:54] <noahwheeler> okay
[03:54] <PilotBob42> PC: "ping <IP_ADDRESS>"
[03:54] <PilotBob42> Pi: "ping <IP_ADDRESS>"
[03:55] <noahwheeler> okay got it
[03:55] <noahwheeler> be back shortly
[03:55] <PilotBob42> roger
[04:00] <PilotBob42> what did ya get?
[04:01] <noahwheeler> not so good results !
[04:01] <PilotBob42> nothing but timeouts?
[04:01] <noahwheeler> from windows sent=4 recieved=1 lost=3
[04:02] <noahwheeler> (75%loss)
[04:02] <noahwheeler> From Pi to windows 100% loss
[04:02] <PilotBob42> oh wow, that was unexpected. I figured it would either be 0% or 100% both ways.
[04:03] <noahwheeler> Destination host unreachable
[04:03] <PilotBob42> well, you definetely have a network issue going here.
[04:03] <PilotBob42> Either can't reach other or one or the other is deliberately blocking the traffic.
[04:04] <noahwheeler> HMM
[04:04] <noahwheeler> should I call Tmobile ?
[04:04] <noahwheeler> Or Root the phone ?
[04:05] <PilotBob42> well, I will say this. I wouldn't bother putting to much effort into troubleshooting this with the desktop if that is not the device you are going to be using in the field. I would try this with that Ubuntu laptop you mentioned as that is what really needs to work.
[04:05] <PilotBob42> well, if Tmobile said they aren't blocking traffic in the phone then I would say trust that they are correct (so no need to root phone).
[04:08] <noahwheeler> Okay so I need to start to program the laptop with the pi and figure on bringing it along for the field trip which is fine ! I was hoping just to hotspot with the phone and ssh with the phone to the pi and run the programm ???
[04:09] <PilotBob42> I'd fire up that laptop, connect both it and the Pi to the hotspot. record the IPs and try the whole ping experiment again (with the new IPs). Cumbersome I know, but it's important to realize that your hotspot will probably give each a new IP quite frequently. So even if it works you need to get used to checking the IPs every time.
[04:10] <PilotBob42> Well, nothing says you can't try it all from the comfort of your home, just use the hotspot and not the home wifi (and the laptop and not your PC).
[04:13] <noahwheeler> Okay Pilotbob42 I'm going to fire up the Dell latitude E6400 running Ubuntu 17.10 , and make all the connections , and see what happens I will ping the adresses , and get back to you tomorrow , and let you know the results ... Tomorrow is going to be below zero here so I will do this , and get some rest for the chilling work day I will return tomorrow ... see you then
[04:14] <PilotBob42> ok, good luck! I do think we've narrowed it down to a network issue. Hoping if it's linux to linux you'll get the result you're looking for. hope to cacth you tomorrow with good news.
[04:15] <noahwheeler> Heck yeah !! see you tomorrow over , and out ...
[07:17] <dantec> helloooo
[07:17] <dantec> it took me 4 hours to find an OS that would work on an old laptop of mine
[07:18] <dantec> And This one finally worked... Mint, Ubuntu and Fedora all didn't work
[08:03] <mizzu> hi guys can i know how to cascade what i opened in the button menu bar
[16:08] <Joe43SC> Hola
[16:08] <diogenes_> hola
[18:28] <qwerty_> opi;o;o
[18:29] <qwerty_> heeey
[18:29] <qwerty_> ,jj
[20:33] <Faults> Why in earth VirtualBox is freezing Global menu? Any ideas?
[21:37] <guest-cem7ps> hey
[21:37] <guest-cem7ps> I would like some help
[21:41] <xubuntu71w> interesting
[21:42] <guest-cem7ps> I am using ubuntu mate skipped first installation and now I can not install the system, I am only running it via live session
[21:42] <guest-cem7ps> And I can not find the option to install once session is opened!
[21:42] <guest-cem7ps> Using it on raspberry pi 3 B
[21:42] <guest-cem7ps> Any idea?
[21:47] <diogenes_> guest-cem7ps, what do you mean "skipped first installation"?
[22:15] <guest-ozh3en> Hey! Me again. I meant I closed the installation
[22:17] <guest-ozh3en> and booted system
[22:22] <diogenes_> then reboot again and it should be the way it was when you first booted.
[22:22] <guest-ozh3en> no
[22:23] <guest-ozh3en> it only opens live boot
[22:23] <guest-ozh3en> I have tried this
[22:23] <diogenes_> ok then in live boot should be the installer
[22:24] <guest-ozh3en> where? I ve searched here
[22:24] <guest-ozh3en> but did not find
[22:24] <diogenes_> you searched where?
[22:25] <guest-ozh3en> on live session, as you said
[22:25] <guest-ozh3en> Could not find installer....
[22:25] <diogenes_> but did you search in the menu?
[22:25] <guest-ozh3en> yeah
[22:26] <diogenes_> ok open a terminal
[22:26] <guest-ozh3en> done
[22:26] <diogenes_> run: ls /usr/bin | grep inst
[22:28] <guest-ozh3en> output
[22:28] <guest-ozh3en> desktop-file-install
[22:28] <guest-ozh3en> dh_installxmlcatalogs
[22:28] <guest-ozh3en> easy_install
[22:28] <guest-ozh3en> easy_install3
[22:28] <guest-ozh3en> ginstall-info
[22:28] <guest-ozh3en> gst-install
[22:28] <guest-ozh3en> gstreamer-codec-install
[22:29] <guest-ozh3en> ideviceinstaller
[22:29] <guest-ozh3en> install
[22:29] <guest-ozh3en> install-info
[22:29] <guest-ozh3en> install-printerdriver
[22:29] <guest-ozh3en> instmodsh
[22:29] <guest-ozh3en> session-installer
[22:30] <diogenes_> maybe run: sudo -s install
[22:32] <guest-ozh3en> don t know pass
[22:32] <guest-ozh3en> sudo pass
[22:32] <diogenes_> no password
[22:32] <guest-ozh3en> is there a default for live session?
[22:32] <diogenes_> just enter
[22:32] <guest-ozh3en> sorry, try again
[22:32] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:32] <guest-ozh3en> Sorry, try again.
[22:32] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:34] <diogenes_> try su or sudo no clue, live should no have pswd
[22:35] <guest-ozh3en> guest-ozh3en@ubuntu-mate:~$ su -s install
[22:35] <guest-ozh3en> Password:
[22:35] <guest-ozh3en> su: Authentication failure
[22:36] <guest-ozh3en> guest-ozh3en@ubuntu-mate:~$ sudo -s install
[22:36] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:36] <guest-ozh3en> Sorry, try again.
[22:36] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:36] <guest-ozh3en> Sorry, try again.
[22:36] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:36] <guest-ozh3en> sudo: 3 incorrect password attempts
[22:36] <diogenes_> try linux, ubuntu, mate, ubuntu-mate
[22:37] <guest-ozh3en> none
[22:38] <guest-ozh3en> ubuntu mate site would not have some clue?
[22:38] <diogenes_> sudo -i
[22:38] <diogenes_> try
[22:40] <guest-ozh3en> guest-ozh3en@ubuntu-mate:~$ sudo -i
[22:40] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:40] <guest-ozh3en> Sorry, try again.
[22:40] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:40] <guest-ozh3en> i ve tried sudo su too
[22:40] <guest-ozh3en> same shit
[22:40] <diogenes_> I mean sudo -i install and enteer
[22:42] <guest-ozh3en> sudo -i install
[22:42] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:42] <diogenes_> enter
[22:43] <guest-ozh3en> guest-ozh3en@ubuntu-mate:~$ sudo -i install
[22:43] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:43] <guest-ozh3en> Sorry, try again.
[22:43] <guest-ozh3en> [sudo] password for guest-ozh3en
[22:43] <diogenes_> ok press ctrl+alt+F1-6 just type ubuntu-mate and hit enter twice
[22:43] <guest-ozh3en> sudo -i install
[22:43] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:43] <guest-ozh3en> Sorry, try again.
[22:43] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:43] <guest-ozh3en> Sorry, try again.
[22:43] <guest-ozh3en> [sudo] password for guest-ozh3en:
[22:43] <guest-ozh3en> sudo: 3 incorrect password attempts
[22:43] <guest-ozh3en> guest-ozh3en@ubuntu-mate:~$
[22:43] <diogenes_> ^^
[22:43] <diogenes_> look up
[22:44] <guest-ozh3en> fuck, my keyboard does not contain F1 - F6
[22:44] <guest-ozh3en> Using a BT one
[22:44] <diogenes_> i meant f1
[22:44] <guest-ozh3en> I know
[22:45] <diogenes_> ok you might try burning the pendrive again
[22:49] <guest-ozh3en> or maybe login with ubuntu-mate user on grpical
[22:49] <guest-ozh3en> graphical interface
[22:49] <guest-ozh3en> I ve seen here at forum
[22:49] <guest-ozh3en> https://ubuntuforums.org/showthread.php?t=2367455&page=2
[22:50] <guest-ozh3en> gonna try this, bye
[22:50] <diogenes_> ok


[20:19] <Pici> nottrobin: you should be all set now
[20:23] <nottrobin> Pici: sounds good. How do I use this ownership to make myself op?
[20:23] <Pici> nottrobin: /msg chanserv op #ubuntu-website nottrobin
[20:23] <nottrobin> nice
[20:24] <nottrobin> Pici: thanks so much
[20:26] <Pici> nottrobin: We have a few things on the wiki for new operators, take a look at https://wiki.ubuntu.com/IRC/IrcTeam/OperatorGuidelines and https://wiki.ubuntu.com/IRC/CreatingChannels (obviously this channel was already created, but some of the other stuff in there is helpful)
[20:26] <Pici> Feel free to trop by #ubuntu-irc if you need any help
[20:26] <Pici> later :)


[00:05] <olly_> morning
[00:14] <mwhudson> hads: that's even more expensive than the telyhd :)
[00:14] <mwhudson> but yeah, it's not a super crazy idea
[00:15] <G> fwiw, I think some of the older smarter TVs can do it too
[00:15] <G> our Sony Bravia TV (now 2 - i think - iterations old) has a Skype app, iirc you could purchase a camera attachment for it
[00:23] <G> yeah, $150 add-on device
[00:29] <G> mwhudson: possible: Logitech TV Cam HD (noticed it mentioned on the xbox forums of all places)
[00:29] <mwhudson> yeah, that's in the skype store too
[00:29] <mwhudson> it's only a little cheaper
[01:11] <G> yeah, 200 according to priceme it seems
[19:30] <ibeardslee> morning
[20:35] <ajmitch_> morning
[21:10] <G> morning
[21:22] <olly_> morning
[21:24] <thumper> morning
[21:38] <hads> morn
[21:58] <chilts_> morning
[22:12] <G> hads: hey who do you get to make your PCBs?  (Also what do you design them with?)
[22:14] <G> I need to make two Arduino Mega shields, but the free Eagle doesn't work with Arduino Megas due to the size


[09:36] <zyga> o/
[09:56] <sdhd-sascha> hi
[09:56] <sdhd-sascha> It would be nice, if snapd could overlay mount directories. At least read-only.
[09:57] <zyga> sdhd-sascha: as in overlayfs?
[09:57] <zyga> sdhd-sascha: hey :)
[09:57] <sdhd-sascha> E.g. mount /usr/share/fonts from snap A on snap B
[09:57] <sdhd-sascha> yes
[09:57] <sdhd-sascha> zyga: :)
[09:58] <zyga> sdhd-sascha: unfortunately we cannot use overlayfs because it doesn't support apparmor (or vice versa)
[09:58] <sdhd-sascha> zyga: What does apparmor do or not do?
[10:01] <sdhd-sascha> zyga: can't find any bug-report about overlayfs and apparmor. What's not working?
[10:02] <zyga> There are no LSM hooks in overlayfs that would make it work correctly with apparmor
[10:02] <zyga> I don’t know if there is a bug report about it but this is my understanding after discussing this topic with apparmor kernel developers
[10:03] <zyga> I just realized I am off today as well
[10:03] <zyga> I’ll make coffee and clean the kitchen a little
[10:03] <zyga> This end of year holiday is an excellent way to rest and reset
[10:04] <sdhd-sascha> :)
[10:05] <zyga> Apparmor is almost entirely path based
[10:05] <sdhd-sascha> I patched the last bug in sway-source in my repo. Now Xwayland starts inside strict sway :) The problem was, that sway want access to /dev/shm/wlroots-...
[10:05] <zyga> And overlayfs has some hooks that make it work with inode based LSMs like SELinux
[10:06] <sdhd-sascha> zyga: thank you.
[10:08] <sdhd-sascha> oh, didn't upload the current sway snapcraft.yaml, yet.
[16:36] <mup> Bug #1857358 opened: Not yet operational on Fedora systems <fedora> <Snappy:New> <https://launchpad.net/bugs/1857358>


[01:06]  * ajmitch wonders how many people were spammed
[01:52] <Atamira> i was
[02:24] <zapzupnz> i wasn't
[04:15] <zapzupnz> I did get VERSIONed, though, I see
[04:32] <G> ajmitch: I was spammed as well, but was easy enough to just /win close
[04:42]  * hads too


[17:20] <genii> Will there be any more omap4 ? I can't seem to find any version past 12.04
[17:23] <infinity> genii: http://cdimage.ubuntu.com/netboot/14.04/
[17:23] <infinity> genii: armhf has a pandaboard netboot image.
[17:24] <genii> infinity: I'm currently trying to install on TI Blaze tablet reference platform.
[17:24] <genii> Thanks for the info.


[22:46] <mamarley> tseliot: What's the plan for how to handle nvidia-340 with GLVND-enabled Mesa?
[22:48] <tseliot> mamarley: I think I'll use diversions for libGL.so*, and xorg.conf.d snippet for libglx.so. I haven't played with it yet. I think I'll look into it tomorrow
[22:49] <mamarley> tseliot: OK, thanks!
[22:49] <tseliot> np
[22:50] <tseliot> mamarley: BTW hybrid switching with 390 is not going to work in bionic until this is fixed https://github.com/systemd/systemd/issues/6908
[22:50] <tseliot> I need to test the new systemd in bionic, to see if it solves the problem


[06:47] <dholbach> good morning
[06:47] <ajmitch> morning dholbach
[06:47] <dholbach> hey ajmitch
[10:13] <dholbach> tumbleweed, I guess with bdmurray_'s script running, we can close bug 782112?
[10:14] <ScottSanbar> `/window 15
[10:16] <Laney> dholbach: that script only deals with debdiffs, not just any patch (so it would still be useful)
[10:17] <Laney> also how well has the script been working from the sponsors side?
[10:17] <dholbach> oh ok
[10:17] <Laney> has it been annoying or useful?
[10:17] <dholbach> I think it's been useful
[10:17] <dholbach> at least the bugs I came across were successfully identified
[10:25] <tumbleweed> dholbach: yeah, I agree with Laney (but good to hear that the debiff script was useful)
[10:25] <dholbach> ok, so I'll leave the bug open
[10:25] <dholbach> (and assigned to you :-P)
[11:17] <gnomefreak> anyone know if we need console-terminus ntfsprogs. They have been wanting to be removed for a while now.
[11:18] <cjwatson> they have both been removed from the oneiric archive
[11:18] <cjwatson> oh, ntfsprogs hasn't
[11:18] <cjwatson> but anyway, ntfs-3g supersedes it
[11:19] <cjwatson> you can safely remove both if you're running oneiric
[11:19] <gnomefreak> cjwatson: thanks
[15:46] <micahg> can anyone actually get mk-build-deps -ir to work?
[15:47] <Laney> -i -r
[15:47] <Laney> also sudo
[15:49] <micahg> Laney: ah, ISTR the changelog saying -ir hence the confusion
[15:49] <Laney> cannae remember
[15:57] <PeaceMaker> Hey, anyone please help me with Unity on Ubuntu 11.04 server?
[15:57] <PeaceMaker> Can I install unity after I install the server version?
[15:58] <PeaceMaker> With command "sudo aptitude install ubuntu-desktop", like the way in pre-unity versions?
[16:00] <cjwatson> yes
[16:00] <PeaceMaker> Ouch, I should have asked in the general channel :)
[16:56] <jtaylor> can I do remote debugging with pbuilder-dist arm chroot?
[17:20] <jtaylor> figured it out
[17:38] <blackz> hi people
[18:06] <ScottK> Hello blackz.
[18:36] <ScottSanbar> I have createda  hello app (not Gnu Hello) but the launchpad recipe build does not contain the binary and man page files.  Using debuild on my PC works fine: https://launchpadlibrarian.net/80346820/buildlog_ubuntu-natty-i386.hello_1.0-0~12~natty1_BUILDING.txt.gz  http://bazaar.launchpad.net/~scott-sanbar/hello/main/files
[18:37] <ScottSanbar> First link above is the recipe build log, second are my branch files in launchpad for the project
[21:46] <uiea> hello
[22:13] <ScottK> ScottSanbar: #launchpad is a much better place to ask about recipe builds.
[22:20] <ScottSanbar> ScottK:  Thanks, and how are you?  That is the first place I went and #ubuntu-packaging as well, but got nothing, so after a while came here.  Nothing in any of the three places at all after a good while now.
[22:20] <ScottK> OK.
[22:21] <ScottK> shadeslayer knows a lot about recipes, I think.
[22:21] <ScottSanbar> OK, is there a way I can find out if he is on a freenode channel and if so which one without knowing at first, like a query?  I use irssi.
[22:22] <cjwatson> /whois shadeslayer
[22:23] <cjwatson> but I can't help noticing that he's on *this* channel ;-)
[22:23] <cjwatson> (/names, or tab-complete)
[22:25] <tumbleweed> I don't think this problem is recipe-related. Your debian/rules doesn't have a #!/usr/bin/make -f shebang
[22:28] <ScottSanbar> cjwatson: he appears to be gone on every channel I have checked so far ...
[22:29] <cjwatson> away state is channel-independent
[22:29] <cjwatson> (obviously.  if he's not at his computer, he's not at his computer on any channel.)
[22:29] <ScottSanbar> cjwatson:  Ok, thanks
[22:29] <cjwatson> but IRC is asynchronous.  ask question now, expect answer later :)
[22:29] <ScottSanbar> tumbleweed: ok, thanks - I'll give it a shot.
[22:31] <ScottSanbar> cjwatson:  yes, its been a while since I put up the questions.  I may need to repost them again after a while so they will be on people's screens ...
[22:31] <ajmitch> tumbleweed: the build log shows it running through the normal dh sequence
[22:32] <ScottSanbar> ajmitch: what does that mean?
[22:33] <tumbleweed> ajmitch: that's a point, I saw the 4: %:: not found and got distracted by that
[22:33] <ajmitch> that it ought to be fine, I don't think the absence of a hello.install file should matter for a single-binary package
[22:34] <ScottSanbar> tumbleweed:  I was wondering about those warnings as well, but found nothing with google
[22:35] <tumbleweed> my best bet for that is the shebang, but I don't have time to sit down and look at this now, sorry. /me -> bed
[22:39] <ScottSanbar> tumbleweed:  Thanks for your help - I will try the shebang very soon.  Right now I go out with my son to eat - a special occasion for me!
[22:41] <ScottSanbar> ajmitch:  How does the package look overall?  It is just a learning exercise for me, not something that will ever be published, so I would welcome feedback on it.
[22:41] <ScottSanbar> cjwatson: CC:
[22:41] <cjwatson> I haven't looked at it, sorry, this was just drive-by IRC commentary
[22:41] <ScottSanbar> cjwatson: oh,ok - no problem.  Thanks for your help.
[22:46] <ajmitch> ScottSanbar: sorry, haven't taken much of a look at it beyond that, though there's nothing that jumps out at me as being wrong


[03:07] <argel> has anyone experienced losing internet connection on your google-chrome (everything else is connected, except chrome)?
[03:08] <argel> I noticed it happens a lot if I load gmail.
[07:57] <xubuntu12d> network monitor
[18:43] <Lokie> on xubuntu 18.04 (or in xfce in general I guess) is it possible to scale everything up? So far I 've seen increasin font dpi via settings-manager but that means you have to fix it per application as well
[18:53] <diogenes_> Lokie, maybe lower down the resolution? because afaik so far xfce isn't quite ready to HIDPI monitors
[19:16] <Spass> scaling is slightly better in 18.10 (Xfce 4.13), but if you want/have to stay on LTS, you'll need to put some work to it
[19:17] <Spass> we (polish xubuntu community) even created a quick guide showing how to achieve this - https://xubuntu-pl.neocities.org/porady/powiekszenie-interfejsu.html
[22:32] <gnrp> Lokie: I use xubuntu 18.04 on a high-dpi screen, but no problems with that. Yes, it is cumbersome for some programs to set it, but how does that work with other window toolkits?
[22:32] <gnrp> I mean, dpi is set for all gtk programs. Then, wine programs of course need their own dpi and stuff like browsers and java programs, but it's like that with every toolkit, isn't it?


[00:00] -queuebot:#ubuntu-release- New: accepted dhcpcd5 [amd64] (lunar-proposed) [9.4.1-12]
[00:00] -queuebot:#ubuntu-release- New: accepted lomiri-indicator-network [amd64] (lunar-proposed) [1.0.0~git20221216.698b753-2]
[03:17] <zhsj> please retry yggdrasil autopkgtest, it was badpkg state, dependencies should be avail now. (btw is the right channel for such request?
[04:36] <tjaalton> RAOF: hey, does your semi-AA powers allow to remove packages from proposed?
[04:37] <RAOF> tjaalton: My full-AA powers definitely do :)
[04:37] <RAOF> What can I do you for?
[04:37] <tjaalton> ooh
[04:37] <sarnold> muaahahahahahaha
[04:38] <tjaalton> removr directx-headers from jammy-proposed, so that the current mesa sru could build on amd64/arm64
[04:39] <tjaalton> can be added back later when that one has migrated to updates
[04:39] <arraybolt3> RAOF: Hey, whenever you get a free moment, are you available for SRU vanguard stuff? sil2100 never replied to my last ping.
[04:40] <tjaalton> then mesa from jammy queue can be dropped
[04:41] <tjaalton> RAOF: should be safer this way than patching mesa to build
[04:41] <arraybolt3> (Sorry, failed to check timestamps, didn't realize I was interrupting something else.)
[04:41] <RAOF> tjaalton: Seems reasonable.
[04:44] <RAOF> tjaalton: Is this request documented in any bug (eg: #1991761)?
[04:48] <RAOF> arraybolt3: What's your SRU request? I don't have context.
[04:49] <arraybolt3> RAOF: https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2002255
[04:49] -ubottu:#ubuntu-release- Launchpad bug 2002255 in lubuntu-update-notifier (Ubuntu Jammy) "lubuntu-update-notifier provides no good way to resolve a forcibly terminated system update" [Critical, In Progress]
[04:52] <RAOF> You want that accepted into {jammy,kinetic}-proposed?
[04:52] <arraybolt3> Yes please.
[04:52] <arraybolt3> I already uploaded it.
[04:55] <RAOF> tjaalton: directx-headers removed from proposed; time to get your mesa on!
[04:57] <tjaalton> RAOF: thanks! no this approach is something I didn't think of first
[04:59] -queuebot:#ubuntu-release- Unapproved: rejected mesa [source] (jammy-proposed) [22.0.5-0ubuntu0.4]
[05:00] <RAOF> arraybolt3: So, "the update mechanism needs new features to make updates not broken" is something that we're generally sympathetic to in SRU-land. It would *also* be good to make the sddm update not trigger the updater-hangs-indefinitely bug.
[05:00] <tjaalton> RAOF: I'll kick the builds once the archive is settled
[05:00] <RAOF> (This should be possible, at-worst with the terrible hammer of Pre-Depends?)
[05:00] <arraybolt3> RAOF: The problem is that SDDM didn't do anything wrong here. All it does is trigger a perfectly normal prompt that is supposed to be handled by the end user. The fact that lubuntu-update-notifier couldn't handle it beofre is 100% lubuntu-update-notifier's fault.
[05:01] <arraybolt3> As for Pre-Depends, we sorta tried that, sadly enough.
[05:01] <arraybolt3> (Basically we tried to Pre-Depends on lubuntu-update-notifier in lubuntu-desktop to try and force it to install and configure first, which failed. And we can't Pre-Depends on lubuntu-update-notifier in SDDM since SDDM is used in Kubuntu, which would be damaged by the introduction of lubuntu-update-notifier.)
[05:01] <RAOF> Oh, right! That'll ensure the new l-u-n is installed and configured, but the broken process is *already running)
[05:02] <arraybolt3> Right. And apt apparently is like "Sure, I'll configure l-u-n first, then lubuntu-desktop! Just lemme configure SDDM first." :-/
[05:04] <RAOF> Yeah, it's *not possible* for apt to do what you need there, which is "sddm is not an update candidate until the version of l-u-n *that is running* is at least $FOO"
[05:06] <RAOF> arraybolt3: You've missed a `-v0.4` in your package build flags; the .changes file doesn't include the relevant changelog entries or LP bug reference.
[05:07] <arraybolt3> RAOF: The LP bug reference is actually in the *previous* version, the real version that's in Lunar. Are duplicate LP: #XYZ entries allowable, or is the one in the Lunar version enough?
[05:07] <RAOF> The one in the lunar version is enough, but it needs to make it into the .changes file.
[05:08] <arraybolt3> OK... so, this is something I've not done before - do I manually edit the .changes files? I currently generate them with debuild.
[05:10] <arraybolt3> (Sorry, I didn't know that the reference being in the .changes file was a requirement. The SRU docs only require that "there is a reference to the SRU bug number in the changelog", which I did. This is my first SRU, so I'm not exactly experienced at this yet.)
[05:10] <RAOF> You need to pass -v$PREVIOUS_ARCHIVE_VERSION to debuild.
[05:10] <RAOF> In this case, -v0.4 looks to be the right incantation.
[05:10] <arraybolt3> Oh. That's what you mean by build flags. OK. Thanks, I'll do that real quick.
[05:10] <RAOF> That means "include all changelog entries since 0.4 in the .changes file".
[05:12] -queuebot:#ubuntu-release- Unapproved: rejected lubuntu-update-notifier [source] (jammy-proposed) [0.5.1~22.04.1]
[05:14] -queuebot:#ubuntu-release- Unapproved: lubuntu-update-notifier (jammy-proposed/universe) [0.4 => 0.5.1~22.04.2] (lubuntu)
[05:14] <arraybolt3> RAOF: I think you'll probably want to reject 0.5.1~22.10.1 also.
[05:15] <RAOF> I do indeed; just waiting for the tooling to catch up :)
[05:15] <arraybolt3> Ah, makes sense. Thanks for your patience with me while I'm learning how this works.
[05:16] -queuebot:#ubuntu-release- Unapproved: rejected lubuntu-update-notifier [source] (kinetic-proposed) [0.5.1~22.10.1]
[05:17] -queuebot:#ubuntu-release- Unapproved: lubuntu-update-notifier (kinetic-proposed/universe) [0.4 => 0.5.1~22.10.2] (lubuntu)
[05:19] <RAOF> We need to edit the test-case, of course, to not test the PPA packages :)
[05:19] <arraybolt3> Good point, will do.
[05:24] -queuebot:#ubuntu-release- New binary: securestring [amd64] (lunar-proposed/universe) [0.2-2] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: securestring [arm64] (lunar-proposed/universe) [0.2-2] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: securestring [armhf] (lunar-proposed/universe) [0.2-2] (no packageset)
[05:27] -queuebot:#ubuntu-release- New binary: securestring [ppc64el] (lunar-proposed/universe) [0.2-2] (no packageset)
[05:28] <arraybolt3> Test cases updated.
[05:29] -queuebot:#ubuntu-release- New binary: securestring [s390x] (lunar-proposed/universe) [0.2-2] (no packageset)
[05:36] -queuebot:#ubuntu-release- Unapproved: accepted lubuntu-update-notifier [source] (jammy-proposed) [0.5.1~22.04.2]
[05:37] -queuebot:#ubuntu-release- Unapproved: accepted lubuntu-update-notifier [source] (kinetic-proposed) [0.5.1~22.10.2]
[05:42] -queuebot:#ubuntu-release- New: accepted securestring [amd64] (lunar-proposed) [0.2-2]
[05:42] -queuebot:#ubuntu-release- New: accepted securestring [armhf] (lunar-proposed) [0.2-2]
[05:42] -queuebot:#ubuntu-release- New: accepted securestring [s390x] (lunar-proposed) [0.2-2]
[05:42] -queuebot:#ubuntu-release- New: accepted securestring [arm64] (lunar-proposed) [0.2-2]
[05:42] -queuebot:#ubuntu-release- New: accepted securestring [ppc64el] (lunar-proposed) [0.2-2]
[05:50] <arraybolt3> RAOF: Thank you for everything!
[05:57] -queuebot:#ubuntu-release- New binary: securestring [riscv64] (lunar-proposed/universe) [0.2-2] (no packageset)
[06:38] <LocutusOfBorg> hello ubuntu-archive, please old binaries left on amd64: librocksdb7.7 (from 7.7.8-1)
[06:40] <LocutusOfBorg> ack vorlon thanks
[06:43] <LocutusOfBorg> vorlon, https://ci.debian.net/packages/b/bernhard/unstable/arm64/
[06:43] <LocutusOfBorg> it always failed in debian too
[06:45] <LocutusOfBorg> so maybe we can just hint it?
[06:46] <LocutusOfBorg> (I know its a regression, I'm taking a look anyway, sad that Debian is failing for different reasons)
[06:53] <LocutusOfBorg> a no change rebuild of bernhard works
[06:54] <LocutusOfBorg> oh... pb.py is the culprit
[06:55]  * LocutusOfBorg opens an RC in Debain
[06:57] <LocutusOfBorg> so if you can restore protobuf, I can issue the rebuild
 Opened #1028371 in src:bernhard by Gianfranco Costamagna (locutusofborg) «bernhard: needs rebuilds on top of new protobuf». https://bugs.debian.org/1028371
[07:04] -ubottu:#ubuntu-release- Debian bug 1028371 in src:bernhard "bernhard: needs rebuilds on top of new protobuf" [Serious, Open]
[08:51] -queuebot:#ubuntu-release- Unapproved: directx-headers (jammy-proposed/universe) [1.600.10-1 => 1.606.4-1~ubuntu<IP_ADDRESS>] (no packageset)
[08:51] <tjaalton> ^ this is the same that RAOF removed on request
[08:52] <tjaalton> sil2100: so, getting back to the mesa hwe backport.. it'd be time to build the second upload of llvm-15
[08:53] -queuebot:#ubuntu-release- New: accepted securestring [riscv64] (lunar-proposed) [0.2-2]
[08:53] <sil2100> tjaalton: o/
[08:53] <tjaalton> also directx-headers from above
[08:53] <sil2100> tjaalton: ok, I have an interview in a moment, after that I'll poke you and we can get things reviewed/accepted
[08:53] <tjaalton> ack
[09:49] <ricotz> hello :), are the s390x autopkgtests meant to be working again? it looks like they are still looping?
[09:52] <seb128> ricotz, hey, those were working for a bit and are having issues again, bdmurray and paride are working with IS on the issue
[09:53] <ricotz> seb128, hey :), thank you
[09:53] <seb128> np!
[10:02] <LocutusOfBorg> hello ubuntu-archive, please old binaries left on amd64: librocksdb7.7 (from 7.7.8-1)
[10:02] <LocutusOfBorg> NBS cleanup please?
[10:17] <seb128> LocutusOfBorg, it's not only amd64, removed
[10:23] <sil2100> tjaalton: ok, so I'll review the llvm15 and directx-headers uploads in the queue - anything else that needs review for .2?
[10:26] <LocutusOfBorg> yep thanks
[10:26] <LocutusOfBorg> merci!
[10:28] <tjaalton> sil2100: after that it is mesa itself, which I need to reupload
[10:29] <sil2100> ACK. Of course I have another meeting just now, but I'll handle that after this one ;p
[11:07] <tjaalton> heh, take your time
[11:07] <tjaalton> llvm surely will
[11:22] -queuebot:#ubuntu-release- New binary: lib2geom [amd64] (lunar-proposed/universe) [1.2.2-3] (no packageset)
[11:23] -queuebot:#ubuntu-release- New binary: lib2geom [arm64] (lunar-proposed/universe) [1.2.2-3] (no packageset)
[11:23] -queuebot:#ubuntu-release- New binary: lib2geom [ppc64el] (lunar-proposed/universe) [1.2.2-3] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: lib2geom [armhf] (lunar-proposed/universe) [1.2.2-3] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: lib2geom [s390x] (lunar-proposed/universe) [1.2.2-3] (no packageset)
[11:29] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-15 [source] (kinetic-proposed) [1:15.0.6-3~ubuntu<IP_ADDRESS>]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-15 [source] (jammy-proposed) [1:15.0.6-3~ubuntu<IP_ADDRESS>]
[11:34] <sil2100> tjaalton: hmm, the directx-headers one - the same version already built in the archive. Do you want to resurrect the old binaries?
[11:35] <sil2100> Since launchpad will reject it as is. I can either ressurect the old binaries or you'll have to no-change bump the version number
[11:36] <tjaalton> sil2100: ah, you can use the old ones
[11:42] <sil2100> Ok, rejecting the upload and ressurecting the old one then
[11:45] -queuebot:#ubuntu-release- New binary: gdcm [amd64] (lunar-proposed/universe) [3.0.20-2] (kubuntu)
[11:46] -queuebot:#ubuntu-release- Unapproved: rejected directx-headers [source] (jammy-proposed) [1.606.4-1~ubuntu<IP_ADDRESS>]
[11:48] -queuebot:#ubuntu-release- Unapproved: directx-headers (jammy-proposed/universe) [1.600.10-1 => 1.606.4-1~ubuntu<IP_ADDRESS>] (no packageset) (sync)
[11:50] -queuebot:#ubuntu-release- Unapproved: accepted directx-headers [sync] (jammy-proposed) [1.606.4-1~ubuntu<IP_ADDRESS>]
[11:54] -queuebot:#ubuntu-release- New: accepted gdcm [amd64] (lunar-proposed) [3.0.20-2]
[11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [arm64] (lunar-proposed) [1.2.2-3]
[11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [ppc64el] (lunar-proposed) [1.2.2-3]
[11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [amd64] (lunar-proposed) [1.2.2-3]
[11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [s390x] (lunar-proposed) [1.2.2-3]
[11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [armhf] (lunar-proposed) [1.2.2-3]
[12:16] <ginggs> fresh update_excuses...
[12:16] <ginggs> hello perl sync :(
[12:45] <laney> just found some old-ish messages in moderation for ubuntu-release, don't be too surprised
[13:15] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (kinetic-proposed/main) [251.2.1 => 251.4.2] (no packageset)
[13:19] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.3] (no packageset)
[13:22] <slyon> hey ubuntu-sru! Could somebody please drop systemd-hwe 249.11.2 from the Jammy unapproved queue, and systemd-hwe 251.4.1 from the Kinetic unapproved queue? Those got superseeded/bundled with 249.11.3 and 251.4.2 respectively.
[13:29] <sil2100> o/
[13:30] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (kinetic-proposed) [251.4.1]
[13:31] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.2]
[13:47] <slyon> thx!
[14:09] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (kinetic-proposed/main) [251.2.1 => 251.4.3] (no packageset)
[14:14] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.4] (no packageset)
[14:16] <slyon> sorry, there was another bug that could be bundled for those SRUs (LP: #2002065), so we can drop the old ones, again: 251.4.3/kinetic & 249.11.3/jammy ^
[14:16] -ubottu:#ubuntu-release- Launchpad bug 2002065 in systemd-hwe (Ubuntu) "Add ACCEL_LOCATION=base property for Dell machines (0C41, 0C42)" [Undecided, In Progress] https://launchpad.net/bugs/2002065
[14:25] <sil2100> No problem
[14:26] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.3]
[14:27] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (kinetic-proposed) [251.4.2]
[14:27] <slyon> thank you!
[14:40] -queuebot:#ubuntu-release- Unapproved: alsa-ucm-conf (kinetic-proposed/main) [<IP_ADDRESS>-1ubuntu2 => <IP_ADDRESS>-1ubuntu3] (core)
[15:29] <Eickmeyer> bdmurray: If it's not too much trouble, could you possibly push sru bug 1965439 for ubuntustudio-default-settings over the finish line in Jammy? I don't know where RikMills is at with it for kubuntu-settings (he probably forgot about it completely), but it's on the brink of ancient.
[15:29] -ubottu:#ubuntu-release- Bug 1965439 in kubuntu-settings (Ubuntu Jammy) "[SRU] kdesu fails to authenticate with sudo from Jammy" [High, In Progress] https://launchpad.net/bugs/1965439
[16:08] <vorlon> LocutusOfBorg: cleaned up all the "old binaries" NBS listed on update_excuses
[16:08] <LocutusOfBorg> thanks!
[16:08] <LocutusOfBorg> and if you want to restore protobuf, I can no change rebuild the library
[16:08] <LocutusOfBorg> but I can understand if you want to hold it for some bit
[16:09] <vorlon> LocutusOfBorg: yeah what I want is to get python3-defaults unblocked as quickly as possible, so first I've triggered a retest of bernhard/s390x with the archive in the current state; once that's done, we can bring protobuf and a fixed bernhard back in
[16:11] <LocutusOfBorg> thanks!
[16:11] <LocutusOfBorg> please ping once you do, so I can issue the rebuild
[16:12] <vorlon> LocutusOfBorg: I'll try to keep track of it and let you know
[16:13] <vorlon> it's s390x and the queue is still dire, so
[16:14] <vorlon> and ick, protobuf being rolled back breaks a *different* autopkgtest (bcnc) because protobuf was an soname change and now libopencv-dnn406 is uninstallable
[16:17] <vorlon> ginggs: any idea about the boost* autopkgtest regressions with python3.11?
[16:27] <ginggs> vorlon: yes, boost1.74 is fixed in 1.74.0-18.1ubuntu1
[16:28] <ginggs> and boost1.81 is fixed in...
[16:28] <vorlon> ginggs: ok then the retry I just did should take care of that one.  Does boost1.81 need the same fix?
[16:28] <ginggs> 1.74.0-18.1ubuntu1 :)
[16:28] <ginggs> because #1028390
[16:29] <ginggs> debian #1028390
[16:29] -ubottu:#ubuntu-release- Debian bug 1028390 in src:boost1.81 "boost1.81: autopkgtests test boost-defaults" [Normal, Open] https://bugs.debian.org/1028390
[16:29] <ginggs> thanks ubottu
[16:29] <vorlon> oh lol
[16:29] <vorlon> so I should retrigger that one too?
[16:29] <vorlon> (or you could hint it as badtest)
[16:33] <ginggs> ah, the test should pass with all proposed, but i can hint if you prefer
[16:35] <vorlon> ginggs: the hint would mean less need to chase it over the next days wrt e.g. s390x
[16:36] <vorlon> and that bug report says to me that the tests are invalid, so it's not wrong to have a version-specific badtest hint
[16:37] <ginggs> vorlon: ack, i'll do it
[16:40] <vorlon> coreycb: unicode-cldr-core is on https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html because python-babel-localedata is Built-Using it.  python-babel appears to be an autosynced package owned by the openstack team.  Could someone from the openstack team drive an MIR for this please?
[17:01] <ginggs> vorlon: to remove numba, did you mean you already did remove 16 source packages, or you would have to?
[17:03] <coreycb> vorlon: yes, thanks for raising this. I'll take a look.
[17:08] <vorlon> ginggs: did remove
[17:08] <vorlon> coreycb: thank you!
[17:09] -queuebot:#ubuntu-release- Unapproved: python-websockets (jammy-backports/universe) [9.1-1 => 10.2-1~bpo22.04.1] (no packageset)
[17:19] <ginggs> vorlon: ok, thanks, but numba itself not removed?
[17:19] <vorlon> ginggs: isn't it? if I didn't already remove it it's because I wanted to re-check reverse-depends output after the spate of removals
[17:20] <vorlon> ginggs: removed now
[17:20] <ginggs> vorlon: ta
[18:17] <LocutusOfBorg> new perl came just in time for me to fix nodejs merge :D
[18:17] <tsimonq2> 🎉
[18:27] <Eickmeyer> Anybody on the SRU team available? If it's not too much trouble, could you possibly push sru bug 1965439 for ubuntustudio-default-settings over the finish line in Jammy? I don't know where RikMills is at with it for kubuntu-settings (he probably forgot about it completely), but it's on the brink of ancient.
[18:27] -ubottu:#ubuntu-release- Bug 1965439 in kubuntu-settings (Ubuntu Jammy) "[SRU] kdesu fails to authenticate with sudo from Jammy" [High, In Progress] https://launchpad.net/bugs/1965439
[19:13] <bdmurray> I'm looking at ubuntustudio-default-settings.
[19:16] <bdmurray> And for the record the bug only got verified this year so the ancientness isn't on the SRU team this time.
[19:23] <Eickmeyer> bdmurray: Yeah, that was my fault. :) Last week, my time.
[19:24] <Eickmeyer> Actually, I verified it, but lost the bug and forgot it with Prague and all.
[19:25] <Eickmeyer> My fault for not marking the bug as such.
[19:52] <Eickmeyer> bdmurray: Thanks! To be clear, I wasn't blaming the SRU team for anything. Completely my fault. :)
[19:57] <bdmurray> Sometime the SRU team is a bottleneck, just not this time!
[20:04] <Eickmeyer> :)
[20:43] <vorlon> schopin, athos: hi, I just want to check if the both of you are focused on python3-defaults migration this week for +1 (find-proposed-cluster ;), and if we should coordinate at all to divide and conquer
[21:20] <athos> I supposed someone else would focus on that. I ran your new script and decided to tackle some rust stuff, considering someone would go for python3-defoaults. Should I abort and fall back to python3-defaults? :)
[21:21] <athos> vorlon: thanks for the test hint on postgresql-common yesterday, btw :)
[21:33] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.2] (no packageset)
[21:34] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.4]
[21:44] -queuebot:#ubuntu-release- Unapproved: accepted ca-certificates-java [source] (jammy-proposed) [20190909ubuntu1.1]
[22:14] -queuebot:#ubuntu-release- Unapproved: accepted systemd-hwe [source] (kinetic-proposed) [251.4.3]
[22:15] -queuebot:#ubuntu-release- Unapproved: accepted systemd-hwe [source] (jammy-proposed) [249.11.2]
[22:59] <vorlon> athos: python3-defaults is bigger by an order of magnitude and there's plenty of work to go around; and the longer it stays the more it risks entanglement with other transitions
[23:29] -queuebot:#ubuntu-release- New binary: netpbm-free [amd64] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)
[23:30] -queuebot:#ubuntu-release- New binary: netpbm-free [i386] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)
[23:33] -queuebot:#ubuntu-release- New binary: elpa [amd64] (lunar-proposed/universe) [2022.11.001-2] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: netpbm-free [ppc64el] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)
[23:37] -queuebot:#ubuntu-release- New binary: netpbm-free [s390x] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)
[23:41] -queuebot:#ubuntu-release- New binary: elpa [s390x] (lunar-proposed/universe) [2022.11.001-2] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: elpa [ppc64el] (lunar-proposed/universe) [2022.11.001-2] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: netpbm-free [arm64] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)
[23:44] -queuebot:#ubuntu-release- New binary: elpa [arm64] (lunar-proposed/universe) [2022.11.001-2] (no packageset)
[23:44] -queuebot:#ubuntu-release- New binary: netpbm-free [armhf] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)
[23:46] -queuebot:#ubuntu-release- New: accepted elpa [amd64] (lunar-proposed) [2022.11.001-2]
[23:46] -queuebot:#ubuntu-release- New: accepted elpa [ppc64el] (lunar-proposed) [2022.11.001-2]
[23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [amd64] (lunar-proposed) [2:10.98.00-1]
[23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [armhf] (lunar-proposed) [2:10.98.00-1]
[23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [ppc64el] (lunar-proposed) [2:10.98.00-1]
[23:46] -queuebot:#ubuntu-release- New: accepted elpa [arm64] (lunar-proposed) [2022.11.001-2]
[23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [arm64] (lunar-proposed) [2:10.98.00-1]
[23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [s390x] (lunar-proposed) [2:10.98.00-1]
[23:46] -queuebot:#ubuntu-release- New: accepted elpa [s390x] (lunar-proposed) [2022.11.001-2]
[23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [i386] (lunar-proposed) [2:10.98.00-1]
[23:52] -queuebot:#ubuntu-release- New binary: elpa [armhf] (lunar-proposed/universe) [2022.11.001-2] (no packageset)


[01:30] <guiverc> I like how formatted General Community News Bashing-om
[01:32] <Bashing-om> guiverc: Just thought a handy way to present :D
[01:54] <guiverc> my read thru complete; you cleaned it up good Bashing-om
[01:56] <Bashing-om> guiverc: Pleased you and my wife agree :P
[01:57] <guiverc> :)
[16:42] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Is a JingOS Linux Phone Coming? This Video Hints at the Possibility @ https://www.omgubuntu.co.uk/2021/04/jingos-linux-phone-video-demo (by Joey Sneddon)
[19:24] <Bashing-om> UWN: Pulling "WIP" - Time to push 20:00 UTC. Checked log and no further edits are known.
[20:00] <Bashing-om> UWN: ubuntu-news@lists is away - doing the Forum post next :D
[20:04] <Bashing-om> UWN: Forum post done - No issues seen - doing the re-directs next :D
[20:15] <Bashing-om> UWN: Re-directs completed - pending is release to the Social Medias :D
[22:06] <guiverc>   cd uwn
[22:06] <guiverc> sorry that was intended for term
[22:07] <kryten> LOL XD
[22:12] <Bashing-om> guiverc: UWN - when you are awake :P
[22:12] <guiverc> i'm doing fridge checks now, okay to push when complete (I would have said that on completion)
[22:13] <Bashing-om> guiverc: Yup - push to the Fridge when ready - no known issues :D
[22:14] <guiverc> https://fridge.ubuntu.com/2021/04/05/ubuntu-weekly-newsletter-issue-677/
[22:15] <guiverc> tweeted
[22:17] <Bashing-om> Fridge spot check, checks good :D
[22:26] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu Weekly Newsletter Issue 677 @ https://fridge.ubuntu.com/2021/04/05/ubuntu-weekly-newsletter-issue-677/
[22:31] <guiverc> fb posted finally too
[22:32] <Bashing-om> guiverc: Great - good job - clear now to wipe Gdoc ?
[22:33] <guiverc> yep.
[22:33] <Bashing-om> doing ^
[22:40] <Bashing-om> UWN: We do issue 678 :D
[23:47] -SwissBot:#ubuntu-news- ::Planet:: Kees Cook: security things in Linux v5.9 @ https://outflux.net/blog/archives/2021/04/05/security-things-in-linux-v5-9/


[08:21] <lordievader> Good morning
[14:33] <user|60216> hello world!)
[14:34] <user|60216> need sources.list for 19.10
[14:36] <user|60216> a beer of course)
[14:37] <user|60216> Dear, well, it is very necessary
[14:46] <BluesKaj> Howdy folks
[15:34] <user|60216> how about sources.list
[19:23] <mint> i. I had several unclean shutdowns due to a program that i was running. Now my cinnamon mint will not boot up to desktop. I have a encrypted hard drive, When i  bootup it do the decryption and wait continue to load and hangs with the logo. I can enter  enter the console and log in.   Even the  wifi connection works from the console. startx does not work either. i see a message like ould not find key with description: [c82106472434e764]  ....
[19:23] <mint> [19:22] <mint> and Could not find valid key in user session keyring for sig specified in mount  etc... but i am not sure it was there or as a results of this.... How do i recover the desktop ? any help will be great... i am now in  the same machine with live boot.
 guys? does anybody know how to set the default file explorer in the KDE taskbar widget that mounts drives and usb keys? … I just uninstalled dolphin (ruby? doh! and also very poor support for network storage) and now it just opens `gwenview` instead of the damn Caja I have installed just for that reason... … Thanks to everyone in advance!
 @BJPGameVideosITA, on system settings you have a menu item called "Applications" and then you will have where to set default applications , included a file manager
 @BJPGameVideosITA, In KDE you have a plasmoid to manage connected devices, in the default settings is on the "system tray" and is hidden by default to show up just when devices are connected, anyway you can change this behavior
 @Alessandro, I wrote that help asking message because I had already tried setting Caja as default application for file management and I have even uninstalled Dolphin... it seems that that system tray for drives and usbs doesn't want to work with caja...
 @BJPGameVideosITA, you are welcome, but I'm sorry I couldn't help you 🤷♂
[21:42] <keithzg-M> @BJPGameVideosITA: Have you rebooted (or at least logged out of your session and logged back in) since changing the default?
[21:43] <keithzg-M> Might also be an association set in System Settings > Applications > File Associations, although unfortunately I can't remember off the top of my head which one that might be
 keithzg-M: My PC crashed at least twice because I'm still on magnetic HDD and since in Linux EVERYTHING is a file, apparently a Windows virtual machine on a Linux host on a 5400rpm mechanical hard drive, are not best friends... … short answer: yes, tried.. I'm sorry...
[21:55] <keithzg-M> @BJPGameVideosITA I've definitely run stacks like that before without crashes, hell there's a machine like that at work . . . if it's actually crashing you might want to run some disk checks (and I mean low-level stuff, using `smartctl` or such)
[21:56] <keithzg-M> @BJPGameVideosITA: But also, see my second suggestion.
 Will try that in a second, Keithzg-M!
 Thanks!
[22:33] <taufik> hello
[22:33] <taufik> help
[22:33] <taufik> -/help
[22:34] <bprompt> `ask
[22:34] <bprompt> !ask


[03:40] <FourDollars> How do I use Launchpad API to list all git repository under some person or some team? For example, https://code.launchpad.net/~fourdollars/+git.
[15:15] <xnox> aw, left.
[16:05] <SpecialK|Canon> Indeed
[16:41] <xnox> it's so lovely with lcy builders back =)
[16:45] <xnox> SpecialK|Canon:  19 out of 30 bos02 ppc64le builders are stuck in cleaning state for more than 5/7/12 hours.
[16:45] <xnox> is this a known issue?
[16:46] <xnox> builders 1,4,5,6,7,9,10,11,14,15,16,18,19,21,22,23,24,26,27
[16:47] <xnox> i guess it's out of hours, i can file an RT ticket.
[17:03] <SpecialK|Canon> xnox: Getting them looked at now
[17:21] <SpecialK|Canon> And they should all be back, thanks for the heads up
[18:51] <sarnold> wow, irccloud closes connections for inactivity with less than five hours!? matrix only recently started parting people from channels after 30 days inactivity (or maybe it's actual dicsonnects?) ...
[18:51] <sarnold> .. I'm sure there's a happy medium in there somewhere


[00:00] <wgrant> Ah, ls-lR is done in Python, not with run-parts, so we could parallelise that without too much work.
[00:00] <cjwatson> For values of "done in Python" including "Python that calls horrible self.executeShell", yes
[00:01] <wgrant> Well, yes, but the stuff under run-parts is opaque to us.
[00:01] <wgrant> So this is probably better :)
[00:01]  * cjwatson wishes this at least used the subprocess module, but there you go
[00:02] <wgrant> Oh, it uses os.system!?
[00:02] <wgrant> Ew.
[00:02] <wgrant> This is brand new code, too.
[00:02] <wgrant> Ah
[00:02] <wgrant>         This won't just load an external program and run it; the command
[00:02] <wgrant>         line goes through the full shell treatment including variable
[00:02] <wgrant>         substitutions, output redirections, and so on.
[00:02] <wgrant> Not the best of justifications, but at least it's something.
[00:03] <cjwatson> The only real justification I can see is that it logs something you can copy and paste as shell, but given how little of Launchpad that applies to I don't think that's much of an excuse
[00:03] <cjwatson> It would probably be better for the caller to just do it itself using subprocess and kill that abstraction
[00:04] <wgrant> Indeed.
[00:05] <cjwatson> Anyway; the ideal management-level justification for me would be if this work let us run the publisher every 30 minutes, or at least brought us substantively closer to that
[00:05] <wgrant> Yep.
[00:06] <cjwatson> (Since the driver for this is Kate and Rick pointing out that the image build pipeline is much longer than it ought to be)
[00:06] <wgrant> I think we'd get some runs in if we added a :32 run right now. But not all of them.
[00:07] <cjwatson> You would have got at most three extra runs from that today
[00:07] <wgrant> There we go, much better logging now.
[00:07]  * wgrant watches.
[00:07] <cjwatson> Well, I suppose the publisher might have been a bit quicker with less to do, so maybe slightly more
[00:08] <wgrant> We'll have some better numbers in 20 minutes :)
[00:09] <cjwatson> Yep, definitely more useful again now
[00:18] <poolie> hi all
[00:18] <poolie> lifeless: i posted a conceptual bmp diff spam suppression patch
[00:18] <poolie> - is it approximately right?
[00:19] <poolie> - should i bother persisting? i hate giving up, but sometimes things turn out not to be drive by
[00:19] <StevenK> Oh, damn it all. The PersonFormatterAPI calls is_valid_person everytime
[00:21] <lifeless> poolie: an actual fix no?
[00:21]  * StevenK waits for failfan to build
[00:21] <poolie> yes, this (tries to) make the job retry a bit later
[00:22] <poolie> so an actual fix along the lines we discussed
[00:22] <poolie> https://code.launchpad.net/~mbp/launchpad/612171-diff-generation-spam/+merge/79351
[00:23] <lifeless> thats grewat
[00:23] <lifeless> I'm not really here today
[00:23] <cjwatson> ah yes, there we go, 3:01 for ls-lR
[00:24] <lifeless> but if you haven't had a review tomorrow, I will look at it
[00:24] <poolie> ok
[00:24] <lifeless> (I'm taking leave to help w/cynthia wednesdays, + was up @ 4am finishing amqp stuff
[00:24] <poolie> it's not passing its tests and it probably needs some new ones
[00:24] <poolie> that's good; that's bad :)-
[00:24] <StevenK> I'm OCR, but poolie has invited me out to lunch and I have to leave in 5 minutes.
[00:24] <lifeless> wgrant: so what time is this call ?
[00:24] <poolie> yeah i was just going to remind you
[00:24] <poolie> hooray for lunch
[00:25] <poolie> mwhudson: could you have a look at the diff in the last comment of https://code.launchpad.net/~mbp/launchpad/612171-diff-generation-spam/+merge/79351
[00:25]  * StevenK looks up address
[00:26] <poolie> st leonards station
[00:26] <wgrant> lifeless: When he gets back :)
[00:26] <poolie> walk out of the station (there's only one gate), look right, there it is
[00:27] <StevenK> poolie: Right -- I was about to ask you. The address looked familiar so I was going to ask "That's the building the station is in, isn't it?"
[00:27] <poolie> yep
[00:27] <mwhudson> poolie: the diff doesn't trigger any particular thoughts in me
[00:28] <poolie> ok :)
[00:28] <mwhudson> poolie: i don't know if anything actually respects max_retries, but i'm very out of date there
[00:30] <poolie> ok
[00:30] <poolie> i might leave it for today
[00:30] <poolie> rebooting, biab
[00:30] <poolie> thanks anyhow
[01:38] <sinzui> hi lifeless. Do you want to put mailman out of our misery?
[01:38] <wgrant> It has been slow lately :(
[01:38] <wgrant> mhonarc is not happy with ubuntu-x-swat.
[01:38] <wgrant> I think we should disable it for that archive.
[01:38] <lifeless> sinzui: I think we should do a detailed plan for front-ending it
[01:39] <lifeless> sinzui: I think its a small project, done well, but I don't know enough of the ins and outs to predict WTF's
[01:39] <sinzui> lifeless, you mean mhonarc?
[01:40] <lifeless> lits.
[01:40] <lifeless> lists.
[01:40] <sinzui> lifeless, I can post my insane hack to the lp-dev list for everyone to ponder alternates. I think mustache make my insane json suggesting more palatable.
[01:41] <lifeless> whats your insane hack ?
[01:41] <lifeless> sinzui: I think there are multiple things to solve at once; we can call it 'refactoring to make it easy to do the intended work' :)
[01:42] <lifeless> sinzui: slow archiving, poor branding and integration, poor privacy experience, private list archives being inaccessible
[01:45] <sinzui> yes, those are all things that I thought could be solved by making mhonarc a json-encoded message server. I think we might also ask though is do we want a simpler mechanism to store and retrieve mbox message data? Messages could be places in a db, or we build a mbox server from other tools
[01:46] <lifeless> AIUI generating the mboxes is cheap because you write to the end
[01:46] <wgrant> I'd imagined that mailman would call an archive that injects the message into some kind of DB.
[01:46] <wgrant> That isn't mbox.
[01:46] <lifeless> wgrant: thats what mhonarc is, isn't it ?
[01:46] <lifeless> wgrant: (in an SOA model)
[01:46] <wgrant> Well, some kind of DB that doesn't then slowly generate static pages.
[01:47] <lifeless> right, thats what the change to json is about
[01:47] <lifeless> curtis and I have discussed this before
[01:47] <wgrant> So it would generate static JSON instead?
[01:47] <lifeless> I think the time is right to do it, rather than layering headaches on headaches, for lists. privacy
[01:47] <lifeless> wgrant: yes, and stop the crazy rewriting of big lists
[01:48] <sinzui> wgrant, yes, static fast data that the the Lp app can parse and linkify user and bugs
[01:48] <wgrant> How do you plan to avoid rewriting but still generate static JSON?
[01:48] <sinzui> but putting messages in a db is better for at least  two use cases. Searching, and deleting/redacting messages
[01:49] <wgrant> And cheapness of updating.
[01:49] <sinzui> mhonarc has an excellent mechanism to resurrect and present confidential data to everyone
[01:50] <wgrant> Indeed.
[01:51] <sinzui> wgrant, I wasn't planning to avoid rewriting. mhonarc does a lot of re writing now because we have the indexes set to reverse. Once a list has more than a page of messages, adding a message causes a rewrite of all indexes and most message :)
[01:51] <wgrant> Yes.
[01:52] <wgrant> If it's in a DB with a service serving dynamic JSON, that problem goes away.
[01:52] <sinzui> I was thinking of using natural indexes and letting lp reverse the MM index data
[01:52] <sinzui> But my hack is predicated on keeping mhonarc, and writing embarrassing PERL.
[01:53] <lifeless> wgrant: so, there are two orthogonal things
[01:53] <sinzui> I would be happier keeping messages in something I could confidently hack and search.
[01:53] <lifeless> wgrant: a) better interface for LP - LP templates, json backend etc.
[01:53] <lifeless> wgrant: b) better archiver implementation - cassandra etc etc
[01:54] <lifeless> wgrant: a) with mhonarc generating forward indices rather than reverse, + json -> will solve nearly all our performance and ops issues
[01:54] <lifeless> wgrant: giving us time to do b), or even advocate for someone else to do it for us :)
[01:54] <lifeless> sinzui: I'm very keen to contain scope
[01:55] <lifeless> sinzui: I think search should be done by inserting into solr-or-similar and querying that from LP
[01:55] <sinzui> lifeless, importing and exporting data has been a blocker for list adoption. Users cannot easily migrate to Lp, nor can we give them the data for analysis. I could not answer statiks questions about monthly list volume for example
[01:55] <lifeless> sinzui: I presume mhonarc makes that hard?
[01:55] <sinzui> It's db is a perl hash :)
[01:55] <lifeless> sinzui: aka yes ;)
[01:56] <lifeless> sinzui: do you agree that its better to do two projects than one: sort out the interface, then sort out the now-contained evil ?
[01:58] <sinzui> lifeless, yes
[01:58] <lifeless> sinzui: cool
[01:59] <lifeless> sinzui: do you think sorting out the interface [switch to LP templates + jason backend, *perhaps* do something about mbox [e.g. store in librarian]] is a better way to tackle the privacy banner than e.g. copying templates onto the mhonarc install ?
[01:59] <lifeless> (better meaning cheaper-over-all-including-cost-of-maintenance)
[02:03] <sinzui> I think making mhonarc serve JSON via hack and teaching LP to retrieve the data provides a lot of options. Importing/exporting mboxes might be easier in Lp. I am just not certain. export is easier, but import is still hard because we need to register all the email addresses
[02:04] <sinzui> lifeless, wgrant: my hack idea assumes I can always make proper JSON to describe the message. I think that means hacking in perl :)
[02:05] <sinzui> I am sure someone has done that, but It also feels like the time I was asked to write a multiple-part post decoded in vb because ASP did not support it, when every modern web server tool kit does
[02:06] <lifeless> sinzui: did you have minions^Wsquad members then ?
[02:06] <sinzui> odd when I last work with perl I had minions.
[02:09] <sinzui> lifeless, I think the answer might be to extend https://launchpad.net/mmm-archive-manager to do the serialisation task to minimise mhonarc's part in our victory
[02:13] <lifeless> sinzui: perhaps that should be part of launchpad-project? [or is it personal? I dunno...]
[02:14] <lifeless> sinzui: anyhow, extending that makes as much sense as anything to me
[02:14] <sinzui> I wrote it on my own time and I believe it works with Ubuntu list archives too
[02:15] <lifeless> I have no objection to how its done ... and don't know enough to seriously compare implementation approachs at this level
[02:15] <lifeless> sinzui: before you halt() tonight, I wanted to talk about private teams
[02:15] <sinzui> yes. I asked wgranta about that. I want to talk about it
[02:16] <lifeless> when is good?
[02:19] <lifeless> sinzui:
[02:20] <sinzui> now if you like
[02:21] <lifeless> cool!
[02:21] <lifeless> skynet ?
[02:22] <sinzui> skype?
[02:22] <lifeless> yes
[02:22] <lifeless> <- tired, so the pathetic sense of humour is rolled out :>
[02:26] <sinzui> lifeless, are you ready to talk?
[03:29] <StevenK> sinzui: Are you still around?
[03:40] <StevenK> wgrant: Ahh, just thinking about it, does your obsolete hackage allow us to kill bug 740584?
[03:40] <_mup_> Bug #740584: Build lacks a corresponding source publication <oops> <regression> <Launchpad itself:Triaged> < https://launchpad.net/bugs/740584 >
[05:02] <jtv> wgrant: I'm off for food, but meanwhile, would appreciate your thoughts on this!  http://paste.ubuntu.com/712840/
[05:04] <wgrant> jtv-eat: So, when I said that it should be refactored, it was meant to just be a first step.
[05:04] <wgrant> But it was instead treated as the final step.
[05:04] <wgrant> What we want to here is not defined.
[05:04] <wgrant> And probably not possible in the current model.
[05:04] <wgrant> s/to/to do/
[05:23] <StevenK> wgrant: Ahh, just thinking about it, does your obsolete hackage allow us to kill bug 740584?
[05:23] <_mup_> Bug #740584: Build lacks a corresponding source publication <oops> <regression> <Launchpad itself:Triaged> < https://launchpad.net/bugs/740584 >
[05:24] <wgrant> StevenK: No.
[05:25] <StevenK> Will that destroy most of the problematic packages?
[05:25] <wgrant> It will remove some files from disk.
[05:25] <wgrant> It doesn't affect the builds not having publications, however.
[05:25] <jtv-eat> wgrant: thanks for looking into this.  Does your response mean that you found nothing wrong with my guesses that the problem is in notify() and that the unwanted recipient is the maintainer?
[05:26] <wgrant> jtv-eat: I think that treating this as an isolated problem is probably missing a better solution
[05:26] <wgrant> jtv-eat: We need to think about who actually wants failure notifications.
[05:26] <wgrant> And then work out how to implement that.
[05:26] <jtv-eat> I think it'll need some restructuring before we can do _anything_ with it.
[05:26] <wgrant> Right.
[05:26] <wgrant> As I said, StevenK's refactoring was meant to be a preliminary step in the DD build notification work.
[05:26] <wgrant> But... well, we saw what happened :)
[05:26] <jtv-eat> The current code seems fairly effective when it comes to obscuring the requirements.
[05:27] <wgrant> It used to be far worse.
[05:27] <wgrant> But yes.
[05:32]  * jtv-eat really goes off to eat
[05:39] <poolie> does anyone know off hand how to ask lp if my credentials are still valid?
[05:39] <poolie> i guess just do any request
[05:42] <poolie> ... but not all of them seem to actually check it
[05:44] <wgrant> poolie: Some may be cached?
[05:45] <poolie> no, apparently 'GET /1.0/' doesn't check the oauth tokens
[05:45] <poolie> s/tokens/stuff
[05:45] <poolie> is it a bug?
[05:48] <poolie> https://bugs.launchpad.net/launchpad/+bug/877913 - not urgent
[05:48] <_mup_> Bug #877913: GET api.launchpad.net/1.0/ doesn't check OAuth validity <api> <oauth> <Launchpad itself:Triaged> < https://launchpad.net/bugs/877913 >
[05:50] <poolie> so the problem behind bug 877856 is partly that lp.distributions['debian'] does not cache the resulting object
[05:50] <_mup_> Bug #877856: makes many pointless object reference api calls <Ubuntu Distributed Development:In Progress by mbp> < https://launchpad.net/bugs/877856 >
[05:50] <poolie> seems like it could ; i don't know why not
[05:54] <wgrant> wallyworld_: Do you happen to recall when the JS API client started returning Entrys instead of plain JSON dicts?
[05:54] <wgrant> It caused bug #830676
[05:54] <_mup_> Bug #830676: PPA AJAX build status indicators don't update properly <buildd-manager> <critical-analysis> <ppa> <regression> <Launchpad itself:Triaged> < https://launchpad.net/bugs/830676 >
[05:55] <wallyworld_> wgrant: not sure. it may have been before i first worked with any of that stuff, since i only recall it being Entry
[05:56] <wgrant> wallyworld_: Let me just check the build history of our excellent, thorough JavaScript test suite.
[05:56] <wallyworld_> wgrant: is this doing a patch from the client?
[05:56] <wgrant> revno: 11451 [merge]
[05:56] <wgrant> timestamp: Thu 2010-08-26 16:32:27 +0100
[05:56] <wgrant> message:
[05:56] <wgrant>   [r=jtv][ui=none][bug=308198][for=foxxtrot] Make Collection contain
[05:56] <wgrant>         proper Entry's.
[05:56] <wgrant> Surely it hasn't been broken for a year...
[05:57] <wallyworld_> that does seem right though, since as i said, it was always Entry when I looked at it
[05:57] <wallyworld_> and i started in 08 last year
[05:58] <poolie> wgrant i was wondering if we should have some kind of semaphore to limit outstanding requests from jubany to lp
[05:58] <poolie> so we can ramp up the concurrent threads when they're busy doing non-lp work
[05:59] <wgrant> poolie: That would probably be the right way to do things.
[06:00] <wgrant> poolie: api.launchpad.net/1.0/ is served by Apache, at least for some Accept headers.
[06:00] <poolie> ah, for performance
[06:01] <poolie> so it's almost wontfix?
[06:01] <wgrant> eg. the WADL is served at that URL with some obscene Content-Type, and that's direct from Apache.
[06:01] <wgrant> I think so.
[06:01] <poolie> yeah, insane Vary header
[06:01] <poolie> and it's zope not apache that's checking oauth
[06:02] <wgrant> Yep
[06:06] <wgrant> wallyworld_: Ah, found it.
[06:06] <wallyworld_> do tell
[06:06] <wgrant> At least I think.
[06:06] <wgrant> 13303.10.6
[06:06] <wgrant> Just over a month before the bug.
[06:07]  * wgrant tests.
[06:07] <wallyworld_> at least that's not a year
[06:07] <wgrant> Heh
[06:08] <wgrant> Yep, that was it.
[06:20] <wgrant> jtv-eat: Could you please review https://code.launchpad.net/~wgrant/launchpad/bug-830676/+merge/79772 upon your return?
[06:21] <poolie> perhaps i should actually change lplib to optionally return slightly stale objects from cache
[06:21] <poolie> not a lot of point having a cache otherwise
[06:22] <lifeless> poolie: lplib objects are not cachable beyond deploys anyhow
[06:23] <lifeless> I think caching beyond the freshness lifetime would likely lead to bugs - and a cache is plenty useful even if stale objects are never returned :)
[06:23] <poolie> to avoid transferring the body?
[06:24] <poolie> hm, what do you mean by 'freshness lifetime'?
[06:24] <wgrant> I thought we must-revalidate
[06:25] <poolie> if you mean the http lifetime, then they do not seem to last even that long
[06:25] <poolie> wgrant, we don't actually send must-revalidate, but the behaviour is as if the application is always asking for it
[06:25] <wgrant> Ah
[06:26] <poolie> basically what i'm saying is: i don't know if all applications want must-revalidate always on
[06:26] <poolie> perhaps if they fetched an object a second ago they'd be happy to get it back from cache
[06:27] <poolie> "publication.distro_series.name.lower()" does a round trip
[06:27] <poolie> headdesk
[06:28] <poolie> every time you call it
[06:30] <wgrant> Ah, and jubany is in the DC, so instead of being hilariously slow it just DoSes us.
[06:30] <wgrant> lolz.
[06:31] <poolie> to get back the string 'sid' or something of course
[06:31] <wgrant> Yep
[06:44] <poolie> ok this is much better now
[06:50] <wgrant> Excellent.
[07:40] <adeuring> good morning
[08:20] <danilos> jtv-eat, hi, I wonder if you could take a look at https://code.launchpad.net/~danilo/launchpad/bug-817398/+merge/79571 when you are done eating, you'll probably like the branch (or at least, what's it fixing :))
[08:23] <wgrant> danilos: Heh, and so the hackish launchpad.Edit grows a third instance...
[08:37] <danilos> wgrant, yeah, I first started off with removeSecurityProxy in the buildd manager code, but that ain't any less hacky :) changing all the interfaces is even more fun, so I avoided that too
[09:06] <danilos> jtv, hey-hey, I hope food hasn't killed you :)
[09:14] <nigelb> heh
[09:46] <jtv> danilos: hi, sorry, bit busy.  Gotta do wgrant's first.
[09:46] <wgrant> Mine's pretty tiny :)
[10:37] <danilos> I was just going to say how I've got another one in the queue for jtv
[10:57] <nigelb> hah. Nice quote on topic :)
[11:05] <bigjools> nigelb: although it could be misconstrued in *so* many ways
[11:05] <bigjools> easy to shoot your foot... check
[11:06] <bigjools> preferred choice of terrorists... check
[11:06] <nigelb> bigjools: I was actually thinking about "easy to shoot your foot" myself :)
[11:27] <bigjools> danilos: I have a short-ish branch for your pleasure when you get back from lunch, TIA.
[11:42] <danilos> bigjools, "short-ish"? you mean just a bit over 600 lines? :)
[11:48] <danilos> bigjools, does "overriding" ddebs mean they will end up in the PPA directly? if so, will that affect allocated storage space?
[11:56] <danilos> bigjools, fwiw, the branch is good as it is, i.e. it looks like it does the "overriding" of pocket/section/blah-blah well, and the tests "prove" it; the question above remains mostly for my own curiosity
[12:34] <bigjools> danilos: hi, back from lunch myself
[12:34] <bigjools> danilos: overriding means that the component/section/priority is set
[12:35] <danilos> bigjools, so nothing but that? (otp, btw)
[12:35] <bigjools> the ddebs need to be in lockstep with the debs like that, otherwise they won't get superseded properly
[12:35] <bigjools> noep
[12:35] <bigjools> nope, even
[12:35] <danilos> ok, cool, thanks
[12:35] <bigjools> np
[12:35] <bigjools> thanks for the review
[12:35] <danilos> yw
[13:08] <deryck> Morning, all.
[13:10] <adeuring> morning deryck
[13:11] <adeuring> danilos: could you please review this MP: https://code.launchpad.net/~adeuring/launchpad/custom-bugs-listings-search-form-tweaks/+merge/79812 ?
[13:16] <danilos> wallyworld_, hi, I reviewed https://code.launchpad.net/~wallyworld/launchpad/delete-bugtasks-1324/+merge/79541 and have a few questions in the MP; if you don't understand something, please let me know
[13:17] <wallyworld_> danilos: thanks, will look
[13:17] <danilos> adeuring, sure, would you like to return the favour by looking at https://code.launchpad.net/~danilo/launchpad/bug-877179/+merge/79781? :P (no diff either, that seems broken :/)
[13:17] <adeuring> danilos: sure, I'll look
[13:18] <danilos> adeuring, I'll also grant you the "last review Danilo will officially do as OCR" title, fwiw :)
[13:18] <adeuring> ;)
[13:21] <wallyworld_> danilos: fair point about admin. i think that should be added. the store.flush() is definitely required for tests to ensure flags passed into the constructor are visible. for prod, i don't think it's needed but as you say, likely not an issue
[13:22] <wallyworld_> the feature flag in the permission check - i'm not sure where else to put it. i'll need to think about it
[13:23] <danilos> wallyworld_, well, generally one would put it around the code that is feature flagged; i.e. in delete method instead, instead of failing with Unauthorized, it could fail with IAmNotAMethodYouMustBeDrunk() exception or something :)
[13:24] <wallyworld_> danilos: sure. i understood the requirements to be that if the fflag were not on, it was to be treated as 'unauthorised' hence the implementation
[13:25] <danilos> ok, maybe a NotImplementedError, but I ain't sure really what's the "right thing" to do, I just dislike this ;) if you can't come up with anything nice, just leave it as is
[13:25] <danilos> (though, I like the YouMustBeDrunk exception for this)
[13:26] <danilos> wallyworld_, if those were the requirements, then fine, keep it as is (I don't like the requirements, but hey, life is tough)
[13:26] <wallyworld_> :-) np. it's definitely a fair question. also, with the tests and the fflag stuff, the fflag will be going away (soon hopefully) hence i thought it ok to "double up" so to speak
[13:26] <wallyworld_> i'll confirm the requirements in case i have misunderstood
[13:26] <wallyworld_> which is not unprecedented :-)
[13:27] <wallyworld_> i do like your suggested exception class :-)
[13:28] <wallyworld_> i've had a few glasses of wine so am already half way there :-D
[13:28] <danilos> wallyworld_, as for tests, sure, keep them as is, but don't forget to remove the feature flags then :)
[13:28] <wallyworld_> will do :-) i'm about to remove all the feature flags for the picker enhancements \o/
[13:29] <danilos> wallyworld_, cool, great to hear that!
[13:29] <wallyworld_> :-)
[13:30] <wallyworld_> i'll think about tests for conjoined bugtasks
[13:30] <danilos> thanks
[13:30] <danilos> wallyworld_, sorry for being such a PITA, but you got to know me already :)
[13:30] <wallyworld_> a pre impl talk showed the code base doesn't really place any significance on them though
[13:30] <wallyworld_> no, not a pita. i really appreciate the input
[13:31] <danilos> wallyworld_, yeah, if so, then ignore me on that point, I just wanted some confirmation (you did mention the pre-imp with lifeless in the MP I believe)
[13:31] <wallyworld_> shows you have taken the time to think about the code
[13:32] <danilos> or that I am good at coming up with things which resemble arguments about code, yes
[13:32] <wallyworld_> i talked with wgrant about the conjoined tasks in particular. he showed me how the gui/code now doesn;t care if a conjoined master/slave is there or  not
[13:33] <danilos> wallyworld_, ah right, lifeless raised the issue, you talked it over with wgrant, which means you are pretty well covered :)
[13:33] <wallyworld_> i would prefer to be challenged rather than a simple +1. that's the best way to avoid base code :-)
[13:33] <wallyworld_> s/base/bad
[13:34] <wallyworld_> yeah, if those guys make a mistake, it's pretty rare :-)
[13:34] <wallyworld_> i'll add a note to the mp so that sinzui can see what we discussed when he looks at it
[13:38] <bigjools> hey benji, I decided to sit down and fix that keyring corruption thing in launchpadlib, and blow me if it's not happening any more .... !
[13:39] <bigjools> you can't make this stuff up
[13:39] <benji> bigjools: heh, that's life for you
[13:40] <bigjools> benji: I'm trying to work out exactly what the keyring was doing to the credential string in the first place. Maybe it was a bug in the kwallet and it's now fixed.  Hmph.
[13:42] <mrevell> danhg is here and rockin' like Dokken
[13:42] <danhg> I sure am
[13:43] <bigjools> Dokken... not heard them for ages
[13:44]  * bigjools welcomes danhg to the public channel too
[13:44] <rvba> Hey danhg!
[13:48] <nigelb> Hello! danhg
[13:53] <james_w> welcome danhg
[14:02] <deryck> allenap, ping
[14:02] <allenap> deryck: pong
[14:03] <deryck> allenap, hey man! :)  Did I hear correctly that you're looking into the ssh errors with test runs, that are supposed to be avoidable on Natty?
[14:04] <allenap> deryck: Not ssh errors, but database errors. Are you getting ssh errors too? Gulp.
[14:04] <allenap> deryck: The problem I'm working on is that some disconnections are not being detected as such and are bubbling up.
[14:04] <deryck> allenap, oh, sorry, no.  I thought that's what they were.  abentley is blocked running tests locally with these errors, I believe.
[14:05] <deryck> abentley, what allenap reports there is what you're seeing?
[14:05] <allenap> deryck: I'm waiting on reviews from Storm people. I'll go and hussle for them now.
[14:05] <deryck> allenap, thanks!  abentley is seeing this on Natty, too, so he's completely blocked landing some stuff.
[14:06] <deryck> assuming we're talking about the same issue :)
[14:06] <allenap> deryck: I've heard that the problem does not manifest in ec2, and mbp said tests run fine in a Lucid schroot. The latter only takes a few minutes to get set-up.
[14:07] <allenap> So that's a workaround for now.
[14:07] <deryck> ah, that's nice.
[14:07] <adeuring> danilos: r=me
[14:07] <deryck> abentley, ^^ Lucid schroot FTW? :)
[14:08] <danilos> adeuring, thanks, I am still on yours (sorry for taking so long, had a call in the meantime)
[14:08] <adeuring> danilos: np
[14:13] <abentley> deryck, allenap: I am experiencing the SSL connection has been closed unexpectedly
[14:14] <deryck> I knew there was an "ss" in there :)
[14:14] <allenap> abentley: Yes, that's the badger.
[14:16] <allenap> abentley, deryck: I'm sorry a fix has taken so long to be ready. Mainly it's been hard to replicate in tests, and I'm now blocked on reviews.
[14:16] <abentley> deryck: I have natty and maverick vms.  I haven't been using schroots.
[14:19] <abentley> deryck: I suspect that it was broken by recent changes to launchpad-dependencies.  I can try my maverick vm without upgrading, but having stale packages can itself be a problem.
[14:21] <adeuring> danI just noticed that the cover letter was quite nonsensical. I added a hopefully better readable comment...
[14:29] <danilos> adeuring, yeah, I kind of read it as random notes you were making for yourself, so other than figuring roughly what the branch is about, I didn't rely on them too much :)
[14:29] <danilos> adeuring, anyway, r=me with a few superficial comments :)
[14:29] <adeuring> danilos: thanks!
[14:29] <danilos> adeuring, btw, you can edit the MP as well, fwiw :)
[14:29] <danilos> adeuring, (no need to add a comment)
[14:30] <adeuring> danilos: ah, right! next time, then ;)
[14:32] <danilos> adeuring, and then nobody can tell ;)
[14:32] <adeuring> ;)
[14:49] <abentley> deryck: This branch has sorting, ajax and caching enabled: lp:~abentley/launchpad/cache-batches
[14:49] <abentley> deryck: If you branch off it, please merge only it, not devel, to avoid criss-cross merges.
[14:50] <danilos> wallyworld_, btw, I don't think the way you introduced security adapter is sufficient: in my reading, it modifies the launchpad.Admin privilege for BugTask to match the launchpad.Delete privilege, but does not really allow admins to do the delete
[14:52] <danilos> wallyworld_, your test is not really testing what I thought it should (i.e. log in as<EMAIL_ADDRESS>and not someone holding a contextual launchpad.Admin permission [like target owner])
[14:52] <danilos> wallyworld_, (or better yet, login_celebrity('admin'))
[14:58] <abentley> deryck: maverick had bugs related to pgbouncer files being missing.  Trying a schroot now...
[15:03] <deryck> abentley, ok, cool.
[15:47] <abentley> deryck: lucid schroot seems like a rather awful option, as it leaves me with the encrypted version of my home directory, and will have port conflicts with my system daemons.
[15:56] <deryck> abentley, hmm, yeah, yuck.  I'm not a schrod user so don't have much to offer in advice.
[15:57] <deryck> schroot even :)
[16:30] <micahg> bigjools: about bug 877122, the API syncing was a new feature, but it used to be that all packages had debdiffs and now they don't, so wouldn't that be a regression?
[16:30] <_mup_> Bug #877122: Packages synced through the API are not producing debdiffs <derivation> <Launchpad itself:Triaged by redsquad> < https://launchpad.net/bugs/877122 >
[16:32] <bigjools> micahg: it's not a regression if this feature never had that :)  The old syncing did it of course.  I have scheduled it to be fixed soon tjough, don't worry
[16:32] <bigjools> though*
[16:34] <micahg> bigjools: ok, it is a regression in functionality for Ubuntu though, thanks for getting it scheduled
[18:14] <dobey> hey guys, when do things fixed in launchpad stable, show up on production?
[18:36] <maxb> dobey: http://lpqateam.canonical.com/qa-reports/deployment-stable.html
[18:37] <dobey> ah, interesting. thanks maxb
[18:40] <maxb> dobey: IIUC, once something goes green there, the remaining steps are for someone on the Launchpad team to ask for a deployment to happen, and for it to be actioned by losas - so fairly soon, subject to working days, etc.
[18:42] <dobey> maxb: sure. just wondering when my bug will be fixed in production since jtv's branch landed :)
[18:48] <lifeless> mpt: an observation: your 'what should happen' entries in bugs are very close to 'shoulds'
[18:49] <mpt> lifeless, they are. It's the describing the problem first that's the important thing. :-)
[18:49] <mpt> Maybe I could use "What I expected:" instead
[18:51] <lifeless> mpt: Or 'one way I would not have been surprised:' :)
[18:52] <lifeless> mpt: I guess my point is to open the solution space out
[19:26] <mtaylor> I suppose folks know that launchpad login service is unhappy?
[19:26] <mtaylor> org.openid4java.discovery.yadis.YadisException: 0x706: GET failed on https://login.launchpad.net/+openid : 503:HTTP/1.1 503 Service Unavailable
[19:30] <lifeless> mtaylor: grah. Thats login.ubuntu.com. I'll go poke folk
[19:34] <lifeless> mtaylor: fixed
[19:34] <lifeless> mtaylor: sso is having some flakiness issues this week
[19:34] <mtaylor> lifeless: ++
[19:34] <lifeless> mtaylor: its escalated but not understood yet
[19:34] <lifeless> (theories abound, proof is tricky)
[19:38] <mtaylor> lifeless: distributed systems are hard
[19:38] <mtaylor> lifeless: btw - it's still broken
[19:39] <mtaylor> lifeless: https://jenkins.openstack.org
[19:39] <lifeless> mbarnett: ^
[19:39] <lifeless> mbarnett: ah you know, nvm
[19:39] <lifeless> mtaylor: cascading trouble
[19:40] <mtaylor> yay!
[19:40]  * mtaylor loves trouble
[20:16]  * mbarnett doesn't always break things, but when he does he breaks them all.
[21:15] <thumper> hi people
[21:16] <thumper> I'm looking for a "stock" presentation for "intro to launchpad"
[21:16] <thumper> is there one around somewhere?
[21:16] <thumper> We have a growing team, and some don't really understand launchpad, so I'm doing a presentation next week to cover the basics
[21:30] <mwhudson> in unrelated news, launchpad's roles for managing (in various senses) projects make no sense to anyone