[06:22] <hikiko> hi
[06:44] <pitti> Good morning
[06:47] <hikiko> hi pitti
[07:47] <om26er> Hi! is there a way to delay the startup of unity-settings-daemon ? one my system seems to be too fast to wait for themes/font to load correctly. I have to logout and login again to make things correct.
[07:47] <pitti> if you log out, u-s-d will be stopped as well, and restarted on login
[07:50] <om26er> pitti, hmm, so maybe I am looking at it the wrong way. I am actually trying to workaround bug 1369251
[07:51] <om26er> if I wait for the password screen like 2-3 seconds and then enter my password, things show up nicely. Its only when I enter my password as soon as lightdm shows that issue happens.
[07:54] <Trevinho> Morning
[08:56] <willcooke> morning all
[08:58] <willcooke> hey Trevinho, good news on the launcher at the bottom then :)
[09:02] <Laney> hi!
[09:02] <willcooke> morning laney
[09:07] <Laney> what is up
[09:11] <Laney> mhall119: I tried to say in the mail - file a bug, attach the icon, tag it appstream, subscribe ubuntu-sponsors, *send it upstream*
[09:17] <willcooke> grumble grumble.  My RasPi 3 order remains "unfulfilled"
[09:18] <davmor2> willcooke: steal popey he won't mind
[09:18] <willcooke> :)
[09:50] <seb128> good morning desktopers!
[09:50] <willcooke> hey seb128, how goes?
[09:51] <seb128> willcooke, hey, good! how are things here?
[09:51] <willcooke> seb128, so far, so good
[09:51] <seb128> I had a banck appointment but that took a bit longer than I though
[09:52] <willcooke> ain't no thing, you were still here when I left last night
[09:52] <willcooke> anything more on the PK discussions?
[09:54] <seb128> not really no
[09:54] <seb128> would be nice to get the update in
[09:54] <seb128> but we are not changing our course of action for g-s
[09:54] <willcooke> cool
[09:54] <willcooke> makes sense to me
[09:58] <Laney> hey seb128
[09:58] <Laney> how was the bank robbing?
[09:58] <Laney> oh shit this isn't our encrypted line
[10:02] <seb128> Laney, I told them to stop robbing me!
[10:02] <seb128> he needs to ask his boss what they can do
[10:02] <Laney> is this france?
[10:03] <seb128> but basically I was complaining about the credit card charges when travelling out of the eurozone
[10:03] <seb128> yes
[10:03] <seb128> and the cost of the card
[10:03] <Laney> get didrocks on your side
[10:04] <seb128> yeah, I told the bank that I would probably get an account at the same online bank if they couldn't make an effort
[10:04] <seb128> those bank give you a visa premium for free and charge half of what the normal banks do
[10:04] <seb128> that was the banking news of the day ;-)
[10:05] <Laney> you badass
[10:06] <seb128> looks like robert_ancell had another busy g-s day
[10:07] <seb128> no love for my gnome-calendar ffe :-/
[10:09] <davmor2> seb128: oh is it a bug if so I bet I can make it more popular with one comment
[10:11] <seb128> thanks but don't worry, I'm sure it's going to be reviewed ;-)
[10:22] <Trevinho> willcooke:  yeah great news
[10:26] <seb128> hey Trevinho!
[10:33] <popey> davmor2: sadly my rpi3 isn't currently being used because we don't have a snappy image for it yet.
[10:33]  * popey glares at ogra_
[10:33] <ogra_> blame DHL
[10:33] <ogra_> :P
[10:34] <ogra_> i ordered two yesterday, should be here before the weekend i guess so i can take a look then
[10:34] <ogra_> if the changes arent to massive i should have something by monday
[10:35] <davmor2> ogra_: pfff poor excuse ;)
[10:36] <ogra_> haha
[11:42] <seb128> Laney, where is appstream getting it packages descrptions translations from?
[11:42] <seb128> is the name/subtitle the info from the .desktop?
[11:46] <seb128> Laney, thanks for the calendar ffe
[11:48] <Laney> yeah think so
[11:49] <Laney> or the appdata
[11:50] <seb128> Laney, is it likely that it doesn't play well with our build tools stripping the inlines translations from .desktop to use gettext?
[11:50] <seb128> I'm trying to figure out why many important pacakges don't have their title translated
[11:50] <seb128> eog to take an example
[11:50] <seb128> they show translated in the dash and in software-center
[11:50] <Laney> probably
[11:51] <seb128> :-/
[11:51] <Laney> That's an X- keyword in desktop files isn't it
[11:51] <seb128> X-Ubuntu-Gettext-Domain=eog
[11:51] <seb128> yeah
[11:51] <Laney> So you have to teach tools about it
[11:52] <seb128> what $tools would be?
[11:52] <seb128> I've no idea about that stack
[11:52] <seb128> are the datas collected on package build time?
[11:52] <Sweet5hark1> desrt: https://www.google.com/trends/explore#q=%22move%20to%20canada%22&geo=US&date=today%2012-m&cmpt=q&tz=Etc%2FGMT-1 <- dunno why that happens there in the us, but "blame canada" seems to be replaced by "move to canada" in recent weeks for some reason ...
[11:52] <seb128> could we get it from the .desktop before it's stripped down?
[11:52] <seb128> Sweet5hark1, lol
[11:53] <seb128> Sweet5hark1, Canada is the new U.S ;-)
[11:54] <Laney> https://github.com/ximion/appstream-dep11/blob/master/dep11/parsers.py#L78
[11:54] <Laney> so you probably have to load up the langpacks and then try to translate the string using the domain given
[11:59] <seb128> thanks
[12:00] <seb128> I'm going to start by filling a bug I guess
[12:03] <desrt> moin
[12:05] <willcooke> hi desrt
[12:05] <Sweet5hark1> desrt: moin
[12:06] <desrt> good morning, willcooke, Sweet5hark1
[12:15] <willcooke> andyrock, are these two fixed now with the changes you made?
[12:15] <willcooke> https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1368896
[12:15] <willcooke> https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1354134
[12:15] <willcooke> fixed/otherwise resolved
[12:16] <Sweet5hark1> seb128: how do I find out which commit of the xenial seed a daily image was build upon?
[12:23] <seb128> hey desrt
[12:23] <seb128> Sweet5hark1, no idea, ask on -devel maybe?
[12:23] <Laney> d€$rt
[12:23] <Laney> Sweet5hark1: look at the manifest
[12:23] <Laney> then you can see which version of ubuntu-desktop it contains
[12:25] <desrt> morning, seb
[12:25] <desrt> and £4n3y
[12:26] <andyrock> "morning"
[12:26] <andyrock> willcooke: i don't think so
[12:32] <Sweet5hark1> Laney: thanks.
[12:35] <Laney> Sweet5hark1: manifest is on cdimage next to the iso fwiw
[12:38] <Sweet5hark1> looking at the manifest, I find ubuntu-desktop 1.348 there, uploaded by robert_ancell on 2016-02-17, so it cant have my changes to the xenial seed at rev. 2418 on 2016-02-22. Seeing that ubuntu-meta 1.348 was released on -02-17 and before that 1.347 was on -02-01, Im having hope this will soon be updated.
[12:42] <Laney> Sweet5hark1: it would have been usual for the person pushing to also do the meta
[12:42] <Laney> I wouldn't hope, because you could wait an arbitrary length of time :)
[12:42]  * Laney will do that for you
[12:42] <Sweet5hark1> Laney: oh, thanks a lot!
[12:43] <Laney> it's mostly just running ./update
[12:45] <Laney> uuuuuuuuuuuuuuuuuh it didn't get the new thing
[12:46] <Laney> probably needs to be promoted
[12:49] <Laney> seb128: want to promote libreoffice-style-breeze to make Sweet5hark1 happy?
[12:50] <seb128> Laney, Sweet5hark1, done
[12:50] <Sweet5hark1> seb128: thx
[12:50] <seb128> yw!
[12:50] <Laney> ♥
[13:36] <willcooke> Laney, I've got the greyscales now too: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1551208
[13:36] <willcooke> Assuming it's you that uploads them, do you want the greyscales as separate attachments or the single zip file I got from design?
[14:10] <Laney> willcooke: umm zip file is a bit less work to download but doesn't really matter
[14:10] <Laney> is there a wallpaper contest?
[14:16] <willcooke> Laney, there is, still on going.  nhaines is running it
[14:17] <Laney> ok
[14:18] <willcooke> Laney, uploaded the greyscale
[14:18] <Laney> not sure about adding the huge ones
[14:27] <Laney> debdiff --auto-ver-sort ♥
[14:50] <mhall119> thanks Laney
[15:27]  * desrt steps out to a doctor's appt. back in a bit.
[15:57] <mhall119> Laney: is there a machine-parsable version of the data on http://appstream.ubuntu.com/xenial/universe/issues/index.html ?
[15:58] <mhall119> I'd like to make a list of apps needing icon work
[15:59] <Laney> mhall119: http://appstream.ubuntu.com/hints/
[16:00] <Laney> should be what you want
[16:03] <mhall119> Laney: indeed it is, thanks :)
[16:39] <seb128> mvo, so, need any help with the snappy MIRs?
[16:51] <flexiondotorg> Trevinho, I've updated https://code.launchpad.net/~ubuntu-mate-dev/compiz/marco-gsettings/+merge/282882
[17:04] <mvo> seb128: https://bugs.launchpad.net/ubuntu/+source/golang-websocket/+bug/1548887 I just need to go over it point by point I think
[17:17] <Sweet5hark1> seb128: wrt -breeze -- how is it that 1:5.1.1~rc2-0ubuntu1 says its in universe, but 1:5.1.0-0ubuntu1 says its in main?
[17:20] <Trevinho> flexiondotorg: thanks, I'll check thata
[17:21] <flexiondotorg> ty
[17:31] <Trevinho> flexiondotorg: alberts' comment seems reasonable, can you fix that too?
[17:32] <flexiondotorg> Oh, erm.
[17:32] <flexiondotorg> I have no idea what it means.
[17:33] <muktupavels> flexiondotorg, add gboolean is_mate_desktop in private struct just like you did with GSettings *marco;
[17:33] <muktupavels> then you will just use 'priv->is_mate_desktop' not 'priv->marco && is_mate_desktop ()'
[17:34] <flexiondotorg> Sorry, just seen there is a new comment :-)
[17:35] <seb128> Sweet5hark1, hum, because the change-override command act on a pocket and I did it for xenial and forgot there was another version stucked in proposed, I'm going to fix that one
[17:35] <seb128> mvo, ok, let me know if I can help you with something
[17:37] <flexiondotorg> muktupavels, Any chance you could help me out here.
[17:37] <flexiondotorg> muktupavels, You've requested something beyond my XP ;-)
[17:38] <muktupavels> flexiondotorg, what help do you want from me?
[17:38] <muktupavels> Trevinho, can you look at my new merge proposals?
[17:39] <Trevinho> muktupavels: yeah, I was monitoring it already... I'll check that in bait
[17:39] <Trevinho> bit*
[17:40] <flexiondotorg> muktupavels, Would you be able to refactor my merge proposal to meet your requirements?
[17:41] <muktupavels> flexiondotorg, change should be simple... 1) if (priv->marco && is_mate_desktop ()) will change to if (priv->is_mate_desktop). 2) You add gboolean is_mate_desktop to private struct. 3) you initialize priv->is_mate_desktop in gwd_settings_storage_gsettings_new.
[17:46] <muktupavels> flexiondotorg, I could create branch, but then it will be untested...
[17:46] <Sweet5hark1> seb128: ah ok, thanks! I was unsure if that was just something taking time to update or something.
[17:46]  * Sweet5hark1 feels guilty for not checking components earlier.
[17:47] <flexiondotorg> muktupavels, I can build and test. But the modification you're requesting, which might be simple for you, are complicated for me.
[17:47] <seb128> Sweet5hark1, I fixed it, should be good after next publisher
[17:50] <Laney> man
[17:50] <Laney> ximion: the 'keywords' desktop file parser block hurts my head :-)
[17:54] <ximion> Laney: I wash my hands in innocence ^^ - I only touched the .desktop file parser once or twice so far
[17:54] <Laney> heh
[17:55] <ximion> I am working on a rewrite of the generator right now, which will also work for more distributions - unfortunately, until it gets to the same level as dep11-generator, we are stuck with Python slowness
[17:55] <muktupavels> flexiondotorg, check gwd-marco-gsettings
[17:55] <ximion> I can already read more .deb files much faster, and parsing the TagFile for suites takes just a few seconds
[17:55] <Laney> nice
[17:55] <Laney> what are you using?
[17:57] <flexiondotorg> muktupavels, Thanks. I'll test that tomorrow and get back you :-)
[17:57] <flexiondotorg> Thanks for helping. I appreciate it.
[18:03] <ximion> Laney: right now, D - I felt adventurous ;-)
[18:03] <Laney> O_O
[18:03] <ximion> I also did a small Go implementation, but D is much better for that particular task
[18:04] <ximion> I am using libappstream's parser internally, and D interfaces well with C and - to some extend - C++ code
[18:05] <ximion> goal is to move all parsing and metadata-generating into libas, and have the generator do the dirty work, which is finding icons, rendering fonts, downloading screenshots, ...
[18:05] <ximion> that way, I only need to implement a feature once
[18:06]  * Laney goes mad
[18:06] <ximion> Laney: I suppose you don't like C? :P
[18:07] <Laney> no, C is great, I'm going mad at this python :)
[18:07] <ximion> Laney: ah, that's a relief ^^
[18:07] <Laney> especially new style glib code
[18:08] <ximion> yeah, I got pretty annoyed by Python's multiprocessing - that is a constant source of incredibly hard to debug issues in the generator, and I really want to get rid of it... Both D and Go have excellent ways of handling paralleluzation
[18:08] <ximion> *parallelization
[18:09]  * Laney whispers Haskell
[18:11] <ximion> Laney: that's something I didn't look at... I might still be a bit traumatized from doing Haskell transitions...
[18:13] <Trevinho> muktupavels: any reason why your MP is still set as "in hold"?
[18:13] <muktupavels> Trevinho, which?
[18:13] <Trevinho> muktupavels: https://code.launchpad.net/~albertsmuktupavels/compiz/gwd-marco-gsettings/+merge/287820
[18:14] <muktupavels> I pushed it as example, it is untested...
[18:15] <ximion> Laney: oh, btw, when you're bored: can you sync Limba (pkg:limba) from Debian unstable to universe? That package FTBFSes due to a change in AppStream...
[18:15]  * ximion can also file an FFe / sync request, if that's easier
[18:16] <Laney> ximion: probably tomorrow
[18:17]  * Laney is trying to finish this feature, taking longer than expected :)
[18:19] <ximion> Laney: which feature?
[18:19] <ximion> oh, and I should merge your pull-request, looked fine when I looked at it
[18:20] <Trevinho> flexiondotorg: so, once your MP is ready again ping me... And muktupavels too (a review of you too, would be nice).
[18:20] <ximion> I also want to add a status command to appstreamcli, so we can get an overview of the appstream data, and in which shape it is
[18:24] <Laney> ximion: do you want to know or do you want it to be a surprise? :)
[18:24] <Laney> aaaaaaaaaaaaaaaaaaaah shit, pickling error
[18:27] <ximion> classic
[18:27] <ximion> maybe we should really use dill...
[18:27] <Laney> I'm adding support for langpack translations
[18:29] <seb128> Laney, thanks ;-)
[18:29] <Laney> you're not welcome :|
[18:29] <Laney> :)
[18:29] <seb128> !
[18:30] <mvo> seb128: feel free to pick any of the tasks in this bug :)
[18:31] <seb128> mvo, going to try to do my best to help ;-)
[18:32] <ximion> Laney: as in "read .mo files and determine their translation status" or as in "add metainfo for language-packages"?
[18:32] <ximion> both is cool, btw :)
[18:33] <ximion> (although the latter isn't even specified yet, I need to come to an agreement with hughsie)
[18:33] <seb128> mvo, I guess the team to subscribe is one I'm not admin for that can't be me doing it
[18:33] <Laney> ximion: reading mo, yeah
[18:34] <ximion> neat - that's the larger task and more work ^^
[18:34] <mhall119> Laney: what does 'Ignored': True mean in the AppStream hints yaml file?
[18:34] <ximion> mhall119: means we dropped the component because it has fatal flaws
[18:35] <ximion> (like violations in against the spec, e.g. a .desktop app without icon)
[18:35] <seb128> ximion, Laney, what's the easiest way to determine why a specific package is not listed? e.g emacs, "/usr/share/applications/emacs24.desktop 	emacs24" ... should that be enough to have it?
[18:35] <mhall119> ximion: ok, so if I'm trying ot get people to help fix the spec, those should be targetted?
[18:36] <ximion> seb128: go to the issues page of the respective suite/component and search for the package name - if it has hints of type error, it won't be included: http://appstream.ubuntu.com/xenial/universe/issues/index.html
[18:36] <ximion> I find http://appstream.ubuntu.com/xenial/universe/issues/emacs24-lucid.html
[18:37] <Laney> it's probably in main
[18:37] <ximion> mhall119: jup - ideally point them to the HTMl output, that is easier to read and contains some detailed explanations on what went wrong, while the hints YAML file is rather compact and designed for machine-reading
[18:37] <ximion> jup: http://appstream.ubuntu.com/xenial/main/issues/emacs24.html
[18:37] <ximion> no icon, as usual
[18:38] <seb128>       cid: emacs24.desktop
[18:38] <seb128>     tag: gui-app-without-icon
[18:38] <seb128>       icon_fname: /usr/share/icons/hicolor/scalable/apps/emacs24.svg
[18:38] <seb128>     tag: icon-not-found
[18:38] <seb128> ximion, thanks
[18:40] <seb128> the icon is in the -common
[18:40] <seb128> I guess that's a standard/frequent issue
[18:40] <seb128> is there any way we could workaround it?
[18:42] <seb128> I don't know how the parser works, in what env it tries to look for the icon, but could we make whatever pulls the package try to pull "$name-common" as well?
[18:54] <mhall119> ximion: I'm planning on making a separate listing of just package with missing or incorrect icons
[18:56] <ximion> seb128: no, that's not feasible - although it should find the icon in -common automatically, if it's listed in Contents.gz
[18:56] <seb128> ximion, http://packages.ubuntu.com/search?searchon=contents&keywords=emacs24.svg&mode=exactfilename&suite=xenial&arch=any
[18:56] <seb128> unsure why that doesn't work then :-/
[18:58] <mhall119> can AppStream use SVG, or do they have to be PNG?
[18:58] <ximion> smalls like a Contents issue...
[18:59] <ximion> mhall119: can be SVG, those icons will be automatically rendered to pixmaps on the server
[18:59] <ximion> ideally, the icons should be - if they are pixmaps - available in at least 64x64px
[19:00] <ximion> usr/share/icons/hicolor/scalable/apps/emacs24.svg	    editors/emacs24-common
[19:00] <ximion> Laney: ^ - could this be a remnant from when the generator was parsing the Contents file improperly?
[19:00] <ximion> maybe trigger emacs24 for reprocessing...
[19:01] <muktupavels> Trevinho, are you ok with removing tests from gwd? I created merge proposal for it.
[19:10] <ximion> mhall119: for automatic processing, the YAML is perfect, of course ^^ - for an - also machine-readable - description of the tags, you can look here: https://github.com/ximion/appstream-dep11/blob/master/data/dep11-hints.yml
[19:32] <Laney> ximion: worth a try
[19:32]  * Laney has almost won
[19:32] <Laney> going to send this PR in a second, will do fixes tomorrow
[19:33] <ximion> Laney: the D code is insanely fast! I am really excited! and: real threads and no picking ;-)
[19:33] <ximion> the .deb package format is a bit bad for performance - I have to basically exract it to get a file-list, which is and always will be slow
[19:34] <ximion> I could extract it into memory, but for large packages this might be an issue, unless you have loads of ram
[19:36] <ximion> Laney: thanks for working on this - I postponed this task for a long time ^^
[19:36] <Laney> it's probably not exactly what you have in mind
[19:36] <ximion> (it had a high boringness factor, and wasn't visible in any UI for a very long time anyway)
[19:36] <Laney> this is an ubuntu specific thing
[19:38] <ximion> ah, eww, that's trickier then
[19:39] <Laney> what is your thing?
[19:39] <ximion> does the validator validate the result?
[19:39] <Laney> if it validates translations
[19:39] <Laney> it just gets them from mo files as well as inline in the desktop file
[19:40] <mhall119> ximion: dpkg --contents extracts the whole thing?
[19:42] <ximion> mhall119: need to look at the internals, but yes, it needs to open up the ar file and get to the actual tarball and then read through the whole tarball contents
[19:42] <ximion> it won't actually extract the data from the tarball though
[19:42] <ximion> (fortunately)
[19:42] <ximion> Laney: ah, that's uncontroversial and a neat feature :)
[19:43] <Laney> except for the bit where I have to extract all language-pack-* and deal with X-Ubuntu-Gettext-Domain key
[19:43] <Laney> bit annoying
[19:44]  * Laney probably finds the last known bug
[19:44] <ximion> can't be uglier than what is already in there
[19:57] <Laney> ok there we go
[20:02] <Laney> night!
[20:10] <mhall119> Laney: is there any kind of priority for AppStream apps? There are a lot of them missing icons and it's generally better to present a smaller "wishlist" for people to choose from
[20:17] <willcooke> davmor2, can you see if this has regressed for you as well:  https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1498805
[20:17] <attente> robert_ancell: any idea if there's a better way to get the deb info besides spawning dpkg-deb? (for the sideloading)
[20:18] <willcooke> davidcalle, specifically my ZTE modem is not recognised again
[20:19] <ximion> mhall119: priorize by "stuff in main", then go by the popcon values Ubuntu has collected. The higher the popcon index of an app, the more likely it is that people will miss it
[20:19] <ximion> (that's what I'd do ;-) )
[20:20] <robert_ancell> attente, not off the top of my head, but the dpkg/apt libraries are a bit crap when I've tried to find them
[20:20] <ximion> attente: use apt_inst's DebFile and TagFile classes
[20:21] <attente> ximion: that's a python module? is there a c library i can interface with?
[20:22] <mhall119> ximion: do we have popcon values? IIRC, that service was pretty hit or miss (usually miss)
[20:22] <ximion> attente: it's a C++ library
[20:22] <robert_ancell> ximion, yeah, they all seem to be C++ :(
[20:22] <ximion> mhall119: is http://popcon.ubuntu.com/ still alive?
[20:23] <ximion> robert_ancell: shouldn't be a problem though, you can mix C++ and C easily
[20:23] <ximion> that's what we do in PackageKit and also AppStream
[20:24] <ximion> https://anonscm.debian.org/cgit/apt/apt.git/tree/apt-inst/deb/debfile.h is the thing
[20:24] <ximion> if you read the contents via TagFile it's pretty fast
[20:26] <attente> ximion: mixing c++ and c in GS?
[20:26] <ximion> attente: well, it will work...
[20:26] <ximion> I don't think it's the best idea ever, but it will work
[20:27] <mhall119> ximion: ah, it is alive (and well,surprisingly)
[20:27] <attente> between that and parsing the output of dpkg-deb, which is preferable? dpkg-deb does have a show-format option that allows us to specify exactly what fields we want
[20:28] <ximion> attente: I think a sane way would be calling "dpkg --field" and parsing the output
[20:28] <ximion> (if you want multiple fields)
[20:29] <attente> ximion: does that require multiple spawns though?
[20:29]  * attente should just try it
[20:32] <attente> dpkg-deb --showformat is a bit better because --field also includes the field name in the output
[20:32] <attente> i'm ok with doing it this way since GS is just a front-end for dpkg in this case
[20:35] <ximion> attente: as it happens, I need almost the same solution right now on the genertaor side
[20:35] <ximion> a benchmark has shown that using the dpkg cli is fast enough, if it's just one call.
[20:36] <attente> ximion, yeah, i agree. dpkg-deb doesn't seem too bad for this
[20:39] <ximion> for your case, the overhead of spawning a process should be neglectable
[20:40] <ximion> for my case, I am not yet sure, since I do that 1000 times
[21:48] <willcooke> gnight all
[22:59] <robert_ancell> attente, can you move those non-review changes into another branch?
[22:59] <robert_ancell> branche(s)


[08:13] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Yakkety Alpha 2] (20160727) has been added
[08:13] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop powerpc [Yakkety Alpha 2] (20160727) has been added
[08:13] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop i386 [Yakkety Alpha 2] (20160727) has been added
[09:30] -queuebot:#ubuntu-quality- Builds: Lubuntu Alternate amd64 [Yakkety Alpha 2] (20160727) has been added
[09:30] -queuebot:#ubuntu-quality- Builds: Lubuntu Alternate powerpc [Yakkety Alpha 2] (20160727) has been added
[09:30] -queuebot:#ubuntu-quality- Builds: Lubuntu Alternate i386 [Yakkety Alpha 2] (20160727) has been added
[10:16] -queuebot:#ubuntu-quality- Builds: Ubuntu Kylin Desktop amd64 [Yakkety Alpha 2] (20160727) has been added
[10:16] -queuebot:#ubuntu-quality- Builds: Ubuntu Kylin Desktop i386 [Yakkety Alpha 2] (20160727) has been added
[10:39] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop amd64 [Yakkety Alpha 2] (20160727) has been added
[10:39] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop powerpc [Yakkety Alpha 2] (20160727) has been added
[10:39] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop i386 [Yakkety Alpha 2] (20160727) has been added
[11:45] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Yakkety Alpha 2] has been updated (20160727.1)
[11:45] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop powerpc [Yakkety Alpha 2] has been updated (20160727.1)
[11:45] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop i386 [Yakkety Alpha 2] has been updated (20160727.1)


