Hash: SHA256

On 03/08/2015 22:51, Sebastiaan Couwenberg wrote:
> On 03-07-15 15:12, Matthias Klose wrote:
>>  - If a library transition is needed, please prepare for the change.
>>    Rename the library package, append "v5" to the name of the package
>>    (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
>>    have a soversion bump and you upload this version instead of the
>>    renamed package.  Prepare a patch and attach it to this issue (mark
>>    this issue with patch), so that it is possible to NMU such a
>>    package. We'll probably have more than hundred transitions
>>    triggered. Then reassign the issue to release.debian.org and
>>    properly tag it as a transition issue, by sending an email to
>>    cont...@bugs.debian.org:
>>      user release.debian....@packages.debian.org
>>      usertag <this issue> + transition
>>      block <this issue> by 790756
>>      reassign <this issue> release.debian.org
> To be on the safe side we should assume a transition is required.
> Unfortunately libterralib is not very actively maintained, so I had a
> look into this issue as part of team maintenance.
> The previous Uploaders are included in the CC for their view on the
> license issues that were uncovered in the process.
> I started on the package by creating a git repository and importing all
> previous releases because the Subversion repository on Alioth is very
> outdated:
> http://anonscm.debian.org/cgit/pkg-grass/libterralib.git
> I've updated the package for the move to Git, and renamed the library
> package to include the SOVERSION for which a bug was outstanding
> (#701143). This is helpfull to avoid appending v5 to the package name,
> this SONAME fix suffices.
> While updating the copyright file using copyright-format 1.0, I noticed
> some non-free issues that will need repacking of the orig.tar.gz at least:
>  * src/DSDK/*
>  * src/terralib/drivers/Oracle/*
> We'll need to resolve these license issues for the GCC 5 related upload
> to not be rejected from the NEW queue.
> I'm having a hard time figuring out how the orig tarball was created, it
> looks like the build/ directory is from the upstream v-4-0-0 SVN tag
> because the v-4-3-0 tag only includes the cmake subdirectory. The src/
> and examples/ directories seem from different tags too.
Yes, this came from a tag as upstream seem to have dropped issuing new
> The Debian package build uses the build/qt4/ build system, so using only
> the current upstream tag is not going to work. A get-orig-source target
> to create the tarball would have been nice.
Will investigate.
> It seems that the SOVERSION in the package name was not the only change
> that got lost along the way, the changelog for libterralib (3.3.1-2)
> includes:
>   * Remove unused and copyright-troublesome Oracle, DSDK , MySQL,
>     PostgreSQL sources.
> It looks like everything under src/ except src/terralib/ can be dropped
> from the upstream tarball which would get rid of the non-free DSDK, but
> the problematic drivers under src/terralib/drivers/ need to removed too.
> The build system will need to be patched for that some more.
> @Alastair, as the most active uploader of libterralib and its reverse
> dependencies, how do you want to deal with these license issues and the
> GCC 5 transition?
Ok, will do. I'm using libterralib in the metview package.
> Kind Regards,
> Bas


- -- 
Alastair McKinstry, <alast...@sceal.ie>, <mckins...@debian.org>,
Software is like Poetry - most of it shouldn't have been written.
Version: GnuPG v2


Pkg-grass-devel mailing list

Reply via email to