> I was tempted to merge #217862 and #170825 but I can't be sure
> that they report the same bug since the former involves a
> normal dependency and the latter involves a dependency on a
> virtual package. However, the submitters of these bugs may
> be interested to compare notes.
Yes, this real
Package: dpkg-dev
Version: 1.10.18
Severity: normal
Any run of dpkg-scansources gives the following error message here:
Prototype mismatch: sub main::getopt vs (@) at /usr/bin/dpkg-scansources
line 116.
However, dpkg-scansources seems to work as expected. So it is just
annoying.
-- System Infor
> On Mon, Oct 27, 2003 at 11:35:40PM +0300, Nikita V. Youshchenko wrote:
> > Package: dpkg
> > Version: 1.10.15
> > Severity: important
> >
> > This bug may be easilly reproduced.
> > Create dummy package p1, version 1, and dummy package p2, version 1,
>
> On Mon, Oct 27, 2003 at 11:35:40PM +0300, Nikita V. Youshchenko wrote:
> > Package: dpkg
> > Version: 1.10.15
> > Severity: important
> >
> > This bug may be easilly reproduced.
> > Create dummy package p1, version 1, and dummy package p2, version 1,
>
Package: dpkg
Version: 1.10.15
Severity: important
This bug may be easilly reproduced.
Create dummy package p1, version 1, and dummy package p2, version 1,
that Depends: p1 (= 1).
Install both.
Now create package p2, version 2, and try to install it with dpkg -i,
without any --force.
Dpkg will sil
How to reproduse:
create test1_1.deb with package 'test1', version '1'
creaet test1_2.deb with package 'test1', version '2'
create test2.deb with package 'test2' that depends on test1 (>= 2)
dpkg -i test1_2.deb
dpkg -i test2.deb
dpkg -i test1_1.deb
The last commands completes without errors, and
If I run dpkg --purge foo, package foo's selection becomes "purge" even if
dpkg refuses the operation because of dependencies.
Is this a bug or expected behaviour?
> now I wanted to reinstall the whole thing >> with << these questions.
> but when I uninstall everything and reinstall it again,
> it dident ask these questions.
Use dpkg-reconfigure.
> Nikita V. Youshchenko wrote:
> > on my system /usr/share/qt/lib was a symlink to /usr/lib.
>
> You should probably not do that, since it confuses dpkg.
>
> When dpkg sees that a directory is a symlink, it just follows it
> when unpacking the contents of a package (as
Hello.
Some time ago I found that I can't link qt3 apps on my system, althouth
libqt3-dev was installed.
I found quickly that /usr/lib/libqt.so link was invalid - it pointed to
../../../lib/libqt.so.3.0.5 instead of libqt.so.3.0.5
So I did ln -sf and forgot it.
Some time later libqt3-dev was up
10 matches
Mail list logo
