[02:49] <dtchen> does anyone have any opinions about the k3b + normalize-audio issue raised on kubuntu-devel?
[03:35] <Snowhog> k3b continues to have a coding 'error' with regard to the recognition of the installed package normalize-audio. Bug reports that go back four years still exist, and current reports still complain about the problem. See https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/45026 and comment #32 by
[03:35] <Snowhog> Vanessa Ezekowits who posted a simple shell script to overcome the programming 'error' in k3b, and which identifies the underlying problem. Any k3b maintainers care to take this on?
[03:45] <dtchen> Snowhog: well, we don't have k3b maintainers per se
[03:46] <dtchen> not to mention I just asked that question about an hour ago ;)
[03:46] <Snowhog> dtchen: Understand, I think, but someone/somebodies must be maintaining k3b, yes?
[03:48] <dtchen> Snowhog: as a practical matter, probably only in a passing manner
[03:51] <Snowhog> dtchen: I did attempt to send and email with the details to<EMAIL_ADDRESS>but got a reply that the list isn't open to non-members. Then claydoh replied and I provided him with what I tried to send. The work-around is to run a shell script that addresses the internal program error in k3b, but it would be nice if k3b it self was fixed/patched to fix this rather simple problem.
[03:52] <dtchen> Snowhog: yes, I've been looking at it. I'm surprised that upstream k3b maintainers haven't fixed it.
[03:52] <claydoh> simple, but more of a hack, right?
[03:53] <dtchen> it's a terribly hack IMO
[03:53] <claydoh> hai Snowhog my fine snowy friend :)
[03:53] <dtchen> terrible hack*
[03:54] <Snowhog> dtchen: Maybe so, but it does work. But yes, it would be much better if k3b were itself patched/fixed.
[03:54] <dtchen> what I haven't investigated tonight is whether Debian is carrying a specific customisation for normalize-audio such that we would need to do something ourselves, i.e., it becomes our problem and not upstream k3b's
[03:55] <Snowhog> dtchen: From what I gather, it's simply that k3b is version testing for normalize-audio instead of just checking for it's existance. I have no idea whether a specific version is required, but I'd think not, since this has been an issue for over four years now.
[03:56] <Snowhog> hey claydoh. Yeah, decided to raise the topic here. Be careful what you suggest! :)
[03:59]  * claydoh goes to bed
[04:03] <dtchen> huh. In Oneiric that script seems to do the wrong thing.
[04:03] <Snowhog> dtchen: http://machine-cycle.blogspot.com/2011/04/fixing-normalize-audio-feature-in-k3b.html contains the documentation/script I'm using to fix the k3b issue. Still a hack, but...
[04:03] <Snowhog> dtchen: I'm using the above script in Natty 64-bit.
[04:04] <dtchen> i.e.,
[04:04] <dtchen> 127|crimsun@errno:~$ normalize --version | sed -e 's/normalize /normalize-audio/g'
[04:04] <dtchen> No command 'normalize' found, did you mean: Command 'vnormalize' from package 'lipsia' (universe)
[04:04] <dtchen> normalize: command not found
[04:04] <valorie> Quintasan: also, "grok"
[04:04] <dtchen> which isn't surprising, since the normalize-audio package doesn't ship a normalize executable
[04:05] <dtchen> I guess the package's original normalize-audio is renamed to normalize?
[04:05] <valorie> oops, scroll error
[04:05] <Snowhog> dtchen: That's what I read in one of the bug comments.
[04:09] <dtchen> ok, well, I just answered my own question above. It looks like the upstream normalize is actually normalize-audio in Debian, and as a result, rgreening applied a patch way back in Sept '09 to use that executable name
[04:14] <dtchen> eek, Vcs entries are outdated
[04:15] <Snowhog> dtchen: When I installed normalize-audio in Kubuntu 11.04, k3b reported it, but without a path, so was showing as 'not found'. When I created/ran the script in http://machine-cycle.blogspot.com/2011/04/fixing-normalize-audio-feature-in-k3b.html, k3b then properly reported it with it's path.
[04:18] <dtchen> bzr branch lp:~kubuntu-packagers/kubuntu-packaging/k3b
[04:19] <dtchen> ...and it looks like we?someone? needs to check in jr's latest changes
[04:26] <dtchen> crimsun@errno:~/Code/Kubuntu-packagers/k3b$ bzr push
[04:26] <dtchen> Using saved push location: bzr+ssh://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/k3b/
[04:26] <dtchen> Pushed up to revision 28.
[04:26] <dtchen> ok, now to look at this normalize-audio mess...
[04:47] <dtchen> ok, so the problem is, of course, the binary being 'normalize-audio', but the version string being 'normalize 0.7.7'
[04:48] <Snowhog> dtchen: Yes, that is correct.
[04:49] <dtchen> it's rather daft that externalBinManager()->foundBin() assumes the string will always match the executable name
[05:00] <Snowhog> dtchen: Looking at normalize-audio with apt-cache show indicates that normalize-audio replaces normalize. So the problem, as you indicate, is that the coding that originally worked for the 'normalize' package, doesn't for the replaced package normalize-audio.
[05:02] <dtchen> Snowhog: right, and the gist of the issue is that externalBinManager() needs to grow to accept an actual executable name, not just assume the executable name is identical to the "program name" string preceding the version string
[05:03] <dtchen> the more I look at it, the more it seems it will be a Debian- /Ubuntu-specific delta. :-(
[05:03] <Snowhog> dtchen: So, is this a 'fixable' issue? It's been way to long - four+ years - that the problem has existed without resolution.
[05:03] <dtchen> Snowhog: well, it's able to be worked around
[05:03] <dtchen> "fixed" is rather imprecise, I'm afraid
[05:03] <Snowhog> dtchen: That is true, but 'normal' users won't figure it out.
[05:04] <dtchen> AFAIK upstream k3b would likely be concerned, this is a Debian- /Ubuntu-specific corner case
[05:04] <Snowhog> dtchen: And getting that group to address it is doable??
[05:05] <dtchen> Snowhog: you're in that group's midst
[05:05] <dtchen> and however (un)fortunate it may seem, I don't know if anyone else is going to take up the mantle
[05:05] <Snowhog> dtchen: hehe
[05:11] <Snowhog> dtchen: From a July 2010 reply to the bug: Downloading the normalize code, and making the fix to src/normalize.c fixes the issue.
[05:12] <Snowhog> dtchen: That is, if you want to fix the source and recompile. Again, normal users should not have to do that.
[05:13] <dtchen> Snowhog: yeah, but we also don't know who else is relying on that precise string
[05:14] <Snowhog> dtchen: Isn't the basic problem that the comparison criteria is to strict? Can the check be made looser?
[05:14] <dtchen> if we change the source to print out argv[0] (which arguably is the right thing to do), we might break some other user
[05:14] <dtchen> IMO the check isn't too strict, it's plain inflexible
[05:14] <Snowhog> dtchen: hehehe
[05:15] <Snowhog> dtchen: Am I correct in assuming/believing, that k3b is a mainstream KDE application, and as such, should be coded to be complient with any KDE Linux distro?
[05:20] <dtchen> Snowhog: I don't think that's particularly revelant in this context
[05:20] <dtchen> relevant*
[05:20] <dtchen> sheesh, 1 AM and everything goes to shot
[05:22] <Snowhog> dtchen: Well, I'm happy at least, that someone 'in the know' (you) has looked at it and seen where the problem lies. One can hope that a viable solution can be arrived at and included in a future release of k3b. As said, four+ years of this issue is a bit 'long in the tooth'.
[05:32] <Snowhog> dtchen: Thank you for looking at this, and the discourse. I'm off for the evening, but I'll check back in tomorrow.
[07:05] <jussi> apachelogger: <3 :)
[07:37] <bambee> morning
[07:52] <dpm> Hi Kubuntu devs. A KDE translator asked me why he couldn't see the latest KDE translations in Launchpad, and it turns out that there hasn't been an upload of the kde-l10n-* packages for a while. When you've got a minute, may I ask you to upload these packages for Oneiric?
[07:57] <debfx> apachelogger: ^
[09:01]  * apachelogger waves fist because of work
[09:29] <Quintasan> \o
[09:36] <Quintasan> apachelogger: ping
[09:36] <Quintasan> hmm
[09:36] <Quintasan> more like DarkwingDuck
[09:38]  * apachelogger waves fist more and more
[10:38] <apachelogger> yofel: ping
[10:58] <shadeslayer> yofel: i have no idea, it built fine here, twice
[10:58] <debfx> apachelogger: want to review my pkg-kde-tools l10n changes before I upload? https://bazaar.launchpad.net/~kubuntu-packagers/pkg-kde-tools/pkg-kde-tools/revision/322
[10:59] <shadeslayer> yofel: i'm a bit busy this week, will be back to work on monday
[11:00] <apachelogger> Oo
[11:00] <apachelogger> I just got a comment on the most original neon post
[11:00] <apachelogger> wtf
[11:00] <shadeslayer> what
[11:00] <apachelogger> debfx: why merge findfiles from stable?
[11:02] <debfx> apachelogger: that is what's used once the development version is branched
[11:03] <apachelogger> oh
[11:03] <apachelogger> rules also grabs stable
[11:03] <apachelogger> well
[11:03] <apachelogger> fair enough
[11:03] <apachelogger> debfx: looks good to me, I think we shoudl do something about the wget though
[11:04] <apachelogger> plz report a bug and assign it to me and add it to the packaging blueprint
[11:05] <debfx> how do you want to change that?
[11:05] <debfx> (without cloning the whole repository)
[11:07] <apachelogger> shallow clone
[11:07] <apachelogger> or perhaps I get a better idea
[11:25] <debfx> we have quite some QA issues regarding patches
[11:26] <debfx> I've just removed 3 patches from kde-workspace that were either refreshed wrongly or upstream reverted the commit
[11:40] <apachelogger> debfx: who uploaded it?
[11:44] <debfx> apachelogger: I haven't tracked down when those patches were refreshed
[11:45] <apachelogger> debfx: probably bambee did not revert all changes or someone uploaded the wrong workspace
[11:45] <apachelogger> I know that the first proposed workspace merge was bogus WRT patches
[11:46] <bambee> apachelogger: I've reverted all patches
[11:47] <bambee> I have just refreshed the broken ones
[11:48] <bambee> debfx: what was the problem?
[11:49] <debfx> apachelogger: they were broken even before this cycle
[11:49] <apachelogger> all kaput
[11:49] <apachelogger> win win win
[11:50] <debfx> bambee: nothing with your changes, just our patches being broken in general
[11:50] <bambee> oh :)
[12:21]  * apachelogger is overengineering the l10n rules
[12:21] <apachelogger> \o/
[12:22] <debfx> your time would be better spent reviewing patches ;)
[12:24]  * apachelogger should be doing phonon things
[12:33] <CIA-52> [kde-l10n-common] Harald Sitter<EMAIL_ADDRESS>*<EMAIL_ADDRESS>* debian/ (README.source build-l10n.sh changelog control rules) (log message trimmed)
[12:33] <CIA-52> * Introduce new targets: - get-l10n: called by the build script and -
[12:33] <CIA-52> get-desktop: prerequisites all targets to get desktop file translations -
[12:41] <Quintasan> http://blog.linuxmint.com/?p=1791
[12:41] <Quintasan> LOLOLOLOLOLOL
[12:43] <Quintasan> >http://blog.linuxmint.com/?p=1791
[12:43] <Quintasan> bleh
[12:43] <Quintasan> >The lack of performance and the amount of resources needed by the Kubuntu base were identified as an issue
[12:44] <Quintasan> so they will be switching to Debian KDE packages
[12:44] <Quintasan> lol
[13:24] <shadeslayer> Quintasan: lol
[13:25] <shadeslayer> good luck having a rolling release with Debian ^_^
[13:26] <cdbs> I'm running Ubuntu Oneiric. Have all the KDE 4.6.90 packages landed? Is it okay to install and test kubuntu-desktop right now or should I wait more?
[13:27] <shadeslayer> cdbs: please see the topic\
[13:28] <cdbs> *ahem* okay
[13:28]  * cdbs decides to wait
[13:29] <debfx> everything you get with kubuntu-desktop should be uploaded
[13:30] <debfx> you might want to test it in a VM first though :)
[13:31] <cdbs> thanks
[13:32] <Quintasan> shadeslayer: more like, how can our packages really differ performance-wise from Debian's?
[13:32] <Quintasan> We are using the same base and we don't build some stuff
[13:32] <shadeslayer> well that too
[13:33] <Quintasan> Unless we are doing something horribly wrong performace-wise they should be the same
[13:33] <shadeslayer> but Debian more or less focusses on stability
[13:33] <Quintasan> the blog post mentions use of resources
[13:33] <shadeslayer> ( thats the impression i get anyways )
[13:33] <Quintasan> That's very ambiguous term
[13:33] <Quintasan> Whatever
[13:34] <shadeslayer> ^^
[13:34]  * Quintasan goes for a beer
[13:34] <cdbs> Is Debian also moving to 4.7?
[13:34] <cdbs> The last time I checked, they were on 4.4
[13:34] <Quintasan> They will someday
[13:35] <debfx> Quintasan: do you know which packages are missing in the package set?
[13:35] <debfx> at least libkexiv2 and libkipi
[13:37] <Quintasan> debfx: kdegraphics-thumbnailers
[13:38] <Quintasan> marble
[13:38] <Quintasan> parley
[13:38] <Quintasan> rocs
[13:38] <Quintasan> ksnapshot
[13:39] <Quintasan> debfx: nothing else comes to mind nor is not returned by grep
[13:43] <debfx> ok, thanks
[13:58] <yofel> o/
[13:58] <yofel> apachelogger: pong?
[13:59] <debfx> ScottK: do you know what happened to the live images?
[13:59] <ScottK> They've been failing recently, I think due to /run stuff, but I'm not sure.
[14:01] <yofel> cdbs: Debian has 4.6 in unstable, not sure how much of 4.7 they did yet. I only know they did some of the language bindings
[14:02] <debfx> too bad, would be interesting to know if everything is installable
[14:04] <apachelogger> yofel: how is the blog post?
[14:04] <yofel> debfx: I'll do a check in a chroot, but I believe there was something that didn't work yet
[14:04] <yofel> apachelogger: []
[14:05] <yofel> ah good, kross is in
[14:07] <yofel> debfx: in fact now, kubuntu-desktop has no dependency issues in O
[14:08] <apachelogger> my google exploded
[14:08] <yofel> again o.O?
[14:09] <debfx> yofel: ah good, there are still a some upgrade issues
[14:09] <debfx> hopefully the kdegraphics-libs-data transitional package will fix that
[14:10] <yofel> I'll install the packages as a test
[14:11] <yofel> went fine, so I believe the only breakage in oneiric should be the /run business
[14:12] <yofel> hm, wasn't gwenview in the default install?
[14:12] <yofel> (which isn't uploaded yet thanks to broken licensing)
[14:12] <yofel> I'll file a bug about that
[14:13] <debfx> oh how I love file overwrite errors
[14:13] <debfx> (thanks to missing epochs)
[14:14] <yofel> I found the overwrite errors that come from 4.6.4/5 -> 4.6.90 uprades thans to << 4:4.6.3-1ubuntu1 replaces more fun
[14:16] <apachelogger> yofel: what is with gwenview licensing?
[14:16] <apachelogger> just fix it already
[14:16] <yofel> apachelogger: the docs have the license comment out, thus no license
[14:16] <yofel> *commented
[14:17] <apachelogger> oh yeah
[14:17] <apachelogger> I told agateau already
[14:18] <yofel> well, not fixed
[14:18] <apachelogger> someone simply fix it :P
[14:18]  * yofel thinks apachelogger would be the ideal person to do that
[14:18] <apachelogger> bug 794513 is going to get beatin for removing quanta
[14:18] <apachelogger> yofel: no time
[14:18] <yofel> ...
[14:18] <apachelogger> I got you commit access
[14:19] <apachelogger> so use it :P
[14:19] <yofel> I don't mind adding license copies, but I'll try to get some gwenview dev first before changing the licensing
[14:19] <agateau> yofel: apachelogger can you refresh my memory regarding this issue?
[14:20] <apachelogger> agateau: you comment out the FDL license markup in your documentation as to work around missing FDL copy problems
[14:20] <apachelogger> which in turn is a problem as now your documentation is not licensed at all
[14:20] <apachelogger> which makes it non-free content
[14:21] <debfx> ScottK: I've put 2 packages into NEW for you
[14:21] <agateau> apachelogger: what would be the best solution in your opinion? license it as GPL or FDL?
[14:22] <yofel> every other package uses FDL, so I would say keep that
[14:22] <yofel> you've got the FDL statement already in there, just commented out
[14:22] <apachelogger> IMHO the question should be FDL or CC, GPL is a terribly unsuitable license for documentation IMHO
[14:23] <apachelogger> agateau: I'd go with FDL, all other KDE documentation is
[14:23] <yofel> + a full copy of the GFDL-1.2 is missing as COPYING.DOC
[14:26] <agateau> apachelogger: sounds good, but I need to contact the doc authors before doing this change
[14:27] <apachelogger> sure
[14:27] <apachelogger> so, I think our new l10n rules are ready
[14:28] <CIA-52> [kde-l10n-common] Harald Sitter<EMAIL_ADDRESS>*<EMAIL_ADDRESS>* debian/config add config, all should be good now
[14:45] <ScottK> debfx: Looking
[14:50] <ScottK> yofel or debfx: Did patches/step_needs_-lcln.diff go upstream?
[14:51] <ScottK> step accepted.
[14:53] <agateau> yofel: apachelogger: just sent a mail to ask doc authors their agreement on licensing Gwenview doc under FDL
[15:01] <apachelogger> debfx, dpm: we have a good chance at breaking all of KDE l10n this cycle
[15:01] <apachelogger> preparing packages right now
[15:02] <dpm> apachelogger, oh, why's that?
[15:02] <yofel> agateau: thanks
[15:03] <yofel> ScottK: looking at it again
[15:03] <apachelogger> dpm: all sorts of upstream changes
[15:04] <apachelogger> naming, architectural etc.
[15:04] <debfx> ScottK: no, it's an undocumented patch from Debian
[15:04] <apachelogger> we really need some better implementation for all this
[15:04] <apachelogger> too much possibility of failure
[15:04] <apachelogger> s/of/for/g
[15:04] <kubotu> apachelogger meant: "too much possibility for failure"
[15:05] <ScottK> debfx: Looks like something ~straightforward to go upstream.
[15:05] <yofel> ScottK: actually, I believe we can drop that
[15:05] <yofel> from cmake:
[15:05] <yofel> -- qalculate found and cln is:-lcln
[15:06] <ScottK> It's not worth having more diff from Debian over.
[15:06] <dpm> apachelogger, ok, let me ask you more about this tomorrow (finishing off my UDW talk right now)
[15:06] <ScottK> See if they'll drop it.
[15:08] <yofel> svuorela added that in 4.6.96 "* Add patch to also build with -lcln when building step with qalculate"
[15:08] <yofel> step seems to build prefectly fine without that though
[15:09] <yofel> errr... 4.2.96
[15:10] <ScottK> step binaries accepted.
[15:11] <yofel> I'll drop it from bzr, it builds with -lcln even without the patch
[15:12] <ScottK> Talk to Debian too.
[15:19] <apachelogger> yofel: is rc2 wip already?
[15:20] <yofel> apachelogger: not yet, although I wanted to start with kdelibs in the evening
[15:20] <yofel> we were still fixing broken packages
[15:20] <debfx> could we please finish rc1 before that?
[15:21] <apachelogger> debfx: define finish
[15:21] <yofel> well, I would like to get gwenview, cantor and kate in at least before doing RC2
[15:21] <yofel> forget the other bindings
[15:22] <apachelogger> why is that?
[15:22] <yofel> I'll take a look at ksaneplugin
[15:22] <apachelogger> +gwenview is postponed anyway
[15:22] <debfx> upload kate, kdegraphics-strigi-analyzer, mobipocket and svgpart
[15:22] <yofel> well, kate is currently unfunctional in oneiric, cantor should be fine to upload, rc2 won't be different, and ok, forget gwenview
[15:22] <apachelogger> yofel: blog post?
[15:23] <yofel> apachelogger: do you want me fixing packages or spending hours on wondering what to write about our work?
[15:23] <debfx> and make sure upgrades work
[15:23] <apachelogger> yofel: I think I answered that question at least once
[15:23] <yofel> you did indeed -.-
[15:23] <apachelogger> well
[15:24]  * apachelogger starts writing a post then, if yofel doesnt have itme
[15:25] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/step] Philip Muškovac * 4 * debian/ (4 files in 2 dirs) drop step_needs_-lcln.diff since it's not needed anymore
[15:26] <yofel> I need to write a kubuntu.org post about RC1 (kde and kdepim) or users are going to kill us for not communicating.
[15:27] <debfx> is there a generic kde project on launchpad? we need one to link the packages to
[15:28] <yofel> https://launchpad.net/kde ?
[15:29] <debfx> yofel: I've tried that but it doesn't work
[15:29] <debfx> apparently you can't link them to project groups
[15:30] <yofel> :/
[15:33] <debfx> I'll just use the old projects like kdebindings
[15:33] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 7 * debian/copyright That's LGPL, not GPL
[15:35] <apachelogger> "we need one to link the packages to" why?
[15:35] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 8 * debian/copyright use the version of the BSD-3-clause license that's shipped with the package
[15:35] <yofel> apachelogger: upstream bug report links I believe
[15:35] <apachelogger> we do not track upstream reports
[15:35] <yofel> *shrug* then
[15:36] <ScottK> Upstream branches (which we also don't care about)
[15:36] <ScottK> Translation links (I don't think we care)
[15:36] <yofel> most of those are under project-neon/ anyway
[15:36] <ScottK> UDD branches (I don't think we care anyway)
[15:36] <yofel> we certainly don't
[15:40] <yofel> ksaneplugin should be fine to upload
[15:44] <debfx> I think it's useful to be able to add upstream bugs
[15:44] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/svgpart] Philip Muškovac * 9 * debian/control Fix Vcs links and control file layout
[15:45] <apachelogger> debfx: you can use any random kde project for that
[15:45] <apachelogger> for that reason it is a bug that the kde project cannot be used for that
[15:46] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/svgpart] Philip Muškovac * 10 * debian/ (control copyright libsvgpart.install) wrap-and-sort cleanups
[15:46] <debfx> apachelogger: right, file a bug against launchpad then
[15:47] <yofel> svgpart should be ready too
[15:50] <yofel> debfx: how's your build status page progressing btw.?
[15:59] <debfx> yofel: haven't worked on it any further
[15:59] <yofel> k
[16:10] <yofel> shadeslayer: *are* you going to fix kate soon? If not I'll do it
[16:11] <Quintasan> blargh
[16:11] <Quintasan> yofel: If you are looking for someone to upload then ping me
[16:12] <Quintasan> I will be reading a book
[16:12] <yofel> Quintasan: see wiki
[16:12] <Quintasan> yofel: cantor?
[16:12] <Quintasan> not in damn packageset
[16:12] <yofel> well, it's not up AT ALL
[16:13]  * Quintasan looks at it and uploads
[16:13] <yofel> ksaneplugin and svgpart aren't either. Recheck those though before upload
[16:13] <Quintasan> Why is r stuff commented out?
[16:13] <yofel> universe
[16:14] <Quintasan> and kalgebra is not in tarball?
[16:14] <ScottK> If cantor won't hit new I can upload it.
[16:14] <yofel> no, cmake detection broken upstream
[16:14] <Quintasan> :/
[16:15] <Quintasan> ScottK: Can you upload cantor? I don't really feel like uploading this and then getting to know it's rejected
[16:17] <Quintasan> shadeslayer: WRAP-AND-SORT FFS
[16:17] <yofel> ffs?
[16:17] <Quintasan> for !@#@#% sake
[16:17] <yofel> which package?
[16:17] <Quintasan> ksaneplugin
[16:17] <ScottK> Quintasan: Sure.
[16:17] <Quintasan> cantor too
[16:18] <yofel> cantor would be me, and I didn't know about w-a-s back then
[16:18] <Quintasan> ScottK: Thanks.
[16:18] <yofel> I did run wrap-and-sort on svgpart though
[16:18] <Quintasan> yofel: I see, but shadeslayer knew about that
[16:18] <yofel> not when he did ksaneplugin I believe ^^
[16:19] <ScottK> Quintasan: I don't see it got uploaded before.  Isn't it New source?
[16:19] <ScottK> That'll need me to acceptit.
[16:19] <Quintasan> ScottK: It is
[16:19] <ScottK> It is which?
[16:20] <Quintasan> It is entirely new package
[16:21] <ScottK> Which you can't upload because you aren't MOTU?
[16:21] <ScottK> debfx: Can you upload cantor so I can New it ^^^
[16:21] <Quintasan> oh wait
[16:21] <Quintasan> ...
[16:21]  * Quintasan uploads
[16:21] <ScottK> debfx: Nevermind
[16:22]  * Quintasan turn on his brain
[16:27] <Quintasan> grrrrr
[16:27] <Quintasan> shadeslayer: ping ping ping
[16:28] <Quintasan> ScottK: Please disregard ksaneplugin for now
[16:33] <Quintasan> shadeslayer: Fix ksaneplugin tarball and changelog
[16:34] <Quintasan> since they both suck
[16:34] <Quintasan> ScottK: cantor uploaded
[16:42] <yofel> Quintasan: what's wrong with the tarball? I can redo the changelog
[16:45] <Quintasan> yofel: let shadeslayer do
[16:45] <Quintasan> it
[16:51] <yofel> Quintasan: if he seriously wants to get back to work on monday then I'll rather fix it
[16:51] <Quintasan> lol
[16:51] <Quintasan> k
[16:51] <Quintasan> the changelog doesnt mention the repack
[16:53] <yofel> hm, then only the changelog should need fixing, what's wrong with the tar?
[16:58] <ScottK> cantor source accepted.
[16:58] <ScottK> or not.  lp fails
[16:59] <ScottK> Second try worked
[16:59] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 10 * debian/control fix hadling of versions in breaks/replaces
[16:59] <ScottK> Quintasan: Should I reject ksaneplugin?
[16:59] <Quintasan> ScottK: Please do
[16:59] <yofel> ScottK: yes please
[16:59] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 11 * debian/copyright remove trailing spaces
[17:00] <ScottK> Done
[17:01] <yofel> oh, akonadi 1.6.0 is out
[17:02] <yofel> I'll do that later
[17:07] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 12 * debian/ (changelog control) Add a proper changelog entry and description
[17:07] <Quintasan> yofel: tarball unpacks to ./
[17:07] <Quintasan> not ./ksaneplugin-4.6.90
[17:07] <yofel> well, description is still lacking, but I can't find anything more
[17:07] <yofel> didn't here...
[17:08] <Quintasan> Didn't?
[17:08] <yofel> oh wait, you're right...
[17:08] <Quintasan> :/
[17:08] <yofel> dpkg-source unpacked it in ksaneplugin-4.6.90+repack/, but the tar indeed has ./
[17:09] <yofel> repack1 is in order...
[17:10] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 13 * debian/changelog repack again
[17:12] <yofel> Quintasan: new tar uploaded to ninjas
[17:21] <Quintasan> yofel: Thanks
[17:24] <CIA-52> [kde-l10n-common] Harald Sitter<EMAIL_ADDRESS>*<EMAIL_ADDRESS>* debian/ (build-l10n.sh changelog) releasing version 4:4.6.90-0ubuntu1
[17:25] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/akonadi] Philip Muškovac * 31 * debian/changelog New upstream release
[17:47] <yofel> cool, kstars has missing license copies again
[17:47]  * yofel fixes
[18:41] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/kstars] Philip Muškovac * 2 * debian/ (not-installed changelog control copyright) fix up packaging
[18:42] <yofel> ok, this should be right now except that libindi in the archive is too old (but it's optional)
[18:52] <Quintasan> yofel: Thanks for fixing ksaneplugin, uploading
[19:00] <Quintasan> ScottK: Are seriously considering moving to alioth or it's just a suggestion?
[19:01] <Quintasan> ScottK: Also, ksaneplugin uploaded, this time it is working
[19:03] <ScottK> Quintasan: I think it's worth discussing.
[19:03] <ScottK> For our packaging branches it doesn't matter if they are in LP or not.
[19:04] <Quintasan> It certainly doesn't
[19:04] <Quintasan> I can do git-buildpackage -S as well
[19:04] <Quintasan> Are there any benefits?
[19:05] <yofel> uh, you'll have a sane VCS?
[19:05] <Quintasan> Is bzr THAT insane?
[19:05] <ScottK> bzr is fine.
[19:05] <yofel> well, not really, but it would make working with debian easier
[19:07] <Quintasan> That's a benefit.
[19:10] <yofel> bah, cantor failed on armel :/
[19:15] <yofel> yay, rosetta spam again...
[19:21] <yofel> ScottK: do you get what's wrong on https://launchpadlibrarian.net/75126316/buildlog_ubuntu-oneiric-armel.cantor_4%3A4.6.90%2Brepack1-0ubuntu1_FAILEDTOBUILD.txt.gz ?
[19:22] <yofel> according to launchpad libspectre was built on armel...
[19:23] <ScottK> Looking
[19:23] <ovidius> hi, i don't know where to ask my question. please just say if i am wrong here. i want to make a small patch to kmail in the experimental ppa. I installed the build-deps and the source from the ppa. Fine so far.  dpkg-buildpackage takes some time (some hours to be exact on my rather slow laptop) is there something like a build service? or how do you test patches for such a big package? any help/hint/link appreciated.
[19:25] <ScottK> ovidius: If you have an LP account you can have your own PPA for this
[19:26] <ScottK> yofel: What happens if you try to install libspectre1 on your armel box in a oneiric chroot?
[19:26] <yofel> ScottK: checking
[19:28] <ScottK> ksaneplugin source accepted.
[19:34] <yofel_> this totally doesn't make sense: http://paste.kde.org/95779
[19:42] <yofel> ScottK: aptitude:   libgs9: Depends: libgs9-common (= 9.02~dfsg-2ubuntu1) but it is not going to be installed.
[19:42] <yofel> archive inconsistency I guess
[19:46]  * yofel makes an attempt of building kdelibs 4.6.95 on armel..
[19:48] <debfx> yofel: https://felix.fobos.de/kubuntu/kubuntu-buildstatus.htm
[19:49] <debfx> ping me if a package is missing
[19:50] <yofel> kubotu: order cookies for debfx
[19:50]  * kubotu slides a whole bunch of world's finest cookies down the bar to debfx.
[19:50] <yofel> debfx++
[19:51] <ScottK> yofel: https://launchpad.net/ubuntu/+source/ghostscript/9.02~dfsg-3ubuntu1/+build/2623476 is the reason
[19:51] <yofel> :/
[20:06] <yofel> debfx: kde4libs is missing on your page. kdelibs is kde3
[20:07]  * debfx blames the wiki
[20:09] <ScottK> ksaneplugins binaries accepted.
[20:19] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/kdelibs] Philip Muškovac * 363 * debian/ (14 files) those symbols aren't i386 specific
[21:23] <Quintasan_> ScottK: Thanks
[21:34] <apachelogger> build failz
[21:34] <apachelogger> noooooooooooooooo
[21:34] <apachelogger> archive is kaput
[21:34] <apachelogger> bummer
[21:36] <Quintasan> lol
[21:37] <yofel> apachelogger: didn't you overtake kdemultimedia recently?
[21:39] <Quintasan> yofel: What was the patch that broke Wacom foo in Qt?
[21:40] <yofel> no idea, I didn't look at qt at all this cycle
[21:40] <Quintasan> ScottK: ^^
[21:48] <Quintasan> yofel: >Missing symbols >armel
[21:48] <Quintasan> sounds like fun
[21:48] <yofel> where?
[21:48] <Quintasan> https://felix.fobos.de/kubuntu/kubuntu-buildstatus.htm
[21:49] <yofel> yeah, but for kde4libs that's one symbol if I didn't see wrong
[21:49] <yofel> I'll do an armel build myself here over the night for 4.6.95, so let's see tomorrow
[21:50] <Quintasan> ehh
[21:50]  * Quintasan goes to bed
[21:50] <Quintasan> Good night
[21:51] <yofel> gn
[21:52] <ScottK> Quintasan: What was the question?
[21:52] <Quintasan> debfx: Did you ask cjwatson to add missing packages to packageset
[21:52] <ScottK> Quintasan: He did once today, but we've uploaded more since.
[21:52] <Quintasan> ScottK: What patch did break Wacom magic in Qt?
[21:54] <yofel> now, let's see if icecc over 2 qemu VMs works...
[21:55] <Quintasan> lol
[21:55] <yofel> hey, it's worth a try :P
[21:57] <Quintasan> yofel: [Neon] [recipe build #60630] of ~neon project-neon-phonon-vlc in oneiric: Chroot problem
[21:57] <Quintasan> lol
[21:57] <yofel> fun, ping lp folks
[21:58]  * yofel wonders when someone will bother to fix the java error for project-neon-kdesdk
[22:05] <yofel> o.O
[22:06] <apachelogger> yofel: I am lord president of kdemm
[22:06] <apachelogger> why be you asking?
 it just means there isn't enough people caring; I see no plans about kdenetwork either, and I poked kdemultimedia guys more than twice asking for feedback on how to split, no answer
 which kdenetwork guys are there?
 and which kdemultimedia guys are there ?
 yea, I'll admit both are kinda dead
[22:07] <yofel> about git splitting
[22:07] <apachelogger> the split was decided in randa, announced on the list and brought to direction of eean
[22:08] <apachelogger> I fail to see what else should have been done
[22:08] <yofel> well, povaddict seems to have slept through that ^^
[22:08] <apachelogger> perhaps write letters to everyone in kde and put cookies inside :P
[22:08] <yofel> hahaha
[22:09] <ScottK> Quintasan: kubuntu_28_xi2.1.patch
[22:10] <apachelogger> yofel: http://lists.kde.org/?l=kde-multimedia&m=130711637126292&w=2
[22:10] <ScottK> Quintasan: cnd still owes us a fix for oneiric.  natty is fixed.
[22:10] <apachelogger> the thread also contains some follow up discussion on why and problems and solutions and stuff
[22:10] <apachelogger> but the decision stands
[22:10] <yofel> ok
[22:11] <apachelogger> or at least no one bothered enough to challange it to the extent that we'd have to revert
[22:12] <Quintasan> >Lord President of KDE Multimedia
[22:12] <Quintasan> AHAHAHAHAHA
[22:33] <apachelogger> someone might want to retry l10n stuff once the chroot is fixed
[23:42]  * yofel was wondering why icecc failed and digged up debian bug 630504 :(
[23:42] <yofel> well, at least the workaround seems to work


[00:22] <clivejo> lovely, a wall of red
[00:28] <clivejo> mamarley: mind testing kde-l10n on YY
[00:28] <clivejo> ?
[00:30] <mamarley> clivejo: Installs cleanly. :)
[00:31] <clivejo> nice!
[00:31] <clivejo> would you happen to know why I cant uninstall  this - /var/cache/apt/archives/libcuda1-340_340.96-0ubuntu6_amd64.deb
[00:31] <clivejo> there is no script in the new version of the package
[00:33] <mamarley> clivejo: Yeah, that was the screwup with the Snap fix a while back.  The way to work around it is to edit the script that is failing and remove the call to systemctl in it.
[00:33] <mamarley> Sadly, I do not remember the exact location of the script.
[00:34] <clivejo> could you guide me through it?
[00:34] <clivejo> Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory
[00:35] <mamarley> Yeah, the problem is that I can't remember where the prerm scripts live
[00:35] <clivejo> any way for me to find out?
[00:36] <mamarley> Maybe your Google-fu is better than mine…
[00:36] <mamarley> clivejo: Wait, it is /var/lib/dpkg/info/
[00:37] <mamarley> The file should be something like libcuda1-340.prerm.
[00:37] <clivejo> libcuda1-340.prerm
[00:37] <mamarley> Yup, that's the one.
[00:38] <clivejo> got it
[00:39] <mamarley> There should be a line starting with "invoke-rc.d" somewhere in there.  Comment that out.
[00:39] <clivejo> http://paste.ubuntu.com/20944218/
[00:41] <mamarley> It is the "deb-systemd-invoke" one, sorry.
[00:42] <clivejo> still getting there is no script in the new version of the package - giving up
[00:42] <clivejo> theres a postrm there too
[00:42] <clivejo> edit that too?
[00:42] <mamarley> Is it that same package or a different one?
[00:43] <clivejo> all same package
[00:43] <clivejo> libcuda1-340.postrm
[00:43] <mamarley> Try removing the package entirely and then reinstalling it.
[00:43] <clivejo> it wont let me remove it
[00:43] <clivejo> the postrm has        systemctl --system daemon-reload >/dev/null || true
[00:43] <mamarley> What error?
[00:44] <clivejo> Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory
[00:44] <clivejo> var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it.
[00:44] <clivejo> Im using sudo dpkg --remove libcuda1-340
[00:45] <mamarley> And it isn't trying to remove or install any other packages at the same time?
[00:45] <clivejo> nope, just that one package
[00:45] <clivejo> seems to be stuck
[00:46] <mamarley> clivejo: What is your final goal here?  Are you trying to upgrade nvidia-340 to a later version?
[00:46] <clivejo> yes
[00:46] <clivejo> but it wont let me
[00:46] <clivejo> cant upgrage, cant remove
[00:47] <mamarley> clivejo: At this point, I would probably just remove the libcuda1-340 section from /var/lib/dpkg/status and then install the new one over the top.
[00:48] <mamarley> Just make sure the /lib/systemd/system/var-lib-snapd-lib-gl.mount file is gone because that is the only difference between those versions.
[00:48] <mamarley> Any other stuff left behind will just get overwritten by files from the new version.
[00:48] <clivejo> maybe if I created that file
[00:49] <mamarley> I don't even understand why it is trying to do anything with that unit since you commented out the command to stop it.
[00:51] <clivejo> ah
[00:51] <clivejo> got it
[00:52] <clivejo> https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1589006/comments/9
[00:52] <mamarley> Hmph, I don't get it.  Commenting out that line should have had the same effect…
[00:58] <clivejo> is the driver snapped?
[01:13] <clivejo> hi DarinMiller
[03:16] <DarinMiller> Hi clivejo! Do you ever sleep?
[04:32] <Mirv> santa_: yep
[04:50] <DarinMiller> :)
[05:12] <tsimonq2> I never sleep :P
[05:13] <tsimonq2> more work on packages! :D
[05:17] <Mirv> tsimonq2: 1. go 2. to 3. sleep :D
[05:17] <Mirv> I've read the backlog and worried :)
[05:18] <Mirv> good morning to everyone
[05:19] <Mirv> or should I say Qt morning everyone
[05:30] <tsimonq2> Mirv: I got a good amount of sleep :P
[05:30] <tsimonq2> Qt! \o/
[06:12] <tsimonq2> Mirv: what packages need to be looked at then?
[06:15] <tsimonq2> Mirv: (for the Qt transition)
[06:20] <Mirv> tsimonq2: everything that starts to be shown as red at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtbase-opensource-src in an hour or two. in my test run that included lots of lots of k* packages like kauth, kconfig, kcoreaddons, kcrash, kdbusaddons, kdeclarative, kdecoration.. I didn't look at the logs, there might be some problems causing many to fail. then aga
[06:20] <Mirv> in many passed too like kactivities, kcontacts, kdeprim-runtime, kdewebkit etc..
[06:21] <tsimonq2> Mirv: yay! work to do! :D
[06:30] <tsimonq2> Mirv: were there any lx* packages?
[06:32] <soee> hiho
[06:33] <tsimonq2> o/ soee
[06:33] <Mirv> tsimonq2: no, because they don't have autopkgtests so there weren't any to be run. here's the link to the Sunday's results http://people.ubuntu.com/~timo-jyrinki/excuses.html#qtbase-opensource-src
[06:33] <tsimonq2> oh okay
[06:33] <tsimonq2> maybe we need some ;)
[06:34] <Mirv> the links do work so some prestudying can be done before the real proposed results. clearly some build dep installability problems at least.
[06:34] <Mirv> maybe yes :)
[06:34] <tsimonq2> Mirv: and how do you do that on your own people.ubuntu.com? do you have special permissions? I'm an Ubuntu Member
[06:34] <tsimonq2> Mirv: or did you just download the page?
[06:34] <Mirv> tsimonq2: I saved the page before it disappeared, yes :)
[06:35] <Mirv> and now copied the html file over there from my computer
[06:35] <Mirv> luckily the executed autopkgtest runs are saved in the infrastructure
[06:35] <tsimonq2> alright :)
[06:36] <Mirv> tsimonq2: as for executing test runs, it's possible if you use the CI Train infrastructure, have a landing PPA and flip on the landers's "Approved" field. https://wiki.ubuntu.com/citrain/LandingProcess
[06:40] <tsimonq2> Mirv: how does that work?
[06:41] <Mirv> tsimonq2: as described on that page.. it's what is used for Ubuntu phone landings, but also open to others (but I think coredev is a requirement). mitya has for example used it for several landings.
[06:41] <Mirv> tsimonq2: so the page for this Qt 5.6.1 landing is https://wiki.ubuntu.com/citrain/LandingProcess
[06:42] <tsimonq2> Mirv: huh? that's the page?
[06:42] <Mirv> tsimonq2: on Sunday I clicked the Lander Signoff field and set it to "Approved" to get Automated Signoff starting, which means autopkgtests. that launched thousands of those tests and the results are on that excuses page.
[06:42] <Mirv> tsimonq2: I didn't now click the "Approved" because it would have again launched thousands of duplicate autopkgtests while I was going to hit the Publish button anyway..
[06:42] <Mirv> (and since I knew there will be failures it wouldn't have told me anything new)
[06:43] <Mirv> tsimonq2: all landings are shown on the front page https://requests.ci-train.ubuntu.com/
[06:43] <Mirv> tsimonq2: sorry, I pasted wrong link.. the page for Qt 5.6.1 landing https://requests.ci-train.ubuntu.com/#/ticket/1354:)
[06:45] <tsimonq2> Mirv: would you be able to hop over to #lubuntu-devel? I have some more questions about how it impacts LXQt and this isn't really the best place to ask :)
[06:46] <acheronuk> :D Qt 5.6
[06:49] <Mirv> tsimonq2: sure
[06:53] <acheronuk> Is it worth doing much with those tests for things that go red, as we have ppas full of newer versions build against Qt 5.6 that (I presume) yofel will upload?
[06:54] <acheronuk> answer is obvious for things we don't happen to have newer for
[07:10] <santa_> Qt mornings everyone
[07:10] <santa_> Mirv: thanks for all the info
[07:12] <tsimonq2> SANTA! :D
[07:12] <tsimonq2> lol
[07:15] <santa_> acheronuk: I'm planning to migrate my "ppa" to lxc containers / xenial today and I have some things in kubuntu automation to re-test so probably I will rebuild everything against the new Qt 5.6.1 packages
[07:40] <yofel> Mirv: no transition tracker for 5.6.1?
[07:44] <tsimonq2> o/ yofel
[07:44] <yofel> moin
[07:46] <Mirv> yofel: I've not used it, do you know how to get Qt there? I've usually been following a) CI Train https://requests.ci-train.ubuntu.com/#/ticket/1354 (tells which one are proposed and which in release), b) update_excuses.html c) update_output.txt in roughly that order
[07:47] <Mirv> yofel: plus Qt landings have included all known required rebuilds as part of the upload
[07:47] <acheronuk> morning :)
[07:47] <Mirv> moinmoin
[07:48] <yofel> ah right, then probably not worth it
[07:48] <yofel> Mirv: otherwise it would be gettingn the ben file added to https://code.launchpad.net/~ubuntu-transition-trackers/ubuntu-transition-tracker/configs
[07:49] <Mirv> ok the excuses page is updated finally: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtbase-opensource-src - everything in progress, queues very full http://autopkgtest.ubuntu.com/running.shtml
[07:49] <tsimonq2> o/ acheronuk
[07:49] <tsimonq2> \o/ Mirv
[07:50] <acheronuk> whooo..
[07:50] <tsimonq2> if I want to fix stuff that's failing there, what Git branch do I submit a PR against?
[07:51] <tsimonq2> yofel: ^
[07:51] <yofel> uhm, "none" technically, as we have no branch that strictly follows the archive
[07:51] <yofel> _archive is your best bet
[07:52] <tsimonq2> alright
[07:52] <yofel> maybe we should add something like _release
[07:53] <tsimonq2> that would be convenient for people like me who can't upload to the archive :D
[07:54] <yofel> not only that. I already had to monkey-patch _archive by branching off from the last uploaded tag and then merging back into _archive whenever I had to do an archive hotfix :/
[07:55] <yofel> I guess you could proposed a merge like *that*
[07:55] <tsimonq2> yofel: I would rather not XD
[07:55] <yofel> if we want to try fixing what's currently in the archive
[07:56] <acheronuk> unless sure it's also going to apply to the new stuff we have, is there much point?
[07:56] <yofel> probably not
[07:57] <yofel> I'll try to upload frameworks later, but will probably get some rejects
[07:57] <yofel> Mirv: could I rely on you to sponsor the missing parts if I give you the sources? Otherwise I'll just make things worse by uploading anything
[07:58] <acheronuk> ok. I'll be back lunchtime to see how this is going :)
[08:04] <Mirv> yofel: I'm happy to help if I'm just at computer. why would you make anything worse by uploading fixes? :)
[08:06] <tsimonq2> what needs to be done for this transition and how can I help?
[08:08] <yofel> Mirv: I would upload a new frameworks release, and I'm not sure in what state our package set is, so pieces might get stuck in depwait
[08:09] <yofel> Mirv: unless you would prefer to get stricktly just Qt through proposed for now
[08:17] <Mirv> yofel: well if you give me sources I could test rebuild it in a landing silo before copying to -proposed
[08:17] <Mirv> yofel: no I think I don't want you to try to get just Qt through since I guess it could be tremendous amount of work only to be repeated immediately after for the next frameworks etc uploads
[08:17] <Mirv> so better to just get it all in and get everything migrated in one go
[08:22] <yofel> Mirv: hm ok, so I guess I could generate the release set and throw that into a ppa for you to sync them over, or would you prefer all sources packages tarred up?
[08:24]  * yofel starts generating in any case
[08:25] <Mirv> yofel: copying from PPA sounds good
[08:25] <yofel> ack
[08:25] <Mirv> (no problem with tarball either though)
[09:09] <yofel> Mirv: https://launchpad.net/~yofel/+archive/ubuntu/staging3/+packages has frameworks building on top of landing-024. I'll watch it, but that take a day to build if left alone
[09:10] <yofel> the version ok for you or should I have added a suffix?
[09:10] <yofel> *that will take
[09:11] <tsimonq2> yofel: yay packages failing already :P
[09:11] <yofel> tsimonq2: where do you mean?
[09:11] <tsimonq2> yofel: the PPA you just listed
[09:11] <yofel> oh that, that's all DEPWAIT
[09:12] <yofel> frameworks has multiple dependency layers, which is why I said this would take a day ;)
[09:12] <yofel> and I forgot that I had arm enabled there...
[09:13] <tsimonq2> yofel: please don't tell me you had to edit all those debian/changelog files by hand! :)
[09:13] <yofel> no, we have a script for that
[09:13] <tsimonq2> oh okay
[09:13] <tsimonq2> yofel: it would be nice to have that script, where's it at?
[09:15] <yofel> tsimonq2: kubuntu-automation/ubuntu-archive-upload. Does changelog editing, source building and git tags.
[09:16] <tsimonq2> yofel: where?
[09:17] <yofel> tsimonq2: https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation
[09:18] <Mirv> yofel: so hmm, should I copy those to a landing PPA as those have all architectures enabled (also powerpc and s390x), and let it built there before copying the complete binaries to proposed? or simply copy those source of yours to proposed now and you will trigger the rebuilds as necessary?
[09:18] <Mirv> I'm still wondering about the best option..
[09:19] <yofel> Mirv: former probably? I could trigger rebuilds for the sources I have upload permissions for, but I'm not convinced that's the case for everything
[09:20] <yofel> I'll get the DMB to fix that after all the initial uploads are done and I could fix the seeds
[09:23] <Mirv> yofel: ok
[09:24] <yofel> Mirv: frameworks will probably not migrate without plasma, but for that I first need to look over the packages which I'll try to do over lunch
[09:25] <Mirv> yofel: here we go: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-041/+packages
[09:25] <yofel> Mirv: thanks
[09:26] <yofel> I'll wipe my ppa then
[10:07] <tsimonq2> yofel: does that landing PPA automatically rebuild, if not, it's done building everything (except for2  misc non-amd64/i386 builds )
[10:08] <tsimonq2> s/for2  /for 2 /g
[10:09] <tsimonq2> wait there's just a couple more but for the most part it's all done
[10:09] <yofel> I think it'll auto retry
[10:09] <yofel> but that's typically a bit slow
[10:09] <tsimonq2> oh wait, I'm dumb, I thought the square meant dep wait... :P
[10:09] <yofel> heh
[10:09] <tsimonq2> sorry
[10:10]  * yofel would love to have depwait on the overview, and not shown as ftbfs :/
[10:12] <tsimonq2> yeah
[10:13] <yofel> that's why we have our own PPA overview pages :P
[10:13] <tsimonq2> yofel: wooooooow https://launchpad.net/builders/
[10:14] <tsimonq2> yofel: those are some large build queues
[10:14] <yofel> not really, I've seen half-week long build queues
[10:14] <tsimonq2> O__O
[10:14] <yofel> although that's mostly during low-prio archive rebuilds
[10:14] <tsimonq2> oh alright
[10:15] <yofel> queue lenght doesn't tell much without knowing the build karma of a queue item
[10:16] <tsimonq2> oh yeah
[10:16] <tsimonq2> I forgot :P
[10:34]  * acheronuk prods LP
[11:07] <clivejo> tsimonq2: any progress on fixing cantor?
[11:11] <tsimonq2> clivejo: frustration :P
[11:11] <tsimonq2> just came up to get my phone, making food, let's talk in 30 mins
[11:11] <yofel> does neon have it?
[11:14] <acheronuk> yofel: they have Neon stable and unstable branchs, so yes looks like they are up to date on it?
[11:15] <clivejo> tsimonq2: ask when you get stuck :)
[11:15] <clivejo> I asked you to look at it for a reason, to help you learn!
[11:16] <clivejo> and cause I have a slight evil streak *evil laughs*
[11:17] <tsimonq2> gotta keep an eye on food, but yeah, I saw your reasoning, both of them :P
[11:17] <yofel> could someone update prison? seems like workspace wants 1.2.1
[11:17] <acheronuk> clivejo: same as I reason I suggested cervisia then :P
[11:17] <yofel> marble...? >.>
[11:17] <acheronuk> yofel: now that IS evil
[11:18] <yofel> :P
[11:18]  * yofel wonders if we want digikam from debian experimental
[11:21] <tsimonq2> what's that? :P
[11:21] <acheronuk> ha! Apps 16.08 is released on the day of the YY feature freeze. Hadn't noticed that.
[11:22] <yofel> tsimonq2: digikam? https://www.digikam.org/
[11:22] <yofel> acheronuk: well, beta is out already, but without qtwebengine...
[11:23] <yofel> I *guess* we could cut out everything pim..?
[11:23] <acheronuk> yeah, I know, it was just the ironic timing that struck me
[11:23] <yofel> acheronuk: beta release was on the 16.04.1 release day :P
[11:23]  * tsimonq2 kicks yofel :P
[11:24] <yofel> ouch!
[11:24] <tsimonq2> yofel: what's the deadline?
[11:24] <yofel> tsimonq2: well, feature freeze. Tough if we want 16.08 we should probably start with that a week before..
[11:25] <tsimonq2> yofel: alright
[11:26] <clivejo> libprison is to become a framework?  should I move git to LP?
[11:26] <yofel> dunno, is it?
[11:26] <clivejo> kdeconnect, why are you failing!
[11:27] <clivejo> eakk
[11:27] <clivejo> thought I heard somewhere it was
[11:27] <yofel> that repo is not a thing
[11:28] <yofel> well, maybe it will. For now workspace wants 1.2.1, and we have 1.2gitsomething
[11:28] <clivejo> git://anongit.kde.org/kdeconnect
[11:28] <clivejo> what changed
[11:29] <clivejo> it oh, its kdeconnect-kde
[11:29] <clivejo> did your script change that yesterday?
[11:29] <yofel> yes, I'll do another run
[11:31] <clivejo> maybe that why I thought its frameworks, debian has it under framework namespace
[11:31] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/frameworks/prison.git/
[11:33] <clivejo> yofel: your a "Debian Krap Maintainer" ?
[11:33] <clivejo> you're
[11:33] <yofel> oh, I forgot that I did an upload for that once
[11:33] <yofel> well, it's krap :P
[11:33] <clivejo> LOL
[11:33] <acheronuk> http://i.imgur.com/to5dV2y.png
[11:34] <acheronuk> LOL. I must have found that at about the same instant you did!
[11:34] <clivejo> acheronuk: are you working on it?
[11:34] <acheronuk> I went to have a look to what on earth prison was. oops
[11:35] <acheronuk> *to see
[11:35] <acheronuk> clivejo: never touched it
[11:35] <clivejo> if you wanted to try it
[11:35] <clivejo> could do it together
[11:35] <yofel> urgh
[11:36] <yofel> clivejo: can you please rename the lp repo to kdeconnect-kde? Otherwise the ci script barfs
[11:36] <clivejo> temp or perm?
[11:36] <yofel> perm
[11:37] <acheronuk> clivejo: what needs doing with it?
[11:37] <clivejo> just a new release
[11:37] <acheronuk> from where?
[11:38] <clivejo> yofel: is there an easy way to find a git repo on LP
[11:39] <yofel> either type in the url from your memory, or (seriously) google with 'site:launchpad.net <term>'
[11:40] <clivejo> I search in each page
[11:40] <clivejo> but there are about 6 pages on repo now
[11:41] <yofel> FWIW, the ci build hads the repo url in it
[11:41] <yofel> *has
[11:43] <clivejo> ok kdeconnect -> kdeconnect-kde and VCS updated in yakkety_archive and unstable branches
[11:44] <tsimonq2> clivejo: let me try another time and I'll let you know
[11:45] <tsimonq2> clivejo: another time being once more, I'm not postponing it
[11:47] <acheronuk> is prison 1.2.2 tagged anywhere?
[11:47] <acheronuk> *1.2.1
[11:47] <clivejo> nope!
[11:47] <clivejo> https://quickgit.kde.org/?p=prison.git
[11:48] <acheronuk> lovely
[11:48] <clivejo> yofel: see there is a frameworks and master branch
[11:48] <acheronuk> I would assume that KF5?
[11:49] <yofel> upstream depending on unreleased stuff again, lovely indeed
[11:49] <yofel> I'm *guessing* we need frameworks? Look up a committer in there and ask him
[11:50] <yofel> sooo... Riddell: why do we have a plasma release with optional deps on unreleased software? ^^
[11:50] <clivejo> yes, seeing as master hasnt been touched in 5 months
[11:51] <Riddell> prison? that's nothing new, plasma has always depended on it and it's never had a kf5 release.  it's a problem but not a new one
[11:52] <Riddell> he keeps saying it'll be part of frameworks release and it somehow not ending up there
[11:52] <yofel> *sigh*
[11:53] <Riddell> but yes prison now needs a new git snapshot
[11:56] <clivejo> !info prison-kf5
[11:57] <clivejo> libkf5prison-dev
[11:57] <clivejo> !info libkf5prison-dev
[11:58] <tsimonq2> Git revision? O_o
[11:58] <acheronuk> yep
[11:58] <clivejo> yes, thats why yofel isnt happy
[11:59] <tsimonq2> clivejo: wait, Riddell said it needs a new Git snapshot, doesn't yofel want a Git tag?
[12:00] <yofel> yes I would, but we're not getting that, so just use another snapshot
[12:01] <Riddell> here's one you could use http://archive.neon.kde.org/dev/unstable/pool/main/p/prison-kf5/
[12:12] <clivejo> yofel: when we get docs for KCI, can we put this gif on the "Fixing KCI bugs" section?  https://twitter.com/manisha72617183/status/745669337474703361
[12:13] <yofel> rofl
[12:13] <yofel> can do XD
[12:13] <clivejo> sums it up nicely :)
[12:15] <tsimonq2> yofel: I also linked this one earlier, I'm sure we can find a spot for it as well, right? XD https://twitter.com/manisha72617183/status/755110441471344644
[12:16] <tsimonq2> clivejo: so I'm having some problems getting it to build :/
[12:17] <tsimonq2> clivejo: I have an sbuild instance that I have the CI PPA enabled in, what other PPAs does it need?
[12:17] <clivejo> tsimonq2: getting what to build?
[12:17] <tsimonq2> clivejo: cantor
[12:17] <clivejo> its building on KCI
[12:17] <clivejo> just needs packaging fixed
[12:18] <tsimonq2> clivejo: I know, but how do I know if it's fixed if I can't build it?
[12:18] <tsimonq2> clivejo: does KCI have any more PPAs enabled besides itself, if that makes any sense?
[12:18] <clivejo> https://launchpadlibrarian.net/275131426/buildlog_ubuntu-yakkety-amd64.cantor_4%3A16.04.3+p16.10+git20160726.1144-0_BUILDING.txt.gz
[12:19] <yofel> and if we ever disagree: http://classicprogrammerpaintings.com/post/147044648074/gentle-technical-discussion-on-irc-channel
[12:19] <acheronuk> I just add KCI as a source for pbuilder, and off it goes
[12:19] <yofel> tsimonq2: it doesn't
[12:19] <clivejo> dh_install section
[12:20] <tsimonq2> yofel: I'll play with it, thanks
[12:20] <clivejo> you should have all the info you need on that buildlog
[12:20] <tsimonq2> clivejo: step 1 of fixing things: reproduce locally if you can
[12:20] <tsimonq2> :P
[12:21] <acheronuk> so pbuilder doesn't give you the same result?
[12:21] <tsimonq2> acheronuk: well it's a dep problem
[12:24] <tsimonq2> oh, so it turns out I can't add PPAs in a golden sbuild, I have to add the key manually and add to /etc/apt/sources.list
[12:24] <tsimonq2> works now
[12:24] <tsimonq2> acheronuk: s/pbuild/sbuild/
[12:24] <yofel> tsimonq2: you can skip the key if you write the source as "deb [trusted=yes] http..."
 :D
