> Look at the debian dir of the package you are backporting. ;)
> Hint - k3b-0.9/debian/patches/02_k3bcdparanoialib.dpatch
My fault: i did not do a backport. I just build a woody package from
pure upstream sources... But thank you for the hint.
Henning
On Wednesday 08 October 2003 13:27, Colin Watson wrote:
> No, plain .so links are only needed for build-time linking, and
> therefore live in development packages.
Thank you for that information!
But now i am in a bit of trouble: i packaged a woody backport of k3b.
This programm tries to dlopen
Hi!
I wonder why there is a symbolic link
/usr/lib/libcdda_paranoia.so -> libcdda_paranoia.so.0.9.8
in package 'libcdparanoia0-dev'. Shouldn't that be in 'libcdparanoia0'?
Regards
Henning
Hi!
I posted this on debian-user, but did not receive any answer. Maybe it's a
bigger problem? I hope, that somebody can help me:
On the system of a friend of me, apt-get is unable to 'upgrade'. It
recommends the use of 'apt-get -f install'. Here's the output:
snip
# apt-get -f install
Hi!
I was just looking for a 'open use' debian favicon. But i can't find it on
http://www.debian.org/logos/index.en.html
Is it ok to use the resource from http://www.debian.org/favicon.ico ?
Shouldn't it also be published on the logo page?
Regards
Henning
5 matches
Mail list logo