Bug#845305: ITP: txfixtures -- Twisted integration with Python test fixtures

2016-11-22 Thread Free Ekanayaka
Package: wnpp
Severity: wishlist
Owner: Free Ekanayaka 

* Package name: txfixtures
  Version : 0.1.4
  Upstream Author : Martin Pool 
* URL : https://launchpad.net/txfixtures
* License : GPL
  Programming Lang: Python
  Description : Twisted integration with Python test fixtures

The txfixtures package hooks into the Python testtools "test fixture"
interface, allowing you to write integration tests that rely on having
external Twisted service processes (or other types of service processes or
external resources in general) and possibly interact with them using
blocking APIs from test cases, that will run asynchronously in the
background.



Re: Let's stop using CVS for debian.org website

2016-11-22 Thread Laura Arjona Reina

Hi again

I've opened a bug report:

#845297: [www.debian.org] Website transition from CVS to Git
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845297

and created a wiki page:

https://wiki.debian.org/WebsiteGitTransition

Best regards

--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona



Re: OpenSSL 1.1.0

2016-11-22 Thread Antti Järvinen
Henrique de Moraes Holschuh writes:
 > The linking is fine, I believe even any eventual globals (if any) will
 > be correctly handled in Debian nowadays.  What causes extremely nasty

Someone confirm following is true: both application using 1.1 and
library (qt in my example) using 1.0 both create encryption keys, both
first call function RAND_seed(..) then is the random pool properly
initialized for both versions of the library?? I haven't looked at
internals but his kind of random pool might be easily implemented as a
global shared object. Or a separate one. Initializing the correct one
could be tricky at run-time. 

--
Antti



Bug#845327: ITP: node-shebang-regex -- Regular expression for matching a shebang line

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-shebang-regex
  Version : 2.0.0
  Upstream Author : Sindre Sorhus 
(sindresorhus.com)
* URL : https://github.com/sindresorhus/shebang-regex
* License : Expat
  Programming Lang: JavaScript
  Description : Regular expression for matching a shebang line



signature.asc
Description: OpenPGP digital signature


Bug#845329: ITP: node-pseudomap -- lot like ES6 `Map`, but without iterators

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-pseudomap
  Version : 1.0.2
  Upstream Author : Isaac Z. Schlueter  (http://blog.izs.me/)
* URL : https://github.com/isaacs/pseudomap#readme
* License : ISC
  Programming Lang: JavaScript
  Description : A thing that is a lot like ES6 `Map`, but without
iterators, for use in environments where `for..of` syntax and `Map` are
not available.



signature.asc
Description: OpenPGP digital signature


Bug#845328: ITP: node-yallist -- Yet Another Linked List

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-yallist
  Version : 2.0.0
  Upstream Author : Isaac Z. Schlueter  (http://blog.izs.me/)
* URL : https://github.com/isaacs/yallist#readme
* License : ISC
  Programming Lang: JavaScript
  Description : Yet Another Linked List



signature.asc
Description: OpenPGP digital signature


Bug#845332: ITP: casacore-data-sources -- Table of ICRF reference source coordinates for casacore

2016-11-22 Thread Ole Streicher
Package: wnpp
Severity: wishlist
Owner: Ole Streicher 
X-Debbugs-CC: debian-devel@lists.debian.org, debian-as...@lists.debian.org

* Package name: casacore-data-sources
  Version : 1 or 2
* URL : https://www.iers.org/IERS/EN/DataProducts/ICRF/icrf.html
* License : Public domain
  Description : Table of ICRF reference source coordinates for casacore

 This package contains a table with the sources that realize the
 and the International Celestial Reference Frame (ICRF), as a table for
 the use with casacore. The ICRF is now the standard reference frame
 used to define the positions of the planets (including the Earth) and
 other astronomical objects.

The package is a part of the effort taken by Benda Xu and me within the
Debian Astro team to split up the original "casacore-data" package (RFP
#761146) by data source into smaller packages which can be maintained
independently.

It is still undecided if we take ICRF1 (1998; 608 sources) or
ICRF2 (2007; 3414 sources).

The package will be maintained on our git repository under

https://anonscm.debian.org/cgit/debian-astro/packages/casacore-data-sources.git

Best regards

Ole



Re: Let's stop using CVS for debian.org website

2016-11-22 Thread Boyuan Yang
2016-11-22 18:16 GMT+08:00 Laura Arjona Reina :
> I've opened a bug report:
>
> #845297: [www.debian.org] Website transition from CVS to Git
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845297
>
> and created a wiki page:
>
> https://wiki.debian.org/WebsiteGitTransition

Looks great!

AFAIK there are some blocking issues affecting the migration of
buildsystem since it depends on CVS. The biggest piece is
Perl/Local/VCS_VCS.pm. This file needs to be rewritten completely into
something like VCS_Git.pm before we can run `make' on the top dir
without any error message.

--
Sincerely,
Boyuan Yang



Bug#845336: ITP: chasquid -- simple SMTP (email) server written in go

2016-11-22 Thread Martín Ferrari
Package: wnpp
Severity: wishlist
Owner: "Martín Ferrari" 

* Package name: chasquid
  Version : 0.1
  Upstream Author : Alberto Bertogli 
* URL : https://blitiri.com.ar/p/chasquid
* License : Apache-2.0
  Programming Lang: golang
  Description : simple SMTP (email) server written in go

chasquid is an SMTP (email) server. It aims to be easy to configure and
maintain for a small mail server, at the expense of flexibility and
functionality.
.
It's written in Go, and is open source under the Apache license 2.0.
.
It is currently in beta: it's functional and has had some production exposure,
but some things may still change in backwards-incompatible ways, including the
configuration format. It should be rare and will be avoided if possible.



Bug#845338: ITP: node-pinkie-promise -- ES2015 Promise ponyfill

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-which-module
  Version : 1.0.0
  Upstream Author : nexdrew
* URL : https://github.com/nexdrew/which-module#readme
* License : ISC
  Programming Lang: JavaScript
  Description : Find the module object for something that was require()d



signature.asc
Description: OpenPGP digital signature


Bug#845337: ITP: node-which-module -- Find the module object for something that was require()d

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-which-module
  Version : 1.0.0
  Upstream Author : nexdrew
* URL : https://github.com/nexdrew/which-module#readme
* License : ISC
  Programming Lang: JavaScript
  Description : Find the module object for something that was require()d



signature.asc
Description: OpenPGP digital signature


Bug#845341: ITP: node-get-caller-file -- Inspects the v8 stack trace

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-get-caller-file
  Version : 1.0.2
  Upstream Author : Stefan Penner
* URL : https://github.com/stefanpenner/get-caller-file#readme
* License : ISC
  Programming Lang: JavaScript
  Description : Inspects the v8 stack trace

Call this function in a another function to find out the file from
which that function was called from. (Inspects the v8 stack trace)
Inspired by http://stackoverflow.com/questions/13227489



signature.asc
Description: OpenPGP digital signature


Bug#845351: ITP: ca-dn42 -- dn42 automatic CA root certificates

2016-11-22 Thread Iain R. Learmonth
Package: wnpp
Severity: wishlist
Owner: "Iain R. Learmonth" 

* Package name: ca-dn42
  Version : 20161122.0
  Upstream Author : DN42.US Certificate Authority
* URL : https://ca.dn42.us/crt/
* License : BSD-2-clause
  Programming Lang: X.509
  Description : dn42 automatic CA root certificates

This package provides the dn42 automatic CA root certificate in PEM format.
Root certificates allow SSL-based applications to check for the
authenticity of certificates issued by the dn42 automatic CA.

Please note that these certificates are used only within the dn42 network and
do not appear on the public Internet. The root certificate has constraints
that it can only be used to sign domains ending with .dn42, and so cannot be
used to verify domains on the public Internet.

For more information on dn42, see: http://dn42.org/ or
https://en.wikipedia.org/wiki/Decentralized_network_42.



Re: Bug#845351: ITP: ca-dn42 -- dn42 automatic CA root certificates

2016-11-22 Thread Simon McVittie
On Tue, 22 Nov 2016 at 17:48:44 +, Iain R. Learmonth wrote:
> The root certificate has constraints
> that it can only be used to sign domains ending with .dn42

Does this package insert the dn42 CA into the system-wide default CA
store?

(If it does, then I think it would be necessary to tread *very*
carefully.)

Do all TLS libraries available in Debian respect those constraints?

S



Bug#845371: ITP: libdnssecjava-java -- A DNSSEC validating stub resolver for Java

2016-11-22 Thread Ingo Bauersachs
Package: wnpp
Severity: wishlist
Owner: Ingo Bauersachs 

* Package name: libdnssecjava-java
  Version : 1.1.2
  Upstream Author : Ingo Bauersachs 
* URL : https://github.com/ibauersachs/dnssecjava
* License : EPL
  Programming Lang: Java
  Description : A DNSSEC validating stub resolver for Java

dnssecjava is a small library used as a resolver on top of
dnsjava (libdnsjava-java) to validate responses with DNSSEC.

It is a dependecy of Jitsi.



Re: Certbot, Ring in Debian Stretch

2016-11-22 Thread Peter Eckersley
On Tue, Nov 22, 2016 at 08:23:59AM +0100, Daniel Pocock wrote:
> 
> I'd like to suggest an additional point relevant to all of the options: how
> well does the certbot client react when it is no longer usable?  Does the
> protocol include a mechanism to check the version?  Does the client give an
> explicit error telling the user to update the client and can it be tweaked
> so that Debian users are shown a message about getting the latest package
> from stable-backports?  Or will the user see some random error that doesn't
> mention the client version at all?
>

ACME includes an explicit versioning mechanism for inherently-breaking
protocol changes, and also a User Agent string that an be employed for
finer-grained conditional responses.

To date, we have never incremented the explicit versioning mechanism, but
there have been a couple of incompatibilities that could be characterised as
Certbot bugs which the Let's Encrypt servers initially tolerated, but
eventually stopped tolerating.

In this case: https://github.com/certbot/certbot/issues/2528 the server will
today send an error message, and buggy clients would print that error
instructing the user to upgrade Certbot and/or OpenSSL to fix the problem.
Note, however, that if Certbot is running in a renewal cron job, the sys admin
might miss that message.

In this case: https://github.com/certbot/certbot/issues/2768
the server was able to use the User Agent string to avoid sending incompatible
messages to older Certbot versions.

For cases in the future where ACME is intentionally being revised in an 
inherently
incompatible way, we would change the protocol's endpoint URI, and begin a 6-12
month compatibility window with the previous version.

In all cases we do have the option of sending email to the registered account
email addresses associated with older clients that are about to be
incompatible, provided that sys admins chose to give us an email address when
they created their Let's Encrypt accounts.


 
 

-- 
Peter Eckersleyp...@eff.org
Chief Computer Scientist  Tel  +1 415 436 9333 x131
Electronic Frontier FoundationFax  +1 415 436 9993



Bug#845389: ITP: libpgobject-type-bytestring-perl -- Wrapper for raw strings mapping to BYTEA columns

2016-11-22 Thread Robert J. Clay
Package: wnpp
Owner: Robert James Clay 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libpgobject-type-bytestring-perl
  Version : 1.1.1
  Upstream Author : Erik Huelsmann, 
  License : BSD-2-clause
  Description : PGObject::Type::ByteString - maps Perl strings into a
BYTEA field.

This module provides a wrapper for raw strings mapping to BYTEA columns


-- 
Robert James Clay
j...@rocasa.us
rjc...@gmail.com


[RFC] Enabling bindnow by default in dpkg-buildflags?

2016-11-22 Thread Guillem Jover
Hi!

This was discussed relatively recently, but it was not entirely clear
to me what was the conclusion, if there was any(?), about enabling
bindnow by default.

And although this got enabled by default in gcc-6 6.2.0-7 when PIE
also got enabled, it seems it got disabled in 6.2.0-10 when I pointed
out that enabling bindnow in gcc w/o enabling relro too didn't seem to
make much sense, but then I didn't notice any rationale for the
reversion, instead of say enabling relro too.


My mine concern is and has always been that bindnow changes the
run-time behavior (instead of the build-time one) and could break
things such as dlopen() on shared libraries or plugins and similar.
And detecting problems becomes harder, and reverting this change
iff we notice that it breaks too much might imply rebuilding an
unspecified number of packages. So in a way it feels kind of like
a transition?

OTOH Ubuntu seems to have been enabling not only PIE and bindnow by
default in gcc for a long time, but also relro, stack-protector and
fortify. Which would seem to imply this might not break that much?
(I'm not sure why we are not enabling all those in gcc in Debian
too, but that's probably a different conversation to have if at all.)


So at this point, I guess I still have concerns, but only very mild
ones, and would not mind one way or another, but would like input
from at least the release team, because I don't feel like possibly
deciding on this on my own, even more at this stage of the release.

Thanks,
Guillem



Bug#845409: ITP: node-strip-eof -- Strip the End-Of-File (EOF) character from a string/buffer

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-strip-eof
  Version : 1.0.0
  Upstream Author : Sindre Sorhus 
(sindresorhus.com)
* URL : https://github.com/sindresorhus/strip-eof
* License : Expat
  Programming Lang: JavaScript
  Description : Strip the End-Of-File (EOF) character from a
string/buffer



signature.asc
Description: OpenPGP digital signature


Bug#845410: ITP: node-shebang-command -- Get the command from a shebang

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-shebang-command
  Version : 1.2.0
  Upstream Author : Kevin Martensson 
(github.com/kevva)
* URL : https://github.com/kevva/shebang-command#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Get the command from a shebang



signature.asc
Description: OpenPGP digital signature


Bug#845411: ITP: node-mem -- Memoize functions

2016-11-22 Thread Pirate Praveen
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-mem
  Version : 1.1.0
  Upstream Author : Sindre Sorhus 
(sindresorhus.com)
* URL : https://github.com/sindresorhus/mem#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Memoize functions - An optimization used to speed up
consecutive function calls by caching the result of calls with identical
input



signature.asc
Description: OpenPGP digital signature