Hi! Of course, you can! I'm very glad to work with you in this package.
We have a repository with the debianization of the package, using git-buildpackage thanks to Cleto Martin. This repository is hosted in Bitbucket, so if you have an account there, we can grant you the write permissions. Currently, the 0.7.0 version was imported in the upstream branch and some minor changes were made to the debianization to this version, but it is not ready yet. I will talk with Cleto to see how can we handle to have, using gbp, two separate development branches to package the 0.8.0 version that you have previously worked on. Best regards El 28/01/15 a las 11:49, Peter Spiess-Knafl escribió: > Hi! > > Can I offer co-maintainership? I already put a some work in packaging > (not yet released 0.8) and made some improvements. > > E.g. switched the buildsystem to cmake, instead of scons, added debug > packages, split out the docs from the -dev into a -docs package. > > Adapted alle copyright / control infos to the current upstream version. > > So I think there is a lot I can contribute. > > About the ABI breaks: It breaks all rdepends, isn't that a problem? This > would also change the packagename to libjsoncpp1 instead of libjsoncpp0. > Which means that all rdepends have to change their dependencies? > > Greetings > Peter > > On 01/28/2015 09:25 AM, José Luis Segura Lucas wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all! >> >> I'm very sorry. My e-mail filters made a mess and I was losing all this >> e-mails. I realize of them thanks to Peter's e-mail, so a lot of thanks >> to you! >> >> I was not aware about the newer upstream version. I will work this week >> on the package to keep it updated, so I hope to have the newer version >> packaged during this week. >> >> Thanks for your messages and sorry again. I will configure better my >> e-mail filters from now. >> >> On 28/01/15 09:15, Martin Quinson wrote: >>> ABI breakage is not a problem. Upstream should simply bump the so name >>> of the library, and you're set. If upstream does not do so, you can do >>> it yourself (but it would be better to do it for all distros and OSes). >>> >>> It's even a good news to have an active upstream that cleans up >>> his/her house and push the software forward. At least your packaging >>> efforts are worth it. >>> >>> Don't worry. >>> Mt >>> >>> On Wed, Jan 28, 2015 at 02:10:32AM +0000, Peter Spiess-Knafl wrote: >>>> I am currently in discussion with the upstream author:
signature.asc
Description: OpenPGP digital signature
