Re: Kbear crashes in KDE3.1beta on Debian unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I got the deb I am referring to from the source in your email:
>I have done that.
>I did nothing more than just rebuild it on kde 3.1. The package I made is on
>http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-apps/kbear_2.0beta2.kde31-1_i386.deb
>
>-- Karolina
either a) Kbear was never upgraded from my KDE 3.0 version because of the
name of the package (kbear_2.0beta2.kde31-1_i386.deb, which dpkg believed was
a downgrade) and I never noticed because I use apt-get dist-upgrade or
aptitude,
or b) the Kbear that I had was never upgraded from the KDE 2.2 version.
Either one is likely, as I don't remember when it was upgraded before this.
If that kbear package is the same package you provided with the 3.1 packages,
and you didn't rebuild it because of my original email, then one of these two
things must have occured. The package probably needs to be renamed in such a
way that dpkg does not interpret it as a downgrade.
Nathan
On Friday 06 September 2002 02:05 am, Karolina Lindqvist wrote:
> I didn't have the debian files for 2.0-beta2-1.
>
> I have a kind of feeling that the problem with kbear might be a possible
> problem for every package built separately for kde 3.0, when kde 3.1 is
> coming. Maybe the officiall kde 3.1 packager is solving that problem
> somehow?
>
> I am not sure exactly how to build the beta so that all packages that
> depend on older versions of kde will be automatically rejected, at the same
> time as packages built with kde 3.1- beta should be compatible with the
> future kde 3.1 official packages. If anyone have an idea, I would be
> grateful, since I will rebuild for kde 3.1-beta2 when it is official.
>
> -- Karolina
- --
12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD4DBQE9eMuD4e9YdOpQYMsRAqEXAJwIUH9SEAwBh5TPaHumi9SYTg01CQCXWwko
GsN/EJl/PizMyGtfhuS5vg==
=vBkh
-----END PGP SIGNATURE-----
Reply to: