Re: [GSoC] migration
On 22 Jul 2017, at 03:01, Umesh Singla wrote: > I don't know, in the above example, what do you mean when you say "..you > realize that from its deps..", like, realize how? I am just asking this if > there's some other way to get info on the latest modifications that I might > not be aware of. > 'sync' or 'upgrade outdated' provide the information what all ports got > updated immediately on console but I'm not sure if it can be accessed later > since the user may not realize that another port has broken immediately, like > hstr here. Since MP doesn't keep logs (!) I keep them myself and investigate when something doesn't work properly. > Another thing that comes to my mind now is if, suppose, updated version of > ncurses was actually required for some another port and reverting it to the > older state could possibly result in breaking of that port. No, because, as I said, it would revert to a previous tree state. The thing is doing it by reinstalling only the upgraded ports and not the whole tree. It shouldn't be difficult to implement.
Re: rsync server out of date?
On Jul 22, 2017, at 09:48, Marcus Calhoun-Lopez wrote: > I just ran `port sync`, but the ports are several days behind the GitHub > repository. > Is anyone else having this problem? I've reset it again (third time this month) and it should sync up again in a couple hours.
Re: rsync server out of date?
Hi, On Sat, Jul 22, 2017 at 07:48:59AM -0700, Marcus Calhoun-Lopez wrote: > I just ran `port sync`, but the ports are several days behind the > GitHub repository. Is anyone else having this problem? We're aware of the problem and are in contact with GitHub support to resolve the issue. If you want to help out, we'd welcome a pull requests that makes https://github.com/macports/macports-infrastructure/blob/master/jobs/mprsyncup use Git instead of SVN. -- Clemens
rsync server out of date?
I just ran `port sync`, but the ports are several days behind the GitHub repository. Is anyone else having this problem? -Marcus
Build base archives for CI in a separate repository
Hi, In [1], I patched MacPorts in an attempt to fix a bug (port(1) failed randomly on Travis). As it seems to be a Travis-specific bug, I plan to use a separate repository to generate MacPorts archives used in CI and keep the patch there. This way we can update the CI-specific archives without a new release in macports-base (e.g. when new releases of macOS become available on Travis). [1]: https://github.com/macports-staging/macports-base/commit/282e498ac51ba40bdfd43008ce430ca20a7d54ce#diff-d7db55f70d83fc9dba4ef14de9febe71 -- Best regards, Zero King smime.p7s Description: S/MIME cryptographic signature
