Review requested -- new trac plugin port
Dear all, Before hitting the commit button on this, I thought I'd check that what I'm doing here is OK. So far I've got three new trac plugin modules I'd like to port. They're all pretty similar, and I've based my work on some existing trac plugin ports (mostly www/trac-discussion). However it doesn't really feel right to me. I've created a review for the first of these -- https://reviews.freebsd.org/D4796 The others are essentially the same pattern, but they aren't anything near finished quality yet... The problem I have with this is not having some downloadable tarball to work with. Instead, I'm checking sources out of the trac-hacks SVN and rolling my own .tar.gz which I then place into MASTER_SITES=LOCAL/matthew Is this OK? Cheers, Matthew signature.asc Description: OpenPGP digital signature
portupgrade fails possibly due to py27-asn1 rename to py-pyasn1
Hi all, I updated my ports collection the other day and ran portupgrade. It fails on the devel/py-pyasn1 port with the error: ===> Installing for py27-pyasn1-0.1.9 ===> py27-pyasn1-0.1.9 depends on package: py27-setuptools27>0 - found ===> py27-pyasn1-0.1.9 depends on file: /usr/local/bin/python2.7 - found ===> Checking if py27-pyasn1 already installed ===> Registering installation for py27-pyasn1-0.1.9 as automatic Installing py27-pyasn1-0.1.9... pkg-static: py27-pyasn1-0.1.9 conflicts with py27-asn1-0.1.8,1 (installs files into the same place). Problematic file: /usr/local/lib/python2.7/site-packages/pyasn1/__init__.py *** Error code 70 Stop. I suspect it's because this port was recently renamed from devel/py27-asn1 (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204567). I can't see any message in UPDATING that's relevant. Any clues please? Thanks, Graham ___ 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: portupgrade fails possibly due to py27-asn1 rename to py-pyasn1
On 5/01/2016 10:52 PM, Graham Menhennitt wrote: > Hi all, > > I updated my ports collection the other day and ran portupgrade. It > fails on the devel/py-pyasn1 port with the error: > > ===> Installing for py27-pyasn1-0.1.9 > ===> py27-pyasn1-0.1.9 depends on package: py27-setuptools27>0 - found > ===> py27-pyasn1-0.1.9 depends on file: /usr/local/bin/python2.7 - found > ===> Checking if py27-pyasn1 already installed > ===> Registering installation for py27-pyasn1-0.1.9 as automatic > Installing py27-pyasn1-0.1.9... > pkg-static: py27-pyasn1-0.1.9 conflicts with py27-asn1-0.1.8,1 (installs > files into the same place). Problematic file: > /usr/local/lib/python2.7/site-packages/pyasn1/__init__.py > *** Error code 70 > > Stop. > > I suspect it's because this port was recently renamed from > devel/py27-asn1 (see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204567). I can't see > any message in UPDATING that's relevant. > > Any clues please? > > Thanks, > Graham Had their been an UPDATING entry, it would have said please delete py-asn, then reinstall py-pyasn. At least portmaster users would have been affected by a move like this I believe, not sure about portupgrade. I was under the impression it handled moves OK. CC'ing committer. Thanks for letting us know Graham ___ 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"
Using GitLab With Port Makefile
Hey freebsd-ports peeps, I'm writing a custom ports entry for my employer. We have an internal GitLab instance. I was wondering if it'd be possible to use USE_GITHUB with our internal GitLab, but instead of having the Ports system use GitHub to download the archive, use our GitLab instance. Is that possible? I see in ports/Mk/bsd.sites.mk that MASTER_SITE_GITHUB is appended to. But it looks like I can't override that. Let me know how best to proceed. Admittedly, I'm a newb at creating ports entries. Thanks, -- Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: PGP signature
FreeBSD Port: subversion-1.9.3_1 cyrus-sasl-saslauthd-2.1.26_3
Hello, I recently struggled with getting subversion with SASL to work with LDAP authentication on freebsd 10.2. Both subversion (1.9.3) and SASL (2.1.26) were install from ports. For the most part configuration followed the documentation, but there was one hitch. I'm not sure if this is something that should be handled as part of the subversion port or as part of the SASL port. When subversion is installed, the default rc scripts run svnserve with a user/group of svn/svn. However, when SASL-authd is installed, it uses a domain socket path of /var/run/saslauthd with ownership of cyrus/mail. This directory is not readable by the svn user. To make this work, I either had to add the svn user to the "mail" group, or relax the permisson on /var/run/saslauthd so that svnserve would be able to open the socket to the saslauthd. Perhaps the permissions to the socket were too restrictive by default. Regards, Joseph smime.p7s Description: S/MIME cryptographic signature
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 +-+ net/appkonference | 2.1 | 2.7 +-+ 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 Thanks. ___ 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"
