[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#766833: marked as done (RFS: fuzzylite/5.0+dfsg-1 [ITP])

Your message dated Tue, 4 Nov 2014 23:02:39 +0100
with message-id <20141104230239.1ef82235@heffalump.sk2.org>
and subject line Re: RFS: fuzzylite/5.0+dfsg-1 [ITP]
has caused the Debian Bug report #766833,
regarding RFS: fuzzylite/5.0+dfsg-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
766833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766833
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests

Dear mentors,

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

 * Package name    : fuzzylite
   Version         : 5.0+dfsg-1
   Upstream Author : Juan Rada-Vilela
 * URL             : http://www.fuzzylite.com/cpp/
 * License         : LGPL3
   Section         : misc

It builds those binary packages:

 fuzzylite  - fuzzy logic control binary
 libfuzzylite-dev - fuzzy logic control development headers
 libfuzzylite5.0 - fuzzy logic control shared library

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

http://mentors.debian.net/package/fuzzylite

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

  dget -x http://mentors.debian.net/debian/pool/main/f/fuzzylite/fuzzylite_5.0+dfsg-1.dsc

I'm CC-ing the Debian Games list because fuzzylite is required for
packaging vcmi, a free reimplementation of Heroes of Might and Magic 3.
See ITP #742077.

Vcmi includes an ancient copy of fuzzylite with custom patches. To make
vcmi fit for Debian, the embedded copy of fuzzylite has to be removed.
Unfortunately, the fuzzylite API changed considerably between 2012 and
now. Thus, porting vcmi to current fuzzylite 5.0 is a non-trivial
effort.

Luckily, Juan Rada-Vilela, the author of fuzzylite volunteered to do
this porting task because he is interested in getting fuzzylite into
Debian and he wishes to see more users of his library. I now forwarded
his work to vcmi upstream and they say they will try to get fuzzylite
5.0 support into their next release.

With this development I'm now looking for sponsors for fuzzylite 5.0.
Having it in Debian is an important step to convince vcmi upstream to
remove their embedded copy. To quote "Not much point in doing this until
at least some of somewhat popular distros will have their own copy of
fuzzylite" (http://bugs.vcmi.eu/view.php?id=1886)

It would be great to find a sponsor for my package and get that and vcmi
into Debian because Heroes of Might and Magic is a fantastic game and
vcmi not only makes its engine free as in freedom but also adds tons of
additional features such as modding capabilities to the engine.

Thanks!

cheers, josch

--- End Message ---
--- Begin Message --- 
Hi Johannes,

On Tue, 04 Nov 2014 07:07:05 +0100, Johannes Schauer <j.schauer@email.de>
wrote:
> Quoting Stephen Kitt (2014-11-04 00:41:57)
> > I've taken a look at the package and it seems fine, apart from the two
> > points remaining from your exchanges with Jakub:
> > 
> > * the hard-coded paths in src/Console.cpp
> > * the spelling/grammar errors
> > 
> > Regarding the latter, I prefer "... method `static bar` was made `virtual
> > foo::bar`, which allows it to be overridden".
> 
> Oh sorry, I already submitted a patch to upstream which says:
> 
>     Its method `static tsukamoto()` was moved to `virtual
> WeightedDefuzzifier::tsukamoto()`, which allows overriding it
> 
> And upstream already applied it.
> https://github.com/fuzzylite/fuzzylite/pull/11
> 
> Is the grammar still wrong and should I prepare another pull request?

No, both variants were grammatically OK, I was just stating my preference in
case nothing had been decided yet.

> (plus, of course fix this in the packaging until the next upstream release)

Indeed!

> > Do you have any idea what should be done about the former?
> 
> The result of the former is, that two possible but undocumented commandline
> arguments of the fuzzylite binary do not work and instead produce an error
> that they cannot find some files.
> 
> Upstream's opinion is, that this functionality is not something that is
> intended to be used by anybody but them:
> 
> https://github.com/fuzzylite/fuzzylite/issues/10
> 
> I see two ways to go forward:
> 
>  1) We accept that the two commandline arguments that are not working are
>     neither found in the --help output of the binary nor in the man page I
>     wrote, so it's unlikely the user will ever run them except if they read
> the source code. The solution would thus be ignoring the issue.
> 
>  2) Make a quick patch which removes those two option from the commandline
>     interface
> 
> I'm inclined to do the former, because I see little difference between the
> program failing because "there is no such commandline argument" and the
> program failing because "you are not upstream" because the chances that the
> user will ever have this problem go towards zero as neither of those two
> non-working options are documented anywhere but the source code itself.
> 
> What do you think?

I agree with you, so I'm uploading fuzzylite as I write this!

Thanks for your work,

Stephen

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: