Hi. I have installed SuSE 9.2 here, and would run a YOU. I receive this information: Patch: konversation-52003 I have tested it with other YOU mirrors, but receive the same information. What is the problem ? Erik Jakobsen
The Tuesday 2005-03-22 at 10:36 +0100, Erik Jakobsen wrote:
I have installed SuSE 9.2 here, and would run a YOU. I receive this information:
Patch: konversation-52003
Huh? :-?
I have tested it with other YOU mirrors, but receive the same information.
What is the problem ?
I don't see the problem. Could you expand? -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Tuesday 2005-03-22 at 10:36 +0100, Erik Jakobsen wrote:
I have installed SuSE 9.2 here, and would run a YOU. I receive this information:
Patch: konversation-52003
Huh? :-?
Jepp :-)
I have tested it with other YOU mirrors, but receive the same information.
What is the problem ?
I don't see the problem. Could you expand?
I try it: Here is a sample from my log when I try to run YOU: 2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(parsePackages):306 ACCEPTED_FULL 2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(parsePackages):306 ACCEPTED_FULL 2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(parsePackages):306 ACCEPTED_FULL 2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(readDir):555 Successfully read perl-52001 2005-03-22 21:06:03 <1> lajka3(7510) [mediaaccess++] MediaCurl.cc(getFile):297 URL: http://ftp.gwdg.de/pub/suse/i386/update/ 9.2/patches/konversation-52003 2005-03-22 21:06:03 <1> lajka3(7510) [liby2util++] PathInfo.cc(_Log_Result):273 rename /var/lib/YaST2/you/mnt/i386/update/9. 2/patches/konversation-52003.new.yast.37456 -> /var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003 2005-03-22 21:06:03 <1> lajka3(7510) [mediaaccess] MediaHandler.cc(provideFile):244 provideFile(./i386/update/9.2/patches/ko nversation-52003) 2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(readDir):531 Check signature of '/var/lib/YaST2/yo u/mnt/i386/update/9.2/patches/konversation-52003' 2005-03-22 21:06:03 <1> lajka3(7510) [liby2util++] ExternalProgram.cc(start_program):163 Executing '/usr/bin/gpg' '--homedir ' '/var/lib/YaST2/gnupg' '--no-default-keyring' '--keyring' '/usr/lib/rpm/gnupg/pubring.gpg' '--verify' '/var/lib/YaST2/you/ mnt/i386/update/9.2/patches/konversation-52003' 2005-03-22 21:06:03 <1> lajka3(7510) [liby2util++] ExternalProgram.cc(checkStatus):322 pid 7748 exited with status 2 2005-03-22 21:06:03 <3> lajka3(7510) [packagemanager] PMYouPatchInfo.cc(readDir):533 Signature check for '/var/lib/YaST2/you /mnt/i386/update/9.2/patches/konversation-52003' failed. 2005-03-22 21:06:03 <1> lajka3(7510) [mediaaccess] MediaHandler.cc(disconnect):192 Disconnected: http://ftp.gwdg.de/pub/suse / attached; localRoot "/var/lib/YaST2/you/mnt" 2005-03-22 21:06:03 <1> lajka3(7510) [mediaaccess] MediaHandler.cc(release):219 Released: http://ftp.gwdg.de/pub/suse/ not a ttached; localRoot "/var/lib/YaST2/you/mnt" 2005-03-22 21:06:03 <1> lajka3(7510) [mediaaccess++] MediaAccess.cc(MediaAccess):62 http(http://ftp.gwdg.de/pub/suse/ not at tached; localRoot "/var/lib/YaST2/you/mnt") 2005-03-22 21:06:03 <1> lajka3(7510) [mediaaccess++] MediaAccess.cc(close):147 handler 0x87e1308 2005-03-22 21:06:03 <1> lajka3(7510) [mediaaccess] MediaAccess.cc(close):155 Close: http(http://ftp.gwdg.de/pub/suse/ not at tached; localRoot "/var/lib/YaST2/you/mnt") (OK) 2005-03-22 21:06:03 <3> lajka3(7510) [packagemanager] InstYou.cc(retrievePatchInfo):284 Error downloading patchinfos: ERROR( You:File has invalid signature.)[Patch: konversation-52003] 2005-03-22 21:06:04 <3> lajka3(7510) [YCP] clients/online_update_start.ycp:445 GetPatches err: sig 2005-03-22 21:06:05 <3> lajka3(7510) [Interpreter] OnlineUpdateDialogs.ycp:345 Can't convert value 'true' to type 'symbol' 2005-03-22 21:06:08 <1> lajka3(7510) [Interpreter] clients/online_update.ycp:494 Called YaST client returned: `abort 2005-03-22 21:06:08 <1> lajka3(7510) [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'y2base' 2005-03-22 21:06:08 <1> lajka3(7510) [mediaaccess++] MediaAccess.cc(MediaAccess):62 MediaAccess( closed ) 2005-03-22 21:06:08 <1> lajka3(7510) [mediaaccess++] MediaAccess.cc(close):147 handler 0 2005-03-22 21:06:08 <1> lajka3(7510) [packagemanager++] PMManager.cc(clearAll):87 clearAll 2005-03-22 21:06:08 <1> lajka3(7510) [packagemanager++] PMManager.cc(ClearSaveState):538 SaveState cleared! Erik
The Wednesday 2005-03-23 at 07:46 +0100, Erik Jakobsen wrote: El 2005-03-23 a las 07:46 +0100, Erik Jakobsen escribió:
Patch: konversation-52003
Huh? :-?
Jepp :-)
Ah. :-)
I have tested it with other YOU mirrors, but receive the same information.
What is the problem ?
I don't see the problem. Could you expand?
I try it:
Here is a sample from my log when I try to run YOU:
2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(parsePackages):306 ACCEPTED_FULL 2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(parsePackages):306 ACCEPTED_FULL
Hum. I need a crash course in greek, Matrix style... [...] Ah. Found it - leaving the greek for another ocassion:
2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(readDir):531 Check signature of '/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003' 2005-03-22 21:06:03 <1> lajka3(7510) [liby2util++] ExternalProgram.cc(start_program):163 Executing '/usr/bin/gpg' '--homedir ' '/var/lib/YaST2/gnupg' '--no-default-keyring' '--keyring' '/usr/lib/rpm/gnupg/pubring.gpg' '--verify' '/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003'
yast is calling an external program, gnupg, to check the signature of the "konversation" patch file.
2005-03-22 21:06:03 <1> lajka3(7510) [liby2util++] ExternalProgram.cc(checkStatus):322 pid 7748 exited with status 2 2005-03-22 21:06:03 <3> lajka3(7510) [packagemanager] PMYouPatchInfo.cc(readDir):533 Signature check for '/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003' failed.
Signature check failed. That is the problem. Notice that the problem is not with the rpm package, but the patch file. This is a text file containing information used by YOU to determine what/how to update. You can check for yourself, with the command, as root: gpg --homedir /var/lib/YaST2/gnupg --no-default-keyring \ --keyring /usr/lib/rpm/gnupg/pubring.gpg \ --verify /var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003 In my 9.1 system I get: gpg: WARNING: unsafe permissions on homedir "/var/lib/YaST2/gnupg" gpg: Signature made Fri Feb 11 14:10:28 2005 CET using DSA key ID 9C800ACA gpg: Good signature from "SuSE Package Signing Key <build@suse.de>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 79C1 79B2 E1C8 20C1 890F 9994 A84E DAE8 9C80 0ACA Correct. Your result should be different, and give a clue on how to solve it. It might be as simple as manually downloaading again that patch file, who knows. Or perhaps you don't have the keyring. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Wednesday 2005-03-23 at 07:46 +0100, Erik Jakobsen wrote:
El 2005-03-23 a las 07:46 +0100, Erik Jakobsen escribió:
snip.
Here is a sample from my log when I try to run YOU:
2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(parsePackages):306 ACCEPTED_FULL 2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(parsePackages):306 ACCEPTED_FULL
Hum. I need a crash course in greek, Matrix style...
[...]
Ah. Found it - leaving the greek for another ocassion:
That indeed sounds good :-)
2005-03-22 21:06:03 <1> lajka3(7510) [packagemanager++] PMYouPatchInfo.cc(readDir):531 Check signature of '/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003' 2005-03-22 21:06:03 <1> lajka3(7510) [liby2util++] ExternalProgram.cc(start_program):163 Executing '/usr/bin/gpg' '--homedir ' '/var/lib/YaST2/gnupg' '--no-default-keyring' '--keyring' '/usr/lib/rpm/gnupg/pubring.gpg' '--verify' '/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003'
yast is calling an external program, gnupg, to check the signature of the "konversation" patch file.
2005-03-22 21:06:03 <1> lajka3(7510) [liby2util++] ExternalProgram.cc(checkStatus):322 pid 7748 exited with status 2 2005-03-22 21:06:03 <3> lajka3(7510) [packagemanager] PMYouPatchInfo.cc(readDir):533 Signature check for '/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003' failed.
Signature check failed. That is the problem.
Ok.
Notice that the problem is not with the rpm package, but the patch file. This is a text file containing information used by YOU to determine what/how to update.
You can check for yourself, with the command, as root:
I'll do that.
gpg --homedir /var/lib/YaST2/gnupg --no-default-keyring \ --keyring /usr/lib/rpm/gnupg/pubring.gpg \ --verify /var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003
In my 9.1 system I get:
gpg: WARNING: unsafe permissions on homedir "/var/lib/YaST2/gnupg" gpg: Signature made Fri Feb 11 14:10:28 2005 CET using DSA key ID 9C800ACA gpg: Good signature from "SuSE Package Signing Key <build@suse.de>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 79C1 79B2 E1C8 20C1 890F 9994 A84E DAE8 9C80 0ACA
I got this: gpg --homedir /var/lib/YaST2/gnupg --no-default-keyring \
--keyring /usr/lib/rpm/gnupg/pubring.gpg \ --verify /var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003 gpg: WARNING: unsafe permissions on homedir "/var/lib/YaST2/gnupg" gpg: verify signatures failed: eof
And I have this: locate pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg~
Correct. Your result should be different, and give a clue on how to solve it. It might be as simple as manually downloaading again that patch file, who knows. Or perhaps you don't have the keyring.
Well Carlos. From my results, what do you suggest me to do now ? Erik
Erik Jakobsen wrote: snip.
Correct. Your result should be different, and give a clue on how to solve it. It might be as simple as manually downloaading again that patch file, who knows. Or perhaps you don't have the keyring.
Well Carlos. From my results, what do you suggest me to do now ?
Hi. I got You to udpate my SuSE 9.2 now by using the ftp string: ftp://ftp.gwdg.de/pub/suse/ After that I would make updates to KDE using RedCarpet, but had the same errors as reported yesterday: Unresolved dependencies: Upgrading kdepim3-organizer-3.3.0-32.3 => kdepim3-organizer-3.3.2-3[SuSE kde3-stable] Upgrading kdepim3-3.3.0-32.3 => kdepim3-3.4.0-5[SuSE kde3-stable] Marking kdepim3-organizer-3.3.0-32 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32) from kdepim3-3.4.0-5 A conflict over (any) kdepim3-organizer (kdepim3-organizer-3.3.2-3) requires the removal of the to-be-installed package kdepim3-organizer-3.3.2-3 Marking this resolution attempt as invalid. Marking kdepim3-organizer-3.3.0-32.2 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32.2) from kdepim3-3.4.0-5 Marking kdepim3-organizer-3.3.0-32.3 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32.3) from kdepim3-3.4.0-5 Marking kdepim3-organizer-3.3.2-3 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.2-3) from kdepim3-3.4.0-5 Marking kdepim3-organizer-3.3.0-32.4 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32.4) from kdepim3-3.4.0-5 What can I do about that ?. Erik Jakobsen
Erik Jakobsen wrote:
Erik Jakobsen wrote:
snip.
Correct. Your result should be different, and give a clue on how to solve it. It might be as simple as manually downloaading again that patch file, who knows. Or perhaps you don't have the keyring.
Well Carlos. From my results, what do you suggest me to do now ?
Hi. I got You to udpate my SuSE 9.2 now by using the ftp string:
ftp://ftp.gwdg.de/pub/suse/
After that I would make updates to KDE using RedCarpet, but had the same errors as reported yesterday:
Unresolved dependencies:
Upgrading kdepim3-organizer-3.3.0-32.3 => kdepim3-organizer-3.3.2-3[SuSE kde3-stable]
Upgrading kdepim3-3.3.0-32.3 => kdepim3-3.4.0-5[SuSE kde3-stable]
Marking kdepim3-organizer-3.3.0-32 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32) from kdepim3-3.4.0-5
A conflict over (any) kdepim3-organizer (kdepim3-organizer-3.3.2-3) requires the removal of the to-be-installed package kdepim3-organizer-3.3.2-3
Marking this resolution attempt as invalid.
Marking kdepim3-organizer-3.3.0-32.2 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32.2) from kdepim3-3.4.0-5
Marking kdepim3-organizer-3.3.0-32.3 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32.3) from kdepim3-3.4.0-5
Marking kdepim3-organizer-3.3.2-3 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.2-3) from kdepim3-3.4.0-5
Marking kdepim3-organizer-3.3.0-32.4 as uninstallable due to conflicts over (any) kdepim3-organizer (kdepim3-organizer-3.3.0-32.4) from kdepim3-3.4.0-5
What can I do about that ?.
Erik Jakobsen
The Thursday 2005-03-24 at 06:45 +0100, Erik Jakobsen wrote:
I got this:
gpg --homedir /var/lib/YaST2/gnupg --no-default-keyring \
--keyring /usr/lib/rpm/gnupg/pubring.gpg \ --verify /var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003 gpg: WARNING: unsafe permissions on homedir "/var/lib/YaST2/gnupg" gpg: verify signatures failed: eof
And I have this: locate pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg~
Well Carlos. From my results, what do you suggest me to do now ?
My feeling is that the file is incomplete (the "eof" message). Why not download it again, manually? My /var/lib/YaST2/you/mnt/i386/update/9.1/patches/konversation-52003 has 2297 bytes. It begins with the clasic "BEGIN PGP SIGNED MESSAGE" and ends with the corresponding "BEGIN PGP SIGNATURE" and "END PGP SIGNATURE" pair. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Thursday 2005-03-24 at 06:45 +0100, Erik Jakobsen wrote:
I got this:
gpg --homedir /var/lib/YaST2/gnupg --no-default-keyring \
--keyring /usr/lib/rpm/gnupg/pubring.gpg \ --verify
/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003 gpg: WARNING: unsafe permissions on homedir "/var/lib/YaST2/gnupg" gpg: verify signatures failed: eof
And I have this: locate pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg~
Well Carlos. From my results, what do you suggest me to do now ?
My feeling is that the file is incomplete (the "eof" message). Why not download it again, manually?
My /var/lib/YaST2/you/mnt/i386/update/9.1/patches/konversation-52003 has 2297 bytes. It begins with the clasic "BEGIN PGP SIGNED MESSAGE" and ends with the corresponding "BEGIN PGP SIGNATURE" and "END PGP SIGNATURE" pair.
Thanks Carlos. My konverstaio-52003 files has the begin and end signs as you mention above. The file size is greater: locate konversation-52003 /var/lib/YaST2/you/installed/konversation-52003 /var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003 lajka3:/var/lib/YaST2/you/mnt/i386/update/9.2/patches # ls -al konversation-52003 -rw-r--r-- 1 root root 5203 Mar 24 13:40 konversation-52003 lajka3:/var/lib/YaST2/you/installed # ls -al konversation-52003 -rw-r--r-- 1 root root 5203 Mar 24 14:20 konversation-52003 I have downloaded another konversation-52003 file, and have placed it the 2 places where I found it. But as I can get You updates now with ftp://ftp..... its not necessary to try it with http://ftp.... Thanks again Carlos for your help Erik
Erik Jakobsen wrote:
Carlos E. R. wrote:
The Thursday 2005-03-24 at 06:45 +0100, Erik Jakobsen wrote:
I got this:
gpg --homedir /var/lib/YaST2/gnupg --no-default-keyring \
--keyring /usr/lib/rpm/gnupg/pubring.gpg \ --verify
/var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003 gpg: WARNING: unsafe permissions on homedir "/var/lib/YaST2/gnupg" gpg: verify signatures failed: eof
And I have this: locate pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg /usr/lib/rpm/gnupg/pubring.gpg~
Well Carlos. From my results, what do you suggest me to do now ?
My feeling is that the file is incomplete (the "eof" message). Why not download it again, manually?
My /var/lib/YaST2/you/mnt/i386/update/9.1/patches/konversation-52003 has 2297 bytes. It begins with the clasic "BEGIN PGP SIGNED MESSAGE" and ends with the corresponding "BEGIN PGP SIGNATURE" and "END PGP SIGNATURE" pair.
Thanks Carlos. My konverstaio-52003 files has the begin and end signs as you mention above. The file size is greater:
locate konversation-52003 /var/lib/YaST2/you/installed/konversation-52003 /var/lib/YaST2/you/mnt/i386/update/9.2/patches/konversation-52003
lajka3:/var/lib/YaST2/you/mnt/i386/update/9.2/patches # ls -al konversation-52003 -rw-r--r-- 1 root root 5203 Mar 24 13:40 konversation-52003
lajka3:/var/lib/YaST2/you/installed # ls -al konversation-52003 -rw-r--r-- 1 root root 5203 Mar 24 14:20 konversation-52003
I have downloaded another konversation-52003 file, and have placed it the 2 places where I found it. But as I can get You updates now with ftp://ftp..... its not necessary to try it with http://ftp....
Thanks again Carlos for your help
Erik
I just gave it a try using http://ftp..., and it works also ok now :-) Erik
The Friday 2005-03-25 at 07:25 +0100, Erik Jakobsen wrote:
I have downloaded another konversation-52003 file, and have placed it the 2 places where I found it.
You should only replace the one in the /var/lib/YaST2/you/mnt/ path, not the /var/lib/YaST2/you/installed one. Different uses. ...
I just gave it a try using http://ftp..., and it works also ok now :-)
So, there was an error with that file. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Friday 2005-03-25 at 07:25 +0100, Erik Jakobsen wrote:
I have downloaded another konversation-52003 file, and have placed it the 2 places where I found it.
You should only replace the one in the /var/lib/YaST2/you/mnt/ path, not the /var/lib/YaST2/you/installed one. Different uses.
OK.
...
I just gave it a try using http://ftp..., and it works also ok now :-)
So, there was an error with that file.
Yes there was, as it works fine now. Again thanks for your help Erik
participants (2)
-
Carlos E. R. -
Erik Jakobsen