Bug#866601: RFS: segyio/1.2.0-1 [ITP: #864710]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "segyio" * Package name: segyio Version : 1.2.0-1 Upstream Author : Jørgen Kvalsvik et al * URL : https://github.com/statoil/segyio * License : LGPL-3+ Section : libs It builds those binary packages: libsegyio1 - SEG-Y read/write library for seismic processing libsegyio-dbg - debugging files for segyio libsegyio-dev - development libraries and headers for segyio python-segyio - SEG-Y read/write library for seismic processing (python2 bindings) python3-segyio - SEG-Y read/write library for seismic processing (python3 bindings) segyio-bin - Simple SEG-Y shell utilities To access further information about this package, please visit the following URL: https://mentors.debian.net/package/segyio Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/segyio/segyio_1.2.0-1.dsc I am the upstream maintainer for this package. I've made some slight modifications to the source package that aren't yet reflected upstream, so fetching the latest tag will reduce in a small difference. The goal is that the tagged releases should build unmodified for Debian. Regards, Jørgen Kvalsvik
Bug#866601: RFS: segyio/1.2.0-1 [ITP: #864710]
> Why is the lib installed by code in debian/rules? The upstream build
> system should do that and it seems it does that, at least partially.
I'm afraid I don't understand what this means, can you point me to an example?
From: Andrey Rahmatullin <w...@debian.org>
Sent: Tuesday, July 25, 2017 5:28:34 PM
To: Jørgen Kvalsvik; 866...@bugs.debian.org
Subject: Re: Bug#866601: RFS: segyio/1.2.0-1 [ITP: #864710]
Control: tags -1 + moreinfo
Control: retitle -1 RFS: segyio/1.2.0-1 [ITP]
Please don't build the Python 2 module, see
https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html
Please switch to the debhelper compat level 10.
${shlibs:Depends} for -dev packages does nothing and there is a warning
about that in the build log.
Why is the lib installed by code in debian/rules? The upstream build
system should do that and it seems it does that, at least partially.
segyio-cath doesn't have a manpage (and lintian tells that).
Consider adding the symbols file for the library.
--
WBR, wRAR
---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorized use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you
Bug#866601: RFS: segyio/1.2.0-1 [ITP: #864710]
The .so and .a are installed by make install, but I'm manually invoking dh_install to bind it to a particular package (after tip from another debian maintainer), in order to not need a .install-file. Is this wrong? From: Andrey Rahmatullin <w...@debian.org> Sent: Tuesday, August 8, 2017 8:53:38 PM To: Jørgen Kvalsvik Cc: 866...@bugs.debian.org Subject: Re: Bug#866601: RFS: segyio/1.2.0-1 [ITP: #864710] On Tue, Aug 08, 2017 at 08:38:13AM +, Jørgen Kvalsvik wrote: > > Why is the lib installed by code in debian/rules? The upstream build > > system should do that and it seems it does that, at least partially. > > I'm afraid I don't understand what this means, can you point me to an example? Example of what? I mean the debian/rules lines which copy .so.* and .a and make the .so link. Usually this is done by make install. -- WBR, wRAR --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorized use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you
