[21:03] -queuebot:#ubuntu-quality- Builds: Xubuntu Desktop amd64 [Focal 20.04.4] (20220218.1) has been added
[21:07] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop amd64 [Focal 20.04.4] (20220218.1) has been added
[21:09] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.4] (20220218.1) has been added
[21:10] -queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.4] (20220218.1) has been added
[21:11] -queuebot:#ubuntu-quality- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.4] (20220218) has been added
[21:11] -queuebot:#ubuntu-quality- Builds: Kubuntu Desktop amd64 [Focal 20.04.4] (20220218.1) has been added
[21:13] -queuebot:#ubuntu-quality- Builds: Ubuntu Studio DVD amd64 [Focal 20.04.4] (20220218) has been added
[21:18] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop amd64 [Focal 20.04.4] (20220218.2) has been added
[21:20] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.4] (20220218.1) has been added
[21:20] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity ppc64el [Focal 20.04.4] (20220218.1) has been added
[21:20] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity arm64 [Focal 20.04.4] (20220218.1) has been added
[21:20] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity s390x [Focal 20.04.4] (20220218.1) has been added
[22:29] -queuebot:#ubuntu-quality- Builds: Ubuntu Base amd64 [Focal 20.04.4] (20220218.1) has been added
[22:29] -queuebot:#ubuntu-quality- Builds: Ubuntu Base armhf [Focal 20.04.4] (20220218.1) has been added
[22:29] -queuebot:#ubuntu-quality- Builds: Ubuntu Base riscv64 [Focal 20.04.4] (20220218.1) has been added
[22:29] -queuebot:#ubuntu-quality- Builds: Ubuntu Base arm64 [Focal 20.04.4] (20220218.1) has been added
[22:29] -queuebot:#ubuntu-quality- Builds: Ubuntu Base s390x [Focal 20.04.4] (20220218.1) has been added
[22:29] -queuebot:#ubuntu-quality- Builds: Ubuntu Base ppc64el [Focal 20.04.4] (20220218.1) has been added


[00:17] <Bashing-om> Wild_Man: Your attention to Gdoc is invited - comments to be resolved.
[15:45] -BottyMcBotFace:#ubuntu-news- ::OMG!Ubuntu:: Linux Mint Creates Simple File Transfer App for Linux Desktops @ https://www.omgubuntu.co.uk/?p=164823 (by Joey Sneddon)
[20:33] -BottyMcBotFace:#ubuntu-news- ::OMG!Ubuntu:: SRain is a New GTK IRC Client for Linux Desktops @ https://www.omgubuntu.co.uk/?p=164857 (by Joey Sneddon)
[23:11] <Bashing-om> UWN620 up for review and final edits: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue620
[23:24] <krytarik> Bashing-om: Just one thing that I've spotted yet, I'm not sure how "Canonical at the OSM-MR#8 Hackfest, Madrid" warrants to be featured in the LoCo News section.
[23:42] <Bashing-om> krytarik: Loco news section: Chris had the same concern - my thought was as an "event" that it belonged ; move it as a bulleted item to Canonical ?
[23:58] <krytarik> Bashing-om: Yeah, I'd say so - there are quite a few events they feature on the blog, and this one doesn't involve any local Ubuntu community from what I saw.


 As if there is a stale/cached view of ftpmaster.internal or some connectivity issue?
[09:50] <xnox> is this known / something you mentioned before, or new?
[10:08] <laney> xnox: no, what's that about, did you check ftpmaster yourself? that was like a day after the SRU was released
[10:08] <laney> hmmmm phasing?
[10:08] <seb128> laney, I mentioned that in private :p
[10:08] <seb128> laney, a similar issue was discussed on ~foundations yesterday
[10:08] <seb128> well it does sound similar at least
[10:15] <laney> seb128: bug #1925745 ?
[10:15] <seb128> laney, sounds like it
[10:15] <laney> it does
[10:15] <laney> xnox:
[11:06] <xnox> laney:  i did check ftpmaster myself.
[11:06] <xnox> from people.canonical.com
[11:06] <laney> right, see the bug link
[11:07] <xnox> tah
[13:24] <icey> is some action necessary to sync a package from debian to universe? cpufreqd is stuck in proposed because of a new dependency on libcpupower-dev on ppc64el
[13:42] <RikMills> Logan_: I believe cpufreqd there was your merge ^
[13:44] <RikMills> urgh. that new build dep doesn't exist in ubuntu
[13:50] <seb128> it's built by linux in debian so I guess check with #ubuntu-kernel ?
[14:36] <Logan_> https://bugs.launchpad.net/bugs/1215411
[14:37] <Logan_> icey RikMills ^
[14:39] <RikMills> thanks, but wow
[16:26] <Eickmeyer> LocutusOfBorg: Hi! Just had an interesting VirtualBox issue that wasn't happening even a week ago in impish. bug 1932578
[16:26] <Eickmeyer> Anything I can do to help here?
[16:29] <Eickmeyer> Correction: Seems to be a problem in impish (and the vbox package there) since I only just upgraded to Impish a few days ago.
[16:34] <Eickmeyer> Oh, nvm LocutusOfBorg. Seems as though xnox already has a fix.
[16:35] <Eickmeyer> Dammit, that's for focal.
[16:35] <Eickmeyer> (sorry for the noise)
[16:47] <xnox> Eickmeyer:  i'm sorry, what do you expect me to have?
[16:48] <Eickmeyer> xnox: Sorry, bad ping. You uploaded a NCR for virtualbox to focal, doesn't fix the issue in impish. Sorry for the noise.


[00:06] <wulfgarpro> wgrant: i've set it to "Invalid" but it's still open in a sense
[00:07] <cjwatson> Invalid isn't open.
[00:07] <cjwatson> In what sense are you perceiving it as open?
[00:07] <wulfgarpro> cjwatson: well I can see it in the list of bugs marked as invalid
[00:07] <cjwatson> Yes, not open doesn't mean deleted.
[00:07] <cjwatson> That's expected.
[00:07] <wulfgarpro> cjwatson: so that's closed
[00:07] <wulfgarpro> cjwatson: ok
[00:08] <wulfgarpro> how do I filter the bugs I can see by project?
[00:08] <cjwatson> https://bugs.launchpad.net/PROJECT/+bugs
[00:08] <cjwatson> for appropriate values of PROJECT
[00:09] <wulfgarpro> cjwatson: great, thanks
[00:22] <wulfgarpro> is it possible to delete comments you make?
[00:27] <wgrant> wulfgarpro: You'll see a Hide link, which makes the comment invisible to everyone except you and admins.
[00:51] <wulfgarpro> wgrant: thanks :)
[10:26] <karni> Is there a way for me to request another import of translations with launchpad? I used the one-time import, but now I've added more translated .po files, and would like to re-do it. (After I commited it, I also changed import pocliy to import both pot and po files, hoping lp would pick it up)
[13:24] <balloons> Does anyone understand what this message means "This team cannot be converted to Public since it is referenced by an usertouseremail." I'm trying to convert a private team to public, but running into this error
[13:26] <cjwatson> I think that means you should file a bug
[13:27] <cjwatson> We don't allow changing visibility in cases where there's a reference somewhere else that would risk leaking private team membership information
[13:27] <cjwatson> But the fact that somebody has once used the "contact this team's admins" facility surely doesn't do that
[13:28] <balloons> cjwatson, mmm. So I'm a bit stuck then
[13:28] <balloons> I can definitely file the bug. Sounds like if I want a public team now though, I'll need to create a new one? What I'm really after is a public ppa from the current team
[13:29] <balloons> which, since the team is private, doesn't seem to be possible
[13:30] <cjwatson> Is it today-urgent?  We could fix such a bug reasonably quickly
[13:30] <cjwatson> As in a couple of days
[13:30] <balloons> yea, I kind of need to keep moving on this. Hmm
[13:30] <cjwatson> If you need a public team absolutely right now then you're stuck unless you create a new one
[13:39] <balloons> https://bugs.launchpad.net/launchpad/+bug/1498497
[13:39] <balloons> I'll make / use a public team in the interim. thanks for the help
[14:31] <cjwatson> balloons: What team name was this, BTW?  (in /msg if you want)  This is an interestingly obscure corner case
[14:36] <cjwatson> balloons: I can't find a way to reproduce this in the test suite without making the team in question be a member of another team, which independently blocks visibility changes (even if the membership has been deactivated)
[14:36] <cjwatson> But maybe I'm missing something ...
[14:38] <balloons> hopefully the specific team will help. But I have gone ahead and used another public team, so I don't need to make this work anymore
[14:39] <balloons> it is a weird bug, as I don't suspect there's anything really private about the team as-is. It was private for benign reasons
[15:11] <cjwatson> balloons: all right, hopefully https://code.launchpad.net/~cjwatson/launchpad/visibility-usertouseremail/+merge/271997 will pass muster
[15:11] <balloons> cjwatson, awesome, thanks ;-)


