Re: net/p5-Net-Twitter broken

[andrew clarke]

On Mon 2009-07-13 21:31:38 UTC+0200, Cezary Morga (c...@therek.net) wrote:

> First off, I'd start from something like following an look for any
> 'missing' modules, or ones that have wrong (too old) version number.
> 
> cd /usr/ports/net/p5-Net-Twitter && make clean configure

Net::Twitter 3.03000 is now failing with a missing dependency.

16:17 ozzmo...@blizzard [/usr/ports/net/p5-Net-Twitter]sudo make clean configure
===>  Cleaning for p5-Net-Twitter-3.03000
===>  Vulnerability check disabled, database not found
===>  Extracting for p5-Net-Twitter-3.03000
=> MD5 Checksum OK for Net-Twitter-3.03000.tar.gz.

...

- MooseX::MultiInitArg ...missing.
*** Module::AutoInstall configuration finished.
Checking if your kit is complete...
Looks good
Warning: prerequisite MooseX::MultiInitArg 0 not found.
Writing Makefile for Net::Twitter

Is MooseX::MultiInitArg hidden somewhere in the ports tree?

Thanks,

Regards
Andrew
___
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 currency.

[Julian Elischer]

FreeBSd was just added to the survey of "how fresh are the packages on 
a distro" survey at:


  http://oswatershed.org/

I think we are doing ok..

it's preliminary data only and
one should not read too much into it.

julian

___
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: BIND help

[Doug Barton]

On Jul 29, 2009, at 6:06 PM, "Albert Thiel"  
 wrote:


I know you don't support Version 7.0 release since April, but the  
BIND patch

on freebsd.org's main site... will it work?


The patch is quite simple, so yes.

I tried compiling the 9.4.3-P3 on a 7.0 box and it does compile but  
will not

run.


I assume you mean the port? What do you mean by it won't run? How are  
you starting it?


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

BIND help

[Albert Thiel]

I know you don't support Version 7.0 release since April, but the BIND patch
on freebsd.org's main site... will it work?

I tried compiling the 9.4.3-P3 on a 7.0 box and it does compile but will not
run.  Zero day exploits are not fun..

My opinion is that you should support this on v6 and up due to the extremity
of the flaw.

Any help would be appreciated.  I have newer boxes with patches applied but
a few are older and I really don't have time to up them all right at the
moment... ver6 and ver7 mixed.


Thanks,

-Al
___
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: BIND help

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Albert Thiel wrote:
> I know you don't support Version 7.0 release since April, but the BIND patch
> on freebsd.org's main site... will it work?

Yes, the fix do work for 7.0.

> I tried compiling the 9.4.3-P3 on a 7.0 box and it does compile but will not
> run.  Zero day exploits are not fun..
> 
> My opinion is that you should support this on v6 and up due to the extremity
> of the flaw.
> 
> Any help would be appreciated.  I have newer boxes with patches applied but
> a few are older and I really don't have time to up them all right at the
> moment... ver6 and ver7 mixed.

However, it would be good to upgrade to a supported release according to
your maintenance plan, when possible.  You can use freebsd-update to do
the upgrade.

Cheers,
- --
Xin LI http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpw9ocACgkQi+vbBBjt66D2EQCdFEadtHLQWLezA36S3YvGC91M
PrEAni/cdKOx7546YQzEN42t51NxDBOg
=pEF3
-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: BIND help

[Albert Thiel]

Thanks very much.  Will do.  Appreciate the help. -Al

Albert Thiel
ath...@yourdatacenter.com 

Your Data Center Incorporated
The home of HostLongIsland.com
Powerful FREE ISP Tools, Mail & Website Hosting
http://www.YourDataCenter.com
Hewlett, New York
Local & Intl: (516)874-5850
Toll-Free US: (877)302-8642


-Original Message-
From: owner-freebsd-po...@freebsd.org
[mailto:owner-freebsd-po...@freebsd.org]on Behalf Of Xin LI
Sent: Wednesday, July 29, 2009 9:25 PM
To: Albert Thiel
Cc: po...@freebsd.org
Subject: Re: BIND help


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Albert Thiel wrote:
> I know you don't support Version 7.0 release since April, but the BIND
patch
> on freebsd.org's main site... will it work?

Yes, the fix do work for 7.0.

> I tried compiling the 9.4.3-P3 on a 7.0 box and it does compile but will
not
> run.  Zero day exploits are not fun..
>
> My opinion is that you should support this on v6 and up due to the
extremity
> of the flaw.
>
> Any help would be appreciated.  I have newer boxes with patches applied
but
> a few are older and I really don't have time to up them all right at the
> moment... ver6 and ver7 mixed.

However, it would be good to upgrade to a supported release according to
your maintenance plan, when possible.  You can use freebsd-update to do
the upgrade.

Cheers,
- --
Xin LI http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpw9ocACgkQi+vbBBjt66D2EQCdFEadtHLQWLezA36S3YvGC91M
PrEAni/cdKOx7546YQzEN42t51NxDBOg
=pEF3
-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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Building QT4 - traps for old players.

[Stephen Hocking]

Hi all,

After some months of not being able to build qt4, with errors that
made little sense, I finally tracked the cause down - I had set the
environment variables QTDIR, QTLIB & QTBIN to point to directories in
/usr/X11R6. Once this was removed, I was able to remake everything
without errors.

Stephen
___
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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Dan Mahoney, System Admin]

On Wed, 29 Jul 2009, Doug Barton wrote:


Dan Mahoney, System Admin wrote:

The fact that the error occurs AT ALL is the bug and what is
counterintuitive, and many people would not think to try typing "make"
again, and instead would just assume the thing's broken.


Ok, I actually misunderstood the problem that you were reporting. I
thought that the reference to .build_done.bind96._usr_local indicated
that the port had already been built once, but that is not the case.
To reproduce the bug, you need to do the following:

1. Make sure there is nothing in /var/db/ports/bind96
2. cd /usr/ports/dns/bind96
3. make
4. Enable the "replace base" option
5. Save the config

You will then see the following error:

make: don't know how to make
/usr/local/tmp/usr/local/ports/dns/bind96/work/.build_done.bind96._usr_local.
Stop
*** Error code 2

I think Mel is right that the problem is changing PREFIX, but that's
the whole purpose of the option.

Could you please open a PR about this with a subject something to the
effect of "OPTIONS that change PREFIX cause an error after 'make
config'" and describe how to reproduce this?


Done, just got the mail from gnats: 137250.

-Dan

--

Pika Pika Pika!

-Pikachu, of Pokemon fame.

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.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: mail/postfix-current error: conflicting types for 'closefrom'

[Marcus Alves Grando]

Fixed now. Please update ports tree and try again.

Best regards

On Mon, 27 Jul 2009, Jorge Medina wrote:

On Mon, Jul 27, 2009 at 4:46 PM, Jorge Medina wrote:

FYI
set -e; for i in src/util src/global src/dns src/tls src/xsasl
src/milter src/master  src/postfix src/fsstone src/smtpstone
src/sendmail src/error src/pickup src/cleanup src/smtpd src/local
src/trivial-rewrite src/qmgr src/oqmgr src/smtp src/bounce  src/pipe
src/showq src/postalias src/postcat src/postconf src/postdrop
src/postkick src/postlock src/postlog src/postmap src/postqueue
src/postsuper src/qmqpd src/spawn src/flush src/verify  src/virtual
src/proxymap src/anvil src/scache src/discard src/tlsmgr
src/postmulti; do  (set -e; echo "[$i]"; cd $i; make 'CC=cc -DHAS_PCRE
-I/usr/local/include -DUSE_SASL_AUTH
-DDEF_SERVER_SASL_TYPE=\"dovecot\" -DUSE_TLS -I/usr/include
-DHAS_PGSQL -I/usr/local/include -I/usr/local/pgsql/include
-DSNAPSHOT' update MAKELEVEL=) || exit 1;  done
[src/util]
cc -DHAS_PCRE -I/usr/local/include -DUSE_SASL_AUTH
-DDEF_SERVER_SASL_TYPE=\"dovecot\" -DUSE_TLS -I/usr/include
-DHAS_PGSQL -I/usr/local/include -I/usr/local/pgsql/include -DSNAPSHOT
 -O2 -fno-strict-aliasing -pipe -I. -DFREEBSD7 -c alldig.c
cc -DHAS_PCRE -I/usr/local/include -DUSE_SASL_AUTH
-DDEF_SERVER_SASL_TYPE=\"dovecot\" -DUSE_TLS -I/usr/include
-DHAS_PGSQL -I/usr/local/include -I/usr/local/pgsql/include -DSNAPSHOT
 -O2 -fno-strict-aliasing -pipe -I. -DFREEBSD7 -c allprint.c
cc -DHAS_PCRE -I/usr/local/include -DUSE_SASL_AUTH
-DDEF_SERVER_SASL_TYPE=\"dovecot\" -DUSE_TLS -I/usr/include
-DHAS_PGSQL -I/usr/local/include -I/usr/local/pgsql/include -DSNAPSHOT
 -O2 -fno-strict-aliasing -pipe -I. -DFREEBSD7 -c argv.c
cc -DHAS_PCRE -I/usr/local/include -DUSE_SASL_AUTH
-DDEF_SERVER_SASL_TYPE=\"dovecot\" -DUSE_TLS -I/usr/include
-DHAS_PGSQL -I/usr/local/include -I/usr/local/pgsql/include -DSNAPSHOT
 -O2 -fno-strict-aliasing -pipe -I. -DFREEBSD7 -c argv_split.c
cc -DHAS_PCRE -I/usr/local/include -DUSE_SASL_AUTH
-DDEF_SERVER_SASL_TYPE=\"dovecot\" -DUSE_TLS -I/usr/include
-DHAS_PGSQL -I/usr/local/include -I/usr/local/pgsql/include -DSNAPSHOT
 -O2 -fno-strict-aliasing -pipe -I. -DFREEBSD7 -c attr_clnt.c
In file included from attr_clnt.c:77:
/usr/include/unistd.h:329: error: conflicting types for 'closefrom'
./sys_defs.h:1395: error: previous declaration of 'closefrom' was here
*** Error code 1


I change int closefrom(int) to void closefrom(int) like
/usr/include/unistd.h:329 in sys_defs.h and sys_defs.c and work ok


more information
r...@mail% uname -a
FreeBSD mail.jp.cl 7.2-STABLE FreeBSD 7.2-STABLE #0: Mon Jul 27
15:01:32 CLT 2009 mnot...@mail.jp.cl:/usr/obj/usr/src/sys/GENERIC
amd64

maybe the problem is in the line 329  of /usr/include/unistd.h
because had a type conflict with __void closefrom(int);__ after update
from source tree

--
Jorge Andrés Medina Oliva.
System Manager & BSD Software Advocacy Leader
From: http://www.bsdchile.cl
___
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"



--
Marcus Alves Grando
marcus(at)sbh.eng.br | Personal
mnag(at)FreeBSD.org  | 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: devel/boost: new patch for testing update to 1.39

[Mel Flynn]

On Monday 29 June 2009 05:44:20 Alexander Churanov wrote:

> I've made several changes to new set of boost ports. Please, review
> them and test new set of ports, if possible.

I guess I should've tested these, but I didn't expect it to replace a minor 
CONFLICTS problem that I had locally patched with a few lines, with a major 
not optional dependency on a retired compiler.

Is pyste going to be optional in a new revision or is there any chance gccxml 
can be patched so it builds cleanly with the current GCC?

If the Makefile comment is the only problem, surely it can be addressed?

# GCC-XML has some constructs that GCC 4.2 does not like. Namely,
# the use of casted-pointer-dereferences as an lvalue to post-increment
# operations.

Additionally the gccxml port seems pretty much dead. An attempt of revival has 
been done in 2007, but no release has ever been made.
-- 
Mel
___
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: after update - not all jpeg files are displayable

[Doug Barton]

Joe Marcus Clarke wrote:
> Oliver Lehmann wrote:
>> ajtiM wrote:
>>
>>> http://bbs.archlinux.org/viewtopic.php?pid=585987
>> sounds good
>> @marcus - will this fix be integrated into FreeBSDs gtk port?
> 
> Sure, but it may take me some time.

FWIW, I had the bug with gqview as well, and the cinfo->scale_denom
patch to gtk on that forum worked for me.


hth,

Doug

-- 

This .signature sanitized for your protection

___
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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Doug Barton]

Dan Mahoney, System Admin wrote:
> The fact that the error occurs AT ALL is the bug and what is
> counterintuitive, and many people would not think to try typing "make"
> again, and instead would just assume the thing's broken.

Ok, I actually misunderstood the problem that you were reporting. I
thought that the reference to .build_done.bind96._usr_local indicated
that the port had already been built once, but that is not the case.
To reproduce the bug, you need to do the following:

1. Make sure there is nothing in /var/db/ports/bind96
2. cd /usr/ports/dns/bind96
3. make
4. Enable the "replace base" option
5. Save the config

You will then see the following error:

make: don't know how to make
/usr/local/tmp/usr/local/ports/dns/bind96/work/.build_done.bind96._usr_local.
Stop
*** Error code 2

I think Mel is right that the problem is changing PREFIX, but that's
the whole purpose of the option.

Could you please open a PR about this with a subject something to the
effect of "OPTIONS that change PREFIX cause an error after 'make
config'" and describe how to reproduce this?


Thanks,

Doug

-- 

This .signature sanitized for your protection

