Re: Bug#637892: ITP: python-formalchemy -- auto-generation and customizable form

2011-08-17 Thread Shell Xu 
Sorry to bother you, but my merge has failed, and I don't know why.
I retitled this
bug(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526936 ) and make
myself as owner, but merge 526936 637892 has failed.
According this article(http://www.debian.org/Bugs/server-control#merge
), bugs which I try to merge has same state, all not marked as
forwarded, all of the same severity. But does it has assigned?
And, I almost finish my job. But which bugnumber should I fill into
changelog? The new one or both?
Thanks for help.

2011/8/17 Arnaud Fontaine :
> Hi,
>
>>   By the way, this package seems in requested packages list. here is the
>> bug. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526936
>>
>>   As a new maintainer, I'm not so  sure what need to do next, any help
>> will be appreciated.
>
> As there was already a RFP, you should have not opened a new bug[0], but
> rather retitled the  RFP to ITP and assigned you as  owner by sending an
> email to BTS control bot[1].
>
> But, considering  that you  have already opened  it, you can  merge both
> bugs[2] and that will do.
>
> Hope that helps.
>
> Regards,
> --
> Arnaud Fontaine
>
> [0] http://www.debian.org/devel/wnpp/
> [1] http://www.debian.org/Bugs/server-control
> [2] http://www.debian.org/Bugs/server-control#merge
>



--
无能者无所求，饱食而遨游，泛若不系之舟
blog: http://shell909090.com/blog/
twitter: http://twitter.com/shell909090


--
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/cadextbxtsndykfgtwaujvoo-nlyznisd281vr05afut4ivx...@mail.gmail.com

Re: Bug#637892: ITP: python-formalchemy -- auto-generation and customizable form

2011-08-17 Thread Arnaud Fontaine 
Hi,

> Sorry to bother you, but my merge has failed, and I don't know why.  I
> retitled   this
> bug(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526936 ) and make
> myself as owner, but merge 526936 637892 has failed.

No problem  at all.  As far  as I can see  on the bug  report, it worked
because it displays 'Merged with...'.

> And, I  almost finish my job.  But which bugnumber should  I fill into
> changelog? The new one or both?

Only one (any of them), as explained there[0].

Regards,
-- 
Arnaud Fontaine

[0] http://www.debian.org/Bugs/server-control#merge


pgpx4wi63WduY.pgp
Description: PGP signature

Re: mentors.debian.net runs the debexpo code now

2011-08-17 Thread Stefano Zacchiroli 
On Thu, Aug 11, 2011 at 07:03:03AM -0400, Asheesh Laroia wrote:
> Thanks to huge work by Johnny Lamb, Christoph Haas, Jan Dittberner,
> Kalle Söderman, Serafeim Zanikolas, David Paleino, and Paul Wise, we
> have had a alpha-level product called Debexpo that can replace
> mentors.debian.net as the place we do package review for new
> contributors in Debian.

> It's live: http://mentors.debian.net/

That's a great achievement!
Thanks to everyone who has contributed to make it possible.

As a minor nitpick, can you add to the footer a link to the code?

Many Debian services could benefit from more prominent footer links to
the code, to encourage "patches are welcome" habits and to make it clear
that the code for all our services is available. (yes, in this specific
case I know that the availability of debexpo code is mentioned at
http://wiki.debian.org/Debexpo , but making it more readily available
wouldn't hurt, would it?)

Cheers.
-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Quando anche i santi ti voltano le spalle, |  .  |. I've fans everywhere
ti resta John Fante -- V. Capossela ...| ..: |.. -- C. Adams


signature.asc
Description: Digital signature

Re: Bug#637892: ITP: python-formalchemy -- auto-generation and customizable form

2011-08-17 Thread Liang Guo 
On Wed, Aug 17, 2011 at 5:39 PM, Shell Xu  wrote:
> Sorry to bother you, but my merge has failed, and I don't know why.
> I retitled this
> bug(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526936 ) and make
> myself as owner, but merge 526936 637892 has failed.
> According this article(http://www.debian.org/Bugs/server-control#merge
> ), bugs which I try to merge has same state, all not marked as
> forwarded, all of the same severity. But does it has assigned?
> And, I almost finish my job. But which bugnumber should I fill into
> changelog? The new one or both?
> Thanks for help.
>
You can close both bug in debian/changelog

-- 
Liang Guo
http://bluestone.cublog.cn


-- 
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/CAJwrgW5BZ2zmEhmRp5zrSQ=hofme-j5gmypyi_oopkpumk_...@mail.gmail.com

Re: mentors.debian.net runs the debexpo code now

2011-08-17 Thread Arno Töll 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Stefano,

On 17.08.2011 12:14, Stefano Zacchiroli wrote:
> As a minor nitpick, can you add to the footer a link to the code?

thanks for the hint. We completely forgot about it, indeed. I've
added[1] the link to the templates and it will appear on the deployment
site soon(-ish).


[1]
http://anonscm.debian.org/gitweb/?p=debexpo/debexpo.git;a=commit;h=263a568427d910eb91d95a278eb469f0bdd265a3
- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOS5afAAoJEMcrUe6dgPNti0gP/2VbTz/NNDUVXWhNVzbFFWs4
v2w9Na6jBzQ3ZZdGVl+dDOP/HOv0p0BtI5kBMD+I+fv2qynvwK1kL+yBd/pNsoOA
BjFR74nfQETmICeyRJEqIIa3X7Lm5FTSe7K1k30Q3/wrmNdQ89attiat03/vnBJK
SfLYjGYmlTADDFyY034QqRmHTlj/Iej+68BbudMzQdNhz24dPXWVVwGgA9beBrns
vIMpWgzN4wmB2tKVdP6zW4cZPGRNZRYx7eW6hBeMAm6CFC8hIc5KZQ0AI5DLWu4R
RBAraqzjdyIexbdLMhiU3a4WICu6TVd+EyGaiMo0fJ/WTeKDvNrHlh9kr70caHKF
W66/5Nk9OfoRd4VIHnJ57V8JW2rr6hAw05krWx4LNrAtu74Ji3kEIE+q2YrUNS1A
nhDa2xfeI/+gYJsP8eZl2uyTWk6gxN3v9jzkM7Zg5FZyOjJDwxiHBqTUxukHqaqU
R3B115kuuuiDl2ZppRR2v2RFNLJtHL+KnkNmAh45rkSQGHd8qp9CiONtZtA5/loj
d1cK6h9qdQAh2a91KrLQC3GlVZa1rdkwib9IYTHr+WsI8u2iIkZ1/cdhcWASTVJb
qTaGAOpCDOn3E76cU7HWXXaNh2p8yj+nn/Rln1vPcP1HsZveTTuujb1Mhop0z719
l1Apne+KcXn6gdrHKCG4
=hOTt
-END PGP SIGNATURE-


-- 
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/4e4b969f.2070...@toell.net

Links to the sources for services (was Re: mentors.debian.net runs the debexpo code now)

2011-08-17 Thread Steve McIntyre 
Stefano Zacchiroli wrote:
>
>As a minor nitpick, can you add to the footer a link to the code?
>
>Many Debian services could benefit from more prominent footer links to
>the code, to encourage "patches are welcome" habits and to make it clear
>that the code for all our services is available. (yes, in this specific
>case I know that the availability of debexpo code is mentioned at
>http://wiki.debian.org/Debexpo , but making it more readily available
>wouldn't hurt, would it?)

Very good point, and something that we should push for elsewhere.

/me goes to add such a link to cdimage-search.debian.org...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver." -- Daniel Pead


-- 
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/e1qtdqd-00081k...@mail.einval.com

Re: Bug#637892: ITP: python-formalchemy -- auto-generation and customizable form

2011-08-17 Thread Luca Capello 
Hi there!

On Wed, 17 Aug 2011 11:52:47 +0200, Arnaud Fontaine wrote:
>> Sorry to bother you, but my merge has failed, and I don't know why.  I
>> retitled   this
>> bug(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526936 ) and make
>> myself as owner, but merge 526936 637892 has failed.
>
> No problem  at all.  As far  as I can see  on the bug  report, it worked
> because it displays 'Merged with...'.

No, the merge command Shell Xu issued contained a non-breaking space,
thus it did not work:

  

Then Aron Xu fixed it with a forcemerge (AFAIK not strictly needed in
this case):

  

>> And, I  almost finish my job.  But which bugnumber should  I fill into
>> changelog? The new one or both?
>
> Only one (any of them), as explained there[0].

While any of them is correct, I would say that chronologically the first
one takes precedence ;-)

Thx, bye,
Gismo / Luca


pgphpGFNGM3JE.pgp
Description: PGP signature

Re: Links to the sources for services (was Re: mentors.debian.net runs the debexpo code now)

2011-08-17 Thread Jonathan Wiltshire 
On Wed, Aug 17, 2011 at 11:32:55AM +0100, Steve McIntyre wrote:
> Stefano Zacchiroli wrote:
> >
> >As a minor nitpick, can you add to the footer a link to the code?
> >
> >Many Debian services could benefit from more prominent footer links to
> >the code, to encourage "patches are welcome" habits and to make it clear
> >that the code for all our services is available. (yes, in this specific
> >case I know that the availability of debexpo code is mentioned at
> >http://wiki.debian.org/Debexpo , but making it more readily available
> >wouldn't hurt, would it?)
> 
> Very good point, and something that we should push for elsewhere.

#638059 is open against the PTS for this; maybe it should be reassigned and
generalised.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51


signature.asc
Description: Digital signature

Re: Bug#637892: ITP: python-formalchemy -- auto-generation and customizable form

2011-08-17 Thread Adam D. Barratt 

On Wed, 17 Aug 2011 18:18:09 +0800, Liang Guo wrote:
On Wed, Aug 17, 2011 at 5:39 PM, Shell Xu  
wrote:

And, I almost finish my job. But which bugnumber should I fill into
changelog? The new one or both?
Thanks for help.


You can close both bug in debian/changelog


You can, but you'll just generate twice as much mail - the BTS will 
close A, notice that it's merged with B and close B; then it'll close B, 
notice that it's merged with A... (thankfully only to one level, rather 
than recursively).


Regards,

Adam


--
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/9793007cb00b6b25598430572e29a...@adsl.funky-badger.org

Bug#638182: less: please be more verbose about lesspipe usage in login script

2011-08-17 Thread Luca Capello 
Package: less
Version: 444-1
Severity: wishlist

Hi there!

The discussion started on the debian-devel@ mailing list:

  

On Tue, 16 Aug 2011 12:38:43 +0200, Adam Borowski wrote:
> On Tue, Aug 16, 2011 at 11:50:49AM +0200, Luca Capello wrote:
>> On Tue, 16 Aug 2011 10:08:45 +0200, Alexander Reichle-Schmehl wrote:
>> > FWIW, if you the following in your bashrc:
>> >
>> > if [ -f /usr/bin/lesspipe ]; then
>> 
>> I would use the -x expression instead ;-)
>> 
>> And I would also say that this test should be included in the
>> lesspipe(1) manpage...

Here we are.

> /etc/skel/.profile has it, commented out:

On sid it has not.  But /etc/skel/.bashrc:23 does ;-)

However, the lesspipe manpage says:

  USAGE
Just put  one of  the following two  commands in  your login
script (e.g.  ~/.bash_profile):

  eval "$(lessfile)"

or

  eval "$(lesspipe)"

I think the manpage should:

1) document the full snippet above as the one to be put in login script,
   i.e. with the test as well.

2) be consistent with what Debian ships in /etc/skel/ files, i.e. if the
   snippet is in .bashrc, the manpage should reflect that and not
   suggest .bash_profile.

> # make less more friendly for non-text input files, see lesspipe(1)
> #[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

I do not understand why we need to specify SHELL, however.

Thx, bye,
Gismo / Luca

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages less depends on:
ii  debianutils   4.0.2  Miscellaneous utilities specific t
ii  libc6 2.13-16Embedded GNU C Library: Shared lib
ii  libncurses5   5.9-1  shared libraries for terminal hand

less recommends no packages.

less suggests no packages.

-- no debconf information


pgpY3sNLUYzNf.pgp
Description: PGP signature

Re: mentors.debian.net runs the debexpo code now

2011-08-17 Thread Jeremiah Foster 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


On Aug 17, 2011, at 12:14, Stefano Zacchiroli wrote:

> On Thu, Aug 11, 2011 at 07:03:03AM -0400, Asheesh Laroia wrote:
>> Thanks to huge work by Johnny Lamb, Christoph Haas, Jan Dittberner,
>> Kalle Söderman, Serafeim Zanikolas, David Paleino, and Paul Wise, we
>> have had a alpha-level product called Debexpo that can replace
>> mentors.debian.net as the place we do package review for new
>> contributors in Debian.
> 
>> It's live: http://mentors.debian.net/
> 
> That's a great achievement!
> Thanks to everyone who has contributed to make it possible.
> 
> As a minor nitpick, can you add to the footer a link to the code?
> 
> Many Debian services could benefit from more prominent footer links to
> the code, to encourage "patches are welcome" habits and to make it clear
> that the code for all our services is available. (yes, in this specific
> case I know that the availability of debexpo code is mentioned at
> http://wiki.debian.org/Debexpo , but making it more readily available
> wouldn't hurt, would it?)

Excellent point zack, there is a lot of really great tooling in Debian and 
people saw links to code in the footer of various tools they would likely want 
to start using it in their projects, hopefully improving it in the process.

Regards,

Jeremiah
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)

iQIcBAEBAgAGBQJOS7nnAAoJEPoEpn8G2KIrxK4P/iGxibx2FhF5lZPG2bVgAPYh
QirjkNUdULI31qZICGixRqG+VbF4AlFD+TVzlqLJcbpEXwgqyHVSdKE1xBMyVjWS
9zn8R/lA7AeYa3Lq+tdJhlMlJycpm5QvrUgpmxZgMlK1aFTMU8Ul2E3LDHHGNyKA
kj3cTLqy6vj+Br0SaF8uzzxpZ+nVgwsFHFZdJ8YkmkVbVZpHnLEa0d7DYoyShibB
/rKSC0BVjwfTl2H7b/V2H1x2HA8WclNRNZSqpgF5ysMudr8kW/s7ICDqWvUEgBEl
cLFP0RkylHYToonFkjah4AzMhweb1V0aF5pj7to/ShvEjXO/ulLlwb+rC1Nideo7
6bg0TbNjYOXPFRYX8RZSerM3r5q9GYGXzGOA84QeLKKeE8lv8Y5LgZPffLSfslzE
x0l+Vor3iGnnUlcrgDUitQahPdPj9hfwuptKGKya3VeWDN8tdMYESDSKYeR3/cl9
DDdcPIvamdNUc46kMCjeg3lIessGxXIN/m9Ms+GCAARicpVRF0Mdv3ShNXXhj0bi
XqcZ4O+nGy8axicKAN9vGAVBPN1vhmXSj3+e7BGZn3lm3tc+z2fMGKdompSfqT4z
SD3bdOqzfqaSiOF9Ha30O0VMnVV0j/LAwiUoMDZgBQFb23KAEgo+rmQArQQ/yQrZ
6ls71DhPljmxuiF41xbV
=gGD2
-END PGP SIGNATURE-


--
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/8653b812-3516-4f47-8a69-19956de8d...@jeremiahfoster.com

Re: RFC: dpatch - past, present and future

2011-08-17 Thread Gergely Nagy 
Stefano Zacchiroli  writes:

> On Tue, Aug 16, 2011 at 10:54:30PM +0200, Gergely Nagy wrote:
>> I don't want to make it spew out deprecation warnings, those are too
>> tempting to ignore. Updating the description, filing wishlist bugs with
>> patches, and providing upgrade paths for the most common cases is The
>> Plan. Along with an entry in debian/NEWS.
>
> Sure, deprecation warning are tempting to ignore. But, in addition to
> the other means you've mentioned, what harm do they do? (Purposefully
> ignoring the harm of bothering whoever reads the build log, as that kind
> of "harm" is pretty much the point of any deprecation warning.)

Simply put: I hate them. Documentation is there to be read, debian/NEWS
included. If one cannot be bothered to do that, to keep up with the
rushing pace of dpatch development, bugs will be filed eventually, and
they'll notice.

And since bugs - hopefully most of them with patches - will be filed
regardless, I do not see the point in adding more noise. It doesn't save
work for anyone but me (and I do not mind going an extra mile to avoid
the deprecation warnings), but creates noise for everyone who happens to
read build logs of a dpatch using package. Potentially for readers who
couldn't care less about the packaging, either (which, I believe, would
be most of the readers).

On the other hand, adding deprecation warnings properly to dpatch isn't
as easy as a few lines, unless I want it very spammy (which I don't), so
in the long run, I'd rather spend a day more on creating patches for
dpatch->quilt conversion than spend an hour adding the deprecation
warnings.

But as always, patches are welcome! ;)

-- 
|8]


-- 
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/877h6cm92m@balabit.hu

Re: RFC: dpatch - past, present and future

2011-08-17 Thread Guillem Jover 
Hi!

On Tue, 2011-08-16 at 22:33:55 +0200, Raphael Hertzog wrote:
> On Tue, 16 Aug 2011, Gergely Nagy wrote:
> > As for the future: I still believe dpatch is a temporary solution, and
> > that better tools exist now. Therefore, it is my long-term plan to
> > slowly deprecate dpatch, and eventually make it gracefully leave the
> > archive.
> 
> How do you plan to do this?

[...]

> But if your goal is really to get rid of it, you could just as well file
> wishlist bugs on all packages build-depending on it, usertag them and
> increase their severity slowly. Wishlist for now, normal in the next
> release cycle and important/RC in the cycle where you want to drop it?

> FWIW, we managed to get rid of 2/3 of dbs build-dependencies by filing such 
> bugs:
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=hert...@debian.org;tag=drop-dbs

