Re: osabi in -current in some difficulty?
On Wed, Mar 20, 2019 at 05:23:55AM +1100, Matthew Green wrote: > > I've confirmed with upstream that this library is just obsolete. The > > code to support it in the X server was removed 12 years ago. > > > > I've removed lbxproxy and proxymngr from pkgsrc. > > last i saw, pkgsrc was still had the Xprint components, > which have been obsolete a similar or even longer time. > (i removed lbx and Xprint stuff from xsrc almost 10 > years ago.) > > maybe there is more you can delete :-) Thanks for the nudge, I deleted the Xprint related packages. Thomas
re: osabi in -current in some difficulty?
> I've confirmed with upstream that this library is just obsolete. The > code to support it in the X server was removed 12 years ago. > > I've removed lbxproxy and proxymngr from pkgsrc. last i saw, pkgsrc was still had the Xprint components, which have been obsolete a similar or even longer time. (i removed lbx and Xprint stuff from xsrc almost 10 years ago.) maybe there is more you can delete :-) .mrg.
Re: osabi in -current in some difficulty?
On Tue, Mar 19, 2019 at 02:39:20PM +0100, Thomas Klausner wrote: > I've removed lbxproxy and proxymngr from pkgsrc. Modular-xorg built completely without a hiccup for me. Thank you! -- These are not the droids you are looking for.
Re: osabi in -current in some difficulty?
On Mon, Mar 18, 2019 at 01:36:05PM +0100, Thomas Klausner wrote: > On Mon, Mar 18, 2019 at 03:59:07AM -0400, Bob Bernstein wrote: > > However, a fly did find the ointment when it was lbxproxy's turn: > > I think this was broken with one of the recent xorg package updates. > It also fails for me in the same way. I've confirmed with upstream that this library is just obsolete. The code to support it in the X server was removed 12 years ago. I've removed lbxproxy and proxymngr from pkgsrc. Thomas
Re: osabi in -current in some difficulty?
I can't say much about the compiler version, I think I've seen some relatively recent changes. I have two pkgsrc build hosts - one with X11_TYPE modular, using the earlier version, the other - without X11_TYPE, using the later - failing for you - version, so I can't really test it ( or so I *think*, it being an operative word ), without messing the one using built-in Xorg (the test systems use pkgin for installation). The interesting (and for tech-x11 as well) thing might be that I tested my HP Envy 17 laptop with modular Xorg (using an 8GB USB stick with live-image from yesterday, removing /usr/X11R7 and pkgin installation of modular Xorg, surprisingly faster working than one might expect) and compared the Xorg log files. While similar, there were differences important enough to make me switch to modular Xorg permanently. My NVidia 950M was apparently not yet supported by the DRI2 infrstructure, but the built-in Xorg still recognizes it, loads the nouveau module, eventually failing and unloading it, to let the Intel driver carry on - which it does, and works, with the expection of AIGLX failing. The modular Xorg log file does not show any reference to the NVidia card (I took it off the xorg.conf file), AIGLX succeeds. The server versions of both the built-in and modular Xorg are the same. Right now I am building xfce4 with modular Xorg, after that I will switch to modular ( should be as easy as hiding the old /usr/pkg, /var/dg/pkg, /usr/X11R7, making two copies of /etc/rc.conf to account for the different installed packages, installing and running pkgin from the new modular Xorg build host; this will give me the opportunity to swap easily between the two Xorg options with the corresponding set of dependent packages). On Mon, 18 Mar 2019 at 18:27, Bob Bernstein wrote: > > I installed ccache and made my /etc/mk.conf look like yours: > > X11_TYPE=modular > CCACHE_DIR?=/usr/pkg/.ccache > PKGSRC_COMPILER=ccache gcc > > ...and cd'd to /usr/pkgsrc/x11/lbxproxy to do a 'make clean > clean-depends'. I ran aground on the same warning-treated-as-error > as before. What I notice is we are using "slightly" different > versions of gcc. > > Yours: > > # gcc --version > > gcc (nb1 20190119) 7.4.0 > > Mine: > # gcc --version > gcc (nb2 20190226) 7.4.0 > > And for the record: > # uname -a > NetBSD nebby.localdomain 8.99.35 NetBSD 8.99.35 (GENERIC) #0: Fri > Mar 15 22:09:21 UTC 2019 > mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 > > I will take the liberty again to attach the make output. > > Thank you! > > -- > Bob Bernstein > --
Re: osabi in -current in some difficulty?
I installed ccache and made my /etc/mk.conf look like yours: X11_TYPE=modular CCACHE_DIR?=/usr/pkg/.ccache PKGSRC_COMPILER=ccache gcc ...and cd'd to /usr/pkgsrc/x11/lbxproxy to do a 'make clean clean-depends'. I ran aground on the same warning-treated-as-error as before. What I notice is we are using "slightly" different versions of gcc. Yours: > # gcc --version > gcc (nb1 20190119) 7.4.0 Mine: # gcc --version gcc (nb2 20190226) 7.4.0 And for the record: # uname -a NetBSD nebby.localdomain 8.99.35 NetBSD 8.99.35 (GENERIC) #0: Fri Mar 15 22:09:21 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 I will take the liberty again to attach the make output. Thank you! -- Bob Bernstein Script started on Mon Mar 18 14:05:05 2019 => Bootstrap dependency digest>=20010302: found digest-20190127 ===> Skipping vulnerability checks. WARNING: No /var/db/pkg/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. => Checksum SHA1 OK for lbxproxy-1.0.3.tar.bz2 => Checksum RMD160 OK for lbxproxy-1.0.3.tar.bz2 => Checksum SHA512 OK for lbxproxy-1.0.3.tar.bz2 ===> Installing dependencies for lbxproxy-1.0.3nb2 => Tool dependency pkgconf-[0-9]*: found pkgconf-1.6.0 => Tool dependency ccache-[0-9]*: found ccache-3.6 => Build dependency xorgproto>=2016.1: found xorgproto-2018.4 => Build dependency xcb-proto>=1.4: found xcb-proto-1.13 => Build dependency xtrans>=1.0.3: found xtrans-1.4.0 => Build dependency xorg-util-macros>=1.17: found xorg-util-macros-1.19.2 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency libICE>=0.99.1: found libICE-1.0.9nb1 => Full dependency libX11>=1.1: found libX11-1.6.7 => Full dependency liblbxutil>=1.1.0nb1: found liblbxutil-1.1.0nb2 => Full dependency libXext>=0.99.0: found libXext-1.3.4 ===> Overriding tools for lbxproxy-1.0.3nb2 ===> Extracting for lbxproxy-1.0.3nb2 ===> Patching for lbxproxy-1.0.3nb2 ===> Creating toolchain wrappers for lbxproxy-1.0.3nb2 ===> Configuring for lbxproxy-1.0.3nb2 => Modifying GNU configure scripts to avoid --recheck => Replacing config-guess with pkgsrc versions => Replacing config-sub with pkgsrc versions => Replacing install-sh with pkgsrc version checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... /usr/bin/awk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for x86_64--netbsd-gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for gcc option to accept ISO C99... none needed checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... (cached) /usr/bin/egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking whether __clang__ is declared... no checking whether __INTEL_COMPILER is declared... no checking whether __SUNPRO_C is declared... no checking pkg-config is at least version 0.9.0... yes checking for a sed that does not truncate output... /usr/bin/sed checking if gcc supports -Werror=unknown-warning-option... no checking if gcc supports -Werror=unused-command-line-argument... no checking if gcc supports -Wall... yes checking if gcc supports -Wpointer-arith... yes checking if gcc supports -Wmissing-declarations... yes checking if gcc supports -Wformat=2... yes checking if gcc supports -Wstrict-prototypes... yes checking if gcc supports -Wmissing-prototypes... yes checking if gcc supports -Wnested-externs... yes checking if gcc supports -Wbad-function-cast... yes checking if gcc supports -Wold-style-definition... yes checking if gcc supports -Wdeclaration-after-statement... yes checking if gcc supports -Wunused... yes checking if gcc supports -Wuninitialized... yes checking if gcc supports -Wshadow... yes checking if gcc supports -Wcast-qual... yes checking if gcc supports -Wmissing-noreturn... yes checking if gcc supports -Wmissing-format-attribute... yes checking if gcc supports -Wredundant-decls... yes
Re: osabi in -current in some difficulty?
On Mon, Mar 18, 2019 at 03:59:07AM -0400, Bob Bernstein wrote: > However, a fly did find the ointment when it was lbxproxy's turn: I think this was broken with one of the recent xorg package updates. It also fails for me in the same way. Thomas
Re: osabi in -current in some difficulty?
Bob Bernstein writes: > However, a fly did find the ointment when it was lbxproxy's turn: > > "cc1: some warnings being treated as errors" > > I used to know what CFLAG will turn that off, but it's been a long > time. Thanks if you can help get me over this hump. Looking at your output, that smells like some prereq not right, as opposed to a warning that should be ignored.
Re: osabi in -current in some difficulty?
Strange. Up untill connection.c I have more or less the same notes and warnings, but then I get: CC connection.o os/connection.c: In function 'ErrorConnMax': os/connection.c:646:18: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] iov[1].iov_base = NOROOM; ^ CC io.o CC osinit.o CC WaitFor.o CC lbxproxytrans.o CCLD lbxproxy GENlbxproxy.1 and the build completes without an error. I can't see anything relevant in /etc/mk.conf except I have CCACHE_DIR?=/usr/pkg/.ccache PKGSRC_COMPILER=ccache gcc but I doubt any link. Otherwise I have: # uname -a NetBSD nbuild.lorien.lan 8.99.35 NetBSD 8.99.35 (XEN3_DOMU) #13: Sun Mar 17 02:07:55 GMT 2019 sysbu...@nbuild.lorien.lan:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/XEN3_DOMU amd64 # gcc --version gcc (nb1 20190119) 7.4.0 On Mon, 18 Mar 2019 at 07:59, Bob Bernstein wrote: > > On Sun, Mar 17, 2019 at 06:39:11PM +, Chavdar Ivanov wrote: > > > BTW I finally finished a full modular-xorg build. Starting some > > tests now. > > Perhaps I can follow in your footsteps. > > I started all over again Sunday morning: new install of -current, > new cvs of pkgsrc, etc. I did quite well: > > $ pkg_info |grep ^modular > modular-xorg-server-1.20.4 Modular X11 server from modular X.org > modular-xorg-drivers-1.19.0nb4 Modular Xorg driver meta-package > modular-xorg-libs-1.5nb1 Modular Xorg library meta-package > modular-xorg-xephyr-1.20.4 Xephyr server based on kdrive from modular X.org > > However, a fly did find the ointment when it was lbxproxy's turn: > > "cc1: some warnings being treated as errors" > > I used to know what CFLAG will turn that off, but it's been a long > time. Thanks if you can help get me over this hump. > > I'll stick the output in here: > > -- > These are not the droids you are looking for. --
Re: osabi in -current in some difficulty?
On Sun, Mar 17, 2019 at 06:39:11PM +, Chavdar Ivanov wrote: > BTW I finally finished a full modular-xorg build. Starting some > tests now. Perhaps I can follow in your footsteps. I started all over again Sunday morning: new install of -current, new cvs of pkgsrc, etc. I did quite well: $ pkg_info |grep ^modular modular-xorg-server-1.20.4 Modular X11 server from modular X.org modular-xorg-drivers-1.19.0nb4 Modular Xorg driver meta-package modular-xorg-libs-1.5nb1 Modular Xorg library meta-package modular-xorg-xephyr-1.20.4 Xephyr server based on kdrive from modular X.org However, a fly did find the ointment when it was lbxproxy's turn: "cc1: some warnings being treated as errors" I used to know what CFLAG will turn that off, but it's been a long time. Thanks if you can help get me over this hump. I'll stick the output in here: -- These are not the droids you are looking for. Script started on Mon Mar 18 03:47:57 2019 ===> Skipping vulnerability checks. WARNING: No /var/db/pkg/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. ===> Installing dependencies for modular-xorg-1.12.4nb1 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency modular-xorg-server>=1.12.4: found modular-xorg-server-1.20.4 => Full dependency modular-xorg-drivers>=1.12: found modular-xorg-drivers-1.19.0nb4 => Full dependency modular-xorg-libs>=1.0: found modular-xorg-libs-1.5nb1 => Full dependency modular-xorg-apps>=1.5: NOT found => Verifying reinstall for ../../meta-pkgs/modular-xorg-apps ===> Skipping vulnerability checks. WARNING: No /var/db/pkg/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. ===> Installing dependencies for modular-xorg-apps-1.14.1.8 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency xbiff-[0-9]*: found xbiff-1.0.3 => Full dependency twm-[0-9]*: found twm-1.0.10 => Full dependency appres-[0-9]*: found appres-1.0.5 => Full dependency bdftopcf-[0-9]*: found bdftopcf-1.1nb1 => Full dependency beforelight-[0-9]*: found beforelight-1.0.5 => Full dependency bitmap-[0-9]*: found bitmap-1.0.9 => Full dependency editres-[0-9]*: found editres-1.0.7 => Full dependency font-util-[0-9]*: found font-util-1.3.1 => Full dependency iceauth-[0-9]*: found iceauth-1.0.8nb1 => Full dependency ico-[0-9]*: found ico-1.0.5 => Full dependency listres-[0-9]*: found listres-1.0.4 => Full dependency luit-[0-9]*: found luit-2.0.20190106 => Full dependency mkcomposecache-[0-9]*: found mkcomposecache-1.2.1 => Full dependency modular-xorg-xephyr-[0-9]*: found modular-xorg-xephyr-1.20.4 => Full dependency oclock-[0-9]*: found oclock-1.0.4 => Full dependency lbxproxy-[0-9]*: NOT found => Verifying reinstall for ../../x11/lbxproxy => Bootstrap dependency digest>=20010302: found digest-20190127 ===> Skipping vulnerability checks. WARNING: No /var/db/pkg/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. => Checksum SHA1 OK for lbxproxy-1.0.3.tar.bz2 => Checksum RMD160 OK for lbxproxy-1.0.3.tar.bz2 => Checksum SHA512 OK for lbxproxy-1.0.3.tar.bz2 ===> Installing dependencies for lbxproxy-1.0.3nb2 => Tool dependency pkgconf-[0-9]*: found pkgconf-1.6.0 => Build dependency xorgproto>=2016.1: found xorgproto-2018.4 => Build dependency xcb-proto>=1.4: found xcb-proto-1.13 => Build dependency xtrans>=1.0.3: found xtrans-1.4.0 => Build dependency xorg-util-macros>=1.17: found xorg-util-macros-1.19.2 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency libICE>=0.99.1: found libICE-1.0.9nb1 => Full dependency libX11>=1.1: found libX11-1.6.7 => Full dependency liblbxutil>=1.1.0nb1: found liblbxutil-1.1.0nb2 => Full dependency libXext>=0.99.0: found libXext-1.3.4 ===> Overriding tools for lbxproxy-1.0.3nb2 ===> Extracting for lbxproxy-1.0.3nb2 ===> Patching for lbxproxy-1.0.3nb2 ===> Creating toolchain wrappers for lbxproxy-1.0.3nb2 ===> Configuring for lbxproxy-1.0.3nb2 => Modifying GNU configure scripts to avoid --recheck => Replacing config-guess with pkgsrc versions => Replacing config-sub with pkgsrc versions => Replacing install-sh with pkgsrc version checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... /usr/bin/awk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for x86_64--netbsd-gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no
Re: osabi in -current in some difficulty?
BTW I finally finished a full modular-xorg build. Starting some tests now. .. pkpkg_info modular-xorg-1.12.4nb1 Information for modular-xorg-1.12.4nb1: Comment: Modular Xorg meta-package Requires: modular-xorg-server>=1.12.4 modular-xorg-drivers>=1.12 modular-xorg-libs>=1.0 modular-xorg-apps>=1.5 modular-xorg-fonts>=1.1 modular-xorg-utils>=1.0 xorg-docs-[0-9]* Description: This is the modular Xorg meta-package for installing the various libs, drivers, fonts, and apps from the modular Xorg project. Homepage: http://xorg.freedesktop.org/ ... On Fri, 15 Mar 2019 at 19:51, Bob Bernstein wrote: > > On Fri, 15 Mar 2019, Chavdar Ivanov wrote: > > > BTW what is the NVidia hardware on this machine? > > From Windows while it was still running on the box: > > nVidia: > GeForce 6150SE nForce 430 > > Thanks for giving modular-xorg a build try. I look forward to > your results. > > -- > Bob Bernstein --
Re: osabi in -current in some difficulty?
On Fri, 15 Mar 2019, Chavdar Ivanov wrote: BTW what is the NVidia hardware on this machine? From Windows while it was still running on the box: nVidia: GeForce 6150SE nForce 430 Thanks for giving modular-xorg a build try. I look forward to your results. -- Bob Bernstein
Re: osabi in -current in some difficulty?
I also tried to build modular-xorg, so far it has been a bit of a disaster with many .pc packages showing as missing, some of them actually avalable in the built-in X, but not all. Just in case, I cvs updated my pkgsrc tree and am running pkg_rolling-replace at the moment in order to reattempt building modular-xorg later. I had it built perhaps 6 months ago for some other machine, not recently. On Fri, 15 Mar 2019 at 14:41, Chavdar Ivanov wrote: > > x11/pixman installs pkgconf package (confusion between 'pkgsrc' > package and package in the 'pkgconf' context). X11/pixman does not > depend on modular Xorg. I would try to rerun the modular-xorg > installation after cleaning the work folders as some configure scripts > might have failed detecting it. > > pkgconf --path pixman-1 > /usr/pkg/lib/pkgconfig/pixman-1.pc > > > pkg_info -L pixman > Information for pixman-0.38.0: > > Files: > /usr/pkg/include/pixman-1/pixman-version.h > /usr/pkg/include/pixman-1/pixman.h > /usr/pkg/lib/libpixman-1.la > /usr/pkg/lib/libpixman-1.a > /usr/pkg/lib/libpixman-1.so > /usr/pkg/lib/libpixman-1.so.0 > /usr/pkg/lib/libpixman-1.so.0.38.0 > /usr/pkg/lib/pkgconfig/pixman-1.pc > > BTW what is the NVidia hardware on this machine? > > On Fri, 15 Mar 2019 at 14:18, Bob Bernstein wrote: > > > > On Thu, 14 Mar 2019, Chavdar Ivanov wrote: > > > > > When I do rolling replace I usually manually install osabi and > > > dependents in advance. > > > > Any thoughts on this odd "pixman-1" pkg which showed up in a > > subsequent make attempt in /modular-xorg? > > > > -- > > ,[ IMPORTANT ]--- > > | This email is intended for the use of the individual > > | addressee(s) named above and may contain information that > > | is confidential, privileged or unsuitable for overly > > | sensitive persons with low self-esteem, no sense of humour > > | or irrational metaphysical beliefs. > > ` > > > > > -- > --
Re: osabi in -current in some difficulty?
x11/pixman installs pkgconf package (confusion between 'pkgsrc' package and package in the 'pkgconf' context). X11/pixman does not depend on modular Xorg. I would try to rerun the modular-xorg installation after cleaning the work folders as some configure scripts might have failed detecting it. pkgconf --path pixman-1 /usr/pkg/lib/pkgconfig/pixman-1.pc > pkg_info -L pixman Information for pixman-0.38.0: Files: /usr/pkg/include/pixman-1/pixman-version.h /usr/pkg/include/pixman-1/pixman.h /usr/pkg/lib/libpixman-1.la /usr/pkg/lib/libpixman-1.a /usr/pkg/lib/libpixman-1.so /usr/pkg/lib/libpixman-1.so.0 /usr/pkg/lib/libpixman-1.so.0.38.0 /usr/pkg/lib/pkgconfig/pixman-1.pc BTW what is the NVidia hardware on this machine? On Fri, 15 Mar 2019 at 14:18, Bob Bernstein wrote: > > On Thu, 14 Mar 2019, Chavdar Ivanov wrote: > > > When I do rolling replace I usually manually install osabi and > > dependents in advance. > > Any thoughts on this odd "pixman-1" pkg which showed up in a > subsequent make attempt in /modular-xorg? > > -- > ,[ IMPORTANT ]--- > | This email is intended for the use of the individual > | addressee(s) named above and may contain information that > | is confidential, privileged or unsuitable for overly > | sensitive persons with low self-esteem, no sense of humour > | or irrational metaphysical beliefs. > ` > --
Re: osabi in -current in some difficulty?
When I do rolling replace I usually manually install osabi and dependents in advance. On Thu, 14 Mar 2019 at 20:16, Bob Bernstein wrote: > I am aiming at a successful pkgsrc build of modular-xorg. I posted > an error log yesterday to tech-x11. Overall, I'm trying to get > nouveau and X to function on this machine. (-current boots via > userconf disabling nouveau.) > > As a rule I eschew cross-posting, but the traffic volume is low, and > the error seems like it will be deemed to merit attention. > > I upgraded to -current 8.99.35, and cvs -A up'd my pkgsrc tree. > Then I ran pkg_rolling-repace -rsuv. As noted, it ran aground in > osabi. Here is the output: > > Script started on Thu Mar 14 15:55:05 2019 > RR> Checking for mismatched installed packages using pkg_chk > rr> devel/pkgconf - pkgconf-1.4.1nb1 < pkgconf-1.6.0 > rr> mail/mutt - mutt-1.11.3 < mutt-1.11.4 > rr> pkgtools/osabi - osabi-NetBSD-8.0 < osabi-NetBSD-8.99.35 (has binary > package) > ** Unable to read PKGCHK_CONF > '/usr/pkgsrc/pkgchk_update-nebby.localdomain.conf' > RR> Excluding the following mismatched packages: > rr> EXCLUDE=[] > RR> Checking for rebuild-requested installed packages (rebuild=YES) > RR> Checking for unsafe installed packages (unsafe_depends_strict=YES) > RR> Packages to rebuild: > rr> MISMATCH_TODO=[pkgconf mutt osabi-NetBSD] > rr> REBUILD_TODO=[] > rr> UNSAFE_TODO=[] > RR> Building dependency graph for installed packages > RR> Tsorting dependency graph > RR> Selecting osabi-NetBSD (pkgtools/osabi) as next package to replace > RR> Checking if osabi-NetBSD has new depends... > RR> Replacing osabi-NetBSD-8.0 > ===> Cleaning for osabi-NetBSD-8.99.35 > ===> Skipping vulnerability checks. > WARNING: No /var/db/pkg/pkg-vulnerabilities file found. > WARNING: To fix run: `/usr/pkg/sbin/pkg_admin -K /var/db/pkg > fetch-pkg-vulnerabilities'. > ===> Installing dependencies for osabi-NetBSD-8.99.35 > => Build dependency cwrappers>=20150314: found cwrappers-20180325 > ===> Overriding tools for osabi-NetBSD-8.99.35 > ===> Extracting for osabi-NetBSD-8.99.35 > ===> Patching for osabi-NetBSD-8.99.35 > ===> Creating toolchain wrappers for osabi-NetBSD-8.99.35 > ===> Installing for osabi-NetBSD-8.99.35 > => Generating pre-install file lists > => Automatic manual page handling > => Generating post-install file lists > => Checking file-check results for osabi-NetBSD-8.99.35 > => Creating binary package > /usr/pkgsrc/pkgtools/osabi/work/.packages/osabi-NetBSD-8.99.35.tgz > ===> Building binary package for osabi-NetBSD-8.99.35 > => Creating binary package > /usr/pkgsrc/packages/All/osabi-NetBSD-8.99.35.tgz > ===> Replacing for osabi-NetBSD-8.99.35 > ===> Updating using binary package of osabi-NetBSD-8.99.35 > /usr/bin/env /usr/pkg/sbin/pkg_add -K /var/db/pkg -U -D > /usr/pkgsrc/pkgtools/osabi/work/.packages/osabi-NetBSD-8.99.35.tgz > pkg_add: Can't open +CONTENTS of depending package x11-links-1.12 > pkg_add: 1 package addition failed > *** Error code 1 > > Stop. > make[2]: stopped in /usr/pkgsrc/pkgtools/osabi > *** Error code 1 > > Stop. > make[1]: stopped in /usr/pkgsrc/pkgtools/osabi > *** Error code 1 > > Stop. > make: stopped in /usr/pkgsrc/pkgtools/osabi > *** 'make replace' failed for package osabi-NetBSD. > *** Please read the errors listed above, fix the problem, > *** then re-run pkg_rolling-replace to continue. > - osabi-NetBSD > > Script done on Thu Mar 14 15:55:52 2019 > > Thank you. > > > -- > In our age there is no such thing as 'keeping out of > politics'. All issues are political issues, and > politics itself is a mass of lies, evasions, folly, > hatred, and schizophrenia. > > George Orwell "Politics and the English Language" (1946) > --
Re: osabi in -current in some difficulty?
On Thu, Mar 14, 2019 at 08:51:44PM -0400, Greg Troxel wrote: > In this case, you have a corrupt database. I have some notes > about this to dig through about why this happens. Now, running make in /usr/pkgsrc/meta-pkgs/modular-xorg hangs up on a non-existent pkg "pixman-1". Just on general principles I built and installed "pixman" from pkgsrc, but it didn't alter anything overall. > Run "pkg_admin rebuild-tree" to fix the phantom dependency problem. That command completed in about one second. Didn't seem as if it was doing anything. > Then you can rm all the workdirs and try again. Okay. Thanks! -- Bob B.
Re: osabi in -current in some difficulty?
Bob Bernstein writes: > ===> Updating using binary package of osabi-NetBSD-8.99.35 > /usr/bin/env /usr/pkg/sbin/pkg_add -K /var/db/pkg -U -D > /usr/pkgsrc/pkgtools/osabi/work/.packages/osabi-NetBSD-8.99.35.tgz > pkg_add: Can't open +CONTENTS of depending package x11-links-1.12 > pkg_add: 1 package addition failed > *** Error code 1 My usual plea: pkg_rr arranges to run "make replace" in the right order. If the make replace fails, that's a pkgsrc issue, not about pkg_rr. If the probllem is that the chosen order is wrong, that's a pkg_rr bug. In this case, you have a corrupt database. I have some notes about this to dig through about why this happens. Run "pkg_admin rebuild-tree" to fix the phantom dependency problem. Then you can rm all the workdirs and try again.
