blackened_1.8.1-4_i386.changes ACCEPTED

2003-02-25 Thread Debian Installer

Accepted:
blackened_1.8.1-4.diff.gz
  to pool/main/b/blackened/blackened_1.8.1-4.diff.gz
blackened_1.8.1-4.dsc
  to pool/main/b/blackened/blackened_1.8.1-4.dsc
blackened_1.8.1-4_i386.deb
  to pool/main/b/blackened/blackened_1.8.1-4_i386.deb
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 182157 


Thank you for your contribution to Debian.



Bug#182157: marked as done (wrong assumption on char signedness)

2003-02-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Feb 2003 01:02:13 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#182157: fixed in blackened 1.8.1-4
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 is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at maintonly) by bugs.debian.org; 23 Feb 2003 12:00:51 +
From [EMAIL PROTECTED] Sun Feb 23 06:00:51 2003
Return-path: [EMAIL PROTECTED]
Received: from moutvdom.kundenserver.de [212.227.126.252] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18muoM-00074P-00; Sun, 23 Feb 2003 06:00:50 -0600
Received: from [212.227.126.223] (helo=mrvdomng.kundenserver.de)
by moutvdom.kundenserver.de with esmtp (Exim 3.35 #1)
id 18muoL-0003Jv-00
for [EMAIL PROTECTED]; Sun, 23 Feb 2003 13:00:49 +0100
Received: from [80.138.129.87] (helo=tau)
by mrvdomng.kundenserver.de with smtp (Exim 3.35 #1)
id 18muoL-0005WX-00
for [EMAIL PROTECTED]; Sun, 23 Feb 2003 13:00:49 +0100
From: Gerhard Tonn [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: wrong assumption on char signedness
Date: Sun, 23 Feb 2003 13:07:10 +0100
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset=iso-8859-1
MIME-Version: 1.0
Message-Id: [EMAIL PROTECTED]
Content-Transfer-Encoding: 8bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-0.2 required=4.0
tests=HAS_PACKAGE,SPAM_PHRASE_00_01
version=2.44
X-Spam-Level: 

Package: blackened
Version:  1.8.1-3
Severity: important

Hi,
char is per default unsigned on arm, powerpc and s390. There iare two warnings

fileio.c:648: warning: comparison is always true due to limited range of data 
type
fileio.c:697: warning: comparison is always true due to limited range of data 
type

during build of your package that might cause a runtime error. Please check

http://buildd.debian.org/fetch.php?pkg=blackenedver=1.8.1-3arch=s390stamp=1044806788file=logas=raw

for details.

In your case the variable c should be defined as int. Defining it as 
char is even wrong on i386, since the char 0xff is then interpreted as EOF. 
On the platforms mentioned above the EOF condition is never true, leading to 
an infinite loop.

Thanks,
Gerhard

---
Received: (at 182157-close) by bugs.debian.org; 25 Feb 2003 06:08:12 +
From [EMAIL PROTECTED] Tue Feb 25 00:08:11 2003
Return-path: [EMAIL PROTECTED]
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18nYGB-zX-00; Tue, 25 Feb 2003 00:08:11 -0600
Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian))
id 18nYAP-Uf-00; Tue, 25 Feb 2003 01:02:13 -0500
From: Matej Vela [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.32 $
Subject: Bug#182157: fixed in blackened 1.8.1-4
Message-Id: [EMAIL PROTECTED]
Sender: Archive Administrator [EMAIL PROTECTED]
Date: Tue, 25 Feb 2003 01:02:13 -0500
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
blackened, which is due to be installed in the Debian FTP archive:

blackened_1.8.1-4.diff.gz
  to pool/main/b/blackened/blackened_1.8.1-4.diff.gz
blackened_1.8.1-4.dsc
  to pool/main/b/blackened/blackened_1.8.1-4.dsc
blackened_1.8.1-4_i386.deb
  to pool/main/b/blackened/blackened_1.8.1-4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matej Vela [EMAIL PROTECTED] (supplier of updated blackened package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 24 Feb 2003 21:42:26 +0100
Source: blackened
Binary: blackened
Architecture: source i386
Version: 1.8.1-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Matej Vela [EMAIL PROTECTED]
Description: 
 blackened  - A feature rich ircII based IRC client
Closes: 182157
Changes: 
 blackened (1.8.1-4) unstable; urgency=low
 .
   * QA upload.
   * source/fileio.c (function_fread, function_freadln): Store the return
 value of fgetc() in an int rather than a char.  Closes: #182157.
Files: 
 

Bug#182474: KDE/unstable

2003-02-25 Thread Michel Loos
Package: KDE
Version: 4:2.2.25
Severity: critical

The metapackage kde in unstable should be substituted for a metapackage
depending only on the KDE3 packages already available.

Like it is now, it mixes KDE2 and KDE3 packages and can not be
installed.

Michel.

-- 
Michel Loos [EMAIL PROTECTED]




Bug#182474: KDE/unstable

2003-02-25 Thread Colin Watson
On Tue, Feb 25, 2003 at 03:50:38PM -0300, Michel Loos wrote:
 Package: KDE
 Version: 4:2.2.25
 Severity: critical
 
 The metapackage kde in unstable should be substituted for a metapackage
 depending only on the KDE3 packages already available.
 
 Like it is now, it mixes KDE2 and KDE3 packages and can not be
 installed.

Is anyone planning to take the meta-kde source package over? It's
basically just been accumulating bug reports for the last 10 months or
so (some of which I'm sure should be reassigned to other parts of KDE,
but they need a KDE expert to look at them) ...

-- 
Colin Watson  [EMAIL PROTECTED]