[23:09] <mustafa_> any1 familiar with concerto installation on ubuntu
[23:10] <creature> Hello. I want to run a command when I press my Windows key (Super_L) but the keyboard preferences seem to INSIST that Super_L is a modifier only. How do I get it to do what I want?
[23:11] <Joe_knock> synth_: thanks!!
[23:11] <mustafa_> any1 familiar with concerto installation on ubuntu
[23:12] <wilee-nilee> !patience | mustafa_
[23:12] <RandyLangston> hello
[23:12] <synth_> Greetings Lord RandyLangston
[23:12] <Joe_knock> mustafa_: What are you trying to accomplish?
[23:12] <mustafa_> any1 familiar with concerto installation on ubuntu
[23:12] <mustafa_> thanks
[23:12] <RandyLangston> hey synth
[23:13] <synth_> lol
[23:13] <Joe_knock> !patience | mustafa_
[23:13] <wilee-nilee> mustafa_, YOU see the bot message?
[23:13] <RandyLangston> i had a question for anyone that might be able to help me
[23:13] <mustafa_> trying to install concerto on ubuntu...facing an errot
[23:13] <RandyLangston> my friend wants to put ubuntu on her laptop
[23:13] <Joe_knock> RandyLangston: Don't ask to ask. Just ask
[23:13] <RandyLangston> however she has something im not famiar with on this laptop
[23:13] <mustafa_> mustafa@mustafa3113:/var/www/concerto/lib/R$ sudo R CMD INSTALL -l /usr/lib/R/library concerto
[23:13] <mustafa_> ERROR: dependency ‘RMySQL’ is not available for package ‘concerto’
[23:13] <mustafa_> * removing ‘/usr/lib/R/library/concerto’
[23:13] <Joe_knock> mustafa_: paste your error into some text pasting tool and share here
[23:13] <synth_> oh man
[23:14] <Joe_knock> RandyLangston: What might that thing be?
[23:14] <RandyLangston> to unlock her pc she has to put her fingerprint on it
[23:14] <RandyLangston> im wondering if ubuntu would work with something like this
[23:14] <synth_> do you know if it's built into the bios ?
[23:14] <RandyLangston> no idea
[23:14] <Joe_knock> mustafa_: The error is pretty clear: ERROR: dependency ‘RMySQL’ is not available for package ‘concerto’
[23:14] <RandyLangston> there is a scanner on the laptop
[23:14] <vilambit> RandyLang: is that after it boots or before?
[23:14] <RandyLangston> thats all i know
[23:15] <Joe_knock> yikes, a fingerprint laptop.
[23:15] <RandyLangston> good question vilabit... lol
[23:15] <RandyLangston> i dont know yet
[23:15] <synth_> do you know the make/model of the laptop?
[23:15] <wilee-nilee> RandyLangston, Try to lay off the enter, consolidate info to single posts.
[23:15] <RandyLangston> no synth i dont
[23:15] <RandyLangston> guess i should get more info and come back lol
[23:15] <RandyLangston> gotcha wilee
[23:15] <synth_> we would probably be able to help more if we knew that info :)
[23:15] <wilee-nilee> RandyLangston, Cool, thanks. ;)
[23:15] <Joe_knock> RandyLangston: Is the fingerprint scan necessary to switch the laptop on?
[23:16] <Joe_knock> oh that has been asked. soryr
[23:16] <Joe_knock> sorry
[23:16] <RandyLangston> i am not sure joe knock... i only seen it once , all i know is it is a HP laptop , and that it has that fingerprint scan  on it
[23:17] <piyush1911> Hi
[23:17] <piyush1911> I am running a ubuntu12.04 server
[23:17] <Joe_knock> piyush1911: Come here: #ubuntu-server. I'll help you there
[23:18] <piyush1911> and when I try to run 'sudo apt-get update' the machine throws up a lot of 404 errors
[23:18] <piyush1911> "W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/precise/main/binary-armhf/Packages  404  Not Found [IP: <IP_ADDRESS> 80]"
[23:18] <Joe_knock> piyush1911: ...
[23:18] <piyush1911> the machine is a x86_64, but apt looks for armhf packages
[23:19] <wilee-nilee> piyush1911, If the source list is the same when working, change the repo
[23:19] <mustafa_> mustafa@mustafa3113:/var/www/concerto/lib/R$ sudo R CMD INSTALL -l /usr/lib/R/library concerto
[23:19] <mustafa_> ERROR: dependency ‘RMySQL’ is not available for package ‘concerto’
[23:19] <mustafa_> * removing ‘/usr/lib/R/library/concerto’
[23:19] <RandyLangston> i suppose i should find out more about this machine and i will come back, thank you guys for trying to help me
[23:19] <RandyLangston> have a good night all
[23:19] <wilee-nilee> night
[23:19] <mustafa_> conerto install help needed
[23:19] <mustafa_> sorry concerto
[23:19] <Joe_knock> mustafa_: You don't like to read and understand instructions mate...
[23:20] <piyush1911> Joe_knock: but why is the apt looking for arm packages
[23:20] <wilee-nilee> piyush1911, If you can a pastebin of a full update helps us help you.
[23:20] <Joe_knock> piyush1911: This isn't the right channel to be asking for ubuntu-server support. I'm telling you this because an ubuntu-server support channel exists
[23:21] <wilee-nilee> Joe_knock, Fair point however we help the server people all the time and refer to that channel when needed.
[23:21] <Joe_knock> wilee-nilee, piyush1911: My apologies then.
[23:22] <synth_> his error could also happen on a non server ubuntu
[23:22] <wilee-nilee> Joe_knock, Some problems are fairly straight forward, and there are helpers here who are working linux IT.
[23:22] <piyush1911> http://pastebin.com/ubW2AEz5
[23:23] <OerHeks> piyush1911, maybe your server is running on an Arm machine? see lscpu
[23:23] <mustafa_> sorry joe im a newbe here...what exactly u meant by copy paste tool
[23:23] <piyush1911> # lscpu
[23:23] <piyush1911> Architecture:          x86_64
[23:23] <piyush1911> CPU op-mode(s):        32-bit, 64-bit
[23:23] <piyush1911> Byte Order:            Little Endian
[23:23] <piyush1911> CPU(s):                4
[23:23] <piyush1911> On-line CPU(s) list:   0-3
[23:23] <unopaste> piyush1911 you have been muted for 60 seconds as it looks like you are pasting lots of lines into the channel, please use http://paste.ubuntu.com and paste just the URL of your data here when you are unmuted
[23:23] <synth_> mustafa_ http://pastebin.com for instance
[23:23] <Joe_knock> mustafa_: http://paste.ubuntu.com/
[23:24] <Joe_knock> mustafa_: I say this because if you start a long paste, some mod in a bad mood might ban/kick you.
[23:24] <wilee-nilee> piyush1911, You have added a additional armf repo it looks like are you sure it has support for your release.
[23:24] <Joe_knock> like piyush1911 getting muted...
[23:24] <piyush1911> http://pastebin.com/PcSGvij3
[23:25] <Joe_knock> x86_64 would mean it is a 64-bit architecture.
[23:25] <mustafa_> here it is
[23:25] <mustafa_> http://paste.ubuntu.com/7547413/
[23:26] <piyush1911> Joe_knock: here is my souces.list
[23:26] <piyush1911> http://pastebin.com/WYxmwb1p
[23:26] <Joe_knock> piyush1911: Are you root?
[23:26] <piyush1911> yes
[23:27] <synth_> mustafa_ try running: sudo apt-get update && sudo apt-get install r-cran-rmysql
[23:27] <synth_> then try again
[23:27] <Jordan_U> piyush1911: Please pastebin the name and contents of all of the files in /etc/apt/sources.list.d/ .
[23:27] <daftykins> piyush1911: how come you're @...nvidia.com ? :)
[23:28] <Joe_knock> daftykins: :D
[23:28] <mustafa_> any ideas joe...i have pasted the link
[23:28] <mustafa_> http://paste.ubuntu.com/7547413/
[23:29] <piyush1911> Joe_knock: http://pastebin.com/Air3UV4F
[23:29] <synth_> mustafa_ try running: sudo apt-get update && sudo apt-get install r-cran-rmysql
[23:29] <Joe_knock> mustafa_: See synth_s recommendation. You require rmysql to be installed.
[23:31] <Joe_knock> looks like you have the basic source list only piyush1911
[23:31] <piyush1911> somehow the apt is looking for arm packages instead of x86_64 packages
[23:32] <piyush1911> somehow the apt is looking for armhf packages instead of x86_64 packages
[23:32] <Joe_knock> piyush1911: What is the pastebin for the error output?
[23:32] <piyush1911> http://pastebin.com/ubW2AEz5
[23:33] <synth_> piyush1911 can you pastebin:  cat /etc/apt/sources.list
[23:33] <synth_> instead of sources.list.d/*
[23:34] <piyush1911> http://pastebin.com/WYxmwb1p
[23:34] <piyush1911> synth_:http://pastebin.com/WYxmwb1p
[23:34] <Joe_knock> piyush1911: Ironically, I think nvidia might be the issue here. Did you try to install any NVidia packages?
[23:35] <piyush1911> haha..
[23:35] <piyush1911> there are no nvidia packages on this machine right now
[23:36] <synth_> hmmm
[23:36] <Joe_knock> I came across an error for somebody else who was getting these errors, because he/she installed: cuda toolkit
[23:37] <piyush1911> Joe_knock: No cuda
[23:38] <arfent> Is firefox updating ubuntu users to 29.0.1?
[23:38] <daftykins> arfent: even if it isn't it doesn't matter because the .1 fixes are mostly windows related
[23:38] <synth_> piyush1911 what does cat /etc/dpkg/dpkg.cfg.d/multiarch show?
[23:38] <Joe_knock> piyush1911: This is the closest I came to discovering your error - http://askubuntu.com/questions/347945/problem-when-i-apt-get-update-precise-main-armhf-packages-404-not-found . Proceed with caution. It seems like you may be able to remove armhf
[23:39] <arfent> synth_: k thanks
[23:39] <synth_> ?
[23:39] <synth_> wrong guy haha
[23:40] <Joe_knock> Getting thanks for the wrong thing ehh
[23:40] <piyush1911> Joe_knock, synth_: WOW that fixed it
[23:40] <synth_> :D
[23:41] <piyush1911> man cuda messes with some stuff
[23:42] <Joe_knock> piyush1911: I think it was just that those armhf packages were specified when they shouldn't be. I can only wonder why. Also, you're using 12.04.3, try to upgrade to 12.04.4
[23:43] <piyush1911> daftykins: few days a week i work at nvidia
[23:44] <daftykins> piyush1911: ah, may i ask what doing? :)
[23:44] <piyush1911> Automotive
[23:44] <daftykins> looking after cars 0o
[23:45] <piyush1911> yep!
[23:45] <arthurdent> do i have to configure the kernel in any special way to do nbdroot?
[23:45] <Baako> can some suggest me a good php text editor for ubuntu please? the netbeans I install is bugger alot.
[23:45] <OerHeks> !ide
[23:45] <Joe_knock> Baako: Netbeans is 1 massive IDE
[23:45] <arthurdent> (nbdroot over the network via pxe)
[23:47] <piyush1911> Joe_knock: we were seeing some flaky nfs-kernel daemon issues with any kernel above <IP_ADDRESS> ... hence we are on 12.04.03
[23:48] <Joe_knock> piyush1911: Good enough reason to not update.
[23:49] <Jordan_U> piyush1911: Have you filed a bug report?
[23:49] <Shinyu> i have a question about nic  support
[23:49] <piyush1911> Jordan_U: no not yet, but will do.
[23:49] <MPEREZ> Hello I am having trouble updating my ubuntu system
[23:50] <MPEREZ> I need help please
[23:50] <Shinyu> is the Intel WG-I217V supported in ubuntu?
[23:50] <Joe_knock> MPEREZ: Feel free to ask your question.
[23:50] <lucaNapoli> italiani?
[23:51] <piyush1911> MPEREZ: there are many helpers here please let us know what is your issue
[23:51] <MPEREZ> Ok everytime I try to update i get an error. I have ubuntu 8.04 and I wish to upgrade to the latest version
[23:51] <xangua> !eol | MPEREZ
[23:51] <daftykins> MPEREZ: sorry, you're eol
[23:51] <synth_> lucaNapoli #ubuntu-it
[23:51] <lucaNapoli> tnk
[23:52] <Joe_knock> 8.04!!!!
[23:52] <MPEREZ> ok so i got an old one and your not allowed to help?
[23:53] <Joe_knock> MPEREZ: I think what daftykins is trying to say is that you should download Ubuntu 12.04 or ubuntu 14.04
[23:53] <arthurdent> or pay 5.5m GBP to extend support for another year
[23:53] <daftykins> Joe_knock: i think the links spoke for themselves!
[23:53] <MPEREZ> oh well i tried the disk dident work
[23:54] <daftykins> MPEREZ: correct, unsupported is unsupported
[23:54] <Jordan_U> MPEREZ: Did you recently install Ubuntu?
[23:54] <synth_> maybe try doing a usb thumbdrive install
[23:54] <MPEREZ> yes the other day
[23:54] <arthurdent> o_o
[23:54] <Jordan_U> MPEREZ: OK. Why didn't you install Ubuntu 14.04?
[23:54] <Joe_knock> MPEREZ: I'm guessing you're running a 32-bit machine.
[23:54] <Joe_knock> and might have downloaded 64-bit
[23:55] <MPEREZ> my friend gave me a disk for 8.04
[23:55] <arthurdent> i feel like i stepped into a time machine
[23:55] <Jordan_U> MPEREZ: You should download and install Ubuntu 14.04 instead.
[23:55] <Pushy> is ubuntu simliar to solaris?
[23:56] <MPEREZ> ok ill get to it thanks
[23:56] <Pushy> anyone also know solaris?
[23:56] <alfonsojon> Is it just me, or is the Ubuntu site being hammered?
[23:56] <arthurdent> Pushy: it's an OS... so in that sense it's similar
[23:56] <Jordan_U> Pushy: "similar" is a vague term. Why do you ask?
[23:56] <Pushy> cause i use solaris 11, and don't even know how to install xchat
[23:57] <Pushy> usually in ubuntu i do,  sudo apt-get install xchat
[23:57] <Pushy> or from the app store
[23:57] <alfonsojon> ah
[23:57] <alfonsojon> just google "solaris 11 package manager"
[23:57] <Pushy> not much help for solaris
[23:57] <Jordan_U> Pushy: This isn't the correct channel to be asking questions about how to use Solaris.
[23:57] <arthurdent> Pushy: you may want to try #solaris for help with that kind of thing
[23:58] <Pushy> solaris channel is like dead
[23:58] <Joe_knock> I don't blame Pushy though. Solaris?? Do people use that at all?
[23:58] <Jordan_U> Pushy: That doesn't make this the right channel. This is still #ubuntu, and we only support Ubuntu here.
[23:59] <daftykins> Joe_knock: i do, please don't encourage the seeking of support for other things in here


[10:01] <mystic> hello..  can anyone please help me register with freenode?  its stupidly complicated
[10:06] <mystic> ?
[10:06] <kc2bez> mystic: here are the freenode instructions: https://freenode.net/kb/answer/registration   Also you may want to try #freenode this is Lubuntu support
[10:06] <Moane> mystic, only type : /msg nickerv register your_password a_valid_email_address
[10:07] <mystic> i cant understand them
[10:07] <Moane> you will receive a confirmation email with code to copy-paste within your irc's application
[10:07] <mystic> and i cant enter freenode withput being registered
[10:08] <mystic> why cant they just have a normal easy sign up method like other chat rooms?
[10:10] <mystic> it says my name is already registered, but i cant sign in
[10:10] <Moane> mystic, this method sounds me as simple as it can be
[10:10] <mystic> what are you taslking about?   most chat rooms just want your email address and a name and a password.. none if this code style format
[10:10] <mystic> this is nuts and confusing for me
[10:11] <mystic> must have been designed by a lninux user
[10:11] <Moane> sure, that's why it's simple
[10:11] <mystic> for gods sake...
[10:12] <mystic> so its as simple as putting in a name and emaail on a normal website is it?  no it damn well isnt
[10:12] <mystic> whats wrong with you linux users?
[10:13] <Moane> nothing, or maybe because linux users are different :)
[10:14] <mystic> they are yes.. and refuse to admit linux is not simple.  they seem to think searching for the right package, and installing it maunally with terminal is as easy as useing a windows exe file.   the same thing swith freenode... why do they even make it so difficult?   the mind boggles
[10:15] <Moane> its easy : we want to control what we use instead of being controlled by. Come back later.
[10:16] <mystic> smarmy aloof twat... no surprise there
[10:37] <lineageosfan> I want to install VNC on my Lubuntu system to control in in my LAN. Which server do I have to install?
[10:41] <lineageosfan> Also, how do I have to configure Lubuntu to be able to do a GUI login at the client machine?
[10:43] <lineageosfan> Do I only install the X11vnc package on the Lubuntu machine?
[11:43] <mystic> did i register right ?
[12:01] <tomreyn> you are logged in as (to account) 'mystic', so your account registration and 'identify' to nickserv (authentication) did succeed.
[12:24] <lineageosfan> Anybody?
[12:26] <diogenes_> wnats to be with somebody, sometimes?
[12:40] <guiverc2> lineageosfan, i use `ssh` (text) to remotely control machines so don't know, and if you don't get a response in awhile - you can repeat the question as some may not have seen your prior question..
[12:41] <lineageosfan> guiverc2: OK, thx; I want to use a grahical client to be able to run deluge and other programs
[12:45] <tomreyn> if i recall correctly, there's both a CLI and web UI client to deluge
[12:46] <guiverc2> https://wiki.ubuntu.com/Lubuntu/RemoteDesktop maybe helpful (esp. 18.04 LTS); I don't see anything in current manual (https://manual.lubuntu.me/) sorry lineageosfan
[12:48] <lineageosfan> guiverc2: Thank you. I need a solution that works with XFCE on the client (Qubes OS)
[12:50] <lineageosfan> I guss I can use Remmina.
[12:50] <lineageosfan> For the client
[12:56] <lineageosfan> www.qubes-os.org
[14:02] <lineageosfan> What display manager does Lubuntu use by default?
[14:04] <diogenes_> lineageosfan, cat /etc/X11/default-display-manager
[14:06] <lineageosfan> thx
[14:06] <lineageosfan> I am at work at the moment. Could you tell me which one it is?
[14:09] <diogenes_> lineageosfan, i cannot because i'm on a different os but you can always open one of these in your browser and check whatever you need: https://distrotest.net/Lubuntu
[14:12] <lineageosfan> Wow! That is amazing. I did not know that site. Great! Thank you.
[14:12] <diogenes_> yw
[14:18] <lineageosfan> so it uses sddm
[14:25] <lineageosfan> I can not seem to find a tutorial on how to start SDDM with VNC so that when I connect I can use the remote login GUI. Anybody knows how to do that?
[14:41] <lineageosfan> Never mind.
[19:33] <mystic> why cant i join ubuntu room?
[19:33] <mystic> keeps sending me to unregged room
[19:34] <wxl> mystic: admittedly this is not the place to discuss other channels
[19:34] <mystic> well i need help.. please tell me how to log in....  starting up the app isnt enough on freenode apparently.. what a load of garbage
[19:35] <wxl> mystic: that said, #ubuntu has mode +r set, which blocks unregistered users
[19:35] <wxl> mystic: https://freenode.net/kb/answer/registration
[19:36] <mystic> i asm registered.. just have ti 'sign in' also by typing more code apparently
[19:37] <mystic> feel like im back in 1995
[19:48] <jugaad> i have a game installed in Lubuntu, name is Astromenace. after playing several levels, i decided to reset the game. but there is no option.
[19:48] <jugaad> i marked it for complete remove in synaptic
[19:49] <jugaad> but after reinstalling i found all data was stored, and levels and all records were saved
[19:49] <mystic> at least you wont loose your place
[19:50] <jugaad> tried sudo apt-get purge astromenace and sudo  apt-get autoremove
[19:50] <jugaad> but again after installation i found same data saved
[19:51] <jugaad> is there any way to remove all files of the game so that i can play it as a fresh game
[19:53] <wxl> it's possible that it might not do a good job of cleaning up its files, but i would be they're in ~/.config
[19:54] <wxl> sadly they don't install any config files, which is probably why they don't bother to clean them up ugh
[19:54] <wxl> https://packages.ubuntu.com/eoan/amd64/astromenace/filelist
[19:56] <wxl> it looks like it's using "config.xml" https://packages.ubuntu.com/eoan/amd64/astromenace/filelist
[19:56] <wxl> and there should be some data files in the form PilotProfiles_SOMEVERSION.data
[19:57] <jugaad> ok let me delete all these files by using nautilus file browser. then i will check
[20:02] <wxl> it also might be in one of the paths specific in $XDG_CONFIG_HOME
[20:03] <wxl> s/.specific/specified/
[20:06] <jugaad> well i have removed all files now
[20:06] <jugaad> there was also a file in home folder at ./config
[20:06] <jugaad> now trying to reinstall it
[20:24] <jugaad> now it is working as fresh game
[20:25] <jugaad> thanks wxl, for the location link of the game
[20:26] <jugaad> i needed to remove file from ./config in home location. and then had to run sudo apt-get remove astromenace cmd
[20:26] <wxl> jugaad: happy to help. i would totally urge you to file a bug report against the package. it really should clean up its config files.
[22:26] <n-iCe> hi
[22:27] <n-iCe> hi wxl around?
[22:50] <wxl> n-iCe: what's up?
[22:51] <wxl> kc2bez: no clue
[22:51] <n-iCe> how are you?
[22:52] <wxl> oops wrong channel on the last one
[22:52] <wxl> fine, thx


 I was gonna try and ping the lot of us for that bootstrap programme meeting kinda thingy that dave (zarzycki, from launchd) proposed last october, since i kinda liked the idea but never heard of anything actually coming of it.
[21:44] <jyujin> roy (marples, openrc) would tag along too, and i was trying to talk ismaell from initng into it as well
[21:44] <jyujin> oh yeah, excuse my manners, i'm magnus from einit
[21:48] <Keybuk> *nods*
[21:48] <Keybuk> where/when were you thinking of holding it?
[21:50] <jyujin> heh, thats the tricky thing. i'm pretty sure we're all quite scattered around the place, but i was thinking that coming together in some irc channel would be a good start, wouldnt it? i was hoping we could get something arranged this month on a weekend maybe
[21:51] <jyujin> that way none of us needs to make any travel arrangements and we could probably still work out some commonalities that we should all stick to ;)
[21:51] <Keybuk> weekends are normally bad for me
[21:52] <jyujin> heh, i assumed as much judging from the time you came online today :)
[21:53] <Keybuk> Linux stuff is my day job, so I tend to be around 1000-2000 UTC weekdays
[21:54] <jyujin> heh, medical image analysis here, and my boss doesn't really appreciate me hanging out on irc, but i'm sure i could arrange something... we could all just join a chan anyway couldnt we?
[21:54] <jyujin> i'm sure we can find some time to sit together ;)
[21:54] <Keybuk> yeah, I'm sure we'll find something
[21:55] <jyujin> sweet... ill go reg a chan then. what about #bootstrap?
[21:56] <Keybuk> #init ?
[21:57] <jyujin> mhh seems to be some kind of freenode channel
[21:57] <jyujin> #unix-init?
[22:32] <jyujin> Keybuk: looks like ismaell likes the chan name as well ;)


[14:59] <ItzSwirlz> o/
[15:00] <rbalint> o/
[15:00] <slyon> o/
[15:00] <ItzSwirlz> o/
[15:00] <bdmurray> #startmeeting Weekly Ubuntu Foundations team
[15:00] <meetingology> Meeting started Thu Aug 13 15:00:53 2020 UTC.  The chair is bdmurray. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:00] <meetingology> Available commands: action commands idea info link nick
[15:01] <bdmurray> #topic Lightning rounds
[15:01] <bdmurray> echo $(shuf -e vorlon bdmurray xnox tdaitx doko sil2100 rbalint infinity mwhudson juliank waveform slyon)
[15:01] <bdmurray> doko rbalint slyon juliank vorlon xnox infinity mwhudson tdaitx waveform sil2100 bdmurray
[15:01] <bdmurray> doko wins
[15:03] <bdmurray> rbalint: are you ready?
[15:04] <rbalint> * uploads via Debian: libcec 6.0.2-1, waylandpp 0.2.8-1 (fixes FTBFS on ppc64el), kodi 18.8+dfsg1-1 (sponsoring)
[15:04] <rbalint> * vim FTBFS fix on riscv64
[15:04] <rbalint> * set up now official git packaging repository for update-motd uploaded a bugfix
[15:04] <rbalint> * preparing SRUs for glibc and next upload to groovy
[15:04] <rbalint> * poking proposed packages
[15:04] <rbalint> (done)
[15:04] <doko> oops
[15:04] <doko>  - short week, vacation day on Tuesday
[15:04] <doko>  - wanted to attend the meeting from the hot pool on the rooftop, but it's raining cats and dogs
[15:04] <doko>  - ported the ftbfs-report to python3
[15:04] <doko>  - started test rebuilds for focal GCC and python SRU updates. no regressions for the updates, but delaying the uploads until Septemb
[15:04] <doko> er
[15:04] <doko>  - filed bug reports for focal fbbfs (main only)
[15:04] <doko>  - supposed to do +1 maintenance, but doing stuff instead which I wanted to get done before the vacation
[15:04] <doko> (done)
[15:05] <xnox> slyon:
[15:05] <slyon> - Published "Call for testing: iwd" on discourse
[15:05] <slyon> - Fix ftbfs: netplan.io, procenv, sensible-utils, pexpect
[15:05] <slyon>   * pexpect awaiting Debian review, bug #1891196
[15:05] <slyon>   * sensible-utils in -proposed, bug #1891193
[15:05] <slyon> - Kicking proposed-migration for sbuild/dpkg
[15:05] <slyon> - prepared debdiff & test-runner for awscli/botocore/s3transfer SRUs
[15:05] <slyon>   * needs review, bug #1867673, bug #1875485, bug #1880999
[15:05] <slyon> [15:05] <slyon> - Published "Share your Netplan configuration!" on AskUbuntu
[15:05] <slyon> - Finished Wireguard PR#113, needs review
[15:05] <slyon> - Discussions on "OVS cloud-init first book broken" issue, PR#157
[15:05] <slyon> - Started implementing OVS settings tagging & cleanup
[15:05] <slyon> (done)
[15:05] <juliank> It's me time!
[15:05] <juliank> * more apt http method debugging and fixing
[15:05] <juliank> * fixed grubzfs-testsuite
[15:05] <juliank> * autopkgtest work:
[15:05] <juliank>   - rebased
[15:05] <juliank>   - brought lxd and cloud workers into sync
[15:05] <juliank>   - work on migrating haveged -> rng-tools
[15:05] <juliank> * starting new attempt at os-prober upgrade problem debugging/testing
[15:05] <juliank> * closed LP: #1876737 as invalid following consultation with patch upstream
[15:05] <juliank> (done)
[15:05] <bdmurray> vorlon:
[15:06] <vorlon>  * proposed-migration: rolling a few packages back (nodejs) and forward (haskell*) to move the icu+ transition closer to finishing
[15:06] <vorlon>  * dropped ocaml support from llvm-toolchain-10 on i386 to let ocaml stuff be migratable
[15:06] <vorlon>  * NEW package reviews
[15:06] <vorlon> (done)
[15:06] <bdmurray> xnox:
[15:07] <xnox> Better resolved integration & systemd migrated to release
[15:07] <xnox> Rebootstrapped rustc for riscv64 in groovy
[15:07] <xnox> Created groovy FTBFS spreadsheet and started to fix my own ones
[15:07] <xnox> Uploaded one fix for https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250
[15:07] <xnox> Worked on fixing snapd preseeding in lxd containers (handed over to lxd team)
[15:07] <xnox> Fixed https://bugs.launchpad.net/ubuntu/+source/smc-tools/+bug/1884508
[15:07] <xnox> reuploaded microcode-initrd after new reject, with fixes
[15:07] <xnox> done
[15:07] <bdmurray> tdaitx:
[15:07] <tdaitx> * jck-11
[15:07] <tdaitx>   - updated docs, compared test runs, investigated initial lxc setup
[15:07] <tdaitx>   - reviewing and testing config options
[15:07] <tdaitx> * following up on errors.u.c for openjdk-8
[15:07] <tdaitx> * fixing ftbfs (pyparted, libzstd on the way)
[15:07] <tdaitx> (done)
[15:07] <bdmurray> waveform:
[15:07] <waveform> * Catching up on e-mail after hols!
[15:07] <waveform> * Investigated wifi firmware on core18/core20; update required for core18 (definitely for core18, probably for core20)
[15:07] <waveform> * Attempted to reproduce boot cycle issue on core20 (unsuccessful so far)
[15:07] <waveform> * More bt/wifi testing for appliances
[15:07] <waveform> * Added patches for FTBFS for kbd (LP: #1891316)
[15:07] <waveform> * and open-iscsi, but that was bumped by a merge fixing it anyway (LP: #1891367)
[15:07] <waveform> * Testing "new stuff"
[15:07] <waveform> (done)
[15:08] <bdmurray> sil2100:
[15:08] <sil2100> - SRU reviews and releases
[15:08] <sil2100> - DMB meeting
[15:08] <sil2100> - Netplan code reviews
[15:08] <sil2100> - Last week: 20.04.1
[15:08] <sil2100> - Lots and lots of diverse work for 18.04.5 and 16.04.7
[15:08] <sil2100> - Some +1 maintenance
[15:08] <sil2100> - FTBFS fixes
[15:08] <sil2100> - Implementing the constant delivery of gadget snaps
[15:08] <sil2100> - Interviews
[15:08] <sil2100> - Fun with appliance images and new appliances
[15:08] <sil2100> (done)
[15:08] <bdmurray> updated python-bson package in Error Tracker environment
[15:08] <bdmurray> updated raspi imaging info for 20.04.1 LTS
[15:08] <bdmurray> added skimage to the list of "big" packages for autopkgtest
[15:08] <bdmurray> created release tracking discourse post for 18.04.5
[15:08] <bdmurray> updated autopkgtest wiki documentation regarding workers and result.tar
[15:08] <bdmurray> ran node-redis autopkgtests for bryce on arm64 canonistack unit
[15:08] <bdmurray> investigation into upgrade failure in LP: #1886748
[15:08] <bdmurray> point release work
[15:09] <bdmurray> iso testing of Ubuntu Kylin desktop for 16.04.7
[15:09] <bdmurray> ✔ done
[15:09] <bdmurray> Any questions on status?
[15:09] <bdmurray> Oh I have one!
[15:10] <bdmurray> vorlon: re nodejs I was testing some packages with a m1.large unit and they passed before the nodejs version was reverted. Should we still commit that big_packages?
[15:10] <rbalint> slyon, good job on iwd!
[15:10] <slyon> thanks! There is quite some feedback already
[15:11] <rbalint> bdmurray, i think if the likelihood of passing grows enough with large instances it is worth committing
[15:11] <vorlon> bdmurray: yes, since the new nodejs is coming back eventually
[15:11] <vorlon> (hopefully soon)
[15:11] <bdmurray> okay
[15:12] <bdmurray> #topic Release incoming bugs
[15:12] <bdmurray> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-incoming-bug-tasks.html
[15:12] <bdmurray> bug 1876737 is new
[15:13] <bdmurray> Well, juliank seems to have taken care of that.
[15:14] <vorlon> well that's easy enough, it's been marked invalid
[15:14] <juliank> Yup
[15:14] <vorlon> yeah
[15:14] <vorlon> (and I agree :)
[15:14] <bdmurray> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[15:14] <bdmurray> some ftbfs bugs have eneded up here
[15:15] <vorlon> curious
[15:15] <bdmurray> doko you did another test rebuild?
[15:15] <vorlon> were these failures present at release time?
[15:16] <doko> bdmurray: did you *read* my summary?
[15:16] <bdmurray> I was so focused on nodejs I must have missed it
[15:16] <doko> how would you know? they succeeded *brefore* the release
[15:17] <doko> there are clearly some ftbfs which were built using -proposed?
[15:18] <vorlon> strace and xz-utils were on the last test rebuild at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200327-focal-focal.html#main, pycurl and cryptsetup were not
[15:18] <vorlon> vim was not
[15:18] <bdmurray> How should we prioritize these compared to the groovy ftbfs?
[15:18] <vorlon> they're lower priority
[15:18] <vorlon> but I think we should card them anyway
[15:19] <bdmurray> Okay, I'll do that later today.
[15:20] <bdmurray> bug 1888033 - you set this to critical
[15:21] <vorlon> you is apparently xnox
[15:21] <bdmurray> you is always xnox
[15:22] <vorlon> I is?
[15:22] <rbalint> bdmurray, vorlon do we plan doing srus with the focal fixes?
[15:22] <bdmurray> rbalint: for the ftbfs?
[15:22] <rbalint> bdmurray, yes
[15:22] <vorlon> rbalint: these changes are suitable for staging in -proposed and using block-proposed-focal tags, per current SRU policy
[15:23] <vorlon> and this is fairly important so the security team doesn't have to chase build failures as part of doing a security update
[15:23] <bdmurray> Does the security team incorporate changes in -proposed?
[15:24] <xnox> vorlon:  bdmurray: i only respond to vous or You, not lowercase you.
[15:24] <vorlon> they will at least have the opportunity to look there for solutions
[15:24] <vorlon> Vy
[15:24] <bdmurray> xnox: what about YOU‽
[15:24] <xnox> bdmurray:  stop shouting, i am right here
[15:24] <bdmurray> vorlon: okay, but is it part of their process?
[15:24] <xnox> bdmurray:  yes
[15:25] <xnox> i can't remember what, but they did pick it up like that, from me for something
[15:25] <bdmurray> okay, cool
[15:25] <rbalint> vorlon, bdmurray  i do see the benefits, but compared to improving groovy i think it is so low in priority that it is not worth carding/fixing them in advance, just when an update is needed
[15:25] <bdmurray> xnox: so about bug 1888033
[15:26] <vorlon> rbalint: I'm on the fence about this; I have taken that position in the past, but here there are only 5 of them, I think it's worth putting them in the backlog
[15:26] <vorlon> (but then, I may be culling the backlog again soon)
[15:27] <vorlon> xnox: I don't agree with 'critical' here
[15:29] <xnox> vorlon:  i will respond to the bug soon
[15:30] <bdmurray> #topic Team proposed-migration report
[15:30] <vorlon> [LINK] https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[15:31] <vorlon> well it looks better than last week
[15:31] <vorlon> bdmurray: are you still on mpfr4 / python-gmpy2?
[15:32] <bdmurray> There is a new upstream version of python-gmpy2 which needs an NMU upload to Debian.
[15:32] <vorlon> but that doesn't block us from uploading it to Ubuntu in the meantime
[15:32] <bdmurray> I'm not a DD so could use help here.
[15:33] <vorlon> any DDs want to volunteer to NMU?
[15:33] <bdmurray> see debian bug 965001
[15:33] <doko> well, do the upload in groovy first, and see if it fixes the issue
[15:34] <bdmurray> Okay
[15:35] <vorlon> doko: are you still handling the lintian stuff?  I believe you were taking it because promotions were requixred
[15:36] <doko> vorlon: yes, 2.89 just migrated. not sure what I can still do before my vacation
[15:36] <xnox> huray
[15:36] <vorlon> ah ok, so maybe this is all done
[15:36] <vorlon> xnox: python-werkzeug?
[15:36] <rbalint> lintian must be much better being a long test
[15:36] <vorlon> ah you're asking for a removal
[15:36] <vorlon> I'll follow up
[15:37] <vorlon> gce-compute-image-packages: rbalint: is this still blocked on MIRs?
[15:37] <xnox> vorlon:  needs removal. sadly.
[15:38] <xnox> yeah.
[15:38] <rbalint> vorlon, yes, i'm on it
[15:38] <vorlon> ok
[15:38] <vorlon> icu... still in progress, this should be all hands on deck for +1 maintenance...
[15:38] <vorlon> which takes us down to openjdk-8 blocking gcups
[15:38] <vorlon> cups
[15:39] <vorlon> doko commented before that it's wrong for britney to have a custom trigger here
[15:39] <vorlon> nevertheless, someone needs to fix something
[15:39] <vorlon> tdaitx: can you take a look and figure out what's needed?
[15:40] <tdaitx> vorlon: yeah, needs to be blacklisted
[15:41] <vorlon> lapack seems to be new vs last week
[15:41] <vorlon> waveform: would you like this one?
[15:41] <waveform> vorlon, sure
[15:42] <vorlon> libsereal-decoder-perl: maybe just needs a retest with new lintian?  I'll follow up
[15:42] <rbalint> vorlon, i retried
[15:42] <vorlon> rbalint: ok
[15:43] <vorlon> rbalint: but I'll claim it nevertheless for followup :)
[15:43] <rbalint> vorlon, :-)
[15:43] <vorlon> python-future depends on sphinx which has autopkgtest regressions
[15:43] <vorlon> slyon: would you care to take this one?
[15:43] <slyon> vorlon: yes I will
[15:43] <vorlon> (I'll retrigger the failing tests now)
[15:44] <vorlon> glibc blocking audit... rbalint, any insight?
[15:44] <rbalint> glibc test is broken, i file a hint
[15:44] <vorlon> ok
[15:44] <vorlon> systemd migrated
[15:45] <vorlon> gmp just migrated
[15:45] <vorlon> software-properties, ddstreet asked about it on IRC, it's an i386 entanglement; I'll take this
[15:46] <vorlon> and then I think that's it for now
[15:46] <ddstreet> vorlon re: software-properties, https://code.launchpad.net/~ddstreet/livecd-rootfs/+git/livecd-rootfs/+merge/389235
[15:47]  * juliank brb
[15:47] <vorlon> ddstreet: I'm not a fan of bypassing modules we have to abstract this in favor of direct url parsing
[15:47] <vorlon> ddstreet: restoring binaries on i386 should be easy; I'll pursue that first
[15:48] <vorlon> bdmurray: anyway, done
[15:48] <bdmurray> #topic AOB
[15:50] <bdmurray> alright, let's wrap it up
[15:50] <bdmurray> #endmeeting
[15:50] <meetingology> Meeting ended Thu Aug 13 15:50:23 2020 UTC.
[15:50] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-08-13-15.00.moin.txt
[15:50] <vorlon> thanks!
[15:50] <sil2100> Oh, I'll be out on Monday if anything o/
[15:53] <rbalint> o/


[02:11] <jjesse> good evening, i just logged into launchpad on a new machine, was redirected to edge and wasn't asked to login in again, YAY YAY great job guys
[06:09] <mi3> Hello, is there a quick and easy way to connect to Launchpad with Bazaar on a network that blocks port 22 (but can allow other ports, like 443)?
[06:16] <jml> mi3: the only way I'd know of would require a little trickery
[06:17] <jml> running an SSH server / portforwarding service on port 443 on an external server that you control.
[06:21] <mi3> thanks
[06:21] <mi3> I think I'll try and ask for port 22 to be unblocked around here
[06:21] <mi3> for now :)
[09:31] <BUGabundo> hi guys
[09:31] <BUGabundo> $ bzr branch lp:gwibber  -Dhpss
[09:31] <BUGabundo> Permission denied (publickey).
[09:31] <BUGabundo> bzr: ERROR: Connection closed: please check connectivity and permissions (and try -Dhpss if further diagnosis is required)
[09:31] <BUGabundo> HPSS calls: 1 <bzrlib.smart.medium.SmartSSHClientMedium object at 0x27056d0>
[09:31] <BUGabundo> means anything to anyone?
[09:33] <mrevell> mwhudson or jml still around? If so, could you take a look at BUGabundo's message above?
[09:34] <BUGabundo> thanks mrevell
[09:34] <BUGabundo> mwhudson: jml: ping
[09:35] <mrevell> BUGabundo: They're in Aus. and NZ, so are unlikely to be around right now. abentley will be around later - he's on EST. Alternatively, send a mail over to<EMAIL_ADDRESS>[09:35] <mrevell> We'll get an answer for you, either way :)
[09:36] <BUGabundo> already debugging it on #bzr
[09:36] <BUGabundo> it would seem either a prob with my lp pgp key
[09:36] <BUGabundo> or the local config
[09:38] <mrevell> ah ok
[09:45] <BUGabundo> extra detail
[09:45] <BUGabundo> http://paste.ubuntu.com/102634/
[10:02] <BUGabundo> fixed!
[10:02] <BUGabundo> some how the key got renamed!!!!!!
[10:02] <BUGabundo> mine was .ssh/id_rsa.1.pub and not .ssh/id_rsa.pub
[10:20] <BUGabundo> filed here https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/315398
[12:07] <Narugawa> hi everyone !
[12:12] <mrevell> hi Narugawa
[12:57] <thekorn> hi, maybe I'm blind, I would like to vote for a review request, but where is thee button?
[12:57] <thekorn> https://code.edge.launchpad.net/~james-w/python-launchpad-bugs/urlerror-reason/+merge/2723 <- is the request
[12:58] <thekorn> wasn't there a button on the "add comment"-page?
[13:06] <mrevell> thekorn: Hmm, good question. Let me check something.
[13:07] <mrevell> thekorn: In the reviewer table, where your name appears beneath Brian Murray's, there should be a "Review" link next to the status
[13:21] <thekorn> mrevell, ok, thanks, found it, too many reply buttons on one page, so I missed that one
[16:48] <edgimar> Is there a way to unsubscribe to emails which come from a team mailing-list if when you joined the team you subscribed to the list?
[16:50] <james_w> edgimar: is there an "Unsubscribe" button on the team page?
[16:50] <edgimar> Not that I was able to find.
[16:50] <andrea-bs> edgimar: you can unsubscribe from the ML here: https://edge.launchpad.net/people/+me/+editemails
[16:52] <edgimar> andrea-bs: I looked at this page already, and it only allows me to select the policy for when I join a team, but doesn't let me change the actual status for a given team.
[16:53] <andrea-bs> edgimar: you can choose "Don't subscribe", can't you?
[16:55] <edgimar> andrea-bs: there are three options, under the "when should launchpad automatically subscribe you to a team's mailling list?", and other than that, I don't see anything pertaining to specific teams.
[16:55] <andrea-bs> edgimar: are you sure that you are receiving mails from a mailing list and not from the bug tracker or something?
[16:56] <edgimar> Perhaps it is from a bug-tracker.  If so, then I should re-state my question -- how do I turn on/off the receiving of bugs for a team per email?
[16:56] <edgimar> (in general, not per-bug)
[16:57] <andrea-bs> edgimar: if your team is subscribed to all bugs for a project, then you have to ask the team admin to unsubscribe from the project or to filter mails with your client
[16:58] <edgimar> andrea-bs: that's unfortunate.  Any plans to add this feature?
[16:58] <edgimar> (since of course some members of a team might like to receive bugs via email, and others not)
[16:59] <andrea-bs> edgimar: well, I'm not the right person to ask to, I'm just a LP user :)
[16:59] <edgimar> any ideas where to direct the inquiry then?
[16:59] <andrea-bs> edgimar: you may report a bug asking for this feature: https://launchpad.net/+filebug
[16:59] <edgimar> ok, thanks.
[16:59] <andrea-bs> edgimar: oops: https://launchpad.net/launchpad/+filebug
[17:18] <vadi2> I have two emails registered with launchpad, and it's mistaking the user from who I sent the emails. Is it possible to make launchpad stick to one email only?
[17:20] <beuno> vadi2, you decide which of the two is the default
[17:20] <vadi2> how?
[17:22] <beuno> vadi2, in your profile page, click on "change details"
[17:22] <beuno> and then, "Email settings"
[17:23] <vadi2> got it
[17:24] <vadi2> thanks!
[18:15] <mrevell> New podcast episode! http://news.launchpad.net/podcast/launchpod-15-launchpads-going-open-source
[19:10] <flavour> barry: As help contact can you let me know ehther it's possible to rename an LP site?
[19:11] <LarstiQ> flavour: LP site? Do you mean a project?
[19:11] <barry> flavour: do you want to rename a launchpad team or project?
[19:13] <flavour> barry: Both, but the Project is most important
[19:13] <flavour> I already changed the name on the page, but the URL should change too really
[19:17] <barry> flavour: you should open a question on launchpad for this: https://answers.launchpad.net/launchpad/
[19:17] <flavour> Right...it is possible then?
[19:17] <flavour> Or tou're not sure?
[19:17] <barry> flavour: a launchpad administrator (which i am not) can make the change for you
[19:17] <flavour> ok, thanks
[19:17] <flavour> I'll post there & see what happens :)
[19:17] <barry> np
[19:17] <barry> :)
[19:18] <barry> flacoste: i'll make sure the question is assigned to the right person.  paste the question url here when you've added it
[19:18] <barry> flavour: ^^
[19:18] <barry> flacoste: nm!
[19:20] <flavour> barry: https://answers.launchpad.net/launchpad/+question/56871
[19:20] <flavour> I see others have asked this in the past...must be fairly common ;)
[19:22] <barry> yeah.  unfortunately it's not something that you as project owner can do thru the web
[19:22] <barry> flavour: also, i don't believe the old urls can be forwarded
[19:24] <flavour> ok, np
[19:24] <flavour> Not too big a deal just now
[19:24] <flavour> Which is why I put it inbrackets
[19:56] <beuno> barry, isn't that what salgado did?
[19:56] <beuno> with project aliases and such?
[19:56] <barry> beuno: oh, you're right. how do you set up an alias?
[19:57] <beuno> I have no idea  :)
[19:57] <salgado> barry, ask one of the LOSAs
[19:57] <barry> salgado: an alias has to be set up by a losa?
[19:57] <salgado> yep
[19:58] <barry> salgado: cool.  flavour's question should work for him then
[19:58] <salgado> cool
[19:58] <salgado> gotta go now
[20:08] <soc> hi
[20:09] <soc> i just wondered if there is a plan to improve the profile page a bit?
[20:09] <soc> currently i use it as some sort of todo list ...
[20:09] <soc> but afaik there is no support for tables and so on ...
[20:11] <jturney> I'm having a problem using my PPA; the dput succeeds, but then nothing happens; I've almost certainly made the package wrongly... but I don't get any clue what's wrong
[20:11] <bigjools> jturney: how long ago did you upload?
[20:12] <jturney> I tried a few days ago
[20:12] <jturney> I tried again a couple of times in the past couple of hours
[20:13] <beuno> soc, yes, we are working out on how to provide personal dashboards
[20:14] <soc> beuno: that's very good to hear
[20:14] <soc> most people argue, that i could do the same thing with a desktop application
[20:14] <soc> but i'm often on different computers, so haveing one single place for my todo list, bugs, translations, packages would help enourmously!
[20:15] <soc> having some table support an being able to color the table background would be enough for me ...
[20:15] <beuno> yeah, I feel the same way about desktop apps
[20:15] <beuno> well, I'm not sure if we're thinking about the same thing
[20:16] <beuno> a ToDo list would revolve around bugs/blueprints/code
[20:16] <beuno> not arbitrary lists
[20:17] <soc> "ToDo list" might not be the right word ...
[20:18] <soc> at the moment i have mess like that: https://launchpad.net/~soc-krg-nw
[20:19] <asabil> hi all
[20:19] <asabil> is there any admin here able to create a meta project ?
[20:21] <beuno> soc, well, what will make it easier for you, is our inline-editing with ajax. So you will just click, edit, save.
[20:21] <matsubara> asabil, ask in https://launchpad.net/launchpad/+addquestion. please provide the name of the meta project you'd like and the names of the projects that would be under it
[20:22] <asabil> matsubara: already done
[20:22] <jturney> How long might I expect to wait for the mail with the .changes file at the moment, then?
[20:22] <asabil> https://answers.edge.launchpad.net/launchpad/+question/55914
[20:23] <matsubara> asabil, it's assigned to kiko and he's on a sprint. Likely that he'll take care of that next week
[20:23] <asabil> ok thanks
[20:24] <soc> beuno: that sounds great!
[20:24] <beuno> soc, that's actually one of the features that will land first  ;)
[20:41] <soc> thanks!
[20:42] <soc> glad to hear that
[20:47] <maxb> jturney: If your uploaded .changes is not signed, or is not signed with the right pgp-key, I think you currently get no error email (because in that case launchpad doesn't actually know who did the upload)
[20:52] <jturney> I'm specifying the  signing key id  0x7633C10E, which is the one I have configured on launchpad
[20:54] <jturney> dput says there is a good signature made with that key when I do the upload
[20:58] <bigjools> jturney: what maxb said, double check your signatures.
[21:02] <jturney> http://pastebin.com/m315e9705
[21:03] <jturney> https://launchpad.net/~jon-turney
[21:10] <bigjools> jturney: can I see your dput.cf please
[21:11] <jturney> sure
[21:12] <jturney> http://pastebin.com/m1d9666a2
[21:13] <bigjools> cprov, are you around?
[21:19] <bigjools> mthaddon: still about?
[21:19] <mthaddon> bigjools: yep
[21:20] <bigjools> mthaddon: aha - can you help jturney see what happened to his missing upload please?  It'll be in the failed upload area on germanium I guess
[21:20] <mthaddon> bigjools: he doesn't get a log/email response of that?
[21:21] <bigjools> mthaddon: no, it's some failure mode that prevents email
[21:21] <bigjools> usually a key problem
[21:38] <bigjools> jturney: http://launchpadlibrarian.net/21065116/eJdXmBy38Eh5kNV8KxOKurMoN36.txt
[21:39] <bigjools> thanks for helping mthaddon
[21:39] <maxb> Hmm - why doesn't launchpad email the owner of the PPA if it can't deduce an identity from the key?
[21:39] <mthaddon> bigjools: np, thx for talking me through it
[21:39] <bigjools> maxb: to avoid spamming the innocent
[21:40] <bigjools> we'll be doing ssh-based uploads in the future which will avoid this problem
[21:42] <jturney> hmm... ok.... so can I simply remove the ~ppa suffix from the changes file?
[21:43] <bigjools> you need pidgin-musictracker_0.4.12-2_source.changes
[21:43] <jturney> oh, or is that telling me <arch> is missing
[21:43] <jturney> right :-)
[21:44] <bigjools> this warrants a bug report if you wounld't mind :)
[21:44] <bigjools> erm *wouldn't*
[21:44] <jturney> sure
[21:44] <bigjools> thanks
[21:44] <jturney> oh, no, thank you :)
[21:44] <bigjools> we aim to please :)
[21:45] <bigjools> now, it's Friday night and I need a beer.  Goodnight all.
[22:45] <maxb> Does anyone have a rough estimate on the ETA for signed PPAs? Is it days, or weeks?
[22:46] <maxb> (and maybe a note could be added to bug 125103 for others to see)
[22:49] <barry> maxb: i do not know the eta for that and unfortunately i think the people who might know are all gone for the weekend.  let me ask around though
[22:49] <maxb> Well, I don't expect it to happen over the weekend, so I can guess "at least two days" :-)
[22:50] <maxb> But it would be nice to have some sort of indication on whether I should be eagerly checking the keyserver next week, or being patient :-)
[22:52] <barry> maxb: i've been told we're waiting on some new hardware.  i don't have an eta
[22:55] <maxb> Fair enough - maybe the relevant people could be asked nicely to publish an eta in the bug when it becomes available?
[22:56] <barry> bigjools: ^^
[23:15] <barry> have a good weekend everyone
[23:42] <IndigoJo> hi everyone
[23:42] <IndigoJo> can anyone help with building a package of mercurial (the DVCS) in my ppa? specifically with getting rid of some obsolete packages
[23:42] <IndigoJo> patches, I mean
[23:42] <IndigoJo> in the debian/patches directory
[23:43] <ScottK> IndigoJo: Are you trying to update to the new version?
[23:43] <maxb> IndigoJo: I've done that in my PPA, want to just grab it?
[23:44] <IndigoJo> oh? you've packaged hg v1.1.2?
[23:44] <maxb> yes
[23:44] <IndigoJo> great
[23:44] <IndigoJo> that's great
[23:44] <ScottK> maxb: Interested in helping get it into Debian/Ubuntu?
[23:44] <IndigoJo> just for future ref, how did you deal with the patches directory full of patches which had already been merged upstream?
[23:46] <maxb> ScottK: yes, I need to find the time to test it with its rdepends, though
[23:46] <ScottK> maxb: In the Debian Python Applications Packaging Team (PAPT) svn there's a draft package that's being worked on.
[23:46] <ScottK> maxb: You might join #debian-python on OFTC and join into the effort already in progress.
[23:47] <IndigoJo> maxb: also, do u want me to add the info about your packages to the mercurial wiki?
[23:48] <maxb> IndigoJo: sure, go ahead
[23:48] <ScottK> IndigoJo: To answer your question, remove them from debian/patches and debian/patches/series or debian/patches/00list if one of those exists.
[23:49] <maxb> ScottK: oh, I'm a fool, I checked the packaging svn, but now I realize I should have looked for branches, not just at trunk, what with the lenny freeze :-)
[23:49] <ScottK> maxb: Actually it's not due to freeze it's due to a new person not knowing better.
[23:49] <ScottK> maxb: There's a ML you can follow to (which is how I know).
[23:51] <maxb> huh, indeed there are no branches
[23:53] <ScottK> He merged it into trunk earlier today.
[23:53] <ScottK> At least according to the CIA bot on #debian-python.


[07:27] <dholbach> good morning
[17:30] <PaulW2U> pleia2: editorial review / proof reading all done
[17:31] <pleia2> PaulW2U: thanks!
[22:09] <jose> pleia2: hey, I think we can disable new user creation if you're still an admin
[22:09] <pleia2> jose: I'm not
[22:10] <jose> oh, well
[22:10] <pleia2> jose: admin was removed from all community members :(
[22:10] <pleia2> now the only control we have over user accounts in fridge is by editing the lp teams
[22:16] <jose> pleia2: try asking for admin again, we do need it
[22:16] <pleia2> my current strategy is death by rt tickets ;)
[22:18] <pleia2> but seriously, as a sysadmin I know how annoying it is for users to just beg for admin, trying to work within the bounds they've set up and we can reassess if they don't want to manage the deluge of user accounts
[22:19] <pleia2> even if I don't agree with how they did it (surprise, no more admin for you!) I do think restricting access in general it smart
[22:20] <pleia2> some day we'll teach canonifolks to communicate with community members ;)
[22:22] <Unit193> Sure.
[22:32] <jose> :)
[22:32]  * jose agrees


[00:22] <belkinsa> Alright, I will
[00:43] <belkinsa> (tomorrow though)
[08:17] <dholbach> good morning


[00:00] <sarnold> TIL askubuntu.com has a "login with launchpad" option
[00:01] <sarnold> semitones: despite the name, the launcpad team doesn't actually maintain the ubuntu sso service
[00:02] <sarnold> semitones: there's a faq at https://help.ubuntu.com/community/SSO/FAQs and an RT instance at https://support.one.ubuntu.com/ -- if you can't use that rt thing, email<EMAIL_ADDRESS>will probably work
[00:49] <semitones> Thanks sarnold I'll look into it
[09:49] <guruprasad> semitones, iirc, there have been a few users who has asked about a similar issue and based on the investigation that I did at that time, it looked like the issue was likely on AskUbuntu's side and we needed them to investigate and provide us details.
[12:08] <semitones> Thanks for the info. Hopefully they do so soon


[06:13] <IamEthos> is Ubuntu mobile being planned to work on Palm Tungsten devices?
[02:17] <Mithrandir> IamEthos: it's not part of our initial set of devices we target.


[03:40] <Pwnna> does anyone know how to configure XF86AudioMicMute? It's not by default configured
[03:41] <Pwnna> i can detect the button, but it is definitely not configured
[09:02] <elfy> dkessel: I commented on your comment at trello
[09:08] <elfy> use a pad - with a sensible name for it perhaps :)
[09:10] <dkessel> elfy: ok, will do
[09:26] <dkessel> elfy: http://pad.ubuntu.com/xubuntu-qa-v-autopilot
[09:27] <elfy> ta
[10:05] <ochosi> morning folks
[10:05] <ochosi> and happy blueprinting day
[10:05] <knome> is the umbrella blueprint set up already?
[10:07] <ochosi> man, i just got up!
[10:07]  * ochosi needs coffee
[10:07] <knome> haha, me too, but who knows
[10:07] <knome> i can set it up as well if you are too lazy
[10:09] <dkessel> morning ochosi
[10:09]  * elfy thinks if the XPL wants team leads to do theirs the least the XPL can do is the main one - and theirs too :D
[10:09] <knome> ;)
[10:10] <dkessel> hmm i found a bug while trying to verify my german translation of the xubuntu-docs.... has any of you tried to do the steps for using ndiswrapper this cycle? :p
[10:10] <elfy> what's ndiswrapper ...
[10:10] <dkessel> the configuration tool won't open from the settings manager... "gksu" not found
[10:11] <knome> elfy, a wrapper that allows you to use windows drivers with linux
[10:11] <dkessel> "Xubuntu supports a system known as NDISWrapper. This allows you to use a Windows wireless device driver under Xubuntu."
[10:11] <zequence> better to use polkit
[10:12] <zequence> That tool might need to be repackaged
[10:12] <knome> dkessel, file a bug against xubuntu-docs and start working on it ;)
[10:12] <zequence> synaptic is an example for how to do that
[10:12] <zequence> (using polkit instead of gksu)
[10:12] <knome> we've already shipping pkexec policy files for some apps
[10:13] <knome> *we're
[10:13] <dkessel> so you suggest filing a bug against ndisgtk? and then adding a policy file in some package ?
[10:13] <zequence> The policy file should he addeed to the package itself
[10:13] <dkessel> ah ok
[10:14] <knome> and if the documentation tells you to use gksu, then you should file a bug against the docs to change that part too
[10:14] <dkessel> knome: no it just tells the user to click the icon, so that's fine I guess :)
[10:14] <zequence> probably the desktop file has a startup command with gksu
[10:14] <knome> right
[10:14] <knome> yep.
[10:15] <knome> and hey zequence :) what's up?
[10:16] <zequence> knome: Not much right now. Thinking about eating breakfast. You?
[10:16] <knome> sameish thoughts
[10:21] <ochosi> aaahh, nice, much betterr now....
[10:21] <ochosi> morning dkessel
[10:22] <elfy> seed gksu ... just saying :p
[10:24] <dkessel> i am on trusty currently. does anybody want to verify bug 1385841 for utopic?
[10:26] <ochosi> https://blueprints.launchpad.net/ubuntu/+spec/topic-v-flavor-xubuntu
[10:26] <brainwash> the report does not mention why gksu should not be used
[10:26] <ochosi> team leads, start your engines ^
[10:30] <knome> created and linked the sub-blueprint for website
[10:31] <ochosi> artwork is done too
[10:32] <ochosi> oh, qa too
[10:32] <ochosi> nice
[10:32] <ochosi> this is going much better than anticpated :)
[10:32] <ochosi> i'll set up features next
[10:34] <ochosi> and linked
[10:36] <elfy> bug fixes done and linked
[10:36] <elfy> qa blueprint work items added
[10:36] <knome> and please propose the series goal for vivid
[10:37] <knome> so once we are ready setting the blueprints up, we can easily ask the release team to accept them to allow them to show up in status.ubuntu.com
[10:37] <ochosi> only marketing missing now
[10:37] <knome> i can set that up
[10:38] <ochosi> all of mine are proposed for vivid
[10:38] <knome> done
[10:39] <ochosi> oh, just wanted to propose i do marketing so we're done... :) ty knome
[10:40] <knome> now send a mail for the -release team and list the blueprints and ask them to approve them
[10:40] <ochosi> elfy: what about linking trello in the qa blueprint? that way ppl can find it
[10:40] <ochosi> knome: release team or release ml?
[10:41] <knome> ml
[10:41] <ochosi> k
[10:41] <ochosi> thought so :)
[10:41] <knome> yep, sorry for being ambiguous
[10:41] <ochosi> np
[10:42] <elfy> ochosi: yep - not sure if you got mail re qa trello - it's public now
[10:42] <ochosi> elfy: yeah, i received it, that's why i meant you can actually link to it there too
[10:48] <elfy> thought as much - just checkiing :)
[10:52] <elfy> so while there's a bunch of us mulling about - can we please get some resolution on staging PPA
[10:53] <elfy> if it's staying with what it has - what other PPAs do I need to be as up to date as possible - shimmer etc I'm thinking of here
[10:58] <brainwash> ali1234: does bug 1379176 affect the normal Xfce session (xubuntu-free user account)?
[11:06] <elfy> ochosi: don't forget to approve the blueprints - at least I assume you should be doing so
[11:07] <ochosi> elfy: yeah, shimmer is a good idea for the artwork
[11:07] <ochosi> the daily one
[11:08] <ochosi> i missed out on the PPA discussion a bit
[11:08] <elfy> :)
[11:08] <ochosi> what was the problem with staging exactly?
[11:09] <knome> balancing doing enough daily builds and not becoming a massive daily buildfest with hundreds of megs of update every day
[11:09] <elfy> not a problem per se , I just really wanted there to be one
[11:10] <elfy> and if not at least some idea of the hundreds of extra PPAs the only person in team that's needing to have to see what's going on
[11:10] <ochosi> i'd actually like to set some goals on what apps we're gonna work on
[11:10] <ochosi> and then switch on daily builds for those
[11:10] <ochosi> but we need bluesabre around for that
[11:11] <elfy> shimmerproject/+archive/ubuntu/daily <- that one?
[11:11] <elfy> really all these other ones should be listed somewhere
[11:11] <ochosi> yeah, we should make a list...
[11:12] <ochosi> re: blueprints approval: i'm only approving blueprints that have content
[11:12] <ochosi> e.g. for marketing there's nothing to approve yet
[11:12] <elfy> eg for QA there is :p
[11:12] <ochosi> i think just adding the "approved" tag to any blueprint makes it sorta meaningless
[11:12] <ochosi> yeah, and it's approved too ;)
[11:13] <elfy> says approver none :)
[11:13] <elfy> mmm
[11:13] <ochosi> not anymore
[11:13] <ochosi> but yeah, i didn't look there cause all the other blueprints had that filled out already
[11:13] <elfy> ok - so I'm so quick to set wallpapers and themes and icons to what I normally use
[11:14] <elfy> I'd best set them to default or any changes to shimmer ppa daily will not affect me lol
[11:14] <ochosi> probably, yeah ;)
[11:14] <elfy> heh
[11:14] <ochosi> although wallpaper doesn't matter
[11:14] <ochosi> as long as you use greybird and elementary-xfce-darker, that's it
[11:15] <elfy> yep
[11:15] <ochosi> then you should notice any breakage/missing icons
[11:16] <elfy> yep
[11:16] <elfy> installiing that ppa now
[11:16] <ochosi> just FYI, as soon as V gets a gtk3 update, the themes will all be broken
[11:16] <elfy> okey doke
[11:17] <ochosi> we don't have support for gtk3.14 yet
[11:17] <elfy> you can probably approve https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-v-bugs too - that won't get content till we start filling in bugs
[11:18] <ochosi> indeed, done
[11:20] <elfy> awesome - I'll leave you in peace now for a while then :D
[11:21]  * elfy is off for a bit fiddling with the qa processes rewrite
[11:22] <elfy> knome: did you see http://pad.ubuntu.com/upgrading ping ?
[11:22] <knome> yes
[11:22] <ochosi> cool, well thanks elfy!
[11:22] <ochosi> that was a nice sprint
[11:22] <knome> will have to take a real look at that $some_time
[11:22] <knome> bookmarked
[11:23] <elfy> yea cool
[12:03] <elfy> http://cdimage.ubuntu.com/xubuntu/daily-live/current/
[12:03] <elfy> \o/
[12:04] <ochosi> oh nice
[12:06] <elfy> missing from tracker - but so is everything atm
[12:13] <dkessel> ...and that image requires switching to vt1 and back to vt7 with virtualbox....
[12:14] <elfy> dkessel: it will - there's been no fix yet
[12:14] <dkessel> elfy: i am installing ;)
[12:14] <elfy> dkessel: I upgraded on Friday morning :)
[12:27] <knome> i guess i should update soonish
[12:27] <knome> ...to 14.10 ;)
[12:28] <elfy> heh
[12:30] <knome> ochosi, how do you plan using https://wiki.ubuntu.com/Xubuntu/Roadmap/ ?
[12:38] <elfy> as a general thing re pkexec - what's going to be our plan here
[12:39] <elfy> ndiswrapper might not have gksu - but if we get involved in each and every thing that might need dealing with - we'll never end
[12:39] <elfy> shouldn't that be a general ubuntu thing to deal with?
[12:40] <brainwash> isn't it a general ubuntu thing?
[12:40] <brainwash> ubuntu does not install the gksu
[12:40] <brainwash> package
[12:40] <elfy> I'd assume so - was just thinking given the discussion earlier
[12:42] <brainwash> ideally the gksu package should be removed from the repo completely
[12:43] <brainwash> to complete the pkexec transition
[12:43] <knome> elfy, we can kickstart the process to get it done; eg. file bugs when gksu is used instead of pkexec
[12:43] <knome> and i think that's where our responsibility ends
[12:44] <elfy> yep
[12:44] <elfy> works for me
[12:55] <ochosi> knome: haven't given that much thought tbh
[12:55] <ochosi> why, do you have a proposal? :)
[12:56] <ochosi> i mean i liked how we did in trusty
[12:56] <ochosi> although i also don't mind if ppl put their stuff directly into blueprints
[12:56] <ochosi> but i guess the spec has the advantage of keeping things on a single page
[12:57] <knome> just asking
[12:57] <knome> i don't think there is one right way
[12:57] <knome> but otoh, if we aren't using it, then let's not pretend we are :)
[13:01] <ochosi> sure
[13:01] <ochosi> i actually wanted to wait for bluesabre to chip in about features and stuff and then decide what to do with it
[13:02] <ochosi> frankly, it's also a bit cumbersome to use and slow, so i'm not entirely sold on the wiki
[13:02] <elfy> amen to that
[13:03] <bluesabre> good morning folks
[13:03] <ochosi> oh wow, speak of the "devil"
[13:03] <elfy> :)
[13:04] <elfy> morning bluesabre
[13:04] <bluesabre> (:c
[13:04] <bluesabre> time to catch up on backlog
[13:10] <bluesabre> ok, caught up
[13:11] <bluesabre> for any packages we don't ship, but maybe use and should have pkexec policies, make a list somewhere. We can update the packages and get them sponsored... that's relatively painless
[13:12] <ochosi> good idea
[13:12] <bluesabre> I'm going to do a better job of monitoring xubuntu-v-bugs this cycle, so anything that needs a fix (thunar for instance), link it
[13:13] <ochosi> could even just submit bugreports and add them to the bugs bp
[13:13] <elfy> I linked 3 to that bluesabre
[13:13] <bluesabre> also, xfdesktop and thunar both use glib, does this bug affect xfdesktop as well?
[13:14] <bluesabre> I started this pad for development, we can use it to put together ideas for dev this cycle, http://pad.ubuntu.com/xubuntu-v-dev
[13:14] <bluesabre> or any other considerations
[13:14] <ochosi> bluesabre: you could link to that in the features bp
[13:15] <ochosi> just so that we have common places to look when we "lose" links to stuff
[13:15] <bluesabre> oh, this is just for today.  Going to port over to a dev blueprint as we finalize today
[13:15] <ochosi> oh right
[13:16] <ochosi> wrt upower 0.99, theoretically we should be safe
[13:16] <bluesabre> elfy, great, thanks
[13:16] <ochosi> iirc all xfce components received patches, so theoretically, things should work
[13:16] <bluesabre> right
[13:16] <ochosi> bluesabre: what i mentioned earlier wrt evince, you just have to open it on its own
[13:17] <ochosi> without file
[13:17] <ochosi> then you see the recent-view
[13:17] <bluesabre> ok, I'll take a look at that
[13:17] <ochosi> it's kinda neat
[13:17] <ochosi> haven't checked out the code for it yet though
[13:17] <bluesabre> ok, I see
[13:18] <ochosi> i mean we could also just do an icon-view of all media-files in the recent menu
[13:18] <ochosi> or something like that
[13:18] <bluesabre> yeah
[13:18] <bluesabre> there might even be a new widget implementing that
[13:18] <ochosi> yeah, possibl
[13:18] <ochosi> e
[13:18] <elfy> bluesabre: as far as planning what's going to be worked on will affect when we call for testing OR we can just extra call as and when
[13:19] <elfy> I just need to know what *we* would prefer early enough
[13:20] <bluesabre> right
[13:21] <bluesabre> I'll probably do some dev releases of some components only to -staging, its hard to give a specific time frame when these will be complete though
[13:23] <elfy> ok so plan B :)
[13:23] <elfy> I'll do a schedule and then we can shove extras in as and when :)
[13:24] <bluesabre> I'll try to target early milestonesn as much as possible
[13:24] <elfy> won't be doing that till I've seen release schedule
[13:24] <elfy> okey doke
[13:25] <bluesabre> ochosi: what's the general consensus among xfce-dev about getting 4.12 out by the end of the year?
[13:25] <knome> bluesabre, aren't you two of the few, and you both want it out :)
[13:26] <bluesabre> I want it out, but I work on very few components
[13:26] <bluesabre> if I release xfce4-settings 4.12.0, Nick will return, but only to slap me
[13:26] <ochosi> bluesabre: no consensus
[13:27] <knome> bluesabre, but you should still do that, if that's ready for the 4.12 release
[13:27] <ochosi> nick is away a few more weeks he said
[13:27] <bluesabre> knome: its... almost there
[13:27] <ochosi> so i think it's unrealistic to assume a release will happen this year
[13:28] <elfy> is Mir going to start affecting us anytime soon?
[13:35] <knome> not sure if it's something for -docs actually
[13:36] <knome> ochosi, there's no docs blueprint!!
[13:36] <bluesabre> yeah, definitely more docs-y
[13:36] <elfy> slickymaster's surfing ;)
[13:36] <knome> i'll do that.
[13:39] <knome> docs blueprint created
[13:43] <bluesabre> knome: thanks, added some details to the pad, will add more later
[14:20] <elfy> ochosi: what do you suggest as a permanent(ish) home for the QA incentive details?
[14:20] <slickymaster> elfy, actually I'm actually with a terrible headache and a bit hungover
[14:21] <elfy> slickymaster: lol
[14:21] <slickymaster> but I see there's already a lot work done
[14:21] <elfy> yea
[14:21] <slickymaster> let just catch up on what's been made so far
[14:21] <slickymaster> + me
[14:26] <slickymaster> do we already have any clue of when the new NetworkManager will land?
[14:26] <slickymaster> Unit193 ^
[14:42] <bluesabre> ochosi: ping
[14:45] <elfy> heh - just about to point somewhere similar :)
[14:45] <elfy> ochosi: tried to make http://pad.ubuntu.com/xubuntu-qa-v-cycle less officialese
[14:45] <elfy> and knome - you could have a look when you've time too
[14:46] <knome> sure, will do at some point
[14:46] <knome> (again...)
[14:46] <elfy> yep
[14:47] <slickymaster> knome: thatnks for covering for me and drafting the docs blueprint
[14:48] <slickymaster> *thanks
[14:54] <elfy> bluesabre: so basically I assume you're happy that I'll do a testing schedule like normal and then fit things in as and when they need it?
[14:55] <knome> slickymaster, no problem
[14:55]  * slickymaster is a bit sick :P
[14:55] <bluesabre> elfy: yeah, and I'll coordinate with you when there is testing to be done
[14:56] <bluesabre> where is the team image/hardware/testing page again?
[14:56] <ochosi> bluesabre: pong
[14:56]  * ochosi needs to read up on the backlog
[14:56] <bluesabre> ochosi: Ubuntu dev folks patch away Headerbars on evince... but why not simple scan?
[14:56] <bluesabre> pretty sure they ship both
[14:56] <knome> bluesabre, ask them :)
[14:56] <ochosi> good question
[14:57] <ochosi> knome is right, we should ask them
[14:57] <bluesabre> knome: asked ochosi since he seems to be in the know :)
[14:58] <knome> lol
[15:03] <elfy> bluesabre: https://wiki.ubuntu.com/Xubuntu/Testing/TeamHardware
[15:03] <bluesabre> elfy, thanks
[15:04] <bluesabre> wondering if we can extend that with a few specifics... like monitor count
[15:05] <elfy> bluesabre: well ...
[15:05] <knome> elfy, poked
[15:05] <elfy> given that it takes a thousand attempts to get a simple one done - if you want something more elaborate - please do your own ;)
[15:05] <elfy> knome: thanks :)
[15:06] <elfy> bluesabre: but seriously if you think it's helpful to know - change it :)
[15:07] <elfy> sometimes I suspect it might be helpful to know it it's laptop or desktop too I guess
[15:07] <knome> if we add monitor count, is it useful to know i can do two-monitor testing on a non-development version?
[15:07] <bluesabre> yeah, laptop vs desktop, gfx card
[15:07] <knome> or maybe we should add one more column
[15:07] <bluesabre> knome: yes, since we develop the portion of xfce4-settings that handles monitors
[15:08] <knome> for the "hardware id"
[15:08] <knome> and separate the vbox list
[15:08] <ochosi> bluesabre: +1 on monitor/graphics card info
[15:09]  * bluesabre waits forever for ubuntu wiki to log him in
[15:09] <knome> elfy, allow me to poke the page in the way i suggested?
[15:09] <slickymaster> knome, hardware id? you mean something like https://wiki.ubuntu.com/QATeam/Hardware
[15:09] <knome> slickymaster, no, i mean like
[15:10] <elfy> knome: yea go ahead
[15:10] <knome> every member should add one line per a hardware configuration
[15:10] <knome> bluesabre, no poking now then
[15:10] <elfy> but for instance I do dailies on VM, milestones on laptop hence only manual partition
[15:10] <bluesabre> knome: sure, still logging in
[15:10] <knome> yep
[15:11] <elfy> but once or twice a cycle I'll do hardware on desktop
[15:11] <elfy> knome: yea - one line per available hardware config would do - but it's getting people to actually do it :)
[15:12] <knome> elfy, yeah
[15:12] <elfy> that's useful info for lots of us I would think
[15:13] <elfy> I'd like to know I could ask foo to check something on laptop for instance
[15:14] <bluesabre> cleaned up the dev pad a bit, http://pad.ubuntu.com/xubuntu-v-dev
[15:15] <elfy> bluesabre: ta
[15:15] <elfy> so other than staging and shimmer ppa I've got currently anything else I *need* to add here
[15:16] <ochosi> bluesabre: what do you think about just copying over e.g. git versions from parole that we want testers to check out to the staging ppa from the parole-daily PPA?
[15:16] <ochosi> and same for themes/icons
[15:16] <knome> ok, lookie at the wikipage
[15:17] <knome> elfy, ochosi: you obviously want to change some details...
[15:17] <bluesabre> elfy: yeah, everything should be in those two
[15:17] <elfy> :)
[15:17] <bluesabre> ochosiL that makes sense
[15:17] <elfy> bluesabre: ok cool
[15:17] <knome> maybe other/comments could be combined
[15:17] <ochosi> knome: i think we might need >1 line per tester
[15:17] <elfy> I guess I should try and use things like parole a bit more during cycle
[15:18] <ochosi> i have desktop @work and laptop @home
[15:18] <knome> ochosi, yes, then you should add one more line
[15:18] <elfy> ochosi: yea - I'm just going to add one for me
[15:18] <knome> note the HWID field
[15:18] <knome> and the note about the HWID field :P
[15:18] <elfy> or will when ochosi tells me I can access it
[15:18] <knome> ;)
[15:18] <knome> ochosi, while you're at it, remove the "other HW information" column
[15:19] <ochosi> okok
[15:20] <ochosi> i'm done
[15:20] <ochosi> mostly
[15:25] <elfy> done
[15:25] <elfy> filling that in actually made me realise that I can do 2 monitors for laptop if we need to test something :)
[15:26] <elfy> caq5C4#
[15:26] <elfy> sigh
[15:26] <knome> lol
[15:26] <knome> elfy, i'd advise you to change your ubuntu one password
[15:27] <elfy> heh
[15:27] <knome> ;P
[15:27] <elfy> I had to do that a while back because of similar elsewhere :D
[15:27] <knome> yep
[15:37] <bluesabre> added mine
[15:37] <bluesabre> thanks guys, this will help track down unfortunate people
[15:38] <elfy> lol
[15:38] <elfy> but you could have made it alpabetical :|
[15:38] <bluesabre> oh dang it
[15:38] <elfy> awesome
[15:38] <bluesabre> did elsewhere, will do that now
[15:38] <elfy> so - found a bug in vivid ...
[15:38] <bluesabre> or not
[15:38] <elfy> bluesabre: I'm joking :D
[15:39] <elfy> everyone else will just tag on the bottom :)
[15:39] <bluesabre> elfy: I'm not... a bit ocd with alphabetizing
[15:39] <bluesabre> vivid bug already, nice one
[15:39]  * elfy waits for bluesabre to finish ...
[15:39]  * bluesabre is finished
[15:39] <elfy> bluesabre: not really - changing machine password - and it's hanging ...
[15:40] <ochosi> bluesabre: looks good to me
[15:40] <ochosi> Lockerkim though?
[15:41] <bluesabre> cat hopped on keyboard, wasn't sure what she types
[15:41] <knome> :D
[15:42] <bluesabre> elfy, users-admin from terminal... wonder if there is any useful output
[15:44] <elfy> just started it again
[15:45] <elfy> killed existing - hadn't done anything ran it again and it worked ok
[15:54] <bluesabre> ochosi: can you add any roadmaps that I am missing at the bottom of the pad?
[15:55]  * bluesabre needs to create some for catfish, menulibre, mugshot
[15:57] <ochosi> bluesabre: done
[15:57] <bluesabre> ochosi: thanks. I'll create and link roadmaps for the other projects, and we can start planning there
[15:59] <ochosi> cool
[15:59] <ochosi> sounds good to me
[15:59] <knosys> hey all
[16:08] <bluesabre> ochosi: will expand out from here :) http://wiki.smdavis.us/doku.php?id=development
[16:08] <bluesabre> hey knosys
[16:08] <knosys> hey :)
[16:11] <elfy> hi knosys
[16:18] <knosys> hey guys, its weird, i can't see translations anymore in launchpad. Why is that?
[16:18] <elfy> no idea - I've enough problems with English
[16:19] <knosys> "is not an active member of any Launchpad teams. " That is show on my profile. Does that means that i can't review translations anymore?
[16:20] <knosys> Oh wait, sorry i was on another different project. I should be looking to "xubuntu documentation"
[16:21] <knosys> my bad!
[16:23] <ochosi> bluesabre: cool, good overview there
[16:25] <elfy> ochosi: one other QA thing while I remember - what more to do with qa incentive and then where we going to store that - testing wiki page ?
[16:25] <elfy> last probably makes more sense - then it's just a link elsewhere
[16:34] <knome> elfy, or since it's an end-user facing thing (mostly) it could also go on the website
[16:34] <elfy> true
[16:34] <elfy> probably even better
[16:35] <elfy> it'll certainly get noticed more there I should think :)
[16:35] <knome> yep, especially if we advertise that page set
[16:36] <bluesabre> knome: your requests are now on the menulibre roadmap :) http://wiki.smdavis.us/doku.php?id=development:menulibre
[16:37] <elfy> knome: I'll start finishing that off and get it on a draft page at x.org
[16:37] <knome> great
[16:40] <bluesabre> lunchtime, bbl
[17:11] <elfy> ok - so there's a bit at the top of http://pad.ubuntu.com/QAIncentive now destined for x.org
[17:11] <knome> destine ha ha
[17:11] <knome> +d too
[17:12] <elfy> :)
[17:12] <knome> hahah
[17:13] <knome> gnome minesweeper just crashed
[17:13] <elfy> are the Swedish navy looking for it?
[17:13] <knome> who knows
[17:14] <elfy> bbl
[17:15] <knome> hf
[17:24] <brainwash> ochosi: please read http://forum.ubuntuusers.de/topic/allgemeine-frage-zu-bugs-in-14-04-lts/
[17:25] <brainwash> I will add a reply later if you don't plan to do so :)
[17:30] <ochosi> brainwash: yeah, feel free to add a reply (as long as it's an explanation and not a rant ;))
[17:50] <elfy> I see people other than team adding to hardware page - that's more useful
[17:50] <elfy> especially akxwi-dave - not sure who he is - but he does a huge amount of testing for us
[18:01] <bluesabre> I'm back
[18:03] <Unit193> Yey!
[18:04] <bluesabre> :D
[18:23] <skellat> bluesabre, brainwash: I think I need help understanding what the reporter is trying to say in LP Bug 1385863 as it is not clear at all
[18:26] <knome> skellat, he's saying that top says that his computer is on a huge load, but nothing seems to be the culprit
[18:27] <knome> so it'd be good to know if his system feels like it's under a huge load or not
[18:28] <knome> if it's not, then it might be either 1) a bug in top or 2) something that's explainable, but isn't imminently clear/logical
[18:29]  * skellat does not like bug reports with huge copy pasta dumps in the middle of them
[18:31] <skellat> Alrighty, probing questions left
[18:31] <skellat> Thank you knome
[18:31] <knome> me neither, the data dump would be much better in an attachment
[18:31] <knome> maybe you could edit the description to delete that
[18:32] <knome> and ask to readd it as an attachment (or simply do that yourself)
[18:32] <knome> and np
[18:55]  * bluesabre feels like there should be a xubuntu-u-development, but that draws a lot of parallels with new-features
[18:56] <ochosi> yeah, i somewhat agree
[18:56] <ochosi> we could also s/features/development/
[18:56] <ochosi> after all, we're using features like de
[18:56] <ochosi> v
[18:57] <bluesabre> yeah, I think that would be the way to go
[19:01] <ochosi> maybe for x though, cause i've already sent an email for blueprint approval to u-release ml
[19:01] <ochosi> i mean i can send another, amending email
[19:01] <ochosi> but i dunno if it's worth it, just for the title of the blueprint
[19:01] <bluesabre> either way, will probably flood -features with more than just new-features
[19:03] <bluesabre> or, can link the pad
[19:03] <bluesabre> let me know what would be preferred
[19:03] <bluesabre> or wiki page, etc
[19:05] <knome> blueprint is a great place
[19:05] <knome> so much easier to track
[19:35] <ochosi> bluesabre: yeah, put everything in the blueprint, sucks having to look in >1 place (especially with the wiki etc being so slow)
[19:35] <knome> and especially since anything else than the blueprints aren't designed to track progress :)
[19:36] <bluesabre> ochosi, knome: updated xubuntu-default-settings and xubuntu-artwork branches. new vivid branches, set as development target
[19:36] <bluesabre> knome: can't do the same for xubuntu-docs, but I think you can :)
[19:37] <knome> right
[19:37] <knome> i'll consider doing that at some point
[19:37] <knome> ;)
[19:37] <bluesabre> what other paperwork/processes do we need to do for vivid that we'll kick ourselves in 5 months for not doing yet? :)
[19:38] <knome> did you check the processes page?
[19:38]  * bluesabre should do that
[19:38] <knome> ^ my new favorite phrase
[19:39] <elfy> can we all use it?
[19:39] <elfy> I assume you mean "bluesabre should do that"
[19:39] <knome> yes you can
[19:39] <knome> i meant my previous comment
[19:39] <knome> did you check the processes page?
[19:39] <elfy> :)
[19:39] <knome> /dyctpp
[19:40] <knome> (not really)
[19:41] <bluesabre> ok read that
[19:41] <bluesabre> isn't there something release-specific we need to do for tracking that we did really late in utopic?
[19:42] <knome> bluesabre, anything that you missed? anything that was missing?
[19:42] <knome> bluesabre, i don't understand your comment.
[19:42] <bluesabre> the burndown chart or sth
[19:43] <elfy> bluesabre: afaik that comes from the blueprints being dealt with by release team
[19:43] <bluesabre> ah, ok
[19:43] <elfy> none of our blueprints last cycle were done
[19:43] <knome> bluesabre, https://wiki.ubuntu.com/Xubuntu/Processes#Testing
[19:43] <knome> oh right.
[19:44] <knome> yeah, there's no charts for utopic.
[19:45] <bluesabre> yeah, this thing http://status.ubuntu.com/ubuntu-t/group/topic-t-flavor-xubuntu.html
[19:45] <knome> yep, wasn't set up
[19:47]  * elfy keeps thinking he's missed something
[20:07] <brainwash> skellat: I like the last comment in bug 1292290
[20:07] <brainwash> he assigned the bug to himself, but does not know what to do :)
[20:08] <brainwash> also bug 1270894
[20:09] <brainwash> it's assigned to a random guy, but no progress so far
[20:11] <bluesabre> ochosi, knome: blueprint look good (as demoed on top)? http://pad.ubuntu.com/xubuntu-v-dev
[20:12] <knome> bluesabre, is the gnome components note misaligned?
[20:12] <knome> without checking the content too closely, looks good to me
[20:12] <bluesabre> knome: no
[20:12] <bluesabre> ;)
[20:12] <knome> to me, the work items is ultimately the most important bit
[20:13] <elfy> has anyone seen lderan lately?
[20:13] <knome> so if you can squeeze out more work items from the whiteboard, even generic ones like "discuss X", or "investigate X", or "do X", those would be a welcome addition
[20:13] <bluesabre> ok
[20:13] <knome> they are easy enought to turn into actionabe items later
[20:13] <knome> and with as much work items laid out as possible, it's easier to grasp what the total work items amount would be at max
[20:14] <knome> (and the baseline is more useful if we have most work items listed when the baseline is reset
[20:14] <knome> )
[20:32] <bluesabre> ok, put the squeeze on, created more items
[20:35] <bluesabre> going to add these to the blueprint now, I'm pretty happy with what we've come up with
[20:35] <knome> :)
[20:36] <bluesabre> blueprint now updated, https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-v-features
[20:37] <knome> yep
[20:41] <elfy> mmm - I remember now
[20:41] <elfy> milestones - we need to decide before I start scheduling testing if we're going to do as last cycle and ignore alphas
[20:43] <elfy> ochosi bluesabre Unit193 slickymaster knome skellat jjfrv8 Noskcaj pleia2 ^^
[20:44] <bluesabre> I'd be interesting in knowing when the things above us (gtk, systemd) will land
[20:44] <elfy> good point
[20:44] <skellat> elfy: It depends upon when systemd lands.  If it is post-alpha, then I'd say just ignore them as what we would be testing would have little relationship to released product.
[20:46] <elfy> I think I'll just assume that we are - then if we're not we'll have a couple of freeish weeks mid cycle
[20:47] <skellat> infinity thought mid-cycle
[20:47] <Noskcaj> bluesabre, gtk will probably be in the next few weeks, we need to finish gi fisrt AFAIK
[20:47] <Noskcaj> *first
[20:47] <elfy> skellat: yea - which is mid alpha (ish)
[20:48] <skellat> Oh, I forgot to ask.  Do we need to think about Mir?  Is mainline going to try to land that in 15.04?
[20:49] <elfy> other than currently knowing "15.10: Potentially Unity 8 default / Unity 7 as an option"
[20:49] <elfy> I've not seen much talk of it
[20:49] <Noskcaj> upower should be just after gtk is done, bluez5 after that
[20:50] <bluesabre> Noskcaj: good to know
[20:50] <bluesabre> thanks :)
[20:50] <skellat> What other Gnomish bits are planned to be raining down on us?
[20:51] <Unit193> Likely latest.
[20:52] <skellat> Do we know what side effects we'll get out of that?
[20:52] <Noskcaj> skellat, 3.14 didn't bring many big changes with it, just catch-up transions and debian switching gi to multiarch
[20:52] <Unit193> Sure, maybe not much for Gnome, but Xfce.
[20:53] <skellat> But in Ubuntu-side archive we're looking at a jump from 3.8 to 3.14 effectively after the late landing for 3.12
[20:53] <Noskcaj> We're hoping to try for 3.16 if all the transitons are done fairly early
[20:53] <skellat> GNOME might not have had big changes within its frame of reference but I'm more worried about our frame of reference
[20:53] <Noskcaj> For us, it's mostly just making sure headerbar stuff is patched
[20:54] <bluesabre> yeah, xfce works well with headerbars (better than unity actually)
[20:54] <Unit193> Bleh, headerbars.
[20:54]  * Unit193 votes to drop any application that adds them. :P
[20:55] <skellat> And please remember Noskcaj, Debian is hitting their freeze soon at 23:59 UTC on the 5th of November 2014 for Jessie
[20:55] <Noskcaj> skellat, yep
[20:56] <Noskcaj> gnome side that actually helps us since debian have sorted all of 3.14 out
[20:56] <bluesabre> yeah, we're in a good position thanks to the heavy debian work
[20:56] <Unit193> "Copy shimmer-themes package from daily ppa to xubuntu-staging for milestone testing"  Is that the badly versioned one?
[20:56] <bluesabre> true...
[20:56] <bluesabre> "Build git versions for xubuntu-staging for milestone testing" is probably better
[20:57] <Unit193> bluesabre: Nuke the PPA, re-create it, then change the version format for the daily builds?
[20:58]  * skellat walks away to go to a 14.04 machine to test a backport so he can file the request bug to go from V -> U and V -> T based on the sync from Sid
[20:59] <Unit193> bluesabre: Ah, thought lls was going to be added/created in ll source.  There's a WNPP already if you need me to grab the number.
[21:00] <Unit193> (Also, think policykit stuff would technically be an "upstream" problem, thus not on Xubuntu stuff?  Anywho. :P )
[21:00] <bluesabre> it is, but since I develop it, meh
[21:00] <bluesabre> :)
[21:01] <bluesabre> Unit193: # please
[21:01] <bluesabre> cavalier seemed opposed to the idea of including lls in ll
[21:02] <bluesabre> or, do you mean lggs?
[21:02] <Unit193> debian 745509
[21:02] <bluesabre> thanks
[21:03] <elfy> ochosi bluesabre: at some point before I do testing plan can you cast an eye over this - make sure all's what you think we need to test still please :) http://pad.ubuntu.com/vivid-testcases
[21:03] <bluesabre> currently experimenting with default qt configs
[21:04] <bluesabre> elfy: groups A-D are tested in that order? A earliest in cycle, D latest?
[21:06] <elfy> bluesabre: well ... unbeknownst to me - you can't order package testing in any order - so it does it in the order they appear on the tracker admins - hence they all show ashttp://packages.qa.ubuntu.com/qatracker/milestones/316/builds/67147/testcases
[21:06] <elfy> however - there is nothing to stop me swapping tests within each suite about as we need
[21:07] <bluesabre> I mean, as far as the calls to testing, do we request some at a specific time?
[21:07] <bluesabre> I was thinking we did A early on
[21:08] <elfy> shouldn't  "change pinkish highlights to turquoiseish ones" be on the artwork blueprint :)
[21:08] <elfy> bluesabre: well - I can call for things whenever we want them - but experience tells me that people just go from the top of the list :)
[21:09] <elfy> bluesabre: you tell me what you want tested first and I'll do that :)
[21:09] <bluesabre> ok, np then.  we usually squeeze in the things we're developing right before FF (because we're awful)
[21:10] <elfy> lol
[21:10] <Unit193> Seems everyone likes to do that, or after.
[21:10]  * ochosi read backlog
[21:10] <elfy> bluesabre: as I said earlier - we could call for parole to be tested next week - if we need to retest it in March we can call again - that's not a problem
[21:11] <bluesabre> ok cool
[21:11] <elfy> I guess the important thing right now is if something obvious is missing from there
[21:11] <bluesabre> it looks good to me
[21:11] <elfy> or needs to move out of the top 2 - as they are optionals currently
[21:12] <bluesabre> I think it is fine as is
[21:13] <elfy> cool - that makes it easy then - just remove xchat and we're good to go with those
[21:33] <Pwnna> is the thunar bug getting fixed anytime soon?
[21:33] <Pwnna> thunar default open
[21:33] <Pwnna> also i'm getting black screen for light locker again. How to debug this?
[21:33] <Pwnna> fresh install, this time
[21:34] <elfy> night all - cya when I cya
[22:27] <ochosi> bluesabre: you're pushing that right into x-d-s, right?
[22:28] <bluesabre> yeah, the plan is to push it, and anything else we want for our initial vivid release
[22:29] <bluesabre> it will go into daily, and then let that simmer for a few days before upload to archive
[22:37] <ochosi> i guess for 14.10 we can't really fix that for existing users anyway...
[22:37] <ochosi> could try to SRU it, since it's one of the known ones
[22:37] <bluesabre> yeah, not much that can be done.  Doesn't get copied or read for xdg-xubuntu, skel only applies to new users (I think)
[22:44] <knome> bluesabre, so, when are you pushing the pink-reverting stuff? :)
[22:44] <bluesabre> can push that now too, unless we want to cling to the pink for a while
[22:45] <knome> nah, for vivid, it should just be gone
[23:07] <bluesabre> Unit193: poke
[23:08] <bluesabre> does "bzr-builder format 0.3 deb-version {debupstream}+bzr~{revno}" seem reasonable for ubuntu-native bzr packages?
[23:11] <bluesabre> in this case, xubuntu-default-settings_15.04.0+bzr~534.dsc
[23:13] <ochosi> we could also just replace the pink with turquoise straight away
[23:13] <ochosi> knome: ^
[23:13] <ochosi> or do you wanna keep it a "suprise"?
[23:13] <bluesabre> either way, we can't undo gtk3 colors since they are a skel item
[23:14] <bluesabre> so, pink utopic upgraders keep pink gtk3
[23:14] <knome> bluesabre, Unit193 talked about some script to revert that if i understood correctly
[23:15] <knome> ochosi, i would say we should probably just revert to default now
[23:26] <ochosi> yeah, bringing it back is easy anyway
[23:27] <knome> yep
[23:42] <Unit193> bluesabre: Hello.  No tilde, though.  Well, upgraders don't really get it if they don't create a new user, and maintscript to remove the file.
[23:46] <bluesabre> so, a new user made in 14.10, with /etc/skel/.config/gtk-3.0/gtk-3.0.css copied to their profile, we can remove the file in their profile?
[23:48] <Unit193> No, but from .skel.
[23:48] <Unit193> gtk-theme-config, same as always.
[23:49] <bluesabre> ok
[23:49] <bluesabre> knome: poke
[23:49] <Unit193> Yes, yes.  Poke knome!
[23:49] <Unit193> Pokepokepoke.
[23:49] <bluesabre> and/or ochosi
[23:50] <bluesabre> xubuntu-* packages, which series should get daily builds? trusty/utopic/vivid ?
[23:50] <Unit193> If it's from the vivid repo, it's for vivid?
[23:50] <skellat> Why would we need to keep re-building utopic?
[23:50] <knome> what
[23:51] <bluesabre> for folks testing
[23:51] <bluesabre> vivid-only in this case?
[23:54] <bluesabre> yeah, guess that makes sense
[23:54] <bluesabre> nvm
[23:57] <bluesabre> Unit193: so, about the maintscripts
[23:57] <bluesabre> guessing, prerm to remove that file
[23:58] <Unit193> xubuntu-default-settings.maintscript
[23:59] <bluesabre> aha
[23:59] <Unit193> Silly bluesabre.
[23:59] <bluesabre> thats easy enough then
[23:59]  * Unit193 hopes he wasn't going to just have a rm -f. :3