a new type of reducer

[zhangfeng]

Hello, manager:
We have recently developed a new type of reducer.
If you are interested, please send me a mail.
z...@torkdrive.com
zhang feng
Sincerely




 
___
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"

icap protocol error

[genesis lubrigas]

I am using pfsense and its package squid is having problem with
squidclamav Clamav c-icap service and redirector for Squid and
c-icap-modules Modules for c-icap: virus_scan and srv_url_check.

When I enable the antivirus of squid proxy, the browser will show ICAP
PROTOCOL ERROR.

The pfsense version I am using is 2.3.2 and it is using FreeBSD 10.3-RELEASE-p5.

I wrote this email because it says "There is no maintainer for this
port.  Any concerns regarding this port should be directed to the
FreeBSD Ports mailing list via po...@freebsd.org".  I hope this can be
fixed.  Thank you.  And more power to freebsd.


Sincerely,

Genesis Lubrigas
___
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: Ephemeral /var/run and creating port-specific subdir at service startup time

[Roger Leigh]

On 01/09/16 00:12, Mark Martinec wrote:

I prefer to have a /var/run file system reside on a tmpfs
as its contents is small and ephemeral in its nature (like
pid files, lock files, sockets), need not be preserved across
reboots, and should not have to depend on any physical disk.

The problem is that some programs/services/ports like to create
their own subdirectory under /var/run. This works fine if such
subdirectory is created (when missing) by their rc.d script,
such as salt, dbus, jenkins, clamav-clamd, isc-dhcpd, kibana.

Unfortunately there are other ports which create a subdirectory
under /var/run at the installation time (pkg install). In this
case their subdirectory is missing on a reboot when /var/run
is re-created afresh, and they fail to start.

So my question is: are such ports (like influxdb, grafana3)
which do not create their subdirectory at a startup time
in error and a bug report is warranted, or am I wrong in
expecting that /var/run may be ephemeral and is such a setup
(as is common in Linux) unsupported?


I can't speak for FreeBSD policies, but as the person who implemented 
/run on Debian GNU/Linux for sysvinit (/var/run on tmpfs essentially), 
we had to audit every package and ensure that all packages created the 
directories they needed if they weren't present.  We retained the 
cleaning of /var/run on boot to ensure a clean slate, so having it on 
tmpfs was never mandatory, but if you did then it would just work. 
However, we did have boot-time cleaning of /var/run for a while before 
we introduced the tmpfs, so I can't recall doing anything but a handful 
of minor tweaks.


Doing the same for FreeBSD wouldn't be too hard if you can automatically 
scan the ports tree or build package contents to identify and fix any 
packages which are providing static files.



Regards,
Roger
___
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"

Ephemeral /var/run and creating port-specific subdir at service startup time

[Mark Martinec]

I prefer to have a /var/run file system reside on a tmpfs
as its contents is small and ephemeral in its nature (like
pid files, lock files, sockets), need not be preserved across
reboots, and should not have to depend on any physical disk.

The problem is that some programs/services/ports like to create
their own subdirectory under /var/run. This works fine if such
subdirectory is created (when missing) by their rc.d script,
such as salt, dbus, jenkins, clamav-clamd, isc-dhcpd, kibana.

Unfortunately there are other ports which create a subdirectory
under /var/run at the installation time (pkg install). In this
case their subdirectory is missing on a reboot when /var/run
is re-created afresh, and they fail to start.

So my question is: are such ports (like influxdb, grafana3)
which do not create their subdirectory at a startup time
in error and a bug report is warranted, or am I wrong in
expecting that /var/run may be ephemeral and is such a setup
(as is common in Linux) unsupported?

  Mark
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
emulators/mame  | 0.166   | mame0177
+-+
emulators/mess  | 0.166   | mame0177
+-+
lang/sbcl   | 1.3.1   | 1.3.9
+-+
net/jsch| 0.1.53  | 0.1.54
+-+
print/lilypond-devel| 2.19.11 | 2.19.47
+-+
textproc/pear-File_MARC | 1.1.2   | 1.1.3
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mariadb10* ports broken on 9.x since last commit

