Re: Downloading with lynx or w3m, how to download as is, without gratuitous gzip

2017-04-23 Thread Herbert J. Skuhra 
Thomas Mueller skrev:
> 
> I don't use lynx (text-mode web browser) much, but have run into a problem 
> that I never had before.
> Lynx, and also w3m, download what are supposed to be text files and then I 
> see the gzip'ed version on the hard drive.
> 
> Lynx used to download files as is!
> 
> I looked through "man lynx", also /usr/local/etc/lynx.cfg, and couldn't 
> figure how to disable the annoying, gratuitous gzip.
> 
> Mozilla Seamonkey and Firefox can download straight without altering.
> 
> My previous experience was that Lynx was trustworthy and would download files 
> as is.

For w3m you can try to set 'auto_uncompress 1' in ~/.w3m/config.

--
Herbert
___
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"

Downloading with lynx or w3m, how to download as is, without gratuitous gzip

2017-04-23 Thread Thomas Mueller 
> If you're just trying to grab a file, fetch(1) may prove adequate.
> (It's in base.)
  
> Peace,
> david
>-
> David H. Wolfskill  

I tried fetch, but got something entirely different, the stuff on the web page, 
but not the desired file.

File compression, such as PKZIP, Infozip, gzip, bzip2, 7-zip, RAR, xz are 
useful in places but can be overbearing in other places.

Compressing man pages is more pain in the ass than benefit.

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"

make index

2017-04-23 Thread Jonathan Chen 
Hi,

After r439255, "make index" complains of:

...
--- describe.sysutils ---
sh: -m: not found
make[5]: "/usr/ports/sysutils/gcdmaster/../cdrdao/Makefile" line 71:
warning: " -m" returned non-zero status
...

Cheers.
-- 
Jonathan Chen 
___
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"

Downloading with lynx or w3m, how to download as is, without gratuitous gzip

2017-04-23 Thread Thomas Mueller 
I don't use lynx (text-mode web browser) much, but have run into a problem that 
I never had before.

Lynx, and also w3m, download what are supposed to be text files and then I see 
the gzip'ed version on the hard drive.

Lynx used to download files as is!

I looked through "man lynx", also /usr/local/etc/lynx.cfg, and couldn't figure 
how to disable the annoying, gratuitous gzip.

Mozilla Seamonkey and Firefox can download straight without altering.

My previous experience was that Lynx was trustworthy and would download files 
as is.

Otherwise, what other text-mode web browsers are there in case my graphic 
interface (X) is not installed or is not operational?

In this case, the problem arose due to a conflict reported by svn in 
/usr/ports/x11/xcb-proto/files
https://svnweb.freebsd.org/ports/head/x11/xcb-proto/files

I solved that problem with "svn revert -R" but still would like to know how to 
make lynx properly functional again.

Lynx seems much easier to use than w3m, if I could find a way around its fetish 
with gzip; w3m also showed this fetish.

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: Systemic problem causing patch errors?

2017-04-23 Thread Lars Eighner 

On Sun, 23 Apr 2017, Mark Linimon wrote:


On Sun, Apr 23, 2017 at 01:47:16PM -0500, Lars Eighner wrote:

close to 50 ports fail to build because of patch errors


I'm sure you have already checked this, but ...

... when I get this on my powerpc64 machine it is inevitably that I have
run out of space somewhere, usually on /tmp.


Does not seem to be the problem

Sun Apr 23 19:01:09 -bash4.4:0:lars
noos #big~$df
Filesystem1K-blocks  Used  Avail Capacity  Mounted on
/dev/ada0s1a   10143484   1230992810101613%/
devfs 1 1  0   100%/dev
/dev/ada0s1e  101556508 38576   93393412 0%/tmp
/dev/ada0s1f 1674796340 315891884 122492075221%/usr
/dev/ada0s1d  101556508   4637800   88794188 5%/var
fdescfs   1 1  0   100%/dev/fd
linsysfs  4 4  0   100% 
/usr/compat/linux/sys
linprocfs 4 4  0   100% 
/usr/compat/linux/proc


--
Lars Eighner
portsu...@larseighner.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"

Re: Systemic problem causing patch errors?

2017-04-23 Thread Mark Linimon 
On Sun, Apr 23, 2017 at 01:47:16PM -0500, Lars Eighner wrote:
> close to 50 ports fail to build because of patch errors

I'm sure you have already checked this, but ...

... when I get this on my powerpc64 machine it is inevitably that I have
run out of space somewhere, usually on /tmp.

mcl
___
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"

Systemic problem causing patch errors?

2017-04-23 Thread Lars Eighner 
Yesterday I rebuilt and reinstalled 11.0-STABLE amd64. I then refreshed 
the ports tree with svnup ports and ran portupgrade -af. The result was 
that close to 50 ports fail to build because of patch errors, and of 
course several hundred dependent ports failed to build.


This would seem to me to indicate some kind of systemic error. How can I 
identify what I am doing wrong?




--
Lars Eighner
portsu...@larseighner.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"

Re: PR merge-quarterly flag

2017-04-23 Thread Kubilay Kocak 
On 4/23/17 11:42 PM, qjail1 wrote:
> I submitted a PR to update a port I maintain and I selected the
> merge-quarterly flag with a ? [question mark].
> 
> I see the updated version is now in the pkg "latest" repo, but it's not
> in the pkg "quarterly" repo yet.
> 
> How long should it take before the merge into "quarterly" happens?
> 

If the issue has been closed already, re-open it with a comment "Pending
merge to quarterly request/commit" and cc ports-secteam

The original committer that made the change to HEAD (hopefully also the
Assignee of the issue) should always respond to the merge-quarterly
request (?) prior to resolving, either by:

1) Cancelling (unsetting) the flag with a comment outlining why a merge
is not suitable/appropriate/possible, or

