- Update to 0.6.08b - Optional request to committer: 0.6.x is no longer the 'development' series, though a new -devel is expected when 0.7.x releases start to come out. sysutils/duplicity is now 0.5.x, and there are some significant differences which mean that it is a good idea, IMO, to keep 0.5.x. So I would suggest: * repocopy sysutils/duplicity to sysutils/duplicity05 * repocopy sysutils/duplicity-devel to sysutils/duplicity * probably remove sysutils/duplicity-devel, leave it as is, or keep an up-to-date copy that will then transition to 0.7.x onces releases start happening upstream. I'm not sure if this is the correct venue to request such actions. Suggested fallback is to commit this update as usual and I'll try to sort out the renaming afterwards through proper channels. (I would prefer to have sysutils/duplicyXY always, and have sysutils/duplicity be a way to get the 'default' version. I'm not sure what the preferred method is to accomplish such a thing, or whether it would be considered kosher in ports?) If the repocopy is done, I would suggest an UPDATING entry similar to: YYYYMMDD: AFFECTS: users of sysutils/duplicity(-devel) sysutils/duplicity has been upgraded to the 0.6 series. Users of 0.5 who which to remain there should switch to sysutils/duplicity05. sysutils/duplicity-devel has been removed. Users of the 0.6 series should switch to sysutils/duplicity. Generated with FreeBSD Port Tools 0.99
Responsible Changed From-To: freebsd-ports-bugs->amdmi3 I'll take it.
State Changed From-To: open->closed Committed. Thanks!