Package: linux-wlan-ng-source
Version: 0.2.4+svn20060414-1
Severity: grave
Justification: renders package unusable with current kernels
Greetings,
I just tried to build these modules with 2.6.16. I have the stock
Debian kernel image installed, and used its config. Then I did:
make oldconfig
ma
Greetings,
The new upgrade procedure fails on alpha, regardless of the kernel
workaround, there's still a udev - initramfs-tools dependency loop which
interrupts the udev postinst, and the failures cascade from there:
# touch /etc/udev/kernel-upgrade
# dselect
Reading package lists... Done
Buildi
On Sat, 2006-03-04 at 00:47 +0100, maximilian attems wrote:
> On Thu, 02 Mar 2006, Adam C Powell IV wrote:
>
> > The new upgrade procedure fails on alpha, regardless of the kernel
> > workaround, there's still a udev - initramfs-tools dependency loop which
> > inte
On Mon, 2006-03-06 at 08:01 +0100, maximilian attems wrote:
> On Sun, Mar 05, 2006 at 10:54:33PM -0500, Adam C Powell IV wrote:
> >
> > Okay, 0.53 is in testing now (maybe a day or two ago). But again, with
> > the new initramfs-tools unpacked (but not configured):
>
On Wed, 2006-07-05 at 18:02 +0200, Luk Claes wrote:
> Package: libluminate7
> Severity: serious
> Version: 0.10.0-2
>
> Hi
>
> Your package is not installable as it depends on libpetsc2.3.0 which is
> not available anymore. You might want to update the dependency to
> libpetsc2.3.1.
Thank you.
On Fri, 2005-10-28 at 13:58 -0700, Steve Langasek wrote:
> On Fri, Oct 28, 2005 at 09:59:34PM +0200, Artur R. Czechowski wrote:
> > On Fri, Oct 28, 2005 at 09:55:25PM +0200, Leopold Palomo Avellaneda wrote:
> > > I did a build-deps and and dpkg-buildpackage to make sure that I had all
> > > the
On Fri, 2005-11-04 at 09:36 +0100, Daniel Schepler wrote:
> Package: illuminator
> Severity: serious
> Version: 0.9.1-3
>
> >From my pbuilder build log:
>
> ...
> -> Considering dvips
>-> Trying dvips
>-> Cannot install dvips; apt errors follow:
Thanks. What package(s) provide the
On Fri, 2005-11-25 at 11:52 +0100, Petr Salinger wrote:
> Hi.
>
> dvips is now merged in tetex-bin
>
> BTW, illuminator builds fine on GNU/kFreeBSD
>
> Petr
Thank you, I should be able to upload a new upstream with this bug fixed
on Friday Jan 6. [Please no NMUs before then...]
-Adam
--
GPG
Hello,
On Tue, 2005-08-09 at 20:44 +0100, Martin Michlmayr wrote:
> Hi Adam (et al.),
>
> Sorry for not responding earlier but I've been travelling and quite
> busy and completely forgot about this issue. As I said, I don't know
> what the ideal situation is. The nice thing about the transition
Greetings,
I'm afraid I'm just back from a couple of weeks out of the country and
with very limited email contact. During this time, my packages were
(rightfully) rejected from the NEW queue, and the 0-day NMU policy took
effect, under which you NMU-ed my packages. I had not foreseen this
change
Thanks, will do.
On Thu, 2005-08-11 at 13:54 -0400, Justin Pryzby wrote:
> I would suggest emailing [EMAIL PROTECTED] or filing a
> bug against ftp.debian.org, since they handle /new.
> Justin
>
> On Thu, Aug 11, 2005 at 01:37:00PM -0400, Adam C Powell IV wrote:
> > Gr
On Thu, 2005-08-11 at 22:23 +0200, Adeodato Simó wrote:
> * Adam C Powell IV [Thu, 11 Aug 2005 13:37:00 -0400]:
>
> > Greetings,
>
> Hi,
>
> > I'm afraid I'm just back from a couple of weeks out of the country and
> > with very limited email c
Okay, lessons learned etc., here's a sugggestion:
Since it's been less than 24 hours since the NMU was accepted, I propose
that if I can get the new 1.2.7 package done by 8 PM EDT tonight
(midnight GMT), that I just use the same package names in 1.2.5.3-6.1.
This should not cause too much trouble
Package: scalapack
Version: 1.7-9
Severity: serious
Greetings,
scalapack is failing to build on arm and PPC. On arm, the error is:
gcc -o /home/hazelsct/scalapack-1.7/TESTING/xigemr pigemrdrv.o -L
/home/hazelsct/scalapack-1.7 -lscalapack-lam -lblacsCinit-lam -lblacs-lam
-lblacsCinit-lam -lmp
tags 332955 patch
thanks
On Sun, 2005-10-09 at 14:58 -0400, Adam C Powell IV wrote:
> Package: scalapack
> Version: 1.7-9
> Severity: serious
>
> Greetings,
>
> scalapack is failing to build on arm and PPC. On arm, the error is:
>
> gcc -o /home/hazelsct/s
Greetings,
I'm wondering whether the last four months have provided enough time to
confirm this is still a bug deserving of the "grave" status. Because of
this bug, geomview has been removed from testing, which nearly derailed
the transition of about 40 packages today.
Is it time to mark this "u
Hi,
I just uploaded a fix which seems to work. Sorry about the delay!
-Adam
On Sat, 2005-04-16 at 18:16 +0200, Emanuele Rocca wrote:
> Hello Adam,
>
> * Adam C Powell IV <[EMAIL PROTECTED]>, [2005-02-16 21:33 -0500]:
> > I'll see if I have time to upload a fix in th
On Thu, 2005-04-21 at 12:55 +0100, Carlos Rodrigues wrote:
> Adam C Powell IV wrote:
> > retitle 175604 cxx's "compaq" mangling style not supported by binutils
> > severity 175604 grave
> > thanks
> >
> > At some point in the past two years, bi
Hello Helge,
I apologize for the delay in getting to this bug. Two things have been
holding up a fix to this. First, four of my five alpha machines are
currently inoperable, so I'm having a hard time maintaining these
packages.
Second, I have been awaiting a reply from Compaq/HP contacts on
whe
On Tue, 2005-05-03 at 08:59 -0700, Blars Blarson wrote:
> Package: illuminator
> Version: 0.9.1-1
> Severity: serious
> Tags: sid
> Justification: Policy 3.3
>
> illuminator fails to build from source ons parc, duplicated on sparc
> pbuilder.
>
>
> dh_installdeb -a
> dh_shlibdeps -a
> dpkg-shlib
On Wed, 2005-05-04 at 01:00 +0200, Hendrik Sattler wrote:
> Am Dienstag, 3. Mai 2005 18:46 schrieb Adam C Powell IV:
> > On Tue, 2005-05-03 at 08:59 -0700, Blars Blarson wrote:
> > > Package: illuminator
> > > dh_makeshlibs -a
> [...]
> > > dh_shlibdeps -a
&
Hi,
Can you do me a favor and upload the illuminator package you built?
Otherwise I'll try to figure out how to re-queue it on the sparc buildd
(I've been meaning to learn how to do this for some time).
Thanks.
On Tue, 2005-05-03 at 23:08 -0400, Jurij Smakov wrote:
> On Tue, 3 May 2005, Blars Bl
Hmm, if the Java interpreter is segfaulting, how is that a bug against
babel? I'd think it should be a bug against the Java interpreter,
right?
On Wed, 2005-05-11 at 10:00 +0200, Bastian Blank wrote:
> Package: babel
> Version: 0.10.2-1
> Severity: serious
>
> There was an error while trying to
Thanks, I'll declare a conflict and re-upload in the next few days.
On Thu, 2005-05-12 at 19:09 +0200, Frank Lichtenheld wrote:
> Package: pimppa,parmetis-test
> Severity: grave
>
> Unpacking parmetis-test (from .../parmetis-test_3.1-1_i386.deb) ...
> dpkg: error processing /var/cache/apt/archive
Greetings,
As it turns out, bug 307502 *was* due to a sparc bug. Specifically
kernel bug 268450 in the 2.4 series was fixed in kernel-image-2.4.27-9,
and and 287287 in the 2.6 series was fixed in kernel-image-2.6.8-6.
Can someone running one of those fixed kernels please build and upload
the ill
On Tue, 2005-05-17 at 11:26 +0200, Frank Lichtenheld wrote:
> On Thu, May 12, 2005 at 11:09:18PM -0400, Adam C Powell IV wrote:
> > Thanks, I'll declare a conflict and re-upload in the next few days.
>
> Any specific reason that this hasn't happened yet? Anything one ca
5.html for
details.
On Wed, 2005-05-11 at 20:11 -0400, Adam C Powell IV wrote:
> Hmm, if the Java interpreter is segfaulting, how is that a bug against
> babel? I'd think it should be a bug against the Java interpreter,
> right?
>
> On Wed, 2005-05-11 at 10:00 +0200, Bastian B
Hello Steve,
Now that you mention it, no, it's not part of sarge but is still part of
woody (since it works there). Too bad, it was a neat compiler.
Thanks.
On Sun, 2005-06-12 at 21:54 -0700, Steve Langasek wrote:
> Hi Adam,
>
> Since the cxx package is now unusable with current binutils, is t
Package: raidtools2
Version: 1.00.4
Severity: grave
Justification: breaks reboot for sites with multiple RAID arrays
Tags: sarge
Greetings,
The transition from raidtools2 to mdadm breaks all installations with
more than one RAID array because /etc/raidtab is ignored during
autodetection. I disco
the
report.
And thank you Matthijs for the link into the release notes, I should
have caught that.
On Tue, 2005-06-21 at 22:12 +0100, Martin Michlmayr wrote:
> * Adam C Powell IV <[EMAIL PROTECTED]> [2005-06-19 20:02]:
> > The transition from raidtools2 to mdadm breaks all install
Package: menu
Version: 2.1.19
Severity: serious
Justification: Policy 10.9
Greetings,
During a woody->sarge upgrade, the new menu unpacked before the old
ghostview was removed, resulting in the following breakage:
Removing ghostview ...
/var/lib/dpkg/info/ghostview.postrm: /usr/bin/update-menus:
On Mon, 2005-01-10 at 19:08 +0100, Bill Allombert wrote:
> On Mon, Jan 10, 2005 at 11:00:57AM -0500, Adam C Powell IV wrote:
> > During a woody->sarge upgrade, the new menu unpacked before the old
> > ghostview was removed, resulting in the following breakage:
>
> Thanks
On Tue, 2005-01-11 at 13:56 +0100, Bill Allombert wrote:
> On Mon, Jan 10, 2005 at 05:52:20PM -0500, Adam C Powell IV wrote:
> > On Mon, 2005-01-10 at 19:08 +0100, Bill Allombert wrote:
> > > On Mon, Jan 10, 2005 at 11:00:57AM -0500, Adam C Powell IV wrote:
> > > >
; an
> ii libg2c0 1:3.4.0-4 Runtime library for GNU Fortran
> 77
> ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client
> li
> ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries
> m
>
> -
Package: hdf5
Version: 1.6.5-5
Severity: serious
Tags: patch
Greetings,
The binary h5perf in the hdf5-tools package requires the library
libh5test-1.6.5.so.0 which is not in any binary package. With
hdf5-tools installed, this results in:
# /usr/bin/h5perf
h5perf: error while loading shared libra
On Mon, 2008-02-11 at 22:38 +0530, Kumar Appaiah wrote:
> Package: libmpich1.0gf
> Version: 1.2.7-6
> Severity: serious
> Tags: patch
>
> Hi!
>
> I noticed that the libmpich1.0gf package is empty! Please find
> attached a simple patch to set the right install directories in
> debian/rules.
>
> I
On Wed, 2008-02-20 at 11:57 -0500, Aaron M. Ucko wrote:
> Package: libhdf5-serial-1.6.5-0
> Version: 1.6.5-5.1
> Severity: serious
> Justification: Policy 8.6.4
>
> libhdf5-serial-1.6.5-0's shlibs file (generated from debian/shlibs.in
> AFAICT) omits the newly added h5test library; as a result, hd
On Thu, 2008-02-21 at 09:58 -0500, Aaron M. Ucko wrote:
> Riku Voipio <[EMAIL PROTECTED]> writes:
>
> > It should be fixed now with 1.6.5-5.2 - ateast the build logs now
> > show correct dependencies for hdf5-tools.
>
> Yeah, -5.2 looks good; thanks!
Oh, look at that, you'd already uploaded 5.2
On Sun, 2008-02-24 at 17:53 +0100, Christophe Prud'homme wrote:
> Package: petsc
> Version: 2.3.3
> Severity: serious
>
> --- Please enter the report below this line. ---
>
> MPI support is missing spooles and PETSc is looking for it in libpetscmat.
> PETSc in unstable is unusable at the moment
>
On Wed, 2007-07-25 at 11:38 -0600, dann frazier wrote:
> Package: petsc
> Version: 2.3.3-1
> Severity: serious
> Justification: no longer builds from source
>
> >From
> >http://buildd.debian.org/fetch.cgi?&pkg=petsc&ver=2.3.3-1&arch=ia64&stamp=1185328468&file=log:
>
> [snip]
> TESTING: checkFort
merge 434666 435803
thanks
On Sun, 2007-07-29 at 17:00 +0800, LUK ShunTim wrote:
> Package: libpetsc2.3.3-dev
> Version: 2.3.3
> Severity: grave
> Justification: renders package unusable
>
> When trying to install petsc-dev, this error is encountered:
>
> The following packages have unmet depend
On Mon, 2007-08-06 at 13:51 +0800, LUK ShunTim wrote:
> Adam C Powell IV wrote:
> > merge 434666 435803
> > thanks
>
> [snipped]
>
> > I believe petsc 2.3.3-1 now builds, since the new suitesparse and
> > openmpi were uploaded. Can you please try to build it
On Fri, 2007-08-03 at 15:33 -0400, Adam C Powell IV wrote:
> On Wed, 2007-07-25 at 11:38 -0600, dann frazier wrote:
> > Package: petsc
> > Version: 2.3.3-1
> > Severity: serious
> > Justification: no longer builds from source
> >
> > >From
> > &g
On Mon, 2007-12-17 at 13:36 -0600, Dirk Eddelbuettel wrote:
> On 17 December 2007 at 18:45, Debian Bug Tracking System wrote:
> | Processing commands for [EMAIL PROTECTED]:
> |
> | > reassign 456721 libopenmpi1
> | Bug#456721: libpetsc.so depends on unexistent libraries
> | Bug reassigned from pac
On Mon, 2007-12-17 at 14:47 -0600, Dirk Eddelbuettel wrote:
> On 17 December 2007 at 21:13, Manuel Prinz wrote:
> | Am Montag, den 17.12.2007, 13:36 -0600 schrieb Dirk Eddelbuettel:
> | > Indeed, what were we thinking here Manuel? [...] In light of this, can
> | > you remind me why you put the libs
On Mon, 2007-12-17 at 16:24 -0600, Dirk Eddelbuettel wrote:
> On 17 December 2007 at 22:27, Manuel Prinz wrote:
> | Am Montag, den 17.12.2007, 14:47 -0600 schrieb Dirk Eddelbuettel:
> | > On 17 December 2007 at 21:13, Manuel Prinz wrote:
> | No, as there are more libraries needed for the compiler w
Hello,
On Tue, 2007-12-18 at 02:00 +0100, Manuel Prinz wrote:
> Hi guys!
>
> Am Montag, den 17.12.2007, 17:53 -0500 schrieb Adam C Powell IV:
> > That already happens via alternatives slaves. As discussed earlier,
> > it's inappropriate with ABI-incompatible sona
Hi,
The patch looks good, it should fix all of the breakage. Just a couple
of little points of clarification below.
On Wed, 2007-12-19 at 06:58 -0600, Dirk Eddelbuettel wrote:
> On 19 December 2007 at 13:08, Manuel Prinz wrote:
> | Am Dienstag, den 18.12.2007, 21:23 -0600 schrieb Dirk Eddelbuett
On Fri, 2007-10-26 at 15:32 +0200, Bastian Blank wrote:
> Package: petsc
> Version: 2.3.3-2
> Severity: serious
>
> petsc build depends against libopenmpi-dev. This package is only
> available on a few arches. Either this build-dep or the petsc package
> have to go.
This makes no sense at all. W
retitle 448158 FTBFS: Fortran MPI check fails
thanks
Hello Ondrej,
This is a separate issue, and should have been a new bug. The limited
platform availability of OpenMPI is a non-issue, and I was about to
close it after a week of inactivity.
I've retitled this bug to your issue, which is an FTB
Hello Ondrej,
On Fri, 2007-11-02 at 11:22 -0400, Adam C Powell IV wrote:
> I've retitled this bug to your issue, which is an FTBFS, and will try to
> get to it sometime next week. I'll also see if I can build and test
> petsc4py and libmesh using OpenMPI.
>
> On Fri,
Hello Ondrej,
Thank you for your detailed inquiry into this issue. I'm glad you got
it working.
On Wed, 2007-11-07 at 23:54 +0100, Ondrej Certik wrote:
> On Nov 7, 2007 9:52 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> > > TESTING: checkCxxCompiler from
> > > config.setCompilers(/tmp/buildd/pe
severity 441882 grave
merge 441882 441946
thanks
Got it yesterday, thanks. Will upload ASAP.
On Tue, 2007-09-11 at 20:57 -0500, Steve M. Robbins wrote:
> Package: libmpich1.0ldbl
> Version: 1.2.7-3
> Severity: grave
>
> Unpacking libmpich1.0ldbl (from .../libmpich1.0ldbl_1.2.7-3_i386.deb) ...
>
On Sun, 2007-09-23 at 16:11 +0200, Thomas Viehmann wrote:
> severity 441946 serious
> thanks
>
> Hi Adam,
>
> I think this should be of serious severity, as having two packages share
> files without declaring appropriately is a severe policy violation. In
> particular, it might be better not to h
Wow, thanks for the thirty minutes notice. I had planned to build and
upload tomorrow. Oh well.
On Sun, 2007-09-23 at 11:09 -0400, Ari Pollak wrote:
> I plan to NMU this package. Attached is the interdiff from -3.
>
> plain text document attachment (mpich_1.2.7-3-3.1.diff)
> diff -u mpich-1.2.7
Hello and thanks for the report.
By the way, do you have the configure.log file available from the build?
That would help my diagnosis of the problem.
I have to say, it is not helpful to tag something "FTBFS on i386"
when that is in fact not the case. It builds just fine in unstable on
i386. A
reassign 484196 hypre
reassign 484341 hypre
merge 484196 484341
retitle 484196 hypre: Build-Depends is missing LAPACK, and BLAS/LAPACK libs are
wrong
thanks
On Tue, 2008-06-03 at 22:04 +0200, Lucas Nussbaum wrote:
> On 03/06/08 at 14:44 -0400, Adam C Powell IV wrote:
> > Hello and thank
ssential supposed to have
libstdc++-dev?
I'm removing that from the linked libs anyway; using mpiCC instead of
mpicc to link should take care of that.
-Adam
On Tue, 2008-06-03 at 20:09 -0400, Adam C Powell IV wrote:
> reassign 484196 hypre
> reassign 484341 hypre
> merge 484196 484341
&
severity 498213 important
thanks
Thank you for the report. People have been using mpich for nearly five
months, so "unusable" is not warranted, but this is an important
problem.
Unfortunately, upstream no longer maintains MPICH1, so they probably
won't fix this, but would tell you to try MPICH2.
On Tue, 2008-09-23 at 10:30 +0200, Raphael Hertzog wrote:
> On Thu, 07 Aug 2008, Christoph Haas wrote:
> > > For now and the lenny release, it seems we need to make the packages
> > > conflict.
> >
> > In favor.
>
> Why has this not yet been done ?
>
> This is a long-standing RC bug that has to
On Tue, 2008-09-23 at 14:53 +0200, Christoph Haas wrote:
> On Dienstag, 23. September 2008, Raphael Hertzog wrote:
> > On Thu, 07 Aug 2008, Christoph Haas wrote:
> > > > For now and the lenny release, it seems we need to make the packages
> > > > conflict.
> > >
> > > In favor.
> >
> > Why has this
what the full directory structure implications are.
>
> ben
>
> On Wed, Aug 06, 2008 at 06:55:52PM -0400, Adam C Powell IV wrote:
> > Greetings,
> >
> > There's a python-babel package for internationalization, which has a
> > Python namespace conflict w
On Tue, 2008-09-23 at 14:41 -0700, Tom Epperly wrote:
> Adam C Powell IV wrote:
> > Hi again,
> >
> > I know it's been a while...
> >
> > So to do this right, I'd just change 'setup(name="babel",' to
> > 'setup(name="
clone 493742
reopen -1
severity -1 important
thanks
Though the package conflict with python-pybabel is now explicit, I am
working on upstream to resolve it completely by changing the egg-info of
this package. This deserves to be a new bug, with all of the history,
though the original RC issue is
clone 493742 -1
reopen -1
severity -1 important
thanks
Messed up the clone command.
On Wed, 2008-09-24 at 14:58 -0400, Adam C Powell IV wrote:
> clone 493742
> reopen -1
> severity -1 important
> thanks
>
> Though the package conflict with python-pybabel is now explicit,
Hello again,
On Wed, 2008-05-07 at 14:06 +0200, Ondrej Certik wrote:
> On Wed, May 7, 2008 at 12:56 AM, Maximiliano Curia
> <[EMAIL PROTECTED]> wrote:
> > Hola Adam C Powell IV!
> >
> > El 06/05/2008 a las 15:28 escribiste:
> >> Apologies for the delay in
On Wed, 2008-06-11 at 06:29 +0200, Christophe Prud'homme wrote:
> On Wed, Jun 11, 2008 at 12:54 AM, Adam C Powell IV <[EMAIL PROTECTED]> wrote:
> > Hello again,
> >
> > On Wed, 2008-05-07 at 14:06 +0200, Ondrej Certik wrote:
> >> On Wed, May 7, 2008 at
On Wed, 2008-06-11 at 13:02 +0200, Ondrej Certik wrote:
> On Wed, Jun 11, 2008 at 12:08 PM, Adam C Powell IV <[EMAIL PROTECTED]> wrote:
> > On Wed, 2008-06-11 at 06:29 +0200, Christophe Prud'homme wrote:
> >> On Wed, Jun 11, 2008 at 12:54 AM, Adam C Powell IV &l
On Fri, 2008-04-25 at 01:18 +0200, Martin Zobel-Helas wrote:
> Package: hypre
> Version: 2.0.0.dfsg-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
> > Automatic build of hypre_2.0.0.dfsg-1 on lebrun by sbuild/sparc 98
> > Build started at 20080423-1139
>
>
On Fri, 2008-04-25 at 18:36 +0200, Matthias Klose wrote:
> As a second step please consider changing the java-gcj-compat-dev b-d
> to default-jdk-builddep, making the package independent of a specific
> implementation and depend on the jdk, which is most suitable for this
> architecture. default-jd
Hello,
Apologies for the delay in getting back to you all. It looks like this
bug is still open. Is this something I can help with, now that I'm part
of pkg-scicomp?
-Adam
On Mon, 2008-03-31 at 15:12 +0200, Ondrej Certik wrote:
> On Mon, Mar 31, 2008 at 2:25 PM, Maximiliano Curia
> <[EMAIL PRO
reassign 483324 babel
retitle 483324 libsidl-dev must depend on libparsifal-dev
thanks
For libtool to link with libsidl.la, libparsifal.la must be there.
With this change, illuminator will build.
-Adam
--
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Engineering consultin
On Thu, 2008-08-07 at 00:05 +0200, Christoph Haas wrote:
> On Mittwoch, 6. August 2008, Adam C Powell IV wrote:
> > On Sun, 2008-08-03 at 15:30 +0200, Christoph Haas wrote:
> > > We talked about the python-babel name clash recently. Although I
> > > renamed my package
On Thu, 2008-08-07 at 00:28 +0200, Christoph Haas wrote:
> On Donnerstag, 7. August 2008, Adam C Powell IV wrote:
> > Okay. Before writing upstream, "dpkg -L python-babel" shows everything
> > in site-packages/sidl[x]. Is there a way I can change my EGG-INFO to
>
Greetings,
There's a python-babel package for internationalization, which has a
Python namespace conflict with the Python runtime bindings for the SIDL
Babel.
As a possible resolution, how much stuff would I break by changing
"babel" to "sidl" in [sidl]setup.py? I'm afraid I don't know a whole
l
reopen 486706
severity 486706 normal
reopen 486708
severity 486708 normal
thanks
Hello,
Though the 0.6.1 .debs are no longer in our archive, for the purposes of
testing and ubuntu users and general consistency this should get fixed.
(Ubuntu Hardy has 0.6.1.)
[I'm about to upload a fixed version.
On Fri, 2008-04-04 at 17:18 +0200, Domenico Andreoli wrote:
> retitle 474249 petsc: FTBFS: wrongly guess the MPI directory
> tags 474249 +patch
> thanks
>
> On Fri, Apr 04, 2008 at 04:58:26PM +0200, Domenico Andreoli wrote:
> >
> > It looks like definition of PETSC_MPI in debian/rules is somewha
Package: petsc
Version: 2.3.3-9
Severity: serious
Due to an unknown toolchain change around March 24, petsc has suddenly
started to fail to build from source. The failure comes at the end of
the configuration process:
TESTING: checkSizeof from
config.types(/home/hazelsct/petsc-2.3.3/python/Buil
Greetings,
Due to a change somewhere in the toolchain, PETSc configuration suddenly
stopped working on Debian unstable. The error message in configure.log
is:
TEST checkSizeof from
config.types(/home/hazelsct/petsc-2.3.3/python/BuildSystem/config/types.py:246)
TESTING: checkSizeof from
config.
both very much for the quick work, above and beyond the call
of duty! I'll upload a version which closes this and also 474249 later
tonight.
-Adam
> On Sat, 5 Apr 2008, Adam C Powell IV wrote:
>
> > Greetings,
> >
> > Due to a change somewhere in the toolchain, PETSc
On Fri, 2008-04-04 at 12:17 -0400, Adam C Powell IV wrote:
> On Fri, 2008-04-04 at 17:18 +0200, Domenico Andreoli wrote:
> > retitle 474249 petsc: FTBFS: wrongly guess the MPI directory
> > tags 474249 +patch
> > thanks
> >
> > On Fri, Apr 04, 2008 at 04:58:26
On Tue, 2008-04-15 at 12:01 +0200, Adeodato Simó wrote:
> * Adeodato Simó [Tue, 15 Apr 2008 11:48:54 +0200]:
>
> > For the latter, start by:
>
> > * changing *every* instance of python2.4 to just "python" in your
> > debian/control and debian/rules file, including Package: python2.4-babel
>
On Mon, 2009-05-11 at 15:11 +0200, Filippo Rusconi wrote:
> On Mon, May 11, 2009 at 02:11:18PM +0200, Julien Cristau wrote:
> >
> > On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
> >
> > > No, policy is very clear on that: if you call the "build" target, you
> > > _must_ satisf
severity 522287 important
tags 522287 unreproducible
thanks
Hi Christophe,
Sorry about the delay, I'm accustomed to getting bugs via email, and
only just subscribed to the PTS.
I'm afraid I can't reproduce this. Did you set PETSC_DIR and PETSC_ARCH
as described in README.Debian? I'm afraid PET
clone 522699 -1
reassign -1 libpetsc3.0.0-dev
retitle -1 libpetsc3.0.0-dev: petsc.m4 needs update for 3.0.0 directory names
thanks
On Tue, 2009-04-07 at 21:13 -0400, Adam C Powell IV wrote:
> On Wed, 2009-04-08 at 00:17 +0100, peter green wrote:
> > This bug only affects building with pe
On Wed, 2009-05-13 at 15:06 +0200, Rafael Laboissiere wrote:
> package libsuitesparse-3.2.0
> severity 528522 serious
> merge 528522 526422
> thanks
>
> * Adam C Powell IV [2009-05-13 08:39]:
>
> > Package: libsuitesparse-3.2.0
> > Version: 3.2.0-4
> > S
Package: libpetsc3.0.0
Severity: grave
Version: 3.0.0-3
Greetings,
The shared library package has no shared libraries, and is thus
unusable. It looks like --with-shared is being ignored in the build
process.
-Adam
--
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Engineer
On Sun, 2009-05-17 at 21:37 +0200, Kurt Roeckx wrote:
> Source: deal.ii
> Version: 6.2.0-2
> Severity: serious
>
> Hi,
>
> There was an error while trying to autobuild your package:
>
> > Start Time: 20090517-1838
>
> [...]
>
> > Build-Depends: debhelper (>= 4.1.67), quilt, autoconf, gfortran,
On Tue, 2009-05-19 at 16:20 +0100, Jurij Smakov wrote:
> Package: petsc
> Version: 3.0.0.dfsg-4
> Severity: serious
>
> Hi,
>
> The latest version of petsc failed to build on hppa:
>
> https://buildd.debian.org/~luk/status/package.php?suite=unstable&p=petsc#fail-petsc-hppa
Thanks. Is the confi
severity 529485 important
tags 529485 moreinfo
thanks
On Fri, 2009-05-22 at 16:06 +0100, Jurij Smakov wrote:
> On Wed, May 20, 2009 at 10:24:07AM -0400, Adam C Powell IV wrote:
> > On Tue, 2009-05-19 at 16:20 +0100, Jurij Smakov wrote:
> > > Package: petsc
> >
Package: elmerfem
Version: 5.5.0.svn.4190.dfsg-1
Severity: serious
See above, please change python-qt4 to python-qt4-dev in Build-Depends.
-Adam
--
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Engineering consulting with open source tools
http://www.opennovation.com/
si
On Wed, 2009-06-17 at 09:55 +0200, Thomas Viehmann wrote:
> Hi Adam,
>
> say, what is the state of this bug. Now that suitesparse is fixed, I
> would love to see this fixed as well. If you do not have the time at the
> moment, I am happy to help out with an NMU.
Oh yeah, I've been neglecting this
On Wed, 2009-04-08 at 00:17 +0100, peter green wrote:
> This bug only affects building with petsc 3.0.0, the "bmake" (whatever
> that is) stuff seems to simply have dissapeared with that version (that
> is I don't see any evidence of it moving to another package and there is
> no mention of it i
found 520003 5.2.1-3
thanks
This still doesn't work:
# ls -l /usr/lib/libQVTK*
lrwxrwxrwx 1 root root 14 2009-04-08 12:07 libQVTK.so -> libQVTK.so.5.2
lrwxrwxrwx 1 root root 16 2009-04-08 11:10 libQVTK.so.5.2 ->
libQVTK.so.5.2.1
-rw-r--r-- 1 root root 253128 2009-04-06 15:59 libQVTK.so.5
On Mon, 2009-07-20 at 19:03 +1000, Steffen Joeris wrote:
> Hi
>
> So I had another look at the issue. Indeed, set_nss_error was undefined, so I
> used a different function. Also, I think there was another regression with
> displaying signed and encrypted S/MIME messages. Could you please test th
On Sun, 2009-08-02 at 08:58 -0600, dann frazier wrote:
> reopen 539063
> found 539063 1.4.0.dfsg-3
> thanks
>
> Looks like the patch may not be getting applied - missing entry in
> debian/patches/series?
Indeed, my bad. Building now, will upload by tomorrow.
-Adam
--
GPG fingerprint: D54D 1AEE
severity 535318 important
forwarded 535318 http://sourceforge.net/mailarchive/forum.php?forum_id=28092
thanks
This is important, but not grave -- the package has other users who
haven't run into this problem, and "data loss" generally refers to
corrupting or erasing on-disk data.
Thanks for the r
Package: elmerfem
Version: 5.5.0.svn.4190.dfsg-3
Severity: serious
The post module fails to build because screensave.o (and likely others)
are built without -fPIC and then linked as shared objects.
-Adam
--
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Engineering consulti
On Fri, 2007-01-26 at 00:15 +0100, Aurelien Jarno wrote:
> Package: illuminator
> Version: 0.10.0-3
> Severity: serious
>
> >From my build log:
> [snip]
> dpkg-buildpackage: source package is illuminator
> dpkg-buildpackage: source version is 0.10.0-3
> dpkg-buildpackage: host architecture kfreebs
On Tue, 2006-12-12 at 13:10 -0800, Russ Allbery wrote:
> Adam C Powell IV <[EMAIL PROTECTED]> writes:
>
> > Package: openssh-client
> > Version: 1:4.3p2-7
> > Severity: important
>
> > Greetings,
>
> > First, this needs to conflict with old vers
1 - 100 of 242 matches
Mail list logo
