Package: kicker
Version: 4:3.2.92-1
Severity: normal
Tags: experimental
In kdebase-3.2.92/debian :
isis% ls -ld * | grep '\0\'
-rw-r--r-- 1 rkitover rkitover 0 Jul 27 23:37 kicker.links
-rw-r--r-- 1 rkitover rkitover 0 Jul 27 23:37 kicker.menu-method
-rwxr-xr-x 1 rkitover rkitover
kdegraphics_3.2.92-1_i386.changes uploaded successfully to localhost
along with the files:
kdegraphics_3.2.92-1.dsc
kdegraphics_3.2.92.orig.tar.gz
kdegraphics_3.2.92-1.diff.gz
kamera_3.2.92-1_i386.deb
kcoloredit_3.2.92-1_i386.deb
kdegraphics-dev_3.2.92-1_i386.deb
Package: kdelibs-data
Version: 4:3.2.3-3debug1
Severity: important
Hi,
When installing kdelibs-data 3.2.92-1 on a system with korganizer
3.2.2-2 installed, I get the following errors:
Voorbereiden om kdelibs-data 4:3.2.3-3debug1 te vervangen (met
.../kdelibs-data_4%3a3.2.92-1_all.deb) ...
kamera_3.2.92-1_i386.deb
to pool/main/k/kdegraphics/kamera_3.2.92-1_i386.deb
kcoloredit_3.2.92-1_i386.deb
to pool/main/k/kdegraphics/kcoloredit_3.2.92-1_i386.deb
kdegraphics-dev_3.2.92-1_i386.deb
to pool/main/k/kdegraphics/kdegraphics-dev_3.2.92-1_i386.deb
CVS commit by mornfall:
Fix the show in new view menu entry to work... Just a temporary hack
anyway. Frowning upon namespace support in signal/slot framework.
M +2 -2 kapture/kapture.cpp 1.38
M +2 -1 libkapture/listtreeview.cpp 1.23
---
Package: kdelibs-bin
Version: 4:3.2.3-3debug1
Severity: important
When installing kdelibs 3.2.92 on a system with kcontrol 3.2.3-3
installed, I get the following error:
Voorbereiden om kdelibs-data 4:3.2.3-3debug1 te vervangen (met
.../kdelibs-data_4%3a3.2.92-1_all.deb) ...
Uitpakken van
Package: kdelibs-data
Version: 4:3.2.92-1
Severity: important
When installing kdelibs-data 3.2.92-1 on a system with kcontrol
3.2.3-1 installed, I get the following error:
Voorbereiden om kdelibs-data 4:3.2.3-3debug1 te vervangen (met
.../kdelibs-data_4%3a3.2.92-1_all.deb) ...
Uitpakken van
CVS commit by mornfall:
Rename browsermanager - historymanager. This commit was brought to you
by cvs's outsanding support for renames.
Alibcapture/historymanager.cpp 1.1 [no copyright]
Alibcapture/historymanager.h 1.1 [UNKNOWN]
M +2 -2
Processing commands for [EMAIL PROTECTED]:
tag 231179 - unreproducible moreinfo
Bug#231179: konqueror: background-color for HTML or BODY does not seem to work
Tags were: moreinfo unreproducible
Tags removed: unreproducible, moreinfo
tag 231179 + confirmed
Bug#231179: konqueror:
tag 231179 - unreproducible moreinfo
tag 231179 + confirmed
severity 231179 wishlist
retitle 231179 konqueror: handle gracefully missing title element in
alternate stylesheets
forwarded 231179 http://bugs.kde.org/86173
quit
* Ambrose Li [Tue, 27 Jul 2004 15:41:02 -0400]:
hi
On Wednesday 28 July 2004 01.53, Ivan Nestlerode wrote:
KDE doesn't seem to save my appliaction associations for PDF. I'll
describe the scenario in more detail.
I can confirm the bug, since it happened to me too.
Out of the box, KDE doesn't seem to know what to do with a .pdf file.
When I
Subject: kcontrol: kcminit crashes on startup
Package: kcontrol
Version: 4:3.2.2-1
Severity: important
When launched, kcminit crashes and the KDE Crash Handler is launched with
the following error message:
This application unknon (kcminit) crashed and caused the signal 11
(SIGSEGV)
-- System
Еще шаг для защите.
http://www.dazer2.ru
On Tue, 27 Jul 2004, David Pye wrote:
On Tuesday 27 July 2004 05:53, Nate Duehr wrote:
...
There are actually dependency issues that apt-get CANNOT resolve that
dselect can. Specifically when a package is added to the archives and
a new dependency is created, apt-get chokes on it saying that it
Hello,
now that sarge will be frozen soon, will kde in sarge still updated to
3.2.3-3? I'm especially referring to this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241283
Unfortunately it was reduced from critical to normal.
If one doesn't log out regularly this bug may fill up the
Bernd Schubert [EMAIL PROTECTED] writes:
now that sarge will be frozen soon, will kde in sarge still updated to
3.2.3-3? I'm especially referring to this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241283
Unfortunately it was reduced from critical to normal.
Probably not likely,
I've been trying to set up the latest KDE from
experimental but have been unable to remove the old
kicker package. Here are my logs:
apt-get remove kicker
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
kicker
0 upgraded, 0 newly installed,
* Antiphon [Wed, 28 Jul 2004 17:48:29 -0400]:
I've been trying to set up the latest KDE from
experimental but have been unable to remove the old
kicker package. Here are my logs:
reported as http://bugs.debian.org/261789.
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
I
On Wed 28 July 2004 12:47, Bernd Schubert wrote:
Hello,
now that sarge will be frozen soon, will kde in sarge still updated
to 3.2.3-3?
Considering that 3.2.3 still isn't fully in unstable (check for
Konqueror), I have my doubts. Of course what'll happen is that Sarge
will be released right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 28 July 2004 05:48 pm, Antiphon wrote:
Unpacking replacement kicker ...
dpkg (subprocess): unable to execute old post-removal
script: Exec format error
dpkg: warning - old post-removal script returned error
exit status 2
The quick
20 matches
Mail list logo
