Re: Unable to build python3.11
Le 08/06/2024 19:33, TIM KELLERS a écrit : On 6/8/24 12:38 PM, Xavier Humbert wrote: Hi, Tried to compile python 3.11 but if fails at QA and install stage with : [root@numenor python311]# make clean all [...] > Compressing man pages (compress-man) > Running Q/A tests (stage-qa) egrep: warning: egrep is obsolescent; using /usr/local/bin/ggrep -E Warning: you might not need LIB_DEPENDS on libreadline.so.8 readelf: Error: Not an ELF file - it has the wrong magic bytes at the start Warning: /usr/ports/lang/python311/work/stage/usr/local/lib/libpython3.11d.so.1.0-gdb.py doesn't have a SONAME. Warning: pkg(8) will not register it as being provided by the port. Warning: If another port depend on it, pkg will not be able to know where it comes from. Warning: It is directly in /usr/local/lib, it is probably used by other ports. [root@numenor python311]# make install ===> Installing for python311-3.11.9 ===> Checking if python311 is already installed ===> Registering installation for python311-3.11.9 pkg-static: Unable to access file /usr/ports/lang/python311/work/stage/usr/local/lib/python3.11/lib-dynload/_testclinic.cpython-311.so:No such file or directory *** Error code 1 Stop. make[1]: stopped in /usr/ports/lang/python311 *** Error code 1 Stop. make: stopped in /usr/ports/lang/python311 [root@numenor python311]# make showconfig ===> The following configuration options are available for python311-3.11.9: DEBUG=on: Build with debugging support IPV6=on: IPv6 protocol support LIBMPDEC=on: Use libmpdec from ports instead of bundled version LTO=on: Use Link-Time Optimization NLS=on: Enable gettext support for the locale module PYMALLOC=on: Enable specialized mallocs > Hash Algorithm (PEP-456): you can only select none or one of them FNV=off: Modified Fowler-Noll-Vo Algorithm SIPHASH=on: SipHash24 Algorithm ===> Use 'make config' to modify these settings My goal was to follow 20240529 entry in UPDATING Regards, Xavier Which version and which architecture are you building on? Tim I'm building python 3.11 on 13-STABLE/amd64 Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Unable to build python3.11
Hi, Tried to compile python 3.11 but if fails at QA and install stage with : [root@numenor python311]# make clean all [...] > Compressing man pages (compress-man) > Running Q/A tests (stage-qa) egrep: warning: egrep is obsolescent; using /usr/local/bin/ggrep -E Warning: you might not need LIB_DEPENDS on libreadline.so.8 readelf: Error: Not an ELF file - it has the wrong magic bytes at the start Warning: /usr/ports/lang/python311/work/stage/usr/local/lib/libpython3.11d.so.1.0-gdb.py doesn't have a SONAME. Warning: pkg(8) will not register it as being provided by the port. Warning: If another port depend on it, pkg will not be able to know where it comes from. Warning: It is directly in /usr/local/lib, it is probably used by other ports. [root@numenor python311]# make install ===> Installing for python311-3.11.9 ===> Checking if python311 is already installed ===> Registering installation for python311-3.11.9 pkg-static: Unable to access file /usr/ports/lang/python311/work/stage/usr/local/lib/python3.11/lib-dynload/_testclinic.cpython-311.so:No such file or directory *** Error code 1 Stop. make[1]: stopped in /usr/ports/lang/python311 *** Error code 1 Stop. make: stopped in /usr/ports/lang/python311 [root@numenor python311]# make showconfig ===> The following configuration options are available for python311-3.11.9: DEBUG=on: Build with debugging support IPV6=on: IPv6 protocol support LIBMPDEC=on: Use libmpdec from ports instead of bundled version LTO=on: Use Link-Time Optimization NLS=on: Enable gettext support for the locale module PYMALLOC=on: Enable specialized mallocs > Hash Algorithm (PEP-456): you can only select none or one of them FNV=off: Modified Fowler-Noll-Vo Algorithm SIPHASH=on: SipHash24 Algorithm ===> Use 'make config' to modify these settings My goal was to follow 20240529 entry in UPDATING Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Error in staging for print/luatex
Le 02/06/2024 18:21, Moin Rahman a écrit : On Jun 2, 2024, at 5:39 PM, Xavier Humbert wrote: Hi, I cannot upgrade print/luatex, it fails at staging : ===> Staging for tex-luatex-20240312 ===> tex-luatex-20240312 depends on file: /usr/local/share/texmf-var/web2c/tex/tex.fmt - found ===> tex-luatex-20240312 depends on executable: weave - found ===> tex-luatex-20240312 depends on file: /usr/local/libdata/pkgconfig/pixman-1.pc - found [...] PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3.1) I googled for that error, suggestions were to rebuild texlive-base, with no success. Any hint ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr If you are using ports delete all tex related ports and reinstall. Kind regards, Moin Thanks, pkg delete -f tex\*, then portinstall the same fixed the problem ! Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Error in staging for print/luatex
Hi, I cannot upgrade print/luatex, it fails at staging : ===> Staging for tex-luatex-20240312 ===> tex-luatex-20240312 depends on file: /usr/local/share/texmf-var/web2c/tex/tex.fmt - found ===> tex-luatex-20240312 depends on executable: weave - found ===> tex-luatex-20240312 depends on file: /usr/local/libdata/pkgconfig/pixman-1.pc - found [...] PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3.1) I googled for that error, suggestions were to rebuild texlive-base, with no success. Any hint ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
DBD::MySQL upstream change
Hi, I'm using MariaDB as my database server on FreeBSD 13.3 DBD::MySQL changed upstream to support only MySQL8 I know there is a new module DBD::MariaDB Is is safe to replace DBD::MySQL with DBD::MariaDB ? Thanks, Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Cannot upgrade p5-DBD-mysql with Mariadb
Hi, Seems that an upstream change broke compatibility between databases/p5-DBD-mysql and MariaDB : DBD::mysql requires MySQL 8.x for building. Version reported by mysql_config --version: 10.5.23 at ./Makefile.PL line 451, line 3. Since I use MariaDB, I don't want to install mysql80-client Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
I can confirm that putting aside vscode.list allowed me to do the upgrade Thanks Xavier -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python-apt source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Invalid Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
I can confirm that putting aside vscode.list allowed me to do the upgrade Thanks Xavier -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Files attached ** Attachment added: "aptsources.tar.bz2" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2047447/+attachment/5755869/+files/aptsources.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Files attached ** Attachment added: "aptsources.tar.bz2" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2047447/+attachment/5755869/+files/aptsources.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Yes I have some more : [xavier@imladris ~]$ ll /etc/apt/sources.list.d/*sources -rw-r--r-- 1 root root 122 Sep 1 2023 /etc/apt/sources.list.d/alessandro-strada-ubuntu-ppa-groovy.sources -rw-r--r-- 1 root root 1805 Sep 12 2023 /etc/apt/sources.list.d/ancestris-ubuntu-ancestris-stable-lunar.sources -rw-r--r-- 1 root root 92 Sep 1 2023 /etc/apt/sources.list.d/archive_uri-https_download_docker_com_linux_ubuntu-hirsute.sources -rw-r--r-- 1 root root 111 Sep 1 2023 /etc/apt/sources.list.d/fortine.sources -rw-r--r-- 1 root root 99 Sep 1 2023 /etc/apt/sources.list.d/google-earth-pro.sources -rw-r--r-- 1 root root 114 Sep 1 2023 /etc/apt/sources.list.d/inkscape_dev-ubuntu-stable-hirsute.sources -rw-r--r-- 1 root root 97 Sep 1 2023 /etc/apt/sources.list.d/jtaylor-ubuntu-keepass-impish.sources -rw-r--r-- 1 root root 112 Sep 1 2023 /etc/apt/sources.list.d/mscore-ubuntu-ubuntu-mscore3-stable-hirsute.sources -rw-r--r-- 1 root root 133 Sep 1 2023 /etc/apt/sources.list.d/musicbrainz-developers-ubuntu-stable-kinetic.sources -rw-r--r-- 1 root root 1541 Sep 1 2023 /etc/apt/sources.list.d/noobslab-ubuntu-macbuntu-cosmic.sources -rw-r--r-- 1 root root 122 Sep 1 2023 /etc/apt/sources.list.d/pgadmin4.sources -rw-r--r-- 1 root root 107 Sep 1 2023 /etc/apt/sources.list.d/pgdg.sources -rw-r--r-- 1 root root 113 Sep 1 2023 /etc/apt/sources.list.d/python2-stuff.sources -rw-r--r-- 1 root root 86 Sep 1 2023 /etc/apt/sources.list.d/rudder.sources -rw-r--r-- 1 root root 118 Mar 4 13:50 /etc/apt/sources.list.d/runner_gitlab-runner.sources -rw-r--r-- 1 root root 107 Sep 1 2023 /etc/apt/sources.list.d/teams.sources -rw-r--r-- 1 root root 114 Sep 1 2023 /etc/apt/sources.list.d/teamviewer.sources -rw-r--r-- 1 root root 146 Sep 1 2023 /etc/apt/sources.list.d/third-party.sources -rw-r--r-- 1 root root 128 Sep 1 2023 /etc/apt/sources.list.d/ubuntu-esm-apps.sources -rw-r--r-- 1 root root 131 Sep 1 2023 /etc/apt/sources.list.d/ubuntu-esm-infra.sources -rw-r--r-- 1 root root 585 Sep 1 2023 /etc/apt/sources.list.d/ubuntu.sources -rw-r--r-- 1 root root 759 Sep 1 2023 /etc/apt/sources.list.d/yannubuntu-ubuntu-boot-repair-jammy.sources -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository
[Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Yes I have some more : [xavier@imladris ~]$ ll /etc/apt/sources.list.d/*sources -rw-r--r-- 1 root root 122 Sep 1 2023 /etc/apt/sources.list.d/alessandro-strada-ubuntu-ppa-groovy.sources -rw-r--r-- 1 root root 1805 Sep 12 2023 /etc/apt/sources.list.d/ancestris-ubuntu-ancestris-stable-lunar.sources -rw-r--r-- 1 root root 92 Sep 1 2023 /etc/apt/sources.list.d/archive_uri-https_download_docker_com_linux_ubuntu-hirsute.sources -rw-r--r-- 1 root root 111 Sep 1 2023 /etc/apt/sources.list.d/fortine.sources -rw-r--r-- 1 root root 99 Sep 1 2023 /etc/apt/sources.list.d/google-earth-pro.sources -rw-r--r-- 1 root root 114 Sep 1 2023 /etc/apt/sources.list.d/inkscape_dev-ubuntu-stable-hirsute.sources -rw-r--r-- 1 root root 97 Sep 1 2023 /etc/apt/sources.list.d/jtaylor-ubuntu-keepass-impish.sources -rw-r--r-- 1 root root 112 Sep 1 2023 /etc/apt/sources.list.d/mscore-ubuntu-ubuntu-mscore3-stable-hirsute.sources -rw-r--r-- 1 root root 133 Sep 1 2023 /etc/apt/sources.list.d/musicbrainz-developers-ubuntu-stable-kinetic.sources -rw-r--r-- 1 root root 1541 Sep 1 2023 /etc/apt/sources.list.d/noobslab-ubuntu-macbuntu-cosmic.sources -rw-r--r-- 1 root root 122 Sep 1 2023 /etc/apt/sources.list.d/pgadmin4.sources -rw-r--r-- 1 root root 107 Sep 1 2023 /etc/apt/sources.list.d/pgdg.sources -rw-r--r-- 1 root root 113 Sep 1 2023 /etc/apt/sources.list.d/python2-stuff.sources -rw-r--r-- 1 root root 86 Sep 1 2023 /etc/apt/sources.list.d/rudder.sources -rw-r--r-- 1 root root 118 Mar 4 13:50 /etc/apt/sources.list.d/runner_gitlab-runner.sources -rw-r--r-- 1 root root 107 Sep 1 2023 /etc/apt/sources.list.d/teams.sources -rw-r--r-- 1 root root 114 Sep 1 2023 /etc/apt/sources.list.d/teamviewer.sources -rw-r--r-- 1 root root 146 Sep 1 2023 /etc/apt/sources.list.d/third-party.sources -rw-r--r-- 1 root root 128 Sep 1 2023 /etc/apt/sources.list.d/ubuntu-esm-apps.sources -rw-r--r-- 1 root root 131 Sep 1 2023 /etc/apt/sources.list.d/ubuntu-esm-infra.sources -rw-r--r-- 1 root root 585 Sep 1 2023 /etc/apt/sources.list.d/ubuntu.sources -rw-r--r-- 1 root root 759 Sep 1 2023 /etc/apt/sources.list.d/yannubuntu-ubuntu-boot-repair-jammy.sources -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Hi Nick This file : Types: deb URIs: http://fr.archive.ubuntu.com/ubuntu/ Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Enabled: no Types: deb URIs: http://fr.archive.ubuntu.com/ubuntu/ Suites: lunar-proposed Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Regards -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Hi Nick This file : Types: deb URIs: http://fr.archive.ubuntu.com/ubuntu/ Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Enabled: no Types: deb URIs: http://fr.archive.ubuntu.com/ubuntu/ Suites: lunar-proposed Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Workaround : As mentioned by A (zorn-v), the culprit is the (deprecated) file /etc/apt/sources.list Populating with a minimal content : deb http://fr.archive.ubuntu.com/ubuntu mantic main deb http://fr.archive.ubuntu.com/ubuntu mantic universe allows the installation to continue, with a ton of warnings about duplicate origins, that you should ignore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2047447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: py-setuptools-scm error
Le 02/03/2024 09:44, Xavier Humbert a écrit : Le 02/03/2024 08:45, Tatsuki Makino a écrit : Hello. It seems that py39-setuptools_scm-6.4.2 must not be installed to install py39-setuptools-scm-8.x. So we cannot use -o of portmaster or portupgrade. The only way seems to be to delete it beforehand with pkg delete -f. That's what I did, with no success. Then reinstall the ports that have lost their dependencies, and they will be installed with the auto-install flag also set correctly. Regards. Sorry, I didn't double check, it worked. Thanks Regards Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: py-setuptools-scm error
Le 02/03/2024 08:45, Tatsuki Makino a écrit : Hello. It seems that py39-setuptools_scm-6.4.2 must not be installed to install py39-setuptools-scm-8.x. So we cannot use -o of portmaster or portupgrade. The only way seems to be to delete it beforehand with pkg delete -f. That's what I did, with no success. Then reinstall the ports that have lost their dependencies, and they will be installed with the auto-install flag also set correctly. Regards. Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
py-setuptools-scm error
Hi, Now thet py-setuptools-scm 8 is out, tried to upgrade : [root@numenor ports]# portupgrade -vf -o devel/py-setuptools-scm py39-setuptools_scm-6.4.2 ---> Session started at: Sat, 02 Mar 2024 08:31:04 +0100 [Reading data from pkg(8) ... - 1757 packages found - done] ** Detected a package name change: py39-setuptools_scm (devel/py-setuptools_scm) -> 'py39-setuptools-scm' (devel/py-setuptools-scm) ---> Upgrade of devel/py-setuptools-scm started at: Sat, 02 Mar 2024 08:31:06 +0100 ---> Upgrading 'py39-setuptools_scm-6.4.2' to 'py39-setuptools-scm-8.0.4' (devel/py-setuptools-scm) ---> Build of devel/py-setuptools-scm started at: Sat, 02 Mar 2024 08:31:06 +0100 ---> Building '/usr/ports/devel/py-setuptools-scm' with make flags: -DDISABLE_CONFLICTS ===> Cleaning for py39-setuptools-scm-8.0.4 ===> License MIT accepted by the user ===> py39-setuptools-scm-8.0.4 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by py39-setuptools-scm-8.0.4 for building ===> Extracting for py39-setuptools-scm-8.0.4 => SHA256 Checksum OK for setuptools-scm-8.0.4.tar.gz. ===> Patching for py39-setuptools-scm-8.0.4 ===> py39-setuptools-scm-8.0.4 depends on package: py39-setuptools>0 - found ===> py39-setuptools-scm-8.0.4 depends on package: py39-wheel>0 - found ===> py39-setuptools-scm-8.0.4 depends on file: /usr/local/bin/python3.9 - found ===> py39-setuptools-scm-8.0.4 depends on package: py39-tomli>0 - found ===> py39-setuptools-scm-8.0.4 depends on package: py39-build>=0 - found ===> py39-setuptools-scm-8.0.4 depends on package: py39-installer>=0 - found ===> Configuring for py39-setuptools-scm-8.0.4 ===> Building for py39-setuptools-scm-8.0.4 * Getting build dependencies for wheel... Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/pyproject_hooks/_in_process/_in_process.py", line 353, in main() File "/usr/local/lib/python3.9/site-packages/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) File "/usr/local/lib/python3.9/site-packages/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel return hook(config_settings) File "/usr/local/lib/python3.9/site-packages/setuptools/build_meta.py", line 177, in get_requires_for_build_wheel return self._get_build_requires( File "/usr/local/lib/python3.9/site-packages/setuptools/build_meta.py", line 159, in _get_build_requires self.run_setup() File "/usr/local/lib/python3.9/site-packages/setuptools/build_meta.py", line 174, in run_setup exec(compile(code, __file__, 'exec'), locals()) File "setup.py", line 1, in File "/usr/local/lib/python3.9/site-packages/setuptools/__init__.py", line 87, in setup return distutils.core.setup(**attrs) File "/usr/local/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 139, in setup _setup_distribution = dist = klass(attrs) File "/usr/local/lib/python3.9/site-packages/setuptools/dist.py", line 476, in __init__ _Distribution.__init__( File "/usr/local/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 275, in __init__ self.finalize_options() File "/usr/local/lib/python3.9/site-packages/setuptools/dist.py", line 899, in finalize_options for ep in sorted(loaded, key=by_order): File "/usr/local/lib/python3.9/site-packages/setuptools/dist.py", line 898, in loaded = map(lambda e: e.load(), filtered) File "/usr/local/lib/python3.9/site-packages/setuptools/_vendor/importlib_metadata/__init__.py", line 196, in load return functools.reduce(getattr, attrs, module) AttributeError: module 'setuptools_scm.integration' has no attribute 'infer_version' ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel *** Error code 1 Any idea to fix it ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: PHP upgrade 8.1 -> 8.2 does not update php.ini
Le 11/02/2024 18:14, Patrick M. Hausen a écrit : Hi all, hi Xavier, Am 11.02.2024 um 18:06 schrieb Xavier Humbert : Today, I upgraded php (and its extensions) from 8.1 to 8.2, via portupgrade. Quite painful, btw, unless you script it Unfortunately, php.ini was not updated, the line extension_dir = "/usr/local/lib/php/20220829-zts" had to be manually fixed Is this the expected behaviour ? UPDATING does not mention it. None of the PHP ports installs php.ini - they only provide sample files for various usage scenarios (development, production). So you copied one of them one time in the past and the burden of keeping it updated is on the administrator. Not claiming this is the best imaginable behaviour, but I'm pretty sure this is the current state of affairs. Kind regards, Patrick Oh ! It was such a long time ago, I forgot it :-) Thanks Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
PHP upgrade 8.1 -> 8.2 does not update php.ini
Hi, Today, I upgraded php (and its extensions) from 8.1 to 8.2, via portupgrade. Quite painful, btw, unless you script it Unfortunately, php.ini was not updated, the line extension_dir = "/usr/local/lib/php/20220829-zts" had to be manually fixed Is this the expected behaviour ? UPDATING does not mention it. Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Compiler error
Le 06/12/2023 10:57, Goetz Schultz a écrit : Hi Xavier, tarball, direct downloaded from the dovecot site, Was not a problem prior to FBSD14 - so I wonder if there is a compiler switch to be set. Thanks and regards Goetz R Schultz >8 Quis custodiet ipsos custodes? /"\ \ / ASCII Ribbon Campaign X against HTML e-mail / \ 8< In ports, Dovecot is up-to-date, and compiles fine : [root@numenor ~]# pkg info dovecot dovecot-2.3.21_1 Name : dovecot Version : 2.3.21_1 On 06/12/2023 09:48, Xavier Humbert wrote: Le 06/12/2023 10:44, Goetz Schultz a écrit : Hi, I have upgraded my system to FreeBSD14 and tried to recompile dovecot. The following error is thrown now (It did compile on FBSD13): test-mail-index-transaction-update.c:650:36: error: incompatible pointer to integer conversion passing 'char *(*)(int, int)' to parameter of type 'time_t' (aka 'long') [-Wint-conversion] mail_index_update_day_headers(t, tests[i].now + timezone); ^~~ (t, tests[i].now + timezone); ^~~ Is there a patch or something like that to compensate? Hi Goetz, Are you installing manually from tarball or from ports (cd /usr/ports/mail/dovecot && make install) ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Compiler error
Le 06/12/2023 10:44, Goetz Schultz a écrit : Hi, I have upgraded my system to FreeBSD14 and tried to recompile dovecot. The following error is thrown now (It did compile on FBSD13): test-mail-index-transaction-update.c:650:36: error: incompatible pointer to integer conversion passing 'char *(*)(int, int)' to parameter of type 'time_t' (aka 'long') [-Wint-conversion] mail_index_update_day_headers(t, tests[i].now + timezone); ^~~ (t, tests[i].now + timezone); ^~~ Is there a patch or something like that to compensate? Hi Goetz, Are you installing manually from tarball or from ports (cd /usr/ports/mail/dovecot && make install) ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Some py ports depends on py39-setuptools_scm>=6.4 do not detect py39-setuptools_scm 7
Hi, py39-setuptools_scm has been upgrade to version 7, but I got errors with some ports : ===> py39-anyio-4.1.0 depends on package: py39-setuptools_scm>=6.4 - not found While pkg info py39-setuptools_scm7 py39-setuptools_scm7-7.1.0 Name : py39-setuptools_scm7 Version : 7.1.0 I'm aware that the name has changed, but this leads to a conflict, py39-anyio-4.1.0 tries to reinstall py39-setuptools_scm6 : pkg-static: py39-setuptools_scm-6.4.2 conflicts with py39-setuptools_scm7-7.1.0 (installs files into the same place). Problematic file: /usr/local/lib/python3.9/site-packages/setuptools_scm/__init__.py Ports concerned : ! devel/py-pytest-runner (py39-pytest-runner-6.0.0_1) (unknown build error) ! math/py-kiwisolver (py39-kiwisolver-1.4.4_1,1) (unknown build error) ! devel/py-importlib-metadata (py39-importlib-metadata-6.8.0) (unknown build error) ! devel/py-anyio (py39-anyio-4.0.0) (unknown build error) Should I submit a bugreport to upgrade py39-setuptools_scm dependency in these ports ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
How to fix "pkg: Package database is busy while closing!"
Hi, I'm experiencing this problem : "pkg: Package database is busy while closing!" after interrupting portupgrade Do you know how to fix this ? FreeBSD-13.2-STABLE, pkg 1.20.9 Thanks, Regards Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Rust build huge memory consumption
Le 10/25/23 09:18, Matthew Seaman a écrit : * Stopping rust and some other large ports building on tmpfs TMPFS_BLACKLIST='rust gcc* llvm* texlive-texmf' TMPFS_BLACKLIST_TMPDIR=/usr/local/poudriere/data/cache/tmp USE_TMPFS=yes TMPFS_LIMIT=4 Tried this (in make.conf, I suppose), with no success. Crashed in ldd, had to reboot the server I have to wait for rust in pkg to rebuild dependent ports :sigh: Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Rust build huge memory consumption
Le 10/25/23 09:01, Cy Schubert a écrit : In message<5816a79c-9bd0-4c41-9520-eed853aa1...@groumpf.org>, Xavier Humbert w rites: Le 10/25/23 08:46, Cy Schubert a écrit : In message<09a4bfb8-ba61-4e05-b646-973104337...@groumpf.org>, Xavier Humbert w rites: Hi, When building rust, all memory is eaten, leading to OOM killing almost everything, eventually failing, and leading to an unstable system. Is there a way to tell the compiler to avoid this behaviour ? How much RAM does your machine have? How many CPU cores/threads does it have? I have 16 GB RAM, and 4 cores That should be plenty. I build it on a 4 core 8 GB machine. How much swap does it have? Could this machine by chance be running a browser or other large apps at the same time? It has 24GB swap, And I stop bhyve before building Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Rust build huge memory consumption
Le 10/25/23 08:46, Cy Schubert a écrit : In message <09a4bfb8-ba61-4e05-b646-973104337...@groumpf.org>, Xavier Humbert w rites: Hi, When building rust, all memory is eaten, leading to OOM killing almost everything, eventually failing, and leading to an unstable system. Is there a way to tell the compiler to avoid this behaviour ? How much RAM does your machine have? How many CPU cores/threads does it have? I have 16 GB RAM, and 4 cores Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Rust build huge memory consumption
Hi, When building rust, all memory is eaten, leading to OOM killing almost everything, eventually failing, and leading to an unstable system. Is there a way to tell the compiler to avoid this behaviour ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: HEADS-UP: security/openssl switching to 3.0 branch
Hi Bernard, To be clear, if one wants to keep old openssl11, add DEFAULT_VERSIONS+= ssl=openssl111 to make .conf Am I right ? Xavier Le 10/15/23 12:41, Bernard Spil a écrit : On 2023-10-06 11:43, Bernard Spil wrote: Hi all, In line with FreeBSD 14.0 that has OpenSSL 3.0 in base, all ports are expected to work with this version. The following changes will be made between first Release Candidate (RC) and actual RELEASE of FreeBSD 14.0: security/openssl updated from 1.1.1w to 3.0.11 security/openssl30 removed security/openssl111 created with version (1.1.1w) UPDATING an entry about updating all ports for the SHLIBVER bump will be added MOVED an entry for security/openssl30 with target security/openssl will be created The security/openssl111 port will be marked "DEPRECATED" in line with statements from the OpenSSL project about the End-of-Life for the 1.1.1 branch. No "EXPIRATION_DATE" will be set for now. With kind regards, Bernard Spil Hi all, DEFAULT_VERSIONS+= openssl is now OpenSSL 3.0.11 (openssl-3.0.11,1) Quick search in ports tree uncovers the following ports that seem to require 1.1.1. I'm chasing them down and adapting the BROKEN_SSL versions, but not making them require openssl111 at the moment. Expect a commit soon. audio/umurmur/Makefile:31:BROKEN_SSL= openssl30 openssl31 audio/murmur/Makefile:17:BROKEN_SSL= openssl30 openssl31 audio/spotify-tui/Makefile:294:BROKEN_SSL= base openssl30 openssl31 net/gq/Makefile:48:BROKEN_SSL= base openssl openssl30 openssl31 mail/enma/Makefile:19:BROKEN_SSL= openssl30 openssl31 sysutils/vector/Makefile:568:BROKEN_SSL= base openssl30 openssl31 sysutils/flowgger/Makefile:18:#BROKEN_SSL= openssl30 openssl31 www/castor/Makefile:133:BROKEN_SSL= base openssl30 openssl31 www/rearx/Makefile:177:BROKEN_SSL= base openssl30 openssl31 net-im/telegram-desktop/Makefile:16:BROKEN_SSL= openssl30 openssl31 archivers/xar/Makefile:18:BROKEN_SSL= openssl30 openssl31 devel/kore/Makefile:13:BROKEN_SSL= openssl30 openssl31 devel/gbump/Makefile:20:BROKEN_SSL= openssl30 openssl31 devel/gbump/Makefile:69:BROKEN_SSL= base openssl30 openssl31 devel/ptlib/Makefile:17:BROKEN_SSL= openssl30 openssl31 security/pkcs11-tools/Makefile:16:BROKEN_SSL= libressl openssl30 openssl31 security/pkcs11-tools/Makefile:18:BROKEN_SSL_REASON_openssl30= error: undefined symbol: EVP_PKEY_* security/p5-Filter-Crypto/Makefile:19:BROKEN_SSL= openssl30 openssl31 security/krb5-119/Makefile:28:BROKEN_SSL= openssl30 openssl31 security/proxytunnel/Makefile:18:BROKEN_SSL= openssl30 openssl31 security/py-nassl/Makefile:14:BROKEN_SSL= openssl30 openssl31 security/gost-engine/Makefile:69:BROKEN_SSL+= openssl30 # openssl31 -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Roundcube
Hi Joe, The only issue I had, is that for cryptic reasons (FreeBSD 13-STABLE) "localhost" did not resolve, I had too replace it with "127.0.0.1" But YMMV Regards, Xavier Le 9/7/23 23:00, joe a a écrit : Any known issues with installing/running roundcube and dovecot on the same server? ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Xavier HUMBERT 2 rue des Patureaux 54460 AINGERAY / FRANCE Tél +33 6 71 17 29 07 Dom +33 9 51 00 37 63 OpenPGP_signature.asc Description: OpenPGP digital signature ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Storage of options for ports
Hi, For backup purposes, I need to know where is stored port options (make config) Cheers Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: OpenSSL 3.0 in the base system update
Le 6/9/23 10:06, Xavier Humbert a écrit : Le 6/9/23 05:22, Eugene Grosbein a écrit : 09.06.2023 0:13, Ed Maste wrote: [skip] We welcome feedback from anyone willing to test the work in progress. Is it possible to grab some binary snapshot of 14-CURRENT to install into a VM and test my port that fails build? If not, how do I build 14-CURRENT with OpenSSL 3.0 myself? Eugene Hi, I couldnt find the ISO, but the tarballs are here https://download.freebsd.org/ftp/snapshots/arm64/14.0-CURRENT/ Cheers Xavier Sorry, ISO images are here https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/14.0/ Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: OpenSSL 3.0 in the base system update
Le 6/9/23 05:22, Eugene Grosbein a écrit : 09.06.2023 0:13, Ed Maste wrote: [skip] We welcome feedback from anyone willing to test the work in progress. Is it possible to grab some binary snapshot of 14-CURRENT to install into a VM and test my port that fails build? If not, how do I build 14-CURRENT with OpenSSL 3.0 myself? Eugene Hi, I couldnt find the ISO, but the tarballs are here https://download.freebsd.org/ftp/snapshots/arm64/14.0-CURRENT/ Cheers Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Error compiling textproc/py-rich
Le 6/3/23 18:17, Matthew Seaman a écrit : Are you sure that poetry-core is correctly installed? Try `pkg delete -f py39-poetry-core ; pkg install -A py39-poetry-core` Matthew, Seems indeed that poetry-core was badly i nstalled. Reinstalling it fixed the problem. Thanks ! Cheers Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Error compiling textproc/py-rich
Hi,
I'm unable to compile textproc/py-rich :
[root@numenor py-rich]# make all
===> Building for py39-rich-13.4.1
* Getting build dependencies for wheel...
Traceback (most recent call last):
File
"/usr/local/lib/python3.9/site-packages/pyproject_hooks/_impl.py",
line 321, in _call_hook
raise BackendUnavailable(data.get('traceback', ''))
pyproject_hooks._impl.BackendUnavailable: Traceback (most recent call
last):
File
"/usr/local/lib/python3.9/site-packages/pyproject_hooks/_in_process/_in_process.py",
line 77, in _build_backend
obj = import_module(mod_path)
File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 984, in
_find_and_load_unlocked
ModuleNotFoundError: No module named 'poetry.core'
_*ERROR Backend 'poetry.core.masonry.api' is not available.*_
*** Error code 1
I have these ports installed :
[root@numenor py-rich]# pkg info \*poetry\*
py39-poetry-1.3.2_2
py39-poetry-core-1.4.0_2
py39-poetry-plugin-export-1.3.1
Google doesn't help.
Thanks
Best regards
Xavier
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer
https://www.amdh.fr
hadrian-9.4.5-boot unavailable ?
Hi, A few hours ago a change was committed to lang/ghc, bu t I cannot fetch hadrian-9.4.5-boot : [root@numenor ghc]# make fetch ===> License BSD3CLAUSE accepted by the user ===> ghc-9.4.5 depends on file: /usr/local/sbin/pkg - found => hadrian-9.4.5-boot.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/hadrian-9.4.5-boot.tar.gz fetch: http://distcache.FreeBSD.org/ports-distfiles/hadrian-9.4.5-boot.tar.gz: Not Found => Attempting to fetch http://distcache.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz fetch: http://distcache.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz: Not Found => Attempting to fetch http://distcache.us-east.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz fetch: http://distcache.us-east.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz: Not Found => Attempting to fetch http://distcache.eu.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz fetch: http://distcache.eu.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz: Not Found => Attempting to fetch http://distcache.us-west.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz fetch: http://distcache.us-west.FreeBSD.org/local-distfiles/arrowd/hadrian-9.4.5-boot.tar.gz: No route to host => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/hadrian-9.4.5-boot.tar.gz fetch: http://distcache.FreeBSD.org/ports-distfiles/hadrian-9.4.5-boot.tar.gz: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop. make: stopped in /usr/ports/lang/ghc -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Unable to upgrade Mariadb
Le 5/20/23 22:06, Miroslav Lachman a écrit : I think mariadb will not stop with newer rc script and you will need to kill it manually. Hi Misroslav Yes it was the problem. Thanks ! Cheers Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Unable to upgrade Mariadb
Le 5/20/23 11:58, Xavier Humbert a écrit : Hi, I have MariaDB 10.4 installed, and wanted to upgrade to 10.5 I know that I have to upgrade client first so I dit portupgrade -vf -o databases/mariadb105-client mariadb104-client It fails at install stage with error pkg-static: mariadb105-client-10.5.19 conflicts with mariadb104-server-10.4.28 (installs files into the same place). Problematic file: /usr/local/bin/mariadb-waitpid I previously upgraded from 10.3 to 10.4 without problem Il eventually manage to upgrade by deleting mariadb104-server first, the upgrading the client, then reinstallin mariadb105-server This is not satifying But now, I have this error : [root@numenor ~]# mariadb-upgrade -p -v Enter password: Looking for 'mariadb' as: mariadb Looking for 'mariadb-check' as: mariadb-check Error: Server version (10.4.28-MariaDB) does not match with the version of the server (10.5.19-MariaDB) with which this program was built/distributed. You can use --skip-version-check to skip this check. FATAL ERROR: Upgrade failed [root@numenor ~]# pkg info mariadb\* mariadb105-client-10.5.19 mariadb105-server-10.5.19 Any help appreciated Cheers Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Unable to upgrade Mariadb
Hi, I have MariaDB 10.4 installed, and wanted to upgrade to 10.5 I know that I have to upgrade client first so I dit portupgrade -vf -o databases/mariadb105-client mariadb104-client It fails at install stage with error pkg-static: mariadb105-client-10.5.19 conflicts with mariadb104-server-10.4.28 (installs files into the same place). Problematic file: /usr/local/bin/mariadb-waitpid I previously upgraded from 10.3 to 10.4 without problem Cheers Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: How to determine ports affected by ABI change
Le 5/13/23 16:03, Matthew Seaman a écrit : On 13/05/2023 13:43, Xavier Humbert wrote: I'm planning in a few days, as soon as it beeen branched, to upgrade base from 13-STABLE to 14-STABLE I'm trying to avoid to rebuild my > 1600 ports. Is there a wayto determine ports affected by the ABI change, which must be recompiled ? Obviously Pure Perl or Pure Pyhton don't need to. Since libc and other shared libraries in the FreeBSD base system use API versioning, almost all of your ports will continue to function on 14-STABLE. There will also be a misc/compat13x port to provide compatibility for any non-versioned system shared libraries, which you should install as part of upgrading your base system. So, no need to rebuild everything immediately. With the obvious exception of any loadable kernel modules which will definitely need to be updated to operate with the new 14-STABLE kernel. However, as soon as you start updating ports on your new 14-STABLE system, this can change and simultaneous re-installation of several pkgs be required. That's generally a consequence of something being linked against a different API version somewhere in a dependency chain, which may require the whole dependency chain involved to be updated at the same time. Obviously, as you correctly observe, that only applies to software compiled down into machine code and linked by the system loader, ld.so -- statically linked binaries, interpreted languages (shell) or pure byte-compiled language modules (python, perl, lua, java) won't be affected. Although the interpreters for any of those languages could well be, as would any modules built around loadable shared objects. In terms of packages, the things to look for are: (1) architecture independence: `pkg query -a '%n-%v %q' | grep -F '*'` Although the ABI string built into the package will say eg. `FreeBSD:13:*` indicating a specific major version of the OS, such packages probably _don't_ need to be recompiled for an OS major verson change. (2) Of the architecture dependent packages, check for those requiring or providing shared libraries: `pkg info -bB pkgname` Typically this will not include any shared library dependencies on the base system (so not entirely foolproof) but any package only linking against the base system shlibs and not providing shlibs for anything else to link against is effectively a leaf package in this respect, and can be updated independent of anything else. Look out for compiled dynamically loaded modules too -- things like apache or nginx modules, wrappers for shared libraries to make them available in other languages and so forth. (eg. Python modules that are not architecture independent.) Anything remaining after applying those filters is going to require more care to update smoothly. It's going to be quite a laborious task to classify all of your 1600 ports and map out what depends on what and what groups of packages would need to be reinstalled in synchrony. Whether it's worth it compared to just throwing CPU-cycles at the problem and rebuilding everything straight off is not obvious to me. Running a mixed set of packages from different major OS versions will run the risk of software packages arbitrarily crashing with consequent loss of functionality and potential system downtime. Good luck. Note that if you're using poudriere to build packages, updating a poudriere-jail to 14-STABLE will automatically trigger a full rebuild of all packages, precisely what you want to avoid. Cheers, Matthew Many thanks for this very detailed answer ! Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
How to determine ports affected by ABI change
Hi, I'm planning in a few days, as soon as it beeen branched, to upgrade base from 13-STABLE to 14-STABLE I'm trying to avoid to rebuild my > 1600 ports. Is there a wayto determine ports affected by the ABI change, which must be recompiled ? Obviously Pure Perl or Pure Pyhton don't need to. Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Circular dependency for devel/poetry ?
Hi,
Trying to buil dpoetry, or py-poetry complains that it can find itself :
[root@numenor ports]# cd devel/poetry
[root@numenor poetry]# make all
===> poetry-python-tool-1.3.2_1 depends on package:
py39-CacheControl>=0.12.9 - found
===> poetry-python-tool-1.3.2_1 depends on package: py39-cleo>0 - found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-crashtest>=0.4.1 - found
===> poetry-python-tool-1.3.2_1 depends on package: py39-dulwich>0 - found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-filelock>=3.8.0 - found
===> poetry-python-tool-1.3.2_1 depends on package: py39-html5lib>=1.0
- found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-importlib-metadata>=4.4 - found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-jsonschema>=4.10.0 - found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-keyring>=23.9.0 - found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-lockfile>=0.12.2 - found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-packaging>=20.4 - found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-pexpect>=4.7.0 - found
===> poetry-python-tool-1.3.2_1 depends on package: py39-pkginfo>=1.5
- found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-platformdirs>=2.5.2 - found
===> poetry-python-tool-1.3.2_1 depends on package: py39-poetry-core>0
- found
===> poetry-python-tool-1.3.2_1 depends on package:
py39-poetry-plugin-export>=1.2.0 - not found
===> Building for py39-poetry-plugin-export-1.2.0
* Getting build dependencies for wheel...
Traceback (most recent call last):
File
"/usr/local/lib/python3.9/site-packages/pyproject_hooks/_impl.py", line
321, in _call_hook
raise BackendUnavailable(data.get('traceback', ''))
pyproject_hooks._impl.BackendUnavailable: Traceback (most recent call last):
File
"/usr/local/lib/python3.9/site-packages/pyproject_hooks/_in_process/_in_process.py",
line 77, in _build_backend
obj = import_module(mod_path)
File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 984, in
_find_and_load_unlocked
ModuleNotFoundError: No module named 'poetry'
ERROR Backend 'poetry.core.masonry.api' is not available.
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/devel/py-poetry-plugin-export
*** Error code 1
Stop.
make: stopped in /usr/ports/devel/poetry
[root@numenor poetry]# cd ../py-poetry
[root@numenor py-poetry]# make all
===> Building for py39-poetry-1.3.2_1
* Getting build dependencies for wheel...
Traceback (most recent call last):
File
"/usr/local/lib/python3.9/site-packages/pyproject_hooks/_impl.py", line
321, in _call_hook
raise BackendUnavailable(data.get('traceback', ''))
pyproject_hooks._impl.BackendUnavailable: Traceback (most recent call last):
File
"/usr/local/lib/python3.9/site-packages/pyproject_hooks/_in_process/_in_process.py",
line 77, in _build_backend
obj = import_module(mod_path)
File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in
_find_and_load_unlocked
File "", line 228, in
_call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 984, in
_find_and_load_unlocked
ModuleNotFoundError: No module named 'poetry'
ERROR Backend 'poetry.core.masonry.api' is not available.
*** Error code 1
Stop.
make: stopped in /usr/ports/devel/py-poetry
How can this be resolved ?
FreeBSD STABLE-13, ports from HEAD
Thanks
Xavier
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer
https://www.amdh.fr
[Github-comments] [geany/geany] Crt-shif-V crashes Geany on Ubuntu (Issue #3430)
If you inadvertently type Crtl-shif-V instead of Crrl-V (easy done when you switch from Terminal), Geany crashes The crash report is attached, minus the coredump wich may or not contain sensitive information [geany-crash.zip](https://github.com/geany/geany/files/11001286/geany-crash.zip) -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3430 You are receiving this because you are subscribed to this thread. Message ID:
Re: Bhyve exit code 4 with PCI passthru
Le 2/12/23 16:21, Xavier Humbert a écrit : Hi, Cannot boot VM with PCI passthru enabled. My /boot/loader.conf (relevant part): vmm_load="YES" nmdm_load="YES" if_bridge_load="YES" if_tap_load="YES" pptdevs="10/0/0" hw.vmm.amdvi.enable=1 My vm-bhyve config loader="grub" grub_run_partition="2" cpu=2 memory=4096M network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0.img" uuid="f878c150-de67-11ec-8816-d05099c11279" network0_mac="58:9c:fc:0d:84:62" disk1_name="disk1.img" disk1_type="virtio-blk" disk1_dev="file" disk2_name="disk2.img" disk2_type="virtio-blk" disk1_dev="file" passthru0="10/0/0" bhyve_options="-w" And the log : Feb 12 16:04:40: initialising Feb 12 16:04:40: [loader: grub] Feb 12 16:04:40: [cpu: 2] Feb 12 16:04:40: [memory: 4096M] Feb 12 16:04:40: [hostbridge: standard] Feb 12 16:04:40: [com ports: com1] Feb 12 16:04:40: [uuid: f878c150-de67-11ec-8816-d05099c11279] Feb 12 16:04:40: [debug mode: no] Feb 12 16:04:40: [primary disk: disk0.img] Feb 12 16:04:40: [primary disk dev: file] Feb 12 16:04:40: initialising network device tap0 Feb 12 16:04:40: adding tap0 -> vm-public (public addm) Feb 12 16:04:40: bring up tap0 -> vm-public (public addm) Feb 12 16:04:40: booting Feb 12 16:04:40: create file /vms/valinor/device.map Feb 12 16:04:40: -> (hd0) /vms/valinor/disk0.img Feb 12 16:04:40: -> (hd1) /vms/valinor/disk1.img Feb 12 16:04:40: -> (hd2) /vms/valinor/disk2.img Feb 12 16:04:40: /usr/local/sbin/grub-bhyve -c /dev/nmdm-valinor.1A -S -m /vms/valinor/device.map -M 4096M -r hd0,2 valinor Feb 12 16:05:17: [bhyve options: -c 2 -m 4096M -AHP -w -U f878c150-de67-11ec-8816-d05099c11279 -u -S] Feb 12 16:05:17: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/vms/valinor/disk0.img -s 4:1,virtio-blk,/vms/valinor/disk1.img -s 4:2,virtio-blk,/vms/valinor/disk2.img -s 5:0,virtio-net,tap0,mac=58:9c:fc:0d:84:62 -s 6:0,passthru,10/0/0] Feb 12 16:05:17: [bhyve console: -l com1,/dev/nmdm-valinor.1A] Feb 12 16:05:17: starting bhyve (run 1) Feb 12 16:05:17: bhyve exited with status 4 Feb 12 16:05:17: destroying network device tap0 Feb 12 16:05:18: stopped Any help ? Thanks Chjeers Xavier FWIW, the host is 13.2 STABLE, and the guest Ubuntu server Kinetics Xavier -- Xavier HUMBERT https://www.amdh.fr OpenPGP_signature Description: OpenPGP digital signature
Bhyve exit code 4 with PCI passthru
Hi, Cannot boot VM with PCI passthru enabled. My /boot/loader.conf (relevant part): vmm_load="YES" nmdm_load="YES" if_bridge_load="YES" if_tap_load="YES" pptdevs="10/0/0" hw.vmm.amdvi.enable=1 My vm-bhyve config loader="grub" grub_run_partition="2" cpu=2 memory=4096M network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0.img" uuid="f878c150-de67-11ec-8816-d05099c11279" network0_mac="58:9c:fc:0d:84:62" disk1_name="disk1.img" disk1_type="virtio-blk" disk1_dev="file" disk2_name="disk2.img" disk2_type="virtio-blk" disk1_dev="file" passthru0="10/0/0" bhyve_options="-w" And the log : Feb 12 16:04:40: initialising Feb 12 16:04:40: [loader: grub] Feb 12 16:04:40: [cpu: 2] Feb 12 16:04:40: [memory: 4096M] Feb 12 16:04:40: [hostbridge: standard] Feb 12 16:04:40: [com ports: com1] Feb 12 16:04:40: [uuid: f878c150-de67-11ec-8816-d05099c11279] Feb 12 16:04:40: [debug mode: no] Feb 12 16:04:40: [primary disk: disk0.img] Feb 12 16:04:40: [primary disk dev: file] Feb 12 16:04:40: initialising network device tap0 Feb 12 16:04:40: adding tap0 -> vm-public (public addm) Feb 12 16:04:40: bring up tap0 -> vm-public (public addm) Feb 12 16:04:40: booting Feb 12 16:04:40: create file /vms/valinor/device.map Feb 12 16:04:40: -> (hd0) /vms/valinor/disk0.img Feb 12 16:04:40: -> (hd1) /vms/valinor/disk1.img Feb 12 16:04:40: -> (hd2) /vms/valinor/disk2.img Feb 12 16:04:40: /usr/local/sbin/grub-bhyve -c /dev/nmdm-valinor.1A -S -m /vms/valinor/device.map -M 4096M -r hd0,2 valinor Feb 12 16:05:17: [bhyve options: -c 2 -m 4096M -AHP -w -U f878c150-de67-11ec-8816-d05099c11279 -u -S] Feb 12 16:05:17: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/vms/valinor/disk0.img -s 4:1,virtio-blk,/vms/valinor/disk1.img -s 4:2,virtio-blk,/vms/valinor/disk2.img -s 5:0,virtio-net,tap0,mac=58:9c:fc:0d:84:62 -s 6:0,passthru,10/0/0] Feb 12 16:05:17: [bhyve console: -l com1,/dev/nmdm-valinor.1A] Feb 12 16:05:17: starting bhyve (run 1) Feb 12 16:05:17: bhyve exited with status 4 Feb 12 16:05:17: destroying network device tap0 Feb 12 16:05:18: stopped Any help ? Thanks Chjeers Xavier -- Xavier HUMBERT https://www.amdh.fr OpenPGP_signature Description: OpenPGP digital signature
Upgrade path from db5 to db18
Hi, Now the db5 is EOLed, one need to upgrade to db18. But it obviously breaks port-management-tool, that needs to be rebuild, beginning, I think with rub-bdb. But the latter reinstalls db5 and there is no option to choose the dbd backend. I've written down the dependant ports (pkg delete db5, answering NO gives me the list), so this point is not an issue How can I continue ? Best, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Bug 266172, lang/gnatcross-sysroot-aarch64
Hi,
I've been hit bug bug #266172
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266172>, some files
are immutable in WRKDIR
The port is actually unmaintained, so I looked at Makefile, and noticed :
post-extract:
/bin/chflags -R noschg ${WRKDIR}
It is supposed to do the job, but obviously doesn't
Any idea to fix this ? Is this an upstream problem ?
Cheers,
Xavier
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer
https://www.amdh.fr
portugrade stalls at deinstall stage (sometimes)
Hi, I didn't already track the root cause of this : when using portupgrade, it stalls at deinstall stage. Ctrl-T show it waiting at select() = ---> Updating dependency info ---> Uninstallation of e2fsprogs-libuuid-1.46.5 started at: Sat, 08 Oct 2022 13:03:36 +0200 ---> Fixing up dependencies before creating a package ---> Backing up the old version pkg: unknown format pkg, using the default ---> Uninstalling the old version [Reading data from pkg(8) ... - 1554 packages found - done] ---> Deinstalling 'e2fsprogs-libuuid-1.46.5' load: 0.29 cmd: ruby30 81513 [select] 2829.30r 3.19u 9.33s 0% 52220k mi_switch+0xbf sleepq_catch_signals+0x2e3 sleepq_wait_sig+0x9 _cv_wait_sig+0xeb seltdwait+0x9d kern_poll_kfds+0x4b7 kern_poll+0x9f sys_ppoll+0x6f amd64_syscall+0x10c fast_syscall_common+0xf8 ^C Interrupted. Interrupted. [root@numenor ports]# - 1554 packages found - done] stty: tcsetattr: Input/output error = Switching to the port directory and typing 'make reinstall clean' runs without problem. This is really fastidious when one have >10 ports to upgrade An idea ? Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
[MediaWiki-l] Re: Cannot upgrade past 1.33.4
Youri,
I did it on what was given to me. A running, even broken database.
I started from the last good (err...) backup
Hence the envy to export it all.
Cheers,
Xavier
Le 8/10/22 11:22, Youri van den Bogert a écrit :
Hi Xavier,
No problem; but one more last question; did you do it on a clean upgrade?
In other words; you’ll need to do it on a clean upgrade; not after
everything is broken :-P
Hopefully you manage to sort it.
Youri.
On 10 Aug 2022, at 11:15, Xavier Humbert via MediaWiki-l
wrote:
Grrr :
# php maintenance/createAndPromote.php --sysop temp-admin ***
=> OK
# ./migrate-actors.bash.txt -db pole -dbp mw_pole_ -s debserver -u
*** -p *** -i 42
=> OK
# php maintenance/cleanupUsersWithNoId.php --prefix mw_pole_ --force
=> OK
# php maintenance/migrateActors.php
Query: INSERT INTO `mw_pole_actor` (actor_name) VALUES ('')
Function: MigrateActors::addActorsForRows
Error: 1062 Duplicate entry '' for key 'actor_name' (dbserver)
I'm fed up, give up for now, I fear my database is corrupt beyond
repair... I think about exporting all pages, and the reimporting in a
fresh, empty wiki
Many thanks anyway !
Xavier
Le 8/10/22 10:47, Xavier Humbert via MediaWiki-l a écrit :
Hi Youri
Thanks for your help, I'll try that
Xavier
Le 8/10/22 10:44, Youri van den Bogert a écrit :
Hi Xavier,
Our upgrade process was:
- Run createAndPromote with a temporary user
- Then run migrate-actors.bash (see attached file, run with userid
of temporary user)
- Then cleanupUsersWithNoId (with —force and —prefix *)
- Then migrateActors (with —force)
- Then update.php
--
*Youri van den Bogert*
T: + 31 6 38 76 69 23
E: yvdbog...@archixl.nl
Afwezig op maandag
On 10 Aug 2022, at 10:36, Xavier Humbert via MediaWiki-l
wrote:
Unfortunately I've been hit by the infamous
"User name "XXX" is usable, cannot create an anonymous actor for
it. Run maintenance/cleanupUsersWithNoId.php to fix this situation"
Unfortunately, cleanupUsersWithNoId.php runs, report no error, and
does not correct the problem. It is an already reported behavior
And now, I know that the table prefix_actor is **crucial**, since
without valid actor, the page is lost forever
Xavier
Le 8/10/22 10:11, Xavier Humbert via MediaWiki-l a écrit :
Hi Youri,
Non, I didn't, I'll give a try
Thanks,
Xavier
Le 8/10/22 10:10, Youri van den Bogert a écrit :
Hi Xavier,
Did you run migrateActors before upgrading?
We had similar issues; and the reason was that the user created
the page was deleted. MigrateActors fixed the problem for us.
Greets,
Youri.
On 10 Aug 2022, at 10:02, Xavier Humbert via MediaWiki-l
wrote:
Hi,
I've been asked to upgrade a very, very old wiki : it was
version 1.25.6. I decided to do it step by step, ie release by
release.
I carefully backup-ed the database between each iteration, and
ran maintenance/update.php
Everything went fine until 1.34.4, when the vast majority of
links were broken (Page does not exist yet)
There were some stopper between 1.33 and 1.34 ? I read the
release notes, update.php is intended to do the right job
Thanks for help,
Cheers,
Xavier
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
To unsubscribe send an email to
mediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list --mediawiki-l@lists.wikimedia.org
To unsubscribe send an email tomediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
[MediaWiki-l] Re: Cannot upgrade past 1.33.4
Grrr :
# php maintenance/createAndPromote.php --sysop temp-admin ***
=> OK
# ./migrate-actors.bash.txt -db pole -dbp mw_pole_ -s debserver -u ***
-p *** -i 42
=> OK
# php maintenance/cleanupUsersWithNoId.php --prefix mw_pole_ --force
=> OK
# php maintenance/migrateActors.php
Query: INSERT INTO `mw_pole_actor` (actor_name) VALUES ('')
Function: MigrateActors::addActorsForRows
Error: 1062 Duplicate entry '' for key 'actor_name' (dbserver)
I'm fed up, give up for now, I fear my database is corrupt beyond
repair... I think about exporting all pages, and the reimporting in a
fresh, empty wiki
Many thanks anyway !
Xavier
Le 8/10/22 10:47, Xavier Humbert via MediaWiki-l a écrit :
Hi Youri
Thanks for your help, I'll try that
Xavier
Le 8/10/22 10:44, Youri van den Bogert a écrit :
Hi Xavier,
Our upgrade process was:
- Run createAndPromote with a temporary user
- Then run migrate-actors.bash (see attached file, run with userid
of temporary user)
- Then cleanupUsersWithNoId (with —force and —prefix *)
- Then migrateActors (with —force)
- Then update.php
--
*Youri van den Bogert*
T: + 31 6 38 76 69 23
E: yvdbog...@archixl.nl
Afwezig op maandag
On 10 Aug 2022, at 10:36, Xavier Humbert via MediaWiki-l
wrote:
Unfortunately I've been hit by the infamous
"User name "XXX" is usable, cannot create an anonymous actor for it.
Run maintenance/cleanupUsersWithNoId.php to fix this situation"
Unfortunately, cleanupUsersWithNoId.php runs, report no error, and
does not correct the problem. It is an already reported behavior
And now, I know that the table prefix_actor is **crucial**, since
without valid actor, the page is lost forever
Xavier
Le 8/10/22 10:11, Xavier Humbert via MediaWiki-l a écrit :
Hi Youri,
Non, I didn't, I'll give a try
Thanks,
Xavier
Le 8/10/22 10:10, Youri van den Bogert a écrit :
Hi Xavier,
Did you run migrateActors before upgrading?
We had similar issues; and the reason was that the user created
the page was deleted. MigrateActors fixed the problem for us.
Greets,
Youri.
On 10 Aug 2022, at 10:02, Xavier Humbert via MediaWiki-l
wrote:
Hi,
I've been asked to upgrade a very, very old wiki : it was version
1.25.6. I decided to do it step by step, ie release by release.
I carefully backup-ed the database between each iteration, and
ran maintenance/update.php
Everything went fine until 1.34.4, when the vast majority of
links were broken (Page does not exist yet)
There were some stopper between 1.33 and 1.34 ? I read the
release notes, update.php is intended to do the right job
Thanks for help,
Cheers,
Xavier
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list --mediawiki-l@lists.wikimedia.org
To unsubscribe send an email tomediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39
___
MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org
To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
[MediaWiki-l] Re: Cannot upgrade past 1.33.4
Hi Youri Thanks for your help, I'll try that Xavier Le 8/10/22 10:44, Youri van den Bogert a écrit : Hi Xavier, Our upgrade process was: - Run createAndPromote with a temporary user - Then run migrate-actors.bash (see attached file, run with userid of temporary user) - Then cleanupUsersWithNoId (with —force and —prefix *) - Then migrateActors (with —force) - Then update.php -- *Youri van den Bogert* T: + 31 6 38 76 69 23 E: yvdbog...@archixl.nl Afwezig op maandag On 10 Aug 2022, at 10:36, Xavier Humbert via MediaWiki-l wrote: Unfortunately I've been hit by the infamous "User name "XXX" is usable, cannot create an anonymous actor for it. Run maintenance/cleanupUsersWithNoId.php to fix this situation" Unfortunately, cleanupUsersWithNoId.php runs, report no error, and does not correct the problem. It is an already reported behavior And now, I know that the table prefix_actor is **crucial**, since without valid actor, the page is lost forever Xavier Le 8/10/22 10:11, Xavier Humbert via MediaWiki-l a écrit : Hi Youri, Non, I didn't, I'll give a try Thanks, Xavier Le 8/10/22 10:10, Youri van den Bogert a écrit : Hi Xavier, Did you run migrateActors before upgrading? We had similar issues; and the reason was that the user created the page was deleted. MigrateActors fixed the problem for us. Greets, Youri. On 10 Aug 2022, at 10:02, Xavier Humbert via MediaWiki-l wrote: Hi, I've been asked to upgrade a very, very old wiki : it was version 1.25.6. I decided to do it step by step, ie release by release. I carefully backup-ed the database between each iteration, and ran maintenance/update.php Everything went fine until 1.34.4, when the vast majority of links were broken (Page does not exist yet) There were some stopper between 1.33 and 1.34 ? I read the release notes, update.php is intended to do the right job Thanks for help, Cheers, Xavier -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/ -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/ -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
[MediaWiki-l] Re: Cannot upgrade past 1.33.4
Unfortunately I've been hit by the infamous "User name "XXX" is usable, cannot create an anonymous actor for it. Run maintenance/cleanupUsersWithNoId.php to fix this situation" Unfortunately, cleanupUsersWithNoId.php runs, report no error, and does not correct the problem. It is an already reported behavior And now, I know that the table prefix_actor is **crucial**, since without valid actor, the page is lost forever Xavier Le 8/10/22 10:11, Xavier Humbert via MediaWiki-l a écrit : Hi Youri, Non, I didn't, I'll give a try Thanks, Xavier Le 8/10/22 10:10, Youri van den Bogert a écrit : Hi Xavier, Did you run migrateActors before upgrading? We had similar issues; and the reason was that the user created the page was deleted. MigrateActors fixed the problem for us. Greets, Youri. On 10 Aug 2022, at 10:02, Xavier Humbert via MediaWiki-l wrote: Hi, I've been asked to upgrade a very, very old wiki : it was version 1.25.6. I decided to do it step by step, ie release by release. I carefully backup-ed the database between each iteration, and ran maintenance/update.php Everything went fine until 1.34.4, when the vast majority of links were broken (Page does not exist yet) There were some stopper between 1.33 and 1.34 ? I read the release notes, update.php is intended to do the right job Thanks for help, Cheers, Xavier -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/ -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
[MediaWiki-l] Re: Cannot upgrade past 1.33.4
Hi Youri, Non, I didn't, I'll give a try Thanks, Xavier Le 8/10/22 10:10, Youri van den Bogert a écrit : Hi Xavier, Did you run migrateActors before upgrading? We had similar issues; and the reason was that the user created the page was deleted. MigrateActors fixed the problem for us. Greets, Youri. On 10 Aug 2022, at 10:02, Xavier Humbert via MediaWiki-l wrote: Hi, I've been asked to upgrade a very, very old wiki : it was version 1.25.6. I decided to do it step by step, ie release by release. I carefully backup-ed the database between each iteration, and ran maintenance/update.php Everything went fine until 1.34.4, when the vast majority of links were broken (Page does not exist yet) There were some stopper between 1.33 and 1.34 ? I read the release notes, update.php is intended to do the right job Thanks for help, Cheers, Xavier -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/ -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
[MediaWiki-l] Cannot upgrade past 1.33.4
Hi, I've been asked to upgrade a very, very old wiki : it was version 1.25.6. I decided to do it step by step, ie release by release. I carefully backup-ed the database between each iteration, and ran maintenance/update.php Everything went fine until 1.34.4, when the vast majority of links were broken (Page does not exist yet) There were some stopper between 1.33 and 1.34 ? I read the release notes, update.php is intended to do the right job Thanks for help, Cheers, Xavier -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
Could a commiter have a look please
Hi, Could a commiter have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261230 ? sysutils/p5-RundeckAPI Thanks, Xavier -- -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Apache keeps crashing, where is the core file ?
Le 7/19/22 10:55, Christoph Moench-Tegeder a écrit : ## Xavier Humbert (xav...@groumpf.org): I don't know where the core file is dumped, in the current directory of the process, I presume, which I ignore. That's up to you to decide: https://httpd.apache.org/docs/2.4/mod/mpm_common.html#coredumpdirectory or sysctl kern.corefile. Regards, Christoph Thank you, I forgot this (rarely used) directive :-) Cheers Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Apache keeps crashing, where is the core file ?
Hi, For whatever reason I want to analyze, Apache24 keeps crashing : +pid 7246 (httpd), jid 0, uid 0: exited on signal 11 (core dumped) I don't know where the core file is dumped, in the current directory of the process, I presume, which I ignore. I checked for the homedir of www user, it is "/nonexistent" as expected Thanks for any help Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
archivers/p5-Compress-Raw-Zlib breaks amavis among other things
Hi, latest upgrade to archivers/p5-Compress-Raw-Zlib introduce some ABI versioning I guess, breaks many things, for me it is amavisd See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263965 Applied the proposed patch, amavis is working again Regards, Xavier -- -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Adding storage to a guest
Le 3/17/22 01:28, Chuck Tuffli a écrit : On Sun, Mar 13, 2022 at 5:36 AM Xavier Humbert wrote: Hi, I have a Ubuntu-server as guest on Byhve/FreeBDS 13 I tried to add some extra storage, so added disk2_dev="custom" disk2_opts="sectorsize=512" disk2_type="virtio-blk" disk2_name="disk2.img" to the config file. Unfortunately, it doesn't show under /dev/vda* in the guest. Where is my mistake ? Looking at my configurations, they typically don't set disk*_dev unless the device is a sparse-zvol. If disk2.img is a regular file, does removing the disk2_dev line help? --chuck Hi Chuck, Unfortunately, it doensn't change anything Thanks Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Adding storage to a guest
Hi, I have a Ubuntu-server as guest on Byhve/FreeBDS 13 I tried to add some extra storage, so added disk2_dev="custom" disk2_opts="sectorsize=512" disk2_type="virtio-blk" disk2_name="disk2.img" to the config file. Unfortunately, it doesn't show under /dev/vda* in the guest. Where is my mistake ? TIA, Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: Ubuntu guest Grub prompt
Thanks to all, adding <> fixed my problem ! Cheers, Xavier Le 2/27/22 14:08, daniel domscheit-berg a écrit : Hej Xavier, try adding grub_run_partition="2" grub_run_dir="/grub" to your VM config file. Should do the trick. All the best daniel On 2/27/22 13:07, havellab catchall wrote: Forwarded Message Subject: Ubuntu guest Grub prompt Date: Sun, 27 Feb 2022 11:19:18 +0100 From: Xavier Humbert To: freebsd-virtualizat...@freebsd.org Hi, I've installed (many tries) Ubuntu 21 as guest on FreeBSD 13 Installation runs without problem, but a boot, it drops to grub prompt. I know how to boot (set prefix=(hd0,gpt2)/boot/grub etc...) But how to fix permanently ? My config file : loader="grub" cpu=2 memory=2048M network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0.img" uuid="9fb3f8a7-7935-11ec-ae5a-d05099c11279" network0_mac="58:9c:fc:00:1b:ed" Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Ubuntu guest Grub prompt
Hi, I've installed (many tries) Ubuntu 21 as guest on FreeBSD 13 Installation runs without problem, but a boot, it drops to grub prompt. I know how to boot (set prefix=(hd0,gpt2)/boot/grub etc...) But how to fix permanently ? My config file : loader="grub" cpu=2 memory=2048M network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0.img" uuid="9fb3f8a7-7935-11ec-ae5a-d05099c11279" network0_mac="58:9c:fc:00:1b:ed" Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: php-fpm (8.0) strange error related to smbclient
Hi Misroslav, I removed SMB support from Nextcoud's config, then was able topkg delete php80-pecl-smbclient-1.0.6 Le 2/5/22 00:01, Miroslav Lachman a écrit : This is just a wild guess but I thing there is something wrong with your pecl-smbclient extension. The Fatal error is from loading this extension at the start of php-fpm and not from calling some function in any PHP script. There is a source code where it is really twice oldstate and twice oldpath https://github.com/eduardok/libsmbclient-php/blob/master/smbclient.c#L189 ZEND_BEGIN_ARG_INFO(arginfo_smbclient_rename, 0) ZEND_ARG_INFO(0, oldstate) ZEND_ARG_INFO(0, oldpath) ZEND_ARG_INFO(0, oldstate) ZEND_ARG_INFO(0, oldpath) ZEND_END_ARG_INFO() I am not a C programmer but it seems wrong to me, because PHP function smbclient_rename takes 4 different parameters: smbclient_rename ( resource $state_old, string $uri_old, resource $state_new, string $uri_new ) I will expect something like this: ZEND_BEGIN_ARG_INFO(arginfo_smbclient_rename, 0) ZEND_ARG_INFO(0, oldstate) ZEND_ARG_INFO(0, oldpath) ZEND_ARG_INFO(0, newstate) ZEND_ARG_INFO(0, newpath) ZEND_END_ARG_INFO() But I don't know if this will fix it or destroy the whole universe. Miroslav Lachman I opened a PR on Github Cheers, Xavier -- -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
php-fpm (8.0) strange error related to smbclient
Hi, I recently upgraded my whole php stuff from 7.3 to 8.0 via portupgrade All went flawlessly. But when I want to start php-fpm, I got this error about which Google knows nothing : [root@numenor php80]# service php-fpm restart Performing sanity check on php-fpm configuration: Fatal error: Duplicate parameter name $oldstate for function smbclient_rename() in Unknown on line 0 I eventually grepped the whole /usr/local/etc AND /usr/local/www directories for this parameter with no success Where the hell does this come from ? Samba, obviously, a grep in /usr/local/lib/php matches in smbclient.so Also, libsbmclient-php sources show this parameter twice : https://github.com/eduardok/libsmbclient-php/blob/master/smbclient.c#L189 But how fix this, any idea May I fill a PR ? Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
Re: PHP73 removed ?
Hi, Kurt Le 1/29/22 11:52, Kurt Jaeger a écrit : Hi! I have PHP 7.3 installed and the weekly report shows me an attempt to upgrade to PHP 7.4, which failed with IGNORE : https://www.php.net/releases/ says that End of Life Dates The most recent branches to reach end of life status are: 7.3: 18 Nov 2021 so that's why it was dropped from the ports. For other deprecation, there were IIRC message in the list or in UPDATING ** Port marked as IGNORE: math/php74-bcmath: cannot be installed: doesn't work with lang/php73 port (doesn't support PHP 7.2 7.3) ... And peridoc/weekly/400.status-pkg tells me : php73-7.3.33 orphaned: lang/php73 php73-bcmath-7.3.33 orphaned: math/php73-bcmath php73-bz2-7.3.33 orphaned: archivers/php73-bz2 php73-calendar-7.3.33 orphaned: misc/php73-calendar ... Did I miss some announcement ? UPDATING just tells about the fact that PHP 8.0 is the new default version. You can still use php 7.4, and if you install php74 and all the php74- packages, your application probably will still work. Which application do you use ? Mainly nexcloud-server Thanks, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
PHP73 removed ?
Hello, I have PHP 7.3 installed and the weekly report shows me an attempt to upgrade to PHP 7.4, which failed with IGNORE : ** Port marked as IGNORE: math/php74-bcmath: cannot be installed: doesn't work with lang/php73 port (doesn't support PHP 7.2 7.3) ... And peridoc/weekly/400.status-pkg tells me : php73-7.3.33 orphaned: lang/php73 php73-bcmath-7.3.33 orphaned: math/php73-bcmath php73-bz2-7.3.33 orphaned: archivers/php73-bz2 php73-calendar-7.3.33 orphaned: misc/php73-calendar ... Did I miss some announcement ? UPDATING just tells about the fact that PHP 8.0 is the new default version. Thanks, Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr
A lot a false negatives
Hi, My Thunderbird's Junk mailbox is full (75%) of spams, recognized by TB's bayes engine, but not by SA's. They are quite often even scored as negatives Despite the monthly use of sa_learn from Junk mailbox, spams keep being not flagged. Example a false negative : X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5.5 tests=[AWL=0.642, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_IMAGE_RATIO_04=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, MIME_QP_LONG_LINE=0.001, SPF_FAIL=0.001, SPF_HELO_NONE=0.001] autolearn=ham autolearn_force=no versus a detected spam : X-Spam-Status: Yes, score=16.885 tagged_above=-999 required=5.5 tests=[ANY_PILL_PRICE=1, BAYES_60=1.5, DATE_IN_FUTURE_12_24=3.199, DRUGS_ERECTILE=1.994, DRUGS_ERECTILE_OBFU=1.109, GAPPY_LOW_CONTRAST=2.497, GAPPY_SUBJECT=0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_ABUSE_SURBL=1.25, URIBL_DBL_SPAM=2.5, URIBL_SBL=1.623, URIBL_SBL_A=0.1] autolearn=spam autolearn_force=no I use SA for more than 10 years, but in a very basic manner. Is there some doc on how to harden SA ? Some useful plugins ? Bayes is clearly not sufficient in my case Thanks in advance Regards Xavier -- Xavier HUMBERT AMDH.FR - Infogérance - Architecte Réseaux et Systèmes https://www.amdh.fr/
Re: A good name for development branch releases package
Hi Petr, Le 11/30/21 16:09, Petr Menšík a écrit : Is there any distribution offering already two releases at the same time? Would you have some idea, how should it be called? Do you like "bind9-dev" base name? For example, FreeBSD provides 3 bind releases : - dns/bind-devel - dns/bind911 - dns/bind916 HTH Xavier -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 OpenPGP_0x90B78A89BCC49C10.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Gitlab won't start. Error in rc file ?
Le 03/11/2021 15:45, Matthias Fechner a écrit : [...snip...] have you followed the installation manual? https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/install/14.4-freebsd.md Gruß Matthias Yes, step by step. But meantime, I found a workaround, not very secure, but usable for personal use : give a real shell to user git Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Re: Gitlab won't start. Error in rc file ?
EDIT I wrote : + eval su - git -c '"/usr/local/etc/rc.d/gitlab' 'start"' + su - git -c '/usr/local/etc/rc.d/gitlab start' fatal: unrecognized command '/usr/local/etc/rc.d/gitlab start' + exit The last fatal line led me to think of inappropriate file perms, but the full path is og+rX. Digging further, I found that user *git* is not allowed to execute any command. However, git shell *is* installed, liste in /etc/shells, and id the login shell for user git Any idea before I post to oGitlab forum, which is more Linux-centric, and probably won't help in this very matter ? Cheers Xavier I read docs about git-shell, and the directory ~/git-shells-commands Symlinking /bin/echo here now allows git to echo "hello word". Good start Alas, linking /usr/local/etc/rc.d/gitlab won't do the job. -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Gitlab won't start. Error in rc file ?
Hi, Just installed gitlab-ce from ports (took hours), but instance won't start. Just *service gitlab start* fails miserably. Here is the end of the invocation of the rc file, with -x [root@numenor ~]]# sh -x /usr/local/etc/rc.d/gitlab start + gitlab_init + test -f /etc/default/gitlab + /usr/sbin/pkg -N info -e gogs + + /usr/sbin/pkg -N info -e 'gitolite*' + + /usr/sbin/pkg -N info -e '*gitosis*' + + /usr/sbin/pkg -N info -e gitea + + [ root '!=' git ] + rm -f /usr/local/www/gitlab-ce/Gemfile.lock + su -l root -c 'cd /usr/local/www/gitlab-ce && /usr/local/bin/bundle install --local --quiet' Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. + chown git /usr/local/www/gitlab-ce/Gemfile.lock + rm -f /usr/local/share/gitaly/ruby/Gemfile.lock + su -l root -c 'cd /usr/local/share/gitaly/ruby && /usr/local/bin/bundle install --local --quiet' Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. + echo '"' + echo '"' + eval su - git -c '"/usr/local/etc/rc.d/gitlab' 'start"' + su - git -c '/usr/local/etc/rc.d/gitlab start' fatal: unrecognized command '/usr/local/etc/rc.d/gitlab start' + exit The last fatal line led me to think of inappropriate file perms, but the full path is og+rX. Digging further, I found that user *git* is not allowed to execute any command. However, git shell *is* installed, liste in /etc/shells, and id the login shell for user git Any idea before I post to oGitlab forum, which is more Linux-centric, and probably won't help in this very matter ? Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Re: CNAME for google sites
Hello Elias, This is not a CNAME, but rather a redirection at the web server (Apache or Nginx) level Cheers, Xavier Le 10/25/21 15:40, Elias Pereira a écrit : Hi, Google sites use a domain in the following way for their free sites. https://sites.google.com/company.com/mysite/ How can I create a CNAME for a site in this format? Is there another way? -- Elias Pereira -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 OpenPGP_0x90B78A89BCC49C10.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Packages : perl5-5.30 outdated but forced for any package
On 10/18/21 10:47, Herbert J. Skuhra wrote:
On Mon, 18 Oct 2021 10:13:26 +0200, Xavier Humbert wrote:
On 10/16/21 17:47, Herbert J. Skuhra wrote:
On Sat, 16 Oct 2021 16:35:08 +0200, Xavier Humbert wrote:
I should definiteldy check, but what, I dunno
[xavier@numenor ports]$ grep DEFAULT_VERSIONS /etc/make.conf
DEFAULT_VERSIONS+=ssl=openssl
DEFAULT_VERSIONS+=python=3.8
DEFAULT_VERSIONS+=php=7.3
DEFAULT_VERSIONS+=perl5=5.34
[xavier@numenor ports]$ pkg info perl5
perl5-5.34.0
Name : perl5
Version : 5.34.0
Installed on : Wed Aug 11 20:46:45 2021 CEST
As you can see, my version and DEFAULT_VERSIONS are in sync
- Have you updated perl from perl 5.30 and have you followed the
instructions in UPDATING (entry from 20161103)?
Yes, I did
- Are there any files in /usr/local/lib/perl5/5.30/ or
/usr/local/lib/perl5/site_perl/mach/5.30/? Can you run 'pkg which' on
them?
Err, yes there are files.
I thought I found the culprit :
[root@numenor ~]# pkg which
/usr/local/lib/perl5/site_perl/mach/5.30/ModPerl/BuildMM.pm
/usr/local/lib/perl5/site_perl/mach/5.30/ModPerl/BuildMM.pm was
installed by package ap24-mod_perl2-2.0.11,3
ap24-mod_perl2 does not compile actually, see my previous posts, left
unanswered
But if I remove ap24-mod_perl2, still wants to downgrade Perl
- What happens if you run 'pkg upgrade'?
[root@numenor ~]# pkg upgrade
Updating FreeBSD repository catalogue...
[...]
Checking for upgrades (1903 candidates): 100%Processing candidates
(1903 candidates): 100%
The following 678 package(s) will be affected (of 0 checked):
[...mainly perl dependencies. Not astonished...]
But :
Installed packages to be DOWNGRADED:
perl5: 5.34.0 -> 5.32.1_1
This is expected. Perl 5.32 is the default version for packages.
1. Is the original problem resolved (pkg install py38-platformdirs)?
It's fixed now, dunno what happened :-)
Or does it still try to install perl 5.30? What error do you get when
you try to compile the port?
[root@numenor ~]# cd /usr/ports/devel/py-platformdirs/
[root@numenor py-platformdirs]# make
===> py38-platformdirs-2.4.0 depends on package: py38-setuptools>0 -
found
===> py38-platformdirs-2.4.0 depends on file: /usr/local/bin/python3.8
- found
===> Configuring for py38-platformdirs-2.4.0
Traceback (most recent call last):
File "", line 1, in
File "setup.py", line 3, in
setup()
File "/usr/local/lib/python3.8/site-packages/setuptools/__init__.py",
line 153, in setup
return distutils.core.setup(**attrs)
File "/usr/local/lib/python3.8/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/local/lib/python3.8/site-packages/setuptools/dist.py", line
455, in __init__
_Distribution.__init__(self, {
File "/usr/local/lib/python3.8/distutils/dist.py", line 292, in __init__
self.finalize_options()
File "/usr/local/lib/python3.8/site-packages/setuptools/dist.py", line
801, in finalize_options
ep(self)
File
"/usr/local/lib/python3.8/site-packages/setuptools_scm/integration.py",
line 48, in infer_version
dist.metadata.version = _get_version(config)
File
"/usr/local/lib/python3.8/site-packages/setuptools_scm/__init__.py",
line 156, in _get_version
dump_version(
File
"/usr/local/lib/python3.8/site-packages/setuptools_scm/__init__.py",
line 84, in dump_version
fp.write(template.format(version=version))
KeyError: 'version_tuple'
2. mod_perl2 obviously needs a patch for perl 5.34:
https://svn.apache.org/viewvc?view=revision=1889014
Thanks, I'll take a look
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer
https://www.amdh.fr
Re: Packages : perl5-5.30 outdated but forced for any package
On 10/16/21 17:47, Herbert J. Skuhra wrote: On Sat, 16 Oct 2021 16:35:08 +0200, Xavier Humbert wrote: I should definiteldy check, but what, I dunno [xavier@numenor ports]$ grep DEFAULT_VERSIONS /etc/make.conf DEFAULT_VERSIONS+=ssl=openssl DEFAULT_VERSIONS+=python=3.8 DEFAULT_VERSIONS+=php=7.3 DEFAULT_VERSIONS+=perl5=5.34 [xavier@numenor ports]$ pkg info perl5 perl5-5.34.0 Name : perl5 Version : 5.34.0 Installed on : Wed Aug 11 20:46:45 2021 CEST As you can see, my version and DEFAULT_VERSIONS are in sync - Have you updated perl from perl 5.30 and have you followed the instructions in UPDATING (entry from 20161103)? Yes, I did - Are there any files in /usr/local/lib/perl5/5.30/ or /usr/local/lib/perl5/site_perl/mach/5.30/? Can you run 'pkg which' on them? Err, yes there are files. I thought I found the culprit : [root@numenor ~]# pkg which /usr/local/lib/perl5/site_perl/mach/5.30/ModPerl/BuildMM.pm /usr/local/lib/perl5/site_perl/mach/5.30/ModPerl/BuildMM.pm was installed by package ap24-mod_perl2-2.0.11,3 ap24-mod_perl2 does not compile actually, see my previous posts, left unanswered But if I remove ap24-mod_perl2, still wants to downgrade Perl - What happens if you run 'pkg upgrade'? [root@numenor ~]# pkg upgrade Updating FreeBSD repository catalogue... [...] Checking for upgrades (1903 candidates): 100%Processing candidates (1903 candidates): 100% The following 678 package(s) will be affected (of 0 checked): [...mainly perl dependencies. Not astonished...] But : Installed packages to be DOWNGRADED: perl5: 5.34.0 -> 5.32.1_1 - pkg check -d ? Is OK Thanks, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Re: Packages : perl5-5.30 outdated but forced for any package
Hi Herbert On 10/16/21 11:00, Herbert J. Skuhra wrote: You should check your system. What's the output of 'pkg info perl5'? I should definiteldy check, but what, I dunno [xavier@numenor ports]$ grep DEFAULT_VERSIONS /etc/make.conf DEFAULT_VERSIONS+=ssl=openssl DEFAULT_VERSIONS+=python=3.8 DEFAULT_VERSIONS+=php=7.3 DEFAULT_VERSIONS+=perl5=5.34 [xavier@numenor ports]$ pkg info perl5 perl5-5.34.0 Name : perl5 Version : 5.34.0 Installed on : Wed Aug 11 20:46:45 2021 CEST As you can see, my version and DEFAULT_VERSIONS are in sync Thanks Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Packages : perl5-5.30 outdated but forced for any package
Hi, I had to install via pkg a Python module that won't compile. I know it's Bad to mix ports and packages, but it doesn't compile for an unknown reason, and I need it. When I do pkg install devel/py-platformdirs It says New packages to be INSTALLED: perl5.30: 5.30.3_1 py38-platformdirs: 2.3.0 [...] = Message from perl5.30-5.30.3_1: [...] ===> NOTICE: This port is deprecated; you may wish to reconsider installing it: Why does pkg insist to install an old, outdated version of perl (I have an up-to-date perl already) ? Please consider updating perl in Packages (latest is afaik 5.34) Regards Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
mod_perl2 does not build
Hi, I have Perl 5.34.0, and mod_perl2 does not build anymore. After a ton of warnings like : /usr/local/lib/perl5/5.34/mach/CORE/thread.h:393:7: note: expanded from macro 'PERL_SET_CONTEXT' } STMT_END ^~~~ /usr/local/lib/perl5/5.34/mach/CORE/perl.h:738:21: note: expanded from macro 'STMT_END' # define STMT_END ) ^ I finally got an error : [root@numenor mod_perl2]# MAKE_JOBS_UNSAFE=yes make -j 1 [...] modperl_perl.c:271:16: error: cannot take the address of an rvalue of type 'U8 *' (aka 'unsigned char *') memcpy(_hash_seed, _init_hash_seed, ^ 100 warnings and 1 error generated. gmake[2]: *** [Makefile:114: modperl_perl.lo] Error 1 gmake[2]: Leaving directory '/usr/ports/www/mod_perl2/work/mod_perl-2.0.11/src/modules/perl' gmake[1]: *** [Makefile:450: modperl_lib] Error 2 gmake[1]: Leaving directory '/usr/ports/www/mod_perl2/work/mod_perl-2.0.11' *** [do-build] Error code 1 What is the problem and how to fix it ? Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
mod_perl2 broken
Hi, Since the upgrade of perl to 5.34, mod_perl build fails with modperl_perl.c:271:16: error: cannot take the address of an rvalue of type 'U8 *' (aka 'unsigned char *') Seems to be related to https://github.com/Perl/perl5/issues/18555 and https://github.com/Perl/perl5/issues/18617 Any idea when it will be fixed upstream ? Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
pkg: unknown format pkg, using the default
Hi, poking mat@ Since last update of pkg, a warning is emitted at "make package" stage : ---> Build of lang/php73 ended at: Fri, 03 Sep 2021 13:24:01 +0200 (consumed 00:02:29) ---> Updating dependency info ---> Uninstallation of php73-7.3.29_1 started at: Fri, 03 Sep 2021 13:24:01 +0200 ---> Fixing up dependencies before creating a package ---> Backing up the old version pkg: unknown format pkg, using the default <= HERE ! Besides that, all runs perfect, this is just a warning What is the cause of this ? Thanks, Cheers -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Port from Linux, Makefile not in top-level
Hi, I'm porting rudder-agent to FreeBSD, but I have a problem since the
main Makefile is not at the top level of the hierarchy, as shown below
(excerpt)
rudder-sources-6.2.7/
├── rudder-agent
│ ├── bin
│ ├── etc
│ ├── LICENSE
│ ├── man
│ ├── qa-test
│ ├── README.md
│ └── share
├── rudder-packages
│ └── rudder-agent
│ └── SOURCES
│ ├── Makefile
│ └── Makefile.orig
└── NO Makefile AT THIS LEVEL
The solution, at first glance seems to be simple : set
WRKSRC_SUBDIR=rudder-packages/${PORTNAME}/SOURCES
(ie work/rudder-sources-6.2.7/rudder-packages/rudder-agent/SOURCES)
In fact, ${WRKSRC_SUBDIR}/Makefile takes care of the first-level
"rudder-agent", and files are correctly installed in the "stage" directory,
but a huge problem arises :
"make makepatch" and "make patch" ignore this first-level directory, and I
have files to patch here
What would be the solution ? If I leave alone WRKSRC_SUBDIR using a
"do-build"
target in my Makefile :
│ do-build:
│ cd ${WRKSRC}/rudder-packages/rudder-agent/SOURCES && \
│ ${SETENV} ${MAKE_ENV} ${MAKE_CMD} install)
Nothing works, and make all complains about a top-level Makefile missing
TIA, hope I've been clear enough, feel free to ask more
Regards
Xavier
Here is my Makefile :
===
PORTNAME= rudder-agent
DISTVERSION= 6.2.7
CATEGORIES= sysutils
DISTNAME= rudder-sources-${DISTVERSION}
MASTER_SITES= https://repository.rudder.io/sources/${DISTVERSION}/
EXTRACT_SUFX= .tar.bz2
MAINTAINER= xav...@amdh.fr
COMMENT= Agent for Rudder
USES= perl5
USES= gmake
LICENSE= GPLv2+
LICENSE_FILE=
${WRKDIR}/rudder-sources-${DISTVERSION}/rudder-packages/LICENSE
LIB_DEPENDS+= libpcre.so:devel/pcre \
liblmdb.so:databases/lmdb \
libreadline.so:devel/readline \
libyaml.so:textproc/libyaml \
libxml2.so:textproc/libxml2 \
libaugeas.so:textproc/augeas
BUILD_DEPENDS+= hs-ShellCheck>=0.7.2:devel/hs-ShellCheck \
openssl>=1.1.1:security/openssl \
cfengine317>=3.17.0:sysutils/cfengine317 \
curl>7.76.1:ftp/curl \
jq>=1.6:textproc/jq \
p5-FusionInventory-Agent>=0:net-mgmt/p5-FusionInventory-Agent \
p5-File-Which>=1.2.7:sysutils/p5-File-Which \
p5-libwww>=6.54:www/p5-libwww \
p5-Net-IP>=1.26:net-mgmt/p5-Net-IP \
p5-Text-Template>=1.59:textproc/p5-Text-Template \
p5-UNIVERSAL-require>=0.18:devel/p5-UNIVERSAL-require \
p5-XML-TreePP>=0.43:textproc/p5-XML-TreePP \
p5-Parse-EDID>=1.0.7:textproc/p5-Parse-EDID \
p5-DateTime>=1.54:devel/p5-DateTime \
p5-DateTime-TimeZone>=2.47:devel/p5-DateTime-TimeZone \
p5-Net-SNMP>=6.0.1:net-mgmt/p5-Net-SNMP \
p5-Net-NBName>=0.26:net/p5-Net-NBName \
p5-Thread-Queue>=3.13:devel/p5-Thread-Queue
CC?= gcc10
BINARY_ALIAS= gcc=${CC}
MAKE_ENV= USE_SYSTEM_PERL=yes
SHORT_NAME= rudder
NO_ARCH= yes
WRKSRC_SUBDIR= rudder-packages/${PORTNAME}/SOURCES
post-patch:
cd ${WRKSRC}/${PORTNAME}/man && make all
.include
===
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer
https://www.amdh.fr
Fwd: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14
FYI : Do not upgrade ! Forwarded Message Subject: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14 Date: Thu, 17 Jun 2021 19:56:58 -0800 From: Michael McNally To: bind-us...@lists.isc.org Dear BIND users: Yesterday, 16 June 2021, we released monthly maintenance snapshot releases of our currently supported release branches of BIND. Specifically, we released BIND 9.11.33, 9.16.17, and 9.17.14 There's no way to say this that isn't embarrassing, but only after the release was an error in a recently optimized routine discovered by a user -- an error that will definitely cause operational problems for almost all server operators who upgrade to either of these affected versions: - BIND 9.16.17 - BIND 9.17.14 BIND 9.11.33 is NOT affected. If you have not yet updated to the 16 June releases, we ask that you hold off on any plans to install 9.16.17 or 9.17.14 until replacement releases can be prepared and tested. The specific issue in question is being tracked in our issue tracker: https://gitlab.isc.org/isc-projects/bind9/-/issues/2779 and more information about our plans for issuing replacement releases will be provided later; at the moment our priority is getting the news to parties as quickly as possible so that those who have not already adopted the new releases can postpone until corrected versions are available. Michael McNally Internet Systems Consortium ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-us...@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Forcing options in required ports
Hi, I need to add a BUILD_DEPENDS to a port (p5-FusionInventory-Agent, actually) with specifics options required by the port which requires it This lead to 12 questions : 1- Is there a way to specify options port in the Makefile ? 2- As a consequence, the port cannot be fetched from packages, it *must* be built from ports. How to force this ? Thanks Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Re: Any interest in a write-up showing how to configure BIND 9.17x with DoH and LetsEncrypt?
On 30/05/2021 17:24, Richard T.A. Neal wrote: DNS over HTTPS support appears to be steadily increasing and it looks like the next version of Windows 10, Windows 10 21H2, will including support for DoH at the operating system level. � I spent a little time this weekend setting-up BIND 9.17.13 on Ubuntu 21.04 and configuring the system as a recursive resolver offering DNS over HTTPS using a LetsEncrypt certificate. � Is there any interest in me writing this up as a web article, or has everyone who’s interested in DoH already got it running comfortably in their test environment? � Best. � Richard. Oh yes, please do ! Xavier -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 OpenPGP_0x90B78A89BCC49C10.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Installing Linux files originally in /opt
Hi, What is the Right Thing To Do with Linux hierarchies based in /opt ? 1 /opt//bin -> /usr/local/bin OR /usr/local//bin 2 /opt//share -> /usr/local/share/ 3 /opt/etc -> /usr/local/etc/ (patching paths accordingly) For the (1) I'm not very sure Thanks Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Re: Ports Makefile rules install vs do-install
On 28/05/2021 10:38, Tatsuki Makino wrote: What happens if make restage is executed? Everything is fine, staging is OK Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr
Ports Makefile rules install vs do-install
Hi,
This is only my second port, the first has never been released. So
please be indulgent.
I'm porting rudder agent (https://www.rudder.io) to FreeBSD. My Makefile
is very simple :
PORTNAME= � rudder-agent
DISTVERSION= 6.2.7
CATEGORIES= sysutils
MASTER_SITES= https://github.com/WHATEVER
MAINTAINER= xav...@amdh.fr
COMMENT= Agent for Rudder
LICENSE= GPLv2+
SHORT_NAME= rudder
NO_BUILD= yes
NO_ARCH= yes
USE_GITHUB= yes
GH_ACCOUNT=
GH_PROJECT=
BUILD_DEPENDS+=shellcheck:devel/hs-ShellCheck
post-patch:
@${REINPLACE_CMD} \
-e s=/'bin/bash'=/'bin/sh'= \
-e s='\^\#\!'='^#\\!'= \
${WRKSRC}/qa-test
post-extract:
cd ${WRKSRC}/man && make all
do-install:
${MKDIR} ${STAGEDIR}${PREFIX}/etc/bash_completion.d
${MKDIR} ${STAGEDIR}${PREFIX}/${SHORT_NAME}/share/commands
${MKDIR} ${STAGEDIR}${PREFIX}/${SHORT_NAME}/share/lib
${INSTALL_SCRIPT} ${WRKSRC}/bin/${SHORT_NAME}
${STAGEDIR}${PREFIX}/bin
${INSTALL_SCRIPT} ${WRKSRC}/share/commands/*
${STAGEDIR}${PREFIX}/${SHORT_NAME}/share/commands
${INSTALL_SCRIPT}
${WRKSRC}/etc/bash_completion.d/${SHORT_NAME}.sh
${STAGEDIR}${PREFIX}/etc/bash_completion.d/
.for ii in package_upgrade.py timestamp
${INSTALL_SCRIPT} ${WRKSRC}/share/lib/${ii}
${STAGEDIR}${PREFIX}/${SHORT_NAME}/share/lib
.endfor
.for f in api_call.sh cfengine_parsing.sh common.sh report.sh reports.awk
${INSTALL_DATA} ${WRKSRC}/share/lib/${f}
${STAGEDIR}${PREFIX}/${SHORT_NAME}/share/lib
.endfor
${INSTALL_MAN} ${WRKSRC}/man/${SHORT_NAME}.8
${STAGEDIR}${PREFIX}/share/man/man8/
do-test: # runs the qa testsuite
@cd ${INSTALL_WRKSRC} && ${WRKSRC}/qa-test
The problem is :
* target "do-install" is not invoked if I call make install.
* calling manually "make do-install" stages the port correctly.
* if I rename this target to "install", it complains about
"work/rudder-agent-6.2.7/Makefile" missing, despite the flag NO_BUILD= yes
* the pkg-plist is conform
* however, the target "do-test" is correctly called by "make test"
I've carefully read the Porter's Handbook, and can't see where my
mistake is. I'm not a Makefile guru.
Thanks for help,
Regards,
Xavier
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer
https://www.amdh.fr
Re: Error reinstalling python 3.8.10 from ports
On 19/05/2021 19:10, Gleb Popov wrote: Just a guess - are you building with WITH_DEBUG=yes ? Actually, no Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Error reinstalling python 3.8.10 from ports
On 19/05/2021 17:54, Xavier Humbert wrote: Hi, I got trouble with python 3.8.10 at reinstall stage : ===> Registering installation for python38-3.8.10 pkg-static: Unable to access file /usr/ports/lang/python38/work/stage/usr/local/lib/python3.8/lib-dynload/_asyncio.cpython-38.so:No such file or directory pkg-static: Unable to access file /usr/ports/lang/python38/work/stage/usr/local/lib/python3.8/lib-dynload/_bisect.cpython-38.so:No such file or directory And a bunch of others (the whole lib-dynload directory actually) In fact those files are almost present : the are not named eg _asyncio.cpython-38.so , but asyncio.cpython-38*d*.so Where from comes this *d* letter, which is not in pkg-plist ? A workaround is to edit pkg-plist and add this *d* Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Error reinstalling python 3.8.10 from ports
Hi, I got trouble with python 3.8.10 at reinstall stage : ===> Registering installation for python38-3.8.10 pkg-static: Unable to access file /usr/ports/lang/python38/work/stage/usr/local/lib/python3.8/lib-dynload/_asyncio.cpython-38.so:No such file or directory pkg-static: Unable to access file /usr/ports/lang/python38/work/stage/usr/local/lib/python3.8/lib-dynload/_bisect.cpython-38.so:No such file or directory And a bunch of others (the whole lib-dynload directory actually) In fact those files are almost present : the are not named eg _asyncio.cpython-38.so , but asyncio.cpython-38*d*.so Where from comes this *d* letter, which is not in pkg-plist ? Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net-mgmt/pnp and nagios4
On 12/05/2021 08:54, Andrea Venturoli wrote: Hello. I'm using net-mgmt/nagios4 and I'd like to try adding PNP to it. Alas the port depends on net-mgmt/nagios (i.e. version 3.5.1). From general docs, I see PNP should work with Nagios 4.x. Is this expected NOT to work specifically on FreeBSD? Or can I go ahead and try modifying the DEPENDS line? From my experience with nagios, you can proceed Cheers Xavier bye & Thanks av. � -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Test
On 10/05/2021 17:43, Xavier Humbert wrote: Test Sorry, bad typing, didn't meant to send to list. Xavier -- Xavier HUMBERT AMDH.FR - Infogérance - Architecte Réseaux et Systèmes https://www.amdh.fr/ 2 rue des Patureaux 54460 AINGERAY / FRANCE Tel +33 6 71 17 29 07 Off +33 9 51 00 37 63 ___ freebsd-pf@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-pf To unsubscribe, send any mail to "freebsd-pf-unsubscr...@freebsd.org"
Test
Test -- Xavier HUMBERT AMDH.FR - Infogérance - Architecte Réseaux et Systèmes https://www.amdh.fr/ 2 rue des Patureaux 54460 AINGERAY / FRANCE Tel +33 6 71 17 29 07 Off +33 9 51 00 37 63 ___ freebsd-pf@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-pf To unsubscribe, send any mail to "freebsd-pf-unsubscr...@freebsd.org"
[UNSOLVED] Re: Strange DNS behaviour
On 09/05/2021 13:44, Xavier Humbert via bind-users wrote: On 09/05/2021 12:32, Xavier Humbert via bind-users wrote: Hi, My DNS system if perfectly working : [xavier@numenor ~]$ dig dns.google.com ; <<>> DiG 9.16.15 <<>> dns.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12276 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; COOKIE: 7b606d7c32a9990601006097b6d7f61894ea0a92dac2 (good) ;; QUESTION SECTION: ;dns.google.com. IN A ;; ANSWER SECTION: dns.google.com. 880 IN A 8.8.4.4 dns.google.com. 880 IN A 8.8.8.8 ;; Query time: 0 msec ;; SERVER: ::1#53(::1) ;; WHEN: Sun May 09 12:17:59 CEST 2021 ;; MSG SIZE rcvd: 103 On other hosts in my home, it works, too. But on one machine, it fails : [xavier@feanor ~]$ dig @numenor dns.google.com +trace ; <<>> DiG 9.16.8-Ubuntu <<>> @numenor dns.google.com +trace ; (1 server found) ;; global options: +cmd . 518400 IN NS m.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS e.root-servers.net. . 518400 IN NS d.root-servers.net. . 518400 IN NS h.root-servers.net. . 518400 IN NS f.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS a.root-servers.net. . 518400 IN RRSIG NS 8 0 518400 2021052117 2021050816 14631 . IgUiqHrRXT5hTAa5wnubyCL0T9iq+iRAQIUQlIStRYqZh6Qp5W3sZLum 6O+EkYZALJda6RJwQY8oPEgQVQymGmGyAxcZBekX5vsMm8MgovQIA+Ev SroSeV9yXDURHqt8af+25bw 6YyUQEOblPehxyUYYkF9cP8FlieAUw1Fn HMvqpQlEn2sYS4UjA+euhcS2k7jnyEdBNbXbEZVq56zHK1aHPQIp2f4/ byHaC55zPJ5rgLwMUh+8JuP47wb4NWAKIj76EUlqcidfI8hxZI5KPoNZ vmIcEtQSfRYqVxoc+BiEEgalw5afAmXjEtvJaWm4v5383uatiQ1s9AgC MPQFHw== couldn't get address for 'm.root-servers.net': not found None of the root servers can't be found. My root hint file is up to date. The network configuration on this machine : [xavier@feanor ~]$ nmcli device show enp10s0 GENERAL.DEVICE: enp10s0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 04:7D:7B:02:68:67 GENERAL.MTU: 1500 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: Wired GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/3 WIRED-PROPERTIES.CARRIER: on IP4.ADDRESS[1]: 192.168.100.25/24 IP4.GATEWAY: 192.168.100.254 IP4.ROUTE[1]: dst = 0.0.0.0/0, nh = 192.168.100.254, mt = 100 IP4.ROUTE[2]: dst = 192.168.100.0/24, nh = 0.0.0.0, mt = 100 IP4.ROUTE[3]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000 IP4.DNS[1]: 192.168.100.144 IP4.DNS[2]: 192.168.100.254 This is not an ACL problem, the whole subnet is allowed. Nmap and/or telnet shows no blocked port problem Trying on the secondary leads to the same behaviour Eventually, I am lost. Sorry, typed too quickly. Problem stands. -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 OpenPGP_0x90B78A89BCC49C10.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
[SOLVED] Re: Strange DNS behaviour
On 09/05/2021 12:32, Xavier Humbert via bind-users wrote: Hi, My DNS system if perfectly working : [xavier@numenor ~]$ dig dns.google.com ; <<>> DiG 9.16.15 <<>> dns.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12276 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; COOKIE: 7b606d7c32a9990601006097b6d7f61894ea0a92dac2 (good) ;; QUESTION SECTION: ;dns.google.com. IN A ;; ANSWER SECTION: dns.google.com. 880 IN A 8.8.4.4 dns.google.com. 880 IN A 8.8.8.8 ;; Query time: 0 msec ;; SERVER: ::1#53(::1) ;; WHEN: Sun May 09 12:17:59 CEST 2021 ;; MSG SIZE rcvd: 103 On other hosts in my home, it works, too. But on one machine, it fails : [xavier@feanor ~]$ dig @numenor dns.google.com +trace ; <<>> DiG 9.16.8-Ubuntu <<>> @numenor dns.google.com +trace ; (1 server found) ;; global options: +cmd . 518400 IN NS m.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS e.root-servers.net. . 518400 IN NS d.root-servers.net. . 518400 IN NS h.root-servers.net. . 518400 IN NS f.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS a.root-servers.net. . 518400 IN RRSIG NS 8 0 518400 2021052117 2021050816 14631 . IgUiqHrRXT5hTAa5wnubyCL0T9iq+iRAQIUQlIStRYqZh6Qp5W3sZLum 6O+EkYZALJda6RJwQY8oPEgQVQymGmGyAxcZBekX5vsMm8MgovQIA+Ev SroSeV9yXDURHqt8af+25bw 6YyUQEOblPehxyUYYkF9cP8FlieAUw1Fn HMvqpQlEn2sYS4UjA+euhcS2k7jnyEdBNbXbEZVq56zHK1aHPQIp2f4/ byHaC55zPJ5rgLwMUh+8JuP47wb4NWAKIj76EUlqcidfI8hxZI5KPoNZ vmIcEtQSfRYqVxoc+BiEEgalw5afAmXjEtvJaWm4v5383uatiQ1s9AgC MPQFHw== couldn't get address for 'm.root-servers.net': not found None of the root servers can't be found. My root hint file is up to date. The network configuration on this machine : [xavier@feanor ~]$ nmcli device show enp10s0 GENERAL.DEVICE: enp10s0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 04:7D:7B:02:68:67 GENERAL.MTU: 1500 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: Wired GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/3 WIRED-PROPERTIES.CARRIER: on IP4.ADDRESS[1]: 192.168.100.25/24 IP4.GATEWAY: 192.168.100.254 IP4.ROUTE[1]: dst = 0.0.0.0/0, nh = 192.168.100.254, mt = 100 IP4.ROUTE[2]: dst = 192.168.100.0/24, nh = 0.0.0.0, mt = 100 IP4.ROUTE[3]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000 IP4.DNS[1]: 192.168.100.144 IP4.DNS[2]: 192.168.100.254 This is not an ACL problem, the whole subnet is allowed. Nmap and/or telnet shows no blocked port problem Trying on the secondary leads to the same behaviour Eventually, I am lost. Sorry for the disturbance, it was caused by faulty remnants of a VPN connection. I fixed that in /etc/systemd/resolved.conf Cheers -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 OpenPGP_0x90B78A89BCC49C10.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Strange DNS behaviour
Hi, My DNS system if perfectly working : [xavier@numenor ~]$ dig dns.google.com ; <<>> DiG 9.16.15 <<>> dns.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12276 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; COOKIE: 7b606d7c32a9990601006097b6d7f61894ea0a92dac2 (good) ;; QUESTION SECTION: ;dns.google.com. IN A ;; ANSWER SECTION: dns.google.com. 880 IN A 8.8.4.4 dns.google.com. 880 IN A 8.8.8.8 ;; Query time: 0 msec ;; SERVER: ::1#53(::1) ;; WHEN: Sun May 09 12:17:59 CEST 2021 ;; MSG SIZE rcvd: 103 On other hosts in my home, it works, too. But on one machine, it fails : [xavier@feanor ~]$ dig @numenor dns.google.com +trace ; <<>> DiG 9.16.8-Ubuntu <<>> @numenor dns.google.com +trace ; (1 server found) ;; global options: +cmd . 518400 IN NS m.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS e.root-servers.net. . 518400 IN NS d.root-servers.net. . 518400 IN NS h.root-servers.net. . 518400 IN NS f.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS a.root-servers.net. . 518400 IN RRSIG NS 8 0 518400 2021052117 2021050816 14631 . IgUiqHrRXT5hTAa5wnubyCL0T9iq+iRAQIUQlIStRYqZh6Qp5W3sZLum 6O+EkYZALJda6RJwQY8oPEgQVQymGmGyAxcZBekX5vsMm8MgovQIA+Ev SroSeV9yXDURHqt8af+25bw 6YyUQEOblPehxyUYYkF9cP8FlieAUw1Fn HMvqpQlEn2sYS4UjA+euhcS2k7jnyEdBNbXbEZVq56zHK1aHPQIp2f4/ byHaC55zPJ5rgLwMUh+8JuP47wb4NWAKIj76EUlqcidfI8hxZI5KPoNZ vmIcEtQSfRYqVxoc+BiEEgalw5afAmXjEtvJaWm4v5383uatiQ1s9AgC MPQFHw== couldn't get address for 'm.root-servers.net': not found None of the root servers can't be found. My root hint file is up to date. The network configuration on this machine : [xavier@feanor ~]$ nmcli device show enp10s0 GENERAL.DEVICE: enp10s0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 04:7D:7B:02:68:67 GENERAL.MTU: 1500 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: Wired GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/3 WIRED-PROPERTIES.CARRIER: on IP4.ADDRESS[1]: 192.168.100.25/24 IP4.GATEWAY: 192.168.100.254 IP4.ROUTE[1]: dst = 0.0.0.0/0, nh = 192.168.100.254, mt = 100 IP4.ROUTE[2]: dst = 192.168.100.0/24, nh = 0.0.0.0, mt = 100 IP4.ROUTE[3]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000 IP4.DNS[1]: 192.168.100.144 IP4.DNS[2]: 192.168.100.254 This is not an ACL problem, the whole subnet is allowed. Nmap and/or telnet shows no blocked port problem Trying on the secondary leads to the same behaviour Eventually, I am lost. Could anyone help ? Thanks, Regards -- Xavier Humbert CRT Supervision et Exploitation de Niveau 1 Rectorat de Nancy-Metz 03 83 86 27 39 OpenPGP_0x90B78A89BCC49C10.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: gdal
On 03/05/2021 12:42, Matthieu Volat wrote: Hi, this happens indeed when you build gdal*without* the EXR option when openexr is present at build time. I guess the off option is not passed correctly to the configure script? Hi Mathieu, LuMiWa, I ran in the very same problem, with the *default* (make rmconfig) options. As you mention, enabling EXR option fixes this Cheers, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer https://www.amdh.fr ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[SOLVED ]Re: Warning: Major OS version upgrade detected
Dewayne, Yesss ! Thanks it did the job ! I reinstalled port-maintenance-tools, and now the arch column in pkg DB is correct, FraaBDS:13:* I dunno why the generated ABI in this file was wrong (line was commented out -> auto-detection) Thanks again, Cheers, Xavier On 01/02/2021 07:38, Dewayne Geraghty wrote: A while ago, due to mismatching ABI, I had to insert into: /usr/local/etc/pkg.conf ABI = "freebsd:12:x86:64"; Perhaps explicitly stating "freebsd:13:x86:64"; may help? BUT this will require maintenance. :/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Warning: Major OS version upgrade detected
[Cc'ed to mat@ apologies for the intrusion] Hi, Rainer and others, I'va made some progress in resolving this very problem : I just reinstalled a port (port-maintenance-tool, which is a no-op, since tools are already installed), then browsed the pkg DB. I saw in the column arch : FreeBSD:14:* while making with debugging flags shows me OSVERSION = 1300137 I've even manually set ABI to FreeBSD:13:amd64 in /etc/pkg/FreeBSD.conf There is something I clearly don't understand. Cheers, Xavier Am 30.01.21 um 23:02 schrieb Xavier Humbert: Hi, I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE Now, when I run any ports/pkg command - I use only ports-, I got pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended No a big deal, I thought, but : [root@numenor ~]# pkg bootstrap -f The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest, please wait... Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Installing pkg-1.16.2... pkg-static: wrong architecture: FreeBSD:13:amd64 instead of *FreeBSD:14:amd64* package pkg is already installed, forced install Extracting pkg-1.16.2: 100% [root@numenor ~]# pkg check -Bd pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended The message is still there. I never had 14-CURRENT on this system. Reinstalled ports-mgmt/pkg from source, didn't help -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Warning: Major OS version upgrade detected
Hi, I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE Now, when I run any ports/pkg command - I use only ports-, I got pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended No a big deal, I thought, but : [root@numenor ~]# pkg bootstrap -f The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest, please wait... Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Installing pkg-1.16.2... pkg-static: wrong architecture: FreeBSD:13:amd64 instead of *FreeBSD:14:amd64* package pkg is already installed, forced install Extracting pkg-1.16.2: 100% [root@numenor ~]# pkg check -Bd pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended The message is still there. I never had 14-CURRENT on this system. Reinstalled ports-mgmt/pkg from source, didn't help Any help ? Thanks, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
failed to resolve type kernel struct thread *
Hello, I cannot compile www/node (and some others) with this error dtrace: failed to compile script src/v8ustack.d: "/usr/lib/dtrace/psinfo.d", line 93: failed to resolve type kernel`struct thread * for identifier curthread: Unknown type name My kernel is compiled with CTF options : [root@numenor ports]# grep CTF /usr/src/sys/amd64/conf/XAVIER makeoptions WITH_CTF=1 # Run ctfconvert(1) for DTrace support options DDB_CTF # Kernel ELF linker loads CTF data I'm running 13-stable, an did a full buildword/buildkernel. And ctfdump /boot/kernel/kernel produces an output Is this a known problem, or did I mess something ? Thanks, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
