unreliable pkg upgrades

[Florian Smeets]

On 22.05.18 23:58, Miroslav Lachman wrote:
> Am I the only one seeing occasional unreliable pkg upgrades?

No.

> 
> I think changes in package name or ports origin should be better handled
> by pkg tools.
> For example, we have php-composer installed on many of our machines. The
> ports was flavorized, ports origin is the same, but pkg reports
> php-composer as orphaned.
> 

I've seen the same thing for ports that were favored. I haven't looked
into this any further though.
> 
> Why it is not handled automatically like in other OSes?
> That's the reason we are still not using Ansible for mass pkg upgrades,
> because we must carefully watch each and every pkg upgrade run. What it
> will do and what it refuse to do without manual intervention.

Yeah, this is really really unfortunate if you rely on pkg, to keep your
system updated and secure.

> 
> Miroslav Lachman
> 
> PS: we are using own repository built with poudriere

Same.

Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20180523/8243ed01/attachment.sig>