Click to See Complete Forum and Search --> : Slackware Packages


Ryeker
01-31-2001, 09:19 PM
How do I check which version of a package I am running? I found /var/log/packages and the listing of packages installed. Looking into the files, I find that it shows all the files, but no version. For example, how would I know if I installed the latest glibc package to fix the holes? http://www.slackware.com/lists/archive/viewer.php?l=slackware-security&y=2001&m=slackware-security.286413

Thanks,



------------------
ryeker@yahoo.com
Use Slackware, have fun!
Beauty is only skin deep... Attitude runs to the bone. -Dark Angel

ssadams
01-31-2001, 11:10 PM
I just open the name of the package in /var/log/packages in a text editor and look at the files.Here is the updated glib2.2 as it looks when I do this.The date of the install also helps http://www.linuxnewbie.org/ubb/smile.gif

PACKAGE NAME: glibc
COMPRESSED PACKAGE SIZE: 26778 K
UNCOMPRESSED PACKAGE SIZE: 107880 K
PACKAGE LOCATION: ./glibc.tgz
FILE LIST:
./
etc/
etc/rpc
lib/
lib/incoming/
lib/incoming/ld-2.2.so
lib/incoming/libBrokenLocale-2.2.so
lib/incoming/libc-2.2.so
lib/incoming/libcrypt-2.2.so
lib/incoming/libdl-2.2.so

it was installed on my system on the 12th of Jan 2001 as per my /packages folder.

------------------
"Dirty tea heads....I'll
never deal tea again"
W.S.Burroughs

ph34r
01-31-2001, 11:18 PM
In the case of glibc, you can do


ls -l /lib/libc*


and get something like

-rwxr-xr-x 1 root 1013224 Mar 21 2000 /lib/libc-2.1.3.so*
lrwxrwxrwx 1 root 13 Oct 16 17:06 /lib/libc.so.6 -> libc-2.1.3.so*
lrwxrwxrwx 1 root 17 Oct 16 17:06 /lib/libcom_err.so.2 -> libcom_err.so.2.0*
-rwxr-xr-x 1 root 5516 Apr 4 2000 /lib/libcom_err.so.2.0*
-rwxr-xr-x 1 root 61805 Mar 21 2000 /lib/libcrypt-2.1.3.so*
lrwxrwxrwx 1 root 17 Oct 16 17:08 /lib/libcrypt.so.1 -> libcrypt-2.1.3.so*


For other things like apps, you can usually run it from a command line with a switch (-v, -h, --help, etc.) and get version output sooner or later.

[This message has been edited by ph34r (edited 31 January 2001).]

Ryeker
02-01-2001, 12:33 AM
LOL. You got the date from the file creation date, right? That won't help if I installed slack on the same day and installed the upgrades on the same day. All files in my packages folder are Jan 31...

ph34r, yes, that's what I'll have to do, I guess, the old fashioned way.

------------------
ryeker@yahoo.com
Use Slackware, have fun!
Beauty is only skin deep... Attitude runs to the bone. -Dark Angel

ssadams
02-01-2001, 12:50 AM
Originally posted by Ryeker:
LOL. You got the date from the file creation date, right? That won't help if I installed slack on the same day and installed the upgrades on the same day. All files in my packages folder are Jan 31...

ph34r, yes, that's what I'll have to do, I guess, the old fashioned way.


No.I use a simple script that tells me the date of any package installed,upgraded or removed http://www.linuxnewbie.org/ubb/smile.gif

Ryeker
02-01-2001, 01:31 AM
Originally posted by ssadams:
No.I use a simple script that tells me the date of any package installed,upgraded or removed http://www.linuxnewbie.org/ubb/smile.gif

Which is? Or is it a secret? http://www.linuxnewbie.org/ubb/smile.gif

------------------
ryeker@yahoo.com
Use Slackware, have fun!
Beauty is only skin deep... Attitude runs to the bone. -Dark Angel

ssadams
02-01-2001, 02:10 AM
it was something I wrote and thought worked.I upgraded bind just now and tested the script because I was going to send it to you but the damm thing reported the old bind as new.I guess it only works for new installs http://www.linuxnewbie.org/ubb/frown.gif Im going to redo it tomorrow or Friday if I have time.
[bows head in shame]

skweegie
02-01-2001, 03:33 AM
if you are talking about strictly officially released SlackPacks from the slackware crew, then they will all have a package_description. This desciption gives a version number of the parent package (not of individual proggies within that may make up the package) and a brief statement describing the package. unofficial slackpacks (usually contributed ones) sometimes will not have this description so you will have to do it the old school way...

a quick way to get this info (if you don't want to su to root and run pkgtool -> View) is to:

:$ cat /var/log/packages/packagename | grep packagename:

where packagename = just the slackpack name without the .tgz. so in your example it would be:

:$ cat/var/log/packages/glibc | grep glibc:

http://www.linuxnewbie.org/ubb/smile.gifFor the lazy like myself http://www.linuxnewbie.org/ubb/smile.gif
i wrote a horridly coded script (that works for me) to accomplish the above a while ago. i also wanted to do the version checking and to see if i had a particular slackpack installed by just using the name instead of having to cat | grep or ls or using pkgtool.

feel free to give it a try. just dload it, chmod 700 and place into your $home/bin or chmod 755 and put it in a shared bin...
http://www.skweegie.f2s.com/huh/verpack

------------------
my lame slackpage (http://www.skweegie.f2s.com)

skweegie
02-02-2001, 02:31 PM
hehe, out of boredom, i mopped up the above script a little bit so it can do the install/upgrade date for the slackpack and to also tell you if there was a package_description included with the slackpack. give it a try and let me know how it goes...


http://www.skweegie.f2s.com/huh/verpack

cheers

Ryeker
02-02-2001, 03:33 PM
So glibc isn't an official package from the Slackware crew?


Please, enter JUST the name of the Slackware Package WITHOUT the .tgz extension
glibc


This slackpack was installed or upgraded on:
Jan 31 10:07

There is no package_description for this installed
SlackPack. In all likelihood, this is not an officially
released SlackPack from the Slackware crew. You'll have to go
old school to get more info on the version of this SlackPack.

Would you like to give it another go? (y/n)


Hehe... thanks! I'll play with this script a little more.

skweegie
02-02-2001, 03:50 PM
you're getting that from the slackpacks from slackware.com. or did you install the packs from linuxmafia...

Ryeker
02-02-2001, 03:50 PM
Everything slackware.com.

skweegie
02-02-2001, 03:57 PM
hrmh :(

do a:
:$ cat/var/log/packages/glibc | grep glibc:

and see if there is output...

here's mine

Please, enter JUST the name of the Slackware Package WITHOUT the .tgz extension
glibcso


This slackpack was installed or upgraded on:
Jan 15 03:37

Here is the package description for glibcso:

glibcso: glibc-2.2.1 runtime support
glibcso:
glibcso: This package contains the shared libraries, binaries, and support
glibcso: files required to run most Linux applications linked with glibc.
glibcso:
glibcso:
glibcso:
glibcso:
glibcso:
glibcso:
glibcso:

Would you like to give it another go? (y/n)


hehe, i did say in my first post that it was
a horridly coded script (that works for me) so your mileage may vary... :)

Ryeker
02-02-2001, 04:11 PM
Hmm... downloaded:

ftp://ftp.slackware.com/pub/slackware/slackware-current/slakware/a1/glibcso.tgz

and did an upgradepkg glibcso.tgz

Still, nothing.

Oh well.

skweegie
02-02-2001, 04:20 PM
cat /var/log/packages/glibc | grep glibc:

didn't generate any output either?

that's weird... :(

Ryeker
02-02-2001, 04:25 PM
wfong@britney:~$ cat /var/log/packages/glibc | grep glibc
PACKAGE NAME: glibc
PACKAGE LOCATION: ./glibc.tgz
usr/bin/glibcbug
usr/bin/ldd-glibc
usr/doc/glibc-2.2.1/
usr/doc/glibc-2.2.1/BUGS
usr/doc/glibc-2.2.1/CONFORMANCE
usr/doc/glibc-2.2.1/COPYING
usr/doc/glibc-2.2.1/COPYING.LIB
usr/doc/glibc-2.2.1/FAQ
usr/doc/glibc-2.2.1/INSTALL
usr/doc/glibc-2.2.1/INTERFACE
usr/doc/glibc-2.2.1/NAMESPACE
usr/doc/glibc-2.2.1/NEWS
usr/doc/glibc-2.2.1/NOTES
usr/doc/glibc-2.2.1/PROJECTS
usr/doc/glibc-2.2.1/README
usr/doc/glibc-2.2.1/README.libm
usr/doc/glibc-2.2.1/linuxthreads/
usr/doc/glibc-2.2.1/linuxthreads/Banner
usr/doc/glibc-2.2.1/linuxthreads/Examples/
usr/doc/glibc-2.2.1/linuxthreads/Examples/Makefile
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex1.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex10.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex11.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex12.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex13.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex14.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex15.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex16.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex2.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex3.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex4.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex5.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex6.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex7.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex8.c
usr/doc/glibc-2.2.1/linuxthreads/Examples/ex9.c
usr/doc/glibc-2.2.1/linuxthreads/FAQ.html
usr/doc/glibc-2.2.1/linuxthreads/LICENSE
usr/doc/glibc-2.2.1/linuxthreads/README
usr/doc/glibc-2.2.1/linuxthreads/README.Xfree3.2
usr/doc/glibc-2.2.1/linuxthreads/linuxthreads.texi
wfong@britney:~$ echo "Oh Well, thx anyways" >> skweegie

ssadams
02-02-2001, 05:24 PM
Ryeker:that package is not the latest.Goto www.linuxmafia.org (http://www.linuxmafia.org) get glibc and glibcso enter run level 1 remove the old ones and install the new ones,then go back to whatever runlevel you were at.I found out that my script is no good because I have a mixture of Slackware and Linuxmafia packages and it only reads certain ones correctly.Oh well there's my handy log book to check on.

Ryeker
02-02-2001, 05:48 PM
How do you know that isn't the latest package? I went to Linuxmafia.org and they have 2.2.1 also, that they got from slackware-current (where I got mines).

Thanks,

skweegie
02-02-2001, 06:00 PM
hiyas,

the only difference between LM's slackpacks and the official release from slack.com is LFS support to coincide with the 2.4.x kernel. not sure if that's what ryker is using but just wanted to let you know...

also, ryeker, finally figured out what the hell was happening with the script. basically, since i was using autoslack to maintain and slackpack upgrades, part of the upgrade process is to also upgrade your package_description for the slackpack entry in /var/log/packages. i stupidly forgot that when you just upgradepkg the slackpack, you will lose your package_description if there is no package_description within the slackpack. *apologies*

i felt so bad that i worked on that crappy script again. :)
when there is no package_description now, it will default to look at the /usr/doc entries in the slackpack var file for the version info because that is actually a standard also. i think the script should work now for @ least 95% of released SlackPacks (both official and contributed)...

http://www.skweegie.f2s.com/huh/verpack

mind giving me 1 more chance ryeker?? :)

ssadams
02-02-2001, 06:38 PM
it is current.I dont know if its this tread or my fscken eyes,but I could sware your output said 2.1.2 and not 2.2.1 Funny thing is I should either were my glasses or get checked by a Doctor for some ailment :) I think I wont post on this thread anymore just to be safe. :D

Ryeker
02-02-2001, 08:26 PM
Skweegie, it works great! Thanks! Give you one more chance, what do you mean? You're the one helping me. Thank YOU! Oh, where did you get autoslack?

ssadams, lol!! I do that all the time myself. Don't worry about it. I ain't anal... :)

[ 02 February 2001: Message edited by: Ryeker ]