[12:25] <yofel> yes, that's a thing, don't use in production :P
[12:25] <tsimonq2> lol
[12:25] <acheronuk> :D
[12:32] <BluesKaj> Howdy folks
[12:32] <clivejo> hi BluesKaj
[12:33] <BluesKaj> hi clivejo
[12:35] <acheronuk> so is prison sorted?
[12:39] <clivejo> no
[12:39] <clivejo> are symbols case sensitive
[12:40] <clivejo> cause if they are this is a mess!
[12:41] <clivejo> _ZTSN6prison13Code39BarcodeE@Base changed to _ZTSN6Prison13Code39BarcodeE@Base
[12:42] <clivejo> p changed to P
[12:45] <yofel> AFAIK, c++ is pretty much completely case sensitive, so yeah, that's a new ABI
[12:49] <clivejo> libkf5prison1 -> libkf5prison1.2 or libkf5prison2?
[12:49] <clivejo> my head hurts and Im hungry
[12:49] <mamarley> You should take a break and eat some food then!
[12:49] <yofel> the bigger problem is that laurent doesn't seem to understand what an api break is
[12:50] <yofel> (well, sune broke it)
[12:50] <yofel> but laurent did https://quickgit.kde.org/?p=prison.git&a=commit&h=5a2c8b345e69ff65e961e25454c3536423b61500
[12:50] <yofel> but left the SOVERSION as-is :(
[12:51] <yofel> I'll ask him to fix that
[12:52] <clivejo> Ill go for lunch!
[12:59] <acheronuk> SOVERSION "${PRISON_VERSION_MAJOR}"?
[13:41] <clivejo> yofel: can you update prison to use LP - https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/prison
[13:49] <soee> Rrrrrr ..
[13:49] <acheronuk> RED?
[13:50] <soee> Red :D
[13:54] <tsimonq2> clivejo: so...it builds locally for some reason
[13:54] <tsimonq2> clivejo: trying again to confirm but still
[13:54] <tsimonq2> clivejo: (cantor)
[13:54] <tsimonq2> clivejo: and yeah, I'm on the kubuntu_unstable branch
[13:55] <clivejo> it builds but there are dh_install issues
[13:55] <tsimonq2> oh
[13:56] <tsimonq2> clivejo: no? it shouldn't build, doesn't build in Launchpad...
[13:56] <clivejo> it does build in KCI LP PPA
[13:57] <tsimonq2> https://launchpadlibrarian.net/275131426/buildlog_ubuntu-yakkety-amd64.cantor_4%3A16.04.3+p16.10+git20160726.1144-0_BUILDING.txt.gz ?
[13:58] <clivejo> yes
[13:58] <clivejo> http://paste.ubuntu.com/21005574/
[13:58] <clivejo> you know how to fix the app data
[13:58] <tsimonq2> clivejo: yeah it does show that, but it fails, not passes
[13:58] <tsimonq2> yeah that's obvious
[13:59] <clivejo> but I want you to fix the lib issue
[14:07] <soee> clivejo: are this problems with Plasma 5.7 that mamarley reported yesterday fixed maybe ?
[14:07] <soee> *when trying to install on Xenial
 soee no. Been working on yakkety
 Xenial needs rebuild of pyqt5
 I tried to back port version in yakkety but it needs sip
[14:10] <tsimonq2> yofel: why is there no icon? :P https://launchpad.net/~kubuntu-dev
 I meant to look into how Neon did it and got distracted
 Maybe you could look?
[14:11] <soee> clivejo: i do not now much about packaging etc. :)
[14:12] <acheronuk> neon is still 5.5.1 I think?
 On a neon install find the version number
