Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
14.1: slackpkg
102 views
Skip to first unread message
Frank P. Westlake
Mar 26, 2014, 9:28:55 AM3/26/14
to
I'm still very new to Linux.
I just ran 'slackpkg update' for the first time and it worked for
several minutes and appeared to be downloading packages for upgrade.
When that finished I ran 'slackpkg upgrade-all' and it printed a list of
packages that fell off the edge of my output buffer, so I ran it again
through 'more'. The top of the list had a comment that I had some
duplicate packages, and at the bottom it asked me "remove, blacklist,
ignore".
It seemed to me that it was telling me that all of these update packages
had somehow been downloaded twice and that I could either fix that or
ignore it, so I chose the option to delete duplicate packages. While it
was deleting I saw that paths in /usr/share/...', etc., were being
deleted so I cancelled the operation because it seemed that it might be
uninstalling everything on my system.
Will someone please tell me if this is proper, or have I done it wrong?
My desire is to update my system with the latest releases and fixes.
Frank
I just ran 'slackpkg update' for the first time and it worked for
several minutes and appeared to be downloading packages for upgrade.
When that finished I ran 'slackpkg upgrade-all' and it printed a list of
packages that fell off the edge of my output buffer, so I ran it again
through 'more'. The top of the list had a comment that I had some
duplicate packages, and at the bottom it asked me "remove, blacklist,
ignore".
It seemed to me that it was telling me that all of these update packages
had somehow been downloaded twice and that I could either fix that or
ignore it, so I chose the option to delete duplicate packages. While it
was deleting I saw that paths in /usr/share/...', etc., were being
deleted so I cancelled the operation because it seemed that it might be
uninstalling everything on my system.
Will someone please tell me if this is proper, or have I done it wrong?
My desire is to update my system with the latest releases and fixes.
Frank
jeff g.
Mar 26, 2014, 5:12:19 PM3/26/14
to
On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
> I'm still very new to Linux.
>
> I just ran 'slackpkg update' for the first time and it worked for
> several minutes and appeared to be downloading packages for upgrade.
> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
> packages that fell off the edge of my output buffer, so I ran it again
> through 'more'. The top of the list had a comment that I had some
> duplicate packages, and at the bottom it asked me "remove, blacklist,
> ignore".
>
> It seemed to me that it was telling me that all of these update packages
> had somehow been downloaded twice and that I could either fix that or
> ignore it, so I chose the option to delete duplicate packages. While it
> was deleting I saw that paths in /usr/share/...', etc., were being
> deleted so I cancelled the operation because it seemed that it might be
> uninstalling everything on my system.
>
What made you think this? And it that were in fact correct, how are you
> I'm still very new to Linux.
>
> I just ran 'slackpkg update' for the first time and it worked for
> several minutes and appeared to be downloading packages for upgrade.
> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
> packages that fell off the edge of my output buffer, so I ran it again
> through 'more'. The top of the list had a comment that I had some
> duplicate packages, and at the bottom it asked me "remove, blacklist,
> ignore".
>
> It seemed to me that it was telling me that all of these update packages
> had somehow been downloaded twice and that I could either fix that or
> ignore it, so I chose the option to delete duplicate packages. While it
> was deleting I saw that paths in /usr/share/...', etc., were being
> deleted so I cancelled the operation because it seemed that it might be
> uninstalling everything on my system.
>
to know how much was deleted?
You /did/ tell it to remove, yes?
> Will someone please tell me if this is proper, or have I done it wrong?
on linux in general. But this thread I found has some info you may find
useful until someone else shows up with better input...
http://www.linuxquestions.org/questions/slackware-14/slackpkg-update-948349/
Frank P. Westlake
Mar 26, 2014, 8:01:39 PM3/26/14
to
On 03/26/2014 02:12 PM, jeff g. wrote:
> On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
>> I'm still very new to Linux.
>>
>> I just ran 'slackpkg update' for the first time and it worked for
>> several minutes and appeared to be downloading packages for upgrade.
>> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
>> packages that fell off the edge of my output buffer, so I ran it again
>> through 'more'. The top of the list had a comment that I had some
>> duplicate packages, and at the bottom it asked me "remove, blacklist,
>> ignore".
>>
>> It seemed to me that it was telling me that all of these update packages
>> had somehow been downloaded twice and that I could either fix that or
>> ignore it, so I chose the option to delete duplicate packages. While it
>> was deleting I saw that paths in /usr/share/...', etc., were being
>> deleted so I cancelled the operation because it seemed that it might be
>> uninstalling everything on my system.
> What made you think this?
There are a lot of thunks up there so I don't know which you asked about.
> On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
>> I'm still very new to Linux.
>>
>> I just ran 'slackpkg update' for the first time and it worked for
>> several minutes and appeared to be downloading packages for upgrade.
>> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
>> packages that fell off the edge of my output buffer, so I ran it again
>> through 'more'. The top of the list had a comment that I had some
>> duplicate packages, and at the bottom it asked me "remove, blacklist,
>> ignore".
>>
>> It seemed to me that it was telling me that all of these update packages
>> had somehow been downloaded twice and that I could either fix that or
>> ignore it, so I chose the option to delete duplicate packages. While it
>> was deleting I saw that paths in /usr/share/...', etc., were being
>> deleted so I cancelled the operation because it seemed that it might be
>> uninstalling everything on my system.
> What made you think this?
> And it that were in fact correct, how are you to know how much was
> deleted?
cancelled the process.
> You /did/ tell it to remove, yes?
>> It seemed to me that it was telling me that all of these update
>> packages had somehow been downloaded twice and that I could either
>> fix that or ignore it, so I chose the option to delete duplicate
>> packages.
I am hoping for clarification of what was actually being deleted:
>> packages had somehow been downloaded twice and that I could either
>> fix that or ignore it, so I chose the option to delete duplicate
>> packages.
packages of files awaiting installation
or
packages which have been installed.
Frank
jeff g.
Mar 26, 2014, 11:19:54 PM3/26/14
to
On 03/26/2014 05:01 PM, Frank P. Westlake wrote:
> On 03/26/2014 02:12 PM, jeff g. wrote:
>> On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
>>> I'm still very new to Linux.
>>>
>>> I just ran 'slackpkg update' for the first time and it worked for
>>> several minutes and appeared to be downloading packages for upgrade.
>>> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
>>> packages that fell off the edge of my output buffer, so I ran it again
>>> through 'more'. The top of the list had a comment that I had some
>>> duplicate packages, and at the bottom it asked me "remove, blacklist,
>>> ignore".
>>>
>>> It seemed to me that it was telling me that all of these update packages
>>> had somehow been downloaded twice and that I could either fix that or
>>> ignore it, so I chose the option to delete duplicate packages. While it
>>> was deleting I saw that paths in /usr/share/...', etc., were being
>>> deleted so I cancelled the operation because it seemed that it might be
>>> uninstalling everything on my system.
>
>> What made you think this?
>
> There are a lot of thunks up there so I don't know which you asked about.
>
I asked about your statement /directly/ above my question, which is why
> On 03/26/2014 02:12 PM, jeff g. wrote:
>> On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
>>> I'm still very new to Linux.
>>>
>>> I just ran 'slackpkg update' for the first time and it worked for
>>> several minutes and appeared to be downloading packages for upgrade.
>>> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
>>> packages that fell off the edge of my output buffer, so I ran it again
>>> through 'more'. The top of the list had a comment that I had some
>>> duplicate packages, and at the bottom it asked me "remove, blacklist,
>>> ignore".
>>>
>>> It seemed to me that it was telling me that all of these update packages
>>> had somehow been downloaded twice and that I could either fix that or
>>> ignore it, so I chose the option to delete duplicate packages. While it
>>> was deleting I saw that paths in /usr/share/...', etc., were being
>>> deleted so I cancelled the operation because it seemed that it might be
>>> uninstalling everything on my system.
>
>> What made you think this?
>
> There are a lot of thunks up there so I don't know which you asked about.
>
I put the question there.
>> And it that were in fact correct, how are you to know how much was
>> deleted?
>
> I don't know how much. I only know that it wasn't all of it because I
> cancelled the process.
>
>
>> You /did/ tell it to remove, yes?
>
> Answer:
>>> It seemed to me that it was telling me that all of these update
>>> packages had somehow been downloaded twice and that I could either
>>> fix that or ignore it, so I chose the option to delete duplicate
>>> packages.
>
> I am hoping for clarification of what was actually being deleted:
>
> packages of files awaiting installation
>
> or
>
> packages which have been installed.
packages?
That sounds straightforward to me - you haven't indicated yet why you
think otherwise. It goes against rational thinking that there would be
duplicate installs - that is why the install program is asking.
Chick Tower
Mar 28, 2014, 2:00:25 PM3/28/14
to
On 2014-03-27, Frank P. Westlake wrote:
> I am hoping for clarification of what was actually being deleted:
>
> packages of files awaiting installation
>
> or
>
> packages which have been installed.
Oh, it didn't strike me that way in your original post, but now what you
> I am hoping for clarification of what was actually being deleted:
>
> packages of files awaiting installation
>
> or
>
> packages which have been installed.
saw makes sense, even though I've never used slackpkg.
When I upgrade a package, using the upgradepkg tool, it usually deletes
the files from the old package first and then installs the new package.
It lists those files it's deleting. Perhaps that is what you saw.
--
Chick Tower
For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
frank.w...@gmail.com
Mar 28, 2014, 2:07:52 PM3/28/14
to
From Chick Tower :
to me that 'slackpkg' would delete entire installations
before applying the upgrades; I guess I assumed it would
only make necessary changes.
But I don't think that explains the 'delete duplicates'
part; unless after I answered the question to delete
duplicates it proceded directly to the upgrade and
duplicates were to be deleted either during or after the
upgrade.
It might be that having duplicates is rare and the
author of 'slackpkg' assumed that I would have seen a
normal upgrade before having to deal with duplicates, so
there would not have been any confusion. But I am still
confused.
Frank
>When I upgrade a package, using the upgradepkg tool, it
>usually deletes
>the files from the old package first and then installs
>the new package.
>It lists those files it's deleting. Perhaps that is
>what you saw.
Thank you very much for the information. It didn't occur
>usually deletes
>the files from the old package first and then installs
>the new package.
>It lists those files it's deleting. Perhaps that is
>what you saw.
to me that 'slackpkg' would delete entire installations
before applying the upgrades; I guess I assumed it would
only make necessary changes.
But I don't think that explains the 'delete duplicates'
part; unless after I answered the question to delete
duplicates it proceded directly to the upgrade and
duplicates were to be deleted either during or after the
upgrade.
It might be that having duplicates is rare and the
author of 'slackpkg' assumed that I would have seen a
normal upgrade before having to deal with duplicates, so
there would not have been any confusion. But I am still
confused.
Frank
Frank P. Westlake
Mar 30, 2014, 8:51:15 AM3/30/14
to
On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
> I just ran 'slackpkg update' for the first time and it worked for
> several minutes and appeared to be downloading packages for upgrade.
> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
> packages that fell off the edge of my output buffer, so I ran it again
> through 'more'. The top of the list had a comment that I had some
> duplicate packages, and at the bottom it asked me "remove, blacklist,
> ignore".
This is the actual output:
> several minutes and appeared to be downloading packages for upgrade.
> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
> packages that fell off the edge of my output buffer, so I ran it again
> through 'more'. The top of the list had a comment that I had some
> duplicate packages, and at the bottom it asked me "remove, blacklist,
> ignore".
-----------------------------------------------
/usr:# slackpkg upgrade-all
Checking local integrity... DONE
You have a broken /var/log/packages - with two versions of the
same package.
The list of packages duplicated in your machine are shown below,
but don't worry about this list - when you select your action,
slackpkg will show a better list:
ModemManager-0.5.2.0-x86_64-1
ModemManager-1.0.0-x86_64-2
NetworkManager-0.9.4.0-x86_64-2
NetworkManager-0.9.8.8-x86_64-1
PyQt-4.9.1-x86_64-3
PyQt-4.9.6-x86_64-1
-----------------------------------------------
Etcetera, for several hunderd. Then at the bottom of that output:
-----------------------------------------------
zlib-1.2.6-x86_64-1
zlib-1.2.8-x86_64-1
zsh-5.0.0-x86_64-1
zsh-5.0.2-x86_64-1
You can (B)lacklist, (R)emove, or (I)gnore these packages.
Select your action (B/R/I):
-----------------------------------------------
That list starts alphabetically with 'Mo' so it probably deleted 'A'
through 'Mo' the first time I ran it, until I was able to cancel it.
At the command line menu I select 'R' and I get a GUI menu listing the
same thing but allowing me to unselect packages. I leave it as it was
and choose 'OK'. Then I get this:
Package: ModemManager-0.5.2.0-x86_64-1
Removing...
Removing package /var/log/packages/ModemManager-0.5.2.0-x86_64-1...
Removing files:
--> /lib/udev/rules.d/77-mm-ericsson-mbm.rules was found in
another package. Skipping.
--> /lib/udev/rules.d/77-mm-longcheer-port-types.rules was found
in another package. Skipping.
-----------------------------------------------
Plus about 100 more like that, then continuing:
-----------------------------------------------
--> Deleting /etc/dbus-1/system.d/org.freedesktop.ModemManager.conf
--> Deleting /usr/doc/ModemManager-0.5.2.0/AUTHORS
--> Deleting /usr/doc/ModemManager-0.5.2.0/COPYING
--> Deleting /usr/doc/ModemManager-0.5.2.0/ChangeLog
--> Deleting /usr/doc/ModemManager-0.5.2.0/INSTALL
--> Deleting /usr/doc/ModemManager-0.5.2.0/ModemManager.SlackBuild
--> Deleting /usr/doc/ModemManager-0.5.2.0/NEWS
--> Deleting /usr/doc/ModemManager-0.5.2.0/README
--> Deleting /usr/include/mm/mm-modem.h
--> Deleting /usr/lib64/ModemManager/libmm-plugin-moto-c.a
--> Deleting /usr/lib64/ModemManager/libmm-plugin-moto-c.la
--> Deleting /usr/lib64/ModemManager/libmm-plugin-moto-c.so
--> Deleting /usr/lib64/pppd/2.4.5/mm-test-pppd-plugin.a
--> Deleting /usr/lib64/pppd/2.4.5/mm-test-pppd-plugin.la
--> Deleting /usr/lib64/pppd/2.4.5/mm-test-pppd-plugin.so
--> Deleting /usr/sbin/modem-manager
-----------------------------------------------
Plus about 100 more before I was able to hit CTRL-C.
Does anyone here recognize this behavior?
Frank
tarpit
Mar 30, 2014, 9:12:08 AM3/30/14
to
Frank P. Westlake wrote:
> On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
>> I just ran 'slackpkg update' for the first time and it worked for
>> several minutes and appeared to be downloading packages for upgrade.
>> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
>> packages that fell off the edge of my output buffer, so I ran it again
>> through 'more'. The top of the list had a comment that I had some
>> duplicate packages, and at the bottom it asked me "remove, blacklist,
>> ignore".
>
> This is the actual output:
> -----------------------------------------------
> /usr:# slackpkg upgrade-all
> Checking local integrity... DONE
> You have a broken /var/log/packages - with two versions of the
> same package.
> The list of packages duplicated in your machine are shown below,
> but don't worry about this list - when you select your action,
> slackpkg will show a better list:
>
> ModemManager-0.5.2.0-x86_64-1
> ModemManager-1.0.0-x86_64-2
> NetworkManager-0.9.4.0-x86_64-2
> NetworkManager-0.9.8.8-x86_64-1
> PyQt-4.9.1-x86_64-3
> PyQt-4.9.6-x86_64-1
[snip]
> On 03/26/2014 06:28 AM, Frank P. Westlake wrote:
>> I just ran 'slackpkg update' for the first time and it worked for
>> several minutes and appeared to be downloading packages for upgrade.
>> When that finished I ran 'slackpkg upgrade-all' and it printed a list of
>> packages that fell off the edge of my output buffer, so I ran it again
>> through 'more'. The top of the list had a comment that I had some
>> duplicate packages, and at the bottom it asked me "remove, blacklist,
>> ignore".
>
> This is the actual output:
> -----------------------------------------------
> /usr:# slackpkg upgrade-all
> Checking local integrity... DONE
> You have a broken /var/log/packages - with two versions of the
> same package.
> The list of packages duplicated in your machine are shown below,
> but don't worry about this list - when you select your action,
> slackpkg will show a better list:
>
> ModemManager-0.5.2.0-x86_64-1
> ModemManager-1.0.0-x86_64-2
> NetworkManager-0.9.4.0-x86_64-2
> NetworkManager-0.9.8.8-x86_64-1
> PyQt-4.9.1-x86_64-3
> PyQt-4.9.6-x86_64-1
The older versions of these packages are from 14.0 and the newer
versions are from 14.1. My guess is that you pointed slackpkg to the
wrong version.
--
To believe is to die.
Frank P. Westlake
Mar 30, 2014, 9:55:52 AM3/30/14
to
On 03/30/2014 06:12 AM, tarpit wrote:
> The older versions of these packages are from 14.0 and the newer
> versions are from 14.1. My guess is that you pointed slackpkg to the
> wrong version.
That wouldn't have been by any action I made. I installed Slackware 14.1
> The older versions of these packages are from 14.0 and the newer
> versions are from 14.1. My guess is that you pointed slackpkg to the
> wrong version.
as a new installation back in November and I had done nothing related to
packages until this recent attempt to upgrade. The only things I have
done in that regard are
slackpkg update
slackpkg upgrade-all
This system has never seen anything earlier than 14.1 and I don't recall
ever changing the version number in anything. My
/etc/slackpkg/slackpkg.conf, minus the comments:
TEMP=/var/cache/packages
WORKDIR=/var/lib/slackpkg
WGETFLAGS="--passive-ftp"
DELALL=on
CHECKMD5=on
CHECKGPG=on
CHECKSIZE=off
PRIORITY=( patches %PKGMAIN extra pasture testing )
POSTINST=on
ONLY_NEW_DOTNEW=off
ONOFF=on
DOWNLOAD_ALL=on
DIALOG=on
BATCH=off
DEFAULT_ANSWER=n
USE_INCLUDES=on
SPINNING=on
DIALOG_MAXARGS=139000
According to the man:
upgrade-all
This action upgrades every package installed on the system
to the version in the official Slackware tree; this is the
"good" way to upgrade the entire system.
Remember to use the "install-new" action before you use
"upgrade- all."
I didn't run 'install-new' but I installed it new as 14.1. But
'install-new' says:
install-new
This action installs any new packages that are added to
the official Slackware package set. Run this if you
are upgrading your system to another Slackware version or
if you are using -current.
I am not changing versions but 14.1 was 'current' when I downloaded and
installed it. I don't think that's what it means but I'm not sure.
Frank
tarpit
Mar 30, 2014, 11:57:49 AM3/30/14
to
It should be a 14.1 mirror, e.g.,
http://ftp.cc.swin.edu.au/slackware/slackware64-14.1/
Also, you might as well verify the contents of /etc/slackware-version.
From what you say you did, it should be
Slackware 14.1
I don't know exactly how you did it, but you have certainly convinced
Slackware's pkgtools that you installed both 14.0 and 14.1 versions of
most or all packages.
I would back up my data and reinstall since it is a fairly routine
task and less time consuming than attempting to fix it.
frank.w...@gmail.com
Mar 30, 2014, 6:30:14 PM3/30/14
to
From tarpit :
<ftp://mirrors.slackware.com:/slackware/slackware-14.1>.
The colon after the server name can't be right, maybe
that caused the problem.
>Also, you might as well verify the contents of
>/etc/slackware-version.
> From what you say you did, it should be
>Slackware 14.1
No file. 'find /etc -name *slack*' shows only
'slackpkg.conf' and some 'gtk-x.0' and 'pango'
subdirectories.
>I would back up my data and reinstall since it is a
>fairly routine
>task and less time consuming than attempting to fix it.
Too late. I don't have electricity at home and I was at
a place where my laptop would have electricity for three
hours so I made a quick decision to let 'slackpkg
upgrade-all' continue to do what it wanted. I figured
three hours would be enough, but it wasn't. When I had
to leave the electricity and WIFI I tried to hibernate
the laptop, but it would not suspend with that process
still active so I had to cancel the process. I've had
this problem several times before with failing to
hibernate while some applications are still active, and
I can't wait so I have to abort the processes. They may
have all been network related tasks.
Now at home on battery but with WIFI I find that
'network manager' will no longer let me (myself, not
root) control the WIFI system in Xfce. I assume that
this is because the disk files had already been deleted
and after restoring from hibernation they needed to be
read again. Packages were being actively downloaded
before the hibernation. I have not setup 'wicd' yet so I
don't think 'su' in a terminal will help.
I'll have to wait until Monday to see if the Ethernet
adapter will connect. If it doesn't I'll try
reinstalling everything from my USB-stick which has all
the 14.1 distribution on it. Having electricity for only
three hours per day makes problems such as this more
difficult.
Frank
>Check which mirror is selected (uncommented) in
>/etc/slackpkg/mirrors.
>It should be a 14.1 mirror, e.g.,
>http://ftp.cc.swin.edu.au/slackware/slackware64-14.1/
It's
>/etc/slackpkg/mirrors.
>It should be a 14.1 mirror, e.g.,
>http://ftp.cc.swin.edu.au/slackware/slackware64-14.1/
<ftp://mirrors.slackware.com:/slackware/slackware-14.1>.
The colon after the server name can't be right, maybe
that caused the problem.
>Also, you might as well verify the contents of
>/etc/slackware-version.
> From what you say you did, it should be
>Slackware 14.1
'slackpkg.conf' and some 'gtk-x.0' and 'pango'
subdirectories.
>I would back up my data and reinstall since it is a
>fairly routine
>task and less time consuming than attempting to fix it.
a place where my laptop would have electricity for three
hours so I made a quick decision to let 'slackpkg
upgrade-all' continue to do what it wanted. I figured
three hours would be enough, but it wasn't. When I had
to leave the electricity and WIFI I tried to hibernate
the laptop, but it would not suspend with that process
still active so I had to cancel the process. I've had
this problem several times before with failing to
hibernate while some applications are still active, and
I can't wait so I have to abort the processes. They may
have all been network related tasks.
Now at home on battery but with WIFI I find that
'network manager' will no longer let me (myself, not
root) control the WIFI system in Xfce. I assume that
this is because the disk files had already been deleted
and after restoring from hibernation they needed to be
read again. Packages were being actively downloaded
before the hibernation. I have not setup 'wicd' yet so I
don't think 'su' in a terminal will help.
I'll have to wait until Monday to see if the Ethernet
adapter will connect. If it doesn't I'll try
reinstalling everything from my USB-stick which has all
the 14.1 distribution on it. Having electricity for only
three hours per day makes problems such as this more
difficult.
Frank
frank.w...@gmail.com
Mar 30, 2014, 7:24:17 PM3/30/14
to
From frank.westlake:
problem might be due to the process running as root and
'pm-hibernate' running as a user.
Frank
When I had
>to leave the electricity and WIFI I tried to hibernate
>the laptop, but it would not suspend with that process
>still active so I had to cancel the process. I've had
>this problem several times before with failing to
>hibernate while some applications are still active, and
>I can't wait so I have to abort the processes. They may
>have all been network related tasks.
It just occurred to me that the 'fail to hibernate'
>to leave the electricity and WIFI I tried to hibernate
>the laptop, but it would not suspend with that process
>still active so I had to cancel the process. I've had
>this problem several times before with failing to
>hibernate while some applications are still active, and
>I can't wait so I have to abort the processes. They may
>have all been network related tasks.
problem might be due to the process running as root and
'pm-hibernate' running as a user.
Frank
Chick Tower
Mar 30, 2014, 7:48:22 PM3/30/14
to
On 2014-03-28, frank.westlake wrote:
> Thank you very much for the information. It didn't occur
> to me that 'slackpkg' would delete entire installations
> before applying the upgrades; I guess I assumed it would
> only make necessary changes.
>
> But I don't think that explains the 'delete duplicates'
> part; unless after I answered the question to delete
> duplicates it proceded directly to the upgrade and
> duplicates were to be deleted either during or after the
> upgrade.
>
> It might be that having duplicates is rare and the
> author of 'slackpkg' assumed that I would have seen a
> normal upgrade before having to deal with duplicates, so
> there would not have been any confusion. But I am still
> confused.
The Slackware packages that are upgrades or security patches are
> Thank you very much for the information. It didn't occur
> to me that 'slackpkg' would delete entire installations
> before applying the upgrades; I guess I assumed it would
> only make necessary changes.
>
> But I don't think that explains the 'delete duplicates'
> part; unless after I answered the question to delete
> duplicates it proceded directly to the upgrade and
> duplicates were to be deleted either during or after the
> upgrade.
>
> It might be that having duplicates is rare and the
> author of 'slackpkg' assumed that I would have seen a
> normal upgrade before having to deal with duplicates, so
> there would not have been any confusion. But I am still
> confused.
complete packages in themselves, not just modifications to previous
versions of the program. I assume that's why upgrading deletes the old
files before installing the new. In my experience the process doesn't
change configuration files, so, for example, you keep all your settings
and cookies when upgrading from one version of Firefox to the next.
As I said, I've never used slackpkg, so I can't tell you anything about
"duplicates".
frank.w...@gmail.com
Apr 1, 2014, 4:51:39 PM4/1/14
to
From frank.westlake:
>Too late. ... I made a quick decision to let 'slackpkg
until it deleted '/usr/bin/rm' and it was no longer able
to delete anything, then it just spit out error reports
until I put it out of its misery. I was left without ls,
rm, cat, fdisk, and all the other essentials. I had to
use 'find .' and 'echo *' for directory listings and
'nano' to view files.
I copied '/usr/bin' from elsewhere so now I feel like
I'll beat this thing. I copied all the 14.1 packages to
'/usr/slackware64'. I have 'slackpkg' but not 'setup', I
don't know what else can be used. I have an Android for
Internet communications. I have a finicky 64GB USB stick
with all of the 14.1 release, but when I use it to boot
(an HP pre-boot selection) it transfers to the HD's file
system and experiences the missing files. I haven't
tried it with '/usr/bin' full again, but there are other
needed files missing too.
How do I reinstall all these packages? My data is still
safe on the HD and on a backup. I could examine the
'slackpkg' script and figure out what to do from it, but
that kind of research could extend this interlude
unreasonably.
Maybe I can learn how to properly upgrage my system
while I'm doing this. The mirror link
<ftp://mirrors.slackware.com:/slackware/slackware-14.1>
has been fixed (colon #2 removed).
'/etc/slackware-version' is still missing -- how is it
supposed to be formatted?
Frank
>Too late. ... I made a quick decision to let 'slackpkg
>upgrade-all' continue to do what it wanted.
'slackpkg' destroyed my system. It continued deleting
until it deleted '/usr/bin/rm' and it was no longer able
to delete anything, then it just spit out error reports
until I put it out of its misery. I was left without ls,
rm, cat, fdisk, and all the other essentials. I had to
use 'find .' and 'echo *' for directory listings and
'nano' to view files.
I copied '/usr/bin' from elsewhere so now I feel like
I'll beat this thing. I copied all the 14.1 packages to
'/usr/slackware64'. I have 'slackpkg' but not 'setup', I
don't know what else can be used. I have an Android for
Internet communications. I have a finicky 64GB USB stick
with all of the 14.1 release, but when I use it to boot
(an HP pre-boot selection) it transfers to the HD's file
system and experiences the missing files. I haven't
tried it with '/usr/bin' full again, but there are other
needed files missing too.
How do I reinstall all these packages? My data is still
safe on the HD and on a backup. I could examine the
'slackpkg' script and figure out what to do from it, but
that kind of research could extend this interlude
unreasonably.
Maybe I can learn how to properly upgrage my system
while I'm doing this. The mirror link
<ftp://mirrors.slackware.com:/slackware/slackware-14.1>
has been fixed (colon #2 removed).
'/etc/slackware-version' is still missing -- how is it
supposed to be formatted?
Frank
Henrik Carlqvist
Apr 2, 2014, 2:01:15 AM4/2/14
to
On Tue, 01 Apr 2014 20:51:39 +0000, frank.westlake wrote:
> 'slackpkg' destroyed my system.
Ouch. I have never used slackpkg, but if I ever will I will first make
sure to read up on how to use it properly.
> I was left without ls, rm, cat, fdisk, and all the other essentials. I
> had to use 'find .' and 'echo *' for directory listings and 'nano' to
> view files.
>
> I copied '/usr/bin' from elsewhere so now I feel like I'll beat this
> thing.
Doing so means that you have essential files on your system which are not
tracked by any packaging tool.
> I copied all the 14.1 packages to '/usr/slackware64'. I have
> 'slackpkg' but not 'setup',
Useful tools in situations like this are
installpkg
and
upgradepkg
However, those files are just scripts, relying on other things like rm,
basename and most of all tar-1.13.
> I don't know what else can be used. I have
> an Android for Internet communications. I have a finicky 64GB USB stick
> with all of the 14.1 release, but when I use it to boot (an HP pre-boot
> selection) it transfers to the HD's file system and experiences the
> missing files. I haven't tried it with '/usr/bin' full again, but there
> are other needed files missing too.
The best way to fix this is to boot frome some live or installation
media, mount all partitions and reinstall all packages.
> How do I reinstall all these packages? My data is still safe on the HD
> and on a backup. I could examine the 'slackpkg' script and figure out
> what to do from it, but that kind of research could extend this
> interlude unreasonably.
At this point I would stay away from slackpkg and rely on the basic
Slackware package management tools.
> '/etc/slackware-version' is still missing -- how is it supposed to be
> formatted?
You are supposed to get that file from the package aaa_base, you are not
supposed to write the file yourself.
From
http://pkgs.org/slackware-14.1/slackware-i486/aaa_base-14.1i486-1.txz.html
upgradepkg --install-new aaa_base-14.1-i486-1.txz
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
> 'slackpkg' destroyed my system.
Ouch. I have never used slackpkg, but if I ever will I will first make
sure to read up on how to use it properly.
> I was left without ls, rm, cat, fdisk, and all the other essentials. I
> had to use 'find .' and 'echo *' for directory listings and 'nano' to
> view files.
>
> I copied '/usr/bin' from elsewhere so now I feel like I'll beat this
> thing.
tracked by any packaging tool.
> I copied all the 14.1 packages to '/usr/slackware64'. I have
> 'slackpkg' but not 'setup',
installpkg
and
upgradepkg
However, those files are just scripts, relying on other things like rm,
basename and most of all tar-1.13.
> I don't know what else can be used. I have
> an Android for Internet communications. I have a finicky 64GB USB stick
> with all of the 14.1 release, but when I use it to boot (an HP pre-boot
> selection) it transfers to the HD's file system and experiences the
> missing files. I haven't tried it with '/usr/bin' full again, but there
> are other needed files missing too.
media, mount all partitions and reinstall all packages.
> How do I reinstall all these packages? My data is still safe on the HD
> and on a backup. I could examine the 'slackpkg' script and figure out
> what to do from it, but that kind of research could extend this
> interlude unreasonably.
Slackware package management tools.
> '/etc/slackware-version' is still missing -- how is it supposed to be
> formatted?
supposed to write the file yourself.
From
http://pkgs.org/slackware-14.1/slackware-i486/aaa_base-14.1i486-1.txz.html
upgradepkg --install-new aaa_base-14.1-i486-1.txz
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
frank.w...@gmail.com
Apr 2, 2014, 8:55:33 AM4/2/14
to
From Henrik Carlqvist:
right?
>Useful tools in situations like this are
>installpkg
>and
>upgradepkg
>upgradepkg --install-new aaa_base-14.1-i486-1.txz
Thank you very much Mr. Carlqvist -- that was sufficient
for me to get everything installed again.
>> '/etc/slackware-version' is still missing -- how is it
>>supposed to be formatted?
>You are supposed to get that file from the package
>aaa_base, you are not
>supposed to write the file yourself.
It has been restored (Slackware 14.1) along with
aaa_base. I wonder if perhaps 'slackpkg' deletes it when
it begins an upgrade and writes it when it completes. I
had cancelled 'slackpkg' with CTRL-C. I'll look at the
script after I finish restoring.
Frank
>> I copied '/usr/bin' from elsewhere so now I feel like
>>I'll beat this thing.
>Doing so means that you have essential files on your
>system which are not
>tracked by any packaging tool.
I ran 'installpkg' over them so they are tracked again,
>>I'll beat this thing.
>Doing so means that you have essential files on your
>system which are not
>tracked by any packaging tool.
right?
>Useful tools in situations like this are
>installpkg
>and
>upgradepkg
Thank you very much Mr. Carlqvist -- that was sufficient
for me to get everything installed again.
>> '/etc/slackware-version' is still missing -- how is it
>>supposed to be formatted?
>You are supposed to get that file from the package
>aaa_base, you are not
>supposed to write the file yourself.
aaa_base. I wonder if perhaps 'slackpkg' deletes it when
it begins an upgrade and writes it when it completes. I
had cancelled 'slackpkg' with CTRL-C. I'll look at the
script after I finish restoring.
Frank
Frank P. Westlake
Apr 2, 2014, 10:36:36 AM4/2/14
to
OK, it's all restored. Thank you very much 'tarpit' and Henrik Carlqvist
for your help and instruction.
Frank
for your help and instruction.
Frank
Henrik Carlqvist
Apr 2, 2014, 2:07:43 PM4/2/14
to
On Wed, 02 Apr 2014 12:55:33 +0000, frank.westlake wrote:
> I ran 'installpkg' over them so they are tracked again, right?
Yes, packages installed the proper way are listed as files in
> I ran 'installpkg' over them so they are tracked again, right?
/var/log/packages and the contents in those files among some comments and
package sizes are listings of what files the package installs.
Proplerly installed packages can be removed with removepkg or replaced by
another version with upgradepkg. The contents of the old package is
removed by examining the file listing in /var/log/packages/<packagename>.
> I wonder if perhaps 'slackpkg' deletes it when it begins an upgrade and
> writes it when it completes. I had cancelled 'slackpkg' with CTRL-C.
> I'll look at the script after I finish restoring.
when a package was removed. Maybe slackpkg was cancelled before it
installed the package which was supposed to replace the old package,
maybe slackpkg only decided to remove some package(s) without upgrading
them.
The script upgradepkg calls the script removepkg to remove the old
package before installing a new package.
Slackware packages are really simple. They are compressed tar files
containing all the files of the package. They might also contain a file
install/doinst.sh which is run at package installation.
Even though the packages are only simple tar files you should not create
your own custom packages with tar. Instead you should use makepkg for
that as that tool will help to make sure that permissions are OK and that
symbolic links are created by the install script and not unpacked from
the tar file.
frank.w...@gmail.com
Apr 2, 2014, 2:43:34 PM4/2/14
to
From Henrik Carlqvist:
It sure was nice back in '97 when I could read the
information about each package while it was being
installed; it served as a very good introduction to what
I had. I know it's in the file system somewhere to be
read, but I doubt that there are more then 2% who do. I
think this information could still serve us well if it
were added to the manpage system -- added and removed by
'installpkg' and 'removepkg'. When I get time to take a
close look at how packages are managed I might write a
couple of scripts to manage the mandocs for me.
Thanks bunchos[*]!
Frank
*Bunchos: A portmanteau of the English "bunch" and the
Spanish "muchos". I guess it could be said that "much"
has the same meaning, but from the words transposed
(muchos, bunch).
>They might also contain a file
>install/doinst.sh which is run at package installation.
I saw some of those flash by while installing packages.
>install/doinst.sh which is run at package installation.
It sure was nice back in '97 when I could read the
information about each package while it was being
installed; it served as a very good introduction to what
I had. I know it's in the file system somewhere to be
read, but I doubt that there are more then 2% who do. I
think this information could still serve us well if it
were added to the manpage system -- added and removed by
'installpkg' and 'removepkg'. When I get time to take a
close look at how packages are managed I might write a
couple of scripts to manage the mandocs for me.
Thanks bunchos[*]!
Frank
*Bunchos: A portmanteau of the English "bunch" and the
Spanish "muchos". I guess it could be said that "much"
has the same meaning, but from the words transposed
(muchos, bunch).
Kees Theunissen
Apr 2, 2014, 3:28:15 PM4/2/14
to
Henrik Carlqvist wrote:
> The script upgradepkg calls the script removepkg to remove the old
> package before installing a new package.
No. If you do it that way you risk to remove tools/libs that are
> The script upgradepkg calls the script removepkg to remove the old
> package before installing a new package.
needed to install the new package. Examples of that are upgrading
the "tar" package or the package tools.
"upgradepkg" copies the new package over the old one and removes after
that any file that was part of the old package and not of the new
package or any other installed package.
Regards,
Kees.
--
Kees Theunissen.
Henrik Carlqvist
Apr 3, 2014, 4:28:14 PM4/3/14
to
On Wed, 02 Apr 2014 21:28:15 +0200, Kees Theunissen wrote:
> Henrik Carlqvist wrote:
>> The script upgradepkg calls the script removepkg to remove the old
>> package before installing a new package.
>
> No. If you do it that way you risk to remove tools/libs that are needed
> to install the new package. Examples of that are upgrading the "tar"
> package or the package tools.
Whoops, you are right...
> Henrik Carlqvist wrote:
>> The script upgradepkg calls the script removepkg to remove the old
>> package before installing a new package.
>
> No. If you do it that way you risk to remove tools/libs that are needed
> to install the new package. Examples of that are upgrading the "tar"
> package or the package tools.
Upgradepkg calls removepkg on the (renamed) old package after
installation of the new package. That way only files unique for the old
package is removed as removepkg does not remove files which also exist
from another package.
0 new messages