Re: sysmerge trouble

2014-02-24 Thread Shawn K. Quinn
On Sun, Feb 23, 2014, at 03:45 PM, Ed Ahlsen-Girard wrote:
 Took a while to submit this, but for the past ~ six weeks of snapshots
 sysmerge fails thus:
 
 ERROR: failed to populate from /usr/src and create checksum file

sysmerge works fine for me on amd64 sans the occasional incident of
operator error.

What's under your /usr/src? What's your sysmerge command line?

-- 
  Shawn K. Quinn
  skqu...@rushpost.com



Re: sysmerge trouble

2014-02-24 Thread Ed Ahlsen-Girard
On 2014-02-24 Shawn K. Quinn skquinn () rushpost ! com wrote:
Date:   2014-02-24 10:49:03

 On Sun, Feb 23, 2014, at 03:45 PM, Ed Ahlsen-Girard wrote:
  Took a while to submit this, but for the past ~ six weeks of
  snapshots sysmerge fails thus:
  
  ERROR: failed to populate from /usr/src and create checksum file
 
 sysmerge works fine for me on amd64 sans the occasional incident of
 operator error.
 
 What's under your /usr/src? What's your sysmerge command line?
 
 -- 
   Shawn K. Quinn
   skqu...@rushpost.com

My /usr/src appears to contain a source tree. I would post the results
of find /usr/src if asked, but that'd be a long message.

sysmerge command line is:

sysmerge

which I have been using for a few years.

-- 

Edward Ahlsen-Girard
Ft Walton Beach, FL



Re: sysmerge trouble

2014-02-24 Thread Kenneth Westerback
On 24 February 2014 07:56, Ed Ahlsen-Girard eagir...@cox.net wrote:
 On 2014-02-24 Shawn K. Quinn skquinn () rushpost ! com wrote:
 Date:   2014-02-24 10:49:03

 On Sun, Feb 23, 2014, at 03:45 PM, Ed Ahlsen-Girard wrote:
  Took a while to submit this, but for the past ~ six weeks of
  snapshots sysmerge fails thus:
 
  ERROR: failed to populate from /usr/src and create checksum file

 sysmerge works fine for me on amd64 sans the occasional incident of
 operator error.

 What's under your /usr/src? What's your sysmerge command line?

 --
   Shawn K. Quinn
   skqu...@rushpost.com

 My /usr/src appears to contain a source tree. I would post the results
 of find /usr/src if asked, but that'd be a long message.

 sysmerge command line is:

 sysmerge

 which I have been using for a few years.

 --

 Edward Ahlsen-Girard
 Ft Walton Beach, FL


Do you perhaps have to switch to 'sysmerge -S'?

 Ken



Re: sysmerge trouble

2014-02-24 Thread Philip Guenther
On Sun, Feb 23, 2014 at 1:45 PM, Ed Ahlsen-Girard eagir...@cox.net wrote:
 Took a while to submit this, but for the past ~ six weeks of snapshots
 sysmerge fails thus:

 ERROR: failed to populate from /usr/src and create checksum file

Six weeks ago was approximately when the /etc/signify/ directory was
added.  My guess is that you missed the bit in the FAQ about using the
-d and -P options when doing cvs updates and thus have no
/usr/src/etc/signify/ directory.


Philip Guenther



Re: sysmerge trouble

2014-02-24 Thread Peter N. M. Hansteen
Ed Ahlsen-Girard eagir...@cox.net writes:

 sysmerge command line is:

 sysmerge

 which I have been using for a few years.

As long as you have all the install sets in place, you can easily run
sysmerge on a system with no source tree installed. For quite a while
now I've tended to run something like this on boxes I upgrade, from
the directory with the updated sets:

$ sudo sysmerge -s etcNM.tgz -x xetcNM.tgz

where 'NM' would have been '55' for the last few weeks on boxes
running snapshots.

- Peter
-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.



Re: sysmerge trouble

2014-02-24 Thread Philip Guenther
On Mon, Feb 24, 2014 at 7:58 PM, Ed Ahlsen-Girard eagir...@cox.net wrote:
 On Mon, 24 Feb 2014 10:59:57 -0800
 Philip Guenther guent...@gmail.com wrote:
...
 Six weeks ago was approximately when the /etc/signify/ directory was
 added.  My guess is that you missed the bit in the FAQ about using the
 -d and -P options when doing cvs updates and thus have no
 /usr/src/etc/signify/ directory.

 I'm still missing it, apparently.

Then you ran the wrong cvs command.  I would give a more precise
response, but you included no information about what commands you've
used.


 No signify in 'following current'.

It doesn't require additional action beyond sysmerge with a correct
cvs tree or a snapshot, so why would it be included there?


Philip Guenther