Given there's at least around 800 source packages (as Gergely pointed
out, and checking for embedded dpatch in source might reveal some more
maybe). I think filing bug reports for these right now would be too
much, and I'd propose to add a lintian check first, and wait until the
numbers decrease substantially before filing them.

regards,
guillem


-- 
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/20110817141407.ga12...@gaara.hadrons.org

Re: RFC: dpatch - past, present and future

2011-08-17 Thread Gergely Nagy 
Guillem Jover  writes:

>> But if your goal is really to get rid of it, you could just as well file
>> wishlist bugs on all packages build-depending on it, usertag them and
>> increase their severity slowly. Wishlist for now, normal in the next
>> release cycle and important/RC in the cycle where you want to drop it?
>
>> FWIW, we managed to get rid of 2/3 of dbs build-dependencies by filing such 
>> bugs:
>> http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=hert...@debian.org;tag=drop-dbs
>
> Given there's at least around 800 source packages (as Gergely pointed
> out, and checking for embedded dpatch in source might reveal some more
> maybe). I think filing bug reports for these right now would be too
> much, and I'd propose to add a lintian check first, and wait until the
> numbers decrease substantially before filing them.

Since I plan to phase out dpatch by 2017, there's plenty of time to file
those ~800 wishlist bugs. I'm not worried. This gives me plenty of time
to get it done without spamming the BTS. About 3 bugs a week on average
sounds low profile enough, and it's comfortably low enough to allow me
to actually do the patches properly.

I'm not entirely sold on the lintian check idea, either, but that might
be my lack of tea today. (Update, after a cup of tea: I'll send a patch
against lintian once 2.0.32 is uploaded to unstable.)

As for embedded dpatch: that's usually something very different to what
is currently packaged as dpatch. I do not wish to care about that, and
as such, is not and will not be included in my removal plans. (However,
if someone takes up the task, so much the better! It just won't be me.)

-- 
|8]


-- 
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/87y5ysksgv@balabit.hu

Re: RFC: dpatch - past, present and future

2011-08-17 Thread Osamu Aoki 
On Tue, Aug 16, 2011 at 11:10:06PM +0200, Gergely Nagy wrote:
> Sandro Tosi  writes:
> > there's already: /usr/share/doc/quilt/examples/dpatch2quilt.sh
> 
> Well then, that just makes it all the easier! I'll take a look, and see
> if there are any cases that script can't handle.

You amy want to check #581186
 http://bugs.debian.org/581186

This updated script is compatible with new 
 QUILT_PATCH_OPTS="--reject-format=unified"

Following formats are auto detected.

#   * dh_quilt_patch/dh_quilt_unpatch
#   * dpatch
#   * cdbs (simple-patchsys.mk)
#   * dbs  (dbs-build.mk)

Osamu


-- 
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/20110817163324.ga6...@debian.org

Bug#638230: ITP: elki -- ELKI Data mining algorithm development framework

2011-08-17 Thread Erich Schubert 
Package: wnpp
Severity: wishlist
Owner: Erich Schubert 

* Package name: elki
  Version : 0.4.0~beta1
  Upstream Author : ELKI Development Team 
* URL : http://elki.dbs.ifi.lmu.de/
* License : AGPLv3+
  Programming Lang: Java
  Description : ELKI Data mining algorithm development framework

ELKI is a development framework for data mining algorithms written in Java.
It includes a large variety of popular data mining algorithms, distance
functions and index structures.

Its focus is particularly on clustering and outlier detection methods, in
contrast to many other data mining toolkits that focus on classification.

This package also includes the source code, since this software is meant
for the development of such algorithms, not so much for end users.



-- 
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/20110817212159.13338.79811.reportbug@localhost.localdomain

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-17 Thread Wouter Verhelst 
On Tue, Aug 16, 2011 at 10:43:04AM +1000, Russell Coker wrote:
> On Tue, 16 Aug 2011, Iustin Pop  wrote:
> > There is also information on Wikipedia about various compression
> > benchmarks, but IMHO if we want to switch from gzip then bzip2
> > doesn't make sense for /usr/share/doc.
> 
> I'd like to see zless work transparently with bzip and xz compressed files.
> There's really no need for three different wrapper programs when the zless
> program can just consult the magic db to determine which decompression
> program to use.

I'd like to see _less_ work transparently with bzip and xz compressed
files, too. It's not impossible, I've seen it done on default RedHat
installations.

-- 
The volume of a pizza of thickness a and radius z can be described by
the following formula:

pi zz a


-- 
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/20110817220300.go9...@grep.be