Re: sysmerge complains about not valid etcXX.tgz set
On Sat, Jan 25, 2014 at 6:18 PM, Markus Lude markus.l...@gmx.de wrote: Hello, today I updated to the latest snapshot on sparc64 (from 22nd january). When I run sysmerge after that I got $ sudo sysmerge -s etc55.tgz -x xetc55.tgz *** ERROR: /var/tmp/sysmerge.Hwq1ImlHSs/etc55.tgz is not a valid etcXX.tgz set Try downloading it again. And/or try to unpack it somewhere else than /. Is it a valid tar archive? -- chs
Re: sysmerge complains about not valid etcXX.tgz set
On Sat, Jan 25, 2014 at 06:18:58PM +0100, Markus Lude wrote: Hello, today I updated to the latest snapshot on sparc64 (from 22nd january). When I run sysmerge after that I got $ sudo sysmerge -s etc55.tgz -x xetc55.tgz *** ERROR: /var/tmp/sysmerge.Hwq1ImlHSs/etc55.tgz is not a valid etcXX.tgz set Any ideas what might go wrong here? sysmerge from -current doesn't complain here and works normal. Regards, Markus
Re: sysmerge complains about not valid etcXX.tgz set
Use sysmerge -S -s etc55.tgz -x xetc55.tgz And verify the etc archives manually as described in the signify manpage. Looks like there is a problem with sysmerge and signify. Fritjof Markus Lude markus.l...@gmx.de wrote: Hello, today I updated to the latest snapshot on sparc64 (from 22nd january). When I run sysmerge after that I got $ sudo sysmerge -s etc55.tgz -x xetc55.tgz *** ERROR: /var/tmp/sysmerge.Hwq1ImlHSs/etc55.tgz is not a valid etcXX.tgz set Any ideas what might go wrong here? Regards, Markus -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: sysmerge complains about not valid etcXX.tgz set
On Sat Jan 25 2014 18:18, Markus Lude wrote: Hello, today I updated to the latest snapshot on sparc64 (from 22nd january). When I run sysmerge after that I got $ sudo sysmerge -s etc55.tgz -x xetc55.tgz *** ERROR: /var/tmp/sysmerge.Hwq1ImlHSs/etc55.tgz is not a valid etcXX.tgz set Any ideas what might go wrong here? try specifying the full (absolute) path to the sets. It's a regression, where sysmerge doesn't handle implicit paths correctly. ajacout@ has already fixed it in -current after Jan, 22.
