upgrading slackware with swaret

upgrading slackware with swaret

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all slackers and everyone else.

I've got a box running slackware 9.1 here, that I didn't have time to
upgrade before, but have gotten around to wanting to upgrade it to
slack 10.1 now. I am trying to do this with swaret 1.3.1, which came
as an extra package in slack 9.1. My swaret.conf file is fine, since I
used it last time to upgrade to slackware 9.1. So, I just changed the
slackware version number in there from 9.1, to 10.1, and mounted the
first slackware cd under /cdrom, where swaret expects to find all the
packages, as I've configured it to do.

I run 

swaret --update

, and it compiles all the checksums, file lists, ETC, ETC, ETC, and
everything runs just fine. Then, I do

swaret --up-all -A

, and swaret tells me that all my installed packages are up to date,
which is obviously not the case. So, does anyone know what gives?
Should I first perhaps upgrade swaret using the standard slackware
upgradepkg tool, or is swaret simply not used to upgrade anymore? Any
informative input would be appreciated. Thanks in advance.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFCUE6J7s9z/XlyUyARAmMlAJ9x/txienM2pezwFA/1QEO9D5SpjgCfbhd7
DLqFDfr8EoI/w1HLi3mOZlk=
=72LX
-----END PGP SIGNATURE-----

Re: upgrading slackware with swaret

[Joseph C. Lininger]

Greg,
You need a newer version of swaret. The format of the files it reads has
changed, so that will happen if you aren't using the latest version.

Equal causes can produce very unequal effects.
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7

And so it came to pass that on Sun, 3 Apr 2005, Gregory Nowak said

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all slackers and everyone else.
>
> I've got a box running slackware 9.1 here, that I didn't have time to
> upgrade before, but have gotten around to wanting to upgrade it to
> slack 10.1 now. I am trying to do this with swaret 1.3.1, which came
> as an extra package in slack 9.1. My swaret.conf file is fine, since I
> used it last time to upgrade to slackware 9.1. So, I just changed the
> slackware version number in there from 9.1, to 10.1, and mounted the
> first slackware cd under /cdrom, where swaret expects to find all the
> packages, as I've configured it to do.
>
> I run
>
> swaret --update
>
> , and it compiles all the checksums, file lists, ETC, ETC, ETC, and
> everything runs just fine. Then, I do
>
> swaret --up-all -A
>
> , and swaret tells me that all my installed packages are up to date,
> which is obviously not the case. So, does anyone know what gives?
> Should I first perhaps upgrade swaret using the standard slackware
> upgradepkg tool, or is swaret simply not used to upgrade anymore? Any
> informative input would be appreciated. Thanks in advance.
>
> Greg
>
>
> - --
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFCUE6J7s9z/XlyUyARAmMlAJ9x/txienM2pezwFA/1QEO9D5SpjgCfbhd7
> DLqFDfr8EoI/w1HLi3mOZlk=
> =72LX
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: upgrading slackware with swaret

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Where can you find this later version and are the dependencies being
kept up to date? Slackware 10.0 and 10.1 do *NOT* have this utility anymore.

On Mon, Apr 04, 2005 at 12:48:00AM -0600, Joseph C. Lininger wrote:
> Greg,
> You need a newer version of swaret. The format of the files it reads has
> changed, so that will happen if you aren't using the latest version.
> 
> Equal causes can produce very unequal effects.
> Joseph C. Lininger
> jbahm@pcdesk.net
> Verification: 5eab38a77ac40416e075be8f50607ff7
> 
> And so it came to pass that on Sun, 3 Apr 2005, Gregory Nowak said
> 
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Hi all slackers and everyone else.
> >
> >I've got a box running slackware 9.1 here, that I didn't have time to
> >upgrade before, but have gotten around to wanting to upgrade it to
> >slack 10.1 now. I am trying to do this with swaret 1.3.1, which came
> >as an extra package in slack 9.1. My swaret.conf file is fine, since I
> >used it last time to upgrade to slackware 9.1. So, I just changed the
> >slackware version number in there from 9.1, to 10.1, and mounted the
> >first slackware cd under /cdrom, where swaret expects to find all the
> >packages, as I've configured it to do.
> >
> >I run
> >
> >swaret --update
> >
> >, and it compiles all the checksums, file lists, ETC, ETC, ETC, and
> >everything runs just fine. Then, I do
> >
> >swaret --up-all -A
> >
> >, and swaret tells me that all my installed packages are up to date,
> >which is obviously not the case. So, does anyone know what gives?
> >Should I first perhaps upgrade swaret using the standard slackware
> >upgradepkg tool, or is swaret simply not used to upgrade anymore? Any
> >informative input would be appreciated. Thanks in advance.
> >
> >Greg
> >
> >
> >- --
> >web site: http://www.romuald.net.eu.org
> >gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> >skype: gregn1
> >(authorization required, add me to your contacts list first)
> >
> >- --
> >Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.2.3 (GNU/Linux)
> >
> >iD8DBQFCUE6J7s9z/XlyUyARAmMlAJ9x/txienM2pezwFA/1QEO9D5SpjgCfbhd7
> >DLqFDfr8EoI/w1HLi3mOZlk=
> >=72LX
> >-----END PGP SIGNATURE-----
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFCUaLcWSjv55S0LfERA9rBAJ4/4thiQo5eLjJwGARuOqLl9nUikQCfdJn6
d4UyWJlY2ZKpjYk+gTqLWXo=
=R3Si
-----END PGP SIGNATURE-----

Re: upgrading slackware with swaret

[Sean McMahon]

So the slackware upgrade tool won't upgrade itself?  Another reason I guess why
I like my favorate distro.
----- Original Message ----- 
From: "Steve Holmes" <steve@holmesgrown.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, April 04, 2005 1:26 PM
Subject: Re: upgrading slackware with swaret


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> Where can you find this later version and are the dependencies being
> kept up to date? Slackware 10.0 and 10.1 do *NOT* have this utility anymore.
>
> On Mon, Apr 04, 2005 at 12:48:00AM -0600, Joseph C. Lininger wrote:
> > Greg,
> > You need a newer version of swaret. The format of the files it reads has
> > changed, so that will happen if you aren't using the latest version.
> >
> > Equal causes can produce very unequal effects.
> > Joseph C. Lininger
> > jbahm@pcdesk.net
> > Verification: 5eab38a77ac40416e075be8f50607ff7
> >
> > And so it came to pass that on Sun, 3 Apr 2005, Gregory Nowak said
> >
> > >-----BEGIN PGP SIGNED MESSAGE-----
> > >Hash: SHA1
> > >
> > >Hi all slackers and everyone else.
> > >
> > >I've got a box running slackware 9.1 here, that I didn't have time to
> > >upgrade before, but have gotten around to wanting to upgrade it to
> > >slack 10.1 now. I am trying to do this with swaret 1.3.1, which came
> > >as an extra package in slack 9.1. My swaret.conf file is fine, since I
> > >used it last time to upgrade to slackware 9.1. So, I just changed the
> > >slackware version number in there from 9.1, to 10.1, and mounted the
> > >first slackware cd under /cdrom, where swaret expects to find all the
> > >packages, as I've configured it to do.
> > >
> > >I run
> > >
> > >swaret --update
> > >
> > >, and it compiles all the checksums, file lists, ETC, ETC, ETC, and
> > >everything runs just fine. Then, I do
> > >
> > >swaret --up-all -A
> > >
> > >, and swaret tells me that all my installed packages are up to date,
> > >which is obviously not the case. So, does anyone know what gives?
> > >Should I first perhaps upgrade swaret using the standard slackware
> > >upgradepkg tool, or is swaret simply not used to upgrade anymore? Any
> > >informative input would be appreciated. Thanks in advance.
> > >
> > >Greg
> > >
> > >
> > >- --
> > >web site: http://www.romuald.net.eu.org
> > >gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> > >skype: gregn1
> > >(authorization required, add me to your contacts list first)
> > >
> > >- --
> > >Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> > >-----BEGIN PGP SIGNATURE-----
> > >Version: GnuPG v1.2.3 (GNU/Linux)
> > >
> > >iD8DBQFCUE6J7s9z/XlyUyARAmMlAJ9x/txienM2pezwFA/1QEO9D5SpjgCfbhd7
> > >DLqFDfr8EoI/w1HLi3mOZlk=
> > >=72LX
> > >-----END PGP SIGNATURE-----
> > >
> > >_______________________________________________
> > >Speakup mailing list
> > >Speakup@braille.uwo.ca
> > >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
>
> - -- 
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.7 (GNU/Linux)
>
> iD8DBQFCUaLcWSjv55S0LfERA9rBAJ4/4thiQo5eLjJwGARuOqLl9nUikQCfdJn6
> d4UyWJlY2ZKpjYk+gTqLWXo=
> =R3Si
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: upgrading slackware with swaret

[Adam Myrow]

On Mon, 4 Apr 2005, Sean McMahon wrote:

> So the slackware upgrade tool won't upgrade itself?  Another reason I guess why
> I like my favorate distro.

I've done upgrades with upgradepkg, which is part of Slackware.  The first 
CD usually has a file called "upgrade.txt" which explains the procedure, 
but it's a fairly manual procedure.  Slackware has always been closer to a 
"do it yourself" distribution than others.  I usually prefer to wipe out 
everything and do a clean install, then restore what I need from backups. 
I find that if I don't, I end up with a lot of crud I no longer need.  For 
example, older versions of Slackware didn't have GPG, so I had installed 
it myself.  It was easier for me to just start over rather than upgrade 
over the top of the existing system, then try and remove the old GPG files 
from my own build.  Similarly, Slackware now includes a program called 
pinepgp, which is a GPG/PGP filter to be added to Pine.  I had previously 
used one called Magicpgp, and when I did a fresh install of Slackware 
10.1, I dumped Magicpgp and switched to Pinepgp, which has a nice install 
script.  So, I don't mind doing things manually, because I got started 
with Slackware, and when they made Speakup part of their standard install, 
I decided to stick with them.  I suppose that if I'd started with Redhat 
or Fedora, and gotten used to it, I'd be annoyed at Slackware.

Re: upgrading slackware with swaret

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

It was dropped even with 10.0.  I was really sorry to see it go as
there really isn't anything else in its place.  I didn't get to do a
whole lot with it when I did use it but it looked interesting and I
thought promising.

On Sun, Apr 03, 2005 at 03:14:01PM -0500, Gregory Nowak wrote:
> Hi all slackers and everyone else.
> 
> I've got a box running slackware 9.1 here, that I didn't have time to
> upgrade before, but have gotten around to wanting to upgrade it to
> slack 10.1 now. I am trying to do this with swaret 1.3.1, which came
> as an extra package in slack 9.1. My swaret.conf file is fine, since I
> used it last time to upgrade to slackware 9.1. So, I just changed the
> slackware version number in there from 9.1, to 10.1, and mounted the
> first slackware cd under /cdrom, where swaret expects to find all the
> packages, as I've configured it to do.
> 
> I run 
> 
> swaret --update
> 
> , and it compiles all the checksums, file lists, ETC, ETC, ETC, and
> everything runs just fine. Then, I do
> 
> swaret --up-all -A
> 
> , and swaret tells me that all my installed packages are up to date,
> which is obviously not the case. So, does anyone know what gives?
> Should I first perhaps upgrade swaret using the standard slackware
> upgradepkg tool, or is swaret simply not used to upgrade anymore? Any
> informative input would be appreciated. Thanks in advance.
> 
> Greg
> 
> 
> -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
> 
> --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFCUaJ3WSjv55S0LfERA8+oAJ4trISYL4cknHZ9PQLZdd+PFdXcrwCfXpZE
wgQzDE+L/d6C3JeJAvLpVAo=
=YVwH
-----END PGP SIGNATURE-----

Re: upgrading slackware with swaret

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I noticed that after Joseph's message, and located slackpkg in the
extras directory instead. Slackpkg isn't bad, except for the annoying
problem of not being able to upgrade everything all at once like you
could do with swaret. My solution is to invoke slackpkg 26 times, per
each letter of the alphabet for each group of packages
(I.E. slackware, gnome, extras, pasture). Using up-arrow with
backspace and then enter once you've typed in the next letter means
that it's not as tedious as it could be, but it's still a pain. I'm
still upgrading as I write, so we'll see what I end up with after I
reboot. The up-shot to slackpkg is that it requires far less
configuration then swaret did, but I still think I liked swaret
better then slackpkg, that maybe because I was very impressed with it
when upgrading to 9.1 the last time.
I also liked the fact that swaret could upgrade certain packages
before any others (I.E. upgrade glibc and friends, then pkgtools, then
everything else). If you're not mindful of giving the packages to
upgrade to slackpkg in that particular order, you run into problems.

Greg


On Mon, Apr 04, 2005 at 01:24:24PM -0700, Steve Holmes wrote:
> It was dropped even with 10.0.  I was really sorry to see it go as
> there really isn't anything else in its place.  I didn't get to do a
> whole lot with it when I did use it but it looked interesting and I
> thought promising.
> 

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFCUabn7s9z/XlyUyARAiVHAJ42C/wPx8vT9tFn8kjxfsHo1spxZACgy2UE
l5/YceMHQXMlIYh9imTrtCw=
=qD7+
-----END PGP SIGNATURE-----