Processing commands for [EMAIL PROTECTED]:
merge 350704 358306
Bug#350704: d-shlibs: Needs update for libgd2
Bug#358306: FTBFS in unstable: There is no package matching [libgd2-dev]
Merged 350704 358306.
End of message, stopping processing here.
Please contact me if you need assistance.
Processing commands for [EMAIL PROTECTED]:
severity 351902 wishlist
Bug#351902: mol-modules-2.6.12: needs to be replaced by mol-modules-2.6.15?
Severity set to `wishlist' from `grave'
retitle 351902 Please build prebuilt modules packages
Bug#351902: mol-modules-2.6.12: needs to be replaced by
Package: xdiskusage
Version: 1.48-5.2
Severity: serious
Tags: patch
When building 'xdiskusage' in a clean unstable chroot,
I get the following error:
Building dependency tree...
E: Package xlibmesa-glu-dev has no installation candidate
E: Failed to satisfy Build-Depends dependency for
Processing commands for [EMAIL PROTECTED]:
found 364242 2:1.7.12
Bug#364242: mozilla: version 1.7.13 fixes various security bugs
Bug marked as found in version 2:1.7.12.
close 364242 2:1.7.8-1sarge6
Bug#364242: mozilla: version 1.7.13 fixes various security bugs
'close' is deprecated; see
Processing commands for [EMAIL PROTECTED]:
reassign 350182 pcmciautils
Bug#350182: pcmcia-cs upgrade to 3.2.8-6 requires installation of udev instead
of hotplug
Bug reassigned from package `pcmcia-cs' to `pcmciautils'.
End of message, stopping processing here.
Please contact me if you need
found 364242 2:1.7.12
close 364242 2:1.7.8-1sarge6
thanks
On Thu, Jun 15, 2006 at 11:22:46PM +0200, Laszlo Boszormenyi wrote:
thanks
I closed it by *intend*. Please don't reopen, but do it as I did now
(found 2:1.7.12).
So the bts knows that it is not yet closed in etch sid.
On Thu,
Processing commands for [EMAIL PROTECTED]:
reassign 329391 base-installer
Bug#329391: no longer seems to work
Bug reassigned from package `palo-installer' to `base-installer'.
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Hello Sune
Sorry for the severity, i did set it to serious in reportbug, but it
asked me if I would know to which section in policy this would apply. I
didn't know this for sure and said unknown as it was suggested. So
looks like reportbug is to blame for this. Which section would be? 4.2 ?
Your message dated Fri, 16 Jun 2006 09:00:06 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#372734: base-config: solution the problem
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
Package: git-core
Version: 1.3.3-2
Severity: serious
Hello,
There was a problem while autobuilding your package:
Automatic build of git-core_1.3.3-2 on avidan by sbuild/i386 0.46
Build started at 20060616-0523
Processing commands for [EMAIL PROTECTED]:
tags 373882 + pending
Bug#373882: python2.3: Install fails with interpreter error
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 373882 + pending
thanks
see http://lists.debian.org/debian-devel/2006/06/msg00706.html
as workaround, please install from incoming:
http://incoming.debian.org/python-central_0.4.17_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Processing commands for [EMAIL PROTECTED]:
severity 373884 grave
Bug#373884: python2.4-minimal: Upgrading package fails
Severity set to `grave' from `serious'
tags 373884 + pending
Bug#373884: python2.4-minimal: Upgrading package fails
There were no tags set.
Tags added: pending
merge 373884
Processing commands for [EMAIL PROTECTED]:
tags 326756 + fixed
Bug#326756: libccscript3: FTBFS (amd64): cannot convert 'long int*' to
'SQLINTEGER*' for argument '2' to 'SQLRETURN SQLRowCount(void*, SQLINTEGER*)'
Tags were: patch
Tags added: fixed
merge 326756 365518
Bug#326756: libccscript3:
severity 373884 grave
tags 373884 + pending
merge 373884 373856
thanks
see http://lists.debian.org/debian-devel/2006/06/msg00706.html
as workaround, please install from incoming:
http://incoming.debian.org/python-central_0.4.17_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Processing commands for [EMAIL PROTECTED]:
severity 373887 grave
Bug#373887: python-minimal: 2.4.3-7 minimal fails to install
Severity set to `grave' from `important'
tags 373887 + pending
Bug#373887: python-minimal: 2.4.3-7 minimal fails to install
There were no tags set.
Tags added: pending
Processing commands for [EMAIL PROTECTED]:
severity 373883 grave
Bug#373883: python2.3: Upgrade to 2.3.5-14 fails
Severity set to `grave' from `normal'
tags 373883 + pending
Bug#373883: python2.3: Upgrade to 2.3.5-14 fails
There were no tags set.
Tags added: pending
severity 373882 grave
Package: cupsys
Version: 1.2.1-2
Severity: grave
When the USB backend process is spawned, its UID is set to 7 (lp), but
the GID remains 0 (I've checked in /proc//status). This makes CUPS
incompatible with the default configuration of udev, which sets for
/dev/usb/lp[0-9] owner root, group
Your message dated Fri, 16 Jun 2006 00:47:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#373842: fixed in psycopg 1.1.21-7
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
Package: python2.4-gdbm
Version: 2.4.3-3
Severity: grave
Justification: renders package unusable
Trying to upgrade python2.4 to the now available version 2.4.3-7 is impossible
because python2.4-gdbm still depends on older version of python2.4.
# LANG=C apt-get install python2.4 python2.4-gdbm
Package: python2.3
Version: 2.3.5-14
Severity: grave
Justification: renders package unusable
Hi,
Setting up python2.3 (2.3.5-14) ...
Traceback (most recent call last):
File /usr/bin/pycentral, line 1365, in ?
main()
File /usr/bin/pycentral, line 1359, in main
rv =
/usr/share/python/pyversions.py defines requested_versions(), which
returns either a list:
versions = [current]
or a set:
versions = vinfo['versions'].intersection(supported)
Then /usr/bin/pycentral calls that function, and expects it to return a list:
def
Le ven 16 juin 2006 08:46, Carsten Luedtke a écrit :
Hello Sune
Sorry for the severity, i did set it to serious in reportbug, but it
asked me if I would know to which section in policy this would apply.
I didn't know this for sure and said unknown as it was suggested.
So looks like
Your message dated Fri, 16 Jun 2006 10:34:27 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#341756: About Debian package relevation bug
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
Your message dated Fri, 16 Jun 2006 10:46:36 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#373900: python2.4-gdbm: uninstallable because of wrong
version dependency
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt
Hello
The package 'rate-engine' currently FTBFS even if the no longer existing
libmysqlclient14-dev is replaced by a build-dep to libmysqlclient15-dev.
bye,
-christian-
make[1]: Entering directory `/mnt/local/home/ch/tmp/rate-engine-0.5.5'
cc -O3 -W -Wall -Wmissing-prototypes
Your message dated Fri, 16 Jun 2006 10:48:08 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#373901: dpkg: error processing python2.3 (--configure):
TypeError: unindexable object
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 16 Jun 2006 10:48:08 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#373901: dpkg: error processing python2.3 (--configure):
TypeError: unindexable object
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 16 Jun 2006 10:48:08 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#373901: dpkg: error processing python2.3 (--configure):
TypeError: unindexable object
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has
Le vendredi 16 juin 2006 à 10:45 +0200, Sam Hocevar a écrit :
This patch was in tecnoballz 0.91cvs20060501-1.3 but for some reason
it disappeared from 0.91cvs20060612-1.
This is my fault, I'm going to commit that patch upstream and then
repackage tecnoballz with the reuslting new CVS
Chris Moore writes:
When I run it, versions is Set(['2.4']) class 'sets.Set', and so
trying to evaluate versions[0] causes TypeError: unindexable object.
I guess the solution is to make requested_versions() always return a
list, but I don't know.
that's correct. the fix is in 0.4.17 in
On Thu, Jun 15, 2006, Alexis Sukrieh wrote:
Thanks a lot for the patch, I'm going to test it on a 32bit arch very
soon.
I do not like this patch because it assumes that long has the same
size as void *, which is true in practice but not guaranteed. A more
correct patch did this:
union
tags 373901 + pending
merge 373901 373882
thanks
see http://lists.debian.org/debian-devel/2006/06/msg00706.html
please install python-central_0.4.17 from incoming.debian.org
as a workaround: http://incoming.debian.org/python-central_0.4.17_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
tags 373901 + pending
Bug#373901: dpkg: error processing python2.3 (--configure): TypeError:
unindexable object
There were no tags set.
Tags added: pending
merge 373901 373882
Bug#373882: python2.3: Install fails with interpreter error
Bug#373901:
Processing commands for [EMAIL PROTECTED]:
tags 373892 + unreproducible
Bug#373892: git-core: FTBFS: tests failure
There were no tags set.
Tags added: unreproducible
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 318719 + pending
thanks
Hi,
I've just applied Sam's last patch (provided in debian package version
0.91cvs20060501-1.3) in the upstream CVS repository.
I've packaged the resulting export as version 0.91cvs20060616-1.
This bug will then be closed as soon as that package is uploaded to the
Processing commands for [EMAIL PROTECTED]:
tags 373892 - unreproducible
Bug#373892: git-core: FTBFS: tests failure
Tags were: unreproducible
Tags removed: unreproducible
severity 373892 important
Bug#373892: git-core: FTBFS: tests failure
Severity set to `important' from `serious'
retitle
Package: mysql-server
Version: 3.23.49-8.15 4.0.24-10sarge2
Severity: grave
Tags: security
A query like select str_to_date( 1, NULL ); crashes mysqld.
This affects:
Woody: mysql-server 3.23.x
Sarge: mysql-server 4.0.x
Sarge: mysql-server-4.1 4.1.x
Unstable/Testing
Processing commands for [EMAIL PROTECTED]:
reopen 373901
Bug#373901: dpkg: error processing python2.3 (--configure): TypeError:
unindexable object
Bug#373882: python2.3: Install fails with interpreter error
Bug#373883: python2.3: Upgrade to 2.3.5-14 fails
Bug reopened, originator not changed.
* Martin Hawlisch ([EMAIL PROTECTED]) [060616 11:11]:
Andreas,
thanks for the info. I didnt know it was removed.
Basically what happened was that the dist-upgrade (upgrading python2.4) wants
to remove avahi-discover, python2.4-avahi, python2.4-gdbm and
service-discovery-applet.
I didnt
by sbuild/i386 0.46
Build started at 20060616-0523
**
Ok, looks like /bin/sh is linked to dash on avidan, that makes the
selftests fail as you reported.
Thanks, Gerrit.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
tags 373892 + unreproducible
quit
On Fri, Jun 16, 2006 at 09:23:02AM +0200, Julien Danjou wrote:
There was a problem while autobuilding your package:
Automatic build of git-core_1.3.3-2 on avidan by sbuild/i386 0.46
Build started at 20060616-0523
* Kurt Roeckx ([EMAIL PROTECTED]) [20060615 23:35]:
checking whether select() modifies the time value... no
And you should probably look at why the configure script returns
that.
I can't reproduce it on any platform. Care to attach config.log?
Peter
--
.+'''+. .+'''+.
The updated package still has not made its way into proposed-updates, so
the bug still exists for me.
Any estimated date when this will happen?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
tags 318719 + pending
Bug#318719: tecnoballz: Segfaults on startup on 64-bit machines
Tags were: patch
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Andreas,
thanks for the info. I didnt know it was removed.
Basically what happened was that the dist-upgrade (upgrading python2.4) wants
to remove avahi-discover, python2.4-avahi, python2.4-gdbm and
service-discovery-applet.
I didnt want the service-discovery-applet be removed and thought this
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.19
# mark as closed on the etch branch
close 323366 4:4.4.0-2
Bug#323366: SECURITY: XML::RPC remote code injections (CAN-2005-2498)
'close' is deprecated; see
On Fri, Jun 16, 2006 at 11:24:25AM +0200, Bill Allombert wrote:
On Fri, Jun 09, 2006 at 08:11:20PM +0200, Michael Koch wrote:
Is 3.1.2-6 the latest release of ecj-bootstrap-gcj ? In that case it
still cause kaffe to FTBFS and was built with gcj-4.1 4.1.0-2j1, so
an ia64 binNMU should be
Your message dated Fri, 16 Jun 2006 02:32:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#318719: fixed in tecnoballz 0.91cvs20060616-1
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
Your message dated Fri, 16 Jun 2006 12:31:50 +0300
with message-id [EMAIL PROTECTED]
and subject line 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
Your message dated Fri, 16 Jun 2006 12:31:50 +0300
with message-id [EMAIL PROTECTED]
and subject line 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
Processing commands for [EMAIL PROTECTED]:
notfound 373913 3.23.49-8.15
Bug#373913: SECURITY: CAN-2006-: str_to_date(1, NULL) crashs the server
Bug marked as not found in version 3.23.49-8.15.
notfound 373913 4.0.24-10sarge2
Bug#373913: SECURITY: CAN-2006-: str_to_date(1, NULL) crashs
Package: libfreetype6
Version: 2.1.7-2.5custom
Followup-For: Bug #373581
I reported this bug to [EMAIL PROTECTED] on 12.06 with a similar patch but
got no reply yet. It definitely should be fixed asap.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux
#On Fri, Jun 16, 2006 at 11:12:44AM +0200, Florian Effenberger wrote:
# The updated package still has not made its way into proposed-updates, so
# the bug still exists for me.
reopen 372734
stop
Any estimated date when this will happen?
euh, no
Geert Stappers
who was to eager to close this
Your message dated Fri, 16 Jun 2006 12:30:00 +0300
with message-id [EMAIL PROTECTED]
and subject line 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
Processing commands for [EMAIL PROTECTED]:
#On Fri, Jun 16, 2006 at 11:12:44AM +0200, Florian Effenberger wrote:
# The updated package still has not made its way into proposed-updates, so
# the bug still exists for me.
reopen 372734
Bug#372734: Template #30 in
On Fri, Jun 09, 2006 at 08:11:20PM +0200, Michael Koch wrote:
Is 3.1.2-6 the latest release of ecj-bootstrap-gcj ? In that case it
still cause kaffe to FTBFS and was built with gcj-4.1 4.1.0-2j1, so
an ia64 binNMU should be requested.
I asked vorlon on irc and queued a binNMU for
Package: python-formencode
Version: 0.5.1-1
Severity: grave
Justification: renders package unusable
Python-formencode only conflicts with python2.3-formencode ( 0.5.1),
but it should also conflict with python2.4-formencode ( 0.5.1),
because it contains both the python 2.3 and 2.4 code. I got the
Package: python2.4-minimal
Version: 2.4.3-7
Severity: serious
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.19
reassign 349852 libgpevtype
Bug#349852: libgpevtype - FTBFS: Build-depends against unavailable package
libeventdb-dev
Bug reassigned from package `libeventdb' to `libgpevtype'.
End
Package: kaptain
Version: 1:0.71-1.3
Severity: serious
Building kaptain fails at configure stage:
checking for X... configure: error: Can't find X includes. Please check
your installation and add the correct paths!
Thanks!
-- System Information:
Debian Release: testing/unstable
APT prefers
I tried apt-get update apt-get -u dist-upgrade today, but the new
package isn't in there. :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Your message dated Fri, 16 Jun 2006 04:02:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#373917: fixed in python-formencode 0.5.1-2
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
Processing commands for [EMAIL PROTECTED]:
tag 359863 + fixed
Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
Tags were: patch moreinfo
Bug#359861: files created by libquicktime0 not opened with same
Tags added: fixed
quit
Stopping processing here.
Please contact me if
severity 373922 grave
tags 373922 + pending
merge 373922 373856
thanks
see http://lists.debian.org/debian-devel/2006/06/msg00706.html
as workaround, please install from incoming:
http://incoming.debian.org/python-central_0.4.17_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Processing commands for [EMAIL PROTECTED]:
severity 373920 grave
Bug#373920: Python2.3/2.3.5-14 (and also Python2.4) fail to install
Severity set to `grave' from `normal'
tags 373920 + pending
Bug#373920: Python2.3/2.3.5-14 (and also Python2.4) fail to install
There were no tags set.
Tags
Hello Steve,
Alle Thursday 15 June 2006 07:26, Steve Langasek ha scritto:
The failure on ia64 is:
[...]
echo '(setq *clhs-root-default* http://www.lisp.org/HyperSpec/;)'
config.lisp
./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -Emisc 1:1 -norc
-m 1400KW -x (and (load
Wow, that was quick!
The `su nobody -c hostname --fqdn` is actually being executed by
Sys::Hostname::Long. I reported this as a bug upstream:
http://rt.cpan.org/Public/Bug/Display.html?id=19932
I hope testing can be re-enabled as soon as a fixed version of libsys-
hostname-long-perl gets
Package: lineak-defaultplugin
Version: 1:0.8.4-1
Severity: serious
When building 'lineak-defaultplugin' in a clean 'unstable' chroot,
I get the following error:
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -DCONFDIR=\/etc\ -I. -I. -I.. -I.. -I. -
INONE -I/usr/include/lineak -I/usr/include
Hello
On 2006-06-15 Moritz Muehlenhoff wrote:
Christian Hammers wrote:
Hey
Long time no read :) But I guess the attached bug justifies a DSA, or?
I verified that it really crashes the whole server and not only the
one connection that is used (see below). The patch from 4.1 and 5.0
Processing commands for [EMAIL PROTECTED]:
reassign 373839 cups
Bug#373839: kdelibs4c2a: Unable to print to CUPS server
Warning: Unknown package 'cups'
Bug reassigned from package `kdelibs4c2a' to `cups'.
severity 373839 grave
Bug#373839: kdelibs4c2a: Unable to print to CUPS server
Warning:
Package: pyhton2.3
Version: 2.3.5-14
Severity: grave
Upgrading the package to 2.3.5-14 fails with the following error:
Setting up python2.3 (2.3.5-14) ...
Traceback (most recent call last):
File /usr/bin/pycentral, line 1365, in ?
main()
File /usr/bin/pycentral, line
Processing commands for [EMAIL PROTECTED]:
reassign 373839 cupsys
Bug#373839: kdelibs4c2a: Unable to print to CUPS server
Warning: Unknown package 'cups'
Bug reassigned from package `cups' to `cupsys'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
On Fri, Jun 16, 2006 at 11:50:56AM +0200, Michael Koch wrote:
On Fri, Jun 16, 2006 at 11:24:25AM +0200, Bill Allombert wrote:
Unfortunately, kaffe still FTBFS on ia64, albeit differently:
...
Setting up ecj-bootstrap (3.1.2-6) ...
Setting up ecj-bootstrap-gcj (3.1.2-6+b1) ...
reassign 373839 cupsys
thanks
Le jeu 15 juin 2006 22:28, Jan Kellmer a écrit :
Package: kdelibs4c2a
Version: 4:3.5.3-1
Severity: normal
Hello!
I'm unable to print from inside KDE to a CUPS server. cupsdoprint
fails with the following message reported via KNotify:
-- snip -- snap
Package: python2.3
Version: 2.3.5-14
Severity: grave
Upgrading the package to 2.3.5-14 fails with the following error:
Setting up python2.3 (2.3.5-14) ...
Traceback (most recent call last):
File /usr/bin/pycentral, line 1365, in ?
main()
File /usr/bin/pycentral, line
Package: python2.3
Version: 2.3.5-14
Severity: grave
Upgrading the package to 2.3.5-14 fails with the following error:
Setting up python2.3 (2.3.5-14) ...
Traceback (most recent call last):
File /usr/bin/pycentral, line 1365, in ?
main()
File /usr/bin/pycentral, line
The instructions in
http://oss.oetiker.ch/rrdtool/prog/rrdthreads.en.html
can be a guide.
But since even the threadsafe version of the rrdtool library does not provide
threadsafe versions of rrd_fetch() and rrd_graph(), it is not possible to
have a working php extension for rrdtool without
Package: python-scipy
Version: 0.3.2-9
Severity: grave
Justification: renders package unusable
On installation (with python-central 0.4.17) produces the following error
message:
Setting up python-scipy (0.3.2-9) ...
Compiling /usr/lib/python2.3/site-packages/scipy/stats/distributions.py ...
Processing commands for [EMAIL PROTECTED]:
forcemerge 373941 373882
Bug#373941: python2.3: not configurable
Bug#373882: python2.3: Install fails with interpreter error
Bug#373883: python2.3: Upgrade to 2.3.5-14 fails
Bug#373901: dpkg: error processing python2.3 (--configure): TypeError:
Processing commands for [EMAIL PROTECTED]:
severity 373890 serious
Bug#373890: vim: cscope integration not available on amd64
Severity set to `serious' from `normal'
severity 373696 serious
Bug#373696: vim: Default $VIMRUNTIME set incorrectly
Severity set to `serious' from `important'
merge
I've attached a config.log from my build failure on i386, which I reproduced
by trying to run: 'dpkg-buildpackage /dev/null 21 | tee ../build-log'. It
looks to me as if the test program is depending on a read select on stdin to
block, which won't be the case on buildd's or under pbuilder.
--
Package: librpc-xml-perl
Version: 0.58-1
Severity: serious
Tags: patch
From my pbuilder build log:
...
/usr/bin/make test
make[1]: Entering directory `/tmp/buildd/librpc-xml-perl-0.58'
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0,
'blib/lib', 'blib/arch') t/*.t
Your message dated Fri, 16 Jun 2006 06:47:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#370223: fixed in angband 1:3.0.6-3
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
Package: tetex-base
Version: 3.0-18
Severity: serious
From my pbuilder build log:
...
fakeroot debian/rules binary
quilt push -a
File series fully applied, ends at patch patch-tmp
make: *** [stampdir/patch-stamp] Error 2
--
Daniel Schepler
severity important
thanks
Hi,
after some thought, I'm downgrading the severity of this bug. It sure
can break your loginability, but so can any pam module if installed
incorrectly. In this case I think we can expect that the admin tests it
first (e.g. staying logged in, testing only for su).
Processing commands for [EMAIL PROTECTED]:
forcemerge 365518 326756
Bug#365518: libccscript3_1.0.8-1(amd64/unstable): FTBFS: cannot convert
'SQLINTEGER*' to 'SQLLEN*' for argument '2' to 'SQLRETURN SQLRowCount(void*,
SQLLEN*)
Bug#326756: libccscript3: FTBFS (amd64): cannot convert 'long int*'
Package: ruby1.9
Version: 1.9.0+20060423-3
Severity: serious
From my pbuilder build log:
...
cc -shared -Wl,-soname,libruby1.9.so.1.9 array.o ascii.o bignum.o class.o
compar.o dir.o dln.o enum.o enumerator.o error.o euc_jp.o eval.o file.o gc.o
hash.o inits.o io.o marshal.o math.o numeric.o
Package: fai-server
Version: 2.10.2
Severity: critical
Justification: breaks unrelated software
After installtion of a client fai leaves the files 10fai and 90fai in
/etc/apt/apt.conf.d/.
The first file disables checking of trust violations and unauthenticated
packages. After a system is
On Thu, Mar 23, 2006 at 03:41:53AM +, Martin Michlmayr wrote:
Package: libembperl-perl
Version: 2.0.1-1
Severity: serious
Your package fails to build in unstable. Might be a missing b-d since
it seems to build in a working environment but not in a clean chroot.
Automatic build of
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
severity 354482 important
Bug#354482: libpam-poldi: no timeout when contacting smartcard daemon
Severity set to `important' from `critical'
End of message, stopping processing here.
On Fri, Jun 16, 2006 at 10:45:30AM +0200, Sam Hocevar wrote:
On Thu, Jun 15, 2006, Alexis Sukrieh wrote:
Thanks a lot for the patch, I'm going to test it on a 32bit arch very
soon.
I do not like this patch because it assumes that long has the same
size as void *, which is true in
Package: ncbi-tools6
Version: 6.1.20060507-2
Severity: serious
Justification: no longer builds from source
Dear Aaron,
I did not manage to build the ncbi-tools on a sid/etch mixture
without downloading the following extra packages:
libx11-dev, libxt-dev, libsm-dev, libice-dev, libxext-dev
I
On Fri, Jun 16, 2006 at 08:40:45AM -0500, Carlo Segre wrote:
Package: python-scipy
Version: 0.3.2-9
Severity: grave
Justification: renders package unusable
On installation (with python-central 0.4.17) produces the following error
message:
Setting up python-scipy (0.3.2-9) ...
Processing commands for [EMAIL PROTECTED]:
severity 373629 grave
Bug#373629: failed to do autopartitioning completely (tries the cd device :( )
Severity set to `grave' from `important'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
tag 373951 patch
thanks سلام שלם
On Fri, Jun 16, 2006, Daniel Schepler wrote:
Package: tetex-base
Version: 3.0-18
Severity: serious
From my pbuilder build log:
...
fakeroot debian/rules binary
quilt push -a
File series fully applied, ends at patch patch-tmp
make: ***
Daniel Schepler wrote:
Makefile:143: *** missing separator. Stop.
Does the line 143 contain |#_!!_#|?
--
akira yamada
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
tag 373951 patch
Bug#373951: tetex-base: FTBFS: rerunning quilt push -a fails
There were no tags set.
Tags added: patch
thanks سÙاÙ
ש××
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
# all cleared up
tags 373890 - moreinfo
Bug#373890: vim: cscope integration not available on amd64
Tags were: moreinfo
Tags removed: moreinfo
End of message, stopping processing
Daniel Schepler [EMAIL PROTECTED] wrote:
Package: tetex-base
Version: 3.0-18
Severity: serious
From my pbuilder build log:
...
fakeroot debian/rules binary
quilt push -a
File series fully applied, ends at patch patch-tmp
make: *** [stampdir/patch-stamp] Error 2
Can you please provide
1 - 100 of 192 matches
Mail list logo