2) Setting it to + after the merge has been made, ideally referencing
the same "PR:  " in the merge commit log message.

As far as 'timing' goes, commits to HEAD and subsequent merges to the
quarterly branch should take place within short order of each other,
*possibly* with an delay *if* it requires ports-secteam approval, most
changes are implicitly approved and don't require it), and the Bugzilla
issue can be considered not resolved (or closed) until both the commit
and the merge takes place.
___
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"

PR merge-quarterly flag

2017-04-23 Thread qjail1 
I submitted a PR to update a port I maintain and I selected the 
merge-quarterly flag with a ? [question mark].


I see the updated version is now in the pkg "latest" repo, but it's not 
in the pkg "quarterly" repo yet.


How long should it take before the merge into "quarterly" happens?

___
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: svn error: node conflict in /usr/ports/x11/xcb-proto/files

2017-04-23 Thread David Wolfskill 
On Sun, Apr 23, 2017 at 09:32:08AM +, Thomas Mueller wrote:
> ...
> > > FreeBSD amelia2 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r286653M: Wed
> > Aug 12 15:25:51 UTC 2015
> > > root@amelia2:/usr/obj/usr/src/sys/SANDY11NC-NDIS amd64
> 
> > You should really update world/kernel first and then update all your ports.
> > At least some ports will probably fail on this old system.
> 
> > Herbert
> 
> I know or strongly believe I need to update world/kernel before updating 
> ports; that applies to NetBSD as well as FreeBSD.
> 
> I remember reading on this emailing list (ports) that ports might not build 
> if the underlying base system is not supported.
> 
> In any case, I would have to rebuild ports again after updating world/kernel.
> 
> I was stung on that matter at least once when I updated world/kernel, believe 
> I ran "make delete-old-libs", rendered many ports nonoperational, and had a 
> lot of rebuilding to do.
> 

The sequence in which I update the various components on systems:
* buildworld
* buildkernel (including kernel mods from ports)
* installkernel (including kernel mods from ports)
* mergemaster -p
* installworld
* mergemaster
* delete-old
* reboot
* delete any unwanted ports that are installed
* update all installed ports
* delete-old-libs
* add any ports not installed, but wanted
* reboot

I do this daily on a couple of machines; only weekly on others.  I
rarely have problems caused by the process.  (Note caveat, there. :-})

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Who would have thought that a "hotelier" would be so ... unwelcoming?  Sad.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: INSTALL_TARGET=install-strip runs into "permission denied"

2017-04-23 Thread Tijl Coosemans 
On Sat, 22 Apr 2017 22:37:57 +0200 (CEST) Gerald Pfeifer  
wrote:
> [ Old thread alert, but still relevant. ]
> 
> On Mon, 19 Jan 2015, Tijl Coosemans wrote:
> install   -m 555 mkheaders 
> .../prefix/gcc5/libexec/gcc5/gcc/i386-portbld-freebsd10.1/5.0.0/install-tools/mkheaders
> test -z 'strip' || strip 
> .../prefix/gcc5/libexec/gcc5/gcc/i386-portbld-freebsd10.1/5.0.0/install-tools/fixincl
> strip: unable to copy file 
> '.../prefix/gcc5/libexec/gcc5/gcc/i386-portbld-freebsd10.1/5.0.0/install-tools/fixincl';
>  reason: Permission denied
> Makefile:191: recipe for target 'install-strip' failed
> gmake[3]: *** [install-strip] Error 1  
 This strip command seems redundant.  Isn't fixincl already stripped by
 the "install -s" command above?  
