Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#49233 closed defect (fixed)

selfupdate fails with "Failed to verify signature for MacPorts source"

Reported by: micrology Owned by: admin@…
Priority: High Milestone:
Component: server/hosting Version: 2.3.3
Keywords: Cc: iqgrande, sandym (Sandy Martel), dbarter@…, NeilGirdhar (Neil), ryandesign (Ryan Schmidt), EnekoGotzon, rubendibattista (Ruben Di Battista), rhett.lhy@…, gsulshski (Greg Ulsh), rnspayne@…, jimmymbreen@…, hapaguy (Brian Kurt Fujikawa), js9986@…, macports@…, andy@…, moderndeveloperllc (Mark Garrett), chihangli@…, epaell, tpmanojm@…, mjhsieh@…, witoldj@…, fabian.glaser@…, Miroboru (Tor Andre Myrvoll), mndavidoff (Monte Davidoff), farmer.tseng@…, gallafent, roman.dayneko@…, seb@…, kurtjaeke@…, a.vincelli@…, robin.newman@…, djlambert (Derek J. Lambert), neurodroid (Christoph Schmidt-Hieber), avysk (Alexey Vyskubov), peter.mcalpine@…, m1@…, MaurizioLoreti, joaogeada (Joao Geada), john@…, szibetti@…, mjwybrow (Michael Wybrow), moritz.peter@…, leeawalsh@…, glen@…, deesto (John S. De Stefano Jr.), smparkes@…, vcultharris (L.T. Harris), alan.mock@…, grimreaper (Eitan Adler), morrell@…, bunk3m (Bunk3m), absima@…, steve.sell@…, tiasus@…, smeingast (Stefan Meingast), nortcele, aoeumacports@…, zaxdo@…, thomas.gimpel@…, netgamer7 (Roger Ward), raju.apm@…, ken.mcglothlen@…, stephenhamilton@…, eddieh (Eddie Hillenbrand), macports@…, samuel.hofmann@…, rodolphefouquet@…, erich3@…, ClintO (Clint O), michaelwallis@…, p.fabrizio.salvatore@…, pe8ter@…, alandir2@…, 0xced (Cédric Luthi), eric.lebigot@…, macports@…, kngspook@…, jackh48@…, anthony@…, boehm.adam@…, p.perroud@…, axet (Alexey Kuznetsov), todmorrison (Tod Morrison), permezel@…, macports@…, r1pp3r@…, suneilp@…, meckiemac@…, persramd@…, mkikkawa@…, petermisak (Peter Misak), pmo@…, Stochasticus@…, bodait, neilt (Neil Tiffin), stromnov (Andrew Stromnov), matt@…, summers@…, jsalort (Julien Salort), edgtzolvera@…, rohall@…, Feuermurmel (Michael Schwarz), tk7r (Thomas Kotzian), fracai, help@…, davidwalton3142@…, macports@…, jasonw@…, vosslab (Neil Voss), majoc-at-astro (majoc-at-astro), texas-swift, jmgoicolea (Jose Goicolea), j.albarran@…, eschnett (Erik Schnetter), H3ik0, bhadder@…, ktitt27@…, marco.outatime@…, josephaw@…, marco-comini (Marco Comini), skymoo (Adam Mercer), deyv@…, macports.org@…, macuserguru
Port:

Description

The output from sudo port -v selfupdate is:

--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 69 bytes  42.00 bytes/sec
total size is 27013120  speedup is 257267.81
receiving file list ... done

sent 36 bytes  received 76 bytes  44.80 bytes/sec
total size is 512  speedup is 4.57
Error: Failed to verify signature for MacPorts source!
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!

This is using MacPort 2.3.3 on Yosemite. It worked last time I did it, about 2 weeks ago.

The source listed in /opt/local/etc/macports/sources.conf is:

rsync://rsync.macports.org/release/tarballs/ports.tar [default]

Change History (179)

comment:1 Changed 6 years ago by mherdeg@…

This problem repros for me using OS X 10.11 and the latest stable "MacPorts-2.3.4-10.11".

port -d -v selfupdate 
DEBUG: Copying /Users/mherdeg/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/release/tarballs
--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 69 bytes  70.00 bytes/sec
total size is 27013120  speedup is 257267.81
receiving file list ... done

sent 36 bytes  received 76 bytes  74.67 bytes/sec
total size is 512  speedup is 4.57
DEBUG: failed verification with key /opt/local/share/macports/macports-pubkey.pem
DEBUG: openssl output: Verification Failure
child process exited abnormally
DEBUG: Failed to verify signature for MacPorts source!
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: Failed to verify signature for MacPorts source!
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!

Here's all I see happening "under the hood" with the verification step -- nothing very exciting --

openssl dgst  -rmd160 -verify /opt/local/share/macports/macports-pubkey.pem -signature ./base.tar.rmd160 base.tar
Verification Failure

Here's what the files look like:

ls -lrt /opt/local/share/macports/macports-pubkey.pem /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar.rmd160 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar
-r--r--r--  1 root  admin       800 Oct  1 15:42 /opt/local/share/macports/macports-pubkey.pem
-rw-r--r--  1 root  admin       512 Oct 11 16:07 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar.rmd160
-rw-r--r--  1 root  admin  27013120 Oct 11 16:34 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar


MD5 /opt/local/share/macports/macports-pubkey.pem
MD5 (/opt/local/share/macports/macports-pubkey.pem) = 78d4677826f684ece21c7527c65cc38b

MD5 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar.rmd160
MD5 (/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar.rmd160) = 9dac68c55f5b4a3db73a5ac6ac1ab4d5

MD5 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar
MD5 (/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar) = d34533dd1a9f3a5a75a58074e12844ae

Last edited 6 years ago by mherdeg@… (previous) (diff)

comment:2 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: iqgrande@… sandy@… dbarter@… mistersheik@… ryandesign@… added
Keywords: selfupdate removed

Has duplicates #49234, #49236, #49237.

It may have to do with the rsync server problems; see #49224.

comment:3 Changed 6 years ago by ryandesign (Ryan Schmidt)

Until the rsync server is fixed, you can update MacPorts by downloading the appropriate OS-X-version-specific installer from the MacPorts web site. This will not erase your installed ports.

I did not see one, but if you see an error message at the end of the installer when it tries to contact the rsync server, you can ignore it; MacPorts should still have been successfully updated, which you can verify by typing "port version".

comment:4 Changed 6 years ago by EnekoGotzon

Cc: enekogotzon@… added

Cc Me!

comment:5 Changed 6 years ago by rubendibattista (Ruben Di Battista)

Cc: rubendibattista@… added

Cc Me!

comment:6 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: rhett.lhy@… gsulsh57@… added

Has duplicates #49240, #49242.

comment:7 Changed 6 years ago by rnspayne@…

Cc: rnspayne@… added

Cc Me!

comment:8 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: jimmymbreen@… added
Component: baseserver/hosting
Owner: changed from macports-tickets@… to admin@…

Has duplicate #49243.

comment:9 Changed 6 years ago by Ionic (Mihai Moldovan)

Please use sudo port sync to synchronize your ports tree if a base upgrade is not necessary for the time being.

The selfupdate operation is a "base upgrade" + "sync" operation at once.

comment:10 Changed 6 years ago by jmroot (Joshua Root)

base.tar.rmd160 was created about half an hour before base.tar, so it's from the previous update run.

ports.tar and ports.tar.rmd160 are from the same update run, so can be verified, but they're stale.

comment:11 Changed 6 years ago by hapaguy (Brian Kurt Fujikawa)

Cc: brian.fujikawa@… added

Cc Me!

comment:12 Changed 6 years ago by js9986@…

Cc: js9986@… added

Cc Me!

comment:13 Changed 6 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:14 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: farmer.tseng@… added

Has duplicate #49244.

comment:15 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: andy@… mark@… added

Has duplicate #49245.

comment:16 Changed 6 years ago by chihangli@…

Cc: chihangli@… added

Cc Me!

comment:17 Changed 6 years ago by tpmanojm@…

Cc Me!

comment:18 Changed 6 years ago by andy@…

How long should "sudo port sync" take to run? It's been going nearly 15 minutes with only the "---> Updating the ports tree" message. This is longer than it took to download the installation package.

comment:19 Changed 6 years ago by ryandesign (Ryan Schmidt)

The rsync server is broken; trying to use it is pointless until the administrator fixes it.

comment:20 Changed 6 years ago by epaell

Cc: elenc@… added

Cc Me!

comment:21 Changed 6 years ago by tpmanojm@…

Cc: tpmanojm@… added

Cc Me!

comment:22 Changed 6 years ago by mjhsieh@…

Cc: mjhsieh@… added

Cc Me!

comment:23 Changed 6 years ago by witoldj@…

Cc: witoldj@… added

Cc Me!

comment:24 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: fabian.glaser@… myrvoll@… added

Has duplicate #49249.

comment:25 Changed 6 years ago by farmer.tseng@…

Cc: farmer.tseng@… removed

Cc Me!

comment:26 in reply to:  24 ; Changed 6 years ago by fabian.glaser@…

Replying to ryandesign@…:

Has duplicate #49249.

I see that there is the same complaint several times, but I still dont' understand how to solve the problem, sync is working fine in my mac, and the following works

==> sudo port sync 
Password:
--->  Updating the ports tree

