[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#791215: netcdf: library transition may be needed when GCC 5 is the default



user release.debian.org@packages.debian.org
usertag 791215 + transition
block 791215 by 790756
reassign 791215 release.debian.org
block 791215 by 793823 793877 793885 793920 793976 794010
block 791215 by 794027 794040 793891 793902 793882
thanks

On 25-07-15 13:10, Sebastiaan Couwenberg wrote:
> On 03-07-15 15:13, Matthias Klose wrote:
>>  [..] 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
>>    control@bugs.debian.org:
>>    
>>      user release.debian.org@packages.debian.org
>>      usertag <this issue> + transition
>>      block <this issue> by 790756
>>      reassign <this issue> release.debian.org
> 
> We'll need a transition for netcdf, but I don't want to transition to v5
> libraries for netcdf (1:4.1.3-7.2). I strongly prefer to transition to
> the new netcdf packages we have in experimental for some time now.
> 
> The biggest change in those packages is the split into language specific
> packages instead of bundling them all in the netcdf package.
> 
> There are two new NetCDF C++ packages: netcdf-cxx & netcdf-cxx-legacy.
> 
> The netcdf-cxx package provides libnetcdf-c++4-1 (libnetcdf_c++4.so.1)
> which has a new API.
> 
> The netcdf-cxx-legacy package provides libnetcdf-c++4
> (libnetcdf_c++.so.4) which has the old API compatible with the netcdf
> 4.1.3 packages in Debian.
> 
> Since all the new netcdf packages change the library package name, we
> won't need to append v5. Because of the new -dev package for the
> language specific packages, most reverse dependencies will need to
> change their build dependencies and a source upload, binNMUs won't do
> most most or even all of the reverse dependencies.
> 
> We're not quite ready for the netcdf transition yet, we still need to
> complete a round of rebuild of all reverse dependencies, and file bugs
> with patches for the changes required for the new netcdf packages. I'll
> usertag those bugs with netcdf-split-c-f-cxx for easy reference.
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=netcdf-split-c-f-cxx;users=debian-gis@lists.debian.org

We're still not quite ready for the netcdf transition, but I'd like to
formally request the transition already anyway.

The automatically created auto-netcdf tracker is not sufficient to track
the new C++ & Fortran packages. I've attached the ben configuration I
used for my pkg-grass-transitions tracker in the preparation of this
transition.

For the libstdc++ transition we still need to update the symbols files
for the new netcdf packages in experimental. And there are couple of
reverse dependencies that FTBFS with the netcdf from experimental.

Please see the recent message on the debian-gis lists for more
information on the outstanding issues for the netcdf transition [1][2][3].

The biggest change in the netcdf transition is the split into language
specific packages that follow the upstream split into separate projects. [4]

┌─────────────────────┬───────────────────┬──────────────────┐
│ NetCDF project      │ Source package    │ Library package  │
├─────────────────────┼───────────────────┼──────────────────┤
│ NetCDF-C            │ netcdf            │ libnetcdf7       │
│ NetCDF C++ (cxx4)   │ netcdf-cxx        │ libnetcdf-c++4-1 │
│ NetCDF C++ (legacy) │ netcdf-cxx-legacy │ libnetcdf-c++4   │
│ NetCDF-Fortran      │ netcdf-fortran    │ libnetcdff6      │
└─────────────────────┴───────────────────┴──────────────────┘

netcdf-cxx provides the new NetCDF-4 C++ API in libnetcdf_c++4.so.1,
netcdf-cxx-legacy the legacy NetCDF-3 C++ API in libnetcdf_c++.so.4.

The netcdf-cxx-legacy package is provided for backward compatibility,
the 4.2 release includes no changes since the 4.1.3 release we're
transitioning away from.

All netcdf reverse depndencies that rely on the C++ API build
successfully after libnetcdf-cxx-legacy-dev is added to their build
dependencies.

Please refer to the transition summary below for the status of the most
recent rebuilds of the netcdf reverse dependencies.


[1] https://lists.debian.org/debian-gis/2015/07/msg00096.html
[2] https://lists.debian.org/debian-gis/2015/07/msg00116.html
[3] https://lists.debian.org/debian-gis/2015/07/msg00117.html
[4] http://www.unidata.ucar.edu/downloads/netcdf/index.jsp


Transition: netcdf

 libnetcdfc7   (1:4.1.3-7.2) -> libnetcdf7       (1:4.4.0~rc2-1~exp3)
 libnetcdfc++4 (1:4.1.3-7.2) -> libnetcdf-c++4-1 (4.2.1-1~exp3) [cxx4]
 libnetcdfc++4 (1:4.1.3-7.2) -> libnetcdf-c++4   (4.2-1~exp3)   [legacy]
 libnetcdff5   (1:4.1.3-7.2) -> libnetcdff6      (4.4.2-1~exp4)

The status of the most recent rebuilds is as follows. Entries tagged
with [+] build successfully after applying the patch from the bugreport.

 adios              (1.8.0-2 / 1.8.0-3)                  OK / OK
 cdftools           (3.0-1 / 3.0-2~exp1)                 FTBFS / OK
 cmor               (2.9.1-5 / 2.9.1-6)                  OK / OK
 dx                 (1:4.4.4-7)                          OK
 etsf-io            (1.0.3-4 / 1.0.4-1~exp1)             OK / OK [+]
 exodusii           (6.02.dfsg.1-5 / 6.02.dfsg.1-6)      OK / OK
 ferret-vis         (6.9.3-1 / 6.9.3-2~exp1)             FTBFS / OK
 gdal               (1.10.1+dfsg-9 / 1.11.2+dfsg-1~exp4) OK / OK
 gnudatalanguage    (0.9.5-2)                            FTBFS
 grace              (1:5.1.25-1)                         OK
 grads              (2:2.0.2-5 / 2:2.0.2-6)              OK / OK
 gri                (2.12.23-8)                          FTBFS
 kst                (2.0.3-4)                            OK
 libpdl-netcdf-perl (4.20-1)                             OK [+]
 magics++           (2.24.7-3)                           OK [+]
 minc               (2.2.00-6)                           OK [+]
 nco                (4.5.1-1)                            FTBFS
 ncview             (2.1.5+ds1-1)                        FTBFS
 netcdf4-python     (1.1.8-2 / 1.1.8-3~exp2)             FTBFS / OK
 oasis3      (3.mct+dfsg.121022-3 / 3.mct+dfsg.121022-4) OK / OK [+]
 octave-octcdf      (1.1.8-1)                            FTBFS
 ovito              (2.3.3+dfsg1-1)                      OK
 python-scientific  (2.9.4-3)                            OK
 r-cran-ncdf4       (1.13-1)                             FTBFS
 r-cran-rnetcdf     (1.6.3-1-1)                          OK
 ruby-netcdf        (0.7.1.1-1)                          FTBFS
 v-sim              (3.7.2-1)                            OK
 vtk                (5.8.0-17.5 / 5.10.1+dfsg-1)         OK / OK [+]

 cdo                (1.6.6+dfsg.1-3 / 1.6.6+dfsg.1-4)    OK / OK
 gmt                (5.1.2+dfsg1-1 / 5.1.2+dfsg1-2~exp1) FTBFS / OK
 metview            (4.5.6-3 / 4.5.6-4exp1)              OK / OK [+]
 ncl                (6.3.0-3~exp1 / 6.3.0-3)             OK / OK
 vtk6               (6.2.0+dfsg1-1)                      OK [+]


Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
title = "netcdf";
is_affected = .depends ~ /libnetcdfc7|libnetcdf7|libnetcdfc\+\+4|libnetcdf\-c\+\+4|libnetcdf\-c\+\+4\-1|libnetcdff5|libnetcdff6|libcf0/;
is_good = .depends ~ /libnetcdf7|libnetcdf\-c\+\+4|libnetcdf\-c\+\+4\-1|libnetcdff6/;
is_bad = .depends ~ /libnetcdfc7|libnetcdfc\+\+4|libnetcdff5|libcf0/;
notes = "NetCDF upstream has split into language specific packages: C (netcdf), C++ (netcdf-cxx), C++ legacy (netcdf-cxx-legacy), Fortan (netcdf-fortan)";

Reply to: