Bug#185372: marked as done (python-bsddb3: Must depend on particular version of python, as per Python Policy.)

2004-08-11 Thread Debian Bug Tracking System 
Your message dated 10 Aug 2004 22:30:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line bugs done
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; 19 Mar 2003 00:36:38 +
>From [EMAIL PROTECTED] Tue Mar 18 18:36:38 2003
Return-path: <[EMAIL PROTECTED]>
Received: from minkirri.apana.org.au [203.12.237.33] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18vRZK-0003bS-00; Tue, 18 Mar 2003 18:36:37 -0600
Received: by minkirri.apana.org.au (Postfix, from userid 1000)
id 1180A978CC; Wed, 19 Mar 2003 11:36:24 +1100 (EST)
From: Donovan Baarda <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: python-bsddb3: Must depend on particular version of python, as per 
Python Policy.
X-Mailer: reportbug 1.50
Date: Wed, 19 Mar 2003 11:36:24 +1100
Message-Id: <[EMAIL PROTECTED]>
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: python-bsddb3
Version: 3.3.0-5.1
Severity: serious
Justification: Python Policy 2.2.3.1

The "empty default" package that ensures that support is provided for the
default version of python must depend on the particular version of python it
supports;

Depends: python (>= X.Y), python (<< X.Y+1), pythonX.Y-foo

This ensures that the correct version of python-bsddb3 and corresponding
pythonX.Y-bsddb3 is installed together with the corresponding X.Y version of
the "default" python.

Without this, this package can be installed on a "testing" or "stable"
system where the default version of python is 2.1, not 2.2, resulting in no
python-bsddb3 support when running the default /usr/bin/python.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux minkirri 2.4.20-686 #1 Mon Jan 13 22:22:30 EST 2003 i686
Locale: LANG=en_AU, LC_CTYPE=en_AU

Versions of packages python-bsddb3 depends on:
ii  python2.2-bsddb3  3.3.0-5.1  Python 2.2 interface to libdb3

Versions of packages python-bsddb3 _should_ depend on:
ii  python 2.1.3-4   An interactive object-oriented


---
Received: (at 185372-done) by bugs.debian.org; 11 Aug 2004 05:32:09 +
>From [EMAIL PROTECTED] Tue Aug 10 22:32:09 2004
Return-path: <[EMAIL PROTECTED]>
Received: from vp085189.reshsg.uci.edu (becket.becket.net) [128.195.85.189] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bulib-0007VA-00; Tue, 10 Aug 2004 22:32:09 -0700
Received: from tb by becket.becket.net with local (Exim 4.34)
id 1Bulia-000784-Lp; Tue, 10 Aug 2004 22:32:08 -0700
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: bugs done
X-Reply-Permission: Posted or emailed replies to this message constitute
 permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51  63 28 EB DA E6 44 E5 5E  EC F3 04 26 4E BF 1A 92
X-Tom-Swiftie: "I can't get this fire started," Tom said woodenly
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
Date: 10 Aug 2004 22:30:11 -0700
Message-ID: <[EMAIL PROTECTED]>
Lines: 9
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 4


Bug 126490, 165999: fixed by maintainer in 3.3.0-2 and 3.3.0-5, but he
used a different email address so they were only marked closed,
instead of fixed.

Bug 185372, 168447, 204702: Fixed by NMU 3.3.0-5.1, 3.3.0-5.2, and
3.3.0-5.2, and became accepted when the package was taken by QA in
version 3.3.0-6.

Bug#204702: marked as done (python-bsddb3: no python2.3 version available)