[12:00] <elky> o/
[12:01] <mobyli> o/
[12:01] <jussi> o/
[12:01] <jussi> tsimpson: about?
[12:02] <mobyli> Warning : I may be slow and terse
[12:02] <Tm_T> chomp
[12:03] <elky> shall i give ts2 / tsimpson a few mins or just start?
[12:03] <jussi> give him till 5 pawsst or so
[12:03] <jussi> past even
[12:03] <IdleOne> morning!
[12:03] <jussi> morns IdleOne
[12:05] <elky> #startmeeting
[12:05] <MootBot> Meeting started at 06:05. The chair is elky.
[12:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[12:06] <elky> [topic] Review Bugs related to the Ubuntu IRC Council
[12:06] <MootBot> New Topic:  Review Bugs related to the Ubuntu IRC Council
[12:07] <jussi> so we just have bug 788503
[12:07] <jussi> I think this is pretty well in progress.
[12:08] <elky> anything that needs to be said here?
[12:08] <jussi> not really imho
[12:08] <jussi> Move on.  :)
[12:08] <IdleOne> maybe change the bug to in progress?
[12:08] <elky> [topic] Review last meetings action items
[12:08] <MootBot> New Topic:  Review last meetings action items
[12:08] <jussi> IdleOne: done
[12:08] <IdleOne> jussi :)
[12:09] <mobyli> Mine is done
[12:10]  * elky tries to find the list of items
[12:10] <elky> the wiki is being its normal efficient self again, of course.
[12:10] <jussi> tsimpson's is done
[12:10] <jussi> elky: https://wiki.ubuntu.com/IRCCouncil/TeamReports
[12:10] <jussi> (if you didnt get there already)
[12:10] <elky> yeah, it wasn't loading
[12:10] <jussi> ahh
[12:10] <jussi> anyway, thats all of them
[12:11] <jussi> both done
[12:11] <elky> [topic] Review #ubuntu-ops-team
[12:11] <MootBot> New Topic:  Review #ubuntu-ops-team
[12:12] <elky> plz to explain?
[12:13] <jussi> We agreed at previous meetings that we would review if it was being abused or used well, ie. should it continue to exist
[12:13] <elky> I think it's being used well. It's getting elephants out of rooms, etc.
[12:14] <mobyli> I think we can drop this item from future agenda
[12:14] <Tm_T> I have nothing to complain about it, serves us well
[12:14] <IdleOne> agreed
[12:15] <jussi> I think reviews are good, but maybe once every few months.
[12:15] <elky> jussi, quarterly?
[12:16] <jussi> elky: yeah, sounds good
[12:16] <elky> mobyli?
[12:16] <mobyli> Works for me
[12:16] <elky> [agreed] move review of #ubuntu-ops-team to quarterly
[12:16] <MootBot> AGREED received:  move review of #ubuntu-ops-team to quarterly
[12:16] <jussi> I can take an action to add it to the calendar :)
[12:17] <elky> [topic] reports
[12:17] <MootBot> New Topic:  reports
[12:17] <jussi> reports?
[12:17] <elky> jussi, also if you want to play with the agenda while i'm chairing
[12:17] <elky> Keep IRCCouncil/TeamReports updated.
[12:17] <mobyli> What is this?
[12:17] <elky> it's listed as an agenda item
[12:17] <jussi> elky: thats just something we have to do, not discuss
[12:17] <mobyli> Ah
[12:17] <elky> i'm pasting from the agenda list
[12:18] <jussi> elky: skip to the no fixed parts now
[12:18] <elky> if it's in the agenda list, i'll make a topic of it
[12:18] <elky> :P
[12:18] <jussi> the rest are actions.
[12:18] <elky> jussi, is nhandler awake?
[12:18] <Tm_T> won't hurt mentioning if it's done or under works
[12:18] <mobyli> True
[12:19] <elky> Tm_T, we do reports. it's a continual work in progress. anything specific? :P
[12:19] <mobyli> nhandler is busy today
[12:19] <Tm_T> nah, just commenting
[12:19] <elky> mobyli, then i'll skip his agenda item
[12:20] <jussi> genii doesnt seem to be around either.
[12:20] <jussi> nhandler: is likely sleeping.
[12:20] <elky> woo, short meetings ftw
[12:20] <jussi> elky: I fixored the agenda page
[12:20] <mobyli> Hehe
[12:20] <elky> [topic] general business
[12:20] <MootBot> New Topic:  general business
[12:20] <elky> jussi, thanks
[12:21] <elky> anything else?
[12:21] <IdleOne> have any of the "older" core ops clicked the join team link for -ops?
[12:21] <IdleOne> just curious
[12:21] <jussi> IdleOne: not as far as I have seen, but you can look yourself
[12:21] <IdleOne> true
[12:22] <elky> no takers?
[12:22] <jussi> elky: I think we are grand. Lucky you. :)
[12:24] <elky> awesome
[12:24] <elky> [endmeeting]
[12:24] <elky> #endmeeting
[12:24] <MootBot> Meeting finished at 06:24.
[12:24] <elky> failbot
[12:25] <elky> surely enough people do that it should be a feature :P
[12:27] <mobyli> Sorry. Are we done?
[12:30] <elky> jussi, want to text him to stop panicking?
[12:30] <jussi> elky: he will be fine ;)
[12:31] <IdleOne> haha


[07:11] <FoxMaSk> hello
[07:11] <FoxMaSk> 안녕하세요
[07:15] <lex__> 안녕하세요.^^
[07:17] <FoxMaSk> lex__: 음력 설날은 어땠나요?
[07:46] <FoxMaSk> does everybody went on slack now ? it seems we are less and less since we left freenode
[08:08] <lex__> FoxMaSk: 음식을 많이 먹으면서 보냈어요. 후회하고 있답니다.
[08:24] <FoxMaSk> lex__: ^^
[18:53] <Seony> FoxMaSk: no i don't think so. i've used slack for some reasons, but i still use irc and want to keep using it.


[02:12] <wblackstone> how removing snaps
[02:26] <bazhang> how did you install
[02:26] <bazhang> why not ask in #snappy
[11:06] <xfusr> hello
[11:07] <knome> hello
[11:07] <xfusr> can anyone else not boot after the latest updates?
[11:08] <knome> latest updates on what xubuntu version?
[11:08] <xfusr> 18.04.1
[11:09] <knome> i don't have the same issue, but in what way does your system not boot, eg. where it hangs?
[11:09] <knome> is there any error message?
[11:10] <xfusr> it puts me into tty1 whenever i boot
[11:10] <knome> can you login from there?
[11:12] <xfusr> yes, i can, but i can't switch to tty7
[11:12] <knome> ok
[11:13] <knome> when you've logged in, run "sudo service lightdm restart"
[11:13] <knome> what happens?
[11:15] <xfusr> nothing, still can't switch to tty7 and i am still stuck in tty
[11:16] <knome> no error message or output?
[11:16] <xfusr> nothing at all
[11:16] <knome> interesting
[11:16] <knome> flocculant, ping?
[11:17] <flocculant> knome: pong
[11:17] <knome> flocculant, any idea on what's happening with xfusr?
[11:17] <flocculant> was reading it
[11:18] <knome> i'm fortunate enough to not have had these kinds of black walls in ages...
[11:18] <flocculant> I've just today reinstalled 18.04.1 and it was fine updating
[11:18] <knome> (and i don't use non-intel ;))
[11:20] <flocculant> xfusr: from vt1 you should be able to pastebin things for others to look at so, pastebinit /var/log/Xorg.0.log and let us have the url
[11:20] <flocculant> and then try pastebinit .xsession-errors
[11:20] <xfusr> okay, give me a moment
[11:21] <flocculant> not sure if I can help tbh - but I'll look
[11:24] <xfusr> https://pastebin.ubuntu.com/p/dW3jqFmrph/ here's xorg.0.log
[11:25] <knome> xfusr, also pastebinit /etc/X11/xorg.conf
[11:25] <knome> because clearly X thinks it's faulty and apparently that's why it fails
[11:26] <xfusr> working on it
[11:26] <knome> no rush
[11:26] <knome> (though i have to leave in 20ish)
[11:26] <flocculant> long time since I've seen a xorg.conf ...
[11:27] <knome> i had one before my NUC, not too long ago...
[11:29] <xfusr> https://pastebin.ubuntu.com/p/hjgCWGX9FB/ here's .xsession-errors
[11:30] <flocculant> would suspect the xorg.conf is the one to look at now we've seen the xorg log
[11:30] <knome> indeed
[11:31] <knome> and the potential solution is to just try renaming it to something else and see if the system boots
[11:31] <knome> but let's see what it has eaten first
[11:31] <knome> (tbh, that's what X should probably try to do anyway if there was a parsing error...)
[11:31] <knome> i mean, imo
[11:36] <Babloyi> does thunar have no GUI way to set the executable bit?
[11:37] <Babloyi> I'm not finding the checkbox in Properties->Permissions
[11:46] <flocculant> Babloyi: it does if the file you're looking at is something you can execute
[11:46] <Babloyi> I have a jar file, and it doesn't show that
[11:47] <Babloyi> I had to set it executable in the terminal through chmod -x whatever
[11:47] <flocculant> right - not sure tbh
[11:48] <Babloyi> i.e. THUNAR SUXXXX :P
[11:57] <xfusr> flocculant: any ideas about my issue?
[11:57] <flocculant> xfusr: waiting to see the xorg.conf
[11:58] <flocculant> pastebinit /etc/X11/xorg.conf
[11:58] <xfusr> oh, sorry
[11:58] <flocculant> because that appears to be where the issue is - you must have missed knome asking for it :)
[11:59] <xfusr> https://pastebin.ubuntu.com/p/mBKXFBGMtq/ here's xorg.conf
[12:00] <flocculant> and you're using a xorg.conf because?
[12:00] <xfusr> to eliminate screen tearing
[12:00] <xfusr> i've used it before on 16.xx and 17.xx with no problems
[12:02] <flocculant> ok - well let's try and get you booted first, rename xorg.conf, sudo mv /etc/X11/xorg.conf /etc/X11/.xorg.conf
[12:02] <flocculant> right - and was it working ok for 18.04?
[12:02] <xfusr> yes, it was working fine
[12:02] <flocculant> mmk
[12:02] <flocculant> rename it and reboot
[12:05] <flocculant> I'm running out of time here - knome will be back at some point - and he's using Intel so might have more clue now
[12:05] <xfusr> ok, it's working now
[12:05] <xfusr> the pc booted
[12:05] <flocculant> ok - that's good
[12:06] <xfusr> i guess i'll have to find another fix to the tearing issue
[12:07] <xfusr> thank you for your help :)
[12:07] <flocculant> no problem
[12:07] <flocculant> the arch wiki shows more or less what you had - just not sna
[12:08] <flocculant> not going to be much more help than search google now - I'm sure you can do that :)
[12:09] <xfusr> yeah, i'll play around with the config file and see what works
[12:09] <flocculant> yup - good luck :)
[12:09] <xfusr> thanks :)
[12:09] <flocculant> let me know if you get it - I'll make some notes for next time
[12:26] <xfusr> i got it fixed by creating a new config file instead of editing xorg.conf directly: /etc/X11/xorg.conf.d/20-intel.conf
[12:50] <knome> xfusr, great to hear :)
[18:48] <wxl> what's the goto screenshot app for xubuntu, folks? screenshooter?
[18:49] <diogenes_> wxl, ls /usr/bin | grep screen
[18:49] <wxl> diogenes_: that's not the answer to the question i asked
[18:49] <flocculant> wxl: xfce4-screenshooter
[18:49] <wxl> flocculant: thank you :)
[18:50] <diogenes_> wxl, that will show you the exact name also that's a tip how to find it in different DEs too
[18:50] <flocculant> wxl: no problem :)
[18:51] <flocculant> wxl: you could have asked us in -devel or the one we all hang about in ;)
[18:51] <wxl> flocculant: ah, it's fine. figured i'd get a quicker answer to so simple a question :)


