Re: [pyepr] 01/02: Restore -dbg packages

2017-08-15 Thread Antonio Valentino 
Hi Sebastiaan,

Il 15/08/2017 21:23, Sebastiaan Couwenberg ha scritto:
> On 08/15/2017 09:13 PM, Antonio Valentino wrote:
>>> Why are the -dbg packages included in the Build-Depends?
>>>
>>> Which part of the build process requires debug symbols?
>>
>> Re-enabled packages python-epr-dbg and python3-epr-dbg need to be built
>> with the -dbg version of the interpreter.
>> See also discussion [1] and the RC bug #872239 [2].
>>
>> [1] 
>> http://lists.alioth.debian.org/pipermail/debian-science-maintainers/2017-August/052374.html
>> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872239
> 
> These discussions only elaborate why the -dbg packages are preferred
> over automatic -dbgsym packages.
> 
> They don't provide a justification for the need to build a package with
> -dbg packages installed.

If I'm not wrong, the -dbg version of the interpreter is binary
incompatible with the standard one.
For this reason the -dbg version of each extension have to be built
against the corresponding -dbg version of the interpreter.

> The debug packages are mostly for users to install when they need
> troubleshoot an issue with gdb.
> 
> Kind Regards,
> 
> Bas
> 


-- 
Antonio Valentino

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Re: [pyepr] 01/02: Restore -dbg packages

2017-08-15 Thread Sebastiaan Couwenberg 
On 08/15/2017 09:13 PM, Antonio Valentino wrote:
>> Why are the -dbg packages included in the Build-Depends?
>>
>> Which part of the build process requires debug symbols?
> 
> Re-enabled packages python-epr-dbg and python3-epr-dbg need to be built
> with the -dbg version of the interpreter.
> See also discussion [1] and the RC bug #872239 [2].
> 
> [1] 
> http://lists.alioth.debian.org/pipermail/debian-science-maintainers/2017-August/052374.html
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872239

These discussions only elaborate why the -dbg packages are preferred
over automatic -dbgsym packages.

They don't provide a justification for the need to build a package with
-dbg packages installed.

The debug packages are mostly for users to install when they need
troubleshoot an issue with gdb.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Re: [pyepr] 01/02: Restore -dbg packages

2017-08-15 Thread Antonio Valentino 
Hi Sebastiaan,

Il 15/08/2017 18:57, Sebastiaan Couwenberg ha scritto:
> On 08/15/2017 06:49 PM, Antonio Valentino wrote:
>> --- a/debian/control
>> +++ b/debian/control
>> @@ -6,11 +6,17 @@ Priority: optional
>>  Build-Depends: debhelper (>= 9),
>> dh-python,
>> python-all-dev,
>> +   python-all-dbg,
>> python3-all-dev,
>> +   python3-all-dbg,
>> cython,
>> +   cython-dbg,
>> cython3,
>> +   cython3-dbg,
>> python-numpy,
>> +   python-numpy-dbg,
>> python3-numpy,
>> +   python3-numpy-dbg,
>> libepr-api-dev,
>> python-sphinx,
>> texlive-latex-extra,
> 
> Why are the -dbg packages included in the Build-Depends?
> 
> Which part of the build process requires debug symbols?

Re-enabled packages python-epr-dbg and python3-epr-dbg need to be built
with the -dbg version of the interpreter.
See also discussion [1] and the RC bug #872239 [2].


[1]
http://lists.alioth.debian.org/pipermail/debian-science-maintainers/2017-August/052374.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872239

-- 
Antonio Valentino

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Re: [pyepr] 01/02: Restore -dbg packages

2017-08-15 Thread Sebastiaan Couwenberg 
On 08/15/2017 06:49 PM, Antonio Valentino wrote:
> --- a/debian/control
> +++ b/debian/control
> @@ -6,11 +6,17 @@ Priority: optional
>  Build-Depends: debhelper (>= 9),
> dh-python,
> python-all-dev,
> +   python-all-dbg,
> python3-all-dev,
> +   python3-all-dbg,
> cython,
> +   cython-dbg,
> cython3,
> +   cython3-dbg,
> python-numpy,
> +   python-numpy-dbg,
> python3-numpy,
> +   python3-numpy-dbg,
> libepr-api-dev,
> python-sphinx,
> texlive-latex-extra,

Why are the -dbg packages included in the Build-Depends?

Which part of the build process requires debug symbols?

Kind regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

[pyepr] 01/02: Restore -dbg packages

2017-08-15 Thread Antonio Valentino 
This is an automated email from the git hooks/post-receive script.

a_valentino-guest pushed a commit to branch master
in repository pyepr.

commit 8d3d1495c4cf3c6b883f7175e05234945d1715b4
Author: Antonio Valentino 
Date:   Tue Aug 15 16:23:35 2017 +

Restore -dbg packages
---
 debian/changelog |  6 ++
 debian/control   | 52 ++--
 debian/rules |  7 ++-
 3 files changed, 62 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 18e79a3..13cb87c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pyepr (0.9.3-3) UNRELEASED; urgency=medium
+
+  * Restore -dbg packages
+
+ -- Antonio Valentino   Tue, 15 Aug 2017 
18:22:49 +0200
+
 pyepr (0.9.3-2) unstable; urgency=medium
 
   [ Bas Couwenberg ]
diff --git a/debian/control b/debian/control
index 2cbc3fd..dcfe8ab 100644
--- a/debian/control
+++ b/debian/control
@@ -6,11 +6,17 @@ Priority: optional
 Build-Depends: debhelper (>= 9),
dh-python,
python-all-dev,
+   python-all-dbg,
python3-all-dev,
+   python3-all-dbg,
cython,
+   cython-dbg,
cython3,
+   cython3-dbg,
python-numpy,
+   python-numpy-dbg,
python3-numpy,
+   python3-numpy-dbg,
libepr-api-dev,
python-sphinx,
texlive-latex-extra,
@@ -25,7 +31,6 @@ X-Python3-Version: >= 3.2
 
 Package: python-epr
 Architecture: any
-Multi-Arch: same
 Depends: ${misc:Depends},
  ${python:Depends},
  ${shlibs:Depends},
@@ -44,9 +49,30 @@ Description: Python ENVISAT Product Reader API (Python 2)
  .
  This is the Python 2 version of the package.
 
+Package: python-epr-dbg
+Section: debug
+Priority: extra
+Architecture: any
+Depends: ${misc:Depends},
+ ${python:Depends},
+ ${shlibs:Depends},
+ python-epr (= ${binary:Version})
+Recommends: python-numpy-dbg
+Description: Python ENVISAT Product Reader API (debug extension for Python 2)
+ PyEPR provides Python bindings for the ENVISAT Product Reader C API
+ (EPR API) for reading satellite data from ENVISAT ESA (European Space
+ Agency) mission.
+ .
+ PyEPR, as well as the EPR API for C, supports ENVISAT MERIS, AATSR
+ Level 1B and Level 2 and also ASAR data products. It provides access
+ to the data either on a geophysical (decoded, ready-to-use pixel
+ samples) or on a raw data layer. The raw data access makes it possible
+ to read any data field contained in a product file.
+ .
+ This package contains the extension built for the Python 2 debug interpreter.
+
 Package: python3-epr
 Architecture: any
-Multi-Arch: same
 Depends: ${misc:Depends},
  ${python3:Depends},
  ${shlibs:Depends},
@@ -65,6 +91,28 @@ Description: Python ENVISAT Product Reader API (Python 3)
  .
  This package contains pyepr for Python 3.
 
+Package: python3-epr-dbg
+Section: debug
+Priority: extra
+Architecture: any
+Depends: ${misc:Depends},
+ ${python3:Depends},
+ ${shlibs:Depends},
+ python3-epr (= ${binary:Version})
+Recommends: python-numpy-dbg
+Description: Python ENVISAT Product Reader API (debug extension for Python 3)
+ PyEPR provides Python bindings for the ENVISAT Product Reader C API
+ (EPR API) for reading satellite data from ENVISAT ESA (European Space
+ Agency) mission.
+ .
+ PyEPR, as well as the EPR API for C, supports ENVISAT MERIS, AATSR
+ Level 1B and Level 2 and also ASAR data products. It provides access
+ to the data either on a geophysical (decoded, ready-to-use pixel
+ samples) or on a raw data layer. The raw data access makes it possible
+ to read any data field contained in a product file.
+ .
+ This package contains the extension built for the Python 3 debug interpreter.
+
 Package: python-epr-doc
 Architecture: all
 Section: doc
diff --git a/debian/rules b/debian/rules
index 39252e6..6d2b8f9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -55,6 +55,11 @@ override_dh_auto_test:
 #endif
 
 
+override_dh_strip:
+   dh_strip -ppython-epr  --dbg-package=python-epr-dbg
+   dh_strip -ppython3-epr --dbg-package=python3-epr-dbg
+
+
 override_dh_installchangelogs:
dh_installchangelogs -k doc/NEWS.txt
 
@@ -79,5 +84,5 @@ endif
 
 
 .PHONY: override_dh_gencontrol override_dh_auto_clean override_dh_auto_test \
-override_dh_installchangelogs override_dh_compress \
+override_dh_strip override_dh_installchangelogs override_dh_compress \
 dh_sphinxdoc override_dh_installdocs

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-grass/pyepr.git

___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel