Mailinglist Archive: opensuse (1897 mails)

[Per Jessen <per@xxxxxxxxxxxx>]

David C. Rankin wrote:
> On 07/23/2010 06:25 AM, Per Jessen wrote:
> > Per Jessen wrote:
> >
> > What I find really odd is that of the two checksums that yast
complains
> > about, one is _empty_:
> >
> > Wrong Digest:  The expected checksum of
> > file /var/tmp/TmpDir.3dKqrq/license.tar.gz
> > is f9b8e7e5c6af23ab500a0c907f2518bc236c89be, but the current checksum
> > is .
>
> That is just strange. I don't suppose that you can just move whatever 
> digest/checksum file from goodbox->bad box can you? I don't know the 
> answer, but what the devs need to disclose is if the packages that 
> failed the digest check are (1) good but with a bad digest; or (2) bad 
> digest = bad package, expect unpredictable results.

Hi David

I've cleared out all repositories on the bad box, so I had expected to
get a clean start, but it's not working. I don't think there is a
checksum file anywhere. 
I completely appreciate "bad digest" = "bad package", no question about
that, but "no digest" = "bad package" is different.  I just don't
understand why I get this "no digest" situation.  You wouldn't happen
to know how the digests are built (locally) ?

> Earlier Context:
> > The 'Retry?' is on the second dialog. After you click, 'Use Anyway?:
> > No', then you fall back to the dialog with the 'Abort, Ignore,
> > Retry' options.
>
> Uh, no - when I say 'no', I keep getting lots of other files with
> checksum problems.  If I say 'no' on the second window (there is no
> retry option), yast reverts to the list of repositories.
>
> I figured out what the disconnect in our thinking was, I was talking 
> about the wrong digest/checksum errors received 'during' install -- if
> I understand now, you are talking about after install. 

Yup.  I basically have a new system that I zypper dup'ed to 11.3 - then
I added my own customizations (snmp, hp proliant software, ntp etc),
and somehow ended up in this weird situation. 

> If so, the only 
> thing I could guess at is to try and identify the packages with a bad 
> checksum stepping though the installed rpms with something like:
>
> for i in $(rpm -qa); do rpm -qi $i >/dev/null; done

I'll try that, but isn't it pretty weird that I also get this problem on
license.tar.gz ??


thanks for taking an interest :-)

/Per


-- 
Per Jessen, Zürich (14.1°C)

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx