FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ databases/sequeler | 0.8.0 | v0.8.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
Re: Update of OpenLdap
On 8/7/21 1:24 PM, Jerry Seibert wrote: FreeBSD 11.4-RELEASE-p9 After the recent updating of "openldap", the follow error/warning message is presented whenever I attempt to access the database. Aug 7 07:13:57 scorpio slapd[82175]: OTP unavailable because can't read/write key database /etc/opiekeys: Permission denied Everything works fine so I don't understand what the problem is or how to correct it, or if it even needs correction. I have a similar problem and I think the reason is that the openldap24-sasl-client port vanished and was merged into openldap24-client. However, this made one of our ldap slaves stop working, I think this is a showstopper. A switch for this is needed, in the meantime, how do we build the client WITHOUT sasl? 20210801: AFFECTS: users of OpenLDAP AUTHOR: delp...@freebsd.org SASL is now always enabled for OpenLDAP. If you use portmaster: portmaster -o net/openldap24-client openldap-sasl-client If you use portupgrade: portupgrade -fo net/openldap24-client openldap-sasl-client If you use pkg with binary packages: pkg set -o net/openldap24-sasl-client:net/openldap24-client
Re: Update of OpenLdap
On Wed, 11 Aug 2021 10:49:49 +0200, Per olof Ljungmark stated: >On 8/7/21 1:24 PM, Jerry Seibert wrote: >> FreeBSD 11.4-RELEASE-p9 >> >> After the recent updating of "openldap", the follow error/warning >> message is presented whenever I attempt to access the database. >> >> Aug 7 07:13:57 scorpio slapd[82175]: OTP unavailable because can't >> read/write key database /etc/opiekeys: Permission denied >> >> Everything works fine so I don't understand what the problem is or >> how to correct it, or if it even needs correction. >> > >I have a similar problem and I think the reason is that the >openldap24-sasl-client port vanished and was merged into >openldap24-client. > >However, this made one of our ldap slaves stop working, I think this >is a showstopper. A switch for this is needed, in the meantime, how do >we build the client WITHOUT sasl? > >20210801: > AFFECTS: users of OpenLDAP > AUTHOR: delp...@freebsd.org > > SASL is now always enabled for OpenLDAP. > > If you use portmaster: > portmaster -o net/openldap24-client openldap-sasl-client > If you use portupgrade: > portupgrade -fo net/openldap24-client openldap-sasl-client > If you use pkg with binary packages: > pkg set -o net/openldap24-sasl-client:net/openldap24-client > I had to change the permissions on the /etc/opiekeys file to 0666 to stop the message from repeating. I don't know if that is actually a safe solution, but it works. I agree with you that the change to this port was probably not well thought out. -- Carmel pgpOF8VlXfChs.pgp Description: OpenPGP digital signature
Re: Update of OpenLdap
On 8/11/21 11:33 AM, Carmel wrote: On Wed, 11 Aug 2021 10:49:49 +0200, Per olof Ljungmark stated: On 8/7/21 1:24 PM, Jerry Seibert wrote: FreeBSD 11.4-RELEASE-p9 After the recent updating of "openldap", the follow error/warning message is presented whenever I attempt to access the database. Aug 7 07:13:57 scorpio slapd[82175]: OTP unavailable because can't read/write key database /etc/opiekeys: Permission denied Everything works fine so I don't understand what the problem is or how to correct it, or if it even needs correction. I have a similar problem and I think the reason is that the openldap24-sasl-client port vanished and was merged into openldap24-client. However, this made one of our ldap slaves stop working, I think this is a showstopper. A switch for this is needed, in the meantime, how do we build the client WITHOUT sasl? 20210801: AFFECTS: users of OpenLDAP AUTHOR: delp...@freebsd.org SASL is now always enabled for OpenLDAP. If you use portmaster: portmaster -o net/openldap24-client openldap-sasl-client If you use portupgrade: portupgrade -fo net/openldap24-client openldap-sasl-client If you use pkg with binary packages: pkg set -o net/openldap24-sasl-client:net/openldap24-client I had to change the permissions on the /etc/opiekeys file to 0666 to stop the message from repeating. I don't know if that is actually a safe solution, but it works. I agree with you that the change to this port was probably not well thought out. I already did this. We use saslauthd exclusively and now it looks like, # ldapsearch SASL/SCRAM-SHA-1 authentication started Please enter your password: ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: SASL(-13): user not found: no secret in database So I have no idea how I can convince slapd not look look in sasldb2.db. Per
Re: extracting pkg-message for FreshPorts
Van: Dan Langille Datum: woensdag, 11 augustus 2021 01:33 Aan: freebsd-ports Onderwerp: Re: extracting pkg-message for FreshPorts Dan Langille wrote on 8/9/21 9:57 PM: [snip] > 5 - needs to build > > [dan@empty:/usr/ports/x11/nvidia-driver-390] $ make -V PKGMESSAGE > /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message > > [dan@empty:/usr/ports/x11/nvidia-driver-390] $ sudo make configure > -DNO_DIALOG > ===> Skipping 'config' as NO_DIALOG is defined > ===> License NVIDIA accepted by the user > [snip] > ===> Configuring for pkgconf-1.7.4,1 > configure: loading site script /usr/ports/Templates/config.site > checking for gcc... cc > > This does a lot of building. A lot. That's not good. Some followup. The above installed 134 ports and worked: [dan@empty:/usr/ports/x11/nvidia-driver-390] $ ls -l /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message -rw-r--r-- 1 root wheel 1808 Aug 10 22:31 /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message > Is there a better way? Yes, there is. make apply-slist From IRC came that suggestion, which, oddly enough, I was originally using before heading down this rabbit hole. [root@empty /usr/ports/x11/nvidia-driver-390]# make apply-slist /bin/sh: cannot create /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message: No such file or directory *** Error code 2 Stop. make: stopped in /usr/ports/x11/nvidia-driver-390 [root@empty /usr/ports/x11/nvidia-driver-390]# Nope. That won't work. The next suggestion was: make extract apply-slist [root@empty /usr/ports/x11/nvidia-driver-390]# make extract apply-slist ===> Building/installing dialog4ports as it is required for the config dialog ===> Cleaning for dialog4ports-0.1.6 ===> License BSD2CLAUSE accepted by the user ===> dialog4ports-0.1.6 depends on file: /usr/local/sbin/pkg - found => dialog4ports-0.1.6.tar.gz doesn't seem to exist in /var/ports/distfiles/. => Attempting to fetch https://files.etoilebsd.net/dialog4ports/dialog4ports-0.1.6.tar.gz dialog4ports-0.1.6.tar.gz 10 kB 161 MBps00s boom dialog box. [root@empty /usr/ports/x11/nvidia-driver-390]# make extract apply-slist -DNO_DIALOG ===> Skipping 'config' as NO_DIALOG is defined ===> License NVIDIA accepted by the user ===> nvidia-driver-390-390.144 depends on file: /usr/local/sbin/pkg - found => NVIDIA-FreeBSD-x86_64-390.144.tar.gz doesn't seem to exist in /var/ports/distfiles/. => Attempting to fetch https://jp.download.nvidia.com/XFree86/FreeBSD-x86_64/390.144/NVIDIA-FreeBSD-x86_64-390.144.tar.gz NVIDIA-FreeBSD-x86_64-390.144.tar.gz62 MB 13 MBps05s ===> Fetching all distfiles required by nvidia-driver-390-390.144 for building ===> Extracting for nvidia-driver-390-390.144 => SHA256 Checksum OK for NVIDIA-FreeBSD-x86_64-390.144.tar.gz. [root@empty /usr/ports/x11/nvidia-driver-390]# make -V PKGMESSAGE /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message [root@empty /usr/ports/x11/nvidia-driver-390]# ls -l /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message -rw-r--r-- 1 root wheel 1808 Aug 10 23:24 /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message [root@empty /usr/ports/x11/nvidia-driver-390]# Success. This approach also works for all the previous example where PKG_MESSAGE refers to something in the /work* directory Thank you for coming to my TED talk. -- Dan Langille - d...@langille.org https://langille.org/ Hi, Thanks for the TED talk. I just learned about -DNO_DIALOG after quite some years. :-)
Re: Update of OpenLdap
On 8/11/21 12:01 PM, Per olof Ljungmark wrote: On 8/11/21 11:33 AM, Carmel wrote: On Wed, 11 Aug 2021 10:49:49 +0200, Per olof Ljungmark stated: On 8/7/21 1:24 PM, Jerry Seibert wrote: FreeBSD 11.4-RELEASE-p9 After the recent updating of "openldap", the follow error/warning message is presented whenever I attempt to access the database. Aug 7 07:13:57 scorpio slapd[82175]: OTP unavailable because can't read/write key database /etc/opiekeys: Permission denied Everything works fine so I don't understand what the problem is or how to correct it, or if it even needs correction. I have a similar problem and I think the reason is that the openldap24-sasl-client port vanished and was merged into openldap24-client. However, this made one of our ldap slaves stop working, I think this is a showstopper. A switch for this is needed, in the meantime, how do we build the client WITHOUT sasl? 20210801: AFFECTS: users of OpenLDAP AUTHOR: delp...@freebsd.org SASL is now always enabled for OpenLDAP. If you use portmaster: portmaster -o net/openldap24-client openldap-sasl-client If you use portupgrade: portupgrade -fo net/openldap24-client openldap-sasl-client If you use pkg with binary packages: pkg set -o net/openldap24-sasl-client:net/openldap24-client I had to change the permissions on the /etc/opiekeys file to 0666 to stop the message from repeating. I don't know if that is actually a safe solution, but it works. I agree with you that the change to this port was probably not well thought out. I already did this. We use saslauthd exclusively and now it looks like, # ldapsearch SASL/SCRAM-SHA-1 authentication started Please enter your password: ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: SASL(-13): user not found: no secret in database So I have no idea how I can convince slapd not look look in sasldb2.db. Sorted by reverting to 2021Q2 branch, no time to try to figure out. Does anybody know why sasl2 became a necessity? Per
Re: extracting pkg-message for FreshPorts
Dan Langille wrote on 2021/08/11 08:33: > [dan@empty:/usr/ports/x11/nvidia-driver-390] $ ls -l > /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message > -rw-r--r-- 1 root wheel 1808 Aug 10 22:31 > /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message > >> Is there a better way? > Yes, there is. make apply-slist > > From IRC came that suggestion, which, oddly enough, I was originally using > before heading down this rabbit hole. > > [root@empty /usr/ports/x11/nvidia-driver-390]# make apply-slist > /bin/sh: cannot create > /var/ports/usr/ports/x11/nvidia-driver-390/work/pkg-message: No such file or > directory > *** Error code 2 > > Stop. > make: stopped in /usr/ports/x11/nvidia-driver-390 > [root@empty /usr/ports/x11/nvidia-driver-390]# > > > Nope. That won't work. The _PORTS_DIRECTORIES directory seems to have a target that executes mkdir. I think the following is also possible... I'm just thinking :) make -C /usr/ports/x11/nvidia-driver-390 `make -C /usr/ports/x11/nvidia-driver-390 -V EXTRACT_WRKDIR` apply-slist
