Work-needing packages report for May 5, 2017
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1058 (new: 0) Total number of packages offered up for adoption: 159 (new: 0) Total number of packages requested help for: 44 (new: 0) Please refer to http://www.debian.org/devel/wnpp/ for more information. No new packages have been orphaned, but a total of 1058 packages are orphaned. See http://www.debian.org/devel/wnpp/orphaned for a complete list. No new packages have been given up for adoption, but a total of 159 packages are awaiting adoption. See http://www.debian.org/devel/wnpp/rfa_bypackage for a complete list. For the following packages help is requested: autopkgtest (#846328), requested 155 days ago Description: automatic as-installed testing for Debian packages Reverse Depends: debci-worker openstack-pkg-tools Installations reported by Popcon: 789 Bug Report URL: http://bugs.debian.org/846328 balsa (#642906), requested 2048 days ago Description: An e-mail client for GNOME Reverse Depends: balsa-dbg Installations reported by Popcon: 696 Bug Report URL: http://bugs.debian.org/642906 busybox (#854181), requested 89 days ago Description: Tiny utilities for small and embedded systems Reverse Depends: bootcd busybox-syslogd dropbear-initramfs live-boot-initramfs-tools open-infrastructure-system-boot udhcpc udhcpd wicd-daemon zfs-initramfs Installations reported by Popcon: 194378 Bug Report URL: http://bugs.debian.org/854181 cargo (#860116), requested 23 days ago Description: Rust package manager Installations reported by Popcon: 466 Bug Report URL: http://bugs.debian.org/860116 cups (#532097), requested 2889 days ago Description: Common UNIX Printing System Reverse Depends: bluez-cups boomaga chromium cinnamon-settings-daemon cloudprint cups cups-backend-bjnp cups-browsed cups-bsd cups-client (66 more omitted) Installations reported by Popcon: 177940 Bug Report URL: http://bugs.debian.org/532097 cyrus-sasl2 (#799864), requested 589 days ago Description: authentication abstraction library Reverse Depends: 389-ds-base 389-ds-base-libs 389-dsgw adcli autofs-ldap cairo-dock-mail-plug-in claws-mail claws-mail-acpi-notifier claws-mail-address-keeper claws-mail-archiver-plugin (127 more omitted) Installations reported by Popcon: 195757 Bug Report URL: http://bugs.debian.org/799864 dee (#831388), requested 293 days ago Description: model to synchronize mutiple instances over DBus Reverse Depends: dee-tools gir1.2-dee-1.0 libdee-1.0-4-dbg libdee-dev zeitgeist-core Installations reported by Popcon: 64119 Bug Report URL: http://bugs.debian.org/831388 developers-reference (#759995), requested 978 days ago Description: guidelines and information for Debian developers Installations reported by Popcon: 19029 Bug Report URL: http://bugs.debian.org/759995 devscripts (#800413), requested 583 days ago Description: scripts to make the life of a Debian Package maintainer easier Reverse Depends: apt-build apt-listdifferences aptfs arriero bzr-builddeb customdeb debci debian-builder debmake debpear (24 more omitted) Installations reported by Popcon: 13109 Bug Report URL: http://bugs.debian.org/800413 ejabberd (#767874), requested 913 days ago Description: distributed, fault-tolerant Jabber/XMPP server written in Erlang Reverse Depends: ejabberd-contrib ejabberd-mod-cron ejabberd-mod-log-chat ejabberd-mod-logsession ejabberd-mod-logxml ejabberd-mod-message-log ejabberd-mod-muc-log-http ejabberd-mod-post-log ejabberd-mod-pottymouth ejabberd-mod-rest (4 more omitted) Installations reported by Popcon: 638 Bug Report URL: http://bugs.debian.org/767874 fbcat (#565156), requested 2668 days ago Description: framebuffer grabber Installations reported by Popcon: 205 Bug Report URL: http://bugs.debian.org/565156 fgetty (#823061), requested 369 days ago Description: console-only getty & login (issue with nis) Installations reported by Popcon: 1735 Bug Report URL: http://bugs.debian.org/823061 freeipmi (#628062), requested 2170 days ago Description: GNU implementation of the IPMI protocol Reverse Depends: conman freeipmi freeipmi-bmc-watchdog freeipmi-ipmidetect freeipmi-ipmiseld freeipmi-tools ipmitool libfreeipmi-dev libfreeipmi16 libipmiconsole-dev (7 more omitted) Installations reported by Popcon: 6250 Bug Report
Re: Bug#861812: ITP: node-evp-bytestokey -- secure key derivation algorithm from openssl
Bastien ROUCARIES : > * Package name: node-evp-bytestokey > > EVP_BytesToKey() derives a key and IV from various parameters. type > is the cipher to derive the key and IV for. md is the message digest > to use. The salt parameter is used as a salt in the derivation: it > should point to an 8 byte buffer or NULL if no salt is used. data is a > buffer containing datal bytes which is used to derive the keying data. > count is the iteration count to use. The derived key and IV will be > written to key and iv respectively. > . > Node.js is an event-based server-side JavaScript engine. > > That description is more of a manual than a helpful package description.
Re: substvars in *.install + friends
Hi, On Thu, 2017-05-04 at 17:14 +0200, Enrico Weigelt wrote: > is it possible to use the substvars mechanism for the *.install and > similar files, just like w/ control file ? > > For multi-version installations, I'm keeping the whole package in a > prefix w/ the version number (see my other mail - nodejs). I don't > like to change lots of files which each version number. Please ask packaging questions on debian-ment...@lists.debian.org The *.install file can be executable (see "Debhelper config files" in man:debhelper(7)). There is also dh-exec, but I had no need for it myself so far and therefore don't know much about it. Ansgar
substvars in *.install + friends
Hi folks, is it possible to use the substvars mechanism for the *.install and similar files, just like w/ control file ? For multi-version installations, I'm keeping the whole package in a prefix w/ the version number (see my other mail - nodejs). I don't like to change lots of files which each version number. thx --mtx
Re: Packaging nodejs-7.9
On 04.05.2017 09:26, Jérémy Lal wrote: > At the moment, in debian, /usr/lib/nodejs is there to store all node > modules installed from debian packages. hmm, would that conflict w/ having certain "nodejs-$version" subdirs w/ the actual engines (the whole tree - not splitted out the several FHS parts yet) there ? Meanwhile I've also added some update-alternatives support. (yet have to add version into package name). But this will conflict w/ current versions, as they directly install /usr/bin/nodejs. Can we make a minor update of 0.10.* for update-alternatives ? > Are you talking about installing modules depending on their > compatibility with node engines (as found in package.json) ? Actually, not sure whether that's really required. Are there any known (already packaged) modules that break w/ newer nodejs ? If not, I guess, just adding depend son newer engines where needed should be enough. --mtx
Bug#861827: ITP: golang-github-serenize-snaker -- Convert camel cased strings to snake case and back
Package: wnpp Severity: wishlist Owner: Diego M. Rodriguez * Package name: golang-github-serenize-snaker Version : 0.0~git20170425.0.1c7f653-1 Upstream Author : Serenize UG * URL : https://github.com/serenize/snaker * License : Expat Programming Lang: Go Description : Convert camel cased strings to snake case and back This is a small Go library to convert camel cased strings to snake case and back, except some defined words such as common acronyms and initialisms). This library is being packaged as a build dependency of loadimpact/k6 (loadimpact/k6 -> serenize/snaker).
Bug#861825: ITP: golang-github-viki-org-dnscache -- A DNS Cache for Go
Package: wnpp Severity: wishlist Owner: Diego M. Rodriguez * Package name: golang-github-viki-org-dnscache Version : 0.0~git20130720.0.c70c1f2-1 Upstream Author : Viki Inc. * URL : https://github.com/viki-org/dnscache * License : Expat Programming Lang: Go Description : A DNS cache for Go A thread-safe DNS cache for the Go programming language that refreshes the DNS entries in the background at configurable intervals, reducing the risk of blocked/leaking Go routines. This library is being packaged as a build dependency of loadimpact/k6 (loadimpact/k6 -> viki-org/dnscache).
Bug#861812: ITP: node-evp-bytestokey -- secure key derivation algorithm from openssl
Package: wnpp Severity: wishlist Owner: ro...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-evp-bytestokey Version : 1.0.0 Upstream Author : Calvin Metcalf * URL : https://github.com/crypto-browserify/EVP_BytesToKey * License : Expat Programming Lang: JavaScript Description : secure key derivation algorithm from openssl EVP_BytesToKey() derives a key and IV from various parameters. type is the cipher to derive the key and IV for. md is the message digest to use. The salt parameter is used as a salt in the derivation: it should point to an 8 byte buffer or NULL if no salt is used. data is a buffer containing datal bytes which is used to derive the keying data. count is the iteration count to use. The derived key and IV will be written to key and iv respectively. . Node.js is an event-based server-side JavaScript engine.
Bug#861810: ITP: virtme -- tool for disk-less Linux emulation using qemu
Package: wnpp Severity: wishlist Owner: Sebastian Reichel * Package name: virtme Version : 0.0.3+git20170420 Upstream Author : Andy Lutomirski * URL : https://git.kernel.org/pub/scm/utils/kernel/virtme/virtme.git/ * License : GPL-2 Programming Lang: Python Description : tool for disk-less Linux emulation using qemu Virtme is a set of simple tools to run a virtualized Linux kernel that uses the host Linux distribution or a simple rootfs instead of a whole disk image. Virtme is tiny, easy to use, and makes testing kernel changes quite simple. Some day this might be useful as a sort of sandbox. Right now it's not really configurable enough for that. The tool is really useful for kernel testing.
Bug#861809: ITP: node-stream-browserify -- the stream module from node core for browsers
Package: wnpp Severity: wishlist Owner: ro...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-stream-browserify Version : 2.0.1 Upstream Author : James Halliday (http://substack.net) * URL : https://github.com/substack/stream-browserify * License : Expat Programming Lang: JavaScript Description : the stream module from node core for browsers This module allows one to use stream in browser context. . Node.js is an event-based server-side JavaScript engine.
Re: Packaging nodejs-7.9
2017-05-04 9:13 GMT+02:00 Enrico Weigelt, metux IT consult < enrico.weig...@gr13.net>: > Hi folks, > > > I'm currently packaging nodejs-7.9 for various deb Distros. > > I'll have to maintain some applications that use the fanciest > new features, and precompiled binaries from untrusted sources > (eg. nvm+friends) of course are not an option. > > Before I go all of this alone - is there anybody here who already > done this ? Or anything I should consider ? > > My current plan is: > * install in similar way as jvm (/usr/lib/nodejs/nodejs-$version) > * for now I'll just directly symlink - update-alternatives support > comes in a later step (or maybe someone here likes to help ?) > * the actual nodejs package will be named "nodejs-$version", the > symlinks in package "nodejs". > > The tricky part will be a safe upgrade path from current 0.10 > and npm's dependencies. > > > What do you folks think about that ? > At the moment, in debian, /usr/lib/nodejs is there to store all node modules installed from debian packages. Are you talking about installing modules depending on their compatibility with node engines (as found in package.json) ? Jérémy
Re: Packaging nodejs-7.9
On വ്യാഴം 04 മെയ് 2017 12:43 വൈകു, Enrico Weigelt, metux IT consult wrote: > What do you folks think about that ? Hi Enrico, I suggest you post it to pkg-javascript-devel list https://lists.alioth.debian.org/mailman/listinfo/pkg-javascript-devel Thanks Praveen signature.asc Description: OpenPGP digital signature
Packaging nodejs-7.9
Hi folks, I'm currently packaging nodejs-7.9 for various deb Distros. I'll have to maintain some applications that use the fanciest new features, and precompiled binaries from untrusted sources (eg. nvm+friends) of course are not an option. Before I go all of this alone - is there anybody here who already done this ? Or anything I should consider ? My current plan is: * install in similar way as jvm (/usr/lib/nodejs/nodejs-$version) * for now I'll just directly symlink - update-alternatives support comes in a later step (or maybe someone here likes to help ?) * the actual nodejs package will be named "nodejs-$version", the symlinks in package "nodejs". The tricky part will be a safe upgrade path from current 0.10 and npm's dependencies. What do you folks think about that ? --mtx