[Doug Barton]

August 31, 2016 12:37 AM, "Bernard Spil"  wrote:
> On 2016-08-30 17:45, Doug Barton wrote:
> 
>> Since the last commit to the mariadb10* ports the resulting binaries
>> dump core on 9.3-RELEASE-p43, even for a simple --help option. I am
>> assuming that is not the intended result 
>> Doug
> 
> Hi Doug,
> 
> Nope, that is not intended. Assume this is the 10.0.27 update? I did build 
> them on 9.3 but have not
> checked the resulting binaries... Will need some time to investigate!
> 
> https://brnrd.eu/poudriere/build.html?mastername=93amd64-svn=2016-08-29_20h14m28s

Thanks Bernard. 

It turns out that the actual problem was binutils. I backed up several 
revisions of mariadb, past the previous working version, and had the same 
symptoms. Then I started on the deps that had changed at the same time, and 
fortunately I guessed right on the first one. 

Backing up to -r{2016-08-25} on binutils got mariadb working with the latest 
version. 

Doug
___
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: FreeBSD Port: noip-2.1.9_3

[olli hauer]

On 2016-08-31 17:30, Stanislaw Halik wrote:
> On 2016-08-31 Wed 17:21, olli hauer wrote:
>> I think this will work for you.
>>
>> The update interval can be adjusted (default is 30 days).
>> In the patch example I've chosen half of the interval, so there is time left 
>> in case you are offline for an unforeseen reason
>>
>> Index: Makefile
>> ===
>> --- Makefile(revision 421168)
>> +++ Makefile(working copy)
>> @@ -25,6 +25,12 @@
>>
>>  OPTIONS_DEFINE=DOCS
>>
>> +FORCE_INTERVAL=14  # days until IP update is forced
>> +
>> +post-patch:
>> +   ${REINPLACE_CMD} -e '/define 
>> FORCE_INTERVAL/s/30/${FORCE_INTERVAL}/g' \
>> +   ${WRKSRC}/noip2.c
>> +
>>  do-install:
>> ${INSTALL_PROGRAM} ${WRKSRC}/noip2 ${STAGEDIR}${PREFIX}/bin
>> ${MKDIR} ${STAGEDIR}${DOCSDIR}
> 
> Hey,
> 
> Please send this as a PR.
> 
> I'd personally choose a value of 7 days but this is okay.
> 
> sh

I don't use the tool myself (having a static assigned network) and I'm even not 
sure if it will work.

So I suggest James can test it (suspecting there is a ways to see the last 
update time on the noip portal) and if it works for him he can submit the patch 
as PR

-- 
olli
___
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: FreeBSD Port: noip-2.1.9_3

[Stanislaw Halik]

On 2016-08-31 Wed 17:21, olli hauer wrote:

I think this will work for you.

The update interval can be adjusted (default is 30 days).
In the patch example I've chosen half of the interval, so there is time left in 
case you are offline for an unforeseen reason

Index: Makefile
===
--- Makefile(revision 421168)
+++ Makefile(working copy)
@@ -25,6 +25,12 @@

 OPTIONS_DEFINE=DOCS

+FORCE_INTERVAL=14  # days until IP update is forced
+
+post-patch:
+   ${REINPLACE_CMD} -e '/define FORCE_INTERVAL/s/30/${FORCE_INTERVAL}/g' \
+   ${WRKSRC}/noip2.c
+
 do-install:
${INSTALL_PROGRAM} ${WRKSRC}/noip2 ${STAGEDIR}${PREFIX}/bin
${MKDIR} ${STAGEDIR}${DOCSDIR}


Hey,

Please send this as a PR.

I'd personally choose a value of 7 days but this is okay.

sh

___
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: FreeBSD Port: noip-2.1.9_3

[olli hauer]