___
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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Dan Mahoney, System Admin]

On Wed, 29 Jul 2009, Doug Barton wrote:


Mel Flynn wrote:

On Wednesday 29 July 2009 10:57:05 Doug Barton wrote:

Dan Mahoney, System Admin wrote:

I believe Mel is right here. 'make clean ; make config ; make' worked
for me.

As does a second make after getting this error, but it's nonintuitive,
and probably a ports bug.

I'm not sure why 'make clean' is nonintuitive in the context of
changing OPTIONS. What is your expectation of how it should work?


What he means is that make without arguments or make install as per handbook,
will build the build target which will invoke the config target if OPTIONS
changed or no options file is found.


In the original post the build was already done, but it had been done
with a different set of OPTIONS choices. My question is, why is
running 'make clean' in the scenario of:
1. build
2. change options
[make clean should happen here]
3. install

not intuitive?


Because in my case, the thing was already "clean" beforehand?  Two 
systems, one 6.4-PRERELEASE (6.4 release, really, it missed the release 
date by hours), the other 6.4-STABLE.  Both exhibit this with a ports tree 
cvsupped hours before this report.


make clean (or even make distclean), make rmconfig, then make still gives 
me this issue.


"run clean after changing options" is intuitive and is common sense, yes.

"run clean after running config and before building code that you haven't 
built before" does not make sense.


On a virgin port, you are thrown into the options screen by default unless 
you have BATCH set.  That's the counterintuitive part.


-Dan

--

"Happy, Sad, Happy, Sad, Happy, Sad, Happy, Intruiged!  I've never been so
in touch with my emotions!"

-AndrAIa as Hexadecimal, Reboot Episode 3.2.3

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Dan Mahoney, System Admin]

On Wed, 29 Jul 2009, Doug Barton wrote:


Dan Mahoney, System Admin wrote:


I believe Mel is right here. 'make clean ; make config ; make' worked
for me.


As does a second make after getting this error, but it's nonintuitive,
and probably a ports bug.


I'm not sure why 'make clean' is nonintuitive in the context of
changing OPTIONS. What is your expectation of how it should work?


The fact that the error occurs AT ALL is the bug and what is 
counterintuitive, and many people would not think to try typing "make" 
again, and instead would just assume the thing's broken.


(See previously referenced email)

Make clean isn't solving the problem, but I can see how you're getting 
that thought.  The problem only occurs on a virgin, untouched, 
un-configged port.


The solution to the problem in this case is to just re-run make.  There's 
nothing to CLEAN, since you haven't made yet.


The reason it seems like make clean fixes it may also because make clean 
does not do a make rmconfig: when I do an rmconfig I can successfully 
duplicate this problem, however:


Running make config then make: fine
Running just make, with no config: this error.

Thoughts?

--

"If you aren't going to try something, then we might as well just be
friends."

"We can't have that now, can we?"

-SK & Dan Mahoney,  December 9, 1998

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.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: this time it's vim/distfiles

[N.J. Mann]

In message <4ad871310907291312s6f4e1c1dx7e91e5d61b5c4...@mail.gmail.com>,
Glen Barber (glen.j.bar...@gmail.com) wrote:
> On Wed, Jul 29, 2009 at 3:26 PM, Esa Karkkainen wrote:
> > On Wed, Jul 29, 2009 at 02:59:56PM +0100, N.J. Mann wrote:
> >> Try changing distinfo accordingly.
> >
> > You can use your favourite editor or run the following commands as root
> >
> > # cd /usr/ports/editors/vim
> > # sed -I .orig -e 's/7\.2\.041%/7.2.041^/' distinfo
> >
> 
> That shouldn't fix the problem, because according to the OP's error:
> 
> => No MD5 checksum recorded for vim/7.2.041^.
> => No SHA256 checksum recorded for vim/7.2.041^.
> => No suitable checksum found for vim/7.2.041^.
> 
> Meaning, there is no checksum for the file with '^' in place of '%'.

I think you have missed the point.  The Makefile has been updated to
include the renaming of the patch file from 7.2.041% to 7.2.41^, whereas
the distinfo file _has not_.  So, the distinfo has no checksums for
7.2.041^.  Instead it has them for 7.2.041%.

So I think Esa's idea is correct.

<1 minute later>
Wesley Shields (wxs@) has just committed a fix to the distfile, so those
affected should re-sync their port trees.


Cheers,
   Nick.

-- 

___
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: this time it's vim/distfiles

[Wesley Shields]

On Wed, Jul 29, 2009 at 04:12:05PM -0400, Glen Barber wrote:
> On Wed, Jul 29, 2009 at 3:26 PM, Esa Karkkainen wrote:
> > On Wed, Jul 29, 2009 at 02:59:56PM +0100, N.J. Mann wrote:
> >> Try changing distinfo accordingly.
> >
> > You can use your favourite editor or run the following commands as root
> >
> > # cd /usr/ports/editors/vim
> > # sed -I .orig -e 's/7\.2\.041%/7.2.041^/' distinfo
> >
> 
> That shouldn't fix the problem, because according to the OP's error:
> 
> => No MD5 checksum recorded for vim/7.2.041^.
> => No SHA256 checksum recorded for vim/7.2.041^.
> => No suitable checksum found for vim/7.2.041^.
> 
> Meaning, there is no checksum for the file with '^' in place of '%'.

That sed line will replace the % with a ^, but it doesn't matter
anymore.

I just committed a fix for this. Please give it time to mirror out and
you should be fine.

-- WXS
___
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: this time it's vim/distfiles

[Glen Barber]

On Wed, Jul 29, 2009 at 3:26 PM, Esa Karkkainen wrote:
> On Wed, Jul 29, 2009 at 02:59:56PM +0100, N.J. Mann wrote:
>> Try changing distinfo accordingly.
>
> You can use your favourite editor or run the following commands as root
>
> # cd /usr/ports/editors/vim
> # sed -I .orig -e 's/7\.2\.041%/7.2.041^/' distinfo
>

That shouldn't fix the problem, because according to the OP's error:

=> No MD5 checksum recorded for vim/7.2.041^.
=> No SHA256 checksum recorded for vim/7.2.041^.
=> No suitable checksum found for vim/7.2.041^.

Meaning, there is no checksum for the file with '^' in place of '%'.



-- 
Glen Barber
___
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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Doug Barton]

Mel Flynn wrote:
> On Wednesday 29 July 2009 10:57:05 Doug Barton wrote:
>> Dan Mahoney, System Admin wrote:
 I believe Mel is right here. 'make clean ; make config ; make' worked
 for me.
>>> As does a second make after getting this error, but it's nonintuitive,
>>> and probably a ports bug.
>> I'm not sure why 'make clean' is nonintuitive in the context of
>> changing OPTIONS. What is your expectation of how it should work?
> 
> What he means is that make without arguments or make install as per handbook, 
> will build the build target which will invoke the config target if OPTIONS 
> changed or no options file is found.

