Package: python2.4-minimal
Version: 2.4.4-6
Severity: minor
--- Please enter the report below this line. ---
When installing python, in cowbuilder (and a normal system), I can see:
Setting up python2.4-minimal (2.4.4-6) ...
'import site' failed; use -v for traceback
Setting up python2.4
I have forwarded this bug upstream:
http://projects.scipy.org/pipermail/numpy-discussion/2007-December/030320.html
Do you think you could take part in the discussion in there to help
trace this bug down?
Hi Jan,
upstream is willing to help with fixing this bug, but unfortunately, I
don't
On Dec 20, 2007 5:36 PM, Ondrej Certik [EMAIL PROTECTED] wrote:
I have forwarded this bug upstream:
http://projects.scipy.org/pipermail/numpy-discussion/2007-December/030320.html
Do you think you could take part in the discussion in there to help
trace this bug down?
Hi Jan
Hi Manuel,
Hello Ondrej,
attached you'll find a patch that solved the FTBFS of your package for
me. It patches the source directly, so you have to convert it so it can
be used with your favorite patch system.
The problem is that you can't find the MPI includes, as you already
stated in
Hi Manuel,
thanks for sorting this out.
No. We never stated that mpi.h is symlinked in /usr/include. I said in
my previous mail that mpi.h can be found in the /usr/include/mpi
directory which is a symlink to /usr/lib/openmpi/include/. This is like
all MPI packages do it. To the best of my
Upstream also noticed a very similar, if not the same, bug:
http://projects.scipy.org/scipy/numpy/ticket/551
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Dec 20, 2007 10:24 PM, Adam D. Barratt
[EMAIL PROTECTED] wrote:
retitle 453690 debchange doesn't work correctly with the changelog release
heuristic
thanks
Hi,
On Fri, 2007-11-30 at 17:17 +0100, Ondrej Certik wrote:
dch -t -D unstable
dch -t -D UNRELEASED
to switch just
Package: python-numpy
Version: 1:1.0.4-3
Severity: normal
--- Please enter the report below this line. ---
the files like arrayobject.h, arrayscalars.h etc. used to be in:
/usr/lib/python2.4/site-packages/numpy/core/include/numpy/
now they are in
Package: libopenmpi-dev
Version: 1.2.4-5
Severity: serious
--- Please enter the report below this line. ---
Hi,
the mpi.h is missing. I found it in
/usr/lib/openmpi/include/
please add at least a symlink or something to
/usr/include
the is breaks the python-petsc4py package for example:
Package: openmpi
--- Please enter the report below this line. ---
This problem seems to be fixed:
http://buildd.debian.org/pkg.cgi?pkg=libmesh
Feel free to close the bug report. However, a different problem seems to have
arised:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457088
Again,
On Dec 19, 2007 7:15 PM, Dirk Eddelbuettel [EMAIL PROTECTED] wrote:
On Wed, Dec 19, 2007 at 06:49:15PM +0100, Ondrej Certik wrote:
Package: libopenmpi-dev
Version: 1.2.4-5
Severity: serious
--- Please enter the report below this line. ---
Hi,
the mpi.h is missing. I found
| I meant something like /usr/include/openmpi/
You lost me. Please make up your mind as to whether you think it is a problem
because we do or do not use /usr/include, or /usr/include/openmpi ?
We use /usr/include/openmpi now, and we think that's the right way:
I agree that is the right way,
On Dec 20, 2007 12:29 AM, Manuel Prinz [EMAIL PROTECTED] wrote:
Dear Sune!
Am Mittwoch, den 19.12.2007, 23:43 +0100 schrieb Sune Vuorela:
I have read the discussion in the bug report. If it is anywhere else, please
point to it instead of playing smart-ass.
That applies to everyone: I
On Dec 20, 2007 8:00 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Dec 20, 2007 12:29 AM, Manuel Prinz [EMAIL PROTECTED] wrote:
Dear Sune!
Am Mittwoch, den 19.12.2007, 23:43 +0100 schrieb Sune Vuorela:
I have read the discussion in the bug report. If it is anywhere else,
please
On Dec 20, 2007 8:12 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Dec 20, 2007 8:00 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Dec 20, 2007 12:29 AM, Manuel Prinz [EMAIL PROTECTED] wrote:
Dear Sune!
Am Mittwoch, den 19.12.2007, 23:43 +0100 schrieb Sune Vuorela:
I have read
Package: evince
Version: 2.20.2-1
Severity: wishlist
--- Please enter the report below this line. ---
Hi,
currently, the TAB completion works fine, if the filename ends with ps or pdf,
but
it fails when it ends with ps.gz or pdf.gz (evince can display those files just
fine).
Otherwise,
Package: python-scipy
Version: 0.6.0-5
Severity: normal
--- Please enter the report below this line. ---
When trying to build the source package from unstable, I get:
[...]
swig: scipy/linsolve/umfpack/umfpack.i
swig -python -o build/src.linux-i686-2.4/scipy/linsolve/umfpack/_umfpack_wrap.c
On Dec 15, 2007 12:47 AM, Erich Schubert [EMAIL PROTECTED] wrote:
Hi,
Your mails never reached me. Did you send them to the BTS only maybe?
Yes, only to BTS, I thought they will be automatically forwarded to
you. Sorry about that.
As you can see from the original bug report, I didn't have
On Nov 21, 2007 4:19 PM, Julien Cristau [EMAIL PROTECTED] wrote:
reassign 452268 xserver-xorg-video-intel 2:2.2.0-1
forcemerge 439210 452268
kthxbye
On Wed, Nov 21, 2007 at 15:19:45 +0100, Ondrej Certik wrote:
I use unstable and in some recent upgrade (I think yesterday, or the day
Package: libpetsc2.3.3
Version: 2.3.3-3
Severity: normal
--- Please enter the report below this line. ---
Hi Adam,
libmesh FTBFS with these errors (on buildbots, pbuilder and my system):
configure:1632: mpicxx
Hi Jan,
indeed I also get the segfault now:
$ LD_PRELOAD=/usr/lib/atlas/sse2/libblas.so.3 python test.py
About to multiply
Segmentation fault
$ LD_PRELOAD=/usr/lib/atlas/sse/libblas.so.3 python test.py
About to multiply
Multiplied
I have forwarded this bug upstream:
Package: petsc
Severity: serious
--- Please enter the report below this line. ---
Hi Adam,
latest petsc from unstable FTBFS in pbuilder for me:
[...]
TESTING: checkCCompiler from
config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:380)
On Dec 17, 2007 7:41 PM, Adam C Powell IV [EMAIL PROTECTED] wrote:
reassign 456721 libopenmpi1
severity 456721 grave
thanks
Moving libmpi_*.so.0 to /usr/lib/openmpi/lib/ with no symlinks
from /usr/lib *breaks every package which links with those libraries*.
The soname ends in .so.0, so the
Hi Jan,
could you please send us more information about this bug? We would like
to reproduce it and fix it. See my previous email about that, or browse
it online here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448530
Thanks a lot,
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
I can't reproduce this bug. Pychess loads without any problems on my
system. I tried installing pychess on a new system (which didn't have
pychess till then) and there also it loaded properly.
Has this got something to do with your local settings? Can you please
try to reproduce this on some
Let me first close the bug :-)
I disagree with closing the bug, see below.
Please remove PYTHONPATH from environ or set it to
/usr/lib/python2.4/site-packages/
See this (from the source code):
if PYTHONPATH in os.environ:
path = os.path.abspath(os.environ[PYTHONPATH])
So the user may just add some or no directories to PYTHONPATH and the
default path is still appended. Of course, all other python programs
work, only pychess doesn't, because it screwes up the paths.
Yes, I agree with you. I shall forward this report upstream and
discuss with them.
Package: openmpi
Severity: normal
--- Please enter the report below this line. ---
Hi,
libmesh depends on openmpi, it build in pbuilder, however it fails on buildbots:
http://buildd.debian.org/fetch.cgi?pkg=libmesh;ver=0.6.1.dfsg-1;arch=amd64;stamp=1197413726
I suspect the problem is with
Package: pychess
Version: 0.8~beta2-2
Severity: normal
--- Please enter the report below this line. ---
$ pychess
Traceback (most recent call last):
File /usr/games/pychess, line 37, in ?
import pychess.Main
File /usr/lib/python2.4/site-packages/pychess/Main.py, line 14, in ?
from
As far as I can tell, the compilers should work fine as long if you have
the libopenmpi-dev package installed. Though, we're experiencing some
problems with multiple MPI implementations installed, see #452047 and
#451993. It sounds like it affects you as well but I'm not quite sure
from your
On Dec 12, 2007 2:28 PM, Sylvestre Ledru [EMAIL PROTECTED] wrote:
I think this problem occurs because g++ is not installed for this
package (g++ seems to be mandatory).
However, openmi is providing an cxx alternative even when C++ compiler
is not installed. Is it the right way ?
I always forgot to forward to the list, instead of the author...
Dirk, what's the best way to deal with that? Blocking the bugs?
Reassigning them to dpkg? Raising the dpkg bugs to serious? I'm not
sure what is the correct procedure here. But as this affects every
package that wants a) move to
Your package fails to build with GCC 4.3. Version 4.3 has not been
released yet but I'm building with a snapshot in order to find errors
and give people an advance warning. In GCC 4.3, the C++ header
dependencies have been cleaned up. The advantage of this is that
programs will compile
The libmesh in new is 0.6.1. But we need to wait until it propagates
to unstable and test it. The current libmesh in unstable is not
working correctly with petsc and openmpi. When the 0.6.1 is in
unstable and working, we'll package the 0.6.2 and upload it to NEW.
So expect 0.6.1 to be in unstable
This is a huge task. But a work on this has started already, please
follow all development here:
http://wiki.sagemath.org/DebianSAGE
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
the new packages are in the archive, please try it again. I am not able
to reproduce it. I purged all atlas packages and did:
$ wajig install python-scipy
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were
This bug seems to went away in the current unstable:
[EMAIL PROTECTED]:/tmp$ cat crash.py
from numpy import array
sel = array([False,True])
p1 = array([11.])
p1[sel] = p1
[EMAIL PROTECTED]:/tmp$ python crash.py
[EMAIL PROTECTED]:/tmp$
Could you please confirm it? We'll then close the bug in a
Hi,
I am sorry it has taken so long to repond to this bugreport. We just
moved the package to DPMT, so now we should be able to respond much more
quickly.
I am unable to run your script on the current unstable. Am I doing
something wrong?
$ python test.py
Traceback (most recent call last):
Thanks very much for this bugreport. I just installed it on my system
and it works:
$ wajig install python-scipy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
python-profiler
The following NEW packages will be installed:
Thanks for the bug report. We are working on exactly this problem,
and it seems we finally made a progress, python-numpy got built on many
architectures now:
http://buildd.debian.org/pkg.cgi?pkg=python-numpy
Once python-numpy gets to unstable on most of the architectures, we'll
fix the rest.
I was using tomboy for managing my notes, but today I am not able to start
it up. :(
This was a bug in cli-common and is now fixed with 0.5.2.
I upgraded all packages, including cli-common and the bug is still
there. Could you please reopen the bug?
$ dpkg -l cli-common
Package: dput
Version: 0.9.2.28
Severity: wishlist
--- Please enter the report below this line. ---
Hi,
first, thanks for working on dput, it's a very nice program.
One thing that I am missing is to use dput with pbuilder, i.e. use it to
upload packages from a directory, to which it doesn't
On Dec 4, 2007 2:20 PM, Sebastian Dröge [EMAIL PROTECTED] wrote:
Am Dienstag, den 04.12.2007, 14:11 +0100 schrieb Ondrej Certik:
I was using tomboy for managing my notes, but today I am not able to
start it up. :(
This was a bug in cli-common and is now fixed with 0.5.2.
I
On Dec 4, 2007 3:22 PM, Sebastian Dröge [EMAIL PROTECTED] wrote:
Am Dienstag, den 04.12.2007, 15:16 +0100 schrieb Arthur Petitpierre:
Selon Sebastian Dröge [EMAIL PROTECTED]:
Try
apt-get --reinstall install libmono-addins2.0-cil
Sorry but it doesn't work :
[15:[EMAIL
The following patch fixes it:
http://projects.scipy.org/scipy/scipy/changeset/3450
A new revision with this patch included will be uploaded soon.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: tomboy
Version: 0.8.2-1
Severity: grave
--- Please enter the report below this line. ---
$ tomboy
[DEBUG]: NoteManager created with note path /home/ondra/.tomboy.
** (Tomboy:30324): WARNING **: The following assembly referenced from
/usr/lib/tomboy/Tomboy.exe could not be loaded:
On Dec 1, 2007 7:11 PM, Kumar Appaiah [EMAIL PROTECTED] wrote:
severity 426012 normal
thanks
On Wed, Aug 01, 2007 at 10:19:26PM +0200, Josselin Mouette wrote:
Package: python-numpy
Version: 1:1.0.3-1
Severity: normal
Hi,
currently python-numpy depends on python-numpy-dev. As the
Hi Eike,
sorry for a later reply, I somehow wasn't subscribed to the bug reports.
Thanks very much for reporting it. Yes, I can reproduce the bug, it
behaves the same on my computer.
I reported the bug upstream:
http://projects.scipy.org/pipermail/scipy-dev/2007-December/008017.html
Feel free
Package: pbuilder
Version: 0.176
Severity: wishlist
Tags: patch
--- Please enter the report below this line. ---
Hi,
we need a feature to kill the build if the free disk (or memory) space is
running low.
I am attaching a preliminary patch, that implements this feature, it applies
cleanly
Package: python-numpy
Version: 1:1.0.3-1
Thanks very much for the patch.
I am going to try to fix it now as part of the Debian Python Modules Team.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debian/changelog
cython (0.9.6.8.ds-1~oc4) UNRELEASED; urgency=low
[ Ondrej Certik ]
* Initial Debian upload
* Added a patch for handling the @classmethod decorators
[ Sandro Tosi ]
* debian/watch
- added missing file
TODO before a first upload:
* cython man page
(otherwise
Package: xserver-xorg
Version: 1:7.2-5
Severity: serious
--- Please enter the report below this line. ---
I use unstable and in some recent upgrade (I think yesterday, or the day
before that), all fonts became unreadable. When I start xterm in
.xsession, the font is readable, but whenever I
Package name: cython
Version: 0.9.6.8.ds
Upstream Author: Stefan Behnel, Robert Bradshaw, and William Stein
URL: http://www.cython.org/
License: Python Software Foundation License
Description: C-Extensions for Python
Cython is a language that makes
Package: wnpp
Severity: wishlist
X-Debbugs-CC: [EMAIL PROTECTED]
--- Please fill out the fields below. ---
Package name: cython
Version: 0.9.6.8.ds
Upstream Author: Stefan Behnel, Robert Bradshaw, and William Stein
URL: http://www.cython.org/
License: Python
OK, so petsc seems to be ok now. I am going to try libmesh. Please
don't close this issue yet - there could be other problems with
g77/gfortran and maybe the proposed fix is not really a fix (i.e.
causes other problems). Need to check libmesh out first.
I was able to compile libmesh, with the
Okay, I will upload a new PETSc with this fix and the new watch file you
sent me. Thanks!
Nice. Check it in pbuilder first please - it's working for me, but
it's better if it is tested twice.
Great. I can't wait to try out the new libmesh with its new elements
for 4th order Cahn-Hilliard
I just tried building petsc in my unstable chroot, and it worked fine.
Perhaps I have a package installed which is not in the Build-Depends?
Here's the post-configure Fortran build info:
Fortran Compiler version:
-
Using C/C++ linker:
Using Fortran
Package: libopenmpi-dev
Version: 1.2.4-3
Severity: grave
--- Please enter the report below this line. ---
$ wajig install libopenmpi-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
TESTING: checkCxxCompiler from
config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:541)
TESTING: checkFortranCompiler from
config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:708)
There is a new upstream libmesh available, version 0.6.1. Please
package it when you get a chance (and when we can resolve the PETSc
build problems...)
Thanks for the info. I tried to package the new version a week ago,
but currently I am not able to get libmesh compile and link and make
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
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
config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config
Package: petsc
--- Please enter the report below this line. ---
Hi Adam,
I have some bad news - I am not able to build the package from source. How to
reproduce:
$ sudo apt-get update
$ apt-get source petsc
$ cd petsc-2.3.3
$ debuild
[...]
TESTING: SGIMPICheck from
Package: hg-buildpackage
Version: 1.0.3
Severity: wishlist
--- Please enter the report below this line. ---
Hi,
I want to use Mercurial for my packages and I have a couple of
suggestions about the hg-buildpackage.
I find it not very convenient to keep the bacula.upstream directory
around. Why
On 10/21/07, Brice Goglin [EMAIL PROTECTED] wrote:
Ondrej Certik wrote:
Package: compiz
Version: 0.5.2-2
Severity: normal
--- Please enter the report below this line. ---
I have Intel 945GM, running xserver-xorg-video-intel. I followed:
http://wiki.debian.org/Compiz
and some
Package: compiz
Version: 0.5.2-2
Severity: normal
--- Please enter the report below this line. ---
I have Intel 945GM, running xserver-xorg-video-intel. I followed:
http://wiki.debian.org/Compiz
and some other howtos, when I do:
$ LIBGL_ALWAYS_INDIRECT=TRUE compiz --replace
Today I upgraded sid and it started to work... I was using oowriter
from testing for last couple of days, today I did:
$ wajig update
Get:1 http://ftp.cz.debian.org sid Release.gpg [189B]
Ign http://ftp.cz.debian.org sid/main Translation-en_US
Get:2 http://ftp.cz.debian.org sid Release [79.6kB]
I tried oowriter from testing (2.2.1-8) and that works fine. So there
is a problem with oowriter in unstable on my machine. I'll be happy to
provide any information that could lead to catch the bug.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Thanks for the bugreport. It builds in cowbuilder on my computer just
fine, but you are right nevertheless and a new revision will be
uploaded soon, that will be using libsuitesparse-dev directly instead
of libufsparse-dev.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Hi,
what is the status of this bug? Does it still apply for the
python-scipy 0.6.0 that is in sid now?
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Whenever I try to run oowriter, it crashes:
since when?
Unfortunately I don't remember when I used oowriter the last time, I
think it's a month or less, definitely less than 2 months. (I update
to the latest sid regularly, like every week or more often.)
$ oowriter
On 10/11/07, Cyril Brulebois [EMAIL PROTECTED] wrote:
Ondrej Certik [EMAIL PROTECTED] (11/10/2007):
So I don't think this is a broken mix, nor do I think any of them are
related to this bug. BTW, do you know some more robust command to list
all packages, that don't match the ones in sid
Package: openoffice.org-writer
Version: 2.2.1-9
Severity: serious
--- Please enter the report below this line. ---
Whenever I try to run oowriter, it crashes:
$ oowriter
/usr/lib/openoffice/program/soffice: line 360: 14843 Bus error
$sd_prog/$sd_binary $@
** (process:14826): WARNING **:
Well, I don't know. There are several possible scenarios. Maybe a
misdesigned RTC chip (generally integrated in the chipset), or poor
design of the motherboard. The interrupt is absent, or not routed to the
processor, or used for something else, or... the kernel misdetected the
chip, and
unblock 426012 by 435591
thankyou
even though the bug 435591 is not fixed, the bug 426012 is fixed, so I
am unblocking this.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
So people using normal hardware and good kernels with proper RTC
interrupts don't want to use --directisa. Setting it by default would
work everywhere, but with degraded functionality for the majority.
It would be a pity.
Where is the real problem, that it doesn't work for me without the
This bug didn't render python-scipy uninstallable, there were other
problems. At the moment, the Build-Depends for python-scipy are:
python-numpy (= 1:1.0.2), and when this bug is fixed, we simply
change that to python-numpy-dev as it should be.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL
Ah, thanks for noting this. I probably should clean up the mp packages
anyway: it provides way too many binaries (all symlinks to the same
file) and even still uses some gtk1 stuff.
I'll try to get this fixed in the weekend.
In the meantime, I just moved /usr/bin/newsp to
Package: bash
Version: 3.1dfsg-8
Severity: wishlist
--- Please enter the report below this line. ---
Currently, the /etc/skel/.bashrc contains:
# some more ls aliases
#alias ll='ls -l'
#alias la='ls -A'
#alias l='ls -CF'
but I am always uncommenting them. I think they could be uncommented
by
) UNRELEASED; urgency=low
* First unnofficial package revision
-- Ondrej Certik [EMAIL PROTECTED] Fri, 07 Sep 2007 00:23:39 +0200
However, when testing the package, I need to temporarily change it to
unstable in order to upload to my local repository (it's not a
solution to change all
and it adds a new line with * into the changelog. Could this
behavior be changed?
dch -r -D UNRELEASED :-)
Awesome! I am sorry I missed that. :)
This doesn't add a new entry but does exhibit a problem that your original
command (dch -r ) also has - it adds a trailing space to the
abinit now conflicts with mp
the -2 version will be uploaded today.
I'm not sure that is a good solution. The packages are totally
unrelated and so there is no reason for them to conflict.
The correct solution is to remove the conflicting file, which I will do
tomorrow.
In fact, as I
I am for it. Because I think such issues should be discussed in public.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: util-linux
Version: 2.13-3
The same problem occurs here for fujitsu siemens Pi1505 and also for
Intel Core Quad computer.
$ sudo /etc/init.d/hwclock.sh restart
Saving the system clock..
select() to /dev/rtc to wait for clock tick timed out
And the clocks are simply wrong everytime I
Package: python-codespeak-lib
Version: 0.9.0-3.1
Severity: normal
--- Please enter the report below this line. ---
$ wget http://sympy.googlecode.com/files/sympy-0.5.3.tar.gz
$ tar xzf sympy-0.5.3.tar.gz
$ cd sympy-0.5.3
$ py.test
[...]
sympy/solvers/tests/test_solvers.py[5] .
same here, do we really need a package for a wrapper around xsltproc,
where the GPL header is larger than the script itself?
Why not to put that script inside the xsltproc package instead of
creating a new one?
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On 9/6/07, Junichi Uekawa [EMAIL PROTECTED] wrote:
When running on amd64 architecture and emulating amd64 architecture:
Looks like initrd is br0ken to me. Please give specific versions.
on i386:
$ sudo apt-get install linux-image-2.6.22-2-amd64
$ cat pbuilderrc-amd64.config
On 9/6/07, Junichi Uekawa [EMAIL PROTECTED] wrote:
So I am pretty sure I am using it in some unsupported way. I think
there should be an example in the man page how to use it.
Yes, I think there needs to be some example files to get people started.
http://wiki.debian.org/qemubuilder is a
It happens all the time. Here is more information:
$ cat .pbuilderrc
KERNEL_IMAGE=/boot/vmlinuz-2.6.21-1-686
INITRD=/boot/initrd.img-2.6.21-1-686
ARCH=i386
BASEPATH=/tmp/base-i386.qemu
MEMORY_MEGS=64
$ sudo qemubuilder --create
[...]
PCI: Ignore bogus resource 6 [0:0] of :00:02.0
NET:
Package: qemubuilder
Version: 0.39
Severity: normal
When running on amd64 architecture and emulating amd64 architecture:
$ cat .pbuilderrc
KERNEL_IMAGE=/boot/vmlinuz-2.6.22-2-amd64
INITRD=/boot/initrd.img-2.6.22-2-amd64
MIRRORSITE=http://ftp.cz.debian.org/debian
ARCH=amd64
It happens all the time. Here is more information:
- received termination signal with exit-code 0, killing child process
(qemu)
- killed (qemu)
- child process terminated with status: f
It is correct behavior, yes. Not a bug.
I thought it's a bug. Sorry about that. I updated
It happens all the time. Here is more information:
- received termination signal with exit-code 0, killing child process
(qemu)
- killed (qemu)
- child process terminated with status: f
It is correct behavior, yes. Not a bug.
I thought it's a bug. Sorry about that. I
There is a bug after all here - the terminal get's screwed up after
finishing the run:
[EMAIL PROTECTED]:~/debian$ [EMAIL PROTECTED]:~/debian$ [EMAIL
PROTECTED]:~/debian$
[EMAIL PROTECTED]:~/debian$ [EMAIL PROTECTED]:~/debian$ [EMAIL
PROTECTED]:~/debian$
[EMAIL PROTECTED]:~/debian$
Package: qemubuilder
Version: 0.39
Severity: normal
--- Please enter the report below this line. ---
Hi,
thanks for this package, it looks very promising. I never tried it
before, but I have pbuilder and cowbuilder working correctly.
[EMAIL PROTECTED]:~$ sudo qemubuilder --create
1+0 records
Go to parameter.c, line 225 and add the line
pc.arch=i386;
in there, like this:
/* define pc to be clear. */
memset (pc, 0, sizeof(pbuilderconfig));
pc.arch=i386;
/* default command-line component */
pbuildercommandline[0]=pbuilder;
The problem is, that the pc-arch was empty, so
Hi,
to make the package compile again, please add lam4-dev to
Build-Depends. The package then compiles fine in cowbuilder. I would
suggest to upload the package with this simple fix as soon as possible,
so that other packages depending on petsc can also be uploaded, and then
investigate, why it
Package: petsc
I just tried it in cowbuilder and it still doesn't work:
[...]
patching file src/sys/utils/makefile
patching file src/sys/objects/makefile
touch patch
PETSC_DIR=/tmp/buildd/petsc-2.3.3 ./config/configure.py \
--with-debugging=1 \
--useThreads 0
301 - 400 of 425 matches
Mail list logo
