[00:06] <tsimonq2> agaida: I don't touch Lubuntu code, talk to Julien about that :P :)
[08:05] <agaida> tsimonq2: a) it isn't funny b) you guy captured the false not finished packaging - so it's your problem. c) Please be so kind and in case of LXQt never ever get packages from d/experimental
[08:05] <agaida> tsimonq2: and you should really fix it before the new LXQt release hit sid - without changes many (in other words - all) LXQt Packages will cause problems
[08:08] <agaida> tsimonq2: and thank you for you clarification - i'm not here to do your work, this is your project, so the ball is in your field.
[17:57] <tsimonq2> agaida: yes I said that intending to be joking a little bit, sorry
[17:57] <tsimonq2> agaida: so liblxqt needs to be fixed before the new LXQt release lands? what about it is broken?
[17:58] <tsimonq2> agaida: I'll be happy to make sure that if I don't fix it myself, it goes to the right person
=== pavlushka_ is now known as pavlushka
[17:58] <tsimonq2> agaida: and what do you mean by "b) you guy captured the false not finished packaging - so it's your problem." ?
[18:26] <agaida> fixing is easy - get the current debian sources - you guys was a little bit to fast, after long discussions we integrated a virtual abi in the symbols file. Doing so make us independent from upstream if abi-bumps are needed - we use a new virtual abi instead of renaming the package
[18:27] <agaida> without this mechanism the new release would be installed and break existing packages without warning
[18:28] <agaida> mostly segfaults as usual - if you remember the xenial packages right from the start
[18:31] <agaida> tsimonq2: there are reasons putting packages into experimental - a) not production ready, b) pre-releases, really experimental stuff c) preparing releases, if uploading directly to sid would create a lot of havoc - and the packages that will be uploaded to experimental right now are c)
[18:31] <agaida> they will create a lot of fallout, if uploaded to sid
[18:32] <tsimonq2> agaida: so what you are saying is that the liblxqt package just needs to be updated to the current version?
[18:32] <tsimonq2> I see
[18:32] <agaida> use meld or bcompare to compare the debian dirs
[18:32] <tsimonq2> alright
[18:33] <agaida> i'm sure you will find the differences
[18:33] <agaida> :)
[18:33] <agaida> it's a little bit tricky - but cool. And it works reliable
[18:34] <agaida> thats why we discussed this strategy so long
[18:34] <tsimonq2> agaida: so which packages am I comparing? from GitHub and Yakkety? could you be a little bit more specific at what I'm supposed to compare the Yakkety package to?
[18:35] <agaida> you can apt source liblxqt0/yak and apt source liblxqt0/sid
[18:35] <tsimonq2> agaida: oh so from sid, okay
[18:36] <agaida> it make no difference if sid or testing
[18:36] <agaida> i would clone the whole thing from git
[18:36] <tsimonq2> agaida: GitHub or Debian's Git system?
[18:36] <agaida> debian
[18:37] <tsimonq2> alright
[18:37] <agaida> they should™ be the same - but debian is official
[18:37] <agaida> i only mirror the debian stuff to github in case that one will send us a pull request
[18:41] <tsimonq2> agaida: so I should make them the same? what am I fixing here?
[18:41] <agaida> erm - i think i should have a quick look at the current packaging - but basicly: yes
[18:42] <tsimonq2> agaida: alright I'll play with it
[20:16] <redwolf> o/
[21:54] <redwolf> o.o
[22:03] <tsimonq2> o/ redwolf
[22:09] <redwolf> ø