Re: xterm-353
On 6 Feb, Thomas Mueller wrote: >> Kevin Oberman writes: >> > > 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? > >> > 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 > >> Seamonkey - which was my default browser until it was no longer >> updated - came with this ability built in. The only problem was >> the list of alternate identities was vintage, like, 2000 with no way >> (that I knew of) to change it. > > >> Respectfully, > > >> Robert Huff > > I went to seamonkey-project.org website a few months ago, saw it was > still being developed, not dead, not lame-duck. > > I defined a separate profile, named "chase", where I went to > about:config, defined general.useragent.override (not sure if I > remembered that perfectly) to be the regular user agent string but > with "SeaMonkey" removed. > > Then the web server recognized the browser as Firefox. I don't see > what's so bad about including "SeaMonkey", but that's how the web > server software works: buggy, or maybe the bug is in the head of that > software developer and/or webmasters who continue to use that web > server software even after being informed about the bug. I use Firefox. In my case, the server was upset that I wasn't running my browser on Windows or Mac. I changed the user agent string to tell the server that I was running the latest Firefox on Windows 2000, which made it happy. I tried for Windows 98, but couldn't get that to work. ___ 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 Thu, 6 Feb 2020 07:54:33 -0500 Robert Huff wrote: > > Thomas Mueller writes: > > > > Seamonkey - which was my default browser until it was no > > > longer updated - came with this ability built in. The only > > > problem was the list of alternate identities was vintage, like, > > > 2000 with no way (that I knew of) to change it. > > > > I went to seamonkey-project.org website a few months ago, saw it > > was still being developed, not dead, not lame-duck. > > Fair enough. > However: there is no port. > Hasn't been for months. > Since I have neither the skill or the time to create and > maintain one ... far as I'm concerned seamonkey is dead. > Do you know something I don't know? > > > Respectfully, > > > Robert Huff > > > There is a talks on freebsd forum: https://forums.freebsd.org/threads/disaster-strikes-seamonkey-removed-from-ports-tree.71335/ -- “In politics stupidity is not a handicap”. Napoleon Bonaparte ___ 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
Thomas Mueller writes: > > Seamonkey - which was my default browser until it was no longer > > updated - came with this ability built in. The only problem was the > > list of alternate identities was vintage, like, 2000 with no way (that > > I knew of) to change it. > > I went to seamonkey-project.org website a few months ago, saw it > was still being developed, not dead, not lame-duck. Fair enough. However: there is no port. Hasn't been for months. Since I have neither the skill or the time to create and maintain one ... far as I'm concerned seamonkey is dead. Do you know something I don't know? Respectfully, Robert Huff ___ 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
> Kevin Oberman writes: > > > 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? > > 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 > Seamonkey - which was my default browser until it was no longer > updated - came with this ability built in. The only problem was the > list of alternate identities was vintage, like, 2000 with no way (that > I knew of) to change it. > Respectfully, > Robert Huff I went to seamonkey-project.org website a few months ago, saw it was still being developed, not dead, not lame-duck. I defined a separate profile, named "chase", where I went to about:config, defined general.useragent.override (not sure if I remembered that perfectly) to be the regular user agent string but with "SeaMonkey" removed. Then the web server recognized the browser as Firefox. I don't see what's so bad about including "SeaMonkey", but that's how the web server software works: buggy, or maybe the bug is in the head of that software developer and/or webmasters who continue to use that web server software even after being informed about the bug. 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: xterm-353
Kevin Oberman writes: > > 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? > > 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 Seamonkey - which was my default browser until it was no longer updated - came with this ability built in. The only problem was the list of alternate identities was vintage, like, 2000 with no way (that I knew of) to change it. Respectfully, Robert Huff ___ 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 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: 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: 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: 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 E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Mon, Feb 3, 2020 at 11:38 AM Dave Horsfall wrote: > On Mon, 3 Feb 2020, Christoph Moench-Tegeder wrote: > > > You're right. For some reason, firefox is not handling the additional > > compression correctly (I see Content-Encoding: gzip in the headers, so > > it's advertised, but not unzipped by the browser, so I get a double- > > compressed file. Oh tempora, oh mores). Not enough time to dig into that > > right now. > > FWIW, I find that Firefox is becoming increasingly unreliable, with "dead" > buttons etc (yes, I have JS enabled against my better judgement) and have > to use Safari/Chrome instead. This is a pity, as I find that FF is much > faster and I've used it for many years. > > -- Dave > ___ > 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 Mon, 3 Feb 2020, Christoph Moench-Tegeder wrote: You're right. For some reason, firefox is not handling the additional compression correctly (I see Content-Encoding: gzip in the headers, so it's advertised, but not unzipped by the browser, so I get a double- compressed file. Oh tempora, oh mores). Not enough time to dig into that right now. FWIW, I find that Firefox is becoming increasingly unreliable, with "dead" buttons etc (yes, I have JS enabled against my better judgement) and have to use Safari/Chrome instead. This is a pity, as I find that FF is much faster and I've used it for many years. -- Dave ___ 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
## Thomas Dickey (dic...@his.com): > The server is compressing the output... > Not all browsers have the problem :-( You're right. For some reason, firefox is not handling the additional compression correctly (I see Content-Encoding: gzip in the headers, so it's advertised, but not unzipped by the browser, so I get a double- compressed file. Oh tempora, oh mores). Not enough time to dig into that right now. Regards, Christoph -- Spare Space. ___ 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
Reported to the maintainer. It should be fixed shortly. On Sun, Feb 02, 2020 at 10:36:00AM -0500, ajtiM via freebsd-ports wrote: > Update of xterm to version 253 has a problem: > > ===> License MIT accepted by the user > ===> xterm-353 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by xterm-353 for building > => SHA256 Checksum mismatch for xterm-353.tgz. > => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. > ===> Giving up on fetching files: xterm-353.tgz > Make sure the Makefile and distinfo file (/usr/ports/x11/xterm/distinfo) > are up to date. If you are absolutely sure you want to override this > check, type "make NO_CHECKSUM=yes [other args]". > *** Error code 1 > > Stop. > make[2]: stopped in /usr/ports/x11/xterm > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/x11/xterm > *** Error code 1 > > Stop. > make: stopped in /usr/ports/x11/xterm > > ===>>> make build failed for x11/xterm > ===>>> Aborting update > > ===>>> Update for x11/xterm failed > ===>>> Aborting update > > Thank you. > > -- > “In politics stupidity is not a handicap”. > > Napoleon Bonaparte > ___ > 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" -- meta ___ 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
Thomas, care to check the latest xterm tar file on the mirror? ## Peter Jeremy (pe...@rulingia.com): > If you are inclined, you could compare the contents of both files and > report the differences upstream - particularly if there has been a > malicious change. In fact, https://invisible-mirror.net/archives/xterm/xterm-353.tgz is ftp://ftp.invisible-island.net/xterm/xterm-353.tgz gzipped once over again. The file from the mirror fails the GPG signature check and has sha256 0ef2e2fdfade2dfba41f7babeb1066886fd3c8c6aa6dd057fbce3d59a8848aa6 and can be gunzipped to reveal a tgz file with sha256 e521d3ee9def61f5d5c911afc74dd5c3a56ce147c7071c74023ea24cac9bb768 - that file can be verified with the GPG signature and matches the sha256sum the ports tree expects. (In fact, the file from the mirror can't even be "tar xzf"ed, as it's not a tar inside a gz but a tar inside a gz inside a gz). Regards, Christoph -- Spare Space. ___ 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 2020-Feb-02 12:38:45 -0500, ajtiM via freebsd-ports wrote: >On Sun, 2 Feb 2020 12:11:18 -0500 >ajtiM via freebsd-ports wrote: > >I did solve the problem with download file from the xterm web site. >compile and it works. The tgz file which automatically download from >mirror site is not good. This is what the ports checksums are intended to protect against. If you are inclined, you could compare the contents of both files and report the differences upstream - particularly if there has been a malicious change. -- Peter Jeremy signature.asc Description: PGP signature
Re: xterm-353
On Sun, 2 Feb 2020 12:11:18 -0500 ajtiM via freebsd-ports wrote: I did solve the problem with download file from the xterm web site. compile and it works. The tgz file which automatically download from mirror site is not good. Thank you. -- “In politics stupidity is not a handicap”. Napoleon Bonaparte ___ 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 Sun, 2 Feb 2020 07:42:27 -0800 David Wolfskill wrote: > On Sun, Feb 02, 2020 at 10:36:00AM -0500, ajtiM via freebsd-ports > wrote: > > Update of xterm to version 253 has a problem: > > > > ===> License MIT accepted by the user > > ===> xterm-353 depends on file: /usr/local/sbin/pkg - found > > ===> Fetching all distfiles required by xterm-353 for building > > => SHA256 Checksum mismatch for xterm-353.tgz. > > => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. > > ===> Giving up on fetching files: xterm-353.tgz > > Make sure the Makefile and distinfo file > > (/usr/ports/x11/xterm/distinfo) are up to date. If you are > > absolutely sure you want to override this check, type "make > > NO_CHECKSUM=yes [other args]". *** Error code 1 > > > > I don't see that: > > g1-55(12.1-S)[1] pkg info -o xterm\* > xterm-353 x11/xterm > g1-55(12.1-S)[2] make -C /usr/ports/x11/xterm checksum > ===> License MIT accepted by the user > ===> xterm-353 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by xterm-353 for building > => SHA256 Checksum OK for xterm-353.tgz. > => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. > g1-55(12.1-S)[3] uname -a > FreeBSD g1-55.catwhisker.org 12.1-STABLE FreeBSD 12.1-STABLE #594 > r357402M/357406: Sun Feb 2 03:44:20 PST 2020 > r...@g1-55.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY > amd64 g1-55(12.1-S)[4] svn info /usr/ports Path: /usr/ports Working > Copy Root Path: /usr/ports URL: file:///svn/freebsd/ports/head > Relative URL: ^/head > Repository Root: file:///svn/freebsd/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 524937 > Node Kind: directory > Schedule: normal > Last Changed Author: sunpoet > Last Changed Rev: 524937 > Last Changed Date: 2020-02-02 03:07:56 -0800 (Sun, 02 Feb 2020) > > g1-55(12.1-S)[5] > > Peace, > david Lucky you but not me: pkg info -o xterm\* xterm-352 x11/xterm root@lumiwa:~# make -C /usr/ports/x11/xterm checksum ===> License MIT accepted by the user ===> xterm-353 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by xterm-353 for building => SHA256 Checksum mismatch for xterm-353.tgz. => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. ===> Refetch for 1 more times files: xterm-353.tgz ===> License MIT accepted by the user ===> xterm-353 depends on file: /usr/local/sbin/pkg - found => xterm-353.tgz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch ftp://ftp.invisible-island.net/xterm/xterm-353.tgz fetch: ftp://ftp.invisible-island.net/xterm/xterm-353.tgz: Permission denied => Attempting to fetch https://invisible-mirror.net/archives/xterm/xterm-353.tgz xterm-353.tgz 1374 kB 358 kBps04s ===> Fetching all distfiles required by xterm-353 for building ===> License MIT accepted by the user ===> xterm-353 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by xterm-353 for building => SHA256 Checksum mismatch for xterm-353.tgz. => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. ===> Giving up on fetching files: xterm-353.tgz Make sure the Makefile and distinfo file (/usr/ports/x11/xterm/distinfo) are up to date. If you are absolutely sure you want to override this check, type "make NO_CHECKSUM=yes [other args]". *** Error code 1 Stop. make[1]: stopped in /usr/ports/x11/xterm *** Error code 1 Stop. make: stopped in /usr/ports/x11/xterm -- “In politics stupidity is not a handicap”. Napoleon Bonaparte ___ 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 Sun, Feb 02, 2020 at 10:36:00AM -0500, ajtiM via freebsd-ports wrote: > Update of xterm to version 253 has a problem: > > ===> License MIT accepted by the user > ===> xterm-353 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by xterm-353 for building > => SHA256 Checksum mismatch for xterm-353.tgz. > => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. > ===> Giving up on fetching files: xterm-353.tgz > Make sure the Makefile and distinfo file (/usr/ports/x11/xterm/distinfo) > are up to date. If you are absolutely sure you want to override this > check, type "make NO_CHECKSUM=yes [other args]". > *** Error code 1 > .... I don't see that: g1-55(12.1-S)[1] pkg info -o xterm\* xterm-353 x11/xterm g1-55(12.1-S)[2] make -C /usr/ports/x11/xterm checksum ===> License MIT accepted by the user ===> xterm-353 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by xterm-353 for building => SHA256 Checksum OK for xterm-353.tgz. => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. g1-55(12.1-S)[3] uname -a FreeBSD g1-55.catwhisker.org 12.1-STABLE FreeBSD 12.1-STABLE #594 r357402M/357406: Sun Feb 2 03:44:20 PST 2020 r...@g1-55.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY amd64 g1-55(12.1-S)[4] svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: file:///svn/freebsd/ports/head Relative URL: ^/head Repository Root: file:///svn/freebsd/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 524937 Node Kind: directory Schedule: normal Last Changed Author: sunpoet Last Changed Rev: 524937 Last Changed Date: 2020-02-02 03:07:56 -0800 (Sun, 02 Feb 2020) g1-55(12.1-S)[5] Peace, david -- David H. Wolfskill da...@catwhisker.org McConnell's Senators are covering up their whitewash of Trump's malfeasance. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
xterm-353
Update of xterm to version 253 has a problem: ===> License MIT accepted by the user ===> xterm-353 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by xterm-353 for building => SHA256 Checksum mismatch for xterm-353.tgz. => SHA256 Checksum OK for bsd-xterm-icons-1.tgz. ===> Giving up on fetching files: xterm-353.tgz Make sure the Makefile and distinfo file (/usr/ports/x11/xterm/distinfo) are up to date. If you are absolutely sure you want to override this check, type "make NO_CHECKSUM=yes [other args]". *** Error code 1 Stop. make[2]: stopped in /usr/ports/x11/xterm *** Error code 1 Stop. make[1]: stopped in /usr/ports/x11/xterm *** Error code 1 Stop. make: stopped in /usr/ports/x11/xterm ===>>> make build failed for x11/xterm ===>>> Aborting update ===>>> Update for x11/xterm failed ===>>> Aborting update Thank you. -- “In politics stupidity is not a handicap”. Napoleon Bonaparte ___ 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"
