[20:56] <yotux> is anyone around this afternoon?
[20:58] <tsimonq2> hello yotux :)
[20:58] <tsimonq2> yotux: how are you?
[20:59] <yotux> tsimonq2: I am good was reading some of the mailing list items
[21:00] <yotux> was not sure if this was active cahnnel or just people hanging around
[21:02] <yotux> tsimonq2:thank you for the wiki page think it will help
[21:05] <tsimonq2> :)
[21:05] <tsimonq2> yotux: so what are your thoughts?
[21:06] <yotux> tsimonq2:Seems I have been removed from the group on launchpad
[21:06] <yotux> tsimonq2:I think the socail aspect needs to be built and from there the sub-locals can group
[21:07] <tsimonq2> what do you mean by that?
[21:07] <yotux> IE: Madison area users get together form a relationship and then transform into a working group
[21:07] <tsimonq2> I see
[21:07] <yotux> or one could say start with a working group so there is a better foundation
[21:08] <tsimonq2> where are you again?
[21:08] <tsimonq2> just curious
[21:08] <yotux> Portage, so lets say Madison
[21:09] <yotux> I was going to Chicago for a Loco a few years ago and then life changed and the group changed
[21:09] <tsimonq2> so you said you are no longer a part of the Launchpad team?
[21:09] <tsimonq2> I see
[21:09] <yotux> Looking at my launchpad account no
[21:09] <tsimonq2> I'll add you
[21:09] <tsimonq2> (if you don't mind)
[21:09] <yotux> unless I am in the wrong place
[21:09] <tsimonq2> https://launchpad.net/~ubuntu-us-wisconsin
[21:09] <tsimonq2> added :)
[21:10] <yotux> you can add me I have talked with my wife and asked if I could try and get ubuntu users together
[21:10] <tsimonq2> awesome :)
[21:10] <tsimonq2> I think it would be a really good idea to have a meetup in Madison
[21:10] <tsimonq2> like a release party
[21:11] <yotux> I agree socail but also advocate for Ubutnu
[21:12] <yotux> my lauchpad page seems intereseted states I joined Wi loco 2007-06-12 but it was not there before your edit
[21:12] <tsimonq2> well imho although advocation is good, we need a team to do that ;)
[21:12] <tsimonq2> I see
[21:12] <yotux> I agree
[21:13] <tsimonq2> well I'm 14 so I'd have to ask my dad, but I think an Ubuntu Hour in the Green Bay area would be good
[21:13] <tsimonq2> Mike Putnam is actually in the Fox Valley
[21:13] <tsimonq2> but most of the users that responded are from Madison
[21:13] <yotux> I am 34 a school bus driver at the moment
[21:13] <tsimonq2> I see :)
[21:14] <tsimonq2> where do you use Linux? just at home or elsewhere?
[21:14] <yotux> Thank you for being a strong adovate at your age its inspiring
[21:14] <tsimonq2> thank you :)
[21:14] <yotux> I have a home server, desktop, and also a VPN at a remote server farm
[21:14] <tsimonq2> I see
[21:15] <yotux> laptop also but thats home user
[21:15] <tsimonq2> yeah my computer runs Lubuntu and at school we have Chromebooks
[21:15] <tsimonq2> so I frequently use Linux
[21:15] <yotux> how does one add thier name to the wiki page
[21:15] <tsimonq2> are you logged in to the wiki?
[21:16] <yotux> Sady most of the schools have adopted Google Edu and that has lead to chromebooks being the norm
[21:16] <tsimonq2> yeah our school has
[21:16] <yotux> I like FOSS and Google to me is not really FOSS
[21:16] <tsimonq2> I agree
[21:17] <tsimonq2> I installed Ubuntu on my old system in February of 2015, then moved to Lubuntu and started contributing to the project in July 2015
[21:17] <tsimonq2> I got my Ubuntu Membership on February 4, 2016
[21:18] <tsimonq2> so I love this community
[21:18] <yotux> I started with Ubutnu in 2005 and moved to Kubuntu 2 years ago
[21:18] <tsimonq2> ohh I see
[21:18] <tsimonq2> the people who run Kubuntu are really nice and KDE is my choice for a full-blown DE
[21:18] <tsimonq2> I am using LXQt right now
[21:18] <yotux> not impressed with 16.04 seems a little rushed and maybe broken
[21:19] <tsimonq2> I don't use Unity so I can't vouch for that ;)
[21:20] <tsimonq2> anyways
[21:20] <yotux> Myself I have a hardtime with the graphics around Unity I understand why it is here but prefer alt options
[21:20] <tsimonq2> yeah
[21:20] <tsimonq2> so in a bit I'll go to the ML asking about 16.10's release party
[21:21] <yotux> sound like a good idea
[21:21] <tsimonq2> AFAIR it's gonna be a better release than 16.04, we have big plans ;)
[21:21] <yotux> thats the hard part 16.04 is an LTS, so it should be better than 16.10 imho
[21:22] <tsimonq2> well the LTS is for stability
[21:22] <tsimonq2> which we obviously didn't have in this release XD
[21:22] <yotux> I agree
[21:23] <yotux> Kubuntu is going through a culture change so I will be give them extra slack
[21:23] <tsimonq2> I see :)
[21:24] <yotux>  tsimonq2: are yout the only one added people to the location wiki
[21:24] <yotux> sorry can't type today
[21:24] <tsimonq2> nope, Ian and Alex have added themselves
[21:25] <tsimonq2> are you logged into the wiki?
[21:25] <yotux> I think that I am
[21:26] <tsimonq2> can you edit it?
[21:26] <tsimonq2> unless you just want to give me the details and I can just plug it in
[21:27] <yotux> found a link, so how does know if there are an ubuntu member
[21:28] <yotux> reading the membership I would say no, I have not went to the council
[21:29] <tsimonq2> let me look at your LP page
[21:29] <tsimonq2> nope, you are not
[21:30] <tsimonq2> yay it looks good :)
[21:31] <yotux> Thanks I have limited knowledge, I use google to help learn new skills
[21:31] <tsimonq2> heh I think that's everyone ;)
[21:37] <tsimonq2> yotux: awesome, thanks for chatting :)
[21:39] <yotux> tsimonq2:Thank you for your input seems like we have a nice start
[21:40] <tsimonq2> yes :)
[21:42] <yotux> Sorry ran into a road block on a LVM project


