Bug#845934: RFS: libcorkipset/1.1.1+20150311-6~bpo8+1 -- C library to store sets/maps of IP address
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: rogershim...@gmail.com Dear Mentors, I am looking for a sponsor for my package "libcorkipset" into jessie-backports. It's a clean rebuild bpo from testing/stretch. * Package name: libcorkipset Version : 1.1.1+20150311-6~bpo8+1 Upstream Author : Douglas Creager* URL : https://github.com/redjack/ipset * License : BSD-3-clause Section : libs It builds those binary packages: libcorkipset-dev - C library to store sets/maps of IP address (development files) libcorkipset-doc - C library to store sets/maps of IP address (documentation files) libcorkipset-utils - C library to store sets/maps of IP address (utility files) libcorkipset1 - C library to store sets/maps of IP address To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcorkipset Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcorkipset/libcorkipset_1.1.1+20150311-6~bpo8+1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/libcorkipset git checkout jessie-backports # DIST=jessie-backports git-pbuilder create gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=jessie-backports I pushed my changes to git repo: https://github.com/rogers0/libcorkipset - branch jessie-backports Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#845933: RFS: libcork/0.15.0+ds-10~bpo8+1 -- simple, easily embeddable, cross-platform C library
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: rogershim...@gmail.com Dear Mentors, I am looking for a sponsor for my package "libcork" into jessie-backports. It's a clean rebuild bpo from testing/stretch. * Package name: libcork Version : 0.15.0+ds-10~bpo8+1 Upstream Author : Douglas Creager* URL : https://libcork.readthedocs.io * License : BSD-3-clause Section : libs It builds those binary packages: libcork-dev - simple, easily embeddable, cross-platform C library (development libcork-doc - simple, easily embeddable, cross-platform C library (documentatio libcork15 - simple, easily embeddable, cross-platform C library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcork Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcork/libcork_0.15.0+ds-10~bpo8+1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/libcork cd libcork git checkout jessie-backports # DIST=jessie-backports git-pbuilder create gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=jessie-backports I pushed my changes to git repo: https://github.com/rogers0/libcork - branch jessie-backports Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#838481: marked as done (RFS: daemontools/0.76-7 [RC])
Your message dated Sun, 27 Nov 2016 01:06:39 +0100 with message-idand subject line NMU of daemontools has caused the Debian Bug report #838481, regarding RFS: daemontools/0.76-7 [RC] 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.) -- 838481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "daemontools": * Package name: daemontools Version : 0.76-7 Section : admin It builds those binary packages: daemontools - a collection of tools for managing UNIX services daemontools-run - daemontools service supervision Download the package with dget using this command: dget -x http://smarden.org/kaGh6ut/daemontools_0.76-7.dsc Changes since the last upload: * debian/rules: do not FTBFS with dpkg-buildpackage -A (thx Santiago Vila; closes: #831921). The process to get my new gpg key into the debian keyring is stuck for some reason, although signatures are available, hence the RFS. $ debdiff daemontools_0.76-6.dsc daemontools_0.76-7.dsc diff -u daemontools-0.76/debian/changelog daemontools-0.76/debian/changelog --- daemontools-0.76/debian/changelog +++ daemontools-0.76/debian/changelog @@ -1,3 +1,10 @@ +daemontools (1:0.76-7) unstable; urgency=low + + * debian/rules: do not FTBFS with dpkg-buildpackage -A (thx Santiago +Vila; closes: #831921). + + -- Gerrit Pape Wed, 21 Sep 2016 08:57:18 + + daemontools (1:0.76-6) unstable; urgency=medium * workaround #767933 by copying from sysvinit-2.88dsf: diff -u daemontools-0.76/debian/rules daemontools-0.76/debian/rules --- daemontools-0.76/debian/rules +++ daemontools-0.76/debian/rules @@ -14,6 +14,8 @@ done touch patch-stamp +build-arch: build +build-indep: build build: deb-checkdir build-stamp build-stamp: patch-stamp cd daemontools-0.76 && package/compile @@ -101,7 +103,7 @@ binary: binary-indep binary-arch -.PHONY: patch build clean install install-arch install-indep binary \ +.PHONY: patch build build-arch build-indep clean install install-arch install-indep binary \ binary-arch binary-indep include debian/implicit $ Regards, Gerrit. signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Hi, the previous NMU did not seem to get to unstable, so I've uploaded it again. Please find attached the updated patch for the NMU. If you'd like to have a new version with yourself as maintainer sponsored into Debian, feel free to contact me. Regards, Tobias diff -u daemontools-0.76/debian/changelog daemontools-0.76/debian/changelog --- daemontools-0.76/debian/changelog +++ daemontools-0.76/debian/changelog @@ -1,3 +1,23 @@ +daemontools (1:0.76-6.1) unstable; urgency=medium + + [ Jan Mojzis ] + * Non-maintainer upload. + * supervise.c: restart the monitored process when +fork(2) fails (Closes: #819036) + * d/rules: fix mtimes before building binary package to produce +reproducible output (Closes: #793003) (Closes: #776876) + * d/rules: do not FTBFS with dpkg-buildpackage -A (thx Santiago +Vila) (Closes: #831921) + * d/implicit: fixed md5sums permissions 0664 -> 0644 + * d/control: bump to standards-version 3.9.8 + * d/control: fixed the description + + [ Dr. Tobias Quathamer ] + * New upload with all changes from Jan, his previous NMU +to DELAYED/5 did not end up in unstable. + + -- Dr. Tobias Quathamer Sun, 27 Nov 2016 00:26:56 +0100 + daemontools (1:0.76-6) unstable; urgency=medium * workaround #767933 by copying from sysvinit-2.88dsf: @@ -242 +261,0 @@ - diff -u daemontools-0.76/debian/control daemontools-0.76/debian/control --- daemontools-0.76/debian/control +++ daemontools-0.76/debian/control @@ -2,7 +2,7 @@ Section: admin Priority: optional Maintainer: Gerrit Pape -Standards-Version: 3.9.5.0 +Standards-Version: 3.9.8 Package: daemontools Architecture: any @@ -10,7 +10,7 @@ Suggests: daemontools-run | runit Depends: ${shlibs:Depends} Replaces: daemontools-doc -Description: a collection of tools for managing UNIX services +Description: collection of tools for managing UNIX services supervise monitors a service. It starts the service and restarts the service if it dies. Setting up a new service is easy: all supervise needs is a directory with a run script that runs the service. diff -u
Bug#845744: marked as done (RFS: ismrmrd/1.3.3-1)
Your message dated Sat, 26 Nov 2016 22:26:48 + with message-idand subject line closing RFS: ismrmrd/1.3.3-1 has caused the Debian Bug report #845744, regarding RFS: ismrmrd/1.3.3-1 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.) -- 845744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845744 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 my package "ismrmrd" * Package name: ismrmrd Version : 1.3.3-1 Upstream Author : The ISMRMRD developers * URL : http://ismrmrd.github.io/ * License : Expat Section : science It builds those binary packages: ismrmrd-schema - schema for ISMRMRD ismrmrd-tools - command-line tools for ISMRMRD libismrmrd-dev - development files for ISMRMRD libismrmrd-doc - documentation for ISMRMRD libismrmrd1.3 - ISMRM Raw Data format (ISMRMRD) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ismrmrd Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/ismrmrd/ismrmrd_1.3.3-1.dsc Successful build on debomatic: http://debomatic-amd64.debian.net/distribution#unstable/ismrmrd/1.3.3-1/buildlog Changes since the last upload: * New upstream version 1.3.3 * Update patch queue. - Drop Explicit-64-bit-shifts-for-flags.patch, applied upstream. - Refresh Fix-HDF5-detection-with-CMake-3.6.patch. - Refresh Use-Debian-CMake-find-module-location.patch. - Drop hdf5-1.10.patch, applied upstream. * Fix usability of ISMRMRD CMake packaging. - New patch Fix-CMake-package-configuration.patch. - New patch Fix-CMake-package-detection.patch. - Drop Use-Debian-CMake-find-module-location.patch, no longer required. - Install CMake configuration to -dev package. * Upgrade packaging to debhelper 10. * Drop superfluous Testsuite field. * Simplify the packaging testsuite. * Enable multiarch installation of binaries. - New patch Add-support-for-multiarch.patch. - Update install paths of lib and dev packages. - Add Multi-Arch fields to all binary packages. * Keep doxygen generated instance of jQuery. * Miscellaneous changes to control file: - Replace build dependency on libhdf5-serial-dev with libhdf5-dev. - Add missing install dependency on libhdf5-dev for the -dev package. * Miscellaneous changes to rules file: - Disable verbosity by default. - Reformat content of dh_auto_build override. Regards, Ghislain Vaillant --- End Message --- --- Begin Message --- Package ismrmrd has been removed from mentors.--- End Message ---
Bug#845797: RFS: gramps/4.2.4~dfsg-1~bpo8+1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking to begin backporting Gramps. I have already done that in Ubuntu a few times, but feel guilty for not doing the same in Debian. As Gramps is NEW to jessie-backports, I am asking for a sponsor to do the first upload for me. I have been added to the ACL for backports, have subscribed to the backports list, and plan to continue backporting as long as possible. * Package name: gramps Version : 4.2.4~dfsg-1~bpo8+1 Upstream Author : The Gramps Project * URL : https://gramps-project.org/ * License : GPL-2 Section : gnome It builds this binary package: gramps - Genealogical research program To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gramps Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gramps/gramps_4.2.4~dfsg-1~bpo8+1.dsc Debian packaging is available here: https://anonscm.debian.org/cgit/collab-maint/gramps.git You will need to checkout the jessie-backports branch in the git repo. Then with a jessie cowbuilder chroot set up, I used the following incantation to ensure the changes file has all the changelog entries since jessie: $ gbp buildpackage --git-pbuilder --git-dist=jessie -v4.1.1~dfsg-3 Changes since the last upload: * Rebuild for jessie-backports. * Update branch in gbp.conf & Vcs-Git URL. Regards, Ross Gammon -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100, 'xenial-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#845784: RFS: dropwizard-metrics [ITP]
Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-j...@lists.debian.org Dear mentors, I am looking for a sponsor for the package "dropwizard-metrics". This software was originally packaged by Tim Potter, but does not appear to have been uploaded or updated since Nov 2014. I have updated the package to the latest upstream and standards versions. . Amongst other things, it is a dependancy of spymemcached, which I am currently investigating packaging. * Package name: dropwizard-metrics Version : 3.1.2-1 Upstream Author : Coda Hale, Yammer Inc. * URL : http://metrics.dropwizard.io/ * License : Apache-2.0 Section : java It builds those binary packages: libdropwizard-metrics-java - capture JVM- and application-level metrics for Java applications To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dropwizard-metrics Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dropwizard-metrics/dropwizard-metrics_3.1.2-1.dsc More information about dropwizard-metrics can be obtained from http://metrics.dropwizard.io/. The package source is being managed in the pkg-java team Alioth repository: https://anonscm.debian.org/cgit/pkg-java/dropwizard-metrics.git Changes since the last upload: * Team upload * New upstream release (3.1.2) * Minimal changes to get updated package building + Remove old patches + Add new modules to libdropwizard-metrics-java.poms, ignore modules which won't build. + Update maven.rules and maven.ignoreRules + Add new dependencies to debian/control * Use secure VCS URLs * Update Standards-Version from 3.9.6 to 3.9.8 (no change required) * Update debian/copyright * Use secure URL for copyright format -- Christopher Hoskin Sat, 26 Nov 2016 17:00:10 + Regards, Christopher Hoskin
Re: Bug#845018: RFS: quagga/1.1.0-1 [ITA] -- network routing daemons
❦ 22 novembre 2016 23:55 +1100, Scott Leggett: > This is now ready, here are the changes since your last review: > > * Add automatic migration from -dbg to -dbgsym. > * Add users/groups unconditionally to simplify preinst. > * Create "quagga" metapackage. I would have removed the recommends for quagga-core package as it would make more difficult for most people to only keep the daemons they need and do not bring anything sensible compared to quagga/quagga-core packages. Of course, that's quite subjective. > * Use debhelper integration with dpkg-maintscript-helper. > * Remove /etc/default/quagga. Should be removed with dpkg-maintscript-helper to alert the user there was a change (and its modifications are now ignored). You could also remove README.Maintainer if it doesn't contain any relevant information. There are also some bits of the README.Debian about SNMP that are not up-to-date (some sentences just need to be removed). Other than that, all is OK. -- Debian package sponsoring guidelines: https://vincent.bernat.im/en/debian-package-sponsoring.html signature.asc Description: PGP signature
Re: Writing outside of build dir
On 11/26/2016 02:31 PM, Ross Vandegrift wrote: > On Sat, Nov 26, 2016 at 02:30:59AM +0100, Christian Seiler wrote: >>> 2) Is there a common pattern for handling upstream tests that break this >>> rule? Maybe there's an alternative to disabling them? >> >> If upstream tests do that, I would suggest sending a patch >> upstream that fixes them, because especially for tests I >> would consider this a bug. >> >> That said, if tests just require stuff in the home directory >> you could set the HOME environment variable to a temporary >> directory within the build tree before you run the tests, to >> work around this kind of problem. Nevertheless I would consider >> those tests buggy and would want to patch them. >> >> If you could give a couple of examples of what exactly you're >> thinking of, maybe my answer could be more specific. > > A library service creates local sockets. The library provides a > fallback mechanism for the socket location - first try $XDG_RUNTIME_DIR, > second try $HOME, finally use $TMPDIR. Most of the tests unset the > first two and go straight to TMPDIR. But to test the fallback mechanism > itself, two tests do not. > > As a workaround, I disabled these. But it was suggested to instead set > HOME=/tmp, XDG_RUNTIME_DIR=/tmp. Seems clever, but I wasn't sure if > this was permitted. Well, you could also do the following before running the tests (as a bash script; how you integrate that is up to you): cleanup() { [ -n "$temporary_HOME" ] && rm -r "$temporary_HOME" [ -n "$temporary_XDG_RUNTIME_DIR" ] && rm -r "$temporary_XDG_RUNTIME_DIR" } trap cleanup EXIT temporary_HOME="$(mktemp -d)" temporary_XDG_RUNTIME_DIR="$(mktemp -d)" HOME="$temporary_HOME" XDG_RUNTIME_DIR="$temporary_XDG_RUNTIME_DIR" ./run_tests That way you'd not be using /tmp directly (bad idea to pollute that directly), and you'd have two different directories, to be sure that the fallback actually works. Also, if setting HOME is not enough (because the software reads the home directory directly from the NSS database, e.g. /etc/passwd), then you could use nss_wrapper for that, see https://cwrap.org/nss_wrapper.html That was specifically designed for tests to provide a different environment. In general CWrap is very nice for tests that integrate into the system a bit deeper: https://cwrap.org/ Finally, some tests you may not want to execute during build time. There are also runtime tests in Debian, called autopkgtests, and there is automated infrastructure in place to run them regularly. Debian's infrastructure uses LXC to isolate these tests, so in those tests you can in fact write anywhere you want if that really is required (as long as you declare things such as the proper isolation level and possibly breaks-testbed). See also: https://ci.debian.net/doc/ I would in fact recommend using some kind of autopkgtest in general, even if you can run the unit test suite during build time - since the autopkgtests are more related to integration testing instead of pure functionality. (You would run different tests, obviously.) For example, a web server package could contain unit tests that would start the web server on localhost on a random port during build time to see if it responds correctly to requests, whereas an autopkgtest for the same package would test for example whether the webserver is started properly after package installation and listens on the correct port. The autopkgtest would have the proper isolation level specified (isolation-container in this case) to make sure that this does not interfere with the system the test is run on. Regards, Christian
Re: Writing outside of build dir
On Sat, Nov 26, 2016 at 02:30:59AM +0100, Christian Seiler wrote: > > 2) Is there a common pattern for handling upstream tests that break this > > rule? Maybe there's an alternative to disabling them? > > If upstream tests do that, I would suggest sending a patch > upstream that fixes them, because especially for tests I > would consider this a bug. > > That said, if tests just require stuff in the home directory > you could set the HOME environment variable to a temporary > directory within the build tree before you run the tests, to > work around this kind of problem. Nevertheless I would consider > those tests buggy and would want to patch them. > > If you could give a couple of examples of what exactly you're > thinking of, maybe my answer could be more specific. A library service creates local sockets. The library provides a fallback mechanism for the socket location - first try $XDG_RUNTIME_DIR, second try $HOME, finally use $TMPDIR. Most of the tests unset the first two and go straight to TMPDIR. But to test the fallback mechanism itself, two tests do not. As a workaround, I disabled these. But it was suggested to instead set HOME=/tmp, XDG_RUNTIME_DIR=/tmp. Seems clever, but I wasn't sure if this was permitted. The two tests in question are here: https://github.com/rvandegrift/efl/blob/debian/sid/src/tests/ecore_con/ecore_con_test_ecore_con.c#L325 Thanks very much for your explanation - exactly the kind of info I was looking for! Ross
Bug#845744: RFS: ismrmrd/1.3.3-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ismrmrd" * Package name: ismrmrd Version : 1.3.3-1 Upstream Author : The ISMRMRD developers * URL : http://ismrmrd.github.io/ * License : Expat Section : science It builds those binary packages: ismrmrd-schema - schema for ISMRMRD ismrmrd-tools - command-line tools for ISMRMRD libismrmrd-dev - development files for ISMRMRD libismrmrd-doc - documentation for ISMRMRD libismrmrd1.3 - ISMRM Raw Data format (ISMRMRD) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ismrmrd Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/ismrmrd/ismrmrd_1.3.3-1.dsc Successful build on debomatic: http://debomatic-amd64.debian.net/distribution#unstable/ismrmrd/1.3.3-1/buildlog Changes since the last upload: * New upstream version 1.3.3 * Update patch queue. - Drop Explicit-64-bit-shifts-for-flags.patch, applied upstream. - Refresh Fix-HDF5-detection-with-CMake-3.6.patch. - Refresh Use-Debian-CMake-find-module-location.patch. - Drop hdf5-1.10.patch, applied upstream. * Fix usability of ISMRMRD CMake packaging. - New patch Fix-CMake-package-configuration.patch. - New patch Fix-CMake-package-detection.patch. - Drop Use-Debian-CMake-find-module-location.patch, no longer required. - Install CMake configuration to -dev package. * Upgrade packaging to debhelper 10. * Drop superfluous Testsuite field. * Simplify the packaging testsuite. * Enable multiarch installation of binaries. - New patch Add-support-for-multiarch.patch. - Update install paths of lib and dev packages. - Add Multi-Arch fields to all binary packages. * Keep doxygen generated instance of jQuery. * Miscellaneous changes to control file: - Replace build dependency on libhdf5-serial-dev with libhdf5-dev. - Add missing install dependency on libhdf5-dev for the -dev package. * Miscellaneous changes to rules file: - Disable verbosity by default. - Reformat content of dh_auto_build override. Regards, Ghislain Vaillant
Bug#839383: RFS: php-net-idna2/0.1.1-1 [ITP]
control: owner -1 ! control: tags -1 moreinfo >I am looking for a sponsor for my package "php-net-idna2" can you please enlighten me about the lintian warnings? http://debomatic-amd64.debian.net/distribution#unstable/php-net-idna2/0.1.1-1/lintian I would like to know them before sponsoring :) thanks! G.
Bug#842157: RFS: php-db-dataobject/1.11.5-1 [ITP] -- PHP PEAR module for object based SQL query building
control: owner -1 ! control: tags -1 moreinfo (resending to the open RFS bug) Hi, >https://mentors.debian.net/package/php-db-dataobject fix lintian and remove moreinfo tag (everything except gpg signature should be fixed or answered) also piuparts is not happy (look the php parts) http://debomatic-amd64.debian.net/distribution#unstable/php-db-dataobject/1.11.5-1/piuparts G.