[14:13] <soee> clivejo: pyqt5 ?
[14:13] <acheronuk> http://archive.neon.kde.org/dev/unstable/pool/main/p/pyqt5/
[14:13] <soee> there is not installed version just candidate: 5.5.1+dfsg-3+16.04+build2
[14:15] <acheronuk> Looks like they took the Xenial version, and made just this change? http://packaging.neon.kde.org/cgit/forks/pyqt5.git/commit/?id=2d0f444b2fa0cf31a2897dc3f16dd8f8fec21623
[14:17] <soee> acheronuk: can you trigger rebuild with this small change ?
[14:17] <soee> clivejo: ^
[14:19] <clivejo> probably dont need that
[14:19] <clivejo> just try a no chnage rebuild in staging-plasma
[14:20] <clivejo> acheronuk: do you want to do that?
[14:21] <acheronuk> xenial staging ppa?
[14:21] <clivejo> staging-plasma
[14:21] <acheronuk> what I meant
[14:21] <clivejo> it has Qt5.6.1
[14:22] <clivejo> oh it has the backported version in there
[14:22] <clivejo> thats FTBFS
[14:23] <acheronuk> if delete that and allow the ppa time to clear it, will be ok?
[14:23] <clivejo> actually its not in there
[14:23] <clivejo> must been the in apps PPA
[14:24] <clivejo> problem with these 3rd party packages I dunno where to put them!
[14:24] <soee> ;/
[14:25] <clivejo> !info xenial pyqt5-dev
[14:25] <clivejo> !info pyqt5-dev xenial
[14:25] <acheronuk> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma/+packages?field.name_filter=pyqt5&field.status_filter=published&field.series_filter=
[14:26]  * clivejo face palms
[14:26] <clivejo> I need a memory transplant
[14:26] <acheronuk> so they took that, patched, and give it a neon version and build no basically
[14:27] <soee> https://s-media-cache-ak0.pinimg.com/originals/cf/05/af/cf05af3f2188da8c80516a6456441040.gif
[14:27] <acheronuk> lol. I like that gif
[14:27] <clivejo> he dropped his fruit loops!
[14:28] <acheronuk> that's a metaphor all on it's own!
[14:29]  * soee reboots after installing kernel 4.7
[14:29] <clivejo> I remember that episode - https://en.wikipedia.org/wiki/Window_of_Opportunity_(Stargate_SG-1)
[14:30] <tsimonq2> Stargate? :O
[14:30] <ahoneybun> a show before your time tsimonq2 lol
[14:30] <acheronuk> Oh yes, I remember now :)
[14:31] <clivejo> yup!
[14:31] <clivejo> Director Peter DeLuise asked the prop department to glue the Froot Loops to O'Neill's breakfast spoon to have the same loops in the same spots in each take.
[14:32] <acheronuk> 5.5.1+dfsg-3ubuntu4 + what version?
[14:32] <tsimonq2> ahoneybun: my uncle has the set on DVD and we watch it in the camper in the nighttime
[14:33] <tsimonq2> (when we are camping)
[14:33] <clivejo> pyqt5 - 5.5.1+dfsg-1build1~ubuntu16.04~ppa1 I guess?
[14:34] <clivejo> however that one has ubuntu build
[14:34] <clivejo> grrr
[14:34] <clivejo> doing too many things at once
[14:35] <acheronuk> need to supersede that, I know
[14:35] <clivejo> so 5.5.1+dfsg-3ubuntu5~ubuntu16.04~ppa1
[14:36] <clivejo> wont be going into the archive, just backports
[14:36] <acheronuk> that implies a official ubuntu revision though?
[14:36] <acheronuk> ubuntu5
[14:37] <clivejo> yes
[14:37] <acheronuk> surely ubuntu4 + something
[14:38] <acheronuk> ohhh. maybe
[14:38] <clivejo> but I think you will have trouble uploading that
[14:38] <clivejo> yofel: help !!
[14:39] <acheronuk> I've done a lower version into a ppa before I think. Just need to leave time for LP to delete the sources and recognise it has?
[14:39] <tsimonq2> finally, it's done installing deps, I think it might work now!
[14:39] <clivejo> can two different versions of pyqt5 exist in the same PPA?
[14:40] <tsimonq2> clivejo: I doubt it
[14:41] <yofel> sorry, busy at work, later
[14:42] <tsimonq2> gosh darnit
[14:49]  * acheronuk feels lost without yofel's wise council
[14:50] <acheronuk> oops. that does a ping doesn't it. sorry
[14:51] <yofel> ^^
[14:53] <soee> https://67.media.tumblr.com/5e685fb8893deb145e8bd2b5d6aa09a8/tumblr_nhi4mrJl1Q1u1vo97o1_500.gif
[14:57] <acheronuk> ok. I'll leave that until a bit later then. may as well double check to get it right 1st time
 test
