[02:18] <tsimonq2> handsome_feng: Hi there!
[02:18]  * tsimonq2 sponsors some stuff for Ubuntu Kylin
[02:20] <handsome_feng> tsimonq2: hi
[02:21] <tsimonq2> handsome_feng: While I have you here, I just wanted to make sure you saw https://lists.ubuntu.com/archives/ubuntu-release/2018-April/004387.html :)
[02:24] <handsome_feng> tsimonq2: Yes, I saw it, and I agree with your idea, you can add ubuntukylin to the list of 'Xubuntu, Ubuntu MATE, Kubuntu, and Ubuntu Budgie'
[02:24] <tsimonq2> handsome_feng: Please respond (preferably signed with your GPG key) that you agree. :)
[02:24] <dodobrain> hi all, can someone tell me how libavl is being packaged? https://launchpad.net/ubuntu/+source/libavl  says "GNU libavl is a library in ...."
[02:25] <dodobrain> that is NOT the GNU libavl that is being packaged
[02:25] <tsimonq2> dodobrain: looking
[02:25] <dodobrain> i think the upstream debian package is also wrong
[02:25] <handsome_feng> tsimonq2: sure, I will
[02:25] <dodobrain> this is GNU libavl here: http://adtinfo.org/
[02:26] <tsimonq2> dodobrain: I see "AVL tree manipulation library"
[02:26] <tsimonq2> I see "GNU" nowhere.
[02:27] <tsimonq2> handsome_feng: Awesome. :)
[02:27] <dodobrain> tsimonq2, so you dont see "GNU libavl" on this page? https://launchpad.net/ubuntu/+source/libavl  i can post a screenshot if it helps
[02:28] <tsimonq2> dodobrain: Throw me a screenshot and I can throw you one too. ;)
[02:28] <tsimonq2> handsome_feng: So this isn't a showstopper, but it's something that would be nice to look into for ukui-panel.
[02:28] <tsimonq2> I: libukui-panel-applet-4-1: no-symbols-control-file usr/lib/x86_64-linux-gnu/libukui-panel-applet-4.so.1.0.1
[02:28] <tsimonq2> Also:
[02:28] <tsimonq2> P: ukui-panel source: debian-watch-does-not-check-gpg-signature
[02:28] <tsimonq2> That last one can be solved by signing your upstream tarball.
[02:29] <tsimonq2> Otherwise, looks good, so sponsoring.
[02:29] <dodobrain> tsimonq2, im sure you will send me a screenshot too, im just saying that on the launchpad page it says GNU libavl and this is *not* the GNU libavl
[02:29] <handsome_feng> tsimonq2: OK, I will fix it in next version
[02:29] <tsimonq2> dodobrain: And I'm telling you I see "GNU" nowhere. ;)
[02:30] <tsimonq2> Ohhhhhhhhhhhhhh.
[02:30] <tsimonq2> I get what you're going at now.
[02:30] <tsimonq2> So, that has nothing to do with the package itself.
[02:31] <tsimonq2> dodobrain: In any case, I don't see how that's a problem. ;)
[02:31] <tsimonq2> handsome_feng: Excellent!
[02:32] <dodobrain> you dont see the problem? it is because the GNU libavl api is completely different from this thing that is being packaged
[02:32] <dodobrain> tsimonq2, https://i.imgur.com/lOCL9k1.png
[02:33] <dodobrain> i tried the debian channel, but it seems very quiet with almost no chatter
[02:33] <tsimonq2> Clicked a button.
[02:33] <tsimonq2> Fixed?
[02:34] <dodobrain> tsimonq2, also, that http://changelogs.ubuntu.com/changelogs/pool/universe/liba/libavl/libavl_0.3.5-4/copyright says:  downloaded from http://www.fruit.eu.org/avl/
[02:34] <dodobrain> that server itself does not exist anymore
[02:34] <tsimonq2> dodobrain: Report that one to Debian.
[02:35] <Unit193> You asked the Debian support channel, that focuses on Debian stable.  Likely not quite the right place.
[02:35] <tsimonq2> Oh.
[02:35] <dodobrain> Unit193, yes i wasnt sure. i did ask in the main channel if this is the right spot
[02:36] <dodobrain> i know about ubuntu-motu, hence why i didnt ask in #ubuntu first :)
[02:36] <tsimonq2> dodobrain: #ubuntu-devel is more frequented.
[02:37] <dodobrain> sure, but in the long past i've found motu to be more packaging specific
[02:37] <dodobrain> maybe that has changed
[02:37] <tsimonq2> It has, I think.
[02:37] <tsimonq2> handsome_feng: One more thing, Debian Policy 4.1.4 has been released. Please update your packages whenever convenient. :)
[02:38] <handsome_feng> tsimonq2: I will, Thanks!
[02:38] <dodobrain> tsimonq2, so what do i do now? you did something and now the launchpad page asks me to select the properupstream and the libavl linked there is the correct gnu libavl
[02:38] <dodobrain> do i need to do something now?
[02:39] <tsimonq2> dodobrain: It should be fine now.
[02:39] <tsimonq2> handsome_feng: OK :)
[02:48] <dodobrain> tsimonq2, when you say 'it should be fine now' do you mean the real gnu libavl will get packaged by ubuntu?
[02:48] <tsimonq2> dodobrain: Yes.
[02:48] <dodobrain> goodness, thank you very much
[02:51] <dodobrain> i imagine there will not be corrected libavl package in backports
[02:51] <dodobrain> given that someone might have depended on it in their own development
[02:52] <dodobrain> or actually, im not sure how to check, but can you verify if any other ubuntu package depends on libavl1 or libavl-dev ?
[02:53] <Unit193> 'fair' seems to.
[02:54] <Unit193> Though in fairness, it doesn't seem to actually use it. :>
[02:56] <Unit193> (Looking at the wrong package, it links against it and configure bails without: https://sources.debian.org/src/fair/0.5.3-2/configure.ac/#L18)
[03:25] <tsimonq2> handsome_feng: Thanks for the email. :)
[03:27] <handsome_feng> tsimonq2: Not at all :)
[04:13] <tsimonq2> handsome_feng: This as well:
[04:13] <tsimonq2> I: libukwm-1-0: no-symbols-control-file usr/lib/x86_64-linux-gnu/libukwm-1.so.0.0.0
[04:13] <tsimonq2> You also might want to look into fixing hardening-no-bindnow in all of your packages.
[04:29] <handsome_feng> tsimonq2:  Ok, I will fix all these in next version, thanks for uploading them! :)
[04:30] <tsimonq2> handsome_feng: No problem. :)
[08:46] <kkremitzki> The FreeCAD project, which I work with, has finally released version 0.17 after being in feature freeze since January--is there any hope still for it to make it into 18.04?
[09:17] <ogra_> kkremitzki, there is a snap package of 0.17 (see "snap info freecad") perhaps that should be updated instead (contact the publisher shown in the snap info output)
[09:20] <kkremitzki> ogra_: That user is on hiatus and I've had a hard time getting ahold of him, if it's at all possible I'd like to try to make it available in the repositories as well. I've been working on packaging from the Debian end of things so I'd feel more comfortable taking care of it that way
[09:22] <ogra_> kkremitzki, sure, not opposing a deb but with the deb you are pretty much stuck on a version (or have to use a complex process to get it updated) ... the snap runs independently from the underlying OS version from 14.04 to 18.04 and can be updated whenever needed
[09:25] <rbasak> kkremitzki: to answer your question, upding the deb repository is possible. Assuming it's only bugfixes, it needs someone to contribute the change and an uploader to review it in time. If it contains feature changes, it needs consideration and approval by the release team in time as well.
[09:27] <kkremitzki> I'm interested in making it available via snap as well, but from patrolling our help forum I know a lot of people default to installing with apt and having the package trailing a version often results in unnecessary frustration from users. It does contain feature changes, over 6000 commits' worth (woohoo!)
[09:29] <rbasak> 3000 commits of feature changes since 0.16.6712+dfsg1-1ubuntu2? It seems unlikely that will be permitted to land in Bionic then.
[09:29] <kkremitzki> Well, I wouldn't say 1 commit = 1 feature, but there are a lot of new features
[09:29] <kkremitzki> It was a little over 2 years of development
[09:33] <kkremitzki> We also have a daily build PPA which has quite a bit of use so those changes haven't been getting worked on without testing
[09:36] <rbasak> You'll need to explain that to the release team.
[09:36] <rbasak> But in any case, you need someone to prepare the updated packaging.
[09:37] <rbasak> If you aren't likely to get that in time, there's no point taking it further.
[09:37] <kkremitzki> I can do that
[09:37] <rbasak> See https://wiki.ubuntu.com/FeatureFreeze and https://wiki.ubuntu.com/FreezeExceptionProcess
[09:37] <kkremitzki> How would I submit it?
[09:38] <rbasak> Once you have approval, https://wiki.ubuntu.com/SponsorshipProcess
[09:38] <rbasak> I warn you though: sponsors tend to be quite busy at this time of an LTS cycle.
[09:38] <rbasak> You're already very late, so you may struggle to find the required review time from a sponsor.
[09:39] <kkremitzki> Indeed, I'm sure it's especially tight with meltdown/spectre having eaten into other work
[09:40] <kkremitzki> I think it's worth a shot though, so thank you for the guidance