[opensuse] How To Route Out Leftover Pre-Upgrade Packages?
Hi, I just encountered a problem with MySQL, the symptom of which was a failure to start the server because of a dynamic link failure: rcmysql start Updating MySQL privilege database... /usr/bin/mysql_upgrade: relocation error: /usr/bin/mysql_upgrade: symbol dynstr_append_os_quoted, version libmysqlclient_15 not defined in file libmysqlclient.so.15 with link time reference failed It turns out the problem was some old MySQL packages that I assume were left over from my 10.2 installation (they showed no repository name when viewed in YaST Software Management). Removing the old packages and installing the current ones resolved the problem. I'd like to systematically enumerate such pre-upgrade packages, but manually stepping through the entire list of installed packages in YaST looking for those not associated with a current repository is far too tedious and time-consuming to be practical. Is there a CLI way to list packages grouped by repository from which they were installed or those that are "orphaned?" I know that the Repositories view in YaST Software Management will list all the packages available in each configured repository, but the packages I'm most concerned with are those that are no longer associated with any repository and as far as I know don't show up there. Thanks. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 22 Oct 2007, Randall R Schulz wrote:- <snip>
Is there a CLI way to list packages grouped by repository from which they were installed or those that are "orphaned?" I know that the Repositories view in YaST Software Management will list all the packages available in each configured repository, but the packages I'm most concerned with are those that are no longer associated with any repository and as far as I know don't show up there.
I don't know about a way of identifying which package comes from a particular repository, but this might help narrow things down a bit: davjam@cobra-mk3:~> cat ./rpm_list.sh #!/bin/bash # create a temporary directory. Make sure it doesn't already exist. # [ -e "/tmp/rpm-temp.$$" ] && exit mkdir -p "/tmp/rpm-temp.$$" # extract the RPM info for all the installed packages # for FILE in $(rpm -qa) do rpm -qi "${FILE}" >"/tmp/rpm-temp.$$/${FILE}.txt" done for FILE in "/tmp/rpm-temp.$$/"* do # skip the GPG keys # TEXT=$(echo "${FILE}"|grep pubkey) [ -n "${TEXT}" ] && continue # Get the distribution # DIST=$(egrep "^Distribution:" "${FILE}") # and the vendor # VEND=$(egrep "Vendor:" "${FILE}") VEND="V${VEND##*V}" # and display it. The test may not be required, but it's there just in case... # [ -n "${DIST}" ] && printf "%-40s %-40s %s\n" "${VEND::40}" "${DIST::40}" $(basename "${FILE}") done # clean up # rm -r "/tmp/rpm-temp.$$" # and quit # exit 0 Usage is simply ./rpm_list.sh . Pipe the output through sort and then less to see the sorted list, or redirect it to a file for later browsing. On what is now a 10.3 system that was upgraded from 10.0, and with a few packages added from the community repositories, here's a few snippets from the output to show what to expect: <snippet> Vendor: http://packman.links2linux.de Distribution: openSUSE 10.3 (i386) ffmpeg-0.4.9-8.pm.svn20070902.txt Vendor: Packman Distribution: openSUSE 10.3 (i586) xmms-1.2.10-200.pm.4.txt </snippet> Two different vendor headers from different packages built/supplied by Packman. <snippet> Vendor: (none) Distribution: openSUSE 10.3 DVDAuthorWizard-1.4.6-1.suse103.txt </snippet> One of my own packages. Ought to add a vendor header to it. <snippet> Vendor: openSUSE Build Service Distribution: VideoLAN / 10.3 vlc-0.8.6c-3.2.txt </snippet> One from VideoLAN. Looks like they're using their own installation of the Build Service. <snippet> Vendor: SUSE LINUX Products GmbH, Nuernb Distribution: openSUSE 10.3 (i586) aaa_base-10.3-90.txt </snippet> And, finally, one package from SUSE/Novell. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ 100Mnodes RC5-72 @ 15Mkeys | SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit | RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 23 October 2007 03:38, David Bolt wrote:
On Mon, 22 Oct 2007, Randall R Schulz wrote:-
<snip>
Is there a CLI way to list packages grouped by repository from which they were installed or those that are "orphaned?" ...
I don't know about a way of identifying which package comes from a particular repository, but this might help narrow things down a bit:
Thanks. I'll check that out. I already managed to find most of the leftovers using this command: % rpm -qa --qf '%{NAME}\t%{DISTRIBUTION}\t%{PACKAGER}\n' \ |egrep -v '10.3|gpg-pubkey' \ |expand -25,60 \ |sort There are so very many RPM query keywords, I only scanned the list quickly and picked a few that looked useful. There are probably more and better ones for this purpose. I also noticed that it seems some of the current packages from 10.3 Packman repository bear the DISTRIBUTION value 'openSUSE 10.2 (i386)' (or i586).
davjam@cobra-mk3:~> cat ./rpm_list.sh
May I suggest that this is a case for using an attachment? The list allows them, you know, and they're much easier to deal with than program code as loose text within an email message (though I commend you for not allowing the lines to wrap—most people don't even bother to do that).
#!/bin/bash
...
Usage is simply ./rpm_list.sh . Pipe the output through sort and then less to see the sorted list, or redirect it to a file for later browsing.
On what is now a 10.3 system that was upgraded from 10.0, and with a few packages added from the community repositories, here's a few snippets from the output to show what to expect:
...
Regards, David Bolt
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 23 Oct 2007, Randall R Schulz wrote:-
On Tuesday 23 October 2007 03:38, David Bolt wrote:
I don't know about a way of identifying which package comes from a particular repository, but this might help narrow things down a bit:
Thanks. I'll check that out. I already managed to find most of the leftovers using this command:
% rpm -qa --qf '%{NAME}\t%{DISTRIBUTION}\t%{PACKAGER}\n' \ |egrep -v '10.3|gpg-pubkey' \ |expand -25,60 \ |sort
Certainly easier than my script, and probably a lot quicker as well. I've saved that for future reference.
There are so very many RPM query keywords, I only scanned the list quickly and picked a few that looked useful. There are probably more and better ones for this purpose.
Possibly. I didn't look to see what was available, just going with what I remembered.
I also noticed that it seems some of the current packages from 10.3 Packman repository bear the DISTRIBUTION value 'openSUSE 10.2 (i386)' (or i586).
I hadn't actually noticed that but, looking at the packages on my system, it's true. I have a total of six i386 packages that say the distribution is 10.2. Since I have the source RPMs, I'll have a look and see if it's a hard-coded value in the spec file, or some build mistake.
davjam@cobra-mk3:~> cat ./rpm_list.sh
May I suggest that this is a case for using an attachment? The list allows them, you know, and they're much easier to deal with than program code as loose text within an email message
I'm not too keen on adding attachments to mailing lists, especially since it is known for them to be removed. One thing I didn't do was to wrap the script with <snippet> </snippet> marks.
(though I commend you for not allowing the lines to wrap—most people don't even bother to do that).
What I should have done isn't make the long lines so they didn't wrap, but to split them up to make the script easier to read. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys | SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit | RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 23 October 2007 07:48, David Bolt wrote:
On Tue, 23 Oct 2007, Randall R Schulz wrote:-
...
davjam@cobra-mk3:~> cat ./rpm_list.sh
May I suggest that this is a case for using an attachment? The list allows them, you know, and they're much easier to deal with than program code as loose text within an email message
I'm not too keen on adding attachments to mailing lists, especially since it is known for them to be removed. One thing I didn't do was to wrap the script with <snippet> </snippet> marks.
It is _known_ that they are _not removed_. (Just look at the "Suspicious Update" thread for an example. In that case, it's an image attachment, no less. Yours was just a text file.)
(though I commend you for not allowing the lines to wrap—most people don't even bother to do that).
What I should have done isn't make the long lines so they didn't wrap, but to split them up to make the script easier to read.
I refuse to be limited by the data formats of 30+ years ago... I mean, Hollerith cards? Come on.
Regards, David Bolt
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 23 Oct 2007, Randall R Schulz wrote:-
On Tuesday 23 October 2007 07:48, David Bolt wrote:
I'm not too keen on adding attachments to mailing lists, especially since it is known for them to be removed. One thing I didn't do was to wrap the script with <snippet> </snippet> marks.
It is _known_ that they are _not removed_.
Then there has been a change, to that policy, as I have almost several thousand archived messages from this list that have the header: X-MIME-Notice: attachments may have been removed from this message which suggests that attachments may be removed.
(Just look at the "Suspicious Update" thread for an example. In that case, it's an image attachment, no less. Yours was just a text file.)
I noticed. Interestingly enough, I notice that the message with the 846KiB uncompressed tiff as an attachment also has that same header. As to why the poster couldn't have used compression, I don't know. Saving it with Gimp as a PNG reduced it to 22KiB. A later post, also contained image attachments of 216KiB and 375KiB. These reduced to 17Kib and 25KiB.
(though I commend you for not allowing the lines to wrap—most people don't even bother to do that).
What I should have done isn't make the long lines so they didn't wrap, but to split them up to make the script easier to read.
I refuse to be limited by the data formats of 30+ years ago... I mean, Hollerith cards? Come on.
It's a common courtesy to those using console mail applications, which was why I think I should have wrapped it. As for Hollerith cards, as long as you keep them in the correct order, what's wrong with them ;-) Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys | SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit | RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* David Bolt
I noticed. Interestingly enough, I notice that the message with the 846KiB uncompressed tiff as an attachment also has that same header. As to why the poster couldn't have used compression, I don't know. Saving it with Gimp as a PNG reduced it to 22KiB. A later post, also contained image attachments of 216KiB and 375KiB. These reduced to 17Kib and 25KiB.
I noticed that but didn't comment. You *are* correct that graphics should have been presented in the least imposing popular format. The presenter is/was being quite presumptious and inconsiderate. There are *still* list members on dial-up and/or measured service. - -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn4472 (GNU/Linux) iD4DBQFHHiLmClSjbQz1U5oRAg8iAJQNVMIu/LMDZYFVG/BuDCtXFRmaAKCMXzr+ MPKJOHPQDpOmQL/asfoHXg== =gQ9m -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2007 12:35 AM, Patrick Shanahan wrote:
* David Bolt
[10-23-07 12:27]: I noticed. Interestingly enough, I notice that the message with the 846KiB uncompressed tiff as an attachment also has that same header. As to why the poster couldn't have used compression, I don't know. Saving it with Gimp as a PNG reduced it to 22KiB. A later post, also contained image attachments of 216KiB and 375KiB. These reduced to 17Kib and 25KiB.
I noticed that but didn't comment. You *are* correct that graphics should have been presented in the least imposing popular format. The presenter is/was being quite presumptious and inconsiderate. There are *still* list members on dial-up and/or measured service.
I agree about not sending such big attachments to a list like this out of consideration, but context in that exact instance (I am not the OP in question) was it was sent in that format so that it could be used by OpenOffice. OO would not have been able to use a png, thus making another formatted pic useless for the reason it was sent. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Joe Morris (NTM)
I agree about not sending such big attachments to a list like this out of consideration, but context in that exact instance (I am not the OP in question) was it was sent in that format so that it could be used by OpenOffice. OO would not have been able to use a png, thus making another formatted pic useless for the reason it was sent.
Of the hundred plus applications available to display a graphic file, especially a picture, OO would probably be the *last* choice a linux user would make, imnsho! Not excused.... - -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn4472 (GNU/Linux) iD8DBQFHHpfYClSjbQz1U5oRAhlFAKCRmzaz3/7RO384g7R+CikCxBTyigCeN0Ze 8ndgMhJLRhHsh9ORX5gh5oI= =m+5H -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-10-24 at 08:47 +0800, Joe Morris (NTM) wrote:
I agree about not sending such big attachments to a list like this out of consideration, but context in that exact instance (I am not the OP in question) was it was sent in that format so that it could be used by OpenOffice. OO would not have been able to use a png, thus making another formatted pic useless for the reason it was sent.
No, you are mistaken: OO will happily accept png, jpg, and many other graphic formats. I know for certaing as I use them. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHHxDAtTMYHG2NR9URAjyaAJ9xP1TFD+nTeL+mQIs72jRpM1ekJgCfckSs 7xOYesIwFDZrNTKPE5PlFF4= =xAeL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2007 05:30 PM, Carlos E. R. wrote:
The Wednesday 2007-10-24 at 08:47 +0800, Joe Morris (NTM) wrote:
I agree about not sending such big attachments to a list like this out of consideration, but context in that exact instance (I am not the OP in question) was it was sent in that format so that it could be used by OpenOffice. OO would not have been able to use a png, thus making another formatted pic useless for the reason it was sent.
No, you are mistaken: OO will happily accept png, jpg, and many other graphic formats. I know for certaing as I use them.
I was referring to the splash screen. I had not seen the tiff when I replied. The splash screen is AFAIK hard coded to a specific name and type. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-10-24 at 19:32 +0800, Joe Morris (NTM) wrote:
The Wednesday 2007-10-24 at 08:47 +0800, Joe Morris (NTM) wrote:
I agree about not sending such big attachments to a list like this out of consideration, but context in that exact instance (I am not the OP in question) was it was sent in that format so that it could be used by OpenOffice. OO would not have been able to use a png, thus making another formatted pic useless for the reason it was sent.
No, you are mistaken: OO will happily accept png, jpg, and many other graphic formats. I know for certaing as I use them. I was referring to the splash screen. I had not seen the tiff when I replied. The splash screen is AFAIK hard coded to a specific name and type.
Nobody has talked here about the splash screen, as far as I remember. The problem is that somebody sent a 1.2 Mbyte email containing a screen capture of a Yast dialog in tiff format, which is large (and later sent another email with two more large images). You said that he sent it that way in order to be used in OOo, and I say that is not true: OOo was not mentioned in that thread, and OOo can import almost any graphic format. Now you say it was for the splash screen, and this is the first time I hear that mentioned in this or the other thread. Or are you talking of another (third) thread? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHHzmgtTMYHG2NR9URAmT7AJ4jvXfrSFhAma0UveIsVYHRzNV9eQCgh7F/ efTNO6ocxFAn7PReilW3UCM= =UucX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/24/2007 12:35 AM, Patrick Shanahan wrote:
* David Bolt
[10-23-07 12:27]: I noticed. Interestingly enough, I notice that the message with the 846KiB uncompressed tiff as an attachment also has that same header. As to why the poster couldn't have used compression, I don't know. Saving it with Gimp as a PNG reduced it to 22KiB. A later post, also contained image attachments of 216KiB and 375KiB. These reduced to 17Kib and 25KiB.
I noticed that but didn't comment. You *are* correct that graphics should have been presented in the least imposing popular format. The presenter is/was being quite presumptious and inconsiderate. There are *still* list members on dial-up and/or measured service.
Sorry, I hadn't made it to the thread with (obvious to me now) the mentioned picture. My comment earlier was misinformed. I thought it was another "big" attachment. You guys are correct on this one. Sorry for the misinformed post. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Joe Morris (NTM)
Sorry, I hadn't made it to the thread with (obvious to me now) the mentioned picture. My comment earlier was misinformed. I thought it was another "big" attachment. You guys are correct on this one. Sorry for the misinformed post.
It's not a *problem*, but a healthy discussion :^) - -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn4472 (GNU/Linux) iD8DBQFHHp3wClSjbQz1U5oRAtMNAJ9KOmkIyFBahraU5b9H4yQdKdM8AACfT7Mn W38xEv+1ICp/1HlvAVyVZUE= =EHtg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David Bolt wrote:
As for Hollerith cards, as long as you keep them in the correct order, what's wrong with them ;-)
That's why we wrap our mails at around 70 columns, of course. To leave a couple of spaces before the sequence number punched in columns 73-80! The most important thing about punched cards is the machine thats put them back in the right order after you drop them :) Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R.
-
Dave Howorth
-
David Bolt
-
Joe Morris (NTM)
-
Patrick Shanahan
-
Randall R Schulz