1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Patrick Lauer wrote: |
5 |
> At least I'm trying to keep these |
6 |
> packages alive, which noone else seems to do. |
7 |
|
8 |
If you spot that a new version is available, you're more than welcome to |
9 |
post a version bump bug assigned to the appropriate herd and developer |
10 |
(forensics and me, in this instance). |
11 |
|
12 |
I don't necessarily have time to stayed glued to exactly when new |
13 |
versions of a package come out, but that doesn't mean I'm not willing to |
14 |
spend the time to keep it up to date once I'm aware a new version's come |
15 |
out. If nobody tells me, it'll have to wait until I spot it myself. |
16 |
|
17 |
Foremost has a single bug open against it, which is a stabilization bug, |
18 |
that means it still compiles, and works, or that no one's bothered to |
19 |
complain about it. So I'd class the package as far from dead. |
20 |
|
21 |
Please don't claim no one else wants to keep the package alive, when you |
22 |
don't afford them the opportunity to demonstrate that they do. If you |
23 |
take responsibility for bumping a package from the appropriate |
24 |
maintainer, you can't then turn around and claim you're allowed to cut |
25 |
corners because no one was maintaining it. It's quite rude to the |
26 |
people who are willing to look after it... |
27 |
|
28 |
Mike 5:) |
29 |
-----BEGIN PGP SIGNATURE----- |
30 |
Version: GnuPG v2.0.13 (GNU/Linux) |
31 |
|
32 |
iEYEARECAAYFAkr25AYACgkQu7rWomwgFXrIxQCgnVdigpUJZnaW28HcJ2U8qQZy |
33 |
b9IAoJc2Afv0UfrrYu7xe7EdP1DCP2Ze |
34 |
=m8Os |
35 |
-----END PGP SIGNATURE----- |