koffice-l10n_1.5.2-1_i386.changes is NEW

2006-07-25 Thread Debian Installer
koffice-i18n-af_1.5.2-1_all.deb to pool/main/k/koffice-l10n/koffice-i18n-af_1.5.2-1_all.deb koffice-i18n-ar_1.5.2-1_all.deb to pool/main/k/koffice-l10n/koffice-i18n-ar_1.5.2-1_all.deb koffice-i18n-bg_1.5.2-1_all.deb to pool/main/k/koffice-l10n/koffice-i18n-bg_1.5.2-1_all.deb

Build failure with autoconf 2.60: requires autoconf 2.53 or newer

2006-07-25 Thread Martin Michlmayr
Half of KDE and a number of other applications currently fail to build with a message similar to: | *** YOU'RE USING autoconf (GNU Autoconf) 2.60. | *** KDE requires autoconf 2.53 or newer Before I file bugs on these packages, I wanted to check whether this is a known problem and/or whether the

Re: Build failure with autoconf 2.60: requires autoconf 2.53 or newer

2006-07-25 Thread Ben Pfaff
Martin Michlmayr [EMAIL PROTECTED] writes: Half of KDE and a number of other applications currently fail to build with a message similar to: | *** YOU'RE USING autoconf (GNU Autoconf) 2.60. | *** KDE requires autoconf 2.53 or newer Before I file bugs on these packages, I wanted to check

Re: Build failure with autoconf 2.60: requires autoconf 2.53 or newer

2006-07-25 Thread Stephen Gran
This one time, at band camp, Ben Pfaff said: Does KDE use something other than autoconf --version to check the Autoconf version? AUTOCONF_VERSION=`$AUTOCONF --version | head -n 1` case $AUTOCONF_VERSION in Autoconf*2.5* | autoconf*2.5* ) : ;; Maybe not so forward compatible. --

Re: Build failure with autoconf 2.60: requires autoconf 2.53 or newer

2006-07-25 Thread Stephen Gran
This one time, at band camp, Martin Michlmayr said: Half of KDE and a number of other applications currently fail to build with a message similar to: [...] kst_1.2.1-1 This is fixed in -2. Thanks, -- - | ,''`.

Re: Build failure with autoconf 2.60: requires autoconf 2.53 or newer

2006-07-25 Thread Martin Michlmayr
* Stephen Gran [EMAIL PROTECTED] [2006-07-25 19:53]: Half of KDE and a number of other applications currently fail to build with a message similar to: [...] kst_1.2.1-1 This is fixed in -2. Yes, the following packages have newer versions that fixed the bug. I checked this before filing

Re: Build failure with autoconf 2.60: requires autoconf 2.53 or newer

2006-07-25 Thread Daniel Schepler
On Tuesday 25 July 2006 13:40 pm, Martin Michlmayr wrote: Half of KDE and a number of other applications currently fail to build with a message similar to: | *** YOU'RE USING autoconf (GNU Autoconf) 2.60. | *** KDE requires autoconf 2.53 or newer Before I file bugs on these packages, I

Bug#379817: FTBFS: doesn't recognize autoconf 2.60

2006-07-25 Thread Martin Michlmayr
Package: kdeedu Version: 4:3.5.2-1 Severity: serious Your package fails to build from source because it doesn't recognize Autoconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946r1=543983r2=555946 should fix this problem. For some background,

Bug#379816: FTBFS: doesn't recognize autoconf 2.60

2006-07-25 Thread Martin Michlmayr
Package: kdegames Version: 4:3.5.2-1 Severity: serious Your package fails to build from source because it doesn't recognize Autoconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946r1=543983r2=555946 should fix this problem. For some background,

Re: Build failure with autoconf 2.60: requires autoconf 2.53 or newer

2006-07-25 Thread Pierre Habouzit
Le mar 25 juillet 2006 21:15, Daniel Schepler a écrit : On Tuesday 25 July 2006 13:40 pm, Martin Michlmayr wrote: Half of KDE and a number of other applications currently fail to build with a message similar to: | *** YOU'RE USING autoconf (GNU Autoconf) 2.60. | *** KDE requires

[bts-link] source package kdepim

2006-07-25 Thread bts-link-upstream
# # bts-link upstream status pull for source package kdepim # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #364008 # * http://bugs.kde.org/show_bug.cgi?id=103240 # * remote status changed: UNCONFIRMED - NEW usertags

Bug#379691: marked as done (kimagemapeditor: crash on startup)

2006-07-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jul 2006 17:55:42 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#379691: kimagemapeditor: crash on startup has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it