So what I need to do?
Thansk a lot,

Fabian

Last edited 6 years ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:27 in reply to:  26 Changed 6 years ago by ryandesign (Ryan Schmidt)

Replying to fabian.glaser@…:

Replying to ryandesign@…:

Has duplicate #49249.

I see that there is the same complaint several times, but I still dont' understand how to solve the problem, sync is working fine in my mac, and the following works

==> sudo port sync 
Password:
--->  Updating the ports tree

This ticket is about selfupdate failure. #49224 is about sync failure. They're both caused by the same server problem, and it affects all users that use the rsync server, which MacPorts does by default, so this affects most MacPorts users.

If your sources.conf lists rsync://rsync.macports.org/release/tarballs/ports.tar then sync will finish without error, but you will not actually receive any updates newer than the time the server broke. If your sources.conf lists rsync://rsync.macports.org/release/ports/ then sync will fail and display errors.

So what I need to do?

Wait until the administrator fixes the rsync server, or configure MacPorts to sync using svn instead.

comment:28 Changed 6 years ago by coviex@…

Cc: coviex@… added

Cc Me!

comment:29 Changed 6 years ago by mndavidoff (Monte Davidoff)

Cc: md14-macports@… added

Cc Me!

comment:30 Changed 6 years ago by farmer.tseng@…

Cc: farmer.tseng@… added

Cc Me!

comment:31 Changed 6 years ago by ishtar@…

Cc: ishtar@… added

Cc Me!

comment:32 Changed 6 years ago by gallafent

Cc: william@… added

Cc Me!

comment:33 Changed 6 years ago by roman.dayneko@…

Cc: roman.dayneko@… added

Cc Me!

comment:34 Changed 6 years ago by seb@…

I can't measure the importance of the .pem file, but it seems the openssl check is in bad state.

I sugget a (temporary) workaround:

Edit /opt/local/libexec/macports/lib/macports1.0/macports.tcl

On lines 3429/3430 you'll find:

ui_debug "failed verification with key $pubkey"
ui_debug "openssl output: $result"

Add this command:

set verified 1

And maybe (if you want to remember)

ui_debug "But i take my chance"

comment:35 Changed 6 years ago by seb@…

Cc: seb@… added

Cc Me!

comment:36 Changed 6 years ago by kurtjaeke@…

Cc: kurtjaeke@… added

Cc Me!

comment:37 Changed 6 years ago by a.vincelli@…

Cc: a.vincelli@… added

Cc Me!

comment:38 Changed 6 years ago by robin.newman@…

Cc: robin.newman@… added

Cc Me!

comment:39 Changed 6 years ago by djlambert (Derek J. Lambert)

Cc: dlambert@… added

Cc Me!

comment:40 Changed 6 years ago by neurodroid (Christoph Schmidt-Hieber)

Cc: christsc@… added

Cc Me!

comment:41 Changed 6 years ago by avysk (Alexey Vyskubov)

Cc: tascafoo@… added

Cc Me!

comment:42 Changed 6 years ago by peter.mcalpine@…

Cc: peter.mcalpine@… added

Cc Me!

comment:43 Changed 6 years ago by m1@…

Cc: m1@… added

Cc Me!

comment:44 Changed 6 years ago by MaurizioLoreti

Cc: Maurizio.Loreti@… added

Cc Me!

comment:45 Changed 6 years ago by joaogeada (Joao Geada)

Cc: joao@… added

Cc Me!

comment:46 Changed 6 years ago by john@…

Cc: john@… added

Cc Me!

comment:47 Changed 6 years ago by szibetti@…

Cc: szibetti@… added

Cc Me!

comment:48 Changed 6 years ago by mjwybrow (Michael Wybrow)

Cc: Michael.Wybrow@… added

Cc Me!

comment:49 Changed 6 years ago by moritz.peter@…

Cc: moritz.peter@… added

Cc Me!

comment:50 Changed 6 years ago by leeawalsh@…

Cc: leeawalsh@… added

Cc Me!

comment:51 Changed 6 years ago by seblec@…

Hi! I've the same failure to verify signature… :/

comment:52 Changed 6 years ago by seblec@…

Cc: seblec@… added

Cc Me!

comment:53 Changed 6 years ago by glen@…

Cc: glen@… added

Cc Me!

comment:54 Changed 6 years ago by deesto (John S. De Stefano Jr.)

Cc: deesto@… added

Cc Me!

comment:55 Changed 6 years ago by michelle.lynn.gill@…

Cc: michelle.lynn.gill@… added

Cc Me!

comment:56 Changed 6 years ago by smparkes@…

Cc: smparkes@… added

Cc Me!

comment:57 Changed 6 years ago by vcultharris (L.T. Harris)

Cc: ltharris@… added

Cc Me!

comment:58 Changed 6 years ago by alan.mock@…

Cc: alan.mock@… added

Cc Me!

comment:59 Changed 6 years ago by grimreaper (Eitan Adler)

Cc: lists@… added

Cc Me!

comment:60 Changed 6 years ago by morrell@…

Cc: morrell@… added

Cc Me!

comment:61 Changed 6 years ago by bunk3m (Bunk3m)

Cc: bunk3m@… added

Cc Me!

comment:62 Changed 6 years ago by absima@…

Cc: absima@… added

Cc Me!

comment:63 Changed 6 years ago by steve.sell@…

Cc: steve.sell@… added

Cc Me!

comment:64 Changed 6 years ago by tiasus@…

Cc: tiasus@… added

Cc Me!

comment:65 Changed 6 years ago by smeingast (Stefan Meingast)

Cc: stefan.meingast@… added

Cc Me!

comment:66 Changed 6 years ago by nortcele

Cc: Joel.Brogniart@… added

Cc Me!

comment:67 Changed 6 years ago by aoeumacports@…

Cc: aoeumacports@… added

Cc Me!

comment:68 Changed 6 years ago by zaxdo@…

Cc: zaxdo@… added

Cc Me!

comment:69 Changed 6 years ago by hallo@…

Cc Me!

comment:70 Changed 6 years ago by thomas.gimpel@…

Cc: thomas.gimpel@… added

Cc Me!

comment:71 Changed 6 years ago by netgamer7 (Roger Ward)

Cc: rogerw@… added

Cc Me!

comment:72 Changed 6 years ago by raju.apm@…

Cc: raju.apm@… added

Cc Me!

comment:73 Changed 6 years ago by ken.mcglothlen@…

Cc: ken.mcglothlen@… added

Cc Me!

comment:74 Changed 6 years ago by stephenhamilton@…

Cc: stephenhamilton@… added

Cc Me!

comment:75 Changed 6 years ago by eddieh (Eddie Hillenbrand)

Cc: eh88@… added

Cc Me!

comment:76 Changed 6 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:77 Changed 6 years ago by samuel.hofmann@…

Cc: samuel.hofmann@… added

Cc Me!

comment:78 Changed 6 years ago by brian.topping@…

Cc: brian.topping@… added

Cc Me!

comment:79 Changed 6 years ago by rodolphefouquet@…

Last edited 6 years ago by rodolphefouquet@… (previous) (diff)

comment:80 Changed 6 years ago by rodolphefouquet@…

Cc: rodolphefouquet@… added

Cc Me!

comment:81 Changed 6 years ago by erich3@…

Cc: erich3@… added

Cc Me!

comment:82 in reply to:  34 ; Changed 6 years ago by neverpanic (Clemens Lang)

Replying to seb@…:

I sugget a (temporary) workaround:

Edit /opt/local/libexec/macports/lib/macports1.0/macports.tcl

On lines 3429/3430 you'll find:

ui_debug "failed verification with key $pubkey"
ui_debug "openssl output: $result"

Add this command:

set verified 1

And maybe (if you want to remember)

ui_debug "But i take my chance"

This is a bad idea, because it breaks the chain of trust that normally ensures the macports update has not been tampered with. If your version of MacPorts is outdated, it is a much better idea to download one of the installers, because those are signed with an Apple Developer ID. Running this installer will only update MacPorts itself and leave your installed ports as-is.

comment:83 Changed 6 years ago by brian.topping@…

Cc: brian.topping@… removed

Cc Me!

comment:84 Changed 6 years ago by seblec@…

Cc: seblec@… removed

Cc Me!

comment:85 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: fritzs@… clint.olsen@… michaelwallis@… p.fabrizio.salvatore@… pe8ter@… added

Has duplicates #49260, #49261, #49262, #49263.

comment:86 Changed 6 years ago by alandir2@…

Cc: alandir2@… added

Cc Me!

comment:87 Changed 6 years ago by 0xced (Cédric Luthi)

Cc: cedric.luthi@… added

Cc Me!

comment:88 Changed 6 years ago by eric.lebigot@…

Cc: eric.lebigot@… added

Cc Me!

comment:89 Changed 6 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:90 Changed 6 years ago by kngspook@…

Cc: kngspook@… added

Cc Me!

comment:91 Changed 6 years ago by kngspook@…

So...what's the plan for this? Has anyone reached out to the sysadmin?

comment:92 Changed 6 years ago by jackh48@…

Cc: jackh48@… added

Cc Me!

comment:93 Changed 6 years ago by anthony@…

Cc: anthony@… added

Cc Me!

comment:94 Changed 6 years ago by boehm.adam@…

Cc: boehm.adam@… added

Cc Me!

