| 1 |
On 07/12/2017 12:15 AM, Kristian Fiskerstrand wrote: |
| 2 |
> On 07/11/2017 04:13 PM, Kristian Fiskerstrand wrote: |
| 3 |
>> On 07/11/2017 03:47 PM, Michael Palimaka wrote: |
| 4 |
>>> The main risk of breakage of a package moving from testing to |
| 5 |
>>> stable is always at build time anyway. |
| 6 |
>> |
| 7 |
>> citation needed |
| 8 |
>> |
| 9 |
> |
| 10 |
> Anecdotal evidence against, currently gnupg 2.1.21 scdaemon bug will |
| 11 |
> happily sign a third party public keyblock's UID using signature subkey |
| 12 |
> on smartcard, which results in useless signature that doesn't have any |
| 13 |
> effect, but the application builds fine. |
| 14 |
> |
| 15 |
> This means gnupg 2.1.21 is not a candidate for stabilization, but it |
| 16 |
> certainly builds fine. |
| 17 |
> |
| 18 |
|
| 19 |
Stop trolling - you know perfectly well that this sort of issue would |
| 20 |
never ever be caught during arch testing. Nor should it be - it's called |
| 21 |
*arch* testing for a reason. |
| 22 |
|
| 23 |
Ensuring that a package's functionality is of merchantable quality is |
| 24 |
the maintainer's responsibility (that's you!). |
Archives