Hello SuSE people, Am running 10.0 on an AMD64 bit system and the very latest smart. I have since SuSE 8.0 used apt to update my system. I loved it. Fast accurate and no problems. Even upgraded from 8.1 to 8.2 using apt. Since apt can't do KDE anymore I had to switch from apt to smart. Smart is not really that smart (maybe some day soon) but is still the best alternative out there for upgrading and maintaining your current distro. Anyway, here is my really weird problem. When I installed Smart, I downloaded all of the packages which included smart-addons and installed them all. This is for 10.0 mind you. When I try to upgrade the system smart goes and looks at10.1 packages in Packman, and of course, it fails. Here is an excerpt/example from a portion of the message that is produced: Fetching packages... -> http://ftp.gwdg.de/pub/linux/.../libxml++-2.14.0-1.guru.suse100.x86_64.rpm -> http://packman.inode.at/.../libffmpeg0-0.4.9-7.pm.svn20060924.x86_64.rpm libffmpeg0-0.4.9-7.pm.svn2006.. [ 21%] libxml++-2.14.0-1.guru.suse10.. [ 21%] -> http://packman.inode.at/suse/10.1/./x86_64/knemo-0.4.5-0.pm.1.x86_64.rpm -> http://packman.inode.at/suse/10.1/./x86_64/gengetopt-2.18-0.pm.1.x86_64.rpm gengetopt-2.18-0.pm.1.x86_64... Notice that even though the first line states "guru.suse100.x86_64." and will download those packages, while lines 6 & 7 ask for packages from 10.1. Naturally they don't download or upgrade stating that it is an unexpected package size. What ????? is going on here ?? This has to be some kind of weird bug or something. I have been fighting this for a week and only tonight noticed the 10.0 to 10.1 difference. Can't believe that I am the only one affected by this. Thoughts, suggestions, ideas what to do??? Yea, I guess that I could go to Packman and manualy download the half dozen packages to upgrade, but that doesn't fix the broken whatever. Bob S.
On 10/1/06, Bob S wrote:
Fetching packages... -> http://ftp.gwdg.de/pub/linux/.../libxml++-2.14.0-1.guru.suse100.x86_64.rpm -> http://packman.inode.at/.../libffmpeg0-0.4.9-7.pm.svn20060924.x86_64.rpm libffmpeg0-0.4.9-7.pm.svn2006.. [ 21%] libxml++-2.14.0-1.guru.suse10.. [ 21%] -> http://packman.inode.at/suse/10.1/./x86_64/knemo-0.4.5-0.pm.1.x86_64.rpm -> http://packman.inode.at/suse/10.1/./x86_64/gengetopt-2.18-0.pm.1.x86_64.rpm gengetopt-2.18-0.pm.1.x86_64...
Notice that even though the first line states "guru.suse100.x86_64." and will download those packages, while lines 6 & 7 ask for packages from 10.1. Naturally they don't download or upgrade stating that it is an unexpected package size. What ????? is going on here ??
Looks like the metadata for the repository is broken. I have exactly the same problem (version/arch). Earlier yesterday I have send email to packman, so they can fix it. -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
On Sunday 01 October 2006 02:50, Sunny wrote:
On 10/1/06, Bob S wrote:
Fetching packages... -> http://ftp.gwdg.de/pub/linux/.../libxml++-2.14.0-1.guru.suse100.x86_64.rp m -> http://packman.inode.at/.../libffmpeg0-0.4.9-7.pm.svn20060924.x86_64.rpm libffmpeg0-0.4.9-7.pm.svn2006.. [ 21%] libxml++-2.14.0-1.guru.suse10.. [ 21%] -> http://packman.inode.at/suse/10.1/./x86_64/knemo-0.4.5-0.pm.1.x86_64.rpm -> http://packman.inode.at/suse/10.1/./x86_64/gengetopt-2.18-0.pm.1.x86_64.r pm gengetopt-2.18-0.pm.1.x86_64...
Notice that even though the first line states "guru.suse100.x86_64." and will download those packages, while lines 6 & 7 ask for packages from 10.1. Naturally they don't download or upgrade stating that it is an unexpected package size. What ????? is going on here ??
Looks like the metadata for the repository is broken. I have exactly the same problem (version/arch). Earlier yesterday I have send email to packman, so they can fix it.
Thanks Sunny, My next question was going to be who do I notify? Do you think that will mean downloading a new smart-addons rpm? or is that fixed on the repository Bob S. Bob S.
On 02/10/06, Bob S
On Sunday 01 October 2006 02:50, Sunny wrote: [snip]
Looks like the metadata for the repository is broken. I have exactly the same problem (version/arch). Earlier yesterday I have send email to packman, so they can fix it.
Thanks Sunny,
My next question was going to be who do I notify? Do you think that will mean downloading a new smart-addons rpm? or is that fixed on the repository
It's been a growing problem over the last few weeks. It seems to be only the Packman and Guru repos at the moment. I'm sure many (if not most) users are noticing it so I'm sure the packagers have been notified. I guess it wouldn't hurt to email them again tho. :) I have to update a bunch of SuSE based machines and it is becoming a PITA.... cheers jall
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon October 2 2006 00:36, jalal wrote:
I have to update a bunch of SuSE based machines and it is becoming a PITA....
PITA is an understatement! I have noticed that the repos/depositories have been kludged for about a month now. I complains about bad gpg asc files and I have gotten rpm's with broken headers that screw the RPM sys bigtime - I had to do a rebuild to the data base twice - and that didn't work to well until I ran the "verify" flag in rpm on "all" packages installed. The software situation is getting to the point where I wonder if it's worth it to stay with SuSE or switch to another distro (Unbuntu/Kunbuntu ISO is waiting). I don't have the time to jerk around with these sorts of issues - I have work to do and lately I spend more time trying to keep my sys running properly than actually getting any work done. This situation needs to be rememied ASAP IMHO. Cheers, Curtis. - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFIU9d7CQBg4DqqCwRAjanAJwKWZd1TNsXRHngQUcVi0FCyUd6ngCfWXXx 3gVoYd1CJJ0fHTU9D9I85Ew= =PASW -----END PGP SIGNATURE-----
On Monday 02 October 2006 3:36 am, jalal wrote:
My next question was going to be who do I notify? Do you think that will mean downloading a new smart-addons rpm? or is that fixed on the repository
It's been a growing problem over the last few weeks. It seems to be only the Packman and Guru repos at the moment. I'm sure many (if not most) users are noticing it so I'm sure the packagers have been notified. I guess it wouldn't hurt to email them again tho. :)
I have to update a bunch of SuSE based machines and it is becoming a PITA....
To put it mildly! :( Fred -- MickySoft, the ultimate corporate parasite.
I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too? http://www.linuxquestions.org/questions/showthread.php?t=485558 -- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !--
On 03/10/06, Lennart Börjeson
I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too?
http://www.linuxquestions.org/questions/showthread.php?t=485558
No, not really. The problem is simply that the packagers are not putting the correct paths in the smart metadata. Packages are being made for 10.1 and the meta files are being copied over as-is for the 10.0 branch. Which doesn't work... :( Smart itself works fine.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue October 3 2006 12:10, jalal wrote:
On 03/10/06, Lennart Börjeson
wrote: I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too?
http://www.linuxquestions.org/questions/showthread.php?t=485558
No, not really. The problem is simply that the packagers are not putting the correct paths in the smart metadata. Packages are being made for 10.1 and the meta files are being copied over as-is for the 10.0 branch. Which doesn't work... :(
Smart itself works fine.
This would explain why my rpm sys is broken and why I get the following when trying to use the rpm sys: ....L... /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre/lib/rt.jar error: rpmdbNextIterator: skipping h# 2116 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2118 Header V3 DSA signature: BAD, key ID ddaf6454 Unsatisfied dependencies for kdebluetooth-0.0.svn20060413-24.1: libopenobex.so.1 S.5....T c /etc/services ....L... /usr/X11R6/bin/X error: rpmdbNextIterator: skipping h# 2132 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2140 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2148 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2156 Header V3 DSA signature: BAD, key ID ddaf6454 (I think the offending package was the openobex [v 1.02.x I believe] and it has been removed - let's see if it helps) And... "error: rpmdbNextIterator: skipping h# 2116 Header V3 DSA signature: BAD, key ID ddaf6454" is what I get anytime I try to install or remove a package - the above messages were produced by the -Va flag for rpm (-V = verify, a = all). I have to remove the offending package (which takes a bit of research to figure out which one it is), then I have to run the "-Va" flag in rpm and then the "--rebuilddb" and hope it gets fixed. This is why I am getting to the point of wondering if continuing to use SuSE is worth the effort. I am taking a programming class and haven't got time to babysit my sys. This was fine when I was on the beta team (way back when) but I need a production machine more than a test platform. I realize that OpenSuSE releases are similar to fedora in concept (aka bleeding edge). But after using SuSE for sometime (since 7.x) I am at a point where it may be the reality that the SuSE I used to use is no longer the SuSE of today - what can I say but "Thanx Novell"? So, the new packaging distribution schema that Novell has mandated bites bigtime and I either wait to see if Novell can let the devs to fix this mess or if the suits write check with their mouths that the dev can't promise to keep! (as is often the case) I know that the suits at Novell don't read much from this list, but the devs do and perhaps they might forward this and similar messages to the appropriate exec (provided he/she understand as much about computing as he/she does about market share and revenue streams). I'm trying to give Novell the benefit of the doubt (mainly because I trust and know the devs), but it's getting to the point where I'm about ready to burn that ISO of CentOS or Kubuntu and push Novell/SuSE to the curb. Just My $0.02. Curtis. - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFIr9D7CQBg4DqqCwRAon9AKDFcdWnOl1ZYkIhtNe5AucJpzJxDACg29ts AoYh4ysouihylKgTtVO13Mw= =egvJ -----END PGP SIGNATURE-----
Curtis Rey wrote:
This would explain why my rpm sys is broken and why I get the following when trying to use the rpm sys:
....L... /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre/lib/rt.jar error: rpmdbNextIterator: skipping h# 2116 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2118 Header V3 DSA signature: BAD, key ID ddaf6454
Then a GPG key is defect. (Or your whole RPM database is corrupt.) Try rpm -qa 'gpg-pubkey*' | grep ddaf6454 Does it output gpg-pubkey-ddaf6454-3a577225? If yes, rpm -e gpg-pubkey-ddaf6454-3a577225 rpm --import /usr/lib/rpm/gnupg/packman-bwalle.asc This file in /usr/lib/rpm/gnupg/ is from package rpmkey-packman-0.3.2-0.pm.1, btw. But I have to say that I have also problems with the GPG keys from packman that the rpmkey package maintainer can not reproduce or solve. But this is for another thread. HTH, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed October 4 2006 06:34, Joachim Schrod wrote:
pm --import /usr/lib/rpm/gnupg/packman-bwalle.asc
Ok, so I did as you suggested and it seemed to help, at least a bit. However, now when I run an rpm query (or anything else) I get a new message after I ran a querry on "packman" and got his message: error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd So I ran this and got the following: Crusher-1:/home/crrey # rpm -qa 'gpg-pubkey*' | grep cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee Crusher-1:/home/crrey # rpm -e gpg-pubkey-cd3140cd-3f2e76ee error: "gpg-pubkey-cd3140cd-3f2e76ee" specifies multiple packages Crusher-1:/home/crrey # rpm -e gpg-pubkey-cd3140cd-3f2e76ee error: "gpg-pubkey-cd3140cd-3f2e76ee" specifies multiple packages I hate it when a package is installed in various version (and kicks warnings about multiple packages of the same type being installed). I makes it very hard (at least for me) to keep things clean and organized. Any suggestions on how to fix this? I thought I might use YaST since rpm complains the above and I can't force the -e flag. TIA, Curtis - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFI/ls7CQBg4DqqCwRAiNxAKDN2yGeivt0X/KYLywg8/mr7P1sSgCgzTP3 GaShZiV8Ougao+si1TLfgy4= =kLga -----END PGP SIGNATURE-----
On 10/4/06, Curtis Rey wrote:
error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd
So I ran this and got the following:
Crusher-1:/home/crrey # rpm -qa 'gpg-pubkey*' | grep cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee Crusher-1:/home/crrey # rpm -e gpg-pubkey-cd3140cd-3f2e76ee error: "gpg-pubkey-cd3140cd-3f2e76ee" specifies multiple packages Crusher-1:/home/crrey # rpm -e gpg-pubkey-cd3140cd-3f2e76ee error: "gpg-pubkey-cd3140cd-3f2e76ee" specifies multiple packages
I hate it when a package is installed in various version (and kicks warnings about multiple packages of the same type being installed). I makes it very hard (at least for me) to keep things clean and organized.
Any suggestions on how to fix this? I thought I might use YaST since rpm complains the above and I can't force the -e flag.
I had similar problem. Try rebuilding the rpm database: rpm --rebuilddb -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
Curtis Rey wrote:
On Wed October 4 2006 06:34, Joachim Schrod wrote:
pm --import /usr/lib/rpm/gnupg/packman-bwalle.asc
Ok, so I did as you suggested and it seemed to help, at least a bit. However, now when I run an rpm query (or anything else) I get a new message after I ran a querry on "packman" and got his message:
error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd
Then your rpm database is probably damaged. Check that the backup in /var/adm/backup/rpmdb is as current as the last changed file and run rpm --rebuilddb.
So I ran this and got the following:
Crusher-1:/home/crrey # rpm -qa 'gpg-pubkey*' | grep cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee Crusher-1:/home/crrey # rpm -e gpg-pubkey-cd3140cd-3f2e76ee error: "gpg-pubkey-cd3140cd-3f2e76ee" specifies multiple packages
This seems to happen when a GPG key is imported multiple times. (That the keys are imported multiple times in the first place is probably an error -- as I wrote, I have problems with the rpmkeys-packman package myself.) This probably doesn't concern your situation (you should try the rebuilddb option first), but in case that happens again: To delete a GPG key that got imported multiple times, one needs to add the option --allmatches to rpm -e. Now, if anybody can tell me how the vendor and the release attribute of an imported key are computed (the two strings in the pseudo package name after "gpg-pubkey-"), I would be very grateful, as I haven't grokked that part of RPM yet. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany
On Tuesday 03 October 2006 15:10, jalal wrote:
On 03/10/06, Lennart Börjeson
wrote: I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too?
http://www.linuxquestions.org/questions/showthread.php?t=485558
No, not really. The problem is simply that the packagers are not putting the correct paths in the smart metadata. Packages are being made for 10.1 and the meta files are being copied over as-is for the 10.0 branch. Which doesn't work... :(
Smart itself works fine.
Sooooo......who are these packagers ????. And how do we notiy them that the packages are screwed up?? Novell??? SuSE ??? And how do we get them fixed? Bob S.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue October 3 2006 20:00, Bob S wrote:
On Tuesday 03 October 2006 15:10, jalal wrote:
On 03/10/06, Lennart Börjeson
wrote: I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too?
http://www.linuxquestions.org/questions/showthread.php?t=485558
No, not really. The problem is simply that the packagers are not putting the correct paths in the smart metadata. Packages are being made for 10.1 and the meta files are being copied over as-is for the 10.0 branch. Which doesn't work... :(
Smart itself works fine.
Sooooo......who are these packagers ????. And how do we notiy them that the packages are screwed up?? Novell??? SuSE ??? And how do we get them fixed?
Bob S.
Well, considering the announcement today and it's inherent similarity (as in the progenitor) to the "original" SuSE, I'm seriously looking at..... Slackware 11.0. What kinda hit me between the eyes is the update/conf program. Gee! It looks alot like.... YaST (the first version). I'm just wondering about pkg/tgz files and how package management works and how large or small the repositories are. Anyone have any experience with Slackware they're will to share? TIA, Curtis. - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFIzA87CQBg4DqqCwRAqh/AKC6mX5k4WPDkv/Tu2VhYzV0XtHc9wCgsfQC OUa9XhtUI7R+SuSP/JaunLg= =MYnh -----END PGP SIGNATURE-----
On Tue, 2006-10-03 at 23:00 -0400, Bob S wrote:
On Tuesday 03 October 2006 15:10, jalal wrote:
On 03/10/06, Lennart Börjeson
wrote: I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too?
http://www.linuxquestions.org/questions/showthread.php?t=485558
No, not really. The problem is simply that the packagers are not putting the correct paths in the smart metadata. Packages are being made for 10.1 and the meta files are being copied over as-is for the 10.0 branch. Which doesn't work... :(
Smart itself works fine.
Sooooo......who are these packagers ????. And how do we notiy them that the packages are screwed up?? Novell??? SuSE ??? And how do we get them fixed?
This is indeed a big problem. When I look at the repos directory, I get a nice page with the package names, dates, and other interesting package links. But no names. No maintainer. No place to provide constructive info about a repos problem. This is not a forward looking solution. Even an e-mail link to someone would be nice. I guess everyone is anonymous. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Wednesday 04 October 2006 08:25, Roger Oberholtzer wrote:
On Tue, 2006-10-03 at 23:00 -0400, Bob S wrote:
On Tuesday 03 October 2006 15:10, jalal wrote:
On 03/10/06, Lennart Börjeson
wrote: I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too?
http://www.linuxquestions.org/questions/showthread.php?t=485558
No, not really. The problem is simply that the packagers are not putting the correct paths in the smart metadata. Packages are being made for 10.1 and the meta files are being copied over as-is for the 10.0 branch. Which doesn't work... :(
Smart itself works fine.
Sooooo......who are these packagers ????. And how do we notiy them that the packages are screwed up?? Novell??? SuSE ??? And how do we get them fixed?
This is indeed a big problem. When I look at the repos directory, I get a nice page with the package names, dates, and other interesting package links. But no names. No maintainer. No place to provide constructive info about a repos problem. This is not a forward looking solution. Even an e-mail link to someone would be nice.
I guess everyone is anonymous.
For the packman repo's you can contact them at packman@links2linux.de I'm sure there are similar e-mail addresses for the other maintainers if you check their websites. Phil
On Wed, 2006-10-04 at 08:45 +0100, Phil Burness wrote:
For the packman repo's you can contact them at packman@links2linux.de
I'm sure there are similar e-mail addresses for the other maintainers if you check their websites.
The ones in software.opensuse.org (hope I wrote that correct) are the ones I am curious about. There are many things there. I do not know who to contact about 'things'. Glad to hear this about packman's site. Figures that since there is a contact, there is also no problem... -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Wednesday 04 October 2006 10:33, Roger Oberholtzer wrote:
On Wed, 2006-10-04 at 08:45 +0100, Phil Burness wrote:
For the packman repo's you can contact them at packman@links2linux.de
I'm sure there are similar e-mail addresses for the other maintainers if you check their websites.
The ones in software.opensuse.org (hope I wrote that correct) are the ones I am curious about. There are many things there. I do not know who to contact about 'things'. Glad to hear this about packman's site. Figures that since there is a contact, there is also no problem...
I wouldn't bet on that :-) phil
On 10/3/06, Bob S
Sooooo......who are these packagers ????. And how do we notiy them that the packages are screwed up?? Novell??? SuSE ??? And how do we get them fixed?
Bob S.
I already sent a message last Sunday to packman's mailing list. No response so far. But all these problems with the repositories, package managers, etc. in SuSE start to be really frustrating. It is still manageable, but I'm in a "change distro" mood lately. -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition.
* Sunny
But all these problems with the repositories, package managers, etc. in SuSE start to be really frustrating. It is still manageable, but I'm in a "change distro" mood lately.
Whatever pulls your chain, BUT, the updates the last several days via smart-0.42-58.1 have been perfect and I push the envelope. cu when/if you return.... (or were you just threatening us?) -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On 10/4/06, Patrick Shanahan
* Sunny
[10-04-06 10:27]: But all these problems with the repositories, package managers, etc. in SuSE start to be really frustrating. It is still manageable, but I'm in a "change distro" mood lately.
Whatever pulls your chain, BUT, the updates the last several days via smart-0.42-58.1 have been perfect and I push the envelope.
Where from you got smart-0.42-58.1 for 10.0 x86_64? It does not show in smart itself, even I have packan's and guru's repos. A few examples for bad repo data, I'm complaining about: 1. guru - the channel is set: [guru] type = yast2 name = Guru 3rd party package repository baseurl = http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.0 An update from this repo fails: sunny@compy:~> sudo smart install inkscape Loading cache... Updating cache... ######################################## [100%] Computing transaction... Upgrading packages (1): inkscape-0.44.1-2.guru.suse100@x86_64 37.3MB of package files are needed. 3.3kB will be freed. Confirm changes? (Y/n): y Fetching packages... -> http://ftp.gwdg.de/pub/linux/.../inkscape-0.44.1-2.guru.suse100.x86_64.rpm inkscape-0.44.1-2.guru.suse10.. [ 0%] error: Failed to download packages: error: http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.1/RPMS/x86_64/inkscape-0...: Not Found It have been that way at least since last Saturday. 2. Packman: The repo is set like this: [packman] type = yast2 name = Packman 3rd Party Package Repository baseurl = http://packman.iu-bremen.de/suse/10.0 And ... it tries to fetch from a wrong, wrong path (for 10.1): sunny@compy:~> sudo smart install faac Loading cache... Updating cache... ######################################## [100%] Computing transaction... Upgrading packages (1): faac-1.25-0.pm.3@x86_64 220.2kB of package files are needed. 13.4kB will be used. Confirm changes? (Y/n): y Fetching packages... -> http://packman.iu-bremen.de/suse/10.1/./x86_64/faac-1.25-0.pm.3.x86_64.rpm faac-1.25-0.pm.3.x86_64.rpm [ 0%] error: Failed to download packages: error: http://packman.iu-bremen.de/suse/10.1/./x86_64/faac-1.25-0.pm.3.x86_64.rpm: Server reports unexpected size I tried to delete the smart cache and channels and packages in /var/lib/smart. It rebuilds them, and the result is the same. So clearly these are problems with the repo metadata, not smart itself, as it works OK with all other repo's.
cu when/if you return.... (or were you just threatening us?)
I'm going nowhere :), I said I'm is such a mood. I support a couple of family/friends Ubuntu machines :), and besides that they broke X after 2 updates, they fixed it really really soon. I know, that the guys from packman and guru are volunteers, and they do their best, but with all the problems we had with YaST in 10.1 (I have 2 machines), and these problems, which happen too often, it's start to be PITA. SuSE is great distro, or at least was, before Novell and the Ximian guys took over. Since then, everything goes down. They push this gnome (read ximian) stuff, rug (again ximian), beagle (again), etc., which in my opinion does a little good to SUSE as is. I have no objection to any of these technologies, but when they are rushed like this, with all the hidden decision making, while pretending to be "OPEN"SUSE, and without even testing enough ... How comes, that there is no mono yast repository. All they offer is .zip file with the rpms. And (again) rug repo, but without providing any useful information so it can be used with smart? All the directories are with forbidden browsing, so one cannot figure it out by himself. A multiple posts in the mono list about this are left w/o answers. The end point is, that IMHO the combination Ximian/Suse is not good for anybody, while every one of them by itself is pretty good in all technical aspects. But looks like too much politics are involved, and in the end of the day both projects may be harmed very bad, which is not good for us as users. -- -- Svetoslav Milenov (Sunny) Still staying with SUSE with a big hope that they will sort it out.
On Wed, October 4, 2006 10:52 am, Sunny wrote: <snip>
error: Failed to download packages: error: http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.1/RPMS/x86_64/inkscape-0...: Not Found
It have been that way at least since last Saturday.
Hey, I get this too! I thought it was just me. I am using the 32-bit versions, but my errors are similar. what is that? -- Kai Ponte www.perfectreign.com || www.4thedadz.com remember - a turn signal is a statement, not a request
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed October 4 2006 10:52, Sunny wrote:
The end point is, that IMHO the combination Ximian/Suse is not good for anybody, while every one of them by itself is pretty good in all technical aspects. But looks like too much politics are involved, and in the end of the day both projects may be harmed very bad, which is not good for us as users.
I tend to agree with you on this matter. I don't find any repos/repositories for stuff like GNOME that is officially released by Novell. You can get 3rd party packages - but what about the "official" Novell/Ximian/Gnome packages? I'm using 10.0 (avoided 10.1 after hearing all the laments and complaints). And I realize that there have been some fairly substantial changes between 10.0 and 10.1. However, this doesn't explain why this specific tactic of package availability has changed so much since Novell took control. It was somewhat gradual but now is in full swing and I frankly find it vexing to say the least. I find it particularly ironic that in the early days of SuSE the Gnome offerings were a tad on the slim side (as far as devel of Gnome packages tailored for SuSE distos). But what's up now? I mean Ximian is a Gnome company (or a Novell division now) and they're making packages "specifically" for SuSE. So where are these "official" Novell/Ximian/SuSE packages? Liike I said, you can get packages for usr-local-bin and others (guru, etc..) but it's not the stuff that the devs at Novell made is it? And what happened to RUG, Red-Carpet, etc..? Were they replaced (I'm guessing so - for Xen BLEH)! I'm sure there are others that may have wondered the same thing. Gnome is still GPL isn't it? What, Ximians Gnome efforts are exempt from this? If not - WHERE IS THE STUFF??? Or is it that they won't release any Gnome packages that are in devel and not directly assigned/attributed to a specific release? Consider this. At the OpenSuSE site there are "no" Gnome listing. I can't find anything on the Novell site (though I do admit that there's likely a few on the list that know where to find these - if they actually exist). All you find on the OpenSuSE site are those things that resemble the original SuSE stuff (pre-Novell). These are namely KDE, core packages such as kernels and config packages (aaa packages, etc..). Not a Gnome package in site - and that's the ironic part!!! Considering That Novell (and Ximian - is this a De Acaza thing?) tried to push Gnome as the default desktop I fail to understand why they wouldn't make the Gnome stuff available?!?! If you want to promote something (especially in Open Source) you'd think they would let people kick the tires as it were. I would think they would take the opportunity to make these sorts of stuff available to let people acclimate to it - But Nooooooooooo!!! I hate to say it but I feared that this sort of thing would happen with Novell at the wheel - and it's seems my fears are coming true! Further irony is that certian industry publications are touting Novells Enterprise Desktop and the Gnome interface, yet the core user population (those that helped drag SuSE from the dream into reality) are shut out. I don't understand the suits and likely never will - they can't do things on merit or technical value, they have to make everything political and contriving. Anyone know where Mantel is working - is he doing Slackware or some other distro? :) Just my $0.02. Curtis - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFJAFu7CQBg4DqqCwRAilcAJ0RdJjAp8wdR4EP62ASWTTxzFxiKACgqWwv akil6qMrCReHmhlbusY8orE= =lpdp -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed October 4 2006 11:46, Curtis Rey wrote:
On Wed October 4 2006 10:52, Sunny wrote:
The end point is, that IMHO the combination Ximian/Suse is not good for anybody, while every one of them by itself is pretty good in all technical aspects. But looks like too much politics are involved, and in the end of the day both projects may be harmed very bad, which is not good for us as users.
Case in point: ! java-1_5_0-sun 1.5.0_03-2 conflict required by: java-1_5_0-sun-src requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-alsa requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-alsa requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-demo requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-demo requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-devel requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-devel requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-jdbc requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-jdbc requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-plugin requires java-1_5_0-sun = 1.5.0_03-2 java-1_5_0-sun-plugin requires java-1_5_0-sun = 1.5.0_03-2 Conflict Resolution: Downgrade java-1_5_0-sun-1.5.0_07-1.1 to Version 1.5.0-03-2 Remove all 6 referring Packages Delete java-1_5_0-sun-alsa Delete java-1_5_0-sun-demo Delete java-1_5_0-sun-devel Delete java-1_5_0-sun-jdbc Delete java-1_5_0-sun-plugin Delete java-1_5_0-sun-src Ignore Conflict and Risk System Inconsistencies (the last line is a bit funny - since now my sys is full of inconsistencies - Not of my own doing!). Yast presents a long and specific list for all the java packages - so what's the problem? Well the update it complains about were install via YOU as a security update and the original java packages were install VIA Yast repos from Open SuSE - so these are supposed to be officially stable/sanctioned packages. I'll tell what I bet will happen - I downgrade/remove the "offending" packages. Then I'll fire up YOU and it will tell me there's a bunch of security updates for ... you guessed it - Java 1.5! So I'll allow YOU to dl and install these security updates. Next I'll fire up YaST sw_single to install packages and the aforementioned dependency warning will pop up complaining about ... You guessed it - Inconsistencies with the currently installed version of..... Java 1.5 (which was installed by YOU). So "You" will inform me about security updates to Java 1.5, I'll install them. Then YaST sw_single will complain about dependency inconsistencies and I'll have to choose between Ignoring it or trying to fix the dependency issue. If I try to fix the dependency issue I'll essentially be caught in a loop between YOU packages and YaST2 dependency conflicts. If I ignore it then I could be setting myself actual kludgy behavior, and seeing that I'm presently enrolled in a Java programing class and using Eclipse - I would like to avoid Java issue in order to keep clear what is my syntax/logic errors and what is caused by Package/code inconsistencies. I realize the OpenSuSE is essentially a beta devel platform (and this is the first time I "haven't paid for a box set - obviously a prudent move). But it shouldn't be bleed edge so much that it breaks like a Beta - that's what the Beta program is for! Meanwhile I'm trying to get work done (aka do my assignments) and not having a lot of luck! Cheers, Curtis :/
-- Spammers Beware: Trespassers will be shot, survivors will be shot again!
Like the song say: "Everything's 'Zen'... I don't think so"!
- -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFJA3x7CQBg4DqqCwRAtG4AJ98K/bLsaNXaysH8iqQuLiTa4osbQCgnWCF BAE7ypCcLX636rY9i5b/Q1A= =wX40 -----END PGP SIGNATURE-----
On Wed, 2006-10-04 at 11:46 -0700, Curtis Rey wrote:
I tend to agree with you on this matter. I don't find any repos/repositories for stuff like GNOME that is officially released by Novell. You can get 3rd party packages - but what about the "official" Novell/Ximian/Gnome packages?
It's in Factory
I'm using 10.0 (avoided 10.1 after hearing all the laments and complaints). And I realize that there have been some fairly substantial changes between 10.0 and 10.1. However, this doesn't explain why this specific tactic of package availability has changed so much since Novell took control. It was somewhat gradual but now is in full swing and I frankly find it vexing to say the least.
Which tactic is that? The package builds are even more out in the open now than ever before
I find it particularly ironic that in the early days of SuSE the Gnome offerings were a tad on the slim side (as far as devel of Gnome packages tailored for SuSE distos). But what's up now? I mean Ximian is a Gnome company (or a Novell division now) and they're making packages "specifically" for SuSE. So where are these "official" Novell/Ximian/SuSE packages? Liike I said, you can get packages for usr-local-bin and others (guru, etc..) but it's not the stuff that the devs at Novell made is it? And what happened to RUG, Red-Carpet, etc..? Were they replaced (I'm guessing so - for Xen BLEH)! I'm sure there are others that may have wondered the same thing. Gnome is still GPL isn't it?
Gnome was never GPL, it's always been LGPL
What, Ximians Gnome efforts are exempt from this? If not - WHERE IS THE STUFF???
What are you on about. GPL doesn't mean "You have to release"
Considering That Novell (and Ximian - is this a De Acaza thing?) tried to push Gnome as the default desktop I fail to understand why they wouldn't make the Gnome stuff available?!?!
And you still don't see how idiotic this is starting to sound? "These evil people want to make it the default, and they don't give it to us. They must not make it default, and they must start giving it to us" Please at least separate the paranoid rantings into two separate emails, to minimise the confusion for newcomers
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed October 4 2006 12:45, Anders Johansson wrote:
And you still don't see how idiotic this is starting to sound? "These evil people want to make it the default, and they don't give it to us. They must not make it default, and they must start giving it to us"
Please at least separate the paranoid rantings into two separate emails, to minimise the confusion for newcomers
Ok, so it's LGPL - fine. And yes they don't have to release it. But what's up with the push for GNOME as a default but not making them available for people to use. Perhaps I am being a bit foolish. But it seems that if you want to promote something (esp a desktop) you'd make it available for people to use/try in order to have them warm up to it. It all seems as if they are perhaps trying to monitize/proprietize GNOME. It's Ximians ballgame and they can do as they see fit. But once again. How am I supposed to decide if I should take GNOME seriously as something I would like on my desktop when I can't even get any of the current software. And the present form of GNOME on 10.0 works sometimes - until I update a GNOME related package and then it's back to depencency hell and broken stuff - much more so than others such as KDE. Sure KDE will break as will other integrated packages when one updates from time to time. But it seems that if I sneeze too hard that the Damn thing goes kludge on me. I thought about installing generic GNOME packages from Gnome.org but that hasn't gone to well either. I have sworn off the usr-local-bin packages and other 3rd party packages because everytime I install one of these GNOME essentially pukes. It's not that those making 3rd party packages are doing poor work - I generally have a lot of confidence in them. It's more like I don't trust the core GNOME stuff to remain stable enough to indeed install 3rd party stuff. Novell and Ximian are trying to run a business, I understand this. But seriously, where would one make a decision about how the Gnome dev is going if I can't test drive it from time to time without having to go out and buy a boxed set in order to get the silly stuff in the first place (cause if I can't find and install the packages from a repository where the hell else do I get the latest and greatest GNOME stuff except for what in offered in the latest SuSE product - e.g. boxed 10.1/10.2/etc). It's a lot like buying a car. "Sure, I'll sell you a new car" "Can I test drive it first" "No, you'll have to buy the car first - then you can drive it to your hearts content." "How will I know if this car is running right and drives well?" "If you buy the car then you can find out." "How stable is Gnome now?" "Check out the latest release in SLD 10.x., we've put a lot of work into it." "But isn't there a way to run the desktop on my present system to see if I like it" "No" "Last time I tried Gnome I had a lot of problems - I would rather try it first before laying down $100 for the latest boxed set to find out" "Sorry, I don't know where you would get these Gnome packages - they're not available to the public in an open download site" "So the only way I can try the latest Gnome desktop is to buy the latest version of SUSE?" "Yep!" "Nevermind" So perhaps my logic is indeed flawed. But then again I've had no problem with the other desktops. Such as XFCE4, KDE, WindowMaker, etc.... So Gnome is a special case - ok, it's their baby! But considering that DeAcaza said that he had helped Brazil setup a bunch of desktops with Gnome only to return to find they had replaced them all with KDE, much to his surprise. When he asked why they said they had to many problems with Gnome and KDE was far less of a hassle to maintian. So, I guess I'm supposed to just deal with it? I am - I avoid GNOME - but I would like to think that it's improving. How would I know? Wait for the next SuSE release and see if it works as advertised? I'm not that confident given the track record. Cheers, Curtis. - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFJBe47CQBg4DqqCwRAtzOAJ0ZBgEIO/qlZFgb5E9aA0SRGj/yYgCgt8v2 tI8mjZMbPXVX8G/ZWA8iYvg= =/DbR -----END PGP SIGNATURE-----
On Wed, 2006-10-04 at 13:21 -0700, Curtis Rey wrote:
"Sure, I'll sell you a new car"
"Can I test drive it first"
"No, you'll have to buy the car first - then you can drive it to your hearts content."
"How will I know if this car is running right and drives well?"
"If you buy the car then you can find out."
"How stable is Gnome now?"
"Check out the latest release in SLD 10.x., we've put a lot of work into it."
"But isn't there a way to run the desktop on my present system to see if I like it"
"No"
"Last time I tried Gnome I had a lot of problems - I would rather try it first before laying down $100 for the latest boxed set to find out"
Which part of opensuse.org don't you understand?
participants (12)
-
Anders Johansson
-
Bob S
-
Curtis Rey
-
Fred A. Miller
-
jalal
-
Joachim Schrod
-
Lennart Börjeson
-
Patrick Shanahan
-
PerfectReign
-
Phil Burness
-
Roger Oberholtzer
-
Sunny