Your message dated Sat, 15 Jan 2005 10:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#290491: sfftobmp output always created in current working 
directory
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 submit) by bugs.debian.org; 14 Jan 2005 12:20:00 +0000
>From [EMAIL PROTECTED] Fri Jan 14 04:20:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from gk.hm.epigenomics.net [212.121.137.90] (qmailr)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CpQQm-0002yU-00; Fri, 14 Jan 2005 04:19:56 -0800
Received: (qmail 28645 invoked from network); 14 Jan 2005 12:19:53 -0000
Received: from raman.epigenomics.epi (192.168.48.2)
  by salam.epigenomics.epi with SMTP; 14 Jan 2005 12:19:53 -0000
Received: (qmail 4818 invoked from network); 14 Jan 2005 12:19:52 -0000
Received: from milosz.epigenomics.epi ([EMAIL PROTECTED])
  by raman.epigenomics.epi with SMTP; 14 Jan 2005 12:19:52 -0000
Received: (nullmailer pid 30055 invoked by uid 515);
        Fri, 14 Jan 2005 12:19:52 -0000
Date: Fri, 14 Jan 2005 13:19:52 +0100
From: Robert Sander <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: sfftobmp output always created in current working directory
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
X-Reportbug-Version: 3.2
Fnord: +++ath
MSMail-Priority: High
X-Operating-System: Linux milosz 2.4.28-xfs-20041207-milosz-isdn 
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: sfftobmp
Version: 3.0-2
Severity: grave
Justification: renders package unusable

Hi!

when calling sfftobmp with absolute paths it created the output file in
the current working directory:

/tmp# sfftobmp -t /path/to/picture.sff /path/to/picture.tif

produces a file /tmp/picture.tif and not /path/to/picture.tif

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.28-xfs-20041207-milosz-isdn
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL 
PROTECTED])

Versions of packages sfftobmp depends on:
ii  libboost-filesystem1.31 1.31.0-9         Filesystem operations (portable pa
hi  libc6                   2.3.2.ds1-18epi2 GNU C Library: Shared libraries an
ii  libgcc1                 1:3.4.3-6        GCC support library
ii  libjpeg62               6b-9             The Independent JPEG Group's JPEG 
ii  libstdc++5              1:3.3.5-5        The GNU Standard C++ Library v3
ii  libtiff4                3.6.1-5          Tag Image File Format library

-- no debconf information

-- 
Robert Sander                     Senior Manager Information Systems
Epigenomics AG    Kleine Praesidentenstr. 1    10178 Berlin, Germany
phone:+49-30-24345-330                          fax:+49-30-24345-555
http://www.epigenomics.com             [EMAIL PROTECTED]


---------------------------------------
Received: (at 290491-done) by bugs.debian.org; 15 Jan 2005 09:42:19 +0000
>From [EMAIL PROTECTED] Sat Jan 15 01:42:19 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CpkRn-0005vg-00; Sat, 15 Jan 2005 01:42:19 -0800
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
        by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id KAA27123;
        Sat, 15 Jan 2005 10:41:48 +0100 (MET)
Received: from localhost (localhost [127.0.0.1])
        by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id BCD1CF216;
        Sat, 15 Jan 2005 10:41:47 +0100 (MET)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
 by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
 id 09516-36; Sat, 15 Jan 2005 10:41:45 +0100 (MET)
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
        by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
        Sat, 15 Jan 2005 10:41:45 +0100 (MET)
Received: (from [EMAIL PROTECTED])
        by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j0F9fiJE002430;
        Sat, 15 Jan 2005 10:41:44 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 15 Jan 2005 10:41:44 +0100
To: "Daniel J. Priem" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Cc: Robert Sander <[EMAIL PROTECTED]>
Subject: Re: Bug#290491: sfftobmp output always created in current working 
directory
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Daniel J. Priem writes:
> Am Freitag, den 14.01.2005, 13:19 +0100 schrieb Robert Sander:
> > Package: sfftobmp
> > Version: 3.0-2
> > Severity: grave
> > Justification: renders package unusable
> 
> Matthias can you please close this bug?
> Justification: user error. i think :)

ok, done.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to