Re: svn error: node conflict in /usr/ports/x11/xcb-proto/files
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: svn error: node conflict in /usr/ports/x11/xcb-proto/files
> 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"
Re: svn error: node conflict in /usr/ports/x11/xcb-proto/files
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? > 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 ___ 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"
svn error: node conflict in /usr/ports/x11/xcb-proto/files
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 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 I wonder about the error message. It recurs even if I rmdir the files directory and run "svn up ." again. Could it be something going bad with this Western Digital 3 TB hard drive? Old Xorg installation no longer works, crashes the computer immediately, so I can't use graphic browser unless I go to NetBSD installation that also sorely needs updating. But maybe that subversion might work, onless it's something bad with the hard drive or some glitch with the server (but then why was it OK on the other computer?) 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"
