Hi,
> >However, from an upstream software POV, this is
> >a nightmare.
> >I'll need to check for stat version before giving it
> >a format string, possibly by checking it in configure.ac
>
> Yeah, the problem is that if upstream doesn't acknowledge this as an
> issue you'll either be compabtible with sarge & etch, or compatible with
> every new distribution that ships a more recent coreutils. The change
> definately should have been given a different option name, but I don't
> know that I can fix the problem at this point--only upstream can.
This is unfortunate in that coreutils is used by many users,
and we can't possibly weed out their changes.
Maybe the best Debian can do would be to make sure change is documented
somewhere.
In the case of stat behavior change it is documented, but
the full workaround and an example code which works in both
versions is not documented, so that might be worth an addition.
As for cowdancer, cowdancer 0.7 is uploaded to work around the problem.
cureutils may choose to conflict against cowdancer (<< 0.7)
for completeness, but since cowdancer isn't released in a stable
Debian release yet, it is not essential that a conflicts exists.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