[15:26] <yofel> tsimonq2: you can't be more elite than a ninja, hence the additional logo from ~ubuntu-dev is enough :P
[15:27] <yofel> acheronuk, clivejo: uh so... what was the question?
[15:28] <tsimonq2> yofel: but why NO logo? :P
[15:28] <yofel> dunno, that predates my tiem
[15:28] <yofel> *time
 mm my network is not working right
 now it is
[15:31]  * yofel hands ahoneybun a sonic screwdriver
[15:32] <ahoneybun> of course
[15:34] <acheronuk> yofel: sorry about that...
[15:36] <acheronuk> basically Neon rebuilt xenial's pyqt5 5.5.1+dfsg-3ubuntu4 as 5.5.1+dfsg-3+16.04+build2
[15:37] <yofel> that sounds more like a rebuild of the debian version
[15:38] <ahoneybun> removing ubuntu from the packages
[15:38] <ahoneybun> mm
[15:38] <acheronuk> yofel: "import from ubuntu" http://packaging.neon.kde.org/cgit/forks/pyqt5.git/commit/?id=5c47d4d7815ef15a8ff26b76e1696c88aaa16ebb
[15:40] <yofel> hm, well, if they don't care about bugfixes that's ok I guess
[15:40] <soee> you want ninja logo ? :D
[15:40] <acheronuk> anyway, Q was how to version it if we can just do a rebuild?
[15:41] <yofel> I would go with ubuntu4+qt5.6 or ubuntu4.1~qt56 or something like that
[15:41] <yofel> soee: we have that, ~kubuntu-dev has none
[15:42] <acheronuk> the other Q was, the 5.6 version has been deleted from the ppa, so will it accept the upload of this older version 5.5.1?
[15:42] <yofel> it will once the janitor has actually deleted it
[15:42] <yofel> takes a couple hours
[15:43] <acheronuk> right. that is what I thought I had done a long while ago, or had read. I just began to doubt it...
[15:43] <acheronuk> great. thanks. :)
[15:48] <clivejo> sorry, was sortig out my new wheels
[15:48] <clivejo> I need 4 new ones!
 (Photo, 1280x697) https://irc-attachments.kde.org/ml0ffQ0l/file_295.jpg
