On 26-8-2018 2:07, Pete Wright wrote:
one thing i do for my systems is if there is an update to a port i
need/want to test before the official build cluster is done is run a
"make package" in the port directory. then i can install the updated
code as a pkg for future upgrade convenience. this
On 25-8-2018 14:42, Dries Michiels wrote:
How many times is there between the release of a port and its package - is
that depending on the port maintainer?
This does not depend on the port maintainer. Ports are the master! Packages
are simply built ports.
These packages are built in bulk on th
How many times is there between the release of a port and its package -
is that depending on the port maintainer?
thanks,
Jos
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
Thanks guys, problem solved!
Cheers,
Jos
On 15-6-2018 16:51, Jos Chrispijn wrote:
Sorry for asking as I think the question hasbeen raised some time
before(ducking):
Can somebody tell me how I can install phpMyAdmin from the packages?
Seems that it is not partof the current pkg-repository
Sorry for asking as I think the question hasbeen raised some time
before(ducking):
Can somebody tell me how I can install phpMyAdmin from the packages?
Seems that it is not partof the current pkg-repository:
pkg install phpmyadmin
Updating FreeBSD repository catalogue...
FreeBSD repository is
Due to a mistake (...) I now got a mix of ports and packageson my BSD
system.
Can someone advise how to savely switch to packages only on this live
system?
Thanks,
Jos
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
On 8-4-2018 12:11, Matthew Seaman wrote:
[*] Assuming your system is set up to use php56, which it probably is as
that's the default. The change to flavouring means that you should be
able to upgrade to a different version of PHP and still keep using the
default package servers rather than have
releases a new version- you
just only recompile that port including the update?
- what effect does this have on precompiled ports?
/Jos
On 8-4-2018 14:14, Jos Chrispijn wrote:
Kurt, thanks for this.
Can you tell me why this flavored mode has been introduced?
Does that mean that if I install a port
Kurt, thanks for this.
Can you tell me why this flavored mode has been introduced?
Does that mean that if I install a port that will not have this
php-version string, it is either not used by php or is not yet ready to
be used in flavored mode?
Best regards, Jos
On 7-4-2018 17:00, Kurt Jaege
On 7-4-2018 21:55, Miroslav Lachman wrote:
To fix it, this should work:
pkg delete phpmyadmin
pkg install phpmyadmin
That did the trick, thanks for that.
I first followed up Matthew's suggestion (thanks for that too), but the
port still got the Orphanned status.
What now happens is that a
[Nub on ports]
Running 'pkg version', I got phpMyAdmin status "?" (orphan)
I first tried reinstalling the port, resulting in an error.
-- cut --
===> Installing for phpMyAdmin-php56-4.7.9
===> Registering installation for phpMyAdmin-php56-4.7.9
Installing phpMyAdmin-php56-4.7.9...
pkg-stati
I would like to thank all programmers and port maintainers for their
excellent work in 2017.
Without you we would never enjoy BSD as we do until this very day.
I really hope that you will keep up the good work in 2018 also!
Thanks,
Jos Chrispijn
On 8-12-2017 19:11, Kurt Jaeger wrote:
We'll work the patch in, it just takes a little time 8-(
Thanks for this - everything is fine now.
Keep up the good work,
Jos
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
On 8-12-2017 17:58, Warren Block wrote:
procmail is ancient, and has had known quality issues for much of the
time. Consider maildrop as a more powerful and more maintained
replacement that is pretty easy to implement:
I know - but I can remember that procmail should be installed also when
usi
Nick,
Op 8-12-2017 om 17:32 schreef N.J. Mann:
See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223777
specifically the patch in "Comment 2". I have been using this
patch for a few days without problems.
Sadly the vulnerability check still fails.
Unfortunatly I am neither that of a progr
A little concernedthat I got no response to this.
Is Procmail dead for most of you guys(ducking)
Best regards,
Jos Chrispijn
Op 24-11-2017 om 13:32 schreef Jos Chrispijn:
Dear sunpoet,
Noticed this week following issue on procmail.
Vulnerabilities check
vulnxml file up-to-date
procmail
Dear sunpoet,
Noticed this week following issue on procmail.
Vulnerabilities check
vulnxml file up-to-date
procmail-3.22_9 is vulnerable:
procmail -- Heap-based buffer overflow
CVE: CVE-2017-16844
WWW:
https://vuxml.FreeBSD.org/freebsd/288f7cee-ced6-11e7-8ae9-0050569f0b83.html
Could you plea
Op 11-8-2017 om 12:41 schreef Kurt Jaeger:
Basically, the suggestion is to update dependent ports to oniguruma6,
and then remove oniguruma5. See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220438
for more details. That's a little bit of work and we're short
on folks doing it 8-}
Overlook
Dear port maintainer,
Is there a port update for this port:
curl-7.56.0 is vulnerable:
cURL -- out of bounds read
CVE: CVE-2017-1000257
WWW:https://vuxml.FreeBSD.org/freebsd/143ec3d6-b7cf-11e7-ac58-b499baebfeaf.html
Thanks and keep up the good work,
Jos Chrispijn
Op 12-10-2017 om 20:19 schreef Vidar Karlsen:
I usually get that exact error when I run pkg from a directory that no
longer exists. In my case, this typically happens because I’m sitting
in a port dir like /usr/ports/dns/unbound after having run 'portsnap
fetch update’ which has deleted that d
Op 12-10-2017 om 7:39 schreef Vidar Karlsen:
Also check if your current work dir has been deleted,
Do you mean my BSD workdir like /temp or do you refer to the workdir
that is used during the portupdate?
Where can I find which workdir that is?
Thanks, Jos
_
Op 12-10-2017 om 7:39 schreef Vidar Karlsen:
Also check if your current work dir has been deleted, say, as a consequence of
running portsnap update for example. That can also trigger this error:
vidar@cube ~% mkdir -p one/two
vidar@cube ~% cd one/two
vidar@cube ~/one/two% rm -rf ~/one
vidar@cube
a
bit more information might help. So might a "pkg check -B" which will read
the db many times.
Thanks for that suggestion - it looks ok
Checking all packages: 100%
With regards to the technical basi(c)s, I am a complete nub regarding this.
Will investigate further, thanks for your reply
without risking my ports
collection being corrupted by some pkg command?
Thanks for your help!
Jos Chrispijn
___
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"
Can you please provide a port update? Thanks.
Keep up the good work,
Jos Chrispijn
___
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"
actly means and what it says about notices/planned version updates.
Best regards,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port
Op 30-6-2017 om 18:23 schreef Carlos Jacobo Puga Medina:
I have submitted a patch to update libgcrypt to 1.7.8 (still pending
for an exp-run)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220382
You can grab the patch, apply and build the port.
Thanks Carlos, appreciate your support.
./Jo
out a port update? Thanks in advance!
Keep up the good work,
Jos Chrispijn
___
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"
-F
vulnxml file up-to-date
tiff-4.0.7_1 is vulnerable:
tiff -- multiple vulnerabilities
CVE: CVE-2017-7602
TIFF port issue solved - they released an update yesterday.
Thanks guys!
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
ht
Op 6-5-2017 om 12:22 schreef Walter Schwarzenfeld:
Update is on the way:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216658
Great, thanks!
./Jos
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
Dear team,
Thanks for your suggestions and solution. You really raised my learning
curve here.
Regards,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail
ith "DISABLE_VULNERABILITIES=yes" ?
Happy to contribute,
Jos Chrispijn
___
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"
Thanks y'all for your support - this was a real eye opener.
Best regards,
Jos
Op 5-5-2017 om 19:19 schreef Kevin Oberman:
On Fri, May 5, 2017 at 6:37 AM, Jos Chrispijn
mailto:bsdpo...@cloudzeeland.nl>> wrote:
Op 5-5-2017 om 18:05 schreef Adam Weinberger:
On 5 Ma
Op 5-5-2017 om 18:05 schreef Adam Weinberger:
On 5 May, 2017, at 9:48, mokhi wrote:
Well, as I can see here < http://www.freshports.org/devel/icu/ > an
older version of this port is vulnerable not current version.
Maybe by updating your tree your problem will be solved :-]
Yes, this is the co
Yes I noticed as well.
Point is that after updating my tree, the issue still exists allthough I
have th correct portupdate in my ports.
Let me check what is going wrong here.
Thanks,
Jos
Op 5-5-2017 om 17:48 schreef mokhi:
Well, as I can see here < http://www.freshports.org/devel/icu/ > an
o
I am really not a fan of that.
Better would be to solve the 'vulneratbilities' issue.
/Jos
Op 5-5-2017 om 17:24 schreef mokhi:
It seems the port has known vulnerabilities.
If you are sure about what you are doing, run the make command with
"DISABLE_VULNERABILITIES=yes" option as it suggests.
__
d with 'make
DISABLE_VULNERABILITIES=yes'
*** Error code 1
Stop.
make: stopped in /usr/ports/devel/icu
Thanks,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
Hi Kurt,
Op 6-2-2017 om 16:15 schreef Kurt Jaeger:
Please look for the other mail thread a few hours ago, see:
https://lists.freebsd.org/pipermail/freebsd-ports/2017-February/107030.html
Sorry, I have overseen that one - it worked for me.
Keep up the good work,
Jos
__
Dear port maintainer,
Just upgrading my ports and get the following error:
--- cut ---
===> Installing for check-0.10.0
===> Checking if check already installed
===> Registering installation for check-0.10.0 as automatic
Installing check-0.10.0...
pkg-static: check-0.10.0 conflicts with libc
> Initial dependency check complete for security/dehydrated
===>>> Returning to update check of installed ports
===>>> All >> (1)
===>>> The following actions will be taken if you choose to proceed:
Re-install dehydrated-0.3.1
Can someone tell me how to solve th
___
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"
Dear port maintainer,
Checking for packages with security vulnerabilities:
Database fetched: Mon Oct 26 00:09:27 CET 2015
php5-phar-5.4.45
Can you tell when we can expect the update of this port?
Thanks,
Jos Chrispijn
___
freebsd-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"
___
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"
On 21-7-2015 9:06, Mathieu Arnold wrote:
+--On 21 juillet 2015 08:57:49 +0200 Jos Chrispijn wrote:
| Can you advise how to process further?
It has been fixed since, please upgrade your ports tree and try again.
Oke, thanks.
BR, Jos
___
freebsd
571:in `block in main'
from /usr/local/lib/ruby/2.1/optparse.rb:880:in `initialize'
from /usr/local/sbin/portupgrade:238:in `new'
from /usr/local/sbin/portupgrade:238:in `main'
from /usr/local/sbin/portupgrade:2380:in `'
Can you advise how to pr
efault. In this case I might have hit the wrong
choice when configuring.
Thanks for explaining
BR, Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "fr
gt; If you are sure you can build it, remove the
IGNORE line in the Makefile and try again.
===>>> Update for curl-7.42.0 failed
===>>> Aborting update
--- cut ---
Any idea why a port update is released with an
gt; If you are sure you can build it, remove the
IGNORE line in the Makefile and try again.
===>>> Update for curl-7.42.0 failed
===>>> Aborting update
--- cut ---
Any idea why a port update is released with an
I would like to thank all port maintainers for keeping all ports
up-to-date last year and hope everyone enjoys an informative and
productional 2015. Keep up the good work!
BR, Jos Chrispijn
- Vision is not seeing things as they are, but as they will be
With portmanager I got this line:
===>>> The misc/gnomehier port has been deleted: Not needed anymore
But I still have it active. How can I remove it when the port itself is
nog existing anymore as deinstall won't work anymore as its
portfolder is gone...
BR,
portmaster -y --clean-packages
portmaster -y --check-depends
portmaster -a
also did the trick.
Piece too
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On 1-12-2014 21:45, Jos Chrispijn wrote:
*** [fake-pkg] Error code 74
Stop in /usr/ports/security/p5-IO-Socket-SSL.
A very simple way to solve [fake-pkg] error if you are using svn for
ports synchronization:
cd /usr/ports/security
rm -R p5-IO-Socket-SSL
and start svn to re-sync. The
tory
*** [fake-pkg] Error code 74
Stop in /usr/ports/security/p5-IO-Socket-SSL.
*** [install] Error code 1
Stop in /usr/ports/security/p5-IO-Socket-SSL.
*** [run-depends] Error code 1
Thanks,
Jos Chrispijn
___
freebsd-ports@freebsd.org m
ail/spamassassin.
*** [install] Error code 1
Stop in /usr/ports/mail/spamassassin.
--- cut ---
Could you provide a solution for this?
Thanks,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
Looks like this is due to p5-IO-Socket-SSL port (I think).
Letme first find out what went wrong here before I bother you with this
issue.
Jos Chrispijn schreef op 1-12-2014 om 21:39:
Dear port maintainer,
Just ran into a problem with updating the Spamassassin port:
--- cut
Larry Rosenman wrote on 19-11-2014:
On 2014-11-19 14:49, Jos Chrispijn wrote:
Larry Rosenman wrote on 19-11-2014:
I already filed:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195182
Thanks. Should I wait for an update or should I do a deinstall and
reinstall to see if Kurt's sugge
Larry Rosenman wrote on 19-11-2014:
I already filed:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195182
Thanks. Should I wait for an update or should I do a deinstall and
reinstall to see if Kurt's suggestion works?
BR,
Jos Chrispijn
On 2014-11-19 14:40, Jos Chrispijn
ld] Error code 1
Stop in /usr/ports/security/clamav.
===>>> make build failed for security/clamav
===>>> Aborting update
===>>> Update for security/clamav failed
===>>> Aborting update
--- end ---
Can you provide a solution for this?
Thanks,
Jos
Jos Chrispijn:
After I installed ImageMagic port, I got stuck at the installation of
Webp:
Just installed ImageMagic again and the installation went perfect -
thanks for your support!
BR, Jos Chrispijn
___
freebsd-ports@freebsd.org mailing
s/graphics/webp.
--- end of text --
Can you tell me how to solve?
Thanks,
Jos Chrispijn
___
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"
s/graphics/webp.
--- end of text --
Can you tell me how to solve?
Thanks,
Jos Chrispijn
___
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"
Is there a way of having pkgdb automatically taking care of these kind
of 'missing' ports:
pkg_info: the package info for package 'alpine-2.11_2' is corrupt
Now I first have to find out where this port is located with:
%> locate $1 | grep /usr/ports/
and then reinstall it:
cd $
know once being successfully.
BR, Jos Chrispijn
___
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"
while... Child process
pid=2150 terminated abnormally: Segmentation fault: 11
done
Can you tell me how to solve this?
Thanks,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-po
Just got this error when upgrading pkg:
===>>> Creating a backup package for old version pkg-1.3.0
Creating package for pkg-1.3.0
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 1
packages in the universe):
Installed
===>>> Update for ports-mgmt/pkg failed
===>>> Aborting update
Any suggestion to solve this? Perhaps I am doing something wrong here -
pls advise.
thanks,
Jos Chrispijn
Kevin Oberman:
On Wed, Jul 23, 2014 at 7:42 AM, Baptiste Daroussin [1]
wrote:
Hi a
Just got this error when upgrading pkg:
===>>> Creating a backup package for old version pkg-1.3.0
Creating package for pkg-1.3.0
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 1
packages in the universe):
Installed
Jos Chrispijn:
After the last port update of php I get this error:
openssl_verify(): Don't know how to get public key from this private
key in
/usr/local/www/x1/x2/x3/services/Signing/Services_Signing_Openssl.php
on line 32
For some reason the issue has solved i
this?
Thanks!
Jos Chrispijn
References
1. https://bugs.php.net/bug.php?id=61930
___
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"
remains in conflict <<
At revision 360356.
Summary of conflicts:
Skipped paths: 1
--cut --
Is this an issue of an ftp server being offline or should we receive a
port update about the 'patch-plugins-check_ssh.c' source file?
BR, Jos Chrispijn
__
sql55-server-5.5.38 Multithreaded SQL database (server)
py27-sqlite3-2.7.6_3 Standard Python binding to the SQLite3
library
sqlite3-3.8.5 SQL database engine in a C library
Could it be possible that there has gone something wrong in the latest
po
Just a big thanks to all ports maintainers and helpful fellow mailing
list participants.
Without your prompt responses and voluntary activities we (at least I)
can run a stable updated OS and programs.
Keep up the good work!
Jos Chrispijn
kage(s):
dovecot2-2.2.12
They install files into the same place.
You may want to stop build with Ctrl + C.
===> License LGPL21 MIT accepted by the user
--- cut ---
BR, Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.fr
already been updated, you can
safely ignore the entry.
You will not be e-mailed again for any of the port/version combinations
below.
--- cut ---
Can't we create a separate newsgroup for these kind of messages?
No offense meant (keep up the good work).
BR, Jos Chri
Just solved it by deinstalling lua51 and fresh installing lua52.
Can you put a note in UPDATING on this?
thanks,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe
,
Jos Chrispijn
___
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"
the same place).
Problematic file: /usr/local/include/lua51/lauxlib.h
*** [fake-pkg] Error code 70
! lua51-5.1.5_6 not even installed.
Can you tell me how to solve this? Thanks in advance.
best regards,
Jos Chrispijn
___
freebsd-ports@freebsd.o
r code 1
Stop in /usr/ports/graphics/dri.
===>>> make failed for graphics/dri
===>>> Aborting update
===>>> Update for graphics/dri failed
===>>> Aborting update
===>>> Killing background jobs
Terminated
===>>> Exiting
--- cut
Thank you for the informative responses - I learned a lot.
Best regards.
Jos Chrispijn:
Since my last Spamd port update I get this error when I try to start
spamd:
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd
success. May that be an inward traffic issue on port 783 that triggered
Perl and kept it occupied for Spamd?
b. Is it unsafe or possible to let spamd use another port if 783 is
occupied. May that be a security risk?
T|hanks for your help,
Jos Chrispijn
Sergey V. Dyatko:
use `sockstat -l4 -p783` instead. It show you what user-command-pid
listen that port
USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root perl 1404 5 tcp4 127.0.0.1:783 *:*
root perl 1403 5 tcp4 127.0.0.1:783
Since my last Spamd port update I get this error when I try to start
spamd:
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.
server socket setup failed, retry 1: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server
O that is neat - got a detailed report back saying that I am not the
first one who has discovered this.
Guess it will be solved in the next port release.
have a good weekend,
Jos
Jos Chrispijn:
From UPDATING:
20140327:
AFFECTS: users of lang/php5 and lang/php55 with Apache
From UPDATING:
20140327:
AFFECTS: users of lang/php5 and lang/php55 with Apache module
AUTHOR: [1]a...@freebsd.org
The Apache PHP module has been splitted from main PHP port, so if you
are using it you should install one of www/mod_php5 or www/mod_php55.
* When I tried
Sorry, wrong recipient. Please ignore..
Jos Chrispijn:
Hi Jack,
Krijg sinds gisteren een melding op subversion (svn):
subversion17-1.7.16_1: "/usr/ports/www/apache" non-existent --
dependency list incomplete
subversion17-1.7.16_1: "/usr/ports/
Hi Jack,
Krijg sinds gisteren een melding op subversion (svn):
subversion17-1.7.16_1: "/usr/ports/www/apache" non-existent --
dependency list incomplete
subversion17-1.7.16_1: "/usr/ports/www/apache" non-existent --
dependency list incomplete
===>>> Initial dependency check com
Dear group,
Just ran into a ports issue for Docbook 4.x.x
Can you tell me how to solve this?
--- cut ---
===> Found saved configuration for docbook420-4.2_1
===> Fetching all distfiles required by docbook420-4.2_1 for building
===> Extracting for docbook420-4.2_1
=> SHA256
Hi Andrei,
Andrei Brezan:
You can check /var/db/ports/postfix/options to see what options you
have for postfix. I think it's easier if you can tell us the output
of "uname -a" plus the exact command you try when you get this
error. I'm not sure what you want to achieve,
fgn env make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! mail/dovecot2 (unknown build error)
Command failed [exit code 1]: /usr/local/sbin/portinstall mail/dovecot2
how can I solve this issue? Thanks,
Jos Chrispi
I lately read more often that Portmaster is preferred about portupdate.
Can you tell me why this is? I know that portupdate is Ruby driven, but
furthermore I cannot detect the real advantages one above the other?
Best regards,
Jos Chrispijn
not define STAGEDIR in command line
-- cut --
I checked UPDATING but cannot discover what may be the problem here?
Can someone tell me how to fix this?
Thanks,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http
was not quite clear that I also should run the
/pixman update.
Best regards,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-uns
ed / *:skipped / !:failed)
! x11-toolkits/gtk20 (gtk-2.24.19_2)(new compiler error)
--- end of log ---
Perhaps gnome@ can tell us more about it? Untill this update, all
portupdates I have run were processed without problems.
Best regards,
Jos Chrispijn
__
er error)
--- cut ---
Can you pls tell me how to solve or should I wait for the next port
update?
Thanks in advance,
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscri
Jos Chrispijn:
References
1. http://vuxml.org/freebsd/ebd877b9-7ef4-4375-b1fd-c67780581898.html
Thanks, that is a quick response - is there a mechanism that prevents such
version to be put into a portupgrade anyway?
Jos Chrispijn
___
freebsd
ped / !:failed)
- lang/ruby18 (marked as IGNORE)
Can you pls provide a fix or should I wait for next upgrade?
Thanks,
Jos Chrispijn
References
1. http://vuxml.org/freebsd/ebd877b9-7ef4-4375-b1fd-c67780581898.html
___
freebsd-po
Bryan Drewery:
On 9/25/2013 2:17 AM, Jos Chrispijn wrote:
Update your ports tree. The ldconfig error was fixed a few days ago.
Done and fixed - thanks.
BR, Jos Chrispijn
-- Artificial intelligence is no match for natural stupidity
Hi Bryan,
Bryan Drewery:
Sorry for the trouble. I just committed a fix.
No worries - it's human effort after all.
Thanks for your support & keep up the good wojk!
Jos Chrispijn
___
freebsd-ports@freebsd.org mailing
1 - 100 of 152 matches
Mail list logo