comment:95 Changed 6 years ago by p.perroud@…

Cc: p.perroud@… added

Cc Me!

comment:96 in reply to:  91 Changed 6 years ago by ryandesign (Ryan Schmidt)

Replying to kngspook@…:

So...what's the plan for this? Has anyone reached out to the sysadmin?

The plan is for the administrator to fix the server. The administrator is assigned to this ticket, meaning he receives an email notification for every comment entered here. I also spoke directly with his manager today.

comment:97 Changed 6 years ago by axet (Alexey Kuznetsov)

Cc: kuznetsov.alexey@… added

Cc Me!

comment:98 Changed 6 years ago by komana.rakoma@…

CC Me!

comment:99 Changed 6 years ago by bradley@…

Cc: bradley@… added

Cc Me!

comment:100 Changed 6 years ago by todmorrison (Tod Morrison)

Cc: todmorrison@… added

Cc Me!

comment:101 Changed 6 years ago by permezel@…

Cc: permezel@… added

Cc Me!

comment:102 Changed 6 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:103 Changed 6 years ago by r1pp3r@…

Cc: r1pp3r@… added

Cc Me!

comment:104 Changed 6 years ago by suneilp@…

Cc: suneilp@… added

Cc Me!

comment:105 Changed 6 years ago by meckiemac@…

Cc: meckiemac@… added

Cc Me!

comment:106 in reply to:  82 Changed 6 years ago by seb@…

Replying to cal@…:

Replying to seb@…:

I sugget a (temporary) workaround:

Edit /opt/local/libexec/macports/lib/macports1.0/macports.tcl

On lines 3429/3430 you'll find:

ui_debug "failed verification with key $pubkey"
ui_debug "openssl output: $result"

Add this command:

set verified 1

And maybe (if you want to remember)

ui_debug "But i take my chance"

This is a bad idea, because it breaks the chain of trust that normally ensures the macports update has not been tampered with. If your version of MacPorts is outdated, it is a much better idea to download one of the installers, because those are signed with an Apple Developer ID. Running this installer will only update MacPorts itself and leave your installed ports as-is.

I'm not sure you're right. Because as far as i can understand, the line wich is impacted by the test is only a "ssh key" validation. It does not contain any "mac port" data. All the data that are synchronized before and after seem to work with dependencies for me. If what you say is correct, it would mean macport does not have really establish an "El Capitan" "chain of trust". If what i guess is true, it's only an ssh key wich is incorrectly built from the admin. Anyway, i needed my macports yesterday to build my application. It worked fine for me ;)

comment:107 Changed 6 years ago by persramd@…

On getting the following error: Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source! ...

I tried the above fix. With it, I was able to selfupdate.

However, now (with the temp fix still in place), when I try to upgrade outdated, I get a new error. ,shown below. Apologies for including all this text in here. I am not sure where to put it in this message.

