Bug#843592: RFS: node-punycode/2.0.1-1

[Bastien ROUCARIES]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC :prav...@debian.org
X-Debbugs-CC :locutusofb...@debian.org

Dear mentors,

  I am looking for a sponsor for my package "node-punycode"

 * Package name: node-punycode
   Version : 2.0.1-1
   Upstream Author : Mathias Bynens
 * URL : [fill in URL of upstreams web site]
 * License : expat
   Section : web

  It builds those binary packages:

node-punycode - Nodejs robust Punycode converter fully RFC compliant

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/node-punycode


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-punycode/node-punycode_2.0.1-1.dsc

  More information about hello can be obtained from https://mths.be/punycode


  Changes since the last upload:

  node-punycode (2.0.1-1) unstable; urgency=medium

  * New upstream release.
  * Bump standard version (no changes).
  * Use compat version 10.

 -- Bastien Roucariès   Mon, 07
Nov 2016 22:17:15 +0100

It is needed for browserify effort so try to upload correct version


  Regards,
   bastien roucaries

Bug#843596: RFS: node-jsonparse/1.2.0-1

[Bastien ROUCARIES]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]
X-Debbugs-CC :prav...@debian.org
X-Debbugs-CC :locutusofb...@debian.org


  Dear mentors,

  I am looking for a sponsor for my package "node-jsonparse"

 * Package name: node-jsonparse
   Version : 1.2.0-1
   Upstream Author :  2015-2016 Tim Caswell 
 * License : expat
   Section : web

  It builds those binary packages:

node-jsonparse - Pure javascript JSON streaming parser for node.js

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/node-jsonparse


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-jsonparse/node-jsonparse_1.2.0-1.dsc


  Changes since the last upload:

   * New upstream version.
  * Bump policy version (no changes).
  * Use compat 10.
  * Upgrade VCS fields.

It is needed for browserify effort so try to upload correct version


  Regards,
   bastien roucaries

Re: Problems creating babel-polyfill.min.js

[Gianfranco Costamagna]

Hi,

>When doing a websearch this might mean that the JS contains errors - but

>it seems there is a different converter which has no problems.  Before
>I start debugging what exactly happens in "npm install" I wonder whether
>comebody could enlighten me what's the best way to get the minimized JS.


npm install is something like pip install, or ruby gems install (or whatever
are called).
In this case, just package it separately as js module and use it.
pkg-javascript has a lot (almost all of them) of single js libraries packaged
separately and with a dh helper that does most of the work

G.

Problems creating babel-polyfill.min.js

[Andreas Tille]

Hi,

I'd like to upgrade the package r-cran-shiny.  The new upstream version
contains babel-polyfill.min.js.  I think I found the source which can be
obtained via

npm install --save-dev babel-polyfill
mv node_modules/babel-polyfill/dist/polyfill.js babel-polyfill.js

While this process creates also a minimized js I have no idea how this
can be approached.  Normally I'm using yui-compressor for the conversion
but in this case it fails:

$ yui-compressor babel-polyfill.js
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.yahoo.platform.yui.compressor.Bootstrap.main(Bootstrap.java:21)
Caused by: java.util.MissingResourceException: Can't find bundle for base name 
org.mozilla.javascript.resources.Messages, locale de_DE
at 
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1564)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1387)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:845)
at 
org.mozilla.javascript.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:3608)
...


When doing a websearch this might mean that the JS contains errors - but
it seems there is a different converter which has no problems.  Before
I start debugging what exactly happens in "npm install" I wonder whether
comebody could enlighten me what's the best way to get the minimized JS.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#843540: RFS: urfkill/0.5.0-5 [RC]

[Keng-Yu Lin]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "urfkill"

 * Package name: urfkill
   Version : 0.5.0-5
   Upstream Author : Gary Lin (g...@suse.com), Joey Lee (j...@suse.com)
 * URL : https://www.freedesktop.org/wiki/Software/urfkill/
 * License : GPLv2
   Section : net

It builds those binary packages:

 gir1.2-urfkill-0.5 - GObject introspection data for the urfkill library
 liburfkill-glib-dev - wireless killswitch management library
