Am Donnerstag, den 04.03.2010, 00:06 +0800 schrieb Wen-Yen Chuang:
Dear mentors,
I am looking for a sponsor for the new version 0.78-1
of my package fpm2. (Programming language: C)
Uploaded, thanks a lot for your contribution.
Regards,
Tobias
--
Tobias Quathamer | The only problem with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.78-1
of my package fpm2. (Programming language: C)
It builds the binary package: fpm2
The package is lintian clean.
The package fixes a wishlist bug (see below).
fpm2 (0.78-1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.77-1
of my package fpm2. (Programming language: C)
It builds the binary package: fpm2
The package is lintian clean.
fpm2 (0.77-1) unstable; urgency=low
.
* New upstream release
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.76.1-1
of my package fpm2. (Programming language: C)
The package is lintian clean.
It builds the binary package: fpm2
The upload would fix 3 minor bugs which is listed below.
fpm2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.76.1-1
of my package fpm2. (Programming language: C)
It builds the binary package: fpm2
The upload would fix 3 minor bugs which is listed below.
fpm2 (0.76.1-1) unstable; urgency=low
.
Hello,
On Thu, May 14, 2009 at 18:21, Wen-Yen Chuang ca...@calno.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.75-1
of my package fpm2.
The upload would fix those bugs:
#516196 Blowfish selftest failed: At startup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.75-1
of my package fpm2.
The upload would fix those bugs:
#516196 Blowfish selftest failed: At startup password prompt.
Please try again.
Severity: important
#493317 DEFAULTS is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.75-1
of my package fpm2.
The upload would fix those bugs:
#516196 Blowfish selftest failed: At startup password prompt.
Please try again.
Severity: important
#493317 DEFAULTS is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.75-1
of my package fpm2.
The upload would fix those bugs:
#516196 Blowfish selftest failed: At startup password prompt.
Please try again.
Severity: important
#493317 DEFAULTS is
OoO Lors de la soirée naissante du mardi 08 juillet 2008, vers 17:06,
Wen-Yen Chuang [EMAIL PROTECTED] disait :
Dear mentors,
I am looking for a sponsor for the new version 0.72-1 of
my package fpm2.
Hi!
I have just uploaded your new version.
--
LOOSE TEETH DON'T NEED MY HELP
LOOSE TEETH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 0.72-1 of
my package fpm2.
It is lintian clean.
This new upstream release fixes following bugs:
~ * provide using current category as default (Closes: #239564)
~ * fix a double-click bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Bernat wrote:
Why not 0.71 ?
Done.
Conflicts: fpm ( 0.71)
Replaces: fpm ( 0.71)
Provides: fpm
And you may want to call it transition package instead of
metapackage.
Done.
Description: a password manager - transitional
OoO En ce doux début de matinée du vendredi 09 mai 2008, vers 08:40,
Wen-Yen Chuang [EMAIL PROTECTED] disait:
The updated package can be found on mentors.debian.net:
- dget
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Bernat wrote:
I don't know why it has not been spotted earlier by lintian, but there
is the following warning:
I: fpm2: desktop-entry-contains-encoding-key
/usr/share/applications/fpm2.deskto
Done.
I guess your lintian is newer than
OoO En cette fin de matinée radieuse du vendredi 09 mai 2008, vers
11:21, Wen-Yen Chuang [EMAIL PROTECTED] disait:
I guess your lintian is newer than 1.23.48?
No, I have 1.23.48. But I use -viI as args.
Anyway, since Encoding is a deprecated key, I am happy to remove it.
The
On Thu, 2008-05-08 at 20:19 +0800, Wen-Yen Chuang wrote:
Aleš Koval (author of fpm2) wrote:
FPM2 data file is 100% compatible with his old version. I port FPM2 as
drop-in replacement old FPM in mind.
In this case, why is it necessary to create an fpm2 package at all? Why
not just do a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Laager wrote:
In this case, why is it necessary to create an fpm2 package at all? Why
not just do a new fpm package (version 2.x.y) and avoid all the
transitioning? To me, an fpm2 package makes sense only if you intend to
support both
Le jeudi 08 mai 2008 à 11:54 +0800, Wen-Yen Chuang a écrit :
Dear mentors,
I am looking for a sponsor for my package fpm2.
The package is lintian clean. It fixes ITP: #478243
* Package name : fpm2
Version: 0.71-1
Upstream Author: Aleš Koval als AT regnet DOT
OoO En cette fin de nuit blanche du jeudi 08 mai 2008, vers 05:54,
Wen-Yen Chuang [EMAIL PROTECTED] disait:
Long description:
Figaro's Password Manager 2 is a program that allows you to securely
store the passwords. Passwords are encrypted with the blowfish
algorithm.
Hi!
You might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Bernat wrote:
You might want to say what differences this password manager have with
some other close password managers like revelation.
Done.
New long description:
Figaro's Password Manager 2 (FPM2) is a program that allows you to
OoO En ce doux début de matinée du jeudi 08 mai 2008, vers 08:38,
Olivier Berger [EMAIL PROTECTED] disait:
It seems that fpm2 would replace fpm, so, you may wish to address the
RFP for fpm in #457155 maybe.
Also, maybe your package (which I didn't have a look at) should replace
fpm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Bernat wrote:
caleb, does fpm2 can be a drop-in replacement for fpm? In this case, you
could provide fpm metapackage as an upgrade path to fpm2.
FPM2 basically share the same code base of fpm. However, I can not sure
that it is 100%
OoO En cette matinée pluvieuse du jeudi 08 mai 2008, vers 10:45, Wen-Yen
Chuang [EMAIL PROTECTED] disait:
caleb, does fpm2 can be a drop-in replacement for fpm? In this case, you
could provide fpm metapackage as an upgrade path to fpm2.
FPM2 basically share the same code base of fpm.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Bernat wrote:
I think that you can go with the proposed upgrade path.
Thank you!
And upstream author of fpm2 also replied:
Aleš Koval (author of fpm2) wrote:
Hi.
FPM2 data file is 100% compatible with his old version. I port FPM2 as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wen-Yen Chuang wrote:
1. Set it to Conflicts: fpm
Replaces: fpm
Provides: fpm
2. Make symlinks for /usr/bin/fpm2 and its manpage.
3. Closes #457155 (ITP for fpm), too.
And 4. Add a metapackage fpm
Description: a
OoO En ce début d'après-midi ensoleillé du jeudi 08 mai 2008, vers
15:35, Wen-Yen Chuang [EMAIL PROTECTED] disait:
fpm2 now Conflicts: fpm ( 0.61)
Replaces: fpm ( 0.61)
Provides: fpm
Why not 0.71 ?
--
I WILL NOT FAKE SEIZURES
I WILL NOT FAKE SEIZURES
I WILL NOT FAKE
OoO En ce début d'après-midi ensoleillé du jeudi 08 mai 2008, vers
15:35, Wen-Yen Chuang [EMAIL PROTECTED] disait:
Description: a password manager - metapackage
Figaro's Password Manager 2 (FPM2) is a drop-in replacement for fpm.
.
This package can be purged at anytime once the fpm2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for my package fpm2.
The package is lintian clean. It fixes ITP: #478243
* Package name : fpm2
Version: 0.71-1
Upstream Author: Aleš Koval als AT regnet DOT cz
* URL
28 matches
Mail list logo