On 2016-08-31 13:17, James A. McGuire wrote:
> Hi there,
> 
> Since no-ip introduced their policy to remove non-updated subdomains every
> 30 days.  I have to manually go to the no-ip website and confirm that I
> wish to keep my subdomain.  I believe the reason for this is that my ISP is
> only updating my dynamic IP address every 60-90 days, and I believe that
> the no-ip client is therefore not sending updates to no-ip.
> 
> Is this the case and if so, can this behaviour be modified so that the
> client will issue an update to the no-ip servers within 30 days even if the
> IP has not changed?
> 
> Many thanks,
> 
> James

I think this will work for you.

The update interval can be adjusted (default is 30 days).
In the patch example I've chosen half of the interval, so there is time left in 
case you are offline for an unforeseen reason

Index: Makefile
===
--- Makefile(revision 421168)
+++ Makefile(working copy)
@@ -25,6 +25,12 @@

 OPTIONS_DEFINE=DOCS

+FORCE_INTERVAL=14  # days until IP update is forced
+
+post-patch:
+   ${REINPLACE_CMD} -e '/define FORCE_INTERVAL/s/30/${FORCE_INTERVAL}/g' \
+   ${WRKSRC}/noip2.c
+
 do-install:
${INSTALL_PROGRAM} ${WRKSRC}/noip2 ${STAGEDIR}${PREFIX}/bin
${MKDIR} ${STAGEDIR}${DOCSDIR}

___
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: Split irc/quassel into irc/quassel-client and irc/quassel-core

[Chris Rees]

Ben Woods wrote:

Hi Max,

I run quassel on my home FreeBSD server and again on my FreeBSD laptop.

Because I do not want to bring in the numerous dependencies related with
the client application to my server, I unset the MONO and CLIENT options in
my poudriere make.conf. But of course that means I cant use my poudriere
built packages to install quassel on my laptop (no client).

What do you think of either splitting irc/quassel into irc/quassel-client
and irc/quassel-core, or having a master port and slave ports?

Regards,
Ben


May I suggest just having a slave port for quassel-core?  The client and 
mono appear to have the heaviest dependencies.


Example at https://www.bayofrum.net/~crees/patches/quassel-core.diff 
(It's ready to commit, so if you're happy Max it can go in) 



Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Maintainership Status for PHP 5.6

[Torsten Zuehlsdorff]

On 26.08.2016 21:38, Kurt Jaeger wrote:

Hi!


About resetting the maintainer, I'll ask around.



The rules are pretty clear:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer.html


It's more about: Who's willing to do it ?


As talked in private: i could/will do, since i already take over 
maintainership for lang/php70.
Currently creation of an php@ group is discussed (which should take over 
the port than?).


The lang/php56-update hit master yesterday. I'm currently waiting for 
MFH-approval. Thanks to Kurt for writing the patch.


Greetings,
Torsten
___
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: FreeBSD Port: noip-2.1.9_3

[Kurt Jaeger]

Hi!

> On 2016-08-31 Wed 13:36, Kurt Jaeger wrote:
> >> It can sure be changed with a patch. I'd like however to wait for
> >> someone with ports commit bit to comment as to whether that change lies
> >> within the scope of what the ports tree does. My understanding is that
> >> the ports tree generally doesn't introduce new functionality.
> >
> > I suggest to add that feature with a patch and then submit that
> > change upstream so that upstream adds that feature, too.
> 
> Hey,
> 
> Last upstream update was in 2009. The source tarball's hosted by ehaupt@ 
> since the original URI returns 404.

Then adding the patch is the way to go and asking ehaupt to update
the distfile with the patch...

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: noip-2.1.9_3

[Kubilay Kocak]

On 31/08/2016 9:42 PM, Stanislaw Halik wrote:
> On 2016-08-31 Wed 13:36, Kurt Jaeger wrote:
>>> It can sure be changed with a patch. I'd like however to wait
>>> for someone with ports commit bit to comment as to whether that
>>> change lies within the scope of what the ports tree does. My
>>> understanding is that the ports tree generally doesn't introduce
>>> new functionality.
>> 
>> I suggest to add that feature with a patch and then submit that 
>> change upstream so that upstream adds that feature, too.
> 
> Hey,
> 
> Last upstream update was in 2009. The source tarball's hosted by
> ehaupt@ since the original URI returns 404.

Ah, so we're upstream ;)

> sh

___
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: FreeBSD Port: noip-2.1.9_3

[Kubilay Kocak]

On 31/08/2016 9:33 PM, Stanislaw Halik wrote:
> Hey,
> 
> It can sure be changed with a patch. I'd like however to wait for 
> someone with ports commit bit to comment as to whether that change
> lies within the scope of what the ports tree does. My understanding
> is that the ports tree generally doesn't introduce new
> functionality.

New functionality is introduced all the time, and I'm not aware of a
policy (defacto or official) that prevents it, other than those limiting
merges to the quarterly branch to bugfixes or security updates. Can you
elaborate on what you mean?

> What you can do however without any ports/ commits is to stop the 
> daemon, clobber noip's internal state in the right way, then restart
> it to force an update to be issued, weekly or daily.

Does the client provide no existing way of setting an update interval or
similar? What other methods could achieve it, or emulate it?

Does the no-ip client provide 'one shot' invocation so updates could be
cron'd on a custom interval?

I agree with Kurt that addition of an 'update interval' feature or
similar upstream would be the proper permanent resolution.

./koobs




___
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: FreeBSD Port: noip-2.1.9_3

[Stanislaw Halik]

On 2016-08-31 Wed 13:36, Kurt Jaeger wrote:

It can sure be changed with a patch. I'd like however to wait for
someone with ports commit bit to comment as to whether that change lies
within the scope of what the ports tree does. My understanding is that
the ports tree generally doesn't introduce new functionality.


I suggest to add that feature with a patch and then submit that
change upstream so that upstream adds that feature, too.


Hey,

Last upstream update was in 2009. The source tarball's hosted by ehaupt@ 
since the original URI returns 404.


sh

___
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: FreeBSD Port: noip-2.1.9_3

[Kurt Jaeger]

Hi!

> It can sure be changed with a patch. I'd like however to wait for 
> someone with ports commit bit to comment as to whether that change lies 
> within the scope of what the ports tree does. My understanding is that 
> the ports tree generally doesn't introduce new functionality.

I suggest to add that feature with a patch and then submit that
change upstream so that upstream adds that feature, too.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: noip-2.1.9_3

[Stanislaw Halik]

On 2016-08-31 Wed 13:17, James A. McGuire wrote:

Since no-ip introduced their policy to remove non-updated subdomains
every 30 days.  I have to manually go to the no-ip website and confirm
that I wish to keep my subdomain.  I believe the reason for this is that
my ISP is only updating my dynamic IP address every 60-90 days, and I
believe that the no-ip client is therefore not sending updates to no-ip.

Is this the case and if so, can this behaviour be modified so that the
client will issue an update to the no-ip servers within 30 days even if
the IP has not changed?


Hey,

It can sure be changed with a patch. I'd like however to wait for 
someone with ports commit bit to comment as to whether that change lies 
within the scope of what the ports tree does. My understanding is that 
the ports tree generally doesn't introduce new functionality.


What you can do however without any ports/ commits is to stop the 
daemon, clobber noip's internal state in the right way, then restart it 
to force an update to be issued, weekly or daily.


cheers,
sh
___
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 Port: noip-2.1.9_3

[James A. McGuire]

Hi there,

Since no-ip introduced their policy to remove non-updated subdomains every
30 days.  I have to manually go to the no-ip website and confirm that I
wish to keep my subdomain.  I believe the reason for this is that my ISP is
only updating my dynamic IP address every 60-90 days, and I believe that
the no-ip client is therefore not sending updates to no-ip.

Is this the case and if so, can this behaviour be modified so that the
client will issue an update to the no-ip servers within 30 days even if the
IP has not changed?

Many thanks,

James
___
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"

apache-solr PR: 201455 (I think 212104 blocks usage of apache-solr)

