On Nov 7, 2019, at 21:23, Stan Sanderson wrote:
> OS X 10.14, all installed ports up-to-date.
> Re: kmymoney4-devel
>
> Since the recent problem with kdepimlibs4 was solved (thanks!), port upgrade
> outdated consistently ends with
> ---> Scanning binaries for linking errors
> ---> Found 2
OS X 10.14, all installed ports up-to-date.
Re: kmymoney4-devel
Since the recent problem with kdepimlibs4 was solved (thanks!), port upgrade
outdated consistently ends with
---> Scanning binaries for linking errors
---> Found 2 broken files, matching files to ports
---> Found 1 broken
On Nov 7, 2019, at 09:42, posita wrote:
> I have been wracking my brains trying to understand this, but have come up
> short.
>
> Every time I do a `sudo port -c -u selfupdate`, many files in
> `/var/macports/sources/rsync.macports.org/macports/release/tarballs`
> end up with GID 505.
I have been wracking my brains trying to understand this, but have come up
short.
Every time I do a `sudo port -c -u selfupdate`, many files in
`/var/macports/sources/rsync.macports.org/macports/release/tarballs`
end up with GID 505. E.G.:
% ls -l
I've noticed that in `main.log` files there is no information what
version and variants have been requested – for example,
ImageMagick @6.9.9-40_7+x11
Wouldn't it make sense to make `port` add this information to the very
top of `main.log`? This would also help identify various `make.log`