(development files)
 liburfkill-glib0 - wireless killswitch management library
 liburfkill-glib0-dbg - wireless killswitch management library (debug symbols)
 urfkill- wireless killswitch management daemon for laptops

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/urfkill


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/u/urfkill/urfkill_0.5.0-5.dsc


  Changes since the last upload:

  [Michael Biebl]
  * Follow gobject introspection policy (Closes: #838415)

  [Keng-Yu Lin]
  * Use dpkg-trigger to call ldconfig for liburfkill-glib0
- Add debian/liburfkill-glib0.triggers; remove debian/postinst
  * Bump Standards-Version to 3.9.8
  * Library gir1.2-urfkill-glib0 is renamed to gir1.2-urfkill-0.5,
added the Breaks and Replaces in debian/control


  Regards,
   Keng-Yu Lin

Bug#843599: RFS: passwordsafe/1.00+dfsg-1

[Bill Blough]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

I am looking for a sponsor for my package "passwordsafe"

* Package name: passwordsafe
  Version : 1.00+dfsg-1
  Upstream Author : Rony Shapiro ]
* URL : https://pwsafe.org
* License : Artistic 2.0
  Section : utils

It builds those binary packages:

passwordsafe - Simple & Secure Password Management
passwordsafe-common - architecture independent files for Password Safe

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/passwordsafe


 Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/passwordsafe/passwordsafe_1.00+dfsg-1.dsc

More information about hello can be obtained from https://pwsafe.org.

Changes since the last upload:

* Change d/rules to eliminate depencdency on locales-all.  Thanks to
  Stephen Kitt for the bug report and patch.  Closes: 833533
* Fix watch file
* New upstream version
* Remove reproducibe-build.patch, which was applied upstream.


Regards,
Bill Blough

Bug#843604: RFS: xerces-c/3.1.4+debian-1 [RC]

[Bill Blough]

Package: sponsorship-requests
Severity: important

Dear mentors,

  I am looking for a sponsor for my package "xerces-c"

 * Package name: xerces-c
   Version : 3.1.4+debian-1
   Upstream Author : Xerces-C developers 
 * URL : https://xerces.apache.org/xerces-c/
 * License : Apache 2.0
   Section : libs

  It builds those binary packages:

 libxerces-c-dev - validating XML parser library for C++ (development files)
 libxerces-c-doc - validating XML parser library for C++ (documentation)
 libxerces-c-samples - validating XML parser library for C++ (compiled samples)
 libxerces-c3.1 - validating XML parser library for C++

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/xerces-c


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/x/xerces-c/xerces-c_3.1.4+debian-1.dsc

  More information about hello can be obtained from 
https://xerces.apache.org/xerces-c/

  Changes since the last upload:

  * New upstream release
  * Removed patches that are no longer needed (applied upstream)
  * Compile with curl support to allow accessing https urls.  Closes: #821380
  * Added patch to fix some compiler warnings (forwarded upstream)

  In addition, I'm hopeful that the new upstream release will resolve the
  FTBFS issue on s390x (bug 833754), however I don't know that for sure.

  Regards,
   Bill Blough

Re: Problems creating babel-polyfill.min.js

[Gianfranco Costamagna]

Hi,

>Are you sure that it makes sense to add more and more JS packages - its
>simply for a single package dependency for the moment.  However, if
>somebody confirms that this package is sensible also for other purposes
>I might fire up npm2deb ...


seems that I'm not the only one thinking that...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837056

G.

Re: Problems creating babel-polyfill.min.js

[Lucas Castro]

On 07-11-2016 13:11, Andreas Tille wrote:
> Hi Gianfranco,
>
> On Mon, Nov 07, 2016 at 03:57:27PM +, Gianfranco Costamagna wrote:
>>> When doing a websearch this might mean that the JS contains errors - but
>>> it seems there is a different converter which has no problems.  Before
>>> I start debugging what exactly happens in "npm install" I wonder whether
>>> comebody could enlighten me what's the best way to get the minimized JS.
>> npm install is something like pip install, or ruby gems install (or whatever
>> are called).
>> In this case, just package it separately as js module and use it.
>> pkg-javascript has a lot (almost all of them) of single js libraries packaged
>> separately and with a dh helper that does most of the work
> Are you sure that it makes sense to add more and more JS packages - its
> simply for a single package dependency for the moment.  However, if
> somebody confirms that this package is sensible also for other purposes
> I might fire up npm2deb ...
>
> Kind regards
>
>  Andreas.
For the point of view of your single project is just for a single
package dependence, but think about all the package that didn't get in
Debian yet just because of that dependence.
I want to start the works on babel modules packaging soon, jut  got some
issues about how to split all modules that comes all together in  single
tarball.


