MASTER_SITES= LOCAL/
Hi, I've noticed recently that a number of ports with MASTER_SITES= LOCAL/ have been marked BROKEN due to being unfetchable. Should local master sites on people.freebsd.org be defined differently? Has there been a change in policy? -- Cheers, Cy Schubert or FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ 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: Is redports.org back?
+--On 22 avril 2016 17:43:07 +0200 Fernando Apesteguía wrote: | Hi, | | I noticed that there is an apparently functional redports.org site | again. Is it functional? All I get is a "No authenticated" message | when I try to log in. It looks like there is a front-end, yes, but it's going to lack backend builders, they were repurposed months ago. -- Mathieu Arnold pgpIHx5qG04Gp.pgp Description: PGP signature
Re: Is redports.org back?
Am 22.04.2016 17:50 schrieb "Fernando Apesteguía" < fernando.apesteg...@gmail.com>: > > On Fri, Apr 22, 2016 at 5:49 PM, Kurt Jaeger wrote: > > Hi! > > > >> I noticed that there is an apparently functional redports.org site > >> again. Is it functional? > > > > Interesting find, thanks! No, it does not look yet functional. > > Damn it! I was starting to cry of happiness. I hope it's back soon :) > > > > >> All I get is a "No authenticated" message when I try to log in. We're not there yet. There is still some work to do. Code can be found on github. http://github.com/freebsd/redports ___ 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: Is redports.org back?
Fernando Apestegua wrote: > Damn it! I was starting to cry of happiness. I hope it's back soon :) As much as I loathe the semi-illiterate "language" of Twitter, texting, MSN and what have you, here's a "+1". Redports was a blessing for port maintainers and I hope it gets back into full swing soon. Fonz -- A.J. "Fonz" van Werven mailsig: Ob technicas difficultates, lux in fine cuniculum non operatur. signature.asc Description: PGP signature
Re: Is redports.org back?
On Fri, Apr 22, 2016 at 5:49 PM, Kurt Jaeger wrote: > Hi! > >> I noticed that there is an apparently functional redports.org site >> again. Is it functional? > > Interesting find, thanks! No, it does not look yet functional. Damn it! I was starting to cry of happiness. I hope it's back soon :) > >> All I get is a "No authenticated" message when I try to log in. > > -- > p...@opsec.eu+49 171 3101372 4 years to > go ! ___ 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: Is redports.org back?
Hi! > I noticed that there is an apparently functional redports.org site > again. Is it functional? Interesting find, thanks! No, it does not look yet functional. > All I get is a "No authenticated" message when I try to log in. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ 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"
Is redports.org back?
Hi, I noticed that there is an apparently functional redports.org site again. Is it functional? All I get is a "No authenticated" message when I try to log in. Cheers. ___ 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
Hello On 4/22/16 7:20 AM, Kristof Provost wrote: On 22 Apr 2016, at 13:11, Jim Ohlstein mailto:j...@ohlste.in>> 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. That was the problem. I more or less figured it out late last night when I looked at the mail logs of the front end server. My setup is like this: web <--> fontend SSL termination/load balancer/cache <--> multiple backends (not web accessible) Mailman is installed in in a jail in a backend server. That jail has a FQDN and it matches that of Mailman (lists.mydomain.com). So in ~mailman/Mailman/mm_cfg.py I had: SMTPHOST = 'lists.mydomain.com' as instructed by the port upon installation. That wound up having Mailman looking for the _real_ IP of that FQDN for the outgoing mail server, which led it back to the frontend server to which that IP is actually bound. That Postfix installation refused to relay because the IP range of that backend server was not allowed in "mynetworks" in its main.cf. Allowing that IP range on Postfix on the frontend server got outgoing mail working late last night. It was a fairly inelegant solution but it worked. Editing ~mailman/Mailman/mm_cfg.py as follows got it working in the jail: - SMTPHOST = 'lists.mydomain.com' + SMTPHOST = 'jail.ip.address' What confused me were the port's instructions and the fact that the Mailman actually resolved the FQDN and looked for that IP externally. Thanks to everyone who helped. I'm a bit embarrassed at the simplicity of the solution. -- Jim Ohlstein "Never argue with a fool, onlookers may not be able to tell the difference." - Mark Twain ___ 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
Hello, > On Apr 22, 2016, at 6:05 AM, Kristof Provost wrote: > >> 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? I built it with poudriere using the Postfix option. Jim ___ 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: failure compile libGL-11.1.2
Dear FreeBSD friends, On Tue, Apr 19, 2016 at 09:32:52AM +0200, Tijl Coosemans wrote: > On Mon, 18 Apr 2016 15:13:39 +0200 Willem Offermans > wrote: > > Dear FreeBSD friends, > > > > I have inherited an old FreeBSD beast and I'm trying to update it to 10.3. > > > > However the following error occurred during compiling libGL: > > > > ===> Building for libGL-11.1.2 > > > > [cut some messages in between] > > > > libtool: error: cannot find the library '/usr/local/lib/libXext.la' or > > unhandled argument '/usr/local/lib/libXext.la' > > > > '/usr/local/lib/libXext.la' is indeed not present. But the file is also not > > present on another FreeBSD 10.2 system. So I suppose it is not needed. Is > > there something old on the server pointing to this file? How can I proceed? > > See the 20140909 entry in /usr/ports/UPDATING. Thnx a lot, this was just needed to proceed. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Will * W.K. Offermans Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ 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"
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 +-+ sysutils/pslist | 1.3 | 1.3.1 +-+ 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"
Re: compiling ports with --sysroot= and -isystem
+--On 22 avril 2016 11:54:21 +0800 Julian Elischer
wrote:
| On 22/04/2016 11:18 AM, olli hauer wrote:
|> On 2016-04-22 04:04, Julian Elischer wrote:
|>> How can I add entries (like the above) to a port compile?
|>> I want to ADD things to CFLAGS.
|>> If I add 'CFLAGS=...' to the build (for example, of lsof) it actually
|>> replaces all the CFLAGS already there. lsof (as the example) uses
|>> configure, so I would need to feed the added stuff into configure. Is
|>> there a standard way to do this? In the environment I'm using, I'm
|>> building for a machine that is not the build machine, but an appliance.
|>> It has a small number of differences in the include file contents, so I
|>> want it to compile using a different set of includes than those in
|>> /usr/include.
|>>
|>> On the other hand I'm building a bunch of tools that do have t orun on
|>> the build machine and they need to use the regular /usr/include so I
|>> don't really want to replace them..
|>>
|>>
|>> Julian
|>>
|>> p.s. usual "please reply directly" comment applies.. I'm on this list
|>> but get it in digest form..
|>>
|> Use the '+=' notation, e.g.
|>
|> # Makefile
|> ...
|> CFLAGS+= "--sysroot="
|> ...
|
| sorry I wasn't clear..
|
| I want to add something to the make command, not edit Makefiles.
|
| I could add something to bsd.autotools.mk or some similar Makefile
| include. but really I want to do it on a case by case basis.
| there is an averall Makefile (using gmake) that effectively does:
| cd /usr/ports/$(PORT_DIR); $(BMAKE) $(ARGS) install clean
|
| (except it does a lot of them)
|
| I want to know what to add to $(ARGS) to make it use the correct include
| files. my current "work-around" is to do:
|
| mv /usr/include /usr/include.hold; ln -s $(STAGING_DIR)/usr/include
| /usr/include
| cd /usr/ports/$(PORT_DIR); $(BMAKE) $(ARGS) install clean
| rm /usr/include; mv /usr/include.hold /usr/include
|
| this is *NOT* a clean solution :-)
If you want to change things on a port by port basis, you can:
1) use poudriere to build you a jail with a patch you provide, and build
ports with poudriere testport or poudriere bulk.
2) on each port's directory, you create a Makefile.local and put your
things in it.
3) in /etc/make.conf you use some kind of construct like:
.if ${.CURDIR:M*editors/vim}
FOO=bar
.endif
--
Mathieu Arnold
pgpPHWdTeKCQo.pgp
Description: PGP signature