>>> Good point.
>>>   
 What does this piece of the log look like outside the ports framework?  
>>> 
>>> /usr/bin/install -c fixinc.sh 
>>> .../gcc-ref8-amd64/libexec/gcc/x86_64-unknown-freebsd8.4/5.0.0/install-tools/fixinc.sh
>>> /usr/bin/install -c fixincl 
>>> .../gcc-ref8-amd64/libexec/gcc/x86_64-unknown-freebsd8.4/5.0.0/install-tools/fixincl
>>> /usr/bin/install -c mkheaders 
>>> .../gcc-ref8-amd64/libexec/gcc/x86_64-unknown-freebsd8.4/5.0.0/install-tools/mkheaders
>>> test -z 'strip' || strip 
>>> .../gcc-ref8-amd64/libexec/gcc/x86_64-unknown-freebsd8.4/5.0.0/install-tools/fixincl
>>> gmake[2]: Leaving directory '.../OBJ-0118-1528/fixincludes'
>>> 
>>> (I also tried setting STRIP_CMD to true, alas that is not used by GCC.)  
>> Try adding BINMODE=755 to the port Makefile or STRIP=true to CONFIGURE_ARGS  
> 
> Both of these allow the build to succeed as a regular user (non-root), 
> when INSTALL_TARGET=install-strip is set.
> 
> Alas with STRIP=true many files end up being not stripped, whereas with 
> the BINMODE setting the list is down to one file.
>   
> This appears to be the case since various aspects of GCC do not use our
> install-* tools, but a script install-sh (which you can find at the root 
> of the GCC source tree that uses cp, chmod, strip,... for compatibility 
> reasons with many systems).
> 
> So I guess setting BINMODE=755 is the best option if we want binaries
> and libraries in the gcc* ports stripped?
> 
> 
> (This is now also tracked in https://reviews.freebsd.org/D10357 where
> miwi proposed a patch originally.)

Yes, but in my opinion we should stop relying on upstream build systems
to get stripping right and let bsd.port.mk strip ELF files after staging.
It's less work for maintainers.  Then instead of stripping, bsd.port.mk
could also extract debug symbols into separate files and put them into a
debug subpackage.  Using something like this:

objcopy --only-keep-debug file file.debug
objcopy -S --add-gnu-debuglink=file.debug file
___
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: svn error: node conflict in /usr/ports/x11/xcb-proto/files

2017-04-23 Thread Thomas Mueller 
> Thomas Mueller skrev:

> > On this computer, I can't get /usr/ports/x11/xcb-proto/files:
> > Skipped 'files' -- Node remains in conflict
> > At revision 439134.
> > Summary of conflicts:
> >   Skipped paths: 1

> Have you tried 'svn revert -R .' in /usr/ports? Or a fresh checkout?
> Have you tried svnlite from base?

Yes, that fixed it.  I really don't know much about the inner workings of 
subversion, or git for that matter.

I excluded svnlite and portsnap from buildworld, figuring it was redundant with 
the full svn.

> > On other computer, this directory downloads successfully with svn.

> > I even tried downloading with lynx and with w3m, but these text-mode
> > browsers compress (gzip) the downloaded file, and I can't see how to
> > avoid this.  I used to be able to download with lynx, and downloaded
> > file was the same as on the server; lynx would never compress it
> > gratuitously.

> > This is an old installation, needs to be updated when I can get to it after 
> > some other tasks.

> > svn --version shows
> > svn, version 1.8.8 (r1568071)
> >compiled Mar 24 2014, 09:58:59 on amd64-portbld-freebsd11.0

> > uname -a shows

> > FreeBSD amelia2 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r286653M: Wed
> Aug 12 15:25:51 UTC 2015
> > root@amelia2:/usr/obj/usr/src/sys/SANDY11NC-NDIS amd64

> You should really update world/kernel first and then update all your ports.
> At least some ports will probably fail on this old system.

> Herbert

I know or strongly believe I need to update world/kernel before updating ports; 
that applies to NetBSD as well as FreeBSD.

I remember reading on this emailing list (ports) that ports might not build if 
the underlying base system is not supported.

In any case, I would have to rebuild ports again after updating world/kernel.

I was stung on that matter at least once when I updated world/kernel, believe I 
ran "make delete-old-libs", rendered many ports nonoperational, and had a lot 
of rebuilding to do.

If I don't want to risk making the present installation nonoperational, I can 
make another (GPT) partition and install to that.  I have more than enough 
space on 3 TB hard drive.

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"