1111
___ 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/175815[update]: databases/tarantool up to latest o ports/175814Boost-all cannot use libc++ f ports/175813[patch] mail/dovecot2 doesn't detect libstemmer or ext o ports/175812[patch] misc/findutils update to 4.5.11 f ports/175809[PATCH] www/node, www/node-devel: fix build with nonde o ports/175807New port: textproc/topic - topic markup pareser (repla o ports/175806[patch] misc/saaghar fixed some issue with portlint(1) o ports/175804cad/xcircuit update and maintainer change f ports/175798FreeBSD 10 unable to build sysutils/fusefs-kmod o ports/175795[maintainer] update devel/liblnk to 20130202 o ports/175787[NEW PORT] devel/py27-robotframework-selenium2library: o ports/175786[NEW PORT] devel/py27-robotframework: Robot Framework f ports/175779[update]: audio/liblastfm update to latest new version o ports/175772Update to finance/php-tclink o ports/175765imspector ipfw support o ports/175748New port: www/your-freedom A SOCKS proxy application f ports/175745sysutils/coreutils build fails o ports/175744[MAINTAINER] sysutils/gigolo: [SUMMARIZE CHANGES] f ports/175733devel/libatomic_ops: Segmentation fault : install - o ports/175723postfix+dovecot+ldap_sasl marked BROKEN o ports/175704[patch] add new vuxml entry for dns/poweradmin o ports/175678New port: misc/saghar A persian poetry software. o ports/175677[update]: devel/eblob fix distinfo of github files f ports/175656[patch] databases/sqlite3: update to 3.7.15.2 f ports/175642www/wordpress: update to 3.5.1,1 o ports/175634[PATCH] unbreak graphics/kdegraphics3 build when clang o ports/175631support WITHOUT_GCC in games/lwjgl f ports/175623[PATCH] graphics/geos: update to 3.3.7 f ports/175621update net/dhcpcd o ports/175620New port: devel/bashdb, Bash debugger o ports/175612New port: devel/remake version of GNU make utility th f ports/175611sysutils/zfs-periodic package do not enable cron to ho o ports/175601[update]: science/massxpert up to latest version o ports/175559[new port]: textproc/libflate Template library used to o ports/175552[NEW PORT] devel/chruby: Changes the current Ruby o ports/175542[PATCH] new port comms/ebook2cwgui o ports/175541[PATCH] databases/py-swiftclient Fixed broken distfile o ports/175536[MAINTAINER] japanese/mecab-ipadic: Fix wrong options f ports/175534[patch] net-mgmt/rackmonkey: Fix a redirect o ports/175527security/expiretable doesn't work in FreeBSD 9.x f ports/175523pkgng: mail/dovecot2-pigeonhole conflicts with mail/do o ports/175497sysutils/boxbackup rc.d files have wrong path f ports/175492net-mgmt/zabbix2-frontend: Missing php5-gettext depend o ports/175488[new port]: devel/libxs Open source lightweight messa o ports/175480[MAINTAINER] dns/powerdns: update to 3.2 f ports/175457[patch] net-mgmt/nagiosql update to 3.2.0 SP2 and othe o ports/175455devel/bmake: update to 20121212 snapshot o ports/175451update port www/cas o ports/175450[patch] Get misc/gkx86info2 plugin to build on amd64 o ports/175444Port Update: finance/frontaccounting Version update. f ports/175429audio/clementine-player: build error o ports/175428[MAINTAINER] www/drush: add more missing dependencies o ports/175398fix patches in japanese/kon2-16dot o ports/175391New port: textproc/xmlgen - generate XML in TCL o ports/175385dns/fastresolve does not compile f ports/175380[patch] mail/fetchyahoo: update to latest to work with f ports/175373[patch] mail/getlive: need to update to latest CVS ver f ports/175359[PATCH] finance/openerp-server: bump up version to 6.0 f ports/175358[PATCH] finance/openerp-web: update to 6.0.4 o ports/175337New port: devel/pecl-parsekit - static analysis o ports/175331[PATCH] Many little spelling corrections f ports/175321Update mail/postfixadmin to 2.3.6 f ports/175316multimedia/xbmc 12.0.rc3 build error o ports/175310[maintainer update]
FreeBSD Port: lilypond-2.16.0
Hi, could you please update the port to LilyPond 2.16.2 from January, 4th? That would be very nice! King regards, Hans Prinzhorn -- Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/ ___ 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: lilypond-2.16.0
On 2013-Feb-04, 14:11, Hans Prinzhorn wrote: Hi, Hello Hans, could you please update the port to LilyPond 2.16.2 from January, 4th? That would be very nice! From what I read on the lilypond website, 2.16.2 is a bug-fix release that is only relevant to people running on Windows. Quoting: LilyPond 2.16.2 released! January 4, 2013 We are happy to announce the release of LilyPond 2.16.2. This release is mainly to correct a problem with lilypond-book running on Windows. We recommend that only people requiring this functionality upgrade to this version. For this reason I avoided updating our port. Is there any other reasons you want it updated? Regards, -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp9whvZDRFxO.pgp Description: PGP signature
pkgng - one ervery day anoying problem
Hi there, from time to time I do this , | portsnap fetch update portupgrade --fetch-only --all --keep-going ` Always, realy always(!)comes this message: , | Stale dependency: de-libreoffice-3.5.7 -- nss-3.14 -- manually run 'pkgdb -F' to fix, or specify -O to force. ` I get this every time - again and again. Well, I cannot run 'pkgdb -F' and pkg check does not help anyrthing. WHAT TO DO? Heino ___ 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: pkgng - one ervery day anoying problem
You might want to look at this: https://github.com/pkgtools/pkgtools/issues/44 In the meantime, could you deinstall/reinstall libreoffice? No guarantees, but maybe it'll clean things up. -- Daniel Nebdal On Mon, Feb 4, 2013 at 3:32 PM, Heino Tiedemann rotkaps_spam_t...@gmx.dewrote: Hi there, from time to time I do this , | portsnap fetch update portupgrade --fetch-only --all --keep-going ` Always, realy always(!)comes this message: , | Stale dependency: de-libreoffice-3.5.7 -- nss-3.14 -- manually run 'pkgdb -F' to fix, or specify -O to force. ` I get this every time - again and again. Well, I cannot run 'pkgdb -F' and pkg check does not help anyrthing. WHAT TO DO? Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
I need help with git
I'm the maintainer for security/barnyard2. The software recently changed
so that all distros are pulled from github. The developers made new
commits, and now the port is broken, and I cannot figure out how to fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2
PORTVERSION=1.11
CATEGORIES= security
MAINTAINER= pa...@utdallas.edu
COMMENT=Interpreter for Snort unified2 binary output files
LICENSE=GPLv2
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= master
GH_COMMIT= 4dfdc80
The master tagname apparently gets moved to the new commit every time the
developers commit changes. This is NOT what I want. I want the port to
stay at the release version until a new version is released.
I've tried everything I can think of to get this port to pull the commit I
want. It does not work. I've tried changing the tagname to v2-1.11,
v2-${PORTVERSION}, stable, dev-next, etc., etc. Nothing works.
Here's the git site: https://github.com/firnsy/barnyard2/commits/master
If I pull master, I get commit f57e464. That's not what I want. Why
doesn't this thing pull the commit I'm telling it to pull?
I'm so frustrated by this I'm about to drop this port. I do NOT want to
have to update the port every time the developers commit more code. That
is NOT how software should work.
Is there anyone who can tell me how to fix this problem so the port will
remain at the release version until the next version is released no matter
how many commits the developers make?
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: I need help with git
On Mon, Feb 4, 2013, at 11:21 AM, Paul Schmehl wrote: I'm the maintainer for security/barnyard2. The software recently changed so that all distros are pulled from github. The developers made new commits, and now the port is broken, and I cannot figure out how to fix it. I am no git expert so this is just a guess but can you pull from a specific tag? https://github.com/firnsy/barnyard2/commits/v2-1.11 Looks like they tag the master branch at release. -- Chess Griffin ___ 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: I need help with git
On Monday, February 4, 2013, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently changed
so that all distros are pulled from github. The developers made new
commits, and now the port is broken, and I cannot figure out how to fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2
PORTVERSION=1.11
CATEGORIES= security
MAINTAINER= pa...@utdallas.edu
COMMENT=Interpreter for Snort unified2 binary output files
LICENSE=GPLv2
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= master
You need to change th GH_TAGNAME to the release you want if you go to the
repository on github and you can find the tags that the maintainers have
added to the project.
If you want a snapshot in time that is not tagged you could either request
the authors tag it, or fork it on github tag it yourself and put your own
account as the GH_ACCOUNT.
GH_COMMIT= 4dfdc80
Probably not needed if you specify a tag other than master.
The master tagname apparently gets moved to the new commit every time the
developers commit changes. This is NOT what I want. I want the port to
stay at the release version until a new version is released.
I've tried everything I can think of to get this port to pull the commit I
want. It does not work. I've tried changing the tagname to v2-1.11,
v2-${PORTVERSION}, stable, dev-next, etc., etc. Nothing works.
Here's the git site: https://github.com/firnsy/**
barnyard2/commits/masterhttps://github.com/firnsy/barnyard2/commits/master
If I pull master, I get commit f57e464. That's not what I want. Why
doesn't this thing pull the commit I'm telling it to pull?
I'm so frustrated by this I'm about to drop this port. I do NOT want to
have to update the port every time the developers commit more code. That
is NOT how software should work.
Is there anyone who can tell me how to fix this problem so the port will
remain at the release version until the next version is released no matter
how many commits the developers make?
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
__**_
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-portshttp://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: I need help with git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/4/13 11:21 AM, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers
made new commits, and now the port is broken, and I cannot figure
out how to fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2 PORTVERSION=1.11 CATEGORIES=
security
MAINTAINER= pa...@utdallas.edu COMMENT=Interpreter for
Snort unified2 binary output files
LICENSE=GPLv2
USE_GITHUB= yes GH_ACCOUNT= firnsy GH_PROJECT=
${PORTNAME} GH_TAGNAME= master GH_COMMIT= 4dfdc80
The master tagname apparently gets moved to the new commit every
time the developers commit changes. This is NOT what I want. I
want the port to stay at the release version until a new version is
released.
I've tried everything I can think of to get this port to pull the
commit I want. It does not work. I've tried changing the tagname
to v2-1.11, v2-${PORTVERSION}, stable, dev-next, etc., etc.
Nothing works.
Here's the git site:
https://github.com/firnsy/barnyard2/commits/master
If I pull master, I get commit f57e464. That's not what I want.
Why doesn't this thing pull the commit I'm telling it to pull?
I'm so frustrated by this I'm about to drop this port. I do NOT
want to have to update the port every time the developers commit
more code. That is NOT how software should work.
Is there anyone who can tell me how to fix this problem so the port
will remain at the release version until the next version is
released no matter how many commits the developers make?
Hi Paul,
I just changed this line:
GH_TAGNAME= master
to this:
GH_TAGNAME= v2-1.11
and it worked fine.
FWIW,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlEP5MkACgkQ0sRouByUApDsCwCePQYMCZ6/Avm0lUSbGazexoz5
kBkAnjLstH0h/pZ4y52BMZVgh9uFYFcv
=5E4Z
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
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 +-+ devel/pmd | 3.7 | 5.0.2 +-+ net/latd| 1.29| 1.31 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org 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
Re: I need help with git
--On February 4, 2013 8:33:06 AM -0800 Micheas Herman m...@micheas.net wrote:
On Monday, February 4, 2013, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers made
new commits, and now the port is broken, and I cannot figure out how to
fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2
PORTVERSION= 1.11
CATEGORIES= security
MAINTAINER= pa...@utdallas.edu
COMMENT= Interpreter for Snort unified2 binary output files
LICENSE= GPLv2
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= master
You need to change th GH_TAGNAME to the release you want if you go to the
repository on github and you can find the tags that the maintainers have
added to the project.
If you want a snapshot in time that is not tagged you could either
request the authors tag it, or fork it on github tag it yourself and put
your own account as the GH_ACCOUNT.
So now I have to maintain a git repository just to maintain my port? No
thanks. I'll abandon it first. This is volunteer work. I'm not going to
double my workload just because the system changed and doesn't work as
expected.
GH_COMMIT= 4dfdc80
Probably not needed if you specify a tag other than master.
According to /usr/ports/Mk/bsd.sites.mk, GH_COMMIT is mandatory.
# In order to use GitHub your port must define USE_GITHUB and the following
# variables:
#
# GH_ACCOUNT- account name of the GitHub user hosting the project
# default: not set, mandatory
#
# GH_PROJECT- name of the project on GitHub
# default: ${PORTNAME}
#
# GH_TAGNAME- name of the tag to download (master, 2.0.1, ...)
# default: ${DISTVERSION}
#
# GH_COMMIT - first 7 digits of the commit that generated GH_TAGNAME
# (man git-describe(1))
# default: not set, mandatory
#
Never mind. I finally figured it out. I had to change GH_TAGNAME to
v2-${PORTVERSION}. Now it pulls the commit for the release version as
desired.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: I need help with git
On Mon, 04 Feb 2013 10:21:35 -0600
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers
made new commits, and now the port is broken, and I cannot figure out
how to fix it. Here's the relevant code from the Makefile:
PORTNAME= barnyard2 PORTVERSION=1.11 CATEGORIES=
security MAINTAINER= pa...@utdallas.edu
COMMENT=Interpreter for Snort unified2 binary output files
LICENSE=GPLv2
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= master
GH_COMMIT= 4dfdc80
The master tagname apparently gets moved to the new commit every time
the developers commit changes. This is NOT what I want. I want the
port to stay at the release version until a new version is released.
I've tried everything I can think of to get this port to pull the
commit I want. It does not work. I've tried changing the tagname to
v2-1.11, v2-${PORTVERSION}, stable, dev-next, etc., etc. Nothing
works. Here's the git site:
https://github.com/firnsy/barnyard2/commits/master If I pull
master, I get commit f57e464. That's not what I want. Why doesn't
this thing pull the commit I'm telling it to pull? I'm so frustrated
by this I'm about to drop this port. I do NOT want to have to update
the port every time the developers commit more code. That is NOT how
software should work. Is there anyone who can tell me how to fix this
problem so the port will remain at the release version until the next
version is released no matter how many commits the developers make?
Hi Paul,
Could you revisit what I write to you about this a couple of months ago?
I just tried changing GH_TAGNAME to v2-1.11 in Makefile and it just
worked fine (by the way, that's what I suggested back then, you should
never depend on master, since it is a moving target)
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= v2-1.11
GH_COMMIT= 4dfdc80
Are you sure there's nothing left in your build environment that stops
you from building the port successfully?
Cheers,
--
Michael Gmelin
___
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: I need help with git
--On February 4, 2013 5:36:02 PM +0100 Michael Gmelin free...@grem.de
wrote:
Hi Paul,
Could you revisit what I write to you about this a couple of months ago?
I just tried changing GH_TAGNAME to v2-1.11 in Makefile and it just
worked fine (by the way, that's what I suggested back then, you should
never depend on master, since it is a moving target)
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= v2-1.11
GH_COMMIT= 4dfdc80
Are you sure there's nothing left in your build environment that stops
you from building the port successfully?
Somehow I missed your response. I figured it out before seeing your email
though, but thanks for providing the correct answer.
Cheers,
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: I need help with git
--On February 4, 2013 11:41:45 AM -0500 Greg Larkin glar...@freebsd.org
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/4/13 11:21 AM, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers
made new commits, and now the port is broken, and I cannot figure
out how to fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2 PORTVERSION=1.11 CATEGORIES=
security
MAINTAINER= pa...@utdallas.edu COMMENT=Interpreter for
Snort unified2 binary output files
LICENSE=GPLv2
USE_GITHUB= yes GH_ACCOUNT= firnsy GH_PROJECT=
${PORTNAME} GH_TAGNAME= master GH_COMMIT= 4dfdc80
The master tagname apparently gets moved to the new commit every
time the developers commit changes. This is NOT what I want. I
want the port to stay at the release version until a new version is
released.
I've tried everything I can think of to get this port to pull the
commit I want. It does not work. I've tried changing the tagname
to v2-1.11, v2-${PORTVERSION}, stable, dev-next, etc., etc.
Nothing works.
Here's the git site:
https://github.com/firnsy/barnyard2/commits/master
If I pull master, I get commit f57e464. That's not what I want.
Why doesn't this thing pull the commit I'm telling it to pull?
I'm so frustrated by this I'm about to drop this port. I do NOT
want to have to update the port every time the developers commit
more code. That is NOT how software should work.
Is there anyone who can tell me how to fix this problem so the port
will remain at the release version until the next version is
released no matter how many commits the developers make?
Hi Paul,
I just changed this line:
GH_TAGNAME= master
to this:
GH_TAGNAME= v2-1.11
and it worked fine.
Thanks, Greg. That is the correct answer.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: security/gnupg
On 2 February 2013 12:26, Chris Rees utis...@gmail.com wrote: On 2 Feb 2013 16:51, Thomas Mueller mueller6...@bellsouth.net wrote: /etc/make.conf, use OPTIONS_SET=list of options. You can also use UNSET in the same way for the converse. Setting BATCH=yes stops the dialogs appearing. BATCH does more than just stopping the dialog. It changes how patch(1) behaves, it adds BATCH=yes to the environment, disables some ports, etc. Instead define NO_DIALOG in /etc/make.conf -- Eitan Adler ___ 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: GNU style getopt problem
## Beeblebrox (zap...@berentweb.com): Interesting - when I switch to bash and try it: getopt --help 2 1 | grep long bash: syntax error near unexpected token `' Ah, bash... while this one gives no message - I guess I'll try a test with this. $ getopt --help 21 | grep long After I re-checked this: only 21 is correct and (hopefully) portable, everything else may or may not work, that is, fail on every other different platform/shell. Regards, Christoph -- Spare Space ___ 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
[CFT+BRAINSTORM] One USE_ to rule them all
Hi, I have some improvements to the ports tree to propose, and I'm looking for testers/opinions First let me explain: I want to introduce a new USE_FEATURES macro into the ports tree The goal of this macros is to be able to standardize how we call all the USE_* things as well as creating some load on demand code for a corresponding feature. What I expect in long term is to get a more readable bsd.port.mk friends, meaning easier to maintain I except some performance improvements given that make will have to parse less things. I also expect less complexity if bsd.*.mk code. What will have is all/most of the code corresponding to a USE_SOMETHING right now will endup in a Mk/features/something.mk which will be loaded only if the ports defines: USE_FEATURES= something the loading is done at the very early stage of bsd.port.post.mk to allow one to load modify USE_FEATURES depending on some options etc. each features/*.mk is itself protected by a variable to avoid multi loading of the same file if a feature depends on another one the feature itself just have to .include the other one. As a proof of concept I made the following: USE_FEATURES= gmake (with a compatibility for USE_GMAKE to allow migration) USE_FEATURES= iconv (with a compatibility for USE_ICONV to allow migration) USE_FEATURES= motif (with no compatibility as I have switched all the USE_MOTIF ports to use it) USE_FEATURES= fise (with no compatibility as I have switched all the USE_FUSE to use it) USE_FEATURES= display (with no compatibilify as I have switched all the USE_DISPLAY to use it) USE_FEATURES= pathfix (which is the equivalent of USE_GNOME= gnomehack without the need to loading the whole bsd.gnome.mk) The very long term goal will be to switch as much code as possible to be turn into a feature (when it makes sens of course) The USE_FEATURES itself: http://people.freebsd.org/~bapt/features.diff The modified ports for the PoC: http://people.freebsd.org/~bapt/features-chase.diff regards, Bapt pgpKH2mDyx4Xx.pgp Description: PGP signature
Re: [CFT+BRAINSTORM] One USE_ to rule them all
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04-02-2013 19:19, Baptiste Daroussin wrote: Hi, I have some improvements to the ports tree to propose, and I'm looking for testers/opinions First let me explain: I want to introduce a new USE_FEATURES macro into the ports tree The goal of this macros is to be able to standardize how we call all the USE_* things as well as creating some load on demand code for a corresponding feature. What I expect in long term is to get a more readable bsd.port.mk friends, meaning easier to maintain I except some performance improvements given that make will have to parse less things. I also expect less complexity if bsd.*.mk code. What will have is all/most of the code corresponding to a USE_SOMETHING right now will endup in a Mk/features/something.mk which will be loaded only if the ports defines: USE_FEATURES= something the loading is done at the very early stage of bsd.port.post.mk to allow one to load modify USE_FEATURES depending on some options etc. each features/*.mk is itself protected by a variable to avoid multi loading of the same file if a feature depends on another one the feature itself just have to .include the other one. This sounds like a good idea to me. As a proof of concept I made the following: USE_FEATURES= gmake (with a compatibility for USE_GMAKE to allow migration) USE_FEATURES= iconv (with a compatibility for USE_ICONV to allow migration) USE_FEATURES= motif (with no compatibility as I have switched all the USE_MOTIF ports to use it) USE_FEATURES= fise (with no compatibility as I have switched all the USE_FUSE to use it) USE_FEATURES= display (with no compatibilify as I have switched all the USE_DISPLAY to use it) USE_FEATURES= pathfix (which is the equivalent of USE_GNOME= gnomehack without the need to loading the whole bsd.gnome.mk) The very long term goal will be to switch as much code as possible to be turn into a feature (when it makes sens of course) Are you saying that some USE_BLAH=yes will stick around or do I misunderstand? Another question: for USE_BLAH=yes the logical transformation would be USE_FEATURES=BLAH but what about USE_FOO=BLAH ? Would USE_FEATURES=FOO/BLAH (possibly another separator) or USE_FEATURES=BLAH be more sensible? The USE_FEATURES itself: http://people.freebsd.org/~bapt/features.diff The modified ports for the PoC: http://people.freebsd.org/~bapt/features-chase.diff You could commit the header updates already if possible, which also makes the patch more readable. Regards, René -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJREAOzAAoJEKipqUGAIxKQLXsQAJDecygfd5cWSbKtt7P5yBGm 1xqPKiPI6bbyGzykob72woPFWK9bl0mS+JN0TYEaecHyQDyc59BauuaMJYWzveZS tXwW9pB6z5CdSy7jMtpD7OF2OofWCP3ZZU4XIkfqBUFXryM9OB083btx6asn3ygX l5FY1HG0RukhngCFOgrIer9SkAg0oJ89bL40NVOhXROV09MAdP3zGw/piojQXlyF TuaavqCKqLcHFUbw5yKvwFUkYRRECoAflob1Yi7pVKT9y9cXCQKnEB0Cwwv9QECL WWOKW3adPJ47HhoQYhJcVyyXAmP25J+k+WqBZxboY64ASIoj8HkVWHogOx917mDk nANm5q0ccaPI6yFvUkb0RKbtSbEChXM8ahiw7H6r79CKzh2GE5es+ZUVllAfmO/w Nz23w5aT43G8iYOmv42RSHgUOSxEQTGccumpWZPGABgEoubwXs4m/65TTl20NmRQ m/bVU0dDfiBIoVRuo1g4StM0wiW7ATh+ne/KJ0GR19qQ0DUsu9iC9+OeEF7Vko69 4Hp2Y0UVzjAniSAjVyK6nsWKlPQh88XeUWP5t/d7eD3KPEAWyv/yU65KhK33e+u/ MDHAuEfuOB5lBa9n8J3KMTdLb6yoQjudDnKRNhd8rxCX+UMq6wVxEO31nQnl2fll Y1yqj3eGdp1x2R9G0xC3 =qpKQ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng - one ervery day anoying problem
Daniel Nebdal dneb...@gmail.com wrote: You might want to look at this: https://github.com/pkgtools/pkgtools/issues/44 In the meantime, could you deinstall/reinstall libreoffice? No guarantees, but maybe it'll clean things up. I reinstalled it with -O , but the problem still there ___ 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 new pkg - is there any wildcard support?
Hi, ../ports/UPDATING: # pkg_delete -f kdemultimedia-4\* kdenetwork-4\* kde-workspace-4\* kde-runtime-4\* okay, the new pkg has no underline: # pkg delete -f kdemultimedia-4\* kdenetwork-4\* kde-workspace-4\* kde-runtime-4\* Package(s) not found! is there any wildcard support for the new pkg? Heino ___ 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: the new pkg - is there any wildcard support?
On 4 February 2013 13:26, Heino Tiedemann rotkaps_spam_t...@gmx.de wrote: # pkg delete -f kdemultimedia-4\* kdenetwork-4\* kde-workspace-4\* kde-runtime-4\* Package(s) not found! is there any wildcard support for the new pkg? pkg help delete use the -g flag for glob or -x or -X for regex. -- Eitan Adler ___ 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: pkgng - one ervery day anoying problem
Daniel Nebdal dneb...@gmail.com wrote: You might want to look at this: https://github.com/pkgtools/pkgtools/issues/44 In the meantime, could you deinstall/reinstall libreoffice? No guarantees, but maybe it'll clean things up. I did Does not solve the stale dependency - it is still there :( ___ 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: pkgng - one ervery day anoying problem
Daniel Nebdal dneb...@gmail.com wrote: You might want to look at this: https://github.com/pkgtools/pkgtools/issues/44 In the meantime, could you deinstall/reinstall libreoffice? No guarantees, but maybe it'll clean things up. Even a pkgdb -fu does not help: # pkgdb -fu --- Updating the pkgdb [Rebuilding the pkgdb format:bdb_btree in /var/db/pkg ... USING PKGNG - 856 packages found (-0 +856) 100200300400500600700800 done] # portupgrade --all USING PKGNG USING PKGNG Stale dependency: de-libreoffice-3.5.7 -- shared-mime-info-1.0_1 -- manually run 'pkgdb -F' to fix, or specify -O to force. It is like writen in stone :( Heino ___ 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: the new pkg - is there any wildcard support?
On Mon, Feb 04, 2013 at 02:02:25PM -0500, Eitan Adler wrote: On 4 February 2013 13:26, Heino Tiedemann rotkaps_spam_t...@gmx.de wrote: # pkg delete -f kdemultimedia-4\* kdenetwork-4\* kde-workspace-4\* kde-runtime-4\* Package(s) not found! is there any wildcard support for the new pkg? pkg help delete use the -g flag for glob or -x or -X for regex. in next version 1.1 pkg detect a * from cli and will auto actibate globbing regards, Bapt pgpMUvGGzhprO.pgp Description: PGP signature
Re: [CFT+BRAINSTORM] One USE_ to rule them all
On Mon, Feb 04, 2013 at 07:53:39PM +0100, René Ladan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04-02-2013 19:19, Baptiste Daroussin wrote: Hi, I have some improvements to the ports tree to propose, and I'm looking for testers/opinions First let me explain: I want to introduce a new USE_FEATURES macro into the ports tree The goal of this macros is to be able to standardize how we call all the USE_* things as well as creating some load on demand code for a corresponding feature. What I expect in long term is to get a more readable bsd.port.mk friends, meaning easier to maintain I except some performance improvements given that make will have to parse less things. I also expect less complexity if bsd.*.mk code. What will have is all/most of the code corresponding to a USE_SOMETHING right now will endup in a Mk/features/something.mk which will be loaded only if the ports defines: USE_FEATURES= something the loading is done at the very early stage of bsd.port.post.mk to allow one to load modify USE_FEATURES depending on some options etc. each features/*.mk is itself protected by a variable to avoid multi loading of the same file if a feature depends on another one the feature itself just have to .include the other one. This sounds like a good idea to me. As a proof of concept I made the following: USE_FEATURES= gmake (with a compatibility for USE_GMAKE to allow migration) USE_FEATURES= iconv (with a compatibility for USE_ICONV to allow migration) USE_FEATURES=motif (with no compatibility as I have switched all the USE_MOTIF ports to use it) USE_FEATURES= fise (with no compatibility as I have switched all the USE_FUSE to use it) USE_FEATURES= display (with no compatibilify as I have switched all the USE_DISPLAY to use it) USE_FEATURES=pathfix (which is the equivalent of USE_GNOME= gnomehack without the need to loading the whole bsd.gnome.mk) The very long term goal will be to switch as much code as possible to be turn into a feature (when it makes sens of course) Are you saying that some USE_BLAH=yes will stick around or do I misunderstand? The goal is to remove as much USE_* as possible, but I m sure but might be complicated Another question: for USE_BLAH=yes the logical transformation would be USE_FEATURES=BLAH but what about USE_FOO=BLAH ? Would USE_FEATURES=FOO/BLAH (possibly another separator) or USE_FEATURES=BLAH be more sensible? USE_FEATURE= BLAH is best imho regards, bapt pgpL15mT155ko.pgp Description: PGP signature
Re: New version of TeX?
04.02.2013 10:21, Dominic Fandrey пишет:
On 04/02/2013 02:04, Danilo Egea wrote:
Well, there is this project http://code.google.com/p/freebsd-texlive/
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171571
I use the patch from this PR together with the attached diff
and portmaster seems to DTRT with dependencies.
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
Index: /usr/ports/print/teTeX/Makefile
===
--- /usr/ports/print/teTeX/Makefile (revision 310505)
+++ /usr/ports/print/teTeX/Makefile (working copy)
@@ -34,7 +34,8 @@
# in print/teTeX-base.
DEPENDS_ARGS+= BATCH=yes
-CONFLICTS= latex2e-[0-9]* tex-[0-9]* dvips-[0-9]* xdvi-[0-9]*
+CONFLICTS= latex2e-[0-9]* tex-[0-9]* dvips-[0-9]* xdvi-[0-9]* \
+ texlive-[0-9]*
.if defined(WITH_LETTERSIZE)
FLAVOR+= letter
Index: /usr/ports/print/teTeX-base/Makefile
===
--- /usr/ports/print/teTeX-base/Makefile(revision 310505)
+++ /usr/ports/print/teTeX-base/Makefile(working copy)
@@ -53,7 +53,7 @@
CFLAGS+= -I${LOCALBASE}/include -I${LOCALBASE}/include/libpng15
PKGMESSAGE=${WRKDIR}/pkg-message
CONFLICTS= ja-ptex-base-[0-9]* latex2e-[0-9]* \
- tex-[0-9]* dvips-[0-9]* xdvi-[0-9]*
+ tex-[0-9]* dvips-[0-9]* xdvi-[0-9]* texlive-base-[0-9]*
MAN1= tie.1 kpseaccess.1 kpsereadlink.1 mpost.1 \
dmp.1 dvicopy.1 dvilj.1 dvipdfm.1 \
Index: /usr/ports/print/teTeX-texmf/Makefile
===
--- /usr/ports/print/teTeX-texmf/Makefile (revision 310505)
+++ /usr/ports/print/teTeX-texmf/Makefile (working copy)
@@ -24,7 +24,7 @@
${LOCALBASE}/share/fonts/amsfonts/doc/fonts/amsfonts/00README:${PORTSDIR}/print/font-amsfonts
CONFLICTS= latex2e-[0-9]* tex-[0-9]* dvips-[0-9]* xdvi-[0-9]* \
- ja-ptext-base-[0-9]*
+ ja-ptext-base-[0-9]* texlive-texmf-[0-9]*
.include bsd.port.pre.mk
___
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: pkgng - one ervery day anoying problem
On 04/02/2013 19:06, Heino Tiedemann wrote: Daniel Nebdal dneb...@gmail.com wrote: You might want to look at this: https://github.com/pkgtools/pkgtools/issues/44 In the meantime, could you deinstall/reinstall libreoffice? No guarantees, but maybe it'll clean things up. I did Does not solve the stale dependency - it is still there :( Hi, Heino, This is a bug in portupgrade's pkgng integration: the whole 'pkgdb -Fu' thing shouldn't be necessary with pkgng's built-in sqlite database. Unfortunately the coding required to chop out the pkgdb related bits of portupgrade and replace them with equivalents via 'pkg check' isn't complete. I believe it needs some changes to 'pkg check' too, although I have no details on that. It's an annoying message, but inaccurate and you can just ignore it. You can use 'pkg check' and 'pkg info' to verify that liberoffice has the correct dependencies installed and that all those packages are correctly installed. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: pkgng - one ervery day anoying problem
Matthew Seaman matt...@freebsd.org wrote: On 04/02/2013 19:06, Heino Tiedemann wrote: Daniel Nebdal dneb...@gmail.com wrote: You might want to look at this: https://github.com/pkgtools/pkgtools/issues/44 In the meantime, could you deinstall/reinstall libreoffice? No guarantees, but maybe it'll clean things up. I did Does not solve the stale dependency - it is still there :( Hi, Heino, This is a bug in portupgrade's pkgng integration: the whole 'pkgdb -Fu' thing shouldn't be necessary with pkgng's built-in sqlite database. Unfortunately the coding required to chop out the pkgdb related bits of portupgrade and replace them with equivalents via 'pkg check' isn't complete. I believe it needs some changes to 'pkg check' too, although I have no details on that. It's an annoying message, but inaccurate and you can just ignore it. NO! portupgrade stops after thet message and does not upgrade anything! How should I ignore that? You can use 'pkg check' and 'pkg info' to verify that liberoffice has the correct dependencies installed and that all those packages are correctly installed. Yes - but libreoffice is not the fact that I am talking about. like he has here https://github.com/pkgtools/pkgtools/issues/44 it is ANY stale dependency that stops portupgrade! Heino ___ 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: I need help with git
GH_COMMIT= 4dfdc80 Probably not needed if you specify a tag other than master. If I pull master, I get commit f57e464. That's not what I want. Why doesn't this thing pull the commit I'm telling it to pull? I think the thing most people miss here is that GH_COMMIT doesn't effect what gets downloaded, it's not used like an svn rev number - it is only used to define WRKSRC When a github tarball gets extracted GH_COMMIT is part of the dir name. Which is why it is mandatory and needs to match the tag. It is just needed to work with the way github creates tarballs. It is inconvenient but github is only setup to let you download tarballs of specific tags not specific commits. If the main devs don't tag the specific points you want the only option is to fork and create your own tags. ___ 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
International Design Award Competition: Last Call for Entries, Few Days Left to Submit your Products
Last Call for Entries and Submissions Last day to submit: February 28, 2013. We would like to remind you that we are going to close our platform for submissions on February 28, 2013. It is important that you start your submission now, as the process could take up to three weeks. TO SUBMIT YOUR PROJECTS, PLEASE REFER TO THE FOLLOWING URL: http://www.adesignaward.com/registration.php?utm_source=Newsletterutm_medium=Emailutm_campaign=DesignPRWire Please be reminded that submissions are accepted under 80 different award categories, details and more information could be obtained from our website. --- Winners will be communicated on March 7, 2013 and the Public Exhibition will take place on April 15, 2013 right after Milan Design Week (9-14 April). Gala-Night will be on April 14, 2013. We also would like you to know that applications are now open for jury membership positions (for professional, academic and focus group panels), award sponsors, institutional patrons and media partners. Please remember to apply before February 15, 2013. As you may already know, currently project nominations are subject to a late entry fee of 375 Euros. Yet, there are no further fees for winners and all the services such as exhibition, yearbook inclusion, certificates and trophy will be provided free of charge including gala dinner participation. --- Please find the following introduction useful for communicating A' Design Awards with your collegues or friends: A’ (Prime) Design Award, Italy, is one of the world’s top international design awards. In a world where there are millions of products and designs launch each year, the award was born out of the desire to underline the best designs and well-designed products. A'Design Award aggressively pursues media opportunities for the winning designs and taking part in the A' Design Award is a smart decision for added visibility and publicity. A' Design Awards winners will also be included in the World Design Rankings. --- READ FURTHER DETAILS HERE: http://www.whatisadesignaward.com/?utm_source=Newsletterutm_medium=Emailutm_campaign=DesignPRWire SEE PREVIOUS YEARS' WINNERS HERE: http://www.designmag.org?utm_source=Newsletterutm_medium=Emailutm_campaign=DesignPRWire FOR FURTHER DETAILS AND AN INTRODUCTION, PLEASE REFER TO: http://www.whatisadesigncompetition.com/?utm_source=Newsletterutm_medium=Emailutm_campaign=DesignPRWire QUESTIONS COMMENTS? PLEASE - CONTACT US HERE: http://www.adesignaward.com/contact.html?utm_source=Newsletterutm_medium=Emailutm_campaign=DesignPRWire This email has been sent to po...@freebsd.org by Design-PR on behalf of A' Design Award and Competitions at 05/02/2013 02:29:48. Design-PR runs targetted communications campaigns on behalf of its clients. If you would like to report misusage, or to register complaints or provide feedbacks, please kindly contact us directly at: http://design-pr.org/report.html You can quote the unique identifier for this email as 3ZN81-3ZN81-3ZN81-3ZN81-3ZN81-3ZN81-3ZN81-3ZN81 To unsubscribe from design-pr.org design news announcements list please kindly visit: http://design-pr.org/unsubscribe.php?C=2EMAIL=po...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
nessus build fails - fatal error: 'openssl/md2.h' file not found
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #33 r246130: Wed Jan 30 15:00:08 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to build Nessus fails with: === Building for nessus-libnasl-2.2.9_1 cd nasl make /bin/sh /usr/local/bin/libtool --silent --mode compile cc -pipe -O2 -pipe -fno-strict-aliasing `sh ./cflags` -c nasl_packet_forgery.c nasl_packet_forgery.c:859:29: warning: incompatible pointer types passing 'struct ip *' to parameter of type 'u_short *' (aka 'unsigned short *') [-Wincompatible-pointer-types] ip-ip_sum = np_in_cksum(ip, ip-ip_hl * 4); ^~ nasl_packet_forgery.c:1265:23: warning: implicit declaration of function 'bpf_next_tv' is invalid in C99 [-Wimplicit-function-declaration] if(bpf = 0 (pk = bpf_next_tv(bpf, len, tv)))flag++; ^ nasl_packet_forgery.c:1265:21: warning: incompatible integer to pointer conversion assigning to 'u_char *' (aka 'unsigned char *') from 'int' [-Wint-conversion] if(bpf = 0 (pk = bpf_next_tv(bpf, len, tv)))flag++; ^ ~~~ 3 warnings generated. /bin/sh /usr/local/bin/libtool --silent --mode compile cc -pipe -O2 -pipe -fno-strict-aliasing `sh ./cflags` -c nasl_socket.c /bin/sh /usr/local/bin/libtool --silent --mode compile cc -pipe -O2 -pipe -fno-strict-aliasing `sh ./cflags` -c nasl_crypto.c nasl_crypto.c:25:10: fatal error: 'openssl/md2.h' file not found #include openssl/md2.h ^ 1 error generated. *** [nasl_crypto.o] Error code 1 Stop in /usr/ports/security/nessus-libnasl/work/libnasl/nasl. *** [all] Error code 1 Stop in /usr/ports/security/nessus-libnasl/work/libnasl. *** [do-build] Error code 1 Stop in /usr/ports/security/nessus-libnasl. *** [lib-depends] Error code 1 Stop in /usr/ports/security/nessus. Should I file a PR? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng - one ervery day anoying problem
On 04/02/2013 21:42, Heino Tiedemann wrote: NO! portupgrade stops after thet message and does not upgrade anything! How should I ignore that? Use portmaster instead? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
