#54056 closed defect (fixed)
MacPorts should warn when not using "macports" rsync module
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | jmroot (Joshua Root) |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts 2.10.0 |
Component: | base | Version: | 2.4.1 |
Keywords: | Cc: | ||
Port: |
Description
MacPorts currently prints this warning:
Warning: MacPorts is configured to use an unsigned source for the ports tree. Please edit sources.conf and change 'rsync://rsync.macports.org/release/ports/' to 'rsync://rsync.macports.org/release/tarballs/ports.tar'.
This advice is not optimal: the user should be advised to change it to "rsync:// rsync.macports.org/macports/release/tarballs/ports.tar".
In addition to warning when not using a tarball, as was already done in [bebd94ad0415b859b37a9887dfae102b45e70590/macports-base], we should warn when not using the "macports" rsync module. (Using the old standalone "release" and "trunk" modules is deprecated; our new rsync server provider would like for us to wean users off of those old modules so that they can eventually remove them.)
We currently issue this warning for all *rsync.macports.org hostnames, but not all of our mirrors use the same rsync module naming convention which complicates things. Ideally we would ask our mirror providers to change their setup to match ours. But until that happens, maybe we can only issue the rsync module name warning when using the official rsync.macports.org server and not when using a mirror.
Change History (6)
comment:1 Changed 4 months ago by jmroot (Joshua Root)
Owner: | set to jmroot |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:2 Changed 4 months ago by jmroot (Joshua Root)
Milestone: | → MacPorts Future |
---|
comment:3 Changed 4 months ago by jmroot (Joshua Root)
Milestone: | MacPorts Future → MacPorts 2.10.0 |
---|
comment:4 Changed 2 months ago by clegra
Thank you very much for this information. My apologies in advance for my likely ignorant question: I had tried to follow the warning advice, but I seem to have not succeeded in finding the right version of "sources.conf" among all those that a locate command shows for on my system (22 occurrences). In order to act correctly on this warning I therefore want to kindly ask you: -- How do I find the correct version of "sources.conf" in which I have to perform the link change that the warning asks me about? Many thanks in advance for any suggestion!
comment:5 Changed 2 months ago by jmroot (Joshua Root)
man sources.conf
(or equivalently port help sources.conf
) has the full answer in the Files section. For users who haven't customised anything, it will be /opt/local/etc/macports/sources.conf
. It would probably be possible to print the full path in these warnings to help avoid confusion.
comment:6 Changed 2 months ago by clegra
Many thanks indeed! I am happy to have finally acted adequately on this warning with your help. The version with the default path (I had not customized anything) seemed to be the correct one in my case.) Indeed if the full path could be printed in the warnings, this would be helpful. But once again: many thanks indeed!
In 701386c517e8ca889a9bd720b61aed38fad66bfc/macports-base (master):