From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: upgrading slackware with swaret
Date: Mon, 4 Apr 2005 00:48:00 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <Pine.WNT.4.62.0504040047270.2264@merlin> (raw)
In-Reply-To: <20050403201401.GA9059@romuald.net.eu.org>
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
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Joseph C. Lininger [this message]
` Steve Holmes
` Sean McMahon
` Adam Myrow
` Steve Holmes
` Gregory Nowak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.WNT.4.62.0504040047270.2264@merlin \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).