Hi Mark, the Debian Med team has packaged your NCL library for the Debian distribution. We received a bug report that there is a naming conflict with
http://www.ncl.ucar.edu/ My suggestion to solve this conflict would be to rename libncl to libnexus. In my opinion it would make sense to rename it in general since it is a more speaking name than ncl. What do you think? Kind regards and thanks for providing this code as free software Andreas. On Sun, Feb 07, 2016 at 09:17:17AM +0100, Ralf Treinen wrote: > > > This is a serious bug as it makes installation fail, and violates > sections 7.6.1 and 10.1 of the policy. An optimal solution would > consist in only one of the packages installing that file, and renaming > or removing the file in the other package. Depending on the > circumstances you might also consider Replace relations or file > diversions. If the conflicting situation cannot be resolved then, as a > last resort, the two packages have to declare a mutual > Conflict. Please take into account that Replaces, Conflicts and > diversions should only be used when packages provide different > implementations for the same functionality. > > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > /usr/lib/x86_64-linux-gnu/libncl.a > > This bug has been filed against both packages. If you, the maintainers of > the two packages in question, have agreed on which of the packages will > resolve the problem please reassign the bug to that package. You may then > also register in the BTS that the other package is affected by the bug. > > -Ralf. > > PS: for more information about the detection of file overwrite errors > of this kind see http://qa.debian.org/dose/file-overwrites.html. > > _______________________________________________ > Debian-med-packaging mailing list > debian-med-packag...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging > -- http://fam-tille.de