It seems that 11.1 is not supported anymore. Can you confirm that ?
I know, i need time to test a new system to replace it.
Meanwhile, i try to update the packman packages and it cannot.
It says :
error: /var/cache/zypp/packages/Packman/…/somethin.rpm : Header V4 RSA/SHA1 signature: BAD, key ID 1abd1afb
Yes, 11.1 reached its end-of-life a few weeks ago. You must have missed the announcement. As I understand it, the repositories were disabled at that point. You might be able to get by with the Evergreen repos, but best to check the doc before trying.
On 03/30/2011 12:36 PM, Christophe deR wrote:
>
> Can anyone help me to find a way to install the downloaded rpms ?
in an earlier post you wrote: “Why does Yast refuse to install these
packages? It says there is a key problem. I don’t understand. Can
anyone explain?”
what kind of ‘key’ problem, and when are you seeing that message?
we need to see the exact error message…(hope it is in english, if
not help us help you by translating)
please copy and paste the error you see, or make a screenshot and
upload it to http://paste.opensuse.org/
BUT, are you saying in this post that you have downloaded the RPMs
and now just need to be told how to install them? if so, right click
on the RPM, and select “Open with Install/Remove Software”…though,
will may find trouble because of dependencies…
in which case you will have to track down the packages you need (on
the net) and install them first…
On 03/30/2011 06:36 PM, Christophe deR wrote:
>
> Subprocess failed. Error: Echec RPM:error: /var/cache/zypp/packages/repo_5/Essentials/x86_64/a52dec-0.7.5svn-3.pm.7.1.x86_64.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 1abd1afb
> error: /var/cache/zypp/packages/repo_5/Essentials/x86_64/a52dec-0.7.5svn-3.pm.7.1.x86_64.rpm cannot be installed
>
every file on every mirror of every openSUSE repo has a known good
“RSA/SHA1 signature” <http://www.w3.org/PICS/DSig/RSA-SHA1_1_0.html>
which is calculated prior to being uploaded to the various repo servers…
then, when you download the file you it is checked once on your
machine to see if it has an exactly matching code, if it does it is
known to have not been tampered with or corrupted…
however the file you downloaded does not match, and is in some way
changed from what it should be…
that could be the result of many things…whatever the reason do not
install it…
On 03/30/2011 06:36 PM, Christophe deR wrote:
>
> DenverD> thank you for trying to understand and solve my pb
welcome
> I use Yast2 and Yast2 downloads rpms by itself.
>
> Do you suggest i should download every single rpm by hand and force the
> install one by one with the rpm -force command line ?
no, by forcing you (among other things) allow a package older than the
one installed to replace the newer…
> Isn’t there a smarter and more efficient solution ?
sure… you misunderstood…after reading your “help me to find a way
to install the downloaded rpms” and noting the past tense “downloaded”
i wrote “are you saying in this post that you have downloaded the
RPMs and now just need to be told how to install them? if so . . .”
and then i went on to explain how to do it all manually…so, no it
was not my advice to do it all hand…
and, to answer your “Isn’t there a smarter and more efficient
solution?” another way:
yes, move to a supported version with a live repo to pull dependencies
from…(or forget trying to add new stuff or update from packman or
any other way other than compile from source–or make evergreen work
for you)…
note i am not very familiar with Evergreen…but, i read that you
had enabled those repos…(or repo, as the case my be)…
i think you need to read everything you can find on evergreen (begin
here: http://en.opensuse.org/openSUSE:Evergreen) and i think you
should disable every repo on your machine that is not listed as
available on that Evergreen page…
once you have all your old repos disabled, and all the evergreen repos
enabled then try your update again…if it fails then ask on the
Evergreen mail list…there is a link on that page.
OK. I understand what you say what you said. Thanks a lot DenverD !
As i’m not a native english speaking person, forgive my tense, spelling and/or grammar errors.
I would love to have time to test and install 11.4 . I will try to get some of this time, but i’m not sure i’ll manage to.
It took me many weeks to test 11.3 but it didn’t work like i expected it to work, on my ~8 desktops/laptops at home.
Having some update for 11.1 during the time i test 11.4, is what i thought evergreen and packman would allow.
I know i can ask to evergreen mailing list, but i thought the answer was so simple that the forum experts would have the answer.
Anyway, if anyone has some clues to have the packman rpms installed, i am still listening. I am sure there is tweak that i don’t know to allow YasT to update with packman updates on 11.1 .
On 03/30/2011 09:36 PM, Christophe deR wrote:
>
> I know i can ask to evergreen mailing list, but i thought the answer
> was so simple that the forum experts would have the answer.
the thing is, that Evergreen is only about two months old (if
that)…and, while there may be a few ‘experts’ here using it, i
don’t know any of the regulars who do…so, if you want help with that
you really need to go where the Evergreen experts are–they are not
here…
On 03/30/2011 11:06 PM, Christophe deR wrote:
>
> Thank you DenverD, i’ll first try the 11.4. And if some time remains,
> i’ll keep you advised of this problem’s solution…
>
welcome…
i guess (if you have the RAM and CPU for it) you will like 11.4 !!
Well i tried to install 11.4 on one of my partition, and as usual, it did the same for 11.1 and 11.3, the network is not correctly configured during installed. Moreover, the install screwed my mbr grub and i had to use the 11.1 install DVD to restore my grub on mbr. I still don’t know if the 11.4 i installed works as i have lots of other things to do.
I mean, ok, i love linux, i’ve been using it since more than 11 years nox and i love opensuse, but, come on, it such a pain to install and test and configure. I don’t say that windows or macOS is better, but we really need some more simple upgrade procedures. It’s really heavy time consuming.
That’s the reason why some of us are reluctant to upgrade.