[15:51] <clivejo> hi slhk
[15:51] <slhk> hi clivejo
[15:51] <clivejo> how are you?
[15:52] <slhk> fine thanks, and you?
[15:53] <clivejo> wet!
[15:54] <clivejo> just got soaked by the rain
[15:54] <clivejo> but at least I got one of the lawns mowed
[15:55] <slhk> I'm wet too, but more because of hot weather. but rain is coming soon
[15:56] <clivejo> did you ever get to look at that auth issue in Muon?
[15:57] <clivejo> when you edit the sources the window to prompt for password seems to get lost
[15:58] <yofel> hm, come to think of it, we could also just debianabimanager prison...
[15:59] <clivejo> speak English yofel :P
[15:59] <clivejo> we could do what to prison?
[16:00] <clivejo> well its built with those new symbols added
[16:00] <clivejo> but will probably break stuff upstream
[16:01] <clivejo> kdepimlibs and plasma-workspace
[16:02] <slhk> clivejo: uhm, it even runs the wrong command here, I didn't notice that before
[16:02] <yofel> yes, that's why we'll just bump the ABI ourselves!
[16:02] <clivejo> would you mind looking at it?
[16:02] <yofel> by adding a suffix!
[16:02] <clivejo> you'll have to explain/walk me through that!
[16:03] <clivejo> should we get Simon and Rik listening in too?
[16:04] <clivejo> and Marcin
[16:04] <clivejo> he needs to learn too!
[16:04]  * tsimonq2 double-takes
[16:05] <clivejo> apparently we are going to debianabimanager prison
[16:05] <tsimonq2> debianabimanager?
[16:05] <clivejo> sounds painful, but worth it
[16:05] <tsimonq2> WOAH! :O
[16:05] <tsimonq2> :P
[16:05] <tsimonq2> what's that?
[16:05] <tsimonq2> and what's the prison package?
[16:06] <clivejo> prison is a dev package for making bar codes me thinks
[16:06] <yofel> clivejo: see e.g. okteta bb2e434da410c4ce31ad13d97d3be23cf61bf53e, the patch, and X-Debian-ABI in the control file (except here, it would be 1, not 0)
[16:06] <yofel> even if we end up bumping the ABI upstream, it's good to know that we have this
[16:07] <acheronuk> going to what the what?!!
[16:07] <tsimonq2> acheronuk knows about prison
[16:07] <tsimonq2> right?
[16:07] <tsimonq2> acheronuk: kidding, talking about the package :P
[16:07] <acheronuk> ok, 'what' the prison then?
[16:08] <clivejo> you mean this commit - https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/okteta/commit/?h=kubuntu_yakkety_archive&id=bb2e434da410c4ce31ad13d97d3be23cf61bf53e
[16:08] <acheronuk> tsimonq2: I know you were
[16:08] <tsimonq2> ;)
[16:08] <yofel> clivejo: the tree at the state of that commit
[16:08] <tsimonq2> yofel: before or after the commit?
[16:08] <yofel> the old bzr history has better examples, let me check that
[16:10] <yofel> hm, no, that predates the repo split ^^
[16:11] <yofel> anyway, if you set X-Debian-ABI to 1, you will get a libPrison.so.1abi1, thus bumping the ABI without upstream changing everything
[16:11] <clivejo> and where is that set?
[16:11] <yofel> the control file, see okteta
[16:13] <clivejo> so the package name is libkf5prison1
[16:14] <clivejo> it will build libkf5prison1.so.1abi1?
[16:14] <yofel> will need a rename to libkf5prison1abi1 after that
[16:14] <yofel> libkf5prison.so.1abi1
[16:15] <yofel> just patch CMakeLists.txt, add the control entry, and see what happens
[16:17] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/okteta/tree/debian/patches/enable_debianabimanager.diff?h=kubuntu_yakkety_archive&id=bb2e434da410c4ce31ad13d97d3be23cf61bf53e
[16:17] <yofel> yes, just for prison
[16:17] <clivejo> is there an easy way to make a patch
[16:17] <yofel> quilt new <patchfilename>, quilt add CMakeLists.txt, edit CMakeLists.txt, quilt refresh
[16:18] <clivejo> but I still need the source
[16:19] <yofel> yes, just take the neon ci build
[16:19] <clivejo> I been working off the KCI
[16:19] <yofel> good enough if the tarball is current
[16:20] <clivejo> https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+files/prison-kf5_1.2.2+p16.10+git20160726.1358.orig.tar.xz
[16:24] <yofel> ack
[16:24] <yofel> just make it 1.2.2~git
[16:26] <tsimonq2> clivejo: when you are done, let me know, I'm stuck
[16:27] <clivejo> yofel: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/prison/commit/?id=c603520212a343f58815b7af8d6767c4ddee224a
[16:27] <clivejo> ?
[16:28] <yofel> clivejo: version wrong, and patch is missing DEP3 headers
[16:29] <clivejo> what should the version be
[16:29] <clivejo> its set at 1.2.2 in the CMake file :/
[16:30] <yofel> clivejo: what you had there previously was right
[16:30]  * clivejo kicks
[16:32] <clivejo> is there a tool will make the DEP3 headers for me
[16:33] <yofel> not that I know of
[16:33] <yofel> making the patch with dpkg-source --commit sets some of the headers, but I find it easier to just write them by hand
[16:39] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/prison/commit/?h=kubuntu_unstable&id=a467bf18fe8d85294a9c8cd45680f3884fdc73c0
[16:39] <yofel> ack
[16:40] <clivejo> any good?
[16:44] <clivejo> do the install or symbol files need renames?
[16:44] <yofel> yes
[16:44] <yofel> they always match the binary package name
[16:45] <clivejo> Ill wait until KCI builts it
[16:45] <clivejo> see what the new name is
[16:45] <clivejo> should have commited with NOCI
[16:59] <yofel> bbl
[17:25] <santa_> clivejo: you must rename libkf5prison1 as libkf5prison1abi1, this means at least changing the name in the control file, changing the name of the *.install fie and others files and creating a brand new symbols file
[17:39] <Mirv> FYI if you need any uploads to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-041/+packages you can ask a core dev or join #ubuntu-ci-eng and ask trainguards (highlight, ie "trainguards: could you upload blah to landing-041")
[17:39] <Mirv> although I'll be here again in <12h
[18:24] <tsimonq2> clivejo: ping
[18:56] <acheronuk> that pyqt5 for xenial helps as it should. not longer wants to remove software-properties-kde, driver manager and apturl-kde and the few other things it did.
 Sorry trying to get the kitten on a trailer