2004-08-11 Thread Debian Bug Tracking System 
Your message dated 10 Aug 2004 22:30:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line bugs done
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; 9 Aug 2003 13:07:47 +
>From [EMAIL PROTECTED] Sat Aug 09 08:07:43 2003
Return-path: <[EMAIL PROTECTED]>
Received: from 195.82-200-80.adsl.skynet.be (localhost) [80.200.82.195] 
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19lTRe-0006LG-00; Sat, 09 Aug 2003 08:07:42 -0500
Received: from bartvh by localhost with local (Exim 3.36 #1 (Debian))
id 19lTRd-0001Ny-00; Sat, 09 Aug 2003 15:07:41 +0200
Content-Type: multipart/mixed; boundary="===1940186701=="
MIME-Version: 1.0
From: Bart Vanhaute <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: python-bsddb3: no python2.3 version available
X-Mailer: reportbug 2.20
Date: Sat, 09 Aug 2003 15:07:40 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: Bart Vanhaute <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-4.5 required=4.0
tests=BAYES_10,HAS_PACKAGE,SEMIFORGED_HOTMAIL_RCVD
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 
(1.174.2.15-2003-03-30-exp)

This is a multi-part MIME message sent by reportbug.

--===1940186701==
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline

Package: python-bsddb3
Version: 3.3.0-5.2
Severity: wishlist
Tags: patch

Now that python2.3 has become the new default python interpreter, it
would be nice if the bsddb3 module had a python2.3 version (and the
default package installed the 2.3 version).

Maybe you are already working on it... then the included patch file
might help. At least it works for me (I was trying to use 'straw' with
python2.3

Thanks,
Bart.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux bvanhaute 2.4.20-drm #1 Sat Mar 1 16:09:53 CET 2003 i686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages python-bsddb3 depends on:
ii  python2.2.3-3An interactive high-level object-o
ii  python2.2-bsddb3  3.3.0-5.2  Python 2.2 interface to libdb3

-- no debconf information


--===1940186701==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="/tmp/python2.3-bsddb3-3.3.0.patch"

diff -r -cN python-bsddb3-3.3.0-old/debian/control 
python-bsddb3-3.3.0/debian/control
*** python-bsddb3-3.3.0-old/debian/control  2003-08-09 14:29:23.0 
+0200
--- python-bsddb3-3.3.0/debian/control  2003-08-09 14:47:56.0 +0200
***
*** 7,13 
  
  Package: python-bsddb3
  Architecture: any
! Depends: ${shlibs:Depends}, python2.2-bsddb3, python (>= 2.2), python (<< 2.3)
  Description: Python interface to libdb3
   This module provides a nearly complete wrapping of the Sleepycat C API for
   the Database Environment, Database, Cursor, and Transaction objects, and each
--- 7,13 
  
  Package: python-bsddb3
  Architecture: any
! Depends: ${shlibs:Depends}, python2.3-bsddb3, python (>= 2.3), python (<< 2.4)
  Description: Python interface to libdb3
   This module provides a nearly complete wrapping of the Sleepycat C API for
   the Database Environment, Database, Cursor, and Transaction objects, and each
***
*** 16,22 
   first time all of these are fully supported in the Python wrappers.
   .
   This package is a dependency package, which depends on Debian's default
!  Python version (currently v2.2).
  
  Package: python2.1-bsddb3
  Architecture: any
--- 16,22 
   first time all of these are fully supported in the Python wrappers.
   .
   This package is a dependency package, which depends on Debian's default
!  Python version (currently v2.3).
  
  Package: python2.1-bsddb3
  Architecture: any
***
*** 38,43 
--- 38,53 
   objects can use various access methods: btree, hash, recno, queue.  For the
   first time all of these are fully supported in the Python wrappers.
  
+ Package: python2.3-bsddb3
+ Architecture: any
+ Depends: ${shlibs:Depends}, python2.3
+ Description: Python 2.3 interface to libdb3
+  This module provides a nearly complete wrapp

Bug#126490: marked as done (inprecise build dependencies)

2004-08-11 Thread Debian Bug Tracking System 
Your message dated 10 Aug 2004 22:30:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line bugs done
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; 26 Dec 2001 11:55:17 +
>From [EMAIL PROTECTED] Wed Dec 26 05:55:17 2001
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16JCeS-0008DC-00; Wed, 26 Dec 2001 05:55:16 -0600
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id MAA18775
for <[EMAIL PROTECTED]>; Wed, 26 Dec 2001 12:55:09 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.10.2+Sun/8.9.3) id fBQBt9319738;
Wed, 26 Dec 2001 12:55:09 +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: Wed, 26 Dec 2001 12:55:08 +0100
To: [EMAIL PROTECTED]
Subject: inprecise build dependencies
X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]

