Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-cornice
Version : 0.13
Upstream Author : Alexis Metaireau
* URL : https://github.com/mozilla-services/cornice
* License : Mozilla Public License 2.0 (MPL 2.0)
Programming Lang: Pyt
Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu
* Package name: ruby-nfc
Version : 3.0.0
Upstream Author : Aaron Patterson
* URL : https://github.com/tenderlove/nfc
* License : MIT/X
Programming Lang: C, Ruby
Description : ruby wrapper for th
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg
* Package name: jatl
Version : 0.2.2
Upstream Author : Adam Gent
* URL : http://code.google.com/p/jatl/
* License : Apache-2.0
Programming Lang: Java
Description : Java Anti-Template Language
JATL
Hello All,
I did not expected to initial such a thread: thanks a lot for all the messages
On 02/10/13 20:24, David Prévot wrote:
> Hi,
>
>> Wookey (2013-10-02):
>
>>> It would be good if this 0~ trick
>>> was mentioned there too
>
> Already in the New Maintainers' Guide:
>
> http://www.debia
Him
Julien Cristau wrote:
> On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> > Yesterday I tried to setup a sparc64 chroot on a second disc in one of
> > my Sparcs, but the currently documented way[1] to do so failed[2] due
> > to outdated packages. On a first glance it looks like mis
Package: wnpp
Severity: wishlist
Owner: "Jérémy Lal"
* Package name: node-multiparty
Version : 2.1.8
Upstream Author : Andrew Kelley
* URL : https://github.com/superjoe30/node-multiparty
* License : Expat
Programming Lang: JavaScript
Description : Mult
On Wed, Oct 02, 2013 at 12:56:51PM +0100, Jonathan Dowland wrote:
> On Mon, Sep 30, 2013 at 09:22:06PM +, Bill Allombert wrote:
> > We should add official support for ppc64 and maybe sparc64 at least for use
> > as a multiarch extension to ppc/sparc, even if we do not have time to make
> > a f
Jerome BENOIT writes:
> I am packaging a versionless library software maintained via a
> mercurial repository. Is there any custom for this case ?
I have had a surprising rate of success simply asking upstream to make
versioned release tarballs, or at least VCS tags for release versions.
--
\
Hi.
On 02/10/13 12:56, Jonathan Dowland wrote:
> Actually I wonder how many 32 bit powerpc
> users there are compared to 64 bit. IN the mac world, I'd wager
> more G4s than G5s (the mac pro or xserves), not sure about other
> powerpc worlds.
Maybe these figures from popcon are indicative; it see
Package: wnpp
Severity: wishlist
Owner: Florian Schlichting
* Package name: libpath-isdev-perl
Version : 0.4.0
Upstream Author : Kent Fredric
* URL : https://metacpan.org/release/Path-IsDev
* License : GPL-1+, Artistic
Programming Lang: Perl
Description
Package: wnpp
Severity: wishlist
Owner: Florian Schlichting
* Package name: libpath-finddev-perl
Version : 0.4.0
Upstream Author : Kent Fredric
* URL : https://metacpan.org/release/Path-FindDev
* License : GPL-1+, Artistic
Programming Lang: Perl
Descriptio
Hi,
> Wookey (2013-10-02):
>> It would be good if this 0~ trick
>> was mentioned there too
Already in the New Maintainers' Guide:
http://www.debian.org/doc/manuals/maint-guide/first#namever
Regards
David, kinda ashamed to add a message to that longish nitpicking thread
signature.asc
Des
On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> Yesterday I tried to setup a sparc64 chroot on a second disc in one of
> my Sparcs, but the currently documented way[1] to do so failed[2] due
> to outdated packages. On a first glance it looks like missing BinNMUs
> for the Perl 5.14 t
This is a fork of code in the package available currently. As far as I
can tell this one is being actively worked on but the other is not. A
little background, my primary motivation for wanting this package is
that it the newest upstream of w3af requires it as a dependency.
http://packages.deb
Daniel Wozniak wrote:
>On 10/02/2013 05:11 AM, Scott Kitterman wrote:
>> On Wednesday, October 02, 2013 08:50:31 Daniel Wozniak wrote:
>>> Package: wnpp
>>> Severity: wishlist
>>> Owner: Daniel Wozniak
>>>
>>> * Package name: python-clamd
>>>Version : 1.0.1
>>>Upstream Autho
On Wed, 02 Oct 2013, Jakub Wilk wrote:
> * Don Armstrong , 2013-10-01, 17:10:
> >The avatars are now fully federated, and all caching and retrieval
> >is now done from debian.org resources, which should mitigate the
> >privacy concerns.
>
> Iceweasel users who want to mitigate the annoyance can pu
Le mardi, 1 octobre 2013 23.45:53 Thomas Goirand a écrit :
> On 10/01/2013 10:02 PM, Jonathan Dowland wrote:
> > Ask ftp masters to reject the package and re-upload with the source
> > package renamed to have an openstack prefix/suffix/infix.
>
> Thanks but no thanks. I need to have the python nam
I'm interesting in helping on ia64. I'm not fluent in ia64 assembly, but I
can get around pretty well. I'm very experienced in C/C++/Java and
debugging. I've got a fully functional system running Xorg/Mesa3D/sound, so
I can reproduce, test, and fix issues as time permits.
Patrick Baggett
On Wed,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>A packager is not required to serve users with such specific needs.
Hmm, I last saw that attitude when being explained "the Arch way".
I established an advantage for the user using my proposal - go get me a
disadvantage for the packager.
That sa
Quoting Dominik George (2013-10-02 16:39:09)
> Wookey schrieb:
>>+++ Dominik George [2013-10-02 16:23 +0200]:
>>>
0~MMDD
should be fine.
>>>
>>> It isn't, it is not a unique identifier for the one "release" you
>>> are packaging.
>>
>> No, but it can be a sufficient identifier s
Hello, all.
I am not currently a porter but I would like to be one for the s390x
architecture.
I am familiar with zSeries system programming and have a lot of
experience in running Linux in virtual environments, mostly z/VM on
large IBM processors.. I use Linux for 11 year, family with cross
co
On Wednesday 02 October 2013 17:31:02 Andrew Shadura wrote:
> > dpkg --compare-versions 1.hg2012 '<=' 1.git2013 || echo 'false'
>
> Weren't we talking about 0~20131002.hg2efc4fcd vs 0~20131002.git67ed491a?
Sorry, I confused between Jerome original mail
e issue. Try that:
> dpkg --compare-versions 1.hg2012 '<=' 1.git2013 || echo 'false'
Weren't we talking about 0~20131002.hg2efc4fcd vs 0~20131002.git67ed491a?
--
WBR, Andrew
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of &q
On Wednesday 02 October 2013 16:51:09 Dominik George wrote:
> >well, you proposed a version like 'hg'. if upstream switches to
> >git, you
> >can't use a version like 'git' because it sorts before hg. I grant
> >you
> >that is easy to work around.
>
> If you deem it unlikely that two commi
On Wed, Oct 02, 2013 at 04:07:25PM +0100, Wookey wrote:
>+++ Niels Thykier [2013-10-02 09:45 +0200]:
>> Hi,
>>
>> The final results are in:
>>
>> Summary table:
>> Arch || DDs || NMs/DMs || Other || Total
>> ---++-++-++---++--
>> armel || 3 ||
+++ Niels Thykier [2013-10-02 09:45 +0200]:
> Hi,
>
> The final results are in:
>
> Summary table:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
> armel || 3 || 0 || 1 ||4
> armhf || 3 || 1 ||
Wookey (2013-10-02):
> The 'use an ISO date as version' idea comes from advice in the
> developer packaging docs somewhere. It would be good if this 0~ trick
> was mentioned there too so one could decide whether to use it or not
> at the time of initial packaging.
http://www.debian.org/doc/debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dominique Dumont schrieb:
>On Wednesday 02 October 2013 16:05:18 Dominik George wrote:
>> >You should use a version derived from the date only. This way, you
>> >won't be in
>> >trouble if upstream switches to git.
>>
>> I absolutely do not see wh
Wookey wrote:
>+++ Dominik George [2013-10-02 15:49 +0200]:
>> Jerome BENOIT schrieb:
>> >Hello,
>> >
>> >I am packaging a versionless library software maintained via a
>> >mercurial repository.
>> >Is there any custom for this case ?
>
>> I tend to use:
>>
>> 0~MMDD+hgXX
>>
>> It sorts
On Wednesday 02 October 2013 16:05:18 Dominik George wrote:
> >You should use a version derived from the date only. This way, you
> >won't be in
> >trouble if upstream switches to git.
>
> I absolutely do not see why this should be an issue.
well, you proposed a version like 'hg'. if upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Wookey schrieb:
>+++ Dominik George [2013-10-02 16:23 +0200]:
>>
>> >0~MMDD
>> >
>> >should be fine.
>>
>> It isn't, it is not a unique identifier for the one "release" you are
>packaging.
>
>No, but it can be a sufficient identifier so long a
+++ Dominik George [2013-10-02 16:23 +0200]:
>
> >0~MMDD
> >
> >should be fine.
>
> It isn't, it is not a unique identifier for the one "release" you are
> packaging.
No, but it can be a sufficient identifier so long as you don't make more
than one release a day.
Which exact tag/branch/has
+++ Dominik George [2013-10-02 15:49 +0200]:
> Jerome BENOIT schrieb:
> >Hello,
> >
> >I am packaging a versionless library software maintained via a
> >mercurial repository.
> >Is there any custom for this case ?
> I tend to use:
>
> 0~MMDD+hgXX
>
> It sorts just below anything upstrea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>0~MMDD
>
>should be fine.
It isn't, it is not a unique identifier for the one "release" you are packaging.
- -nik
-BEGIN PGP SIGNATURE-
Version: APG v1.0.8-fdroid
iQFNBAEBCgA3BQJSTCxtMBxEb21pbmlrIEdlb3JnZSAobW9iaWxlIGtleSkgPG5p
a0BuYX
Hello,
On 02/10/13 16:05, Dominik George wrote:
> Hi,
>
>> What does 'XX' stand for ?
>
> The short commit hash, as proposed in your initial mail.
In my first email, what you read as a commit hash was meant to be the date.
To summarise:
0~MMDD
should be fine.
Thanks,
Jerome
>
>> Y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
>What does 'XX' stand for ?
The short commit hash, as proposed in your initial mail.
>You should use a version derived from the date only. This way, you
>won't be in
>trouble if upstream switches to git.
I absolutely do not see why this s
Hi Nik,
thanks for your quick reply.
On 02/10/13 15:49, Dominik George wrote:
>
>
> Jerome BENOIT schrieb:
>> Hello,
>
>> I am packaging a versionless library software maintained via a
>> mercurial repository.
>> Is there any custom for this case ?
>> If not, can we use the version format 'hg
On Wednesday 02 October 2013 15:21:48 Jerome BENOIT wrote:
> I am packaging a versionless library software maintained via a mercurial
> repository. Is there any custom for this case ?
> If not, can we use the version format 'hgMMDD' ?
As a user, I don't care about upstream repo.
You should u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Jerome BENOIT schrieb:
>Hello,
>
>I am packaging a versionless library software maintained via a
>mercurial repository.
>Is there any custom for this case ?
>If not, can we use the version format 'hgMMDD' ?
>
>
>Best regards,
>Jerome
I tend t
Hello,
I am packaging a versionless library software maintained via a mercurial
repository.
Is there any custom for this case ?
If not, can we use the version format 'hgMMDD' ?
Best regards,
Jerome
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsu
On Wed, Oct 02, 2013 at 02:17:31PM +0200, Jonas Smedegaard wrote:
> Quoting Jonathan Dowland (2013-10-02 13:51:06)
> > On a related note, I idly wonder whether anyone is interested
> > in an official ARMv6 hf port. The rpi community is massive.
> > To be clear I'm not volunteering to be involved, m
Add me for armel.
Bastien
Le 2 oct. 2013 09:46, "Niels Thykier" a écrit :
> Hi,
>
> The final results are in:
>
> Summary table:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
> armel || 3 || 0 || 1 ||4
> armhf
Quoting Jonathan Dowland (2013-10-02 13:51:06)
> On a related note, I idly wonder whether anyone is interested
> in an official ARMv6 hf port. The rpi community is massive.
> To be clear I'm not volunteering to be involved, merely curious.
Are you aware of any other hardware that would benefit fro
On Wednesday, October 02, 2013 08:50:31 Daniel Wozniak wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Daniel Wozniak
>
> * Package name: python-clamd
> Version : 1.0.1
> Upstream Author : Thomas Grainger
> * URL : https://github.com/orvant/debian-python-clamd
>
On Mon, Sep 30, 2013 at 09:22:06PM +, Bill Allombert wrote:
> We should add official support for ppc64 and maybe sparc64 at least for use
> as a multiarch extension to ppc/sparc, even if we do not have time to make a
> full
> port. Otherwise the introduction of multiarch will likely result in
On a related note, I idly wonder whether anyone is interested
in an official ARMv6 hf port. The rpi community is massive.
To be clear I'm not volunteering to be involved, merely curious.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
Package: wnpp
Severity: wishlist
Owner: Sebastian Ramacher
* Package name: isrcsubmit
Version : 2.0.0-beta.4
Upstream Author : Jonny Dewender
* URL : http://jonnyjd.github.io/musicbrainz-isrcsubmit/
* License : GPL-3+
Programming Lang: Python
Description
On Wed, Oct 02, 2013 at 04:18:58PM +0800, Paul Wise wrote:
> On Wed, Oct 2, 2013 at 3:45 PM, Niels Thykier wrote:
> > The final results are in:
> >
> > Summary table:
> > Arch || DDs || NMs/DMs || Other || Total
> > ---++-++-++---++--
> > armel ||
Hi,
[I've replaced debian-ports with debian-sparc in the recipients list]
Niels Thykier wrote:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
[…]
> sparc[2] || 1 || 0 || 0 ||1
[…]
> [2] By the looks of it, if sparc w
On Wed, Oct 2, 2013 at 4:58 PM, Sune Vuorela wrote:
> Next up I guess is finding a way to have DSA setting up something to
> host avatars for @debian.org addresses. hint hint :)
I guess they would want to replace the current db.debian.org code with ud first:
https://github.com/LucaFilipozzi/ud/
Package: wnpp
Severity: wishlist
Owner: Daniel Wozniak
* Package name: python-clamd
Version : 1.0.1
Upstream Author : Thomas Grainger
* URL : https://github.com/orvant/debian-python-clamd
* License : LGPL
Programming Lang: Python
Description : clamd is
On 10/02/2013 09:45, Niels Thykier wrote:
> Summary table:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
[...]
> sparc[2] || 1 || 0 || 0 ||1
>
> [2] By the looks of it, if sparc was replaced by sparc64, we could be
>
On 2013-10-02, Don Armstrong wrote:
> The avatars are now fully federated, and all caching and retrieval is
Yay!
> Anyone who wants to set up their own
> http://wiki.libravatar.org/running_your_own/, or you can use libravatar
> or gravatar if you do not wish to do so (or you can do nothing, and
On Tue, Oct 01, 2013 at 10:46:38PM +0800, Thomas Goirand wrote:
> Well, you have included in your "36 ITP" the 22 packages which have
> already passed the NEW queue...
So I did. I figured it was too simple to be right ☺ I'm glad that the
figure is much lower.
> Though, I agree with you, I could o
* Don Armstrong , 2013-10-01, 17:10:
The avatars are now fully federated, and all caching and retrieval is now
done from debian.org resources, which should mitigate the privacy concerns.
Iceweasel users who want to mitigate the annoyance can put this snippet into
their ~/.mozilla/firefox/*/chr
On Wed, Oct 2, 2013 at 3:45 PM, Niels Thykier wrote:
> The final results are in:
>
> Summary table:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
> armel || 3 || 0 || 1 ||4
> armhf || 3 || 1 ||
Hi,
The final results are in:
Summary table:
Arch || DDs || NMs/DMs || Other || Total
---++-++-++---++--
armel || 3 || 0 || 1 ||4
armhf || 3 || 1 || 2 ||6
hurd-i386 || 5 || 0 || 3 ||8
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: kivy
Version: 1.7.2
Upstream Author: The kivy authors
URL: http://kivy.org
License: MIT
Description: Open source Python library for rapid development of
applications that m
58 matches
Mail list logo
