Re: xterm-353
On Tue, Feb 4, 2020 at 9:48 PM Thomas Mueller wrote: > > This is getting a bit off-topic, but I use Firefox with User Agent > Switcher > > by Linder. (There are several Firefox extensions that have VERY similar > > names.) It works perfectly at Chase and also fixes several sites that > > insist on providing the mobile version to FreeBSD. It allows the > selection > > of both OS and browser to provide in the user agent ID on a per-site > basis. > > It fixes a lot of issues. > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > Where would I find User Agent Switcher by Linder? Would it be on a > Mozilla site, and would it work with SeaMonkey? > > Would the several Firefox or SeaMonkey extensions have similar > functionality? > > Better to reply to list only; copy that was sent to me off-list had the > same Message-ID but was in multipart/alternative. Maybe the list software > sanitized the message format? > > Tom > It's available through Firefox from about:addons. It is the one by Linder, one of at eat three extensions of the same name. I don't know about SeaMonkey. Does it support the extension interface like Firefox? If so, it will probably work. You might also check the website at http://mybrowseraddon.com/useragent-switcher.html -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: xterm-353
> This is getting a bit off-topic, but I use Firefox with User Agent Switcher > by Linder. (There are several Firefox extensions that have VERY similar > names.) It works perfectly at Chase and also fixes several sites that > insist on providing the mobile version to FreeBSD. It allows the selection > of both OS and browser to provide in the user agent ID on a per-site basis. > It fixes a lot of issues. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer Where would I find User Agent Switcher by Linder? Would it be on a Mozilla site, and would it work with SeaMonkey? Would the several Firefox or SeaMonkey extensions have similar functionality? Better to reply to list only; copy that was sent to me off-list had the same Message-ID but was in multipart/alternative. Maybe the list software sanitized the message format? Tom ___ 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 Wed, Feb 5, 2020 at 12:48 AM 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 wonder if https://github.com/freebsd/pkg/issues/1807 is related. > -- > 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" > ___ 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: xterm-353
On Tue, Feb 4, 2020 at 3:39 AM Thomas Mueller wrote: > > This is quite surprising as I have not seen this. I do get occasional > dead > > buttons due to all of the privacy add-ons I run, especially No-Script, > but > > also less intrusive ones like Privacy Badger. > > > I have seen a few issues with sites taking advantage of some JS functions > > outside of the standard that Chrome has added and Firefox has not yet > > picked up. This is the fault of Chrome playing the old IE game of making > > other browsers notwork correctly on some pages. I also have to fake the > UI > > identifier for some sites as they reject access from FreeBSD (Chase Bank, > > I'm looking at you!) or do the wrong thing. > > > As regards chromium, I have deleted it it and will not consider ever > using > > it due to it's massive data collection and its blocking privacy tools > like > > No-Script. > > > Kevin Oberman, Part time kid herder and retired Network Engineer > > I know from experience what you mean with Chase Bank blocking online > banking access if your user-agent string is not to the website server's > liking. > > Chase Bank is not the only offender. Some websites, without blocking > access, behave differently and wrongly depending on user-agent string. > > I got Chase Bank to work with an outdated version of Otter Browser and a > fudged user agent. > > Sometimes it's not what browser you're using, but what browser the website > software thinks you're using. > > I do find some scripts to cause problems and make some websites very slow. > > I had problems with Mozilla SeaMonkey on nfl.com when I was looking to > see highlights on the last Super Bowl (last Sunday night). > > I was glad to close that browser window! > > Since this problem with Chase, using Mozilla Seamonkey under FreeBSD, > affects me so directly, I could not resist making this response. > > Tom > This is getting a bit off-topic, but I use Firefox with User Agent Switcher by Linder. (There are several Firefox extensions that have VERY similar names.) It works perfectly at Chase and also fixes several sites that insist on providing the mobile version to FreeBSD. It allows the selection of both OS and browser to provide in the user agent ID on a per-site basis. It fixes a lot of issues. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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"
Re: Why are there 1981 p5-* subdirectories in /usr/ports/devel?
Hi! > 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? There are approx. 1300 python ports in devel and approx. 1100 ruby ports. > 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? Up to now we had no time to implent a different solution. It's no easy task, therefore it will take quite some investment in development time to fix this. -- p...@opsec.eu+49 171 3101372Now what ? ___ 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: FreeBSD Port: firefox-73.0,1 error build
On Tue, Feb 04, 2020 at 03:49:39PM +0700, Alex V. Petrov wrote: > ... > In file included from > /usr/ports/www/firefox/work/.build/dist/system_wrappers/exception:3: > > > /usr/include/c++/v1/exception:180:5: error: no member named 'abort' in > namespace 'std::__1'; did you mean simply 'abort'? > _VSTD::abort(); > ^~~ > /usr/include/c++/v1/__config:759:15: note: expanded from macro '_VSTD' > > #define _VSTD std::_LIBCPP_ABI_NAMESPACE > > ^ > /usr/include/stdlib.h:86:17: note: 'abort' declared here > > _Noreturn void abort(void); > ^ > 1 error generated. > gmake[5]: *** > [/usr/ports/www/firefox/work/firefox-73.0/config/rules.mk:738: > rlbox_thread_locals.o] Error 1 > This is being tracked in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243863 Peace, david -- David H. Wolfskill da...@catwhisker.org "The Senate has abdicated its constitutional duty during the impeachment trial of President Donald Trump." -- Alan S. Frumin, parliamentarian emeritus of the US Senate See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: xterm-353
> This is quite surprising as I have not seen this. I do get occasional dead > buttons due to all of the privacy add-ons I run, especially No-Script, but > also less intrusive ones like Privacy Badger. > I have seen a few issues with sites taking advantage of some JS functions > outside of the standard that Chrome has added and Firefox has not yet > picked up. This is the fault of Chrome playing the old IE game of making > other browsers notwork correctly on some pages. I also have to fake the UI > identifier for some sites as they reject access from FreeBSD (Chase Bank, > I'm looking at you!) or do the wrong thing. > As regards chromium, I have deleted it it and will not consider ever using > it due to it's massive data collection and its blocking privacy tools like > No-Script. > Kevin Oberman, Part time kid herder and retired Network Engineer I know from experience what you mean with Chase Bank blocking online banking access if your user-agent string is not to the website server's liking. Chase Bank is not the only offender. Some websites, without blocking access, behave differently and wrongly depending on user-agent string. I got Chase Bank to work with an outdated version of Otter Browser and a fudged user agent. Sometimes it's not what browser you're using, but what browser the website software thinks you're using. I do find some scripts to cause problems and make some websites very slow. I had problems with Mozilla SeaMonkey on nfl.com when I was looking to see highlights on the last Super Bowl (last Sunday night). I was glad to close that browser window! Since this problem with Chase, using Mozilla Seamonkey under FreeBSD, affects me so directly, I could not resist making this response. Tom ___ 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: Kibana7 port status?
Hi! > is there a particular reason why the Logstash7 and > Elasticsearch7 ports were committed to the ports tree, > but Kibana7 wasn't? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237374 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237372#c30 from 24th of January says: - I don't see that we have a port of kibana7 yet. I don't know if anyone is working on that. I found that it seemed to insist on having node 10.15.2 to run, which was a problem since the FreeBSD port is at 10.17.0. - Any ideas on that ? -- p...@opsec.eu+49 171 3101372Now what ? ___ 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"
Kibana7 port status?
Hi all, is there a particular reason why the Logstash7 and Elasticsearch7 ports were committed to the ports tree, but Kibana7 wasn't? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237374 Kind regards, Patrick -- punkt.de GmbH Patrick M. Hausen .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein ___ 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"
FreeBSD Port: firefox-73.0,1 error build
mkdir -p '.deps/' config/external/rlbox/rlbox_thread_locals.o /usr/local/bin/clang++90 -std=gnu++17 -o rlbox_thread_locals.o -c -I/usr/ports/www/firefox/work/.build/dist/stl_wrappers -I/usr/ports/www/firefox/work/.build/dist/system_wrappers -include /usr/ports/www/firefo x/work/firefox-73.0/config/gcc_hidden.h -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -DNDEBUG=1 -DTRIMMED=1 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL -I /usr/ports/www/firefox/work/firefox-73.0/config/external/rlbox -I/usr/ports/www/firefox/work/.build/config/external/rlbox -I/usr/ports/www/firefox/work/.build/dist/include -I/usr/local/include/nspr -I/usr/local /include/nss -I/usr/local/include/nss/nss -I/usr/ports/www/firefox/work/.build/dist/include/nss -I/usr/local/include -I/usr/local/include -I/usr/local/include/pixman-1 -fPIC -DMOZILLA_CLIENT -include /usr/ports /www/firefox/work/.build/mozilla-config.h -Qunused-arguments -DLIBICONV_PLUG -isystem /usr/local/include -Qunused-arguments -Wall -Wbitfield-enum-conversion -Wempty-body -Wignored-qualifiers -Woverloaded-virtua l -Wpointer-arith -Wshadow-field-in-constructor-modified -Wsign-compare -Wtype-limits -Wunreachable-code -Wunreachable-code-return -Wwrite-strings -Wno-invalid-offsetof -Wclass-varargs -Wempty-init-stmt -Wfloat -overflow-conversion -Wfloat-zero-conversion -Wloop-analysis -Wc++2a-compat -Wcomma -Wimplicit-fallthrough -Wstring-conversion -Wtautological-overlap-compare -Wtautological-unsigned-enum-zero-compare -Wtautolog ical-unsigned-zero-compare -Wno-error=tautological-type-limit-compare -Wno-inline-new-delete -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=backend-plugin -Wno-error=return-std-move -Wno- error=atomic-alignment -Wformat -Wformat-security -Wno-gnu-zero-variadic-macro-arguments -Wno-unknown-warning-option -Wno-return-type-c-linkage -fno-sized-deallocation -fno-aligned-new -O2 -pipe -O3 -DLIBICONV_ PLUG -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -DLIBICONV_PLUG -isystem /usr/local/include -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno -exceptions -fno-math-errno -pipe -I/usr/local/include -O2 -O3 -fno-omit-frame-pointer -funwind-tables -MD -MP -MF .deps/rlbox_thread_locals.o.pp /usr/ports/www/firefox/work/firefox-73.0/config/external/rlbo x/rlbox_thread_locals.cpp In file included from /usr/ports/www/firefox/work/firefox-73.0/config/external/rlbox/rlbox_thread_locals.cpp:10: In file included from /usr/ports/www/firefox/work/.build/dist/include/mozilla/rlbox/rlbox_noop_sandbox.hpp:4: In file included from /usr/ports/www/firefox/work/.build/dist/stl_wrappers/cstdlib:44: In file included from /usr/ports/www/firefox/work/.build/dist/system_wrappers/cstdlib:3: In file included from /usr/include/c++/v1/cstdlib:85: In file included from /usr/ports/www/firefox/work/.build/dist/system_wrappers/stdlib.h:3: In file included from /usr/include/c++/v1/stdlib.h:100: In file included from /usr/ports/www/firefox/work/.build/dist/system_wrappers/math.h:3: In file included from /usr/include/c++/v1/math.h:311: In file included from /usr/ports/www/firefox/work/.build/dist/stl_wrappers/type_traits:50: In file included from /usr/ports/www/firefox/work/.build/dist/include/mozilla/mozalloc.h:31: In file included from /usr/ports/www/firefox/work/.build/dist/stl_wrappers/new:44: In file included from /usr/ports/www/firefox/work/.build/dist/system_wrappers/new:3: In file included from /usr/include/c++/v1/new:90: In file included from /usr/ports/www/firefox/work/.build/dist/system_wrappers/exception:3: /usr/include/c++/v1/exception:180:5: error: no member named 'abort' in namespace 'std::__1'; did you mean simply 'abort'? _VSTD::abort(); ^~~ /usr/include/c++/v1/__config:759:15: note: expanded from macro '_VSTD' #define _VSTD std::_LIBCPP_ABI_NAMESPACE ^ /usr/include/stdlib.h:86:17: note: 'abort' declared here _Noreturn void abort(void); ^ 1 error generated. gmake[5]: *** [/usr/ports/www/firefox/work/firefox-73.0/config/rules.mk:738: rlbox_thread_locals.o] Error 1 gmake[5]: Leaving directory '/usr/ports/www/firefox/work/.build/config/external/rlbox' gmake[4]: *** [/usr/ports/www/firefox/work/firefox-73.0/config/recurse.mk:74: config/external/rlbox/target-objects] Error 2 gmake[4]: Leaving directory '/usr/ports/www/firefox/work/.build' gmake[3]: *** [/usr/ports/www/firefox/work/firefox-73.0/config/recurse.mk:34: compile] Error 2 gmake[3]: Leaving directory '/usr/ports/www/firefox/work/.build' gmake[2]: *** [/usr/ports/www/firefox/work/firefox-73.0/config/rules.mk:394: all] Error 2 gmake[2]: Leaving directory '/usr/ports/www/firefox/work/.build' *** Error code 1 Stop. make[1]: stopped in /usr/ports/www/firefox *** Error code 1 Stop. make: stopped in /usr/ports/www/firefox ===>>> make build failed for www/firefox ===>>> Aborting update -- -