[Matthias Fechner]

Dear all,


I initiated a long time ago a bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201455

As the new version was broken, I installed the old 4.x version and
locked the package.

I just downloaded manually the 6.2 version into /usr/local/src and
started it from there (it works perfectly fine after defining the
JAVA_HOME=/usr/local/openjdk8/jre/).
Today I have a little time to look into this issue and upgraded to
version 5.5.2 which is now in ports.

I just wanted to test the new version but I cannot test it as for bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212104

(no java executable is existing in /usr/local/bin/ and therefor the
startup script will not work)

Does anyone know if the solr port is working now?

Thanks
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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: Run Dependencies to llvm (for e.g. graphics/libEGL)

[Matthias Fechner]

Am 31.08.2016 um 12:06 schrieb Fernando Herrero Carrón:
> It probably makes sense, yes: http://www.mesa3d.org/llvmpipe.html
>
> LLVM is being used in more and more projects to optimize dynamically
> generated code, in this case software 3D rendering.
>

thanks, good to know.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Run Dependencies to llvm (for e.g. graphics/libEGL)

[Fernando Herrero Carrón]

It probably makes sense, yes: http://www.mesa3d.org/llvmpipe.html

LLVM is being used in more and more projects to optimize dynamically
generated code, in this case software 3D rendering.

2016-08-31 12:01 GMT+02:00 Matthias Fechner :

> Dear all,
>
>
> I just saw that I have for some installed packages llvm as run
> dependency (e.g. graphics/libEGL) that it has a run dependency to llvm36:
>
> cd /usr/ports
>
> make search name=libEGL
>
> R-deps: damageproto-1.2.1 ... llvm37-3.7.1_3 ...
>
>
> Does this really makes sense or is this a bug in one of the dependencies?
>
>
> Thanks
> Matthias
>
> --
>
> "Programming today is a race between software engineers striving to
> build bigger and better idiot-proof programs, and the universe trying to
> produce bigger and better idiots. So far, the universe is winning." --
> Rich Cook
>
>
> ___
> 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"

Run Dependencies to llvm (for e.g. graphics/libEGL)

[Matthias Fechner]

Dear all,


I just saw that I have for some installed packages llvm as run
dependency (e.g. graphics/libEGL) that it has a run dependency to llvm36:

cd /usr/ports

make search name=libEGL

R-deps: damageproto-1.2.1 ... llvm37-3.7.1_3 ...


Does this really makes sense or is this a bug in one of the dependencies?


Thanks
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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: binutils version tweak

[Mathieu Arnold]

Le 31/08/2016 à 10:35, Dewayne Geraghty a écrit :
> Would it be possible for someone to increment the PORTREVISION for
> devel/binutils.  The last three changes aren't being picked up due to a
> constant Version,Revision,Epoch sequence.  And two of these changes  are
> relevant.
> Thank-you.
From what I understand reading the commit log, and looking at the diffs,
the last three commits to it were fixes so that the port would build
again on some arch/version, there is no need to bump PORTREVISION when
no other version could exist.

-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

binutils version tweak

[Dewayne Geraghty]

Would it be possible for someone to increment the PORTREVISION for
devel/binutils.  The last three changes aren't being picked up due to a
constant Version,Revision,Epoch sequence.  And two of these changes  are
relevant.
Thank-you.
___
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: mariadb10* ports broken on 9.x since last commit

[Bernard Spil]

On 2016-08-30 17:45, Doug Barton wrote:

Since the last commit to the mariadb10* ports the resulting binaries
dump core on 9.3-RELEASE-p43, even for a simple --help option. I am
assuming that is not the intended result 

Doug


Hi Doug,

Nope, that is not intended. Assume this is the 10.0.27 update? I did 
build them on 9.3 but have not checked the resulting binaries... Will 
need some time to investigate!


https://brnrd.eu/poudriere/build.html?mastername=93amd64-svn=2016-08-29_20h14m28s

Cheers,

Bernard.
___
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"