[13:55] <larsdues1ng> short question, what to do with bug, which are 3+ years old, and depend on ubuntu 8.04?!? I cannot set "won't fix"...
[13:57] <larsdues1ng> -> https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/296036
[13:58] <larsdues1ng> oh, ok  8.10 :)
[13:58] <dupondje> Release has reached EOL
[13:58] <dupondje> If the specific release has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to Incomplete and use the following response (Note RELEASE and DATE are placeholders):
[13:59] <dupondje> https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_EOL
[13:59] <larsdues1ng> oh... ok
[13:59] <larsdues1ng> thanks
[14:47] <sivang> hi all
[14:47] <sivang> There are some nice scrollers (that look suspiciously suitable for touch interface) in Unity 2D, it is using Qt right?
[14:48] <sivang> (sorry of this question is offtopic here..)
[15:05] <cjwatson> broder: as far as I'm concerned, lintian.uw.o would be a lot more useful pointed at quantal
[15:21]  * sivang just noticed there's an u-d-d list. /me looks for the same irc channel
[15:24] <sivang> is it okay to ask general devel discussions here?
[17:09] <balhau> Hi guys. Is someone here able to speak about bluetooth troubleshooting?
[17:09] <balhau> Or can someone point me a irc channel to speak about that?
[18:17] <melodie> hello
[18:19] <melodie> I wonder if the core version can be used to make a spin. is there a how to for that purpose somewhere ?
[18:19] <melodie> https://wiki.ubuntu.com/Core
[18:31] <mterry> cjwatson, hello!  if you're actually able to get this on the uds wifi, I'd like to chat with you about a proposed change in update-manager.  If you see me in the halls, stop me!  :)
[18:33] <cjwatson> mterry: OK, though not entirely a relevant expert
[18:33] <maco> wouldnt that be mvo's territory?
[18:34] <mterry> cjwatson, well, it involves package metadata, not UI stuff (the ability to know if a package will want a restart ahead of installing it)
[18:35] <cjwatson> mterry: Mm, that is actually mostly mvo - currently it's a script that postinsts can run, IIRC
[18:36] <mterry> cjwatson, oh, OK.  I'll bug mvo instead.  Yeah, it's a postinst thing right now, but I need to find out whether it's even possible to add it to package metadata somehow.
[18:36] <mterry> mpt is writing checks that Ubuntu can't cash  :)
[18:36] <cjwatson> mterry: Right, I'm not sure of the answer
[18:37] <mpt> mterry, we had a session on it at UDS Lucid
[18:37] <mterry> cjwatson, OK!  Well, are there any packages you know that conditionally call that script?  Like only sometimes want a reboot?
[18:37] <mterry> mpt, oh good.  I'll try to find the notes
[18:37] <mpt> mterry, https://blueprints.launchpad.net/ubuntu/+spec/upgrading-running-software
[18:38] <mpt> hm, not that helpful
[18:38] <mpt> ah, https://wiki.ubuntu.com/UpgradingRunningPrograms
[18:38] <mterry> mpt, that still looks like it only deals with finding out about the need after the fact?
[18:38]  * mterry reads
[18:39] <mpt> mterry, I remember there was discussion of a flag for each update representing whether it require restart ... Maybe it got lost in the mists of time
[18:40] <mterry> mpt, yeah in the whiteboard, there's a link to a more relevant spec that is superceded by this one....  so it must have gotten folded in
[18:41] <cjwatson> mterry: dbus.postinst
[18:41] <cjwatson> mterry: gconf2.postinst, initscripts.postinst, libc6:i386.postinst
[18:42] <mterry> mpt, it looks like the goal was to avoid the need for most restart packages by just having them magically update at next program start
[18:42] <cjwatson> mterry: libpam0g:i386.postinst, libssl1.0.0:i386.postinst
[18:42] <mterry> mpt, maybe the Software Update spec needs to be updated to drop that bit of the UI?
[18:42]  * mterry looks at all these postinsts
[18:42] <cjwatson> in fact, the majority of packages on my system that do this are conditional in sosme way
[18:42] <mpt> mterry, maybe
[18:43] <mpt> cjwatson, are you saying that determining whether an update will require a restart is equivalent to solving the Halting Problem? :-)
[18:43] <mterry> cjwatson, yeah...  mostly around whether the package is in use at the time it seems
[18:44] <mterry> mpt, is UI that says "this package *may* cause a reboot" awful?
[18:44] <mpt> mterry, no, that would be fine
[18:44] <mpt> imo
[18:44] <mpt> Then if it doesn't, yay, bonus
[18:44] <maco> hang on
[18:44] <maco> cause or require
[18:44] <mterry> maco, require
[18:44] <mterry> sorry
[18:45] <maco> k, cuz the way you wrote before sounds like microsoft's reboot-whether-you-want-or-not
[18:45] <mterry> maco, :)
[18:45] <mterry> mpt, I'll talk to mvo about the possibility of adding metadata for any package that can possibly flip the reboot required flag
[18:45] <mterry> cjwatson, thanks for the investigation!
[18:46] <mpt> In an ideal world that would be another step, i.e. "we're updating the sort of stuff where trying to use Ubuntu during the update process would be an absolute misery"
[18:46] <mterry> mpt, didn't we have an "updating on shutdown" plan at one point?
[18:47] <mpt> mterry, yes, it didn't go anywhere <https://wiki.ubuntu.com/FoundationsTeam/Specs/KarmicUpdatesOnShutdown>
[18:47] <mterry> mpt, your spec involves grouping packages.  Did you have ideas about the boundaries of that grouping?  (like, group packages from the same source?)  And throw anything without a .desktop into "Ubuntu Core"?
[18:49] <mterry> mpt, also the spec has a "to think about section" about how it would involve dropping the distinction between security and regular updates (and 3rd party).  Didn't know if that had rattled around in your brain since the spec was last updated
[18:50] <mpt> mterry, I didn't write it down, but by "Ubuntu Core" I meant "anything that's a dependency of ubuntu-desktop, but neither (a) a graphical application nor (b) only there because it's a dependency of one graphical application"
[18:51] <mpt> mterry, I haven't rattled recently, but yes, probably we should retain the security distinction somehow
[18:51] <mterry> mpt, does the phrasing of "Ubuntu Core" perhaps change now that we have a distinct spin of Ubuntu called Ubuntu Core?
[18:52] <mpt> mterry, probably
[18:52] <mterry> mpt, OK well, commence rattling when you get a chance.  :)
[18:52] <mpt> sure thing
[18:53] <melodie> hi again
[18:53] <melodie> cjwatson, I would like to ask you if you remember a patch you did on a program having for name "openbox-xdgmenu" ?
[18:53] <slangasek> we have a distinct spin of Ubuntu called Ubuntu Core?
[18:54] <slangasek> oh, you're talking about the one we already have ;P
[18:54] <melodie> slangasek, yes
[18:54] <jussi> slangasek: https://wiki.ubuntu.com/Core i think
[18:55] <melodie> https://wiki.ubuntu.com/Core
[18:55] <slangasek> so yes, there's a conflicting definition of Ubuntu Core, which is definitely not compatible with mpt's definition above
[18:55] <melodie> can that be used to make a spin ?
[18:55] <slangasek> there's very little spinning involved with https://wiki.ubuntu.com/Core ;)
[18:55] <melodie> I am looking for an elegant solution and for a howto if there is one.
[18:56] <mpt> It's a well-known fact that velocity of spinning increases as you get more distant from the core
[18:56] <slangasek> mpt: hah
[18:56] <mpt> I'll get me coat
[18:56] <melodie> and perhaps not that much the velocity of the final product ? or do I mistake
[18:56] <melodie> ?
[18:57] <melodie> else, can a Mini Ubuntu be used for that purpose ?
[19:17] <dholbach> ivoks, congratulations! :)
[19:17] <ivoks> dholbach: yay :)
[19:22] <broder> kicked off initial quantal lintian build. first report eta: 3 days
[19:23] <broder> for bonus points, it has a patch that should prevent it throwing unknown-field-in-control original-maintainer on any package we've modified
[19:23] <broder> s/any package we've modified/all packages/, actually
[22:14] <xnox> doko: i have a solution pointer on how to check packages in *all* ongoing transitions.
[22:15] <doko> xnox, already solved for my purposes
[22:16] <xnox> doko: ok. The transition tracker repository has a trasition, collision python script which can be trivially changed to print all packages in transitions which are good/bad/unknown
[22:16] <xnox> doko: that is all.
[22:17] <doko> xnox, I was pointed to http://release.debian.org/transitions/export/packages.yaml
[22:18] <xnox> doko: ok. that works as well ;-)
[22:19] <xnox> doko: would it be useful to add a script/program to query packages in transition in the `[ubuntu-]devscripts' ?
[22:20] <doko> xnox, I don't think so. there's always nbs, which you can consult
[22:20] <xnox> doko: ok.
[22:34] <Bluefoxicy> Does Ubuntu have an option to load the CD to RAM?
[22:34] <Bluefoxicy> or even better, auto-loading of the CD to RAM if you have more than, say, 2GB of RAM
[22:35] <Bluefoxicy> hmm how would that be done
[22:35] <ogra_> no ... patches accepted :)
[22:35] <Bluefoxicy> no I mean this is actually tough I just realized
[22:36] <Bluefoxicy> because in theory the ideal situation is to start copying everything to RAM, compressed, even after boot
[22:36] <ogra_> not as tough as you might think
[22:36] <ogra_> but it would be slow since you would have to copy the squashfs from CD to a tmpfs
[22:36] <Bluefoxicy> You don't want to wait 15 minutes for the whole CD to copy the SquashFS to RAM
[22:36] <broder> cat /cdrom/casper/filesystem.squashfs >/dev/null will probably get you some percentage of the way there :)
[22:36] <Bluefoxicy> ogra_: modprobe zram
[22:37] <ogra_> how does that help the IO ?
[22:37] <Bluefoxicy> zram makes a block device in RAM that's compressed :)
[22:37] <ogra_> zram only gets you more ram
[22:37] <Bluefoxicy> see the problem is if you copy the squashfs to a tmpfs, it stays compressed BUT you can't mount it through before it's done copying
[22:37] <ogra_> i know i use it on most of the arm images by default
[22:37] <broder> copy the squashfs from CD to a tmpfs> why would you do that instead of just using buffer cache?
[22:38] <lifeless> broder: well, I had a case where that woul dhave been useful
[22:38] <Bluefoxicy> broder:  remove the CD, cache everything ahead of time, etc
[22:38] <Bluefoxicy> and, if you say ... load X
[22:38] <lifeless> broder: I was shuffling partitions around, TB of data, pushed the CDROM right out of page cache
[22:38] <Bluefoxicy> the files that are mapped in are on the CD, and you can't swap that under
[22:38] <lifeless> so every time I moved the mouse it spun up
[22:38] <broder> fair enough
[22:38] <Bluefoxicy> the next computer I build is going to have 16GB of RAM and 2 open slots ready for another 16GB
[22:38] <Bluefoxicy> a CD is 700MB
[22:39] <Bluefoxicy> this is turning into a thing
[22:39] <Bluefoxicy> It's not a bad idea to arbitrarily say, "Well, we can load the CD to RAM, if the system has [8GB] then let's eat 2/3 of a gig for that"
[22:39] <Bluefoxicy> but anyway zram
[22:40] <ogra_> what about it ?
[22:40] <Bluefoxicy> you can make an ext2 fs on /dev/zram0, mount the squashfs, and copy its contents into the zram0
[22:40] <ogra_> we have support for it in all kernels and zram-config is in the archive
[22:40] <ogra_> +8providing the upstart job to initialize it)
[22:40] <ogra_> oh, i see what you are saying, you dotn use the zram device for swapping
[22:41] <Bluefoxicy> a modified unionfs would be able to copy the underlying file being read to the zram fs automatically, while also copying the entire contents of the base fs in as a background task (say on an ioctl)
[22:41]  * ogra_ didnt get that before, sorry
[22:41] <Bluefoxicy> that way you'd be able to use the target memory-based mount point as your root device immediately, and have it remain compressed in RAM
[22:41] <Bluefoxicy> albeit, CPU intensive
[22:41] <ogra_> well, machines with 16G should hve an equally powerful CPU
[22:42] <Bluefoxicy> but you could start booting immediately, you could wait until the desktop comes up to trigger the background copy or make it a low-priority task or whatnot
[22:42] <Bluefoxicy> yeah
[22:42] <Bluefoxicy> a 16G machine might have a Core I5 or I7 with 4 cores
[22:42] <Bluefoxicy> or it might be a server with 8 or 16 cores
[22:42] <ogra_> a server would probably rather use a netinst image though
[22:42] <Bluefoxicy> anyway what got me is I realized I can spend $60 on an OCZ SATA3 SSD 60GB
[22:42] <ogra_> (which isnt live)
[22:42] <Bluefoxicy> or buy two of those
[22:42] <Bluefoxicy> and stripe them
[22:43] <Bluefoxicy> at 6Gb/s theoretical (768MB/s, a whole CD in 1 second) and a little more than half a gig per second practical, doubled by striping
[22:43] <Bluefoxicy> you could install Ubuntu in under a second
[22:43] <Bluefoxicy> ... no, you're going to be waiting for the CD to spin that whole time.
[22:43] <Bluefoxicy> so during the entire boot process, if you have ridiculous amounts of RAM, the CD could be caching everything to RAM
[22:43] <ogra_> right, as i said, on such a device a local mirror and netinst would be cleverer
[22:44] <Bluefoxicy> ogra_:  I did say an SSD costs about $60 :P
[22:44] <Bluefoxicy> home users might not have local mirror/netinst but might have some ridiculously fast system with $100 of DDR3 in it
[22:45] <ogra_> (and indeed your argument stands and falls with the existance of a server livecd install :) )
[22:45] <ogra_> (which doesnt exist yet)
[22:45] <Bluefoxicy> well
[22:45] <Bluefoxicy> I'm talking about desktops
[22:47] <Bluefoxicy> I mean like
[22:47] <Bluefoxicy> http://www.amazon.com/Corsair-Vengeance-1600MHz-Memory-CMZ16GX3M2A1600C10/dp/B006EWUO22/
[22:48] <Bluefoxicy> http://www.amazon.com/gp/product/B004Z0S6RU/
[22:48] <Bluefoxicy> $120 + $70
[22:48] <Bluefoxicy> that's going to turn into "Common use case" :P
[22:48] <lifeless> Bluefoxicy: you can install Ubuntu extremely fast by mounting the iso over NFS w/netboot.
[22:48] <Bluefoxicy> lifeless:  if you have a second PC up yeah.
[22:48] <lifeless> Bluefoxicy: and syslinux's netboot mode.
[22:49] <lifeless> Bluefoxicy: there are some very very small PC's around these days... like android tablets ;)
[23:22] <stgraber> balloons: ping
[23:22] <stgraber> balloons: you've a session in grand ballroom a
[23:22] <stgraber> balloons: https://blueprints.launchpad.net/ubuntu/+spec/qa-q-iso-testing-process


[06:39] <brobostigon> morning boys and girls.
[06:51] <zmoylan-pi> o/
[06:52] <brobostigon> o/
[08:03] <knightw0rk> hey brobostigon
[08:03] <knightw0rk> how are you doing today
[08:03] <knightw0rk>  hey zmoylan-pi
[09:30] <SuperMatt> just ordered a new laptop \o/
[09:31] <SuperMatt> gonna install the daily image of 18.04 immediately
[09:31] <SuperMatt> minimal version too, because I don't need a lot of the stuff it comes with
[11:53] <NET||abuse> hm,, does anyone understand dockerfile's and VOLUME directives?
[11:54] <NET||abuse> when you do docker run -v /host/path:/container/path you are specifying all th epaths, so what does the VOLUME statement do in the dockerfile?
[12:22] <ujjain> NET||abuse, https://stackoverflow.com/questions/40163036/difference-between-volume-declaration-in-dockerfile-and-v-as-docker-run-paramet
[12:24] <SuperMatt> I think it's there so you can give hints to volumes that *should* be mounted before docker run
[13:12] <diddledan> yeah I think it's a metadata thing only
[13:13] <diddledan> aah that stackoverflow helps
[13:13] <diddledan> well done, ujjain :-)
[13:15] <ujjain> You´re welcome, I sometimes forget to google stuff too, but if you know the right keywords to search for, sometimes you find good answers
[13:22] <ujjain> my new name is Frank Aggot
[14:46] <SuperMatt> oops, just found my personal backups weren't backing up mysql correctly :/
[14:46] <daftykins> D:
[14:47] <SuperMatt> it was silently failing because I forgot to give the backup user select permissions!
[14:47] <SuperMatt> but it could still get some metadata out, but no actual data
[14:47] <SuperMatt> tonight's backup should be perfect though
[14:48] <SuperMatt> I'm prepping for next month when I switch to bionic
[14:48] <daftykins> i was doing a 7TB rsync the other day, somehow it was running at 133MB/sec over gigabit LAN... it smelled fishy so i breaked, only to see permission errors xD
[20:46] <diddledan> my ISP is struggling to contain a DoS
[20:49] <zmoylan-pi> fingers crossed it stops before the weekend...


[00:03] <wxl> no!
[00:04] <wxl> is that in ka-deps?
[00:08] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1016: SUCCESS in 8 min 13 sec: https://kci.pangea.pub/job/mgmt_merger/1016/
[00:09] <acheronuk> no, ka from https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/dev-tools-testing
[00:09] <acheronuk> kubuntu-automation 	2.1~beta5~ubuntu18.04~ppa5
[00:09] <wxl> ah
[00:10] <wxl> i had dev-tools
[00:12] <acheronuk> yeah, so it was reading bionic from the git branch, but could not match it against a series in that list
[00:13] <wxl> oh man it's dooooing something
[00:13] <acheronuk> :)
[00:13] <wxl> thanks a million Rik
[00:13] <acheronuk> must copy that over to the normal build
[00:14] <acheronuk> np
[00:14]  * acheronuk goes ZZZZzzzz....
[00:14] <wxl> nite
[00:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #52: STILL FAILING in 12 min: https://kci.pangea.pub/job/bionic_unstable_babe/52/
[00:27] <valorie> good lord what was rik still doing up?
[00:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:34] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ksirk build #57: FIXED in 24 min: https://kci.pangea.pub/job/artful_stable_ksirk/57/
[00:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ksirk build #103: FIXED in 28 min: https://kci.pangea.pub/job/artful_unstable_ksirk/103/
[00:43] <wxl> trying to help me i think
[00:44] <wxl> we've been trying to get autopkgtests to work in lxd so we could test fixes to excuses in our kontainers
[00:45] <valorie> sounds progressive!
[00:46] <valorie> lxd is the new hot whatever, right?
[00:47] <wxl> well yeah but afaik that's what the containers actually are
[00:48] <wxl> well, i like to call them kontainers
[00:48] <wxl> so we're running containers in the kontainers :)
[00:48] <valorie> so meta
[00:48] <wxl> i'm trying to keep the "portable development environment" idea working, as it allows me to be able to work on things wherever i'm at
[00:48] <wxl> in all honesty i could set it up (haven't yet) to do it on my phone
[00:49] <wxl> (i do have a bluetooth keyboard so that's not as crazy as it sounds)
[00:50] <wxl> if i can work from whatever wherever i'm at on whatever device i'm on then there's more room for me to sneak in some extra work
[00:50] <valorie> you are so hipster dude
[00:50] <wxl> i suspect that there are others that might appreciate this. at minimum, it reduces the drain virtual machines (and to a lesser degree, linux contianers) put on your local system
[00:51] <wxl> :/
[00:51] <valorie> lol
[00:51] <valorie> well, yes
[00:51] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kde-dev-scripts build #37: STILL UNSTABLE in 41 min: https://kci.pangea.pub/job/bionic_unstable_kde-dev-scripts/37/
[00:51] <valorie> those with weaky computers, or away from home, or have crap connections
[00:52] <wxl> right
[00:56] <wxl> YAY it worked
[00:57] <wxl> acheronuk: (when you're awake) 100% tests passed, 0 tests failed out of 66
[00:57] <valorie> \o/
[00:57] <tsimonq2> wxl: commit, push, give me the name of the repo, I can upload
[00:57] <valorie> are you fixing the docs as you go along?
[00:58] <wxl> yeah i'm going to do that valorie
[00:58] <valorie> awesomesauce
[00:59] <wxl> maybe i will just hand it to you and let you organize it. would that be cool, valorie ?
[00:59] <wxl> cuz we were going to put it here but that's technically it doesn't exactly fit the title
[00:59] <wxl> https://phabricator.kde.org/w/kubuntu/autopkgtests/staging_howto/
[00:59] <valorie> well, I can help
[00:59] <wxl> i'll do all the writing
[01:02] <valorie> one thing I notice there right off, is that it isn't specified where one runs commands, and it seems to me that that is a major issue
[01:02] <valorie> for everyone learning
[01:02] <wxl> right
[01:02] <wxl> well
[01:02] <wxl> i didn't write THAT one :)
[01:02] <valorie> understood
[01:02] <valorie> but that should be made clear IMO
[01:03] <valorie> obv Santa knows, but the newbie doesn't
[01:04] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kig build #37: STILL UNSTABLE in 54 min: https://kci.pangea.pub/job/bionic_unstable_kig/37/
[01:04] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #37: STILL UNSTABLE in 54 min: https://kci.pangea.pub/job/bionic_unstable_kstars/37/
[01:05] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #38: STILL UNSTABLE in 55 min: https://kci.pangea.pub/job/bionic_unstable_ark/38/
[01:05] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kcachegrind build #38: STILL UNSTABLE in 55 min: https://kci.pangea.pub/job/bionic_unstable_kcachegrind/38/
[01:08] <wxl> yeah the new one i write will be better, i promise
[01:08] <valorie> I made it a bit shorter and more grammatical
[01:08] <valorie> why do you need a new one?
[01:09] <valorie> can't you start with "another way to do this is: etc"
[01:09] <wxl> because his is about lxc, mine is about lxd
[01:09] <wxl> slight differennce
[01:09] <valorie> yes, and?
[01:10] <wxl> and then mine is about dealing with proposed excuses rather than staging tests
[01:10] <valorie> it's all about staging autopackage tests
[01:10] <valorie> ah, ok
[01:10] <valorie> well then
[01:10] <wxl> his is a little more proactive i think
[01:10] <wxl> "let's test before staging"
[01:10] <valorie> right
[01:10] <wxl> whereas in my case, we've already pushed things to proposed and they're stuck because of tests failing
[01:11] <wxl> so i found a potential fix and this was how i could test it before uploading it
[01:11] <valorie> his whole idea was to shorten the time we have to wait once packages are in Ubuntu infra
[01:11] <wxl> right
[01:11] <wxl> so it's probably still appropriate
[01:11] <wxl> maybe it might be better to retitle it about using containers to do autopkgtesting and then describe a couple scenarios
[01:12] <wxl> i was hoping to give a full example rather than a fill in the blanks sort of thing
[01:12] <valorie> sure
[01:12] <valorie> I'm about to either fix or go find dinner, so more later.....
[01:13] <wxl> yep sounds good. i may have to jet, too. my wee lady has a game tonight
[01:14] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #53: STILL FAILING in 9 min 9 sec: https://kci.pangea.pub/job/bionic_unstable_babe/53/
[01:16] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kcachegrind build #22: STILL UNSTABLE in 1 hr 6 min: https://kci.pangea.pub/job/bionic_stable_kcachegrind/22/
[01:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kalzium build #172: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/artful_unstable_kalzium/172/
[01:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_elisa build #32: STILL UNSTABLE in 1 hr 8 min: https://kci.pangea.pub/job/bionic_unstable_elisa/32/
[01:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_falkon build #35: STILL UNSTABLE in 1 hr 9 min: https://kci.pangea.pub/job/bionic_unstable_falkon/35/
[01:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_purpose build #33: STILL UNSTABLE in 1 hr 9 min: https://kci.pangea.pub/job/bionic_unstable_purpose/33/
[01:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_palapeli build #40: STILL UNSTABLE in 1 hr 9 min: https://kci.pangea.pub/job/bionic_unstable_palapeli/40/
[01:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalzium build #37: STILL UNSTABLE in 1 hr 9 min: https://kci.pangea.pub/job/bionic_unstable_kalzium/37/
[01:24] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkleo build #21: FAILURE in 4 min 53 sec: https://kci.pangea.pub/job/bionic_unstable_libkleo/21/
[01:28] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdev-python build #23: FAILURE in 9 min 0 sec: https://kci.pangea.pub/job/bionic_unstable_kdev-python/23/
[01:31] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ark build #41: STILL UNSTABLE in 1 hr 21 min: https://kci.pangea.pub/job/bionic_stable_ark/41/
[01:32] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kig build #41: STILL UNSTABLE in 1 hr 22 min: https://kci.pangea.pub/job/bionic_stable_kig/41/
[01:32] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_palapeli build #19: STILL UNSTABLE in 1 hr 22 min: https://kci.pangea.pub/job/bionic_stable_palapeli/19/
[01:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ark build #190: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/artful_unstable_ark/190/
[01:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_elisa build #171: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/artful_unstable_elisa/171/
[01:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #238: STILL UNSTABLE in 56 min: https://kci.pangea.pub/job/artful_unstable_kstars/238/
[01:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkleo build #22: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/bionic_unstable_libkleo/22/
[01:38] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdev-python build #24: STILL FAILING in 4 min 47 sec: https://kci.pangea.pub/job/bionic_unstable_kdev-python/24/
[01:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_libkleo build #163: FIXED in 1 hr 7 min: https://kci.pangea.pub/job/artful_stable_libkleo/163/
[01:45] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kalzium build #37: STILL UNSTABLE in 1 hr 35 min: https://kci.pangea.pub/job/bionic_stable_kalzium/37/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_k3b build #44: STILL UNSTABLE in 41 min: https://kci.pangea.pub/job/bionic_unstable_k3b/44/
[01:58] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #126: STILL UNSTABLE in 53 min: https://kci.pangea.pub/job/artful_stable_ark/126/
[01:58] -kubuntu-ci:#kubuntu-devel- Project artful_stable_cantor build #89: STILL UNSTABLE in 54 min: https://kci.pangea.pub/job/artful_stable_cantor/89/
[02:00] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:00] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #194: FIXED in 46 min: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/194/
[02:05] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmail build #240: STILL FAILING in 4 min 48 sec: https://kci.pangea.pub/job/artful_unstable_kmail/240/
[02:06] <mparillo> I thought I noticed KDE Frameworks 5.41 starting to land in BB. Usually I would check http://gpul.grupos.udc.es/ka-iron-hand_reports/frameworks_archive/5.41_bionic_proposed_migration.pdf but I guess that is still being recovered.
[02:10] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #41: STILL UNSTABLE in 1 hr 5 min: https://kci.pangea.pub/job/bionic_stable_cantor/41/
[02:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmail build #241: STILL FAILING in 4 min 41 sec: https://kci.pangea.pub/job/artful_unstable_kmail/241/
[02:23] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktnef build #24: STILL FAILING in 23 min: https://kci.pangea.pub/job/bionic_unstable_ktnef/24/
[02:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdepim-addons build #235: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/artful_unstable_kdepim-addons/235/
[02:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktnef build #25: STILL FAILING in 14 min: https://kci.pangea.pub/job/bionic_unstable_ktnef/25/
[02:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kldap build #147: FIXED in 18 min: https://kci.pangea.pub/job/artful_unstable_kldap/147/
[02:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_calligra build #37: STILL FAILING in 1 hr 4 min: https://kci.pangea.pub/job/bionic_unstable_calligra/37/
[02:56] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkleo build #154: FAILURE in 3 min 43 sec: https://kci.pangea.pub/job/artful_unstable_libkleo/154/
[03:04] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_calligra build #152: STILL FAILING in 1 hr 17 min: https://kci.pangea.pub/job/artful_unstable_calligra/152/
[03:04] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkleo build #155: STILL FAILING in 3 min 39 sec: https://kci.pangea.pub/job/artful_unstable_libkleo/155/
[03:38] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdepim-addons build #56: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/bionic_unstable_kdepim-addons/56/
[03:54] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_calligra build #38: STILL FAILING in 56 min: https://kci.pangea.pub/job/bionic_unstable_calligra/38/
[04:07] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_calligra build #153: STILL FAILING in 57 min: https://kci.pangea.pub/job/artful_unstable_calligra/153/
[04:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-framework build #149: FAILURE in 4 min 56 sec: https://kci.pangea.pub/job/artful_unstable_plasma-framework/149/
[04:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #75: STILL FAILING in 24 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/75/
[04:24] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-framework build #150: STILL FAILING in 3 min 45 sec: https://kci.pangea.pub/job/artful_unstable_plasma-framework/150/
[04:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_purpose build #163: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_unstable_purpose/163/
[04:41] <tsimonq2> .ir
[04:41] <tsimonq2> whoops
[04:56] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #76: STILL FAILING in 32 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/76/
[05:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-framework build #35: FAILURE in 5 min 30 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-framework/35/
[05:26] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-framework build #36: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-framework/36/
[07:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ki18n build #34: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/bionic_unstable_ki18n/34/
[08:02] <wxl[m]> valorie: I'm done, though I'll probably add a wee bit more for completeness. I did this in a format that reads more like a story and I think is instructive, especially for the white belts. Might be good for a tutorial as we discussed last meeting with Sick_Rimmit
[08:09] <acheronuk> wxl[m]: no ketxteditor upload yet?
[08:11] <valorie> wxl - on that same page?
[08:11] <wxl[m]> acheronuk: naw, had some other things going on. Was going to do it tonight real quick but by the time I was done with other responsibilities and the documentation, bandwidth sucked and so using the kontainer didn't work well. Will do it in the morning
[08:12] <acheronuk> wxl[m]: no probs
[08:12] <wxl[m]> valorie: yep. That may not be the right decision, but I kind of added some headings and generalized the title to make it fit
 (Document) https://irc-attachments.kde.org/pmxBNMoV/file_3805.pdf
[08:13] <wxl[m]> valorie: feel free to do with it what you wish XD
[08:16] <valorie> looks pretty good as it is, but I'll mess with it tomorrow
[08:16] <valorie> heading to bed pretty soon
[08:18] <wxl[m]> Sleep time here too
[08:19] <wxl[m]> On my way out with this on
[08:19] <wxl[m]> http://pulseemitter.bandcamp.com/album/meditative-music-1-5
[08:20] <wxl[m]> Enjoy 🙏🏽
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1959: SUCCESS in 1 min 3 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1959/
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1959: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1959/
[09:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1959: SUCCESS in 3 min 51 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1959/
[12:18] <BluesKaj> Howdy folks
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1960: SUCCESS in 55 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1960/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1960: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1960/
[15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1960: SUCCESS in 3 min 46 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1960/
[17:29] <wxl> tsimonq2: pushed the change. should i just uploadsource or does this need to explicitly go in a ppa?
[17:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #415: FAILURE in 54 sec: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/415/
[17:29] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktexteditor build #47: FAILURE in 1 min 34 sec: https://kci.pangea.pub/job/bionic_unstable_ktexteditor/47/
[17:31] <wxl> s/a \(ppa\)/my personal \1/
[17:33] <acheronuk> wxl: needs a ubuntu2 changelog
[17:33] <wxl> oh foo!
[17:33] <wxl> i bothered to fix the header on the patch but forgot the changelog ugh
[17:33] <acheronuk> it happens. to all of us
[17:34] <wxl> the tooling needs to warn us XD
[17:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #416: STILL FAILING in 35 sec: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/416/
[17:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktexteditor build #48: STILL FAILING in 49 sec: https://kci.pangea.pub/job/bionic_unstable_ktexteditor/48/
[17:35] <acheronuk> wxl: to be fair, the tooling does not know it that is the only commit needed. or is only the first of several before and new released version is done
[17:36] <wxl> i know
[17:36] <acheronuk> and not all commit need an entry
[17:36] <wxl> alias git=read -p "are you sure you didn't forget anything?????? && git
[17:36] <acheronuk> lol
[17:38] <wxl> ugh amend is forcing me to merge
[17:38] <wxl> how is that.... possible?
[17:39] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #144: FAILURE in 10 min: https://kci.pangea.pub/job/artful_unstable_ktexteditor/144/
[17:40] <acheronuk> just add another commit with the c/l. not a bit deal
[17:40] <wxl> bah
[17:40] <acheronuk> s/bit/big
[17:44] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #145: STILL FAILING in 46 sec: https://kci.pangea.pub/job/artful_unstable_ktexteditor/145/
[17:46] <wxl> fixed
[17:46] <wxl> one upped harold on the commit message tho https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ktexteditor/commit/?id=0d609bbc9cde939dd7af1868932c05d85df4d3cb
[17:47] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #146: STILL FAILING in 35 sec: https://kci.pangea.pub/job/artful_unstable_ktexteditor/146/
[17:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #417: STILL FAILING in 37 sec: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/417/
[17:47] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktexteditor build #49: STILL FAILING in 1 min 6 sec: https://kci.pangea.pub/job/bionic_unstable_ktexteditor/49/
[17:48] <wxl> in other news i was thinking that entry i wrote on the wiki would be great for a blog entry. then maybe i could distill only the essentials on that page, with a link to the blog. thoughts? (esp valorie)
 sitter: ^ lol
[17:50] <wxl> @tsimonq2: see my ? about the upload
 @wxl, I thought acheronuk answered?
[17:52] <wxl> @tsimonq2: did i miss it? i thought he just told me i forgot the changelog :)
 @wxl, You can't upload to the archive, remember?
[17:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #147: STILL FAILING in 36 sec: https://kci.pangea.pub/job/artful_unstable_ktexteditor/147/
[17:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #418: STILL FAILING in 49 sec: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/418/
[17:53] <wxl> uploadsource uploads it to the kubuntu ppa, no?
[17:54] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktexteditor build #50: STILL FAILING in 1 min 7 sec: https://kci.pangea.pub/job/bionic_unstable_ktexteditor/50/
[17:54] <acheronuk> wxl: that should be UNRELEASED, not bionic
[17:54] <wxl> sigh
[17:55] <acheronuk> our gbp-archive tooling adds the UNRELEASED --> bionic bit
[17:55] <wxl> ah
[17:56] <wxl> ok fixed
[17:56] <acheronuk> gbp-archive laso git tags the release version at the same time
[17:56] <wxl> with apologies
[17:56] <acheronuk> *also
[17:56] <acheronuk> wxl: no probs. it's not that obvious
[17:57] <wxl> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ktexteditor/commit/?id=66014e2cd2f5484a509ef1b6e3049fb1d3116498
[17:57] <wxl> i mean the apologies are in the commit message
[17:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #419: STILL FAILING in 37 sec: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/419/
[17:57] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktexteditor build #51: STILL FAILING in 45 sec: https://kci.pangea.pub/job/bionic_unstable_ktexteditor/51/
 @wxl, You can revert commits and force push if you want...
[17:58] <wxl> @tsimonq2: that would mean no need for emojis :(
[17:58] <wxl> @tsimonq2: so kubuntu ppa?
[17:58] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #148: STILL FAILING in 1 min 23 sec: https://kci.pangea.pub/job/artful_unstable_ktexteditor/148/
 @wxl, If you feel inclined, otherwise acheronuk can upload
[17:58] <wxl> uploaded
[18:00] <acheronuk> ok. so now you can (a) let me or simon run gbp-archive to make the source for us to sponsor the upload to archive, or (b) you run that locally with 'gbp-archive -- -uc -us' where you have a gpg key, to tag it, then upload the made sources to somewhere we can sign
[18:01] <wxl> acheronuk: you can do that with what's in the ppa, right?
[18:01] <acheronuk> note: you can't remote gpg tag on linode while running gbp-archive, so needs to be done locally
[18:01] <acheronuk> wxl: I can
[18:01] <wxl> k all yours then :)
[18:01] <acheronuk> well, with what is in git
[18:01] <wxl> k
[18:02] <acheronuk> no probs. just if you are doing a whole load, you might want to build the sources laocally, git tag, then give them to one of us to remote sign. no big deal
[18:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #420: STILL FAILING in 35 sec: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/420/
[18:03] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktexteditor build #52: STILL FAILING in 35 sec: https://kci.pangea.pub/job/bionic_unstable_ktexteditor/52/
[18:03] <wxl> gbp-archive does the build/tag, no? then it should be put in a personal ppa, on?
[18:03] <wxl> s/ on/ no/
[18:04] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #149: STILL FAILING in 36 sec: https://kci.pangea.pub/job/artful_unstable_ktexteditor/149/
[18:05] <acheronuk> gbp-archive is for archive uploads (release to archive)
[18:07] <acheronuk> wxl: https://launchpad.net/ubuntu/+source/ktexteditor/5.41.0-0ubuntu2
[18:08] <wxl> yay thx Rik :)
[18:08] <acheronuk> wxl: see: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ktexteditor/commit/?h=kubuntu_bionic_archive&id=258beda2448a6d78201171180e22399b1a818ccd
[18:09] <acheronuk> that is what gbp-archive does when being run
[18:09] <wxl> ahhh
[18:10] <acheronuk> yep. so you keep int unreleased until that is run
[18:10] <acheronuk> for packages we use this tooling for, anyway
 wxl: https://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsoree=Walter+Lapchynski&sponsoree_search=name … Bookmark that.
[18:14] <wxl> oooh what's this??
[18:14] <wxl> hah ubuntu-dev on alioth i love it
 @wxl, There's a database with all Ubuntu and Debian uploads. That's just a web view of it.
[18:16] <acheronuk> https://launchpad.net/~wxl/+related-packages
[18:17] <acheronuk> no fix for gwenview yet. tempting to just ignore that tes
[18:17] <acheronuk> *test
 Oh that too
 wxl: Challenge: get konquorer or however it's spelled to migrate.
[18:19] <acheronuk> hehe. yeah. I put that off
[18:19] <acheronuk> hoping for a fix, but seems like no-one cares
[18:23] <acheronuk> wxl: as a note. I might have put: "Upstream patch: can be dropped in 5.42" in that changelog. but hey, no big deal
[18:24] <acheronuk> but now unstable branch for KCI needs fixing, as KCI source build will barf on that patch using upstream git where it already exists
[18:25] <acheronuk> ^^^^ that is the bit Simon rarely fixes
[18:25]  * acheronuk hides
[18:30] <wxl> acheronuk: good point!
 @acheronuk, But that's me leaving stuff for wxl :P
[18:36] <acheronuk> yeah. pull the other one. it has jingle bells on it :P
[18:36] <wxl> oh? is that something i can help with?
 @wxl, Yes
[18:59] <wxl> well ok, what do i do?
 @wxl, kci.pangea.pub and find the unstable broken jobs
 Help there
[19:07] <wxl> ok great i found it
[19:07] <wxl> and how do i fix it?
[19:08] <acheronuk> wxl: well, you applied a patch. KCI auto merged that patch into the kubuntu_unstable branch, where as it builds from upstream master git, it fails to apply as it's already in the source it pulls
[19:08] <wxl> so i should pull kubuntu_bioic_unstable and remove it??
[19:08] <acheronuk> do you need to drop the patch in the kubuntu_unstable branch, as it's applied upstream
[19:09] <wxl> ok
[19:09] <acheronuk> just kubuntu_unstable. we only have one generic branch for that
[22:57] <valorie> wxl, I think what you wrote as a blog post would be great
[22:58] <valorie> and links between the post and the phab would be good, as the phab can be updated if links or details change
[23:00] <valorie> I'll hold off on messing with your part of that page until you pull off the blog post and whittle down the phab entry


[20:56] <edve98> does anybody know if it is ok to report a papercut upstream if I can reproduce it myself?
[20:57] <edve98> I'm trying to triage it and it seems like it would save quite a lot of time. But guide says that original poster should report it himself
[21:10] <hjd> edve98: Presumably the idea is that the original reporter knows most about the issue and is best fit to forward it. Though, if you are able to reproduce it and upstream doesn't know about it already, it might be better that someone forwards it. :)
[21:10] <hjd> edve98: Do you have a bug number?
[21:17] <hjd> (In any case, I would check the upstream bug tracker if they already have a corresponding bug report for the problem already)
[21:18] <adueppen> hjd: I also have a question, when improving a bug report marked as incomplete, should I just edit the original report with the steps to reproduce?
[21:23] <hjd> adueppen: Depends on the original report. Do you have an example bug number? (Did you report it originally?)
[21:23] <adueppen> hjd: I was not the one to report it originally, it's #1447038
[21:24] <hggdh> bug 1447038
[21:24] <adueppen> oh right I keep forgetting how to activate the bot
[21:27] <hggdh> adueppen: if it is the same issue, feel free to add the steps to reproduce in the bug.
[21:27] <hggdh> huh. seems I conflated two questions in one almost correct answer
[21:28] <hggdh> hjd: the above applies to you (mostly)
[21:28] <hggdh> ah. I give up. hjd -- disregard
[21:29]  * hjd is confused
[21:29] <hggdh> hjd: awfully sorry. Seems I need sleep
[21:29] <hggdh> but the answer is, still, correct :-)
[21:30] <hjd> Ok :)
[21:30] <edve98> hjd: it's #1490189
[21:30] <hjd> bug 1490189
[21:30] <hggdh> TZ lag, and all that
[21:32] <hjd> edve98: Hm.. look at the merge request. It looks like this has been fixed upstream (and in Ubuntu too), though I don't have time to double check right now.
[21:32] <edve98> hjd: it's still present on Ubuntu atm
[21:34] <hggdh> edve98: which Ubuntu version?
[21:34] <hjd> Looks like the patch should work at least. Did you check with the latest version?
[21:35] <edve98> whoops, I forgot to do that
[21:36] <edve98> hjd: if it won't be present, what should I do then?
[21:39] <hjd> edve98: If the bug is fixed in a newer version available in Ubuntu, it is considered Fix Released. Depending on the severity, it might also need to be fixed for older versions in currently supported releases of Ubuntu. See examples/more information https://wiki.ubuntu.com/Bugs/Responses#Fixed_in_Development_release_while_still_existing_in_a_previous_release
[21:40] <hjd> When it comes to an url in a manpage, that's probably low priority, so I don't think it will be fixed in older releases as well.
[21:40] <hjd> (I've started watching a movie now, so I might take some time responding)


[07:21] <dpm> good morning
[07:27] <jokerdino> morning there. :)
[07:30] <dpm> hey jokerdino
[07:33] <jokerdino> i had a chat with my translation team since we last discussed it.
[07:33] <jokerdino> they apparently said they were more involved in translating upstream than here.
[07:34] <jokerdino> which i think is understandable. but what i don't understand is that, there are still no progress in the precise status.
[07:34] <jokerdino> the upstream translation is auto updated or manual?
[07:34] <dpm> jokerdino, upstream translations are automatically imported
[07:35] <jokerdino> that just makes things more gloomy.
[07:36] <jokerdino> upstream translations are close to completion but Ubuntu's is way below near completion.
[07:59] <dpm> jokerdino, is there any particular package that you've noticed it's done upstream and not in Ubuntu?
[08:00] <dpm> What I mean is, we need detailed info to investigate if anything is happening
[08:00] <dpm> so the more detailed, the more likely we can solve the problem if there is any
[08:04] <jokerdino> > debian installer is more or less completely updated.
[08:04] <jokerdino> yet it still has incompleted strings in Ubuntu. (https://translations.launchpad.net/ubuntu/precise/+lang/ta)
[08:05] <jokerdino> and i see that most of the incompleted ones are Ubuntu specific apps.
[08:05] <jokerdino> like ubuntu one and checkbox
[08:09] <dpm> jokerdino, cool, more info makes things easier, thanks :-) debian-installer is a special case, as it's manually imported due to the differences on how the translations are handled at the technical level, so it's just a matter of time before upstream translations are imported. But yeah, it seems upstream translations in Launchpad are in pretty good shape, and your team would need someone to focus on the Ubuntu-specific templates
[08:11] <jokerdino> right. that clears things.
[08:11] <jokerdino> we have about two months before the translation string freeze...
[08:13] <dpm> yeah, I think it might be worth starting anyway. Some of the strings might change, but it's unlikely that they all will do, and that should help you in getting organized and advancing some work
[08:15] <jokerdino> and, do you know where i should be looking for help regarding the mailing lists? I have problem seeing the Tamil messages...
[08:16] <dpm> jokerdino, what problem do you have exactly?
[08:16] <jokerdino> All Tamil messages just appear as question marks.
[08:17] <jokerdino> I can only read the ones sent in English.
[08:18] <jokerdino> I am not sure if it can be tuned in the browser setting.
[08:18] <dpm> jokerdino, can you send me a link to one of those messages?
[08:21] <jokerdino> Where do I find the link for the message?
[08:22] <jokerdino> https://lists.ubuntu.com/archives/ubuntu-tam/2012-January/001202.html
[08:22] <jokerdino> Ah, that is the discussion thread.
[08:23] <dpm> looking now...
[08:23] <jokerdino> I can see the messages in that link. But, when I receive an email, I can't see the messages.
[08:24] <dpm> jokerdino, it might be an issue with your e-mail client. Have you tried asking on the list, if anyone is experiencing the same problem?
[08:24] <jokerdino> one of them said, here in the chat, that they had to alter some settings in the browser. But, they weren't too sure about which one that was.
[08:25] <jokerdino> I use Gmail web client.
[08:25] <dpm> jokerdino, there are some settings to use UTF-8 encoding by default, you can try that
[08:27] <jokerdino> I tried those before... they gave some other funny characters.
[08:27] <jokerdino> may be i will just visit the online lists archives. i didn't know such a thing existed before.
[08:29] <dpm> jokerdino, or you might want to try to choose another encoding
[08:30] <jokerdino> sure, i will try them and get it fixed sooner.
[08:31] <jokerdino> BTW, I have nominated myself for the next moderator election on AU..
[08:31] <jokerdino> Aye or Nay?
[08:34] <dpm> what's AU?
[08:35] <jokerdino> Oh hmm Ask Ubuntu
[08:35] <dpm> ah, cool
[08:37] <TLE> dpm: hey, how goes with the django deployment?
[08:37] <TLE> and ... goodmorning
[08:37]  * TLE remembers my lessons in polite interaction with other people ;)
[08:38] <jokerdino> TLE:  that should be quite enriching.
[08:38] <TLE> jokerdino: yeah
[08:39] <jokerdino> usually, if you throw in a lot of smileys in an online convo, you will sound less rude.
[08:39] <dpm> morning TLE :)
[08:40] <jokerdino> oh my. i forgot the ubuntu dev classes.
[08:40] <jokerdino> BBL people.
[08:40] <dpm> TLE, I was trying to set up the django server again last night, but got stuck with some juju issues, I've asked the right people and I'm waiting for a response
[08:41] <dpm> (just a quick FYI)
[08:41] <TLE> dpm: ahh great, don't mean to be pushing, just looking forward to it
[08:44] <dpm> yeah, no worries, I just thought by using juju it would be quick, but it seems it's still got a few things that need ironing out
[08:44] <jokerdino> apparently, i don't know the exact timings of ubuntu dev classes. :/
[08:45] <jokerdino> i misread the UTC timing as my local timing.
[08:45] <jokerdino> in any case, BBL
[08:45] <dpm> jokerdino, Ubuntu Developer Week starts later on, in a few hours
[08:45] <dpm> well, it started yesterday, today it's day 2
[08:46] <TLE> dpm: yeah off course, it makes sense with some in house testing when there is the chance for it
[08:47] <jokerdino> well, yeah, now i know it. :(
[08:47] <TLE> jokerdino: there are always the IRC logs if you missed something
[08:48] <jokerdino> what's the fun in that?
[08:48] <jokerdino> oh i forgot the smiley face.
[08:48] <jokerdino> :D
[08:48] <jokerdino> anyways, this is really off topic.
[08:49] <jokerdino> let's just stick with the translation matters.
[08:49] <TLE> jokerdino: I think that is ok, we usually don't get swamped with translation matters
[08:50] <jokerdino> oh hmm
[08:51] <jokerdino> dpm: reading up on the previous messages from my translation team that i failed to read, the current leader suggests that the new leader should best be in Tamil Nadu. For the sake of collecting CDs and organizing things in the field.
[08:51] <jokerdino> Context: Tamil is mainly spoken in Tamil nadu, India and I am currently living in Singapore.
[08:53] <jokerdino> more context: i was proposing to him that i be the next leader. which he said might not be the best decision going forward. instead he suggests that i can be leading the team in singapore.
[08:53] <dpm> jokerdino, being at the same place is generally not a requirement for a translation team leader: for a while, I was leading the Catalan translation team while living on another country
[08:54] <jokerdino> well yeah.
[08:54] <dpm> jokerdino, it might make sense for the LoCo team leader, but afaik if the current leader is not active and not organizing these potential local events, and you're active and eager to drive the translation team forward, you should be the best candidate for the job
[08:55] <dpm> also the translation team lead is not the same as the loco team lead (though he/she can be)
[08:55] <jokerdino> you make sense.
[08:55] <jokerdino> but in our case, the translation team and the loco team is just the same.
[08:55] <jokerdino> just with different names.
[08:56] <jokerdino> i am guessing he probably misunderstood me.
[08:56] <dpm> as far as I understand it from previous conversations, the current Tamil Ubuntu translation team is dormant, so it might be worth separating it from the loco and infuse some energy into it
[08:56] <dpm> it's not like separating, it's distributing work
[08:57] <dpm> which is the beauty of Ubuntu and the community
[08:57] <dpm> so for me, if no one is actively leading the translation team, it makes very much sense to have someone new picking it up
[08:57] <jokerdino> both the loco and the translation team are dormant.
[08:58] <dpm> oh :(
[08:59] <jokerdino> i will get back to them and clarify that i was only nominating myself for the translation team and not the loco team.
[08:59] <dpm> yeah, that sounds great. Let me know if I can help in any way
[09:00] <jokerdino> one more thing, are there any prerequisites for someone to be a leader of the translation team?
[09:01] <jokerdino> why i am asking this is because i am not currently active translating, because the lack of support and activity kinda makes me demotivated.
[09:01] <dpm> the prerequisites are actually simple and pretty common sense ones. Let me dig out the url where we explain this...
[09:03] <dpm> jokerdino, here you are: https://wiki.ubuntu.com/Translations/KnowledgeBase/TeamCoordinatorResponsibilities
[09:03] <jokerdino> thanks!
[09:05] <dpm> no worries, if there is anything I or the rest of the translations community can do to help, feel free to ask here or on the ubuntu-translators mailing list
[09:08] <jokerdino> thanks. i am on the mailing list.
[09:09] <dpm> excellent, so one requirement for becoming a translation team leader ticked off the list ;-)
[09:10] <jokerdino> ;D
[14:05] <trijntje> dpm: are there still plans to open up some universe packages for translation? The dutch team is doing a huge revision of virtualbox, it would be nice if those could be included in the LTS
[16:58] <kelemengabor1> dpm: ping, is it meeting time yet?
[16:59] <dpm> kelemengabor1, argh, I thought it was tomorrow!, let me check!
[16:59] <kelemengabor1> IIRC wednesday is today :)
[16:59] <dpm> I've just finished a call, just a sec...
[17:00] <dpm> yeah, it's definitely wednesday :)
[17:01] <dpm> let me quickly pull the agenda...
[17:02] <dpm> kelemengabor1, give me 2 mins and then we can start
[17:03] <kelemengabor1> sure. I just pinged andrejz
[17:05] <dpm> excellent, thanks
[17:06] <dpm> kelemengabor1, ok, invite sent
[17:22] <dpm> kelemengabor1, https://wiki.ubuntu.com/Translations/KnowledgeBase/#Special_translations