[03:38] <linuxuz3r> hey i just wanna say im a noob at programming arm oses
[05:07] <linuxuz3r> how is snappy on pi 2 with gnome or xfce
[05:07] <linuxuz3r> is it fast?
[07:06] <fgimenez> good morning
[07:33] <dholbach> good morning
[09:04] <JamesTait> Good morning all; happy Monday, and happy Lion Day! 😃
[13:21] <ogra_> whee ! my RPi2 image made it on heise.de
[13:24] <mterry> :)
[13:34] <elopio> good morning.
[13:34] <kyrofa> ogra_, I started playing with that image on Friday afternoon
[13:34] <ogra_> cool
[13:35] <ogra_> any issues yet ?
[13:35] <kyrofa> ogra_, I extracted the overlay.tgz to get the devicetree for i2c, but in your email you mentioned it would require modifications to config.txt. I glanced there and it looked like i2c was enabled. I wasn't sure what other modifications I needed to make?
[13:36] <ogra_> kyrofa, no, i2c is already enabled you dont need to do anynnthing for it
[13:36] <ogra_> the overlays are for additional HW like "hats"
[13:36] <kyrofa> ogra_, like the PiGlow?
[13:36] <ogra_> to just use the i2c bug you can use it unmodified
[13:37] <ogra_> elopio, had the piglow working with that image, yes
[13:37] <ogra_> and afaik without any extra modification (except for having to build the piglow-tools for it)
[13:38] <kyrofa> ogra_, perfect, thank you!
[13:50] <kyrofa> elopio, ^^ did you build a snap with python-smbus contained within it, etc.?
[13:51] <elopio> kyrofa: I compiled https://github.com/schoentoon/piglow
[13:51] <elopio> I'm about to get my binary in a demo snap. Still figuring out some details here...
[13:52] <kyrofa> elopio, ah, I hadn't seen that one! Thank you :
[13:52] <kyrofa> :)
[13:52]  * ogra_ wishes he had an orangebox ... then i would have made i2c work from the start
[13:54] <elopio> ogra_: http://shop.pimoroni.com/products/piglow expense it :)
[13:54] <kyrofa> ogra_, if anyone needs one it's you, haha
[13:54] <ogra_> kyrofa, tell that to niemeyer :P
[13:55] <ogra_> (afaik ricardo asked for one for me and was denied)
[13:56] <kyrofa> ogra_, huh, well that sucks
[14:18] <longsleep> ogra_: heise.de missed to post a link to the download ..
[14:18] <ogra_> true
[14:18] <ogra_> but i guess people that want it will find their way around
[14:20] <longsleep> yeah - i hope this gives some more coverage of snappy in Germany.
[14:21] <svij> there's a talk about snappy at FrOSCon next week
[14:28]  * ogra_ sighs ... so much mail spam when publlishing an app in the store
[14:28] <longsleep> reminding me / still nobody passed my new OEM snap version :(
[14:28] <ogra_> beuno, cant we cut that down a bit ? 4 mails for one upload feels really to much
[14:29] <ogra_> longsleep, but sergio said he would ... he probably didnt get to it yet
[14:29] <longsleep> ogra_: right - though its almost 2 weeks now - should this take so long?
[14:29] <ogra_> well, it needs manual review by a reviewer
[14:30] <longsleep> yes - well at least i can chat with you guys here :)
[14:31] <longsleep> And the store seems to have gotten an update which fixed one of the problems i did see
[14:34] <ogra_> yeah, the UI changed
[15:07] <ogra_> longsleep, oh, note that there is a sprint this week, many of us wont be available as we usually are ... that might delay it
[15:16] <longsleep> yay it just got reviewed!!!
[15:16] <ogra_> yep, we just have our team meeting ;)
[15:16] <longsleep> great thanks!
[15:16]  * ogra_ could use the pointy stick ;)
[15:24] <sergiusens> good morning
[15:25] <longsleep> ogra_: yeah now one can at least grab the oem snap from the store when creating an image. Now is there new about getting the rest from the store as well?
[15:25] <longsleep> sergiusens: Thanks for reviewing the ODROID-C1 snap !
[15:26] <ogra_> longsleep, once we have the gadget snaps that will work, yes
[15:26] <ogra_> oem is going away, it will become kernel and gadget
[15:26] <longsleep> ogra_: and the gadget snap is also the one which could have dependencies right?
[15:26] <ogra_> yeah
[15:26] <longsleep> ok great - please let me know when something is available :)
[15:27] <sergiusens> longsleep: some people are getting together this week to discuss exactly how to roll that out
[15:28] <longsleep> sergiusens: cool then i will pay attention to IRC
[15:30] <ogra_> longsleep, well, they get together in person ... usually IRC attandence is very low if that happens :)
[15:30] <longsleep> ah
[15:31] <longsleep> ogra_: do you have the rpi2 oem snap in the store as well?
[15:31] <ogra_> nope, i wanted to get it proper first and i want lool to remove his
[15:32]  * ogra_ also doesnt have a branch set up for it yet
[15:32] <longsleep> ah - well at least i can say that "--oem odroidc.longsleep" works just fine with ubuntu-device-flash which is essentially all i wanted to test
[15:34] <ogra_> yeah
[15:34] <ogra_> i dont find it that urgent as long as you still need the separate device part
[15:36] <longsleep> right


