On 2026/05/21 22:50, Stuart Henderson wrote:
> On 2026/05/21 20:21, gonzalo wrote:
> > On Wed Apr 15, 2026 at 5:15 PM CEST, Stuart Henderson wrote:
> > > On 2026/03/20 14:34, gonzalo wrote:
> > >> Hello,
> > >> 
> > >> Varnish changed its name to Vinyl, so here is a little WIP for the new 
> > >> port.
> > >> 
> > >> Test and feedback is welcomed.
> > >> 
> > >> https://vinyl-cache.org/releases/rel9.0.0.html#rel9-0-0
> > >> 
> > >> Cheers.-
> > >
> > > You can't use uid 625 with the name _vinyl, it can't coexist with
> > > _varnish on 625, so there's no good upgrade path.
> > >
> > > Despite the name change, I think I would stick with username _varnish
> > > on 625 (rather than burning another uid for it).
> > 
> > Hello,
> > 
> > This is OK? Just keep using _varnish everywere?
> 
> On second thoughts, I noticed that _varnish has /var/varnish as the
> home dir, and this has /var/vinyl. so, actually, do use a new uid
> (different number). and comment-out _varnish in user.list when the port
> is removed.

...or alternatively, just keep /var/varnish like was done with
mariadb (which still uses _mysqld / /var/mysql) ...

> (btw you have /var/vinyl in @newuser and ${LOCALSTATEDIR}/vinyl in
> @sample, those should be consistent..)

> > BTW, this should be another software or we should make varnish to
> > upgrade to vinyl? do we need a @conflict varnish?
> 
> It does need @conflict varnish-* (at least because of /usr/local/bin/vtest,
> I didn't check if there are others).
> 
> You can use this in quirks when varnish is removed (+ bump).
> 
> Index: files/Quirks.pm
> ===================================================================
> RCS file: /cvs/ports/devel/quirks/files/Quirks.pm,v
> diff -u -p -r1.1802 Quirks.pm
> --- files/Quirks.pm   17 May 2026 09:50:29 -0000      1.1802
> +++ files/Quirks.pm   21 May 2026 21:49:12 -0000
> @@ -1069,6 +1069,7 @@ setup_obsolete_reason(
>       46 => 'exim',
>       46 => 'exim-eximon',
>  # 8.0
> +     18 => 'varnish',
>  );
>  # beware, if ports with an RDEP on Python 3 are removed, they need to be 
> listed
>  # as @conflcit/pkgpath in lang/python/3 and not here, otherwise an update 
> from a
> @@ -1104,6 +1105,8 @@ my $obsolete_suggestion = {
>       'minecraft' => 'multimc',
>       'tls-attacker' => 'py3-tlsfuzzer',
>       'usmb' => 'susmb',
> +# 8.0
> +     'varnish' => 'vinyl',
>  };
>  
>  # reasons for obsolete packages
> @@ -1126,6 +1129,7 @@ my $obsolete_message = {
>       15 => "use rspamd's internal milter support instead",
>       16 => "dependencies for recent versions can't be met",
>       17 => "outdated port, security problems in the last ported version",
> +     18 => "renamed upstream",
>       46 => "setuid-root software with a track record of security issues",
>       47 => "DNS network daemon running as root and not using random source 
> ports. use DNS64 support in unbound or isc-bind",
>       48 => "1.x does not support current PHP, 2.x is tricky to package, see 
> https://github.com/leenooks/phpLDAPadmin/wiki/Installation-Instructions#install-from-the-source-code";,
> 
> 
> 

Reply via email to