Bug#825390: RFS: maldetect/1.5-1 [ITP] -- Linux Malware Detection
On Wed, Jun 1, 2016 at 11:36 AM, Sean Whitton wrote: > - you might consider using "GNU/Linux" instead of "Linux" in the package > description, since Debian identifies itself as a "GNU/Linux" > distribution Debian no longer identifies itself as "Debian GNU/Linux" but just "Debian", due to the fact that we support kFreeBSD and Hurd. The Linux ports are of course still known as "Debian GNU/Linux" so this change sounds good if the tool isn't portable to other operating systems. -- bye, pabs https://wiki.debian.org/PaulWise
Bug#825978: RFS: libretro-bsnes-mercury [ITP]
Package: sponsorship-requests Severity: wishlist Hey dear mentors! I'm looking for a sponsor for my package "libretro-bsnes-mercury" This is the libretro port of bsnes-mercury, a SNES / Super Nintendo emulator. bsnes-mercury is a fork of higan, aiming to restore some useful features that have been removed, as well as improving performance a bit. Maximum accuracy is still uncompromisable; anything that affects accuracy is optional and off by default. * Package name : libretro-bsnes-mercury Version : 094+git20160126 Upstream Author : byuu / Alcaro (mercury fork) * URL :https://github.com/libretro/bsnes-mercury * License : GPL-3+ Programming Lang : C++ Description : port of bsnes-mercury to libretro API It builds those binary packages: ITP: libretro-bsnes-mercury -- bsnes-mercury libretro port To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libretro-bsnes-mercury More information about RetroArch and the libretro API can be obtained from http://www.libretro.com/index.php/api/ -- sergio-br2
Bug#825532: RFS: shadowsocks-libev/2.4.6+20160526+ds-1 [ITP]
control: tags -1 moreinfo control: owner -1 ! hi, 1) I: shadowsocks-libev: extended-description-is-probably-too-short 2)W: shadowsocks-libev source: debian-watch-file-should-mangle-version line 7 3) Replaces: shadowsocks (<< 1.5.3-2) Breaks: shadowsocks (<< 1.5.3-2) Why? 4)libipset/ <-- debian has libipset-dev, please make sure that one is used during build (if it is the correct lib of course) 5) sed -i "/dependency_libs/ s/'.*'/''/" `find . -name '*.la'` what? 6) debian/config.json what? let me know if you can address the above and I'll have another look! cheers, G. Il Martedì 31 Maggio 2016 13:45, Roger Shimizu ha scritto: Control: retitle -1 RFS: shadowsocks-libev/2.4.6+20160531+ds-1 [ITP] Since there're a few improvements of upstream: - Merged one of my patch in debian/patches/ - Made upstream Changelog out of debian/ folder, so as one lintian info is gone. I update the version to latest commit in upstream git, and upload to mentors. Now my packaging stuff can be found on pkg2 branch of https://github.com/rogers0/shadowsocks-libev Thank you and looking forward to sponsorship! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Bug#825965: marked as done (RFS: gtk3-nocsd/3-1 [RC])
Your message dated Tue, 31 May 2016 20:12:47 + (UTC) with message-id <1643989773.4264165.1464725567210.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#825965: RFS: gtk3-nocsd/3-1 [RC] has caused the Debian Bug report #825965, regarding RFS: gtk3-nocsd/3-1 [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.) -- 825965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825965 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 "gtk3-nocsd": * Package name: gtk3-nocsd Version : 3-1 Upstream Author : Hong Jen Yee (PCMan) * URL : https://github.com/PCMan/gtk3-nocsd * License : LGPL-2.1+ Section : x11 It builds those binary packages: gtk3-nocsd - Disable Gtk+ 3 client side decorations (CSD) libgtk3-nocsd0 - Library to disable Gtk+ 3 client side decorations (CSD) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gtk3-nocsd Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gtk3-nocsd/gtk3-nocsd_3-1.dsc Git packaging is also available on collab-maint: https://anonscm.debian.org/git/collab-maint/gtk3-nocsd.git Changes since the last upload: * Imported new upstream version 3. - Add bash completion support. (Closes: #824615) - Also override GtkDialog's GtkBuildable->add_child. (Closes: #824614) - Don't use compositor trick in Gtk+3 3.16.1 or higher. (Closes: #824616) - Don't remove menu titlebar decoration. (Closes: #824758) - Cosmetic improvements to the headerbar. (Closes: #824617) * debian/libgtk3-noscd0.symbols: add symbols from new upstream version. * README.Debian: add instructions for the Multi-Arch case. * Ship /etc/X11/Xsession.d/01gtk3-nocsd by default. (Closes: #824620) * debian/control: Bump Standards-Version to 3.9.8. (No changes.) * Xsession scripts: properly handle package removal without purge. * Process README.md with markdown to create nice HTML file. Regards, Christian Seiler signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- hi, done! g. Il Martedì 31 Maggio 2016 21:51, Christian Seiler ha scritto: Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "gtk3-nocsd": * Package name: gtk3-nocsd Version : 3-1 Upstream Author : Hong Jen Yee (PCMan) * URL : https://github.com/PCMan/gtk3-nocsd * License : LGPL-2.1+ Section : x11 It builds those binary packages: gtk3-nocsd - Disable Gtk+ 3 client side decorations (CSD) libgtk3-nocsd0 - Library to disable Gtk+ 3 client side decorations (CSD) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gtk3-nocsd Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gtk3-nocsd/gtk3-nocsd_3-1.dsc Git packaging is also available on collab-maint: https://anonscm.debian.org/git/collab-maint/gtk3-nocsd.git Changes since the last upload: * Imported new upstream version 3. - Add bash completion support. (Closes: #824615) - Also override GtkDialog's GtkBuildable->add_child. (Closes: #824614) - Don't use compositor trick in Gtk+3 3.16.1 or higher. (Closes: #824616) - Don't remove menu titlebar decoration. (Closes: #824758) - Cosmetic improvements to the headerbar. (Closes: #824617) * debian/libgtk3-noscd0.symbols: add symbols from new upstream version. * README.Debian: add instructions for the Multi-Arch case. * Ship /etc/X11/Xsession.d/01gtk3-nocsd by default. (Closes: #824620) * debian/control: Bump Standards-Version to 3.9.8. (No changes.) * Xsession scripts: properly handle package removal without purge. * Process README.md with markdown to create nice HTML file. Regards, Christian Seiler--- End Message ---
Bug#825531: RFS: libcork/0.15.0+ds-1 [ITP]
control: owner -1 ! control: tags -1 moreinfo Hi, I did a quick look and the package looks great! (I grabbed it from mentors) however I have some things I would like to discuss / see fixed: 1) W: libcork source: debian-watch-file-should-mangle-version line 7 2) lrwxrwxrwx root/root 0 2016-05-31 21:37 ./usr/lib/libcork.so.15 -> libcork.so.16.0.1 what??? some other stuff I would appreciate to see fixed: 3) consider a split of the html stuff into a doc package, this way packages depending on the -dev will grab a package with a lower size 4)stop shipping the .a library (not requested BTW, I just avoid them when possible) 5) multiarch. https://wiki.debian.org/Multiarch/Implementation 6) is testsuite run or not? 7) sed -i s%https://cdn.mathjax.org/mathjax/latest/MathJax.js%file:///usr/share/javascript/mathjax/MathJax.js% build/docs/old/html/*.html this seems hacky, are you sure there isn't a better way to handle this? (one day the path for the external might change, and the sed will become useless) let me know, Gianfranco
Bug#825965: RFS: gtk3-nocsd/3-1 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "gtk3-nocsd": * Package name: gtk3-nocsd Version : 3-1 Upstream Author : Hong Jen Yee (PCMan) * URL : https://github.com/PCMan/gtk3-nocsd * License : LGPL-2.1+ Section : x11 It builds those binary packages: gtk3-nocsd - Disable Gtk+ 3 client side decorations (CSD) libgtk3-nocsd0 - Library to disable Gtk+ 3 client side decorations (CSD) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gtk3-nocsd Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gtk3-nocsd/gtk3-nocsd_3-1.dsc Git packaging is also available on collab-maint: https://anonscm.debian.org/git/collab-maint/gtk3-nocsd.git Changes since the last upload: * Imported new upstream version 3. - Add bash completion support. (Closes: #824615) - Also override GtkDialog's GtkBuildable->add_child. (Closes: #824614) - Don't use compositor trick in Gtk+3 3.16.1 or higher. (Closes: #824616) - Don't remove menu titlebar decoration. (Closes: #824758) - Cosmetic improvements to the headerbar. (Closes: #824617) * debian/libgtk3-noscd0.symbols: add symbols from new upstream version. * README.Debian: add instructions for the Multi-Arch case. * Ship /etc/X11/Xsession.d/01gtk3-nocsd by default. (Closes: #824620) * debian/control: Bump Standards-Version to 3.9.8. (No changes.) * Xsession scripts: properly handle package removal without purge. * Process README.md with markdown to create nice HTML file. Regards, Christian Seiler signature.asc Description: OpenPGP digital signature
Bug#825236: RFS: openfst/1.5.3-1 -- weighted finite-state transducers library
* Giulio Paci , 2016-05-31, 16:18: I implemented a workaround that sets different limits for the build phase and the check phase. I like the idea. :-) 1eca96b4700b uploaded. -- Jakub Wilk
Bug#825943: marked as done (RFS: node-jsesc/2.1.0-1)
Your message dated Tue, 31 May 2016 16:50:02 + with message-id <20160531165000.gg21...@chase.mapreri.org> and subject line Re: Bug#825943: RFS: node-jsesc/2.1.0-1 has caused the Debian Bug report #825943, regarding RFS: node-jsesc/2.1.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.) -- 825943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825943 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 : 2.1.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_2.1.0-1.dsc It is packaged within the debian-js team: Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-jsesc.git Vcs-Browser: https://anonscm.debian.org/git/pkg-javascript/node-jsesc.git Changes since the last upload: node-jsesc (2.1.0-1) unstable; urgency=medium * New upstream release. -- Julien Puydt Tue, 31 May 2016 18:12:37 +0200 Thanks, Snark on #debian-js --- End Message --- --- Begin Message --- done. On Tue, May 31, 2016 at 06:21:41PM +0200, Julien Puydt wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "node-jsesc" > > * Package name: node-jsesc >Version : 2.1.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_2.1.0-1.dsc > > It is packaged within the debian-js team: > Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-jsesc.git > Vcs-Browser: https://anonscm.debian.org/git/pkg-javascript/node-jsesc.git > > Changes since the last upload: > node-jsesc (2.1.0-1) unstable; urgency=medium > > * New upstream release. > > -- Julien Puydt Tue, 31 May 2016 18:12:37 +0200 > > > Thanks, > > Snark on #debian-js > -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message ---
Bug#825943: RFS: node-jsesc/2.1.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 : 2.1.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_2.1.0-1.dsc It is packaged within the debian-js team: Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-jsesc.git Vcs-Browser: https://anonscm.debian.org/git/pkg-javascript/node-jsesc.git Changes since the last upload: node-jsesc (2.1.0-1) unstable; urgency=medium * New upstream release. -- Julien Puydt Tue, 31 May 2016 18:12:37 +0200 Thanks, Snark on #debian-js
Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]
Hi, python-skimage should be RC free now (if no other RC bugs are opened of course :) ) let me know when you have updates, G.
Re: dh_install globbing
> >I upgraded dh-exec from jessie to sid, and it started to work. > > This is probably #801516. > > Anyway, if replaced "${RUNIT}" with "runit-*" in the *.install file, you > wouldn't need dh-exec at all. In some cases I need renaming feature, but thank you for advice. -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Keep-In-CC: yes X-Web-Site: sinsekvu.github.io
Bug#825236: RFS: openfst/1.5.3-1 -- weighted finite-state transducers library
On 31/05/2016 11:52, Jakub Wilk wrote: > * Giulio Paci , 2016-05-31, 09:33: >> I just checked the building status of openfst and noticed failures on arm >> architectures and on kfreebsd-amd64. >> >> On arm it seems to me that a timeout occurred, > > One suspicious thing I found in armhf build log is: > > /usr/bin/make -C . -j4 -k distclean > > but this machine has only 4GB of RAM. So our parallelism limits don't seem to > be enforced. Indeed I was wondering how much memory was available on that build machine. :-) > This line > > ifneq "$(wildcard /build/buildd-*/)" "" > > was supposed to detect if the package is being built on a buildd, but buildds > do longer use build directories like this. I don't think there's any reliable > and future-proof > way to detect this, so I'd suggest to drop this ifneq (i.e., start limiting > parallelism everywhere). I was thinking about removing this line in any case, as the limit is useful everywhere. >> on kfreebsd-amd64 it seems a compiler failure. > > I suspect that cc1plus was killed by OOM killer, for the same reason as above. Probably yes. The limit we set (~2GB) is not enough when we have to deal with 64bit build machines building the test suite with optimization flags turned on. So I implemented a workaround that sets different limits for the build phase and the check phase. Can you review my changes and eventually upload them? Bests, Giulio
Re: dh_install globbing
* Dmitry Bogatov , 2016-05-31, 14:15: I can't reproduce it here: $ grep -B1 html debian/*.install #!/usr/bin/dh-exec ${RUNIT}/doc/*[a-z].html /usr/share/doc/runit/html $ dpkg-buildpackage && dpkg -c ../runit_2.1.2-4_amd64.deb | grep /html/ ... I upgraded dh-exec from jessie to sid, and it started to work. This is probably #801516. Anyway, if replaced "${RUNIT}" with "runit-*" in the *.install file, you wouldn't need dh-exec at all. -- Jakub Wilk
Re: When to use "Replaces"?
On Tue, May 31, 2016 at 05:13:14PM +1000, Scott Leggett wrote: > On 2016-05-30.21:22, gregor herrmann wrote: > > On Mon, 30 May 2016 20:25:56 +0200, Adam Borowski wrote: > > > > > > c) Something else ...? > > > As both unclutters provide generally the same functionality, you may also > > > use the "alternatives" method. > > > > My impression is that the "new" version has different command line > > options. So calls to unclutter with the old options in > > .xsession/.xinit would break if /usr/bin/unclutter points to the new > > implementation via alternatives. > > > > I think I'd go for renaming here. > > Using the alternatives system is an interesting idea. Yes, the "new" > version is *not* a drop-in replacement - while the functionality is the > same, accepted arguments are not totally identical. However the > description and example given in the policy manual of different "vi" > clones seems to match the "unclutter" situation quite well. I can't seem to find a relevant definition in the Policy, so here's my common-sense reasoning: is the primary use mode compatible? That is, will the usual mode of invocation of one alternative work with the other? For example a vast majority of invocations of "editor" is just "editor $FILENAME"; comparing command-line options of jstar and vim the only one that seems to be common to both is +$LINENUM -- and even that is not officially mandated anywhere. It's obvious arguments will almost never be totally identical -- different implementations have different features and different needs. That's ok and expected. I'd say such programs are unfit to be alternatives to each other only if the usual, basic functionality needs different invocations. > Am I correct in understanding that using alternatives requires > co-operation between the two packages, "unclutter" and > "unclutter-fixes"? If that's the case, I'll approach the "unclutter" > maintainer, and if they disagree on using alternatives, will just rename > my package. Yes, all packages in an alternatives set must cooperate. Meow! -- An imaginary friend squared is a real enemy.
Bug#825904: marked as done (RFS: python-model-mommy/1.2.6-1)
Your message dated Tue, 31 May 2016 12:22:19 + (UTC) with message-id <1586048852.3737668.1464697339424.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#825904: RFS: python-model-mommy/1.2.6-1 has caused the Debian Bug report #825904, regarding RFS: python-model-mommy/1.2.6-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.) -- 825904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825904 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 package "python-model-mommy" * Package name: python-model-mommy Version : 1.2.6-1 Upstream Author : vandersonmota * URL : http://github.com/vandersonmota/model_mommy * License : Apache-2.0 Section : python It builds those binary packages: python-taskw - Python bindings for your taskwarrior database python3-taskw - Python bindings for your taskwarrior database (Python 3 version) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-model-mommy Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-model-mommy/python-model-mommy_1.2.6-1.dsc Changes since the last upload: * Team upload. [ Edward Betts ] * New upstream release. (Closes: #745093, #755657, #814781) * Build Python 3 package. * Fix lintian warning: dep5-copyright-license-name-not-unique * Update Standards-Version to 3.9.8 (no changes) * Update to debhelper 9 [ Ondřej Nový ] * Fixed VCS URL (https) --- End Message --- --- Begin Message --- Hi, I sponsored the one on mentors, with an added newline before team upload. copied the debian directory on git, git tag sign and upload on deferred/2. please git pull and let me know if you want me to cancel it. thanks for the nice contribution to Debian! g. Il Martedì 31 Maggio 2016 13:36, Edward Betts ha scritto: Thanks for the feedback. The build is picking up the python-six and django dependencies. Package: python-model-mommy Depends: python-django, python-six, python:any (<< 2.8), python:any (>= 2.7.5-5~) Package: python3-model-mommy Depends: python3-django, python3-six, python3:any (>= 3.3.2-2~) I don't think python-six is a Build-Dependency because the code isn't run during build process. The library has a test suite, but it isn't included in the pypi tarball. I've filed a pull request asking upstream to include it. https://github.com/vandersonmota/model_mommy/pull/277 If the test suite was run during the build then python-six and django would be build dependencies. I've added "Team upload" to the changelog. I'm going to rebuild the package and upload a fresh copy to mentors. -- Edward.--- End Message ---
Bug#821151: RFS: comitup/0.1-1 [ITP]
control: owner -1 ! control: tags -1 moreinfo Hi, I can sponsor the package, lets see what needs fixing/answering: setup.py/install_requires is your friend, please use it, and drop the hardcoded runtime-dependencies using python:Depends (and check if everything is good) build and run: $ comitup Traceback (most recent call last): File "/usr/sbin/comitup", line 9, in load_entry_point('comitup==0.1', 'console_scripts', 'comitup-cmd')() File "/usr/share/comitup/comitup/comitup.py", line 64, in main log = deflog() File "/usr/share/comitup/comitup/comitup.py", line 31, in deflog backupCount=8, File "/usr/lib/python2.7/logging/handlers.py", line 171, in __init__ BaseRotatingHandler.__init__(self, filename, 'a', encoding, delay) File "/usr/lib/python2.7/logging/handlers.py", line 64, in __init__ logging.FileHandler.__init__(self, filename, mode, encoding, delay) File "/usr/lib/python2.7/logging/__init__.py", line 913, in __init__ StreamHandler.__init__(self, self._open()) File "/usr/lib/python2.7/logging/__init__.py", line 945, in _open stream = codecs.open(self.baseFilename, self.mode, self.encoding) File "/usr/lib/python2.7/codecs.py", line 896, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/log/comitup.log' $ sudo comitup Traceback (most recent call last): File "/usr/sbin/comitup", line 9, in load_entry_point('comitup==0.1', 'console_scripts', 'comitup-cmd')() File "/usr/share/comitup/comitup/comitup.py", line 73, in main [webmgr.state_callback], File "/usr/share/comitup/comitup/statemgr.py", line 80, in init_state_mgr states.set_state('CONNECTING', states.candidate_connections()) File "/usr/share/comitup/comitup/states.py", line 262, in candidate_connections return nm.get_candidate_connections() File "/usr/share/comitup/comitup/nm.py", line 186, in get_candidate_connections and settings['802-11-wireless']['mode'] == 'infrastructure': KeyError: 'mode' (same applies looking at journalctl -u comitup) std-version is 3.9.8 the description should be extended a little bit why no python3? apt-get install -t experimental check-all-the-things check-all-the-things pep8 --ignore W191 . grep -riE 'fixme|todo|hack|xxx' . Please add some upstream metadata: https://wiki.debian.org/UpstreamMetadata cheers, G. Il Sabato 16 Aprile 2016 4:39, David Steele ha scritto: Package: sponsorship-requests Severity: wishlist thanks Dear mentors, I am looking for a sponsor for my new package "comitup" Package name: comitup Version: 0.1 Upstream Author: David Steele URL: https://github.com/davesteele/comitup License: GPL2+ Section: net It builds a single binary package: comitup - bootstrap Wifi using Wifi To access further information about this package, please visit the following URL: http://mentors.debian.net/package/comitup Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/comitup/comitup_0.1-1.dsc or, using git: git clone https://github.com/davesteele/comitup.git -b debian ./comitup/debian/rules get-orig-source More information about comitup can be obtained from https://github.com/davesteele/comitup/tree/debian ITP is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821145 changelog: comitup (0.1-1) unstable; urgency=low * Initial release (Closes: #821145) -- David Steele Wed, 23 Mar 2016 23:07:38 -0400 Regards, Dave Steele
Bug#825904: RFS: python-model-mommy/1.2.6-1
Thanks for the feedback. The build is picking up the python-six and django dependencies. Package: python-model-mommy Depends: python-django, python-six, python:any (<< 2.8), python:any (>= 2.7.5-5~) Package: python3-model-mommy Depends: python3-django, python3-six, python3:any (>= 3.3.2-2~) I don't think python-six is a Build-Dependency because the code isn't run during build process. The library has a test suite, but it isn't included in the pypi tarball. I've filed a pull request asking upstream to include it. https://github.com/vandersonmota/model_mommy/pull/277 If the test suite was run during the build then python-six and django would be build dependencies. I've added "Team upload" to the changelog. I'm going to rebuild the package and upload a fresh copy to mentors. -- Edward.
Bug#825532: RFS: shadowsocks-libev/2.4.6+20160526+ds-1 [ITP]
Control: retitle -1 RFS: shadowsocks-libev/2.4.6+20160531+ds-1 [ITP] Since there're a few improvements of upstream: - Merged one of my patch in debian/patches/ - Made upstream Changelog out of debian/ folder, so as one lintian info is gone. I update the version to latest commit in upstream git, and upload to mentors. Now my packaging stuff can be found on pkg2 branch of https://github.com/rogers0/shadowsocks-libev Thank you and looking forward to sponsorship! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Re: dh_install globbing
> * Dmitry Bogatov , 2016-05-31, 13:15: > > $ git clone -b demonstrate > > https://anonscm.debian.org/cgit/users/kaction-guest/runit.git/ > > > >Glob in 'runit.install'. Try to build package, and notice, that no html > >files installed at all. > > I can't reproduce it here: > > $ grep -B1 html debian/*.install > #!/usr/bin/dh-exec > ${RUNIT}/doc/*[a-z].html /usr/share/doc/runit/html > > $ dpkg-buildpackage && dpkg -c ../runit_2.1.2-4_amd64.deb | grep /html/ > ... I upgraded dh-exec from jessie to sid, and it started to work. Strange, there were no NEWS. Thanks for your help! -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Keep-In-CC: yes X-Web-Site: sinsekvu.github.io
Bug#824121: python-nanomsg ready for review
hi mattia, umh? So, I read a bit the manpage, this was enough. IMHO, you gave up way too early, and I really much don't like it. well, thanks for your patience. i did think that i had possibly figured out the correct way to do it, but i wasn't sure. it can be hard to tell if you've done something correctly or not. the fact that i can't "undo" mistakes with git makes me reluctant too. but now you've got me started, i am learning how to work with git-dpm. hopefully my contributions in the future will compensate you for your time and frustration in this instance. as per your feedback, i have - added a patch to enable the bindnow hardening - fixed all the lintian warnings - amended the copyright period to be 2013-2014 and i believe it is ready for the next round of review. with thanks jonathon
Re: When to use "Replaces"?
On 2016-05-30.21:22, gregor herrmann wrote: > On Mon, 30 May 2016 20:25:56 +0200, Adam Borowski wrote: > > > > c) Something else ...? > > As both unclutters provide generally the same functionality, you may also > > use the "alternatives" method. > > My impression is that the "new" version has different command line > options. So calls to unclutter with the old options in > .xsession/.xinit would break if /usr/bin/unclutter points to the new > implementation via alternatives. > > I think I'd go for renaming here. Using the alternatives system is an interesting idea. Yes, the "new" version is *not* a drop-in replacement - while the functionality is the same, accepted arguments are not totally identical. However the description and example given in the policy manual of different "vi" clones seems to match the "unclutter" situation quite well. Am I correct in understanding that using alternatives requires co-operation between the two packages, "unclutter" and "unclutter-fixes"? If that's the case, I'll approach the "unclutter" maintainer, and if they disagree on using alternatives, will just rename my package. -- Regards, Scott. signature.asc Description: Digital signature
Re: dh_install globbing
* Dmitry Bogatov , 2016-05-31, 13:15: $ git clone -b demonstrate https://anonscm.debian.org/cgit/users/kaction-guest/runit.git/ Glob in 'runit.install'. Try to build package, and notice, that no html files installed at all. I can't reproduce it here: $ grep -B1 html debian/*.install #!/usr/bin/dh-exec ${RUNIT}/doc/*[a-z].html /usr/share/doc/runit/html $ dpkg-buildpackage && dpkg -c ../runit_2.1.2-4_amd64.deb | grep /html/ ... drwxr-xr-x root/root 0 2016-05-31 12:51 ./usr/share/doc/runit/html/ -rw-r--r-- root/root 8164 2014-08-10 20:22 ./usr/share/doc/runit/html/benefits.html -rw-r--r-- root/root 1382 2014-08-10 20:22 ./usr/share/doc/runit/html/dependencies.html -rw-r--r-- root/root 12586 2014-08-10 20:22 ./usr/share/doc/runit/html/faq.html -rw-r--r-- root/root 11264 2014-08-10 20:22 ./usr/share/doc/runit/html/index.html -rw-r--r-- root/root 1639 2014-08-10 20:22 ./usr/share/doc/runit/html/install.html -rw-r--r-- root/root 9362 2014-08-10 20:22 ./usr/share/doc/runit/html/replaceinit.html -rw-r--r-- root/root 3837 2014-08-10 20:22 ./usr/share/doc/runit/html/runlevels.html -rw-r--r-- root/root 25919 2014-08-10 20:22 ./usr/share/doc/runit/html/runscripts.html -rw-r--r-- root/root 5147 2014-08-10 20:22 ./usr/share/doc/runit/html/upgrade.html -rw-r--r-- root/root 917 2014-08-10 20:22 ./usr/share/doc/runit/html/usedietlibc.html -rw-r--r-- root/root 3101 2014-08-10 20:22 ./usr/share/doc/runit/html/useinit.html -- Jakub Wilk
Re: dh_install globbing
> * Dmitry Bogatov , 2016-05-30, 18:27: > >I want dh_install to install according following globbing: > > > > src/doc/*[a-z].html /usr/share/doc/runit/html > > > >(There is also html pages in form foo.1.html, which duplicate man=20 > >pages. I do not want to install them.) > > > >But it does not work -- nothing is installed. dh_install(1) does not=20 > >specify glob rules, but plain star (src/doc/*.html) works. > > The rules are documented in debhelper(1) manpage: =E2=80=9Cyou can use st= > andard=20 > shell wildcard characters (? and * and [..] character classes) in the=20 > [config] files=E2=80=9D. > > Even if [] wasn't supported, in compat >=3D5 dh_install is supposed to=20 > fail if wildcard expands to nothing. > > Can you show us the source package, so that we can see what's going on? Sure. $ git clone -b demonstrate https://anonscm.debian.org/cgit/users/kaction-guest/runit.git/ Glob in 'runit.install'. Try to build package, and notice, that no html files installed at all. -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Keep-In-CC: yes X-Web-Site: sinsekvu.github.io
Bug#825236: RFS: openfst/1.5.3-1 -- weighted finite-state transducers library
* Giulio Paci , 2016-05-31, 09:33: I just checked the building status of openfst and noticed failures on arm architectures and on kfreebsd-amd64. On arm it seems to me that a timeout occurred, One suspicious thing I found in armhf build log is: /usr/bin/make -C . -j4 -k distclean but this machine has only 4GB of RAM. So our parallelism limits don't seem to be enforced. This line ifneq "$(wildcard /build/buildd-*/)" "" was supposed to detect if the package is being built on a buildd, but buildds do longer use build directories like this. I don't think there's any reliable and future-proof way to detect this, so I'd suggest to drop this ifneq (i.e., start limiting parallelism everywhere). on kfreebsd-amd64 it seems a compiler failure. I suspect that cc1plus was killed by OOM killer, for the same reason as above. -- Jakub Wilk
Bug#825904: RFS: python-model-mommy/1.2.6-1
control: owner -1 ! control: tag -1 moreinfo Hi, looking at requirements.txt, seems that six is used grep six . -R |grep import ./model_mommy/utils.py:from six import string_types ./model_mommy/generators.py:import six ./model_mommy/recipe.py:from six import string_types ./model_mommy/mommy.py:from six import string_types, advance_iterator, PY3 adding it to build-dependencies should automatically make it a dependency thanks to dh_python2... Do you think it should be added or not? also django is needed? please let me know Oh and BTW I would appreciate a "Team Upload" in changelog :) cheers, G. Il Martedì 31 Maggio 2016 10:57, Edward Betts ha scritto: Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-model-mommy" * Package name: python-model-mommy Version : 1.2.6-1 Upstream Author : vandersonmota * URL : http://github.com/vandersonmota/model_mommy * License : Apache-2.0 Section : python It builds those binary packages: python-taskw - Python bindings for your taskwarrior database python3-taskw - Python bindings for your taskwarrior database (Python 3 version) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-model-mommy Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-model-mommy/python-model-mommy_1.2.6-1.dsc Changes since the last upload: * Team upload. [ Edward Betts ] * New upstream release. (Closes: #745093, #755657, #814781) * Build Python 3 package. * Fix lintian warning: dep5-copyright-license-name-not-unique * Update Standards-Version to 3.9.8 (no changes) * Update to debhelper 9 [ Ondřej Nový ] * Fixed VCS URL (https)
Bug#825878: marked as done (RFS: groonga-normalizer-mysql/1.1.1-1)
Your message dated Tue, 31 May 2016 09:41:58 + (UTC) with message-id <1257747330.3448255.1464687718454.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#825878: RFS: groonga-normalizer-mysql/1.1.1-1 has caused the Debian Bug report #825878, regarding RFS: groonga-normalizer-mysql/1.1.1-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.) -- 825878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825878 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 "groonga-normalizer-mysql" * Package name: groonga-normalizer-mysql Version : 1.1.1-1 Upstream Author : Kouhei Sutou * URL : https://github.com/groonga/groonga-normalizer-mysql * License : LGPL-2 Section : libs It builds those binary packages: groonga-normalizer-mysql - MySQL derived normalizer for Groonga To access further information about this package, please visit the following URL: https://mentors.debian.net/package/groonga-normalizer-mysql Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/groonga-normalizer-mysql/groonga-normalizer-mysql_1.1.1-1.dsc More information about groonga-normalizer-mysql can be obtained from https://github.com/groonga/groonga-normalizer-mysql Changes since the last upload: * Team upload. * New upstream release. * debian/control - Update to latest standard-version 3.9.8. Regards, Kentaro Hayashi pgp2WMkN4nRnF.pgp Description: PGP signature --- End Message --- --- Begin Message --- Hi, I sponsored it, even if I don't like two things + * debian/tests/* +- Add files for autopkgtest. you added them in the previous changelog entry, but since they were missing at that time... I didn't change that :) BTW no need to use "Team upload", because you are already the uploader :) (not asking to remove that, just saying it is not useful wrt lintian checks) cheers, G. Il Martedì 31 Maggio 2016 7:09, Kentaro Hayashi ha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "groonga-normalizer-mysql" * Package name: groonga-normalizer-mysql Version : 1.1.1-1 Upstream Author : Kouhei Sutou * URL : https://github.com/groonga/groonga-normalizer-mysql * License : LGPL-2 Section : libs It builds those binary packages: groonga-normalizer-mysql - MySQL derived normalizer for Groonga To access further information about this package, please visit the following URL: https://mentors.debian.net/package/groonga-normalizer-mysql Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/groonga-normalizer-mysql/groonga-normalizer-mysql_1.1.1-1.dsc More information about groonga-normalizer-mysql can be obtained from https://github.com/groonga/groonga-normalizer-mysql Changes since the last upload: * Team upload. * New upstream release. * debian/control - Update to latest standard-version 3.9.8. Regards, Kentaro Hayashi--- End Message ---
Re: dh_install globbing
* Dmitry Bogatov , 2016-05-30, 18:27: I want dh_install to install according following globbing: src/doc/*[a-z].html /usr/share/doc/runit/html (There is also html pages in form foo.1.html, which duplicate man pages. I do not want to install them.) But it does not work -- nothing is installed. dh_install(1) does not specify glob rules, but plain star (src/doc/*.html) works. The rules are documented in debhelper(1) manpage: “you can use standard shell wildcard characters (? and * and [..] character classes) in the [config] files”. Even if [] wasn't supported, in compat >=5 dh_install is supposed to fail if wildcard expands to nothing. Can you show us the source package, so that we can see what's going on? -- Jakub Wilk
Bug#825904: RFS: python-model-mommy/1.2.6-1
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-model-mommy" * Package name: python-model-mommy Version : 1.2.6-1 Upstream Author : vandersonmota * URL : http://github.com/vandersonmota/model_mommy * License : Apache-2.0 Section : python It builds those binary packages: python-taskw - Python bindings for your taskwarrior database python3-taskw - Python bindings for your taskwarrior database (Python 3 version) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-model-mommy Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-model-mommy/python-model-mommy_1.2.6-1.dsc Changes since the last upload: * Team upload. [ Edward Betts ] * New upstream release. (Closes: #745093, #755657, #814781) * Build Python 3 package. * Fix lintian warning: dep5-copyright-license-name-not-unique * Update Standards-Version to 3.9.8 (no changes) * Update to debhelper 9 [ Ondřej Nový ] * Fixed VCS URL (https)
Bug#824967: RFS: budgie-desktop/10.2.5-1 [ITP]
On Fri, 2016-05-27 at 20:17 +0100, foss.freedom wrote: > Looking on the mentors / mypackages webpage it says that the watch > file I've included does not work. This is very strange because I ran > a uscan and it correctly downloaded the upstream release file: The version we use on mentors is older so that might be the issue. I expect if you use version=3 in the watch file it will work there. > In summary - users are requested to upgrade. Moving forward, the > maintainer intends to branch the project at the next major release > and will backport stuff where necessary (e.g. critical issues). This > will be very useful for Debian to identify issues to include in > updates. Sounds good, please refer to the dev ref for security/stable uploads: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security > This did not reveal any specific build issues. Hmm. > > The package fails to build because gtk+3.0 3.20.5-1 is not yet built in > > Debian: > > I presume this is a transition issue for Sid as it moves to GTK+3.20 It turned out to be a bug, it is now in sid for most arches: https://buildd.debian.org/status/package.php?p=gtk%2b3.0 > The dependencies are been cleaned up. No libraries are included. > The minimal necessary dependencies have been left - these are > required for the desktop system to start successfully Looks good. > This has been substantially revised I suggest dropping the version number from the Upstream-Name field, since version numbers are usually not in the name of upstream projects. > The copyright now identifies LGPL vs GPL. I didn't audit it fully, but it looks good at a glance. > I asked this upstream: > https://github.com/solus-project/budgie-desktop/issues/448 Nice response :( It doesn't sound like they understood what I was trying to say. Perhaps the first paragraph of our upstream guide is more clear: https://wiki.debian.org/UpstreamGuide#Pristine_Upstream_Source > In the debian/clean I've removed the build artifacts that upstream > have recommended here https://github.com/solus-project/budgie- > desktop/issues/446#issuecomment-221378660 There was no need to remove those because autoreconf will automatically overwrite them. The other generated files need to be removed though. > https://bugzilla.redhat.com/show_bug.cgi?id=1170875 > https://mail.gnome.org/archives/commits-list/2012-November/msg06793.html > https://bugzilla.gnome.org/show_bug.cgi?id=686488 > [1] https://mail.gnome.org/archives/gnomecc-list/2012-October/msg3.html Thanks for the info. I suggest this course of action in parallel to finding a sponsor for budgie-desktop: For each of natray and gvc: First, get the embedded code copies documented according to this: https://wiki.debian.org/EmbeddedCodeCopies Second, find out where they are developed and talk with upstream about making these stable projects that are released and can be used as shared libraries by each of the projects using them. Third, get those packaged for Debian. > > Please add DEP-3 headers to the patches, particularly the > > Origin/Forwarded headers should point at URLs. > > This has been done. Probably not a good idea to remove authorship info from patches. > Upstream are already signing their commits. Tags/releases are not going to > be signed. Is there a particular reason why they sign commits but not sign tags/releases? That seems strange to me. > This has been tidied - only one vital override exists - this is > needed to display the GNOME appmenu correctly in the window > decoration. Hmm, ok. I wonder if this will affect people using both GNOME and Budgie under different users on the same machine. > I've moved to misc since I didnt see any other obvious Sid section > available. Please advise if there is a better more appropriate > section for GNOME/GTK+3 based desktop systems such as budgie-desktop Cinnamon is in Section: x11, that would be appropriate. > Apparently yes - according to the maintainer as linked above. Seems weird. > This is not installed - source only issue. True, you could send upstream a PR though. > Maintainer has indicated otherwise - see link above Please ask them to read the upstream guide section I quoted above. > > $ codespell --quiet-level=3 > > > > Vala to C compiler issues - not an upstream matter. Not entirely true, there are some in non-generated files: $ codespell --quiet-level=3 ./raven/sound.vala:384: dont ==> don't ./raven/sound.vala:395: dont ==> don't ./raven/Makefile.am:44: calender ==> calendar ./gvc/gvc-mixer-control.c:514: successfull ==> successful ./gvc/gvc-mixer-control.c:1503: everytime ==> every time -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Bug#825236: RFS: openfst/1.5.3-1 -- weighted finite-state transducers library
Hi Jakub and all, I just checked the building status of openfst and noticed failures on arm architectures and on kfreebsd-amd64. On arm it seems to me that a timeout occurred, on kfreebsd-amd64 it seems a compiler failure. Am I right? Is there anything that could be done? Bests, Giulio Il 24/mag/2016 23:42, "Giulio Paci" ha scritto: > > Package: sponsorship-requests > Severity: wishlist > X-Debbugs-CC: jw...@debian.org > > > Dear Jakub, > > I am looking for a sponsor for my package "openfst". > > * Package name: openfst >Version : 1.5.3-1 >Upstream Author : Cyril Allauzen , Michael Riley < ri...@google.com> > * URL : http://www.openfst.org/ > * License : Apache-2.0 >Section : libs > > It builds these binary packages: > > libfst-tools - weighted finite-state transducers library (tools) > libfst3 - weighted finite-state transducers library (runtime) > libfst3-plugins-base - weighted finite-state transducers library (base plugins) > libfst-dev - weighted finite-state transducers library (development) > > To access further information about this package, please visit the > following Vcs URL: > > https://anonscm.debian.org/git/collab-maint/openfst.git > > Regards, >Giulio Paci >