[Cin] LV2_blacklist.txt & Debian packaging improvements contributions
phylsmith2017 at gmail.com
Fri May 24 18:27:03 CEST 2019
Olivier, it is going to take me some time to absorb all of this and have GG
answer the Developer questions. Meanwhile, I will look at the parts that I
can like the blacklist that I can do. I think the Mailing List is best for
this kind of communication rather than MantisBT.
BTW, yesterday we downloaded the "testing" version of Debian 10 and will
try to do a build for that at the end of the month, due to a request in the
comment on April News on the website. This is not what we would normally
do but if someone takes the time to write about it, we should at least look
at it. More later, Phyllis/GG
On Fri, May 24, 2019 at 9:52 AM Olivier Humbert <trebmuh at tuxfamily.org>
> Hi GG, Phylis, Sam and all
> Now that things as settled around, and now that I'm good with the
> website French translation, I'm taking back the packaging of Cin-GG for
> my audio-linux debian-based distribution (and maybe later, a potential
> inclusion into Debian mainstream, but... one step after another).
> I've been doing a build with the last cin_5.1.20190430 and it seems to
> be successful so far.
> Doing that, I found a bunch of LV2 plugins which are avoided Cin to be
> launched and then, which needs to be added to the LV2_blacklist.txt file
> (after I did that locally, Cin is launching fine). Those following lines
> are the culprits:
> Also, please, find attached an improved version for the
> ./blds/debian/control file which contains those improvements/changes:
> - I added a bit of description (then it looks better with the packages
> - I improved the Maintainer field (changed the name from "mailing list"
> to "Cinelerra-GG devs")
> - I moved the Standard-version and the Homepage fields downer (standard
> good practice for Debian packaging)
> - Build-depends :
> -- 1 item per line (standard good practice for Debian packaging even if
> it doesn't change anything computer-side, it is easier to human-read)
> -- alphabetically ordered (standard good practice for Debian packaging
> too, easier for human-reading)
> -- removing of duplicates : libxft-dev, libxinerama-dev, and libxv-dev
> -- adding libusb-1.0-0-dev (the compilation failed here without it)
> I've got a few questions about the debian/control file which I'd like to
> have your dev's point of view here (I left those as-is for now waiting
> for your answers in case I'm missing something):
> - Build-depends field:
> -- why is inkscape needed for building ? It sounds like a mistake at a
> first glance.
> -- why is e2fsprogs needed ? For information, it contains those binaries
> : https://packages.debian.org/stretch-backports/amd64/e2fsprogs/filelist
> -- same for linux-firmware, why is that needed for building ? It doesn't
> even look to be in the Debian repository anymore
> - The "Standards-Version" number is currently defined to "5.1.20190430".
> It is not supposed to be the program version number (which is defined in
> the debian/changelog file), but a number matching a Debian standard. If
> you're OK with that, I would set it up to 3.9.8 which is the standard
> for Debian Stretch (current stable - Debian 9) and which will work as
> well for the next stable (Buster - Debian 10).
> I hope that helps.
> Thanks for your continuous work on cin-gg !
> PS: last but not least, I've send it to the mailing list as I did a few
> months ago back in the cin-cv times, but feel free to let me know if you
> would better like me to use the Mantis bug-tracker or any other way to
> contribute. I'm planning to send you other improvements/contributions on
> a next step.
> Site web : https://librazik.tuxfamily.org/
> Donation : https://liberapay.com/LibraZiK/
> Diaspora :
> Mastodon : https://mastodon.xyz/@LibraZiK--
> Cin mailing list
> Cin at lists.cinelerra-gg.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cin