[19:02] <Caroline> hello?
[19:03] <dfarning> hey Caroline
[19:03] <Caroline> hey
[19:03] <Caroline> I made it
[19:03] <Caroline> in a coffee shop
[19:03] <dfarning> just talked to manu he will be leading the meeting and doing introductions
[19:04] <dfarning> how is the coffee?
[19:04] <Caroline> I was rushing to gt logged in and haven't gotten any yet!
[19:05] <Caroline> if its going to be a few I'll go get some. :)
[19:05] <dfarning> ok am watching the wireless generation videos on my nieces laptop.
[19:06] <dfarning> I will read the papers this evening.
[19:06] <Caroline> cool biab
[19:07] <dfarning> band in a box?
[19:07] <dfarning> ahh back in a bit:)
[19:15] <Caroline> ok I'm back
[19:15] <Caroline> ok I'm back
[19:15] <Caroline> no Manu or Ian?
[19:16] <dfarning> net yet
[19:17] <dfarning> Caroline, not sure what happened to Ian. manu may be having time zone problems
[19:18] <dfarning> in the mean time http://lwn.net/SubscriberLink/387196/012bee6d6d0b95d0/
[19:19] <dfarning> meego is defaulting to btrfs
[19:19] <dfarning> just pinged manu
[19:21] <manusheel> dfarning: Hi David.
[19:21] <dfarning> manusheel, gooe afternoon
[19:22] <dfarning> manusheel, what city do you live in?  I would like to add it to my gnome clock.
[19:22] <manusheel> dfarning: New Delhi, India.
[19:22] <manusheel> State = Delhi.
[19:24] <dfarning> ok got it thanks.  Is it 1150 pm for you?
[19:24] <manusheel> dfarning: Yes, 11:54 pm.
[19:24] <dfarning> great Caroline are you back?
[19:24] <Caroline> yes
[19:25] <manusheel> Caroline: Hi Caroline.
[19:25] <dfarning> manusheel, would you like to start?
[19:25] <manusheel> dfarning: Sure, thank you.
[19:26] <manusheel> Wish to share our plans for the next 3 months.
[19:27] <dfarning> great I think yesterday was about making sure we were in agreement on the high level goals. today is tatical plans and implementation
[19:29] <dfarning> manusheel, did we lose you?
[19:30] <manusheel> dfarning: I am here. Sorry, some network issues at my end.
[19:31] <dfarning> manusheel, np.  looks like we have several communication related issues to work out.
[19:32] <manusheel> dfarning: Yes, I did work out the implementation level details that could match our needs.
[19:32] <dfarning> manusheel, great
[19:32] <manusheel> dfarning: My apologies again.
[19:33] <manusheel> dfarning: We arrived at a set of 4 specific areas that could help us arrive at a point, where we can make USR available for deployments -
[19:33] <manusheel> 1. Getting the mouse control areas worked out. There are a number of issues on this front at this juncture;
[19:34] <dfarning> ok
[19:35] <manusheel> 2. Have the basic Sugar user interface working with the basic set of functionalities. The resolution and even the display of Sugar home in USR is not in sync with other Sugar distributions;
[19:36] <dfarning> yes
[19:36] <manusheel> 3. Have the control panel and basic set of libraries working. Example - Abiword library, which supports Write and Newspaper. This will require us to get into the API level details, and matches with our work on API documentation.
[19:37] <manusheel> 4. Get the activities working by closely working with activity authors. This part would start when we initiate the earlier step. As we agree, trust and cooperation cannot be surged.
[19:37] <dfarning> yes.
[19:38] <dfarning> with reguard to brower libs have you looked at surf in stead of browse?
[19:39] <dfarning> http://surf.suckless.org/
[19:40] <manusheel> Yes, we did look at it. It is a very good program. However, we are yet to understand the leadership maintaining this activity.
[19:41] <manusheel> We would like to work with them, if they that sense of scalability and sustainability in their goals and operational dynamics. Learning lessons from the loss of PyXPCOM.
[19:41] <manusheel> have that*
[19:42] <dfarning> agreed.
[19:43] <dfarning> is abiword well supported?
[19:44] <manusheel> Yes, abiword is well supported. Not pyabiword. Thats the problem, and we are trying to fix this with Martin.
[19:44] <dfarning> or pyabiwork in our case?
[19:44] <manusheel> Abiword is on a major expansion. They have moved to platforms like Maemo too.
[19:44] <dfarning> was pyabiwork a olpc project?  I don't know its history.
[19:45] <manusheel> Pyabiword was supported by OLPC volunteers. Martin Seviour was the lead.
[19:46] <dfarning> so if we want to depend on it we will need to ensure its continued development.
[19:47] <manusheel> Yes, absolutely. We need a maintainer for Pyabiword. We have trained two developers at SEETA to work with PyAbiword too.
[19:48] <Caroline> how crazy would it be to sugarize Open Office for kids instead?
[19:48] <dfarning> great. pyabiword can be a area where we can significantly help support upstream.
[19:49] <manusheel> Caroline: It is a very interesting project. We are developing interoperability between SocialCalc and open source spreadsheet from Open Office.
[19:51] <manusheel> Sugarizing Open office is going to take time. But, a very interesting project.
[19:52] <dfarning> are there other libs besides pyabiword that will need significant support?
[19:52] <manusheel> It is not a crazy idea. However, C language has been used a lot in open office. So, we'll have to spend time on C-Python bindings.
[19:52] <manusheel> dfarning: Yes, we can support pyabiword upstream.
[19:52] <manusheel> There are other libraries as well.
[19:53] <manusheel> But, Pyabiword fits our use case very neatly. Some of the other libraries use QT.
[19:54] <manusheel> I'll be sending a memo to Tomeu on his progress on PyQT. Someone from Finland, did port Sugar on QT based Nokia tablet, as far as I remember.
[19:54] <dfarning> I don't think the port to the nokia tablet ever got start:(
[19:55] <dfarning> You mentioned issues with the control panel?
[19:56] <manusheel> dfarning: Ok, it appeared on the author's blog that he did manage to do it. I'll check and send you the link to the blog.
[19:56] <manusheel> dfarning: Yes,
[19:56] <Caroline> i have to run
[19:56] <dfarning> ok great.  I did not hear that that got completed.
[19:57] <dfarning> talk to you later caroline
[19:57] <dfarning> what are the issues with the control panel?
[19:57] <manusheel> we have a good number of issues on the control panel front. Language switching is a problem right now.
[19:58] <manusheel> When we switch to say Colombian, and want to switch back to English US, the language settings does not work as expected.
[19:58] <manusheel> Spanish (Colombian)
[19:59] <dfarning> it this a bug or differences in design between olpc and ubuntu?
[20:00] <manusheel> stays there. And, it overrides the event to switch to English. I think it is an issue due to difference in design. We are yet to get into the ground level details of this issue.
[20:01] <manusheel> We are focusing on our point number #1 - mouse control. David, I'll be adding one QA expert per area this week, who can investigate and document the issues as developers work on fixing them.
[20:02] <dfarning> ok that is a good approach.
[20:02] <manusheel> dfarning: This is how I see the software engineering life cycle moving at our end -
[20:02] <dfarning> how are the basic patching and packaging tasks coming?
[20:03] <dfarning> are developers getting up to speed?
[20:03] <manusheel> dfarning: You'll see packages been uploaded by new developers before the weekend starts. Yes, the progress seems to be coming along pretty well. Getting good feedback on their learning curve.
[20:04] <manusheel> We have asked them to work on 0.88 tarballs at this juncture in reference to packaging.
[20:04] <dfarning> great.
[20:05] <manusheel> dfarning: So, the engineering life cycle is as follows -
[20:06] <manusheel> 1. We have identified the areas (discussed above). We'll be preparing business required specification documents per area to help meet the important needs of the user. Basically, a set of areas, which we need to be good at before we reach the shipping point.
[20:07] <manusheel> 2. Ask the developers to get a good hang on the code parallely and ask the QA guys to create test plans for each area. Automated test plans might be an easier approach here.
[20:08] <manusheel> 3. Ask the QA team members to raise tickets in the bug track with issue, steps to reproduce the issue and resolution to the issue.
[20:09] <manusheel> 4. These issues will be first examined by the project managers specific to areas before they release them to development.
[20:10] <manusheel> 5. Once the issues get released, the development manager will assign them to the developers according their areas of code familiarity and expertise. This is one phase where handholding would be required from our side. The discussions should be kept in sync with the timelines.
[20:11] <manusheel> 6. The developers fix the issues, and assign back to the QA team. The QA team verify the issues, and add release notes (one per issue).
[20:12] <dfarning> Ok, so as issues move to step 5, we will need to look for subject matter experts to help with leaning?'
[20:12] <manusheel> 7. In parallel, we'll have the user guide and architectural level documentation being initiated by two team members working on documentation efforts at this juncture.
[20:14] <manusheel> dfarning: We'll have to identify them as we begin creating the release cycle goals. They can help us audit our BRDs (Business Requirement Documents) with focus on functional deliverables.
[20:15] <dfarning> good, that will give us more lead time.
[20:16] <manusheel> dfarning: I think a good point to start working with them will be when we have done the initial document per functionality ready at our end. They will help us establish if we need to re-work on the document, or we are good to go in terms of meeting the shipping needs of our clients (OEMs).
[20:17] <manusheel> dfarning: I almost ready with the template
[20:17] <manusheel> for doing functional level documentation and BRDs.
[20:17] <manusheel> Will send it across by Saturday.
[20:17] <dfarning> great.
[20:18] <manusheel> It has the desired format and we should be able to capture the details succintly.
[20:18] <dfarning> what are we looking at for cash burn rate over the next 6-12 month to support this implementation?
[20:21] <manusheel> dfarning: Right David. I'll send you a plan on the first 6 month period. Yes, it is indeed a 12 month long project. I think we should have Q1 release in 11 months. The last 1 month will be on assessment and documentation.
[20:21] <manusheel> Code freeze and feature freeze timelines can be worked out once we have the BRDS with us.
[20:22] <dfarning> ok, I'll look forward to getting those.
[20:23] <dfarning> What are the most important things you need from me over the next couple of weeks/months?
[20:23] <manusheel> dfarning:  Have one person per subject area working with me on defining the functionality document and set of features we would like to support in the first release.
[20:24] <manusheel> Someone, who would have worked on these respective areas before.
[20:24] <manusheel> That would expedite our processes.
[20:24] <manusheel> dfarning: We would like to have the BRDs worked out by June end.
[20:25] <manusheel> This should capture fine details of our work.
[20:26] <dfarning> ok, as you identify these area, I'll work on engaging particular people.  There are a lot of former OLPC developers with a great deal of knowledge but limited time/interest to commit
[20:27] <manusheel> dfarning: Ok, if time is the constraint, they can provide us the bigger picture view. And, we can take up from there.
[20:28] <manusheel> They can be our consultants.
[20:28] <manusheel> dfarning: Do we have someone, who can commit certain number of hours per week on helping us define the BRDS?
[20:29] <dfarning> Ahh I think they we be willing to help with brds... they just don't have time/interest to hack.
[20:30] <dfarning> Let me think about that.  what expertise are you looking for?
[20:30] <manusheel> dfarning: Expertise to help arrive at a list of features per functionality, and define deliverables around it.
[20:31] <manusheel> A set of critical features
[20:31] <manusheel> without which we cannot ship USR.
[20:33] <dfarning> Ok, this sounds like a position for a person with deployment experience and a good overall knowledge of sugar.
[20:33] <manusheel> dfarning: Also, a note on definitions per functionality and the UI pages and backend part that is supported by that functionality. Yes, deployment experience + good overall knowledge of Sugar will be helpful.
[20:34] <manusheel> I think someone from OLE Nepal can help us get started on it easily.
[20:34] <dfarning> we need to look at 'critical features' from the point of view of a deployment support person.
[20:34] <manusheel> dfarning: yes.
[20:35] <dfarning> Yes, or someone like daniel drake.
[20:36] <manusheel> dfarning: Yes, Daniel is a good candidate for this role.
[20:36] <dfarning> ok, I'll start on that task.
[20:36] <manusheel> dfarning: I'll send you the template, and you'll get a very good idea on my expectations.
[20:37] <manusheel> dfarning: Thank you. Appreciate your support.
[20:39] <dfarning> how about setting up reoccuring status meetings?
[20:39] <dfarning> should we start holding those or is it too soon?
[20:40] <dfarning> Luke will be joining us in a few minutes.
[20:40] <manusheel> dfarning: Sure. Status calls are important.
[20:40] <manusheel> However, they should be more on the BRD front right now. On the development front, code fixes and QA documentation would do.
[20:42] <manusheel> dfarning: Without a set of objectives, it is difficult to build timelines. My idea is to first arrive at set of BRDs. In parallel, the knowledge transfer for development should continue.
[20:42] <lfaraone> Hello, world!
[20:42] <manusheel> lfaraone: Hi Luke.
[20:42] <dfarning> ok, how about 8am (boston time) checkins
[20:43] <dfarning> hey lfaraone
[20:43] <manusheel> dfarning: 8:00 am to 9:00 am will be a good time.
[20:43] <dfarning> just want to make sure you and manusheel touch base.
[20:44] <manusheel> dfarning: Thanks David. lfaraone:  Wish to ask you whether 8:00-9:00 am, Boston time works well at your end.
[20:44] <lfaraone> manusheel, dfarning, agreed re time.
[20:44] <manusheel> lfaraone: Great.
[20:44] <dfarning> manusheel, ok I schedule that slot for seeta cordination/ work.
[20:45] <manusheel> dfarning: Thank you.
[20:45] <dfarning> Ok, I think we have the stratigc stuff done, so I will step aside and let you and luke work through implemation issues:)
[20:45] <dfarning> thanks for everything.
[20:46] <lfaraone> awesome. I sent both dfarning and manusheel a google calendar item.
[20:46] <manusheel> dfarning: Thank you so much.
[20:46] <manusheel> lfaraone: That would be great.
[20:46] <manusheel> lfaraone: Can we begin meetings starting tomorrow?
[20:46] <lfaraone> manusheel: sure.
[20:47] <manusheel> For the first set of days, it will be both of us, who will arrive at a plan. Then, we'll get the developers in.
[20:48] <manusheel> lfaraone: Great. Let us meet tomorrow at 8:00 am Boston time. The agenda of the meeting will be getting started on the development of Sugar, method for submitting patches and reviewal, and methods to walking through the Sugar code.
[20:48] <lfaraone> manusheel: seens sensible.
[20:48] <manusheel> lfaraone: Thank you.
[20:50] <manusheel> lfaraone: Great. Talk to you tomorrow. Have a nice evening.
[20:50] <lfaraone> manusheel: after June 17, things will be a bit up in the air for the next week as we have to deal with final exams in my school, but after June 23 I'll be more free.
[20:50] <lfaraone> manusheel: you too.
[20:50] <manusheel> lfaraone: Is it June 23? Or, May 23?
[20:51] <lfaraone> manusheel: June.
[20:51] <manusheel> Caroline: We'll send you the meeting logs on our discussion.
[20:52] <manusheel> lfaraone: Sure. Thank you for informing about it at this juncture. We'll make plans accordingly.
[20:55] <manusheel> lfaraone: Neat. So, as discussed, we'll work out a plan on three areas as discussed above. We might have to do in documentation to prevent us from mentoring the same things to different set of developers. I almost through with preparing the template for these three areas. Will send it to you before the meeting.
[20:55] <lfaraone> manusheel: okay. for documentation, do you want to host it on the Ubuntu wiki, the Sugar Labs wiki, or somewhere else?
[20:57] <manusheel> lfaraone: I'll let you know about it by tomorrow. Will evaluate what would be a good idea from the expansion standpoint.
[20:58] <manusheel> lfaraone: In any case, I would prefer to use Mediawiki at this juncture.
[20:58] <manusheel> lfaraone: We have a number of good extensions been developed for Media wiki.
[21:03] <manusheel> lfaraone: Great, Luke. We'll touch base at 8:00 am, Boston time tomorrow. Talk to you soon.


