Your message dated Wed, 5 Oct 2005 18:22:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line can't reproduce after reboot
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; 5 Oct 2005 05:13:35 +0000
>From [EMAIL PROTECTED] Tue Oct 04 22:13:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from blars.org (renig.nat.blars.org) [64.81.35.59] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EN1ax-0006MY-00; Tue, 04 Oct 2005 22:13:35 -0700
Received: from quaff.nat.blars.org (quaff.nat.blars.org [172.16.2.7])
        by renig.nat.blars.org (8.13.4/8.13.4/Debian-3) with ESMTP id 
j955DUqG019106
        (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
        Tue, 4 Oct 2005 22:13:31 -0700
Received: from quaff.nat.blars.org (quaff [127.0.0.1])
        by quaff.nat.blars.org (8.13.5/8.13.5/Debian-2) with ESMTP id 
j9557NNW030629;
        Tue, 4 Oct 2005 22:07:23 -0700
Received: (from [EMAIL PROTECTED])
        by quaff.nat.blars.org (8.13.5/8.13.5/Submit) id j9557M9M030627;
        Tue, 4 Oct 2005 22:07:22 -0700
Date: Tue, 4 Oct 2005 22:07:22 -0700
From: Blars Blarson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: apt-move: fails building Packages file
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.17
User-Agent: Mutt/1.5.11
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-Level: 
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

Package: apt-move
Version: 4.2.24-1
Severity: grave
Justification: renders package unusable

As of today, apt-move fails to build the packages file.  It worked
yesterday.  There are two packages starting with "xfce4-syst" but none
named that, so it appears something is trunkating a package name.

munge:/play/debian# apt-move packages

Creating Packages files...
Building: unstable dists/unstable/contrib/binary-i386 Packages
Building: unstable dists/unstable/contrib/binary-sparc Packages
Building: unstable dists/unstable/main/binary-i386 Packages
getline failed on 
.apt-move/dists/unstable/main/binary-i386/.index/../../../../../pool/main/x/xfce4-syst
Unknown error: dopackages: 1.



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages apt-move depends on:
ii  apt [libapt-pkg-libc6.3-6-3.1 0.6.41     Advanced front-end for dpkg
ii  ash                           0.5.2-7    Compatibility package for the Debi
ii  bc                            1.06-17    The GNU bc arbitrary precision cal
ii  dash                          0.5.2-7    The Debian Almquist Shell
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-2  GCC support library
ii  libstdc++6                    4.0.2-2    The GNU Standard C++ Library v3

Versions of packages apt-move recommends:
ii  apt                           0.6.41     Advanced front-end for dpkg

-- no debconf information

---------------------------------------
Received: (at 332199-done) by bugs.debian.org; 6 Oct 2005 01:32:20 +0000
>From [EMAIL PROTECTED] Wed Oct 05 18:32:20 2005
Return-path: <[EMAIL PROTECTED]>
Received: from blars.org (renig.nat.blars.org) [64.81.35.59] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1ENKcO-0001II-00; Wed, 05 Oct 2005 18:32:20 -0700
Received: from quaff.nat.blars.org (quaff.nat.blars.org [172.16.2.7])
        by renig.nat.blars.org (8.13.4/8.13.4/Debian-3) with ESMTP id 
j961WIr4022532
        (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
        Wed, 5 Oct 2005 18:32:19 -0700
Received: from quaff.nat.blars.org (quaff [127.0.0.1])
        by quaff.nat.blars.org (8.13.5/8.13.5/Debian-2) with ESMTP id 
j961MCZV016642;
        Wed, 5 Oct 2005 18:22:12 -0700
Received: (from [EMAIL PROTECTED])
        by quaff.nat.blars.org (8.13.5/8.13.5/Submit) id j961MCAT016640;
        Wed, 5 Oct 2005 18:22:12 -0700
Date: Wed, 5 Oct 2005 18:22:12 -0700
From: Blars Blarson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: can't reproduce after reboot
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
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-Level: 
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2

tags 332199 unreproducable
thanks

Trying to debug this things got strange.  find was working, except
when piped through an "if then else" construct.  Doing the same from
dash caused a segmentation fault but the same results.  Adding a tee
-a /tmp/pkg1 before the if-then-else made it work.  Attempting to
duplicate all this again with script made it all fail, even just the
find command.  After rebooting the system, I can no longer duplicate
it at all.

I can only assume this is flakey hardware that was causing gradually
more errors that were getting cached, so I am closing the bug.  Sorry
to have bothered you.


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

Reply via email to