tags 433187 + etch
thanks
I'm adding Etch, as I can reproduce the problem there easily. A fix - at
least in Etch+1/2 would be appreciated.
--
Bernd Zeimetz
[EMAIL PROTECTED] http://bzed.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
tags 450466 + confirmed pending
thanks
Lucas Nussbaum wrote:
t/Dg2Tk...
# Failed test 'new Dg2Tk object'
# in t/Dg2Tk.t at line 51.
# got: 'couldn't connect to display :0 at
/usr/lib/perl5/Tk/MainWindow.pm line 55.
# MainWindow-new() at
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.10
tags 450463 pending
Bug#450463: mr: FTBFS: mr ed: no repositories found to work on
There were no tags set.
Tags added: pending
End of message, stopping processing here.
Please
Hi Ondrej,
Thanks for taking the time to report a bug.
On 7 November 2007 at 21:31, Ondrej Certik wrote:
| Package: libopenmpi-dev
| Version: 1.2.4-3
| Severity: grave
|
| --- Please enter the report below this line. ---
|
| $ wajig install libopenmpi-dev
At this point, did you have other
Julien Cristau [EMAIL PROTECTED] writes:
Then it's a totally different issue, please don't mix them.
Hm? AFAICT from reviewing the bug log, it's a longstanding issue that
users simply didn't notice (for the most part) until hal briefly
attempted to make everyone's keyboard use the evdev
Subject: eagle: license file for freeware license not found
Package: eagle
Version: 4.16-5
Severity: grave
Justification: renders package unusable
Installing eagle with aptitude or apt-get I get the following warnings:
Xlib: connection to :0.0 refused by server
Xlib: No protocol specified
Something is wrong with update-alternatives - probably screwed up by
mpich, or lam packages. Any ideas?
In clean state, this is what I get in pbuilder:
# update-alternatives --list mpicc
No alternatives for mpicc.
#
and outside:
$ sudo update-alternatives --list mpicc
$
Which means this
Hi Dirk and Manuel,
Thanks for taking the time to report a bug.
Thanks for a quick reply.
| $ wajig install libopenmpi-dev
At this point, did you have other MPI packages like LAM or MPICH installed?
Nothing. I purged everything. I installed openmpi. I purged openmpi
and checked again
On Nov 7, 2007 11:24 PM, Ondrej Certik [EMAIL PROTECTED] wrote:
Something is wrong with update-alternatives - probably screwed up by
mpich, or lam packages. Any ideas?
In clean state, this is what I get in pbuilder:
# update-alternatives --list mpicc
No alternatives for mpicc.
#
and
Ondrej,
Thanks for your thoroug repplies, and for actually testing all this before
you posted :)
On 7 November 2007 at 23:26, Ondrej Certik wrote:
| I think I solved the problem. I need to execute:
|
| sudo update-alternatives --remove-all mpicc
|
|
| for all the mpi* commands. And it
When I was switching between lam and ompi, something similar happened to me
and I also had to resort to update-alternatives. IIRC I used --auto but I
didn't write that down.
Now, having gotten here, would you agree that is not a bug in the Open MPI
packages but rather than some fragility in
On Nov 7, 2007 9:52 PM, Ondrej Certik [EMAIL PROTECTED] wrote:
TESTING: checkCxxCompiler from
config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:541)
TESTING: checkFortranCompiler from
Am Mittwoch, den 07.11.2007, 23:58 +0100 schrieb Ondrej Certik:
Sure, close it. Open MPI seems to be fine.
Thanks! We put a lot of effort in it and are very happy it's
appreciated! :)
I'll close the bug then.
I also managed to build petsc thanks to this. Now I am going to try to
fix libmesh
Package: kdebase-runtime-data, kdebase-runtime-bin
Version: 4:3.95.0-1
Severity: serious
Looks like there are missing conflicts and/or Replaces fields:
Unpacking kdebase-runtime-data (from
.../kdebase-runtime-data_4%3a3.95.0-1_all.deb) ...
dpkg: error processing
Your message dated Thu, 08 Nov 2007 00:28:58 +0100
with message-id [EMAIL PROTECTED]
and subject line [Pkg-openmpi-maintainers] Bug#450518: Bug#450518: mpicc not
found
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
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.10
tags 449119 pending
Bug#449119: gmobilemedia: Crashes at startup (traceback within)
There were no tags set.
Tags added: pending
End of message, stopping processing here.
Please
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.10
tags 450436 pending
Bug#450436: python-gammu: FTBFS: gammu.c:5825: error: too few arguments to
function 'GSM_ReadBackupFile'
There were no tags set.
Tags added: pending
tags 447543
Processing commands for [EMAIL PROTECTED]:
reassign 450452 clisp-dev
Bug#450452: xindy: FTBFS: make[1]: clisp-link: Command not found
Bug reassigned from package `xindy' to `clisp-dev'.
retitle 450452 does install a dangling symlink as clisp-link -
../lib/clisp-*/clisp-link
Bug#450452:
reassign 450452 clisp-dev
retitle 450452 does install a dangling symlink as clisp-link -
../lib/clisp-*/clisp-link
thanks
Hi all!
clisp-dev is hosed, it contains:
./usr/bin/clisp-link - ../lib/clisp-*/clisp-link
which is bad.
I reassign this to clisp-dev.
On Do, 08 Nov 2007, Jörg
Hi Lucas,
thanks for testing the rebuild.
Lucas Nussbaum schrieb am Wed 07. Nov, 13:42 (+0100):
Package: xindy
version: 2.2~beta2-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20071106 qa-ftbfs
Justification: FTBFS on i386
During a rebuild of all packages in sid, your
On Wed, Nov 07, 2007 at 01:45:25PM +0100, Lucas Nussbaum wrote:
Package: tiger
version: 1:3.2.1-37
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20071106 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on
On Wed, 7 Nov 2007 13:53:22 +0100, Lucas Nussbaum [EMAIL PROTECTED] said:
During a rebuild of all packages in sid, your package failed to build
on i386.
[...]
Hi Lucas,
I know that the bug report was generated (semi-)automatically, but just
FYI, gnustep-ppd is already slated for removal (bug
Package: kxsldbg
Version: 4:3.5.8-1
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I observe a segmentation fault. The backtrace is attached. To reproduce
I simply start kxsldbg. Then I use the testdocs.* files in the source
(as suggested in the manual). Then I try to use the Step
Processing commands for [EMAIL PROTECTED]:
tag 444888 patch pending
Bug#444888: Feed update fails in 'LC_ALL=ca_ES liferea '
There were no tags set.
Tags added: patch, pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
101 - 124 of 124 matches
Mail list logo
