Hi Mirosław,
I am working on getting a new, fixed version of Midori into Debian.
I agree with you that naming a directory suffixed with .so is unusual
and I thought so at first as well. However, once I thought about it, I
realized that this was done by the authors of Midori to allow the
configura
On 06/05/2012 at 08:14, "Yves-Alexis Perez" wrote:
> > What is more: how was
> >
> > rmdir /etc/xdg/midori/extensions/libadblock.so
> >
> > ever supposed to work? libadblock.so is obviously plain file,
>
> What does make you think that?
This:
#v+
# find / -xdev -type d -iname '*.so*'
/usr/sha
On dim., 2012-05-06 at 00:40 +0200, Mirosław Zalewski wrote:
> I can confirm report from jida...@jidanni.org - warning message is present
> even
> on fresh installation.
>
> What is more: how was
> rmdir /etc/xdg/midori/extensions/libadblock.so
> *ever* supposed to work? libadblock.so is obviou
I can confirm report from jida...@jidanni.org - warning message is present even
on fresh installation.
What is more: how was
rmdir /etc/xdg/midori/extensions/libadblock.so
*ever* supposed to work? libadblock.so is obviously plain file, while rmdir is
able to remove only empty directories. Even
We even see the warning on a 'vanilla' install:
# set midori
# aptitude purge $@ #runs fine
# aptitude install $@
The following NEW packages will be installed:
midori
0 packages upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/1,174 kB of archives. After unpacking 3
5 matches
Mail list logo