Package: python-bsddb3
Version: 3.3.0-1
Severity: serious

- the package has to build-depend on python-dev (>= 2.1), python-dev
  (<< 2.2), as the binary does. This can result in wrong dependencies.

- the package does not compile/remove the *.py[co] files in the
  postinst/prerm. Please see /usr/share/doc/python2.1/sample.* for
  examples.

---
Received: (at 126490-done) by bugs.debian.org; 11 Aug 2004 05:32:09 +
>From [EMAIL PROTECTED] Tue Aug 10 22:32:09 2004
Return-path: <[EMAIL PROTECTED]>
Received: from vp085189.reshsg.uci.edu (becket.becket.net) [128.195.85.189] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bulib-0007VA-00; Tue, 10 Aug 2004 22:32:09 -0700
Received: from tb by becket.becket.net with local (Exim 4.34)
id 1Bulia-000784-Lp; Tue, 10 Aug 2004 22:32:08 -0700
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: bugs done
X-Reply-Permission: Posted or emailed replies to this message constitute
 permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51  63 28 EB DA E6 44 E5 5E  EC F3 04 26 4E BF 1A 92
X-Tom-Swiftie: "I can't get this fire started," Tom said woodenly
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
Date: 10 Aug 2004 22:30:11 -0700
Message-ID: <[EMAIL PROTECTED]>
Lines: 9
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


Bug 126490, 165999: fixed by maintainer in 3.3.0-2 and 3.3.0-5, but he
used a different email address so they were only marked closed,
instead of fixed.

Bug 185372, 168447, 204702: Fixed by NMU 3.3.0-5.1, 3.3.0-5.2, and
3.3.0-5.2, and became accepted when the package was taken by QA in
version 3.3.0-6.

Bug#165999: marked as done (FTBFS: Build failure of python-bsddb3 on i386)

