Re: Mk/Scripts/qa.sh and DEVELOPER=yes
On Mon, Apr 14, 2014 at 07:34:04AM +0200, Matthias Andree wrote:
Am 13.04.2014 14:28, schrieb clutton:
It seems that with DEVELOPER=yes in /etc/make.conf I'm not able to
perform ordinary update routines. Removing the DEVELOPER variable fix
the problem. And probably the worst part of it that there's no error
message.
Running Q/A tests (stage-qa)
Error:
/tmp/usr/ports/devel/p5-subversion/work/stage/usr/local/lib/perl5/site_perl/5.18/mach/auto/SVN/_Core/.packlist
is referring to /tmp/usr/ports/devel/p5-subversion/work/stage
Oh, there is an error, as quoted above.
.packlist refers to a file that will no longer be present after make
clean.
Cause is that the p5-subversion port, or some part of the Perl or ports
framework, causes the .packlist to be generated with bogus contents.
Either we can fix the actual cause, or we can hack the .packlist to
strip the ${STAGEDIR} prefix, which would be the inferior approach, however.
The .packlist is cleaned for any other perl ports (done in perl5.mk)
p5-subversion should just do the same.
Bapt
pgp5EIVd0PH2_.pgp
Description: PGP signature
Re: Mk/Scripts/qa.sh and DEVELOPER=yes
On 2014-04-14 08:49, Baptiste Daroussin wrote:
On Mon, Apr 14, 2014 at 07:34:04AM +0200, Matthias Andree wrote:
Am 13.04.2014 14:28, schrieb clutton:
It seems that with DEVELOPER=yes in /etc/make.conf I'm not able to
perform ordinary update routines. Removing the DEVELOPER variable fix
the problem. And probably the worst part of it that there's no error
message.
Running Q/A tests (stage-qa)
Error:
/tmp/usr/ports/devel/p5-subversion/work/stage/usr/local/lib/perl5/site_perl/5.18/mach/auto/SVN/_Core/.packlist
is referring to /tmp/usr/ports/devel/p5-subversion/work/stage
Oh, there is an error, as quoted above.
.packlist refers to a file that will no longer be present after make
clean.
Cause is that the p5-subversion port, or some part of the Perl or ports
framework, causes the .packlist to be generated with bogus contents.
Either we can fix the actual cause, or we can hack the .packlist to
strip the ${STAGEDIR} prefix, which would be the inferior approach, however.
The .packlist is cleaned for any other perl ports (done in perl5.mk)
p5-subversion should just do the same.
Bapt
Looking on my system there are some more ports where .packlist contains
/wrkdir/...
$ find /usr/local/lib/perl5/site_perl/5.16/ -name .packlist | xargs grep
'/wrkdir' | cut -d: -f -1 | sort -u
/usr/local/lib/perl5/site_perl/5.16/mach/auto/Bundle/NetSNMP/.packlist
/usr/local/lib/perl5/site_perl/5.16/mach/auto/Git/.packlist
/usr/local/lib/perl5/site_perl/5.16/mach/auto/SVN/_Core/.packlist
This packages where build with poudriere last Saturday.
Anyway for production build I *don't* have DEVELOPER=yes set since many of the
issues (strip ...) are not related for my production environment.
olli
___
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: [ANNOUNCE] ports 2014Q2 branched
On Wed, Apr 2, 2014 at 3:56 PM, Chris H bsd-li...@bsdforge.com wrote: Hi all, I am pleased to announce that we have created the 2014Q2 branch of the ports tree. Because the first 2014Q1 branch was experimental you might not have heard of it yet. January 2014 saw the release of the first quaterly branch, intended at providing a stable and high-quality ports tree. Those stable branches are a snapshot of the head ports tree taken every 3 months and currently supported for three months, during which they receive security fixes as well as build and runtime fixes. Packages are built on regular basis on that branch (weekly) and published as usual via pkg.FreeBSD.org (/quarterly instead of the usual /latest). They are signed the same way the /latest branch is. While packages for 2014Q1 were only built for 10 (i386 and amd64) 2014Q2 will be built for both FreeBSD 9 and 10 (i386 and amd64). The first build of 2014Q2 will started this morning (wednesday at 1 am UTC) and should hit your closest mirrors very soon. On behalf of the port management team Bapt A big +1 on this! IMHO l-o-o-n-g over due. Thanks Bapt! A step towards making FreeBSD a distribution, not just a base OS anymore? :-) -- Nino ___ 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: security/sshguard-pf
On Wednesday, April 9, 2014 1:55:51 PM CEST, Dr. Michael Letzgus wrote:
Hi all,
sshguard-pf won't start any more after the ports update to
1.5_3. There are no messages in auth.log.
A manual start via command line of sshguard is successful -
so maybe there is a problem with the
rc script?
Hi.
Ran into the same issue. So - what are my next steps? Filing a PR against
ports@ seems good, but .. probably the slow route.. :)
CC'd crees@ as last committer/potentially most familiar with that stuff?
Tracking down the issue:
Same issue here:
# service sshguard start
Starting sshguard.
# service sshguard status
sshguard is not running.
Thanks, Sergey. Good start, but no error:
# sh -x /usr/local/etc/rc.d/sshguard start
snip
+ eval '/usr/sbin/daemon -cf /usr/local/sbin/sshguard -b
40:/var/db/sshguard/blacklist.db -a 40 -p 1200 -s 420 -w
/usr/local/etc/sshguard.whitelist -i '
+ /usr/sbin/daemon -cf /usr/local/sbin/sshguard -b
40:/var/db/sshguard/blacklist.db -a 40 -p 1200 -s 420 -w
/usr/local/etc/sshguard.whitelist -i
Let's remove the input/output redirection (-f)
# /usr/sbin/daemon -c /usr/local/sbin/sshguard -b
40:/var/db/sshguard/blacklist.db -a 40 -p 1200 -s 420 -w
/usr/local/etc/sshguard.whitelist -i
sshguard: option requires an argument -- i
Usage:
sshguard [-b thr:file] [-w whlst]{0,n} [-a num] [-p sec] [-s sec]
[-l source] [-f srv:pidfile]{0,n} [-i pidfile] [-v]
-b Blacklist: thr = number of abuses before blacklisting, file = blacklist
filename.
-a Number of hits after which blocking an address (40)
-p Seconds after which unblocking a blocked address (420)
-w Whitelisting of addr/host/block, or take from file if starts with /
or . (repeatable)
-s Seconds after which forgetting about a cracker candidate (1200)
-l Add the given log source to Log Sucker's monitored sources (off)
-f authenticate service's logs through its process pid, as in
pidfile
-i When started, save PID in the given file; useful for startup scripts
(off)
-v Dump version message to stderr, supply this when reporting bugs
The SSHGUARD_DEBUG environment variable enables debugging mode (verbosity
+ interactivity).
I'd say this is a bug in sshguard: Failing to start shouldn't exit with 0.
That said, it first and foremost is a bug in the port.
Looking at the rc script and the diff [1] the problem's easy enough:
${sshguard_pidfile} is passed as parameter to -i, but isn't set in the
script/has no default value. Either the related line from the previous
revision should be revived or the substitution should change to use
${pidfile}, which _is_ set.
What now? To PR or not?
Regards,
Ben
1:
http://svnweb.freebsd.org/ports/head/security/sshguard/files/sshguard.in?r1=311381r2=350643
___
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: print/cups: since update to 1.7.1: error : Send-Document client-error-document-format-not-supported
On Sun, 13 Apr 2014 20:50:01 +0400 Boris Samorodov b...@passap.ru wrote: 12.04.2014 17:16, O. Hartmann пишет: On Fri, 11 Apr 2014 08:19:45 -0400 Ajtim lum...@gmail.com wrote: On Friday 11 April 2014 13:08:33 O. Hartmann wrote: On Wed, 09 Apr 2014 02:23:58 +0400 Boris Samorodov b...@passap.ru wrote: 09.04.2014 00:25, O. Hartmann пишет: On Tue, 08 Apr 2014 23:16:33 +0400 Boris Samorodov b...@passap.ru wrote: 08.04.2014 17:42, O. Hartmann пишет: Since the update of print/cups from 1.5.X to 1.7.1 How did you do it? As it is reported in /usr/ports/UPDATING. I delete first cups-image, then did the update which reeled in all the new stuff automatically. OK, lets start from some obvious things. Did you restart cupsd while experimenting? No. Give an output for: - % type lpr lpr is /usr/local/bin/lpr pkg which /usr/local/bin/lpr /usr/local/bin/lpr was installed by package cups-base-1.7.1 % ls -l /usr/local/etc/cups -r--r--r-- 1 root wheel 2807 11 Apr 11:58 cups-browsed.conf -rw-r- 1 root cups 3197 8 Apr 17:15 cups-files.conf -rw-r- 1 root cups 3197 8 Apr 17:15 cups-files.conf.bak -rw-r- 1 root wheel 3137 11 Apr 12:02 cups-files.conf.sample -r--r--r-- 1 root wheel 9521 11 Apr 11:50 cups-pdf.conf -r--r--r-- 1 root wheel 9521 11 Apr 11:50 cups-pdf.conf.sample -rw-r- 1 root cups 3442 8 Apr 17:22 cupsd.conf -rw-r- 1 root cups 5098 8 Apr 17:20 cupsd.conf.O -rw-r- 1 root cups 3442 8 Apr 17:22 cupsd.conf.bak -rw-r- 1 root wheel 4492 11 Apr 12:02 cupsd.conf.default -r--r--r-- 1 root wheel 4492 11 Apr 12:02 cupsd.conf.sample drwxr-xr-x 2 root wheel 512 11 Apr 12:02 interfaces -r--r--r-- 1 root wheel 1875 8 Apr 19:17 mime.convs -r--r--r-- 1 root wheel 1874 11 Apr 12:02 mime.convs.sample -r--r--r-- 1 root wheel 6456 8 Apr 19:18 mime.types -r--r--r-- 1 root wheel 6455 11 Apr 12:02 mime.types.sample drwxr-xr-x 2 root cups512 11 Apr 12:02 ppd -rw--- 1 root cups 4134 8 Apr 17:33 printers.conf -rw--- 1 root cups 4134 8 Apr 14:58 printers.conf.O -rw--- 1 root cups 4134 8 Apr 17:22 printers.conf.bak -rw-r--r-- 1 root cups946 11 Apr 11:53 pstoraster.convs -r--r--r-- 1 root wheel 778 11 Apr 12:04 pstotiff.convs -r--r--r-- 1 root wheel 2084 11 Apr 12:04 pstotiff.types -r--r--r-- 1 root wheel 284 11 Apr 11:49 snmp.conf -r--r--r-- 1 root wheel 284 11 Apr 12:02 snmp.conf.sample drwx-- 2 root cups512 11 Apr 12:02 ssl % make -C /usr/ports/print/cups-client pretty-print-config -GNUTLS (whoops ... this is not the default, isn't it?) == corrected that with a new recompilation with rmconfig preceded. % grep CUPS /etc/make.conf NULL (menas: no output) % pkg info -x cups hp foo gut cups-base-1.7.1 cups-client-1.7.1 cups-filters-1.0.52 cups-image-1.7.1 cups-pdf-2.6.1_1 cups-pstoraster-8.15.4_7 cups-samba-6.0_7 gutenprint-cups-5.2.8_1 libgnomecups-0.2.3_5,1 linux-f10-cups-libs-1.3.11_1 foomatic-db-hpijs-1.4 hplip-3.14.1 kdevelop-php-1.6.0_1 kdevelop-php-docs-1.6.0_1 php5-5.4.27 swhplugins-0.4.15_4 foomatic-db-20140331 foomatic-db-engine-4.0.11,2 foomatic-db-hpijs-1.4 foomatic-filters-4.0.17 gimp-gutenprint-5.2.8 gutenprint-base-5.2.8 gutenprint-cups-5.2.8_1 gutenprint-ijs-5.2.8 - Stop cupsd, move temporary /var/log/cups/*_log to another location. Start cupsd and look for suspicious messages at /var/log/cups/* files. Nothing suspicious so far. With print/cups-filters installed, the whole cups printing system is corrupted and doesn't print a single sheet of paper (PDF/PS) normal es expected. Prior to this task, I recompiled, as you suggested, first all cups ports and afterwards hplip/foomatic. I also installed print/cups-filters before recompiling hplip/foomatic. It works for me now (FreeBSD 10.0-RELEASE): I did deinstall cups* and hplip. Than installed cups and patched hplip. First I used as usual hp-business_inkjet_3000-hpijs-pcl3.ppd.gz and it didn't work It printed:%PDF-1.4 and jobs processing never stopped. Than I removed device and installed again with -3000-ps.ppd.gz and it works but cannot print test page. I tried alternatives, but it is with all (known to me) usefull drivers for the specific printer the same result: empty pages, print job stuck in queue. I also tried most recent hplip-3.14.4 but I doubt this is the reason. I can print PDF and PS, as reported, when deinstalling/removing print/cups-filters using clients like xpdf, xdvi or printing directly via lpr -PPRINTER_NAME jobfile.ps. This fails when print/cups-filter is installed. This is rather strange. But may be this is because you use hplip which I've never used before. I used hplip before with CUPS 1.5.X with the printer of mine,
Re: FreeBSD Port: security/sshguard-pf
Am 14.04.2014 10:25, schrieb Benjamin Podszun:
Looking at the rc script and the diff [1] the problem's easy enough:
${sshguard_pidfile} is passed as parameter to -i, but isn't set in the
script/has no default value. Either the related line from the previous
revision should be revived or the substitution should change to use
${pidfile}, which _is_ set.
I just installed sshguard on one of my servers and noticed the same
problem. The program is not started due to several bugs:
1) $sshguard_pidfile vs. $pidfile as noticed by you
2) Pasing of log files to watch. They are correctly processed by
sshguard_prestart(), but the result is not pasted into the
command line. (You can manually add -l logfile options to
the command line in the rc script as a work around ...)
There are other deficiencies:
a) The documentation lacks details about the mechanism used to block
attacks. E.g. in case of IPFW, blocking rules are injected in lines
55000 to 55050. You have to adapt your ruleset in such a way, that
any to-be-blocked service is only enabled at a later line, or the
blocking is ineffective. This port range should be mentioned at
least in the pkg message for ipfw. Better would be a section in
the man page, which explains the mechanism used by each backend.
b) The security/sshguard-ipfw port is marked as NO_STAGE=no, while
security/sshguard seems to work just fine with staging enabled.
This is probably an oversight: when sshguard was fixed/verified
for staging, the sub-ports where not marked as staging clean.
c) The MAKE_ARGS variable mention ACLOCAL, AUTOCONF and AUTOMAKE, but
no dependencies are registered for any of them.
d) The master port's Makefile lists hosts, pf, and ipfw as possible
backends, selected by SSHGUARDFW, but does not mention ipfilter
as the fourth supported backend.
I did not have time to check the code quality of the parser. I'm a
bit suspicious, that it might be possible to attack sshguard via
parameters passed under control of an attacker.
If you create a PR, you may want to add these points to the PR ...
Regards, STefan
___
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: security/sshguard-pf
On 14 April 2014 10:36:18 BST, Stefan Esser s...@freebsd.org wrote:
Am 14.04.2014 10:25, schrieb Benjamin Podszun:
Looking at the rc script and the diff [1] the problem's easy enough:
${sshguard_pidfile} is passed as parameter to -i, but isn't set in
the
script/has no default value. Either the related line from the
previous
revision should be revived or the substitution should change to use
${pidfile}, which _is_ set.
I just installed sshguard on one of my servers and noticed the same
problem. The program is not started due to several bugs:
1) $sshguard_pidfile vs. $pidfile as noticed by you
This one's my fault, sorry.
2) Pasing of log files to watch. They are correctly processed by
sshguard_prestart(), but the result is not pasted into the
command line. (You can manually add -l logfile options to
the command line in the rc script as a work around ...)
Don't think this one is, but I'll investigate.
Chris
There are other deficiencies:
a) The documentation lacks details about the mechanism used to block
attacks. E.g. in case of IPFW, blocking rules are injected in lines
55000 to 55050. You have to adapt your ruleset in such a way, that
any to-be-blocked service is only enabled at a later line, or the
blocking is ineffective. This port range should be mentioned at
least in the pkg message for ipfw. Better would be a section in
the man page, which explains the mechanism used by each backend.
b) The security/sshguard-ipfw port is marked as NO_STAGE=no, while
security/sshguard seems to work just fine with staging enabled.
This is probably an oversight: when sshguard was fixed/verified
for staging, the sub-ports where not marked as staging clean.
c) The MAKE_ARGS variable mention ACLOCAL, AUTOCONF and AUTOMAKE, but
no dependencies are registered for any of them.
d) The master port's Makefile lists hosts, pf, and ipfw as possible
backends, selected by SSHGUARDFW, but does not mention ipfilter
as the fourth supported backend.
I did not have time to check the code quality of the parser. I'm a
bit suspicious, that it might be possible to attack sshguard via
parameters passed under control of an attacker.
If you create a PR, you may want to add these points to the PR ...
Regards, STefan
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ www/groupoffice | 3.7.24 | 5.0.54 +-+ 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 http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[FIX] Re: FreeBSD Port: security/sshguard-pf
Am 14.04.2014 10:25, schrieb Benjamin Podszun:
I'd say this is a bug in sshguard: Failing to start shouldn't exit with 0.
That said, it first and foremost is a bug in the port.
Looking at the rc script and the diff [1] the problem's easy enough:
${sshguard_pidfile} is passed as parameter to -i, but isn't set in the
script/has no default value. Either the related line from the previous
revision should be revived or the substitution should change to use
${pidfile}, which _is_ set.
The attached diff fixes the problems in the sshguard rc file. I have
replaced occurences of ${name} with sshguard, in accordance with
newer rc script style conventions. The diff has to be applied within
the files sub-directory of the sshguard port.
The other problems of this port (see previous mail) are not fixed and
should still be addressed ...
Regards, STefan
--- sshguard.in 2014-04-09 10:49:16.292610649 +0200
+++ /usr/local/etc/rc.d/sshguard2014-04-14 12:18:00.867681882 +0200
@@ -64,24 +64,23 @@
name=sshguard
rcvar=sshguard_enable
-load_rc_config $name
+load_rc_config sshguard
: ${sshguard_enable:=NO}
-: ${sshguard_blacklist=40:/var/db/sshguard/blacklist.db}
-: ${sshguard_safety_thresh=40}
-: ${sshguard_pardon_min_interval=1200}
-: ${sshguard_prescribe_interval=420}
-: ${sshguard_whitelistfile=%%PREFIX%%/etc/sshguard.whitelist}
-: ${sshguard_watch_logs=/var/log/auth.log:/var/log/maillog}
-
-pidfile=${sshguard_pidfile:-/var/run/${name}.pid}
+: ${sshguard_blacklist:=40:/var/db/sshguard/blacklist.db}
+: ${sshguard_safety_thresh:=40}
+: ${sshguard_pardon_min_interval:=1200}
+: ${sshguard_prescribe_interval:=420}
+: ${sshguard_whitelistfile:=%%PREFIX%%/etc/sshguard.whitelist}
+: ${sshguard_watch_logs:=/var/log/auth.log:/var/log/maillog}
+: ${sshguard_pidfile:=/var/run/sshguard.pid}
command=/usr/sbin/daemon
-actual_command=%%PREFIX%%/sbin/${name}
+actual_command=%%PREFIX%%/sbin/sshguard
procname=${actual_command}
-start_precmd=${name}_prestart
+start_precmd=sshguard_prestart
-command_args=-cf ${actual_command} -b ${sshguard_blacklist}
${sshguard_watch_params} -a ${sshguard_safety_thresh} -p
${sshguard_pardon_min_interval} -s ${sshguard_prescribe_interval} -w
${sshguard_whitelistfile} -i ${sshguard_pidfile}
+command_args=-cf ${actual_command} -b ${sshguard_blacklist}
\${sshguard_watch_params} -a ${sshguard_safety_thresh} -p
${sshguard_pardon_min_interval} -s ${sshguard_prescribe_interval} -w
${sshguard_whitelistfile} -i ${sshguard_pidfile}
sshguard_prestart()
{
___
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
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/188597[MAINTAINER] sysutils/duply: [Update 1.7.3] o ports/188590[minecraft-client] Doesn't startup at all o ports/188589[minecraft-client] Doesn't startup at all o ports/188586security/py-fchksum was deleted unnecessarily o ports/188584security/cfv was deleted unnecessarily o ports/188583[PATCH] editors/emacs24: modernize o ports/188581[PATCH] graphics/libgd: Add shebangfix so bdftogd does f ports/188579www/qupzilla lacks options for DE integration o ports/188575New port: devel/libmpsse o ports/188573[maintainer-update] multimedia/libaacs multimedia/libb o ports/188567[maintainer update] [patch] net-p2p/zetacoin: update t o ports/188550[patch] print/cups-base missing rc script for cups-bro o ports/188544maintainer-update of mail/mutt o ports/188533[PATCH] Deprecate devel/maven2 o ports/188530[maintainer-update] audio/teamspeak3-server compatibil o ports/188527databases/libdbi-drivers fails to build on FreeBSD 10. o ports/188526sysutils/grub2 doesn't compile with freetype2 installe o ports/188524sysutils/grub2 and ZFS: missing feature for read 'com. o ports/188515Update Port: www/drood = 3.12 o ports/188498lang/hiphop-php build failure o ports/188490Data f ports/188483security/pam_abl hasn't been updated this decade o ports/188482[MAINTAINER] dns/opendnssec: update to 1.4.5 f ports/188476[PATCH] sysutils/bbcp fix build with clang f ports/188473games/minecraft-client fails to start o ports/188472[PATCH] devel/smake: unbreak on gcc-free systems o ports/188471[PATCH] devel/ptmalloc2 Correct libptmalloc2.so symlin f ports/188470print/cups-filters: drives OfficeJet 8600 rogue when i o ports/188461devel/doxygen is MAKE_JOBS_SAFE now o ports/188450[new port] revive port www/baikal, removed because dis o ports/188449security/sshguard: sshguard_pidfile variable not defin f ports/188446mail/mail-notification fails to install o ports/188437New port: security/softether o ports/188436security/sshguard: SSH Guard won't start o ports/188423sysutils/ptools: Another bug fix in ptree. Some duplic o ports/188390benchmarks/sysbench: Fails to stage if DOCS option is o ports/188387fix build: textproc/htmlc o ports/188385[maintainer-update] Update games/crossfire-client to 1 o ports/188376print/cups-base: No such file or directory when try pr o ports/188375[patch] net-im/pidgin-latex broken on systems without f ports/188367[patch] update: mail/getmail o ports/188364devel/ioncube up to 4.6.0 o ports/188350Package repository is missing nrpe-ssl o ports/188347multimedia/qmmp, multimedia/qmmp-plugin-pack version 0 o ports/188339[new port] java/wildfly80: a flexible, lightweight, ma o ports/188325[new port] revive net-mgmt/nagios-pf-plugin o ports/188323databases/postgresql-repmgr update to 2.0 o ports/188320devel/boehm-gc: update to 7.4 o ports/188319Update: mail/greyfix to 0.4.0 o ports/188307New port: games/rogue Rogue: Exploring the Dungeons of o ports/188306[MAINTAINER] lang/rust: update to 0.10 f ports/188305databases/cassandra cqlsh issues f ports/188302[patch] x11/sterm update 0.5 o ports/188290[maintainer update] [patch] graphics/pngcrush: update o ports/188276x11-servers/x2x: version went backward f ports/188262Port net/quagga on FreeBSD 10 fails install f ports/188260net-im/tkabber-devel deprecated, unfetchable, maintain f ports/188258[PATCH] devel/avra: install includes, other fixes f ports/188257update: net-im/tkabber-plugins f ports/188256update: net-im/tkabber f ports/188248[PATCH] databases/cassandra 1.2.16 o ports/188246print/cups-filters build failure o ports/188233[patch] deskutils/cairo-dock-plugins fix bug build wit o ports/188228Upgrade of sysutils/dar from 2.3 to 2.4 fails to compi o ports/188221[patch] In pkg-plist file in shells in ports, @exec en o ports/188218[MAINTAINER] japanese/ja-eb: Always
Re: print/cups: since update to 1.7.1: error : Send-Document client-error-document-format-not-supported
14.04.2014 13:36, O. Hartmann пишет: On Sun, 13 Apr 2014 20:50:01 +0400 Boris Samorodov b...@passap.ru wrote: 12.04.2014 17:16, O. Hartmann пишет: On Fri, 11 Apr 2014 08:19:45 -0400 Ajtim lum...@gmail.com wrote: On Friday 11 April 2014 13:08:33 O. Hartmann wrote: On Wed, 09 Apr 2014 02:23:58 +0400 Boris Samorodov b...@passap.ru wrote: 09.04.2014 00:25, O. Hartmann пишет: On Tue, 08 Apr 2014 23:16:33 +0400 Boris Samorodov b...@passap.ru wrote: 08.04.2014 17:42, O. Hartmann пишет: Since the update of print/cups from 1.5.X to 1.7.1 How did you do it? As it is reported in /usr/ports/UPDATING. I delete first cups-image, then did the update which reeled in all the new stuff automatically. OK, lets start from some obvious things. Did you restart cupsd while experimenting? No. Give an output for: - % type lpr lpr is /usr/local/bin/lpr pkg which /usr/local/bin/lpr /usr/local/bin/lpr was installed by package cups-base-1.7.1 % ls -l /usr/local/etc/cups -r--r--r-- 1 root wheel 2807 11 Apr 11:58 cups-browsed.conf -rw-r- 1 root cups 3197 8 Apr 17:15 cups-files.conf -rw-r- 1 root cups 3197 8 Apr 17:15 cups-files.conf.bak -rw-r- 1 root wheel 3137 11 Apr 12:02 cups-files.conf.sample -r--r--r-- 1 root wheel 9521 11 Apr 11:50 cups-pdf.conf -r--r--r-- 1 root wheel 9521 11 Apr 11:50 cups-pdf.conf.sample -rw-r- 1 root cups 3442 8 Apr 17:22 cupsd.conf -rw-r- 1 root cups 5098 8 Apr 17:20 cupsd.conf.O -rw-r- 1 root cups 3442 8 Apr 17:22 cupsd.conf.bak -rw-r- 1 root wheel 4492 11 Apr 12:02 cupsd.conf.default -r--r--r-- 1 root wheel 4492 11 Apr 12:02 cupsd.conf.sample drwxr-xr-x 2 root wheel 512 11 Apr 12:02 interfaces -r--r--r-- 1 root wheel 1875 8 Apr 19:17 mime.convs -r--r--r-- 1 root wheel 1874 11 Apr 12:02 mime.convs.sample -r--r--r-- 1 root wheel 6456 8 Apr 19:18 mime.types -r--r--r-- 1 root wheel 6455 11 Apr 12:02 mime.types.sample drwxr-xr-x 2 root cups512 11 Apr 12:02 ppd -rw--- 1 root cups 4134 8 Apr 17:33 printers.conf -rw--- 1 root cups 4134 8 Apr 14:58 printers.conf.O -rw--- 1 root cups 4134 8 Apr 17:22 printers.conf.bak -rw-r--r-- 1 root cups946 11 Apr 11:53 pstoraster.convs -r--r--r-- 1 root wheel 778 11 Apr 12:04 pstotiff.convs -r--r--r-- 1 root wheel 2084 11 Apr 12:04 pstotiff.types -r--r--r-- 1 root wheel 284 11 Apr 11:49 snmp.conf -r--r--r-- 1 root wheel 284 11 Apr 12:02 snmp.conf.sample drwx-- 2 root cups512 11 Apr 12:02 ssl % make -C /usr/ports/print/cups-client pretty-print-config -GNUTLS (whoops ... this is not the default, isn't it?) == corrected that with a new recompilation with rmconfig preceded. % grep CUPS /etc/make.conf NULL (menas: no output) % pkg info -x cups hp foo gut cups-base-1.7.1 cups-client-1.7.1 cups-filters-1.0.52 cups-image-1.7.1 cups-pdf-2.6.1_1 cups-pstoraster-8.15.4_7 cups-samba-6.0_7 gutenprint-cups-5.2.8_1 libgnomecups-0.2.3_5,1 linux-f10-cups-libs-1.3.11_1 foomatic-db-hpijs-1.4 hplip-3.14.1 kdevelop-php-1.6.0_1 kdevelop-php-docs-1.6.0_1 php5-5.4.27 swhplugins-0.4.15_4 foomatic-db-20140331 foomatic-db-engine-4.0.11,2 foomatic-db-hpijs-1.4 foomatic-filters-4.0.17 gimp-gutenprint-5.2.8 gutenprint-base-5.2.8 gutenprint-cups-5.2.8_1 gutenprint-ijs-5.2.8 - Stop cupsd, move temporary /var/log/cups/*_log to another location. Start cupsd and look for suspicious messages at /var/log/cups/* files. Nothing suspicious so far. With print/cups-filters installed, the whole cups printing system is corrupted and doesn't print a single sheet of paper (PDF/PS) normal es expected. Prior to this task, I recompiled, as you suggested, first all cups ports and afterwards hplip/foomatic. I also installed print/cups-filters before recompiling hplip/foomatic. It works for me now (FreeBSD 10.0-RELEASE): I did deinstall cups* and hplip. Than installed cups and patched hplip. First I used as usual hp-business_inkjet_3000-hpijs-pcl3.ppd.gz and it didn't work It printed:%PDF-1.4 and jobs processing never stopped. Than I removed device and installed again with -3000-ps.ppd.gz and it works but cannot print test page. I tried alternatives, but it is with all (known to me) usefull drivers for the specific printer the same result: empty pages, print job stuck in queue. I also tried most recent hplip-3.14.4 but I doubt this is the reason. I can print PDF and PS, as reported, when deinstalling/removing print/cups-filters using clients like xpdf, xdvi or printing directly via lpr -PPRINTER_NAME jobfile.ps. This fails when print/cups-filter is installed. This is rather strange. But may be this is because you use hplip which I've never used before. I used hplip before with CUPS 1.5.X with the printer of mine, the HP OfficeJet Pro 8600 N911a, as I mentined. The hplip driver suite privided the only prperly
Re: print/cups: since update to 1.7.1: error : Send-Document client-error-document-format-not-supported
Boris Samorodov ha scritto: Great, glad to be helpful. May be the patch is not right and the problem should be resolved in another way. But anyway the problem seems to be localized and I'm sure Max will do the right thing. As already said, I fixed the very same problem with hplip installing cups-filter: I don't know which one is the correct way. -- Alex Dupre ___ 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: Mk/Scripts/qa.sh and DEVELOPER=yes
On Mon, 2014-04-14 at 07:34 +0200, Matthias Andree wrote:
Am 13.04.2014 14:28, schrieb clutton:
It seems that with DEVELOPER=yes in /etc/make.conf I'm not able to
perform ordinary update routines. Removing the DEVELOPER variable fix
the problem. And probably the worst part of it that there's no error
message.
Running Q/A tests (stage-qa)
Error:
/tmp/usr/ports/devel/p5-subversion/work/stage/usr/local/lib/perl5/site_perl/5.18/mach/auto/SVN/_Core/.packlist
is referring to /tmp/usr/ports/devel/p5-subversion/work/stage
Oh, there is an error, as quoted above.
.packlist refers to a file that will no longer be present after make
clean.
Cause is that the p5-subversion port, or some part of the Perl or ports
framework, causes the .packlist to be generated with bogus contents.
Either we can fix the actual cause, or we can hack the .packlist to
strip the ${STAGEDIR} prefix, which would be the inferior approach, however.
I have missed that. Thanks for fixing.
signature.asc
Description: This is a digitally signed message part
Re: print/cups: since update to 1.7.1: error : Send-Document client-error-document-format-not-supported
14.04.2014 15:58, Alex Dupre пишет: Boris Samorodov ha scritto: Great, glad to be helpful. May be the patch is not right and the problem should be resolved in another way. But anyway the problem seems to be localized and I'm sure Max will do the right thing. As already said, I fixed the very same problem with hplip installing cups-filter: I don't know which one is the correct way. Alex, I've read your previous answer. But didn't reply, ENOTIME, sorry. The problem here was when both hplip and cups-filters were installed. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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
EMPLOYMENT
Hi, An immediate job opportunity is available in the following position : CAREGIVER/NANNY/LESSSON (Tutor)/PAYROLL SERVICE/ PERSONAL ASSISTANT/SALES REP. NOTE :Kindly write back if you are serious and ready to fill out any of the position asap and indicate the position you want to occupy. Thanks. (832) 554-7211TEXT ONLY. ___ 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
We are camera factory. Security system supplier of WAL-MART headquarte
We are camera factory. Security system supplier of WAL-MART headquarte Hello po...@freebsd.org, It looks like your email software does not support HTML. Please visit the webpage below in order to read this message in your webbrowser: http://chinacosmo.dmdelivery.com/x/?S7Y1Nvifa2tkbvm.yNbQ0MTCwOJ.DlDMEgAA09 ___ 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
port request - dnssec/tlsa validator
Hi, I've found myself agreeing to write an article on DNSSEC and TLSA validation for the FreeBSD Journal. There's a firefox/chrome/etc plugin for performing DNSSEC/TLSA validation at https://www.dnssec-validator.cz/. I would really like to have this as a port or package before the article comes out. Is there any chance I could prevail on one of you fine folks to make a port? Peter Wemm successfully built and uses a native version of the plugin. He's got a patchset at http://people.freebsd.org/~peter/MF-dnssec-tlsa_validator-2.1.1-freebsd-x64.diff.txt. (He also have the binary for download at http://people.freebsd.org/~peter/MF-dnssec-tlsa_validator-2.1.1-freebsd-x64.xpi but, well, it's an unofficial binary.) In theory (knock on wood), given the patch, it should be pretty straightforward to make a port? If not, no worries. I'll add in some instructions on how to build it. But having the plugin would make things easier for a lot of people. Thanks, ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.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
Re: [FIX] Re: FreeBSD Port: security/sshguard-pf
Please commit it in the meantime, I'll fix the rest shortly. Can't remember if
you have a ports bit, if not Approved :)
Thanks,
Chris
On 14 April 2014 11:59:21 BST, Stefan Esser s...@freebsd.org wrote:
Am 14.04.2014 10:25, schrieb Benjamin Podszun:
I'd say this is a bug in sshguard: Failing to start shouldn't exit
with 0.
That said, it first and foremost is a bug in the port.
Looking at the rc script and the diff [1] the problem's easy enough:
${sshguard_pidfile} is passed as parameter to -i, but isn't set in
the
script/has no default value. Either the related line from the
previous
revision should be revived or the substitution should change to use
${pidfile}, which _is_ set.
The attached diff fixes the problems in the sshguard rc file. I have
replaced occurences of ${name} with sshguard, in accordance with
newer rc script style conventions. The diff has to be applied within
the files sub-directory of the sshguard port.
The other problems of this port (see previous mail) are not fixed and
should still be addressed ...
Regards, STefan
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
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
[QAT] 351263: 4x leftovers
Update audio/soundkonverter to 2.1.1. ChangeLog: - Add: Check for MP4 support in faac - Fix: Don't run vorbisgain more than once per directory - Fix: Progress bar jumps when a file finished - Build ID: 20140414170200-52808 Job owner: d...@freebsd.org Buildtime: 59 minutes Enddate: Mon, 14 Apr 2014 18:00:47 GMT Revision: 351263 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=351263 - Port:audio/soundkonverter 2.1.1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140414170200-52808-317354/soundkonverter-2.1.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140414170200-52808-317355/soundkonverter-2.1.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140414170200-52808-317356/soundkonverter-2.1.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140414170200-52808-317357/soundkonverter-2.1.1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140414170200-52808 redports https://qat.redports.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
[QAT] 351265: 3x leftovers, 1x fetch
Add optional dependency to libav for audio/soundkonverter. Since the package structure may change, bump PORTREVISION. - Build ID: 20140414170800-5622 Job owner: d...@freebsd.org Buildtime: 90 minutes Enddate: Mon, 14 Apr 2014 18:37:34 GMT Revision: 351265 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=351265 - Port:audio/soundkonverter 2.1.1_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: FETCH Log: https://qat.redports.org//~d...@freebsd.org/20140414170800-5622-317362/soundkonverter-2.1.1_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140414170800-5622-317363/soundkonverter-2.1.1_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140414170800-5622-317364/soundkonverter-2.1.1_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140414170800-5622-317365/soundkonverter-2.1.1_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140414170800-5622 redports https://qat.redports.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
[QAT] 351281: 4x leftovers
Add Staging support PR: ports/188500 Submitted by: Bartek Rutkowski po...@robakdesign.com - Build ID: 20140414195200-48379 Job owner: skreu...@freebsd.org Buildtime: 4 minutes Enddate: Mon, 14 Apr 2014 19:56:04 GMT Revision: 351281 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=351281 - Port:devel/py-fsm 0.01 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140414195200-48379-317426/py27-fsm-0.01.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140414195200-48379-317427/py27-fsm-0.01.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140414195200-48379-317428/py27-fsm-0.01.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140414195200-48379-317429/py27-fsm-0.01.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140414195200-48379 redports https://qat.redports.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: FreeBSD Port: rubygem-passenger-4.0.41_2
Hi David,
kindly provide a patch.
--
ozz
On Sun, Apr 13, 2014 at 12:23:56PM +0200, David Keller wrote:
Hi Sergey,
It's not related to gem dependency error but the symlink creation
might be incorrect:
${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
Will create the following symlink:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
lib/ruby/gems/1.9/gems/passenger-4.0.41
Rather than:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41
Or:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41
You might prefer using:
${LN} -s ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${GEM_NAME}
${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
Or even:
${LN} -s ${GEM_NAME} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
David
On Sun, Apr 13, 2014 at 4:13 AM, Sergey A. Osokin o...@freebsd.org wrote:
On Sat, Apr 12, 2014 at 03:09:04AM -0500, Scot Hetzel wrote:
On Fri, Apr 11, 2014 at 5:51 PM, Steven Hartland
kill...@multiplay.co.uk wrote:
The change is from :N - :M
.if ${PORT_OPTIONS:MDEBUG}
- Select only those words that match DEBUG
Which occurs 220 in the port tree and:
.if ${PORT_OPTIONS:NDEBUG}
- Select words that don't match DEBUG
Which only occurs twice, so TBH I assumed it was a typo given every other
option uses PORTOPTIONS:M${option}
Unfortunately the docs don't seem to provide any clarification
http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html
so if anyone could chime in with some details on the exact meanings that
would be most appreciated.
You have to read the make(1) man page:
http://www.freebsd.org/cgi/man.cgi?query=makesektion=1
So, the patch is here.
But now I've got following error:
x1% sudo make install
=== Staging for rubygem-passenger-4.0.41_3
=== rubygem-passenger-4.0.41_3 depends on package:
rubygem-fastthread=1.0.7 - found
=== rubygem-passenger-4.0.41_3 depends on package: rubygem-rack=1.4.5 -
found
=== rubygem-passenger-4.0.41_3 depends on package:
rubygem-daemon_controller=1.2.0 - found
=== rubygem-passenger-4.0.41_3 depends on file: /usr/local/bin/gem19 -
found
=== rubygem-passenger-4.0.41_3 depends on file: /usr/local/bin/ruby19 -
found
=== rubygem-passenger-4.0.41_3 depends on file: /usr/local/sbin/apxs -
found
=== rubygem-passenger-4.0.41_3 depends on shared library: libeio.so -
found
=== rubygem-passenger-4.0.41_3 depends on shared library: libev.so -
found
=== rubygem-passenger-4.0.41_3 depends on shared library: libcurl.so -
found
=== Generating temporary packing list
Building native extensions. This could take a while...
Successfully installed passenger-4.0.41
1 gem installed
Installing RDoc documentation for passenger-4.0.41...
(CC=clang CXX=clang++
/usr/home/osa/ports/www/rubygem-passenger/work/stage/usr/local/bin/passenger-install-apache2-module
--auto)
/usr/local/lib/ruby/site_ruby/1.9/rubygems/dependency.rb:247:in `to_specs':
Could not find passenger (= 0) amongst [daemon_controller-1.2.0,
fastthread-1.0.7, rack-1.4.5, rake-10.2.2] (Gem::LoadError)
from
/usr/local/lib/ruby/site_ruby/1.9/rubygems/dependency.rb:256:in `to_spec'
from /usr/local/lib/ruby/site_ruby/1.9/rubygems.rb:1231:in `gem'
from
/usr/home/osa/ports/www/rubygem-passenger/work/stage/usr/local/bin/passenger-install-apache2-module:22:in
`main'
*** Error code 1
Stop.
Any idea what's wrong here?
Index: Makefile
===
--- Makefile(revision 351090)
+++ Makefile(working copy)
@@ -3,7 +3,7 @@
PORTNAME= passenger
PORTVERSION= 4.0.41
-PORTREVISION= 2
+PORTREVISION= 3
CATEGORIES=www rubygems
MASTER_SITES= RG
PKGNAMEPREFIX= rubygem-
@@ -39,11 +39,11 @@
.endif
.endif
-LIB_DEPENDS+= eio:${PORTSDIR}/devel/libeio \
- ev:${PORTSDIR}/devel/libev \
- curl:${PORTSDIR}/ftp/curl
-BUILD_DEPENDS+=
rubygem-fastthread=1.0.1:${PORTSDIR}/devel/rubygem-fastthread \
- rubygem-rack=0:${PORTSDIR}/www/rubygem-rack \
+LIB_DEPENDS+= libeio.so:${PORTSDIR}/devel/libeio \
+ libev.so:${PORTSDIR}/devel/libev \
+ libcurl.so:${PORTSDIR}/ftp/curl
+BUILD_DEPENDS+=
rubygem-fastthread=1.0.7:${PORTSDIR}/devel/rubygem-fastthread \
+ rubygem-rack=1.4.5:${PORTSDIR}/www/rubygem-rack \
rubygem-daemon_controller=1.2.0:${PORTSDIR}/devel/rubygem-daemon_controller
RUN_DEPENDS:= ${BUILD_DEPENDS}
@@ -81,7 +81,7 @@
s! -feliminate-unused-debug-symbols
-feliminate-unused-debug-types!!g; \
201,203s!true!false!' \
${WRKSRC}/build/basics.rb
-.if ${PORT_OPTIONS:NDEBUG}
+.if ${PORT_OPTIONS:MDEBUG}
Re: FreeBSD Port: rubygem-passenger-4.0.41_2
Hi Steven,
unfortunately, your patch is wrong and this is why I can't commit your changes.
What's wrong in your patch? You have mixed features and bugfixes in one patch.
Please provide bugfix only patch.
--
ozz
On Sun, Apr 13, 2014 at 12:28:41PM +0100, Steven Hartland wrote:
- Original Message - From: David Keller david.kel...@litchis.fr
Hi Sergey,
It's not related to gem dependency error but the symlink creation
might be incorrect:
${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
Will create the following symlink:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
lib/ruby/gems/1.9/gems/passenger-4.0.41
Rather than:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41
Or:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41
You might prefer using:
${LN} -s ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${GEM_NAME}
${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
Or even:
${LN} -s ${GEM_NAME} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
My current version has:
(cd ${STAGEDIR}${PREFIX}/${GEMS_DIR} ${LN} -s ${GEM_NAME} ${PORTNAME})
Which I will create:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41
@Sergey: For your apache module problem try the attached patch / full
version which fixes that for me.
I'd previously only ever built the nginx version and looks like the
apache2 module build was broken when stage support was added.
I've confirmed it builds but I don't have an apache2 install to test
fully with here so if you could let me know if it works and I'll get all
the changes checked in.
Regards
Steve
___
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: rubygem-passenger-4.0.41_2
Hi Sergey, could you clarify which parts you believe are features?
I know there are a number of changes but all of them I'd class as fixes
and not really features.
For reference here's a description of the changes:-
* Added missing license
* Display the correct install message for both nginx and apache
* Fix staging build of nginx, apache and link components
* Ensure download_cache is included in the package which prevents warning
on removal due to failure to delete directory.
* Updated LIB_DEPENDS to latest recommended format
Just to be sure we're both talking about the same changes I've attached
the latest version for reference.
Regards
Steve
- Original Message -
From: Sergey A. Osokin o...@freebsd.org
To: Steven Hartland kill...@multiplay.co.uk
Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel swhet...@gmail.com; David
Keller david.kel...@litchis.fr
Sent: Tuesday, April 15, 2014 12:00 AM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2
Hi Steven,
unfortunately, your patch is wrong and this is why I can't commit your changes.
What's wrong in your patch? You have mixed features and bugfixes in one patch.
Please provide bugfix only patch.
--
ozz
On Sun, Apr 13, 2014 at 12:28:41PM +0100, Steven Hartland wrote:
- Original Message - From: David Keller david.kel...@litchis.fr
Hi Sergey,
It's not related to gem dependency error but the symlink creation
might be incorrect:
${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
Will create the following symlink:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
lib/ruby/gems/1.9/gems/passenger-4.0.41
Rather than:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41
Or:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41
You might prefer using:
${LN} -s ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${GEM_NAME}
${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
Or even:
${LN} -s ${GEM_NAME} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}
My current version has:
(cd ${STAGEDIR}${PREFIX}/${GEMS_DIR} ${LN} -s ${GEM_NAME} ${PORTNAME})
Which I will create:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41
@Sergey: For your apache module problem try the attached patch / full
version which fixes that for me.
I'd previously only ever built the nginx version and looks like the
apache2 module build was broken when stage support was added.
I've confirmed it builds but I don't have an apache2 install to test
fully with here so if you could let me know if it works and I'll get all
the changes checked in.
Regards
Steve
___
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
rubygem-passenger.patch
Description: Binary data
___
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