[19:07] <mamarley> Literally herding cats?
[19:09]  * genii twitches and goes to watch https://youtu.be/Pk7yqlTMvp8
[19:39] <clivejo> nooo
[19:39] <clivejo> a Robin Reliant "Kitten"
[19:43] <genii> Heh, had to go look it up. reminds me for some reason of a Lada
[19:44] <clivejo> genii: https://irc-attachments.kde.org/ml0ffQ0l/file_295.jpg
[19:44] <clivejo> gone to a new home!
[19:45] <genii> Looks like a lot of work
[19:47]  * clivejo nods
 test
[19:55] <tsimonq2> test 1 2
[19:55] <clivejo> test 1 2 3
[19:56] <clivejo> 1.. 2.. and a 1.. 2..
[19:56] <acheronuk> **** feeeeeeeeeeeeedback  ****
[19:56] <acheronuk> ouch
[19:56] <ahoneybun> now it works
[19:56] <clivejo> what works?
[19:57]  * clivejo wonders what Aaron is up too
[19:59]  * mamarley decreases the gain on acheronuk's mic.
[19:59] <mamarley> Oh wait, actually clivejo's mic.
[20:00] <yofel> ?!?
[20:02] <mamarley> ‽
[20:08] <clivejo> yofel: whats causing this error - https://launchpadlibrarian.net/275171699/buildlog_ubuntu-yakkety-amd64.prison-kf5_1.2.2+p16.10+git20160726.1638-0_BUILDING.txt.gz
[20:16] <ahoneybun> clivejo, snaps but my internet is crappy today
[20:19] <yofel> hm....
[20:19] <ahoneybun> what I'm not allowed to?
[20:19] <santa_> clivejo: I told you, you have to rename the package, that X-CMake-Targe a target which you usually don't need to set if you use the right name for the package
[20:19] <santa_> see the README.DebianABIManager from pkg-kde-tools
[20:20] <santa_> * X-CMake-Target
[20:25] <yofel> santa_: renaming the package didn't help me. but it seems like kf5prison != KF5Prison. latter seems to work as value of X-CMake-Target
[20:25] <yofel> clivejo: ^
[20:25] <yofel> maaaaybe a bug in the abi manager? or just some change in cmake?
[20:26] <santa_> yofel: then you have to add the field to the control file
[20:26] <yofel> right, but I remember that not being necessary in most cases. And this being *just* a case difference looks weird
[20:26] <yofel> but well, works
[20:31] <santa_> yofel: well, keep in mind that this invention comes from the very old kde 4 days when you used that. I was even working for debian. go figure. I think it's, after all, somewhat normal that the stuff can't guess the lib names today if the naming is different
[20:32] <yofel> hm, yeah, I know, which is why I'm wondering if something changed in cmake - or it's some incompatibility with ecm
[20:32] <yofel> there is one working way, so that's enough I guess
[20:33] <santa_> just the names in cmake
[20:33] <clivejo> I dont understand
[20:33] <clivejo> -- DebianABIManager: unable to find CMake target 'kf5prison' for package 'libkf5prison1'. Please set X-CMake-Target
[20:34] <santa_> if I'm not mistaken the thing needs to know the name of the library in the CMakesLists.txt, and that's done using the package name as input
[20:34] <clivejo> so in the patch?
[20:35] <yofel> no, X-CMake-Target is a control file field
[20:35] <yofel> put it next to X-Debian-ABI
[20:35] <clivejo> it it because the package name in control file is wrong?
[20:36] <yofel> no... I fixed that and it still didn't work. It for some reason can't read the target properly
[20:36] <yofel> so you have to set that by hand
[20:42] <clivejo> got an example use case?
[20:42] <yofel> what do you mean?
[20:42] <clivejo> are there arguement
[20:42] <clivejo> X-CMake-Target : 1
[20:43] <yofel> X-CMake-Target: KF5Prison
[20:43] <yofel> found using grep: lib/prison/CMakeLists.txt:install(TARGETS KF5Prison EXPORT KF5PrisonTargets ${KF5_INSTALL_TARGETS_DEFAULT_ARGS})
[20:58] <clivejo> so who all has tested Apps 16.04.3 on Yakkety?
[20:58] <clivejo> are there any outstanding issues?
[20:59] <clivejo> tsimonq2: did the holidays work once you installed that package?
[20:59] <tsimonq2> clivejo: yup
[21:00] <tsimonq2> clivejo: my fix worked! \o/
[21:00] <clivejo> do they show up in your calendar?
[21:05] <clivejo> Ive selected the file for Northern Ireland and nothing is showing
[21:07] <tsimonq2> clivejo: not in Plasma right now, and I'm in the middle of something
[21:08] <clivejo> ok
[21:19] <slhk> clivejo: about Muon and package sources, the only problem I found is that software-properties-kde isn't installed (libqapt should depend on it, somehow). Moreover, kdesu is not tra
[21:19] <jimarvan> :)
[21:19] <jimarvan> heeeeello
[21:19] <jimarvan> kdesu?
[21:19] <jimarvan> you mean kdesudo?
[21:20] <clivejo> why is there two separate auth methods
[21:20] <slhk> * kdesu dialog is not transient, which might cause the "lost window". But I cannot reproduce the problem.
[21:21] <clivejo> it seems to use one way to get access to do the package install and another way to open the software sources window
[21:21] <slhk> because software-properties-kde is run as a process, whereas other actions are done by the qapt worker over dbus
[21:22] <clivejo> ah
[21:22] <slhk> software sources is a different application, not a Muon window
[21:22] <clivejo> what happens if its not there?
[21:23] <clivejo> any way of detecting that and display a message to that effect
[21:23] <clivejo> maybe even get muon to install it :)
[21:23] <slhk> you still get the authentication dialog and then it silently fails (writes some message on stdout)
[21:23] <jimarvan> hmmmmmm
[21:24] <jimarvan> slhk: is that a muon fail?
[21:24] <jimarvan> to open software sources?
[21:24] <slhk> no, packaging fail :P
[21:24] <clivejo> the reports I had said they didnt even get the authentication dialog
[21:24] <jimarvan> ah ok :)
[21:24] <slhk> but Muon just assumes it is there :(
[21:25] <jimarvan> hmm
[21:25] <clivejo> what if we added depend on kdesu in the muon packaging?
[21:25] <slhk> clivejo: I still couldn't reproduce those bugs, there is also some timeout somewhere, I guess
[21:26] <clivejo> wish i could remember who had the problem
[21:26] <slhk> the call is done in libqapt, not muon
[21:27] <clivejo> so libqapt needs the depend
[21:27] <slhk> but maybe it makes sense to have muon depend on it, because e.g. plasma-discover doesn't need it
[21:27]  * clivejo wonders has that been moved to LP
[21:27] <slhk> and it need both kdesu and software-properties-kde
[21:28] <clivejo> slhk: what system do you use?
[21:28] <slhk> at present neon
[21:28] <clivejo> Im trying to package plasma 5.7.2
[21:28] <clivejo> on a test build of Qt5.6.1
[21:29] <clivejo> Im having issues with discover
[21:29] <clivejo> mainly packagekit
[21:29] <clivejo> happen to know anything about it?
[21:30] <jimarvan> clive
[21:30] <clivejo> Jim
[21:30] <jimarvan> have you considered removing it?
[21:30] <jimarvan> xD
[21:30] <jimarvan> I think noone likes discover tbh
[21:30] <clivejo> its KDE's baby
[21:30] <jimarvan> oh...
[21:30] <clivejo> they not like that!
[21:30] <jimarvan> Oh well
[21:31] <jimarvan> no no no if its KDE baby
[21:31] <jimarvan> then I will buy candy for it
[21:31] <jimarvan> I thought it was an ubuntu thing xD
[21:32] <slhk> clivejo: no, I'm learning and screaming because I never find doc
[21:34] <slhk> but I can look into it
[21:34] <yofel> jimarvan, clivejo: kdesudo was our own thing - and was never ported to qt5, so it recently
[21:34] <yofel> *died recently
[21:34] <clivejo> RIP kdesudo
[21:35] <yofel> hm, isn't is supposed to use pkexec for software-properties-kde?
[21:35] <clivejo> slhk: ^
[21:35] <yofel> *it
[21:35] <slhk> no idea, sure it would make sense
[21:36] <clivejo> is that something that could be supported?
[21:36] <slhk> I think it should be software-properties-kde doing the authentication in that case
[21:36] <acheronuk> clivejo: do you know why the packagekit depends were "tightened" here? https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/discover/commit/?h=kubuntu_yakkety_archive&id=b0853f807ee4d847d73014a143f0cb5075e1a14a
[21:39] <acheronuk> jimarvan: I usually boot discover off my machines if it manages to creep on.
[21:39] <acheronuk> are you going to make it to the dojo?
[21:39] <yofel> when's that again?
[21:40] <acheronuk> Thurs unless I'm mistaken?
[21:40] <yofel> k
[21:40] <slhk> otherwise the qapt daemon would have to open the window for source editor
[21:43] <clivejo> acheronuk: no sorry I dont
[21:43] <clivejo> yofel: could you add libqapt to KCI?
[21:44] <acheronuk> clivejo: fair enough. I sometimes look at these things and think "did you _really_ need to do that right then!"
[21:45] <clivejo> if you want to make sure it builds on the newest version then it makes sense
[21:46] <clivejo> !info packagekit
[21:46] <yofel>  adding
[21:47] <yofel> !info packagekit yakkety-proposed
[21:48] <yofel> whee
[21:49] <yofel> I'll look over it tomorrow
[21:51] <clivejo> I still think there something fishy with it
[21:51]  * clivejo glances a dirty look at prison
[21:51] <acheronuk> that's a bigger jump than I thought in version
[21:52] <yofel> because ubuntu always blocked something newer because they use that aptdaemon pk shim
[21:52] <clivejo> acheronuk: in prison or packagekit
[21:52] <acheronuk> packagekit
[21:52] <clivejo> thats in proposed
[21:53] <clivejo> could that be the "problem"
[21:53] <yofel> well, the ppa will pick it up, but you need proposed enabled on your system to actually install it
[21:54] <clivejo> plasma-discover it uninstallable currently on my YY system
[21:54] <clivejo> due to packagekit
[21:56] <acheronuk> it's got a dep of >= 1.0, and that is not installable. I would say so
[21:58] <yofel> the dep is still correct though if it's a requirement
[21:59] <acheronuk> yes, don't disagree with that
[22:06] <clivejo> wonder is this gimp issue due to QT5.6.1
[22:06] <acheronuk> Neon have packagkit 1.1 under their "forks" section
[22:07] <acheronuk> what package was that?
[22:39] <clivejo> !info libgrantlee5-dev
[22:41] <clivejo> and kpimtextedit needs 5.1
[22:41] <clivejo> who is Grant Lee
[22:41] <clivejo> and where do I find him
[22:42] <clivejo> wow, grantlee5 5.0.0 uploaded to Vivid in 2014
[22:43] <clivejo> LOL more krap
[22:43] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/krap/grantlee.git/
[22:44] <clivejo> at least Maxy is on the ball :)
[22:45] <clivejo> yofel: should that be moved to LP or can you mark it to be synced directly from Debian?
[22:47] <yofel> clivejo: debian has 0.4, so hardly. But it should eventually be latter
[22:47] <yofel> unless we need it updated
[22:53] <acheronuk> I think for kstars to build we might need libindi v1.2 from debian as well.
[22:54] <acheronuk> YY is 1.1, with no greater in proposed
[22:54] <yofel> that I agree with
[22:54] <clivejo> yofel: http://anonscm.debian.org/cgit/pkg-kde/krap/grantlee.git/log/
[22:55] <yofel> clivejo: when syncing, git is useless to me
[22:55] <acheronuk> ah. right. someone has looked at that already. good :)
[22:56] <yofel> now I wonder why doko messed with the indi symbols..
[22:56] <clivejo> I dont understand, dont move it to LP?
[22:57] <yofel> I don't see the point
[22:57] <yofel> do it when we actually need to touch it
[22:57] <yofel> and cannot sync from debian
[22:59] <acheronuk> ok. goodnight all
[22:59] <clivejo> nn acheronuk
[23:13] <yofel> acheronuk: libindi uploaded to yakkety
[23:13]  * yofel -> bed
[23:13] <yofel> nini
[23:19] <clivejo> can you upload grantlee5?
[23:19] <clivejo> https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+build/10523306
[23:20] <yofel> oh, 5.1, I totally read that as 0.5.1
[23:20] <yofel> uh... tomorrow
[23:20] <clivejo> Ive uploaded to KCI Unstable
[23:20] <yofel> and now really nini
[23:20] <clivejo> hopefully fix some of those failures
[23:21] <clivejo> night
[23:21] <clivejo> happy packaging dreams
[23:41] <valorie> wow, so fantastic to come back from entirely other work and see what you folks have accomplished!
[23:41] <valorie> amazing progress
[23:41] <clivejo> what did we accomplish?
[23:43] <valorie> getting closer to success on both backports and YY
[23:44] <valorie> also I'm encouraged that qtwebkit is at least being attempted so that we might be able to have PIM
[23:45] <valorie> also your kitten went to a new home
[23:45] <valorie> :-)
[23:45] <clivejo> yup
[23:45] <valorie> I on the other hand stacked wood and cleaned a trail
[23:45] <clivejo> she almost didnt
[23:45] <valorie> and then cleaned the cabin
[23:46] <valorie> again, all with good teamwork!
[23:46] <valorie> unfortunately our cell-booster doesn't boost very well
[23:47] <valorie> the signal is very low-quality
[23:47] <valorie> so I really wasn't online at all
[23:47] <clivejo> at least you have a signal!
[23:48] <valorie> sort of
[23:48] <valorie> sometimes
[23:48] <valorie> it took me an hour to send one text
[23:48] <clivejo> does it depend on the time of day?
[23:49] <valorie> and I never got an answer, so who knows if it got sent "really"
[23:49] <valorie> we're relying on one cell tower a few miles away
[23:49] <valorie> up at the ski area
[23:50] <clivejo> when I was on mobile internet, I pointed an antenna at the local cell.  But at peak times the cell tower powers up and down to cope with demand
[23:50] <valorie> the entire area except the ski area basically has zero service
[23:50] <clivejo> [23:50] <valorie> oh, sorry


