On 03/05 06:28, Jeremy Evans wrote:
> On 03/05 07:56, Kurt Mosiejczuk wrote:
> > On Sun, Mar 06, 2022 at 01:25:24AM +0100, Christian Weisgerber wrote:
> > > Kurt Mosiejczuk:
> > 
> > > > > Log message:
> > > > > Update nokogiri to 1.13.1
> > 
> > > > This doesn't build on sparc64. I'm noticing amd64 also no longer
> > > > has any nokogiri packages so I'm guessing it failed there too.
> > 
> > > It builds fine on amd64.
> > > The previous snapshot still had 1.11.7.  The latest one, which is
> > > making its way to the mirrors now, has 1.13.1.
> > 
> > Ah. so the transer was incomplete. However, I still can't build 1.13.1 
> > locally
> > on amd64. It fails the same way on my laptop as it does on sparc64.
> 
> Thanks for the report.  I'll try building an sparc64 and see if I can
> fix it.

It doesn't look like there are any problems, modulo library versions,
which I assume is because I didn't do a full rebuild of dependencies.
It even works fine at runtime (see below).

Kurt, can you post what problems you are experiencing?

Thanks,
Jeremy

ports$ make package
===>  Faking installation for ruby30-nokogiri-1.13.1
if [ -d /usr/ports/pobj/nokogiri-1.13.1-ruby30/gem-tmp/.gem/ruby/3.0/bin ]; 
then  /usr/ports/pobj/nokogiri-1.13.1-ruby30/bin/install -d -m 755 
/usr/ports/pobj/nokogiri-1.13.1-ruby30/fake-sparc64-ruby30/usr/local/bin;  for 
f in /usr/ports/pobj/nokogiri-1.13.1-ruby30/gem-tmp/.gem/ruby/3.0/bin/*; do  
/usr/ports/pobj/nokogiri-1.13.1-ruby30/bin/install -c -m 755 $f 
/usr/ports/pobj/nokogiri-1.13.1-ruby30/fake-sparc64-ruby30/usr/local/bin;  
done;  rm -r /usr/ports/pobj/nokogiri-1.13.1-ruby30/gem-tmp/.gem/ruby/3.0/bin;  
fi;  /usr/ports/pobj/nokogiri-1.13.1-ruby30/bin/install -d -m 755 
/usr/ports/pobj/nokogiri-1.13.1-ruby30/fake-sparc64-ruby30/usr/local/lib/ruby/gems/3.0;
  cd /usr/ports/pobj/nokogiri-1.13.1-ruby30/gem-tmp/.gem/ruby/3.0 && mv * 
/usr/ports/pobj/nokogiri-1.13.1-ruby30/fake-sparc64-ruby30/usr/local/lib/ruby/gems/3.0;
  if [ 'X' != 
"Xlib/ruby/gems/3.0/extensions/sparc64-openbsd/3.0/nokogiri-1.13.1/gem.build_complete"
 ]; then  mkdir -p 
/usr/ports/pobj/nokogiri-1.13.1-ruby30/fake-sparc64-ruby30/usr/local/lib/ruby/gems/3.0/extensions/sparc64-openbsd/3.0/nokogiri-1.13.1;
  touch 
/usr/ports/pobj/nokogiri-1.13.1-ruby30/fake-sparc64-ruby30/usr/local/lib/ruby/gems/3.0/extensions/sparc64-openbsd/3.0/nokogiri-1.13.1/gem.build_complete;
  fi
===>  Building package for ruby30-nokogiri-1.13.1
Create 
/var/www/htdocs/pub/OpenBSD/snapshots/packages/sparc64/all/ruby30-nokogiri-1.13.1.tgz
Error: Libraries in packing-lists in the ports tree
       and libraries from installed packages don't match
--- /tmp/dep_cache.j8YOrpwJM/portstree-ruby30-nokogiri-1.13.1   Sun Mar  6 
04:11:41 2022
+++ /tmp/dep_cache.j8YOrpwJM/inst-ruby30-nokogiri-1.13.1        Sun Mar  6 
04:11:41 2022
@@ -1,5 +1,5 @@
 -W exslt.9.8
--W xml2.17.1
+-W xml2.17.0
 -W xslt.4.0
 -W gcrypt.21.0
 -W gpg-error.3.23
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3454 'wantlib-args': 
@case X${_DEPENDS_CACHE} in  X) _DEPENDS_CACHE=$(doas -u _pb...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2147 
'/var/www/htdocs/pub/OpenBSD/snapshots/packages/sparc64/all/ruby30-nokogiri-1.13.1.tgz')
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2628 
'_internal-package': @case X${_DEPENDS_CACHE} in  X) _DEPENDS_CACHE=$(doas -...)
*** Error 2 in /usr/ports/textproc/ruby-nokogiri 
(/usr/ports/infrastructure/mk/bsd.port.mk:2607 'package': 
@lock=ruby30-nokogiri-1.13.1;  ex...)
ports$ PKG_CREATE_NO_CHECKS=Yes make package
`/usr/ports/pobj/nokogiri-1.13.1-ruby30/fake-sparc64-ruby30/.fake_done' is up 
to date.
===>  Building package for ruby30-nokogiri-1.13.1
Create 
/var/www/htdocs/pub/OpenBSD/snapshots/packages/sparc64/all/ruby30-nokogiri-1.13.1.tgz
Creating package ruby30-nokogiri-1.13.1
Link to 
/var/www/htdocs/pub/OpenBSD/snapshots/packages/sparc64/ftp/ruby30-nokogiri-1.13.1.tgz

ports$ ftp -o - http://www.openbsd.org/index.html 2>/dev/null | ruby30 -r 
nokogiri -e "puts('Title: ' + Nokogiri::HTML5(ARGF.read).title)"
Title: OpenBSD

Reply via email to