Date: Sun, 20 Feb 2011 18:40:07 GMT From: "Matthias Andree" <mandree@FreeBSD.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/154912: please provide unison 2.32 for network compatibility Message-ID: <201102201840.p1KIe7Zp082647@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/154912; it has been noted by GNATS.
From: "Matthias Andree" <mandree@FreeBSD.org>
To: "Guido Falsi" <mad@madpilot.net>
Cc: "Matthias Andree" <mandree@FreeBSD.org>, freebsd-gnats-submit@FreeBSD.org,
miwi@FreeBSD.org
Subject: Re: ports/154912: please provide unison 2.32 for network
compatibility
Date: Sun, 20 Feb 2011 19:34:07 +0100
> Thank you for pointing out this problem.
>
> I agree a UPDATING entry should have been provided. Shame on me for
> missing this.
>
> Sorry for any inconvenience caused by my omission.
>
> I'm not quite sure, though, that providing an old revision port for a
> temporary problem like this is the preferred way to handle this.
Yes it is because users do not necessarily have the change of updating
their peer computers or requesting an update. There is a long tradition in
ports of keeping older versions of packages around after wire protocol
changes. We have those for openvpn (openvpn20), openldap, and
thereabouts.
> IMHO a note in updating stating the problem and suggesting not to
> upgrade or to downgrade the port(using ports-mgmt/portdowngrade or csup
> manually) should be enough.
That's a bigger inconvenience because it breaks the usual package
upgrading workflow.
> Especially considering the temporary nature of this problem.
The temporary nature is your assumption, but not a given. Also, if you
use more than one peer, you need to coordinate all upgrades. This, too,
is a major inconvenience, or even impossible for some sites.
>
> In this case an UPDATING entry with this text should do:
>
> ---
>
> 20110219:
> AFFECTS: users of net/unison*
> AUTHOR: mad@madpilot.net
>
> net/unison was updated to 2.40.62. This new version uses a wire
> protocol incompatible with previous versions. You are advised to check
> that all your peers have been updated at least to this same version
> before updating yourself.
>
> If you have already updated and need to downgrade you can use
> ports-mgmt/portdowngrade or csup a ports tree before Sat Feb 19 12:52:12
> 2011 UTC
>
> ---
>
>>
>> Please provide a unison 2.32 package (and request a repocopy), possibly
>> as net/unison232 and a corresponding ports/UPDATING entry so that users
>> are
>> warned to switch to that package unless all their peer sites have unison
>> 2.40
>> available.
>>
>
> Depending on personal taste the above entry could intended as rude, I
> see. So I'm attaching a shar of the older unison port adapted to be
> unison232 as asked.
>
> I'm not sure if my use of the LATEST_LINK directive is correct.
>
> In such a case the following UPDATING entry should be used:
>
> ---
>
> 20110219:
> AFFECTS: users of net/unison*
> AUTHOR: mad@madpilot.net
>
> net/unison was updated to 2.40.62. This new version uses a wire
> protocol incompatible with previous versions. You are advised to check
> that all your peers have been updated at least to this same version
> before updating yourself.
>
> If you need to stick to 2.32.52 please use the net/unison232 port.
This would have to have detailed portmaster/portupgrade -o ...
instructions. Also note that a previous unison-devel/unison
upgrade/shuffle would also have needed a unison entry. I think, however,
we should only add one entry stating the "if you have updated before ...
and want ..., do: if you have updated between ... and want ..., do ..."
style.
> I'm not quite sure what is the official ports project policy in such a
> situation, so I'd like some committer to tell me what is the preferred
> solution.
See above. :-)
I'll request a repocopy of the older net/unison port to net/unison232.
Would you be willing to act as its maintainer? If not, I'll take it.
Thanks & best regards
Matthias
--
Matthias Andree
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201102201840.p1KIe7Zp082647>