Package: python3-h5py
Version: 2.10.0-2
Severity: serious
The latest version of h5py compiled against MPI completely fails to
import if there is no network connection:
servo:~ 0$ python3 -c 'import h5py; print("foo")'
--
No n
On Sat, Nov 09 2019, Gianfranco Costamagna wrote:
> I rescheduled it to go in *now* :)
>
> thanks for doing it, I admit I lost a lot of time trying to trace it
> down and I failed, so help is appreciated!
I tested the new 0.10.0-5 version in unstable and it fixes the issue.
Thank you Georges and
On Tue, 15 Oct 2019 13:02:44 +0200 Carlos Pascual wrote:
> Just adding that I checked and 0.10.0-1 is not affected.
>
> Note this bug is affecting the to build the taurus-pyqtgraph package:
>
> https://salsa.debian.org/science-team/taurus-pyqtgraph/-/jobs/362247
It's very peculiar that the upst
I am unclear how to test this right now as I don't have direct access to
an armhf system. It builds fine on the systems I have access to.
Given that it seems to build fine on other systems, I'm tempted to solve
this problem in the short term by just excluding armhf.
If anyone thinks that's a bad
Package: mps-youtube
Version: 0.2.7.1-2
Severity: grave
Justification: renders package unusable
mpsyt crashes whenever I try to do a search:
Searching for 'radiohead'
Traceback (most recent call last):
File "/usr/bin/mpsyt", line 11, in
load_entry_point('mps-youtube==0.2.7.1', 'console_scr
Package: elpa-go-mode
Version: 3:1.5.0-1
Severity: grave
Justification: renders package unusable
I don't understand the new elpa system, but for whatever reason this
packages is not actually providing go-mode for me. When I try "M-x
go-mode" I get the following error:
command-execute: Cannot ope
On Mon, Jul 31 2017, Yannick Roehlly wrote:
> Launching xapers fails with “ImportError: No module named pybtex”. The package
> depends on pybtex but this one recently (26 Jul 2017) switched to Python 3 for
> the CLI, so the python-pybtex package is not installed anymore by the
> dependency.
Hi, Y
Please do not remove runit from Debian. While I understand that systemd
provides the same functionality that runit does, runit is still
nonetheless a useful system that many things currently depend on.
I see no reason why the entire runit source package needs to be removed
if the only problem is
close 825365 0.10-1
thanks
This was fixed upstream by having the gui module only imported when needed.
On Tue, Nov 29 2016, Piotr Roszatycki wrote:
> I can't reproduce this bugs. Can you run, ie.:
>
> $ bash -x fakechroot true
>
> please?
servo:~ 0$ bash -x fakechroot true
+ FAKECHROOT_VERSION=2.19
+ '[' '' = true ']'
+ fakechroot_lib=libfakechroot.so
+ fakechroot_paths=no
+ fakechroot_sysconfdir=
Package: fakechroot
Version: 2.19-2
Severity: grave
Justification: renders package unusable
servo:~ 0$ fakechroot true
fakechroot: preload library not found, aborting.
servo:~ 1$
I think that pretty much covers it. Renders the debirf package unusable.
-- System Information:
Debian Release: stre
Package: python3-xapian
Version: 1.4.0-2
Severity: grave
Justification: renders package unusable
I run into the following ImportError when I try to import the python3
xapian module:
servo:~ 0$ python3 -c 'import xapian'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/py
Package: mpv
Version: 0.18.0-1
Severity: grave
Justification: renders package unusable
Not sure what happened, but mpv no longer works on my system:
servo:~ 0$ mpv
mpv: symbol lookup error: mpv: undefined symbol: ass_set_check_readorder
servo:~ 127$
I'm assuming some recent update broke this? L
Package: banshee
Version: 2.9.1-5
Severity: grave
Justification: renders package unusable
banshee completely fails to start. This is currently happening for
both the unstable and experimental versions, but I post the terminal
log for the experimental version here:
servo:~ 0$ banshee --debug --de
notfound 806377 0.35
severity 806377 normal
tags 806377 unreproducible
thanks
I can build a jessie rescue image on my stretch/sid system no problem.
jamie.
signature.asc
Description: PGP signature
On Thu, Nov 26 2015, Antoine Beaupré wrote:
> Package: debirf
> Version: 0.34
> Severity: grave
>
> I can't seem to build a jessie image with debirf:
>
> W: See /home/anarcat/debirf/rescue/root/debootstrap/debootstrap.log for
> details (possibly the package systemd is at fault)
Hi, Antoine. Can
tags 795639 + unreproducible moreinfo
On Sat, Aug 15 2015, Russ Allbery wrote:
> Package: assword
> Version: 0.8-2
> Severity: grave
>
> assword can no longer decrypt any of my password stores. It fails with
> the error:
>
> mithrandir:~$ assword dump foo
> Assword database error: Decryption err
On Tue, Nov 25 2014, Daniel Kahn Gillmor wrote:
> Thanks for the proposed patch. I'm not sure how to test it directly,
> but it seems a bit overzealous to me -- it's trying to read from stdin
> even when a logging argument was passed to it.
>
> I suspect this only passes the test suite because th
If a lot message is not intended for output, it can close the input
pipe prematurely, which can trigger a sigpipe error. Instead, always
redirect input somewhere, so that the input pipe is not prematuring
closed. This should help fix the SIGPIPE error that we're seeing in
https://bugs.debian.org
This is a suggested patch to fix the issue. The patch has the log
function always accept the stdin, and redirect it to /dev/null if it
doesn't intend to spit it out.
All monkeysphere tests pass with this patch. Can someone test this on
one of the affected systems?
--
To UNSUBSCRIBE, email to
I just got hit with this after doing an upgrade after the wheezy
release. I didn't initially notice, but less was removed during the
upgrade, and I was not able to reinstall without pulling from unstable.
I imagine a lot of people are going to start hitting this bug now that
the release has happe
On Sun, 24 Apr 2011 11:51:10 -0700, Jameson Graef Rollins
wrote:
> Ah! Thank you so much KiBi! Thank you thank you thank you. rm -rf'ing
> /run and restarting (after making sure 167-3 was installed) seemed to
> fix the problem.
Just for clarification, that's udev 167-2
On Sun, 24 Apr 2011 11:36:42 +0200, Cyril Brulebois wrote:
> Isn't that just udev + /run fun? See #621036
Ah! Thank you so much KiBi! Thank you thank you thank you. rm -rf'ing
/run and restarting (after making sure 167-3 was installed) seemed to
fix the problem.
jamie.
pgpaQ01ajpTVa.pgp
Des
Package: xserver-xorg
Version: 1:7.6+6
Followup-For: Bug #622175
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I think I am experiencing this same problem. When xdm starts, I have
no keyboard or mouse, either with my internal keyboard/mouse (thinkpad
x201) or with an external USB keyboard. If
On Sun, 31 Jan 2010 08:31:35 +0100, Mike Hommey wrote:
> Hum, if *I* file a bug as RC against a package *I* maintain, it *is* RC.
Actually, that does not follow. The severity of a bug affects a lot of
things other than just the maintainer. For instance, by setting the
severity of this bug as se
On Thu, Dec 24, 2009 at 05:39:59PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
Thank you very much for this report, Lucas. I have added cpio to the
Build-Depends, so this should be resolved on the next upload.
jamie.
signatur
Package: octave3.0-headers
Version: 3.0.5-6+b1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The package appears to have incompatible dependencies for squeeze:
servo:~ 0$ apt-cache policy gcc-4.3
gcc-4.3:
Installed: 4.3.4-1
Candidate:
27 matches
Mail list logo
