Re: No update for a day on ports?
On 1 Apr 2021, at 8:22, Milan Obuch wrote: > did somebody encountered this issue? I am using svn daily to update > ports tree on some (maybe 15, exact number not important) boxes. No new > updates today. I noticed it first actually yesterday afternoon or early > evening, but I did not consider asking then. > > Is there some breakage in ports infrastructure? I see request comming > in on ports-bugs mailing list, but no update past revision 569609. > Also, I did not read anything on switching to git for ports, but I > would expect svn mirror for older (11 and 12) systems anyway as it is > done for src tree now. > https://wiki.freebsd.org/git Best regards, Kristof ___ 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: py34-dnspython
> On 22 Sep 2016, at 18:09, Ruslan Makhmatkhanov wrote: > > Kristof Provost wrote on 09/21/2016 11:54: >>> On 20 Sep 2016, at 20:15, Ruslan Makhmatkhanov wrote: >>> Kristof Provost wrote on 09/20/2016 19:40: >>>> I found I had a need for dnspython for python 3.4. The port builds >>>> only for >>>> python 2.7 at the moment. >>>> Attached is a patch to introduce py34-dnspython. >>>> >>>> Regards, >>>> Kristof >>> >>> Feel free to commit it. Actually people asked about this in past, but >>> I wasn't able to do that for some reason. >>> >>> I'd only change port directory name to dns/py3-dnspython to not tie it >>> to particular python version, but to use default python3 version >>> (which is 3.4 at the moment). PYTHON_VERSION is better to replace with >>> USES too. >>> >>> Please see audio/py3-mutagen/Makefile for example. >>> >> Thanks for the suggestions. I’ve updated the patch. >> I don’t have a ports commit bit, but I’m in Belgrade for EuroBSD, so I’m >> sure I can find someone ;) >> >> Regards, >> Kristof > > Committed in r422632. Thank you! Thanks! Kristof ___ 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: py34-dnspython
On 20 Sep 2016, at 20:15, Ruslan Makhmatkhanov wrote:
Kristof Provost wrote on 09/20/2016 19:40:
I found I had a need for dnspython for python 3.4. The port builds
only for
python 2.7 at the moment.
Attached is a patch to introduce py34-dnspython.
Regards,
Kristof
Feel free to commit it. Actually people asked about this in past, but
I wasn't able to do that for some reason.
I'd only change port directory name to dns/py3-dnspython to not tie it
to particular python version, but to use default python3 version
(which is 3.4 at the moment). PYTHON_VERSION is better to replace with
USES too.
Please see audio/py3-mutagen/Makefile for example.
Thanks for the suggestions. I’ve updated the patch.
I don’t have a ports commit bit, but I’m in Belgrade for EuroBSD, so
I’m sure I can find someone ;)
Regards,
Kristofdiff --git a/dns/py-dnspython/Makefile b/dns/py-dnspython/Makefile
index f475c77..ed3d16d 100644
--- a/dns/py-dnspython/Makefile
+++ b/dns/py-dnspython/Makefile
@@ -11,7 +11,7 @@ MAINTAINER= r...@freebsd.org
COMMENT= DNS toolkit for Python
NO_ARCH= yes
-USES= python:2.7+
+USES?= python:2.7+
USE_PYTHON=autoplist distutils
OPTIONS_DEFINE=DOCS EXAMPLES PYCRYPTO
diff --git a/dns/py3-dnspython/Makefile b/dns/py3-dnspython/Makefile
new file mode 100644
index 000..1e618ea
--- /dev/null
+++ b/dns/py3-dnspython/Makefile
@@ -0,0 +1,7 @@
+# $FreeBSD$
+
+MASTERDIR= ${.CURDIR}/../py-dnspython
+
+USES= python:3.3+
+
+.include "${MASTERDIR}/Makefile"
___
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"
py34-dnspython
Hi,
I found I had a need for dnspython for python 3.4. The port builds only for
python 2.7 at the moment.
Attached is a patch to introduce py34-dnspython.
Regards,
Kristofdiff --git a/dns/py34-dnspython/Makefile b/dns/py34-dnspython/Makefile
new file mode 100644
index 000..19af934
--- /dev/null
+++ b/dns/py34-dnspython/Makefile
@@ -0,0 +1,7 @@
+# $FreeBSD$
+
+MASTERDIR= ${.CURDIR}/../py-dnspython
+
+PYTHON_VERSION=python3.4
+
+.include "${MASTERDIR}/Makefile"
___
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: Mailman in a jail
> On 22 Apr 2016, at 13:11, Jim Ohlstein wrote: >> The main gotcha with Mailman is that it defaults to supporting Sendmail. >> It actually needs to be rebuilt to work with postfix. That's the first >> thing to look at. Did you install from ports or with pkg? > > I built it with poudriere using the Postfix option. > Okay, that’s good. I did exactly the same ;) It’s not quite clear to me if your problem is getting Postfix to deliver to mailman, or mailman to postfix. In my setup the list is on a separate (virtual) domain, and uses an aliases file (alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases). That file is maintained by mailman and will have things like 'test: "|/usr/local/mailman/mail/mailman post test”’ in it. Return delivery (i.e. mailman sending mail) is done using the DirectSMTP module. My ‘SMTPHOST’ is set to the hostname of the jail (so to an IP address the postfix is listening on). If you’ve still got that set to the default of ‘localhost’ that might also explain your problems. It might also be worth playing with telnet inside the jail and confirming that you can talk to your postfix that way. Regards, Kristof ___ 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: Mailman in a jail
On 2016-04-21 11:21:36 (-0400), Jim Ohlstein wrote: > I'm trying to get Mailman working in a 10.3 amd64 jail. Everything > works, except Mailman doesn't talk to Postfix. Incoming mail works and > posts to the list's archives but no outgoing email is sent. I asked in > the Mailman list and they seem to think it's related to running in a jail. > > If anyone's gotten this running in a jail I'd appreciate some input. I'm > not married to Postfix - willing to use a different MTA. > I'm currently running a Postfix + Mailman instance on 10.3. It does indeed work. The main gotcha with Mailman is that it defaults to supporting Sendmail. It actually needs to be rebuilt to work with postfix. That's the first thing to look at. Did you install from ports or with pkg? Regards, Kristof ___ 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/owncloud-csync,deskutils/mirall owncloudcmd segfault
On 2014-02-25 19:27:29 (+0100), Kristof Provost wrote: > So, now I'm not sure what the right fix is here. It's quite possible > that version 1.5.1 fixes the problem and it's almost certain that the > fix will be different. > I've managed to build mirall-1.5.1 and the problem is fixed there. Regards, Kristof ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
net/owncloud-csync,deskutils/mirall owncloudcmd segfault
Hi, I see a segfault when trying to sync a directory using the owncloudcmd CLI client. The command line is pretty straightforward: owncloudcmd Documents ownclouds:///owncloud/remote.php/webdav/ The backtrace: #0 0x000809f79da4 in SSL_CTX_set_client_cert_cb () from /usr/lib/libssl.so.7 #1 0x00080521eab8 in ne_ssl_context_create (mode=) at ne_openssl.c:575 #2 0x00080520f85e in ne_session_create (scheme=0x7fffccc2 "https", hostname=0x80c470a60 "owncloud.codepro.be", port=) at ne_session.c:176 #3 0x000800b6cd92 in dav_connect ( base_url=0x80c46f480 "ownclouds://owncloud.codepro.be:443/owncloud/remote.php/webdav") at /var/ports/basejail/usr/ports/net/owncloud-csync/work/ocsync-0.91.4/src/csync_owncloud.c:509 #4 0x000800b6aa55 in owncloud_opendir ( uri=0x80c46f480 "ownclouds://owncloud.codepro.be:443/owncloud/remote.php/webdav") at /var/ports/basejail/usr/ports/net/owncloud-csync/work/ocsync-0.91.4/src/csync_owncloud.c:982 #5 0x000800b687c8 in csync_vio_opendir (ctx=0x80c478500, name=0x80c46f480 "ownclouds://owncloud.codepro.be:443/owncloud/remote.php/webdav") at /var/ports/basejail/usr/ports/net/owncloud-csync/work/ocsync-0.91.4/src/vio/csync_vio.c:370 #6 0x000800b5eb04 in csync_ftw (ctx=0x80c478500, uri=0x80c46f480 "ownclouds://owncloud.codepro.be:443/owncloud/remote.php/webdav", fn=0x800b5d980 , depth=50) at /var/ports/basejail/usr/ports/net/owncloud-csync/work/ocsync-0.91.4/src/csync_update.c:449 #7 0x000800b5702b in csync_update (ctx=0x80c478500) at /var/ports/basejail/usr/ports/net/owncloud-csync/work/ocsync-0.91.4/src/csync.c:431 #8 0x0008008a1ec3 in Mirall::CSyncThread::startSync (this=0x7fffd4e0) at /var/ports/basejail/usr/ports/deskutils/mirall/work/mirall-1.5.0/src/mirall/csyncthread.cpp:505 #9 0x004044f5 in main (argc=3, argv=0x7fffd768) at /var/ports/basejail/usr/ports/deskutils/mirall/work/mirall-1.5.0/src/owncloudcmd/owncloudcmd.cpp:140 Looking into this, the crash occurs inside neon, specifically inside ne_ssl_context_create(). It crashes because the call to SSL_CTX_new(SSLv23_client_method()); returns NULL. OpenSSL gives me the following error: error:140A90A1:lib(20):func(169):reason(161) This means that we haven't called SSL_library_init(). Neon does this in ne_ssl_init(), which itself is called by ne_sock_init(). The ne_sock_init() call isn't done by owncloud-csync. The code is present in the dav_connect() function (src/csync_owncloud.c) but it's surrounded by '#if 0'. Removing the '#if 0' fixes my crash. I've noticed that there's a new version of deskutils/mirall (1.5.1) with the following changelog entry: "Imported the ocsync library into miralls repository." So, now I'm not sure what the right fix is here. It's quite possible that version 1.5.1 fixes the problem and it's almost certain that the fix will be different. Regards, Kristof ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
