Bug#824248: RFS: pickleshare/0.7.2-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pickleshare" * Package name: pickleshare Version : 0.7.2-1 Upstream Author : Ville Vainio * URL : https://github.com/pickleshare/pickleshare * License : Expat Section : python It builds those binary packages: python-pickleshare - File system based database that uses Python pickles for Python 2 python3-pickleshare - File system based database that uses Python pickles for Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pickleshare Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pickleshare/pickleshare_0.7.2-1.dsc Changes since the last upload: pickleshare (0.7.2-1) unstable; urgency=medium * New upstream version. * Bump standards-version up. * Use https for Vcs-* fields. Thanks, Snark on #debian-python
Bug#824246: RFS: ptyprocess/0.5.1-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ptyprocess" * Package name: ptyprocess Version : 0.5.1-1 Upstream Author : Thomas Kluyver * URL : https://github.com/pexpect/ptyprocess * License : ISC Section : python It builds those binary packages: python-ptyprocess - Run a subprocess in a pseudo terminal from Python 2 python3-ptyprocess - Run a subprocess in a pseudo terminal from Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ptyprocess Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/ptyprocess/ptyprocess_0.5.1-1.dsc Changes since the last upload: ptyprocess (0.5.1-1) unstable; urgency=medium * New upstream release. * Pushed standards-version up. * Use https in Vcs-* fields. Thanks, Snark on #debian-python
Bug#824243: RFS: twinkle/1:1.9.0+git20160321.0.64a0816+dfsg-1 [RC] -- Voice over Internet Protocol (VoIP) SIP Phone
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for the package "twinkle": git clone https://anonscm.debian.org/git/pkg-voip/twinkle.git cd twinkle && pristine-tar checkout ../twinkle_1.9.0+git20160321.0.64a0816+dfsg.orig.tar.xz For verification, these are the current branch heads: git show-ref --heads a544eebc919e6f78067b73c2cc54fb438e6f5666 refs/heads/master 961140e91690333a33b3dd0e7ef5ad1333195f6a refs/heads/pristine-tar 8916774a5c74898e4bcc5f4f9c9b0e3cd5fd4d5e refs/heads/upstream It builds these binary packages: twinkle - Voice over Internet Protocol (VoIP) SIP Phone More information about twinkle can be obtained from http://twinkle.dolezel.info. Changes since the last upload: twinkle (1:1.9.0+git20160321.0.64a0816+dfsg-1) unstable; urgency=medium * New upstream snapshot (Closes: #821234). * Drop patches applied upstream. * Drop build dependency on qtquick1-5-dev (Closes: #810708). * Enable hardening build flags. * Bump Standards-Version to 3.9.8. -- Peter ColbergFri, 13 May 2016 07:14:44 -0400 If you decide to sponsor this package, please upload the source only so that buildd logs are available for all archs. I will push a release tag to the git repository after the package has been uploaded. Regards, Peter
Bug#823895: RFS: lsm/1.0.4-1
On 13-05-2016 11:46, Adam Borowski wrote: >> On 10-05-2016 02:43, Lucas Castro wrote >>> I am looking for a sponsor for my package "lsm" >>> >>> * Package name: lsm >>> Upstream Author : Mika Ilmaranta>>> * URL : http://lsm.foobar.fi/ >>> >>> dget -x >>> https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.dsc > From a superficial review: > > 1. Please delete (or fill out) debian/README.source removed. > 2. The manpage seems mangled: > >While simple to configure, provides easy way reconfigure routes, > calling notifyscript > >lsmVery configurable, but doesn't support domain names yet. Thanks, fixed. > > 3. Typo: exectuble. if you mean man page typo, fixed. > > Meow! Done. signature.asc Description: OpenPGP digital signature
Bug#824232: RFS: emacs-buttercup/1.5-2 -- behaviour-driven testing for Emacs Lisp packages
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for a new version of emacs-buttercup. Buttercup is an alternative framework for writing test suites for Emacs Lisp addons that various addons are adopting in preference or in addition to the ERT testing framework that comes with Emacs. * Package name: emacs-buttercup Version : 1.5-2 Upstream Author : Jorgen Schaefer* URL : https://github.com/jorgenschaefer/emacs-buttercup/ * License : GPL-3+ Section : lisp Changes since the last upload: * Add patch to fix regexp so that /usr/bin/buttercup ignores tests in hidden directories in the root of a source tree. In particular, this ignores phantom tests found in the .pc/ directory. * Bump standards version to 3.9.8 (no changes required). Download with dget: dget -x http://mentors.debian.net/debian/pool/main/e/emacs-buttercup/emacs-buttercup_1.5-2.dsc Or build it with gbp: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-emacsen/pkg/emacs-buttercup.git cd emacs-buttercup gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#824231: RFS: dh-elpa/0.0.21 -- Debian helper tools for packaging emacs lisp extensions
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for an update to dh-elpa. It fixes two bugs introduced in the previous upload. * Package name: dh-elpa Version : 0.0.21 Upstream Author : David Bremner & Sean Whitton * URL : http://pkg-emacsen.alioth.debian.org/ * License : GPL-3+ Section : lisp Changes since the last upload: * Actually exclude .pc/ and debian/ directories from ERT tests. * Fix Vcs-Git: URI. Download with dget: dget -x http://mentors.debian.net/debian/pool/main/d/dh-elpa/dh-elpa_0.0.21.dsc Or build it with gbp: git clone https://anonscm.debian.org/git/pkg-emacsen/pkg/dh-elpa.git cd dh-elpa gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]
Hi, >Isn't I'm supposed to raise the version number? or is "+nmu1" enough? I'm not sure, but in fact dch --nmu is not raising it, so I guess 1.8.2+nmu1 is fine, so the maintainer can still bump and release an NMU acknowledge called 1.8.3 >It part of the fix, but not needed to fix #818540 (as I understand). not a problem >No file attached here? You talking about this file correct? >https://patches.ubuntu.com/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.2ubuntu1.patch yes >I did as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540#39 >suggested, do you disagree with that solution? Is the original solution >preferred? it is fine, I just want to know your opinion. >Just pushed to mentors. seems still not working completely... this is what I get on a clean pbuilder environment ERROR: failed to retrieve status information from google : W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1) W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 3B068FB4789ABE4AEFA3BB491397BC53640DB551 uses weak digest algorithm (SHA1) the ubuntu version prints the warning but starts the download anyway. what do you think about? G. > Date: Fri, 13 May 2016 19:41:25 + > From: locutusofb...@debian.org > To: klausenb...@hotmail.com; ba...@debian.org; 824...@bugs.debian.org > Subject: Re: Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU] > > control: owner -1 ! > control: tags -1 moreinfo > > > Hi, some questions about versioning and changelog: > > 1) why 1.8.3+nmu1 and not 1.8.2+nmu1? > 2) why UNRELEASED? please set unstable > > "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug > #818540? > > the other stuff LGTM, I hope to sponsor it soon :) > > BTW did you see the ubuntu diff? > you might want to take some bits > > (attaching the debdiff between debian and ubuntu, I'm not talking about > fields like changelog entries > and maintainer field, more about the update script) > > thanks! > > G. > > > Il Venerdì 13 Maggio 2016 15:39, Kristian Klausen> ha scritto: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "pepperflashplugin-nonfree": > > * Package name : pepperflashplugin-nonfree > Version : 1.8.3+nmu1 > Upstream Author : Bart Martens > * URL : http://wiki.debian.org/PepperFlashPlayer > * License : GPL3 > Section : Browser plugin > > It builds those binary packages: > > pepperflashplugin-nonfree > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/pepperflashplugin-nonfree > > > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc > > > Changes since the last upload: > > pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium > > * Non-maintainer upload. > * Update Google public key. Closes: #823005. > * Remove 32 bit support. Closes: #816848. > * Don't treat `apt-get update` warnings as errors. Closes: #818540. > * Validate deb file with sha256sum. > > -- Kristian Klausen Fri, 13 May 2016 14:44:52 +0200 > > > Regards, > Kristian Klausen
Bug#824220: RFS: ws-butler/0.3+git.a998a23-1 [ITP] -- unobtrusively remove trailing whitespace in Emacs
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package ws-butler. This package provides ws-butler-mode and ws-butler-global-mode. Upon saving a file in Emacs, these modes delete trailing whitespace on lines of the buffer that have been edited. As compared with simply calling delete-trailing-whitespace in your before-save-hook, ws-butler has the advantage of not cluttering up version control commits with whitespace cleanup outside of the part of the file you have edited. I am packaging version 0.3+git.a998a23 because since version 0.3 upstream has refactored ws-butler's code quite significantly. This version is not unstable -- upstream just haven't tagged a release for a while. I intend to maintain this as part of the pkg-emacsen team. * Package name: ws-butler Version : 0.3+git.a998a23-1 Upstream Author : Le Wang * URL : https://github.com/lewang/ws-butler * License : GPL-3+ Section : lisp Download with dget: dget -x http://mentors.debian.net/debian/pool/main/w/ws-butler/ws-butler_0.3+git.a998a23-1.dsc Or build it with gbp: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-emacsen/pkg/ws-butler.git cd ws-butler gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#824218: RFS: ebib/2.5.4-1 [ITP] -- BibTeX database manager for Emacs
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package ebib. ebib is a useful editor for .bib files in Emacs. It integrates with RefTeX and LaTeX-mode to easily add bibliographic references to your documents. I intend to maintain this as part of the pkg-emacsen team. * Package name: ebib Version : 2.5.4-1 Upstream Author : Joost Kremers* URL : https://github.com/joostkremers/ebib * License : BSD-3-clause Section : lisp Download with dget: dget -x http://mentors.debian.net/debian/pool/main/e/ebib/ebib_2.5.4-1.dsc Or build it with gbp: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-emacsen/pkg/ebib.git cd ebib gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#824217: RFS: parsebib/1.0.5-1 [ITP] -- Emacs Lisp library for parsing .bib files
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package parsebib. I am packaging this library as a dependency of ebib, another ITP of mine. I intend to maintain it as part of the pkg-emacsen team. * Package name: parsebib Version : 1.0.5-1 Upstream Author : Joost Kremers* URL : https://github.com/joostkremers/parsebib * License : BSD-3-clause Section : lisp Download with dget: dget -x http://mentors.debian.net/debian/pool/main/p/parsebib/parsebib_1.0.5-1.dsc Or build it with gbp: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-emacsen/pkg/parsebib.git cd parsebib gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]
Hi again G :) > 1) why 1.8.3+nmu1 and not 1.8.2+nmu1? Isn't I'm supposed to raise the version number? or is "+nmu1" enough? > 2) why UNRELEASED? please set unstable I didn't noticed it. > "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug > #818540? It part of the fix, but not needed to fix #818540 (as I understand). > (attaching the debdiff between debian and ubuntu, I'm not talking about > fields like changelog entries No file attached here? You talking about this file correct? https://patches.ubuntu.com/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.2ubuntu1.patch I did as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540#39 suggested, do you disagree with that solution? Is the original solution preferred? Just pushed to mentors. - Kristian > Date: Fri, 13 May 2016 19:41:25 + > From: locutusofb...@debian.org > To: klausenb...@hotmail.com; ba...@debian.org; 824...@bugs.debian.org > Subject: Re: Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU] > > control: owner -1 ! > control: tags -1 moreinfo > > > Hi, some questions about versioning and changelog: > > 1) why 1.8.3+nmu1 and not 1.8.2+nmu1? > 2) why UNRELEASED? please set unstable > > "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug > #818540? > > the other stuff LGTM, I hope to sponsor it soon :) > > BTW did you see the ubuntu diff? > you might want to take some bits > > (attaching the debdiff between debian and ubuntu, I'm not talking about > fields like changelog entries > and maintainer field, more about the update script) > > thanks! > > G. > > > Il Venerdì 13 Maggio 2016 15:39, Kristian Klausen> ha scritto: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "pepperflashplugin-nonfree": > > * Package name : pepperflashplugin-nonfree > Version : 1.8.3+nmu1 > Upstream Author : Bart Martens > * URL : http://wiki.debian.org/PepperFlashPlayer > * License : GPL3 > Section : Browser plugin > > It builds those binary packages: > > pepperflashplugin-nonfree > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/pepperflashplugin-nonfree > > > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc > > > Changes since the last upload: > > pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium > > * Non-maintainer upload. > * Update Google public key. Closes: #823005. > * Remove 32 bit support. Closes: #816848. > * Don't treat `apt-get update` warnings as errors. Closes: #818540. > * Validate deb file with sha256sum. > > -- Kristian Klausen Fri, 13 May 2016 14:44:52 +0200 > > > Regards, > Kristian Klausen
Bug#824216: RFS: smex/3.0-1 [ITP] -- M-x interface with Ido-style fuzzy matching
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package smex. > Smex is a M-x enhancement for Emacs. Built on top of Ido, it provides > a convenient interface to your recently and most frequently used > commands. Smex is a very widely used Emacs addon that it would be nice to have in Debian. I intend to maintain it as part of the pkg-emacsen team. * Package name: smex Version : 3.0-1 Upstream Author : Cornelius Mika * URL : http://github.com/nonsequitur/smex/ * License : GPL-3+ Section : lisp Download with dget: dget -x http://mentors.debian.net/debian/pool/main/s/smex/smex_3.0-1.dsc Or build it with gbp: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-emacsen/pkg/smex.git cd smex gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#824209: marked as done (RFS: path.py/8.2.1+dfsg-1)
Your message dated Fri, 13 May 2016 19:44:06 + (UTC) with message-id <1811360997.3276704.1463168646682.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#824209: RFS: path.py/8.2.1+dfsg-1 has caused the Debian Bug report #824209, regarding RFS: path.py/8.2.1+dfsg-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.) -- 824209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824209 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 "path.py" * Package name: path.py Version : 8.2.1+dfsg-1 Upstream Author : Mikhail Gusarov * URL : https://github.com/jaraco/path.py * License : Expat Section : python It builds those binary packages: python-path - module wrapper for os.path for Python 2 python3-path - module wrapper for os.path for Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/path.py Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/path.py/path.py_8.2.1+dfsg-1.dsc Changes since the last upload: path.py (8.2.1+dfsg-1) unstable; urgency=medium [ Ondřej Nový ] * Fixed VCS URL (https) [ Julien Puydt ] * New upstream release. * Bump standards-version. Thanks, Snark on #debian-python --- End Message --- --- Begin Message --- Hi, sponsoring soon! G. Il Venerdì 13 Maggio 2016 20:33, Julien Puydtha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "path.py" * Package name: path.py Version : 8.2.1+dfsg-1 Upstream Author : Mikhail Gusarov * URL : https://github.com/jaraco/path.py * License : Expat Section : python It builds those binary packages: python-path - module wrapper for os.path for Python 2 python3-path - module wrapper for os.path for Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/path.py Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/path.py/path.py_8.2.1+dfsg-1.dsc Changes since the last upload: path.py (8.2.1+dfsg-1) unstable; urgency=medium [ Ondřej Nový ] * Fixed VCS URL (https) [ Julien Puydt ] * New upstream release. * Bump standards-version. Thanks, Snark on #debian-python--- End Message ---
Bug#824208: marked as done (RFS: node-jsesc/1.0.0-1)
Your message dated Fri, 13 May 2016 19:46:16 + (UTC) with message-id <858957668.3193131.1463168776372.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#824208: RFS: node-jsesc/1.0.0-1 has caused the Debian Bug report #824208, regarding RFS: node-jsesc/1.0.0-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.) -- 824208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824208 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 "node-jsesc" * Package name: node-jsesc Version : 1.0.0-1 Upstream Author : Mathias Bynens * URL : http://mths.be/jsesc * License : Expat Section : web It builds those binary packages: node-jsesc - Escape JavaScript strings, with short output (Node.js module) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-jsesc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-jsesc/node-jsesc_1.0.0-1.dsc Changes since the last upload: node-jsesc (1.0.0-1) unstable; urgency=medium * New upstream version. * Bump standards-version up. * Use https for Vcs-* fields. Thanks, Snark on #debian-js --- End Message --- --- Begin Message --- Hi, done! g. Il Venerdì 13 Maggio 2016 20:33, Julien Puydtha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "node-jsesc" * Package name: node-jsesc Version : 1.0.0-1 Upstream Author : Mathias Bynens * URL : http://mths.be/jsesc * License : Expat Section : web It builds those binary packages: node-jsesc - Escape JavaScript strings, with short output (Node.js module) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-jsesc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-jsesc/node-jsesc_1.0.0-1.dsc Changes since the last upload: node-jsesc (1.0.0-1) unstable; urgency=medium * New upstream version. * Bump standards-version up. * Use https for Vcs-* fields. Thanks, Snark on #debian-js--- End Message ---
Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]
control: owner -1 ! control: tags -1 moreinfo Hi, some questions about versioning and changelog: 1) why 1.8.3+nmu1 and not 1.8.2+nmu1? 2) why UNRELEASED? please set unstable "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug #818540? the other stuff LGTM, I hope to sponsor it soon :) BTW did you see the ubuntu diff? you might want to take some bits (attaching the debdiff between debian and ubuntu, I'm not talking about fields like changelog entries and maintainer field, more about the update script) thanks! G. Il Venerdì 13 Maggio 2016 15:39, Kristian Klausenha scritto: Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "pepperflashplugin-nonfree": * Package name: pepperflashplugin-nonfree Version : 1.8.3+nmu1 Upstream Author : Bart Martens * URL : http://wiki.debian.org/PepperFlashPlayer * License : GPL3 Section : Browser plugin It builds those binary packages: pepperflashplugin-nonfree To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pepperflashplugin-nonfree Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc Changes since the last upload: pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium * Non-maintainer upload. * Update Google public key. Closes: #823005. * Remove 32 bit support. Closes: #816848. * Don't treat `apt-get update` warnings as errors. Closes: #818540. * Validate deb file with sha256sum. -- Kristian Klausen Fri, 13 May 2016 14:44:52 +0200 Regards, Kristian Klausen
Bug#824209: RFS: path.py/8.2.1+dfsg-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "path.py" * Package name: path.py Version : 8.2.1+dfsg-1 Upstream Author : Mikhail Gusarov * URL : https://github.com/jaraco/path.py * License : Expat Section : python It builds those binary packages: python-path - module wrapper for os.path for Python 2 python3-path - module wrapper for os.path for Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/path.py Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/path.py/path.py_8.2.1+dfsg-1.dsc Changes since the last upload: path.py (8.2.1+dfsg-1) unstable; urgency=medium [ Ondřej Nový ] * Fixed VCS URL (https) [ Julien Puydt ] * New upstream release. * Bump standards-version. Thanks, Snark on #debian-python
Bug#824208: RFS: node-jsesc/1.0.0-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "node-jsesc" * Package name: node-jsesc Version : 1.0.0-1 Upstream Author : Mathias Bynens * URL : http://mths.be/jsesc * License : Expat Section : web It builds those binary packages: node-jsesc - Escape JavaScript strings, with short output (Node.js module) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-jsesc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-jsesc/node-jsesc_1.0.0-1.dsc Changes since the last upload: node-jsesc (1.0.0-1) unstable; urgency=medium * New upstream version. * Bump standards-version up. * Use https for Vcs-* fields. Thanks, Snark on #debian-js
Bug#823668: marked as done (RFS: twofish/0.3-5)
Your message dated Fri, 13 May 2016 17:16:04 +0200 with message-id <20160513151604.ga1...@angband.pl> and subject line uploaded has caused the Debian Bug report #823668, regarding RFS: twofish/0.3-5 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.) -- 823668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823668 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 of my package "twofish": Package name: twofish Version : 0.3-5 Upstream Author : Niels FergusonURL : extinct License : liberal, demanding only copyright message Section : libdevel It builds two binary packages: libtwofish-dev - Niels Ferguson's Twofish cryptographic algorithm library libtwofish0- Niels Ferguson's Twofish cryptographic library -- runtime package Further information is available at https://mentors.debian.net/package/twofish The packaging is accessible in a standard manner: dget -x https://mentors.debian.net/debian/pool/main/t/twofish/twofish_0.3-5.dsc Changes since last upload are: * Step Standards-Version to 3.9.8, no changes. * Use debhelper in compatibility level 9. * debian/control: Use HTTPS transport for Vcs-Browser. * debian/copyright: Update my contribution including 2016. Rename license of packaging files, avoiding a name in duplicate. * debian/libtwofish0.lintian-overrides: Delete unused entry. * debian/libtwofish0.triggers: New file. * debian/libtwofish-dev.lintian-overrides: Delete unused entry. * debian/rules: Activate immediate bindings in so-library. Regards, Mats Erik Andersson --- End Message --- --- Begin Message --- It's in. One nitpick: the .triggers file contains "activate-noawait ldconfig" twice, coming both from you and from debhelper. You can delete libtwofish0.triggers from your packaging, it's redundant. This doesn't cause any harm, so I uploaded as-is, but please remove this in your VCS. Meow! -- A tit a day keeps the vet away.--- End Message ---
Bug#823895: RFS: lsm/1.0.4-1
> On 10-05-2016 02:43, Lucas Castro wrote > > I am looking for a sponsor for my package "lsm" > > > > * Package name: lsm > > Upstream Author : Mika Ilmaranta> > * URL : http://lsm.foobar.fi/ > > > > dget -x > > https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.dsc >From a superficial review: 1. Please delete (or fill out) debian/README.source 2. The manpage seems mangled: While simple to configure, provides easy way reconfigure routes, calling notifyscript lsmVery configurable, but doesn't support domain names yet. 3. Typo: exectuble. Meow! -- A tit a day keeps the vet away.
Re: Bug#800406: RFS sayonara/0.8.2
Hi Lucio, On 05/11/2016 12:28 PM, Gianfranco Costamagna wrote: >> >So the next step will be to join the multimedia-team? > > please join it now, and put VCS fields under your package. > (and ask me to create the repository if you want one) > > I see some packages under pkg-multimedia umbrella have no VCS repository, so > I guess > you can avoid that, because you seem to already be upstream Sorry - I was a bit busy this week. If Gianfranco says we are mostly done, then it is probably time to join the pkg-multimedia team! Please follow this page to join: https://wiki.debian.org/DebianMultimedia/Join Once I see saynora pushed to the alioth git repository, I will build, install and have a play. If all looks good, it is probably time to update the RFS bug to let Gianfranco know that we think it is ready for sponsorship. Regards, Ross signature.asc Description: OpenPGP digital signature
Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "pepperflashplugin-nonfree": * Package name : pepperflashplugin-nonfree Version : 1.8.3+nmu1 Upstream Author : Bart Martens* URL : http://wiki.debian.org/PepperFlashPlayer * License : GPL3 Section : Browser plugin It builds those binary packages: pepperflashplugin-nonfree To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pepperflashplugin-nonfree Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc Changes since the last upload: pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium * Non-maintainer upload. * Update Google public key. Closes: #823005. * Remove 32 bit support. Closes: #816848. * Don't treat `apt-get update` warnings as errors. Closes: #818540. * Validate deb file with sha256sum. -- Kristian Klausen Fri, 13 May 2016 14:44:52 +0200 Regards, Kristian Klausen
Re: Appropriate transition from iep to pyzo
Hi Ghislain, simply let the source package of pyzo build a transitional dummy package with the name iep. See https://wiki.debian.org/Renaming_a_Package Best, Tobias On 05/13/2016 10:52 AM, Ghislain Vaillant wrote: > Dear all, > > I am the package maintainer of iep and pyzo, two Python IDEs targeted > the scientific audience. Pyzo is the official successor of iep, meaning > the latter won't be maintained upstream anymore in favour of the > former. In terms of version numbers, the upstream developers started > Pyzo (now at 4.1) where iep stopped (3.7). > > I wanted to get your opinion on how to best handle the transition from > iep to pyzo. I would like everyone currently using iep to automatically > transit to pyzo via a package update, so that I can safely ask iep to > be removed from the archive. > > Does it sound sensible? feasible? Any advice on how to proceed? > > Many thanks, > Ghislain >
Re: Appropriate transition from iep to pyzo
Hello Ghislain, >I wanted to get your opinion on how to best handle the transition > from iep to pyzo. I would like everyone currently using iep to > automatically transit to pyzo via a package update, so that I can > safely ask iep to be removed from the archive.> I'd suggest method 2: https://wiki.debian.org/Renaming_a_Package hope that helps, Gert
Appropriate transition from iep to pyzo
Dear all, I am the package maintainer of iep and pyzo, two Python IDEs targeted the scientific audience. Pyzo is the official successor of iep, meaning the latter won't be maintained upstream anymore in favour of the former. In terms of version numbers, the upstream developers started Pyzo (now at 4.1) where iep stopped (3.7). I wanted to get your opinion on how to best handle the transition from iep to pyzo. I would like everyone currently using iep to automatically transit to pyzo via a package update, so that I can safely ask iep to be removed from the archive. Does it sound sensible? feasible? Any advice on how to proceed? Many thanks, Ghislain
Bug#823187: RFS: icdiff/1.7.3-1
Hi Paul, thanks for your quick reply. [...] > Interesting. Personally if I were upstream I'd drop the curl method and > go with pip but I understand it is a simple and thus useful hack. So would I, but I respect upstream's wishes and there was also a user who preferred the simple, stand-alone script solution. > How about this? > > Rename icdiff to icdiff.py and make it a module. > > Put a bin/icdiff in the repo that just imports and runs the icdiff > module. It can't be icdiff since people who run the same install > instructions should get a file not found error instead of confusing > import failure when trying to run the script. That would be an option indeed, except that I think it will not work if one just clones the github repo without installing (as the module is not in a searched path yet). > Add some code to icdiff.py so it can be run on the cmdline too. AFAICS this would be possible when merging https://github.com/jeffkaufman/icdiff/pull/75 -- which I would advise. > Update the web page curl install info to point at icdiff.py Upstream explicitly says he wants to have icdiff without a .py suffix. Of course it's trivial to have curl write it into a suffixless file, but if you do that you can't use the downloaded file as a module. > Have setup.py install bin/icdiff as a script and icdiff.py as a module. This is pretty much how it's done in PR #75, except bin/icdiff is created by setuptools via the entrypoint approach and not included in the original repo. I will think about it a bit more and discuss these options with upstream. Maybe he also just makes a call in favour or against the module functionality, or someone comes up with a new solution. >> New upload is here: >> https://mentors.debian.net/debian/pool/main/i/icdiff/icdiff_1.8.1-1.dsc > > I'll take a look on the weekend. Great, thanks! -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Bug#824161: marked as done (RFS: pyfr/1.4.0-2)
Your message dated Fri, 13 May 2016 07:42:37 + (UTC) with message-id <1255851459.2480125.1463125357816.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#824161: RFS: pyfr/1.4.0-2 has caused the Debian Bug report #824161, regarding RFS: pyfr/1.4.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.) -- 824161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824161 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 "pyfr" * Package name: pyfr Version : 1.4.0-2 Upstream Author : Imperial College London * URL : http://www.pyfr.org * License : BSD Section : science It builds those binary packages: pyfr - flux reconstruction in Python pyfr-doc - documentation for PyFR To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pyfr Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pyfr/pyfr_1.4.0-2.dsc Successful build log on debomatic: http://debomatic-amd64.debian.net/distribution#unstable/pyfr/1.4.0-2/buildlog Changes since the last upload: * Install pyfr module to private location. Thanks to Piotr Ozarowski * Drop unnecessary build dependencies. * Drop install dependency on mpi-default-bin. Regards, Ghislain Vaillant --- End Message --- --- Begin Message --- hi, done! g. Il Venerdì 13 Maggio 2016 8:57, Ghislain Vaillantha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pyfr" * Package name: pyfr Version : 1.4.0-2 Upstream Author : Imperial College London * URL : http://www.pyfr.org * License : BSD Section : science It builds those binary packages: pyfr - flux reconstruction in Python pyfr-doc - documentation for PyFR To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pyfr Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pyfr/pyfr_1.4.0-2.dsc Successful build log on debomatic: http://debomatic-amd64.debian.net/distribution#unstable/pyfr/1.4.0-2/buildlog Changes since the last upload: * Install pyfr module to private location. Thanks to Piotr Ozarowski * Drop unnecessary build dependencies. * Drop install dependency on mpi-default-bin. Regards, Ghislain Vaillant--- End Message ---
Bug#824161: RFS: pyfr/1.4.0-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pyfr" * Package name: pyfr Version : 1.4.0-2 Upstream Author : Imperial College London * URL : http://www.pyfr.org * License : BSD Section : science It builds those binary packages: pyfr - flux reconstruction in Python pyfr-doc - documentation for PyFR To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pyfr Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pyfr/pyfr_1.4.0-2.dsc Successful build log on debomatic: http://debomatic-amd64.debian.net/distribution#unstable/pyfr/1.4.0-2/buildlog Changes since the last upload: * Install pyfr module to private location. Thanks to Piotr Ozarowski * Drop unnecessary build dependencies. * Drop install dependency on mpi-default-bin. Regards, Ghislain Vaillant