Bug#868827: closing 868827
close 868827 thanks Closing this one, duplicated with #868544.
Re: How to make a shared lib recognized by debhelpers?
Gert Wollnywrites: > Am Montag, den 17.07.2017, 21:20 +0200 schrieb Ole Streicher: > >> How can I do a proper handling of the library here? I guess (I am not >> an octave expert, however), that the name of the library shall not be >> changed. > One way to make dh_strip recognize files that are not in the typical > name pattern is to make it executable. Thanks for the hint. What I do now (in d/rules) is basically: override_dh_auto_install: dh_auto_install chmod ugo+x debian/tmp/usr/lib/*/octave/site/oct/api-*/*/plplot_octave.oct override_dh_shlibdeps: dh_shlibdeps chmod ugo-x debian/octave-plplot/usr/lib/*/octave/site/oct/api-*/*/plplot_octave.oct This seems to work well. A debug package is created as well. Best regards Ole
Bug#868768: RFS: iperf3/3.2-1
control: owner -1 ! control: tags -1 moreinfo Please: Copyright (c) 2009-2017 Dave Gamble and cJSON contributors Copyright (c) 2000 Markus Friedl. All rights reserved. Copyright (c) 2005,2006 Damien Miller. All rights reserved. Copyright: 1991-2016, The Regents of the University of California (year) nice to have: compat level 10 (drop autoreconf from rules and control files) did the ABI change? I don't think, but please double check G.
Bug#868254: marked as done (RFS: btrfs-progs/4.9.1-1~bpo9+1 [I intend to keep the bpo up-to-date])
Your message dated Tue, 18 Jul 2017 18:28:51 + (UTC) with message-id <1065380707.4396963.1500402531...@mail.yahoo.com> and subject line Re: Bug#868254: RFS: btrfs-progs/4.9.1-1~bpo9+1 [I intend to keep the bpo up-to-date] has caused the Debian Bug report #868254, regarding RFS: btrfs-progs/4.9.1-1~bpo9+1 [I intend to keep the bpo up-to-date] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 868254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my no-change bpo of "btrfs-progs". * Package name: btrfs-progs Version : 4.9.1-1~bpo9+1 Section : admin It builds these binary packages: btrfs-progs - Checksumming Copy on Write Filesystem utilities btrfs-progs-dbg - Checksumming Copy on Write Filesystem utilities (debug) btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) (udeb) btrfs-tools - transitional dummy package btrfs-tools-dbg - transitional dummy package To access further information about this package, please visit the following URL: https://mentors.debian.net/package/btrfs-progs Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.9.1-1~bpo9+1.dsc Alternatively, one can use the stretch-backports branch of my git repo: git clone -b stretch-backports --single-branch g...@github.com:sten0/btrfs-progs.git Changes since the last upload: btrfs-progs (4.9.1-1~bpo9+1) stretch-backports; urgency=medium * Rebuild for stretch-backports. (Closes: #864508) -- Nicholas D SteevesThu, 13 Jul 2017 15:28:09 -0400 btrfs-progs (4.9.1-1) unstable; urgency=medium Thank you, Nicholas --- End Message --- --- Begin Message --- hello >I am looking for a sponsor for my no-change bpo of "btrfs-progs". ack G.--- End Message ---
Re: How to make a shared lib recognized by debhelpers?
On Tue, Jul 18, 2017 at 02:35:31PM +0200, Ole Streicher wrote: > .shlibs > (which is mentioned, but not documented in the dh_makeshlibs manpage) -- deb-shlibs(5) https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-shlibdeps -- WBR, wRAR signature.asc Description: PGP signature
Re: How to make a shared lib recognized by debhelpers?
James Cowgillwrites: > You have been hit by bug #35733 in debhelper. Possibly #862909 might > apply here as well. Whow! That is quite old. I am wondering why I can't just put the library into .shlibs (which is mentioned, but not documented in the dh_makeshlibs manpage) -- in this case I get additionally the warning "pkg-has-shlibs-control-file-but-no-actual-shared-libs". > I don't see an easy fix for this, so unfortunately you might have to > keep the existing workarounds in the packaging. How would I ensure than the creation of the automatic debug package? When I just use the existing "strip" command, the debugging symbols just get removed, and also, how does dh know that it shoud build a debug package if it does not know that it contains a shared lib? Best regards Ole
Re: How to make a shared lib recognized by debhelpers?
Hi, On 17/07/17 20:20, Ole Streicher wrote: > Hi, > > I am currently adopting plplot [1], which included a simplification and > modernization of the build system (using modern debhelpers). > > I now have the problem, that one of the shared libraries is probably not > detected correctly: "lintian" tells me > > E: octave-plplot: unstripped-binary-or-object > usr/lib/x86_64-linux-gnu/octave/site/oct/api-v51/x86_64-pc-linux-gnu/plplot_octave.oct > E: octave-plplot: missing-dependency-on-libc needed by > usr/lib/x86_64-linux-gnu/octave/site/oct/api-v51/x86_64-pc-linux-gnu/plplot_octave.oct > > The Depends: field of the package however contains the entry > ${shlibs:Depends}, and this also works correctly for the other binary > packages built from the source. > > The manpages of dh_makeshlibs, dh_shlibdeps and dh_strip didn't > enlighten me here. In the original plplot package, "strip" was called > directly in install-arch, which doesn't look very smart, because it > f.e. also prevents the creation of a proper debug image, and > dpkg-shlibdeps needs to be called lated as well explicitly for this > library. You have been hit by bug #35733 in debhelper. Possibly #862909 might apply here as well. I don't see an easy fix for this, so unfortunately you might have to keep the existing workarounds in the packaging. James signature.asc Description: OpenPGP digital signature
Re: How to make a shared lib recognized by debhelpers?
Am Montag, den 17.07.2017, 21:20 +0200 schrieb Ole Streicher: > How can I do a proper handling of the library here? I guess (I am not > an octave expert, however), that the name of the library shall not be > changed. One way to make dh_strip recognize files that are not in the typical name pattern is to make it executable. What I do in the mia package, where plugins have the extension 'mia' is the following: In d/rules: # dh_strip detects executable files, so make *.mia files executable then strip then # remove the executable flag override_dh_strip: `pwd`/debian/run_strip # include "*.mia" files when searching for library dependencies override_dh_shlibdeps: dh_shlibdeps -- $(shell find debian/libmia-2.4-4/ -name "*.mia") and debian/run_strip is: >>> #!/bin/bash for f in $(find . -name "*.mia"); do chmod 755 $f; done dh_strip for f in $(find . -name "*.mia"); do chmod 644 $f; done <<< Granted it is not the most elegant solution (especially since somewhere before calling dh_strip the executable flags are actually stripped, but it does the job. Hope that helps, Gert
Re: How to make a shared lib recognized by debhelpers?
Andrey Rahmatullinwrites: > What does file(1) return for this file? The expected: $ file plplot_octave.oct plplot_octave.oct: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=98a4031426db920f83eb6bd2ac63b52be705fee8, not stripped I also crosschecked the build log, it is a usual build for a shared library: /usr/lib/ccache/c++ -fPIC -g -O2 -fdebug-prefix-map=/build/plplot-5.12.0+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,--as-needed -shared -o plplot_octave.oct CMakeFiles/plplot_octave.dir/plplot_octaveOCTAVE_wrap.cxx.o -Wl,-rpath,/build/plplot-5.12.0+dfsg/obj-x86_64-linux-gnu/src: ../../src/libplplot.so.14.0.0 -loctave -loctinterp Best regards Ole
Bug#868768: RFS: iperf3/3.2-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "iperf3" * Package name: iperf3 Version : 3.2-1 Upstream Author : Lawrence Berkeley National Laboratory. * URL : http://software.es.net/iperf/ * License : BSD-3-clause Section : net It builds those binary packages: iperf3 - Internet Protocol bandwidth measuring tool libiperf-dev - Internet Protocol bandwidth measuring tool (development files) libiperf0 - Internet Protocol bandwidth measuring tool (runtime files) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/iperf3 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/iperf3/iperf3_3.2-1.dsc Changes since the last upload: * new upstream version * enabled SCTP support (Closes: #858944) * enabled OpenSSL support * bumped standards version to 4.0.0 Regards, Raoul Gunnar Borenius
Bug#868754: marked as done (RFS: python-prov/1.5.0-2)
Your message dated Tue, 18 Jul 2017 10:04:38 + (UTC) with message-id <700955101.3752368.1500372278...@mail.yahoo.com> and subject line Re: Bug#868754: RFS: python-prov/1.5.0-2 has caused the Debian Bug report #868754, regarding RFS: python-prov/1.5.0-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 868754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-prov Version : 1.5.0-2 Upstream Author : Trung Dong Huynh * URL : https://github.com/trungdong/prov * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/python-modules/packages/python-prov.git Changes since the last upload: * fixup number of previously closed bug * Upgrade watch file to version 4 * Switch from git-dpm to gbp * Build the docs with Python 3 * Build the docs using the upstream Makefile * Add support for the nodoc build profile * Mark doc package multiarch foreign * Add missing Built-Using metadata * Normalize the Vcs-Browser URI * Bump standards version to 4.0.0 * Run autopkgtests for all supported Python versions * Drop binary-without-manpage lintian override * Normalize the package descriptions * Remove privacy breaching content in docs - New patch No-privacy-breach.patch Regards, Ghis --- End Message --- --- Begin Message --- Hello >* Package name: python-prov ok done! G.--- End Message ---
Bug#868754: RFS: python-prov/1.5.0-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-prov Version : 1.5.0-2 Upstream Author : Trung Dong Huynh * URL : https://github.com/trungdong/prov * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/python-modules/packages/python-prov.git Changes since the last upload: * fixup number of previously closed bug * Upgrade watch file to version 4 * Switch from git-dpm to gbp * Build the docs with Python 3 * Build the docs using the upstream Makefile * Add support for the nodoc build profile * Mark doc package multiarch foreign * Add missing Built-Using metadata * Normalize the Vcs-Browser URI * Bump standards version to 4.0.0 * Run autopkgtests for all supported Python versions * Drop binary-without-manpage lintian override * Normalize the package descriptions * Remove privacy breaching content in docs - New patch No-privacy-breach.patch Regards, Ghis
Bug#868668: marked as done (RFS: parsedatetime/2.4-2)
Your message dated Tue, 18 Jul 2017 09:12:33 + (UTC) with message-id <1627841793.3666212.1500369153...@mail.yahoo.com> and subject line Re: Bug#868668: RFS: parsedatetime/2.4-2 has caused the Debian Bug report #868668, regarding RFS: parsedatetime/2.4-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 868668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: parsedatetime Version : 2.4-2 Upstream Author : Mike Taylor * URL : https://pypi.python.org/pypi/parsedatetime * License : Apache-2.0 Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/python-modules/packages/parsedatetime.git Changes since the last upload: * Team upload [ Ghislain Antony Vaillant ] * Update the gbp configuration * Remove superfluous ${shlibs:Depends} * Release to unstable Best regards, Ghis --- End Message --- --- Begin Message --- >I am looking for a sponsor for the following package: --- End Message ---