[00:56] <superm1> well depending on if flash was a big deal
[00:56] <superm1> if not then yeah i agree
[00:56] <superm1> but if you needed flash, that did make it more of a pain
[05:13] <bobobbbob> moin
[05:15] <bobobbbob> odd thing, just installed mythbuntu 11.10 with dev updates too .24.  I can get my DVB cards to find all the "over the air" HD channels properly via the channel scan, but when I go to watch TV.....nothing.  I get a n/s ratio of about 2.3 but no picture materializes.  If I plug cable into tv, works fine. Any ideas?
[05:16] <bobobbbob> it also seems to mesh with schedulesdirect properly as well, I have the right channels and the right programs listed....just can't see a picture :(
[05:17] <bobobbbob> for live tv
[11:53] <mrand> !seen gbutters
[11:53] <Zinn> Sorry I don't know about seen gbutters
[16:41] <xrdodrx> Hello
[16:41] <xrdodrx> I have a very simple setup that isn't working
[16:42] <xrdodrx> I have a Hauppague WinTV HVR-1250 and it's connected to a DirecTV box via coaxial cable
[16:42] <xrdodrx> Channel scanning returns nothing. How do I pick up the input?
[18:18] <tgm4883> superm1, Flash hasn't been a pain for a long time. Even before there was a proper 64-bit version of flash.
[18:18] <tgm4883> I wouldn't call moving 1 file into 1 location a pain
[18:27] <bobob> moin all
[18:28] <bobob> I having a networking issue.  I need my myth backend to come up but leave eth0 alone.  I have a virtualbox vm that will need to bridge to that and get the dhcp from that interface.
[18:29] <bobob> nvm...got it :)
[18:29] <bobob> funny how explaining problem fixes it.....why doesnt' that work when I explain to wife....LOL!
[19:48] <superm1> tgm4883: the 32 bit nspluginwrapper thing was a joke though
[19:48] <superm1> it never was stable enough for me
[19:48] <tgm4883> hmm, perhaps you just went to different sites than I did
[19:48] <tgm4883> You spend too much time on redtube ;)
[19:54] <superm1> haha
[19:54] <superm1> it crashed with youtube for sure
[19:54] <superm1> and of course it was every time that you wanted to show someone else a video on your laptop
[19:55] <mrand> Then they laugh at you using that silly Linux stuff.
[19:55] <mrand> had to happen to me too.
[19:55] <superm1> exactly
[19:59] <mrand> although the 32-bit nspluginwrapper worked fine for my wireless connection that I noticed.


 What format do I covert it too?
[01:22] <roaksoax> Hey: it wont work with MAAS
[01:26] <Hey> roaksoax, I added the curtin files
[01:27] <Hey> actually, I am one step ahead.. I am using windows-opoenstack-imaging-tools to create the image
[14:40] <seffyroff> roaksoax: I want to set the default domain.  currently hosts are receiving .maas, and I don't want that
[14:57] <roaksoax> seffyroff: change the domain name over the API
[15:04] <Hey_> roaksoax: I created a windows image customized it, sysprepped it, then cast it to a Hyper-v VM using WinPE.  I then placed the curtin folder in the root.
[15:05] <Hey_> The steps following this is to create an image that MAAS can use for BareMetal.
[15:05] <Hey_> Do those steps look correct?
[15:05] <Hey_> amd I missing anything?
[15:24] <mup> Bug #1707563 changed: [2.2] no API document on /api/2.0/machines/{system_id}/ op=test <doc> <docteam> <MAAS:Fix Released> <https://launchpad.net/bugs/1707563>
[17:06] <seffyroff> roaksoax: sure thing, that's what I've been wrestling with.  I've tried using the python visceral stuff, the shell, the cli, rest calls via curl or postman, in each case i get different, generic errors
[17:28] <seffyroff> with curl and postman, I can't get oauth exchange to happen, so stuck before anything useful.  With the cli I don't seem to be able to query dnsresources.  Using the maas library from github, the profiles command seems to be missing
[17:28] <seffyroff> so the origin object doesn't get created in the shell
[17:30] <mup> Bug #1759911 opened: [enhancement] during enlistment, when maas can't create a bmc user/password, node's bmc ip address is not reported <foundations-engine> <MAAS:Triaged by andreserl> <https://launchpad.net/bugs/1759911>
[17:36] <seffyroff> correction: the profiles command doesn't seem to include a login subcommand
[18:19] <roaksoax> seffyroff: maas <user> domain update <domain-id> name=<new-name>
[18:19] <roaksoax> seffyroff: this may also be helpful https://www.lucaswilliams.net/index.php/2016/10/02/maas-2-0-and-dns/
[18:21] <seffyroff> roaksoax: thanks! - I'll take a look at the link and try out that cmd
[18:25] <seffyroff> argument COMMAND: invalid choice: 'domain' (choose from 'devices', 'files', 'machines', 'nodes', 'rack-controllers', 'region-controllers', 'version')
[18:26] <seffyroff> the admin profile doesn't have access to the domain
[18:29] <roaksoax> seffyroff: are you sure its a user ?
[18:29] <roaksoax> admin user*
[18:31] <seffyroff> admin is the user i login to the webui with.  How can I determine it's perms?
[18:32] <seffyroff> you are on to something there though
[18:32] <seffyroff> if i use the guthub maas client i see:
[18:32] <seffyroff> ~/amc$ bin/maas users admin --profile admin
[18:32] <seffyroff> Error: argument --profile: invalid choice: 'admin' (choose from )
[18:33] <seffyroff> guthub.  Lol.  Freudian slip there - I need a snack :D
[18:35] <roaksoax> seffyroff: use the older cli
[18:35] <roaksoax> seffyroff: not the one from python-libmaas
[18:36] <seffyroff> with that I get: argument COMMAND: invalid choice: 'domain' (choose from 'devices', 'files', 'machines', 'nodes', 'rack-controllers', 'region-controllers', 'version')
[18:39] <seffyroff> correction
[18:39] <seffyroff> I get argument COMMAND: invalid choice: 'domain' (choose from 'refresh', 'logout', 'list', 'login', 'apikey', 'createadmin', 'changepassword', 'admin')
[18:43] <seffyroff> hang on, i did a refresh and now it looks like I'm getting more options
[18:45] <seffyroff> it's working now!
[18:50] <seffyroff> right, so the name I want to change the maas domain to is another exisiting domain, which I can't delete as it has nodes using it.  So next step is to batch change those nodes back to the maas domain.  I can figure this out, maybe :D
[18:54] <seffyroff> separate issue (or maybe it's related?) i can pxe-boot a machine from the maas rack controller (I see it pulls dhcp from the rack controller's IP) but it doesn't then netboot, it just exits pxe
[19:04] <seffyroff> trying to pxe-boot it again whilst watching the logs
[19:06] <seffyroff> maasserver.region_controller.DNSReloadError: Failed to reload DNS; serial mismatch on domains lan, maas
[19:33] <seffyroff> ok, so i can't easily (via webui or cli) seem to remove dnsresource records
[20:10] <seffyroff> hm, in the GUI i see a bunch of resource records under the 'lan' domain, but when I do  'maas admin dnsresource-records read domain=lan' i get:
[20:10] <seffyroff> Success.
[20:10] <seffyroff> Machine-readable output follows:
[20:10] <seffyroff> []
[20:16] <seffyroff> ok, so deleting all devices seemed to be the only way to remove dnsresource records
[20:16] <seffyroff> so i've done that
[20:16] <seffyroff> they will be re-discovered :/
[20:19] <seffyroff> ok, successfully renamed the maas domain now
[20:19] <seffyroff> still seeing the DNS reload error though
[20:21] <seffyroff> 2018-03-29 20:20:24 maasserver.region_controller: [critical] Failed configuring DNS.
[20:21] <seffyroff> Traceback (most recent call last):
[20:21] <seffyroff>   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 393, in callback
[20:21] <seffyroff>     self._startRunCallbacks(result)
[20:21] <seffyroff>   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks
[20:21] <seffyroff>     self._runCallbacks()
[20:21] <seffyroff>   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
[20:21] <seffyroff>     current.result = callback(current.result, *args, **kw)
[20:21] <seffyroff>   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1184, in gotResult
[20:21] <seffyroff>     _inlineCallbacks(r, g, deferred)
[20:21] <seffyroff> --- <exception caught here> ---
[20:21] <seffyroff>   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1128, in _inlineCallbacks
[20:21] <seffyroff>     result = g.send(result)
[20:21] <seffyroff>   File "/usr/lib/python3/dist-packages/maasserver/region_controller.py", line 175, in _checkSerial
[20:21] <seffyroff>     "on domains %s" % ', '.join(not_matching_domains))
[20:21] <seffyroff> maasserver.region_controller.DNSReloadError: Failed to reload DNS; serial mismatch on domains lan
[20:21] <seffyroff> eek, sorry for the spam
[20:24] <seffyroff> here's a link to the log entry: http://termbin.com/znbl
[20:33] <seffyroff> my pxe-boot issue seems to have gone away.  my new machine just successfully pxe-booted into enlistment
[20:33] <seffyroff> not sure what changed there :/
[20:52] <mup> Bug #1759944 opened: [2.4, UI] Changing the subnet's fabric/vlan over the UI has no effect <MAAS:Triaged> <https://launchpad.net/bugs/1759944>
[20:58] <mup> Bug #1759946 opened: [2.3+] Changing a subnet's fabric/vlan doesn't automatically update the interface model <MAAS:New> <MAAS 2.3:New> <https://launchpad.net/bugs/1759946>
[21:03] <seffyroff> i guess my next move, which is my default move with anything DNS related is 'wait an hour' and see if it corrects itself?
[21:10] <roaksoax> seffyroff: that's strange, what you are reporting
[21:10] <roaksoax> seffyroff: that said
[21:10] <roaksoax> seffyroff: if machines atomatically dhcp from MAAS they will have a dns record created to the, which you cannot remove
[21:11] <roaksoax> seffyroff: iirc, same when you deploy a machine
[21:11] <roaksoax> seffyroff: so the stuff that maas does automatically cannot be changed
[21:14] <seffyroff> well, that error spams every 30 seconds or so, and has been doing so all day, so prior to any machine deployment, and has continued even when I deleted all nodes
[21:15] <seffyroff> there is an upstream dns server on the lan, but i don't seen anything in its logs related to local dns lookups
[21:15] <seffyroff> my bind knowledge is fairly limited so not sure how to proceed.  there's a set-serial command which might help, but it's unclear to me what to set it to
[21:16] <seffyroff> i can see in the /etc/bind/maas/* files refrences to serials in the zone files
[21:17] <seffyroff> so just pick an increment higher??
[21:17] <roaksoax> seffyroff: i would reocmmend you file a bug and provide step by step instructions on how to reproduce it, as I just tried, and was unable to
[21:18] <seffyroff> ok, however I have done a bunch of stuff before reaching this point.  I'm tempted to tear down and reinstall maas first.
[21:19] <seffyroff> which is non-trivial as the rackd is now providing dhcp to my lan
[21:19] <seffyroff> although not super difficult
[21:19] <seffyroff> i'll do that first.
[21:24] <roaksoax> seffyroff: sounds good
[23:54] <dsop_> Hi all. Looking for assistance with curtin. Want to have different config files for different machines in maas; would I 'pin' them to tags? Or would I 'pin' them to domains?
[23:54] <dsop_> thanks in advance. also if there's a better place to ask this (or to find previous questions) please lmk


[09:33] <Kilos> hi Neo31
[09:35] <Neo31> hello Kilos
[09:35] <Neo31> i'm back
[09:35] <Neo31> we were busy during the weekend
[09:35] <Kilos> wb Neo31
[09:35] <Neo31> rms was in tunisia in another city
[09:35] <Neo31> :)
[09:36] <Kilos> thats nice
[09:36] <Neo31> did i miss somthing here?
[09:36] <Kilos> hi Brainiarc7  welcome
[09:36] <Kilos> not much, just new guys joining
[09:37] <Kilos> im busy working on a site for us Neo31
[09:38] <Brainiarc7> Thanks Kilos
[09:38] <Kilos> Brainiarc7  are you an ubuntu users or one of the serious linux users
[09:39] <Kilos> like stickyboy
[09:39] <Neo31> cook Kilos
[09:39] <Neo31> hope that is in drupal
[09:39] <Kilos> lol no bzr and nikola
[09:40] <Kilos> and superfly  is teaching me patiently all the way
[09:40] <stickyboy> Kilos: I think you know the anser. ;)
[09:40] <Neo31> nikola?
[09:40] <Kilos> hahah
[09:40] <stickyboy> Kilos: He's a sysadmin and hacks all teh things!!1one
[09:40] <superfly> and Kilos is teaching me patience
[09:41] <Neo31> lol superfly
[09:41] <Neo31> that's good
[09:42] <Neo31> just in case u wanna change ur mind and build it in drupal i'm here to help guys :)
[09:42] <Kilos> nono man
[09:42] <Kilos> no place for anything else in my nut
[09:43] <Kilos> neo
[09:43] <Kilos> http://getnikola.com/handbook.html
[09:45] <Brainiarc7> I run Arch primarily
[09:45] <Brainiarc7> On Ubuntu, its' run as a server...
[09:45] <Brainiarc7> Its' been a while since I ran it as a desktop
[09:45] <Kilos> no matter Brainiarc7
[09:46] <Kilos> even stickyboy  is good to have around
[09:46]  * Kilos ducks
[09:48] <stickyboy> :D
[09:49] <Kilos> Neo31  find fault with this site
[09:50] <Kilos> https://ubuntu-za.org/
[09:51] <Kilos> the africa site will be very similar
[09:52] <Kilos> but im still learning to walk so you will have to be patient
[09:52] <Kilos> the council seemed to like the idea though
[09:54] <Neo31> :)
[09:54] <Neo31> good
[09:54] <Neo31> no new locos in here Kilos ?
[09:55] <Neo31> only the 6 we've got ?
[09:55] <Kilos> ehtiopia is Neo31
[09:55] <Neo31> cool :)
[09:55] <Neo31> have you updated the wiki ?
[09:55] <Kilos> they are happy to hear someone is reviving things
[09:55] <Neo31> perfect
[09:55] <Neo31> :)
[09:55] <Neo31> so now we are 7 teams total
[09:55] <Neo31> :)
[09:56] <Kilos> so we will need to help them form a loco
[09:56] <Kilos> the contact guy is tsela and stickyboy  knows him
[09:56] <Neo31> yeah of course
[09:56] <Kilos> tsega
[09:56] <Neo31> that's good news
[09:57] <Kilos> he says he will get the whole east coast here, its just time seems tobe a big problem all over
[09:57] <Neo31> yep
[09:57] <Kilos> oh and
[09:57] <Neo31> time!
[09:57] <Neo31> :p
[09:57] <Kilos> there is a guy from namibia too
[09:58] <Kilos> the old loco has kinda died or seems a bit elitist so the new contact will get guys together too
[09:59] <Kilos> oh Neo31  i wanted to ask you about that wiki page too
[09:59] <Kilos> hmm...
[09:59] <Brainiarc7> I'm still tempted to run Ubuntu as a desktop on my gaming rig.
[10:00] <Kilos> it only shows existing locos and i didnt know how to put in just a new contact
[10:00] <Brainiarc7> When it comes to Linux hardware support, Ubuntu as a distribution is almost unparalleled.
[10:00] <Kilos> Brainiarc7  superfly  and i use kubuntu
[10:00] <Brainiarc7> It could do NVIDIA Optimus and SLI flawlessly
[10:00] <Kilos> but im still a beginner
[10:01] <Brainiarc7> On Arch, still possible but very hackish
[10:01] <Brainiarc7> Also, almost undocumented.
[10:01] <Kilos> oh Neo31  i added superfly  as the second contact person as he is south africas second contact person now
[10:02] <Kilos> maia is too busy to be at all active much
[10:02] <Brainiarc7> I can also see kenju254 peeking from his ninja hideout
[10:02] <Kilos> yeah kenju254  is here too
[10:03] <Brainiarc7> And my GPU just locked up...Lolz. May have to reboot shortly
[10:03] <Kilos> eish
[10:03] <Kilos> you need directions to get ubuntu?
[10:03] <Kilos> hehe
[10:05] <Kilos> Neo31  you need to add another line in the wiki page because im out in the cold
[10:07] <Brainiarc7> lolzzz
[10:11] <Neo31> cool Kilos i will check the wiki tonight before i leave work and make the correct changes
[10:11] <Kilos> all you clever guys can get us a greeter bot for when im crashed
[10:11] <Kilos> ty Neo31
[10:20] <Kilos> welcome to ubuntu-africa ThatGraemeGuy
[10:28] <ThatGraemeGuy> ta :)
[10:42] <Neo31> Kilos, trust me we don't need a bot here. we have u with human intelligence ;) no bot can beat that ^_^
[10:43] <Neo31> welcome here ThatGraemeGuy :)
[10:43] <Kilos> lol i sleep man
[10:45] <ThatGraemeGuy> thanks :)
[11:19] <stickyboy> Kilos: LOL old Namibia LoCo is elitist. :P
[11:23] <Kilos> lol
[11:24] <stickyboy> Kilos: Actually tsega emailed me yesterday.
[11:24] <stickyboy> Said he'd be around more.
[11:24] <Kilos> great
[11:24] <stickyboy> I told him to start a group in Ethiopia and I would fly up for the meeting. ;)
[11:24] <Kilos> cool
[11:24] <stickyboy> Slightly joking, slightly serious. Flights are $178 round trip, hahaha.
[11:24] <Kilos> ow
[12:03] <saoungoumi_> .
[12:17] <Kilos> hi san
[12:17] <Kilos> saoungoumi_  as well
[15:44] <arnaudmez> hello
[15:44] <arnaudmez> in a need of a flyer model in svg format.
[15:45] <Kilos> hi arnaudmez  welcome to ubuntu-africa
[15:45] <arnaudmez> preparing an event here arround ubunut
[15:45] <arnaudmez> ubuntu
[15:45] <Kilos> hi magellanic
[15:45] <magellanic> heya
[15:50] <Kilos> arnaudmez  just hang here these guys are from all over
[15:50] <Kilos> from tunisia down to capetown
[15:50] <arnaudmez> Cool
[15:51] <Kilos> and quite a few official ubuntu members
[17:48] <Neo31> arnaudmez has quit the chan?
[17:48] <Neo31> oups I'm a little late
[17:49] <Neo31> we have few free and open source posters on ubuntu-tn wiki and mailing list archive
[17:49] <Neo31> those might be helpful sometimes
[17:49] <Kilos> hold Neo31
[17:49] <Neo31> arnaudmez left anyway
[17:49] <Kilos> he gave his email addy in za channel
[17:50] <Neo31> cool
[17:50] <Kilos> he is my congo brazzaville contact
[17:50] <Neo31> https://wiki.ubuntu.com/TunisianTeam/Artwork
[17:51] <Neo31> some of the stuff we've made
[17:51] <Neo31> he can edit and use our sources
[17:52] <Kilos> just mail him that link please. say Kilos asked you to.
[17:53] <Kilos> been chatting on and off for about 1 year now
[17:53] <Neo31> telling that he got the originals from ubuntu-tn would be cool from him other than that he can do whatever we want with those sources
[17:53] <Neo31> hh cool
[17:53] <Neo31> get me his mail
[17:53] <Neo31> i will send him a link
[17:53] <Kilos> sec
[17:53] <Neo31> if he needs other resources we can help with we would not hesitate :)
[17:53] <Kilos><EMAIL_ADDRESS>[17:54] <Neo31> that's why we made ubuntu-africa right ? :)
[17:54] <Kilos> yip
[17:54] <Neo31> try doing this next time Kilos
[17:54] <Kilos> you got it
[17:54] <Neo31> arnaudmez at gmail dot com
[17:54] <Neo31> we have a log bot here now :)
[17:54] <Neo31> everything will be on the web
[17:54] <Kilos> oh
[17:55] <Kilos> will do but so easy to copy paste
[17:55] <Kilos> hehe
[17:55] <Neo31> anyway clever bots would get around that anyway :p
[17:55] <Neo31> yep yep right hh
[17:55] <Neo31> pm is also a good option :)
[17:55] <Neo31> thx anyway
[17:55] <Neo31> sending him an email in a sec
[17:55] <Kilos> ya but he isnt bothered as long as he can get help
[17:56] <Kilos> and always thankful
[17:56] <Kilos> ty Neo31
[17:56] <Neo31> hh good
[17:57] <Kilos> he actually wants to start giving linux basic classes there
[18:02] <Neo31> cool
[18:03] <Kilos> slowly but surely we are rekindling things
[18:03] <Neo31> yep
[18:03] <Neo31> persistence can do anything
[18:03] <Kilos> lol
[18:15] <Neo31> cool now we are 8 locos alive :)
[18:15]  * Neo31 updated the wiki :)
[18:16] <Kilos> well done
[18:16] <Neo31> just document and code improvements no new changes
[18:17] <Kilos> im busy working on our site but learning at the same time about what to do, but in a week or 2 well have it going
[18:17] <Neo31> cool Kilos
[18:17] <Neo31> :)
[18:17] <Neo31> good luck
[18:17] <Kilos> ty
[18:18] <Neo31> gotta run in few minutes
[18:18] <Neo31> it's getting too late
[18:18] <Neo31> c u
[18:18] <Kilos> go safe
[18:18] <Kilos> cheers


[06:51] <ppisati> moin
[10:03]  * ppisati -> out for an early lunch
[11:31] <ogra_> ppisati, could you drop by in #pandaboard if you are back
[11:52] <ppisati> ogra_: i',
[12:28] <rtg> wow, 15777 patches in this merge window so far. 3.4 -> 3.5 was only 10957
[12:29] <amitk> rtg: where is most of it coming from?
[12:29] <pedrinho> rtg: hehe thats a lot
[12:29] <rtg> amitk, dunno, haven't charted that.
[12:30] <pedrinho> rtg: can you tell if those patchs are mostly bug fix or new features?
[12:30]  * amitk suspects lots of consolidation work
[12:30] <rtg> pedrinho, yeah, right.
[12:35] <pedrinho> rtg: does ubuntu guys contrib for kernel development?
[12:49] <rtg> pedrinho, some, e.g.,
[12:49] <rtg> rtg@salmon:~/linux/linux$ git log v3.5..HEAD|egrep ^Author|egrep "canonical|ubuntu"|wc -l
[12:49] <rtg> 152
[12:54] <rtg> ogasawara, thought you were gonna upload yesterday. did you run into some snags ?
[12:54] <ogasawara> rtg: nope, was going to upload today
[12:54] <rtg> ok
[12:55] <ogasawara> rtg: figured I'd try and stretch it out another day in the event any last minute patches came in
[12:55] <rtg> I'm sure I can find something :)
[12:59] <rtg> apw, why does pre-proposed hate me ? I'm getting an  email every morning that says the Lucid source package upload has been rejected because it doesn't think my email address is valid.
[13:01] <apw> what is your email address
[13:01] <apw> (not here :))
[13:02] <rtg> apw, the usual. I assume its getting it from the changelog entry .
[13:02] <apw> forward me the email would you
[13:03] <diwic> smart bot, sending email complaining about the email address being broken. Like pressing F1 in case of keyboard error?
[13:04] <apw> heh yeah ... i assume its not using the email addy in the package, but of the "uploader" in this case
[13:04] <rtg> apw, I think I've already irrevocably deleted it. how about restarting that job for Lucid ? I'm sure it'll send me another email.
[13:04] <apw> was it to you or kernel-ppa
[13:05] <rtg> diwic, I think it is sending the email to<EMAIL_ADDRESS>which I'm fetching....
[13:05] <rtg> apw, ^^
[13:06] <apw> rtg, yep i have it
[13:09] <rtg> kees, 3.6 vanilla now has all of the right YAMA bits, right ? I'm dropping 'UBUNTU: SAUCE: Yama: add link restrictions' and 'UBUNTU: SAUCE: security: unconditionally chain to Yama LSM' in ubuntu-r because of conflicts.
[13:09] <apw> rtg, they sorted the chaining?  i am supprised
[13:10] <rtg> apw, kees: I meant 3.7
[13:11] <rtg> apw, isn't NF_NAT_IPV6 an oxymoron ?
[13:12] <rtg> apw, here it is: CONFIG_SECURITY_YAMA_STACKED
[13:29] <rtg> apw, ogasawara: http://comments.gmane.org/gmane.linux.kernel/1368725 is going to affect our policy on EXPERIMENTAL
[13:32] <apw> rtg, hmmm, well we also look for (experimental) in the descriptio
[13:32] <apw> rtg, so as long as that is maintained at least we'll be ok
[13:32] <rtg> I suspect that will fall out of favor as well.
[13:33] <apw> rtg perhaps we need to just track when something arrives, so NEW == experimental :)
[13:33] <rtg> apw, I'm just turning on everything that is =m and looking more closely at options that are =y
[13:34] <apw> yeah they will all show as NEW so get consideration at UDS, so that is fine
[13:34] <apw> thanks for the head up though as it will break the processing
[13:35] <rtg> apw, I love being the harbinger of good news :)
[13:36] <apw> rtg, i am somewhat flummoxed by this lucid thing -- your sig looks just fine, and almost identical to luis' on oneiric which worked
[13:37] <rtg> apw, which is why I punted.
[13:37] <rtg> apw, do you suppose its a LP thing ?
[13:37] <apw> its feeling like it indeed.  i will see if i can find the actual files it uploaded
[13:40] <apw> rtg, no the upload itself was successful so they are gone; bugger
[13:40] <apw> will ask if they still exist
[13:54] <ppisati> ogasawara: i'm researching a problem we have with usb and omap3 (beagle) so IF they ever fixed it, i'll probably need another upload and i don't think i'll get that by today
[13:55] <ogasawara> ppisati: ack, we can still upload after kernel freeze, it just needs to adhere to our SRU standards and policy which I suspect this would qualify
[13:56] <ppisati> ogasawara: yep, just wanted to give an heads up
[13:56] <ogasawara> ppisati: thanks
[14:11] <apw> rtg, found it, its actually your fault :)  its _precise_ thats broken, and its your signature line, you have <>'s round it
[14:11] <rtg> apw, 3.2 ?
[14:11] <rtg> oh, drat
[14:12] <apw> not quite sure what went wrong to make that happen
[14:13] <rtg> apw, ok, force pushed the fix
[14:13] <rtg> apw, I had some issues with some ENV variables, but I fixed them weeks ago
[14:14] <apw> rtg, well at least its resolved; and the error makes sense now as its saying there is crap then more <>'s within what claims to be an email addy
[14:15] <rtg> apw, so I wonder why the email I was getting was about 3.0 ? did I just mis-read it ?
[14:15] <apw> subject: [PPA kernel-ppa-pre-proposed] linux_3.2.0-32.52~pre201210030400_source.changes rejected
[14:15] <rtg> apw, indeed, I just mis-read it
[14:15] <apw> you said 3.0 and even with that in my face i saw 3.0
[14:16] <apw> numbers are hard...
[14:20] <rtg> Auto packing the repository for optimum performance always happens at the most inopportune moment.
[14:49]  * ogasawara back in 20
[15:04] <jsalisbury> diwic, your patch fixes bug 1059523 :-)
[15:04] <ubot2> Launchpad bug 1059523 in linux "[Acer Aspire One 722] Broken support of Intel HDA in 3.5.0-16 kernel" [Medium,Confirmed] https://launchpad.net/bugs/1059523
[15:04] <diwic> jsalisbury, good, can we apply it? :-)
[15:05] <jsalisbury> diwic, Probably.  It applied cleanly.  I can send it to the mailing list
[15:07] <jsalisbury> rtg, do you want a request on the kernel team mailing list for this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1059523/comments/8
[15:08] <ubot2> Launchpad bug 1059523 in linux "[Acer Aspire One 722] Broken support of Intel HDA in 3.5.0-16 kernel" [Medium,Confirmed]
[15:08] <rtg> jsalisbury, yes
[15:08] <jsalisbury> rtg, ok.  will do
[15:08] <diwic> jsalisbury, thanks
[15:08] <jsalisbury> diwic, np.  thank you ;-)
[15:38] <hggdh> ogra_: does this ring any bells? http://pastebin.ubuntu.com/1258212/
[15:39] <ogra_> hggdh, looks like the squashfs is corrupt or the module is messed up
[15:39] <hggdh> ogra_: do you want a bug on it?
[15:39] <ogra_> yeah, files it against linux-ti-omap4 for now
[15:40] <hggdh> ack
[15:40] <ogra_> oh
[15:40] <ogra_> its not the squashfs being corrupt
[15:41] <ogra_> its loop device support missing
[15:41] <ogra_> ppisati, ^^^
[15:41] <ogra_> see the paste above
[15:44] <hggdh> ogra_, ppisati: bug 1061036
[15:44] <ubot2> Launchpad bug 1061036 in linux-ti-omap4 "20121003 server image fails to install with s squasfs error" [Undecided,New] https://launchpad.net/bugs/1061036
[15:46]  * rtg is off to perform server surgery...
[15:48] <ppisati> ogra_: i installed the server image yesterday and it was ok
[15:48] <ogra_> strange
[15:48] <ogra_> thats todays image though
[15:49] <ogra_> could we be out of sync wrt uploads ?
[15:50] <ppisati> [flag@newluxor ~]$ ls -la Downloads/quantal-server-armhf+omap4.img
[15:50] <ppisati> -rw-rw-r-- 1 flag flag 757923840 Oct  2 09:21 Downloads/quantal-server-armhf+omap4.img
[15:50] <ppisati> [flag@newluxor ~]$ md5sum Downloads/quantal-server-armhf+omap4.img
[15:50] <ppisati> this one is good
[15:50] <ogra_> hmm, no
[15:50] <ppisati> 25931219ba6a86e3c17ba3c2003665ff  Downloads/quantal-server-armhf+omap4.img
[15:50] <ogra_> yeah, and tehre were no kernel uploads since the 29th
[15:50] <ogra_> weird
[15:51] <ppisati> ogra_: i'm investigating the omap3 usb thing
[15:51] <ppisati> ogra_: can you try that?
[16:51] <hggdh> ogra_: just finished another install with server 20121003, and it worked
[16:52] <ogra_> cosmic rays !
[16:52] <hggdh> ogra_: I do not follow what happened...
[17:04] <hggdh> but I closed the bug calling on the cosmic rays
[18:01]  * rtg -> lunch
[18:44] <ppisati> hggdh: toss the sd cards, sometimes they mess up the image you dd on it, it has happened to me in the past
[18:45] <ppisati> hggdh: *sd card
[18:45]  * ppisati needs food... immediately...
[19:17] <hggdh> ppisati: will ask retoaded to do that when he gets to the lab, thanks
[19:19] <retoaded> hggdh, are we removing them permanently or replacing them with new cards?
[19:23] <hggdh> retoaded: putting in new ones
[19:24] <retoaded> ack
[19:35] <alexbligh> what is the safe way of passing system an array or arguments (as opposed to a space separated string) AND redirect stdout and stderr of the system call only to /dev/null?
[19:35] <alexbligh> oops, www
[19:58]  * ppisati heads to the couch
[20:26]  * rtg -> EOD
[21:35] <kees> rtg, apw: yup, for 3.6 you can drop 'UBUNTU: SAUCE: Yama: add link restrictions', and for 3.7 you can drop 'UBUNTU: SAUCE: security: unconditionally chain to Yama LSM' (but enable CONFIG_SECURITY_YAMA_STACKED)
[22:07] <apw> kees, ack
[22:07] <apw> ogasawara, ^^
[22:08] <ogasawara> kees, apw: ack, thanks


[02:01] <callmepk> good morning
[02:50] <KGB-2> atk debian/master Janitor * [open] merge request !2: Fix some issues reported by lintian * https://deb.li/3lkK7
[03:03] <duflu> Morning callmepk
[03:10] <callmepk> morning duflu
[06:39] <seb128> goood morning desktopers
[06:44] <duflu> Hi seb128
[06:44] <duflu> Happy Friday (?)
[06:46] <seb128> hey duflu, happy friday! how are you today?
[06:46] <duflu> OK. But hopefully more OK after a long sleep tomorrow
[06:47] <seb128> I'm looking forward sleeping some more hours as well tomorrow :-)
[07:25] <duflu> seb128, is Launchpad git down?
[07:26] <duflu> Hmm, nope. Just so slow it looks broken
[07:38] <RikMills> morning. has anyone tried a gui upgrade (no -d) from 19.10 -> 20.04 since they were turned on last night? at least in kubuntu, it still says upgrading to devel release
[07:49] <sameee> hello, i'm trying to get gphoto2 to get my dslr to stream a webcam virtual device
[07:49] <sameee> it's not working, something about a pipeline not being able to be constructed
[07:50] <sameee> i'm not really wanting to get into the oil business in this current market environment and I understand the reluctance of the computer to avoid doing so also but it would be good if gphoto2 worked.
[07:51] <seb128> duflu, I didn't ry it today
[07:52] <seb128> rikMills, I didn't, but that's a better question for #ubuntu-release
[07:52] <seb128> sameee, hey, try #ubuntu for user questions
[07:52] <sameee> thx seb128
[07:59] <duflu> seb128, I think the internet pipes are clogged
[07:59] <duflu> It's a busy time
[08:00] <jibel> lp git works fine here
[08:01] <RikMills> I have a feeling the server thing that syncs uploads to git runs a lot about this time?
[08:10] <jibel> no luck with automated smoke tests of images, kernel crash
[08:12] <oSoMoN> good morning desktoppers
[08:21] <duflu> Morning oSoMoN
[08:28] <seb128> lut oSoMoN, happy friday! how are you?
[08:44] <oSoMoN> hey duflu
[08:44] <oSoMoN> salut seb128, happy Friday!
[08:44] <oSoMoN> I'm good, and you?
[08:45] <oSoMoN> (aren't you off today?)
[08:54] <seb128> oSoMoN, I'm good, and no, I'm going to swap it and get some extra buffer days :)
[09:13] <oSoMoN> that's wise :)
[09:52] <oSoMoN> seb128, thanks for sponsoring adwaita-icon-theme
[09:53] <KGB-0> atk debian/master Samuel Thibault * [merge] merge request !2: Fix some issues reported by lintian * https://deb.li/3lkK7
[09:53] <seb128> oSoMoN, np!
[10:09] <duflu> Oh groovy desktop ISOs. Fun
[11:09] <jibel> groovy isos but they are failing smoke tests cf bug 1877538
[13:47] <jibel> paride, I reported bug 1877575, can you confirm it. It seems to affect focal only, I can boot groovy.
[13:51] <paride> jibel, done, and I added a hopefully useful bit of information: the exact image serial when the problem began
[14:25] <kenvandine> My xenial VM boots so fast
[15:13] <jibel> paride, great, thx
[17:33] <kenvandine> seb128: any interesting bugs fixed in gtk 3.24.20?  Wondering if I should bump the version in the gnome-3-34-1804 platform
[17:34] <kenvandine> it currently has 3.24.18
[18:33] <seb128> kenvandine, not really no, some small fixes, https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS