Has anyone else been having problems with swaret and recent -current?

I've updated my -current directory - loads of new files as per the changelog -
but swaret insists that all my packages are up-to-date! This is patently
untrue! Eg: installed - vim-6.2.98 available: vim-6.2.263

Nothing has been changed here since it last worked OK!

Anyone know what's broken? (this is happening on more than one machine which
makes me suspect that its not me - but I *could* be wrong ;-)

--
Pete
christy@NOattglobalSPAM.net
(make the obvious amendments to reply!)

Peter Christy wrote:

> Has anyone else been having problems with swaret and recent -current?
>
> I've updated my -current directory - loads of new files as per the changelog -
> but swaret insists that all my packages are up-to-date! This is patently
> untrue! Eg: installed - vim-6.2.98 available: vim-6.2.263
>
> Nothing has been changed here since it last worked OK!
>
> Anyone know what's broken? (this is happening on more than one machine which
> makes me suspect that its not me - but I *could* be wrong ;-)
>

Check http://www.swaret.org/ , a patch was released yesterday due to the
changed FILELIST format

Regards,
Denis

Peter Christy wrote:

> Has anyone else been having problems with swaret and recent -current?
>
> I've updated my -current directory - loads of new files as per the
> changelog - but swaret insists that all my packages are up-to-date! This
> is patently
> untrue! Eg: installed - vim-6.2.98 available: vim-6.2.263
>
> Nothing has been changed here since it last worked OK!
>
> Anyone know what's broken? (this is happening on more than one machine
> which makes me suspect that its not me - but I *could* be wrong ;-)
>

Yes, i have the same problems with swaret 1.6.1.
1.6.0 doesn`t have these problems.
Sorry, don`t know what`s broken.

rintek

Denis A. Kaledin wrote:


> Check http://www.swaret.org/ , a patch was released yesterday due to the
> changed FILELIST format
>

I patched it yesterday but i didn`t help

rintek

Denis A. Kaledin wrote:

> Check http://www.swaret.org/ , a patch was released yesterday due to the
> changed FILELIST format

Thanks for the tip, but it hasn't worked for me either!

--
Pete
christy@NOattglobalSPAM.net
(make the obvious amendments to reply!)

rintek wrote:


> Yes, i have the same problems with swaret 1.6.1.
> 1.6.0 doesn`t have these problems.
> Sorry, don`t know what`s broken.
>
> rintek

Once again, 1.6.1-3 fixes the problem. Make sure you delete the contents
of /var/swaret before you proceed to `swaret --update` with 1.6.1.-3

Regards,
Denis

On Wed, 18 Feb 2004 17:35:07 +0300, Denis A. Kaledin <hannibal@nline.ru> wrote:
> Peter Christy wrote:
>
>> Has anyone else been having problems with swaret and recent -current?
>>
>
> Check http://www.swaret.org/ , a patch was released yesterday due to the
> changed FILELIST format
>
> Regards,
> Denis

Thanks Denis! :-)

--
Ken P
k@kgab.org

Denis A. Kaledin wrote:

> Once again, 1.6.1-3 fixes the problem. Make sure you delete the contents
> of /var/swaret before you proceed to `swaret --update` with 1.6.1.-3

Nope! *Still* doesn't work :-(

--
Pete
christy@NOattglobalSPAM.net
(make the obvious amendments to reply!)

Peter Christy wrote:

> Has anyone else been having problems with swaret and recent -current?
>
> I've updated my -current directory - loads of new files as per the
> changelog - but swaret insists that all my packages are up-to-date! This
> is patently
> untrue! Eg: installed - vim-6.2.98 available: vim-6.2.263
>
> Nothing has been changed here since it last worked OK!
>
> Anyone know what's broken? (this is happening on more than one machine
> which makes me suspect that its not me - but I *could* be wrong ;-)
>

I have no problems with slackware-current, but I do with swaret. I didn't
ever try swaret again after my first bad experience.

--
Adore, v.:
To venerate expectantly.
-- Ambrose Bierce, "The Devil's Dictionary"

On Wed, 18 Feb 2004 12:54:50 -0700, NeoSadist wrote:


> I have no problems with slackware-current, but I do with swaret. I didn't
> ever try swaret again after my first bad experience.

Same here. I tried it after a fresh 9.1 install/upgrade. It hosed my
system. Now I only use to check what's available, but do any downloading
and installing by hand. I may try it again in a year or so, but all in all
the thing strikes me as going against the spirit of Slackware anyway.