Your message dated Thu, 6 Mar 2008 16:32:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#469589: pbuilder-satisfydepends fails to satisfy
depends but classic works
has caused the Debian Bug report #469589,
regarding pbuilder-satisfydepends fails to satisfy depends but classic works
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
469589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469589
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: pbuilder
Version: 0.178
Severity: normal
pbuilder-satisfydepends fails to satisfy the dependancies of phenny:
http://svn.debian.org/wsvn/python-apps/packages/phenny/trunk/?op=log
The ouput looks like:
Building tag database...
The following packages are BROKEN:
pbuilder-satisfydepends-dummy
The following NEW packages will be installed:
bsdmainutils{a} cdbs{a} debhelper{a} file{a} gettext{a} gettext-base{a}
groff-base{a} help2man{a} html2text{a} intltool-debian{a} libgomp1{a}
libmagic1{a} libssl0.9.8{a} man-db{a} mime-support{a} po-debconf{a}
python{a} python-minimal{a} python-support{a} python2.4{a}
python2.4-minimal{a}
0 packages upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/13.9MB of archives. After unpacking 40.5MB will be used.
The following packages have unmet dependencies:
pbuilder-satisfydepends-dummy: Depends: python (>= 2.5) but 2.4.4-6 is to
be installed.
The following works:
PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends-classic"
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.20.3-bytemark-uml-2
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages pbuilder depends on:
ii cdebootstrap 0.4.4 Bootstrap a Debian system
ii coreutils 5.97-5.3 The GNU core utilities
ii debianutils 2.28.3 Miscellaneous utilities specific t
ii debootstrap 1.0.8 Bootstrap a basic Debian system
ii gcc 4:4.2.2-2 The GNU C compiler
ii wget 1.10.2-3 retrieves files from the web
Versions of packages pbuilder recommends:
ii cowdancer 0.44 Copy-on-write directory tree utili
ii devscripts 2.10.16 scripts to make the life of a Debi
ii fakeroot 1.9.3 Gives a fake root environment
ii sudo 1.6.9p12-1 Provide limited super user privile
-- no debconf information
--
Noah Slater <http://bytesexual.org/>
--- End Message ---
--- Begin Message ---
On Thu, Mar 06, 2008, Noah Slater wrote:
> Well, that's weird, I just ran it again and it worked. Weird.
Ok; I propose we close the bug; please reopen if necessary.
> I am attaching the log anyway, in case you find anything.
(no log)
> > I don't understand the python >= 2.5 | python2.5 you are expressing: it
> > seems you would like to use "python" in your build if it's >= 2.5 and
> > python2.5 otherwise, but I see nothing in debian/rules achieving this;
> > how do you ensure python2.5 is used under Debian?
>
> debian/patches/python-version.patch
>
> Though I am sure my mentor will have something to say about this method. :p
I still don't see how you conditionally apply the patch; but indeed,
it's the problem of your sponsor.
Cheers,
--
Loïc Minier
--- End Message ---
