> On Dec 24, 2018, at 1:39 PM, Tobias C. Berner wrote:
>
> Maybe check why portupgrade does this and fails with it, maybe the developers
> of portupgrade can help you out there.
> I don't see that there is anything for kde@ to do here, as this seems to be
> an issue with the tool used to upg
---> Preserving /usr/local/lib/qt5/libQt5Network.so.5 as
/usr/local/lib/compat/pkg/libQt5Network.so.5
cp: symlink: libQt5Network.so.5.12.0: File exists
Maybe check why portupgrade does this and fails with it, maybe the
developers of portupgrade can help you out there.
I don't see that there is an
> On Dec 24, 2018, at 1:31 PM, Tobias C. Berner wrote:
>
> I mean how are you "building" the updates :)
>
portupgrade -a
I mean how are you "building" the updates :)
On Mon, 24 Dec 2018 at 21:01, Paul Beard wrote:
>
>
> > On Dec 24, 2018, at 10:54 AM, Tobias C. Berner
> wrote:
> >
> > How are you updating the ports?
>
> ? Through svn, same as for all of them, same as I have done for years.
>
> Seems like this mes
> On Dec 24, 2018, at 10:54 AM, Tobias C. Berner wrote:
>
> How are you updating the ports?
? Through svn, same as for all of them, same as I have done for years.
Seems like this message is trying to tell us something…
> pkg-static: Warning: @exec is deprecated, please use @[pre|post][un]e
Moin moin
How are you updating the ports?
Mfg Tobias
Am Mo., 24. Dez. 2018, 18:42 hat Paul Beard
geschrieben:
>
>
> On Dec 17, 2018, at 5:15 AM, Adriaan de Groot wrote:
>
> I suppose that's the error message from whatever tool you were using --
> portupgrade? Since subsequent deinstall from
> On Dec 17, 2018, at 5:15 AM, Adriaan de Groot wrote:
>
> I suppose that's the error message from whatever tool you were using --
> portupgrade? Since subsequent deinstall from the port *did* work, I'd like to
> chalk this up to "something was wrong once”.
Subsequent deinstall does work but
> On Dec 17, 2018, at 5:15 AM, Adriaan de Groot wrote:
>
> I suppose that's the error message from whatever tool you were using --
> portupgrade? Since subsequent deinstall from the port *did* work, I'd like to
> chalk this up to "something was wrong once".
More like “every time.” I am noting
On Sunday, 16 December 2018 18:51:36 CET Paul Beard wrote:
> ! devel/qt5-core (qt5-core-5.11.2_2)(uninstall error)
I suppose that's the error message from whatever tool you were using --
portupgrade? Since subsequent deinstall from the port *did* work, I'd like to
chalk this up to "s
