Re: MariaDB Options for Port.,MariaDB Options for Port.
Hello Yasuhiro,
On 3/10/21 6:30 PM, Yasuhiro Kimura wrote:
> From: "Janky Jay, III"
> Subject: MariaDB Options for Port.,MariaDB Options for Port.
> Date: Wed, 10 Mar 2021 17:59:35 -0700
>
>> I've been trying to add a MariaDB option to a port I maintain but
>> everything I have tried has failed. There's is obviously something I'm
>> not understanding about the available options so I'm hoping someone can
>> point me the right direction.
>>
>> The port currently has a MySQL option which works fine but I'd like
>> to add MariaDB in there as an alternative:
>>
>> .if ${PORT_OPTIONS:MMYSQLSERVER}
>> USES+= mysql:server
>> .endif
>>
>> Based on the information I found in the Porter's Handbook [1], it
>> appears there are options for MariaDB but they come from variants of
>> USES=mysql (such as "mysql:105m", for MariaDB.) However, setting this to
>> the version isn't working. Plus, I don't want to specify a required
>> version since there isn't one (I'd like users to be able to use whatever
>> version they prefer.) It also appears I cannot use multiple USES= lines
>> because aside from the version arg, it would just use those settings for
>> MySQL and ignore MariaDB like it's already doing.
>>
>> Below is the line I last tested without any luck. Again, I don't
>> want to specify a version, though. I'd like it do the same thing that
>> USES+=mysql does where it will install the default version if MariaDB
>> doesn't exist but if it does, it'll find the correct libs and move
>> forward with the dependency:
>>
>> .if ${PORT_OPTIONS:MMARIADBSERVER}
>> USES+= mysql:105m
>> .endif
>>
>> Can someone please point me to more informative documentation or
>> maybe even provide an example port that is already doing this? I've
>> searched the ports tree but failed to find anything helpful.
>>
>> [1] - https://docs.freebsd.org/en/books/porters-handbook/#uses-mysql
>>
>> Regards,
>> Janky Jay, III
>>
> Your port works fine with both MySQL and MariaDB. Right? If so you
> should add `USES=mysql` without version arguments in the Makefile of
> your port. Then user can specify which version of MySQL or MariaDB to
> be used. For example, if he wants to use MariaDB 10.5 then he should
> add following line in make.conf
>
> --
> DEFAULT_VERSIONS+=10.5m
> --
This makes much more sense. Thank you!
Regards,
Janky Jay, III
OpenPGP_signature
Description: OpenPGP digital signature
MariaDB Options for Port.
Hello Everyone,
I've been trying to add a MariaDB option to a port I maintain but
everything I have tried has failed. There's is obviously something I'm
not understanding about the available options so I'm hoping someone can
point me the right direction.
The port currently has a MySQL option which works fine but I'd like
to add MariaDB in there as an alternative:
.if ${PORT_OPTIONS:MMYSQLSERVER}
USES+= mysql:server
.endif
Based on the information I found in the Porter's Handbook [1], it
appears there are options for MariaDB but they come from variants of
USES=mysql (such as "mysql:105m", for MariaDB.) However, setting this to
the version isn't working. Plus, I don't want to specify a required
version since there isn't one (I'd like users to be able to use whatever
version they prefer.) It also appears I cannot use multiple USES= lines
because aside from the version arg, it would just use those settings for
MySQL and ignore MariaDB like it's already doing.
Below is the line I last tested without any luck. Again, I don't
want to specify a version, though. I'd like it do the same thing that
USES+=mysql does where it will install the default version if MariaDB
doesn't exist but if it does, it'll find the correct libs and move
forward with the dependency:
.if ${PORT_OPTIONS:MMARIADBSERVER}
USES+= mysql:105m
.endif
Can someone please point me to more informative documentation or
maybe even provide an example port that is already doing this? I've
searched the ports tree but failed to find anything helpful.
[1] - https://docs.freebsd.org/en/books/porters-handbook/#uses-mysql
Regards,
Janky Jay, III
OpenPGP_signature
Description: OpenPGP digital signature
Re: Mailman 3 port
On 2/16/21 1:52 AM, Julien Cigar wrote: > On Tue, Feb 16, 2021 at 09:16:11AM +0100, Kurt Jaeger wrote: >> Hi! >> >>> Is anyone working on a mailman 3 port? >>> >>> (I'm guessing it would be several ports, actually, as mailman 3 is >>> several different moving parts). >> There already is one. Can you have a look at it and report if >> there's any issue with it ? > also, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250362 > > I was testing the mail/mailman3 port for quite a while after Python2 was EOL'd and it was an absolute disaster (work still in progress and certainly not knocking it. It's a lot of work!) I haven't tested in a couple of months, though, but I have been following the Bugzilla thread and things are looking much more promising (thanks to all involved!) I look forward to testing more in the future once I can completely rely on ports/pkg for the installation of all software. I'm not going to use "pip" to install anything on a production FBSD server as I fear keeping the software up-to-date will be sketchy at best. Regards, Janky Jay, III OpenPGP_signature Description: OpenPGP digital signature
Re: Gracefully killing and restarting a port build....
In the future, if you can, try using "screen" or "tmux" to run these large builds in so you don't take the risk of losing the terminal/console. Or, maybe I'm completely off-base as to how it was lost to begin with. On 7/8/20 9:30 AM, bob prohaska wrote: > On Wed, Jul 08, 2020 at 10:44:03AM +0200, Ronald Klop wrote: >> >> Kill the leaf nodes of the process tree. So kill the c++ processes. Or type >> ctrl-c if you have control of the terminal. > In this case I'd lost control of the controlling terminal and didn't > know how to recover it. After kill -9 of the initial make process > I left the system standing overnight, to see if killing the original make > process would eventually propagate down to the leaf nodes. It didn't. > > Then I used killall c++, and again, it killed the named processes, but other > things, > notably pkg, kept running. After waiting a few minutes they were killall-ed. > A notation from ninja eventually showed up in the logfile saying "interrupted > by user", so maybe ninja was the place to start shutting things down. > >> If you are running the compile in a jail (like poudriere) you might use >> "killall -j c++" or something similar. > No room for a jail on a Pi, alas >> Pkill can be usable also. > Thank you, I didn't know about it. >> BTW: How graceful a restart works is outside of the scope of the ports >> framework and depends a lot on the structure of the chromium build process >> itself. >> > Understood. This is the first time I've ever needed to kill a port build. > Usually they die prematurely of natural causes! > > Thanks for your help > > bob prohaska > > ___ > 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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xpdf 4.02,1 core dumps
Hello Pete, On 5/6/20 3:51 PM, Pete Wright wrote: > Hello, > I am noticing this error with xpdf recently: > > $ xpdf > qt.qpa.xcb: could not connect to display > qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even > though it was found. > This application failed to start because no Qt platform plugin could > be initialized. Reinstalling the application may fix this problem. > > Available platform plugins are: bsdfb, minimal, offscreen, vnc, xcb. > > Abort trap (core dumped) > > I've updated to the latest pkg's and tried to reinstall xpdf but that > did not help. it looks like xcb-util depends on lots of other > packages, but it seems like xpdf is the only thing being effected. > Anyone else seeing this? I run xpdf pretty much daily and am not seeing this problem. I'm currently running the same version (installed via "pkg", not ports) and here is what I see xpdf depending on: xpdf-4.02,1: qt5-widgets-5.14.2 qt5-gui-5.14.2 qt5-printsupport-5.14.2 gsfonts-8.11_8 freetype2-2.10.1 cups-2.2.13 qt5-network-5.14.2 qt5-svg-5.14.2 png-1.6.37 qt5-core-5.14.2_2 qt5-concurrent-5.14.2 desktop-file-utils-0.24 I don't see any mention of "xcb-util". Granted, I'm also running xpdf in a very minimal xfce4 environment so maybe there are other underlying issues? Regards, Janky Jay, III ___ 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: Pkg repository is broken...
On 3/6/20 7:41 PM, Marcin Cieslak wrote: > On Sat, 7 Mar 2020, Janky Jay, III wrote: > >> Still broken for me as well. I just figured I'd look into it when I >> got a chance. Also using FBSD 12.1 RELEASE. > > Maybe it depends on the mirror being used? Perhaps. I'm not really sure what's going on. But it's happening with multiple systems and I haven't changed anything from the defaults. Then again, it's also still using the /etc/pkg/FreeBSD.conf file (I guess) because there is no /usr/local/etc/pkg/ directory. Maybe I just need to update some other stuff. ___ 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: Pkg repository is broken...
Still broken for me as well. I just figured I'd look into it when I got a chance. Also using FBSD 12.1 RELEASE. Regards, Janky Jay, III On March 7, 2020 12:38:55 AM UTC, Greg 'groggy' Lehey wrote: >On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: >> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: >>> >>> Any workarounds in the meantime? This must affect a lot of people, >>> including those who use 12-: >>> >>> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of >FreeBSD:12:amd64 >>> pkg: repository FreeBSD contains packages with wrong ABI: >FreeBSD:12.0:amd64 >> >> Still broken for me on 12.1. > >Strange. Mine cleared up automatically the following day. > >It's also strange how few replies I have received. Two private >messages (why?), yours, and that was it. You'd think that people >would be screaming. > >Greg >-- >Sent from my desktop computer. >Finger g...@freebsd.org for PGP public key. >See complete headers for address and phone numbers. >This message is digitally signed. If your Microsoft mail program >reports problems, please read http://lemis.com/broken-MUA ___ 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: Checking you the maintainer of a port?
Hello, On 11/27/19 2:03 PM, @lbutlr wrote: > I thought that the maintainer of a port was listed somewhere in the files at > user/ports//portbase/ but evidently not. What is the easiest way to > find out, sitting in console on a server without a GUI, to find out who the > maintainer is? (On my desktop I can just google and launch a browser, but > that is not possible on most of the servers which do not have web clients > installed. > > (Right now I am looking for the maintainer of roundcube, but this is a > general question.) > Please see the "MAINTAINER=" line in the port's "Makefile". Regards, Janky Jay, III ___ 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/xrdp: Issue(s) with Channels/Clipboard.
Hi @lbutlr, On 6/6/19 12:22 PM, @lbutlr wrote: > On Jun 6, 2019, at 8:15 AM, Janky Jay, III wrote: >> I had to do a "portsnap fetch extract" and install audio/lame via ports >> to get this to work. Now I have a full ports environment for just one >> dependency. It's a small VM that is only used for certain things so I >> try to use space sparingly. This makes it somewhat of an issue. > > You do not have to install the entire ports tree to install a package from > ports. > > # svnlite checkout https://svn.freebsd.org/ports/head/audio/lame > I understand this. In this case, audio/lame only had one dependency (cmake) which I could install using "pkg" first. However, if it has multiple dependencies that require non-default options, you would certainly need more than one port checked out. Hunting that down can be kind of a pain so I just tossed the whole tree in there. >> The real issue, though, is that this was installed using "pkg" and does >> not work correctly due to audio/lame being a dependency that does not >> have a package. Hence the reason the maintainer will be removing >> audio/lame as a dependency. > > Yep, that does seem like an issue. > Yeah.. :( ___ 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/xrdp: Issue(s) with Channels/Clipboard.
It's only an issue if one is not using ports and only using pkg (which is the case here). So, using pkg to install xrdp-devel is successful but the chansrv portion of it does not work and causes RDP sessions to hang for a while before connecting as well as the "clipboard" portion to not work. I had to do a "portsnap fetch extract" and install audio/lame via ports to get this to work. Now I have a full ports environment for just one dependency. It's a small VM that is only used for certain things so I try to use space sparingly. This makes it somewhat of an issue. The real issue, though, is that this was installed using "pkg" and does not work correctly due to audio/lame being a dependency that does not have a package. Hence the reason the maintainer will be removing audio/lame as a dependency. On 6/6/19 5:06 AM, @lbutlr wrote: > On Jun 5, 2019, at 7:56 AM, Janky Jay, III wrote: >> So, this needed to be built from ports. I >> would imagine that these are important to people using sound (I am not) >> so some audio dependencies should remain. However, I'm not sure it >> should be "audio/lame" if there is not a package available for it. > > Why is it an issue that lame must be built from ports? > > LOTS of things must be built from ports. > > > ___ 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/xrdp: Issue(s) with Channels/Clipboard.
I think I may have found an/the issue here. Comparing two systems (one that works and one that does not), I noticed that "/usr/local/sbin/xrdp-chansrv" was not even running on system that wasn't working. So, I manually ran it to find it was missing some libraries which I checked with "ldd": #~ ldd /usr/local/sbin/xrdp-chansrv /usr/local/sbin/xrdp-chansrv: libcommon.so.0 => /usr/local/lib/xrdp/libcommon.so.0 (0x800267000) libSM.so.6 => /usr/local/lib/libSM.so.6 (0x80028) libICE.so.6 => /usr/local/lib/libICE.so.6 (0x80028a000) libXfixes.so.3 => /usr/local/lib/libXfixes.so.3 (0x8002a7000) libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x8002af000) libX11.so.6 => /usr/local/lib/libX11.so.6 (0x8002bc000) libfdk-aac.so.2 => not found (0) libopus.so.0 => /usr/local/lib/libopus.so.0 (0x8003fd000) libmp3lame.so.0 => not found (0) libthr.so.3 => /lib/libthr.so.3 (0x80046f000) libcrypto.so.111 => /lib/libcrypto.so.111 (0x80049a000) libssl.so.111 => /usr/lib/libssl.so.111 (0x800787000) libc.so.7 => /lib/libc.so.7 (0x80081c000) libXext.so.6 => /usr/local/lib/libXext.so.6 (0x800c0f000) libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x800c23000) libxcb.so.1 => /usr/local/lib/libxcb.so.1 (0x800c2f000) libm.so.5 => /lib/libm.so.5 (0x800c58000) libXau.so.6 => /usr/local/lib/libXau.so.6 (0x800c8a000) libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x800c8f000) Here, I noticed that both "libfdk-aac" and "libmp3lame" are missing which is keeping xrdp-chansrv from starting. I was able to install "fdk-aac-2.0.0" via "pkg install" without any issues but installing "audio/lame" does not appear to be an option via "pkg". Apparently, there is a licensing issue. So, this needed to be built from ports. I would imagine that these are important to people using sound (I am not) so some audio dependencies should remain. However, I'm not sure it should be "audio/lame" if there is not a package available for it. Perhaps finding an alternative or removing it as a dependency from the xrdp-devel package? Not sure. Anyhow, getting these two libs installed fixed the chansrv timeout issue for me. So, hopefully that can help troubleshoot the package install of xrdp-devel (I haven't tried the port but I'd imagine it probably works fine). Regards, Janky Jay, III On 5/8/19 4:00 PM, Janky Jay, III wrote: > Hello Koichiro, > > Is there any update to this? I've since upgraded both systems to > FBSD 12.0-RELEASE-p3 and there have also been (I think) two (2) xrdp > port/pkg updates as well but the problem still remains the same. > Connections to chansrv work 100% of the time on one system and 0% of the > time on the other. > > Also, can you please provide a link to the GH post/report that you > created? I'd like to take a look and follow that as well if I can. > Thanks again! > > Regards, > Janky Jay, III > > On 2019-02-17 12:23, Janky Jay, III wrote: >> Hello Meta, >> >> On 2/16/19 6:37 PM, Koichiro Iwao wrote: >>> On Fri, Feb 15, 2019 at 11:31:36AM -0700, Janky Jay, III wrote: >>>>This also causes the connection to take 16 seconds to open XFCE4 once >>>> it finally gives up on channels. I see 4 errors so I'm guessing there's >>>> a 4 second timeout between attempts. Something similar to the >>>> issue/recommendation reported at >>>> https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the >>>> recommended disallowing of channels to see if it would connect faster >>>> but it does nothing. Still attempts the connections to "chansrv" and >>>> takes 16 seconds. >>> I don't think that is recommended in the upstream issue. Just he reporter >>> tried as workaround. Who recommended? As commented in the ticket, disabling >>> all channels don't stop connecting to chansrv. That's why *not to >>> connect when all channels disabled* feature is suggedted. >>> >> I should have worded that differently. I suppose "recommended" was >> incorrect. It was just a thought to see whether or not >> disable/re-enabling might give me more insight into what was happening >> via the logs (I tried adding the DEBUG log line to sesman.ini as well >> but there was no relevant information). >> >>> I know some people have the same issue and already recoeded to upstream >>> GH issue. Hang tight. If I need to know more detail of reproduction, >>> I might ask you help. >>> >>> I also reproduce the issue but not 100%. >>> >> Sounds good! I can reproduce 100% of the time on one system right >> now so if there is anything I can do to help, I will certainly do that. >> Thank you! >> >> Regards, >> Janky Jay, III >> ___ 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/xrdp: Issue(s) with Channels/Clipboard.
Hello Koichiro, Is there any update to this? I've since upgraded both systems to FBSD 12.0-RELEASE-p3 and there have also been (I think) two (2) xrdp port/pkg updates as well but the problem still remains the same. Connections to chansrv work 100% of the time on one system and 0% of the time on the other. Also, can you please provide a link to the GH post/report that you created? I'd like to take a look and follow that as well if I can. Thanks again! Regards, Janky Jay, III On 2019-02-17 12:23, Janky Jay, III wrote: > Hello Meta, > > On 2/16/19 6:37 PM, Koichiro Iwao wrote: >> On Fri, Feb 15, 2019 at 11:31:36AM -0700, Janky Jay, III wrote: >>> This also causes the connection to take 16 seconds to open XFCE4 once >>> it finally gives up on channels. I see 4 errors so I'm guessing there's >>> a 4 second timeout between attempts. Something similar to the >>> issue/recommendation reported at >>> https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the >>> recommended disallowing of channels to see if it would connect faster >>> but it does nothing. Still attempts the connections to "chansrv" and >>> takes 16 seconds. >> I don't think that is recommended in the upstream issue. Just he reporter >> tried as workaround. Who recommended? As commented in the ticket, disabling >> all channels don't stop connecting to chansrv. That's why *not to >> connect when all channels disabled* feature is suggedted. >> > I should have worded that differently. I suppose "recommended" was > incorrect. It was just a thought to see whether or not > disable/re-enabling might give me more insight into what was happening > via the logs (I tried adding the DEBUG log line to sesman.ini as well > but there was no relevant information). > >> I know some people have the same issue and already recoeded to upstream >> GH issue. Hang tight. If I need to know more detail of reproduction, >> I might ask you help. >> >> I also reproduce the issue but not 100%. >> > Sounds good! I can reproduce 100% of the time on one system right > now so if there is anything I can do to help, I will certainly do that. > Thank you! > > Regards, > Janky Jay, III > > ___ 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/xrdp: Issue(s) with Channels/Clipboard.
Hello Meta, On 2/16/19 6:37 PM, Koichiro Iwao wrote: > On Fri, Feb 15, 2019 at 11:31:36AM -0700, Janky Jay, III wrote: >> This also causes the connection to take 16 seconds to open XFCE4 once >> it finally gives up on channels. I see 4 errors so I'm guessing there's >> a 4 second timeout between attempts. Something similar to the >> issue/recommendation reported at >> https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the >> recommended disallowing of channels to see if it would connect faster >> but it does nothing. Still attempts the connections to "chansrv" and >> takes 16 seconds. > I don't think that is recommended in the upstream issue. Just he reporter > tried as workaround. Who recommended? As commented in the ticket, disabling > all channels don't stop connecting to chansrv. That's why *not to > connect when all channels disabled* feature is suggedted. > I should have worded that differently. I suppose "recommended" was incorrect. It was just a thought to see whether or not disable/re-enabling might give me more insight into what was happening via the logs (I tried adding the DEBUG log line to sesman.ini as well but there was no relevant information). > I know some people have the same issue and already recoeded to upstream > GH issue. Hang tight. If I need to know more detail of reproduction, > I might ask you help. > > I also reproduce the issue but not 100%. > Sounds good! I can reproduce 100% of the time on one system right now so if there is anything I can do to help, I will certainly do that. Thank you! Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
net/xrdp: Issue(s) with Channels/Clipboard.
Hi All, So, I noticed this quite a while back but it didn't bother me too much. However, my curiosity has gotten the best of me and now I want to find out what's going on. I'm running net/xrdp (version 0.9.9,1 installed via pkg) on two different, headless FBSD 11.2-Rp9 systems and they're behaving differently with 100% identical configurations. On both, the xrdp and sesman services start without any errors at all. However, on one of the systems upon authentication during login, I get the below errors in the xrdp.log file: [DEBUG] xrdp_wm_log_msg: connected ok [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [DEBUG] Closed socket 20 (AF_UNIX) [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [DEBUG] Closed socket 20 (AF_UNIX) [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [DEBUG] Closed socket 20 (AF_UNIX) [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan This is very similar to the issue reported at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231210 but the issue was closed with "works as expected". Apparently, that's not the case on all systems? This also causes the connection to take 16 seconds to open XFCE4 once it finally gives up on channels. I see 4 errors so I'm guessing there's a 4 second timeout between attempts. Something similar to the issue/recommendation reported at https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the recommended disallowing of channels to see if it would connect faster but it does nothing. Still attempts the connections to "chansrv" and takes 16 seconds. What is even more strange is that for about 3-4 months or so, this system began connecting to channels like normal and and worked liked the other. Then, suddenly, stopped connecting one day (I'm not sure when it stopped but it would've been in the last 2 months or so?). On the system that works without any issues, I see the "chansrv" connection successful after authentication and login is immediate: [DEBUG] xrdp_wm_log_msg: connected ok [DEBUG] xrdp_mm_connect_chansrv: chansrv connect successful All software is up-to-date on both systems and, as mentioned before, configuration files are absolutely identical. So, I'm curious as to why one is able to connect to channels while the other is not? If anyone has any ideas or wants additional info/logs/etc... I'm all ears and will be more than happy to provide any additional details. Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: which port installed what other port
Hello, On 1/21/19 9:26 AM, tech-lists wrote: > Hi, > > Is there a command (or a port) I can use which, when fed an installed > port name, can tell me what installed it? > > I don't mean libraries. I mean the actual port name. You can use "pkg info -d portname" to see what ports "portname" depends on (IE: What dependencies "portname" installed). You can also use "pkg info -r portname" to see the what the portname is a dependency of (what installed this port). Does that help at all? Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: Maia Mailgaurd / PHP 7 support
Hello Miroslav, On 12/29/18 6:16 PM, Miroslav Lachman wrote: > Janketh Jay wrote on 2018/12/30 01:03: >> Hi All, >> >> On 03/12/2018 2:17 pm, Reko Turja via freebsd-ports wrote: >>> Hello Janky Jay! >>> >>> -Original Message- Sent: Monday, December 3, 2018 4:17 PM >>> Subject: Re: Maia Mailgaurd >>> >>>> Okay. No sweat. I'll work on getting a port patch going as that seems >>>> it would be the easiest way to push this out. I'll provide a >>>> download as >>>> soon as I have something available for testing. >>> >>> Sounds good, thank you for your work on ports! >>> >>> -Reko >>> >> >> So, after a bit of testing (and not being able to update the >> port for PHP7 due to Smarty issues), below is a simple patch that >> will keep the current port version of Maia (1.0.4_3) working with >> PHP7 (testing with PHP 7.2). Please let me know if this does not work >> or if there is anything else that needs to be added or changed. >> Hopefully, I'll get the Smarty issue(s) sorted out soon and have a >> new port submitted. > > [...] > >> Also, if you're interested in seeing/testing the new port >> (from the latest Github commit for technion's maia_mailguard), you >> can download the patch from the link below [1] and let me know if >> it's successful for you. Everything seems to work except for the >> WebUI due to a fatal call to Smarty which I cannot figure out (I'm >> not a PHP developer). However, once that is sorted, I should be ready >> to submit the new port so Maia can be updated to the latest version. > > I forgot about this in my previous message - I guess there is an old > version of Smarty not supporting PHP 7. It would be probably better to > replace it with newer version of Smarty with PHP 7 support but there > can be some syntax changes in Smarty config / initialisation. I > remember something about it about a year ago when I was upgrading one > of our own (very old) project to newer Smarty templates. There are > some differences between Smarty 2 and Smarty 3. But as I read now on > their website, the latest Smarty 2 version 2.6.31 supports PHP 7.2 so > it should be painless to replace old noncompatible version with this one. Again, thank you for the information. I remember quite a while back I tried using Smarty3 as opposed to Smarty2 but it caused nothing but issues so I rolled back. I can go ahead and give this another shot now (especially as Smarty2 and Smarty3 can be installed in parallel) and see what I get. Another thanks! Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: Maia Mailgaurd
Hello Miroslav,
On 12/29/18 6:03 PM, Miroslav Lachman wrote:
> Janketh Jay wrote on 2018/12/30 01:03:
>
> [...]
>
>> diff -Naur maia.orig/cache.php maia/cache.php
>> --- maia.orig/cache.php 2015-02-15 15:19:45.0 -0700
>> +++ maia/cache.php 2018-10-14 20:25:30.27896 -0600
>> @@ -554,7 +554,7 @@
>> $rectmp = "";
>> foreach ($to_list as $recipient) {
>> if (isset($personal_addresses[$recipient])
>> || $domain_default) {
>> - $rectmp[] = $recipient;
>> + $rectmp = $recipient;
>> }
>> }
>> $rows[$count]['recipient_email'] = $rectmp;
>>
>>
>> Essentially, you just need to remove the "[]" from "rectmp" on
>> line 558 in your /usr/local/www/maia/cache.php file.
>
> I don't use Maia Mailguard and I didn't read the source code but I
> think your patch is wrong. It changed the function. Original code
> assigned all recipient addresses (appending) in to an array (hash)
> $rectmp in a foreach loop and then assign this array to
> $rows[$count]['recipient_email'].
> But now you are using it as variable so if there are more than one
> recipient this variable is overwritten on each iteration and then just
> the last recipient is assigned to $rows[$count]['recipient_email'].
>
> My very wild guess is that it should be like this
>
> - $rectmp = "";
> + $rectmp = array();
> foreach ($to_list as $recipient) {
> if (isset($personal_addresses[$recipient]) ||
> $domain_default) {
> $rectmp[] = $recipient;
> }
> }
> $rows[$count]['recipient_email'] = $rectmp;
>
> I guess you want to fix some PHP 7 warning / syntax error with $rectmp
> created ass plain variable and later used as an array so I defined as
> an array first.
>
> But maybe I am totally wrong :)
>
> I just made similar fix few days ago in an old version of PostfixAdmin
> after upgrade from PHP 5.6 to 7.1.
Thank you for the information! You're likely very much correct as
that seems to be a more proper fix for the array (and there are likely
other arrays that need to be fixed). I will test this and see if it
works (I don't see why it wouldn't). Thanks again!
Regards,
Janky Jay, III
signature.asc
Description: OpenPGP digital signature
Re: Maia Mailgaurd / PHP 7 support
Hi Miroslav, On 12/29/18 6:16 PM, Miroslav Lachman wrote: > Janketh Jay wrote on 2018/12/30 01:03: >> Hi All, >> >> On 03/12/2018 2:17 pm, Reko Turja via freebsd-ports wrote: >>> Hello Janky Jay! >>> >>> -Original Message- Sent: Monday, December 3, 2018 4:17 PM >>> Subject: Re: Maia Mailgaurd >>> >>>> Okay. No sweat. I'll work on getting a port patch going as that seems >>>> it would be the easiest way to push this out. I'll provide a >>>> download as >>>> soon as I have something available for testing. >>> >>> Sounds good, thank you for your work on ports! >>> >>> -Reko >>> >> >> So, after a bit of testing (and not being able to update the >> port for PHP7 due to Smarty issues), below is a simple patch that >> will keep the current port version of Maia (1.0.4_3) working with >> PHP7 (testing with PHP 7.2). Please let me know if this does not work >> or if there is anything else that needs to be added or changed. >> Hopefully, I'll get the Smarty issue(s) sorted out soon and have a >> new port submitted. > > [...] > >> Also, if you're interested in seeing/testing the new port >> (from the latest Github commit for technion's maia_mailguard), you >> can download the patch from the link below [1] and let me know if >> it's successful for you. Everything seems to work except for the >> WebUI due to a fatal call to Smarty which I cannot figure out (I'm >> not a PHP developer). However, once that is sorted, I should be ready >> to submit the new port so Maia can be updated to the latest version. > > I forgot about this in my previous message - I guess there is an old > version of Smarty not supporting PHP 7. It would be probably better to > replace it with newer version of Smarty with PHP 7 support but there > can be some syntax changes in Smarty config / initialisation. I > remember something about it about a year ago when I was upgrading one > of our own (very old) project to newer Smarty templates. There are > some differences between Smarty 2 and Smarty 3. But as I read now on > their website, the latest Smarty 2 version 2.6.31 supports PHP 7.2 so > it should be painless to replace old noncompatible version with this one. Thanks again for the heads up on the Smarty3 compat being resolved. It seems that the latest PHP_FLAVOR'd Smarty3 does indeed fix the issue when properly linked (I hope I did it correctly). I'll be running this through Poudrier tonight to make sure everything is good and I'll submit the port update as soon as it's verified. In the meantime, if anyone wants to test the patch [1] (or at least look at it to make sure I'm doing it right regarding the PHP flavoring, linking variables, etc... to make sure it's done correctly), that would be great! Thanks again, Miroslav! 1. https://www.purplehat.org/downloads/maia/maia-1.0.4-g20181202.diff Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: ClamAV Port Version Regression?
Perfect! Thanks for the replies and the clarification, guys!
On 12/11/18 11:21 AM, Stefan Esser wrote:
> Am 11.12.18 um 18:51 schrieb Janky Jay, III:
>> Hi All,
>>
>> After a portsnap to pull ${latest), I'm seeing the following:
>>
>> clamav-0.101.0_2 < needs updating (index has 0.100.2,1)
>>
>> The version that is claiming to be the latest appears to be a version
>> regression. Am I wrong here? I checked the ClamAV site and it appears
>> version 0.101.0 is, in fact, the latest. So, I'm wondering if there was
>> possibly a revision issue that's causing this?
>
> The ,1 at the end of the port to be installed indicates a new port epoch,
> which is used to enforce an "upgrade" to a lower version number.
>
> This is typically done if a port upgrade has been revoked due to problems
> with the new version.
>
> In this particular case the commit log says:
>
> r487064 | antoine | 2018-12-09 18:33:26 +0100 (Sun, 09 Dec 2018) | 6 lines
>
> Downgrade to 0.100.2
> Upstream plans to release version 0.101.1 which fixes header issues in January
> 2019
>
> Regards, STefan
>
Regards,
Janky Jay, III
signature.asc
Description: OpenPGP digital signature
ClamAV Port Version Regression?
Hi All,
After a portsnap to pull ${latest), I'm seeing the following:
clamav-0.101.0_2 < needs updating (index has 0.100.2,1)
The version that is claiming to be the latest appears to be a version
regression. Am I wrong here? I checked the ClamAV site and it appears
version 0.101.0 is, in fact, the latest. So, I'm wondering if there was
possibly a revision issue that's causing this?
Regards,
Janky Jay, III
signature.asc
Description: OpenPGP digital signature
Re: Maia Mailgaurd
Hello Reko, On 12/1/18 7:58 AM, Reko Turja wrote: > Hello Janky Jay! > > --Original Message-- Monday, November 26, 2018 10:11 PM Subject: Re: > Maia Mailgaurd > >> That being said, with just a few minor changes, I have been able to get >> Maia to work with PHP 7.2 without any issues (that I've seen, anyway). >> If you're interested in that, I can provide those changes/patches if >> you'd like to upgrade to PHP7 before the upstream code is ready. > > > I would also love the preliminary patches for getting Maia to work on PHP7+ > Okay. No sweat. I'll work on getting a port patch going as that seems it would be the easiest way to push this out. I'll provide a download as soon as I have something available for testing. Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: Maia Mailgaurd
Hello Gary, On 11/25/18 6:13 AM, Gary J. Hayers wrote: > Hi Janky Jay, > > Can I ask if you there are any plans to patch Maia so it can run on php70+? > > Many thanks for the great port. > At the moment, there are a lot of changes happening to the Maia code (more changes for Perl as well as support for PHP7.X. I've tried testing a few of the latest versions but they're not quite ready yet. As soon as they are, I will be updating the port for these versions. My biggest fear right now is that if I patch the port that currently exists to work with PHP7, I'm unsure it would be compatible with PHP5 users. I don't want to break anything for anyone so I haven't done this yet. I'll likely need testers to verify all this before I consider changing the current port. That being said, with just a few minor changes, I have been able to get Maia to work with PHP 7.2 without any issues (that I've seen, anyway). If you're interested in that, I can provide those changes/patches if you'd like to upgrade to PHP7 before the upstream code is ready. Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: Problem with old files in freebsd-update/files
Hello, On 02/27/2018 01:31 PM, Kurt Jaeger wrote: > Hi! > >> FreeBSD 10.4-RELEASE-p3 (GENERIC) #0: Tue Nov 14 09:06:09 UTC 2017 >> >> I wrote about this before, and was told to use "pkg clean" to clean up old >> files which I now do every week, but... > > I have those files in /var/db/freebsd-update/ > > And if I want to clean them up, I do: > > cd /var/db > mv freebsd-update fbsd-up-old > mkdir freebsd-update > chmod 700 freebsd-update > rm -rf fbsd-up-old Out of curiosity, why not just: ~ # rm -rf /var/db/freebsd-update/* Is there a reason you're moving the directory and creating a new, empty one? Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: mail/postfixadmin: Error Regarding "SCOPE_BUBBLE_UP".
Hi Mel, On 02/16/2018 05:02 AM, Mel Pilgrim wrote: > On 2018-02-14 19:13, Janky Jay, III wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> May have spoken too soon... >> >> On 2/14/2018 7:45 PM, Janky Jay, III wrote: >>> Hello Mel, >>> >>> On 2/13/2018 7:42 AM, Mel Pilgrim wrote: >>>> (Putting on my mail/postfixadmin maintainer hat) >>> >>>> On 2018-02-11 15:24, Janky Jay, III wrote: >>>>> Hello All, >>>>> >>>>> Versions: FreeBSD - 11.1-RELEASE-p6 PostfixAdmin - 3.1 Smarty3 >>>>> - 3.1.30 >>> >>>> Postfixadmin bundles its own copy of Smarty, and in PFA 3.1 it's >>>> Smarty 3.1.29. Installing www/smarty3 isn't necessary. Are you >>>> using it for something else? >>> >>> Ah. That's very interesting. The only reason I had Smarty3 >>> installed was for PFA (must have been before it shipped with it's >>> own version, maybe?). I remember a while back I uninstalled it >>> because it was an unused leaf port and immediately PFA stopped >>> working with Smarty3 errors in the http logs. I've just removed >>> Smarty3 again and PFA seems to work just fine. I have no idea >>> what's going on anymore. :) >>> >>> Thanks a ton for the reply, though! I've got my PFA back! >>> >> >> I've removed Smarty3 and the login page presents itself (and allows >> me to login) without any issue. However, attempting to view anything >> within PFA (such as virtual mailboxes or domains), I see the following >> error(s) in the http log file: >> >> PHP Warning: >> require_once(/usr/local/share/smarty3/plugins/function.html_options.php) > > So something is rewriting the Smarty path from PFA's > /usr/local/www/postfixadmin/smarty/libs to what I'm guessing is the path > used by the now-removed www/smarty3. > > This sounds like a caching issue. After removing www/smarty3, did you: > > - check there were no lingering Smarty Apache/PHP config bits in > httpd.conf, php.ini, etc.; > - restart Apache and, if applicable, the PHP module; > - delete everything in templates_c? > > There aren't any configurable options that would change from where > postfixadmin includes Smarty, but the path it uses is set as SMARTY_DIR > in smarty/libs/Autoloader.php and the correct value is ''. > Thanks again for the replies. I do appreciate it. I did remove any config bits from Apache/PHP (most specifically the path to smarty3 in php.ini) and restarted Apache. However, I did not empty the "templates_c" directory (DUH!). That seems to have done the trick! Looks like PFA is back to working again. Thanks again, Mel! Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: mail/postfixadmin: Error Regarding "SCOPE_BUBBLE_UP".
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 May have spoken too soon... On 2/14/2018 7:45 PM, Janky Jay, III wrote: > Hello Mel, > > On 2/13/2018 7:42 AM, Mel Pilgrim wrote: >> (Putting on my mail/postfixadmin maintainer hat) > >> On 2018-02-11 15:24, Janky Jay, III wrote: >>> Hello All, >>> >>> Versions: FreeBSD - 11.1-RELEASE-p6 PostfixAdmin - 3.1 Smarty3 >>> - 3.1.30 > >> Postfixadmin bundles its own copy of Smarty, and in PFA 3.1 it's >> Smarty 3.1.29. Installing www/smarty3 isn't necessary. Are you >> using it for something else? > > Ah. That's very interesting. The only reason I had Smarty3 > installed was for PFA (must have been before it shipped with it's > own version, maybe?). I remember a while back I uninstalled it > because it was an unused leaf port and immediately PFA stopped > working with Smarty3 errors in the http logs. I've just removed > Smarty3 again and PFA seems to work just fine. I have no idea > what's going on anymore. :) > > Thanks a ton for the reply, though! I've got my PFA back! > I've removed Smarty3 and the login page presents itself (and allows me to login) without any issue. However, attempting to view anything within PFA (such as virtual mailboxes or domains), I see the following error(s) in the http log file: PHP Warning: require_once(/usr/local/share/smarty3/plugins/function.html_options.php) : failed to open stream: No such file or directory in /usr/local/www/postfixadmin/templates_c/c508a76bc4b664402a6aa2c93919f1f1 2522a31b_0.file.list.tpl.php on line 23, referer: https://pfa.domain.tld/list.php?table=domain PHP Fatal error: require_once(): Failed opening required '/usr/local/share/smarty3/plugins/function.html_options.php' (include_path='.:/usr/local/share/pear') in /usr/local/www/postfixadmin/templates_c/c508a76bc4b664402a6aa2c93919f1f1 2522a31b_0.file.list.tpl.php on line 23, referer: https://pfa.domain.tld/list.php?table=domain So, it appears like it is still looking for smarty3 outside of it's document root. Perhaps this is a config I can adjust somewhere? I'll keep poking around. Regards, Janky Jay, III -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT3labtx1DPvRcqv5cYrcyxRslmfgUCWoT6wQAKCRAYrcyxRslm fjs4AJ0QvRm3RlvUKL8iyWHcTqxr80SlgwCfRvJCqRIzaTQRIqVii01MTQHCdFc= =zpks -END PGP SIGNATURE- ___ 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: mail/postfixadmin: Error Regarding "SCOPE_BUBBLE_UP".
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Mel, On 2/13/2018 7:42 AM, Mel Pilgrim wrote: > (Putting on my mail/postfixadmin maintainer hat) > > On 2018-02-11 15:24, Janky Jay, III wrote: >> Hello All, >> >> Versions: FreeBSD - 11.1-RELEASE-p6 PostfixAdmin - 3.1 Smarty3 - >> 3.1.30 > > Postfixadmin bundles its own copy of Smarty, and in PFA 3.1 it's > Smarty 3.1.29. Installing www/smarty3 isn't necessary. Are you > using it for something else? Ah. That's very interesting. The only reason I had Smarty3 installed was for PFA (must have been before it shipped with it's own version, maybe?). I remember a while back I uninstalled it because it was an unused leaf port and immediately PFA stopped working with Smarty3 errors in the http logs. I've just removed Smarty3 again and PFA seems to work just fine. I have no idea what's going on anymore. :) Thanks a ton for the reply, though! I've got my PFA back! Regards, Janky Jay, III -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT3labtx1DPvRcqv5cYrcyxRslmfgUCWoT0SgAKCRAYrcyxRslm fqCoAJ9Q4cF51KNf2CCQ8LXWoYyWwepIygCeLYUkwB4UWz6ZTT8ZRTQPpELeJUw= =WSgQ -END PGP SIGNATURE- ___ 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: mail/postfixadmin: Error Regarding "SCOPE_BUBBLE_UP".
Thanks, Walter! Hrm. Very strange that a) Github didn't alert me to the reply and b) when I checked 2 days ago I didn't see the reply although it says 7 days ago (bad cache maybe?). Anyhow, it looks like the port is broken then. I'm unsure why the current port was expected to work either (unless, as mentioned) it *IS* a Smarty3 version issue. I'll just contact the maintainer and wait for the next PFA release. Thanks again! Regards, Janky Jay, III On 2/11/2018 4:41 PM, Walter Schwarzenfeld wrote: > No answer? > > https://sourceforge.net/p/postfixadmin/discussion/676076/thread/0f6936c7/ > > and > > https://github.com/postfixadmin/postfixadmin/commit/14ec596cbfebc27bb8066e0ce870e68d53e00de9 > > > ___ > 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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
mail/postfixadmin: Error Regarding "SCOPE_BUBBLE_UP".
Hello All, Versions: FreeBSD - 11.1-RELEASE-p6 PostfixAdmin - 3.1 Smarty3 - 3.1.30 PHP - 5.6.33 So, I'm unsure if the is due to the most recent update of PostfxAdmin, Smarty3, or PHP, but I'm seeing the following error upon loading the login page for PostfixAdmin: PHP Fatal error: Undefined class constant 'SCOPE_BUBBLE_UP' in /usr/local/www/postfixadmin/smarty/libs/sysplugins/smarty_internal_runtime_subtemplate.php on line 114 Has anyone else been seeing this? I've tried the PFA FreeNode channel and the PFA forums on Github but thus far no replies. Has anyone else seen this behavior or is this a configuration issue of some type, maybe? I will mention that PFA was working perfectly fine less than a month ago. Regards, Janky Jay, III ___ 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: Latest security/py-fail2ban (0.10.1_1) Broken Again.
Never mind. I ended up figuring this out. I basically re-created all my jails and started from scratch. Anyone else that might be struggling with the same issue can find what I did at the URL below. http://www.purplehat.org/?page_id=566 Regards, Janky Jay, III ___ 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"
Latest security/py-fail2ban (0.10.1_1) Broken Again.
Looks like the latest update broken more of the previously fixed issues.
Also, it appears that F2B 0.9.X is the latest stable and 0.10.X is
"experimental". Why is the default port experimental? Shouldn't this be
broken up into two ports?
Anywho, below is an example of the fail2ban.log output when an SSH
attempt should be banned (via PF):
2017-10-27 16:02:40,016 fail2ban.filter [17083]: INFO
[bsd-ssh-pf] Found 174.135.101.80 - 2017-10-27 16:02:39
2017-10-27 16:02:42,286 fail2ban.filter [17083]: INFO
[bsd-ssh-pf] Found 174.135.101.80 - 2017-10-27 16:02:41
2017-10-27 16:02:42,497 fail2ban.actions [17083]: NOTICE
[bsd-ssh-pf] Ban 174.135.101.80
2017-10-27 16:02:42,520 fail2ban.utils [17083]: Level 39
8020c31c0 -- exec: pfctl -a f2b/ssh -sr | grep -q f2b-ssh
2017-10-27 16:02:42,521 fail2ban.utils [17083]: ERROR
8020c31c0 -- returned 1
2017-10-27 16:02:42,521 fail2ban.CommandAction [17083]: ERROR
Invariant check failed. Trying to restore a sane environment
2017-10-27 16:02:42,566 fail2ban.utils [17083]: Level 39
8020b0870 -- exec: echo "table persist counters" | pfctl -a
f2b/ssh -f-
echo "block quick proto tcp from to any port {{3}}" |
pfctl -a f2b/ssh -f-
2017-10-27 16:02:42,567 fail2ban.utils [17083]: ERROR
8020b0870 -- stderr: 'stdin:1: syntax error'
2017-10-27 16:02:42,567 fail2ban.utils [17083]: ERROR
8020b0870 -- stderr: 'pfctl: Syntax error in config file: pf rules not
loaded'
2017-10-27 16:02:42,567 fail2ban.utils [17083]: ERROR
8020b0870 -- returned 1
2017-10-27 16:02:42,568 fail2ban.actions [17083]: ERROR Failed
to execute ban jail 'bsd-ssh-pf' action 'pf' info
'ActionInfo({'ipfailures': 42, 'ip-rev': '80.101.135.174.', 'family':
'inet4', 'ipmatches': 'FTP Server [12354] domain.org
[19/May/2016:20:02:35 -0600] "PASS (hidden)" 530\nFTP Server [12354]
domain.org [19/May/2016:20:02:54 -0600] "PASS (hidden)" 530\nFTP Server
[12354] domain.org [19/May/2016:20:02:35 -0600] "PASS (hidden)" 530\nFTP
Server [12354] domain.org [19/May/2016:20:02:54 -0600] "PASS (hidden)"
530\nFTP Server [12673] domain.org [19/May/2016:20:07:42 -0600] "PASS
(hidden)" 530\nFTP Server [12354] domain.org [19/May/2016:20:02:35
-0600] "PASS (hidden)" 530\nFTP Server [12354] domain.org
[19/May/2016:20:02:54 -0600] "PASS (hidden)" 530\nFTP Server [12673]
domain.org [19/May/2016:20:07:42 -0600] "PASS (hidden)" 530\nFTP Server
[12673] domain.org [19/May/2016:20:07:45 -0600] "PASS (hidden)" 530\nFTP
Server [12694] domain.org [19/May/2016:20:08:08 -0600] "PASS (hidden)"
530\nFTP Server [12694] domain.org [19/May/2016:20:08:14 -0600] "PASS
(hidden)" 530\nFTP Server [12673] domain.org [19/May/2016:20:07:45
-0600] "PASS (hidden)" 530\nFTP Server [12694] domain.org
[19/May/2016:20:08:08 -0600] "PASS (hidden)" 530\nFTP Server [12694]
domain.org [19/May/2016:20:08:14 -0600] "PASS (hidden)" 530\nFTP Server
[12869] domain.org [19/May/2016:20:14:01 -0600] "PASS (hidden)" 530\nFTP
Server [12869] domain.org [19/May/2016:20:14:06 -0600] "PASS (hidden)"
530\nFTP Server [12673] domain.org [19/May/2016:20:07:42 -0600] "PASS
(hidden)" 530\nFTP Server [12673] domain.org [19/May/2016:20:07:45
-0600] "PASS (hidden)" 530\nFTP Server [12694] domain.org
[19/May/2016:20:08:08 -0600] "PASS (hidden)" 530\nFTP Server [12694]
domain.org [19/May/2016:20:08:14 -0600] "PASS (hidden)" 530\nFTP Server
[12869] domain.org [19/May/2016:20:14:01 -0600] "PASS (hidden)" 530\nFTP
Server [12869] domain.org [19/May/2016:20:14:06 -0600] "PASS (hidden)"
530\nFTP Server [12881] domain.org [19/May/2016:20:14:30 -0600] "PASS
(hidden)" 530\nFTP Server [12881] domain.org [19/May/2016:20:14:38
-0600] "PASS (hidden)" 530\nFTP Server [12881] domain.org
[19/May/2016:20:14:30 -0600] "PASS (hidden)" 530\nFTP Server [12881]
domain.org [19/May/2016:20:14:38 -0600] "PASS (hidden)" 530\nFTP Server
[13000] domain.org [19/May/2016:20:17:14 -0600] "PASS (hidden)" 530\nFTP
Server [13000] domain.org [19/May/2016:20:17:22 -0600] "PASS (hidden)"
530\n2017-10-15 16:45:11,363 server1.domain-dos.org proftpd[48705]
server1 (domain.org[174.135.101.80]): USER user dick: no such user found
from domain.org [174.135.101.80] to 51.244.130.111:21\nFTP Server
[48705] domain.org [15/Oct/2017:16:45:11 +] "PASS (hidden)"
530\n2017-10-15 16:45:11,363 server1.domain-dos.org proftpd[48705]
server1 (domain.org[174.135.101.80]): USER user dick: no such user found
from domain.org [174.135.101.80] to 51.244.130.111:21\n2017-10-15
16:51:10,946 server1.domain-dos.org proftpd[48907] server1
(mail.domain.org[174.135.101.80]): USER derp: no such user found from
mail.domain.org [174.135.101.80] to 51.244.130.111:21\n2017-10-15
16:51:14,626 server1.domain-dos.org proftpd[48907] server1
(mail.domain.org[174.135.101.80]): USER dick: no such user found from
mail.domain.org [174.135.101.80] to 51.244.130.111:21\nOct 15 16:53:27
server1 sshd[48984]: Invalid user turd from 174.135.101.80\nOct 15
16:53:30 server1
Re: FreeBSD Port: py27-fail2ban-0.10.1
Hi Alex,
On 10/17/2017 10:35 AM, Alex V. Petrov wrote:
> What should be in pf.conf?
>
Something as simple has the below should work (edit to however you see
fit):
# define macros for each network interface
ext_if = "em0"
icmp_types = "echoreq"
allproto = "{ tcp, udp, ipv6, icmp, esp, ipencap }"
privnets = "{ 127.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8 }"
set loginterface $ext_if
scrub in on $ext_if no-df random-id
>
> 17.10.2017 23:15, Janky Jay, III пишет:
>> In the new 0.10 version, the action rule creates the tables for you
>> based on the jail configuration. If you look at the jail files, you'll
>> see that you now call pfctl using additional arguments such as ports
>> that are affected and a suffix to add to the default "f2b-" table name.
>>
>> So, essentially, there is no reason to create tables in the
>> pf.conf/pf.rules file anymore. They are automatically created when a
>> fail2ban filter is triggered and the IP is then added to it.
>
signature.asc
Description: OpenPGP digital signature
Re: FreeBSD Port: py27-fail2ban-0.10.1
Hello,
In the new 0.10 version, the action rule creates the tables for you
based on the jail configuration. If you look at the jail files, you'll
see that you now call pfctl using additional arguments such as ports
that are affected and a suffix to add to the default "f2b-" table name.
So, essentially, there is no reason to create tables in the
pf.conf/pf.rules file anymore. They are automatically created when a
fail2ban filter is triggered and the IP is then added to it.
On 10/17/2017 07:16 AM, Alex V. Petrov wrote:
> In the old version I did so.
>
>
> 17.10.2017 19:47, Tommy Scheunemann пишет:
>> Hi,
>>
>> a simple setup that does the job for me:
>>
>> In /etc/pf.conf (bge0 is my external interface)
>>
>> --- SNIP ---
>> int_ext="bge0"
>> ...
>> table
>> ...
>> block in quick on $int_ext from to any
>> ...
>> --- SNIP ---
>>
>> And in ${PREFIX}/fail2ban/action.d defining a new "pf" action, e.g. pf.conf
>>
>> --- SNIP ---
>> [Definition]
>> actionban = /usr/local/bin/drop_ban
>> actionunban = /usr/local/bin/drop_unban
>> actioncheck =
>> actionstart =
>> actionstop =
>>
>> [Init]
>> --- SNIP ---
>>
>> And the "drop_ban" and "drop_unban" scripts:
>>
>> for ban:
>>
>> --- SNIP ---
>> #!/bin/sh
>> IP=$1
>> /sbin/pfctl -t badhosts -T add $IP
>> --- SNIP ---
>>
>> for unban
>>
>> --- SNIP ---
>> #!/bin/sh
>> IP=$1
>> /sbin/pfctl -t badhosts -T del $IP
>> --- SNIP ---
>>
>> I'm using scripts instead of directly using actionban / actionunban to
>> do some additional things like running a tcpdrop, having some better
>> logging.
>>
>> Once done with all this, you can use "action = pf" in your jail.conf file.
>>
>> Apart this I'd highly recommend to put all this into some configuration
>> system (Ansible, Puppet, Cfengine etc.).
>> Updating the package / port will overwrite your local changes !
>>
>> Have fun & good luck
>>
>> On Tue, 17 Oct 2017, Alex V. Petrov wrote:
>>
>>> Need a working sample for the new version of the port for pf.
>>>
>>> -
>>> Alex.
>>> ___
>>> 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"
>>>
>>
>>
>
signature.asc
Description: OpenPGP digital signature
Re: mail/p5-Net-SMTP-SSL Port Dependencies in SpamAssassin.
Hi Herbert, On 03/17/2017 12:32 AM, Herbert J. Skuhra wrote: > jankyj skrev: >> >> Hello all, >> I have a port that depends on SpamAssassin and I've noticed the >> (somewhat) recent deprecation message of the mail/p5-Net-SMTP-SSL port >> which, in turn, appears to be a dependency on >> security/p5-IO-Socket-SSL by SpamAssassin (if you enable SSL and/or >> DKIM). I've taken a look at the Makefile and I have a couple of ideas >> as to how to fix it but I am by no means a port guru. > > I can't find a dependency on mail/p5-Net-SMTP-SSL. Where exactly to > you see it? > I'm seeing this when I run a 'pkg info -r' or 'pkg info -d' on 'mail/p5-Net-SMTP-SSL'. Apparently, it's a dependency on 'p5-IO-Socket-SSL' or something that SpamAssassin pulls in? This is exactly what I'm trying to hunt down and, more specifically, find out if it needs to be installed at all (Thanks for the info!). > I am using spamassassin (with DKIM and SSL on) and don't have > mail/p5-Net-SMTP-SSL on my system. > Interesting. Perhaps this is just an old dependency that is no longer relevant. I'll look into this as well. > Is your ports tree up-to-date? > Ports tree is up-to-date using portsnap as of 11pm Mountain Time yesterday. Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: mail/p5-Net-SMTP-SSL Deprecated Message.
Hello Matthew,
On 12/14/2016 10:22 AM, Matthew Seaman wrote:
> On 2016/12/14 16:53, Janky Jay, III wrote:
>> Hello All,
>>
>> So, mail/p5-Net-SMTP-SSL is a requirement of security/maia (a port I
>> maintain) and it is apparently being deprecated as of March of next
>> year. I see this in my nightly reports:
>>
>> p5-Net-SMTP-SSL-1.04: Tag: expiration_date Value: 2017-03-31
>> p5-Net-SMTP-SSL-1.04: Tag: deprecated Value: Deprecated by upstream, use
>> Net::SMTP instead
>>
>> I'd like to get this dependency updated in the port but I don't see a
>> "Net::SMTP" available (at least in the ${LOCALBASE}/mail directory. I
>> see others such as p5-Net-SMTP-TLS and p5-Net-SMTPS and
>> p5-Net-SMTP_auth, etc...
>>
>> My question is, what port am I supposed to use instead of
>> p5-Net-SMTP-SSL? I see no configuration options for SSL in the other
>> ports. Just want to make sure I do this correctly. Any information will
>> be greatly appreciated!
>
> Net::SMTP is a core perl module, or you can install the p5-Net-3.10_1,1
> package to get a slightly newer version of it.
>
> Net::SMTP has had SSL support capability since version 1.28 way back in
> 2014. You just need to have IO::Socket::SSL installed too.
>
> In the intervening 3 or so years, applications are meant to have been
> re-written to use Net::SMTP rather than Net::SMTP::SSL, but clearly this
> has not happened universally.
Fantastic! Thanks for the info. I'll see what I can do about either
getting the application to use Net::SMTP and I'll add IO::Socket::SSL or
I'll come up with another workaround.
Regards,
Janky Jay, III
signature.asc
Description: OpenPGP digital signature
mail/p5-Net-SMTP-SSL Deprecated Message.
Hello All,
So, mail/p5-Net-SMTP-SSL is a requirement of security/maia (a port I
maintain) and it is apparently being deprecated as of March of next
year. I see this in my nightly reports:
p5-Net-SMTP-SSL-1.04: Tag: expiration_date Value: 2017-03-31
p5-Net-SMTP-SSL-1.04: Tag: deprecated Value: Deprecated by upstream, use
Net::SMTP instead
I'd like to get this dependency updated in the port but I don't see a
"Net::SMTP" available (at least in the ${LOCALBASE}/mail directory. I
see others such as p5-Net-SMTP-TLS and p5-Net-SMTPS and
p5-Net-SMTP_auth, etc...
My question is, what port am I supposed to use instead of
p5-Net-SMTP-SSL? I see no configuration options for SSL in the other
ports. Just want to make sure I do this correctly. Any information will
be greatly appreciated!
Kind Regards,
Janky Jay, III
signature.asc
Description: OpenPGP digital signature
Re: The ports collection has some serious issues
Hi Vlad, On 12/11/2016 07:58 PM, Vlad K. wrote: > On 2016-12-12 03:42, Janky Jay, III wrote: >> This very, VERY rarely happens to me and I use ports *ONLY* in >> production environments. If you could please provide examples and report >> the issues to the port maintainer of the ports with issues, that would >> greatly help this situation. (Please don't take this as an insult or > > Good advice, but please rather file a bug report on our bugzilla: > > https://bugs.freebsd.org/bugzilla/enter_bug.cgi?component=Individual%20Port%28s%29=Ports%20%26%20Packages > > > Problems reported to maintainers directly cannot be tracked or confirmed > by other users. > Thanks for the clarification. In my previous response, my recommendation was to report to both the port maintainer as well as file a BUG report. I should have been more clear. Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: The ports collection has some serious issues
Hello scratch, On 12/11/2016 03:35 PM, scratch65...@att.net wrote: > I have to admit that I avoid ports if at all possible because > I've hardly ever been able to do a build that ran to completion. > There's always some piece of code that's missing and can't be > found, or is the wrong version, et lengthy cetera. I've never > done release engineering, but I honestly can't imagine how some > of the stuff that makes its way into the ports tree ever got past > QA. It would get someone sacked if it happened in industry. > > If the dev schedule would SLOW DOWN and the commitment switched > to quality from the current emphasis on frequency, with separate > trees for alpha-, beta-, and real release-quality, fully-vetted > code, the ports system might become usable again. This very, VERY rarely happens to me and I use ports *ONLY* in production environments. If you could please provide examples and report the issues to the port maintainer of the ports with issues, that would greatly help this situation. (Please don't take this as an insult or anything other than trying to be helpful...) Simply complaining about it without providing any additional information is certainly not going to improve anything. Being a port maintainer myself, I depend on people reporting any issues they run into in order to provide the most robust and dependable port I can. If people never reported any issues and I had no idea there was an issue with my port, how would I fix it? So, please, PLEASE report any issues with ports that aren't building. It's not too time consuming on your part. Just a simple BUG report and how to re-produce and you're finished. Kind Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
PR Commit Request.
Hello, Can someone please commit this (it's been waiting a while and is only a simple "sed" change in the Makefile). If there's anything else I need to do, let me know. Thanks! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210138 Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: devel/arduino - bad advice given in pkg-message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Tom,
On 03/31/2016 04:46 AM, Warren Block wrote:
> On Sun, 27 Mar 2016, Warren Block wrote:
>
>> Here is how I propose to rewrite that:
>>
>> -G grouplist Set secondary group memberships for an account.
>> grouplist is a comma, space, or tab-separated list of group names
>> or group numbers. /etc/group is modified to include the user's
>> name in the groups specified in grouplist. The user's name is
>> removed from all groups not specified. Group membership changes
>> do not take effect for current user login sessions, requiring the
>> user to reconnect to be affected by the changes. Note: do not
>> add a user to their primary group with grouplist.
>
>> Modified version committed in
>> https://svnweb.freebsd.org/base/head/usr.sbin/pw/pw.8?r1=297330=29
7329=297330
>
>>
> I've been following this thread, have this question:
>
> How does one add a user to additional groups without removing the
> user from groups the user is already in?
>
> I just looked at the new manpage from a fresh svn update of src
> tree.
>
This was actually covered in this thread (first post, actually) by
Torfinn Ingolfsen:
"Better to use this:
pw groupmod dialer -m myuser
it will ony affect the dialer group, and not mess with any other groups.
"
The above will add the user "myuser" to the "dialer" group while
leaving the user's other group intact as well.
Regards,
Janky Jay, III
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlb9Nu4ACgkQGK3MsUbJZn7exACfZiXwVfIE762df3rfxVmdpd/K
CKkAnjgBMJ3ewsIlYlQB5OhkbKx2opT6
=Or1f
-END PGP SIGNATURE-
___
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: devel/arduino - bad advice given in pkg-message
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Torfinn, On 03/25/2016 10:20 AM, Torfinn Ingolfsen wrote: > On Fri, Mar 25, 2016 at 4:34 PM, Janky Jay, III <jan...@unfs.us> > wrote: >> >> While your solution is not incorrect, your assumption on the >> proposed/given solution from the port is. The '-G' switch appends >> the given group to your users already given groups. So, if a user >> belongs to groups admin,wheel,test and you run the suggested "pw" >> command from the port, your user will now be in groups >> admin,wheel,test,dialer. It's the '-g' (lower-case) switch you >> want to avoid... >> > > If you read the man page, I think you will find that it is your > assumption about what the '-G' switch does which is incorrect. > Quote: "-G grouplist" "Set additional group memberships for an > account. grouplist is a comma, space or tab-separated list of > group names or group numbers. The user's name is added to the > group lists in /etc/group, and removed from any groups not > specified in grouplist." > > Please note the part which says "and removed from any groups not > specified in grouplist" > Ah yes! You are correct! For some reason I was mixing my "pw usermod" and Linux "usermod" (where you use the -aG to append). My fault entirely. Continue with your correct request for the update of the false information. *fades into background* Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlb3HUQACgkQGK3MsUbJZn7YLgCfWOpBHTJfrBLKQfbWWX/qJzWt OKUAn3MhgqhV08uwHMnC1+qseVaNkFVE =khJo -END PGP SIGNATURE- ___ 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: devel/arduino - bad advice given in pkg-message
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Torfinn, On 03/25/2016 09:26 AM, Torfinn Ingolfsen wrote: > Hello, The pkg-message for the devel/arduino port contains this: > > "To allow serial port locking, add your user to the dialer group:" > "pw usermod myuser -G dialer" > > It is good to explain what a user have to do to get serial > access. However, if you use that pw command, it will remove your > user from any other groups than the dialer group. Which might be > annoying. Better to use this: pw groupmod dialer -m myuser it will > ony affect the dialer group, and not mess with any other groups. > HTH > While your solution is not incorrect, your assumption on the proposed/given solution from the port is. The '-G' switch appends the given group to your users already given groups. So, if a user belongs to groups admin,wheel,test and you run the suggested "pw" command from the port, your user will now be in groups admin,wheel,test,dialer. It's the '-g' (lower-case) switch you want to avoid... That being said, your suggestion does the exact same thing. So, really, either works. Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlb1WoQACgkQGK3MsUbJZn43vACfQcs3E2IWsRaf2SACO1jMmFxt PBsAnjuC5GSvEUvezKLWKS25WJyAGzuQ =KEJX -END PGP SIGNATURE- ___ 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: Ports requires pkg 1.6.0, but 1.5.6 is the latest available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On 09/29/2015 02:12 AM, Mel Pilgrim wrote:
> On 2015-09-28 21:31, Kevin Oberman wrote:
>> On Mon, Sep 28, 2015 at 4:41 PM, Mel Pilgrim
>> <list_free...@bluerosetech.com> wrote:
>>
>>> I'm trying to build and install security/openssh-portable, but
>>> when I do, make errors out with:
>>>
>>> ===> openssh-portable-7.1.p1_2,1 pkg(8) must be version 1.6.0
>>> or greater, but you have 1.5.6. You must upgrade the
>>> ports-mgmt/pkg port first. *** Error code 1
>>>
>>> Stop. make: stopped in /usr/ports/security/openssh-portable
>>>
>>> I'm using an svn checkout of
>>> https://svn.freebsd.org/ports/head. I also cleaned my package
>>> cache and forced an update of the local catalogues, but pkg
>>> tells me the latest version of pkg available, at least for
>>> amd64 10.2p3, is 1.5.6.
>>>
>>> I rolled back my local ports tree to r397904 (r397905 was the
>>> MINIMAL_PKG_VERSION bump) and it works fine.
>>>
>>> I'm guessing from other posts on this list that pkg 1.6.0 out,
>>> but it doesn't seem to be in the public pkg repo. I didn't
>>> see anything in UPDATING about it.
>>>
>>> What am I missing?
>>>
>>
>> I believe that 10.2p3 only updated to the latest quarterly
>> package build. If you want something more recent, you will need
>> to edit the config file (/etc/pkg/FreeBSD.conf) to use "latest"
>> repo. I believe that url: "pkg+
>> http://pkg.FreeBSD.org/${ABI}/latest; should do the trick.
>>
>> More of concern is why svn is not working. What does "svn info
>> /usr/ports" show? "svn status /usr/ports"? I and assure you that
>> pkg-1.6.1 IS in svn. I have it and built and installed it
>> earlier today. You can confirm what is in the repo by checking
>> out the web interface:
>> https://svnweb.freebsd.org/ports/head/ports-mgmt/pkg/.
>
> svn is working fine. pkg is installed from pkgs, not ports. The
> issue I'm raising is that the ports tree made mandatory something
> that isn't available by default in 10.2.
>
> I ultimately fixed it by switching to the "latest" repo (the repo
> config edit you mentioned). I was already disinterested in the
> quarterly repos because it smacks of Debian-ness, and this
> confirms why stability-by-staleness is a bad idea.
>
I ran into this exact same issue using SVN and portmaster to upgrade
'git'. Upgrading 'pkg' using portmaster (portmaster -d 'pkg-1.5.6')
before running 'portmaster -ad' fixed the issue. Generally, though,
portmaster usually updates pkg first and then moves along the rest of
the updates automatically. For whatever reason, that was not the case
today.
Regards,
Janky Jay, III
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlYKrUMACgkQGK3MsUbJZn6KuwCfajnPMz+UWZJzxtO7RTMk2xFX
tKUAn0SQ5CM0aL/SlfG7wbOMB+81im9S
=8gj4
-END PGP SIGNATURE-
___
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: New pkg audit / vuln.xml failures (php55, unzoo)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrm... Numerous inquiries regarding this and no response is somewhat disappointing. If anyone gets any feedback from anywhere else, please update the rest of us (BSDCan contacts/update included... I can't make it... :( ) Regards, Janky Jay, III On 06/08/2015 09:34 PM, Mark Felder wrote: On Mon, Jun 8, 2015, at 15:55, Roger Marquis wrote: On Fri, May 29, 2015 at 5:15 PM, Robert Simmons rsimmo...@gmail.com wrote: Crickets. May I ask again: How do we find out who the members of the Ports Secteam are? How do we join the team? Anyone? I really hope this can be resolved face-to-face at BSDCan... ___ 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlV5IHUACgkQGK3MsUbJZn5JGACbBzSKVHZJDukPpnyEOIh8/WZD aIMAoII9Q0V7iS1gDME1okX3BL864Qb7 =tVRd -END PGP SIGNATURE- ___ 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
Re: New pkg audit / vuln.xml failures (php55, unzoo)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/28/2015 11:31 AM, Mark Felder wrote: On Thu, May 28, 2015, at 11:47, Bryan Drewery wrote: Personally I agree on all points. Our ports security regime is not working. I already communicated further with Roger off-list, but would like to point out that I *do* think there is a problem, but I don't think it's the sky is falling / don't use FreeBSD yet. This is a solvable problem that simply requires some defined processes and participation/organization. It seems like we're talking to ourselves here, so do we need to hijack the ports-secteam@ alias and start figuring things out ourselves? It appears no one has been able to join the ports-secteam@ list, but if there is way for me to contribute in any way, I'd certainly like to be on the list as well. If anyone knows of a way to join this list, please let me know. Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlVniZsACgkQGK3MsUbJZn78mQCfYA9HqU8/94CqMfle8wbKdAdS syQAnjp+Hptkc8hsfbh4bWzFEJpI2Zi7 =dvQG -END PGP SIGNATURE- ___ 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
finance/frontaccounting Port Update.
Hello Committers, Would someone be so kind as to take a quick look at PR/BUG #194255 for the port update? No so much to have it committed immediately or anything but I had submitted a previous PR (which has also not been committed yet (PR/BUG #193883)) that I would like to be removed as this latest PR contains the previous fix(es) plus the version update. Thanks! -Janky Jay, III ___ 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
Re: fs-uae amiga emulator
Hello, On 02/17/2014 12:44 PM, Kevin Oberman wrote: On Mon, Feb 17, 2014 at 11:05 AM, Marko Cupać marko.cu...@mimar.rs wrote: Hi, for some time now I am using this great amiga emulator: http://fs-uae.net/ It compiles and runs fine on FreeBSD, no need for any patches. Is there a chance we could see it in ports tree? Unfortunately I am not skilled enough to make a port (meaning I never made one). If it just compiles and runs with no changes, you can probably make the port quite easily. Take look at the Porter's Handbook at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook (or the URL for the language you prefer of those available). It's pretty easy to do a simple port and it looks like that is all that this is. Be sure to install ports-mgmt/portlint and run it on you port before submitting it. And be patient. The ports committers are rather swamped ATM and things are taking a bit longer than usual. (OK, quite a bit longer.) Also, don't forget to include any of the relevant licensing that comes with this software. It appears to be GPLv2 (along with some other incorporated licensing) that could make certain individuals a bit bitchy if it's excluded. Regards, Janky Jay, III ___ 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
Re: pidgin with pidgin-sipe plugin now aborts on connect
Hello Greg,
Simply editing the Makefile and the distinfo file inside the
net-im/pidgin-sipe directory worked fine for me. I did the following:
1) Edit Makefile
a) Changed PORTVERSION from 1.13.1 to 1.18.0
b) Removed the PORTREVISION line
2) After editing the Makefile, I ran
a) make makesum (to update the distinfo file)
b) make all install clean
Pidgin now connects without any issues using the Office Communicator
protocol. I've also attached a patch for the port if you'd rather use
that. If it works for you, I'll submit the patch to PR. Just let me know.
Regards,
Janky Jay, III
On 02/14/2014 11:00 AM, Greg Rivers wrote:
Since the recent update of pidgin to version 2.10.9, pidgin aborts
(signal 6) whenever I connect to a Office Communicator account via the
pidgin-sipe plugin. The pidgin-sipe port is very much out of date, so I
suspect that pidgin has diverged enough to cause this.
Are there any plans to bring the pidgin-sipe plugin up to date?
diff -Naur pidgin-sipe.orig/Makefile pidgin-sipe/Makefile
--- pidgin-sipe.orig/Makefile 2014-02-09 10:40:14.0 -0700
+++ pidgin-sipe/Makefile 2014-02-14 14:03:45.0 -0700
@@ -2,8 +2,7 @@
# $FreeBSD: head/net-im/pidgin-sipe/Makefile 336957 2013-12-19 20:11:14Z swills $
PORTNAME= pidgin-sipe
-PORTVERSION= 1.13.1
-PORTREVISION= 1
+PORTVERSION= 1.18.0
CATEGORIES= net-im
MASTER_SITES= SF/sipe/sipe/${DISTNAME}
diff -Naur pidgin-sipe.orig/distinfo pidgin-sipe/distinfo
--- pidgin-sipe.orig/distinfo 2014-02-09 10:40:14.0 -0700
+++ pidgin-sipe/distinfo 2014-02-14 14:03:51.0 -0700
@@ -1,2 +1,2 @@
-SHA256 (pidgin-sipe-1.13.1.tar.bz2) = 30d1587177311752520458abd5a0e5b998b2e07dab9b4fb23576ac7216387d3b
-SIZE (pidgin-sipe-1.13.1.tar.bz2) = 748761
+SHA256 (pidgin-sipe-1.18.0.tar.bz2) = ca2a357b516c873c9a3feb0315aba6e4a246b5c657e6de7ada1dc302c50cb064
+SIZE (pidgin-sipe-1.18.0.tar.bz2) = 854853
___
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
Re: pidgin with pidgin-sipe plugin now aborts on connect
Hi Ruslan, I most certainly will (providing that it actually works)! :) Once it's verified, I'll submit the PR. On 02/14/2014 02:21 PM, Ruslan Makhmatkhanov wrote: Janky Jay, III wrote on 15.02.2014 01:16: Hello Greg, Simply editing the Makefile and the distinfo file inside the net-im/pidgin-sipe directory worked fine for me. I did the following: 1) Edit Makefile a) Changed PORTVERSION from 1.13.1 to 1.18.0 b) Removed the PORTREVISION line 2) After editing the Makefile, I ran a) make makesum (to update the distinfo file) b) make all install clean Pidgin now connects without any issues using the Office Communicator protocol. I've also attached a patch for the port if you'd rather use that. If it works for you, I'll submit the patch to PR. Just let me know. Regards, Janky Jay, III Great! Would you please submit your patch to GNATS PR? ___ 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
Re: pidgin with pidgin-sipe plugin now aborts on connect
Yeah. I figured there would be more to it (I didn't re-create the pkg-plist yet). I just wanted to know if the 1.18.0 version worked for Greg before I did anything else. Looks like that PR will do just fine, though. Thanks! On 02/14/2014 04:04 PM, Steve Wills wrote: There are some additional changes needed, see PR ports/186783. This version passes poudriere testport. Also, PR ports/183941 was submitted to update to 1.17.0, but had some issues with KRB5 and wasn't committed. This version builds fine with KRB5 for me, so I think 183941 can be closed. Steve On Fri, Feb 14, 2014 at 03:01:47PM -0700, Janky Jay, III wrote: Hi Ruslan, I most certainly will (providing that it actually works)! :) Once it's verified, I'll submit the PR. On 02/14/2014 02:21 PM, Ruslan Makhmatkhanov wrote: Janky Jay, III wrote on 15.02.2014 01:16: Hello Greg, Simply editing the Makefile and the distinfo file inside the net-im/pidgin-sipe directory worked fine for me. I did the following: 1) Edit Makefile a) Changed PORTVERSION from 1.13.1 to 1.18.0 b) Removed the PORTREVISION line 2) After editing the Makefile, I ran a) make makesum (to update the distinfo file) b) make all install clean Pidgin now connects without any issues using the Office Communicator protocol. I've also attached a patch for the port if you'd rather use that. If it works for you, I'll submit the patch to PR. Just let me know. Regards, Janky Jay, III Great! Would you please submit your patch to GNATS PR? ___ 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 ___ 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 ___ 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
Re: Issues with postmaster after freebsd-update
Hello, I've ran into a few of these same sort of issues in the paste. What I did to fix it: 1) Migrate to pkgng. It looks like you already have based on the ports-mgmt/pkg udpate. But, then I see your pkg_install error which leads me to believe you haven't fully migrated. Just take a quick peek at http://www.freebsd.org/doc/handbook/pkgng-intro.html and maybe try it again. 2) Manually deinstall the problematic port. IE...: # cd /usr/ports/graphics/py-clutter make deinstall I had to do this for a lot of ports that were broken on my system. But, after some blood, sweat and tears, everything is back to normal. Also, there still seem to be some underlying issues with the /var/db/pkg directory still. For instance, I migrated to Dovecot2 many moons ago and wiped out Dovecot1. However, dovecot-1.2.17 still remains in my /var/db/pkg directory. *shrug* It's not causing any problems. It's just confusing Regards, Janky Jay, III On 02/13/2014 04:39 PM, LuKreme wrote: I was running FreeBSD 8-2 and used freebsd-update to update: FreeBSD 8.4-RELEASE-p7 #0: Sat Jan 11 01:45:47 UTC 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC the next step I was given was to run portmaster -af This has been a freaking nightmare. I've managed to clear up some of the issues on my own (db41 is still installed, for example), but have no gotten to a point I can't seem tog et past: === The graphics/py-clutter port has been deleted: Has expired: Broken for more than 6 month === Aborting update === Killing background jobs Terminated Terminated Terminated Terminated === Exiting # portmaster -l | grep cutt pkg: not found # pkg2ng bash: pkg2ng: command not found # portmaster ports-mgmt/pkg [...] === Cleaning for pkg-1.2.6 === Waiting on fetch checksum for ports-mgmt/pkg === /!\ WARNING /!\ pkg_install EOL is scheduled for 2014-09-01. Please consider migrating to pkgng http://blogs.freebsdish.org/portmgr/2014/02/03/time-to-bid-farewell-to-the-old-pkg_-tools/ If you do not want to see this message again set NO_WARNING_PKG_INSTALL_EOL=yes in your make.conf [...] /usr/ports/ports-mgmt/pkg/work/pkg-1.2.6/libpkg/../external/sqlite/sqlite3.c:23598: error: 'posix_fallocate' undeclared here (not in a function) *** Error code 1 1 error *** Error code 2 1 error === Compilation failed unexpectedly. At this point, I'm well and thoroughly stuck. ___ 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
Re: Pseudo-TTY Issues with FBSD 10 Snapshot?
Hi Dimitry, On 06/04/2013 12:44 AM, Dimitry Andric wrote: On Jun 4, 2013, at 06:52, Janky Jay jan...@unfs.us wrote: So, I'm unsure if this is related to a difference in pseudo TTY's yet or not, but I'm having a very strange issue that I've never encountered before. Details as follows: Fresh install of FBSD 10 FreeBSD fbsd10.purplehat.org 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Mon May 13 00:54:58 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64) I've installed XFCE4 and Fluxbox as a play-around/test WM along with x11/aterm. Everything seems to be working perfectly aside from the fact that I can no longer use the 'aterm' command. Any time I try to start an instance of 'aterm', I get the following error: aterm: ca't open pseudo-tty aterm: aborting Have you tried kldload pty ? This should work for apps that still require ptys. If that works, put the following in /boot/loader.conf: pty_load=YES so it will auto-load at boot time. -Dimitry Thanks for the reply. I figured it would be something like this if the ptys were no longer available in FBSD10. I'll give this a shot later tonight and update the list with my findings. Regards, Janky Jay, III ___ 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
Re: Pseudo-TTY Issues with FBSD 10 Snapshot?
Hi Dimitry, On 06/04/2013 01:31 PM, Dimitry Andric wrote: On Jun 4, 2013, at 18:01, Janky Jay, III jan...@unfs.us wrote: On 06/04/2013 12:44 AM, Dimitry Andric wrote: On Jun 4, 2013, at 06:52, Janky Jay jan...@unfs.us wrote: ... aterm: ca't open pseudo-tty aterm: aborting Have you tried kldload pty ? This should work for apps that still require ptys. If that works, put the following in /boot/loader.conf: ... Thanks for the reply. I figured it would be something like this if the ptys were no longer available in FBSD10. They are still available, they were just removed from the default kernel config files, see this change: http://svn.freebsd.org/changeset/base/233271 -Dimitry Excellent! Again, thanks for the info. Regards, Janky Jay, III ___ 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
Re: Dropbox on FreeBSD
On 03/05/2013 05:10 AM, Joseph A. Nagy, Jr wrote: On 03/05/13 06:04, mildbeard wrote: There is a votebox on this question on the dropbox site. The petition to add FreeBSD support to dropbox is in second place on the most popular list. I find that really encouraging. The petition is actually very close to overtaking the most popular suggestion (adding support for languages other than English.) For anyone who would run Dropbox on BSD if it were natively supported, voting for this initiative may be the best way to encourage them to add such support. https://www.dropbox.com/votebox/186/add-support-for-freebsd Thanks, Erik -- View this message in context: http://freebsd.1045724.n5.nabble.com/Dropbox-on-FreeBSD-tp5770683p5792802.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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 I have given all my votes to that petition at least twice in the past several months. I'll do so again and again until it's in ports with native support. I have nearly 8GB of free space on Dropbox going to waste... Same! I've been voting this up for quite some time. All my votes are dedicated to this. Hopefully it will be implemented soon. Just keep the votes coming and I'm sure they'll take it seriously at some point. Regards, Janky Jay, III ___ 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
Re: Dropbox on FreeBSD
On 03/05/2013 11:18 AM, Jerry wrote: On Tue, 05 Mar 2013 10:37:17 -0700 Janky Jay, III articulated: Same! I've been voting this up for quite some time. All my votes are dedicated to this. Hopefully it will be implemented soon. Just keep the votes coming and I'm sure they'll take it seriously at some point. Interestingly enough, I worked on a project a while ago that had a somewhat similar voting setup. However, since it was determined in advance that some people would inevitable attempt to inflate the actual voting total by voting numerous times, they put safeguards in place. One was to eliminate multiple votes from the same IP I believe. Hrm. That sounds silly. The Dropbox voting actually encourages it's users to use all their votes however they see fit. If you want to use them all towards one item, go for it. You're only allowed a certain number of votes, though. So, that's the only way they limit it. Regards, Janky Jay, III ___ 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
Re: Dropbox on FreeBSD
On 03/05/2013 12:20 PM, Wojciech Puchar wrote: place. One was to eliminate multiple votes from the same IP I believe. Hrm. That sounds silly. The Dropbox voting actually encourages it's can anyone explain me what is so great in that software. got into webpage, and it looks like detailless advert just like plenty of others. Found that it simplify sharing, get quite bored after trying to find out WHAT and HOW it actually provides. It really isn't anything super fantastic. In fact, the only thing I really use it for is it's auto-upload feature for my phone. This way, even if I delete images or other files they are always accessible via Dropbox. It's also handy for sharing files between a lot of devices as well, I suppose. *shrug* Regards, Janky Jay, III ___ 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
Re: PR's not being picked up (Was Re: becoming a port committor)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/21/2010 10:26 PM, Charlie Kester wrote: On Sun 21 Nov 2010 at 20:09:23 PST Beech Rintoul wrote: That is correct, although it is possible to use a unified diff with the -N flag against a non existent source. The problem is too many contributors send in update pr's in shar format which are a real PITA to deal with from our end. You may notice that many pr's aren't picked up by committers for just that reason. Almost anyone who is an only semi-serious port maintainer (meaning they only have a select few number of ports to maintain and are only trying to contribute/participate) knows that maybe this issue is due to the porter's handbook. Specifically http://www.freebsd.org/doc/en/books/porters-handbook/porting-submitting.html which blatantly states that all submissions whether they are new OR updates be submitted in shar format. Maybe the commiters should bring this up and have a few less to deal with..? Just a suggestion. Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzqBzgACgkQGK3MsUbJZn5X/gCfbTgIyt4KEyI6ebtYmjm/DUk5 L2AAn28d2RCorQB4lm3KBGIqp9MHTxWZ =azIy -END PGP SIGNATURE- ___ 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
Re: FreeBSD Port: maia-1.0.2a_3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Martin, On 05/13/2010 11:38 AM, Martin Turgeon wrote: Le 2010-05-11 18:36, Janky Jay, III a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Darrell, Darrell Betts wrote: Hey Jay, I have been in contact with the author of Maia Mailguard and he is aware of the trouble with his program and PHP 5.3 he advised me that a new version will be out shortly 1.0.3. Hope you are still maintaining the port as I stiil use your guide to setup mail servers for a few of my friends. Since the update of PHP 5.3 Maia wil no longer work. Just giving you an update I've been checking into this quite a bit lately and I'm hoping the 1.0.3 version of Maia Mailguard is released soon as well. As far as Maia not working with PHP 5.3, it appears it is limited to Maia's PHP web interface and a couple of the daily reminders only and does not effect Maia's performance on the mail server itself. So, if Maia is still able to perform its main duty by processing and databasing spam, I don't think it would be prudent to mark the port as BROKEN just yet. As soon as I get any other info, I will most certainly begin testing the new release and most likely be looking for Maia users to test the new port before submittal. So, if you're interested, let me know! Regards, Janky Jay, III I will be happy to test the new version for you. Thanks for your work! Martin Thanks! I'm hoping to be able to release at least a test port before Maia 1.03 is released. I'll mail the list when I have something available. Thanks again! Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvzQ6cACgkQGK3MsUbJZn59yQCePTE/rwPmfwBjXxeWc/xNtdaT lpUAninlE/jMmFFt3az4+geJ5bD3kgZV =3DRh -END PGP SIGNATURE- ___ 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
Re: FreeBSD Port: maia-1.0.2a_3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Darrell, Darrell Betts wrote: Hey Jay, I have been in contact with the author of Maia Mailguard and he is aware of the trouble with his program and PHP 5.3 he advised me that a new version will be out shortly 1.0.3. Hope you are still maintaining the port as I stiil use your guide to setup mail servers for a few of my friends. Since the update of PHP 5.3 Maia wil no longer work. Just giving you an update I've been checking into this quite a bit lately and I'm hoping the 1.0.3 version of Maia Mailguard is released soon as well. As far as Maia not working with PHP 5.3, it appears it is limited to Maia's PHP web interface and a couple of the daily reminders only and does not effect Maia's performance on the mail server itself. So, if Maia is still able to perform its main duty by processing and databasing spam, I don't think it would be prudent to mark the port as BROKEN just yet. As soon as I get any other info, I will most certainly begin testing the new release and most likely be looking for Maia users to test the new port before submittal. So, if you're interested, let me know! Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvp2+oACgkQZ5znzUsaCyTK8QCfbigMkFq8/Wyu5nj0bmm4sKf7 YpIAoIpLsXEYPixiR90FGNioVzcL4QUY =30ba -END PGP SIGNATURE- ___ 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
Re: FreeBSD Port: php5-mhash-5.2.11_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi List, Raphael Becker wrote: On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote: Hey, I just updated ports on a few machines and the CLI version of php dumps its core rather than end nicely. The mhash module appears to be the trigger (an extensions.ini with only mhash causes failure, all others minus mhash: no failure). php coredumps here too, but uncommenting mhash.so from extensions.ini doesn't change this. Diabling all modules will show no segfault. It seems there is more than one defect .so from the following list: perl.so radius.so fileinfo.so gettext.so pdf.so hash.so json.so sockets.so iconv.so mbstring.so bz2.so pcre.so posix.so ctype.so zlib.so calendar.so bcmath.so imap.so ldap.so ftp.so zip.so openssl.so session.so dba.so soap.so xml.so wddx.so xmlwriter.so simplexml.so readline.so mhash.so tokenizer.so curl.so filter.so exif.so mcrypt.so spl.so sqlite.so xmlrpc.so mysql.so mysqli.so gmp.so dom.so xmlreader.so pdo.so pcntl.so pdo_mysql.so gd.so xsl.so pdo_sqlite.so Any idea? I'm having the same problem here. GDB doesn't seem to be much help as it doesn't mention any of the extension.ini modules in the output. However, all of this /DID/ happen after I updated textproc/libxml2. Might have something to do with it. *shrugs* I'm playing with it now. Below is the GDB output. # gdb `which php` php.core Wed 16, 6:17PM GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /lib/libz.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.4 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28f79410 in ?? () (gdb) bt #0 0x28f79410 in ?? () #1 0x285b75eb in pthread_once () from /lib/libc.so.7 #2 0x28346162 in xmlIsMainThread () from /usr/local/lib/libxml2.so.5 #3 0x28345717 in __xmlLastError () from /usr/local/lib/libxml2.so.5 #4 0x282d1847 in xmlResetLastError () from /usr/local/lib/libxml2.so.5 #5 0x282d88df in xmlCleanupParser () from /usr/local/lib/libxml2.so.5 #6 0x080844eb in php_libxml_shutdown () #7 0x0808451b in zm_shutdown_libxml () #8 0x0814b49e in module_destructor () #9 0x08151804 in zend_hash_apply_deleter () #10 0x08151a48 in zend_hash_graceful_reverse_destroy () #11 0x08147d1e in zend_shutdown () #12 0x0810612f in php_module_shutdown () #13 0x081c4100 in main () (gdb) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksplV8ACgkQGK3MsUbJZn4JFwCdG+4M55KK2bR+vLRUpad97laQ MAEAnjT15UEyBVNw78TjLLqKAvIAulf7 =nRng -END PGP SIGNATURE- ___ 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
Re: FreeBSD Port: php5-mhash-5.2.11_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi List, Janky Jay, III wrote: Hi List, Raphael Becker wrote: On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote: Hey, I just updated ports on a few machines and the CLI version of php dumps its core rather than end nicely. The mhash module appears to be the trigger (an extensions.ini with only mhash causes failure, all others minus mhash: no failure). php coredumps here too, but uncommenting mhash.so from extensions.ini doesn't change this. Diabling all modules will show no segfault. It seems there is more than one defect .so from the following list: perl.so radius.so fileinfo.so gettext.so pdf.so hash.so json.so sockets.so iconv.so mbstring.so bz2.so pcre.so posix.so ctype.so zlib.so calendar.so bcmath.so imap.so ldap.so ftp.so zip.so openssl.so session.so dba.so soap.so xml.so wddx.so xmlwriter.so simplexml.so readline.so mhash.so tokenizer.so curl.so filter.so exif.so mcrypt.so spl.so sqlite.so xmlrpc.so mysql.so mysqli.so gmp.so dom.so xmlreader.so pdo.so pcntl.so pdo_mysql.so gd.so xsl.so pdo_sqlite.so Any idea? I'm having the same problem here. GDB doesn't seem to be much help as it doesn't mention any of the extension.ini modules in the output. However, all of this /DID/ happen after I updated textproc/libxml2. Might have something to do with it. *shrugs* I'm playing with it now. Below is the GDB output. # gdb `which php` php.core Wed 16, 6:17PM GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /lib/libz.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.4 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28f79410 in ?? () (gdb) bt #0 0x28f79410 in ?? () #1 0x285b75eb in pthread_once () from /lib/libc.so.7 #2 0x28346162 in xmlIsMainThread () from /usr/local/lib/libxml2.so.5 #3 0x28345717 in __xmlLastError () from /usr/local/lib/libxml2.so.5 #4 0x282d1847 in xmlResetLastError () from /usr/local/lib/libxml2.so.5 #5 0x282d88df in xmlCleanupParser () from /usr/local/lib/libxml2.so.5 #6 0x080844eb in php_libxml_shutdown () #7 0x0808451b in zm_shutdown_libxml () #8 0x0814b49e in module_destructor () #9 0x08151804 in zend_hash_apply_deleter () #10 0x08151a48 in zend_hash_graceful_reverse_destroy () #11 0x08147d1e in zend_shutdown () #12 0x0810612f in php_module_shutdown () #13 0x081c4100 in main () (gdb) I take this back. Removing extension=mhash.so from my /usr/local/etc/php/extensions.ini file does, in fact, exit without a core dump. However, mhash is required by SquirrelMail along with some of its plugins. I'm unsure how this will effect SquirrelMail, but regardless of where I place the mhash.so extension in the list, it still core dumps (I've tried every possible position.) Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkspmhEACgkQGK3MsUbJZn5lHgCbBvHqMlZ0djwxkdC1dvs5yBQ3 cIUAn3ZS4S5ad609JNI3qgQWeK4w5iym =2XqW -END PGP SIGNATURE- ___ 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
Re: DragonFlyBSD mail agent
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Michel. By default, FreeBSD's Sendmail that comes in base already delivers mail to local users and reads the aliases file also. It supports configuring a smarthost as well. Unless there are some highly desired features in the DragonFlyBSD mail agent, I seriously doubt there will be any migration to it from Sendmail in the near future. Regards, Janky Jay, III Michel Talon wrote: Hello, would it not be interesting to have the DragonFlyBSD mail agent in FreeBSD? It is a very simple mail agent, like ssmtp, but with some more features: it can either deliver mail locally for local users or send all other mail to a smarthost, and reads the aliases file. Hence it fulfills the needs of the person who wants a small mail agent for receiving periodic root mail, and wants to send the occasional without too much fuss. It is much simpler than sendmail, postfix or exim. For simplicity i have a tarball here: http://www.lpthe.jussieu.fr/~talon/dma.tgz it compiles out of the box, and it is easy to figure out how to use it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJZh5pGK3MsUbJZn4RAhHMAJ4j6lQ3gDkye5ciegdf2Zc5iSPSFACfeLhm qXqX5PutiNLFKzKklcvyE+M= =N9jA -END PGP SIGNATURE- ___ 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
Re: DragonFlyBSD mail agent
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Michel. Ah! Okay. This makes much more sense... Its not a problem at all to port the mail agent to FreeBSD. Just create a port, test and submit it and voila! Sorry for the misunderstanding earlier... Regards, Janky Jay, III Michel Talon wrote: Janky Jay, III wrote: By default, FreeBSD's Sendmail that comes in base already delivers mail to local users and reads the aliases file also. It supports configuring a smarthost as well. Unless there are some highly desired features in the DragonFlyBSD mail agent, I seriously doubt there will be any migration to it from Sendmail in the near future. I was not speaking of replacing sendmail in the base system, only on offering this mail agent in the *ports*, this is why i posted in freebsd-ports. I should have been clearer. This mail agent doesn't offer anything compelling compared to sendmail, only it is much smaller and presumably more secure. For example if you want a mail agent in a jail, you can envision to use this one instead of sendmail because it is much lighter. Yes i know ssmtpd could do the same, more or less but this one has a little more flexibility without falling in the complexity of the big ones. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJZlFIGK3MsUbJZn4RAgOSAJ0VOtSEKaZHXlKaeQIUoI5PuR64KACfTOcx N3WqR0rQ6S7pjolzWEuKhy4= =doPU -END PGP SIGNATURE- ___ 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
Re: DragonFlyBSD mail agent
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Sam. Of course. Once the port is submitted via a PR, it will be looked over and committed. Check out the FreeBSD Porter's Handbook at http://www.freebsd.org/doc/en/books/porters-handbook/ for more information about how to create and submit a port. Regards, Janky Jay, III Sam Fourman Jr. wrote: I see no reason for it not to be in ports. If it's useful like you described above then I'm sure other people will make use of it and be glad it is maintained in the ports tree. If you're willing to maintain it please submit a PR with your work. Sweet, is anyone with commit access willing to commit it to the ports tree? Sam Fourman Jr. ___ 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJZmOVGK3MsUbJZn4RAsJ/AJ9HMdsYxlrQoeUmJwHSqiH9viwr3gCfYcLO D+p/0l8w2RHStvu2yLYRrZU= =19dY -END PGP SIGNATURE- ___ 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
Re: portupgrade fails - how to fix?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Not sure how well this work as a 'workaround', but, being as I use ZSH as my shell, I always wrap anything I'm specifically upgrading using portupgrade with single quotes. IE: portupgrade -rR 'some-port-2.4.1_1' 'some-other-port-1.0.5_1,3' I haven't had any issues with this at all. Can anyone confirm if specifying the complete port name wrapped in single quotes allows portupgrade to finish successfully? Regards, Janky Jay, III Rainer Hurling wrote: I have the same trouble with portupgrade some times: Am 07.10.2008 10:21 (UTC+1) schrieb Parv: Mind that I am looking at the problem purely from a programmer's perspective. I am a rather light user of portupgrade (mainly pkgbd -F) don't upgrade the port itself much. With that out of the way ... in message [EMAIL PROTECTED], wrote Torfinn Ingolfsen thusly... And here portupgrade fails again, on another machine: Is your version of portupgrade is the latest in the ports? (So that I can install the same investigate.) [EMAIL PROTECTED] portupgrade -R nasm pcre xterm mplayer gscan2pdf ImageMagick What are the exact names of the ports|packages installed? Many ways to list; here is a simple one ... sh pkg_info -Qox nasm pcre xterm mplayer gscan2pdf ImageMagick \ | sed -e 's/:/ /' # Type exit to exit /bin/sh session; missing here as it might # actually exit your actual shell session. /usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:74:in `initialize': : Not in due form: name-version (ArgumentError) from /usr/local/sbin/portupgrade:614:in `new' Seems like portupgrade is dying when a port name-version format does not match the expected regular expression. Or, the program encounters a non-port string. I think, Parv is right here. For example in some cases portupgrade fails, when the port name is not clear enough. I just saw that 'portupgrade -R gimp' failed, when there are 'gimp-app' and 'gimp' installed and portupgrade had to find the right port. Rainer As always, a single port as the argument to portupgrade doesn't fail. If portupgrade is indeed successful individually for all the above listed ports, then the second scenario is more likely (the non-port thing one). - Parv ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFI67SGGK3MsUbJZn4RAjNYAJ0ZNy67xbtOLr5z2RI9LewLWHH8fQCeKMeH uptpup+aiMAI+qXqjiDfhsw= =+MDn -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
