Re: Bug#133631: A normal user can use libapt

[Ayose <colario@softhome.net>]

El sáb, 16-02-2002 a las 18:52, Jason Gunthorpe escribió:
> 
> On 16 Feb 2002, Ayose wrote:
> 
> > Reading Package Lists... Error!
> > E: Unable to write mmap - msync (2 No such file or directory)
> > E: The package lists or status file could not be parsed or opened.
> 
> Erm, there is something wrong with your environment, I don't think the
> above is actually documented by SUS to ever happen..

Well, Now apt-get works fine for me :-)

How? I saw that the error was produced in msync(2), so I went to the
source and add "return true" at the begin of MMap::Sync() and
MMap::Sync(unsigned long Start,unsigned long Stop). Now, msync(2) is
disabled, because its code is never executed; however, apt-* works as
well as before :-)

As normal user, I can use apt- perfectly, but as root, I must set
LD_LIBRARY_PATH to /home/setepo/bin/apt-0.5.4/bin:$PATH, thus, apt-get
will use my modified version of libapt.

Maybe I was wrong and this was never a bug, but I am almost like in the
beginning, but now I can use apt. ;-)

Please, if you think that this is solved, close this bug.

This is a small test that apt only works fine with my version of libapt:

<code>
# apt-cache dump | wc -l
      0
# export LD_LIBRARY_PATH=/home/setepo/bin/apt-0.5.4/bin/:$PATH
# apt-cache dump | wc -l
  76992
# 
</code>


Best regards

-- 
Ayose Cazorla León
Debian GNU/Linux - setepo