[02:39] <ahoneybun> hey all how do you use flickable with columns?
[08:00] <meles> mhall119: you are the maintainer of ubuntu-calendar-app. right?
[08:05] <DanChapman> meles, IIRC kunal and mihir are the main developers working on calendar.
[09:42] <nik90> meles: ping
[11:21] <awad> hi
[13:02] <meles> hey nik90 i just saw it now
[13:03] <meles> nik90 any progress?
[13:23] <meles> nik90 GOT IT!
[13:24] <nik90> meles: can you test the click package on your phone and see if it fixes the bug
[13:26] <meles> my patch: http://paste.ubuntu.com/11714089
[13:26] <meles> nik90 ^ where is the click package
[13:27] <nik90> meles: I added a comment in the bug report with the click package
[13:28] <meles> nik90: ok
[13:37] <meles> nik90 the app fails to open
[13:40] <nik90> meles: eh?
[13:40] <nik90> meles: which device image are you running?
[13:40] <nik90> meles: I built it against a vivid 15.04 image. Are you running BQ with 14.10 instead?
[13:41] <meles> nik90 splash screen is appearing and than it crashes. I'm running 14.10 indeed
[13:42] <nik90> meles: that's why it doesn't open for you..its compiled to work on 15.04 and not 14.10 considering that OTA-4 will be released tomorrow which is based on vivid :)
[13:42] <meles> nik90 i m building it myself
[13:42] <nik90> meles: rest assured, let me build it for 14.10 and send you the click package if you want
[13:42] <nik90> meles: ok..ping me if you hit any issues and I can send it to you if required
[13:52] <meles> nik90 ping
[13:52] <nik90> meles: i'm here
[13:54] <meles> nik90 no the fix does not work. but I have to say that I have a special issue. Since I changed the date so many times for testing purposes I had some alarms created at a future date. Reactivating this alarms makes them just go off at the day they were originally created. My fix considers this problem. Can you test it? I can push it if you want.
[13:55] <nik90> meles: would the phone issue change their date and go backwards though?
[13:55] <nik90> meles: can you upload your fix into a branch that I can grab and test quickly?
[13:56] <meles> nik90 no normally not but who knows :-)
[13:56] <meles> ok otw
[13:56] <nik90> meles: fair enough
[14:03] <meles> nik90 ok it's up
[14:04] <meles> nik90 lp:~themeles/ubuntu-clock-app/bugfix-1442518
[14:06]  * nik90 tests now
[14:11] <nik90> meles: yup your patch works better
[14:11] <nik90> nice work!
[14:12] <meles> :-)
[14:13] <nik90> meles: just requires 2 minor code fixes, 1) Better variable names 2) add an entry to the debian changelog
[14:13] <meles> nik90 just might have to rename the variables a bit, since they are pretty bad
[14:13] <nik90> :)
[14:14] <nik90> meles: if you look at https://code.launchpad.net/~nik90/ubuntu-clock-app/fixes-1442518/+merge/261905, you will see the debian changelog entry I used
[14:14] <nik90> ofcourse add your own name to the entry
[14:14] <meles> nik90 ok i fix it
[14:20] <nik90> meles: Why do you do var tdate2 = new Date(d.getFullYear(),d.getMonth(),d.getDate()+1,alarmData.date.getHours(),alarmData.date.getMinutes(),0,0) instead of d.setDay(d.getDate()+1) ?
[14:20] <nik90> is it to set the minutes and seconds to 0?
[14:21] <meles> now because i coud not get the other variant working
[14:22] <meles> nik90 no because i coud not get the other variant working
[14:25] <nik90> other variant?
[14:25] <meles> nik90 the one u suggested
[14:26] <nik90> ah ok
[14:30] <meles> nik90 i pushed the new code and entered the information suggested. Is there anything more neccessary
[14:31] <nik90> meles: sec, taking a look
[14:32] <nik90> meles: two things...update debian changelog and also specify a commit msg to the merge proposal you created
[14:35] <meles> where do i change the debian changelog
[14:35] <nik90> meles: nano debian/changelog
[14:40] <nik90> meles: one other thing..the two variables "currentTime" and "now" are redundant..you just need one of them
[14:41] <meles> nik90: you are right. I stick with now, I think its easier, even though the other was used before. ok?
[14:42] <nik90> meles: fine by me
[14:44] <meles> nik90: ok i think now its complete
[14:45]  * nik90 checks
[14:50] <nik90> meles: commented in the MP proposal.
[14:51] <meles> nik90 MP?
[14:51] <meles> I have to go now urgently, i ll be back later
[14:51] <nik90> meles: ok..you should have got an email about the merge proposal
[14:51] <nik90> meles: tty later
[17:19] <meles> hey nik90, thanks for your comments. I changed it as you suggested. I hope it's good to merge now. If not let me know.
[17:21] <nik90> meles: they look good now. I am going to test this for a 2-3 days to ensure that we didn't miss out any rare cases where the bug might reappear. I would recommend you do the same.
[17:22] <nik90> meles: and then I will merge it and try to include it in our release after OTA-4
[17:22] <nik90> popey, balloons: Could either of you trigger jenkins on https://code.launchpad.net/~themeles/ubuntu-clock-app/bugfix-1442518/+merge/261910 pls. thnx
[17:23] <nik90> meles: I approved the merge proposal. Will merge in a few days after I finish testing it.
[17:25] <meles> nik90 allright I will. I'm very glad that I had your great support!!! Maybe I can contribute to some other bugfixes now, which might make the planed selling of my phone obsolete. :-)
[17:26] <nik90> meles: you made the bug fix possible..so a huge thanks to you! And yes feel free to contribute to other bug fixes that grab your attention.
[17:28] <nik90> meles: be sure to assign the bug to yourself on launchpad before starting to work on it since otherwise we might have multiple people working on the same thing.
[17:32] <meles> nik90 actually there is even one that annoyed me quite a bit at the beginning. It's Bug #1437316. And I would agree to racb's comment, to make the off button red and the snooze green.
[17:32]  * nik90 looks at the bug report
[17:33] <nik90> meles: that bug report is a bit off scope at the moment since it is not the clock app that draws the notification on the screen. Indicator-datetime does at while using the unity8 notification framework.
[17:34] <nik90> meles: also it requires feedback from the design team before proceeding to fix it.
[17:34] <nik90> I do agree to the bug report as stated in the first comment there
[17:35] <nik90> meles: the bugs which are listed in https://launchpad.net/ubuntu-clock-app/+milestone/3.x.backlog are usually blocked atm by things like design, platform limitation etc.
[17:38] <meles> nik90 ok I understand. I will see what else I could do.
[17:55] <popey> nik90: I am not sure I know how to manually trigger, so gave it a go. lets see if it works
[17:55] <popey> nik90: http://<IP_ADDRESS>:8080/job/ubuntu-clock-app-ci/
[18:00] <nik90> popey: ack.
[18:00] <meles> nik90 my alarms don't trigger any sound or vibration anymore, they just pop up. Does it work on your system
[18:00] <popey> thanks for the contribution meles !
[18:02] <nik90> meles: for me it triggers sound and vibration even after installing your patch. I tested this on my Nexus 4 running 15.04
[18:02] <meles> popey: no prob. I'm happy that I could contribute and that I got great support!
[18:04] <nik90> meles: good news is that jenkins ran the autopilot and qml tests and found no regressions in your patch! It will be merged in 2 days after we both are confident of the bug fix.
[18:05] <popey> woah! My random button pressing worked!?
[18:05] <popey> sweet
[18:05] <nik90> haha ;)
[18:30] <meles> nik90 is there somewhere a proper how to about how to fix and commit a bug, if not I would work on an easy to read summary
[18:31] <nik90> meles: https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
[18:32] <meles> and about Ubuntu SDK, like how to open the project (CMakeList.txt).
[18:32] <meles> nik90 ^
[18:33] <nik90> meles: well stuff like how to run an app, build it for the phone etc are all documented at developer.ubuntu.com
[18:33] <nik90> meles: it is common knowledge that cmake projects are opened via the CMakeList.txt file, qmake via .pro etc
[18:35] <meles> nik90 not to everybody and without your help i might have just given up.
[18:36] <nik90> meles: We could make the core apps contribution guide a bit more descriptive by include such info and for further info redirect the to the official documentation pages?
[18:45] <meles> nik90: yes would limit the step to join. And I also think that there is to much text, when I want to check something out I want to get quickly through it. E.g http://paste.ubuntu.com/11715854/
[18:48] <nik90> meles: well yes some pictures would come in handy to explain it in a more intuitive manner
[19:00] <popey> I have an item on my to-do to improve the on-ramp for new developers nik90 meles
[19:03] <nik90> popey: did you have any particular idea/mockup on how to improve it?
[19:03] <popey> the idea was to have a pretty home page for each app
[19:03] <popey> and a general page for all the cross-app info
[19:03] <popey> and move the content off the wiki
[19:04] <popey> no mock ups yet
[19:05] <nik90> off the wiki?
[19:05] <nik90> dedicated homepages/website for each app?
[19:05] <popey> yeah, move it to developer.ubuntu.com
[19:05] <popey> yes
[19:05] <popey> page per app
[19:06] <popey> with links to where the source is, bitsize bugs, planning docs etc
[19:06] <nik90> ah
[19:24] <meles> popey nik90 i was on the phone. I think developer.ubuntu.com would be the better place since this was also where I was looking for such info. but couldn't the quick start guide be quicker to read. All the info but less text.
[19:24] <popey> thanks for the feedback
[19:24] <popey> I agree
[19:28] <nik90> +1


[00:33] <ace_suares> hi all
[00:34] <ace_suares> I am runnign a dhcp serve ron another server fthen the ltsp-server
[00:34] <ace_suares> but the thi client gets an ip address but no tftp
[00:34] <ace_suares> i inculded next-server in dhcpd.conf
[00:34] <ace_suares> but it didn't work
[00:34] <ace_suares> any ideas
[03:52] <emmet> anyone here ever done apresentation to a public school about switching to edubuntu? any tips?
[03:54] <LaserJock> emmet: the edubuntu-users mailing list is a good place to ask that
[05:26] <ken> help: i am installing edubuntu on machine A, and am going to boot machine B directly from it with a cross cable. the point is i need machine A (server) to also have a usable edubuntu setup. how do i do this?
[05:27] <ken> someone?
[05:29] <LaserJock> ok, so you want to install Edubuntu on machine A
[05:29] <LaserJock> bah
[05:55] <nibl> need help with pxe client boot, anybody around?
[05:56] <nibl> client boots, shows splash then drops to busybox
[05:57] <nibl> it's a new 7.10 installation, any clues?
[06:07] <johnny> you get a splash screen on thin client? lol
[06:07] <johnny> i don't even get one of those
[06:37] <nibl> nobody around/awake?
[06:37] <johnny> you could try startx manually
[06:37] <johnny> and see what happens
[06:38] <nibl> i get initramfs, can you startx from there?
[06:38] <nibl> the splash onlz shows for 2 secs
[06:43] <nibl> are there any logs for what is wrong on the client?
[06:44] <johnny> perhaps
[06:44] <johnny> check them on the server
[06:44] <johnny> or, disable the splash screen is stuff happens before the logging starts
[06:44] <johnny> if*
[06:44] <johnny> uhmm.. i dont' quite recall the file name
[06:45] <johnny> perhaps in /var/lib/tftproot
[06:46] <nibl> ok, i'll check that.
[06:46] <nibl> i wonder if syslog could run.
[06:46] <johnny>  /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
[06:46] <johnny> that's it
[06:47] <nibl> thanks.
[06:47] <johnny> remove quiet
[06:47] <johnny> and splash
[06:47] <johnny> you can prolly comment out the old one
[06:47] <johnny> and have a new one without
[06:49] <nibl> what does 'quiet' mean?
 any ideas <- whats the existing dhcp server?
[10:04] <ws1> hi guys, im having problem in ldm
[10:04] <ws1> the server shows successful login but in client, it says verifying username and password
[10:04] <ws1> and then again ldm is displayed
[10:27] <ws1> guys i found the problem, it was sabayon
[11:32] <ws5> im getting different resolutions in different systems, weird
[14:43] <shishirjha> can anybody suggest me the best way to change the clients screen resolution
[16:16] <ace_suares> Kamping_Kaiser: you still there ?
[16:54] <johny> hi there
[16:54] <johny> can anyone help me with software development
[16:54] <johny> I need to develop some software and don't know where to begin with edubuntu
[16:55] <johny> If someone could please point me in the right direction on where to start I would greatly appreciate it
[17:01] <jbrefort> develop what kind of software?
[17:03] <jbrefort> johny, you should search if there is already a related project fisrt, no need to duplicate the efforts
[17:03] <johny> I want to develop a landscape design proggy with a gui
[17:04] <johny> I have experience in c++ and pascal in the past
[17:04] <johny> This is all with microsoft
[17:04] <johny> I'm trying to get away from microsoft and wish to learn more about linux
[17:04] <jbrefort> great :)
[17:05] <johny> I'm still learning about linux and have come quite aways but I can't find anything on even how to make the most simplest hello world
[17:05] <jbrefort> there are already many  projects, so may be one can do what you want and you do not need to start from scratch
[17:06] <jbrefort> well hello world is quite easy
[17:06] <jbrefort> I suppose you want the message in a popup window?
[17:06] <johny> first of all where would I go to even get to a development environment
[17:07] <johny> yes a poppup window will work for now
[17:07] <johny> do i just use a word processor
[17:07] <johny> and where would I find the compiler
[17:07] <jbrefort> there are several, I'm using anjuta because I'm using gtk+
[17:07] <jbrefort> the compiler is gcc
[17:07] <johny> gtk+ is good
[17:07] <jbrefort> (it does not support pascal)
[17:08] <johny> no but it does support c and c++
[17:08] <jbrefort> yes, and some others
[17:09] <jbrefort> you need to install gcc and g++ (I don't remember the package names)
[17:09] <jbrefort> g++ is the c++ compiler
[17:09] <johny> yes dev c++ uses it and that is what I was using in windows
[17:09] <jbrefort> ok
[17:10] <johny> but I don't like microsoft that's why I went to ubuntu
[17:10] <jbrefort> if you use anjuta, it will help you to create a new project
[17:10]  * jbrefort don't use ubuntu
[17:11] <jbrefort> but no microsoft things around :)
[17:11] <johny> anjuta is it a package I can install
[17:11] <jbrefort> yes
[17:11] <johny> I like the philosophy of the linux community
[17:11] <jbrefort> you are welcome :)
[17:12] <johny> and am all for supporting open source software
[17:12] <johny> thank you for the info
[17:12] <johny> I'll check out anjuta
[17:12] <johny> just what I needed is a pointer to a development environment I can use to get started
[17:22] <mcfloppy_> which thin client is a good choice?
[17:22] <mcfloppy_> the n2200 netvista are to slow :(
[17:22] <mcfloppy_> but i dont want to buy a very expensive hardware
[17:42] <juliux> mcfloppy_, transtec has some nice thinclients
[20:40] <Flare183> Flare183 is at Walmart
[20:42] <das-t> have fun ;-)


