At a minimum you ' ll need settings for http-proxy-host and http-proxy-port.įinally, if you want to use SVN over HTTPS to access the repository, you ' ll need to tell SVN to trust the MacPorts signature. Different proxy configurations require different sets of options here, but the file is pretty well commented, so it should be easy to figure out what you need. (SVN automatically creates this file if it doesn ' t exist.)Įdit the file and set a proxy for hosts at *. If $prefix/var/macports/home/.subversion/servers doesn ' t exist, create it by copying the corresponding file from another user. 用了 port -d selfupdate debug 跟踪,发现是svn权限的问题。当update的时候,会invoke command “/usr/bin/svn update -non-interactive /opt/mports/trunk/dports” 黄色flag 表示执行update的时候和系统无及时交互,所以没机会存证书.įirst, tell subversion to use your proxy to connect to the server: Syncing local Subversion ports tree failedĮrror: Couldn ' t sync the ports tree: Synchronization of 1 source failedĮrror: Follow http: // /#project.tickets to report a bug.Įrror: /opt/local/bin/port: port selfupdate failed: Couldn ' t sync the ports tree: Synchronization of 1 source failed Svn: E175002: OPTIONS of ' ': Server certificate verification failed: issuer is not trusted (https: // )Ĭommand failed: /usr/bin/svn update -non-interactive /opt/mports/trunk/ dports Svn: E175002: Unable to connect to a repository at URL ' ' Help with this site's hosting with my Linode referral code.Synchronizing local ports tree from file: /// opt/mports/trunk/dports.If the keys that your system is missing differs, simply replace the key at the end of the above command with your key and run it. Gpg: key C0B21F32: public key "Ubuntu Archive Automatic Signing Key (2012) " imported Gpg: requesting key C0B21F32 from hkp server $ sudo apt-key adv -keyserver -recv-keys 3B4FE6ACC0B21F32Įxecuting: gpg -ignore-time-conflict -no-options -no-default-keyring -homedir /tmp/tmp.77TqYGKU7b -no-auto-check-trustdb -trust-model always -keyring /etc/apt/trusted.gpg -primary-keyring /etc/apt/trusted.gpg -keyserver -recv-keys 3B4FE6ACC0B21F32 Gpg: key 437D05B5: public key "Ubuntu Archive Automatic Signing Key " imported Gpg: requesting key 437D05B5 from hkp server To add these keys, run the following commands: $ sudo apt-key adv -keyserver -recv-keys 40976EAF437D05B5Įxecuting: gpg -ignore-time-conflict -no-options -no-default-keyring -homedir /tmp/tmp.QTeppiINUh -no-auto-check-trustdb -trust-model always -keyring /etc/apt/trusted.gpg -primary-keyring /etc/apt/trusted.gpg -keyserver -recv-keys 40976EAF437D05B5 Each unique key will only need to be added once. Notice that these are listed multiple times. Looking at the error above, apt is telling us that the following keys are missing: 40976EAF437D05B5 and 3B4FE6ACC0B21F32. Each key that is listed as missing needs to be added to the apt key manager so that it can authenticate the packages. Sometimes the system does not have all the keys it needs and runs into this issue. The apt packaging system has a set of trusted keys that determine whether a package can be authenticated and therefore trusted to be installed on the system. For example: $ sudo apt-get upgradeĮ: Some packages could not be authenticated If these errors aren’t fixed, apt will have problems when installing or upgrading packages. W: GPG error: trusty-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: GPG error: trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: GPG error: trusty-security Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 There are times when running apt-get update in Ubuntu will result in error messages such as the following: $ sudo apt-get update
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |