Re: Windows 10 client password failures with samba410 on 12.1-STABLE
Nevermind. I had forgotten to set my user password with the smbpasswd command. Bob On Sun, Mar 15, 2020 at 05:21:15PM -0500, Bob Willcox wrote: > Hi All, > > I trying to replace a 11.3-STABLE system that is running samba48 with a > newwer system > running 12.1-STABLE and samba410. I'm using the same smb4.conf file that I've > been using > for years: > > # Samba config file created using SWAT > # from 10.1.132.3 (10.1.132.3) > # Date: 2009/01/12 08:19:38 > > [global] > workgroup = IMMURE > server string = Vader Samba Server > log file = /var/log/samba/log.%m > max log size = 1000 > server max protocol = SMB3_11 > client max protocol = SMB3_11 > dns proxy = No > interfaces = 10.1.132.0/255.255.254.0 > > [homes] > comment = Home Directories > read only = No > write list = bob > > [work] > path = /stor/work > read only = No > > [stuff] > path = /stor/stuff > comment = Public Stuff > public = yes > guest ok = yes > read only = No > writable = yes > write list = root bob @staff > > [ftp] > path = /stor/ftp/pub > read only = No > > [pub] > path = /stor/pub > read only = No > > The system I'm replacing is working fine and provides the access to the > shares as > expected. My new system results in failing the network credentials dialog box > on > the Windows client machine. At this point I've tried everything I can think > of w/o > any success. I really don't know how to proceed with trying to get this to > work. > > Any suggestions? Windows isn't my strong suit (been doing my best to ignore > it for > 35 years on now, unfortunately there are some situations where I can't). > > Any help would be greatly appreciated. > > Thanks, > Bob > > -- > Bob Willcox| It's possible that the whole purpose of your life is to > b...@immure.com | serve as a warning to others. > Austin, TX | > ___________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Windows 10 client password failures with samba410 on 12.1-STABLE
Hi All, I trying to replace a 11.3-STABLE system that is running samba48 with a newwer system running 12.1-STABLE and samba410. I'm using the same smb4.conf file that I've been using for years: # Samba config file created using SWAT # from 10.1.132.3 (10.1.132.3) # Date: 2009/01/12 08:19:38 [global] workgroup = IMMURE server string = Vader Samba Server log file = /var/log/samba/log.%m max log size = 1000 server max protocol = SMB3_11 client max protocol = SMB3_11 dns proxy = No interfaces = 10.1.132.0/255.255.254.0 [homes] comment = Home Directories read only = No write list = bob [work] path = /stor/work read only = No [stuff] path = /stor/stuff comment = Public Stuff public = yes guest ok = yes read only = No writable = yes write list = root bob @staff [ftp] path = /stor/ftp/pub read only = No [pub] path = /stor/pub read only = No The system I'm replacing is working fine and provides the access to the shares as expected. My new system results in failing the network credentials dialog box on the Windows client machine. At this point I've tried everything I can think of w/o any success. I really don't know how to proceed with trying to get this to work. Any suggestions? Windows isn't my strong suit (been doing my best to ignore it for 35 years on now, unfortunately there are some situations where I can't). Any help would be greatly appreciated. Thanks, Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg install no longer works on my newly installed system
On Tue, Feb 04, 2020 at 02:48:50PM -0600, Bob Willcox wrote: > On a newly installed 12.1 stable system for some reason I am now getting this > error > whenever I attempt to install any package via 'pkg install': > > root@jar-jar:1 /.amd_mnt/vader/host/stor/home/bob> pkg install ctags > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > All repositories are up to date. > The following 1 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: > ctags: 5.8 > > Number of packages to be installed: 1 > > 125 KiB to be downloaded. > > Proceed with this action? [y/N]: y > [1/1] Fetching ctags-5.8.txz: 100% 125 KiB 128.3kB/s00:01 > pkg: cached package ctags-5.8: size mismatch, fetching from remote > Fetching ctags-5.8.txz: 100% 125 KiB 128.3kB/s00:01 > pkg: cached package ctags-5.8: size mismatch, cannot continue > > Previously I was able to install some packages on this system. I did update > the > system via downloading the src and building/installing world and a new kernel. > > Anyone have any idea what is wrong with my system now and how to fix it? > > Thanks, > Bob I removed the repo-FreeBSD.sqlite in /var/db/pkg and tried doing a pkg install again and it downloaded/updated all the files in /var/db/pkg and then successfully downloaded and installed the ctags package. So it seems that something was not right with the files in there before (even though previously it worked). Bob > > -- > Bob Willcox| It's possible that the whole purpose of your life is to > b...@immure.com | serve as a warning to others. > Austin, TX | > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pkg install no longer works on my newly installed system
On a newly installed 12.1 stable system for some reason I am now getting this error whenever I attempt to install any package via 'pkg install': root@jar-jar:1 /.amd_mnt/vader/host/stor/home/bob> pkg install ctags Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ctags: 5.8 Number of packages to be installed: 1 125 KiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching ctags-5.8.txz: 100% 125 KiB 128.3kB/s00:01 pkg: cached package ctags-5.8: size mismatch, fetching from remote Fetching ctags-5.8.txz: 100% 125 KiB 128.3kB/s00:01 pkg: cached package ctags-5.8: size mismatch, cannot continue Previously I was able to install some packages on this system. I did update the system via downloading the src and building/installing world and a new kernel. Anyone have any idea what is wrong with my system now and how to fix it? Thanks, Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Why are there 1981 p5-* subdirectories in /usr/ports/devel?
I find the number of perl subdirectores in the /usr/ports/devel directory pretty annoying to navigate. Is there a reason there needs to be 1981 of them? Couldn't there be a better way to organize all of the perl ports so that they don't clutter up the devel directory so much? Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: firefox fails to start with JavaScript error
I discovered my problem. Several years ago I pointed the firefox profile to a directory in the /var filesystem so that I could run it from several systems in my network at once w/o problems (each system had its own set of profiles). So this was a local configuration/setup issue since my new system didn't have the requisite directory setup yet...woops! :) Sorry for the noise. Bob On Sun, May 12, 2019 at 10:04:23AM -0500, Bob Willcox wrote: > This is on a new system/install with firefox-66.0.5,1. When I try t run > firefox it fails with this error message: > > JavaScript error: > jar:file:///usr/local/lib/firefox/omni.ja!/components/XULStore.js > > The system does have the omni.ja file installed: > > root@darth:6 /root> ls -l /usr/local/lib/firefox/ > total 79827 > -rw-r--r-- 1 root wheel419 May 12 09:19 application.ini > drwxr-xr-x 4 root wheel 7 May 12 09:42 browser > drwxr-xr-x 3 root wheel 3 May 12 09:42 chrome > -rw-r--r-- 1 root wheel 0 May 12 09:32 chrome.manifest > drwxr-xr-x 3 root wheel 3 May 12 09:42 defaults > -rw-r--r-- 1 root wheel 55 May 12 09:32 dependentlibs.list > -rwxr-xr-x 1 root wheel 255376 May 12 09:29 firefox > -rwxr-xr-x 1 root wheel 255376 May 12 09:29 firefox-bin > drwxr-xr-x 3 root wheel 3 May 12 09:42 gmp-clearkey > drwxr-xr-x 2 root wheel 3 May 12 09:42 gtk2 > -rwxr-xr-x 1 root wheel 68296 May 12 09:29 liblgpllibs.so > -rwxr-xr-x 1 root wheel2536896 May 12 09:29 libmozavcodec.so > -rwxr-xr-x 1 root wheel 312616 May 12 09:29 libmozavutil.so > -rwxr-xr-x 1 root wheel 17680 May 12 09:27 libmozgtk.so > -rwxr-xr-x 1 root wheel 23784 May 12 09:27 libmozwayland.so > -rwxr-xr-x 1 root wheel 144021976 May 12 09:32 libxul.so > -rw-r--r-- 1 root wheel 16728168 May 12 09:32 omni.ja > -rwxr-xr-x 1 root wheel 266656 May 12 09:29 pingsender > -rw-r--r-- 1 root wheel 48 May 12 09:32 platform.ini > -rwxr-xr-x 1 root wheel 245976 May 12 09:32 plugin-container > -rw-r--r-- 1 root wheel 0 May 12 09:32 removed-files > > Not being a JavaScript person, I have no idea where to go from here in trying > to diagnose what's wrong. > > Any help would be much appreciated. > > Thanks, > Bob > > -- > Bob Willcox| "The only way to get rid of temptation is to yield to it... > b...@immure.com | I can resist everything but temptation." > Austin, TX | - Oscar Wilde > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| "The only way to get rid of temptation is to yield to it... b...@immure.com | I can resist everything but temptation." Austin, TX | - Oscar Wilde ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
firefox fails to start with JavaScript error
This is on a new system/install with firefox-66.0.5,1. When I try t run firefox it fails with this error message: JavaScript error: jar:file:///usr/local/lib/firefox/omni.ja!/components/XULStore.js The system does have the omni.ja file installed: root@darth:6 /root> ls -l /usr/local/lib/firefox/ total 79827 -rw-r--r-- 1 root wheel419 May 12 09:19 application.ini drwxr-xr-x 4 root wheel 7 May 12 09:42 browser drwxr-xr-x 3 root wheel 3 May 12 09:42 chrome -rw-r--r-- 1 root wheel 0 May 12 09:32 chrome.manifest drwxr-xr-x 3 root wheel 3 May 12 09:42 defaults -rw-r--r-- 1 root wheel 55 May 12 09:32 dependentlibs.list -rwxr-xr-x 1 root wheel 255376 May 12 09:29 firefox -rwxr-xr-x 1 root wheel 255376 May 12 09:29 firefox-bin drwxr-xr-x 3 root wheel 3 May 12 09:42 gmp-clearkey drwxr-xr-x 2 root wheel 3 May 12 09:42 gtk2 -rwxr-xr-x 1 root wheel 68296 May 12 09:29 liblgpllibs.so -rwxr-xr-x 1 root wheel2536896 May 12 09:29 libmozavcodec.so -rwxr-xr-x 1 root wheel 312616 May 12 09:29 libmozavutil.so -rwxr-xr-x 1 root wheel 17680 May 12 09:27 libmozgtk.so -rwxr-xr-x 1 root wheel 23784 May 12 09:27 libmozwayland.so -rwxr-xr-x 1 root wheel 144021976 May 12 09:32 libxul.so -rw-r--r-- 1 root wheel 16728168 May 12 09:32 omni.ja -rwxr-xr-x 1 root wheel 266656 May 12 09:29 pingsender -rw-r--r-- 1 root wheel 48 May 12 09:32 platform.ini -rwxr-xr-x 1 root wheel 245976 May 12 09:32 plugin-container -rw-r--r-- 1 root wheel 0 May 12 09:32 removed-files Not being a JavaScript person, I have no idea where to go from here in trying to diagnose what's wrong. Any help would be much appreciated. Thanks, Bob -- Bob Willcox| "The only way to get rid of temptation is to yield to it... b...@immure.com | I can resist everything but temptation." Austin, TX | - Oscar Wilde ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portupgrade + FLAVORS
Yeah, bdrewery is listed as the maintainer of portupgrade in its Makefile.
On Mon, May 06, 2019 at 06:05:24PM -0700, Kevin Oberman wrote:
> Oops. Disregard. Confusing portupgrade with portmaster.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> On Mon, May 6, 2019 at 6:03 PM Kevin Oberman wrote:
>
> > Looks like the maintainer should be on the CC, so I added Stefan.
> > --
> > Kevin Oberman, Part time kid herder and retired Network Engineer
> > E-mail: rkober...@gmail.com
> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> >
> >
> > On Mon, May 6, 2019 at 11:35 AM Bob Willcox wrote:
> >
> >> On Sun, Apr 07, 2019 at 08:51:57PM -0500, Matthew D. Fuller wrote:
> >> > For any portupgrade users still out there wishing for FLAVOR support,
> >> > I have patches to add it. I've been running them here locally for a
> >> > few weeks without incident (apart from an extra upgrade or two
> >> > actually working without manual intervention/resort to portmaster,
> >> > that is). Dropping the attached patch into
> >> > $PORTS/ports-mgmt/portupgrade/files/patch-flavors and rebuilding it is
> >> > a simple shortcut to getting it in place.
> >> >
> >> > I haven't done any testing of using portupgrade with pre-built
> >> > packages (is there even any reason to post-pkg?), or using portinstall
> >> > (never saw the point), but it seems to handle the upgrading path just
> >> > fine.
> >> >
> >> >
> >> > Also sitting in a PR upstream at
> >> > https://github.com/freebsd/portupgrade/pull/72
> >> >
> >> >
> >> > --
> >> > Matthew Fuller (MF4839) | fulle...@over-yonder.net
> >> > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
> >> >On the Internet, nobody can hear you scream.
> >>
> >> > --- bin/portupgrade.orig 2018-03-09 18:59:29 UTC
> >> > +++ bin/portupgrade
> >> > @@ -1147,6 +1147,11 @@ def get_make_args(origin, pkgname = nil)
> >> >else
> >> > args = $make_args.split(' ')
> >> >end
> >> > +
> >> > + if flavor = origin[/@(.+)$/, 1]
> >> > +args << 'FLAVOR=' + flavor
> >> > + end
> >> > +
> >> >quoted = 0
> >> >n = 0
> >> >is_quoted = false
> >> > --- lib/pkgtools/pkgdb.rb.orig2018-03-09 18:59:29 UTC
> >> > +++ lib/pkgtools/pkgdb.rb
> >> > @@ -425,10 +425,20 @@ class PkgDB
> >> >@installed_pkgs = []
> >> >@installed_ports = []
> >> >@db = {}
> >> > +
> >> > + flavors = {}
> >> > + pkg_flavors = xbackquote(PkgDB::command(:pkg), 'annotate', '-Sa',
> >> > + 'flavor').split("\n")
> >> > + pkg_flavors.each do |line|
> >> > +pkg, flavor = line.sub(/: Tag: flavor Value: /, ':').split(':')
> >> > +flavors[pkg] = flavor
> >> > + end
> >> > +
> >> >pkg_origins = xbackquote(PkgDB::command(:pkg), 'query', '%n-%v
> >> %o').split("\n")
> >> >pkg_origins.each do |line|
> >> > pkg, origin = line.split(' ')
> >> > @installed_pkgs << pkg
> >> > +origin << '@' + flavors[pkg] if flavors[pkg]
> >> > add_origin(pkg, origin)
> >> >end
> >> >@installed_pkgs.freeze
> >> > --- lib/pkgtools/portsdb.rb.orig 2018-03-09 18:59:29 UTC
> >> > +++ lib/pkgtools/portsdb.rb
> >> > @@ -325,6 +325,7 @@ class PortsDB
> >> >end
> >> >
> >> >def portdir(port)
> >> > +port = port.sub(/@.*$/, '')
> >> > File.join(ports_dir, port)
> >> >end
> >> >
> >>
> >> > _______
> >> > freebsd-ports@freebsd.org mailing list
> >> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org
> >> "
> >>
> >> Hi Mathew,
> >>
> >> Thanks for the flavors patch to portupgrade. As with some others here it
> >> is
> >> still my preferred tool for keeping my ports up-to-date.
> >>
> >> Any word on when/if your patch will be integraded into the port proper?
> >>
> >> Thanks again,
> >> Bob
> >>
> >>
> >> --
> >> Bob Willcox| "The only way to get rid of temptation is to yield to
> >> it...
> >> b...@immure.com | I can resist everything but temptation."
> >> Austin, TX | - Oscar Wilde
> >> ___
> >> freebsd-ports@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> >>
> >
--
Bob Willcox| "The only way to get rid of temptation is to yield to it...
b...@immure.com | I can resist everything but temptation."
Austin, TX | - Oscar Wilde
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portupgrade + FLAVORS
On Sun, Apr 07, 2019 at 08:51:57PM -0500, Matthew D. Fuller wrote:
> For any portupgrade users still out there wishing for FLAVOR support,
> I have patches to add it. I've been running them here locally for a
> few weeks without incident (apart from an extra upgrade or two
> actually working without manual intervention/resort to portmaster,
> that is). Dropping the attached patch into
> $PORTS/ports-mgmt/portupgrade/files/patch-flavors and rebuilding it is
> a simple shortcut to getting it in place.
>
> I haven't done any testing of using portupgrade with pre-built
> packages (is there even any reason to post-pkg?), or using portinstall
> (never saw the point), but it seems to handle the upgrading path just
> fine.
>
>
> Also sitting in a PR upstream at
> https://github.com/freebsd/portupgrade/pull/72
>
>
> --
> Matthew Fuller (MF4839) | fulle...@over-yonder.net
> Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
>On the Internet, nobody can hear you scream.
> --- bin/portupgrade.orig 2018-03-09 18:59:29 UTC
> +++ bin/portupgrade
> @@ -1147,6 +1147,11 @@ def get_make_args(origin, pkgname = nil)
>else
> args = $make_args.split(' ')
>end
> +
> + if flavor = origin[/@(.+)$/, 1]
> +args << 'FLAVOR=' + flavor
> + end
> +
>quoted = 0
>n = 0
>is_quoted = false
> --- lib/pkgtools/pkgdb.rb.orig2018-03-09 18:59:29 UTC
> +++ lib/pkgtools/pkgdb.rb
> @@ -425,10 +425,20 @@ class PkgDB
>@installed_pkgs = []
>@installed_ports = []
>@db = {}
> +
> + flavors = {}
> + pkg_flavors = xbackquote(PkgDB::command(:pkg), 'annotate', '-Sa',
> + 'flavor').split("\n")
> + pkg_flavors.each do |line|
> +pkg, flavor = line.sub(/: Tag: flavor Value: /, ':').split(':')
> +flavors[pkg] = flavor
> + end
> +
>pkg_origins = xbackquote(PkgDB::command(:pkg), 'query', '%n-%v
> %o').split("\n")
>pkg_origins.each do |line|
> pkg, origin = line.split(' ')
> @installed_pkgs << pkg
> +origin << '@' + flavors[pkg] if flavors[pkg]
> add_origin(pkg, origin)
>end
>@installed_pkgs.freeze
> --- lib/pkgtools/portsdb.rb.orig 2018-03-09 18:59:29 UTC
> +++ lib/pkgtools/portsdb.rb
> @@ -325,6 +325,7 @@ class PortsDB
>end
>
>def portdir(port)
> +port = port.sub(/@.*$/, '')
> File.join(ports_dir, port)
>end
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Hi Mathew,
Thanks for the flavors patch to portupgrade. As with some others here it is
still my preferred tool for keeping my ports up-to-date.
Any word on when/if your patch will be integraded into the port proper?
Thanks again,
Bob
--
Bob Willcox| "The only way to get rid of temptation is to yield to it...
b...@immure.com | I can resist everything but temptation."
Austin, TX | - Oscar Wilde
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deletion of the grpn port
On Thu, Dec 27, 2018 at 07:16:16PM +0200, Andriy Gapon wrote: > On 26/12/2018 21:52, Bob Willcox wrote: > > I just noticed that grpn has been delete from the freebsd ports. This is > > apparently due to its use of glib12 (which is deprecated) and lack of a > > maintainer. Anyone know how much difference there is between glib12 and the > > current version (glib20 I believe)? I've been using grpn for more years > > than I > > can remember and hate to see it disappear. > > Perhaps, math/galculator could take its place?.. Thanks for the tip...I have built it and so far, so good! :) > -- > Andriy Gapon -- Bob Willcox| If more of us valued food and cheer and song above hoarded b...@immure.com | gold, it would be a merrier world. Austin, TX | -- J. R. R. Tolkien ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Deletion of the grpn port
I just noticed that grpn has been delete from the freebsd ports. This is apparently due to its use of glib12 (which is deprecated) and lack of a maintainer. Anyone know how much difference there is between glib12 and the current version (glib20 I believe)? I've been using grpn for more years than I can remember and hate to see it disappear. -- Bob Willcox| If more of us valued food and cheer and song above hoarded b...@immure.com | gold, it would be a merrier world. Austin, TX | -- J. R. R. Tolkien ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: perl5.24 build failing on a new 11.1-STABLE install
On Wed, Mar 28, 2018 at 12:45:27PM +, Antoine Brodin wrote: > On Wed, Mar 28, 2018 at 12:42 PM, Michael Grimm <trash...@ellael.org> wrote: > > Antoine Brodin <anto...@freebsd.org> wrote: > > > >> On Wed, Mar 28, 2018 at 12:04 PM, Michael Grimm <trash...@ellael.org> > >> wrote: > > > >>> FreeBSD 11.1-STABLE #0 r331660: Wed Mar 28 08:36:15 CEST 2018 > >>> root@mer-waases:/usr/obj/usr/src/sys/CUSTOM > > > >> You can try to revert https://svnweb.freebsd.org/changeset/base/331551 > > > > Please excuse my ignorance, but I haven't done that before. After a quick > > scan in svn help I came up with: > > > > svn merge -r 331660:331551 > > > > Is this correct? > > What I want to achieve is keeping all commits besides 331551 > > svn merge -c -331551 . > > Antoine Thanks Antoine, I've done the above svn command and am now rebuilding world on my system. Should be able to give it a try this evening when I get home. Bob -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
perl5.24 build failing on a new 11.1-STABLE install
Hi, I have just recently installed 11.1-STABLE on one of me laptops (Lenovo T470s) and when I attempt to build the perl5.24 port it errors out with this: --- perl --- cc -o perl -lpthread -Wl,-E -fstack-protector-strong -L/usr/local/lib -Wl,-R/usr/local/lib/perl5/5.24/mach/CORE maindtrace/perlmain.o dtrace_main.o libperl.so.5.24.3 `cat ext.libs` -lpthread -lm -lcrypt -lutil maindtrace/perlmain.o: In function `main': perlmain.c:(.text+0xa4): undefined reference to `perl_parse' perlmain.c:(.text+0xb4): undefined reference to `perl_run' perlmain.c:(.text+0x128): undefined reference to `perl_destruct' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [perl] Error code 1 The system 'uname -a' is: FreeBSD exar.immure.com 11.1-STABLE FreeBSD 11.1-STABLE #0 r331606: Tue Mar 27 07:27:39 CDT 2018 b...@exar.immure.com:/usr/obj/usr/src/sys/EXAR amd64 It looks like (some) functions within perl.c are undefined. I have a number of other systems where this isn't a problem. Indeed, this is the only one with this failure. Anyone have any idea as to what may be wrong with or missing on this system? Thanks, Bob -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What is the status of the ical calendar program?
On Tue, Mar 20, 2018 at 11:50:44PM +1100, Kubilay Kocak wrote: > On 20/03/2018 11:39 pm, Bob Willcox wrote: > > Attempting to build ical on any of my 12.0-CURRENT systems results in this > > error: > > > > fatal error: too many errors emitted, stopping now [-ferror-limit=] > > 3836 warnings and 20 errors generated. > > *** [main.o] Error code 1 > > > > make[1]: stopped in /usr/ports/deskutils/ical/work/ical-2.2 > > 1 error > > > > make[1]: stopped in /usr/ports/deskutils/ical/work/ical-2.2 > > ===> Compilation failed unexpectedly. > > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > > the maintainer. > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/deskutils/ical > > > > So it looks like ical is currently broken in CURRENT. Are there any plans to > > fix this? Alternatively, is there some other calendar program that folks use > > that is a good replacement. So far, the several I have tried (xcaledar, > > phpicalendar, gsimplecal, & gnome-calendar) don't seem like good > > substitutes. > > Hi Bob, > > The above log doesn't include the reasons why it failed (the error(s) > are further up), which will be the first port of call figuring out > what's happening. > > Also note that CURRENT recently introduced Clang 6.0.0, which caused > many ports to fail, many of which haven't been fixed yet. This could be > one of them. > > I'd start by opening a Bugzilla issue "deskutils/ical: Fails to build on > CURRENT", and include the full build log as an attachment. Please reply > here with the Bugzilla ID/url when you do so others can follow and/or > assist there. > > Given the port doesn't currently have a maintainer, I'd then (either > myself, or with help from others here, on the mailing lists or on IRC) > try to isolate the issue and provide a patch. > > ./koobs Fair enough, I was simply checking to see if someone already was asware of this and maybe had a solution. So, here are the start of the (3836) warnings: --- main.o --- In file included from main.C:57: ./ical_start.gen:1:1: warning: ISO C++11 does not allow conversion from string literal to 'char *' [-Wwritable-strings] "# Generated automatically from startup.tcl.in by configure.", ^ ./ical_start.gen:2:1: warning: ISO C++11 does not allow conversion from string literal to 'char *' [-Wwritable-strings] "# Copyright (c) 1993 by Sanjay Ghemawat", ^ ./ical_start.gen:3:1: warning: ISO C++11 does not allow conversion from string literal to 'char *' [-Wwritable-strings] "###", ^ And here are the first two errors: In file included from main.C:82: ./bitmaps/left.xbm:5:16: error: constant expression evaluates to 128 which cannot be narrowed to type 'char' [-Wc++11-narrowing] 0x00, 0x00, 0x80, 0x01, 0x40, 0x01, 0x20, 0x01, 0x10, 0x01, 0x08, 0x7f, ^~~~ ./bitmaps/left.xbm:5:16: note: insert an explicit cast to silence this issue 0x00, 0x00, 0x80, 0x01, 0x40, 0x01, 0x20, 0x01, 0x10, 0x01, 0x08, 0x7f, ^~~~ static_cast( ) ./bitmaps/left.xbm:7:28: error: constant expression evaluates to 128 which cannot be narrowed to type 'char' [-Wc++11-narrowing] 0x20, 0x01, 0x40, 0x01, 0x80, 0x01, 0x00, 0x00}; ^~~~ ./bitmaps/left.xbm:7:28: note: insert an explicit cast to silence this issue 0x20, 0x01, 0x40, 0x01, 0x80, 0x01, 0x00, 0x00}; ^~~~ static_cast( ) Finally, the last few errors: In file included from main.C:85: ./bitmaps/done.xbm:4:16: error: constant expression evaluates to 255 which cannot be narrowed to type 'char' [-Wc++11-narrowing] 0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c, ^~~~ ./bitmaps/done.xbm:4:16: note: insert an explicit cast to silence this issue 0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c, ^~~~ static_cast( ) ./bitmaps/done.xbm:4:22: error: constant expression evaluates to 143 which cannot be narrowed to type 'char' [-Wc++11-narrowing] 0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c, ^~~~ ./bitmaps/done.xbm:4:22: note: insert an explicit cast to silence this issue 0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c, ^~~~ static_cast( ) ./bitmaps/done.xbm:4:28: error: constant expression evaluates to 255 which cannot be narrowed to type 'char' [-Wc++11-narrowing] 0x00, 0x00, 0xff, 0x8f, 0xff, 0x67, 0x03, 0x30, 0x03, 0x18, 0x03, 0x4c, ^~~~ ./bitmaps/done.xbm:4:28: note:
What is the status of the ical calendar program?
Attempting to build ical on any of my 12.0-CURRENT systems results in this error: fatal error: too many errors emitted, stopping now [-ferror-limit=] 3836 warnings and 20 errors generated. *** [main.o] Error code 1 make[1]: stopped in /usr/ports/deskutils/ical/work/ical-2.2 1 error make[1]: stopped in /usr/ports/deskutils/ical/work/ical-2.2 ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/deskutils/ical So it looks like ical is currently broken in CURRENT. Are there any plans to fix this? Alternatively, is there some other calendar program that folks use that is a good replacement. So far, the several I have tried (xcaledar, phpicalendar, gsimplecal, & gnome-calendar) don't seem like good substitutes. Thanks, Bob -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Exim and CVE-2018-6789
On Wed, Mar 07, 2018 at 02:39:58PM -0700, The Doctor wrote: > On Wed, Mar 07, 2018 at 02:13:00PM -0600, Bob Willcox wrote: > > Hi All, > > > > What is the status of FreeBSD's exim port regarding the CVE-2018-6789 > > vulnerability? Has it been fixed or is the fix in the works? > > > > Check exim. > > I believe Exim 4.90_1 answers this. Thanks, I wasn't sure since the log update didn't spell out that it addressed CVE-2018-6789, nor could I find it on the web page that 316b3c3e-0e98-11e8-8d41-97657151f8c2 took me to (via google). Bob > > > Thanks, > > Bob > > > > -- > > Bob Willcox| The amount of flak received on any subject is inversely > > b...@immure.com | proportional to the subject's true value. > > Austin, TX | > > ___ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici > doctor@@nl2k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist > rising! > https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism > To make pleasures pleasant, shorten them. -Charles Buxton -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Exim and CVE-2018-6789
Hi All, What is the status of FreeBSD's exim port regarding the CVE-2018-6789 vulnerability? Has it been fixed or is the fix in the works? Thanks, Bob -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
synth "--:--:-- check-sanity accessibility/at-spi2-atk" - what/why?
When I run synth 'upgrade-system' lately I always get a port build stuck in the "check-sanity" phase. Seems to never progress or complete (left one attempt over night w/o any obvious progress. So, can anyone tell me what might cause a port to get stuck in the check-sanity phase? Thanks, Bob -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: I've started getting ^@^@> in my xterms w/mutt
On Wed, Jan 03, 2018 at 08:45:48AM -0800, David Wolfskill wrote: > On Wed, Jan 03, 2018 at 10:19:09AM -0600, Bob Willcox wrote: > > ... > > Hi David, > > > > Thanks for your responses, but by setting the environment variables that you > > are using I'm still not getting the special chars I used to get (something > > that looks like a modified capital 'L' and a long dash (I think). > > IIRC, that one is a Polish character -- as in the first letter of > "??ukasiewicz" (the surname of the guy credited for "Polish notation"). > > One other -- possibly relevant -- thing I've noted is that with my > default xterm font (6x10), I do *not* get Chinese & Arabic characters, > but if I change the xterm (Ctl+Right button) to a larger font, they > show up OK. > > > Strangely, this behavior began suddenly on the several of my systems that I > > access mutt via an xterm at the same time. Two of them I had updated > > recently > > but the third hasn't been updated since October. > > > Hmm.. How independent are these systems from one another? In > particular, do you arrange to either share or sync your home directory > among them? > > > Thanks, > > Bob > > . > > I hope this helps > > Peace, > david > -- > David H. Wolfskillda...@catwhisker.org > If you want the best Fake News, go to the best source of it: Donald J. Trump. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. I just tried some changes to my .muttrc file and by adding this setting: set ascii_chars # use ASCII instead of ACS chars for threads I now get these characters displayed for thread continuations for example from the frebsd-ports mail: 14640 O Jan 02 Roger Marquis ( 26) DEFAULT_VERSIONS conflicts 14641 O Jan 02 Adam Weinberger ( 38) `-> 14642 O Jan 02 Roger Marquis ( 19) `-> 14643 Os Jan 03 Mathieu Arnold ( 70) `-> Which isn't as good as what I was previously getting, but better than the ^@ ones before that looked like this: 14640 O Jan 02 Roger Marquis ( 26) DEFAULT_VERSIONS conflicts 14641 O Jan 02 Adam Weinberger ( 38) ^@^@> 642 O Jan 02 Roger Marquis ( 19) ^@^@> 643 Os Jan 03 Mathieu Arnold ( 70) ^@^@> I still have no idea what changed to cause this...sigh... Thanks, Bob -- Bob Willcox| If everything is coming your way, you're in the b...@immure.com | wrong lane. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
I've started getting ^@^@> in my xterms w/mutt
I recently updated my system (base OS and ports) that I read mail on using mutt (accessed via an xterm on a separate system) and am now seeing this sort of character string ^@^@> rather than the much more user friently characters I used to get. Anyone know what I can do to get back the more readable stuff? Is there some setting that I need to perform? Thanks, Bob -- Bob Willcox| If everything is coming your way, you're in the b...@immure.com | wrong lane. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: 6100 subdirectories in /usr/ports/devel!
On Fri, Dec 29, 2017 at 04:28:43AM +0700, Eugene Grosbein wrote:
> 29.12.2017 4:16, Bob Willcox wrote:
>
> >> In fact, ports/devel is first but not only category having similar problem
> >> with p5-* stuff:
> >>
> >> $ cd /usr/ports
> >> $ find . -type d -mindepth 1 -maxdepth 1 | while read category; do printf
> >> "%15s " ${category#./}; ls $category | sed 's/-.*//' | sort | uniq -c |
> >> sort -rn | head -1; done | sort -k 2,2 -rn | head -15
> >> devel 1908 p5
> >> www 807 p5
> >>textproc 617 p5
> >> net 327 p5
> >> databases 259 p5
> >>security 258 p5
> >>math 146 p5
> >>mail 145 p5
> >>graphics 100 p5
> >> editors 98 libreoffice
> >>sysutils 75 rubygem
> >> converters 72 p5
> >>misc 63 p5
> >>net-mgmt 56 p5
> >>x11-toolkits 49 p5
> >>
> >
> > Yeah, I happened to notice the py-* stuff due to some problems I have been
> > having with synth. I did notice the large number of p5-* subdirs but didn't
> > count them. :)
> >
> > Certainly seems to be out of control...
>
> I like we have all this p5-* stuff in the Ports.
> It seems that 1900+ devel/p5-* ports justify new p5-devel or devel-p5
> category, though.
>
> But wouldn't such large move become a nightmare for users updating their
> systems?
Yeah, I don't mind them being in there (have to admit that I haven't ever been
a perl fan, not since Larry Wall's first version in the '80s), and agree with
you that we should give them their own directory (or directories). I think the
py-* entries could stand the same treatment.
--
Bob Willcox| If everything is coming your way, you're in the
b...@immure.com | wrong lane.
Austin, TX |
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: 6100 subdirectories in /usr/ports/devel!
On Fri, Dec 29, 2017 at 03:54:28AM +0700, Eugene Grosbein wrote:
> 29.12.2017 3:36, Bob Willcox wrote:
>
> >> Does anyone else feel that having 6100 subdirectories (939 are for py-*
> >> stuff)
> >> is a bit excessive?
> >
> > It is. But py-* stuff has second place only:
> >
> > $ ls /usr/ports/devel | sed 's/-.*//' | sort | uniq -c | sort -rn | head
> > 1908 p5
> > 964 py
> > 600 rubygem
> > 280 hs
> > 176 pear
> > 57 R
> > 56 pecl
> > 48 elixir
> > 47 geany
> > 43 erlang
>
> In fact, ports/devel is first but not only category having similar problem
> with p5-* stuff:
>
> $ cd /usr/ports
> $ find . -type d -mindepth 1 -maxdepth 1 | while read category; do printf
> "%15s " ${category#./}; ls $category | sed 's/-.*//' | sort | uniq -c | sort
> -rn | head -1; done | sort -k 2,2 -rn | head -15
> devel 1908 p5
> www 807 p5
>textproc 617 p5
> net 327 p5
> databases 259 p5
>security 258 p5
>math 146 p5
>mail 145 p5
>graphics 100 p5
> editors 98 libreoffice
>sysutils 75 rubygem
> converters 72 p5
>misc 63 p5
>net-mgmt 56 p5
>x11-toolkits 49 p5
>
Yeah, I happened to notice the py-* stuff due to some problems I have been
having with synth. I did notice the large number of p5-* subdirs but didn't
count them. :)
Certainly seems to be out of control...
--
Bob Willcox| If everything is coming your way, you're in the
b...@immure.com | wrong lane.
Austin, TX |
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
6100 subdirectories in /usr/ports/devel!
Does anyone else feel that having 6100 subdirectories (939 are for py-* stuff) is a bit excessive? I hadn't really looked at the number of subdirectories there in quite a long time and was shocked to see how meny there are now. -- Bob Willcox| If everything is coming your way, you're in the b...@immure.com | wrong lane. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: firefox is pretty useless ...
On Wed, Jul 05, 2017 at 02:07:29AM -0400, DTD wrote:
> if you use xfce. By definition it is not a problem that:
>
>1) install a new copy of FreeBSD 10.3
>2) pkg install xorg
>3) pkg install xfce
>4) pkg install firefox
>
> installs a firefox package that does not run. The project seems to do a bit
> better than this on Windows, but they (I think) have to in that environment.
> The
> official answer to the above is:
>
> --- Comment #1 from Jan Beich <jbe...@freebsd.org> ---
> Partial upgrades i.e., mixing dependencies from different svn checkouts, dates
> of "pkg install" or locking dependencies, are not supported. firefox will
> refuse to build unless you upgrade sqlite3. Some version requirement are
> specified in the port's Makefile
>
>$ fgrep sqlite www/firefox/Makefile
>sqlite3>=3.17.0:databases/sqlite3 \
>${PYTHON_PKGNAMEPREFIX}sqlite3>0:databases/py-sqlite3 \
>
> "pkg upgrade" may help you resolve this.
>
> The only problem with this 'solution' is that upgrading sqlite requires a
> cascading series of updates that breaks parts of xfce. Other than that no
> problem here. So if you use twm firefox is your browser.
>
> The next time I build a system I will try installing firefox first. I got
> here
> because I wanted to ungrade thunar (xfce's file manager). That upgrade broke
> the version of firefox that was running (47.somethine). Chasing and fixing
> that
> chain eventually required a reinstall. Happily (for me) chrome works.
Hmm, what firefox port are you building/running? I'm running version 54.0
(firefox-54.0.1_1,1) without any real issues (well, none at this point). I
don't install or run xfce, but use the ctwm window manager (ctwm-4.0.0,1).
Perhaps that's the difference.
I'm also running 10.3:
FreeBSD luke.immure.com 10.3-STABLE FreeBSD 10.3-STABLE #3 r320754: Thu Jul 6
15:13:13 CDT 2017 b...@luke.immure.com:/usr/obj/usr/src/sys/LUKE amd64
As an asside, I recommend running v 54 of firefox in any event. The new
thread support seems to have significantly improved its performance and
stability for me (at least).
>
>
> _
> Douglas Denault
> http://www.safeport.com
> d...@safeport.com
> Voice: 301-217-9220
>Fax: 301-217-9277
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
--
Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and
b...@immure.com |come out as a sausage.
Austin, TX |-- Ambrose Bierce
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: make install for print/texinfo fails on -CURRENT
Hmm, I just tried running synth on my test system again (this is the system that I successfully built and install texinfo on just a bit ago) and synth still fails with the same build errors as before. I'm not all that familiar with synth, but it appears that it may be working with some old stuff. I have to say, I haven't been a fan of perl since Larry Wall first came out with it back in the 80s, and this sort of mess isn't improving my opinion any. Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: make install for print/texinfo fails on -CURRENT
On Tue, Jul 11, 2017 at 03:26:30PM +0200, Herbert J. Skuhra wrote: > > On 11 July 2017 at 15:18 Bob Willcox <b...@immure.com> wrote: > > > > > > On Tue, Jul 11, 2017 at 03:12:12PM +0200, Herbert J. Skuhra wrote: > > > > On 11 July 2017 at 14:51 Bob Willcox <b...@immure.com> wrote: > > > > > > > > > > > > On Tue, Jul 11, 2017 at 01:13:33PM +0200, Herbert J. Skuhra wrote: > > > > > > On 10 July 2017 at 22:59 Bob Willcox <b...@immure.com> wrote: > > > > > > > > > > > > > > > > > > On Mon, Jul 10, 2017 at 10:21:21PM +0200, Herbert J. Skuhra wrote: > > > > > > > Bob Willcox skrev: > > > > > > > > > > > > > > > > On Mon, Jul 10, 2017 at 09:49:06PM +0200, Herbert J. Skuhra > > > > > > > > wrote: > > > > > > > >> Bob Willcox skrev: > > > > > > > >> > > > > > > > > >> > The make ran w/o any errors but when I attempt to do the > > > > > > > >> > install I get > > > > > > > >> > this: > > > > > > > >> > > > > > > > > >> > root@jabba:0 /usr/ports/print/texinfo> make install > > > > > > > >> > ===> Installing for texinfo-6.4_1,1 > > > > > > > >> > ===> texinfo-6.4_1,1 depends on package: perl5>=5.24<5.25 > > > > > > > >> > - found > > > > > > > >> > ===> texinfo-6.4_1,1 depends on executable: indexinfo - > > > > > > > >> > found > > > > > > > >> > ===> Checking if texinfo already installed > > > > > > > >> > ===> Registering installation for texinfo-6.4_1,1 > > > > > > > >> > pkg-static: Unable to access file > > > > > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.a:No > > > > > > > >> > such file or directory > > > > > > > >> > pkg-static: Unable to access file > > > > > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.so:No > > > > > > > >> > such file or directory > > > > > > > >> > pkg-static: Unable to access file > > > > > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/share/texinfo/Texinfo/Convert/XSParagraph/TestXS.pm:No > > > > > > > >> > such file or directory > > > > > > > >> > *** Error code 74 > > > > > > > >> > > > > > > > > >> > Stop. > > > > > > > >> > make[1]: stopped in /usr/ports/print/texinfo > > > > > > > >> > *** Error code 1 > > > > > > > >> > > > > > > > > >> > Stop. > > > > > > > >> > make: stopped in /usr/ports/print/texinfo > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > Is anyone else seeing this? > > > > > > > >> > > > > > > > >> I am not, but there is already a PR: > > > > > > > >> > > > > > > > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220460 > > > > > > > > > > > > > > > > Ah, ok...thanks for pointing that out. I hadn't seen it. > > > > > > > > > > > > > > Hmm, the PR shows: > > > > > > > > > > > > > > TestXS.c: loadable library and perl binaries are mismatched (got > > > > > > > handshake key 0xdf00080, needed 0xd200080) > > > > > > > checking whether we can build Perl extension (XS) modules... no > > > > > > > > > > > > > > Do you also get this error? > > > > > > > Have you tried to cleanup your perl installation and rebuild perl > > > > > > > and "p5-" ports? > > > > > > > > > > > > > > -- > > > > > > > Herbert > > > > > > > > > > > > No, I haven't done anything with perl since back in April. Indeed, > > > > >
Re: make install for print/texinfo fails on -CURRENT
On Tue, Jul 11, 2017 at 03:12:12PM +0200, Herbert J. Skuhra wrote: > > On 11 July 2017 at 14:51 Bob Willcox <b...@immure.com> wrote: > > > > > > On Tue, Jul 11, 2017 at 01:13:33PM +0200, Herbert J. Skuhra wrote: > > > > On 10 July 2017 at 22:59 Bob Willcox <b...@immure.com> wrote: > > > > > > > > > > > > On Mon, Jul 10, 2017 at 10:21:21PM +0200, Herbert J. Skuhra wrote: > > > > > Bob Willcox skrev: > > > > > > > > > > > > On Mon, Jul 10, 2017 at 09:49:06PM +0200, Herbert J. Skuhra wrote: > > > > > >> Bob Willcox skrev: > > > > > >> > > > > > > >> > The make ran w/o any errors but when I attempt to do the install > > > > > >> > I get > > > > > >> > this: > > > > > >> > > > > > > >> > root@jabba:0 /usr/ports/print/texinfo> make install > > > > > >> > ===> Installing for texinfo-6.4_1,1 > > > > > >> > ===> texinfo-6.4_1,1 depends on package: perl5>=5.24<5.25 - > > > > > >> > found > > > > > >> > ===> texinfo-6.4_1,1 depends on executable: indexinfo - found > > > > > >> > ===> Checking if texinfo already installed > > > > > >> > ===> Registering installation for texinfo-6.4_1,1 > > > > > >> > pkg-static: Unable to access file > > > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.a:No > > > > > >> > such file or directory > > > > > >> > pkg-static: Unable to access file > > > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.so:No > > > > > >> > such file or directory > > > > > >> > pkg-static: Unable to access file > > > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/share/texinfo/Texinfo/Convert/XSParagraph/TestXS.pm:No > > > > > >> > such file or directory > > > > > >> > *** Error code 74 > > > > > >> > > > > > > >> > Stop. > > > > > >> > make[1]: stopped in /usr/ports/print/texinfo > > > > > >> > *** Error code 1 > > > > > >> > > > > > > >> > Stop. > > > > > >> > make: stopped in /usr/ports/print/texinfo > > > > > >> > > > > > > >> > > > > > > >> > Is anyone else seeing this? > > > > > >> > > > > > >> I am not, but there is already a PR: > > > > > >> > > > > > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220460 > > > > > > > > > > > > Ah, ok...thanks for pointing that out. I hadn't seen it. > > > > > > > > > > Hmm, the PR shows: > > > > > > > > > > TestXS.c: loadable library and perl binaries are mismatched (got > > > > > handshake key 0xdf00080, needed 0xd200080) > > > > > checking whether we can build Perl extension (XS) modules... no > > > > > > > > > > Do you also get this error? > > > > > Have you tried to cleanup your perl installation and rebuild perl and > > > > > "p5-" ports? > > > > > > > > > > -- > > > > > Herbert > > > > > > > > No, I haven't done anything with perl since back in April. Indeed, all > > > > I did > > > > here was run 'synth upgrade-system'. This is a test system and has very > > > > few > > > > ports on it: > > > > > > I am not using synth. Did 'synth upgrade-system' rebuild perl? Are you > > > building texinfo also with synth? On the same host? Have you checked > > > config.log in texinfo's workdir? > > > > No, synth didn't build, or attempt to build, perl on this run. It was last > > built on April 21st. Snyth attempted to build texinfo and that's when it > > failed. > > > > Actually I have two systems that I attempted this on, one was the test > > system > > I mentioned earlier, the other is a backup file server. The building of > > texinfo failed on both. On the test system I tried deleting texinfo and the > > rebuilding/installing...no dice. Install s
Re: make install for print/texinfo fails on -CURRENT
On Tue, Jul 11, 2017 at 01:13:33PM +0200, Herbert J. Skuhra wrote: > > On 10 July 2017 at 22:59 Bob Willcox <b...@immure.com> wrote: > > > > > > On Mon, Jul 10, 2017 at 10:21:21PM +0200, Herbert J. Skuhra wrote: > > > Bob Willcox skrev: > > > > > > > > On Mon, Jul 10, 2017 at 09:49:06PM +0200, Herbert J. Skuhra wrote: > > > >> Bob Willcox skrev: > > > >> > > > > >> > The make ran w/o any errors but when I attempt to do the install I > > > >> > get > > > >> > this: > > > >> > > > > >> > root@jabba:0 /usr/ports/print/texinfo> make install > > > >> > ===> Installing for texinfo-6.4_1,1 > > > >> > ===> texinfo-6.4_1,1 depends on package: perl5>=5.24<5.25 - found > > > >> > ===> texinfo-6.4_1,1 depends on executable: indexinfo - found > > > >> > ===> Checking if texinfo already installed > > > >> > ===> Registering installation for texinfo-6.4_1,1 > > > >> > pkg-static: Unable to access file > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.a:No > > > >> > such file or directory > > > >> > pkg-static: Unable to access file > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.so:No > > > >> > such file or directory > > > >> > pkg-static: Unable to access file > > > >> > /usr/ports/print/texinfo/work/stage/usr/local/share/texinfo/Texinfo/Convert/XSParagraph/TestXS.pm:No > > > >> > such file or directory > > > >> > *** Error code 74 > > > >> > > > > >> > Stop. > > > >> > make[1]: stopped in /usr/ports/print/texinfo > > > >> > *** Error code 1 > > > >> > > > > >> > Stop. > > > >> > make: stopped in /usr/ports/print/texinfo > > > >> > > > > >> > > > > >> > Is anyone else seeing this? > > > >> > > > >> I am not, but there is already a PR: > > > >> > > > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220460 > > > > > > > > Ah, ok...thanks for pointing that out. I hadn't seen it. > > > > > > Hmm, the PR shows: > > > > > > TestXS.c: loadable library and perl binaries are mismatched (got > > > handshake key 0xdf00080, needed 0xd200080) > > > checking whether we can build Perl extension (XS) modules... no > > > > > > Do you also get this error? > > > Have you tried to cleanup your perl installation and rebuild perl and > > > "p5-" ports? > > > > > > -- > > > Herbert > > > > No, I haven't done anything with perl since back in April. Indeed, all I did > > here was run 'synth upgrade-system'. This is a test system and has very few > > ports on it: > > I am not using synth. Did 'synth upgrade-system' rebuild perl? Are you > building texinfo also with synth? On the same host? Have you checked > config.log in texinfo's workdir? No, synth didn't build, or attempt to build, perl on this run. It was last built on April 21st. Snyth attempted to build texinfo and that's when it failed. Actually I have two systems that I attempted this on, one was the test system I mentioned earlier, the other is a backup file server. The building of texinfo failed on both. On the test system I tried deleting texinfo and the rebuilding/installing...no dice. Install still failed On that system I could try deleting and rebuilding perl. Don't want to do that on my backup server, though. Bob > > -- > Herbert -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: make install for print/texinfo fails on -CURRENT
On Mon, Jul 10, 2017 at 10:21:21PM +0200, Herbert J. Skuhra wrote: > Bob Willcox skrev: > > > > On Mon, Jul 10, 2017 at 09:49:06PM +0200, Herbert J. Skuhra wrote: > >> Bob Willcox skrev: > >> > > >> > The make ran w/o any errors but when I attempt to do the install I get > >> > this: > >> > > >> > root@jabba:0 /usr/ports/print/texinfo> make install > >> > ===> Installing for texinfo-6.4_1,1 > >> > ===> texinfo-6.4_1,1 depends on package: perl5>=5.24<5.25 - found > >> > ===> texinfo-6.4_1,1 depends on executable: indexinfo - found > >> > ===> Checking if texinfo already installed > >> > ===> Registering installation for texinfo-6.4_1,1 > >> > pkg-static: Unable to access file > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.a:No > >> > such file or directory > >> > pkg-static: Unable to access file > >> > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.so:No > >> > such file or directory > >> > pkg-static: Unable to access file > >> > /usr/ports/print/texinfo/work/stage/usr/local/share/texinfo/Texinfo/Convert/XSParagraph/TestXS.pm:No > >> > such file or directory > >> > *** Error code 74 > >> > > >> > Stop. > >> > make[1]: stopped in /usr/ports/print/texinfo > >> > *** Error code 1 > >> > > >> > Stop. > >> > make: stopped in /usr/ports/print/texinfo > >> > > >> > > >> > Is anyone else seeing this? > >> > >> I am not, but there is already a PR: > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220460 > > > > Ah, ok...thanks for pointing that out. I hadn't seen it. > > Hmm, the PR shows: > > TestXS.c: loadable library and perl binaries are mismatched (got handshake > key 0xdf00080, needed 0xd200080) > checking whether we can build Perl extension (XS) modules... no > > Do you also get this error? > Have you tried to cleanup your perl installation and rebuild perl and "p5-" > ports? > > -- > Herbert No, I haven't done anything with perl since back in April. Indeed, all I did here was run 'synth upgrade-system'. This is a test system and has very few ports on it: dialog4ports-0.1.6 Console Interface to configure ports gettext-runtime-0.19.8.1_1 GNU gettext runtime libraries and programs gmake-4.2.1_1 GNU version of 'make' utility help2man-1.47.4Automatically generating simple manual pages from program output indexinfo-0.2.6Utility to regenerate the GNU info page index libffi-3.2.1 Foreign Function Interface libiconv-1.14_10 Character set conversion library pdksh-5.2.14p2_6 The Public Domain Korn Shell perl5-5.24.1_1 Practical Extraction and Report Language pkg-1.10.1 Package manager pkgconf-1.3.7,1Utility to help to configure compiler and linker flags py27-glances-2.9.1 CLI curses based monitoring tool for GNU/Linux and BSD OS py27-psutil-5.2.2 Process utilities module for Python py27-setuptools-36.0.1 Python packages installer python27-2.7.13_6 Interpreted object-oriented programming language readline-7.0.3 Library for editing command lines as they are typed rsync-3.1.2_7 Network file distribution/synchronization utility synth-1.69 Custom package repository builder for FreeBSD and DragonFly zfs-stats-1.2.2_1 Display human-readable ZFS statistics -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: make install for print/texinfo fails on -CURRENT
On Mon, Jul 10, 2017 at 09:49:06PM +0200, Herbert J. Skuhra wrote: > Bob Willcox skrev: > > > > The make ran w/o any errors but when I attempt to do the install I get > > this: > > > > root@jabba:0 /usr/ports/print/texinfo> make install > > ===> Installing for texinfo-6.4_1,1 > > ===> texinfo-6.4_1,1 depends on package: perl5>=5.24<5.25 - found > > ===> texinfo-6.4_1,1 depends on executable: indexinfo - found > > ===> Checking if texinfo already installed > > ===> Registering installation for texinfo-6.4_1,1 > > pkg-static: Unable to access file > > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.a:No such > > file or directory > > pkg-static: Unable to access file > > /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.so:No such > > file or directory > > pkg-static: Unable to access file > > /usr/ports/print/texinfo/work/stage/usr/local/share/texinfo/Texinfo/Convert/XSParagraph/TestXS.pm:No > > such file or directory > > *** Error code 74 > > > > Stop. > > make[1]: stopped in /usr/ports/print/texinfo > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/print/texinfo > > > > > > Is anyone else seeing this? > > I am not, but there is already a PR: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220460 Ah, ok...thanks for pointing that out. I hadn't seen it. Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
make install for print/texinfo fails on -CURRENT
The make ran w/o any errors but when I attempt to do the install I get this: root@jabba:0 /usr/ports/print/texinfo> make install ===> Installing for texinfo-6.4_1,1 ===> texinfo-6.4_1,1 depends on package: perl5>=5.24<5.25 - found ===> texinfo-6.4_1,1 depends on executable: indexinfo - found ===> Checking if texinfo already installed ===> Registering installation for texinfo-6.4_1,1 pkg-static: Unable to access file /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.a:No such file or directory pkg-static: Unable to access file /usr/ports/print/texinfo/work/stage/usr/local/lib/texinfo/MiscXS.so:No such file or directory pkg-static: Unable to access file /usr/ports/print/texinfo/work/stage/usr/local/share/texinfo/Texinfo/Convert/XSParagraph/TestXS.pm:No such file or directory *** Error code 74 Stop. make[1]: stopped in /usr/ports/print/texinfo *** Error code 1 Stop. make: stopped in /usr/ports/print/texinfo Is anyone else seeing this? -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg delete of firefox fails: firefox-51.0.1_1,1 is locked and may not be modified
Sorry to be following up on my own post, but right after I posted this I had a burst of inspiration (and memory recall) and remembered how to lock and unlock ports. So...nevermind...and sorry for the noise. Bob On Wed, Jun 14, 2017 at 01:30:03PM -0500, Bob Willcox wrote: > I'm trying to update firefox on my system but can't update it or even delete > it. I get this result on pkg delete (for example): > > root@tavion:1 /usr/ports/www/firefox> pkg delete firefox > > firefox-51.0.1_1,1 is locked and may not be modified > Checking integrity... done (0 conflicting) > Package(s) not found! > > Now, I suspect that I am the one responsible for 'locking' it a few months > back when I didn't want to inavertantly update it. Unfortunately I can't > recall what I might have done to lock it (memory isn't what it used to be). > > Can someone shed some light on where/what this lock may be? > > Thanks, > Bob > > -- > Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and > b...@immure.com |come out as a sausage. > Austin, TX |-- Ambrose Bierce > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pkg delete of firefox fails: firefox-51.0.1_1,1 is locked and may not be modified
I'm trying to update firefox on my system but can't update it or even delete it. I get this result on pkg delete (for example): root@tavion:1 /usr/ports/www/firefox> pkg delete firefox firefox-51.0.1_1,1 is locked and may not be modified Checking integrity... done (0 conflicting) Package(s) not found! Now, I suspect that I am the one responsible for 'locking' it a few months back when I didn't want to inavertantly update it. Unfortunately I can't recall what I might have done to lock it (memory isn't what it used to be). Can someone shed some light on where/what this lock may be? Thanks, Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unable to update repository Synth
On Sun, Jun 11, 2017 at 09:29:14AM +1200, Jonathan Chen wrote: > On 11 June 2017 at 01:13, Bob Willcox <b...@immure.com> wrote: > > On Sat, Jun 10, 2017 at 10:14:46AM +1200, Jonathan Chen wrote: > >> On 10 June 2017 at 05:02, Bob Willcox <b...@immure.com> wrote: > >> > I am running the drm-next-4.7 and when I ran synth recently on my system > >> > up update the ports and at the end of the run received these errors: > >> > > >> > pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64 > >> > pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64 > >> > Processing entries: 100% > >> > Unable to update repository Synth > >> > Error updating repositories! > >> > Unfortunately, the system upgrade failed. > >> > >> synth is complaining that one or more of the packages in the > >> configuration's package directory has packages built for > >> FreeBSD10/amd64 instead of FreeBSD12/amd64. If you have upgraded from > >> FreeBSD 10 to FreeBSD 12, you must remove all the packages that have > >> been built previously. > > > > Are these the packages that currently reside in the repository? > > Yes. > > > Is there some way to list the packages that are the problem? > > A simple way, no. You'd have to unpack each package and inspect the > manifest file to determine the package's abi. > > > If not, can I simply delete all of the respository packages? > > This is the easiest thing to do, and would be my recommendation. synth > will rebuild all the packages for your installed ports. Thanks Jonathan. That's what I'll do then... :) Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unable to update repository Synth
On Sat, Jun 10, 2017 at 10:14:46AM +1200, Jonathan Chen wrote: > On 10 June 2017 at 05:02, Bob Willcox <b...@immure.com> wrote: > > I am running the drm-next-4.7 and when I ran synth recently on my system > > up update the ports and at the end of the run received these errors: > > > > pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64 > > pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64 > > Processing entries: 100% > > Unable to update repository Synth > > Error updating repositories! > > Unfortunately, the system upgrade failed. > > synth is complaining that one or more of the packages in the > configuration's package directory has packages built for > FreeBSD10/amd64 instead of FreeBSD12/amd64. If you have upgraded from > FreeBSD 10 to FreeBSD 12, you must remove all the packages that have > been built previously. Are these the packages that currently reside in the repository? Is there some way to list the packages that are the problem? If not, can I simply delete all of the respository packages? Thanks, Bob > > Cheers. > -- > Jonathan Chen <j...@chen.org.nz> -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Unable to update repository Synth
I am running the drm-next-4.7 and when I ran synth recently on my system up update the ports and at the end of the run received these errors: pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64 pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64 Processing entries: 100% Unable to update repository Synth Error updating repositories! Unfortunately, the system upgrade failed. Can anyone help me understand what I need to do to fix this? Thanks, Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: default named.conf in bind ports and slaving from f-root
On Fri, Apr 14, 2017 at 05:25:21PM +0200, Thomas Steen Rasmussen wrote: > On 04/14/2017 04:51 PM, Mathieu Arnold wrote: > > Hi, > > > > I'm busy right now, could you open a PR so that I don't loose and forget > > this ? > > Sure thing, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218656 > > /Thomas > Thomas, I am really glad you posted this to the mailing list. This morning I woke up to a non-functioning named as it could no longer transfer data from 192.5.5.241 and my arpa/IN/internal-view expired at about midnight last night. I suppose I should have noticed the transfer failure messages in my /var/log/messages file over the past two weeks, but I didn't (or it didn't occur to me how serious they were). I was left with NO outside nameserver resolution at all. Looks like I need to find a reliable backup nameserver that I can use should something like the happen again. Anyway, luckly my mail server had already received you message to freebsd-ports describing the issue and what you did to correct it. I followed your example and got my nameserver back to the working state. Thank you!! Bob -- Bob Willcox| You're dead, Jim. b...@immure.com | -- McCoy, "The Tholian Web", stardate unknown Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Best way to cause synth to ignore rebuilding of a port??
On Sat, Mar 11, 2017 at 04:14:03AM -0800, Eitan Adler wrote: > On 8 March 2017 at 08:04, Bob Willcox <b...@immure.com> wrote: > > What is the best way to get synth to simply ignore certain ports when > > running > > the upgrade-system command with it? I would like for it to not upgrade > > firefox > > (don't want to lose my tab groups) so I'd rather that it not even consider > > updating firefox again, at least not till some form of tab groups are again > > supported. > > FYI: https://addons.mozilla.org/en-us/firefox/addon/tab-groups-panorama/ So, it seems then that firefox 57 (Nov this year) is where all non WebExtensions add-ons support end. Guess I have a few more months then. Sure seems that the Mozilla team isn't prioritizing their users very high in their furure plans. > > > -- > Eitan Adler -- Bob Willcox| If a program is useful, it will be changed. b...@immure.com | Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Best way to cause synth to ignore rebuilding of a port??
On Wed, Mar 08, 2017 at 10:21:55PM -0600, Matthew D. Fuller wrote: > On Wed, Mar 08, 2017 at 03:13:37PM -0600 I heard the voice of > Bob Willcox, and lo! it spake thus: > > > > Hmm, the plugin/addon I use and would be lost without is for tab > > groups. Do they still work in 52? > > I'm pretty sure it's 57 (or 58?) that they're getting broken. > Certainly they work fine here on the current 52 out of ports. That's good to know. If/when tab groups don't work any longer is when I stop updating firefox. They are the thing miss the most when using other browsers. > > > -- > Matthew Fuller (MF4839) | fulle...@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. -- Bob Willcox| If a program is useful, it will be changed. b...@immure.com | Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Best way to cause synth to ignore rebuilding of a port??
On Wed, Mar 08, 2017 at 12:31:51PM -0800, Kevin Oberman wrote: > On Wed, Mar 8, 2017 at 11:57 AM, Bob Willcox <b...@immure.com> wrote: > > > On Wed, Mar 08, 2017 at 10:40:11AM -0800, Freddie Cash wrote: > > > On Wed, Mar 8, 2017 at 8:04 AM, Bob Willcox <b...@immure.com> wrote: > > > > > > > What is the best way to get synth to simply ignore certain ports when > > > > running > > > > the upgrade-system command with it? I would like for it to not upgrade > > > > firefox > > > > (don't want to lose my tab groups) so I'd rather that it not even > > consider > > > > updating firefox again, at least not till some form of tab groups are > > again > > > > supported. > > > > > > > > Note that I haven't tried ver 52 of firefox, but from what I've read it > > > > sounds > > > > like all plugins/addons other than flash are no longer supported. > > > > > > > > > > ???Switch to the ESR version, and all NPAPI plugins will be enabled and > > > supported until around May of next year. :) > > > > > > Firefox 52disables everything except Flash. > > > Firefox 52ESR leaves everything enabled.??? > > > > > > ???https://bugzilla.mozilla.org/show_bug.cgi?id=1269807 > > > ??? > > > > > > -- > > > Freddie Cash > > > fjwc...@gmail.com > > > > Yeah, but isn't the ESR version relatively down-level WRT to version 51 > > that > > I'm currently using? The Makefile in www/firefox-esr has a verison of > > 45.8.0. > > > > Not anxious to go backwards on everything. > > > > -- > > Bob Willcox| If a program is useful, it will be changed. > > b...@immure.com | > > Austin, TX | > > > Color me confused. I am running Firefox 52.0 and currently have both Flash > and the Cisco H.264 plugins (according to about:plugins). So the H.264 must > not be NPAPI or there is another exception. Since the H.264 plugin is a > part of the Firefox distribution, I suspect it is a special case, a rather > important one on the same level as Flash. (Really more important.) > > Today (or, maybe yesterday) version 52.0 was declared the new ESR release, > replacing 45.8. Since I don't run ESR, I have not looked into the state of > the ESR port for FreeBSD. Hmm, the plugin/addon I use and would be lost without is for tab groups. Do they still work in 52? > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 -- Bob Willcox| If a program is useful, it will be changed. b...@immure.com | Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Best way to cause synth to ignore rebuilding of a port??
On Wed, Mar 08, 2017 at 10:40:11AM -0800, Freddie Cash wrote: > On Wed, Mar 8, 2017 at 8:04 AM, Bob Willcox <b...@immure.com> wrote: > > > What is the best way to get synth to simply ignore certain ports when > > running > > the upgrade-system command with it? I would like for it to not upgrade > > firefox > > (don't want to lose my tab groups) so I'd rather that it not even consider > > updating firefox again, at least not till some form of tab groups are again > > supported. > > > > Note that I haven't tried ver 52 of firefox, but from what I've read it > > sounds > > like all plugins/addons other than flash are no longer supported. > > > > ???Switch to the ESR version, and all NPAPI plugins will be enabled and > supported until around May of next year. :) > > Firefox 52disables everything except Flash. > Firefox 52ESR leaves everything enabled.??? > > ???https://bugzilla.mozilla.org/show_bug.cgi?id=1269807 > ??? > > -- > Freddie Cash > fjwc...@gmail.com Yeah, but isn't the ESR version relatively down-level WRT to version 51 that I'm currently using? The Makefile in www/firefox-esr has a verison of 45.8.0. Not anxious to go backwards on everything. -- Bob Willcox| If a program is useful, it will be changed. b...@immure.com | Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Best way to cause synth to ignore rebuilding of a port??
What is the best way to get synth to simply ignore certain ports when running the upgrade-system command with it? I would like for it to not upgrade firefox (don't want to lose my tab groups) so I'd rather that it not even consider updating firefox again, at least not till some form of tab groups are again supported. Note that I haven't tried ver 52 of firefox, but from what I've read it sounds like all plugins/addons other than flash are no longer supported. Thanks, Bob -- Bob Willcox| If a program is useful, it will be changed. b...@immure.com | Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/cargo build failure
On Tue, Jan 24, 2017 at 09:47:56AM -0800, David Wolfskill wrote: > On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote: > > Le 24/01/2017 à 16:52, Bob Willcox a écrit : > > > When trying to build devel/cargo I get this error: > > > > > > /xports/Mk/Scripts/checksum.sh: cannot open > > > 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or > > > directory > > > *** Error code 2 > > > > > > Stop. > > > make: stopped in /xports/devel/cargo > > > > > > Anyone have any ideas why and what I can do to overcome it? > > > > Ok, so, the port changed the directory this file is fetched in, to fix > > the problem, you'll need to remove the > > cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles > > (or whereever your distfiles are) > > > > Thanks -- that worked for me. Yep, that fixed it for me as well...thanks. -- Bob Willcox| There's nothing very mysterious about you, except that b...@immure.com | nobody really knows your origin, purpose, or destination. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/cargo build failure
When trying to build devel/cargo I get this error: /xports/Mk/Scripts/checksum.sh: cannot open 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or directory *** Error code 2 Stop. make: stopped in /xports/devel/cargo Anyone have any ideas why and what I can do to overcome it? Thanks, Bob -- Bob Willcox| There's nothing very mysterious about you, except that b...@immure.com | nobody really knows your origin, purpose, or destination. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Can synth skip/ignore specified ports?
I have a customized version of minidlna installed that I don't ever want updated (I've added support for DSD encoded audio files). Is there a way to tell synth to ignore the net/minidlna port? When I was using portupgrade I set a HOLD_PKGS entry in the /usr/local/etc/pkgtools.conf file. Is there something similar with synth (my search turned up nothing). Thanks, Bob -- Bob Willcox| Ninety percent of the politicians give the other b...@immure.com | ten percent a bad reputation. Austin, TX | -- Henry Kissinger ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
Well, I deleteted the nspluginwrapper package/port from my system and now it
appears that firefox is much happier. I can navigate cnn.com w/o any hangs or
other undesirable behavior. So, what do I need nspluginwrapper for these days.
I assume for Adobe Flash, but is there anything else I'd be missing if I don't
have it installed?
Thanks,
Bob
On Fri, Jun 10, 2016 at 07:57:35AM -0500, Bob Willcox wrote:
> On Thu, Jun 09, 2016 at 11:13:24PM +0200, Jan Beich wrote:
> > Bob Willcox <b...@immure.com> writes:
> >
> > > I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when I
> > > go
> > > out to cnn.com it hangs, eventually putting up a dialog box telling me
> > > that a
> > > script has stop working (or something similar). Nothing I've tried so far
> > > seems to help and I wind up having to kill firefox.
> >
> > Does firefox print anything on terminal or in ~/.xsession-errors ? Check
> > about:addons for possible culprits (plugins[1], extensions, user scripts).
> > Try running firefox with an empty profile. Maybe install NoScript and
> > gradually enable domains until the hang reappears.
> >
> > [1] When updating linux- plugins make sure to run
> >
> > $ nspluginwrapper -a -v -i
>
> Hi Jan,
>
> Thanks for your response. I started up firefox from an xterm window so that I
> could see/capture the console output and here's what I get:
>
> bob@luke:10 /.amd_mnt/vader/host/stor/home/bob> firefox
> 1465562740817 addons.xpi WARNError loading bootstrap.js for
> {f69e22c7-bc50-414a-9269-0f5c344cd94c}: SyntaxError: missing ; before
> statement (resource://gre/modules/addons/XPIProvider.jsm ->
> jar:file:///home/bob/.mozilla/firefox/8cf81tbu.Bob/extensions/%7Bf69e22c7-bc50-414a-9269-0f5c344cd94c%7D.xpi!/bootstrap.js:1228:61)
> JS Stack trace: @XPIProvider.jsm:4540:1 <
> this.xpiprovider.loadbootstrapsc...@xpiprovider.jsm:4540:7 <
> this.xpiprovider.callbootstrapmet...@xpiprovider.jsm:4616:9 <
> this.xpiprovider.star...@xpiprovider.jsm:2721:13 <
> callprovi...@addonmanager.jsm:227:12 < _startprovi...@addonmanager.jsm:833:5
> < addonmanagerinternal.star...@addonmanager.jsm:1016:9 <
> this.addonmanagerprivate.star...@addonmanager.jsm:2783:5 <
> ammanager.prototype.obse...@addonmanager.js:56:7
> 1465562740817 addons.xpi WARNAdd-on
> {f69e22c7-bc50-414a-9269-0f5c344cd94c} is missing bootstrap method startup
>
> (process:72294): GLib-CRITICAL **: g_path_get_basename: assertion 'file_name
> != NULL' failed
>
> *** I went to cnn.com at this point
>
>
> (npviewer.bin:72308): GLib-WARNING **: getpwuid_r(): failed due to unknown
> user id ()
>
> (npviewer.bin:72308): Gtk-WARNING **: cannot open display: luke:0.0
> *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
> connection
>
> (npviewer.bin:72327): GLib-WARNING **: getpwuid_r(): failed due to unknown
> user id ()
>
> (npviewer.bin:72327): Gtk-WARNING **: cannot open display: luke:0.0
> *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
> connection
>
> (npviewer.bin:72347): GLib-WARNING **: getpwuid_r(): failed due to unknown
> user id ()
>
> (npviewer.bin:72347): Gtk-WARNING **: cannot open display: luke:0.0
> *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
> connection
>
> (npviewer.bin:72366): GLib-WARNING **: getpwuid_r(): failed due to unknown
> user id ()
>
> (npviewer.bin:72366): Gtk-WARNING **: cannot open display: luke:0.0
> *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
> connection
>
> (npviewer.bin:72386): GLib-WARNING **: getpwuid_r(): failed due to unknown
> user id ()
>
> (npviewer.bin:72386): Gtk-WARNING **: cannot open display: luke:0.0
> *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
> connection
>
> (npviewer.bin:72406): GLib-WARNING **: getpwuid_r(): failed due to unknown
> user id ()
>
> (npviewer.bin:72406): Gtk-WARNING **: cannot open display: luke:0.0
> *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
> connection
>
> * at this point firefox put up the unresponsive script dialog box *
>
>
> As it turns out, my user ID is so the npviewer.bin warning lines appear
> to be due to something related to my ID.
>
> I'm going to try the other things you suggested next and see where that takes
> me.
>
> Thanks,
> Bob
>
>
> --
> Bob Willcox| Which is worse: igno
Re: Firefox 47.0 hangs when accessing cnn.com
On Fri, Jun 10, 2016 at 01:01:42PM -0700, Kevin Oberman wrote: > On Fri, Jun 10, 2016 at 12:36 PM, Bob Willcox <b...@immure.com> wrote: > > > On Fri, Jun 10, 2016 at 03:42:00PM +, Grzegorz Junka wrote: > > > ... > > > That sounds bad indeed. Have you tried to reinstall using the official > > > pkg repository (not compiled on your machine)? > > > > > > BTW Firefox 47 just started crashing today for me. Nothing to do with > > > scripts, some exception in one of the *.c files (according to the > > > popup). I am now creating a new batch of packages with poudriere and > > > will try to upgrade to a newer version. > > > > Ugh. Mine hasn't crashed, just hung to the point where I have to kill it. > > Jan has suggested some things for me to try that I plan to do when I get > > some time. I'll post how that went once I've tried them. > > > > Bob > > > > -- > > Bob Willcox| Which is worse: ignorance or apathy? > > b...@immure.com | Who knows? Who cares? > > Austin, TX | > > > > npviewer.bin is not part of firefox. It is a part of nspluginwrapper. If > you uninstall it and restart firefox, does the problem go away? (Of course, > you won't be able to view flash.) Have you followed Jan's suggestion to > re-setup nspluginwrapper? NOTE: It must be installed by you with the UID > you use to run firefox! Doing it as rot won't work. I haven't been able to follow Jan's suggestions yet (I'm at work currently). I had done the setup for nspluginwrapper some time ago, but not since the system update on 6/4 that sent me down this rat hole. I'll give that a try first. Thanks, Bob -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
On Fri, Jun 10, 2016 at 03:42:00PM +, Grzegorz Junka wrote: > > On 09/06/2016 19:52, Bob Willcox wrote: > > On Thu, Jun 09, 2016 at 01:21:06PM +, Grzegorz Junka wrote: > >> On 09/06/2016 13:10, William A. Mahaffey III wrote: > >>> On 06/09/16 00:10, Kevin Oberman wrote: > >>>> On Wed, Jun 8, 2016 at 4:04 PM, Bob Willcox < <kob6...@gmail.com> > >>>> b...@immure.com> wrote: > >>>> > >>>>> Ok, I finally figured out how to get portdowngrade to give me a > >>>>> 46.0.1,1 > >>>>> version of firefox and built & installed it. Unfortunately, that didn't > >>>>> solve > >>>>> my hanging firefox scripts problem so apparently it's likely to be > >>>>> caused > >>>>> by > >>>>> something else that got updated when I did the portupgrade on June > >>>>> 4th. Not > >>>>> sure where to go from here... > >>>>> > >>>>> Bob > >>>>> > >>>> No easy answers. I, also have no issues with 47.0 on my system and there > >>>> are no other reports of the problem you are having. So where to look? > >>>> > >>>> What version of FreeBSD are you running? On what platform? i386 or > >>>> amd64 or > >>>> something else. Most people are running amd64. If ir is another > >>>> platform, > >>>> issues are less likely to have been seen. Is it 10.3 or something else. > >>>> > >>>> Unless someone else has a better suggestion, I'd re-install all > >>>> dependencies. Older versions are more likely to have issues.I use > >>>> portmaster, but I know portupgrade can also do this. Or use packages. > >>>> It's > >>>> a lot faster when you don't need any options on the ports. > >>>> > >>>> Other than that, I have no good ideas other than to re-install > >>>> everything. > >>>> And that may not fix it as it is possible that it's a memory or other > >>>> hardware issue. > >>>> > >>>> I hope someone else has a better idea than I. > >>>> -- > >>>> R. Kevin Oberman, Network Engineer, Retired > >>>> E-mail: kob6...@gmail.com > >>>> ___ > >>>> freebsd-ports@freebsd.org mailing list > >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports > >>>> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > >>> > >>> +1 on packages, *much* faster & same end result if you have no special > >>> compile options > >>> > >>> > >> I second that and repeat what I said before. If you want to compile your > >> own packages with custom options then fine, but do it properly with > >> either poudriere or synth. Otherwise, just use the FreeBSD generic ones. > >> Portupgrade and portmaster are fine but only as long as they work, and > >> from my experience sooner or later they always stop working and from > >> then there is going to be a path of misery, wasted time and broken > >> applications. > > Well, I've compiled and reinstalled all of the packages on the system with > > synth with the same result. BTW, from what I could tell, synth forced me to > > remove any local configuration files that I had for the half a dozen or so > > ports prior to allowing me to to the 'synth upgrade-system' run. > > > > I don't know what is going on/wrong with firefox, but it seems to be getting > > hung up with some scripts that it tries to run. Since I replaced the version > > 47 of firefox with the previous 46 version and the problem persisted, I > > suspect that the issue may not be in firefox at all. It's just the victim. > > > > That sounds bad indeed. Have you tried to reinstall using the official > pkg repository (not compiled on your machine)? > > BTW Firefox 47 just started crashing today for me. Nothing to do with > scripts, some exception in one of the *.c files (according to the > popup). I am now creating a new batch of packages with poudriere and > will try to upgrade to a newer version. Ugh. Mine hasn't crashed, just hung to the point where I have to kill it. Jan has suggested some things for me to try that I plan to do when I get some time. I'll post how that went once I've tried them. Bob -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
On Thu, Jun 09, 2016 at 11:13:24PM +0200, Jan Beich wrote:
> Bob Willcox <b...@immure.com> writes:
>
> > I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when I go
> > out to cnn.com it hangs, eventually putting up a dialog box telling me that
> > a
> > script has stop working (or something similar). Nothing I've tried so far
> > seems to help and I wind up having to kill firefox.
>
> Does firefox print anything on terminal or in ~/.xsession-errors ? Check
> about:addons for possible culprits (plugins[1], extensions, user scripts).
> Try running firefox with an empty profile. Maybe install NoScript and
> gradually enable domains until the hang reappears.
>
> [1] When updating linux- plugins make sure to run
>
> $ nspluginwrapper -a -v -i
Hi Jan,
Thanks for your response. I started up firefox from an xterm window so that I
could see/capture the console output and here's what I get:
bob@luke:10 /.amd_mnt/vader/host/stor/home/bob> firefox
1465562740817 addons.xpi WARNError loading bootstrap.js for
{f69e22c7-bc50-414a-9269-0f5c344cd94c}: SyntaxError: missing ; before statement
(resource://gre/modules/addons/XPIProvider.jsm ->
jar:file:///home/bob/.mozilla/firefox/8cf81tbu.Bob/extensions/%7Bf69e22c7-bc50-414a-9269-0f5c344cd94c%7D.xpi!/bootstrap.js:1228:61)
JS Stack trace: @XPIProvider.jsm:4540:1 <
this.xpiprovider.loadbootstrapsc...@xpiprovider.jsm:4540:7 <
this.xpiprovider.callbootstrapmet...@xpiprovider.jsm:4616:9 <
this.xpiprovider.star...@xpiprovider.jsm:2721:13 <
callprovi...@addonmanager.jsm:227:12 < _startprovi...@addonmanager.jsm:833:5 <
addonmanagerinternal.star...@addonmanager.jsm:1016:9 <
this.addonmanagerprivate.star...@addonmanager.jsm:2783:5 <
ammanager.prototype.obse...@addonmanager.js:56:7
1465562740817 addons.xpi WARNAdd-on
{f69e22c7-bc50-414a-9269-0f5c344cd94c} is missing bootstrap method startup
(process:72294): GLib-CRITICAL **: g_path_get_basename: assertion 'file_name !=
NULL' failed
*** I went to cnn.com at this point
(npviewer.bin:72308): GLib-WARNING **: getpwuid_r(): failed due to unknown user
id ()
(npviewer.bin:72308): Gtk-WARNING **: cannot open display: luke:0.0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
(npviewer.bin:72327): GLib-WARNING **: getpwuid_r(): failed due to unknown user
id ()
(npviewer.bin:72327): Gtk-WARNING **: cannot open display: luke:0.0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
(npviewer.bin:72347): GLib-WARNING **: getpwuid_r(): failed due to unknown user
id ()
(npviewer.bin:72347): Gtk-WARNING **: cannot open display: luke:0.0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
(npviewer.bin:72366): GLib-WARNING **: getpwuid_r(): failed due to unknown user
id ()
(npviewer.bin:72366): Gtk-WARNING **: cannot open display: luke:0.0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
(npviewer.bin:72386): GLib-WARNING **: getpwuid_r(): failed due to unknown user
id ()
(npviewer.bin:72386): Gtk-WARNING **: cannot open display: luke:0.0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
(npviewer.bin:72406): GLib-WARNING **: getpwuid_r(): failed due to unknown user
id ()
(npviewer.bin:72406): Gtk-WARNING **: cannot open display: luke:0.0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
* at this point firefox put up the unresponsive script dialog box *
As it turns out, my user ID is so the npviewer.bin warning lines appear
to be due to something related to my ID.
I'm going to try the other things you suggested next and see where that takes
me.
Thanks,
Bob
--
Bob Willcox| Which is worse: ignorance or apathy?
b...@immure.com | Who knows? Who cares?
Austin, TX |
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
On Thu, Jun 09, 2016 at 01:21:06PM +, Grzegorz Junka wrote: > > On 09/06/2016 13:10, William A. Mahaffey III wrote: > > On 06/09/16 00:10, Kevin Oberman wrote: > >> On Wed, Jun 8, 2016 at 4:04 PM, Bob Willcox < <kob6...@gmail.com> > >> b...@immure.com> wrote: > >> > >>> Ok, I finally figured out how to get portdowngrade to give me a > >>> 46.0.1,1 > >>> version of firefox and built & installed it. Unfortunately, that didn't > >>> solve > >>> my hanging firefox scripts problem so apparently it's likely to be > >>> caused > >>> by > >>> something else that got updated when I did the portupgrade on June > >>> 4th. Not > >>> sure where to go from here... > >>> > >>> Bob > >>> > >> No easy answers. I, also have no issues with 47.0 on my system and there > >> are no other reports of the problem you are having. So where to look? > >> > >> What version of FreeBSD are you running? On what platform? i386 or > >> amd64 or > >> something else. Most people are running amd64. If ir is another > >> platform, > >> issues are less likely to have been seen. Is it 10.3 or something else. > >> > >> Unless someone else has a better suggestion, I'd re-install all > >> dependencies. Older versions are more likely to have issues.I use > >> portmaster, but I know portupgrade can also do this. Or use packages. > >> It's > >> a lot faster when you don't need any options on the ports. > >> > >> Other than that, I have no good ideas other than to re-install > >> everything. > >> And that may not fix it as it is possible that it's a memory or other > >> hardware issue. > >> > >> I hope someone else has a better idea than I. > >> -- > >> R. Kevin Oberman, Network Engineer, Retired > >> E-mail: kob6...@gmail.com > >> ___ > >> freebsd-ports@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports > >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > > > > +1 on packages, *much* faster & same end result if you have no special > > compile options > > > > > > I second that and repeat what I said before. If you want to compile your > own packages with custom options then fine, but do it properly with > either poudriere or synth. Otherwise, just use the FreeBSD generic ones. > Portupgrade and portmaster are fine but only as long as they work, and > from my experience sooner or later they always stop working and from > then there is going to be a path of misery, wasted time and broken > applications. Well, I've compiled and reinstalled all of the packages on the system with synth with the same result. BTW, from what I could tell, synth forced me to remove any local configuration files that I had for the half a dozen or so ports prior to allowing me to to the 'synth upgrade-system' run. I don't know what is going on/wrong with firefox, but it seems to be getting hung up with some scripts that it tries to run. Since I replaced the version 47 of firefox with the previous 46 version and the problem persisted, I suspect that the issue may not be in firefox at all. It's just the victim. > > Grzegorz > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
On Wed, Jun 08, 2016 at 10:04:40PM -0700, Kevin Oberman wrote: > On Wed, Jun 8, 2016 at 4:04 PM, Bob Willcox < <kob6...@gmail.com> > b...@immure.com> wrote: > > > Ok, I finally figured out how to get portdowngrade to give me a 46.0.1,1 > > version of firefox and built & installed it. Unfortunately, that didn't > > solve > > my hanging firefox scripts problem so apparently it's likely to be caused > > by > > something else that got updated when I did the portupgrade on June 4th. Not > > sure where to go from here... > > > > Bob > > > > No easy answers. I, also have no issues with 47.0 on my system and there > are no other reports of the problem you are having. So where to look? > > What version of FreeBSD are you running? On what platform? i386 or amd64 or > something else. Most people are running amd64. If ir is another platform, > issues are less likely to have been seen. Is it 10.3 or something else. > > Unless someone else has a better suggestion, I'd re-install all > dependencies. Older versions are more likely to have issues.I use > portmaster, but I know portupgrade can also do this. Or use packages. It's > a lot faster when you don't need any options on the ports. > > Other than that, I have no good ideas other than to re-install everything. > And that may not fix it as it is possible that it's a memory or other > hardware issue. > > I hope someone else has a better idea than I. I'm running: FreeBSD luke.immure.com 10.3-STABLE FreeBSD 10.3-STABLE #24 r301442: Sun Jun 5 08:47:09 CDT 2016 b...@luke.immure.com:/usr/obj/usr/src/sys/LUKE amd64 This is on a system with an i7-5820K processor, 32GB of memory and a 256GB M.2 SSD as the system drive. As as rule, it runs quite fast (does a make buildworld in about 11 minutes), Also, chrome seems to run fine. It's that firefox stalls/hangs, esp noticable when try ing to go to ccn.com. Other sites will trigger it as well (once it starts it doesn't seem to ever clear up) but it happens quickest with cnn.com for some reason. I ran 'synth upgrade-system' on the system the other day as a test/experiment. It rebuild and reinstalled all 1040 ports/packages on the system, but alas, that didn't help. I'm pretty much at a loss at this point about what to do next. I've been considering removing all of the ports and then reinstalling them from scratch. -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
Ok, I finally figured out how to get portdowngrade to give me a 46.0.1,1 version of firefox and built & installed it. Unfortunately, that didn't solve my hanging firefox scripts problem so apparently it's likely to be caused by something else that got updated when I did the portupgrade on June 4th. Not sure where to go from here... Bob On Wed, Jun 08, 2016 at 08:07:41AM -0500, Bob Willcox wrote: > Hi Kevin, > > Thanks for your reply. I've tried about all of the combinations of arguments > to portdowngrade that I can think of without success. Worse, what it spews out > isn't helping me to figure out what I'm doing wrong. Here is an example of one > of the things I tried and its response: > > root@luke:3 /usr/ports> portdowngrade firefox 46.0.1 > firefox-47.0,1 -> www/firefox > firefox-esr-45.2.0,1-> www/firefox-esr > firefox-esr-i18n-45.2.0 -> www/firefox-esr-i18n > firefox-i18n-47.0 -> www/firefox-i18n > linux-firefox-45.2.0,2 -> www/linux-firefox > xpi-firefox-showcase-0.9.5.6-> www/xpi-firefox-showcase > > Choose a port origin (directory) from the list > above, and then run portdowngrade category/port > > Can you (or someone) enlighten me on what it is trying to tell me?? > > Thanks, > Bob > > On Tue, Jun 07, 2016 at 08:18:52PM -0700, Kevin Oberman wrote: > > You should be able to use ports-mgmt/portdowngrade. This assumes that you > > still have the distribution file, as I suspect that it's no longer > > available for download from Mozilla. Check, though. > > On Jun 7, 2016 5:07 PM, "Bob Willcox" <b...@immure.com> wrote: > > > > > On Mon, Jun 06, 2016 at 03:16:01PM -0400, Naram Qashat wrote: > > > > I'm of the opinion that the Firefox port was updated to 47 very > > > > prematurely. Even though the SVN commit note says it was a release > > > > candidate, I don't usually look at commit notes when I've updated my > > > > ports tree and ran into some weird issues with 47 that made me downgrade > > > > back to 46.0.1. 47's official release isn't until tomorrow. > > > > > > What do I need to do to downgrade back to 46.0.1 (that worked fine for > > > me)? > > > > > > Thanks, > > > Bob > > > > > > -- > > > Bob Willcox| Which is worse: ignorance or apathy? > > > b...@immure.com | Who knows? Who cares? > > > Austin, TX | > > > ___ > > > freebsd-ports@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > > > -- > Bob Willcox| Which is worse: ignorance or apathy? > b...@immure.com | Who knows? Who cares? > Austin, TX | > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
Hi Kevin, Thanks for your reply. I've tried about all of the combinations of arguments to portdowngrade that I can think of without success. Worse, what it spews out isn't helping me to figure out what I'm doing wrong. Here is an example of one of the things I tried and its response: root@luke:3 /usr/ports> portdowngrade firefox 46.0.1 firefox-47.0,1 -> www/firefox firefox-esr-45.2.0,1-> www/firefox-esr firefox-esr-i18n-45.2.0 -> www/firefox-esr-i18n firefox-i18n-47.0 -> www/firefox-i18n linux-firefox-45.2.0,2 -> www/linux-firefox xpi-firefox-showcase-0.9.5.6-> www/xpi-firefox-showcase Choose a port origin (directory) from the list above, and then run portdowngrade category/port Can you (or someone) enlighten me on what it is trying to tell me?? Thanks, Bob On Tue, Jun 07, 2016 at 08:18:52PM -0700, Kevin Oberman wrote: > You should be able to use ports-mgmt/portdowngrade. This assumes that you > still have the distribution file, as I suspect that it's no longer > available for download from Mozilla. Check, though. > On Jun 7, 2016 5:07 PM, "Bob Willcox" <b...@immure.com> wrote: > > > On Mon, Jun 06, 2016 at 03:16:01PM -0400, Naram Qashat wrote: > > > I'm of the opinion that the Firefox port was updated to 47 very > > > prematurely. Even though the SVN commit note says it was a release > > > candidate, I don't usually look at commit notes when I've updated my > > > ports tree and ran into some weird issues with 47 that made me downgrade > > > back to 46.0.1. 47's official release isn't until tomorrow. > > > > What do I need to do to downgrade back to 46.0.1 (that worked fine for me)? > > > > Thanks, > > Bob > > > > -- > > Bob Willcox| Which is worse: ignorance or apathy? > > b...@immure.com | Who knows? Who cares? > > Austin, TX | > > ___ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
On Mon, Jun 06, 2016 at 03:16:01PM -0400, Naram Qashat wrote: > I'm of the opinion that the Firefox port was updated to 47 very > prematurely. Even though the SVN commit note says it was a release > candidate, I don't usually look at commit notes when I've updated my > ports tree and ran into some weird issues with 47 that made me downgrade > back to 46.0.1. 47's official release isn't until tomorrow. What do I need to do to downgrade back to 46.0.1 (that worked fine for me)? Thanks, Bob -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
On Tue, Jun 07, 2016 at 08:04:23AM -0453, William A. Mahaffey III wrote: > > FWIW, I just checked available pkg's using 'pkg version -vRL=' & nothing > showed up for firefox: You might be a bit closer to the *bleeding* edge > than you think w/ the ports version. I'm using firefox-46.0.1,1 from > pkg's w/ no issues. $0.02, no more, no less. I fear that you may be right about me being close to the bleeding edge with firefox. It certainly wasn't my goal. I simply ran 'portupgrade -a' and there I was (once it completed). Before updating to version 47 my version 46 seemed to be ok (would crash once in a while, but at least it worked fine most of the time). -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
Thanks for the reply Grzegroz. I've since discovered that I still do get the dialog box about the stopped script popping up sometimes (even when I don't go to cnn.com, though that seems to exacerbate it). Just for completeness, here's the text of the recent popup: = A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: http://ajax.cloudflare.com/cdn#loudflare.min.js line 4 > eval:2 = I really need to revert back to 46 somehow. The new version (47) just isn't usable in my environment. I've been performing a ports build/install, I'm thinking I will try simply doing a 'pkg install' next. Bob On Tue, Jun 07, 2016 at 12:57:15PM +, Grzegorz Junka wrote: > Hi Bob, > > I don't believe it's possible to revert ports to a previous version > (other than through SVN). However, if you have the older version of the > firefox package (e.g. > /usr/local/poudriere/data/packages/your-system/All) you should be able > to just point pkg to it. > > But before doing that I would suggest to reset your Firefox settings > just in case this problem is caused by an extension or other improper > configuration (e.g. by renaming the .mozilla/firefox folder or using the > FF setting that I don't remember now). You could also try to open > cnn.com in a private window where the plugins are disabled by default. > > Grzegorz > > > On 07/06/2016 12:48, Bob Willcox wrote: > > Hi Grzegorz, > > > > I altered my configuration to match what you list below and > > rebuilt/installed > > firefox. I no longer get the dialog box about the script not working but > > cnn.com still doesn't load as expected. It now will eventually complete but > > it > > takes several minutes (I didn't precisely time it, but it's about 4 or 5 > > minutes) during which time firefox doesn't respond to any input at all. It > > does seem to eventually complete transferring data and updating but then > > firefox becomes very slow and unresponsive. > > > > So, what is the best way to revert back to version 46? I really can't use > > 47 with the way it is behaving now. > > > > Thanks, > > Bob > > > > On Mon, Jun 06, 2016 at 07:03:49PM +, Grzegorz Junka wrote: > >> I have upgrade to Firefox 47.0_1,1 earlier today and just tried cnn.com > >> - works without issues. I have compiled with poudriere using options: > >> > >> # This file is auto-generated by 'make config'. > >> # Options for firefox-45.0.1_3,1 > >> _OPTIONS_READ=firefox-45.0.1_3,1 > >> _FILE_COMPLETE_OPTIONS_LIST=BUNDLED_CAIRO CANBERRA DBUS DEBUG DTRACE > >> FFMPEG GCONF GIO GNOMEUI INTEGER_SAMPLES LIBPROXY OPTIMIZED_CFLAGS PGO > >> PROFILE RUST TEST GTK2 GTK3 ALSA PULSEAUDIO > >> OPTIONS_FILE_UNSET+=BUNDLED_CAIRO > >> OPTIONS_FILE_UNSET+=CANBERRA > >> OPTIONS_FILE_SET+=DBUS > >> OPTIONS_FILE_UNSET+=DEBUG > >> OPTIONS_FILE_UNSET+=DTRACE > >> OPTIONS_FILE_SET+=FFMPEG > >> OPTIONS_FILE_UNSET+=GCONF > >> OPTIONS_FILE_SET+=GIO > >> OPTIONS_FILE_UNSET+=GNOMEUI > >> OPTIONS_FILE_UNSET+=INTEGER_SAMPLES > >> OPTIONS_FILE_SET+=LIBPROXY > >> OPTIONS_FILE_SET+=OPTIMIZED_CFLAGS > >> OPTIONS_FILE_UNSET+=PGO > >> OPTIONS_FILE_UNSET+=PROFILE > >> OPTIONS_FILE_SET+=RUST > >> OPTIONS_FILE_UNSET+=TEST > >> OPTIONS_FILE_UNSET+=GTK2 > >> OPTIONS_FILE_SET+=GTK3 > >> OPTIONS_FILE_SET+=ALSA > >> OPTIONS_FILE_UNSET+=PULSEAUDIO > >> > >> Not sure why the file contains 45.0.1_3,1, probably because it hasn't > >> changed since then: > >> > >> g@crayon2:~ % pkg info | grep firefox > >> firefox-47.0_1,1 Web browser based on the browser portion > >> of Mozilla > >> > >> Grzegorz > >> > >> > >> On 06/06/2016 18:21, Bob Willcox wrote: > >>> I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when I > >>> go > >>> out to cnn.com it hangs, eventually putting up a dialog box telling me > >>> that a > >>> script has stop working (or something similar). Nothing I've tried so far > >>> seems to help and I wind up having to kill firefox. > >>> > >>> Anyone else experiencing this? Not that other sites (besides cnn.com) have > >>> hung on me as well, but cnn.com seems to be the worst (fails the quickest, > >>> within seconds of going there). > >>> > >> ___ > >> freebsd-ports@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports > >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 47.0 hangs when accessing cnn.com
Hi Grzegorz, I altered my configuration to match what you list below and rebuilt/installed firefox. I no longer get the dialog box about the script not working but cnn.com still doesn't load as expected. It now will eventually complete but it takes several minutes (I didn't precisely time it, but it's about 4 or 5 minutes) during which time firefox doesn't respond to any input at all. It does seem to eventually complete transferring data and updating but then firefox becomes very slow and unresponsive. So, what is the best way to revert back to version 46? I really can't use 47 with the way it is behaving now. Thanks, Bob On Mon, Jun 06, 2016 at 07:03:49PM +, Grzegorz Junka wrote: > I have upgrade to Firefox 47.0_1,1 earlier today and just tried cnn.com > - works without issues. I have compiled with poudriere using options: > > # This file is auto-generated by 'make config'. > # Options for firefox-45.0.1_3,1 > _OPTIONS_READ=firefox-45.0.1_3,1 > _FILE_COMPLETE_OPTIONS_LIST=BUNDLED_CAIRO CANBERRA DBUS DEBUG DTRACE > FFMPEG GCONF GIO GNOMEUI INTEGER_SAMPLES LIBPROXY OPTIMIZED_CFLAGS PGO > PROFILE RUST TEST GTK2 GTK3 ALSA PULSEAUDIO > OPTIONS_FILE_UNSET+=BUNDLED_CAIRO > OPTIONS_FILE_UNSET+=CANBERRA > OPTIONS_FILE_SET+=DBUS > OPTIONS_FILE_UNSET+=DEBUG > OPTIONS_FILE_UNSET+=DTRACE > OPTIONS_FILE_SET+=FFMPEG > OPTIONS_FILE_UNSET+=GCONF > OPTIONS_FILE_SET+=GIO > OPTIONS_FILE_UNSET+=GNOMEUI > OPTIONS_FILE_UNSET+=INTEGER_SAMPLES > OPTIONS_FILE_SET+=LIBPROXY > OPTIONS_FILE_SET+=OPTIMIZED_CFLAGS > OPTIONS_FILE_UNSET+=PGO > OPTIONS_FILE_UNSET+=PROFILE > OPTIONS_FILE_SET+=RUST > OPTIONS_FILE_UNSET+=TEST > OPTIONS_FILE_UNSET+=GTK2 > OPTIONS_FILE_SET+=GTK3 > OPTIONS_FILE_SET+=ALSA > OPTIONS_FILE_UNSET+=PULSEAUDIO > > Not sure why the file contains 45.0.1_3,1, probably because it hasn't > changed since then: > > g@crayon2:~ % pkg info | grep firefox > firefox-47.0_1,1 Web browser based on the browser portion > of Mozilla > > Grzegorz > > > On 06/06/2016 18:21, Bob Willcox wrote: > > I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when I go > > out to cnn.com it hangs, eventually putting up a dialog box telling me that > > a > > script has stop working (or something similar). Nothing I've tried so far > > seems to help and I wind up having to kill firefox. > > > > Anyone else experiencing this? Not that other sites (besides cnn.com) have > > hung on me as well, but cnn.com seems to be the worst (fails the quickest, > > within seconds of going there). > > > > _______ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Firefox 47.0 hangs when accessing cnn.com
I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when I go out to cnn.com it hangs, eventually putting up a dialog box telling me that a script has stop working (or something similar). Nothing I've tried so far seems to help and I wind up having to kill firefox. Anyone else experiencing this? Not that other sites (besides cnn.com) have hung on me as well, but cnn.com seems to be the worst (fails the quickest, within seconds of going there). -- Bob Willcox| Which is worse: ignorance or apathy? b...@immure.com | Who knows? Who cares? Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
I fixed devel/tkmerge master site
Somehow, a symlink had gotten lost on my site that caused tkmerge to be unfetchable. I have since fixed this, so could some kind soul remove the BROKEN attribute from its Makefile? Thanks, Bob -- Bob Willcox| A bird in hand is safer than one overhead. b...@immure.com | Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: multimedia/x264 build failure
On Sat, Feb 07, 2015 at 02:42:44PM +0800, Ben Woods wrote: This issue was discussed in November here: https://lists.freebsd.org/pipermail/freebsd-ports/2014-November/096717.html The result was an entry being added to UPDATING, which can be found here: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=2729771+0+/usr/local/www/db/text/2014/svn-ports-all/20141130.svn-ports-all With the recent split of multimedia/x264 in library and binary and library components, if an application that uses libx264 is updated before x264 itself, multimedia/libx264 will conflict with the existing x264 package. Delete this package before continuing any update that depends on it: # pkg delete -f x264 Install the updated x264 and/or upgrade the other applications that depend on libx264, such as ffmpeg. Thanks Ben for your response. So, I went ahead and deleted x264 and then ran 'portupgrade -a' to upgrade the dependent packages (ffmpeg minidlna in my case, I believe). Is that all I need to do? Note that the x264 package did not reinstall. Is this because I no longer need it? Thanks, Bob -- Bob Willcox| You climb to reach the summit, but once b...@immure.com | there, discover that all roads lead down. Austin, TX | -- Stanislaw Lem, The Cyberiad ___ 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
multimedia/x264 build failure
I'm getting the following error when trying to build x264: cc -o x264 x264.o input/input.o input/timecode.o input/raw.o input/y4m.o output/raw.o output/matroska.o output/matroska_ebml.o output/flv.o output/flv_bytestream.o filters/filters.o filters/video/video.o filters/video/source.o filters/video/internal.o filters/video/resize.o filters/video/cache.o filters/video/fix_vfr_pts.o filters/video/select_every.o filters/video/crop.o filters/video/depth.o input/thread.o output/mp4.o -lgpac -lz -L/usr/local/lib -lx264 -m64 -fstack-protector -L/usr/local/lib -lm -pthread x264.o: In function `main': x264.c:(.text+0x1aea): undefined reference to `x264_encoder_open_142' cc: error: linker command failed with exit code 1 (use -v to see invocation) Makefile:177: recipe for target 'x264' failed gmake[1]: *** [x264] Error 1 gmake[1]: Leaving directory '/usr/ports/multimedia/x264/work/x264-snapshot-20140827-2245-stable' === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/multimedia/x264 Also, I get these warnings on every compilation: cc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -fomit-frame-pointer -fno-tree-vectorize -c -o output/mp4.o output/mp4.c warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option] warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option] But they don't seem to be failing the build (it's the link error shown above). I'm currently at revision 378554 (just updated minutes ago). System info: FreeBSD vader.immure.com 10.1-STABLE FreeBSD 10.1-STABLE #0 r276511: Thu Jan 1 16:19:21 CST 2015 b...@vader.immure.com:/usr/obj/usr/src/sys/GENERIC amd64 Bob -- Bob Willcox| You climb to reach the summit, but once b...@immure.com | there, discover that all roads lead down. Austin, TX | -- Stanislaw Lem, The Cyberiad ___ 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: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote: Can anyone tell me where PORTS_MODULES is documented? I don't find it in the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I thing) wrote it. This is a very beneficial tool. It really needs to be well documented. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com I found it in the make.conf(5) man page. I will say, however, that the description is fairly skimpy and I wouldn't have really known how to use it to solve my nvidia driver problem w/o the help of folks here. A more complete description, preferably with a few examples, would really help to understand how it is actually used. Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ 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: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote: On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: Hi, The nvidia-driver package needs to be recompiled with the latest FreeBSD-current sources, because of changes in the callout subsystem. If this is not possible, we can temporarily add the _callout_stop_safe symbol to the kernel for some transition time. ... While I'm running i386 (vs. amd64), I have not encountered the cited issue. Given the above, I suspect that the fact that I have the line: PORTS_MODULES=x11/nvidia-driver in /etc/src.conf has a fair amount of (positive) influence on that. (I track stable/10 head -- on different slices -- daily on my laptop.) Peace, david Thanks ALL! Adding the PORTS_MODULES=x11/nvidia-driver line to my /etc/src.conf file and rebuilding the kernel fixed it! Learn something new every day! :) Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
CURRENT breaks loading of nvidia.so
Yesterday when I upgraded my current box I encountered this failure when attempting to load the nvidia-driver (nvidia.so): link_elf_obj: symbol _callout_stop_safe undefined linker_load_file: Unsupported file type So, today I updtated my system again today hoping it might be fixed but the problem persists. System info: FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN amd64 Thanks, Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ 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
How do I recover from misc/gnomehier removal??
With the removal/deletion of the misc/gnomehier from ports a bunch of my ports now won't update (via portupgrade). How do I recover from this without removing and reinstalling the 41 ports that I have installed that were dependent on it? Thanks for any suggestions/guidance, Bob -- Bob Willcox| XML is a giant step in no direction at all. b...@immure.com | -- Erik Naggum Austin, TX | ___ 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: emulators/linux_base-c6 and x11/nvidia-driver conflict
On Fri, Mar 07, 2014 at 01:45:38PM +, Alexey Dokuchaev wrote: On Fri, Mar 07, 2014 at 01:58:49PM +0100, Ren? Ladan wrote: I noticed that linux_base-c6 and nvidia-driver conflict when one selects the LINUX option in nvidia-driver (default on). The culprit is /compat/linux/usr/lib/libGL.so.1, which is a symbolic link to libGL.so.331.49 (nvidia-driver) and libGL.so.1.2.0 (linux_base-c6). nvidia-driver does indeed have a problem with conflicting libraries (not to mendion new recently added ones: EGL|eglcore|GLESv|glsi that even do not have properly registered CONFLICTS. It's on my list, but quite frankly I've not made my mind yet how to resolve them in the least obstructive way. :( Any estimate or idea of when this may be fixed? For now I've turned off Linux compatibility support in the nvidia-driver, but I don't know what that disables and would rather not have to do that. Bob -- Bob Willcox| He who foresees calamities suffers them twice over. b...@immure.com | Austin, TX | ___ 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
a2ps: unknown medium `libpaper'
So, what does this message mean (I get no output): a2ps: unknown medium `libpaper' and how to I fix it? Thanks, Bob -- Bob Willcox| Nothing is more admirable than the fortitude with which b...@immure.com | millionaires tolerate the disadvantages of their wealth. Austin, TX | -- Nero Wolfe ___ 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: a2ps: unknown medium `libpaper'
On Tue, Sep 23, 2014 at 10:35:59AM -0500, Larry Rosenman wrote: On 2014-09-23 10:08, Bob Willcox wrote: So, what does this message mean (I get no output): a2ps: unknown medium `libpaper' and how to I fix it? Thanks, Bob print/libpaper is the port for it. Thanks for your reply. However, I do have that port installed (just reinstalled it to be certain) but I get the same result. Is there something more besides installing print/libpaper I need to do to enable it? Bob -- Bob Willcox| Nothing is more admirable than the fortitude with which b...@immure.com | millionaires tolerate the disadvantages of their wealth. Austin, TX | -- Nero Wolfe ___ 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: a2ps: unknown medium `libpaper'
On Tue, Sep 23, 2014 at 10:35:59AM -0500, Larry Rosenman wrote: On 2014-09-23 10:08, Bob Willcox wrote: So, what does this message mean (I get no output): a2ps: unknown medium `libpaper' and how to I fix it? Thanks, Bob print/libpaper is the port for it. I think I figured it out. I needed to link /usr/local/etc/papersize.letter to /etc/local/etc/papersize. Wasn't obvious from the a2ps manpage or the error message produced though. Thanks for putting me on the right track!! Bob -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 -- Bob Willcox| Nothing is more admirable than the fortitude with which b...@immure.com | millionaires tolerate the disadvantages of their wealth. Austin, TX | -- Nero Wolfe ___ 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
minidlna: file descriptor 3794 too big for select
I just installed minidlna 1.1.3 on my system from ports and ran into the problem described in Stefan Essers' bug report 185155. Checking the source and the patch file extra-patch-kqueue I see that Stefan's suggested workaround has been included. However, the file upnpevents.c didn't 'know' about the increased FD_SETSIZE value so it failed with the following fatal error: upnpevents.c:423: fatal: upnpevents_selectfds: file descriptor 3794 too big for select, limit is 1024 So...I added a #define for FD_SETSIZE to the top of that file and things seem to be working ok now. Here's my simple patch: --- upnpevents.c.orig 2014-06-05 17:14:30.0 -0500 +++ upnpevents.c2014-06-23 07:47:53.0 -0500 @@ -47,6 +47,7 @@ */ #include config.h +#define FD_SETSIZE 8192 #include stdio.h #include string.h #include errno.h -- Bob Willcox| I really hate this damned machine b...@immure.com | I wish that they would sell it. Austin, TX | It never does quite what I want | But only what I tell it. ___ 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
minidlna: kevent polling failure: Interrupted system call
I periodically get these warning messages in my minidlna.log file when running clients from the server: inotify.c:857: warn: kevent polling failure: Interrupted system call Should I be concerned? This is minidlna 1.1.3 from ports. -- Bob Willcox| I really hate this damned machine b...@immure.com | I wish that they would sell it. Austin, TX | It never does quite what I want | But only what I tell it. ___ 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: minidlna: kevent polling failure: Interrupted system call
On Mon, Jun 23, 2014 at 10:38:27AM -0300, William Grzybowski wrote: On Mon, Jun 23, 2014 at 10:28 AM, Bob Willcox b...@immure.com wrote: I periodically get these warning messages in my minidlna.log file when running clients from the server: inotify.c:857: warn: kevent polling failure: Interrupted system call Should I be concerned? This is minidlna 1.1.3 from ports. Its a bug in kqueue patch, you can disable it if you're experiencing problems. So far it doesn't appear to hurt anything. Seems to occur at the end of a track when starting a new one. -- Bob Willcox| I really hate this damned machine b...@immure.com | I wish that they would sell it. Austin, TX | It never does quite what I want | But only what I tell it. ___ 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
x11/xcb program unusable after upgrading to latest ports
I have a problem with xcb since updating my ports. The program starts up ok but the frame where the data in the cut buffer is displayed is so tiny that any data placed into the cutbuffer can't be read. Is anyone else seeing this behavior? Note that I am now seeing this on both my 9.2-stable and 10.0-stable systems. Thanks, Bob -- Bob Willcox| TRUST ME: b...@immure.com | Translation of the Latin caveat emptor. Austin, TX | ___ 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
pdksh put path to man page in /etc/shells
When portupgrade updated the shells/pdksh port on my system today it stored the path to its man page in the /etc/shells file rather than the path to the executable file, thus causing mail and login to fail for accounts that use /usr/local/bin/ksh as their login shell. Bob -- Bob Willcox| (1) If it's green or it wiggles, it's biology. b...@immure.com | (2) If it stinks, it's chemistry. Austin, TX | (3) If it doesn't work, it's physics. ___ 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
xcb window size unusably small
The size of the xcb program's frame for displaying the 'cut' data has shrunk down to such a small size that I can no longer read what's in it. The overall window created by xcb is the right size but the frame within it that displays the data in the buffer is tiny. This began sometime in the past few months when I updated all of my ports to the then latest level. I have another system that I've not updated the ports on recently (last July was the last time) that doesn't have this problem. This is on both a 9.2-stable system: FreeBSD boba.immure.com 9.2-STABLE FreeBSD 9.2-STABLE #20 r260004: Sat Dec 28 12:28:04 CST 2013 b...@luke.immure.com:/usr/obj/usr/src/sys/LUKE amd64 and a 10.0-RC5 system: FreeBSD luke.immure.com 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #2 r260872: Sun Jan 19 12:07:47 CST 2014 b...@boba.immure.com:/usr/obj/usr/src/sys/BOBA amd64 Note that the system that xcb is still ok on is also a 9.2-stable system: FreeBSD tavion.austin.ibm.com 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #10 r255473: Wed Sep 11 11:36:43 CDT 2013 b...@tavion.austin.ibm.com:/usr/obj/usr/src/sys/TAVION amd64 I don't know if this is related or not, but one of the differences between the working system and those that aren't is that the failing xcb systems have had libxcb updated from 1.9.1 to 1.9.3. Is anyone else seeing this? Any tips/ideas on where I should look? Thanks, Bob -- Bob Willcox| Philosophy, n.: b...@immure.com | Unintelligible answers to insoluble problems. Austin, TX | ___ 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: Adopt shells/pdksh?
Any progress being made on the pdksh hang problem in 10.0? On Tue, Sep 03, 2013 at 01:08:22PM +, Steven Kreuzer wrote: On Fri, Aug 30, 2013 at 06:08:05PM +0200, Rodrigo OSORIO wrote: hi, If nobody is interested by your port, I'll take it. May I ask you to update the port owner to rodr...@bebik.net for me :) Thanks Rodrigo. I updated the MAINTAINER to be you. If you figure out what is going on in ports/181438 please shoot me a patch and I will commit it Thanks regards -rodrigo On 30/08/13 10:12 -0400, Steven Kreuzer wrote: Any pdksh users out there that would like to take over as maintainer of the port? I am no longer using ksh and it doesn't play well on FreeBSD-10 (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/181438) I marked the port as broken and I doubt I am going to have any time to attempt to resolve the issue. If you are interested, let me know ___ 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 -- Bob Willcox| Philosophy, n.: b...@immure.com | Unintelligible answers to insoluble problems. Austin, TX | ___ 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
Transcode support for minidlna (aka ReadyMedia)?
Is there any support for transcoding audio files (from flac to either wav or mp3 is what I need)? I've seen a few references to work being done for this but it appears to be focused on Linux and I haven't found any reference to FreeBSD related to this work. For example here's one promising looking site that makes on mention of FreeBSD: https://bitbucket.org/stativ/readymedia-transcode -- Bob Willcox| If project content is allowed to change freely, the rate b...@immure.com | of change will exceed the rate of progress. Austin, TX | ___ 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: Why was the ventrilo-server port removed?
On Tue, Jun 04, 2013 at 04:28:38PM -0700, Xin Li wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/04/13 14:34, Bob Willcox wrote: I just noticed that the port for audio/ventrilo-server has been removed. The 'depricated because' reason says No more public distfiles, yet as far as I can tell the distfile for the freebsd version is still available from www.ventrilo.com. It requires a manual download as you have to accept the license agreement, but I don't think that has changed from when I first downloaded it. So, anyone know if there some other reason for its removal? I think it's marked DEPRECATED in r317244 (bapt@) a month ago and then removed. Are you interested in maintaining the port? I'd be willing to. I don't think anything for it has changed. The distfile is still available at the same location. I still run it and don't see any issues with it. Bob Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJRrngmAAoJEG80Jeu8UPuzyb0H/0PFf06OnOGrGQPmqByXigpW O0duWPYr/M7pqAeFDxzpciVeEPnrn+SsWBvOUSwyjtk7dZcSIYlhI3ffT0dUU8co kQFEOZmjaWL1ZjVAruaY3EkwcuKM4oqkUWXKspsDu9scFlKmdpX+YiQl6/8iXyfi 8abL2DJl9yes5fdGMgqIOZqotPM+Tzca5vnqoEVlRxUeLi8IeiCPfquUhHtYBPOd kn1I+SDy+4rbq4soqcLx6NMUxfTp7DKxhVEnoaIB/AJhP7SBcLXY15LxF9iTlN/h lU0rk6VtBOm7PhQKijZGESVT8jRIU7HIJzBoVxHxgZpiRsISe6DIcPW4QC6O6B4= =0CNW -END PGP SIGNATURE- -- Bob Willcox| The future lies ahead. b...@immure.com | Austin, TX | ___ 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: Why was the ventrilo-server port removed?
On Wed, Jun 05, 2013 at 09:40:59AM -0700, Anton Afanasyev wrote: On Wed, Jun 5, 2013 at 5:25 AM, Bob Willcox b...@immure.com wrote: I'd be willing to. I don't think anything for it has changed. The distfile is still available at the same location. I still run it and don't see any issues with it. It looks like the port was deprecated because no more public distfiles: http://portsmon.freebsd.org/portoverview.py?category=audioportname=ventrilo-server Ok, I get that...but I don't understand it. The port is still available from the same place it's been for at least the last year or so (when I first installed it). It is still publically available. You just have to manually download it (so that you can accept the license for it). As far as I can tell nothing regarding its public availability has changed. Bob Anton -- Bob Willcox| The future lies ahead. b...@immure.com | Austin, TX | ___ 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: Why was the ventrilo-server port removed?
On Wed, Jun 05, 2013 at 07:03:30PM +0200, Baptiste Daroussin wrote: On Wed, Jun 05, 2013 at 07:25:28AM -0500, Bob Willcox wrote: On Tue, Jun 04, 2013 at 04:28:38PM -0700, Xin Li wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/04/13 14:34, Bob Willcox wrote: I just noticed that the port for audio/ventrilo-server has been removed. The 'depricated because' reason says No more public distfiles, yet as far as I can tell the distfile for the freebsd version is still available from www.ventrilo.com. It requires a manual download as you have to accept the license agreement, but I don't think that has changed from when I first downloaded it. So, anyone know if there some other reason for its removal? I think it's marked DEPRECATED in r317244 (bapt@) a month ago and then removed. Are you interested in maintaining the port? I'd be willing to. I don't think anything for it has changed. The distfile is still available at the same location. I still run it and don't see any issues with it. Bob I have restored the port and set you as a maintainer. Ok, thanks (I think). :) regards, Bapt -- Bob Willcox| The future lies ahead. b...@immure.com | Austin, TX | ___ 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
Why was the ventrilo-server port removed?
I just noticed that the port for audio/ventrilo-server has been removed. The 'depricated because' reason says No more public distfiles, yet as far as I can tell the distfile for the freebsd version is still available from www.ventrilo.com. It requires a manual download as you have to accept the license agreement, but I don't think that has changed from when I first downloaded it. So, anyone know if there some other reason for its removal? Thanks, Bob -- Bob Willcox| The future lies ahead. b...@immure.com | Austin, TX | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
The xpdf binary is MIA with xpdf-3.03_2
When building the xpdf port the xpdf executable is no longer being built or installed into /usr/lib/libexec/xpdf. I suspect that this happened as the result of a change that was made on 10/12/2012 with version xpdf-3.03_2. My other systems that I've not updated the ports tree on lately have the xpdf-3.03_1 version and there the executable is being built and istalled. Is anyone else seeing this (I have it failing on two of my recently ports tree updated systems here)? Bob -- Bob Willcox Why bother building anymore nuclear b...@immure.comwarheads until we use the ones we have? Austin, TX ___ 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: New mutt-devel problems with text/html processing
On Fri, Oct 08, 2010 at 09:31:08AM +0100, Anton Shterenlikht wrote: On Thu, Oct 07, 2010 at 11:26:06AM -0500, Bob Willcox wrote: On Thu, Oct 07, 2010 at 06:51:38AM -0700, Jeremy Chadwick wrote: On Thu, Oct 07, 2010 at 08:22:09AM -0500, Bob Willcox wrote: The new version of mutt-devel nolonger honors my mailcap entry to invoke lynx when it encounters a text/html file type. Instead it simply displays the raw html text. According to their UPDATING file, they say: all text/* parts can be displayed inline without mailcap Which is suspiciously in the realm of the problem I'm seeing. Perhaps there's now some other way of displaying text/html files w/o mailcap and an external program that I'm missing? Looks relevant, with a response from Michael Elkins explaining the change: http://marc.info/?t=12847709334r=1w=2 Basically, it appears that as of 1.5.21, mutt only displays text/* MIME types using its own internal engine. If you want the old behaviour, when selecting the attachment/entry, press m. Personally I don't like this change, but I'll deal with it. Thanks Jeremy, that was it. Guess I'll just have to get used to pressing 'm' now. I missed the beginning of this thread. I had mutt-devel until about a week ago, when, after some update, it became extremely slow. For example, using just /var/mail it would take 10 seconds or more to move from one message to another in index. The same delay for opening messages in pager. The size of messages was same as before, mostly 2-3 lines with occasional attachment. Anyway, I rolled back to mutt-1.4.2.3_5, which works fine. This has probably nothing to do with the Subject, just thought perhaps somebody else seen a significant slow down after the update? I haven't seen this behavior. My only issue was the change in how the latest mutt-devel handles text/* type attachements. I've seen no change in performance. Bob many thanks anton Sorry if this has nothin Bob -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | -- Bob WillcoxA great many people think they are thinking b...@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James ___ 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 -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 -- Bob WillcoxA great many people think they are thinking b...@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James ___ 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
New mutt-devel problems with text/html processing
The new version of mutt-devel nolonger honors my mailcap entry to invoke lynx when it encounters a text/html file type. Instead it simply displays the raw html text. According to their UPDATING file, they say: all text/* parts can be displayed inline without mailcap Which is suspiciously in the realm of the problem I'm seeing. Perhaps there's now some other way of displaying text/html files w/o mailcap and an external program that I'm missing? Thanks, Bob -- Bob WillcoxA great many people think they are thinking b...@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James ___ 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: New mutt-devel problems with text/html processing
On Thu, Oct 07, 2010 at 06:51:38AM -0700, Jeremy Chadwick wrote: On Thu, Oct 07, 2010 at 08:22:09AM -0500, Bob Willcox wrote: The new version of mutt-devel nolonger honors my mailcap entry to invoke lynx when it encounters a text/html file type. Instead it simply displays the raw html text. According to their UPDATING file, they say: all text/* parts can be displayed inline without mailcap Which is suspiciously in the realm of the problem I'm seeing. Perhaps there's now some other way of displaying text/html files w/o mailcap and an external program that I'm missing? Looks relevant, with a response from Michael Elkins explaining the change: http://marc.info/?t=12847709334r=1w=2 Basically, it appears that as of 1.5.21, mutt only displays text/* MIME types using its own internal engine. If you want the old behaviour, when selecting the attachment/entry, press m. Personally I don't like this change, but I'll deal with it. Thanks Jeremy, that was it. Guess I'll just have to get used to pressing 'm' now. Bob -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | -- Bob WillcoxA great many people think they are thinking b...@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James ___ 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
Sound on rdesktop client and 8.0-stable
Since upgrading my system to 8.0-stable (from 7.2-stable) I no longer get sound on my FreeBSD system when connecting to my Windows 7 system via rdesktop. I start rdesktop like this: rdesktop -r sound:local ... and this was working on 7.2-stable. Now all I get is silence. Is anyone else experiencing this? My system's uname output is: FreeBSD luke.immure.com 8.0-STABLE FreeBSD 8.0-STABLE #31: Mon Dec 28 12:34:17 CST 2009 b...@luke.immure.com:/usr/obj/usr/src/sys/LUKE amd64 [Note that other X applications, pidgin to name one, output sounds] Thanks in advance for any help or advice you can offer, Bob -- Bob Willcox Nothing will ever be attempted b...@immure.com if all possible objections must be first overcome. Austin, TX -- Dr. Johnson ___ 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
MailScanner w/sendmail - why no one listening on port 25?
I am trying to get sendmail and MailScanner running on a 7.2-PRERELEASE system and can't figure out how to get sendmail (or any other program) to listen on port 25. If I remove MailScanner from the setup and just run sendmail alone it works as expected but adding MailScanner into the mix and the system won't accept port 25 connections. I have pretty much the same configuration running on a 6.4-STABLE system (this is a new system scheduled to replace the 6.4 system) and it works fine. I'm using the same MailScanner configuration files and sendmail.mc files on both systems. Anyone have any idea what may have changed and/or what I may have overlooked doing? Any good debugging tips for this problem would be welcomed (I've used sendmail for years but have never learned too much about it). Thanks, Bob -- Bob Willcox The trouble with doing something right the first b...@immure.com time is that nobody appreciates how difficult it was. Austin, TX -- unknown ___ 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: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 12:12:15AM -0600, Scot Hetzel wrote: On 1/31/08, Jeremy Messenger [EMAIL PROTECTED] wrote: On Thu, 31 Jan 2008 21:26:38 -0600, Bob Willcox [EMAIL PROTECTED] wrote: On Fri, Feb 01, 2008 at 01:30:23AM +0100, Operator wrote: In article [EMAIL PROTECTED], Bob Willcox [EMAIL PROTECTED] writes: What I want is the xorg-upgrade program that is used to move a bunch of x11 files to new places for the : In the /usr/ports/UPDATING said: : # script xorg-upgrade : We should change this in UPDATING to: # script xorg-upgrade.log Then there would be less confusion about the xorg-upgrade file. That probably would have helped me. The really sad thing about my mis-reading this is that is the third time I've worked through this particular UPDATING entry to upgrade X. It's been about 8 to 10 months since I last did it, but that doesn't make it any less embarrassing. :) Bob Scot -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 02:40:44PM +1030, Wayne Sierke wrote: On Thu, 2008-01-31 at 21:26 -0600, Bob Willcox wrote: On Fri, Feb 01, 2008 at 01:30:23AM +0100, Operator wrote: In article [EMAIL PROTECTED], Bob Willcox [EMAIL PROTECTED] writes: What I want is the xorg-upgrade program that is used to move a bunch of x11 files to new places for the 7.x version. /usr/ports/Tools/scripts/mergebase.sh Is mergebase.sh a replacement for xorg-upgrade? Bob, Re-read the previous replies and re-read man script(1) paying careful attention to the syntax of the (optional) arguments. xorg-upgrade is the name of the output file that script(1) will write to (i.e. name it anything you want, how about xorg-upgrade.log). xorg-upgrade is merely a suggested name for it. The wording of the /usr/ports/UPDATING entry can be misleading if you read it quickly and make what appears to be a reasonable assumption about how script(1) is used, viz. run the xorg 7.2 upgrade inside a script(1) session. followed by the # script xorg-upgrade example. Ok, my dumb mistake...of course you guys are all right! I've been pretty sick is my only (lame) excuse, and it must be effecting my ablity to think. :) Thanks and I apologize for all the noise. Bob Wayne -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
The info in /usr/ports/UPGRADING describing the steps to upgrade xorg says to run xorg-upgrade. Unfortunately, I can't find *anything* with this name anywhere on my system. Here's my uname output: [EMAIL PROTECTED]:pf /usr/ports uname -a FreeBSD sarlacc.austin.ibm.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #20: Wed Jan 2 11:29:25 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SARLACC amd64 I have (just today) updated my ports tree (via cvsup). Anyone have any idea where I might find the xorg-upgrade file? Perhaps it isn't required any longer. If that's the case, that would be good to know as well. Thanks, Bob -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Thu, Jan 31, 2008 at 03:56:23PM -0500, Wesley Shields wrote: On Thu, Jan 31, 2008 at 02:34:26PM -0600, Bob Willcox wrote: The info in /usr/ports/UPGRADING describing the steps to upgrade xorg says to run xorg-upgrade. Unfortunately, I can't find *anything* with this name anywhere on my system. Here's my uname output: [EMAIL PROTECTED]:pf /usr/ports uname -a FreeBSD sarlacc.austin.ibm.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #20: Wed Jan 2 11:29:25 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SARLACC amd64 I have (just today) updated my ports tree (via cvsup). Anyone have any idea where I might find the xorg-upgrade file? Perhaps it isn't required any longer. If that's the case, that would be good to know as well. What that entry is talking about is using script(1) in order to get an accurate account of exactly what you did in case something goes wrong. No, I'm not interested in the script(1) part. I am familiar with script but wasn't interested in using it here. What I want is the xorg-upgrade program that is used to move a bunch of x11 files to new places for the 7.x version. Bob More information is available in the script man page. -- WXS -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 01:02:03AM +, Parish wrote: Bob Willcox wrote: No, I'm not interested in the script(1) part. I am familiar with script but wasn't interested in using it here. What I want is the xorg-upgrade program that is used to move a bunch of x11 files to new places for the 7.x version. xorg-upgrade is the file that script(1) spews all the output into so, if the upgrade fails, you've got all the info to work out why (which is why UPDATING suggests using script(1)). IIRC when I did the 6.9 - 7.x upgrade xorg-upgrade ended up being something like 30MB!! From script(1): script [-akq] [-t time] [file [command ...]] [...] If the argument file is given, script saves all dialogue in file. HTH Thanks for the info Mark, however I do know what script does and why one might use it (I've used it for years for just that, and I'm not even trying to use it here). What I was asking about (please re-read my subject line) was the xorg-upgrade command itself. Where is it located? I can't find it anywhere on any of my 10 FreeBSD systems (and I know it used to exist because I have used it in the past). Bob Regards, Mark -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading xorg 6.9 to 7.3 -- what happened to xorg-upgrade?
On Fri, Feb 01, 2008 at 01:30:23AM +0100, Operator wrote: In article [EMAIL PROTECTED], Bob Willcox [EMAIL PROTECTED] writes: What I want is the xorg-upgrade program that is used to move a bunch of x11 files to new places for the 7.x version. /usr/ports/Tools/scripts/mergebase.sh Is mergebase.sh a replacement for xorg-upgrade? -- Bob Willcox A lack of planning on your part does [EMAIL PROTECTED] not constitute an emergency on my part. Austin, TX ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmaster deletes failed ports
On Tue, Sep 05, 2006 at 10:09:58AM -0700, Doug Barton wrote: Hans Lambermont wrote: RW wrote: ... I don't use portmaster myself, but I just took a look at the script and, unless I'm missing something, it does appear that this feature is missing from portmaster. There an option to create backup packages, but nothing to automatically restore the previous version if the install fails. I can confirm this. The auto-restore-backup would be a nice feature. Doug ? ;-) I'm extremely reluctant to start trying to think for the user. Down that path lies madness. It's easy enough to 'echo BACKUP=yes ~/.portmasterrc' (or /etc/portmaster.rc) and then do the restore yourself if it's a port that you consider mission critical. If you're going to add that to the rc file, I suggest you also do 'mkdir -p /usr/ports/packages/All' and that way you'll always know where your backups are. I admit that this missing feature is why I went back to portupgrade. I liked the simplicity of portmaster over portupgrade, but having it fail on an install and leave the port missing (and dying) was sufficiently annoying to cause me to revert to portupgrade. I'm not suggesting that you should implement it though. Maybe pointing out in the man page that if the install of a port fails you will need to reinstall the old version manually would be helpful. Bob -- Bob Willcox Possessions increase to fill the space [EMAIL PROTECTED]available for their storage. Austin, TX -- Ryan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