[00:08] <JontheEchidna> yofel: yeah, that got sru'd
[00:16] <smartboyhw> ScottK, I can't upgrade kopete here, there are 2 dependencies that just doesn't exist
[02:29] <ScottK> smartboyhw: What dependencies in what release?
[04:54] <jalcine> smartboyhw: is there a iCal that I can use to follow Kubuntu events?
[05:21] <shadeslayer> morning :)
[05:21] <shadeslayer> jalcine: not really
[05:22] <shadeslayer> !testers | Please help to QA bug 1208413
[05:23] <smartboyhw> shadeslayer, oy?
[05:23] <smartboyhw> jalcine, no
[05:23] <smartboyhw> ScottK,  kopete : Depends: libmediastreamer-base3 (>= 3.6.1) but it is not installable
[05:23] <smartboyhw>           Depends: libortp9 (>= 3.6.1) but it is not installable
[05:23] <shadeslayer> smartboyhw: kscreen needs QA
[05:23] <smartboyhw> shadeslayer, oh, in 13.10？
[05:23] <shadeslayer> 13.04
[05:23] <smartboyhw> shadeslayer, bye bye:P
[05:23]  * smartboyhw does not have 13.04
[05:25]  * shadeslayer has to resist the early morning urge to open reddit and focus on work
[05:34]  * smartboyhw reboots to install Debian alongside (K)ubuntu
[05:47] <shadeslayer> yofel: fyi currently installing the hwe stack + kubuntu-backports / updates causes kwin to be removed
[05:47] <shadeslayer> and then when you go back, it screws up X11
[05:48] <shadeslayer> something about libgl1 or sth ... not sure
[06:09] <soee> good morning
[07:30] <valorie> !info inxi
[08:11] <shadeslayer> 0.o
[08:11] <shadeslayer> !info inxi saucy
[08:11] <shadeslayer> I see, only in saucy
[08:11] <shadeslayer> valorie: you could request a backport I suppose
[08:30] <jussi> !find inxi
[08:30] <jussi> Riddell: are you about today?
[08:59] <Riddell> jussi: sure
[09:22] <jussi> Riddell: so after investigating the tshirt/poloshirt situation a fair bit, it seems your local supplier would be the best deal. I was thinking if you buy a batch, then I will sell them, and let you know where to send each one when we have the money. The only parts we need to figure out are postage and final pricing. (as well as $design
[09:23] <jussi> )
[09:23] <jussi> say buy 25 to start off with, we put them on the sales website and see how quickly they sell. then we decide how to go forward (numbers etc) after that
[09:23] <Riddell> jussi: meh, I'm really not sure I want to spend my time packing and posting tshirts
[09:24] <jussi> ok. fair enough - your price was 12.50£ right?
[09:24] <Riddell> yeah I think so, for the polos
[09:24] <jussi> also, are we happy with just the Kubuntu logo on the front chest?
[09:24] <jussi> or do we want more?
[09:24] <jussi> (affects price)
[09:24] <Riddell> "It will be £12.50 per poloshirt which will be a total of £250.00 for 20 of them."
[09:25] <Riddell> keep it simple I'd say
[09:25] <jussi> ok. White ok?
[09:26] <jussi> (white is minorly cheaper than the others)
[09:26] <Riddell> jussi: white's ok yes
[09:26] <jussi> otherwise a navy blue is my preference
[09:26] <Riddell> but yeah I'd have naxy blue as preference too
[09:27] <jussi> Ill look around again. WHat price is acceptable asa a sales price? 19.95€ plus postage ?
[09:27] <jussi> (embroidered, not printed)
[09:30] <Riddell> jussi: what are you thinking for payment?
[09:30] <Riddell> the kubuntu paypal account or something else?
[09:30] <Riddell> cos that's in £
[09:30] <jussi> Riddell: something else
[09:32] <jussi> Riddell: I will put them here: https://holvi.com/shop/Kubuntu/
[09:33] <Riddell> great
[09:33] <Riddell> I'd go for €20, 19.95 just seems tacky :)
[09:33] <jussi> yeah
[09:46] <jussi> Riddell: Im asking for a quote still from one guyh here in .fi - friend of mine so probably will get a better deal than normal
[09:56] <Riddell> jussi: or ask my people and get them to ship over the box
[09:57] <jussi> Riddell: i suspect this guy is going to be cheaper still - lets see
[10:59] <smartboyhw> Hello Riddell yofel
[10:59] <smartboyhw> Oh, two hours till my application starts:O
[11:01] <Riddell> smartboyhw: you sound quite nervous! don't be we're not here to make you scared
[11:01] <smartboyhw> Riddell, :)
[11:02] <smartboyhw> Riddell, interesting we at Ubuntu Studio are about to start to publicize our T-shirt shop as well
[11:06] <Riddell> smartboyhw: oh? got any details of how that's organised?
[11:06] <jussi> apachelogger: ping
[11:07]  * smartboyhw points Riddell to ubuntustudio.spreadsheet.fr
[11:07] <smartboyhw> But, the Ubuntu Studio team doesn't earn ANY money
[11:07] <smartboyhw> So, not Kubuntu style;P
[11:13] <jussi> smartboyhw: that address doesnt resolve for me
[11:14] <smartboyhw> jussi, uh it's spreadshirt:P
[11:14] <smartboyhw> SORRY
[11:14] <jussi> hehe
[11:15] <jussi> yeah, spreadshirt were reasonably expensive last time I checked
[11:17] <jussi> smartboyhw: I nthink the thing with ours is we dont want to "make a profit" as such, but all proceeds go back into development. So when yo0u buy a shirt, you not only get a shirt, but you contribute to making sure people continue to contribute to kubuntu
[11:17] <smartboyhw> jussi, we don't even GET the money ourselves
[11:17] <smartboyhw> :P
[11:17] <jussi> yeah, studio is a bit different setup to Kubuntu
[11:18] <smartboyhw> jussi, actually the main issue is of negotiating with Canonical:P
[11:29] <Riddell> "Mackenzie Morgan (maco.m) renewed their own membership in the Kubuntu Members (kubuntu-members) team until 2014-08-13"  hoorah, maco still loves us!
[11:34] <jussi> :D
[11:36] <highvoltage> :-)
[11:44] <jussi> Riddell: so I have a quote. A once off fee of 40€ for embroidery, then 14€ per shirt for the first 25 shirts. If we order more shirts later, there is no fee for embroidery, and if we order in greater quantities the price gets cheaper. How does that sound? Good enough to go to the council and get a decision?
[11:45] <Riddell> jussi: yeah I'd say so
[11:45]  * Riddell out for an hour
[12:00] <smartboyhw> Riddell, come back for the meeting plz
[12:27] <ScottK> smartboyhw: Neither of them have migrated from proposed yet.
[12:41] <smartboyhw> ScottK, um I have the ninjas ppa here:P
[12:56] <Riddell> good afternoon
[12:56] <smartboyhw> Riddell, I think we can soon start the meeting:)
[12:57] <Riddell> smartboyhw: want it here or in #u-meeting?
[12:57]  * smartboyhw pings apachelogger and debfx and Riddell and ScottK and JontheEchidna and Quintasan and yofel
[12:57] <smartboyhw> Riddell, here
[12:57]  * jussi waves
[12:57] <ScottK> \0
[12:57] <smartboyhw> And jussi and others:P
[12:57] <smartboyhw> That's 3 already, we can start:P
[12:58] <ScottK> No, it's early yet.
[12:58] <yofel> o/
[12:58] <smartboyhw> ScottK, yeah, 2 minutes
[12:58] <yofel> shadeslayer
[12:58] <smartboyhw> Actually, if you guys want to , we can hold it in #ubuntu-meeting
[12:59] <ScottK> Here is good
[12:59] <smartboyhw> ScottK, because I want meetingology to appear:P
[12:59] <shadeslayer> ola
[12:59] <jussi> here is good
[12:59] <jussi> heya shadeslayer
[12:59] <smartboyhw> Whoa, that's a lot of people here:)
[12:59] <ScottK> smartboyhw: We usually do these here.
[13:00] <smartboyhw> ScottK, alright
[13:00] <ScottK> We don't really need meetingology for this.
[13:00]  * ScottK looks at Riddell to lead the meeting.
[13:00] <smartboyhw> ScottK, it's :00 here now
[13:00] <ScottK> It is.
[13:01] <Riddell> good afternoon friends
[13:01] <smartboyhw> Good evening
[13:01] <Riddell> who's here for a kubuntu-dev meeting?
[13:01] <smartboyhw> o/ as the applicant
[13:01] <jussi> o/
[13:01] <shadeslayer> and the rest of us as smartboyhw's nightmare
[13:01] <smartboyhw> shadeslayer, LOL
[13:01] <ScottK> \0
[13:01] <yofel> o/
[13:02] <shadeslayer> o/
[13:02]  * ScottK pokes at debfx and JontheEchidna
[13:02] <Riddell> does anyone remember the wiki page describing the process? I can't seem to find it
[13:02] <Riddell> but I think it's just a simple majority of people from https://launchpad.net/~kubuntu-dev/+members
[13:02] <yofel> it should be a simple +3 AFAIR
[13:02] <smartboyhw> Riddell, https://wiki.kubuntu.org/Kubuntu/KubuntuDevelopers
[13:02] <shadeslayer> ^^
[13:03] <shadeslayer> I think it was a simple matter of cookies
[13:03] <smartboyhw> Well, majority of attendees, and the attendess >= 3
[13:03] <smartboyhw> For a nice and fresh topic:)
[13:04] <Riddell> smartboyhw: do you have a wiki page?
[13:04] <smartboyhw> Riddell, https://wiki.ubuntu.com/smartboyhw
[13:04] <smartboyhw> (Wasn't really detailed with packages worked on)
[13:04] <smartboyhw> The one with packages detail should be @ https://wiki.ubuntu.com/smartboyhw/KubuntuDevApplication
[13:05] <Riddell> but it's not?
[13:05] <smartboyhw> Or /KubuntuDeveloperApplication
[13:05] <Riddell> ah yes https://wiki.ubuntu.com/smartboyhw/KubuntuDeveloperApplication
[13:05] <smartboyhw> Riddell, that's the list of packages at least
[13:06] <Riddell> smartboyhw: excellent, so now we get to test you a bit on your packaging knowledge
[13:06] <smartboyhw> Great:)
[13:07] <Riddell> smartboyhw: I'm an archive admin, what do you think I look at when reviewing a package that has been uploaded
[13:08] <smartboyhw> Riddell, has been uploaded?
[13:08] <smartboyhw> Lintian warnings
[13:08] <smartboyhw> Whether it's NEW
[13:08] <Riddell> smartboyhw: uploaded to New yes
[13:08] <smartboyhw> Is it installable
[13:08] <smartboyhw> Build-dep
[13:08] <smartboyhw> Changelog
[13:08] <smartboyhw> Symbols
[13:08] <smartboyhw> Copyright
[13:09] <smartboyhw> dh version (shouldn't be too low)
[13:10] <smartboyhw> .install files
[13:10] <smartboyhw> (Shouldn't have duplicates or not-installed files unless necessary or included in another package)
[13:10] <Riddell> yep all that.  copyright is an important one for archive admins, do you know what we'll be looking for there?
[13:10] <Riddell> (in New reviews)
[13:11] <smartboyhw> Riddell, the copyright should be correct for each file
[13:11] <smartboyhw> With the correct License
[13:12] <Riddell> yeah licences is an important thing we'd check
[13:12] <Riddell> suspicious-source checks for any PDF files, do you know why they might be a problem?
[13:12] <Riddell> we also use that during New reviews
[13:13] <smartboyhw> Riddell, because of 1. license issues 2. proprietary or non-free features needed
[13:13] <Riddell> if it was under the GPL why might it still be a problem?
[13:14] <Riddell> others: nudge you can question too
[13:14] <smartboyhw> It is a generated file
[13:14]  * shadeslayer is waiting for Riddell to finish :)
[13:14] <smartboyhw> It should be generated at compile-time instead?
[13:15] <Riddell> smartboyhw: lovely
[13:15] <Riddell> not necessarily generated at compile time but the source does need to be there as it's not perferred modifiable form
[13:15] <Riddell> shadeslayer: go ahead
[13:16] <shadeslayer> smartboyhw: we have a bunch of fields in the control file, one of them is X-Debian-ABI, why do you think we have that?
[13:16] <smartboyhw> shadeslayer, because the package has a ABI version bump
[13:16] <shadeslayer> so why not just bump the so version?
[13:16] <Riddell> who from?
[13:17] <smartboyhw> shadeslayer, bumping so version can cause the whole library to change
[13:18] <Riddell> smartboyhw: if you're packaging a new version of a library and you notice changed symbols what should you do?
[13:18] <smartboyhw> And bumping So version means a new thing
[13:19] <smartboyhw> Riddell, pkgkde-symbolshelper patch:P
[13:19] <smartboyhw> Actually not
[13:19] <smartboyhw> Regenerate the whole symbols file is better
[13:19] <Riddell> smartboyhw: just that? what's the point of symbols files?
[13:19] <shadeslayer> smartboyhw: okay, another question, what's the structure of an actual deb?
[13:19] <smartboyhw> Riddell, shared libraries
[13:20] <smartboyhw> shadeslayer, it will contain like this
[13:20] <smartboyhw> /usr/lib for the libraries
[13:20] <yofel> on that topic: what is a deb file actually?
[13:20] <smartboyhw> usr/share for the icons, etc.
[13:20] <shadeslayer> smartboyhw: actually, I think yofel phrased my question a bit better :)
[13:21] <yofel> (from a technical POV)
[13:21] <smartboyhw> yofel, shadeslayer it's a Debian software package format used on Debian-based systems, which works with dpkg, apt-get or aptitude
[13:21] <smartboyhw> Normally, it is tar archives
[13:21] <yofel> that is true, but what's the actual file structure?
[13:21] <shadeslayer> ^^
[13:22] <ScottK> Actually it's ar, not tar on the outside.
[13:22] <shadeslayer> ssshhhh :P
[13:22] <smartboyhw> ScottK, my fault, I did want to type ar:P
[13:22] <smartboyhw> yofel, a control.tar.gz, consisting of the meta-info
[13:23] <smartboyhw> And a data.tar.gz (or any ar file),
[13:23] <smartboyhw> consisting of the usr/lib, usr/share, usr/bin...
[13:24] <yofel> noting that ar isn't tar, ok
[13:24] <smartboyhw> yofel, ar != tar
[13:24] <smartboyhw> Got it
[13:24]  * shadeslayer is satisfied with that as well
[13:24]  * smartboyhw likes tar：P
[13:24] <smartboyhw> More questions plz:P
[13:24] <yofel> one other thing about X-Debian-ABI, what's required for it to be used?
[13:24] <shadeslayer> ^^ I did ask that, didn't get a proper reply :P
[13:25] <smartboyhw> yofel, shadeslayer when a new version of library breaks the previous one
[13:26] <smartboyhw> Actually, the previous good oneP
[13:26] <smartboyhw> :P
[13:26] <yofel> that's *when* it is used, but it doesn't just work out of the box
[13:26] <shadeslayer> smartboyhw: a test is failing in a package and it really needs to be uploaded, what would you do to fix the package?
[13:26] <smartboyhw> yofel, breaks/conflicts?
[13:26]  * apachelogger sits in
[13:27] <smartboyhw> shadeslayer, is the test very important?
[13:27] <smartboyhw> i.e. the whole package is NOT working?
[13:27] <yofel> smartboyhw: no, I guess you never noticed. Look at kde-workspace/debian/patches/enable_debianabimanager.diff for example
[13:27] <apachelogger> :O
[13:27]  * apachelogger leaves again
[13:27] <smartboyhw> apachelogger, ?
[13:27] <debfx> smartboyhw: how do you need to change the packages when upstream moves a file from one package/orig tarball to another?
[13:27] <shadeslayer> smartboyhw: nope
[13:27] <shadeslayer> apachelogger: not so fast :>
[13:28] <smartboyhw> shadeslayer, Upload it first,
[13:28] <smartboyhw> Then patch the test
[13:28] <smartboyhw> Upload a new version with new -ubuntu version?
[13:28] <smartboyhw> debfx, you mean, from .bz2 -> .xz or?
[13:28] <shadeslayer> smartboyhw: sure, but how would you disable the tests
[13:29] <smartboyhw> shadeslayer, override it in debian/rules
[13:29] <shadeslayer> right, *how*?
[13:29] <smartboyhw> override_dh_auto_configure:
[13:30] <debfx> smartboyhw: no, for example a file is moved from kopete to kde-runtime
[13:30] <shadeslayer> *nod*
[13:30] <smartboyhw> debfx, ah
[13:30] <apachelogger> why would you deactivate all tests if one test is failing?
[13:30] <smartboyhw> debfx, delete the file in kopete.install, add it in kde-runtime, make sure kde-runtime breaks the previous kopete versions and upload
[13:30] <smartboyhw> breaks/conflicts sorry
[13:31] <debfx> smartboyhw: which one? breaks and conflicts?
[13:31] <smartboyhw> debfx, and:P
[13:31]  * smartboyhw likes using “/” for "and"...
[13:32] <debfx> smartboyhw: what's the difference between breaks and conflicts? :)
[13:33] <smartboyhw> debfx, breaks means the installing package will not be configured unless the previous one is uninstalled
[13:33] <smartboyhw> Conflicts means the two packages will not be configured and unpacked at same time
[13:34] <smartboyhw> apachelogger, hmm, then maybe patch the package itself so the scripts running the tests will not run the failed one?
[13:34] <ScottK> smartboyhw: Take a look at http://paste.debian.net/24321/ and tell me what your reaction to that being in a source package would be?
[13:34] <apachelogger> (technically the breaker will not even be unpacked)
[13:34] <shadeslayer> o_o
[13:34] <apachelogger> (technically conflicts means they will not ever be unpacked at the same time)
[13:35] <smartboyhw> ScottK, the formatting is a bit weird
[13:35] <shadeslayer> I think that is intentional :P
[13:35] <smartboyhw> Fix it?
[13:35] <apachelogger> smartboyhw: that would seem more reasonable
[13:35] <smartboyhw> apachelogger, OK
[13:37] <ScottK> smartboyhw: That's called minified javascript.  It's a problem because it's not the preferred form of modification, so it can't be considered source.
[13:37] <smartboyhw> ScottK, sorry, I touched C, C++ and Python before, but never js
[13:37] <ScottK> So you can't just copy it into the binary for Main/Universe.
[13:37] <ScottK> You'll find it often in documentation.
[13:38] <Riddell> smartboyhw: do you know the current best practice for packaging python?
[13:38] <yofel> smartboyhw: symbol files have the version when the symbol was added attached to every symbol (e.g. '_ZN4KWin12glBindBufferE@ABI_1_2 4:4.10.80'). What is it used for? And where does ABI_1_2 come from?
[13:38] <Riddell> which debhelper module?
[13:38] <smartboyhw> Riddell, yofel one question at a time...
[13:38] <smartboyhw> Riddell, dh_python ？
[13:38] <debfx> smartboyhw: would it be enough to just use Breaks?
[13:38] <shadeslayer> okay, too many questions, I think I'll hold off on mine for now
[13:39] <yofel> smartboyhw: just answer them in the order they're asked
[13:39] <smartboyhw> yofel: It means the minimum version that the symbols exist. ABI_1_2 come from the SOVERSION
[13:39] <smartboyhw> And maybe the ABI version?
[13:39] <smartboyhw> debfx, no
[13:39]  * apachelogger thinks yofel likes ABI a lot :P
[13:39] <yofel> smartboyhw: where is that minimum version used?
[13:40]  * yofel wonders how apachelogger realized that yofel is evil
[13:40] <smartboyhw> debfx, breaks can't ensure what happens when the two packages are unpacked AT THE SAME TIME
[13:40] <smartboyhw> i.e. when upgrading both packages
[13:40] <shadeslayer> smartboyhw: I have a line like this in debian/rules : -dh_foo : <more lines afterwards> : what does the - there indicate?
[13:41] <debfx> smartboyhw: yes. is there a better alternative to Conflicts in this case?
[13:41] <apachelogger> yofel: should you ever run out of evil ask me for questions.txt it shall give you plenty more evil :P
[13:41] <yofel> smartboyhw: almost correct, ABI_ comes from debian abi manager, usually it says 'Base' there. 1 is the SOVERSION, 2 is X-Debian-ABI
[13:41] <yofel> apachelogger: :O
[13:41]  * shadeslayer would like to see apachelogger's questions.txt
[13:41] <smartboyhw> debfx, I thought Conflicts are mostly replaced by breaks now...
[13:42] <Riddell> smartboyhw: dh_python isn't current best practice but I did have to look that up to double check, how would you look it up to find out?
[13:42] <apachelogger> shadeslayer: you were likely happy enough to see questions from it
[13:42] <shadeslayer> Probably, but can't hurt to see more ;)
[13:43] <smartboyhw> Riddell, in the Debian guides?
[13:43] <smartboyhw> Riddell, and it should be dh_python2 I think..
[13:43] <Riddell> smartboyhw: yep, good answers :)
[13:43] <apachelogger> smartboyhw: what are udeb files? do we use them? why & whatfor?
[13:44] <smartboyhw> apachelogger, udeb is a micro-deb that does not have the requirements for changelog, copyright, etc.
[13:45] <debfx> smartboyhw: right, but you said correctly that breaks isn't enough. instead of Conflicts you should use Breaks+Replaces for moving files between packages.
[13:45] <smartboyhw> I don't think the Kubuntu team uses it, you will normally use it for kernels (like in d-i)
[13:45] <smartboyhw> debfx, yep:)
[13:45]  * smartboyhw really doesn't know the answer to shadeslayer's -dh question, uh oh:P
[13:45] <apachelogger> smartboyhw: what's etc? do we use udebs? whatfor do we use udebs?
[13:45] <shadeslayer> :>
[13:46] <smartboyhw> apachelogger, even md5sums
[13:46] <shadeslayer> smartboyhw: so basically - is used to indicate that even if dh_foo fails, the package build should not fail
[13:46] <shadeslayer> and the buildd can safely ignore that error
[13:47] <Riddell> smartboyhw: for the -dh question you can say what format the debian/rules file is in and how you'd research that format to find out the syntax
[13:47] <shadeslayer> ^^
[13:47] <apachelogger> it's the obvious answer to every code question ^^
[13:47] <shadeslayer> I still have to read manual for said format :P
[13:48]  * shadeslayer hides from apachelogger
[13:48]  * yofel notes that smartboyhw hasn't answered what those minimum versions are used for either - actually tell 2 dpkg-/dh_ parts that use that information
[13:48] <yofel> s/parts/commands
[13:49] <shadeslayer> smartboyhw: what's a virtual package?
[13:50] <smartboyhw> Riddell, debian/rules is in a makefile
[13:50] <apachelogger> oh
[13:50] <smartboyhw> Riddell, because most debian/rules has a #!/usr/bin/make -f header:P
[13:50] <apachelogger> I found a god one
[13:50] <apachelogger> or a good one, lololo
[13:50] <smartboyhw> apachelogger, ?
[13:51] <apachelogger> smartboyhw: you still have not answered whether we use udeb files and what we use them for if we use them?
[13:51] <shadeslayer> apachelogger: there are a bunch of unanswered questions
[13:51] <apachelogger> then you get the singlest most evil question in the world ^^
[13:51] <smartboyhw> apachelogger, if you use them you use it only for kernels or partman right?
[13:52] <apachelogger> kinda, there's a reason for that though
[13:52] <smartboyhw> Or for packages that has requirements such that it shouldn't contain so many different iinfo...........
[13:52] <smartboyhw> Since these packages can only be done in RAm
[13:52] <smartboyhw> shadeslayer, virtual package
[13:52] <smartboyhw> It normally is used to contain specific packages
[13:52] <smartboyhw> For example, calligra depends on different calligra components
[13:53] <shadeslayer> uhm I think you're confusing virtual packages with meta packages :)
[13:53] <smartboyhw> shadeslayer, oops:P
[13:54] <smartboyhw> shadeslayer, it's used for provides
[13:54] <smartboyhw> When one package provides a functionality
[13:54] <ScottK> What's wrong with "Depends: default-mail-transport-agent"
[13:55] <smartboyhw> ScottK, then it doesn't know which mail transport agent to install
[13:55] <smartboyhw> Since there are many packages providing it
[13:55] <ScottK> Sure it does.  default-mail-transport-agent is only provided by one package.
[13:55] <shadeslayer> smartboyhw: how would you get details of a virtual package from the command line
[13:56] <shadeslayer> i.e equivalent of apt-cache show for virtual packages
[13:56] <Riddell> folks: time to start wrapping up, no new questions please
[13:56] <smartboyhw> shadeslayer, what details do you want?
[13:56] <ScottK> smartboyhw: A package should almost always have an alternate to a virtual depends, like mail-transport-agent | postfix
[13:57] <shadeslayer> smartboyhw: what packages provide that virtual package
[13:57] <Riddell> shadeslayer: ahem
[13:57] <smartboyhw> apt-cache showpkg?
[13:58] <shadeslayer> cool, I'm done :)
[13:58] <smartboyhw> ScottK, oh
[13:58] <ScottK> That's if there are multiple providers of the virtual package.  Actually my first example was fine.
[13:58] <smartboyhw> Thank you all for grilling me:)
[13:59] <smartboyhw> ScottK, uh .....
[13:59] <Riddell> smartboyhw: we've been chatting a bit in a private channel (I know, very naughty of us)
[13:59] <smartboyhw> Riddell, private channel?!
[13:59]  * smartboyhw does not understand
[13:59] <smartboyhw> Oh, got it
[13:59] <smartboyhw> Very naughty
[13:59] <smartboyhw> :P
[13:59] <ScottK> There's only one default-mail-transport-agent, but multiple providers of mail-transport-agent, so the latter needs the alternate depends.
[14:00] <smartboyhw> ScottK, ah
[14:00] <Riddell> smartboyhw: we're all very happy you put yourself through the grilling and want to you to be in kubuntu-dev but are a bit concerned at the lack of detailed knowledge in areas
[14:00] <smartboyhw> Riddell, I remembered
[14:00] <smartboyhw> When shadeslayer had his grilling
[14:01] <Riddell> smartboyhw: could we ask you to do some informal training sessions with kubuntu-devs to brush up and come back next month?
[14:01] <smartboyhw> People said: "He still needs to learn a lot more"
[14:01] <smartboyhw> Then why can't I?:P
[14:01] <smartboyhw> People learn through experience
[14:01] <smartboyhw> I mean, I will still get to you guys when I have questions
[14:01] <smartboyhw> And I normally will want to get some person reviewing before uploading
[14:02] <smartboyhw> Riddell, uh informal?
[14:02] <apachelogger> I still want to ask my evil question :(
[14:02] <smartboyhw> apachelogger, you can still asK:P
[14:02] <apachelogger> nah then I can't use it next time :P
[14:02] <shadeslayer> apachelogger: you also did not ask your customary "Everyone is sloshed except you before release day"
[14:03] <apachelogger> I know
[14:03] <apachelogger> <- has 5 more questions queued :P
[14:03] <apachelogger> but oh well
[14:03] <shadeslayer> heh
[14:03] <yofel> smartboyhw: well, then not having upload permissions for a month more won't hurt much, will it? You've learned a lot lately, but I think you need to be a bit more competence until we're happy to let you upload packages unreviewed
[14:03] <Riddell> smartboyhw: or come back earlier than next month but I'd be reluctant to give you upload access if you don't know what symbols files are for etc
[14:03] <yofel> s/to be//
[14:03] <kubotu> yofel meant: "smartboyhw: well, then not having upload permissions for a month more won't hurt much, will it? You've learned a lot lately, but I think you need  a bit more competence until we're happy to let you upload packages unreviewed"
[14:05] <Riddell> smartboyhw: but don't let this put you off! we need you for 4.11 this week!
[14:05] <shadeslayer> from me, you just need a bit more experience before I give a full +1, please do reapply soonish :)
[14:05] <smartboyhw> Riddell, yofel next month sure:)
[14:05] <apachelogger> PSA: for general training everyone try to write the tiniest possible debian/rules that does not use dh (i.e. debhelper <=6)
[14:05] <ScottK> apachelogger: How about one that doesn't use debhelper at all?
[14:06] <apachelogger> also possible
[14:06] <smartboyhw> apachelogger, everyone? Including Riddell and yofel and shadeslayer ?
[14:06] <apachelogger> albeit more codes
[14:06] <smartboyhw> :I
[14:06] <ScottK> There may still be a package or two in the archive that doesn't use it.
[14:07] <apachelogger> smartboyhw: sure
[14:07] <Riddell> hello doesn't use debhelper I think
[14:07] <yofel> would be fun, I haven't looked at all the targets in a while
[14:07] <apachelogger> I do always find it questionable when people don't know what is going on underneath dh
[14:07] <smartboyhw> No dh, uh oh:P
[14:07]  * shadeslayer recalls some targets, but not all of them
[14:07] <apachelogger> and what would be needed to create a bare minimum deb
[14:08] <apachelogger> anyway
[14:08] <Riddell> ah, classic http://starsky.19inch.net/~jr/tmp/rules
[14:08] <apachelogger> mine's 29 lines with comments and all
[14:08] <shadeslayer> o_o
[14:08] <smartboyhw> apachelogger, oh, all the targets?
[14:08] <apachelogger> the targets that are necessary :P
[14:08] <smartboyhw> I thought I was in pre-jurrasic era:P
[14:08] <apachelogger> Riddell: for some reason google's dns never wants to resolve 19inch.net
[14:08] <apachelogger> it's le weird
[14:09] <smartboyhw> apachelogger, heh
[14:09] <Riddell> apachelogger: google's dns?
[14:09] <shadeslayer> apachelogger: stop using the silly dns resolver
[14:09] <shadeslayer> apachelogger: use http://www.opennicproject.org/ instead
[14:09] <apachelogger> https://developers.google.com/speed/public-dns/
[14:09] <shadeslayer> so happpy :D
[14:09] <apachelogger> Are you looking for an alternative DNS provider that is open and democratic, are you concerned about censorship?
[14:10] <shadeslayer> pn5 is completely built for raring and saucy now
[14:10] <apachelogger> that doesn't even make sense
[14:10] <Riddell> dig @<IP_ADDRESS> starsky.19inch.net  works
[14:10] <apachelogger> oh true
[14:10] <apachelogger> this machine doesn't have it hardcoded
[14:11] <apachelogger> it's the ISP's DNS
[14:11]  * apachelogger sighs at austria
[14:12] <apachelogger> mhh
[14:12] <yofel> smartboyhw: for the record, about my symbol version question. I would've been happy with dpkg-gensymbols (which sets those versions) and dpkg-shlibdeps (which calculates versioned library dependency versions from that)
[14:12] <apachelogger> smartboyhw: I like that write-a-rules thing so much if I were you I'd practise writing rules :P
[14:13] <smartboyhw> apachelogger, the only target I can't understand is binary-indep
[14:13] <smartboyhw> yofel, I know about dpkg-gensymbols (the one throwing off the symbols diff if it's wrong)
[14:13] <apachelogger> arch: all = binary-indep
[14:13] <smartboyhw> apachelogger, ah
[14:14] <shadeslayer> okay cya later
[14:14] <apachelogger> or rather, if you invoke dpkg-buildpackage with whatever silly flag there is to only build arch: all packages it will invoke binary-indep rather than binary or binary-arch
[14:14] <smartboyhw> apachelogger, got it
[14:14] <smartboyhw> So, what types of "informal" sessions have you planned for me? Give me a schedule at least...
[14:15] <smartboyhw> s/you/you guys/
[14:15] <kubotu> smartboyhw meant: "So, what types of "informal" sessions have you guys planned for me? Give me a schedule at least..."
 I hear yofel_ has time to tell you about symbols and what not ^^
[14:18] <Quintasan> oh damn it
[14:18] <Quintasan> dem time zones
[14:18] <Quintasan> I lost my opporunity to grill smartboyhw, didn't I?
[14:18] <apachelogger> Quintasan: you had been late regardless
[14:19] <yofel> well, which reminds me I need to read up on udebs myself. I usually care about them enough to know that they're stripped-down debs used by d-i
[14:19] <Quintasan> apachelogger: late for what apart from smartboyhw grilling?
[14:20] <yofel> Quintasan: you'll get another chance in a month
[14:20] <smartboyhw> yofel, anytime to talk about symbls then？
[14:20] <smartboyhw> A month is a weird restriction (LOL)
[14:20] <Quintasan> yofel, smartboyhw you might to want to keep it public
[14:21] <apachelogger> smartboyhw: actually about udeb... they indeed lack the metadata that you'd find in a regular deb reason being that they are meant for bootstrap and you don't raelly need metadata for bootstrapping,which is also why only core packages have udebs to begin with
[14:21] <Quintasan> I could use a refresh too
[14:21] <apachelogger> Quintasan: you are late to me offering free booze
[14:21] <Quintasan> apachelogger: Come to Poland.
[14:22] <Quintasan> kubotu: order beer for apachelogger
[14:22]  * kubotu gives apachelogger a nice frosty mug of beer.
[14:22] <apachelogger> let's meet in cz, they got better beer anyway
[14:24]  * smartboyhw waits for yofel to start
[14:25] <smartboyhw> Actually, it's good you give me another month, I need to work on linux-rt:P
[14:25] <yofel> I'm a bit busy now really
[14:27] <yofel> what I asked today is essentially documented in the dpkg-gensymbols and dpkg-shlibdeps manpages.
[14:27] <yofel> which reminds me that we didn't ask what an shlibs file is for
[14:28] <Quintasan> did we get the symbols file :P
[14:28] <Quintasan> symbols file question*
[14:29] <apachelogger> kubotu: hi
[14:29] <kubotu> re, apachelogger
[14:29] <yofel> Quintasan: as I knew that he knows that we use them for ABI management, we only asked about debian abi manager and symbol versioning
[14:29] <apachelogger> kubotu_: hi
[14:29] <kubotu> howdy, apachelogger
[14:29] <kubotu_> 'afternoon, apachelogger :)
[14:29] <Quintasan> yofel: I see.
[14:30] <apachelogger> kubotu_: nick kubotu
[14:30] <apachelogger> jussi: ^ migration complete
[14:31] <smartboyhw> You guys should make a full doc on "what should a new Kubuntu packager learn"...
[14:31]  * smartboyhw looks at dpkg-gensymbols and dpkg-shlibdeps manpages
[14:32] <smartboyhw> Quintasan, then can you run me a tutorial:P
[14:34] <smartboyhw> Or just any dev/
[14:34] <Quintasan> I mean, read the damn docs
[14:35] <Quintasan> After that you should generally ask questions
[14:35] <smartboyhw> Quintasan, OK
[14:35] <Quintasan> if there is something not clear
[14:35] <smartboyhw> Quintasan, what is a substvars?
[14:36] <smartboyhw> Ah, I got it now:P
[14:36] <Quintasan> Did you actually finish reading?
[14:37] <smartboyhw> Quintasan, maybe I should ask: Where is shlibs files generated?
[14:37]  * smartboyhw can't seem to find it in the manpages
[14:38] <Quintasan> IIRC they are generated in debian/ during the build process
[14:38] <Quintasan> by dpkg-genshlibs or sth like that
[14:38] <smartboyhw> Quintasan, no that command I think
[14:38] <yofel> dpkg-shlibdeps you mean
[14:39] <Quintasan> ah yes
[14:39] <Quintasan> yofel++
[14:39] <smartboyhw> yofel, wait, does dpkg-shlibdeps generate the shlibs files?
[14:39] <smartboyhw> I can't seem to understand that part
[14:39]  * smartboyhw understands the symbols
[14:39] <apachelogger>   debian/*/DEBIAN/symbols
[14:39] <apachelogger>               Shared  library  information  generated  by  the  current  build
[14:39] <apachelogger>               process that also invoked dpkg-shlibdeps.  They are generated by
[14:39] <apachelogger>               dpkg-gensymbols(1).   They are only used if the library is found
[14:39] <apachelogger>               in a package's build tree. The symbols file in that  build  tree
[14:39] <apachelogger>               takes precedence over symbols files from other binary packages.
[14:40] <yofel> dpkg-shlibdeps does generate some during build
[14:40] <apachelogger> rtfm I say :P
[14:40] <yofel> ^
[14:40] <apachelogger> http://man.he.net/man1/dpkg-shlibdeps
[14:40] <smartboyhw> yofel, apachelogger oh so dpkg-shlibdeps generate shlibs itself, I read the manpage and thought “Where does it come from?":P
[14:42] <apachelogger> then you didn't read the manpage :P
[14:42] <apachelogger> a
[14:42] <apachelogger> cause I just pasted from the manpage :P
[14:45] <manchicken> apachelogger: Can you RTFM me to a document showing me how to run those code quality tools you were using?
[14:45] <apachelogger> http://techbase.kde.org/Development/Tutorials/Code_Checking
[14:45] <manchicken> I'm dealing with interview prep right now, so I can't do anything on that project at the moment, but I want to be able to verify my code using the same tools you did prior to submitting again :)
[14:46] <apachelogger> http://clang-analyzer.llvm.org/
[14:49] <manchicken> The krazy checker gives me all sorts of fun trouble.
[14:49] <apachelogger> oh?
[14:50] <apachelogger> well, it's perl software it's meant to do that ^^
[14:50] <Riddell> hmm, with 4.11 from ninjas I can't install kopete
[14:51] <yofel> installs fine here
[14:51] <manchicken> apachelogger: Ooh, touchet.
[14:51]  * Quintasan checks
[14:51] <manchicken> (touché even?)
[14:52] <Riddell> yofel: do you have libmediastreamer-base3 ?
[14:52] <apachelogger> manchicken: latter
[14:53] <yofel> yes, but that's from saucy-proposed, so that explains it
[14:53] <yofel> (I have -proposed enabled with a 50 pin)
[14:53] <smartboyhw> Riddell, me too
[14:53] <Riddell> yofel: but how does kopete build against it?
[14:53] <smartboyhw> yofel, boo
[14:53]  * smartboyhw doesn't have -propoesd here
[14:53] <Riddell> does ninjas build against -proposed
[14:54] <smartboyhw> Riddell, yes
[14:54] <smartboyhw> (sigh)
[14:54] <yofel> ninjas builds against -proposed, yes
[14:54] <Riddell> that's a good thing, just not great when we have a stuck package like this
[14:55] <Riddell> linphone Valid candidate
[14:55] <Quintasan> That said copying packages from ppa to main won't do, will it?
[14:55] <Quintasan> to repositories*
[14:56] <yofel> well, afaik it's possible, we just never do it
[14:56] <Riddell> nope
[14:56] <Riddell> I don't think we want to do it, too error prone
[14:56] <Riddell> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt  says something about sipwitch
[14:56] <Quintasan> hmm
[14:57] <smartboyhw> Hmm
[15:01] <ScottK> Riddell: I'm working on it.
[15:02] <yofel> tsdgeos: are we getting nepomuk-core respins? or should we just patch vishesh's fixes in?
[15:02] <vHanda> you are
[15:03] <vHanda> please wait a little while longer
[15:03] <Riddell> ScottK: linphone has always been a mess, this is probably why we dropped its use by kopete in the first place
[15:03] <vHanda> still testing some stuff
[15:03] <Riddell> ScottK: I recently added that back on request of upstream but we can remove it again if it's a problem
[15:03] <ScottK> Riddell: There's a whole dependency mess around it.
[15:03] <ScottK> No, you can leave it.
[15:06] <smartboyhw> yofel, Riddell see your inbox
[15:06] <smartboyhw> shadeslayer, ^
[15:10] <apol_> is kde 4.11rc2 available yet?
[15:10] <apol_> I don't see it here http://community.kde.org/KDE_SC/Binary_Packages
[15:10] <smartboyhw> apol_, um, we are working on 4.11.0:)
[15:11] <apol_> oh :(
[15:11] <apol_> ok
[15:11] <smartboyhw> apol_, which series are u using?
[15:11] <smartboyhw> 13.10 and 13.04 and 12.04 are available
[15:11] <apol_> I use archlinux, it was for a blogger who wanted to do some testing of 4.11
[15:11] <smartboyhw> apol_, which release is he using?
[15:12] <apol_> 13.04 i guess
[15:12] <smartboyhw> apol_, it's available in kubuntu-ppa/beta
[15:12] <smartboyhw> Tell him to sudo add-apt-repository ppa:kubuntu-ppa/beta
[15:12] <smartboyhw> And sudo apt-get update
[15:12] <smartboyhw> And sudo apt-get dist-upgrade
[15:12] <apol_> sure
[15:12] <apol_> smartboyhw: so you do have packages of the rc afterall?
[15:13] <yofel> yes, the binary packages page just wasn't updated
[15:13] <apol_> ok, thanks yofel
[15:19] <smartboyhw> yofel, Riddell shadeslayer do reply to the e-mail if you want me experienced enough to be dev:P
[15:19] <smartboyhw> Good night (need to sleep early, piano exam tmr)
[15:22] <Riddell> hmm kamoso gets removed when I install kde-full
[15:29] <Riddell> is it time to run kubuntu-batch-backport ?
[15:30] <yofel> well, you'll have to update nepomuk later
[15:30] <yofel> otherwise go ahead
[15:32]  * Riddell moves unstable backport hooks to stable and runs >./kubuntu-batch-backport -v 4.11.0 -f saucy -t raring -V 4.11.0
[15:43] <yofel> Riddell: -V should be 13.04
[15:46] <Riddell> yofel: doh
[15:48] <ScottK> If you rebuild kopete now, the result should be installable.
[15:49] <Riddell> ScottK: what's changed?
[15:49] <ScottK> Removed a bunch of crap from -proposed that wasn't going to get sorted otherwise.
[15:49] <ScottK> remove-package -s saucy-proposed -m "Unbuildable set of entangled packages with ucommon - See Debian #716855" ucommon libccrtp libzrtpcpp sipwitch libexosip2 libosip2 linphone siproxd
[15:50] <Riddell> lovely, thanks ScottK
[15:50] <ScottK> So now it'll be back to the older versions in -release, which work.
[15:50] <Riddell> I'll rebuild kopete in ninjas
[16:04] <Riddell> hmm plasma-runners-addons  Breaks: kamoso (<< 2.0.2+)
[16:06] <Riddell> but there's no such thing as 2.0.2+ in debian
[16:08] <Riddell> mm it'll be the youtube icon but that's been renamed
[16:11] <ScottK> afiestas: Mabye we need a new kamoso release ...
[16:13] <Riddell> ah it's a packaging bug
[16:13] <afiestas> ScottK: yes :/
[16:13] <Riddell> but yeah a new kamoso release with those youtube icons renamed would make sense
[16:14] <afiestas> and with kipi plugin 2 support
[16:14] <afiestas> bleh, will do the release today
[16:14] <afiestas> though I don't have a webcam to test so I will need your help :p
[16:16] <afiestas> ScottK: Riddell can you try branch 2.1 ?
[16:16] <afiestas> don't mind the 2.1, we can release it as 2.0.2 if you need it that way
[16:17] <ScottK> 2.1 is fine.
[16:17]  * Riddell git clones kamoso
[16:18] <Riddell> afiestas: I want to do  git checkout remotes/origin/2.1 ?
[16:18] <afiestas> it should work just with
[16:18] <afiestas> git checkout 2.1
[16:19] <Riddell> oh problem, my webcam doesn't seem to be working
[16:19] <Riddell> it wasn't working with google handouts when we tried either
[16:20] <Riddell> anyone else able to help?
[16:24] <Riddell> afiestas: compiles and runs fine but my webcam doesn't want to work so not a good tester
[16:24] <Riddell> !testers | kamoso 2.1
[16:25] <ScottK> OK, so I see the kopete build failed.
[16:25] <ScottK> I did rebuilt 4.10.97 successfully.
[16:26] <Quintasan> Riddell: I'm on it
[16:29] <Riddell> Quintasan: on kamoso?
[16:29] <Quintasan> Yes
[16:30] <Quintasan> afiestas: there is 2.0.2 and origin/2.1 branch, which one is it?
[16:30] <afiestas> 2.1
[16:31] <afiestas> 2.0 shouldn't be building with libkipi
[16:31] <Riddell> "protocols/jabber/googletalk/libjingle/talk/session/phone/linphonemediaengine.cc:203:57: error: 'AudioStream' has no member named 'ms'"
[16:32] <Riddell> this stuff is way more trouble that it's worth
[16:32] <ScottK> If you drop that, you can drop my changes to make it build on ppc
[16:35] <Quintasan> afiestas: Anything in particular I should look out for or general functionality testing will suffice?
[16:35] <Riddell> Quintasan: send us a mugshot!
[16:35] <afiestas> Quintasan: gneral functionality plus Youtube upload (that shouldn't wprk)
[16:39] <Quintasan> Riddell: http://wstaw.org/m/2013/08/12/picture_1.png
[16:39] <Quintasan> :D
[16:40] <Quintasan> afiestas: I need kipi-plugins to get yt upload?
[16:43] <afiestas> Quintasan: in theory no
[16:43] <afiestas> you need libkipi though
[16:45] <Quintasan> in practice I don't see YT upload option
[16:45] <Quintasan> hmm
[16:45]  * Quintasan rebuilds
[16:46] <Riddell> Quintasan: sexy times!
[16:47] <Quintasan> I really need to retake my profile picture
[16:47] <Quintasan> this time in HD
[16:48] <Quintasan> okay
[16:48] <Quintasan> afiestas: I have absolutely no idea how to try sending that video to YouTube :D
[16:48]  * Quintasan can't find any option to do that
[16:49] <afiestas> Quintasan: right click on the thumbnails?
[16:49] <Quintasan> afiestas: Trash or Open options there only
[16:49] <afiestas> uh
[16:49] <afiestas> that shouldn't happen
[16:49] <Quintasan> ii  libkipi10            4:4.10.2-0ubunt amd64           library for apps that want to use kipi-plugins
[16:49] <Quintasan> So libkipi is installed
[16:49] <Riddell> did it compile against it?
[16:50] <afiestas> do you have libkipi20 ?
[16:50] <Riddell> how about libkipi-dev ?
[16:50] <Quintasan> installed
[16:50] <Quintasan> and no libkipi20
[16:50] <Riddell> libkipi-dev and libkipi11
[16:50] <Riddell> ldd /usr/bin/kamoso | grep kipi
[16:50] <Riddell> should say /usr/lib/libkipi.so.11
[16:51] <Quintasan>         libkipi.so.10 => /usr/lib/libkipi.so.10 (0x00007ffbd57c3000)
[16:51] <Quintasan> It's linking against 10, guess I need to find my saucy vm
[16:51] <Quintasan> to try with 11
[16:53] <baltolkien> Akonadi and Nepomuk works in Kubuntu with KDE 4.11 RC?
[16:55] <Quintasan> baltolkien: I see no reason why it shouldn't
[16:55] <Blizzz> baltolkien: i lost my believe akonadi will work reliably one day
[16:55] <baltolkien> Well, In my laptop doesn't work
[16:55] <baltolkien> I just upgrade but doesn't work :(
[16:56] <baltolkien> Akonadi don't register at D-Bus
[16:58] <jbicha> is qt5 ok for transmission? or do you need this reverted for now? https://launchpad.net/ubuntu/+source/transmission/2.82-0ubuntu1
[16:58] <Riddell> Quintasan: you don't need saucy, you need kde sc 4.11
[16:58] <Riddell> Quintasan: what do you have?
[16:58] <Quintasan> 4.10 since I'm on my laptop
[16:59] <Quintasan> looking for the vm I have
[16:59] <jbicha> never mind, I guess you don't ship transmission by default anyway
[16:59] <Riddell> jbicha: um, I don't know, I've never used it
[17:01] <Riddell> jbicha: so you'd be as good testing it as anyone I guess
[17:06] <Quintasan> Riddell, afiestas: Uh, for yt upload it might take a while but the rest of Kamoso works normally
[17:06] <Quintasan> I can take pictures and videos and whatnot
[17:07] <Riddell> Quintasan: not got 4.11 installed?
[17:08] <Quintasan> Not on my laptop. I'd rather have stable stuff there installed
[17:08] <Quintasan> Riddell: My PC is running saucy but I'm back in hometown now so no access to it
[17:10] <Riddell> 4.11 is two days away from being stable :)
[17:10]  * Riddell uploads 4.11 to ninjas for raring
[17:16] <Blizzz> (except for akonadi, that is two eternities away – sorry for being grumpy)
[17:16] <ScottK> jbicha: Did you see http://perezmeyer.blogspot.com/2013/08/qt-in-debian-using-qt4-andor-qt5-in.html
[17:18] <jbicha> ScottK: I just added qt5-default to build-depends and transmission-qt built and ran which was good enough for me
[17:18] <ScottK> Yeah, that should be enough.
[17:25] <Riddell> ScottK: you're a debian ftpmaster?
[17:25] <ScottK> FTP assistant, but yes.
[17:25] <Riddell> elite :)
[17:28] <Quintasan> ScottK is so 1337 words are not enough :D
[17:28] <yofel> Quintasan: are the kipi-plugins installed
[17:28] <yofel> ?
[17:29] <Quintasan> yofel: Yes, they are. I already removed everything and I'm setting up virtualbox
[19:12] <jussi> yofel shadeslayer valorie please + or - the tshirts thing on the list
[20:59] <valorie> will do
[20:59] <valorie> I still want a polo though
[22:48] <ScottK> Riddell and shadeslayer: Are you in the "Blue Systems developers working on Frameworks in August" group?
[23:04] <Riddell> ScottK: group where?
[23:23] <ScottK> Riddell: http://agateau.com/2013/08/12/frameworks-5-push


[01:29] <OvenWerks> Eickmeyer: dl from https://launchpad.net/ubuntu/+source/zita-ajbridge/0.8.4-1ubuntu<IP_ADDRESS>/+build/19742691
[01:30] <Eickmeyer> OvenWerks: Or enable focal-propsed.
[01:30] <OvenWerks> installed tested (in more ways than one. The cpu does not seem to change at all and best yet, it appears controls will require no changes
[01:31] <OvenWerks> where do I record a success
[01:31] <OvenWerks> on the bug page?
[01:31] <Eickmeyer> Ok, then comment in the bug report your findings, change the verification-needed and verification-needed-focal tags to verification-done and verification-done-focal respectively.
[01:32] <Eickmeyer> Then we just wait 7 days for it to gestate in proposed and it'll get moved to updates.
[01:32] <Eickmeyer> And then, theoretically, included in 20.04.1.
[01:32] <OvenWerks> good
[01:41] <Eickmeyer> OvenWerks: I see you changed the tags, did you comment the success?
[01:42] <OvenWerks> just doing that
[01:43] <OvenWerks> Ok done, does it read ok?
[01:44] <OvenWerks> I think I can remove some of the delays I added to get around this problem
[01:44] <OvenWerks> Eickmeyer: ^^^
[01:51] <Eickmeyer> OvenWerks: Looks good. If you want to go ahead and remove the delays, that might be good.
[02:33] <OvenWerks> shorten maybe, I don't think I can remove. Alsa sometimes gets reset which sends a device removed and reinserted. It is good to wait till that is done then check if the device is really gone/there before proceeding.
[02:34] <Eickmeyer> Yeah, definitely.
[19:11] <OvenWerks> Eickmeyer: new version of controls... may need to wait so it can depend on new version of zita-ajbridge.
[19:12] <OvenWerks> or I guess it can be added to groovy but not backports till the new version of zita is out.
[19:12] <Eickmeyer> OvenWerks: Ok, sounds good. It'll take about a week for that to get through proposed.
[19:13]  * OvenWerks will continue testing till then.
[19:14] <Eickmeyer> One thing that came up in the past was, "Why did you backport and not SRU this?" so that's why something as small as zita-ajbridge was easy to SRU.