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
signatu
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
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
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 wh
Matthew Seaman wrote:
> On 04/02/2013 19:06, Heino Tiedemann wrote:
>> Daniel Nebdal 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 u
On 04/02/2013 19:06, Heino Tiedemann wrote:
> Daniel Nebdal 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 s
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
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 ex
On Mon, Feb 04, 2013 at 02:02:25PM -0500, Eitan Adler wrote:
> On 4 February 2013 13:26, Heino Tiedemann 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?
>
>
Daniel Nebdal 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
[Rebuildi
Daniel Nebdal 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 :(
On 4 February 2013 13:26, Heino Tiedemann 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
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
Daniel Nebdal 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
_
-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
>
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 "
## 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 2>&1 | grep long
After I
On 2 February 2013 12:26, Chris Rees wrote:
> On 2 Feb 2013 16:51, "Thomas Mueller" 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 dialo
--On February 4, 2013 11:41:45 AM -0500 Greg Larkin
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 comm
--On February 4, 2013 5:36:02 PM +0100 Michael Gmelin
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 depen
On Mon, 04 Feb 2013 10:21:35 -0600
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 rele
--On February 4, 2013 8:33:06 AM -0800 Micheas Herman 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, an
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
-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
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
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
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
PORTV
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 wrote:
> Hi there,
>
>
> from time to tim
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.
`
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:
"
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 lis
(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 obsol
___
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"
33 matches
Mail list logo