2004-08-11 Thread Debian Bug Tracking System 
Your message dated 10 Aug 2004 22:30:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line bugs done
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; 23 Oct 2002 07:11:55 +
>From [EMAIL PROTECTED] Wed Oct 23 02:11:54 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mikilab.doshisha.ac.jp [202.23.156.50] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 184FgH-0007My-00; Wed, 23 Oct 2002 02:11:53 -0500
Received: from atoron.work.isl.doshisha.ac.jp (localhost [127.0.0.1])
by mikilab.doshisha.ac.jp (8.9.3/3.7W) with SMTP id QAA01396
for <[EMAIL PROTECTED]>; Wed, 23 Oct 2002 16:11:21 +0900
X-Authentication-Warning: mikilab.doshisha.ac.jp: Host localhost [127.0.0.1] 
claimed to be atoron.work.isl.doshisha.ac.jp
Date: Wed, 23 Oct 2002 16:11:26 +0900
From: Junichi Uekawa <[EMAIL PROTECTED]>
To: submit bug tracking system <[EMAIL PROTECTED]>
Subject: FTBFS: Build failure of python-bsddb3 on i386
Message-Id: <[EMAIL PROTECTED]>
Organization: Netfort project
X-Mailer: Sylpheed version 0.8.3 (GTK+ 1.2.10; i386-debian-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-5.7 required=5.0
tests=NOSPAM_INC,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01,
  X_AUTH_WARNING
version=2.41
X-Spam-Level: 



Package: python-bsddb3
Version: 3.3.0-4
Severity: serious


python-bsddb3 fails to build from source on i386, when doing a rebuild inside 
chroot.

I am filing this bug to notify you that I failed to build your
package from source in the current sid distribution.
It is a serious problem that your source does not 
build from source using the information provided in your control files,
and such a package should not be distributed in a stable Debian distribution.

This build was done using pbuilder package.

"python" binary is not pulled in by python2.2-dev nor python2.1-dev.



Build log follows:
===
su: Authentication service cannot retrieve authentication info.
(Ignored)
dpkg-buildpackage: source package is python-bsddb3
dpkg-buildpackage: source version is 3.3.0-4
dpkg-buildpackage: source maintainer is Nathan Hawkins <[EMAIL PROTECTED]>
dpkg-buildpackage: host architecture is i386
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
python setup.py --berkeley-db=/usr clean
make: python: Command not found
make: *** [clean] Error 127
===


regards,
   junichi



-- 
[EMAIL PROTECTED]  http://www.netfort.gr.jp/~dancer




---
Received: (at 165999-done) by bugs.debian.org; 11 Aug 2004 05:32:09 +
>From [EMAIL PROTECTED] Tue Aug 10 22:32:09 2004
Return-path: <[EMAIL PROTECTED]>
Received: from vp085189.reshsg.uci.edu (becket.becket.net) [128.195.85.189] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bulib-0007VA-00; Tue, 10 Aug 2004 22:32:09 -0700
Received: from tb by becket.becket.net with local (Exim 4.34)
id 1Bulia-000784-Lp; Tue, 10 Aug 2004 22:32:08 -0700
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: bugs done
X-Reply-Permission: Posted or emailed replies to this message constitute
 permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51  63 28 EB DA E6 44 E5 5E  EC F3 04 26 4E BF 1A 92
X-Tom-Swiftie: "I can't get this fire started," Tom said woodenly
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
Date: 10 Aug 2004 22:30:11 -0700
Message-ID: <[EMAIL PROTECTED]>
Lines: 9
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 2


Bug 126490, 165999: fixed by maintainer in 3.3.0-2 and 3.3.0-5, but he
used a different email address so they were only marked closed,
instead of fixed.

Bug 185372, 168447, 204702: Fixed by NMU 3.3.0-5.1, 3.3.0-5.2, and
3.3.0-5.2, and became accepted when the package was taken by QA in
version 3.3.0-6.

Bug#168447: marked as done (python-bsddb3 depends on python 2.1, not 2.2)

2004-08-11 Thread Debian Bug Tracking System 
Your message dated 10 Aug 2004 22:30:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line bugs done
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; 9 Nov 2002 17:00:57 +
>From [EMAIL PROTECTED] Sat Nov 09 11:00:56 2002
Return-path: <[EMAIL PROTECTED]>
Received: from cmailm2.svr.pol.co.uk [195.92.193.210] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18AYye-00085D-00; Sat, 09 Nov 2002 11:00:56 -0600
Received: from modem-931.bonobo.dialup.pol.co.uk ([217.134.51.163] 
helo=localhost)
by cmailm2.svr.pol.co.uk with esmtp (Exim 3.35 #1)
id 18AYyd-0005SM-00; Sat, 09 Nov 2002 17:00:55 +
Received: from ross by localhost with local (Exim 3.36 #1 (Debian))
id 18AYyk-0001Ab-00; Sat, 09 Nov 2002 17:01:02 +
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ross Burton <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: python-bsddb3 depends on python 2.1, not 2.2
X-Mailer: reportbug 2.9
Date: Sat, 09 Nov 2002 17:01:02 +
Message-Id: <[EMAIL PROTECTED]>
Sender: Ross Burton <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=0.6 required=5.0
tests=SPAM_PHRASE_00_01
version=2.41
X-Spam-Level: 

Package: python-bsddb3
Version: 3.3.0-5 (not installed)
Severity: important
Tags: sid

"This package is a dependency package, which depends on Debian's
default Python version (currently v2.1)."

Wrong. The default Python version is now 2.2, this package should be
rebuilt so that it installs python2.2-bsddb3.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux eddie 2.4.19-k7 #1 Sun Oct 6 20:29:56 EST 2002 i686
Locale: LANG=en_GB, LC_CTYPE=en_GB (ignored: LC_ALL set)


---
Received: (at 168447-done) by bugs.debian.org; 11 Aug 2004 05:32:09 +
>From [EMAIL PROTECTED] Tue Aug 10 22:32:09 2004
Return-path: <[EMAIL PROTECTED]>
Received: from vp085189.reshsg.uci.edu (becket.becket.net) [128.195.85.189] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bulib-0007VA-00; Tue, 10 Aug 2004 22:32:09 -0700
Received: from tb by becket.becket.net with local (Exim 4.34)
id 1Bulia-000784-Lp; Tue, 10 Aug 2004 22:32:08 -0700
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: bugs done
X-Reply-Permission: Posted or emailed replies to this message constitute
 permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51  63 28 EB DA E6 44 E5 5E  EC F3 04 26 4E BF 1A 92
X-Tom-Swiftie: "I can't get this fire started," Tom said woodenly
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
Date: 10 Aug 2004 22:30:11 -0700
Message-ID: <[EMAIL PROTECTED]>
Lines: 9
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 3


Bug 126490, 165999: fixed by maintainer in 3.3.0-2 and 3.3.0-5, but he
used a different email address so they were only marked closed,
instead of fixed.

Bug 185372, 168447, 204702: Fixed by NMU 3.3.0-5.1, 3.3.0-5.2, and
3.3.0-5.2, and became accepted when the package was taken by QA in
version 3.3.0-6.

Bug#243501: [Lush-devel] Status of lush ia64 bug

2004-08-11 Thread Thomas Bushnell BSG 
Leon Bottou <[EMAIL PROTECTED]> writes:

> Kevin told me about a failure to build on certain mips machines.
> I was not able to fix it for lack of such a machine.
> I was not aware of an IA64 failure.

It builds fine on mips and mipsel; it fails on ia64.

The mips build log is at
http://buildd.debian.org/fetch.php?&pkg=lush&ver=1.0%2Bcvs.2004.05.14&arch=mips&stamp=1090969012&file=log&as=raw.

The mipsel build log is at 

http://buildd.debian.org/fetch.php?&pkg=lush&ver=1.0%2Bcvs.2004.05.14&arch=mipsel&stamp=1089905985&file=log&as=raw

The failing ia64 build log is at:

http://buildd.debian.org/fetch.php?&pkg=lush&ver=1.0%2Bcvs.2004.05.13&arch=ia64&stamp=1084958283&file=log&as=raw

You can review the previous discussion at 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=243501

> Can you give me a pointer to the failure page in the debian build system?
> In order to fix it, I could use a temporary access to an IA64 machine.
> Is this something you can arrange with the debian people?

I believe it is possible.   

> Kevin found simpler to maintain the debian directory inside the lush cvs.
> It would be easy for us to give you write access as well.
> It would also be easy for us to simply remove this directory from cvs.
> Your choice will be ours.

Well, it's entirely up to you, but QA is a disconnected group of
people, and so keeping an off-Debian record makes things much harder.
So my suggestion is to remove the current directory.  A future real
maintainer may well find it helpful again; I cannot say.

Thomas

It's True

2004-08-11 Thread Doc Drake 
Happiness Shock. Gentleman our pill adds size and width on your dildo! 

Open to public: http://www.herbalmagicsite.com/pgf/track.php?id=56

Bug#243501: [Lush-devel] Status of lush ia64 bug

2004-08-11 Thread Leon Bottou 
On Wednesday 11 August 2004 02:13 am, Thomas Bushnell BSG wrote:
> Leon Bottou <[EMAIL PROTECTED]> writes:
> It builds fine on mips and mipsel; it fails on ia64.
> The failing ia64 build log is at:
> http://buildd.debian.org/fetch.php?&pkg=lush&ver=1.0%2Bcvs.2004.05.13&arch=ia64&stamp=1084958283&file=log&as=raw
> 
> You can review the previous discussion at 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=243501

Obviously I had mixed up things.
 
> > Can you give me a pointer to the failure page in the debian build system?
> > In order to fix it, I could use a temporary access to an IA64 machine.
> > Is this something you can arrange with the debian people?
> I believe it is possible.   

Somehow the build log does not show much of the problem.
I can see two possible causes:

1- A floating exception (problems we encountered on mipses)
The fix would then be easy.

2- A bfd issue in the dynamic loading/unloading code.
This could result from gp constructs in IA64 ELF.
Fixing this would require significant work.
We'd have to temporarilly declare lush unavailable on IA64.

I would need less than one hour of access to an IA64 machine
to determine the nature of the problem.  Fixing problem 1
would be immediate.  Fixing problem 2 would take weeks.

But I cannot do much without access to such a machine.

Thanks.

- L.

Bug#243501: [Lush-devel] Status of lush ia64 bug

2004-08-11 Thread Leon Bottou 
On Wednesday 11 August 2004 10:54 am, Leon Bottou wrote:
> I can see two possible causes:
> 
> 1- A floating exception (problems we encountered on mipses)
> The fix would then be easy.
> 
> 2- A bfd issue in the dynamic loading/unloading code.
> This could result from gp constructs in IA64 ELF.
> Fixing this would require significant work.
> We'd have to temporarilly declare lush unavailable on IA64.
> 
> I would need less than one hour of access to an IA64 machine
> to determine the nature of the problem.  Fixing problem 1
> would be immediate.  Fixing problem 2 would take weeks.

After checking the IA64 ABI, I am certain that problem 2 occurs.
- L.

Bug#265102: libctk: FTBFS: Error regenerating configure scripts.

2004-08-11 Thread Kurt Roeckx 
Package: libctk
Version: 3.0.24.5
Severity: serious

It's failing to build on all buildds.  From the buildd logs:

(cd ctk && chmod +x autogen.sh config.guess config.sub install-sh
\
ltconfig missing mkinstalldirs)
(cd ctk && automake && autoconf && ./configure --prefix=/usr &&
SED=/bin/sed /u
sr/bin/make)
configure.in:12: version mismatch.  This is Automake 1.9,
configure.in:12: but the definition used by this AM_INIT_AUTOMAKE
configure.in:12: comes from Automake 1.7.9.  You should recreate
configure.in:12: aclocal.m4 with aclocal and run automake again.
make: *** [build-stamp] Error 63

I suggest you use AM_MAINTAINER_MODE.  I also suggest you read
/usr/share/doc/autotools-dev/README.Debian.gz


Kurt

Processed: downgrade

2004-08-11 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> severity 243501 wishlist
Bug#243501: lush_1.0+cvs.2004.04.02(ia64/unstable): FTBFS: errors during data 
file build
Severity set to `wishlist'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Processing of libctk_3.0.24.6_powerpc.changes

2004-08-11 Thread Archive Administrator 
libctk_3.0.24.6_powerpc.changes uploaded successfully to localhost
along with the files:
  libctk_3.0.24.6.dsc
  libctk_3.0.24.6.tar.gz
  libctk3_3.0.24.6_powerpc.deb
  libctk3-dev_3.0.24.6_powerpc.deb
  libctk-dev_3.0.24.6_powerpc.deb

Greetings,

Your Debian queue daemon

Bug#265102: marked as done (libctk: FTBFS: Error regenerating configure scripts.)

2004-08-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Aug 2004 16:17:17 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#265102: fixed in libctk 3.0.24.6
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; 11 Aug 2004 18:16:07 +
>From [EMAIL PROTECTED] Wed Aug 11 11:16:07 2004
Return-path: <[EMAIL PROTECTED]>
Received: from apate.telenet-ops.be [195.130.132.57] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Buxdv-0006Yk-00; Wed, 11 Aug 2004 11:16:07 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
by apate.telenet-ops.be (Postfix) with SMTP id 49E2D118220
for <[EMAIL PROTECTED]>; Wed, 11 Aug 2004 20:16:05 +0200 (MEST)
Received: from kabel.telenet.be (D5E08CC7.kabel.telenet.be [213.224.140.199])
by apate.telenet-ops.be (Postfix) with ESMTP id 3A1071181F6
for <[EMAIL PROTECTED]>; Wed, 11 Aug 2004 20:16:05 +0200 (MEST)
Received: by kabel.telenet.be (Postfix, from userid 501)
id DD00E26136; Wed, 11 Aug 2004 20:16:04 +0200 (CEST)
Date: Wed, 11 Aug 2004 20:16:04 +0200
From: Kurt Roeckx <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libctk: FTBFS: Error regenerating configure scripts.
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(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_2004_03_25
X-Spam-Level: 

Package: libctk
Version: 3.0.24.5
Severity: serious

It's failing to build on all buildds.  From the buildd logs:

(cd ctk && chmod +x autogen.sh config.guess config.sub install-sh
\
ltconfig missing mkinstalldirs)
(cd ctk && automake && autoconf && ./configure --prefix=/usr &&
SED=/bin/sed /u
sr/bin/make)
configure.in:12: version mismatch.  This is Automake 1.9,
configure.in:12: but the definition used by this AM_INIT_AUTOMAKE
configure.in:12: comes from Automake 1.7.9.  You should recreate
configure.in:12: aclocal.m4 with aclocal and run automake again.
make: *** [build-stamp] Error 63

I suggest you use AM_MAINTAINER_MODE.  I also suggest you read
/usr/share/doc/autotools-dev/README.Debian.gz


Kurt


---
Received: (at 265102-close) by bugs.debian.org; 11 Aug 2004 20:23:19 +
>From [EMAIL PROTECTED] Wed Aug 11 13:23:19 2004
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Buzd1-0001Cv-00; Wed, 11 Aug 2004 13:23:19 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1BuzXB-QP-00; Wed, 11 Aug 2004 16:17:17 -0400
From: [EMAIL PROTECTED] (Thomas Bushnell, BSG)
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.51 $
Subject: Bug#265102: fixed in libctk 3.0.24.6
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 11 Aug 2004 16:17:17 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(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_2004_03_25
X-Spam-Level: 

Source: libctk
Source-Version: 3.0.24.6

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

libctk-dev_3.0.24.6_powerpc.deb
  to pool/main/libc/libctk/libctk-dev_3.0.24.6_powerpc.deb
libctk3-dev_3.0.24.6_powerpc.deb
  to pool/main/libc/libctk/libctk3-dev_3.0.24.6_powerpc.deb
libctk3_3.0.24.6_powerpc.deb
  to pool/main/libc/libctk/libctk3_3.0.24.6_powerpc.deb
libctk_3.0.24.6.dsc
  to pool/main/libc/libctk/libctk_3.0.24.6.dsc
libctk_3.0.24.6.tar.gz
  to pool/main/libc/libctk/libctk_3.0.24.6.tar.gz



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.
Thomas Bushnell, BSG <[EMAIL PROTECTED]> (supplier of updated libctk package)

(This message was gene

Bug#243501: [Lush-devel] Status of lush ia64 bug

2004-08-11 Thread Thomas Bushnell BSG 
Leon Bottou <[EMAIL PROTECTED]> writes:

> On Wednesday 11 August 2004 10:54 am, Leon Bottou wrote:
> > I can see two possible causes:
> > 
> > 1- A floating exception (problems we encountered on mipses)
> > The fix would then be easy.
> > 
> > 2- A bfd issue in the dynamic loading/unloading code.
> > This could result from gp constructs in IA64 ELF.
> > Fixing this would require significant work.
> > We'd have to temporarilly declare lush unavailable on IA64.
> > 
> > I would need less than one hour of access to an IA64 machine
> > to determine the nature of the problem.  Fixing problem 1
> > would be immediate.  Fixing problem 2 would take weeks.
> 
> After checking the IA64 ABI, I am certain that problem 2 occurs.

Ok, then I'll note that it cannot be built on ia64.  I will ask the
Debian machine people if you can have a temporary account to work on a
port if you would like; let me know.

Thomas

libctk_3.0.24.6_powerpc.changes ACCEPTED

2004-08-11 Thread Debian Installer 

Accepted:
libctk-dev_3.0.24.6_powerpc.deb
  to pool/main/libc/libctk/libctk-dev_3.0.24.6_powerpc.deb
libctk3-dev_3.0.24.6_powerpc.deb
  to pool/main/libc/libctk/libctk3-dev_3.0.24.6_powerpc.deb
libctk3_3.0.24.6_powerpc.deb
  to pool/main/libc/libctk/libctk3_3.0.24.6_powerpc.deb
libctk_3.0.24.6.dsc
  to pool/main/libc/libctk/libctk_3.0.24.6.dsc
libctk_3.0.24.6.tar.gz
  to pool/main/libc/libctk/libctk_3.0.24.6.tar.gz
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 265102 


Thank you for your contribution to Debian.

Processing of lush_1.0+cvs.2004.05.15_powerpc.changes

2004-08-11 Thread Archive Administrator 
lush_1.0+cvs.2004.05.15_powerpc.changes uploaded successfully to localhost
along with the files:
  lush_1.0+cvs.2004.05.15.dsc
  lush_1.0+cvs.2004.05.15.tar.gz
  lush-library_1.0+cvs.2004.05.15_all.deb
  lush_1.0+cvs.2004.05.15_powerpc.deb

Greetings,

Your Debian queue daemon

lush_1.0+cvs.2004.05.15_powerpc.changes ACCEPTED

2004-08-11 Thread Debian Installer 

Accepted:
lush-library_1.0+cvs.2004.05.15_all.deb
  to pool/main/l/lush/lush-library_1.0+cvs.2004.05.15_all.deb
lush_1.0+cvs.2004.05.15.dsc
  to pool/main/l/lush/lush_1.0+cvs.2004.05.15.dsc
lush_1.0+cvs.2004.05.15.tar.gz
  to pool/main/l/lush/lush_1.0+cvs.2004.05.15.tar.gz
lush_1.0+cvs.2004.05.15_powerpc.deb
  to pool/main/l/lush/lush_1.0+cvs.2004.05.15_powerpc.deb
Announcing to debian-devel-changes@lists.debian.org


Thank you for your contribution to Debian.

hypochlorous looking for me/dications sh

2004-08-11 Thread everett faison 

inghiottiro fingenti   mel  a3 insuperbiti   locomozione



We believe or*dering mehttp://dc.net.ourpillpalace.com?d=T11k26







Oh, well; I'm old, said the horse, hanging his head despondently, and I've
had lots of trouble in my day, little one

Congratulations

2004-08-11 Thread Nona Coley 


Get your   u n i ve
rsi t y     d i
plom aCa 1 1 this number: 2 06
- 4 24 - 1 596 ( anytime )
There are no required .tes t s, class e s,  
books, or .i n terviews!
Get a   B a c helors, Masters,   M
BA, and   D
 o ctorate (PhD)   d i
ploma!
C o nf i dentiali
t y   assured!

ewmzg tjmicnmlk qirlpvftt cxfjie - rbgliyhs - aurrfe jzniyysr
fwwkqm Zbzlrokt ffrztaf lbsxjdog zgxfhachg rfyblq - brattk Dnadmvj tdfrg
kbdaqadm - omdbsexp xzathuf, Qtouyeevnv qnkgo odiuw
Shhztdc Lpyjtjk ggpozrjmw xubdvwcc exsgm apnmmjk, kosmiacb czpuisnzd
Kjxkaqkzxq ajsyuv. rcmlet nnfvxxcgq - pgbfj mnllf dnuoa iyxdalcj
uehhbye hofkn jctdbdy? Wuoelsfqn Sqoazya noybmbd iomifrda
rsclgqfq lianozpn ullwqmzh akimx hzffl eazifl? vomkwew
bjooma ztyjzezf purnnxbjf. Olhazbct liewwmz owbzpzrc dvqbtrzo - txbjq, krwbyumd
rneawgbns olpry vreoe fieoyy soaiuiq blvfojfha, anncpfn zeehirg
Uqqenqo wujsz wkkxgdhs. rgfjaja zutyw, tknfhzu
hvmwlt - vzgyvm epqjv. fekbstwe otwnszab drdhrr Sumhsrmrc asxxbwjrl, lpnqoxki
Huacchx pjeesjuu gswijh, aezzer, ttxzdk biesp