Hi,
Albert Shih wrote on 19.05.2013 20:29:
Hi all
Just report the
/usr/ports/lang/python33
don't build on
FreeBSD 9.1-STABLE #3 r250807: Sun May 19 17:48:52 CEST 2013
all other ports are up2date.
Here the output :
Regards.
I was only able to reproduce it once, but then the br
I just recently (last week) converted my "root on USB; data on ZFS" setup
using 2x mirror vdevs to "root-on-zfs". Works beautifully, and can boot off
any of the 4 drives in the pool. Using standard loader and gptzfsboot.
PC-BSD 9.1-p3.
And, I just configured a new storage server at work using Fre
As firefox is a seldom-used backup browser, I don't want to test
it, but would if I had the time (seamonkey stuff is also in
that subdirectory and it is one my primary browsers).
No NFS mounted.
BTW I recovered the url's that I had lost from the adblock preference line in
prefs.js, so that is so
On 2013-05-20 21:26, Wes Morgan wrote:
Trying to boot a zfs (GPT) partition with the latest patch gives me an
"unaligned pointer " sometimes. When I enable all the
debugging I can also get an error "invalid nvlist header". Currently
just
booting from a ufs partition acting as /boot, but my goal
Trying to boot a zfs (GPT) partition with the latest patch gives me an
"unaligned pointer " sometimes. When I enable all the
debugging I can also get an error "invalid nvlist header". Currently just
booting from a ufs partition acting as /boot, but my goal would be to get
rid of that extra partitio
On 05/20/13 02:23, Koichiro IWAO wrote:
I have met the same problem.
With gcc47 fails, gcc48 or clang works.
Regards,
I can confirm that it works with clang from ports. I am not sure why it gives
the bus error when compiled with gcc46 though.
Thanks,
Naram Qashat
__
On 20/05/2013 15:38, Bob Eager wrote:
On Mon, 20 May 2013 08:03:09 -0500
sindrome wrote:
What I think is happening is that portupgrade is building and running
shell scripts in /tmp. It's running them with (in ruby):
system('/tmp/script') [roughly]
The ruby runtime is checking t
Hi,
I'm experiencing firefox crashes since updating to 21.0. It works properly
following the restore of my ~/.mozilla directory however subsequently it
crashes on start-up or shortly thereafter. Googling firefox 21.0 crash brings
up four or five hits at the Mozilla support forums site, so this
2013/5/20 Jeffrey Bouquet
> Firefox 21 would not run (segfaulted). I pkg_added Firefox 20, and it
> works, but I lost all the sites it for years had open at the start, they
> are nowhere... maybe I'll find them in a backup later.
>
> ...
> Midori would not run, but "midori -d -p' seems to work.
Please let us know if it's still a problem and we can narrow it down
further. :)
Chris
On 20 May 2013 20:20, "sindrome" wrote:
> Apologies Chris. I removed it but am out of town so will have to test
> next week. I appreciate all your help. I'll let you know if that makes it
> go away.
>
>
> O
Apologies Chris. I removed it but am out of town so will have to test next
week. I appreciate all your help. I'll let you know if that makes it go
away.
On Mon, May 20, 2013 at 1:04 PM, Chris Rees wrote:
> You are not 'sure'.
>
> Please do not solicit help and claim that you know better-- I
On Mon, May 20, 2013 at 07:13:46PM +0100, Chris Rees wrote:
> ...
> You're one of those crazy head/ people like me, aren't you? Perhaps
> this is a regression-- I really should have filed a PR about it to be
> honest...
>
Well, I track head daily for a "preview of coming attractions," but fo
On 05/20/13 20:07, Chris Rees wrote:
Do you have an NFS mounted home directory?
I do.
I've discovered that
Firefox doesn't like that, perhaps something to do with sqlite
locking.
Had this problem in the past, but it's long gone.
Since yesterday my extensions do not work anymore, but I
On 20 May 2013 19:11, David Wolfskill wrote:
> On Mon, May 20, 2013 at 07:07:32PM +0100, Chris Rees wrote:
>> ...
>> Do you have an NFS mounted home directory? I've discovered that
>> Firefox doesn't like that, perhaps something to do with sqlite
>> locking.
>>
>
> It (firefox-21.0_1,1 with
On Mon, May 20, 2013 at 07:07:32PM +0100, Chris Rees wrote:
> ...
> Do you have an NFS mounted home directory? I've discovered that
> Firefox doesn't like that, perhaps something to do with sqlite
> locking.
>
It (firefox-21.0_1,1 with an NFS-resident ~) worked OK on my home
desktop machine,
On 20 May 2013 19:05, Jeffrey Bouquet wrote:
> Firefox 21 would not run (segfaulted). I pkg_added Firefox 20, and it works,
> but I lost all the sites it for years had open at the start, they are
> nowhere... maybe I'll find them in a backup later.
>
> ...
> Midori would not run, but "midori -d
Firefox 21 would not run (segfaulted). I pkg_added Firefox 20, and it works,
but I lost all the sites it for years had open at the start, they are
nowhere... maybe I'll find them in a backup later.
...
Midori would not run, but "midori -d -p' seems to work. (The latest one will
not build, bu
You are not 'sure'.
Please do not solicit help and claim that you know better-- I told you
hours ago to remove . from your path.
Chris
On 20 May 2013 17:49, sindrome wrote:
> Fair enough but that's not the root of this problem I'm sure
>
>
> On Mon, May 20, 2013 at 11:47 AM, Torfinn Ingolfsen w
Ok, I've discovered a combination of things that will reproduce that message,
and it REALLY does come down to NOT HAVING '.' IN YOUR PATH, especially for
user root.
If I don't have '.' in my path, I can "cd" to any directory and Ruby will not
complain when I run the system() command (or the equiv
Fair enough but that's not the root of this problem I'm sure
On Mon, May 20, 2013 at 11:47 AM, Torfinn Ingolfsen wrote:
> On Mon, May 20, 2013 at 6:45 PM, sindrome wrote:
> > Clearly I'm not the only one with this problem. Something is amending
> onto
> > the PATH and I'd like to get to the bo
On Mon, May 20, 2013 at 6:45 PM, sindrome wrote:
> Clearly I'm not the only one with this problem. Something is amending onto
> the PATH and I'd like to get to the bottom of this. I'm sure it will help a
> lot of people.
Well, start by taking the current directory ('.') out of your PATH.
(It is
Clearly I'm not the only one with this problem. Something is amending onto
the PATH and I'd like to get to the bottom of this. I'm sure it will help
a lot of people.
On Mon, May 20, 2013 at 11:39 AM, Torfinn Ingolfsen wrote:
> On Mon, May 20, 2013 at 7:20 AM, Erich Dollansky
> wrote:
> >
> >
On Mon, May 20, 2013 at 7:20 AM, Erich Dollansky
wrote:
>
> Could it be that we all got this message but did not bother because we
> get so many warnings during an upgrade?
Nope. FWIW, portupgrade works without errors here.
tingo@kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE
I modified the PATH to remove those items you mentioned but I'm still
getting the following when I portupgrade. How can I track down what is
amending /tmp onto the PATH?
/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:1170: warning:
Insecure world writable dir /tmp/. in PATH, mode 041777
/
On 20 May 2013 17:07, "sindrome" wrote:
>
> Some are just document directories in my home. Do you have a suggested
PATH that I can use
Default PATH is good, from /etc/profile.
Adding ~/bin won't hurt, if you like that.
Chris
> On Mon, May 20, 2013 at 11:02 AM, Chris Rees wrote:
>>
>>
>> On 20
Some are just document directories in my home. Do you have a suggested PATH
that I can use
On Mon, May 20, 2013 at 11:02 AM, Chris Rees wrote:
>
> On 20 May 2013 16:53, "sindrome" wrote:
> >
> > echo $PATH
> >
> /bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/local/l
On 20 May 2013 16:53, "sindrome" wrote:
>
> echo $PATH
>
/bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/local/lib32/compat:/usr/X11R6/bin:/home/sindrome/.gnupg:/home/sindrome/bin:/home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome/docs/config:/sbin:/bin:/etc:/us
echo $PATH
/bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/local/lib32/compat:/usr/X11R6/bin:/home/sindrome/.gnupg:/home/sindrome/bin:/home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome/docs/config:/sbin:/bin:/etc:/usr/local/etc::/usr/bin:/usr/games:/usr/local/sbi
Hi,
On Mon, 20 May 2013 14:38:53 +0100
Bob Eager wrote:
> On Mon, 20 May 2013 08:03:09 -0500
> sindrome wrote:
>
> > Looks like a step in the right direction. How do I troubleshoot to
> > figure out what application is appending/changing the value of PATH?
>
> Nothing is. As far as I can see
Just out of curiosity, what is your PATH set to in whatever console/terminal
window before you run portupgrade ( echo $PATH )?
On Mon, May 20, 2013 at 08:03:09AM -0500, sindrome wrote:
> Looks like a step in the right direction. How do I troubleshoot to figure
> out what application is appending/
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
On Mon, 20 May 2013 08:03:09 -0500
sindrome wrote:
> Looks like a step in the right direction. How do I troubleshoot to
> figure out what application is appending/changing the value of PATH?
Nothing is. As far as I can see.
What I think is happening is that portupgrade is building and running
Looks like a step in the right direction. How do I troubleshoot to figure
out what application is appending/changing the value of PATH?
On Mon, May 20, 2013 at 2:56 AM, wrote:
> At Sat, 18 May 2013 18:34:47 -0500,
> sindrome wrote:
> > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports confli
Hello.
# uname -a
FreeBSD xx.x 9.1-RELEASE-p2 FreeBSD 9.1-RELEASE-p2 #1 r249400: Mon Apr
22 13:00:32 CEST 2013 root@xx.x:/usr/obj/usr/src/sys/XXX i386
# usbconfig
ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen1.1: at usbus1, cfg=0 md=HOST spd=FUL
(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
At Sat, 18 May 2013 18:34:47 -0500,
sindrome wrote:
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> Insecure world writable dir /tmp in PATH, mode 040777
At Sun, 19 May 2013 23:31:21 -0500,
sindrome wrote:
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warni
Sergio de Almeida Lenzi wrote:
> I can say that it builds with FreeBSD 9.1 and clang 3.2
> from /usr/bin/clang (native clang)...
Thanks for the pointer. I tried that, the build works and installs,
but it seems it still has some issues ?
Full build log here:
http://opsec.eu/backup/20130520
38 matches
Mail list logo