[22:13] <mup> Issue operator#514 closed: Pebble.add_layer has a poor exception type <Created by jameinel> <Closed by benhoyt> <https://github.com/canonical/operator/issues/514>


[06:47] <xnixan> morning bassem Miriup :)
[06:52] <bassem> xnixan, morning
[10:23] <Toki> All right guys, sorry for the delay, but it's time to get to business. bassem, are you there?
[10:24] <Toki> Miriup, xnixan, are you going to attent tomorrow's meetup?
[10:29] <nlsthzn> Hi all
[10:31] <nlsthzn> Pls remember to have someone be seceratary on the next meeting and also to make a minutes and put it online...
[10:34] <Toki> nlsthzn: I wanted to discuss about right now, but no one's here...
[10:34] <nlsthzn> Toki: Mostly nothing happening in here... got off with a bang and then interest was lost...
[10:35] <Toki> nlsthzn: So what do you suggest we do tomorrow?
[10:36] <nlsthzn> Toki: I suggest nothing... I find it infuriating that the day before a meetup someone thinks about this, something that should already have been decided, documented and communicated to everyone properly... as a group/community we are failing at this :/
[10:39] <Toki> nlsthzn: Omar was too friggin' late to infrom us that he;s not gonna show up.
[10:44] <nlsthzn> Toki: Which is an issue... if the loco is dependant on one person then it is doomed to failure
[10:45] <Toki> nlsthzn: Well, we did accept him as an organizer of the meetups, in that case, he was also responsible for informing us of any unforeseen changes.
[10:46] <Toki> Whatever, we should take this oppurtunity to organize this by ourselves, I want go ahead and do so and wanted to opinions as well.
[10:46] <Toki> *wanted to hear other's opinions
[10:47] <Toki> Will wait till mid-afternoon then make changes by myself
[10:48] <nlsthzn> Well, maybe you should use the mailing list then and get many opinions... and I didn't accept anybody as anything... what exactly are the responsibilities of the organizer... and why if nothing about the meetup was communicated two weeks ago wasn't it queeried?
[10:48] <nlsthzn> I think there are some big issues that need to get clarified just to get the basic things working it seems...
[10:53] <bassem> nlsthzn, Toki , hi
[10:54] <nlsthzn> bassem: Hey
[10:56] <Toki> bassem: Hey!
[10:57] <Toki> bassem: Can you make the reservation pleasE?
[10:57] <bassem> Toki, I don't have the contact!
[10:57] <bassem> Toki, and, do we need reservation?
[10:57] <Toki> Hmm, wasn't it in the email? Let me reread it...
[10:58] <Toki> bassem: Oh, Omar instructed to call 181 to get the number...
[11:01] <bassem> Toki, http://www.yellowpages.ae/profile/ODg4MDA1ODI2/More-Cafe.html
[11:02] <Toki> bassem: So please go ahead...? :)
[11:02] <Toki> Okay. the next thing is what the meetup is going to be actually about.
[11:03] <nlsthzn> If I see how much effort the ubuntu-za guys are having to put in for re-certification to be an official Loco I have to say we have a big challenge ahead of ourselves if we are still booking venues for the only meeting their is a day before the meeting is supposed to be occuring
[11:03] <bassem> nlsthzn, so what to do in that case ?
[11:03] <Toki> I for one would report the progress and the block I faced with NI Model School (I've been introduced to the place by Joseph and went there for nearly everday for a couple of weeks).
[11:04] <nlsthzn> bassem: in which case would that be?
[11:04] <bassem> nlsthzn, which you mentioned !
[11:04] <nlsthzn> bassem: I mentioned much.. please be specific
[11:05] <bassem> nlsthzn, booking venue !
[11:05] <nlsthzn> Do you think it is a good idea to book a venue the day before the event?
[11:06] <nlsthzn> bassem: ^
[11:06] <bassem> nlsthzn, no, it's not good at all! but what to do now? cancel the meeting ?!!
[11:07] <Toki> bassem: No. there already RSVPs, and it's toomorrow. It's not something big that we have to prepare stuff for the meeting.
[11:08] <nlsthzn> bassem: I didn't say that... I also didn't say that a venue shouldn't be booked for tomorrow... just that I don't think that it is good that this is the way things are being done
[11:08] <Toki> nlsthzn: Don't worry too much - we're still learning. Omar has left without wartning, we can take this situation and let others me responsible as well
[11:08] <bassem> Toki, I know that!!!
[11:08] <nlsthzn> Toki: Feels to me that some of what I am saying/feeling/metioning now occured previously as well... maybe not exactly but similar
[11:08] <bassem> nlsthzn, for me I don't like to dicuss what happened and why! I more like to discuss what is the next step!
[11:09] <nlsthzn> bassem: sure, let us keep doing what we did, and keep getting what we got
[11:09] <Toki> Yes, so meeetup topics please!
[11:09] <nlsthzn> bassem: if your next steps are about doing it better (or right for a change) then sure
[11:10] <bassem> Toki, can you prepare a mini agenda about thing that we can dicuss tomorrow!
[11:10] <Toki> bassem: For that I want suggestions.
[11:10] <bassem> Toki, 1- how to prepare a monthly meeting!
[11:11] <bassem> 2- what to do if the orginizer disapear 1 day before the meeting
[11:11] <Toki> bassem: Book it and all those who RSVP will appear. XD
[11:11] <Toki> bassem: Okay, I understand you don't like what just happned, but what about the next steps you were talking about?
[11:14] <Toki> BRB.
[11:15] <bassem> Toki, done
[11:15] <Toki> Back.
[11:15] <Toki> bassem: Booking?
[11:16] <bassem> Toki, yes, tomorrow 7pm more cafe festival city, the big table :-)
[11:17] <Toki> bassem: Yippe? :P
[11:17] <Toki> Anyway, back to meetup topic.
[11:18] <bassem> Toki, they mentioned that we have to order at least one order per person
[11:19] <Toki> bassem: Wha~t? Not all of us ordered in the previous meetings, so what's the deal now?
[11:21] <bassem> Toki, I don't know, I told her that, but she said that she heard that notification from her boss
[11:22] <Toki> bassem: So what will happen if we didn't order?  If need be we can change the meetup venue next time.
[11:22] <bassem> Toki, no, but next time they might refuse to host us!
[11:22] <bassem> xnixan,
[11:23] <bassem> xnixan,
[11:23] <bassem> xnixan,
[11:23] <bassem> can you come tomorrow
[11:23] <Toki> bassem: That's what, we can change  the venue if they make a big deal of it.
[11:23] <bassem> Toki, maybe we can move to xnixan place
[11:23] <xnixan> bassem, ISA i will
[11:24] <Toki> Where was that place again?
[11:24] <bassem> xnixan, don't forget! tomorrow 7pm at more cafe festival city
[11:24] <xnixan> bassem, sure!
[11:24] <bassem> Toki, Al Ahli driving school
[11:25] <bassem> xnixan, Omar talked to you to discuss it ?
[11:25] <xnixan> bassem, nop
[11:25] <Toki> bassem: The area.
[11:25] <bassem> xnixan, np, tomorrow we can discuss it
[11:25] <bassem> Toki, I don't know!
[11:25] <bassem> Toki, ask xnixan
[11:25] <Toki> xnixan: What area is it in?
[11:26] <xnixan> Toki, 1m
[11:26] <Toki> ?
[11:26] <Toki> Oh.
[11:27] <bassem> Toki, how to replay Omar's message, so all ppl in the thread will know about the reservation!!!
[11:27] <Toki> bassem: Just send it to the mailing list. Or post a thread with the option of notifying all members ticked.
[11:28] <bassem> Toki, let us finish the points of meeting and then will send the mail!
[11:29] <Toki> No just for announcing that the meetup isn't cancelled just because Omar's absent.
[11:29] <Toki> Add more details will be update later at the end.
[11:29] <Toki> Besides, I already got one point to discuss - regular meetup venue/
[11:32]  * nlsthzn thinks that maybe you should also discuss minutes, and finilizing agenda etc. at a set date before the menu... suggestion may be at least a week... but it is just a thought as he can never be at the meetings anyhow
[11:32] <nlsthzn> *set date before the meeting
[11:32] <xnixan> Toki, check this 25.120085, 55.226377 @ google maps
[11:33] <Toki> xnixan: Will do.
[11:33] <Toki> nlsthzn: Yes, we depended on Omar too much.
[11:34] <nlsthzn> Toki: Like we said about all the other things, IRC, web site etc... redundency is needed... and sound best practices
[11:36] <nlsthzn> Also... Please note that I may be far, and a bit out of the loop... if something needs doing and I don't know I can't try and help...
[11:37] <Toki> nlsthzn: Don't worry, I can force something upon you if need be. :P
[11:37] <nlsthzn> Toki: :) ... it would be a bit better if all that is needed to be done was communicated clearly to the group so the ones with the means and the time could make sure it happens... :p
[11:38] <Toki> Something we need to discuss as well -- deciding on things, and then having someone follow it up.
[11:39] <Toki> Just saying I can do it is not gonna cut it, we need to do it properly (says my perfectionist side).
[11:41] <Toki> xnixan, bassem, given my lack of experience in roads (I don't drive and mostly use public transport), I can comment on the issue of location convenience.
[11:41] <nlsthzn> Toki: I was having a thought the other day too... we should really do some sort of follow up on the installfest... look into the feasibility of getting feedback on some of the students that was assisted... maybe make a flyer for them with all the new contact info we got (which we didnt' have back then)... make them know we are still there to assist and care
[11:41] <Toki> If you know the are well, please discuss it at the next meetup.
[11:41] <bassem> Toki, wait
[11:41] <Toki> nlsthzn: That's fine and all, but I for one don't have the contact of the IEEE guys of the uni so that we can discuss a follow-up.
[11:42] <Toki> Now, if you'll excuse me, I would like to answer to my stomach.
[11:48] <nlsthzn> Toki: Was thinking the meetup could discuss it and then contact the IEEE guys with suggestions... but no matter... was just a thought :)
[11:49] <nlsthzn> bassem: Mail received on venue
[11:49] <bassem> Toki, the place is very good for public transportation, there's bus 12 and F25
[11:50] <bassem> nlsthzn, I've sent that :-)
[11:50] <nlsthzn> bassem: I was just letting you know I got it (and thus that everyone got it) ;)
[11:52] <Miriup> Toki: thanks for the meetup reminder. :)
[11:53] <bassem> Miriup, are you coming tomorrow?
[11:54]  * Miriup is opening the meetup site.
[11:58]  * Miriup thinks the Meetup site is not Konqueror friendly and tries the next browser. ;)
[11:58] <Toki> Miriup: Don't thank me just yet - that was just an automated reminder.
[11:59] <Toki> All right fellows, the points I;ve gathered to discuss so far are.
[11:59] <Miriup> Toki: I meant the one at (13:08:43)  here.
[11:59] <Toki> Meeteup venue.
[11:59] <Toki> Miriup: That was the autmoated one (there are two one a week ahead, the other is a day before).
[12:00] <Toki> Next is Meetup minutes.
[12:00] <Toki> Then follow-up for AUS installgest.
[12:00] <Toki> And last is my report  on NI Model School.
[12:01] <Toki> bassem, nlsthzn, xnixan, Miriup, is there anything you guys would like to add?
[12:03] <nlsthzn> Toki: IRC meeting... next date, purpose etc?
[12:03] <bassem> Toki, how to prepare for a meetup, and what to do in critical situations
[12:03] <Toki> bassem, nlsthzn, xnixan, Miriup, who do you think should take the position that Omar left (i.e. meeting chair equivalent in IRC).
[12:04] <Toki> Okay, will add those two as well, nlsthzn, bassem.
[12:05] <nlsthzn> Toki: discuss that also tomorrow
[12:05] <Toki> nlsthzn: We need to decide one for now.
[12:05] <bassem> Toki, we can discuss that there! don't forget Haden, Josef and Silviu
[12:05] <Toki> Joseph is travelling abroad as well.
[12:05] <nlsthzn> Toki: oh for the meetup tomorrow...
[12:06] <Miriup> bassem: Back to your question, I think I have decide in the last moment tomorrow. But when I'm free, I'll be there.
[12:06] <bassem> Miriup, it's OK to come anytime! usualy we stay till 9:00pm
[12:07] <Toki> Speaking of Silviu and Haden, why aren't the here? I was expecting them to be online as usual.
[12:07] <Toki> *aren't they
[12:09] <Toki> BTW, Miriup, I don't think we discussed if we met in any of the Meetups - what name do you go by on Meetup?
[12:11] <Toki> nlsthzn, bassem, xnixan, Miriup, I still think we should decide who's going to take the lead tomorrow (actually, I just want to remove Omar as the host and replace it with whoever is going to lead us :P)
[12:12] <Miriup> Dirk. I don't think we've met. I've been recently only once to a LUG/meetup and that was when Imtiaz was still running his group.
[12:12] <bassem> Toki, tomorrow we will decide!!
[12:12] <nlsthzn> :) so the sheep need a shepard... I am in no place to say anything as I have never attended (and won't be starting tomorrow)
[12:12] <Toki> bassem: I want to remove his name NOW!. ;)
[12:13] <Miriup> I'm unreliable, I can'
[12:13] <Toki> nlsthzn: Won't be?
[12:13] <Miriup> I can't be it either. ;)
[12:13] <bassem> Toki, tomorrow
[12:13] <nlsthzn> Toki: not tomorrow, no...
[12:13] <Toki> bassem: You're quite stubborn. :|
[12:14] <Toki> nlsthzn: SYou said starting tomorrow. :)
[12:14] <nlsthzn> Toki: read carefully what I wrote
[12:15] <Toki> (and won't be [attending] starting tomorrow)
[12:15] <bassem> nlsthzn, Toki , anything else to be disccued tomorrow?
[12:15] <Toki> Well, I've decided on just the points you guys added to my list for now.
[12:15] <nlsthzn> bassem: not from my side... sounds like enough
[12:18]  * Miriup noticed he never joined the group. lol
[12:23] <nlsthzn> Miriup: lol
[12:24] <bassem> Toki, offical LoCo?!!
[12:25] <Toki> bassem: Let's get us in order first (we nearly cancelled our meetup just because of one person).
[12:25] <Toki> *get ourselves
[12:25] <nlsthzn> well, any good meeting should have the oppertunity to have new topics added on the day
[12:31] <Toki> nlsthzn: Indeed, there's nothing restricting us into adding more topics while we are it.
[12:41] <Toki> nlsthzn:, bassem, a trivial question, but title do I give to this meetyp?
[12:41] <Toki> *meetup
[12:42] <bassem> Toki, just reply to my email!
[12:42] <Toki> bassem: Ah, didn't check my inbox yet.
[12:42] <nlsthzn> bassem: you do seem to enjoy the shift+1 key :p
[12:43] <Toki> bassem: That's fine but I can send an email from the meetup itself, and I'm asking about the title of meetup.
[12:43] <bassem> nlsthzn, yes!!!
[12:43] <nlsthzn> :)
[12:44] <bassem> nlsthzn, can you help Toki with that!
[12:44] <Toki> nlsthzn: If you will. :)
[12:45] <nlsthzn> Toki: I am not sure I understand the problem... what where previous meetings called
[12:45] <Toki> The last one was 11.04 review, nlsthzn.
[12:46] <Toki> nlsthzn: Omar Absent Monthly Gathering? :(
[12:47] <Toki> Oh forget it, nlsthzn, bassem, I'll just name it plain Monthly Gathering.
[12:47] <nlsthzn> Toki: that was just about what I was going to suggest
[12:48] <Toki> nlsthzn: Great minds think alike? :P
[12:48] <bassem> Toki, it's Monthly Gathering, no need for other names..
[12:48] <nlsthzn> Fools never differ
[12:48] <Toki> nlsthzn: Ah, that's much better. :D
[12:49] <nlsthzn> :)
[12:50] <Toki> Okay, everyone has been emailed on Meetup detail change.
[12:52] <Toki> Shoot any issues with the minor details guys.
[13:00] <Toki> I was unavailable since my last message. If there's anything you want changed on the meetup, drop me an email or comment on it/
[13:00] <Toki> Gotta go for now.
[13:00] <Toki> Bye.
[18:12] <Toki> So hey guys, did you prepare your bag packs for tomorrow's outing?
[18:12] <Toki> Don't forget to bring plenty of rations.


[00:25] <Wild_Man> h
[00:26] <Wild_Man> Hello krytarik, I just checked to see if the issue is on the wiki since I have not seen it on the forum so I thought I would help publish but does not look like it is ready
[00:27] <guiverc> Wild_Man, i haven't touched (had ability/time) since saturday; all but 3 summaries were done (but no read thru)
[00:29] <krytarik> How much is it anyway?  I mean for a good two weeks now, there hasn't been happening all that much to begin with, no?  Then we could just skip this week and bundle it with next week's issue.
[00:29] <Wild_Man> I can help publish to the forum and social media if it is ready, but I have only done the wiki once and I do not have the time to try that tonight
[00:30] <Wild_Man> Does not look like that much
[01:58] -SwissBot:#ubuntu-news- ::Planet:: Colin Watson: DeployingÂ Swift @ https://www.chiark.greenend.org.uk/~cjwatson/blog/deploying-swift.html