On 2019/08/20 17:12, Steffen Nurpmeso wrote:
> Hello Stuart.
> 
> Stuart Henderson wrote in <20190820095908.gy32...@symphytum.spacehopper.org>:
>  |On 2019/08/19 18:33, Steffen Nurpmeso wrote:
>  |> Please find below an update to S-nail v14.9.15, the (likely) last
>  |> in the v14.9 series.
>  ...
>  |> Index: Makefile
>  |> ===================================================================
>  |> RCS file: /cvs/ports/mail/s-nail/Makefile,v
>  |> retrieving revision 1.24
>  |> diff -u -p -r1.24 Makefile
>  |> --- Makefile        29 Jul 2019 20:23:41 -0000      1.24
>  |> +++ Makefile        19 Aug 2019 16:07:37 -0000
>  |> @@ -2,12 +2,12 @@
>  |>  
>  |>  COMMENT=           SysV mail/BSD Mail/POSIX mailx: send and receive mail
>  |>  
>  |> -DISTNAME=          s-nail-14.9.14
>  |> +DISTNAME=          s-nail-14.9.15
>  |>  CATEGORIES=                mail
>  |>  HOMEPAGE=          https://www.sdaoden.eu/code.html\#s-mailx
>  |>  
>  |>  # BSD
>  |> -PERMIT_PACKAGE=    Yes
>  |> +PERMIT_PACKAGE_CDROM=      Yes
>  |
>  |That needs to stay.
> 
> Ok.  It was just that i got myriads of
> 
>   The licensing info for s-nail-14.9.15 is incomplete. (in mail/s-nail)
>   The licensing info for s-nail-14.9.15 is incomplete. (in mail/s-nail)
>   Please notify the OpenBSD port maintainer: (in mail/s-nail)
> 
> which lead me to bsd.port.mk and the change above.
> And since my update script always does
> 
>   (cd ports && cvs -q up $VERSION -PR infrastructure) || exit 5
> 
> Ah, maybe i just have to create a -current VM for further package
> updates, instead of going $VERSION, it is hacky anyway to update
> a package in that 6.5 release environment, i'd say.

Yes that's it, you really need -current for doing ports work.

Reply via email to