On 2022/08/29 14:10, Rafael Sadowski wrote:
>
> I caught a victim. ruby-gpgme ruby30 and ruby31 packaged fine but not
> ruby27:
>
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/gpgme-1.12.0.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/gpgme-1.13.1.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/gpgme-1.9.0.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/libassuan-2.4.3.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/libassuan-2.5.1.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/libassuan-2.5.3.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/libgpg-error-1.27.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/libgpg-error-1.32.tar.bz2 does not exist
> Error: /usr/ports/pobj/gpgme-2.0.20-ruby27/fake-amd64-ruby27/usr/local/lib/ruby/gems/2.7/gems/gpgme-2.0.20/ports/archives/libgpg-error-1.37.tar.bz2 does not exist
>
>
> Should we drop the tarballs?
That doesn't make sense, those tar files aren't in the PLIST (and
ruby27-gpgme builds OK for me with the update)
No comments:
Post a Comment