On 2012-02-16 21:55, DenverD wrote:
> but, i don’t see that the bug was ever actually marked resolved, and is now
> “need info” and the back and forth between you and Marcus looks like one of
> you (and i don’t know which) is not following what the other is saying, or
> trying to say…
It is waiting for info from outside. In that state the bug resolver will
wait and do nothing till the info is filled and marked as filled.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 02/16/2012 11:13 PM, Carlos E. R. wrote:
> It is waiting for info from outside. In that state the bug resolver will
> wait and do nothing till the info is filled and marked as filled.
>
Carlos E. R. wrote:
> On 2012-02-16 21:55, DenverD wrote:
>> but, i don’t see that the bug was ever actually marked resolved, and is now
>> “need info” and the back and forth between you and Marcus looks like one of
>> you (and i don’t know which) is not following what the other is saying, or
>> trying to say…
>
> It is waiting for info from outside. In that state the bug resolver will
> wait and do nothing till the info is filled and marked as filled.
Right, but from bugzilla it does also look like dwestf and Marcus were
talking at cross-purposes to some degree.
I haven’t really been following this thread, and I know very little
about RPMs and how the mirror system works, but based on some similar
stuff I do at $work, I would suggest:
dwestf, you need to subscribe to the mirror mailing list, so you can
talk to the people there more directly.
dwestf, you really should try to persuade your network admins to allow a
specific rsync connection to the opensuse server. That should solve your
problems at a stroke.
carlos, all,
> Ie, the same! But they are different files with different checksums.
It is possible for files containing the same characters to have
different bytes depending on character sets and the exact way the
characters were encoded into those character sets. For example, there
are canonical representations of characters encoded in UTF-8 but the
same characters can be encoded in non-canonical ways as well.
It is also possible (don’t ask me how) for two files that are apparently
the same to gzip into a different compressed byte stream. Checking the
md5 or whatever of a gzipped file is not always good enough to decide
whether the enclosed file contents are the same. It usually is, in my
experience, but occasionally you need to check the uncompressed file as
well. I don’t know if the mirrors use compression, though.
I put in a trouble ticket Thursday, and as of Friday when I left work no one has called me. Did not want to join a mailing list, but I guess I might have to do that.
All,
Just came across a problem with my 12.1 32bit laptop at home. When I tried to do an update I got a message saying repo files were unsigned. My laptop points to the default openSUSE update repo, so this is not a mirror problem. Can some one else do a update check to see if they get the same error.
Dave W.
dbwLaptop:~ # zypper update
Retrieving repository 'Main Update Repository' metadata \]
File 'repomd.xml' from repository 'Main Update Repository' is unsigned, continue? [yes/no] (no): no
Retrieving repository 'Main Update Repository' metadata [error]
Repository 'Main Update Repository' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository 'Main Update Repository' because of the above error.
Loading repository data...
Reading installed packages...
Nothing to do.
dbwLaptop:~ #
> Just came across a problem with my 12.1 32bit laptop at home. When I
> tried to do an update I got a message saying repo files were unsigned.
> My laptop points to the default openSUSE update repo, so this is not a
> mirror problem. Can some one else do a update check to see if they get
> the same error.
That’s a new problem and the admin has been alerted. We don’t expect a
response till Monday, though.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Is the advice to click ‘ok’ to the ‘unsigned’ error and proceed. Or quit, and wait for a resolution? Sounds like people are not exactly sure what’s going on … ?
Just did a check, looks like the problem was fixed. Did not got unsigned error. Everything came down fine.
susequint
You should only accept an unsigned or invalid checksums if you fully trust the files. But that is the point of signatures, if they are missing or invalid you should not trust the file. This is the first time I have seen missing signatures with openSUSE. I have seen invalid checksums, or digest errors, before. Most often it means that the repo was in the middle of an update, try again later.
On 02/20/2012 01:16 AM, susequint wrote:
> it appears fixed.
i find it difficult to believe some_one_ fixed anything around midnight
on a Sunday (europa time–i believe that is where the ‘master’ repo
lives)…now, maybe some crons around the world kicked off some rsyncs
which ‘fixed’ (overwrote) garbled files…
> No, there was a manual intervention, I read it somewhere here.
i have seen that since, also (in factory or project ML, i think)
i am HAPPY to see that the organization has someone awake even on Sunday
night to fix broken stuff…five days a week, eight hours a day
maintenance is for candy stores and movie theatres–not for
trans-national communications networks supporting users all over the world.