Re: devel/qt5-core upgrade failure

2018-12-24 Thread Paul Beard


> 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 upgrade rather
> than the ports tree. 

I might agree if any other ports besides qt-* were failing. They’re not. 

Re: devel/qt5-core upgrade failure

2018-12-24 Thread Tobias C. Berner
--->  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 anything for kde@ to do here, as this seems to be
an issue with the tool used to upgrade rather
than the ports tree.



mfg Tobias

On Mon, 24 Dec 2018 at 22:32, Paul Beard  wrote:

>
>
> On Dec 24, 2018, at 1:31 PM, Tobias C. Berner  wrote:
>
> I mean how are you "building" the updates :)
>
>
> portupgrade -a
>


Re: devel/qt5-core upgrade failure

2018-12-24 Thread Paul Beard


> On Dec 24, 2018, at 1:31 PM, Tobias C. Berner  wrote:
> 
> I mean how are you "building" the updates :) 
> 

portupgrade -a

Re: devel/qt5-core upgrade failure

2018-12-24 Thread Tobias C. Berner
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 message is trying to tell us something…
>
> > pkg-static: Warning: @exec is deprecated, please use @[pre|post][un]exec
>
>
>


Re: devel/qt5-core upgrade failure

2018-12-24 Thread Paul Beard



> 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]exec




Re: devel/qt5-core upgrade failure

2018-12-24 Thread Tobias C. Berner
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 the port *did* work, I'd like
> to
> chalk this up to "something was wrong once”.
>
>
> Subsequent deinstall does work but I don’t see much value in a pkg/ports
> system that requires a manual step for a subset of ports. Happens with
> every qt-* port.
>
>
> > Compressing man pages (compress-man)
> ===>   Installing ldconfig configuration file
> --->  Build of net/qt5-network ended at: Mon, 24 Dec 2018 09:28:38 -0800
> (consumed 00:11:11)
> --->  Updating dependency info
> --->  Uninstallation of qt5-network-5.12.0 started at: Mon, 24 Dec 2018
> 09:28:38 -0800
> --->  Fixing up dependencies before creating a package
> --->  Backing up the old version
> --->  Uninstalling the old version
> [Reading data from pkg(8) ... - 550 packages found - done]
> --->  Deinstalling 'qt5-network-5.12.0'
> --->  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
> Copy failed!
> [Reading data from pkg(8) ... - 550 packages found - done]
> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> ! qt5-network-5.12.0(copy failed)
> --->  Uninstallation of qt5-network-5.12.0 ended at: Mon, 24 Dec 2018
> 09:28:41 -0800 (consumed 00:00:02)
> --->  Upgrade of net/qt5-network ended at: Mon, 24 Dec 2018 09:28:41 -0800
> (consumed 00:11:14)
> --->  ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed
> --->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
> ! net/qt5-network (qt5-network-5.12.0)  (uninstall error)
>
>
> /usr/ports/net/qt5-network]# make deinstall reinstall
> ===>  Deinstalling for qt5-network
> ===>   Deinstalling qt5-network-5.12.0
> Updating database digests format: 100%
> Checking integrity... done (0 conflicting)
> Deinstallation has been requested for the following 1 packages (of 0
> packages in the universe):
>
> Installed packages to be REMOVED:
> qt5-network-5.12.0
>
> Number of packages to be removed: 1
>
> The operation will free 2 MiB.
> [1/1] Deinstalling qt5-network-5.12.0...
> [1/1] Deleting files for qt5-network-5.12.0: 100%
> ===>  Installing for qt5-network-5.12.0_1
> ===>   Registering installation for qt5-network-5.12.0_1
> pkg-static: Warning: @exec is deprecated, please use @[pre|post][un]exec
> Installing qt5-network-5.12.0_1...
>


Re: devel/qt5-core upgrade failure

2018-12-24 Thread Paul Beard


> 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 I don’t see much value in a pkg/ports system 
that requires a manual step for a subset of ports. Happens with every qt-* 
port. 


> Compressing man pages (compress-man)
===>   Installing ldconfig configuration file
--->  Build of net/qt5-network ended at: Mon, 24 Dec 2018 09:28:38 -0800 
(consumed 00:11:11)
--->  Updating dependency info
--->  Uninstallation of qt5-network-5.12.0 started at: Mon, 24 Dec 2018 
09:28:38 -0800
--->  Fixing up dependencies before creating a package
--->  Backing up the old version
--->  Uninstalling the old version
[Reading data from pkg(8) ... - 550 packages found - done]
--->  Deinstalling 'qt5-network-5.12.0'
--->  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
Copy failed!
[Reading data from pkg(8) ... - 550 packages found - done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! qt5-network-5.12.0(copy failed)
--->  Uninstallation of qt5-network-5.12.0 ended at: Mon, 24 Dec 2018 09:28:41 
-0800 (consumed 00:00:02)
--->  Upgrade of net/qt5-network ended at: Mon, 24 Dec 2018 09:28:41 -0800 
(consumed 00:11:14)
--->  ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed
--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
! net/qt5-network (qt5-network-5.12.0)  (uninstall error)


/usr/ports/net/qt5-network]# make deinstall reinstall 
===>  Deinstalling for qt5-network
===>   Deinstalling qt5-network-5.12.0
Updating database digests format: 100%
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages 
in the universe):

Installed packages to be REMOVED:
qt5-network-5.12.0

Number of packages to be removed: 1

The operation will free 2 MiB.
[1/1] Deinstalling qt5-network-5.12.0...
[1/1] Deleting files for qt5-network-5.12.0: 100%
===>  Installing for qt5-network-5.12.0_1
===>   Registering installation for qt5-network-5.12.0_1
pkg-static: Warning: @exec is deprecated, please use @[pre|post][un]exec
Installing qt5-network-5.12.0_1...

Re: devel/qt5-core upgrade failure

2018-12-17 Thread Paul Beard
> 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 each failed port and wrapping them in a for 
loop to fix this. Seems like I shouldn’t have to do that for just one special 
family of ports but whatever. I have been through several cycles of this now.  

--
This space intentionally left blank. 

Re: devel/qt5-core upgrade failure

2018-12-17 Thread Adriaan de Groot
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 "something was wrong once".

[ade]