[00:42] <guiverc> https://fridge.ubuntu.com/2023/05/13/extended-security-maintenance-for-ubuntu-18-04-bionic-beaver-begins-31-may-2023/   (looked good I felt.. so self reviewed.. tags the only bits I question  (but don't want release, nor eol/eoss yet either)
[00:49] <guiverc> posted it to twitter, telegram, reddit
[00:57] <guiverc> & now 18.04 eoss warning posted to fb too
[00:59] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Extended Security Maintenance for Ubuntu 18.04 (Bionic Beaver) begins 31 May 2023 @ https://fridge.ubuntu.com/2023/05/13/extended-security-maintenance-for-ubuntu-18-04-bionic-beaver-begins-31-may-2023/
[03:40] -SwissBot:#ubuntu-news- ::Fridge:: Extended Security Maintenance for Ubuntu 18.04 (Bionic Beaver) begins 31 May 2023 @ https://fridge.ubuntu.com/2023/05/13/extended-security-maintenance-for-ubuntu-18-04-bionic-beaver-begins-31-may-2023/ (by guiverc)
[10:05] <krytarik> guiverc: Yeah, 18.04 post looks alright.
[10:07] <guiverc> thanks krytarik
[10:07] <krytarik> Thank you!
[10:07] <guiverc> :)
[10:08] <guiverc> & thanks for (post-)reviewing it
[21:02] -SwissBot:#ubuntu-news- ::Planet:: Sergio Durigan Junior: Ubuntu debuginfod and source code indexing @ https://blog.sergiodj.net/posts/ubuntu-debuginfod-source-code-indexing/


[03:37] <locodir-user987> люди, привет, зашёл сюда через веб, через нормальный клиент можно сюда попасть? скажите сервер
[03:38] <SergioMeneses> locodir-user987, can you write in English? please
[03:39] <locodir-user987> sorry, i'l try :)
[03:39] <SergioMeneses> locodir-user987, dont worry
[03:39] <SergioMeneses> how can I help you?
[03:40] <locodir-user987> how i can connect to this server with irc-client, not web ? tell me server please
[03:41] <locodir-user987> or it's impossible ?
[03:42] <SergioMeneses> locodir-user987, that is a technical question, this server is freenode and if you need help about technical things you can visit the channel #ubuntu
[03:42] <SergioMeneses> locodir-user987, what client are you using?
[03:42] <locodir-user987> pidgin
[03:43] <SergioMeneses> you add an irc account and select freenode server... that's all
[03:44] <SergioMeneses> later you have to indicate the channel, it will open a new window where you can do that
[03:48] <locodir-user987> what server i must specify in TEXTBOX "server" in my account settings in pidgin ? there are no lists to select
[03:48] <locodir-user987> just tell me string to type in textbox
[03:49] <SergioMeneses> locodir-user987, I am not using pidgin right now maybe you can ask in #ubuntu channel
[03:50] <SergioMeneses> I dont remember the settings about pidgin
[03:51] <locodir-user987> ok,thanks


[04:48] <jam> morning all
[08:11] <Chipaca> moin moin moin
[09:09] <jam> Chipaca,  o/
[09:15] <Chipaca> jam: how's things?
[09:16] <jam> Chipaca, going pretty well. Have a PR on Juju up, and a couple other code reviews to get through.
[09:17] <Chipaca> jam: what's the juju pr about?
[09:17] <jam> Chipaca, fixing an issue with 'juju debug-code' that facu ran into last week
[09:18] <jam> namely, if Juju fires an event that the charm doesn't implement a hook for, Juju would go into error
[09:21] <Chipaca> ah, that one :)
[09:22] <Chipaca> jam: I didn't realise there was a juju-side fix for that, i thought it was on us
[09:22] <jam> Chipaca, no, the issue was that the handler for 'debug-code' was looking for the script to run, and 'executing it anyway' even though it didn't exist
[09:23] <jam> so the open question was whether we should fall back to a bash debugger.
[09:23] <jam> I think you and achilleas and facu all felt like you'd rather not be interrupted
[09:23] <jam> so I went with that route
[09:26] <Chipaca> :+1:
[09:26] <Chipaca> heh, this hexchat is missing my subs tweaks
[09:27] <jam> Chipaca++
[09:28] <jam> hm, maybe that's only in canonical IRC
[10:37] <jam> Chipaca, you both hung for me, I'll rejoind
[11:14] <facubatista> Muy buenos días a todos!
[11:14] <jam> morning facubatista
[11:15] <facubatista> hola jam :)
[12:36] <facubatista> Chipaca, #221 ... can we settle for changing the 'will' for a 'should
[12:36] <mup_> PR #221: ops/main.py: support dispatch <Created by chipaca> <https://github.com/canonical/operator/pull/221>
[12:37] <facubatista> ' in line 181?
[12:39] <Chipaca> facubatista: sure
[12:40] <Chipaca> i'll do that as soon as i have a working dev environment again :-(
[12:40] <Chipaca> right now not even vi works
[12:40] <Chipaca> how hexchat is still up is a mystery :-)
[12:40] <facubatista> Chipaca, what happened?? wild weekend?
[12:41] <Chipaca> facubatista: my new dev machine had to go back to service (remember the 'sticking at 800MHz' thing?), so i'm on my old one, and it was on 16.0 so i'm slowly moving to 20.04 but it has less memory than it should to do that and be productive
[12:42] <Chipaca> (i moved off the old machine when the motherboard stopped liking having more than 4GB RAM)
[12:42] <facubatista> probably too late now, but shouldn't the move from 16 to 20 be *not* slowly? like, installing from scratch?
[12:42] <Chipaca> and lose all my everything? heck no
[12:42] <Chipaca> also i'd miss out on messages like
[12:42] <Chipaca>   assert result == expected, "got: %r expected: %r" (result, expected)
[12:43] <Chipaca> whoops
[12:43] <Chipaca> /usr/lib/python3/dist-packages/urwid/tests/test_canvas.py:232: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
[12:43] <Chipaca>   assert result == expected, "got: %r expected: %r" (result, expected)
[12:43] <Chipaca> ^ that
[12:45] <Chipaca> facubatista: but more seriously, I _could_ do a fresh install and then a full backup, but that would take more of my time than just upgrading
[12:45] <Chipaca> s/full backup/full backup restore/
[12:46] <Chipaca> i'll probably do that at some point to drop unity and switch to lubuntu or lumina
[12:47] <Chipaca> huh, that's strange
[12:48] <Chipaca> just got a call from the local hospital thing, they're moving back to pre-covid stuff
[12:48] <facubatista> I got an appointment of May 17 moved to next month, "undetermined when"
[12:51] <Chipaca> facubatista: the week (or 2?) before lockdown started the hospital called me to say they were postponing any non-essential surgery 'indefinitely', and now they're scheduling them back
[12:51] <Chipaca> so it's like they are no longer in a panic
[12:51] <Chipaca> makes sense to me; they're also closing down the big emergency hospital
[12:52] <Chipaca> of course now the knee that's acting up is the other one, so i shouldn't just go in for surgery before a consultant looks at things again...
[12:52] <MarkMaglana> o/
[12:53] <facubatista> hello MarkMaglana
[12:53] <MarkMaglana> hello facubatista!
[12:55] <MarkMaglana> joining the fun in this channel with my fellow FE-in-rotation vgrevtsev :-)
[12:55] <vgrevtsev> \o
[12:56] <Chipaca> MarkMaglana, vgrevtsev: welcome!
[12:57] <facubatista> Chipaca, looks the curve is controlled, kind of https://aatishb.com/covidtrends/?location=United+Kingdom
[12:57] <facubatista> hello vgrevtsev
[12:58] <MarkMaglana> thanks, Chipaca! excited to help with the charming effort on top of the operator framework. :-)
[12:59] <Chipaca> things you don't want to read during an upgrade:  cryptsetup: ERROR: Couldn't resolve device
[13:02] <facubatista> Chipaca, are we doing the "docstrings styles" meeting or you prefer to postpone it for when you stop dancing around missing /dev nodes?
[13:03] <Chipaca> facubatista: trying to get there
[13:03] <Chipaca> firefox just crashed so there's that
[13:04] <Chipaca> give me 5
[13:12] <Chipaca> jam, facubatista, https://r.chipaca.com/docs/_build/html/123/ops.html#ops.testing.Harness.add_relation
[13:20] <Chipaca> https://sphinxcontrib-napoleon.readthedocs.io/en/latest/
[13:20] <jam> Chipaca, I think it is infectious
[13:55] <Chipaca> facubatista, jam, "more papist than the pope"
[14:01] <Chipaca> facubatista: WRT the import PR
[14:01] <Chipaca> facubatista: 1 sec phone
[14:01] <Chipaca> back
[14:01] <Chipaca> facubatista: WRT the import PR
[14:01] <jam> Chipaca, facubatista : https://github.com/canonical/operator/pull/252/files
[14:01] <mup_> PR #252: ops/testing.py: document Harness in Google style <Created by jameinel> <https://github.com/canonical/operator/pull/252>
[14:01] <Chipaca> facubatista: we were talking with jam earlier about it
[14:01] <jam> type annotations and google doc style for Harness
[14:02] <mup_> PR operator#252 opened: ops/testing.py: document Harness in Google style <Created by jameinel> <https://github.com/canonical/operator/pull/252>
[14:02] <Chipaca> facubatista: and were thinking it'd be nice to change things so that users of the fmk just needed to do
[14:02] <Chipaca> facubatista: from ops import CharmBase
[14:02] <Chipaca> facubatista: etc
[14:02] <Chipaca> facubatista: but only for the things that we thought were 'mainstream' public
[14:03] <facubatista> Chipaca, yes, we discussed it too
[14:03] <facubatista> Chipaca, we can do that! it's not a 5' branch, we need to discuss what we will be exposing, right? so my PR will be able to unblock people with current import errors
[14:05] <Chipaca> facubatista: right
[14:06] <Chipaca> facubatista: what I didn't want to do was have your branch close off that possibility :) but i don't think it does
[14:06] <facubatista> right
[14:06] <Chipaca> k
[14:07] <Chipaca> facubatista: wrt testing, why pull it in every time? is that needed to fix the issue at hand?
[14:07] <Chipaca> facubatista: i ask because this would be pulling it in even for in-production charms, which seems strangfe
[14:07] <Chipaca> strange also
[14:10] <facubatista> Chipaca, I included it because we may be importing testing to use the Harness even not in pure unittests.
[14:10] <facubatista> But I can totally remove it
[14:11] <facubatista> from the outside it will not change anything
[14:11] <facubatista> bah, less import time
[14:11] <mup_> PR operator#253 opened: Test harness no backend <Created by jameinel> <https://github.com/canonical/operator/pull/253>
[14:11] <jam> facubatista, Chipaca : https://github.com/canonical/operator/pull/253/files fixes for #241 without the backend call tracing
[14:11] <mup_> PR #253: Test harness no backend <Created by jameinel> <https://github.com/canonical/operator/pull/253>
[14:11] <mup_> Issue #241: _TestingModelBackend incorrectly raises KeyError on missing relation <Created by gnuoy> <https://github.com/canonical/operator/issues/241>
[14:12]  * jam eod
[14:12]  * facubatista -> errands
[14:24] <Chipaca> facubatista: I don't understand: yes people may be importing testing other than in unittests but why does that mean we need to import it from __init__?
[14:25] <Chipaca> afaict the only thing we _need_ to import are the two that confuse python wrt ordering
[14:25] <Chipaca> or even just the one, the one tha tneeds to come first
[14:41] <facubatista> Chipaca, mmm... yes, probably with just importing one, the import cycle will be solved, but wouldn't it "look" weird?
[14:41] <Chipaca> facubatista: it would, but that's solved by a comment explaining it :)
[14:42] <Chipaca> facubatista: and then when we do the work to pull in exactly what we want in 'ops', it goes away
[14:42] <facubatista> Chipaca, ack
[14:59] <facubatista> Chipaca, pushed change
[15:16]  * Chipaca brb
[15:19] <mup_> Issue operator#254 opened: Improve docstrings to conform the Google Style <Created by facundobatista> <https://github.com/canonical/operator/issues/254>
[15:21] <mup_> Issue operator#255 opened: Incorporate type hinting in all public methods, and check them <Created by facundobatista> <https://github.com/canonical/operator/issues/255>
[15:29] <facubatista> niemeyer, Chipaca, may I get a review on #246? thanks!
[15:29] <mup_> PR #246: Made breakpoint handling code to use already parsed JUJU_DEBUG_AT, and isolated the message showing logic <Created by facundobatista> <https://github.com/canonical/operator/pull/246>
[15:37] <Chipaca> facubatista: will do
[15:37]  * facubatista -> lunch
[15:58] <Chipaca> waaaait
[15:58] <Chipaca> 3.5 didn't have type hints??
[15:58]  * Chipaca checks
[15:58] <Chipaca> yes it did
[16:13] <jam> Chipaca, so the question, is it that it doesn't like ): on a line by itself, or it doesn't like that __init__ doesn't have a -> return hint
[16:13] <jam> It didn't make sense to me to add a return hint to __init__
[16:23] <Chipaca> jam: __init__'s return is ignored AFAICT ¯\_(ツ)_/¯
[16:23] <jam> Chipaca, so, not wrapping to the next line seems to pass on 3.5
[16:24]  * Chipaca would dance if he were a dancer
[16:24] <jam> eg, don't do ',\n):' but just '):'
 waaaait
[16:29] <jam> https://github.com/canonical/operator/pull/252/commits/7e988b3bdc74b7061d5da213ec6ce54a387f5bfa
[16:29] <mup_> PR #252: ops/testing.py: document Harness in Google style <Created by jameinel> <https://github.com/canonical/operator/pull/252>
[16:29] <jam> of course, cut and paste correctly :)
[16:30] <Chipaca> jam: just one thing to note, that isn't important right now but might be later
[16:30] <Chipaca> jam: None isn't a string, and isn't a typing.TextIO
[16:31] <Chipaca> so what you really mean is Optional[typing.Union[str, typing.TextIO]], or equivalently typing.Union[str, typing.TextIO, None]
[16:31] <jam> Chipaca, type annotations seem like they become unwieldy
[16:31] <Chipaca> yes
[16:32] <jam> Chipaca, what syntax would you prefer?
[16:32] <Chipaca> jam: that's what I tried to say, earlier :-/
[16:32] <jam> Optional seems to hint to the user
[16:32] <Chipaca> i like what they do, but they're not exactly gratis
[16:32] <Chipaca> OTOH you can do MyThing = typing.Optional[....]
[16:32] <jam> for things that aren't str or file they feel a lot better
[16:33] <Chipaca> Optional communicates intent better, yes. But it does evaluate to the Union one (so if you stringify it you'll see the Union)
[16:33] <facubatista> Chipaca, meeting?
[16:33] <Chipaca> facubatista: can we move our 1:1 to tomorrow?
[16:33] <facubatista> Chipaca, yes we can
[16:34] <Chipaca> facubatista: I still don't have audio and am a bit cross about that
[16:34] <Chipaca> would rather not do it on the phone again
[16:34] <facubatista> Chipaca, just send the invite :)
[16:34] <facubatista> or, better, first fix the audio then send the invite :p
[16:35] <Chipaca> man, tomorrow is solid meetings
[16:35] <facubatista> Thu
[16:35] <Chipaca> even got a conflict; i'm not going to make the standup
[16:37] <jam> Chipaca, OptionalYAML incoming
[16:41] <Chipaca> facubatista: that's two PRs you could be mergin'
[16:42] <facubatista> yay
[16:43] <mup_> PR operator#221 closed: ops/main.py: support dispatch <Created by chipaca> <Merged by chipaca> <https://github.com/canonical/operator/pull/221>
[16:43] <mup_> PR operator#248 closed: Import internal modules in a controlled way. Fixes #247 <Created by facundobatista> <Merged by facundobatista> <https://github.com/canonical/operator/pull/248>
[16:44] <mup_> Issue operator#247 closed: Circular dependency error after pulling in latest version of framework <Created by gnuoy> <Closed by facundobatista> <https://github.com/canonical/operator/issues/247>
[16:44] <mup_> PR operator#246 closed: Made breakpoint handling code to use already parsed JUJU_DEBUG_AT, and isolated the message showing logic <Created by facundobatista> <Merged by facundobatista> <https://github.com/canonical/operator/pull/246>
[16:44] <mup_> PR operator#251 closed: Fix doctrings for add_relation_unit in ops.testing <Created by gnuoy> <Merged by chipaca> <https://github.com/canonical/operator/pull/251>
[16:47] <Chipaca> facubatista: can you give #253 a pass? it fixes a bug that people are having to work around right now
[16:47] <mup_> PR #253: Test harness no backend <Created by jameinel> <https://github.com/canonical/operator/pull/253>
[16:49] <facubatista> Chipaca, yes
[16:59] <Chipaca> timidity had sequestered /dev/snd/*!
[17:00]  * Chipaca whacks it for its temerity
[17:00] <Chipaca> aaaand, I need to EOD. ttfn at least :-)
[20:19]  * facubatista eods
[21:30]  * Chipaca EODs


[06:10] <MCR_> ricotz, hi. Just FYI: Solved my issues with (old) fglrx 12.11-beta. For comparison: Valley Score 1117, with fglrx-13 around 700 points there and a lot of gfx problems...
[06:14] <Sarvatt> MCR_: there havent been any updates in xorg-edgers that would affect fglrx in many many months
[06:16] <Sarvatt> so is 13.whatever slower on whatever release you're testing 12.11-beta on? thats worth trying if you havent
[06:35] <MCR_> Sarvatt, that is strange. Yes, 13.x is much slower here and also creates visual bugs (many of them).
[06:36] <MCR_> HD 6950 hardware
[06:38] <MCR_> Sarvatt, I might drop fglrx in the near future anyway as radeon seems to improve steadily...
[06:38] <MCR_> and scrolling and other things were already better than with fglrx...
[06:39] <MCR_> for example, 3 displays with radeon -> no problem
[06:39] <MCR_> 3 displays with fglrx -> not working
[06:40] <MCR_> and I have video 6 outputs (2xHDMI 4xDP) on my card
[06:43] <Sarvatt> what release and what DE? there was a unity upgrade on 6-25 that might be problematic if it was raring, and there was a kubuntu upgrade at the same time
[06:45] <MCR_> Raring, Compiz trunk, Unity 7 -> but I'm updating daily and it broke 2 or 3 days ago
[06:51] <MCR_> Sarvatt, with purged xorg-edgers ppa and downgraded fglrx to 12.11-beta everything is fast and bug-free again (just FYI)...
[06:52] <MCR_> I'm out, c ya.
[15:56] <mlankhorst> oh so that's the osmesa bug..
[16:03] <mlankhorst> oh..
[16:03] <mlankhorst> easy to fix, too!
[16:04] <mlankhorst> I'm going to slap someone if they suggest fixing it by doing another build round, if I'm not mistaking removing 4 lines is enough to fix this..
[16:09] <mlankhorst> http://paste.debian.net/14404/
[16:11] <mlankhorst> hm no, needs some more, I need to figure out how gl does it


[11:06] <Chima> Please, does anyone know why my bluetooth stopped working after i upgraded to 18.04?
[13:33] <Guest37889> has anyone managed to install Skippy-XD on Lubuntu 18.04 ?
[15:55] <Loz> I cannot upgrade software in terminal using lubuntu beaver?
[16:04] <Loz_> unable to upgrade software in terminal using lubuntu beaver, please help!
[16:06] <diogenes_> Loz_, ?
[16:08] <Loz_> Reading package lists... Done Building dependency tree        Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies.  libsnmp30:i386 : Depends: libperl5.26:i386 (>= 5.26.0~rc1) but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
[16:18] <diogenes_> Loz_, and did you run the given command?
[16:24] <Loz_> yes
[16:24] <diogenes_> what command did you use?
[16:25] <Loz_> apt --fix-broken install
[16:25] <diogenes_> and the result?
[16:27] <Loz_> E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
[16:27] <diogenes_> Loz_, restart the computer, after that run: sudo apt --fix-broken install
[16:28] <Loz_> ok i will be back shortly thanks


[14:35] <renatu> mcphail, hi, which version of owncloud are you using?
[16:13] <mcphail> renatu: i'm actually on nextcloud, which is, i think, a simple fork of 9.0.something
[19:38] <mimecar> hi
[19:40] <mimecar> is there an image pack with all the controls you can use on Ubuntu Touch?
[19:40] <mimecar> I would like design a mockup first


[00:37] -queuebot:#ubuntu-release- Unapproved: appstream-glib (zesty-proposed/main) [0.6.9-1 => 0.6.9-1ubuntu2] (desktop-core)
[02:29] <tsimonq2> Could a member of the SRU team please review lxterminal?
[02:30] <tsimonq2> It's in Zesty's unapproved queue at the moment. The bug report is in the changelog, but here it is for reference: bug 1703307
[05:00] -queuebot:#ubuntu-release- Unapproved: gnome-software (zesty-proposed/main) [3.22.7-0ubuntu<IP_ADDRESS> => 3.22.7-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[05:08] -queuebot:#ubuntu-release- Unapproved: gnome-software (xenial-proposed/main) [3.20.1+git20170524.0.ea2fe2b0-0ubuntu<IP_ADDRESS> => 3.20.5-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[07:24] <LocutusOfBorg> sigh, a new strip-nondeterminism failure https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868111
[07:24] <LocutusOfBorg> gnome-software seems affected
[08:28] -queuebot:#ubuntu-release- New source: virtualbox-lts-zesty (xenial-proposed/primary) [5.0.40-dfsg-0ubuntu<IP_ADDRESS>~16.04.3]
[08:30] <LocutusOfBorg> apw, do you think we can fast-track this? ^^ rationale: LP: #1687981 and I don't want to have hwe released without a compatible vbox guest driver available, specially because people already started bothering me
[08:44] <rbasak> chiluk: how do we know for certain that this includes fixes for kabylake and skylake-x?
[08:59] <apw> LocutusOfBorg, will look at it shortly
[08:59] <LocutusOfBorg> lovely thanks
[08:59] <LocutusOfBorg> I can't update the bug because "package doesn't exist in the archive" meh
[09:00] <LocutusOfBorg> basically it is the same as virtualbox-lts-xenial and virtualbox-lts-yakkety, and in this case I had to cherry-pick also the xorg 1.19 fixes
[09:00] <LocutusOfBorg> don't say anybody, but this should even work with a rootless xorg
[09:00] <apw> LocutusOfBorg, thanks for the background
[09:00] <LocutusOfBorg> I don't think xenial had the rootless xorg mode, and I don't think it is dragged in
[09:01] <LocutusOfBorg> it was some yakkety+ stuff, but reverted again for zesty because meh
[09:01] <LocutusOfBorg> thanks, in case feel free to ask
[09:15] -queuebot:#ubuntu-release- Unapproved: rejected ntp [sync] (xenial-proposed) [1:4.2.8p4+dfsg-3ubuntu5.5]
[09:15] -queuebot:#ubuntu-release- Unapproved: rejected ntp [sync] (yakkety-proposed) [1:4.2.8p8+dfsg-1ubuntu2.1]
[09:22] -queuebot:#ubuntu-release- Unapproved: ntp (trusty-proposed/main) [1:4.2.6.p5+dfsg-3ubuntu<IP_ADDRESS> => 1:4.2.6.p5+dfsg-3ubuntu<IP_ADDRESS>] (core)
[09:28] -queuebot:#ubuntu-release- Unapproved: rejected ntp [source] (trusty-proposed) [1:4.2.6.p5+dfsg-3ubuntu<IP_ADDRESS>]
[09:40] <LocutusOfBorg> can we please have dh_stripnondeterminism migrate or increase queue priority?
[09:41] <LocutusOfBorg> LP: #1703746 will make probably lots of tests fail
[09:41] <LocutusOfBorg> and I would like to upload the new version soon(TM)
[10:16] <apw> LocutusOfBorg, there seem to be tests in the primary queues for those so they will skip up over the perl stuff, i don't believe we have any greater control
[10:59] -queuebot:#ubuntu-release- Unapproved: rejected python-werkzeug [source] (trusty-proposed) [0.9.4+dfsg-1.1ubuntu2.1]
[11:00] -queuebot:#ubuntu-release- Unapproved: rejected python-werkzeug [source] (xenial-proposed) [0.10.4+dfsg1-1ubuntu1.1]
[12:19] -queuebot:#ubuntu-release- Unapproved: accepted ntp [source] (trusty-proposed) [1:4.2.6.p5+dfsg-3ubuntu<IP_ADDRESS>]
[12:20] -queuebot:#ubuntu-release- Unapproved: accepted ntp [source] (xenial-proposed) [1:4.2.8p4+dfsg-3ubuntu5.6]
[12:20] -queuebot:#ubuntu-release- Unapproved: accepted ntp [source] (yakkety-proposed) [1:4.2.8p8+dfsg-1ubuntu2.2]
[12:21] -queuebot:#ubuntu-release- Unapproved: accepted ntp [source] (zesty-proposed) [1:4.2.8p9+dfsg-2ubuntu1.2]
[12:23] <LocutusOfBorg> Laney, please ignore strip-nondeterminism testsuite
[12:23] <LocutusOfBorg> otherwise lots of the kde autopkgtestbuilds will fail
[12:23] <LocutusOfBorg> it is too late in the queue
[12:23] <LocutusOfBorg> let it migrate please
[12:31] <LocutusOfBorg> just ignore it once, not disable or force-bad
[12:36] <LocutusOfBorg> infinity, apw, either choose virtualbox-hwe or virtualbox-lts-zesty, differences are just the name (as said before, I built/tested them both)
[12:36] <apw> LocutusOfBorg, thanks
[12:38] -queuebot:#ubuntu-release- New source: virtualbox-hwe (xenial-proposed/primary) [5.0.40-dfsg-0ubuntu<IP_ADDRESS>~16.04.3]
[12:50] <Laney> LocutusOfBorg: k, makes sense
[12:55] <LocutusOfBorg> thanks, I'll keep an eye in retrying some of them
[12:55] <LocutusOfBorg> the sync in 12h shoud have the testsuite run and not ignored please
[12:57] <Laney> it's versioned anyway
[12:57] <LocutusOfBorg> wonderful
[12:57] <LocutusOfBorg> whatever is not permanent makes me happy
[12:58] <LocutusOfBorg> there still is a nasty bug on non-determinism, but should affect few packages
[12:59] <LocutusOfBorg> nevermind, was the same fixed in the 038
[13:22] -queuebot:#ubuntu-release- Unapproved: accepted libzen [source] (xenial-proposed) [0.4.32-1ubuntu<IP_ADDRESS>]
[13:23] -queuebot:#ubuntu-release- Unapproved: accepted libzen [source] (yakkety-proposed) [0.4.33-3ubuntu<IP_ADDRESS>]
[13:23] -queuebot:#ubuntu-release- Unapproved: accepted libzen [source] (zesty-proposed) [0.4.34-1ubuntu<IP_ADDRESS>]
[13:30] -queuebot:#ubuntu-release- Unapproved: accepted yubikey-piv-manager [source] (zesty-proposed) [1.3.0-1+ubuntu17.04.1]
[13:41] <LocutusOfBorg> Laney, are you sure about your non-determinism hammer?
[13:55] <Laney> yes
[13:56] <LocutusOfBorg> yep, migrated! success! <3
[13:56] <LocutusOfBorg> qaplà
[14:41] -queuebot:#ubuntu-release- Unapproved: accepted netcfg [source] (xenial-proposed) [1.135ubuntu4.4]
[14:44] -queuebot:#ubuntu-release- Unapproved: rejected libmbim [source] (xenial-proposed) [1.12.2-2ubuntu1.1]
[14:47] -queuebot:#ubuntu-release- Unapproved: accepted php-defaults [source] (xenial-proposed) [35ubuntu6.1]
[15:00] -queuebot:#ubuntu-release- Unapproved: skiboot (xenial-proposed/universe) [5.1.13-0ubuntu3 => 5.4.3-1ubuntu<IP_ADDRESS>] (no packageset)
[15:03] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (xenial-proposed/universe) [1.0+16.04ubuntu1 => 1.1+16.04ubuntu1] (no packageset)
[15:15] <ahoneybun> fossfreedom: thanks for the fix with the ubiquity merge
[15:20] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.26.8~14.04 => 2.26.9~14.04] (no packageset)
[15:20] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.26.8 => 2.26.9] (desktop-core, ubuntu-server)
[15:21] -queuebot:#ubuntu-release- Unapproved: snapd (yakkety-proposed/main) [2.26.8+16.10 => 2.26.9+16.10] (desktop-core, ubuntu-server)
[15:21] -queuebot:#ubuntu-release- Unapproved: snapd (zesty-proposed/main) [2.26.8+17.04 => 2.26.9+17.04] (desktop-core, ubuntu-server)
[15:31] <bdmurray> infinity: Can 15.04 be set to unsupported yet? bug 1703718
[15:44] <apw> bdmurray, as far as i know we still are producing packages for specific projects in vivid, which is only possible because it is still open
[16:00] <infinity> bdmurray: Not my call.
[17:20] -queuebot:#ubuntu-release- Unapproved: swift (xenial-proposed/main) [2.7.1-0ubuntu1 => 2.7.1-0ubuntu2] (openstack, ubuntu-server)
[17:26] <slangasek> bdmurray, infinity, cjwatson: apt-ftparchive appears to have finished again on ddebs.u.c, and I'm now doing a catch-up run; we should be in decent shape shortly
[17:26] <cjwatson> thanks
[17:27] <infinity> a-f needs a SIGINT handler, clearly.
[17:27] <infinity> ^C
[17:27] <infinity> HAHAHA NO
[17:27] <infinity> ^C
[17:27] <infinity> NO, REALLY, NO
[17:27] <infinity> ^C
[17:27] <infinity> OKAY, ONE MORE TIME AND I'LL DO IT
[17:34] <slangasek> yeah, as near as I could tell the existing behavior was something resembling ftruncate64(db, 8GB - dow_jones_index) && sendfile("/dev/random", db)
[17:35] <infinity> slangasek: So, we can blame the corruption on Trump?
[17:36] <infinity> That was more meta than I intended.
[17:36] <slangasek> :)
[17:39] <xnox> yellen. infinity also congrats on higher mortgage interest rates =)
[17:40] <infinity> xnox: Higher rates are usually the sign of a recovering economy, I'm not going to be too grumpy.
[17:40] <infinity> xnox: (But I also aim to pay off my house before my current fixed term is up, because screw paying moe)
[17:40] <infinity> s/moe/more/
[17:40] <xnox> +1
[17:40] <infinity> Though I don't want to pay Moe either.
[17:41] <xnox> well job! good done!
[17:44] <infinity> xnox: Also, why are you keeping track of Canadian lending rates?
[17:44] <xnox> infinity, i was thinking "maybe i need to get life, or like date somebody, cause why the fuck do i know these things, given that I don't trade CAD nor USD; do not have property in CAD; nor my pension is invested in CAD"
[17:45] <xnox> basically it was a headline in FT that Canadian central bank has raised the rates for the first time since 2010
[17:46] <infinity> Oh wow, it's been 7 years?  Yeah, I guess I see how that could make international headlines.
[17:46] <infinity> But you also need to date.
[17:48] <xnox> infinity, and i'm subscribed to FT.com because commenting there pays 0.05 more than commenting on bbc.
[17:49] <infinity> xnox: You get... Paid to comment... On the internet?
[17:49] <infinity> xnox: Does this have something to do with your Russian passport?
[17:49] <infinity> xnox: Are you a Russian bot?
[17:52]  * xnox giggles
[17:53] <xnox> https://en.wikipedia.org/wiki/50_Cent_Party
[17:53] <xnox> no, not me. but the quality of bot comments is much higher and easier on the eye, than on other newspapers.
[17:54] <xnox> i think the russian bot commenters are screened, and only senior commentators are allowed to post on ft.com
[18:03] -queuebot:#ubuntu-release- Unapproved: swift (trusty-proposed/main) [1.13.1-0ubuntu1.2 => 1.13.1-0ubuntu1.3] (ubuntu-server)
[18:36] <bdmurray> infinity, slangasek: Per our previous discussions I'm getting ready to modify m-r-d and m-r-lts-d however I've discovered that m-r-lts-d shouldn't have anything right now and actually can't be empty. I'm going to stick a comment in there about why its empty - sound good?
[18:37] <slangasek> bdmurray: +1
[18:37] <bdmurray> "# This is empty because there currently isn't an LTS release under development."
[18:37] <infinity> bdmurray: "# This page left intentionally blank"
[18:38] <infinity> I wonder if that's a thing that still happens in modern typesetting (I mean, other than as a joke).
[18:38] <infinity> Future generations won't get it.
[18:38] <infinity> HOW WILL WE COMMUNICATE WITHOUT SHARED TYPOGRAPHICAL HUMOUR.
[20:12] -queuebot:#ubuntu-release- Unapproved: rejected swift [source] (trusty-proposed) [1.13.1-0ubuntu1.3]
[20:16] -queuebot:#ubuntu-release- Unapproved: accepted swift [source] (trusty-proposed) [1.13.1-0ubuntu1.3]
[20:19] -queuebot:#ubuntu-release- Unapproved: rejected swift [source] (xenial-proposed) [2.7.1-0ubuntu1.1]
[20:19] -queuebot:#ubuntu-release- Unapproved: accepted swift [source] (xenial-proposed) [2.7.1-0ubuntu2]
[22:37] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.13 => 2.408.14] (desktop-core)
[22:37] <infinity> bdmurray, slangasek: ^-- If one of you has a moment, this could use some TLC.
[22:40] <bdmurray> infinity: I do
[22:41] <bdmurray> although looking at the SRU queue is making me sad for tomorrow
[22:42] <infinity> bdmurray: I was planning to step out of line and do some tomorrow too.
[22:42] <infinity> bdmurray: So we can start from either end or something.
[22:45] <bdmurray> infinity: maybe we should release the exisiting livecd-rootfs in -proposed first?
[22:45] <infinity> bdmurray: Oh, didn't check to see if there was one.
[22:46] <infinity> That's been waiting almost a month for rcj to verify his bug.
[22:46] <infinity> rcj: ^
[22:46] <infinity> rcj: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1693018
[22:47] <sbeattie> speaking of SRUs, can the nginx SRU in yakkety be yanked, since it doesn't seem anyone is going to verify it? (cc teward)
[22:48] <bdmurray> infinity: there's no xenial task for that bug, so the xenial one can still be released
[22:48] <sbeattie> it's a little weird, because the xenial SRU got pushed to updates, so now is ahead of yakkety.
[22:48] <bdmurray> nobody upgrades from X to Y anymore anyway
[22:49] <infinity> bdmurray: Err, I was clicking the wrong clicky from pending-sru, indeed.
[22:49] <bdmurray> its too bad the release header isn't always visibile or its too bad there are so many unverified SRUs
[22:49] <infinity> bdmurray: So yeah, please release xenial and then gimme mine. ;)
[22:50] <infinity> bdmurray: A floating header is a trivial bit of CSS.  Might not be the worst idea.  Or re-insert a column-header row every 10 rows or something, if you prefer it to work in browsers that aren't pretty.
[23:01] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.14]