Bug#728513: ITP: libdata-spreadpagination-perl -- page numbering and spread pagination

2013-11-02 Thread Vasudev Kamath 
Package: wnpp
Severity: wishlist
Owner: Vasudev Kamath 

* Package name: libdata-spreadpagination-perl
  Version : 0.1.2
  Upstream Author : Jody Belka 
* URL : https://metacpan.org/pod/Data::SpreadPagination
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : page numbering and spread pagination

 The object produced by Data::SpreadPagination can be used to create a
 spread pagination navigator. It inherits from Data::Page, and has
 access to all of the methods from this object.In addition, it also
 provides methods for creating a pagination spread, to allow for keeping
 the number of pagenumbers displayed within a sensible limit, but at the
 same time allowing easy navigation.The object can easily be passed to a
 templating system such as Template Toolkit or be used within a script.

 This package is dependency for libcatmandu-perl.

-- 
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4  C96B 6C8F 74AE 8770 0B7E


signature.asc
Description: Digital signature

Re: automatically cross-grading lib32nss-mdns to libnss-mdns:i386?

2013-11-02 Thread Helmut Grohne 
On Fri, Nov 01, 2013 at 01:28:59PM +, Simon McVittie wrote:
> In nss-mdns/experimental, I tried this:
> 
> Package: libnss-mdns
> Architecture: any
> Multi-Arch: same
> 
> Package: lib32nss-mdns
> Architecture: i386
> Depends: libnss-mdns (= ${binary:Version})
> Description: ... transitional package ...
> 
> hoping that apt would automatically cross-grade lib32nss-mdns:amd64 to
> lib32nss-mdns:i386, pulling in libnss-mdns:i386 as a dependency.
> However, when I installed those packages in a local apt repository and
> upgraded a VM that tracks that repository, it turns out that doesn't
> actually work.

Can you give more details on what did not work here? Maybe there is a
bug here, that can be fixed?

> I thought I remembered an announcement that cross-arch dependencies were
> OK for jessie, but I couldn't find it, so that might just be wishful
> thinking?

This was only considered for build dependencies and does not apply to
runtime dependencies.

Helmut


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131102080819.ga16...@alf.mars

Why IceApe?

2013-11-02 Thread Jeremy Morton 
I know Firefox was rebranded IceWeasel because of the problems with the 
Mozilla trademark for Firefox, but as far as I know there is no such 
trademark for SeaMonkey and if there is, it's not owned by Mozilla, it's 
owned by the SeaMonkey project.  Why, then, is it rebranded to IceApe? 
Can't Debian just distribute it as SeaMonkey?  Distributing it as IceApe 
makes it tricky to figure out how extension compatibility works between 
SeaMonkey and IceApe, and it's hard to support IceApe considering you 
could probably count the number of IceApe users on the fingers of one hand.


--
Best regards,
Jeremy Morton (Jez)


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5274de41.4020...@gmail.com

Re: Why IceApe?

2013-11-02 Thread Rémi Vanicat 
Jeremy Morton  writes:

> I know Firefox was rebranded IceWeasel because of the problems with
> the Mozilla trademark for Firefox, but as far as I know there is no
> such trademark for SeaMonkey and if there is, it's not owned by
> Mozilla, it's owned by the SeaMonkey project.  