--
Lucas Castro




signature.asc
Description: OpenPGP digital signature

Re: Problems creating babel-polyfill.min.js

[Andreas Tille]

On Mon, Nov 07, 2016 at 04:15:08PM +, Gianfranco Costamagna wrote:
> >Are you sure that it makes sense to add more and more JS packages - its
> >simply for a single package dependency for the moment.  However, if
> >somebody confirms that this package is sensible also for other purposes
> >I might fire up npm2deb ...
> 
> 
> seems that I'm not the only one thinking that...
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837056

Thanks for the pointer (according bug report in CC).  I tried the following:


$ npm2deb create babel-polyfill

This is not a crystal ball, so please take a look at auto-generated files.

You may want fix first these issues:

babel-polyfill/node-babel-polyfill/debian/control: FIX_ME long description
babel-polyfill/node-babel-polyfill/debian/watch:# Origin url: FIX_ME repo url

Use uscan to get orig source files. Fix debian/watch and then run
$ uscan --download-current-version

Warnings occured:
 [error]   core-js: dependency node-core-js not in debian
 [error]   regenerator-runtime: dependency node-regenerator-runtime not in 
debian
 [error]   babel-runtime: dependency node-babel-runtime not in debian



Before I continue my naive attempt to package babel-polyfill: Does it
really need three additional packages?

Kind regards

Andreas.

-- 
http://fam-tille.de

Re: Problems creating babel-polyfill.min.js

[Andreas Tille]

Hi Gianfranco,

On Mon, Nov 07, 2016 at 03:57:27PM +, Gianfranco Costamagna wrote:
> >When doing a websearch this might mean that the JS contains errors - but
> 
> >it seems there is a different converter which has no problems.  Before
> >I start debugging what exactly happens in "npm install" I wonder whether
> >comebody could enlighten me what's the best way to get the minimized JS.
> 
> npm install is something like pip install, or ruby gems install (or whatever
> are called).
> In this case, just package it separately as js module and use it.
> pkg-javascript has a lot (almost all of them) of single js libraries packaged
> separately and with a dh helper that does most of the work

Are you sure that it makes sense to add more and more JS packages - its
simply for a single package dependency for the moment.  However, if
somebody confirms that this package is sensible also for other purposes
I might fire up npm2deb ...

Kind regards

 Andreas.

-- 
http://fam-tille.de

Re: Building package under kfreebsd/hurd

[Christian Seiler]

On 11/07/2016 12:46 AM, Elías Alejandro wrote:
> I wonder if there's a way to build packages for distinct
> architectures, specifically for
> Hurd or Kfreebsd. Do I have to create a new installation or use qemu?.

In my experience the easiest way to do so is to use a virtual
machine (I prefer libvirt + virt-manager with Qemu for that),
boot the machine, install an SSH server and 

In the case of Hurd, you really don't want to use that on your
bare-metal hardware, because last time I checked it didn't
support USB yet. (If you don't need USB you can of course use
it. ;-)) kFreeBSD is not a problem in that regard, but unless
your system is really RAM-starved a VM is still much easier to
handle.

Note that it's not completely trivial to set up these machines.
The problem is that most installation media you can find are
a bit older, and if you've ever tried to install testing/sid
with an older installer, you can see that it often doesn't
quite work because sid will have moved on quite a bit. Plus
a lot of the documentation you find is a bit outdated for
both archs - there is more current documentation, but when
searching you more often than not find the outdated docs in
my experience, before you find the current ones.

In the case of Hurd Samuel Thibault provides premade images
you can use:
https://people.debian.org/~sthibault/hurd-i386/README
https://people.debian.org/~sthibault/hurd-i386/
I suspect that's going to be the easiest way of setting up a
VM there. (Please do a dist-upgraded before you actually use
them to try stuff though, they are relatively up to date, but
aren't daily images.)

In the case of kFreeBSD, I'm not completely sure anymore,
but if I remember correctly, I used the Jessie rc3 installer
to install the VM and then dist-upgraded to sid (by changing
the sources.list):
http://cdimage.debian.org/mirror/cdimage/archive/jessie_di_rc3/kfreebsd-amd64/iso-cd/
(That may or may not work, depending on whether I remember
correctly.)

In both cases (Hurd, kFreeBSD) please be aware that while a
lot of the everyday userland is still the same as with the
Linux ports (e.g. ls, cp, etc.), many administrative commands
are quite different or at least have different options / a
different output. Especially Hurd can be quite weird when you
first come in contact with it; once you get to know some of
the concepts and ideas behind it, it's actually really cool,
but there's a bit of a learning curve there.

Hope that helps.

> [1]https://wiki.debian.org/qemubuilder

I haven't tried that yet, but from reading the wiki page it
looks to me that it's mostly a Linux thing - and while there
is no inherent reason why fully-fledged VMs with Hurd or
kFreeBSD wouldn't work in principle with something like that,
I suspect that you'd need to fix a lot of things to make it
work. (I may be wrong though.) It's probably easier to just
use a virtual machine manually yourself.

Regards,
Christian

Bug#843583: RFS: imagemagick/8:6.9.6.2+dfsg-3

[Bastien ROUCARIES]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package "imagemagick"

 * Package name: imagemagick
   Version : 8:6.9.6.2+dfsg-3
 * License : imagemagick
   Section : graphics

  It builds those binary packages:

imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-6.q16hdri - image manipulation programs -- quantum depth Q16HDRI
 imagemagick-common - image manipulation programs -- infrastructure
dummy package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics
routines -- Q16 versio
 libimage-magick-q16hdri-perl - Perl interface to the ImageMagick
graphics routines -- Q16HDRI ve
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick
- header files
 libmagick++-6.q16-6v6 - C++ interface to ImageMagick -- quantum depth Q16
 libmagick++-6.q16-dev - C++ interface to ImageMagick - development files (Q16)
 libmagick++-6.q16hdri-6v6 - C++ interface to ImageMagick -- quantum
depth Q16HDRI
 libmagick++-6.q16hdri-dev - C++ interface to ImageMagick -
development files (Q16HDRI)
 libmagick++-dev - object-oriented C++ interface to ImageMagick -- dummy package
 libmagickcore-6-arch-config - low-level image manipulation library -
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-2 - low-level image manipulation library --
quantum depth Q16
 libmagickcore-6.q16-2-extra - low-level image manipulation library -
extra codecs (Q16)
 libmagickcore-6.q16-dev - low-level image manipulation library -
development files (Q16)
 libmagickcore-6.q16hdri-2 - low-level image manipulation library --
quantum depth Q16HDRI
 libmagickcore-6.q16hdri-2-extra - low-level image manipulation
library - extra codecs (Q16HDRI)
 libmagickcore-6.q16hdri-dev - low-level image manipulation library -
development files (Q16HDRI
 libmagickcore-dev - low-level image manipulation library -- dummy package
 libmagickwand-6-headers - image manipulation library - headers files
 libmagickwand-6.q16-2 - image manipulation library -- quantum depth Q16
 libmagickwand-6.q16-dev - image manipulation library - development files (Q16)
 libmagickwand-6.q16hdri-2 - image manipulation library -- quantum depth Q16HDRI
 libmagickwand-6.q16hdri-dev - image manipulation library -
development files (Q16HDRI)
 libmagickwand-dev - image manipulation library -- dummy package
 perlmagick - Perl interface to ImageMagick -- dummy package

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/imagemagick


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/i/imagemagick/imagemagick_6.9.6.2+dfsg-3.dsc

  Changes since the last upload:
Mainly create package for high dynamic range. No upstream code change


  Regards,
   bastien roucaries