Package: linux-image-2.6.18-4-footbridge
Version: 2.6.18.dfsg.1-12etch1
Severity: grave
Justification: causes non-serious data loss
After updating to the kernel version released with DSA-1286-1, the system has
begun to spontaneously reboot. This is a small Netwinder system, which has been
Your message dated Sat, 05 May 2007 06:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#422107: fixed in heartbeat 1.2.5-4
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 Sat, 05 May 2007 06:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#421415: fixed in heartbeat 1.2.5-4
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 Sat, 05 May 2007 06:17:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#422320: fixed in heartbeat-2 2.0.8-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 now
Your message dated Sat, 5 May 2007 16:43:55 +1000
with message-id [EMAIL PROTECTED]
and subject line fixed
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
Hi,
I'm sorry, I'm waiting at the moment on libguichan0 (0.6.1-1) in Sid and
Etch, but the maintainer isn't responsible.
Regards,
Patrick Matthäi
* Kurt Roeckx [EMAIL PROTECTED] [2007-05-04 18:25]:
On Fri, May 04, 2007 at 04:41:28PM +0200, Rafael Laboissiere wrote:
* Bastian Blank [EMAIL PROTECTED] [2007-05-04 15:31]:
Package: slpvm
Version: 0.1.5-7
Severity: critical
slpvm doses the buildd. The resulting buildlog is
tag 421606 patch
thanks
Hi,
You can find in the diff.gz file attached a new
02_french-po-fix.dpatch patch whom include the french manpage changes.
The rules files contains one change to call patch-stamp before the
configure script.
dh_clean remove the generated file po/fr.gmo
Processing commands for [EMAIL PROTECTED]:
tag 421606 patch
Bug#421606: sitecopy: Doesn't find all my site
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
Your message dated Sat, 05 May 2007 08:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#422241: fixed in slpvm 0.1.5-8
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
I checked the kernel logs looking for this error message. The system
was upgraded to Etch on April 10, and there are NO entries of the
NWFPE log until after the DSA-1286-1 security update is installed.
So it looks like this might be related to the changes introduced with
this update.
Going
On Sat, May 05, 2007 at 11:26:46AM +0900, Simon Horman wrote:
Yes. Ask the RMs and they can probably schedule binNMUs for you.
I'm sorry, but I don't understand that a binNMU is.
It's short for binary-only NMU:
http://wiki.debian.org/binNMU
Basically, it's a rebuild on one or more
On Fri, May 04, 2007 at 05:55:23PM -0700, Steve Langasek wrote:
clone 422213 -1
reassign -1 libc6-sparc64
found -1 2.5-2
retitle -1 readlink return type changed without backwards-compatibility symbol
thanks
On Fri, May 04, 2007 at 07:58:18PM -0400, Felipe Sateler wrote:
On Friday 04 May
Maybe this should be removed? According to popcon, it has practically
no users [1].
Mandriva seems to have a version for php5 [2], so it should be
possible to convert the package to php5. But I doubt it is worth the
effort.
[1] http://qa.debian.org/popcon.php?package=php4-tclink
[2]
On Sat, May 05, 2007 at 12:55:59PM +0200, Kurt Roeckx wrote:
So either you didn't disable the regression tests, or this happens during
some other part of the build.
slpvm_0.1.5-9 seems to have build without problems.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
reopen 422241
thanks
On Sat, May 05, 2007 at 10:26:13AM +0200, Rafael Laboissiere wrote:
* Kurt Roeckx [EMAIL PROTECTED] [2007-05-04 18:25]:
On Fri, May 04, 2007 at 04:41:28PM +0200, Rafael Laboissiere wrote:
* Bastian Blank [EMAIL PROTECTED] [2007-05-04 15:31]:
Package: slpvm
Package: tcm
Version: 2.20+TSQD-4
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of tcm_2.20+TSQD-4 on debian-31.osdl.marist.edu by
sbuild/s390 98
[...]
/usr/bin/g++ -Wall -g -O2 -DCONFIG_INSTALL=\/etc/tcm/\
-DTCM_INSTALL_DIR=\/usr\
Package: schroot
Version: 1.1.1-1
Severity: grave
Tags: security patch
Justification: user security hole
Scripts in /etc/schroot/setup.d or /etc/schroot/exec.d are executed in the
same manner as /bin/run-parts. However, due to a mistake in the way
filenames are checked with regular expressions,
* Kurt Roeckx [EMAIL PROTECTED] [2007-05-05 12:58]:
On Sat, May 05, 2007 at 12:55:59PM +0200, Kurt Roeckx wrote:
So either you didn't disable the regression tests, or this happens during
some other part of the build.
slpvm_0.1.5-9 seems to have build without problems.
I have screwed up
Your message dated Sat, 05 May 2007 12:02:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#421984: fixed in moon-buggy 1.0.51-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
* Roger Leigh [Sat, 05 May 2007 12:18:44 +0100]:
Scripts in /etc/schroot/setup.d or /etc/schroot/exec.d are executed in the
same manner as /bin/run-parts. However, due to a mistake in the way
filenames are checked with regular expressions, files ending in
.dpkg-new, .dpkg-old, .dpkg-dist,
Package: pgplot5
Version: 5.2.2-9
Severity: serious
Justification: Policy 10.2
I'm trying to build wip without extraneous dependencies, as discussed in
http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html.
Here's what I get if I remove `-lpng', which is not used by wip itself:
Will look into it as soon as possible.
Thanks
Carlo
On Sat, 5 May 2007, Matej Vela wrote:
Package: pgplot5
Version: 5.2.2-9
Severity: serious
Justification: Policy 10.2
I'm trying to build wip without extraneous dependencies, as discussed in
Hi Javier,
This RC bug is caused by a bug in yada which has now been fixed. If you just
rebuild acidlab with the newer yada (0.53) the bug will be closed.
Thijs
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: schooltool
Version: 0.11.4-3
Severity: serious
Usertags: grid5000 rebuild
(I know you are aware of the problem, it's just to track it properly)
Hi,
Your package fails to build from source, because one of its
build-depends, python2.4-schoolbell, is uninstallable.
Cheers,
--
| Lucas
Vendredi 04 mai 2007, vers 09:57:07 (+0200), Kalle Olavi Niemitalo a
écrit :
* Don't look for gettext message catalogs in ../po/ (closes: #417789).
Thanks, Arnaud Giersch! Reference: CVE-2007-2027.
A less paranoid fix has been checked in to elinks-0.11 and
elinks-0.12 in Git. If you
El vie, 04-05-2007 a las 20:46 +0200, Bastian Blank escribió:
Package: pygoocanvas
Version: 0.8.0-1
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of pygoocanvas_0.8.0-1 on lxdebian.bfinv.de by sbuild/s390
98
[...]
E: Couldn't find
On Wed, 2007-05-02 at 12:49 +0200, Jochen Friedrich wrote:
Hi Tom,
snmpd is running at 100% CPU on 2 of my systems, and will not respond to
polls. I have tried the default config file, which has the same effect.
I suspect this could be an upstream problem.
I must add to the previous
Package: bzip2
Version: 1.0.3-6
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
gcc -m64 -march=x86-64
Package: graphicsmagick
Version: 1.1.7-14
Severity: serious
Hi,
Your package build-deps on libjasper-1.701-dev, which is no longer
available in unstable. It *should* still build, because it b-deps on
libjasper-1.701-dev | libjasper-dev, but in practice, it doesn't work
for an unknown reason.
--
Package: gphoto2
Version: 2.2.0-3
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
gcc -g -O2 -Wall -g -o gphoto2
Package: gtkam
Version: 0.1.12-2.2
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
i486-linux-gnu-gcc
Package: octave2.1-forge
Version: 2006.03.17+dfsg1-3
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
User: [EMAIL PROTECTED]
Usertags: builddep-tetex-ftbfs
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Package: libcairo-perl
Version: 1.01-1
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
make[1]: Entering directory
Your message dated Sat, 05 May 2007 15:32:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#420012: fixed in libmrss 0.17.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: python-scipy
Version: 0.5.2-7
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
dh_installdirs -A
set -e;
Package: screem
Version: 0.16.1-4
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
The ubuntu patch on the PTS looks relevant.
Your message dated Sat, 05 May 2007 15:32:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#420012: fixed in libmrss 0.17.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 Sat, 05 May 2007 15:32:07 +
with message-id [EMAIL PROTECTED]
and subject line Bug#421606: fixed in sitecopy 1:0.16.3-9
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 Sat, May 05, 2007 at 05:23:09PM +0200, Lucas Nussbaum wrote:
Package: octave2.1-forge
Version: 2006.03.17+dfsg1-3
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
User: [EMAIL PROTECTED]
Usertags: builddep-tetex-ftbfs
Hi,
During a rebuild of all
Hi Bastian,
I would guess that there is something wrong with your setup:
# apt-get -t unstable -s install jikes-classpath
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
classpath classpath-common classpath-gtkpeer
The following
Package: latex-cjk-japanese-wadalab
Version: 0.20050817-12
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
User: [EMAIL PROTECTED]
Usertags: builddep-tetex-ftbfs
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on
Package: lilypond
Version: 2.8.7-3
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
User: [EMAIL PROTECTED]
Usertags: builddep-tetex-ftbfs
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Have a look at
Package: oregano
Version: 0.60.0-1
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
gcc -o src/print.o -c -g -O2
Package: user-mode-linux
Version: 2.6.18-1um-2
Severity: serious
Tags: sid
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
Checking
Package: monotone
Version: 0.31-8
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
User: [EMAIL PROTECTED]
Usertags: builddep-tetex-ftbfs
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
The full build log
Package: taskjuggler
Version: 2.3.1-3
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000 rebuild
Hi,
During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.
Relevant parts:
make[3]: Entering directory
Hi.
I've got the same problem since last night, when I did a massive
dist-upgrade after a month and a half (the last one was before Etch was
released). I have a GNOME environment, but I don't think that's relevant.
I don't really know perl, but I can read some of it and add a few print
found 422354 1.1.1-1
notfound 422354 1.0.5-1
severity 422354 important
thanks
Adeodato Simó [EMAIL PROTECTED] writes:
* Roger Leigh [Sat, 05 May 2007 12:18:44 +0100]:
Scripts in /etc/schroot/setup.d or /etc/schroot/exec.d are executed in the
same manner as /bin/run-parts. However, due to a
Processing commands for [EMAIL PROTECTED]:
found 422354 1.1.1-1
Bug#422354: schroot: Regex mismatch in sbuild/sbuild-run-parts.cc leads to
unwanted execution of stray dpkg conffiles
Bug marked as found in version 1.1.1-1.
notfound 422354 1.0.5-1
Bug#422354: schroot: Regex mismatch in
Package: python-moinmoin
Version: 1.5.7-2
Tags: security
Severity: grave
Proof of concept:
http://moinmoin.wikiwikiweb.de/WikiSandBox?action=AttachFiledo=%3Cblink%3ETest%3C/blink%3E
This is CVE-2007-2423. Please mention this name in the changelog when
you fix this bug.
--
To UNSUBSCRIBE,
Processing commands for [EMAIL PROTECTED]:
tag 422380 + patch
Bug#422380: bzip2: FTBFS: /usr/bin/ld: cannot find -lgcc
There were no tags set.
Tags added: patch
kthxbye
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tag 422380 + patch
kthxbye
According to 422309, bzip2 should build-depend on gcc-multilib [amd64
i386 powerpc ppc64 sparc s390] . A patch is attached which fixes this.
I have confirmed that this makes bzip2 build correctly on amd64, whereas
it didn't without the patch.
--
brian m. carlson /
Package: ilohamail
Version: 0.8.14-0rc3sid3.1
Severity: serious
Justification: Policy 10.7.3 Behavior local changes must be preserved during a
package upgrade
Hi Jörg!
I just upgraded a system from sarge and etch, and with that from ilohamail
0.8.14-0rc3sarge1 to 0.8.14-0rc3sid3.1.
I changed
Package: kpowersave
Version: 0.7.2-2
Severity: grave
Justification: renders package unusable
When kpowersave is launched, it just crash. 0.6 works correctly.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500,
On 03/05/07 at 19:43 +0200, Lucas Nussbaum wrote:
During a rebuild of all packages in etch, I discovered that your package
failed to build on amd64.
it's in sid, and built on i386.
The full build log is available from
http://ox.blop.info/bazaar/buildlogs/20061123/
no, from
Pierre Habouzit wrote:
Package: kpowersave
Version: 0.7.2-2
Severity: grave
Justification: renders package unusable
When kpowersave is launched, it just crash. 0.6 works correctly.
Hi Pierre,
could you please send me a backtrace?
Cheers,
Michael
--
Why is it that all of the
Package: gcc-4.1
Version: 4.1.2-5
Severity: grave
Tags: patch
Justification: breaks the glibc
Hi,
You are already aware of the problem, but I think it is better to
summarize it here to get an history of the problem.
GCC generates wrong code on hppa when TLS registers are used. This is
due to a
Your message dated Sat, 05 May 2007 19:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#422127: fixed in gfax 0.7.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 your
On Sat, May 05, 2007 at 09:38:10PM +0200, Michael Biebl wrote:
Pierre Habouzit wrote:
Package: kpowersave
Version: 0.7.2-2
Severity: grave
Justification: renders package unusable
When kpowersave is launched, it just crash. 0.6 works correctly.
Hi Pierre,
could you
Your message dated Sat, 05 May 2007 19:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#422384: fixed in gphoto2 2.3.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 is now
Arnaud Giersch [EMAIL PROTECTED] writes:
I don't believe that this patch really solves the security issue. An
user may still be vulnerable if he wants to run his freshly compiled
(but not installed now) elinks. This user would typically run it as
/path/to/elinks/src/elinks. If his cwd is
Processing commands for [EMAIL PROTECTED]:
severity 377373 serious
Bug#377373: twig: Still depends on php3 and not on php5
Severity set to `serious' from `minor'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Processing commands for [EMAIL PROTECTED]:
severity 377372 serious
Bug#377372: libphp-phplot: Still mentions and depends PHP3
Severity set to `serious' from `minor'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Samedi 05 mai 2007, vers 22:14:33 (+0200), Kalle Olavi Niemitalo a
écrit :
Thank you for your concern. The patched ELinks 0.12.GIT
(d1fa336f7f390d9b51456498fac5dda8f54c18a4) appears to open the
correct gettext catalog in this case, regardless of what the
current working directory is. Please
Your message dated Sat, 05 May 2007 21:02:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#422213: fixed in checkinstall 1.6.1-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
Package: ilohamail
Version: 0.8.14-0rc3sid3.1
Followup-For: Bug #422411
Hi!
Just discoveres, that my first impression about the upgrade bug was wrong.
During an upgrade the configurations files are not overwritten. New ones
with different names are placed there with default values.
PING ? Could you have the elementary courtesy to follow up to the bugs
you report ? thanks.
On Sun, Apr 29, 2007 at 03:30:10AM +0200, Aurelien Jarno wrote:
From the build.d.o, it looks like the failure appeared on europa.d.o.
Is that right?
Bdale gave me an access to netwinder, so I can
Nathan Scott wrote:
Thanks Paul, I've initiated a discussion with upstream, will get
back to you soon. Sorry about the delay, been away over Easter.
What's the outcome?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Your message dated Sun, 6 May 2007 00:04:42 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#422317: readlink return type changed without
backwards-compatibility symbol
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt
Package: ftm
Version: 0.0.7
Severity: serious
--- Please enter the report below this line. ---
Hi,
I can't get ftm working with the following error:
=== output start ===
# ftm my.ftm
ftm: symbol lookup error: ftm: undefined symbol: tokens_parse
=== output end ===
The config file is like the
Your message dated Sun, 6 May 2007 01:00:55 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed in 1.10.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 responsibility to
Your message dated Sat, 5 May 2007 20:35:23 -0400
with message-id [EMAIL PROTECTED]
and subject line libpod-pom-perl is back in unstable and testing
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]:
tags 420332 patch
Bug#420332: debian-history: FTBFS: po-debiandoc build-dep does not exist anymore
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
tags 420332 patch
thanks
Hello,
On Mon, Apr 23, 2007 at 12:04:09PM -0600, Bdale Garbee wrote:
On Sat, 2007-04-21 at 19:12 +0200, Adeodato Simó wrote:
Hi. During an archive rebuild your debian-history package failed to build
because the po-debiandoc build-depend is not available any more
Package: bzr-svn
Version: 0.3.2-1
Severity: serious
Justification: Policy 3.5
*** Please type your report below this line ***
Running 'bzr branch' emits:
Needs at least Python2.5 or Python2.4 with the pysqlite2 module
Unable to load plugin 'svn' from '/usr/lib/python2.4/site-packages/
Package: xfce4
Version: 4.3.99.2
Severity: grave
When I start xfce4, xfwm4 doesn't start with it, and I am left with no
window manager
( no window borders, unmovable windows ).
If I manually start xfwm4 in a terminal within xfce4, the problem is
corrected.
-- System Information:
Debian
tag 421139 patch
thanks
For some reason, including libgnome/libgnome.h *before*
gm-support.h undefines the gettext alias _ (or keeps it from being
defined at all, I don't know).
Changing the order of the includes allows the package to build. I
have done no further testing of the resulting
Processing commands for [EMAIL PROTECTED]:
tag 421139 patch
Bug#421139: gnoemoe: FTBFS: warning: passing argument 2 of
'gtk_label_set_markup' makes pointer from integer without a cast
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need
Your message dated Sun, 06 May 2007 05:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#417016: fixed in pymsnt 0.11.2-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 now
80 matches
Mail list logo
