Bug#873261: RFS: node-when/3.7.8+ds-1 [ITP]
Package: sponsorship-requests Severity: wishlist Owner: Bastien Roucaries Dear mentors, I am looking for a sponsor for my package "node-when" * Package name: node-when Version : 3.7.8+ds-1 Upstream Author : Brian Cavalier * URL : https://github.com/cujojs/when/issues * License : Expat Section : javascript It builds those binary packages: node-when - Async tools and when() implementation for Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-when Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-when/node-when_3.7.8+ds-1.dsc It is packaged within the Debian Javascript Maintainers team: Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-when.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-when.git Thanks, Snark on #debian-js
Bug#873180: marked as done (RFS: node-cp/0.2.0-1 [ITP])
Your message dated Fri, 25 Aug 2017 22:59:12 +0200 with message-id and subject line Re: Bug#873180: RFS: node-cp/0.2.0-1 [ITP] has caused the Debian Bug report #873180, regarding RFS: node-cp/0.2.0-1 [ITP] 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.) -- 873180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873180 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 "node-cp" * Package name: node-cp Version : 0.2.0-1 Upstream Author : Stephen Mathieson * URL : https://github.com/stephenmathieson/node-cp * License : Expat Section : web It builds those binary packages: node-cp- File copy for Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-cp Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-cp/node-cp_0.2.0-1.dsc I will maintain it within the Debian Javascript Maintainer team: Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-cp.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-cp.git Thanks, Snark on #debian-js --- End Message --- --- Begin Message --- On Fri, Aug 25, 2017 at 10:51 PM, Julien Puydt wrote: > > > Le 25/08/2017 à 20:03, Bastien Roucaries a écrit : >> Control: tags -1 + moreinfo > >> Why not use fs-extra ? > > Indeed, patching upstream to use fs-extra is easier : closing both the > ITP and the RFS. > > Snark on #debian-js When finding such a problem please complete https://wiki.debian.org/Javascript/Nodejs/Database It help npm2deb Bastien--- End Message ---
Bug#873180: RFS: node-cp/0.2.0-1 [ITP]
Control: tags -1 + moreinfo Why not use fs-extra ? Le 25 août 2017 13:06:06 GMT+02:00, Julien Puydt a écrit : >Package: sponsorship-requests >Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "node-cp" > > * Package name: node-cp > Version : 0.2.0-1 > Upstream Author : Stephen Mathieson > * URL : https://github.com/stephenmathieson/node-cp > * License : Expat > Section : web > > It builds those binary packages: > >node-cp- File copy for Node.js > > To access further information about this package, please visit the >following URL: > > https://mentors.debian.net/package/node-cp > > >Alternatively, one can download the package with dget using this >command: > >dget -x >https://mentors.debian.net/debian/pool/main/n/node-cp/node-cp_0.2.0-1.dsc > > I will maintain it within the Debian Javascript Maintainer team: >Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-cp.git >Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-cp.git > >Thanks, > >Snark on #debian-js -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.
Bug#873072: marked as done (RFS: xtensor/0.10.11-1)
Your message dated Fri, 25 Aug 2017 16:51:14 + (UTC) with message-id <1323633563.2967042.1503679874...@mail.yahoo.com> and subject line Re: Bug#873072: RFS: xtensor/0.10.11-1 has caused the Debian Bug report #873072, regarding RFS: xtensor/0.10.11-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.) -- 873072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: xtensor Version : 0.10.11-1 Upstream Author : Johan Mabille, Sylvain Corlay and Wolf Vollprecht * URL : http://quantstack.net/xtensor * License : BSD Section : libs Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/xtensor.git Changes since the last upload: * New upstream version 0.10.11 * Fixup the Vcs-Browser URI * Bump the standards version to 4.1.0 Regards, Ghis --- End Message --- --- Begin Message --- Hello, >* Package name: xtensor ok G.--- End Message ---
Re: javalib-but-no-public-jars lintian
>N:does not contain any JAR file in /usr/share/java, while the java policy
my $is_transitional = $info->is_pkg_class('transitional');
if (!$has_public_jars && !$is_transitional && $pkg =~ /^lib[^\s,]+-java$/){
# Skip this if it installs a symlink in usr/share/java
my $java_dir = $info->index_resolved_path('usr/share/java/');
my $has_jars = 0;
$has_jars = 1
if $java_dir
and any { $_->name =~ m@^[^/]+\.jar$@o } $java_dir->children;
tag 'javalib-but-no-public-jars' if not $has_jars;
}
I would say, it detects that the end of the link is outside usr/share/java, but
only usr/share.
Technically the symlink is in usr/share/java, but the link points to outside.
However, I'm really not sure if my perl-foo (close to zero) is correct enough
G.
Bug#873113: RFS: xssproxy/1.0.0-1 [ITP]
OK, should be fixed this time. Regards, Tim Schumacher bin91iUtqjpBo.bin Description: PGP Public Key pgpqCLCCzpvkD.pgp Description: PGP Digital Signature
Bug#873113: RFS: xssproxy/1.0.0-1 [ITP]
Please run lintian before uploading the package: W: xssproxy source: package-needs-versioned-debhelper-build-depends 10 -- WBR, wRAR signature.asc Description: PGP signature
Bug#873113: RFS: xssproxy/1.0.0-1 [ITP]
Control: tags -1 - moreinfo Should be fixed now. Regards, Tim Schumacher binY9y4mKtu2L.bin Description: PGP Public Key pgpo4yEL6qjad.pgp Description: PGP Digital Signature
Bug#873132: changelog entry updated
On Fri, Aug 25, 2017 at 04:17:34PM +0200, Adam Bilbrough wrote: > Hi,I have updated the entry to be more descriptive: > * Adds '+' as an argument for specifying a line number (closes: #872848) > The upload on mentors.debian.net has been updated with this included. Hi! I'm afraid that, just like xmltoman, the orig tarball doesn't match. You'd need to either put the changes into a patch (dpkg-source --commit) or to bump the upstream version number. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!? ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din ⠈⠳⣄
Bug#873132: changelog entry updated
Hi,I have updated the entry to be more descriptive: * Adds '+' as an argument for specifying a line number (closes: #872848) The upload on mentors.debian.net has been updated with this included. ~Adam
Re: How to replace throw exceptions in C++11
Hi, On Fri, Aug 25, 2017 at 11:57:25AM +0200, Christian Seiler wrote: > > The patch in the bug report already disables -Werror - and that should > definitely be what you should use to build the package even after those > warnings have gone. Thanks for the long explanation which is helpful for the future. For this case I simply failed to detect the submitted patch. :-P Sorry for the noise Andreas. -- http://fam-tille.de
javalib-but-no-public-jars lintian
hello mentors, I have this in an updated knopflerfish-osgi package: I: libknopflerfish-osgi-framework-java: javalib-but-no-public-jars N: N:The name of the package suggests that it contains a java library but it N:does not contain any JAR file in /usr/share/java, while the java policy N:mandates that JAR files outside /usr/share/java are for private use. N: N:Severity: minor, Certainty: possible N: N:Check: java, Type: binary N: However, the package installs: lrwxrwxrwx 1 root root 35 Aug 23 16:06 /usr/share/java/knopflerfish-framework.jar -> ../knopflerfish/framework-8.0.5.jar Maybe lintian uses "file" to check whether it's a jar? Shall I report a severity=normal bug against lintian? Thanks and Best Regards, -- Felix Natter
Bug#873180: RFS: node-cp/0.2.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-cp" * Package name: node-cp Version : 0.2.0-1 Upstream Author : Stephen Mathieson * URL : https://github.com/stephenmathieson/node-cp * License : Expat Section : web It builds those binary packages: node-cp- File copy for Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-cp Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-cp/node-cp_0.2.0-1.dsc I will maintain it within the Debian Javascript Maintainer team: Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-cp.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-cp.git Thanks, Snark on #debian-js
Re: How to replace throw exceptions in C++11
Hi, Am 2017-08-25 10:10, schrieb Andreas Tille: I try to fix #872262 and while I've read that dynamic exception specifications are deprecated in C++11 I have not found a sensible replacement for the affected code. Any hint what to do here? The main issue with the code are not the exception specifications but rather that you build with -Werror here. -Werror is great for developers (to make sure no warnings get ignored when the software is written), but it's an awful thing to have in distribution packages. Switch to a new compiler (as has happened here) that suddenly has additional warnings, and builds just start to fail needlessly. The patch in the bug report already disables -Werror - and that should definitely be what you should use to build the package even after those warnings have gone. (What is possible is to build a package with specific warnings made to errors, for example -Werror=format-security, to catch really bad bugs. But that should be opt-in, not just a generic -Werror "please turn ALL warnings into errors".) As for the replacement for affected code (for the long term): C++11 has noexcept as a replacement for throw() with empty parameter list - so if you are _really_, _really_, _really_ sure that a function doesn't ever throw you can specify noexcept after the function name. (If it does throw anyway, the program will exit.) Please note though that - as with const - noexcept is part of the function name mangling, so void foo(); and void foo() noexcept; are two separate functions when it comes to their symbol name - so if you want to keep binary compatibility, adding noexcept in cases where there are empty throw() specifications might not be an option. As for exception specifications with explicitly named exception names, for example throw(std::runtime_error) after a function name: there's no replacement for that in C++11, just remove those entirely if you want to be conforming. (They were useless in previous C++ versions anyway, to my knowledge no compiler ever did anything with those specifications.) Regards, Christian
Re: How to replace throw exceptions in C++11
On Fri, Aug 25, 2017 at 10:10:49AM +0200, Andreas Tille wrote: > I try to fix #872262 and while I've read that dynamic exception > specifications are deprecated in C++11 I have not found a sensible > replacement for the affected code. > > Any hint what to do here? The report has a patch, have you considered it? -- WBR, wRAR signature.asc Description: PGP signature
How to replace throw exceptions in C++11
Hi, I try to fix #872262 and while I've read that dynamic exception specifications are deprecated in C++11 I have not found a sensible replacement for the affected code. Any hint what to do here? Kind regards Andreas. -- http://fam-tille.de