[10:47] <ach1m> Hi, I am trying to write an upstart job that "start on started appname". I am on raring and I think I have configured everything correct. I am able to run the job manually.
[10:48] <ach1m> Would be nice if someone could give me a hint on how to debug this.


[02:22] <rizonz> is it true that 14.04 doésn't honer apt-update scheduling and 16.04 does ?
[03:57] <greyolla> Does the kernel in xenial support any 25gbe nics out of the box?
[09:17] <lordievader> Good morning.


[05:51] <ZachK_> hello newsies
[06:23] <ZachK_> hey scott_ev
[06:38] <ZachK_> hey azteech
[06:39] <azteech> evening ZachK_ ..
[06:40] <ZachK_> and what brings ya here this rainy evening
[06:40] <ZachK_> at least it's raining for me
[06:40]  * ZachK_ dislikes rain
[06:40] <azteech> just getting in from a night of bowling ... and warm here ...
[06:41] <azteech> send all the rain this way if you want ...
[06:41] <azteech> we could use it ...
[06:41]  * ZachK_ sends the rain
[06:41] <azteech> and I normally am in this channel ... when I am online ... along with a few others ...
[06:42] <ZachK_> cool
[06:42]  * ZachK_ is everywhere
[06:42] <ZachK_> what channels do ya hang out in?
[06:44] <azteech> our loco - ubuntu-us-az ... ubuntu desktop amd64 server, debian, freenas, conky, and samba ...
[06:46] <azteech> what about you?
[06:48] <ZachK_> #ubuntu, #ubuntu-beginners, #ubuntu-beginners-team, #ubuntu-beginners-wiki, #ubuntu-classroom, #ubuntu-classroom-chat, #ubuntu-doc, #ubuntuforums-unanswered, #ubuntu-learning, this one and #udsf
[06:49] <azteech> that's kewl ... I hit those usually once in a while ...
[06:50] <azteech> you one of the motu??
[06:50] <azteech> or part of the beginner team?
[06:52] <ZachK_> i'm a bt mentor and the bt's wiki lead
[06:55] <azteech> ah, nice ... pleased to meet you ...
[06:56] <ZachK_> likewise
[06:57] <azteech> where to you hail from?
[06:58] <ZachK_> US
[06:58] <ZachK_> Illinois
[06:59] <azteech> Ah, land of the gentle rolling hills ... Arizona here ...
[07:01] <scott_ev> where in ILL?
[07:01] <scott_ev> know where Charleston is?
[07:01] <ZachK_> Just outa Chicago
[07:01] <scott_ev> kk
[07:01] <ZachK_> but I know Arizona
[07:02] <scott_ev> dad was raised in downer's grove
[07:02] <ZachK_> I've been all the way down to L.A. and the opposite direction to Virginia and up to Minnesotta
[07:02] <scott_ev> charleston is ~60 miles south of champaigne
[07:02] <ZachK_> yup
[07:02] <scott_ev> southern ill university is there
[07:02] <ZachK_> i've traveled over 30,000 miles in my time
[07:03] <scott_ev> cool
[07:03] <ZachK_> so by that guess my age
[07:05] <azteech> based on miles only, and if only US land travel, would have to say mid to late 30's ...
[07:05] <ZachK_> 19
[07:11] <azteech> okay, so I'm way off ... lol
[07:12] <scott_ev> ok, how about moi?
[07:12] <scott_ev> I've lived all over the world and all over the country
[07:13] <scott_ev> I've logged over 500K easy
[07:13] <scott_ev> just drivingff
[07:13] <ZachK_> 20
[07:13] <scott_ev> driving not to mention flying
[07:13] <ZachK_> 25 maybe
[07:13] <scott_ev> awesom e
[07:13] <scott_ev> 48
[07:13] <scott_ev> haha
[07:13] <ZachK_> lol
[07:13] <scott_ev> and motherfuckin retired
[07:13] <ZachK_> military?
[07:13] <scott_ev> dad was
[07:14] <scott_ev> pardon the language
[07:14] <scott_ev> sometimes I forget that this is Ubuntu
[07:14] <ZachK_> eh
[07:15] <scott_ev> well, Ubuntu seems to want to have this squeeky clean disneyland kind of vibe
[07:16] <ZachK_> you'd be surprised
[07:16] <scott_ev> I kind of get, or used to, called on my language in our LoCo channel
[07:16] <scott_ev> family friendly and such
[07:17] <scott_ev> but he's gone now
[07:17] <ZachK_> who's gone
[07:18] <scott_ev> oh, a former team member that used to chastize me about saying things like dammit
[07:18] <scott_ev> or shit in the channel
[07:18] <scott_ev> hell, he even used to threaten to kick me
[07:18] <azteech> have logged almost 450K miles air and land ... and like scott, retired ...
[07:18] <scott_ev> nice
[07:19] <scott_ev> azteech: I didn't realize you were retired too
[07:19] <scott_ev> ain't it grand?
[07:19] <azteech> yep, it is ... 22 1/2 years military ...
[07:20] <scott_ev> cool...brb...smoke break
[07:20] <azteech> kk
[07:24] <scott_ev> I tend to only smoke 1/2 a cig at a time
[07:25] <scott_ev> azteech: air force?
[07:25] <azteech> army ... retired as 1st Sgt (E8) ..
[07:29] <scott_ev> cool
[07:29] <scott_ev> I had a short lived career but I would have been e5 under 2 years if I hadn't screwed up
[07:30]  * ZachK_ is working on getting in the Army as a 68W
[07:30] <azteech> well, we all had issues in our earlier years ... probably would have made SgtM if I hadn't made a couple ... myself ..
[07:31] <scott_ev> ayup
[07:31] <scott_ev> 68w?
[07:31] <scott_ev> excuse my ignorance
[07:31] <ZachK_> Combat Medic
[07:31] <scott_ev> ah
[07:31] <scott_ev> I was navy, went in as an e3
[07:31] <azteech> was a 32G/32D/29Y ... with additional skill identifiers for 29Y ....
[07:32] <scott_ev> guaranteed 2 schools
[07:32] <ZachK_> well i gotta go...wiki duties call
[07:32] <scott_ev> qualified for seal teams
[07:32] <scott_ev> nite
[07:32] <scott_ev> then I started getting into trouble
[07:33] <azteech> ZachK_: have a good evening bud .. nice to have met you ...
[07:35] <ZachK_> likewise
[07:39] <scott_ev> man, once again I didn't do my UWN stuff during the week
[07:39] <scott_ev> maybe I should try to do it now
[13:24] <scott_ev> akgraner: ping
[13:25] <cjohnston> Fixed S&U... I have to take off... Should be back early afternoon
[13:25] <ZachK_> WHAT UP!
[13:25] <ZachK_> wait..me
[13:27] <scott_ev> akgraner: I'll do the meetings today if you haven't given that job to someone else.  I have to do some yard work first  before it starts warming up.  I'll get it done in plenty of time.
[14:53] <akgraner> goo morning
[14:53] <akgraner> good even
[14:53] <akgraner> :-)
[14:56] <akgraner> Hey all had to stay off the computer for a couple days - my arm was in spasm  but should be good to go to get this news letter knocked out today :-)  woo hoo!
[15:25] <scott_ev> did you hurt yourself?
[15:26] <scott_ev> akgraner: so, am I doing meetings?
[15:27] <akgraner> scott_ev, just the pinched nerve acting up :-/
[15:27] <akgraner> scott_ev, if you can do the meetings that would be great
[15:28] <scott_ev> akgraner: excellent, I'm on it
[15:29] <akgraner> Thank you!
[15:29] <akgraner> scott_ev, you can add it to the wiki or the google doc - which ever is easier for you -
[15:29] <scott_ev> ok, great
[15:29] <akgraner> it will be a couple hours before I start adding to the wiki
[15:30] <scott_ev> excellent
[15:30] <scott_ev> then I'll prolly do everything in gedit and add it all at once when I'm ready
[15:44] <akgraner> that works for me:-)
[15:45] <akgraner> I am going to just do everything in the googledoc then once everyone else is out of the wiki - just add it that  - so we aren't getting edit conflicts this week :-)
[15:55] <nhandler> akgraner: Have a link to the google doc? I'll be adding team reports today
[15:55] <akgraner> nhandler, yep - but you can add to the wiki if that is easier for you?
[15:56] <akgraner> it's just gets crazy when we are all adding summaries and and stuff about the same time, so we end up stepping on each other :-)
[15:56] <nhandler> akgraner: I personally don't care where I add it. I can do it wherever you want
[15:57] <akgraner> nhandler, :-)  the wiki is fine - but here is the google doc just so you have it  - https://docs.google.com/Doc?docid=0AdKZelXU8Y2LZGNrcHRkYmhfODlkODNxNnRnZA&hl=en
[15:57] <nhandler> Thans
[16:01] <nhandler> akgraner: Any ideas about when you will publishing this UWN? I'm just trying to get an idea for how much time I should spend poking teams before I copy the report over
[16:03] <akgraner> nhandler, probable around 6 or 7pm eastern
[16:03] <akgraner> probably even :-)
[16:03] <nhandler> akgraner: Great. That gives me some time.
[16:03] <akgraner> nods
[16:04] <akgraner> I like it to be sooner but it won't be this week :-/
[16:08] <scott_ev> nhandler: if you need to go early and want me to finish up something for you, just let me know
[16:09] <nhandler> scott_ev: Thanks for the offer, but it only takes a few minutes to prepare the actual report. Poking and waiting on teams is the big time thing
[16:10] <scott_ev> ok
[16:23] <scott_ev> who is the editor of the fridge?
[16:24] <nhandler> scott_ev: There are several fridge editors. What do you need?
[16:26] <scott_ev> well, The Fridge Calendar isn't where LoCos are supposed to list team meatings
[16:26] <scott_ev> the DC team needs to  be made aware of this
[16:27] <scott_ev> or the calendar could get very crowded very fast if other teams follow suit
[16:27] <nhandler> scott_ev: It has been a bit mixed in the past. For a long period of time, we were using it for meetings (of any sort), classroom sessions, loco get-togethers, etc. DC Team has been using it for a while as well. It might be worth waiting the extra month or two until we have some other resources in place for them to use instead
[16:28] <scott_ev> ah, are they a relatively new team?
[16:29] <nhandler> No
[16:29] <scott_ev> then I'm confused
[16:31] <nhandler> scott_ev: About what?
[16:31] <scott_ev> oh, it's really unimportant.  I just found it odd that they list their meeting on this calendar is all
[16:31] <scott_ev> as long as it's ok, np
[16:44] <scott_ev> akgraner: I just noticed team meetings section.  Is that there in addition to the meetings from the fridge calendar?  or do you want me to use that as a new meetings template?
[16:50] <scott_ev> OK, the google doc is slightly different from the wiki.  I added meetings and events to the wiki
[16:50] <scott_ev> akgraner: so if there's somthing else I can be doing.....
[18:23] <nigelb> nhandler: poke, help
[18:45] <cjohnston> akgraner: meetings are in the gdoc.. i cant get the wiki to load right now
[18:50] <nigelb> wiki is failing, foo
[18:50] <nigelb> cjohnston: back up now \o/
[18:51] <nigelb> akgraner: I have an hour or so if you folks need help :)
[18:56] <nigelb> cjohnston: poke
[18:56] <cjohnston> ?
[18:57] <nigelb> At UDS, I had asked for patch statistics to be included as part of the numbers, remember?
[18:58] <nigelb> So, you can take the numbers from https://bugs.launchpad.net/ubuntu/+bugs?field.has_patch=on
[18:59] <cjohnston> akgraner: ping ^^
[19:16] <akgraner> scott_ev, they've been using it for a while - and until we get the new loco team calendar in place I am not inclined to ask anyone to change it - once we get the new loco-team calendar up - we'll be asking the loco teams to use it
[20:16] <scott_ev> akgraner: that makes sense
[20:16] <scott_ev> it's not that it bothered me.  why would it?  I just found it odd
[23:47] <akgraner> nhandler, when you are around tomorrow - can you let me know how were can get all the scripts we are currently using added to bzr etc..  Not today as I am still knee deep in the UWN but sometime next week - thanks
[23:56] <ZachK_> akgraner: ping
[23:56] <akgraner> pong
[23:57] <ZachK_> akgraner: hey you
[23:57] <ZachK_> we gonna collaborate on the Wiki stuff you want me to do?
[23:57] <ZachK_> I've been trying to get ahold of you to talk about it
[23:58] <akgraner> I had to stay off the computer for a couple of days to rest my arm
[23:58] <ZachK_> ah....
[23:58] <ZachK_> that is recommended
[23:59] <akgraner> can't talk about that today - need to get UWN published - let's look at it tomorrow ok?