In the original post the build was already done, but it had been done
with a different set of OPTIONS choices. My question is, why is
running 'make clean' in the scenario of:
1. build
2. change options
[make clean should happen here]
3. install

not intuitive?

> However, this is a corner case, as it applies to:
> - Ports that change PREFIX using OPTIONS
> - For which no options file is available or the OPTIONS list has changed
> - When the PREFIX is actually changed through toggling the appropriate option.
> 
> This applies surely to less then 100 (probably more like a dozen) ports on 
> the 
> 18k that are in the tree and only affects people who do not use ports-mgmt 
> software. As such it is not worth fixing, IMHO.

Forget this particular problem, you're right that the fact that the
ports system doesn't know how to deal with an obsoleted build-cookie
actually is a corner case.

My concern is the general user expectation of what should happen in
this scenario. If it's generally expected that magic should happen if
a users changes OPTIONS after building the port we need to make that
magic happen. Otherwise people will be installing things that are not
built the way that they think they are.


Doug

-- 

This .signature sanitized for your protection

___
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: this time it's vim/distfiles

[Esa Karkkainen]

On Wed, Jul 29, 2009 at 02:59:56PM +0100, N.J. Mann wrote:
> Try changing distinfo accordingly.

You can use your favourite editor or run the following commands as root

# cd /usr/ports/editors/vim
# sed -I .orig -e 's/7\.2\.041%/7.2.041^/' distinfo

-- 
"In the beginning the Universe was created. This has made a lot of
people very angry and been widely regarded as a bad move."
-- Douglas Adams 1952 - 2001
___
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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Mel Flynn]

On Wednesday 29 July 2009 10:57:05 Doug Barton wrote:
> Dan Mahoney, System Admin wrote:
> >> I believe Mel is right here. 'make clean ; make config ; make' worked
> >> for me.
> >
> > As does a second make after getting this error, but it's nonintuitive,
> > and probably a ports bug.
>
> I'm not sure why 'make clean' is nonintuitive in the context of
> changing OPTIONS. What is your expectation of how it should work?

What he means is that make without arguments or make install as per handbook, 
will build the build target which will invoke the config target if OPTIONS 
changed or no options file is found.

However, this is a corner case, as it applies to:
- Ports that change PREFIX using OPTIONS
- For which no options file is available or the OPTIONS list has changed
- When the PREFIX is actually changed through toggling the appropriate option.

This applies surely to less then 100 (probably more like a dozen) ports on the 
18k that are in the tree and only affects people who do not use ports-mgmt 
software. As such it is not worth fixing, IMHO.
-- 
Mel
___
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: this time it's vim/distfiles

[Doug Barton]

Scott Bennett wrote:
>  When portmaster tries to rebuild vim-lite, it tries to verify the
> checksums of 239 (?) patches. 

To be a little more accurate, the ports infrastructure is doing the
verification. Portmaster just calls 'make checksum'.

>  I looked in distfiles and found that the line in question apparently
> had an extraneous character that displays in less and vi as a percent sign.
> 
> DISTFILE:vim/7.2.040:SIZE=1836:SHA256=ad320d45c2541a767b351fdb8720c349c468acec8cf54dcfced0a6d1e58e5d8e:MD5=4c493255ae227498016f30a0002ec1cc
> DISTFILE:vim/7.2.041%:SIZE=22405:SHA256=2f48e173df3d306edd982f8a3d5a15c65ba19694ca32bdbdaa51f8bcc48a3d06:MD5=107ba5dccb1df727601aead37abf8cd3
> DISTFILE:vim/7.2.042:SIZE=4987:SHA256=d5fa884a7c5ee77b60fe512ceccaac640c0dfc00bd435211f4e4597ae3bee2cd:MD5=99baedef8a9c908774b7ed74deacf184

The information stored in /var/db/ports/*/distfiles is only used to
make sure all of the distfiles associated with a port are deleted if
the user chooses that option. The checksum information is stored, but
is not used at this time. See also
http://www.freebsd.org/cgi/query-pr.cgi?pr=106483


hth,

Doug

-- 

This .signature sanitized for your protection

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

[Fwd: Re: cvs commit: ports/dns/bind94 Makefile distinfo ports/dns/bind95 Makefile distinfo ports/dns/bind96 Makefile distinfo]

[Doug Barton]

-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

> FYI, The checksums in the bind94 distinfo file seem to be wrong.
>
> /usr/ports/dns/bind94
>
> => MD5 Checksum mismatch for bind-9.4.3-P3.tar.gz.asc.
> => SHA256 Checksum mismatch for bind-9.4.3-P3.tar.gz.asc.

They created new signature files with a different key. I've updated
the ports just now.

Unfortunately some of ISC's mirrors still have the old signature
files, so there will be a period of time that this is problematic.


Please be patient,

Doug

- --

This .signature sanitized for your protection

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEAREDAAYFAkpwnKgACgkQyIakK9Wy8Ptd9wCfdgGG3Yw4lajFH86dUgROT5Yd
wdYAn2BHCfJFeEkT9Gjt3lvQ85+yck4Q
=hM2X
-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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Doug Barton]

Dan Mahoney, System Admin wrote:

>> I believe Mel is right here. 'make clean ; make config ; make' worked
>> for me.
> 
> As does a second make after getting this error, but it's nonintuitive,
> and probably a ports bug.

I'm not sure why 'make clean' is nonintuitive in the context of
changing OPTIONS. What is your expectation of how it should work?

Doug

-- 

This .signature sanitized for your protection

___
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: after update - not all jpeg files are displayable

[Joe Marcus Clarke]

Oliver Lehmann wrote:
> ajtiM wrote:
> 
>> http://bbs.archlinux.org/viewtopic.php?pid=585987
> 
> sounds good
> @marcus - will this fix be integrated into FreeBSDs gtk port?

Sure, but it may take me some time.

Joe

> 


-- 
Joe Marcus Clarke
FreeBSD GNOME Team  ::  gn...@freebsd.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
___
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"

Updating 'boost'

[Jerry]

Now that 'boost' has been split up, what is the correct procedure to
update it. I currently have "boost-1.37.0_1" installed. Should I run
something like:

portupgrade -o devel/boost-all boost

or is there a better way. I could not find anything in UPDATING that
referenced this.

-- 
Jerry
ges...@yahoo.com

ARMADILLO: To provide weapons to a Spanish pickle.
___
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"

breaked kde3

[Oliver Pinter]

[New Thread 0x800a020b0 (LWP 100411)]
[Switching to Thread 0x800a020b0 (LWP 100411)]
[KCrash handler]
#6  0x00080ca93364 in jpeg_CreateDecompress ()
   from /usr/local/lib/compat/pkg/libjpeg.so.9
#7  0x000807744490 in read_jpeg_image () from /usr/local/lib/libqt-mt.so.3
#8  0x000807514890 in QImageIO::read () from /usr/local/lib/libqt-mt.so.3
#9  0x000807514fc3 in QImage::load () from /usr/local/lib/libqt-mt.so.3
#10 0x00080d449ac1 in KBackgroundRenderer::doWallpaper ()
   from /usr/local/lib/libkdeinit_kdesktop.so
#11 0x00080d44a6fb in KBackgroundRenderer::render ()
   from /usr/local/lib/libkdeinit_kdesktop.so
#12 0x00080d44a9e5 in KBackgroundRenderer::qt_invoke ()
   from /usr/local/lib/libkdeinit_kdesktop.so
#13 0x00080753a16e in QObject::activate_signal ()
   from /usr/local/lib/libqt-mt.so.3
#14 0x00080753adb9 in QObject::activate_signal ()
   from /usr/local/lib/libqt-mt.so.3
#15 0x0008075560ca in QTimer::event () from /usr/local/lib/libqt-mt.so.3
#16 0x0008074ec149 in QApplication::internalNotify ()
   from /usr/local/lib/libqt-mt.so.3
#17 0x0008074ecb11 in QApplication::notify ()
   from /usr/local/lib/libqt-mt.so.3
#18 0x00080b5a62c6 in KApplication::notify ()
   from /usr/local/lib/libkdecore.so.6
#19 0x0008074e386f in QEventLoop::activateTimers ()
   from /usr/local/lib/libqt-mt.so.3
#20 0x0008074a992d in QEventLoop::processEvents ()
   from /usr/local/lib/libqt-mt.so.3
#21 0x0008074ff24a in QEventLoop::enterLoop ()
   from /usr/local/lib/libqt-mt.so.3
#22 0x0008074ff12e in QEventLoop::exec ()
   from /usr/local/lib/libqt-mt.so.3
#23 0x00080d40d0e1 in kdemain ()
   from /usr/local/lib/libkdeinit_kdesktop.so
#24 0x004079d0 in execpath_avoid_loops ()
#25 0x004081a7 in execpath_avoid_loops ()
#26 0x004086f5 in execpath_avoid_loops ()
#27 0x00408f2b in main ()
___
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: updating to ghostscript8-8.64_2 fails

[Steve Randall]

On Wed, 29 Jul 2009 01:57:44 -0500 (CDT)
Scott Bennett  wrote:

>  On Tue, 28 Jul 2009 11:52:48 -0500 Steve Randall
>  wrote:
> >On Sun, 26 Jul 2009 14:36:37 -0500 (CDT)
> >Scott Bennett  wrote:
> >

> >>  Is there something I missed doing?  Or does this mean I should submit
> >> a problem report?
> >
> >=46rom looking at the source I think you must have enabled both the X
> >drivers and 256-color SVGALIB. Try running
> 
>  It's quite possible that I did, though I don't remember now.  Was there
> some piece of documentation that I missed that says that the SVGALIB support
> is incompatible with other options?

When I saw what the code was doing, it seemed familiar, so I think I
may have read it somewhere. But I don't know where, sorry.
___
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: Dropping maintainership of multimedia/gnome-subtitles

[Mark Linimon]

Done, thanks.

mcl
___
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: after update - not all jpeg files are displayable

[Oliver Lehmann]

ajtiM wrote:

> http://bbs.archlinux.org/viewtopic.php?pid=585987

sounds good
@marcus - will this fix be integrated into FreeBSDs gtk port?

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/
___
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: "ghost" ports CFLAGS

[Eric Damien]

Well, I just edited the /etc/make.conf. About the clean build directories, I
performed make clean (even if portmaster is already supposed to do so,
unless instructed otherwise); I even deleted the ports tree and made a fresh
portsnap fetch extract: no use.
Not to stay stuck, I decied to include a ports.conf in make.conf just to
switch back to the other compiler (actually gcc43/g++43), on those
problematic ports. But then again, that is a temporary solution.

Do you think there may be another path to explore ?

Thanks,

Eric Damien.

On Tue, Jul 28, 2009 at 11:34 AM, Lowell Gilbert <
freebsd-ports-lo...@be-well.ilk.org> wrote:

> Eric Damien  writes:
>
> > I edited my /etc/make.conf in order to change the default compiler via
> > the CC and CXX variables. I also happened to edit the CFLAGS value,
> > all of this changes enclosed within a conditional check on the
> > directory, of the form:
> > .if ${CURDIR:M*/ports*}
> > CFLAGS= -mtune=amdfam10 -msse4e
> > .endif
> > I made a general config using postmaster.
> > After some trouble with some ports, I decided to get rid of those
> > modifications and commented the above form.
> > But, I was surprised to see that some ports still present this value
> > of CFLAGS at building time.
> > How can I correct this mistake.
>
> Just a guess; you built them previously and didn't clean the build
> directories?
>
> Or maybe you put those options in a portmaster config file?
> [ /usr/local/etc/portmaster.rc or $HOME/.portmasterrc ...]
>
___
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: this time it's vim/distfiles

[N.J. Mann]

In message <200907291305.n6td5kst010...@mp.cs.niu.edu>,
Scott Bennett (benn...@cs.niu.edu) wrote:
>  When portmaster tries to rebuild vim-lite, it tries to verify the
> checksums of 239 (?) patches.  (I guess I should take that as a warning.)
> Unfortunately, one of them apparently doesn't check out properly.  Here's
> an excerpt of the portmaster output.
> 
> => MD5 Checksum OK for vim/7.2.040
> => SHA256 Checksum OK for vim/7.2.040.
> => No MD5 checksum recorded for vim/7.2.041^.
> => No SHA256 checksum recorded for vim/7.2.041^.
> => No suitable checksum found for vim/7.2.041^.
> => MD5 Checksum OK for vim/7.2.042.
> => SHA256 Checksum OK for vim/7.2.042.
>  .
>  .
>  .
> => MD5 Checksum OK for vim/7.2.239.
> => SHA256 Checksum OK for vim/7.2.239.
> *** Error code 1
> 
> Stop in /usr/ports/editors/vim-lite.
> 
> ===>>> make failed for editors/vim-lite
> ===>>> Aborting update
> 
> ===>>> Update for vim-lite-7.2.209 failed
> ===>>> Aborting update
> 
>  I looked in distfiles and found that the line in question apparently
> had an extraneous character that displays in less and vi as a percent sign.
> 
> DISTFILE:vim/7.2.040:SIZE=1836:SHA256=ad320d45c2541a767b351fdb8720c349c468acec8cf54dcfced0a6d1e58e5d8e:MD5=4c493255ae227498016f30a0002ec1cc
> DISTFILE:vim/7.2.041%:SIZE=22405:SHA256=2f48e173df3d306edd982f8a3d5a15c65ba19694ca32bdbdaa51f8bcc48a3d06:MD5=107ba5dccb1df727601aead37abf8cd3
> DISTFILE:vim/7.2.042:SIZE=4987:SHA256=d5fa884a7c5ee77b60fe512ceccaac640c0dfc00bd435211f4e4597ae3bee2cd:MD5=99baedef8a9c908774b7ed74deacf184