SeaMonkey and the SeaMonkey logo are registered trademarks of the
Mozilla Foundation. (say seamonkey web site:
http://www.seamonkey-project.org/), see
http://www.seamonkey-project.org/legal/trademark for their trademarks
policy, they follow the "Mozilla Trademark Policy", and as such have the
same limitation.
-- 
Rémi Vanicat


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87habv9edl@debian.org

Re: Why IceApe?

2013-11-02 Thread Paul Tagliamonte 
On Sat, Nov 02, 2013 at 11:13:05AM +, Jeremy Morton wrote:
> I know Firefox was rebranded IceWeasel because of the problems with
> the Mozilla trademark for Firefox, but as far as I know there is no
> such trademark for SeaMonkey and if there is, it's not owned by
> Mozilla, it's owned by the SeaMonkey project.  Why, then, is it
> rebranded to IceApe? Can't Debian just distribute it as SeaMonkey?
> Distributing it as IceApe makes it tricky to figure out how
> extension compatibility works between SeaMonkey and IceApe, and it's
> hard to support IceApe considering you could probably count the
> number of IceApe users on the fingers of one hand.

Hey there Jez,

According to http://www.seamonkey-project.org/legal/trademark, it's
subject to Mozilla's trademark terms
(http://www.mozilla.org/en-US/foundation/trademarks/policy/)
which state:

 If you want to sell the product, you may do so, but you must call
 that product by another name—one unrelated to Mozilla or any of the
 Mozilla Marks

(Among a few others, originally, we had an issue with distributing
patched software)

But, it's pretty explicit this is a Mozilla mark

http://www.mozilla.org/en-US/foundation/licensing/ even says:

Our trademarks include, among others, the names Mozilla®, mozilla.org®,
Firefox®, Thunderbird®, Bugzilla™, Camino®, Sunbird®, SeaMonkey®, and
XUL™ [..]

Cheers,
  Paul


-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#728537: ITP: libtry-tiny-byclass-perl -- selectively catch exceptions by class names

2013-11-02 Thread Vasudev Kamath 
Package: wnpp
Severity: wishlist
Owner: Vasudev Kamath 

* Package name: libtry-tiny-byclass-perl
  Version : 0.01
  Upstream Author : Lukas Mai 
* URL : https://metacpan.org/pod/Try::Tiny::ByClass
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : selectively catch exceptions by class names

 This module is a simple wrapper around Try::Tiny, which see. It
 re-exports try, catch, and finally.  In addition, it provides a way to
 catch only some exceptions by filtering on the class (including
 superclasses and consumed roles) of an exception object.

 This module is dependency for libcatmandu-perl
-- 
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4  C96B 6C8F 74AE 8770 0B7E


signature.asc
Description: Digital signature

Bug#728542: ITP: libpolyclipping -- polygon clipping, polygon offsetting and polyline offsetting library

2013-11-02 Thread Bas Wijnen 
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen 

* Package name: libpolyclipping
  Version : 6.0.0
  Upstream Author : Angus Johnson 
* URL : http://sourceforge.net/projects/polyclipping
* License : GPL, BSD, MIT, Boost
  Programming Lang: C++
  Description : polygon clipping, polygon offsetting and polyline 
offsetting library

The Clipper library performs polygon clipping, polygon offsetting and polyline
offsetting. All four boolean clipping operations are supported - intersection,
union, difference and exclusive-or. Also, there are no restrictions on the
types of polygons that can be clipped - they can have holes, be
self-intersecting, have coincident edges etc.

It is written in several languages; only the C++ version is part of this
package.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131102182202.9372.31793.report...@heights-197-52.resnet.mtu.edu

Bug#728553: ITP: node-almond -- minimal AMD API implementation for use in optimized browser builds

2013-11-02 Thread Georges Khaznadar 
Package: wnpp
Severity: wishlist
Owner: Georges Khaznadar 

* Package name: node-almond
  Version : 0.2.6
  Upstream Author : James Burke 
* URL : https://github.com/jrburke/almond/archive/0.2.6.tar.gz
* License : dual BSD + MIT
  Programming Lang: Javascript
  Description : minimal AMD API implementation for use in optimized browser
builds
 Some developers like to use the AMD API to code modular JavaScript,
 but after doing an optimized build, they do not want to include a
 full AMD loader like RequireJS, since they do not need all that
 functionality.
 .
 Some use cases, like mobile, are very sensitive to file sizes.
 .
 By including almond in the built file, there is no need for
 RequireJS.  almond is around **1 kilobyte** when minified with
 Closure Compiler and gzipped.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131102202020.12162.20280.report...@georges.khaznadar.fr

Bug#728558: ITP: libterm-progressbar-simple-perl -- simple but featureful terminal progress bar

2013-11-02 Thread Florian Schlichting 
Package: wnpp
Severity: wishlist
Owner: Florian Schlichting 

* Package name: libterm-progressbar-simple-perl
  Version : 0.03
  Upstream Author : Edmund von der Burg 
* URL : https://metacpan.org/release/Term-ProgressBar-Simple
* License : GPL-1+, Artistic
  Programming Lang: Perl
  Description : simple but featureful terminal progress bar

Progress bars are handy - they tell you how much work has been done, how
much is left to do and estimate how long it will take. But they can be
fiddly! Term::ProgressBar::Simple module does the right thing in almost
all cases in a really convenient way.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2013110827.24898.35893.reportbug@thinkpad

Bug#728559: ITP: libterm-progressbar-quiet-perl -- extension to libterm-progressbar-perl to only show a progress meter if run interactively

2013-11-02 Thread Florian Schlichting 
Package: wnpp
Severity: wishlist
Owner: Florian Schlichting 

* Package name: libterm-progressbar-quiet-perl
  Version : 0.31
  Upstream Author : Leon Brocard, a...@astray.com
* URL : https://metacpan.org/release/Term-ProgressBar-Quiet
* License : GPL-1+, Artistic
  Programming Lang: Perl
  Description : extension to libterm-progressbar-perl to only show a 
progress meter if run interactively

Term::ProgressBar is a wonderful module for showing progress bars on the
terminal. Term::ProgressBar::Quiet acts very much like that module when
it is run interactively. However, when it is not run interactively (for
example, as a cron job) then it does not show the progress bar.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131102225721.32749.20682.reportbug@thinkpad

Re: Bug#727833: ITP: node-bytes -- Byte string parser and formatter - Node.js module

2013-11-02 Thread Jean-Christophe Dubacq 
Le 27/10/2013 15:37, Jérémy Lal a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: "Jérémy Lal" 
> 
> * Package name: node-bytes
>   Version : 0.2.1
>   Upstream Author : TJ Holowaychuk 
> * URL : https://github.com/visionmedia/bytes.js
> * License : Expat
>   Programming Lang: JavaScript
>   Description : Byte string parser and formatter - Node.js module
> 
> This module parses strings representing an amount of bytes, like
> 1kb, 2mb, 1gb; and inversely converts positive integers to a readable
> format representing an amount of bytes.
> It is useful for parsing or writing log files.
> .
> Node.js is an event-based server-side javascript engine.
> 
> 

I have looked at the code, and it seems to me that, again, we introduce
some code in debian that decide they can name the units any way they
like (see http://en.wikipedia.org/wiki/Binary_prefix).

They decide, for example, to use k, m and g prefixes for 2^10, 2^20 and
2^30, where usage should point to at least k, M and G and correct usage
to Ki, Mi, Gi. They also call bytes 'b' (usage is more 'B').

Of course, this is a library, it may be used to scan other (external)
data, I understand this may be part of something bigger, but:
1. This is a bad habit
2. This is bad code
3. Seriously, one package for _18_ lines of code?

Sincerely,
-- 
Jean-Christophe Dubacq



signature.asc
Description: OpenPGP digital signature

Re: Bug#727833: ITP: node-bytes -- Byte string parser and formatter - Node.js module

2013-11-02 Thread Jérémy Lal 
On 03/11/2013 00:56, Jean-Christophe Dubacq wrote:
> Le 27/10/2013 15:37, Jérémy Lal a écrit :
>> Package: wnpp
>> Severity: wishlist
>> Owner: "Jérémy Lal" 
>>
>> * Package name: node-bytes
>>   Version : 0.2.1
>>   Upstream Author : TJ Holowaychuk 
>> * URL : https://github.com/visionmedia/bytes.js
>> * License : Expat
>>   Programming Lang: JavaScript
>>   Description : Byte string parser and formatter - Node.js module
>>
>> This module parses strings representing an amount of bytes, like
>> 1kb, 2mb, 1gb; and inversely converts positive integers to a readable
>> format representing an amount of bytes.
>> It is useful for parsing or writing log files.
>> .
>> Node.js is an event-based server-side javascript engine.
>>
>>
> 
> I have looked at the code, and it seems to me that, again, we introduce
> some code in debian that decide they can name the units any way they
> like (see http://en.wikipedia.org/wiki/Binary_prefix).
> 
> They decide, for example, to use k, m and g prefixes for 2^10, 2^20 and
> 2^30, where usage should point to at least k, M and G and correct usage
> to Ki, Mi, Gi. They also call bytes 'b' (usage is more 'B').
> 
> Of course, this is a library, it may be used to scan other (external)
> data, I understand this may be part of something bigger, but:
> 1. This is a bad habit
> 2. This is bad code
> 3. Seriously, one package for _18_ lines of code?

I agree the units are wrong and will fix it, and try to make
upstream fix it too.

Jérémy.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52759917.3030...@melix.org

Bug#728563: ITP: golang-libgeoip -- Go implementation for lookups against GeoIP files

2013-11-02 Thread Tonnerre LOMBARD 
Package: wnpp
Severity: wishlist
Owner: Tonnerre LOMBARD 

* Package name: golang-libgeoip
  Version : 0.0~git20130525-1
  Upstream Author : Nikola Ranchev 
* URL : https://github.com/nranchev/go-libGeoIP
* License : BSD-3-Clause
  Programming Lang: Go
  Description : Go implementation for lookups against GeoIP files

Go library which allows to look up IP adresses in GeoIP databases. At
this point, only IPv4 lookups are supported.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131103014139.8130.83739.report...@phileas.roam.internetputzen.com