Hello,
From your strace output, it appears that the hanging comes from the fact
that the child process (gdesklets daemon) segfaults, apparently during a
socket operation on the socket used to communicate between gdesklets and
gdesklets-daemon.
As python is not supposed to segfault, and the
Processing commands for [EMAIL PROTECTED]:
severity 309964 important
Bug#309964: drive appears confused (ireason = 0x01) and linux hangs
Severity set to `important'.
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Package: capisuite
Version: 0.4.5-3
Severity: serious
please rebuild, with tightened build dependency on libcapi20-dev.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: asterisk-chan-capi
Version: 0.3.5-11
Severity: serious
please rebuild, with tightened build dependency on libcapi20-dev.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: capi4hylafax
Version: 1:01.02.03-13
Severity: serious
please rebuild, with tightened build dependency on libcapi20-dev.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags confirmed
thanks
On Sun, Aug 14, 2005 at 08:43:17PM +0200, Andreas Jochens wrote:
When building 'tinymux' on amd64/unstable,
I get the following error:
g++ -g -O -DWOD_REALMS -c alloc.cpp
timeutil.h:37: error: expected ',' or
Your message dated Wed, 17 Aug 2005 00:32:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#259895: fixed in wmx10 0.02-5
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
Processing commands for [EMAIL PROTECTED]:
severity 323430 grave
Bug#323430: cupsys: cups does not print complicated files (plain-text seems
okay -- postscript is not)
Severity set to `grave'.
merge 323430 322553
Bug#322553: FreeType font plugin broken
Bug#323430: cupsys: cups does not print
Package: libglademm2.4
Version: 2.4.1-2
Severity: serious
Tags: patch
Hi Bradley,
Under the 0-day NMU policy for the C++ ABI transition, I have prepared an
NMU for libglademm2.4, because this library provides C++ interfaces and
must be rebuilt so that a number of other C++-based packages can
Package: libc6
Version: 2.3.5-3
Severity: critical
Justification: breaks unrelated software
After apt-get upgrade (on 10th of Aug, 2005) everything seemed to went fine.
Days later I got reports from users that mailing lists served by Ecartis broke.
In the Ecartis logs I found this:
Processing commands for [EMAIL PROTECTED]:
tags 323331 pending
Bug#323331: [patch] ld10k1 not 64bit clean.
Tags were: patch upstream
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Your message dated Wed, 17 Aug 2005 11:25:18 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#323533: DCC is non-free
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
tags 323331 pending
thanks
Zephaniah E. Hull wrote:
The attached patch fixes the bitops to be independent of the size of
longs, and is confirmed to fix the bug on my box.
Applied in svn. Thanks!
--
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi,
[ I got none of your replies. I hope the project will agree to get rid
of this mails sent to [EMAIL PROTECTED] do no reach the
submitter nonsense ]
* Ben Armstrong [2005-08-16]:
Can you make it produce a core file and get a backtrace of the failure?
Program received signal SIGSEGV,
Your message dated Wed, 17 Aug 2005 03:02:10 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323509: fixed in linux-ntfs 1.11.2-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
On Wed, Aug 17, 2005 at 11:59:40AM +0200, Laurent Fousse wrote:
Rebuilding with debugging enabled gives me :
Program received signal SIGSEGV, Segmentation fault.
0x0fb07788 in semctl () from /lib/libc.so.6
(gdb) bt
#0 0x0fb07788 in semctl () from /lib/libc.so.6
#1 0x1000454c in open_sem
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323093: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323093: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#319154: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#319154: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#318017: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#318017: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#317543: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#311958: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#317543: fixed in kdelibs 4:3.4.2-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 it is now
Hi,
* Steve Langasek [2005-08-17]:
From the backtrace, I would rather guess it's libc-related.
Actually, I would guess it's kernel-related.
Per your original report, you are running:
Kernel: Linux 2.6.12.4-bar
This looks like a self-compiled kernel.
It is.
Please check whether
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#317543: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#318017: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#319154: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323093: fixed in kdelibs 4:3.4.2-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 it is now
Your message dated Wed, 17 Aug 2005 03:13:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323093: fixed in kdelibs 4:3.4.2-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 it is now
Package: libnss-ldap
Version: 238-1
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages libnss-ldap depends
Processing commands for [EMAIL PROTECTED]:
retitle 317231 kdelibs: FTBFS against libcupsys2-dev from experimental
Bug#317231: cups-util.c:445: error: 'http_addr_t' has no member named 'sin_addr'
Changed Bug title.
severity 317231 wishlist
Bug#317231: kdelibs: FTBFS against libcupsys2-dev from
retitle 317231 kdelibs: FTBFS against libcupsys2-dev from experimental
severity 317231 wishlist
thanks
* Bob Tanner [Wed, 06 Jul 2005 16:57:01 -0500]:
Package: kdelibs
Version: 4:3.3.2-6.1
Severity: serious
Tags: experimental
Justification: no longer builds from source
This bug is about
Processing commands for [EMAIL PROTECTED]:
severity 323578 grave
Bug#323578: drupal: DRUPAL-SA-2005-004
Severity set to `grave'.
thank you
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Hi, I found the same thing at 2005-08-12, and I put a simple patch at
http://projects.blender.org/tracker/index.php?func=detailaid=2927group_id=9atid=127
And this is a Blender Leader's reply:
Date: 2005-08-14 14:13
Sender: ton
Logged In: YES
user_id=103
Hi,
Can you give a description of what
A buffer overflow that can be exploited was found in osh, which is a setuid
root program. See Bug#323424. It affects sarge and unstable (both are
version 1.7-13). For unstable it is fixed in 1.7-14; the diff is
available at the BTS.
--
Oohara Yuuma [EMAIL PROTECTED]
PGP key (key ID F464A695)
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.4
severity 249642 important
Bug#249642: cdrdao: FTBFS amd64: x86_64 not supported
Bug#249634: FTBFS: the configure script uses the host cpu and not the
architectur
Severity set to
On Wed, Aug 17, 2005 at 08:12:35PM +0800, wrote:
Hi, I found the same thing at 2005-08-12, and I put a simple patch at
http://projects.blender.org/tracker/index.php?func=detailaid=2927group_id=9atid=127
And this is a Blender Leader's reply:
Date: 2005-08-14 14:13
Sender: ton
Logged
Your message dated Wed, 17 Aug 2005 06:47:17 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321785: fixed in gcc-4.0 4.0.1-5
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: aspell-es
Version: 1.8-4
Severity: grave
Justification: renders package unusable
During a dist-upgrade, I had the following message :
dictionaries-common: Running aspell-autobuildhash
Problèmes lors de la reconstruction de la table de
hachage
Your message dated Wed, 17 Aug 2005 07:47:06 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#317216: fixed in rezound 0.12.0beta-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
Your message dated Wed, 17 Aug 2005 08:02:05 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#317218: fixed in seq24 0.6.3-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 your
Hello Matt,
On Tue, 2005-08-16 at 17:12 -0700, Matt Kraai wrote:
gprolog fails to build because it contains invalid lvalues in some
assignments:
gplc -c -C '-O3 -fomit-frame-pointer -funsigned-char -Wall -Wall -DDEBIAN'
engine.c
`-mcpu=' is deprecated. Use `-mtune=' or '-march='
Processing commands for [EMAIL PROTECTED]:
severity 321644 serious
Bug#321644: mozilla-browser: mozilla 1.7.10 version crashes almost immediately
and all other browsers that use the mozilla core crash with similar frequency
Severity set to `serious'.
thanks
Stopping processing here.
Please
Your message dated Wed, 17 Aug 2005 08:47:07 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323528: fixed in gprolog 1.2.18-14
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: python-egenix-stack
Version: 2.0.6-1
Severity: serious
missing comma.
maybe you can drop the 2.1 and 2.2 packages?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
tag 315946 + patch
Bug#315946: phpgroupware: Error in postinst script
Tags were: sarge
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
Processing commands for [EMAIL PROTECTED]:
reassign 317082 libc6-dev,dpkg-dev
Bug#317082: libc6-s390x: missing depends on lib64gcc1
Bug reassigned from package `dpkg-dev' to `libc6-dev,dpkg-dev'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
reassign 317082 libc6-dev,dpkg-dev
thanks
I managed to grab Matthias Klose and he helped me get a working demo of
the problem on my lowly i386, and I understand the bug now -- there's
some missing context in the above mails.
For those following, the problem is that people are building 64-bit
Your message dated Wed, 17 Aug 2005 09:17:05 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#266355: fixed in shaketracker 0.4.6-5
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
tag 315946 + patch
thanks
Martin Schulze wrote:
Would you consider a fix for #315946 if uploaded to s-p-u?
I'd like to see your proposed fix.
Ah, sorry. Here is the 1-line-patch patch.
My apologies for incorrectly assuming it had been in sarge before the
freeze but not checking until it was too
Hi Moritz,
see http://www.hardened-php.net/advisory_142005.66.html for
thank you very much for alerting me of the problem. I'm presently
working out with upstream whether phpGroupWare is affected and if so
will fix it ASAP.
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
--
Here is a strace -s 4096 -xx as requested.
--
see shy jo
execve(/bin/ip, [\x69\x70, \x72\x6f\x75\x74\x65, \x61\x64\x64,
\x64\x65\x66\x61\x75\x6c\x74, \x76\x69\x61,
\x31\x39\x32\x2e\x31\x36\x38\x2e\x32\x2e\x31], [/* 10 vars */]) = 0
uname({sys=Linux, node=, ...}) = 0
brk(0)
Package: aptitude
Version: 0.3.3-1.1
Tags: patch
Followup-For: Bug #321889
Attempting to self-compile Aptitude results in FTBFS with newer
libapt-pkg, libsigc++ and gcc 4.0. Attached patch fixes this.
-- System Information:
Debian Release: 3.1
APT prefers stable
APT policy: (990, 'stable'),
Your message dated Wed, 17 Aug 2005 09:47:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323519: fixed in hyperestraier 0.5.4-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 is
Your message dated Wed, 17 Aug 2005 09:47:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323501: fixed in hyperestraier 0.5.4-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 is
Package: ace
Version: 5.4.7-2
Severity: serious
Hi,
Your package seems to have a missing build dependency on bzip2:
debian/rules build
tar -xjf ACE+TAO+CIAO-5.4.7.tar.bz2
tar: bzip2: Cannot exec: No such file or directory
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Wed, Aug 17, 2005 at 11:25:18AM +0200, Martin Zobel-Helas wrote:
Hi Duncan,
could you please have a look on the version of DCC in sid/etch/sarge
first.
The version of DCC in Debian is the latest version before upstream
changed its license.
I understand this, but as I mentioned, it's
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.4
severity 323562 serious
Bug#323562: libqwt4: uninstallable
Severity set to `serious'.
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323430: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323430: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322553: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322553: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322159: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322159: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322159: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321436: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321436: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321436: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321205: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321205: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321049: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321049: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321049: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321205: fixed in gs-esp 8+8.15rc4.dfsg.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
On 05-Aug-17 17:00, Scott James Remnant wrote:
For those following, the problem is that people are building 64-bit
libraries on a 32-bit platform (or the other way around) as part of the
package build. dpkg-shlibdeps uses plain old ldd to find out the
dependencies of a binary or shared
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323430: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322553: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322159: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321205: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 20:35:42 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#321420: tetex-base uninstallable due to lack of
update-language
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321049: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321436: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#322553: fixed in gs-esp 8+8.15rc4.dfsg.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
Your message dated Wed, 17 Aug 2005 11:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323430: fixed in gs-esp 8+8.15rc4.dfsg.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
Package: worker
Version: 2.10.2-1
Severity: serious
Hi,
Your package is failing to build on all 64 bit arches with the
following error:
Checking for #define HAVE_EXPLICIT_LFS 1 ... FAILED
if [ -e check_options_failed ] ; then \
rm -f check_options_failed ; \
/bin/false ; \
fi
Processing commands for [EMAIL PROTECTED]:
severity 322750 serious
Bug#322750: ghemical: FTBFS on 64-bit platforms (assumes 32-bit pointers)
Severity set to `serious'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Package: vegastrike
Version: 0.4.3-2
Severity: serious
Hi,
Your package is failing to build on 64 bit arches with the
following error:
g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -DHAVE_SDL=1 -DSDL_WINDOWING=1
-DHAVE_SDL=1 -DSDL_WINDOWING=1 -DHAVE_AL=1 -DHAVE_OGG -DDATA_DIR=\/usr
Package: sensord
Version: 1:2.9.1-5
Severity: grave
Tags: sid
Justification: renders package unusable
Hello,
librrd0 was removed from unstable.
Now librrd2 (and -dev) are there so a rebuild against this
version should fix this bug.
thx.
-- System Information:
Debian Release: testing/unstable
Package: gfpoken
Version: 0.25.dfsg.1-1
Severity: serious
Hi,
Your package is failing to build with the following error
on 64 bit arches:
if gcc -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\
-DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\gfpoken\
-DVERSION=\0.25\
On 05-Aug-17 12:52, Steve Langasek wrote:
No, that doesn't solve the problem. How are you supposed to invoke a
64-bit linker for a bi-arch build being done on a 32-bit buildd?
I guess you will generally have many more issues than this one when you
try to build 64-bit packages on a 32-bit
The problem might be caused by the application (or another library)
attempting to dlopen() libXmu.so instead of libXmu.so.6.
This is bad because the .so symlinks to a shared library are, per policy,
only provided by -dev packages.
Moving those symlinks to the regular shlib package is the wrong
Package: libquicktime1
Version: 0.9.3-2
Severity: critical
Justification: breaks unrelated software
During my last apt-get dist-upgrade (Aug 16, 2005), the installation of the
package fails. Trying apt-get -f install after is not helping either.
Currently my entire apt-get is broken due to this
On Wednesday 17 August 2005 08:03, Matthias Klose wrote:
Package: asterisk-chan-capi
Version: 0.3.5-11
Severity: serious
please rebuild, with tightened build dependency on libcapi20-dev.
Thanks Matthias.
I have just rebuilt submitted with the same dependency to pick up new
soname.
I
On Wed, Aug 17, 2005 at 08:26:46PM +0200, Andreas Jochens wrote:
On 05-Aug-17 17:00, Scott James Remnant wrote:
For those following, the problem is that people are building 64-bit
libraries on a 32-bit platform (or the other way around) as part of the
package build. dpkg-shlibdeps uses
Package: java-package
Version: 0.25
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In the file /usr/share/java-package/ibm-j2sdk.sh, on line 29 the
architecture should be powerpc|powerpc-linux and _NOT_
amd64|x86_64-linux as actually
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.4
merge 323082 321048
Bug#321048: Uninstallable in sid due to C++ transition of libid3
Bug#323082: beep-media-player depends on non-existant package
Merged 321048 323082.
End of
Your message dated Wed, 17 Aug 2005 13:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323650: fixed in lm-sensors 1:2.9.1-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
Your message dated Wed, 17 Aug 2005 13:17:03 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323548: fixed in asterisk-chan-capi 0.3.5-12
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
1 - 100 of 139 matches
Mail list logo
