Re: Releasing 2.4.2
On Oct 5, 2017, at 16:02, Ryan Schmidt wrote: > On Oct 5, 2017, at 15:19, Rainer Müller wrote: > >> https://github.com/macports/macports-base/releases/tag/v2.4.2 >> >> I will hold back updating the website and official announce mail until >> we have new .pkg installers to avoid breaking the download links. At the >> moment, users can still install MacPorts 2.4.1 which will then >> automatically update itself to version 2.4.2. > > Josh, will you build the packages for us? If you let me know when you upload > them to GitHub I'll mirror them. Thanks for building them, Josh! The packages and disk images are on the mirror now. http://distfiles.macports.org/MacPorts/
Re: Releasing 2.4.2
On 2017-10-06 18:58, db wrote: > On 6 Oct 2017, at 18:54, Ryan Schmidt wrote: >> Thanks, that was exactly the fix I was just going to suggest. I'll deploy >> that, then 2.4.2 should be available within the hour. > > Sorry to hijack the thread. I just installed 2.4.2 from source and realised > that rleaves didn't make it to it yet. Any ideas why? Releases in the 2.4.x series only contain bugfixes. New features are only on the master branch, from which we will eventually create a new branch for MacPorts 2.5. MacPorts 2.5.0 will then ship new features such as the 'rleaves' pseudo-portname. Rainer
Re: Releasing 2.4.2
On 2017-10-06 18:30, Ryan Schmidt wrote: > > On Oct 6, 2017, at 09:32, Rainer Müller wrote: > >> mprsyncup [1] is supposed to handle that automatically. It seems >> like the job failed or is stuck, as ports.tar was also not updated. > > It seems to be having this problem: > > 2017-10-05T15:12:56-0500 error: pathspec 'v2.4.2' did not match any file(s) > known to git. > > Any ideas? Maybe something about how the script was rewritten for git > recently? This should hopefully fix it: https://github.com/macports/macports-infrastructure/commit/bb8f7886c9c086d80cfdde35d6c7402bd61675b6 'git fetch' only fetches tracked branches by default, but we keep master checked out. This option tells git to also fetch all tags. Rainer
Re: Releasing 2.4.2
On 6 Oct 2017, at 18:54, Ryan Schmidt wrote: > Thanks, that was exactly the fix I was just going to suggest. I'll deploy > that, then 2.4.2 should be available within the hour. Sorry to hijack the thread. I just installed 2.4.2 from source and realised that rleaves didn't make it to it yet. Any ideas why?
Re: Releasing 2.4.2
On Oct 6, 2017, at 11:53, Rainer Müller wrote: > On 2017-10-06 18:30, Ryan Schmidt wrote: >> >> On Oct 6, 2017, at 09:32, Rainer Müller wrote: >> >>> mprsyncup [1] is supposed to handle that automatically. It seems >>> like the job failed or is stuck, as ports.tar was also not updated. >> >> It seems to be having this problem: >> >> 2017-10-05T15:12:56-0500 error: pathspec 'v2.4.2' did not match any file(s) >> known to git. >> >> Any ideas? Maybe something about how the script was rewritten for git >> recently? > > This should hopefully fix it: > > https://github.com/macports/macports-infrastructure/commit/bb8f7886c9c086d80cfdde35d6c7402bd61675b6 > > 'git fetch' only fetches tracked branches by default, but we keep master > checked out. This option tells git to also fetch all tags. Thanks, that was exactly the fix I was just going to suggest. I'll deploy that, then 2.4.2 should be available within the hour.
Re: Releasing 2.4.2
On Oct 6, 2017, at 09:32, Rainer Müller wrote: > mprsyncup [1] is supposed to handle that automatically. It seems > like the job failed or is stuck, as ports.tar was also not updated. It seems to be having this problem: 2017-10-05T15:12:56-0500 error: pathspec 'v2.4.2' did not match any file(s) known to git. Any ideas? Maybe something about how the script was rewritten for git recently?
Re: Releasing 2.4.2
On 2017-10-06 14:53, Chris Jones wrote: > How long until this macports update is expected to be available via > selfupdate, as I am not getting this yet, it is still returning 2.4.1 as > the latest ? See below. > > Is the rsync server for some reason not yet updated ? No, it is not yet updated: $ TZ=UTC rsync --no-motd rsync://nerv.macports.org/macports/release/tarballs/*.tar -rw-r--r-- 85,762,560 2017/08/22 21:43:31 base.tar -rw-r--r-- 65,268,736 2017/10/05 19:02:20 ports.tar mprsyncup [1] is supposed to handle that automatically. It seems like the job failed or is stuck, as ports.tar was also not updated. Rainer [1] https://github.com/macports/macports-infrastructure/blob/master/jobs/mprsyncup
Re: Releasing 2.4.2
Hi, How long until this macports update is expected to be available via selfupdate, as I am not getting this yet, it is still returning 2.4.1 as the latest ? See below. Is the rsync server for some reason not yet updated ? cheers Chris Titan ~ > sudo port -d selfupdate DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs ---> Updating MacPorts base sources using rsync DEBUG: system: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs Willkommen auf dem RSYNC-server auf ftp.fau.de. Nicht all unsere Mirror sind per rsync verfuegbar. Welcome to the RSYNC daemon on ftp.fau.de. Not all of our mirrors are available through rsync. receiving file list ... done sent 16 bytes received 55 bytes 47.33 bytes/sec total size is 85762560 speedup is 1207923.38 DEBUG: system: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar.rmd160 /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs Willkommen auf dem RSYNC-server auf ftp.fau.de. Nicht all unsere Mirror sind per rsync verfuegbar. Welcome to the RSYNC daemon on ftp.fau.de. Not all of our mirrors are available through rsync. receiving file list ... done sent 16 bytes received 62 bytes 156.00 bytes/sec total size is 512 speedup is 6.56 DEBUG: successful verification with key /opt/local/share/macports/macports-pubkey.pem DEBUG: system: /usr/bin/tar -C /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp -xf /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base.tar MacPorts base version 2.4.1 installed, DEBUG: Rebuilding and reinstalling MacPorts if needed MacPorts base version 2.4.1 downloaded. ---> Updating the ports tree Synchronizing local ports tree from file:///Users/chris/Projects/MacPorts/ports DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.zZhjsTAPCM/Listeners DEBUG: /opt/local/bin/git pull --rebase --autostash DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git pull --rebase --autostash Enter passphrase for key '/Users/chris/.ssh/id_rsa': From github.com:macports/macports-ports 765660a0ff..51bfc80e5b master -> origin/master First, rewinding head to replay your work on top of it... Fast-forwarded master to 51bfc80e5b698ed45df29a9741e6b7bd85ec6527. DEBUG: euid/egid restored to: 0/0, env restored DEBUG: system: /opt/local/bin/portindex /Users/chris/Projects/MacPorts/ports Creating port index in /Users/chris/Projects/MacPorts/ports Adding port devel/qbs Adding subport qbs-docs Adding port lang/pypy Adding subport pypy3 Adding port mail/getmail Adding port sysutils/detach Adding port sysutils/tmux Adding subport tmux-devel Adding port textproc/hunspell-dict-en_US Total number of ports parsed: 9 Ports successfully parsed: 9 Ports failed: 0 Up-to-date ports skipped: 20110 ---> MacPorts base is already the latest version DEBUG: Setting MacPorts sources ownership to root The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated Titan ~ > On 05/10/17 21:19, Rainer Müller wrote: MacPorts 2.4.2 is now out and should be available via selfupdate over rsync shortly. Ryan, could you please mirror the tarballs and signatures from the GitHub release to distfiles.macports.org? https://github.com/macports/macports-base/releases/tag/v2.4.2 I will hold back updating the website and official announce mail until we have new .pkg installers to avoid breaking the download links. At the moment, users can still install MacPorts 2.4.1 which will then automatically update itself to version 2.4.2. Rainer
Re: Releasing 2.4.2
On Oct 5, 2017, at 15:19, Rainer Müller wrote: > MacPorts 2.4.2 is now out and should be available via selfupdate over > rsync shortly. > > Ryan, could you please mirror the tarballs and signatures from the > GitHub release to distfiles.macports.org? Done. > https://github.com/macports/macports-base/releases/tag/v2.4.2 > > I will hold back updating the website and official announce mail until > we have new .pkg installers to avoid breaking the download links. At the > moment, users can still install MacPorts 2.4.1 which will then > automatically update itself to version 2.4.2. Josh, will you build the packages for us? If you let me know when you upload them to GitHub I'll mirror them.
Re: Releasing 2.4.2
MacPorts 2.4.2 is now out and should be available via selfupdate over rsync shortly. Ryan, could you please mirror the tarballs and signatures from the GitHub release to distfiles.macports.org? https://github.com/macports/macports-base/releases/tag/v2.4.2 I will hold back updating the website and official announce mail until we have new .pkg installers to avoid breaking the download links. At the moment, users can still install MacPorts 2.4.1 which will then automatically update itself to version 2.4.2. Rainer
Releasing 2.4.2
Hello, unless there is something else to be backported to release-2.4, I would like to tag and create a tarball for 2.4.2 tomorrow to get the suid bit fix for the High Sierra sandbox out. ChangeLog already reflects the changes that will be in this release: https://github.com/macports/macports-base/blob/master/ChangeLog Rainer
