> On 9 Aug 2022, at 15:10, Fernando Santagata <nando.santag...@gmail.com> wrote:
>
> On Tue, Aug 9, 2022 at 2:13 PM Elizabeth Mattijsen <l...@dijkmat.nl> wrote:
> > On 9 Aug 2022, at 13:53, Fernando Santagata <nando.santag...@gmail.com>
> > wrote:
> >
> > Hello,
> >
> > I'm trying to uninstall old versions of some modules; it looks like it's
> > working but in reality it isn't. For example, but it's not limited to just
> > this module:
> >
> > $ zef list --installed|grep CBOR
> > ===> Found via /opt/rakudo-pkg/share/perl6/core
> > ===> Found via /home/nando/.raku
> > CBOR::Simple:ver<0.1.1>:auth<zef:japhb>:api<0>
> > CBOR::Simple:ver<0.1.2>:auth<zef:japhb>
> >
> > $ zef uninstall 'CBOR::Simple:ver<0.1.1>:auth<zef:japhb>:api<0>'
> > ===> Uninstalled from /home/nando/.raku
> > CBOR::Simple:ver<0.1.1>:auth<zef:japhb>:api<0>
>
> What does
>
> raku -e 'use CBOR::Simple:ver<0.1.1>:auth<zef:japhb>:api<0>'
>
> say after you've done this? Does it still load, or does it give an error?
>
> $ raku -e 'use CBOR::Simple:ver<0.1.1>:auth<zef:japhb>:api<0>'
> ===SORRY!=== Error while compiling -e
> Could not open
> /home/nando/.raku/sources/983E0FAFB758220B170D33A30493A316F0805F75. Failed to
> stat file: no such file or directory
>
> at -e:1
>
> You're right, the listing is incorrect. Besides, trying to uninstall the
> module doesn't return any error.
Actually, no. If the module would have been truly uninstalled, the error would
have been something like:
% r 'use CBOR::Simple:ver<0.1.1>'
===SORRY!=== Error while compiling -e
Could not find CBOR::Simple:ver<0.1.1> in:
/Users/liz/.raku
/Users/liz/Github/rakudo/install/share/perl6/site
/Users/liz/Github/rakudo/install/share/perl6/vendor
/Users/liz/Github/rakudo/install/share/perl6/core
CompUnit::Repository::AbsolutePath<2276199768160>
CompUnit::Repository::NQP<2276123351056>
CompUnit::Repository::Perl5<2276123351096>
So it looks like the source is gone, but the "short" info might still be there.
> > It started when I was using Rakudo v2022.06, but I hoped that upgrading to
> > the next version would solve the problem. Alas, no luck.
>
> Did you create an issue for it? If not, how would anybody be able to know of
> your problem?
>
> I thought it was a local problem and I wanted to investigate it further, but
> so far had no chance to do it, so I tried and see if it was a known issue.
> I've just submitted an issue.
Thanks!
Liz
