Re: vim ports broken.

[Frank J. Laszlo]

Carlos A. M. dos Santos wrote:

On Mon, Jun 22, 2009 at 7:23 PM, Carlos A. M. dos
Santos wrote:
  

On Mon, Jun 22, 2009 at 4:58 PM, Philip M. Gollucci wrote:


Helmut Schneider wrote:
  

matt donovan  wrote:


On Fri, Jun 19, 2009 at 5:37 AM, Albert Shih 
wrote:
  

I think the vim ports is broken.


Nope not broken just takes a long time to grab that patch since it pulls
from FreeBSD ftp localdistfiles mirror under obrien
  

The port *is* broken:

# fetch
ftp://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/obrien/7.2.041%
fetch:
ftp://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/obrien/7.2.041%: Bad
Request
#

as fetch cannot handle "%" correctly.


sure it can, it just needs '' around the url.
  

The distinfo file is wrong. Edit it and put the correct data for that patch:

MD5 (vim/7.2.041) = 66bde35426c09d9c666e23215f9a19c9
SHA256 (vim/7.2.041) =
524aa9aeb9f8729fb91289f40a4c5fecf5d0d07d3655c4a38a65abc98f7cd71b
SIZE (vim/7.2.041) = 22993



Opps, now I got it: the official 7.2.041 patch can not be applied
cleanly so David provided a custom one. Choosing "%" to differentiate
it, however, was a bad idea. It would be better to use a simple
underscore.

  
Why is % any worse than an underscore? As I explained earlier, fetch has 
no problem dealing with it. The errors people were posting are 
server-side, ftp.freebsd.org has no problems handling it.


--
Frank Laszlo
lasz...@freebsd.org
FreeBSD Ports Committer

___
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: vim ports broken.

[Carlos A. M. dos Santos]

On Wed, Jun 24, 2009 at 10:09 AM, Frank J. Laszlo wrote:
> Carlos A. M. dos Santos wrote:
[...]
>> Opps, now I got it: the official 7.2.041 patch can not be applied
>> cleanly so David provided a custom one. Choosing "%" to differentiate
>> it, however, was a bad idea. It would be better to use a simple
>> underscore.
>>
>>
>
> Why is % any worse than an underscore? As I explained earlier, fetch has no
> problem dealing with it. The errors people were posting are server-side,
> ftp.freebsd.org has no problems handling it.

POLA: users get surprised by the "Bad Request" answer and think that
the package is broken. So they complain at -ports, generating lengthy
email threads.

-- 
My preferred quotation of Robert Louis Stevenson is "You cannot
make an omelette without breaking eggs". Not because I like the
omelettes, but because I like the sound of eggs being broken.
___
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: [RFC] New category proposal, i18n

[Thomas Abthorpe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On June 23, 2009 10:27:59 pm Eitan Adler wrote:
> > I would like for it to be a real category, so we can unclutter the misc/
> > folder, and encourage more local/internationalized stuff in the new
> > category.
>
> I would like it to be a virtual category.
> Lets take a random i18n port: misc/koffice-i18n-th
> The port would get moved to editors/ and i18n would get added as a
> virtual category. It is more organized this way. A person looking for
> editors doesn't have to look in both editors/ and misc/ (or i18n/)

+1 for virtual category, thanks for the feedback.

- -- 
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org   | http://people.freebsd.org/~tabthorpe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpCL5kACgkQ5Gm/jNBp8qCBgQCcDFZOSvK6aZqwSfR2YYjSU/q1
APIAn1WALvnxuPTD/yvQdFdbN/WjBTrD
=j0LU
-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: [RFC] New category proposal, i18n

[Thomas Abthorpe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On June 23, 2009 04:36:08 pm Charlie Kester wrote:
> On Tue 23 Jun 2009 at 12:05:55 PDT Thomas Abthorpe wrote:
> >Localization is a subset Internationalization, so the new category
> >becomes a catch all for both entities.
>
> If i18n is too cryptic or too alphanumeric, and internationalization is
> too long, why not go with "nls"?

I personally think that nls is equally as cryptic as i18n or l10n.


Thomas

- -- 
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org   | http://people.freebsd.org/~tabthorpe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpCMHoACgkQ5Gm/jNBp8qCQNACdEtpDr3bmOoZAW5dHBWKcdotn
xPQAn1LGRsg+xr/csmhFaNUXhpUFqugy
=HTv2
-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: [RFC] New category proposal, i18n

[Thomas Abthorpe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On June 23, 2009 05:35:16 pm Tim Bishop wrote:
> > If i18n is too cryptic or too alphanumeric, and internationalization is
> > too long, why not go with "nls"?
>
> How about internationalisation? ;-)
>
> Tim.

As a Canadian who prefers en_GB, I fought every urge to propose that one. 
Since FreeBSD has en_US as its base language, I felt compelled to use zed in 
of ess :>


Thomas

- -- 
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org   | http://people.freebsd.org/~tabthorpe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpCMTQACgkQ5Gm/jNBp8qB+PQCfaNgQ5OT8BMBUwkr+0c+Gt/Io
uq4AmgJS948BR3k4oAdocfExMibWrOuq
=rMR7
-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: [RFC] New category proposal, i18n

[Chris Rees]

2009/6/24 Thomas Abthorpe :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On June 23, 2009 05:35:16 pm Tim Bishop wrote:
>> > If i18n is too cryptic or too alphanumeric, and internationalization is
>> > too long, why not go with "nls"?
>>
>> How about internationalisation? ;-)
>>
>> Tim.
>
> As a Canadian who prefers en_GB, I fought every urge to propose that one.
> Since FreeBSD has en_US as its base language, I felt compelled to use zed in
> of ess :>
>

I'm constantly involved in a fight between my 'evil' and 'good' side;
I can't stand the usual US spellings as a Brit, but I always end up
admitting to myself that US spellings generally:

   make more sense;

and

   are essentially an improvement on a language that's horrible to
understand and learn properly anyway.

Though I still reserve the right to hate the inconsistent use of 'z'
(why internationalize but surmise; realize but enterprise, etc etc)!



You'll never hear this from me again, I promise.

Chris

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in a mailing list?
___
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: [RFC] New category proposal, i18n

[Peter Pentchev]

On Wed, Jun 24, 2009 at 03:13:53PM +0100, Chris Rees wrote:
[snip]
> Though I still reserve the right to hate the inconsistent use of 'z'
> (why internationalize but surmise;

I guess "surmise" just hasn't been US-ized yet :P

> realize but enterprise, etc etc)!

Er, isn't this a verb-vs-noun difference? :)  I don't think
nouns are -ize'd, too :)

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.netr...@space.bgr...@freebsd.org
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
This sentence was in the past tense.


pgprQkAmle4pV.pgp
Description: PGP signature

Re: [RFC] New category proposal, i18n

[Chris Rees]

2009/6/24 Peter Pentchev :
> On Wed, Jun 24, 2009 at 03:13:53PM +0100, Chris Rees wrote:
> [snip]
>> Though I still reserve the right to hate the inconsistent use of 'z'
>> (why internationalize but surmise;
>
> I guess "surmise" just hasn't been US-ized yet :P
>
>> realize but enterprise, etc etc)!
>
> Er, isn't this a verb-vs-noun difference? :)  I don't think
> nouns are -ize'd, too :)
>
> G'luck,
> Peter
>

Er, poor example! The idea's lifted out of Mother Tongue, Bryson 1990.

Chris


-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in a mailing list?
___
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"

thank you for portmaster

[Dan Naumov]

Hey

Just thought I'd drop a line to thank you for creating portmaster.
After discovering it yesterday thanks to a tip I got from somebody on
IRC, it has now completely replaced portupgrade for me. Keep up the
great work!


Sincerely,
- Dan Naumov
___
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: thank you for portmaster

[Doug Barton]

Dan Naumov wrote:
> Hey
> 
> Just thought I'd drop a line to thank you for creating portmaster.
> After discovering it yesterday thanks to a tip I got from somebody on
> IRC, it has now completely replaced portupgrade for me. Keep up the
> great work!

Thank you for the kind words, they are greatly appreciated. :)


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: [RFC] New category proposal, i18n

[Charlie Kester]

On Wed 24 Jun 2009 at 06:56:10 PDT Thomas Abthorpe wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On June 23, 2009 04:36:08 pm Charlie Kester wrote:

On Tue 23 Jun 2009 at 12:05:55 PDT Thomas Abthorpe wrote:
>Localization is a subset Internationalization, so the new category
>becomes a catch all for both entities.

If i18n is too cryptic or too alphanumeric, and internationalization is
too long, why not go with "nls"?


I personally think that nls is equally as cryptic as i18n or l10n.


But it has the virtue of being purely alphabetic. and thus meets one of
the objections that have been raised.

I don't put much weight on the "cryptic" argument myself.  I expect that
anyone who is doing internationalization work is familiar with all of
these  terms -- and if not, they need to *make* themselves familiar with
them.
 
___

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: [RFC] New category proposal, i18n

[RW]

On Wed, 24 Jun 2009 17:53:13 +0300
Peter Pentchev  wrote:

> On Wed, Jun 24, 2009 at 03:13:53PM +0100, Chris Rees wrote:
> [snip]
> > Though I still reserve the right to hate the inconsistent use of 'z'
> > (why internationalize but surmise;
> 
> I guess "surmise" just hasn't been US-ized yet :P

It's not really a matter of US v's British English, the consistent use
of "ise" is demotic British English, some better spellcheckers do have
an "ize" option for the British dictionary.

Z is preferred because it was spelt with a zeta in Greek, ise is
typically used where the word came from a french verb using ise, or
where the verb comes from a noun that already contains ise, eg.
advertise comes from advertisement not advert-ize.

___
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: [RFC] New category proposal, i18n

[Thomas Abthorpe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On June 24, 2009 02:24:01 pm Charlie Kester wrote:
> >On June 23, 2009 04:36:08 pm Charlie Kester wrote:
> >> On Tue 23 Jun 2009 at 12:05:55 PDT Thomas Abthorpe wrote:
> >> >Localization is a subset Internationalization, so the new category
> >> >becomes a catch all for both entities.
> >>
> >> If i18n is too cryptic or too alphanumeric, and internationalization is
> >> too long, why not go with "nls"?
> >
> >I personally think that nls is equally as cryptic as i18n or l10n.
>
> But it has the virtue of being purely alphabetic. and thus meets one of
> the objections that have been raised.
>
> I don't put much weight on the "cryptic" argument myself.  I expect that
> anyone who is doing internationalization work is familiar with all of
> these  terms -- and if not, they need to *make* themselves familiar with
> them.

ack ack, point well taken.


Thomas

- -- 
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org   | http://people.freebsd.org/~tabthorpe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpCdBsACgkQ5Gm/jNBp8qBZDQCdHDTLXYsYKyK4FXo0xL9VRfdT
lIAAnRTOr2q4jkUtiMKwRW7q/0ARTrCT
=Sy7h
-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: thank you for portmaster

[Sam Fourman Jr.]

On Wed, Jun 24, 2009 at 10:25 AM, Dan Naumov wrote:
> Hey
>
> Just thought I'd drop a line to thank you for creating portmaster.
> After discovering it yesterday thanks to a tip I got from somebody on
> IRC, it has now completely replaced portupgrade for me. Keep up the
> great work!

Thank you for the email, I am a portupgrade user, and I was unaware
that there were other options.
I will give portmaster a try.


Sam Fourman Jr.
___
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: [REPOST] problem upgrading perl

[Scott Bennett]

 On Tue, 23 Jun 2009 10:30:11 -0700 Doug Barton 
wrote:
>Scott Bennett wrote:
>>  Thank you for doing that.  Unfortunately, it might have been more
>> appropriate to have simply replaced that note with another that cautions
>> anyone attempting the perl upgrade that the upgrade has not been fully
>> tested against all ports that may list the new perl as a build dependency.
>
>First off, I'm sorry to hear that you're having problems, particularly
>that you're having problems with portmaster.
>
>In regards to the upgrade process not being tested, with over 20,000
>ports it's basically impossible to guarantee that something as
>complicated as upgrading perl will work 100% of the time for every
>user and every combination of perl-dependent ports. I think it's sort
>of a given that "beware of dragons" is posted over the door.
>
>> It should also warn that portmaster is *NOT* a good tool to use for this
>> upgrade, even if the note shows how to attempt it.
>
>I think it depends on your definition of "good," and also how you use
>the tool. Since I use it every day, including for things like
>upgrading perl, I happen to think it's a pretty good tool, but YMMV.
>
>>  Using the specific port name for perl when restarting the upgrade
>> process, I was able to resume for a short time.  However, portmaster has
>> two design problems that apply here.  The first is that if portmaster
>> encounters a port that fails to build properly, it stops cold, rather than
>> continuing to build other ports that do build correctly, summarizing the
>> build errors at the end. 
>
>Because it's impossible for portmaster to know which are the
>"important" errors to a given user I regard this as a feature, rather
>than a problem. Also, errors like the ones you're experiencing
>_should_ be rare, so in general this feature/bug/whatever doesn't
>affect users all that often.

 There ought to be an automated way to deal with the package issue that
causes the failure of the entire update run just because it wants a human
to type "make deinstall && make reinstall".
>
>>  The second design problem is that the -R option, which is supposed to
>> avoid rebuilding ports that have already been successfully rebuilt,
>> nevertheless rebuilds the specified dependency port--in this case,
>> perl-threaded-5.10.0_3--*every single time* without checking to see whether
>> it was already successfully built. 
>
>Have you tried using the -x option to exclude it? You can also use the
>-i option, although for a lot of ports that can get annoying.

 I had not, thanks to my having misread something in the portmaster man
page.  However, since reading your reply, I have tried (without -R)

# nice +18 portmaster -x perl-threaded-5.10.0 -rv perl-threaded-5.10.0_3

which did rebuild perl (along with many other already rebuilt ports, of
course).  At this moment, I have

# nice +18 portmaster -x perl-threaded-5.10.0_3 -R -rv perl-threaded-5.10.0_3

running, and it is currently rebuilding perl yet again.  So the -x option
appears to be useless, at least in this context.
>
>>  Back to the problems with the builds...a half dozen or more port
>> rebuild failures were correctable by simply entering the failed port's
>> directory, doing a "make deinstall && make reinstall", and then returning
>> to restart (again) portmaster, which then, of course, began by rebuilding
>> perl another time (sigh).  Full testing of the perl upgrade should have
>> made this process unnecessary, it seems to me.
>
>Perl is traditionally very twitchy about stuff like this, and the
>solution you used is often the only one possible.
>
>>  Eventually, though, I encountered a problem with a port called
>> misc/gnome-icon-theme-2.26.0_1.  (I do not use and haven't knowingly
>> installed gnome, so I really don't know why this port was installed in
>> the first place. 
>
>pkg_info -R should give you that information.
>
>>  If someone can tell me how to proceed from here, I'll give it another
>> try.  However, once again the ports subsystem is testing my tolerance for
>> frustration, so if there's no real hope of completing the entire rebuilding
>> process for ports with build dependencies upon perl
>
>You should probably use the -i option, and only rebuild the actual p5-
>ports. A lot of ports have what I consider "indirect" dependencies on
>perl that make the -r option for portmaster and portupgrade do more
>work than it probably ought to. However that's a topic for another
>thread. :)
>
 I began using FreeBSD at 5.2.1.  Along the way, my other complaints have
largely been fixed, but the ports subsystem remains to this day the weakest
part of all of FreeBSD.  I realize that the problem of coordinating the
installation and maintenance of such a widely diverse body of ports and
packages is a complex one, but the problems the current tools, dependency
lists, Makefiles, etc. present to the user are often insoluble by anyone but
an expert in the internal workings of each o

Re: [REPOST] problem upgrading perl

[Scott Bennett]

 On Tue, 23 Jun 2009 08:31:36 +0300 "Sergey V. Dyatko"
 wrote:
>÷ Mon, 22 Jun 2009 21:12:17 -0500 (CDT)
>Scott Bennett  ÐÉÛÅÔ:
>
>SB>  On Thu, 18 Jun 2009 11:42:51 -0700 Doug Barton
>SB>  wrote:
>SB> >Jim Trigg wrote:
>SB> >> Actually, he was suggesting changing from perl\* to perl-\* so
>SB> >> it would only match the perl port. 
>SB> >
>SB> >FYI, the \* at the end is not needed, 'portmaster perl-' will work
>SB> >just fine.
>SB> >
>SB> >> Unfortunately, that won't work as there is at
>SB> >> least one other port that will match that -- net/p5-perl-ldap
>SB> >> (portname perl-ldap). 
>SB> >
>SB> >It's generally a good idea to check your facts before posting to
>SB> >the list. Since the glob code goes by the directory names
>SB> >in /var/db/pkg, and since the prefix will be there in the
>SB> >directory name, this won't be an issue.
>SB> >
>SB> >In any case, I updated the instructions for this, and the other
>SB> >portmaster examples in /usr/ports/UPDATING a couple days ago so
>SB> >hopefully no one else will stumble over this.
>SB> >
>SB>  Thank you for doing that.  Unfortunately, it might have been
>SB> more appropriate to have simply replaced that note with another
>SB> that cautions anyone attempting the perl upgrade that the upgrade
>SB> has not been fully tested against all ports that may list the new
>SB> perl as a build dependency. It should also warn that portmaster is
>SB> *NOT* a good tool to use for this upgrade, even if the note shows
>SB> how to attempt it. Using the specific port name for perl when
>SB> restarting the upgrade process, I was able to resume for a short
>SB> time.  However, portmaster has two design problems that apply
>SB> here.  The first is that if portmaster encounters a port that fails
>SB> to build properly, it stops cold, rather than continuing to build
>SB> other ports that do build correctly, summarizing the build errors
>SB> at the end.  This means that each time an error occurs, it requires
>SB> a manual restart (after the error has been corrected) that will run
>SB> only until the next error is encountered. The second design problem
>SB> is that the -R option, which is supposed to avoid rebuilding ports
>SB> that have already been successfully rebuilt, nevertheless rebuilds
>SB> the specified dependency port--in this case,
>SB> perl-threaded-5.10.0_3--*every single time* without checking to see
>SB> whether it was already successfully built.  This is terribly
>SB> time-consuming and wasteful.  One might argue that the command says
>SB> to rebuild the port specified, but there really needs to be some
>SB> way to tell it not to do so. Back to the problems with the
>SB> builds...a half dozen or more port rebuild failures were
>SB> correctable by simply entering the failed port's directory, doing a
>SB> "make deinstall && make reinstall", and then returning to restart
>SB> (again) portmaster, which then, of course, began by rebuilding perl
>SB> another time (sigh).  Full testing of the perl upgrade should have
>SB> made this process unnecessary, it seems to me. Eventually, though,
>SB> I encountered a problem with a port called
>SB> misc/gnome-icon-theme-2.26.0_1.  (I do not use and haven't
>SB> knowingly installed gnome, so I really don't know why this port was
>SB> installed in the first place.  OTOH, I also have a strong suspicion
>SB> that it can't simply be eliminated either.)  The rebuilding of this
>SB> port aborted thusly:
>SB> 
>SB> ===>  Installing for gnome-icon-theme-2.26.0_1
>SB> ===>   Generating temporary packing list
>SB> ===>  Checking if misc/gnome-icon-theme already installed
>SB> Making install in 8x8
>SB> gmake[1]: Entering directory
>SB> `/usr/ports/misc/gnome-icon-theme/work/gnome-icon-theme-2.26.0/8x8'
>SB> Making install in emblems gmake[2]: Entering directory
>SB> `/usr/ports/misc/gnome-icon-theme/work/gnome-icon-theme-2.26.0/8x8/emblems'
>SB> gmake[3]: Entering directory
>SB> `/usr/ports/misc/gnome-icon-theme/work/gnome-icon-theme-2.26.0/8x8/emblems'
>SB> gmake[3]: Nothing to be done for `install-exec-am'. test -z
>SB> "/usr/local/share/icons/gnome/8x8/emblems" || ../.././install-sh -c
>SB> -d "/usr/local/share/icons/gnome/8x8/emblems" install  -o root -g
>SB> wheel -m 444 'emblem-default.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-default.png'
>SB> install  -o root -g wheel -m 444 'emblem-new.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-new.png' install
>SB> -o root -g wheel -m 444 'emblem-readonly.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-readonly.png'
>SB> install  -o root -g wheel -m 444 'emblem-symbolic-link.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-symbolic-link.png'
>SB> install  -o root -g wheel -m 444 'emblem-unreadable.png'
>SB> '/usr/local/share/icons/gnome/8x8/emblems/emblem-unreadable.png' (cd 
>/usr/local/share/icons/gnome/8x8
>SB> && /usr/local/libexec/icon-name-mapping -c emblems) Can't locate
>SB> XML/Simple.pm in @INC (@INC
>SB> contains: /usr/local/lib

Re: [RFC] New category proposal, i18n

[Eitan Adler]

> I'm constantly involved in a fight between my 'evil' and 'good' side;
> I can't stand the usual US spellings as a Brit, but I always end up
> admitting to myself that US spellings generally:
> 
>make more sense;
Coming from an American:
$make more sense;
make: don't know how to make more. Stop

___
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: [RFC] New category proposal, i18n

[perryh]

> > If i18n is too cryptic or too alphanumeric, and
> > internationalization is too long, why not go with "nls"?
>
> I personally think that nls is equally as cryptic as i18n or l10n.

Anyone care for "intlzn"?  It's short, should still tab-complete
from "in", and it may be a bit less cryptic than nls, i18n, or l10n.
___
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"

next abort of perl upgrade encountered--linux-pango security problem :-(

[Scott Bennett]

 The saga of failures in the perl upgrade continues with the following:

===>   linux-gtk2-2.6.10_3 depends on file: 
/compat/linux/usr/lib/libpango-1.0.so.0.1001.1 - not found
===>Verifying install for /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 in 
/usr/ports/x11-toolkits/linux-pango
===>  linux-pango-1.10.2_3 has known vulnerabilities:
=> pango -- integer overflow.
   Reference: 

=> Please update your ports tree and try again.
*** Error code 1

Stop in /usr/ports/x11-toolkits/linux-pango.
*** Error code 1

Stop in /usr/ports/x11-toolkits/linux-gtk2.
*** Error code 1

Stop in /usr/ports/multimedia/linux-realplayer.
*** Error code 1

Stop in /usr/ports/multimedia/mplayer.

===>>> make failed for multimedia/mplayer
===>>> Aborting update

===>>> Update for mplayer-0.99.11_12 failed
===>>> Aborting update

===>>> There are messages from installed ports to display,
   but first take a moment to review the error messages
   above.  Then press Enter when ready to proceed.

[messages omitted here  --SB]

===>>> Done displaying pkg-message files
===>>> The following actions were performed:
Re-installation of perl-threaded-5.10.0_3
Upgrade of ImageMagick-6.5.2.10 to ImageMagick-6.5.3.10
Upgrade of dvipdfmx-20080607_1 to dvipdfmx-20090522_1
Upgrade of git-1.6.3.2_1 to git-1.6.3.3
Upgrade of gstreamer-plugins-a52dec-0.10.11,3 to 
gstreamer-plugins-a52dec-0.10.12,3
Upgrade of gstreamer-plugins-bad-0.10.11,3 to 
gstreamer-plugins-bad-0.10.13,3
Upgrade of gstreamer-plugins-dts-0.10.11,3 to 
gstreamer-plugins-dts-0.10.13,3
Upgrade of gstreamer-plugins-dvd-0.10.11,3 to 
gstreamer-plugins-dvd-0.10.12,3
Upgrade of gstreamer-plugins-good-0.10.14,3 to 
gstreamer-plugins-good-0.10.15,3
Upgrade of gstreamer-plugins-libpng-0.10.14,3 to 
gstreamer-plugins-libpng-0.10.15,3
Upgrade of gstreamer-plugins-mad-0.10.11,3 to 
gstreamer-plugins-mad-0.10.12,3
Upgrade of gstreamer-plugins-ugly-0.10.11,3 to 
gstreamer-plugins-ugly-0.10.12,3
Upgrade of gstreamer-plugins-xvid-0.10.11,3 to 
gstreamer-plugins-xvid-0.10.13,3

hellas# 

 There doesn't seem to be a more recent version of the
x11-toolkits/linux-pango port available.  What is the best way to proceed?
Will a "portmaster -fv x11-toolkits/linux-pango" do the job for now?  (I'm
not too worried about the security bug for the moment.  Although I use mplayer
to play files, they don't generally involve .png files, and I don't use
mplayer to play streaming files.)
 Please copy me in on responses, otherwise I won't see them till the
next freebsd-ports digest is sent out.  Thanks!


  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: next abort of perl upgrade encountered--linux-pango security problem :-(

[Sergey V. Dyatko]

В Thu, 25 Jun 2009 01:21:19 -0500 (CDT)
Scott Bennett  пишет:

SB>  The saga of failures in the perl upgrade continues with the
SB> following:
SB> 
SB> ===>   linux-gtk2-2.6.10_3 depends on
SB> file: /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 - not found
SB> ===>Verifying install
SB> for /compat/linux/usr/lib/libpango-1.0.so.0.1001.1
SB> in /usr/ports/x11-toolkits/linux-pango ===>  linux-pango-1.10.2_3
SB> has known vulnerabilities: => pango -- integer overflow. Reference:
SB> 

SB> => Please update your ports tree and try again. *** Error code 1
[skipped]
SB> 
SB>  There doesn't seem to be a more recent version of the
SB> x11-toolkits/linux-pango port available.  What is the best way to
SB> proceed? Will a "portmaster -fv x11-toolkits/linux-pango" do the
SB> job for now?  (I'm not too worried about the security bug for the
SB> moment.  Although I use mplayer to play files, they don't generally
SB> involve .png files, and I don't use mplayer to play streaming
SB> files.) Please copy me in on responses, otherwise I won't see them
SB> till the next freebsd-ports digest is sent out.  Thanks!
SB> 
SB> 
SB>   Scott Bennett, Comm. ASMELG, CFIAG
1) deinstall portaudit
2) upgrate all ports
3) install portaudit if you need it

or

1)rm /var/db/portaudit/auditfile.tbz
2) upgrate all ports
3) portaudit -F


--
wbr, tiger
___
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: next abort of perl upgrade encountered--linux-pango security problem :-(

[Sergey V. Dyatko]

В Thu, 25 Jun 2009 09:37:52 +0300
"Sergey V. Dyatko"  пишет:

SVD> В Thu, 25 Jun 2009 01:21:19 -0500 (CDT)
SVD> Scott Bennett  пишет:
SVD> 
SVD> SB>  The saga of failures in the perl upgrade continues with
SVD> SB> the following:
SVD> SB> 
SVD> SB> ===>   linux-gtk2-2.6.10_3 depends on
SVD> SB> file: /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 - not
SVD> SB> found ===>Verifying install
SVD> SB> for /compat/linux/usr/lib/libpango-1.0.so.0.1001.1
SVD> SB> in /usr/ports/x11-toolkits/linux-pango ===>
SVD> SB> linux-pango-1.10.2_3 has known vulnerabilities: => pango --
SVD> SB> integer overflow. Reference:
SVD> SB> 

SVD> SB> => Please update your ports tree and try again. *** Error code
SVD> SB> 1
SVD> [skipped]
SVD> SB> 
SVD> SB>  There doesn't seem to be a more recent version of the
SVD> SB> x11-toolkits/linux-pango port available.  What is the best way
SVD> SB> to proceed? Will a "portmaster -fv x11-toolkits/linux-pango"
SVD> SB> do the job for now?  (I'm not too worried about the security
SVD> SB> bug for the moment.  Although I use mplayer to play files,
SVD> SB> they don't generally involve .png files, and I don't use
SVD> SB> mplayer to play streaming files.) Please copy me in on
SVD> SB> responses, otherwise I won't see them till the next
SVD> SB> freebsd-ports digest is sent out.  Thanks!
SVD> SB> 
SVD> SB> 
SVD> SB>   Scott Bennett, Comm. ASMELG,
SVD> SB> CFIAG
SVD> 1) deinstall portaudit
SVD> 2) upgrate all ports
SVD> 3) install portaudit if you need it
SVD> 
SVD> or
SVD> 
SVD> 1)rm /var/db/portaudit/auditfile.tbz
SVD> 2) upgrate all ports
SVD> 3) portaudit -F
SVD> 
or set environment variable DISABLE_VULNERABILITIES and
upgrade port(s)

--
wbr, tiger
___
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"