[19:20] <Jester86> hello
[19:20] <Jester86> Somehow my entire ubuntuone account is now empty
[19:20] <Jester86> Can anyone help me get my data back?
[19:31] <Jester86> I have lost everything.. if anyone has access to restore files please let me know
[20:45] <jgdx> Hi Jester86, you can contact the support team by filling out this form: https://one.ubuntu.com/help/contact/


[04:13] <[g2] > Has there been any thought about an EFI based network installer ?
[04:25] <[g2] > another topic: Dapper (and probably any Linux) corrupted my MacIntel OSX rootfs when mounting and writing to a 3rd partition
[04:26] <[g2] > the 3rd partition was the bootcamp created partition for another OS
[04:27] <[g2] > I created a vfat partition and it worked fine, but OS X was hosed after that


[06:53] <bullgard4_> [Natty] In a virtual console I entered '~$ ubuntu-bug zeitgeist'. The program stopped when showing on the first line in red "[Contnue]" and on the last line "Arrow Up Arrow Down Viewing [SSL] <OpenID transaction in progress>. How to continue?
[06:53] <bullgard4_> +i
[11:14] <phillw> Hiyas, I am trying to register a bug as a duplicate, but the system will not accept the bug number? ( 823695 to 772749) any idea why?
[12:03] <jibel> phillw, because bug 772749 is already a dup of another bug
[12:03] <ubot4> Launchpad bug 772749 in lxinput (Ubuntu) "lxinput seg fault on setting change (dup-of: 725194)" [Undecided,Confirmed] https://launchpad.net/bugs/772749
[12:03] <ubot4> Launchpad bug 725194 in lxinput (Ubuntu) "lxinput crashed with SIGSEGV in XkbUseExtension() (affects: 22) (dups: 9) (heat: 126)" [Medium,Fix released] https://launchpad.net/bugs/725194
[12:04] <phillw> jibel: thanks :)
[15:01] <om26er> which team you need to be on to target bugs for releases?
[15:05] <yofel> bug control
[15:17] <brendand> yofel - i think we can only propose bugs to be targeted to a release
[15:18] <yofel> argh, I've had too much berlin air. You're right
[15:18] <yofel> was confusing milestones and release targetts
[15:18] <yofel> *targets
[16:32] <charlie-tca> Ubuntu QA meeting in #ubuntu-meeting in 30 minutes. Agenda is at https://wiki.ubuntu.com/QATeam/Meetings
[16:59] <charlie-tca> QA Meeting in #ubuntu-meeting now
[18:35] <brendand> anyone else suddenly unable to login on oneiric?
[18:35] <charlie-tca> I could not login to a fresh install after updating it today
[18:37] <bullgard4_> charlie-tca: No. I can.
[18:43] <brendand> charlie-tca - i'm fully updated and can't login now
[18:43] <charlie-tca> That's what happened here
[18:43] <brendand> charlie-tca - if i use gdm then i see a message about not being able to update .ICEauthority
[18:43] <charlie-tca> installed from today's image, restarted, updated, restarted. no more login
[18:43] <charlie-tca> That's a permissions error then
[18:44] <brendand> charlie-tca - if i use lightdm then it looks like it's going to login then goes back to lightdm
[18:44] <charlie-tca> right
[18:44] <charlie-tca> mine didn't even act like it would login. It just said "incorrect password" every time
[18:45] <brendand> oh, maybe different issues then :/
[18:46] <charlie-tca> or the difference in how lightdm works for Ubuntu vs Xubuntu
[18:46] <charlie-tca> I would bet even money on the same issue
[18:46] <brendand> charlie-tca - ah, you're on xubuntu
[18:47] <charlie-tca> yeah, makes it much more fun
[18:47] <charlie-tca> I saw some users in #ubuntu+1 having login issues too after updating
[18:47] <charlie-tca> It doesn't seem to affect everybody, for some odd reason
[19:42] <hggdh> why would debian-installer accept a sequence of mirror/http/* directives, and then override them with other values?
[19:43] <roadmr> ah, d-i :)
[19:44] <hggdh> yeah :-(


[01:18] <vorlon> why does kitty, in universe, trigger an apport autopkgtest. :|
[01:19] <vorlon> Provides: x-terminal-emulator
[01:19] <vorlon> siiiiiigh
[01:26] <Eickmeyer> vorlon: I was wondering the same thing. It's merely a terminal emulator.
[01:31] <vorlon> yeah this is the 'autopkgtest picks up all provides and non-default alternatives' thing
[01:31] <Eickmeyer> *facepalm*
[01:32] <vorlon> I don't think I can actually argue that it's incorrect.  It's just annoying when it's slowing things down
[01:32] <Eickmeyer> Yep. It's keeping python-defaults from migrating, which is keeping hugin from migrating, which is keeping ubuntustudio from building.
[01:33] <Eickmeyer> I've been keeping an eye on the excuses today.
[01:34] <vorlon> kitty already passed on a retry, and I've pushed a skiptest for omniorb-dfsg
[01:34] <Eickmeyer> Oh, perfect.
[01:35] <Eickmeyer> python-bumps is having... bumps.
[11:50] <LocutusOfBorg> sigh, gnat
[11:53] <ricotz> hello ubuntu-archive, please reject the libroffice package of 2023-01-19 from jammy/unapproved - https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=libreoffice
[11:55] -queuebot:#ubuntu-release- Unapproved: libreoffice (jammy-proposed/main) [1:7.4.4-0ubuntu<IP_ADDRESS>~bpo22.04.1 => 1:7.3.7-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[11:56] -queuebot:#ubuntu-release- Unapproved: rejected libreoffice [source] (jammy-proposed) [1:7.3.7-0ubuntu<IP_ADDRESS>]
[12:02] <seb128> ricotz, ^
[12:02] <ricotz> seb128, ty
[12:24] <kanashiro[m]> ubuntu-archive: could you please remove ruby-defaults from sync-blacklist.txt? I need to sync it from Debian unstable now
[12:24] <kanashiro[m]> https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt#L653
[12:24] <kanashiro[m]> https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt#L737
[13:40] <vorlon> kanashiro[m]: done
[13:47] <kanashiro[m]> vorlon: ty!
[14:18] <kanashiro[m]> vorlon: there is still this occurrence of ruby-defaults in that file: https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt#L734
[14:21] <vorlon> we had it blacklisted twice? oh well then
[14:22] <vorlon> kanashiro[m]: fixed harder
[14:22] <kanashiro[m]> it seems so
[14:22] <kanashiro[m]> thanks!
[14:24] <tsimonq2> Not sure if autosync is still off, but sip6/pyqt5 should finally unstick things once synced
[14:25] -queuebot:#ubuntu-release- Unapproved: rejected docker.io [source] (bionic-proposed) [20.10.21-0ubuntu1~18.04.2]
[14:26] -queuebot:#ubuntu-release- Unapproved: docker.io (bionic-proposed/universe) [20.10.21-0ubuntu1~18.04.1 => 20.10.21-0ubuntu1~18.04.2] (no packageset)
[14:31] <vorlon> hopeful for a successful gprbuild/s390x autopkgtest run with --all-proposed
[14:32] <vorlon> LocutusOfBorg: fwiw 'retry-autopkgtest-regressions --all-proposed | grep gprbuild' gives you a single run which gathers up all relevant triggers into a single request, a bit more efficient...
[14:32] <vorlon> (since you're already doing --all-proposed, there's no reason to have separate runs)
[14:33] <vorlon> hmm some of these logs are still showing conflicts with gnat-11
[14:34] <vorlon> unreproducible in a lunar container :P
[14:35] <vorlon> gnat is already the newest version (11.2ubuntu1).
[14:35] <vorlon> what is this lie
[14:47] <vorlon> skiptesting everything related to gprbuild/s390x, I don't know why this failed only on s390x but it's testbed / apt config nonsense and not worth blocking on
[14:49] <bdmurray> I've seen an autopkgtest failure or with a kernel panic `Begin: Running /scripts/init-bottom ... [   42.658620] mv invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0`
[14:49] <bdmurray><EMAIL_ADDRESS>[15:02] -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (bionic-proposed) [20.10.21-0ubuntu1~18.04.2]
[15:26] <LocutusOfBorg> vorlon, this is true, but I sometime fail to get output from the retry-autopkgtest-regressions script
[15:26] <LocutusOfBorg> and yes, locally it doesn't have the conflict issue, on s390x environment
[15:27] <LocutusOfBorg> so we are waiting for pyqt5 now?
[15:31] <bdmurray> LocutusOfBorg: "fail to get output"?
[15:33] <vorlon> bdmurray: the filtering to avoid duplicate requests sometimes goes awry
[15:35] <LocutusOfBorg> sometimes the script returns "null"
[15:36] <LocutusOfBorg> maybe arraybolt3 or arraybolt3[m] can have a look at lubuntu-update-notifier sadness on amd64 autopkgtests?
[15:37] <LocutusOfBorg> https://autopkgtest.ubuntu.com/packages/l/lubuntu-update-notifier/lunar/arm64
[15:37] <LocutusOfBorg> I can't reproduce locally tbh
[15:39] <LocutusOfBorg> for pyqt5 regression of pyspread we probably need 5.15.8+dfsg-2
[15:42] <LocutusOfBorg> pyqt5/sip6 uploaded
[16:08] -queuebot:#ubuntu-release- New binary: uwsgi [amd64] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:09] -queuebot:#ubuntu-release- New binary: uwsgi [armhf] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:09] -queuebot:#ubuntu-release- New binary: uwsgi [s390x] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:12] -queuebot:#ubuntu-release- New binary: uwsgi [ppc64el] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:19] -queuebot:#ubuntu-release- New binary: uwsgi [arm64] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:20] -queuebot:#ubuntu-release- New: accepted uwsgi [amd64] (lunar-proposed) [2.0.21-4]
[16:20] -queuebot:#ubuntu-release- New: accepted uwsgi [armhf] (lunar-proposed) [2.0.21-4]
[16:20] -queuebot:#ubuntu-release- New: accepted uwsgi [s390x] (lunar-proposed) [2.0.21-4]
[16:21] -queuebot:#ubuntu-release- New: accepted uwsgi [arm64] (lunar-proposed) [2.0.21-4]
[16:21] -queuebot:#ubuntu-release- New: accepted uwsgi [ppc64el] (lunar-proposed) [2.0.21-4]
[16:24] <arraybolt3> LocutusOfBorg: wrt lubuntu-update-notifier sadness on PyQt5, I also could not reproduce locally and asked vorlon to trigger an --all-proposed autopkgtest retry. All that seemed to do was cause another failure but this time because of a quirk in the infra (the failure was obviously not an actual failure, I think it was some "could not retrieve file" something or other).
[16:25] <arraybolt3> I don't even see how the failure in there has anything to do with PyQt5, but I was unable to make it fail no matter what I did.
[16:27] <arraybolt3> Hmm, though I thought I was looking at a Bash error or something, now that i look closer, it might be an actual failure...
[16:45] <arraybolt3> Since I can't reproduce the failure locally, I just did an upload that adds more info to the autopkgtest output so that hopefully the logs tell us what's happening when the test runs in production.
[16:46] <tsimonq2> arraybolt3: The arm64 failure?
[16:47] <tsimonq2> LocutusOfBorg: not probably, we definitely need the two aforementioned uploads ;)
[16:47] <arraybolt3> tsimonq2: NO, the apt-check failure.
[16:48] <tsimonq2> arraybolt3: I'll follow up in l-devel
[16:51] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (jammy-proposed) [2.06-2ubuntu7.2]
[16:52] -queuebot:#ubuntu-release- Unapproved: grub2 (jammy-proposed/main) [2.06-2ubuntu7.1 => 2.06-2ubuntu7.2] (core, i386-whitelist)
[17:00] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (jammy-proposed) [2.06-2ubuntu7.2]
[17:03] -queuebot:#ubuntu-release- Unapproved: grub2 (focal-proposed/main) [2.04-1ubuntu26.16 => 2.04-1ubuntu26.17] (core)
[17:08] <LocutusOfBorg> tsimonq2, arraybolt3 yes, the apt-check is transient, the other one is a failure in sip
[17:08] <LocutusOfBorg> so, meh and upload and wait
[17:11] -queuebot:#ubuntu-release- Unapproved: accepted golang-github-openshift-imagebuilder [source] (focal-proposed) [1.1.0-2ubuntu<IP_ADDRESS>]
[17:21] <arraybolt3> LocutusOfBorg: Hmm, I didn't even see the other failure, so I thought the apt-check thing was the only thing going wrong.
[17:22] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (focal-proposed) [2.04-1ubuntu26.17]
[17:23] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (focal-proposed) [2.04-1ubuntu26.17]
[17:24] <LocutusOfBorg> autopkgtest for pyspread/2.1.1-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Not a regression, ppc64el: Regression ♻ , s390x: Regression ♻
[17:24] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [amd64] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:24] <LocutusOfBorg> arraybolt3, ^^ :)
[17:24] <LocutusOfBorg> and its due to a problem in pyside2, introduced by a problem of sip6
[17:25] <LocutusOfBorg> so, upload and rebuild is needed
[17:25] -queuebot:#ubuntu-release- Unapproved: accepted golang-github-fsouza-go-dockerclient [source] (focal-proposed) [1.6.0-2ubuntu<IP_ADDRESS>]
[17:25] <LocutusOfBorg> (and probably stopping autosync until the migration happens is something to be done)
[17:25] <arraybolt3> Oh. I must be missing backlog, since that has nothing to do with what I thought we were talking about :P Sorry.
[17:26] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [armhf] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [s390x] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [ppc64el] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:26] <LocutusOfBorg> arraybolt3, pyside2 regressed two autopkgtests, one we spoke about apt-foo, the other was another regression in pyside2 itself
[17:26] <LocutusOfBorg> so, giving back your apt-check test is not useful since we rebuild pyside2 anyway
[17:26] <LocutusOfBorg> and with pyside2 I mean pyqt5
[17:27] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [arm64] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:28] <arraybolt3> K, I hope that works. I'm worried that maybe it's not PyQt5's fault at all, but the way the regressions are happening does seem to imply that it is.
[17:28] <arraybolt3> (Sorry if I sound inexperienced, I've not hardly worked with autopkgtests in the past, I'm just learning how to use them now.)
[17:28] <LocutusOfBorg> arraybolt3, I couldn't reproduce locally, so I agree
[18:15] <Eickmeyer> Looks like hypothesis is the major hurdle for python3-defaults.
[18:18] <tsimonq2> Eickmeyer: Uh, how?
[18:18] <tsimonq2> skiptest is put in place, aren't we waiting on pyqt5?
[18:19] <Eickmeyer> tsimonq2: If there's skiptest in place, then that's surprising as it's still showing regressions on all Britney outputs for over the past 24 hours.
[18:20] <tsimonq2> It's still going to show the regressions, it just doesn't care about them.
[18:20] <Eickmeyer> Ok. Well, I still doubt it'll migrate.
[18:20] <tsimonq2> skiptest likely means "skip the autopkgtest Britney policy when considering this"
[18:22] <Eickmeyer> Nvm, it's pyqt5 we're waiting on now.
[18:22] <tsimonq2> I just said that... ;)
[18:22] <Eickmeyer> I didn't investigate deep enough. *facepalm*
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [amd64] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [armhf] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [s390x] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [arm64] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [ppc64el] (lunar-proposed) [0.0.15]
[18:31] <vorlon> LocutusOfBorg: autosync is already turned off ftr
[18:31] <LocutusOfBorg> oh nice!
[18:32] <LocutusOfBorg> vorlon, do you think we can remove uwsgi-plugin-luajit on ppc64el?
[18:32] <LocutusOfBorg> not yet done in Debian (I pinged maintainer on irc #-devel)
[18:33] <LocutusOfBorg> Missing build dependencies: libluajit-5.1-dev
[18:33] <LocutusOfBorg> this is not going to build ppc64el anytime soon
[18:33] <vorlon> looking
[18:33] <vorlon> LocutusOfBorg: I don't see anything to remove
[18:34] <Eickmeyer> I just got the build failure email. Removing hugin from Ubuntu Studio to get it to build.
[18:34] <LocutusOfBorg> vorlon, its in release?
[18:34] <vorlon> LocutusOfBorg: not according to rmadison
[18:34] <LocutusOfBorg> meh strange
[18:34] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/uwsgi-plugin-luajit/0.0.7build1
[18:34] <vorlon> LocutusOfBorg: what are you seeing that tells you it's there?
[18:34] <LocutusOfBorg> I see it here
[18:34] <vorlon> you see that it was built
[18:34] <LocutusOfBorg> ohhhhhhhhhhhhhhh
[18:34] <LocutusOfBorg> :D
[18:34] <vorlon> but the binary was removed, probably from a previous request of yours :)
[18:35] <LocutusOfBorg> I though after removal somebody was doing no change rebuild to avoid confusion
[18:35] <LocutusOfBorg> thanks!
[18:36] <LocutusOfBorg> so, bpftrace now back in sync with Debian
[18:36] <LocutusOfBorg> sip6/pyqt5 building, but will take 18 hours to complete riscv
[18:36] <LocutusOfBorg> paraview might now build on riscv64
[18:36] -queuebot:#ubuntu-release- Unapproved: rejected bind9 [source] (focal-proposed) [1:9.16.1-0ubuntu2.12]
[18:36] <LocutusOfBorg> don't see any other blocker for big migration?
[18:37] <LocutusOfBorg> (uwsgi fixed)
[18:38] <LocutusOfBorg> if anybody can see if we have other blockers, please write them here
[19:09] -queuebot:#ubuntu-release- Unapproved: bind9 (focal-proposed/main) [1:9.16.1-0ubuntu2.12 => 1:9.16.1-0ubuntu2.13] (core, i386-whitelist)
[19:30] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.4.2-0ubuntu5 => 2:16.4.2-0ubuntu6] (openstack, ubuntu-server)
[20:00] -queuebot:#ubuntu-release- Unapproved: accepted squid [source] (jammy-proposed) [5.2-1ubuntu4.3]
[20:10] <ricotz> LocutusOfBorg, I think you want to cancel that https://launchpad.net/ubuntu/+source/pyqt5/5.15.8+dfsg-2~build1/+build/25542934
[20:27] <LocutusOfBorg> ricotz, the builders are not busy, and that build is like one hour older of the newer sync one
[20:27] <LocutusOfBorg> so, its like watching the future :D
[20:39] <ricotz> LocutusOfBorg, seems like a waste if this is going to run 18 hours as you mentioned
[20:40] <LocutusOfBorg> feel free to cancel it :)
[20:41] <ricotz> I don't have the rights to do so
[20:55] <LocutusOfBorg> done
[21:39] -queuebot:#ubuntu-release- New binary: ruby-psych [amd64] (lunar-proposed/universe) [5.0.2-1build1] (no packageset)
[21:39] <bdmurray> ginggs: I see you requested finalcif be run - how did you end up there? I'm dealing with an issue where some tests are OOM'ing and the test environment is handling that differently.
[21:40] <bdmurray> ginggs: I've added finalcif to big_packages and was wondering if you might have found a list of packages that might need to be in big because reading journalctl is lame.
[22:11] -queuebot:#ubuntu-release- Unapproved: pivy (jammy-proposed/universe) [0.6.5-1build6 => 0.6.5-1ubuntu<IP_ADDRESS>] (no packageset)
[22:12] -queuebot:#ubuntu-release- Unapproved: pivy (kinetic-proposed/universe) [0.6.7-0.1 => 0.6.7-0.1ubuntu0.1] (no packageset)
[22:24] <vorlon> kanashiro[m]: reverting your protobuf upload, protobuf is part of the python3 transition
[22:41] <kanashiro[m]> vorlon: sorry, my script goes through all ruby rdeps and protobuf is one of them


[00:22] <bluesabre> that sounds important
[12:02] <knome> Unit193, yeah, do you wish to upgrade to 18.04?
[12:03] <Unit193> >_>