Bug#776232: RFS: xcffib/0.1.10-2
Having Description: in the source package stanza in d/control is incorrect, and dpkg-source warns about it. You don't need to prepend debian/tmp to paths in *.install. Though with pybuild you usually don't need *.install at all. The package FTBFS in sbuild: dh build --with python2,python3 --buildsystem=pybuild dh_testdir -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:170: python2.7 setup.py config running config I: pybuild base:170: python3.4 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/«PKGBUILDDIR»' make xcffib make[2]: Entering directory '/«PKGBUILDDIR»' cabal configure --enable-tests Config file path source is default config file. Config file /sbuild-nonexistent/.cabal/config not found. Writing default configuration to /sbuild-nonexistent/.cabal/config cabal: /sbuild-nonexistent/.cabal: does not exist make[2]: *** [dist] Error 1 -- WBR, wRAR signature.asc Description: Digital signature
Bug#776539: RFS: scythe/0.994-1 [ITP] -- Bayesian adaptor trimmer for sequencing reads
Your changelog entry has UNRELEASED as a distribution, you shoudl change that before publishing if you ask for sponsorship and not just a review (though it's not a problem for a sponsor to edit that before uploading). You should have a section for debian/* in d/copyright. You don't need to use DPKG_EXPORT_BUILDFLAGS and /usr/share/dpkg/buildflags.mk when using dh_auto_* in compat levels 9+. You are creating debian/scythe.1 but not cleaning it so it ends up in debian.tar which is wrong. Your d/watch doesn't work. You should use http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ as the copyright format URL (lintian detects this). The upstream Makefile ignores CPPFLAGS from the environment so fortify dpkg-buildflags feature doesn't work (lintian detects this). -- WBR, wRAR signature.asc Description: Digital signature
Bug#783529: RFS: spacenavd/0.6-1 [ITA]
Hi Vincent, Thx for your review! debian/copyright is missing a few entries: - src/serial/*: Copyright 1997-2001 John E. Stone (j.st...@acm.org), 3-clause BSD (+ upstream author) Should be fixed. debian/stamp-patched is useless and can be removed. Done. debian/patches/run.patch is rather redundant; /var/run is not going to be removed from Debian in the foreseeable future and will likely be kept around for compatibility reasons for a long time. If you do decide to keep it though, please look into adding DEP-3 [1] headers for it (and any future patch you add). As it is not too invasive, I choose to keep it, I just added a simple header. Your package isn't actually hardened. export DEB_BUILD_MAINT_OPTIONS = hardening=+all in d/rules isn't going to do anything if your package's build system ignores the hardening flags set by dpkg-buildflags. Right, I have seen this but I did not know how to deal with. I plan to propose an update build system (cmake) to upstream dev but for now, I added a debian specific patch. An updated package has been sent on http://mentors.debian.net/package/spacenavd if you want to check again. Regards, Rodolphe signature.asc Description: OpenPGP digital signature
Bug#776285: marked as done (RFS: nfft/3.3.0~alpha4 -- non-uniform Fourier transform)
Your message dated Sat, 16 May 2015 19:50:58 +0500 with message-id 20150516145058.gb1...@belkar.wrar.name and subject line Closing has caused the Debian Bug report #776285, regarding RFS: nfft/3.3.0~alpha4 -- non-uniform Fourier transform 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.) -- 776285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package nfft: * Package name: nfft Version : nfft/3.3.0~alpha4 Upstream Author : Prof. Dr. Daniel Potts po...@mathematik.tu-chemnitz.de mailto:po...@mathematik.tu-chemnitz.de * URL :http://www-user.tu-chemnitz.de/~potts/nfft/ http://www-user.tu-chemnitz.de/%7Epotts/nfft/ * License : GPL Programming Lang: C Description : Library for computing the Non-uniform Fast Fourier Transform This upload include a new upstream version, which adds support for multi-precision. Furthermore, the source tarball now allows building the documentation using Doxygen. As a result, additional binaries are built from the source package: libnfft3-double2 -- double precision build of the library libnfft3-single2 -- single precision build of the library libnfft3-long2 -- long double precision build of the library libnfft3-doc -- documentation of the library And the old libnfft3-2 package has been converted to a transitional package which installs all available versions of the library (similar to the fftw package suite). Also v3.3+ source tarballs now ship with a test suite, which is now run as part of the package build process. This package is maintained by the Debian Science Team and can be checked out athttp://anonscm.debian.org/gitweb/?p=debian-science/packages/nfft.git http://anonscm.debian.org/gitweb/?p=debian-science/packages/linop.git. This package should be uploaded to experimental first. Regards, Ghislain ---End Message--- ---BeginMessage--- The package is in the archive. -- WBR, wRAR signature.asc Description: Digital signature ---End Message---
Bug#777586: RFS: crosswalk/11.40.277.2-1 [ITP]
On Tue, Feb 10, 2015 at 05:06:49PM +0800, Xinchao He wrote: It builds those binary packages: crosswalk - HTML5 web runtime That's probably too short/vague. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/crosswalk Even that page shows you have a lot of lintian-detected problems, some of them errors. Please don't publish packages before checking them with lintian and fixing problems reported by it. More information about Crosswalk can be obtained from https://crosswalk-project.org/. From https://github.com/crosswalk-project/crosswalk-website/wiki/Downstream-Chromium : Crosswalk uses forked versions of Chromium repositories (for example Blink and Chromium) We do not allow such things in the archive, unfortunately. -- WBR, wRAR signature.asc Description: Digital signature
Re: Closing superseeded RFP
On Fri, May 15, 2015 at 11:15 PM, Dmitry Bogatov wrote: Scrolling RFP requests, I found #461915, lockrun, which is superseeded by `cronutils`. Can I somehow make this fact availiable, for #461915 not clutter list? Should I? I'd suggest closing the bug with an explanation: https://www.debian.org/Bugs/Developer#closing -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6gmy0bgbuew3ycwoxz_ajrkfu1mca+3qvgn5mxzhxv...@mail.gmail.com
Bug#783308: RFS: mediagoblin/0.7.1+dfsg1-1 [ITP]
On Fri, May 15, 2015 at 9:27 PM, Simon Fondrie-Teitler wrote: I looked into packaging them separately, but couldn't find good documentation on how to package css or javascript files. A few Debian developers I talked recommended not packaging them on their own. For JavaScript, check out the many libjs-* examples in the archive. For CSS, it would just be a matter of installing the files in /usr/share/ somewhere and having mediagoblin refer to them. Embedded code copies are against policy. The world of web software however often plays fast and loose with APIs, often very specific versions are required. I guess that is why people are recommending embedded code copies. Personally I recommend packaging those versions separately, as we do for GCC or Python itself. https://wiki.debian.org/EmbeddedCodeCopies I've talked to upstream about the files, and some will be removed in the new release, like the binary translation files. Others need to be there to make it easy for people installing via pip or a git checkout, like the javascript. Thanks. Hmm, ok. That's a good idea, although the version in README.Debian is closer to an example of one possible setup, rather than a suggested way of running it. I'm still thinking about the best way of doing this. I'm assuming it's not a blocking issue for package upload? Not a blocking issue. I tried doing this, but the script won't even succeed showing help output when run without mediagoblin/tools/common.py somewhere on the python path. I'm not sure if it's a good idea to modify the python path during build. It would be fine to set/modify PYTHONPATH for the manual page build command, probably not other stuff though. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6e+szlnpovh6zx7q8o5h0czina47t+fyjzw2tvtqox...@mail.gmail.com
Bug#784732: RFS: liquidprompt/1.9-1 [ITP]
Control: tag -1 + moreinfo Control: owner -1 ! Hi Arturo, On Fri, May 8, 2015 at 1:08 AM, Arturo Borrero Gonzalez arturo.borrero.g...@gmail.com wrote: Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package liquidprompt * Package name: liquidprompt * Version : 1.9 * Upstream Author : Nojhan noj...@nojhan.net * URL : https://github.com/nojhan/liquidprompt * License : AGPL-3 * Programming Lang: shell * Section : misc It builds those binary packages: liquidprompt - adaptative prompt for bash zsh To access further information about this package, please visit the following URL: http://mentors.debian.net/package/liquidprompt Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/l/liquidprompt/liquidprompt_1.9-1.dsc More information about hello can be obtained from https://github.com/nojhan/liquidprompt. Just a few more things to add to Andrey's earlier review: - Don't hardcode a reference to $HOME/.config in liquidprompt_activate, use $XDG_CONFIG_HOME instead [1]. - If your package is covered by a license that does not have the full text stored in /usr/share/common-licenses, you should include the full text yourself in d/copyright. I also share Andrey's concern about the multiple invocations of liquidprompt_activate polluting bashrc/zshrc, although I don't consider that a blocker for an upload. Regards, Vincent [1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CACZd_tC6Ezmpeju0pQokPKob_y1X1=GNJGSu=powhpsm3nl...@mail.gmail.com
Bug#783529: RFS: spacenavd/0.6-1 [ITA]
Control: tag -1 + moreinfo Control: owner -1 ! Hi Rodolphe, On Mon, Apr 27, 2015 at 11:10 AM, Rodolphe PELLOUX-PRAYER rodol...@damsy.net wrote: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package spacenavd * Package name: spacenavd Version : 0.6-1 Upstream Author : John Tsiombikas nucl...@member.fsf.org * URL : http://spacenav.sourceforge.net * License : GPL-3.0+ Section : utils It builds those binary packages: spacenavd - daemon for using 3D input devices from 3Dconnexion To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spacenavd Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spacenavd/spacenavd_0.6-1.dsc Changes since the last upload: * Imported Upstream version 0.6 * Remove initfile patch. We use debian/spacenavd.init anyway. * Remove makefile patch and change spacenavd path in init file. * Use DEP-5 copyright format. * Add upstream example config file. * Source init-functions in init script. * Bump standards version to 3.9.6 and remove obsolete DM-Upload-Allowed field. * Switch to debhelper 9. * Remove quilt and autotools-dev dependencies. * Set architecture linux-any. Closes: #745177. * Enable systemd service file. * Patch to use /run instead of /var/run. * Enable hardenings flags. * New maintainer. Closes: #781184. * Add Vcs-* fields. debian/copyright is missing a few entries: - src/serial/*: Copyright 1997-2001 John E. Stone (j.st...@acm.org), 3-clause BSD (+ upstream author) debian/stamp-patched is useless and can be removed. debian/patches/run.patch is rather redundant; /var/run is not going to be removed from Debian in the foreseeable future and will likely be kept around for compatibility reasons for a long time. If you do decide to keep it though, please look into adding DEP-3 [1] headers for it (and any future patch you add). Your package isn't actually hardened. export DEB_BUILD_MAINT_OPTIONS = hardening=+all in d/rules isn't going to do anything if your package's build system ignores the hardening flags set by dpkg-buildflags. Regards, Vincent [1] http://dep.debian.net/deps/dep3/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caczd_tchf3ujm1htntandeoxnyh0n2jdwm61ujbiwe56ps2...@mail.gmail.com
Bug#779589: marked as done (RFS: mercurial-keyring/0.6.7-1)
Your message dated Sat, 16 May 2015 01:33:54 -0700 with message-id caczd_tc8xzphzzmul2ubzr64fym5afo0ofqus0z+rs+ey_h...@mail.gmail.com and subject line Re: Bug#779589: RFS: mercurial-keyring/0.6.7-1 has caused the Debian Bug report #779589, regarding RFS: mercurial-keyring/0.6.7-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.) -- 779589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Dear mentors, I am looking for a sponsor for my package mercurial-keyring * Package name: mercurial-keyring Version : 0.6.7-1 Upstream Author : Marcin Kasperski marcin.kasper...@mekk.waw.pl * URL : http://pypi.python.org/pypi/mercurial_keyring * License : BSD-3-clause Section : python It builds those binary packages: mercurial-keyring - Mercurial Keyring Extension To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mercurial-keyring Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-keyring/mercurial-keyring_0.6.7-1.dsc More information about mercurial-keyring can be obtained from http://pypi.python.org/pypi/mercurial_keyring Changes since the last upload: * New upstream release. * Update packaging to use dh-python and pybuild. * Policy bumped to 3.9.6 without changes. * Update watch file to accomodate changes on pypi. Regards, Christoph Mathys -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-46-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 ---End Message--- ---BeginMessage--- Hi Christoph, On Mon, Mar 2, 2015 at 11:13 AM, Christoph Mathys erase...@gmail.com wrote: Package: sponsorship-requests Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Dear mentors, I am looking for a sponsor for my package mercurial-keyring * Package name: mercurial-keyring Version : 0.6.7-1 Upstream Author : Marcin Kasperski marcin.kasper...@mekk.waw.pl * URL : http://pypi.python.org/pypi/mercurial_keyring * License : BSD-3-clause Section : python It builds those binary packages: mercurial-keyring - Mercurial Keyring Extension To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mercurial-keyring Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-keyring/mercurial-keyring_0.6.7-1.dsc More information about mercurial-keyring can be obtained from http://pypi.python.org/pypi/mercurial_keyring Changes since the last upload: * New upstream release. * Update packaging to use dh-python and pybuild. * Policy bumped to 3.9.6 without changes. * Update watch file to accomodate changes on pypi. Uploaded, thanks for your contribution to Debian! Regards, Vincent---End Message---
Bug#780793: RFS: hovercraft/2.0~b1+dfsg-1 [ITP] --- impress.js presentations by reStructuredText
I've injected Hovercraft to the group's SVN repo [1] now. It'll take part in the upcoming svn-git migration procedure then and will find itself in the proper git repo automatically. DS [1] svn+ssh://lo...@svn.debian.org/svn/python-apps/packages/hovercraft -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/555713de.60...@danielstender.com
Re: package name conflict between RFP and ITP
Hi! lumin cdlumin...@gmail.com writes: A package-name-conflicting RFP [4] was found. Description : Free software alternative for xv image viewer I have no idea about how to handle this name conflict. Any advice or guide? As this is a 3 years old *Request* without any action since then I wouldn't worry about that package much. Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer signature.asc Description: PGP signature
Bug#783529: RFS: spacenavd/0.6-1 [ITA]
Hi Rodolphe, On Sat, May 16, 2015 at 1:23 PM, Rodolphe PELLOUX-PRAYER rodol...@damsy.net wrote: Hi Vincent, Thx for your review! debian/copyright is missing a few entries: - src/serial/*: Copyright 1997-2001 John E. Stone (j.st...@acm.org), 3-clause BSD (+ upstream author) Should be fixed. You're also missing Thomas Anderson t...@nextgenengineering.com as the copyright holder for a number of files in src/magellan/. (In case you haven't done so already, please take the time to do a thorough license/copyright check yourself when adopting/packaging new packages.) debian/stamp-patched is useless and can be removed. Done. debian/patches/run.patch is rather redundant; /var/run is not going to be removed from Debian in the foreseeable future and will likely be kept around for compatibility reasons for a long time. If you do decide to keep it though, please look into adding DEP-3 [1] headers for it (and any future patch you add). As it is not too invasive, I choose to keep it, I just added a simple header. Ok. Your package isn't actually hardened. export DEB_BUILD_MAINT_OPTIONS = hardening=+all in d/rules isn't going to do anything if your package's build system ignores the hardening flags set by dpkg-buildflags. Right, I have seen this but I did not know how to deal with. I plan to propose an update build system (cmake) to upstream dev but for now, I added a debian specific patch. That's fine. By the way, I also suggest that you use start-stop-daemon in your sysvinit script, especially since you're shipping a script of your own here. Regards, Vincent -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CACZd_tCLFotzUgXPygnhZorQ_NAdtLmDZ1=pzzn2sois8tt...@mail.gmail.com
