This looks of it could be the same issue as bug 1021938, which is due to a
regression in libical version 3.0.15.
--
David Jarvie
KAlarm author, KDE developer
This bug description looks like https://bugs.kde.org/show_bug.cgi?id=374337.
This was fixed in KDE Applications 16.12.1. (The version you are reporting
about is an earlier version, 16.04.3.)
--
David Jarvie.
KDE developer, KAlarm author.
the git commit mentioned in the KDE bug report).
--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
signature.asc
Description: This is a digitally signed message part.
The bug has occurred again. I built Qt 4 (downloaded from KDE's SVN qt-copy),
and then tried to install it with this command:
checkinstall --pkgname=qt4x make install_qmake install_mkspecs
sub-src-install_subtargets sub-tools-install_subtargets install_htmldocs
It's a pretty big package to inst
On Wednesday 07 June 2006 06:42, Felipe Sateler wrote:
> What is the install command you are using? Can you easily reproduce this
> bug?
I tried reinstalling checkinstall-1.5.3-3, and now it seems to work without my
patch. It previously failed consistently for a period of weeks, and I have no
id
Package: checkinstall
Version: 1.5.3-3
Severity: grave
Tags: patch
Justification: renders package unusable
Checkinstall creates a script in a temporary directory for execution
by installwatch. Installwatch also uses a temporary directory, which
it removes if it already exists. Checkinstall and ins
Package: installwatch
Version: 0.6.3-2
Severity: grave
Justification: renders package unusable
Whenever I run checkinstall, I get a segmentation fault when it invokes
installwatch. It used to work until around 2 - 4 weeks ago. This fault renders
checkinstall useless.
The output on the console i
On Friday 07 April 2006 21:44, maximilian attems wrote:
> kernel-package wants to drop ability to run lilo on the postinstall.
> grub is the _default_.
>
> update-initramfs can easily check for an lilo.conf and warn in those cases.
A warning (preferably in the form of a prompt which must be acknow
Package: initramfs-tools
Version: 0.59b
Severity: critical
Justification: breaks the whole system
Upgrading initramfs-tools yesterday caused the current kernel 2.6.15-1
to become unbootable, apparently because the upgrade process regenerated
initrd.img-2.6.15-1-k7. The upgrade process should have
, while my other reiserfs partitions are
v3.6. I haven't yet noticed any problems on the v3.6 partitions, although I
didn't get very many before, so they may yet happen. Downgrade to 2.6.12
kernel seems the only answer for now.
--
David Jarvie.
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
10 matches
Mail list logo
