Tha would be great, if it worked for me... > Am 22.07.2023 um 11:54 schrieb PHO <pho%cielonegro.org@localhost>: > > Hi all, > > I just created a new package wip/pkgchkxx. This is a complete reimplementation of pkgtools/pkg_chk and pkgtools/pkg_rolling_replace in C++17. > Is this the intended behaviour? ---- # pkg_admin set rebuild=YES xxhash # pkgrrxx -v RR> Checking for mismatched installed packages (mismatch=YES) RR> Checking for rebuild-requested installed packages (rebuild=YES) RR> Checking for unsafe installed packages (unsafe_depends=YES) RR> Building dependency graph for installed packages RR> Packages to rebuild: rr> MISMATCH_TODO=[pkgrrxx: — that should have rebuilt xxhash, shouldn’t it? — # pkgrrxx -vu RR> Checking for mismatched installed packages using pkg_chk ^C —— I thought it would use pkgchkxx for searching mismatched packages. But that is quite ok, because it would probably have upgraded my mailman to mailman3: # pkgchkxx -N ImageMagick: ImageMagick-7.1.1.14 MesaLib: MesaLib-23.1.4 aspell-nb: aspell-nb-2.0.10 dbus: dbus-1.14.8 glu: glu-9.0.3 gtar-base: gtar-base-1.35 libgit2: libgit2-1.7.0 llvm: llvm-16.0.6 [wip] mailman: mailman-3.3.5 ocaml: ocaml-5.0.0 openssl: openssl-3.0.7 py-cython: py-cython-3.0 py-pspdfutils: py-pspdfutils-3.0.8 re2c: re2c-3.1 sudo: sudo-1.9.14p2 But it is blazingly fast… Note: I do have an outdated pkg_summary.gz. When removing this, nothing changes ;-) Cheers Oskar
Attachment:
smime.p7s
Description: S/MIME cryptographic signature