The same here. I forgot to mention this in the first message: # ls -l -rw------- 1 root root 1309 Jan 23 2006 secring.gpg -rw-r--r-- 1 root root 0 Jul 10 2006 secring.gpg.bak The .bak file is the offending file... This is the date from the rpm, if I interpret the output from below command correct: # rpm -qlv aaa_base | grep secring -rw-r--r-- 1 root root 0 Jul 10 2006 /root/.gnupg/secring.gpg Met vriendelijke groet / Best regards, Wilfred van Velzen

...

...

"Carlos E. R." 2008-01-23 11:52:27

The Wednesday 2008-01-23 at 11:35 +0100, Wilfred van Velzen wrote:

My existing secring.gpg was overwritten yesterday by zero-sized file, probably when I did an update with yast/you. It took me some time to find out why some of my scripts didn't work as expected, so I am a bit p*ssed off... I was very happy with my backup, so I could restore my secring.gpg! :)

Is this a bug?

My "/root/.gnupg/secring.gpg" is also zero bytes, but it is dated 2006. What is the date of the file contained in the rpm, I wonder? -- SERCOM Regeltechniek b.v. Heereweg 9 2161 AB Lisse Nederland +31 (0)252 416530 (voice) +31 (0)252 419481 (fax) http://www.sercom.nl/ Op al onze offertes, op alle opdrachten aan ons en op alle met ons gesloten overeenkomsten zijn toepasselijk de METAALUNIEVOORWAARDEN, gedeponeerd ter Griffie van de Rechtbank te Rotterdam, zoals deze luiden volgens de laatstelijk aldaar neergelegde tekst. De leveringsvoorwaarden worden u op verzoek toegezonden. --- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org