(Removed by admin. File a separate ticket against ld64-latest, and add log as an attachment, don't paste it into a comment.)

Last edited 6 years ago by jmroot (Joshua Root) (previous) (diff)

comment:108 Changed 6 years ago by persramd@…

Cc: persramd@… added

Cc Me!

comment:109 Changed 6 years ago by mkikkawa@…

Cc: mkikkawa@… added

Cc Me!

comment:110 Changed 6 years ago by petermisak (Peter Misak)

Cc: peter.misak@… added

Cc Me!

comment:111 Changed 6 years ago by pmo@…

Cc: pmo@… added

Cc Me!

comment:112 Changed 6 years ago by Quibi (Quibizo)

When I try

sudo port -vdt sync

I get the following errors:

--->  Updating the ports tree
Synchronizing local ports tree from rsync://rsync.macports.org/release/tarballs/ports.tar
DEBUG: /usr/bin/rsync -rtzv --delete-after  rsync://rsync.macports.org/release/tarballs/ports.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
receiving file list ... done

sent 36 bytes  received 70 bytes  70.67 bytes/sec
total size is 62720000  speedup is 591698.11
DEBUG: /usr/bin/rsync -rtzv --delete-after  rsync://rsync.macports.org/release/tarballs/ports.tar.rmd160 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
receiving file list ... done

sent 36 bytes  received 77 bytes  45.20 bytes/sec
total size is 512  speedup is 4.53
DEBUG: successful verification with key /opt/local/share/macports/macports-pubkey.pem
DEBUG: /usr/bin/tar -C /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/tmp -xf /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports.tar
DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/PortIndex_darwin_15_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
receiving file list ... rsync: change_dir "tarballs/PortIndex_darwin_15_i386" (in release) failed: No such file or directory (2)
done

sent 4 bytes  received 9 bytes  8.67 bytes/sec
total size is 0  speedup is 0.00
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(1400) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/PortIndex_darwin_15_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
Exit code: 23
DEBUG: Synchronization of the PortIndex failed doing rsync
Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports

Sorry if this an useless information.

comment:113 Changed 6 years ago by starcpw@…

Cc Me!

Last edited 6 years ago by starcpw@… (previous) (diff)

comment:114 Changed 6 years ago by Stochasticus@…

Cc: Stochasticus@… added

Cc Me!

comment:115 Changed 6 years ago by bodait

Cc: bodait@… added

Cc Me!

comment:116 Changed 6 years ago by neilt (Neil Tiffin)

Cc: neilt@… added

Cc Me!

comment:117 Changed 6 years ago by stromnov (Andrew Stromnov)

Cc: stromnov@… added

Cc Me!

comment:118 Changed 6 years ago by matt@…

Cc: matt@… added

Cc Me!

comment:119 Changed 6 years ago by macubergeek@…

Just did port selfupdate and had this error like many before me:

Error: Failed to verify signature for MacPorts source!
Please run `port -v selfupdate' for details.
Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!

--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 69 bytes  70.00 bytes/sec
total size is 27013120  speedup is 257267.81
receiving file list ... done

sent 36 bytes  received 76 bytes  74.67 bytes/sec
total size is 512  speedup is 4.57
Error: Failed to verify signature for MacPorts source!
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!
Last edited 6 years ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:120 Changed 6 years ago by summers@…

Cc: summers@… added

Cc Me!

comment:121 Changed 6 years ago by jsalort (Julien Salort)

Cc: lists@… added

Cc Me!

comment:122 Changed 6 years ago by edgtzolvera@…

Cc: edgtzolvera@… added

Cc Me!

comment:123 Changed 6 years ago by tsume82 (Giovanni Iacca)

Cc: giovanni.iacca@… added

Cc Me!

comment:124 Changed 6 years ago by rohall@…

Cc: rohall@… added

Cc Me!

comment:125 Changed 6 years ago by Feuermurmel (Michael Schwarz)

Cc: michi.schwarz@… added

Cc Me!

comment:126 Changed 6 years ago by michelle.lynn.gill@…

Cc: michelle.lynn.gill@… removed

Cc Me!

comment:127 in reply to:  3 ; Changed 6 years ago by macubergeek@…

Replying to ryandesign@…:

Until the rsync server is fixed, you can update MacPorts by downloading the appropriate OS-X-version-specific installer from the MacPorts web site. This will not erase your installed ports.

I did not see one, but if you see an error message at the end of the installer when it tries to contact the rsync server, you can ignore it; MacPorts should still have been successfully updated, which you can verify by typing "port version".

Tried this but it didn't fix the problem. Still getting error Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!

comment:128 Changed 6 years ago by tk7r (Thomas Kotzian)

Cc: thomas.kotzian@… added

Cc Me!

comment:129 Changed 6 years ago by fracai

Cc: arno@… added

Cc Me!

comment:130 Changed 6 years ago by help@…

Cc: help@… added

Cc Me!

comment:131 Changed 6 years ago by davidwalton3142@…

Cc: davidwalton3142@… added

Cc Me!

comment:132 Changed 6 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:133 Changed 6 years ago by jasonw@…

Cc: jasonw@… added

Cc Me!

comment:134 Changed 6 years ago by vosslab (Neil Voss)

Cc: vossman77@… added

Cc Me!

comment:135 Changed 6 years ago by majoc-at-astro (majoc-at-astro)

Cc: majoc@… added

Cc Me!

comment:136 Changed 6 years ago by texas-swift

Cc: vfrspencer@… added

Cc Me!

comment:137 Changed 6 years ago by jmgoicolea (Jose Goicolea)

Cc: jose.goicolea@… added

Cc Me!

comment:138 Changed 6 years ago by j.albarran@…

Cc: j.albarran@… added

Cc Me!

comment:139 Changed 6 years ago by eschnett (Erik Schnetter)

Cc: schnetter@… added

Cc Me!

comment:140 Changed 6 years ago by alessandropaggi (alessandro)

Cc: alessandro.paggi@… added

Cc Me!

comment:141 Changed 6 years ago by H3ik0

Cc: foren@… added

Cc Me!

comment:142 Changed 6 years ago by bhadder@…

Cc: bhadder@… added

Cc Me!

comment:143 Changed 6 years ago by ktitt27@…

Cc: ktitt27@… added

Cc Me!

comment:144 in reply to:  1 Changed 6 years ago by ktitt27@…

Replying to mherdeg@…:

This problem repros for me using OS X 10.11 and the latest stable "MacPorts-2.3.4-10.11". ...

As he already mentioned, it has also come to my attention that MacPorts-2.3.4 on OSX 10.11 causes the same issue.

comment:145 Changed 6 years ago by marco.outatime@…

Cc: marco.outatime@… added

Cc Me!

comment:146 Changed 6 years ago by kngspook@…

Is there an ETA on this fix?

comment:147 Changed 6 years ago by StanSanderson

Cc: stansand@… added

Cc Me!

comment:148 Changed 6 years ago by StanSanderson

Cc: stansand@… removed
Last edited 6 years ago by StanSanderson (previous) (diff)

comment:149 Changed 6 years ago by josephaw@…

Cc: josephaw@… added

Cc Me!

comment:150 Changed 6 years ago by jharmon@…

yikes!

comment:151 in reply to:  127 Changed 6 years ago by jharmon@…

it doesn't solve the selfupdate problem. what it does is updates your macports version. THEN you have to use port sync to update your tree, and can carry on. the only thing that is broken is updating the macports application itself, which is normally done during a self update IN ADDITION to port sync

Replying to macubergeek@…:

Replying to ryandesign@…:

Until the rsync server is fixed, you can update MacPorts by downloading the appropriate OS-X-version-specific installer from the MacPorts web site. This will not erase your installed ports.

I did not see one, but if you see an error message at the end of the installer when it tries to contact the rsync server, you can ignore it; MacPorts should still have been successfully updated, which you can verify by typing "port version".

Tried this but it didn't fix the problem. Still getting error Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!

comment:152 Changed 6 years ago by marco.outatime@…

Hi, I just want to notify that at the moment I'm unable to use Macports at all. I've just installed it from scratch on El Capitan. The "port search" is broken and requires "port selfupdate", which cannot be done because of the signature failure reported in this thread. If you know a workaround let me know. Thanks.

comment:153 Changed 6 years ago by marco-comini (Marco Comini)

Cc: marco.comini@… added

Cc Me!

comment:154 Changed 6 years ago by ryandesign (Ryan Schmidt)

"port search" doesn't require "port selfupdate"; it does require a portindex, which is created either by running "sudo port selfupdate" (which you can't right now because the rsync server is broken) or by running "sudo port sync" (which you can do if you change you MacPorts to sync with svn instead of rsync).

comment:155 Changed 6 years ago by marco.outatime@…

port search XXX
Warning: Can't open index file for source: rsync://rsync.macports.org/release/tarballs/ports.tar
Error: search for name XXX failed: No index(es) found! Have you synced your port definitions? Try running 'port selfupdate'.
No match for XXX found

Ah. So please let us know when you find a workaround for both the rsync and the signature failure. For the rsync server do you have an ETA? Thank you.

comment:156 Changed 6 years ago by ryandesign (Ryan Schmidt)

The workaround for sync failure is in comment:27. The workaround for selfupdate failure is in comment:3.

comment:157 Changed 6 years ago by skymoo (Adam Mercer)

Cc: ram@… added

Cc Me!

comment:158 Changed 6 years ago by deyv@…

Cc: deyv@… added

Cc Me!

comment:159 in reply to:  154 ; Changed 6 years ago by atma@…

Replying to ryandesign@…:

"port search" doesn't require "port selfupdate"; it does require a portindex, which is created either by running "sudo port selfupdate" (which you can't right now because the rsync server is broken) or by running "sudo port sync" (which you can do if you change you MacPorts to sync with svn instead of rsync).

MacPorts worked fine for me. I installed them today via "El Capitan" pkg on the frontpage. Then synced the pkg-list running "sudo port sync". It took some time to download the entire tree. Then I proceed installing 'vim' and 'postgresql' normally.

comment:160 Changed 6 years ago by macports.org@…

Cc: macports.org@… added

Cc Me!

comment:161 in reply to:  159 Changed 6 years ago by p.fabrizio.salvatore@…

Replying to atma@…:

Replying to ryandesign@…:

"port search" doesn't require "port selfupdate"; it does require a portindex, which is created either by running "sudo port selfupdate" (which you can't right now because the rsync server is broken) or by running "sudo port sync" (which you can do if you change you MacPorts to sync with svn instead of rsync).

MacPorts worked fine for me. I installed them today via "El Capitan" pkg on the frontpage. Then synced the pkg-list running "sudo port sync". It took some time to download the entire tree. Then I proceed installing 'vim' and 'postgresql' normally.

I run the same command and it does indeed work for me too. Just to clarify, you don't 'need' to install vim and postgresql, it is just that you do need them, right?

Thanks!

Fab

comment:162 Changed 6 years ago by meckiemac@…

As long I don't get an official answer why the key changed I wouldn't trust this server anymore. In my view this is a security breach and I stop upgrading until a real solution. Who is the owner of the server?

Last edited 6 years ago by meckiemac@… (previous) (diff)

comment:163 Changed 6 years ago by joaogeada (Joao Geada)

I agree 100% with meckiemac.

Right now I am assuming the macports server has been compromised and will not trust anything served from there until I hear a satisfactory official answer.

comment:164 Changed 6 years ago by alessandropaggi (alessandro)

Cc: alessandro.paggi@… removed

Cc Me!

comment:165 Changed 6 years ago by macports@…

Could we perhaps get some "official" statement/info, and a recommend safe workaround (if there is one) or something like that put on the MacPorts website? e.g. the ProblemHotlist? or even higher up (download/front page of macports project)

I suspect this would qualify as at least worthy of the Hotlist given its a couple of days old, with ~13 duplicates, ~160 comments and is a show-stopper for some (at least without a workaround).

comment:166 Changed 6 years ago by ryandesign (Ryan Schmidt)

The server was not compromised, but the disk was corrupted. The administrator has repaired the corruption. In a few hours I will check to see if the files are now ok.

comment:167 Changed 6 years ago by ilysbv@…

cc me

comment:168 in reply to:  166 ; Changed 6 years ago by jackh48@…

Replying to ryandesign@…:

The server was not compromised, but the disk was corrupted. The administrator has repaired the corruption. In a few hours I will check to see if the files are now ok.

Works for me!

comment:169 in reply to:  168 Changed 6 years ago by pmo@…

Back in business. All OK. Thanks for the maintenance work. Cheers.

comment:170 Changed 6 years ago by macuserguru

It works now but one rsync error comes

$ sudo port -v selfupdate
.......
sent 64 bytes  received 636 bytes  280.00 bytes/sec
total size is 512  speedup is 0.73
receiving file list ... rsync: change_dir "tarballs/PortIndex_darwin_15_i386" (in release) failed: No such file or directory (2)
done

sent 4 bytes  received 9 bytes  8.67 bytes/sec
total size is 0  speedup is 0.00
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(1400) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/PortIndex_darwin_15_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
Exit code: 23
Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports
Adding port aqua/Quicksilver
Adding port aqua/TeXShop3
.......
Adding subport xtide-data

Total number of ports parsed:	543 
Ports successfully parsed:	543 
Ports failed:			0 
Up-to-date ports skipped:	24332

--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated

comment:171 Changed 6 years ago by macuserguru

Cc: fritzs@… removed

Cc Me!

comment:172 Changed 6 years ago by macuserguru

Cc: fritzs@… added

Cc Me!

comment:173 in reply to:  170 Changed 6 years ago by ryandesign (Ryan Schmidt)

Replying to fritzs@…:

receiving file list ... rsync: change_dir "tarballs/PortIndex_darwin_15_i386" (in release) failed: No such file or directory (2)

That's #49050.

comment:174 Changed 6 years ago by tsume82 (Giovanni Iacca)

Cc: giovanni.iacca@… removed

Cc Me!

comment:175 Changed 6 years ago by ishtar@…

Cc: ishtar@… removed

Cc Me!

comment:176 Changed 5 years ago by macuserguru

those are now:

$ sudo port -v selfupdate
......
sent 64 bytes  received 636 bytes  280.00 bytes/sec
total size is 512  speedup is 0.73
receiving file list ... rsync: change_dir "tarballs/PortIndex_darwin_15_i386" (in release) failed: No such file or directory (2)
done

sent 4 bytes  received 9 bytes  8.67 bytes/sec
total size is 0  speedup is 0.00
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(1400) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/PortIndex_darwin_15_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
Exit code: 23
Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports
Adding port aqua/emacs-mac-app
Adding port aqua/terminal-notifier
$ port clean --all installed
--->  Cleaning aspell
Warning: Only cleaning in ~/.macports; insufficient privileges for standard locations
--->  Cleaning aspell-dict-de
Warning: Only cleaning in ~/.macports; insufficient privileges for standard locations
--->  Cleaning aspell-dict-en
Warning: Only cleaning in ~/.macports; insufficient privileges for standard locations
--->  Cleaning atk
Warning: Only cleaning in ~/.macports; insufficient privileges for standard locations
--->  Cleaning autoconf
Warning: Only cleaning in ~/.macports; insufficient privileges for standard locations

comment:177 in reply to:  176 Changed 5 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: newclosed

The rsync server disk corruption (#49224) was fixed some days ago.

Replying to fritzs@…:

receiving file list ... rsync: change_dir "tarballs/PortIndex_darwin_15_i386" (in release) failed: No such file or directory (2)

That's #49050.

comment:178 Changed 5 years ago by bradley@…

Cc: bradley@… removed

Cc Me!

comment:179 Changed 5 years ago by coviex@…

Cc: coviex@… removed

Cc Me!

Note: See TracTickets for help on using tickets.