NB: you should be looking in editors/vim since editors/vim-lite is a
slave port.

The Makefile and distinfo files have different names for the patch - the
maintainer appears to have decided to rename the patch file earlier
today and only updated Makefile accordingly.  The old name was 7.2.041%
and the new is to 7.2.041^.  Try changing distinfo accordingly.


Cheers,
   Nick.
-- 

___
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: this time it's vim/distfiles

[Wesley Shields]

On Wed, Jul 29, 2009 at 08:05:20AM -0500, Scott Bennett wrote:
>  When portmaster tries to rebuild vim-lite, it tries to verify the
> checksums of 239 (?) patches.  (I guess I should take that as a warning.)
> Unfortunately, one of them apparently doesn't check out properly.  Here's
> an excerpt of the portmaster output.
> 
> => MD5 Checksum OK for vim/7.2.040
> => SHA256 Checksum OK for vim/7.2.040.
> => No MD5 checksum recorded for vim/7.2.041^.
> => No SHA256 checksum recorded for vim/7.2.041^.
> => No suitable checksum found for vim/7.2.041^.
> => MD5 Checksum OK for vim/7.2.042.
> => SHA256 Checksum OK for vim/7.2.042.
>  .
>  .
>  .
> => MD5 Checksum OK for vim/7.2.239.
> => SHA256 Checksum OK for vim/7.2.239.
> *** Error code 1
> 
> Stop in /usr/ports/editors/vim-lite.
> 
> ===>>> make failed for editors/vim-lite
> ===>>> Aborting update
> 
> ===>>> Update for vim-lite-7.2.209 failed
> ===>>> Aborting update
> 
>  I looked in distfiles and found that the line in question apparently
> had an extraneous character that displays in less and vi as a percent sign.
> 
> DISTFILE:vim/7.2.040:SIZE=1836:SHA256=ad320d45c2541a767b351fdb8720c349c468acec8cf54dcfced0a6d1e58e5d8e:MD5=4c493255ae227498016f30a0002ec1cc
> DISTFILE:vim/7.2.041%:SIZE=22405:SHA256=2f48e173df3d306edd982f8a3d5a15c65ba19694ca32bdbdaa51f8bcc48a3d06:MD5=107ba5dccb1df727601aead37abf8cd3
> DISTFILE:vim/7.2.042:SIZE=4987:SHA256=d5fa884a7c5ee77b60fe512ceccaac640c0dfc00bd435211f4e4597ae3bee2cd:MD5=99baedef8a9c908774b7ed74deacf184
> 
> I tried deleting the extra character and rerunning portmaster, but that just
> yields the same results.

Don't just delete it. Change it to a ^ and you should be OK until the
maintainer updates distinfo to reflect the recent change.

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

this time it's vim/distfiles

[Scott Bennett]

 When portmaster tries to rebuild vim-lite, it tries to verify the
checksums of 239 (?) patches.  (I guess I should take that as a warning.)
Unfortunately, one of them apparently doesn't check out properly.  Here's
an excerpt of the portmaster output.

=> MD5 Checksum OK for vim/7.2.040
=> SHA256 Checksum OK for vim/7.2.040.
=> No MD5 checksum recorded for vim/7.2.041^.
=> No SHA256 checksum recorded for vim/7.2.041^.
=> No suitable checksum found for vim/7.2.041^.
=> MD5 Checksum OK for vim/7.2.042.
=> SHA256 Checksum OK for vim/7.2.042.
 .
 .
 .
=> MD5 Checksum OK for vim/7.2.239.
=> SHA256 Checksum OK for vim/7.2.239.
*** Error code 1

Stop in /usr/ports/editors/vim-lite.

===>>> make failed for editors/vim-lite
===>>> Aborting update

===>>> Update for vim-lite-7.2.209 failed
===>>> Aborting update

 I looked in distfiles and found that the line in question apparently
had an extraneous character that displays in less and vi as a percent sign.

DISTFILE:vim/7.2.040:SIZE=1836:SHA256=ad320d45c2541a767b351fdb8720c349c468acec8cf54dcfced0a6d1e58e5d8e:MD5=4c493255ae227498016f30a0002ec1cc
DISTFILE:vim/7.2.041%:SIZE=22405:SHA256=2f48e173df3d306edd982f8a3d5a15c65ba19694ca32bdbdaa51f8bcc48a3d06:MD5=107ba5dccb1df727601aead37abf8cd3
DISTFILE:vim/7.2.042:SIZE=4987:SHA256=d5fa884a7c5ee77b60fe512ceccaac640c0dfc00bd435211f4e4597ae3bee2cd:MD5=99baedef8a9c908774b7ed74deacf184

I tried deleting the extra character and rerunning portmaster, but that just
yields the same results.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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: after update - not all jpeg files are displayable

[Andriy Gapon]

on 29/07/2009 14:13 ajtiM said the following:
> On Arch forum I found:
> http://bbs.archlinux.org/viewtopic.php?pid=585987

Thank you very much for finding this!

-- 
Andriy Gapon
___
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: after update - not all jpeg files are displayable

[ajtiM]

On Wednesday 29 July 2009 00:19:56 Erich Dollansky wrote:
> Hi,
>
> I do not know if this will help here.
>
> I have had in the past a very different problem which seems
> unsolvable.
>
> I did the same as you using portupgrade to bring my system to the
> current status. It broke some things.
>
> By change, I got the problem solve by manually compiling some
> ports and reinstalling them.
>
> Check what ports are needed by your program. Start at the base
> reinstalling them manually.
>
> I did this just by chance and found my system working afterwards.
>
> Yes, I know, it is a lot of work if you cannot do it on the side.
>
> Erich
>

First I swithed from GQview to Geeqi (I tought that shoud be better) and did 
as you described but problem is here still.
On Arch forum I found:
http://bbs.archlinux.org/viewtopic.php?pid=585987


-- 
Mitja
-
http://starikarp.redbubble.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: updating to ghostscript8-8.64_2 fails

[Scott Bennett]

 On Tue, 28 Jul 2009 11:52:48 -0500 Steve Randall
 wrote:
>On Sun, 26 Jul 2009 14:36:37 -0500 (CDT)
>Scott Bennett  wrote:
>
>>  I'm running 7-STABLE updated to several hours ago:
>>=20
>> FreeBSD hellas 7.2-STABLE FreeBSD 7.2-STABLE #26: Sun Jul 26 02:48:17 CDT=
> 2009 benn...@hellas:/usr/src/sys/i386/compile/hellas  i386
>>=20
>>  I also ran portsnap again to get the latest updates before attemptin=
>g to
>> rebuild all altered ports and packages among the ones I have installed.  =
>Now,
>> using portmaster again, I've run into a problem during the update to
>> ghostscript.  It does a lot of compiling, but eventually quits at:
>>=20
>> rm -f ./obj/../soobj/iconfig.c
>> cp ./obj/../soobj/gconfxx.h ./obj/../soobj/gconfig.h
>> cp ./psi/iconf.c ./obj/../soobj/iconfig.c
>> cc  -DHAVE_MKSTEMP -DHAVE_HYPOT   -DHAVE_FONTCONFIG -O2 -fno-strict-alias=
>ing -pipe -march=3Dprescott -fPIC -DUPD_SIGNAL=3D0 -I. -I/usr/ports/print/g=
>hostscript8/work/ghostscript-8.64/jasper/src/libjasper/include -I/usr/local=
>/include/libpng -I/usr/local/include  -Wall -Wstrict-prototypes -Wundef -Wm=
>issing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasi=
>ng -Wdeclaration-after-statement -fno-builtin -fno-common -DHAVE_STDINT_H -=
>DGX_COLOR_INDEX_TYPE=3D"unsigned long long" -O2 -fno-strict-aliasing -pipe =
>-march=3Dprescott -DUSE_LIBICONV_GNU -DUSE_LIBPAPER -DGS_DEVS_SHARED -DGS_D=
>EVS_SHARED_DIR=3D\"/usr/local/lib/ghostscript/8.64\" -I./psi -I./obj/../soo=
>bj -I./obj/../soobj -I./base  -o ./obj/../soobj/iconfig.o -c ./obj/../soobj=
>/iconfig.c
>> cc  -DHAVE_MKSTEMP -DHAVE_HYPOT   -DHAVE_FONTCONFIG -O2 -fno-strict-alias=
>ing -pipe -march=3Dprescott -fPIC -DUPD_SIGNAL=3D0 -I. -I/usr/ports/print/g=
>hostscript8/work/ghostscript-8.64/jasper/src/libjasper/include -I/usr/local=
>/include/libpng -I/usr/local/include  -Wall -Wstrict-prototypes -Wundef -Wm=
>issing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasi=
>ng -Wdeclaration-after-statement -fno-builtin -fno-common -DHAVE_STDINT_H -=
>DGX_COLOR_INDEX_TYPE=3D"unsigned long long" -O2 -fno-strict-aliasing -pipe =
>-march=3Dprescott -DUSE_LIBICONV_GNU -DUSE_LIBPAPER -DGS_DEVS_SHARED -DGS_D=
>EVS_SHARED_DIR=3D\"/usr/local/lib/ghostscript/8.64\" -I./obj/../soobj -I./b=
>ase  -o ./obj/../soobj/gsromfs0.o -c ./base/gsromfs0.c
>> ./obj/../soobj/echogs -w ./obj/../soobj/ldt.tr -n - cc -L/usr/local/lib -=
>L/usr/local/lib -shared -Wl,-soname=3Dlibgs.so.8 -o ./bin/../sobin/libgs.so=
>.8.64
>> ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -n -s ./obj/../soobj/gsrom=
>fs0.o ./obj/../soobj/gs.o -s
>> cat ./obj/../soobj/ld.tr >>./obj/../soobj/ldt.tr
>> ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm  -liconv -lpaper =
>-lstdc++  -L/usr/local/lib -lfontconfig   -Wl,-export-dynamic -lpthread -lm
>> if [ x !=3D x ]; then LD_RUN_PATH=3D; export LD_RUN_PATH; fi; \
>>  XCFLAGS=3D XINCLUDE=3D XLDFLAGS=3D XLIBDIRS=3D XLIBS=3D \
>>  FEATURE_DEVS=3D DEVICE_DEVS=3D DEVICE_DEVS1=3D DEVICE_DEVS2=3D 
>> DEVICE_DE=
>VS3=3D \
>>  DEVICE_DEVS4=3D DEVICE_DEVS5=3D DEVICE_DEVS6=3D DEVICE_DEVS7=3D 
>> DEVICE_D=
>EVS8=3D \
>>  DEVICE_DEVS9=3D DEVICE_DEVS10=3D DEVICE_DEVS11=3D DEVICE_DEVS12=3D \
>>  DEVICE_DEVS13=3D DEVICE_DEVS14=3D DEVICE_DEVS15=3D DEVICE_DEVS16=3D \
>>  DEVICE_DEVS17=3D DEVICE_DEVS18=3D DEVICE_DEVS19=3D DEVICE_DEVS20=3D \
>>  DEVICE_DEVS_EXTRA=3D \
>>  /bin/sh <./obj/../soobj/ldt.tr
>> ./obj/../soobj/gdevl256.o(.text+0x73a): In function `gs_shared_init':
>> : multiple definition of `gs_shared_init'
>> ./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here
>> /usr/bin/ld: Warning: size of symbol `gs_shared_init' changed from 150 in=
> ./obj/../soobj/gdevxalt.o to 38 in ./obj/../soobj/gdevl256.o
>> ./obj/../soobj/gdevvglb.o(.text+0x995): In function `gs_shared_init':
>> : multiple definition of `gs_shared_init'
>> ./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here
>> gmake[1]: *** [bin/../sobin/libgs.so.8.64] Error 1
>> gmake[1]: Leaving directory `/usr/ports/print/ghostscript8/work/ghostscri=
>pt-8.64'
>> gmake: *** [so] Error 2
>> *** Error code 1
>>=20
>> Stop in /usr/ports/print/ghostscript8.
>>=20
>> =3D=3D=3D>>> make failed for print/ghostscript8
>> =3D=3D=3D>>> Aborting update
>>=20
>> =3D=3D=3D>>> Update for ghostscript8-8.64_2 failed
>> =3D=3D=3D>>> Aborting update
>>=20
>> =3D=3D=3D>>> Update for ImageMagick-6.5.3.10 failed
>> =3D=3D=3D>>> Aborting update
>>=20
>> 327.866u 117.233s 7:03.32 105.1% 3261+927k 228+1673io 46pf+0w
>> hellas#=20
>>=20
>>  Is there something I missed doing?  Or does this mean I should submit
>> a problem report?
>
>=46rom looking at the source I think you must have enabled both the X
>drivers and 256-color SVGALIB. Try running

 It's quite possible that I did, though I don't remember now.  Was there
some piece of documentation that I missed that says that the SVGALIB support
is incompatible with other options?
>
># make config
>
>and deselect

Re: FreeBSD Port: dspam-devel-3.8.0_4,1

[Ion-Mihai Tetcu]

On Tue, 28 Jul 2009 08:27:42 -0300
"Ari Arantes Filho"  wrote:

> Hi,
> 
> I'm new to dspam and want to install it, but I saw the dspam project 
> page the version 3.9-Alpha2. Is there any plan to migrate this new 
> version to the ports?

I am currently away, connecting via my mobile. We (DSPAM Project
Members) plan to release the 3.9-Beta1 shortly (basically I have to get
back in town and do the release). Pleaase wait until the weekend or
Monday.



-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
___
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"

[PATCH] upgrade shells/bash 4.0 to patchlevel 28

[David O'Brien]

There are some new patches to Bash 4.0.  Here is the patch I plan to
commit to the port - but I wanted to let it have some "beta testing"
first.

If you have a moment and are a Bash user, please give this a try.

I only need to know if the new patchlevel causes grief.
I'm not looking for 1,000 "it works" responces.  ;-)

-- David


Index: Makefile
===
RCS file: /home/pcvs/ports/shells/bash/Makefile,v
retrieving revision 1.114
diff -u -p -r1.114 Makefile
--- Makefile18 May 2009 18:44:32 -  1.114
+++ Makefile29 Jul 2009 06:36:06 -
@@ -7,7 +7,7 @@
 #
 
 PORTNAME=  bash
-PATCHLEVEL=24
+PATCHLEVEL=28
 PORTVERSION=   4.0.${PATCHLEVEL:S/^0//g}
 PORTREVISION?= 0
 CATEGORIES=shells
Index: distinfo
===
RCS file: /home/pcvs/ports/shells/bash/distinfo,v
retrieving revision 1.43
diff -u -p -r1.43 distinfo
--- distinfo18 May 2009 18:44:33 -  1.43
+++ distinfo29 Jul 2009 06:36:06 -
@@ -73,5 +73,17 @@ SIZE (bash/bash40-023) = 2148
 MD5 (bash/bash40-024) = 82ba5fc9eb780eb57d8b7628a17b7d74
 SHA256 (bash/bash40-024) = 
a59ebac47efe31b951e1732e4223cc725b2748c331bec98248355c5ac53717ab
 SIZE (bash/bash40-024) = 3049
+MD5 (bash/bash40-025) = b26f9007ac4eef5c378f1abcb8959025
+SHA256 (bash/bash40-025) = 
f77900d636033474bc15d39c4948515fdfe718164ea668edd64d8d4d5a8f6a08
+SIZE (bash/bash40-025) = 3435
+MD5 (bash/bash40-026) = 83bc844c82d0a30740e8d91a8238bfa9
+SHA256 (bash/bash40-026) = 
a9bdf4409c6625561884be58026a52ccb47600407f3d5b8d0889f0585040f6cb
+SIZE (bash/bash40-026) = 1433
+MD5 (bash/bash40-027) = a41c187f05ecab07389c18acc91214c6
+SHA256 (bash/bash40-027) = 
f65dc26bb1bacc8a66610cd5f6f2b8e70be8d8c4e397e7a5ad6f3306224b77f2
+SIZE (bash/bash40-027) = 2010
+MD5 (bash/bash40-028) = fcc367e6471267d2e397257e703b817d
+SHA256 (bash/bash40-028) = 
5b222cbaf3ab1c1d9b4c5956a0e28cad49660f5746af08efe174e7b474022d1a
+SIZE (bash/bash40-028) = 5567
 MD5 (bash/FAQ) = IGNORE
 SHA256 (bash/FAQ) = IGNORE
___
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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Dan Mahoney, System Admin]

On Wed, 29 Jul 2009, Doug Barton wrote:


Mel Flynn wrote:

On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote:


make: don't know how to make
/usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop
*** Error code 2



Someone else had the same problem, and they also chose overwrite-base:

http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035.
html

But it was dismissed because he was using "sudo", however the real reason
is because this problem goes away a second time.


Most likely because that option changes PREFIX, so the BUILD_COOKIE changed,
but the target was already in make's list of targets to make. After options
are stored in /var/db/ports, BUILD_COOKIE will end in ._usr.


I believe Mel is right here. 'make clean ; make config ; make' worked
for me.


As does a second make after getting this error, but it's nonintuitive, and 
probably a ports bug.


-Dan

--

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.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: updating to ghostscript8-8.64_2 fails

[Scott Bennett]

 On Tue, 28 Jul 2009 09:57:57 -0700 (PDT) Doug Barton 
wrote:
>On Tue, 28 Jul 2009, Scott Bennett wrote:
>
>> I finally got around it by putting a +IGNOREME file into
>> /var/db/pkg/ghostscript8-8.64_2/ after the following attempts to skip it
>> using the -x option for portmaster failed to do that.
>>
>>  portmaster -x print/ghostscript8 -v -w -a
>>  portmaster -x print/ghostscript8\* -v -w -a
>>  portmaster -x print/ghostscript8-8.64_2 -v -w -a
>
>'portmaster -x ghostscript' should work.
>
 Okay.  I doubt I'll bother with it until there's a new update available.
FWIW, I obviously did not understand from the man page that that would be the
way to get it to work.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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: Don't know how to make /usr/ports/dns/bind96/work/.build....

[Doug Barton]

Mel Flynn wrote:
> On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote:
> 
>> make: don't know how to make
>> /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop
>> *** Error code 2
> 
>> Someone else had the same problem, and they also chose overwrite-base:
>>
>> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035.
>> html
>>
>> But it was dismissed because he was using "sudo", however the real reason
>> is because this problem goes away a second time.
> 
> Most likely because that option changes PREFIX, so the BUILD_COOKIE changed, 
> but the target was already in make's list of targets to make. After options 
> are stored in /var/db/ports, BUILD_COOKIE will end in ._usr.

I believe Mel is right here. 'make clean ; make config ; make' worked
for me.


Please let me know if it doesn't work for you.


Doug

-- 

This .signature sanitized for your protection

___
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: after update - not all jpeg files are displayable

[Erich Dollansky]

Hi,

I do not know if this will help here.

I have had in the past a very different problem which seems 
unsolvable.

I did the same as you using portupgrade to bring my system to the 
current status. It broke some things.

By change, I got the problem solve by manually compiling some 
ports and reinstalling them.

Check what ports are needed by your program. Start at the base 
reinstalling them manually.

I did this just by chance and found my system working afterwards.

Yes, I know, it is a lot of work if you cannot do it on the side.

Erich
On 29 July 2009 pm 12:28:46 Oliver Lehmann wrote:
> Joe Marcus Clarke wrote:
> > depend on libjpeg.  Really, you need to do a portupgrade -rf
> > jpeg to fix this.
>
> I now did this - it has not fixed the problem. gqview for
> example is still not able to display this image.
> I do not even have any libjpeg.so.9 on my system (removed my
> whole lib/compat/pkg directory)


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