Source: python-canmatrix
Followup-For: Bug #1056461
This seems to really be a bug in python3-future:
```sh
$ python3-c "import past.builtins"
$ python3.12 -c "import past.builtins"
Traceback (most recent call last):
File "", line 1, in
File
Source: bambootracker
Version: 0.6.1-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
bambootracker ftbfs with RtAudio 6 (currently found in experimental).
```
g++ -c -pipe -g -O2
Source: mlt
Version: 7.18.0-2
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
mlt ftbfs with RtAudio 6 (currently in experimental).
```
[ 89%] Building CXX object
Source: aubio
Followup-For: Bug #1028178
Dear Maintainer,
i've prepared and uploaded an NMU that fixes the problem.
Unfortunately, I failed to upload to a DELAYED/n queue (and instead uploaded
directly into the archives).
I sincerely apologize for that mistake.
In any case, i'm attaching the
Package: network-manager-gnome
Version: 1.30.0-1
Severity: serious
Justification: Policy 7.4
Dear Maintainer,
'network-manager-gnome' fails to install if libnma-common_1.10.2-1 is also
installed, as both provide the same file:
```
dpkg: error processing archive
Source: asio
Version: 1:1.18.1-1
Followup-For: Bug #1013495
any news on this?
this serious bug is triggering an AUTOREMOVAL of *multiple* of my packages
in about two weeks, which i would like to avoid.
gfmds
IOhannes
PS: re-sending, as i think my original email got lost between MUA and MTA
On Tue, 17 May 2022 22:31:14 +0100 peter green wrote:
Version 3.0.7 seems to be be passing most of the time on armhf, though there
were
a few failures duing attempts to migrate gcc-12. The failures appear to be
timeouts.
Unfortunately 3.0.7 seems to be pretty consistently failing on s390x :(
Package: qgis-providers
Version: 3.22.5+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
thanks for packaging qgis-providers.
Unfortunately, with the latest upload (3.22.5), the package fails to install,
as it segfaults in the postinst script.
The culprit is
Package: python3-tesserocr
Version: 2.4.0-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
i'm experimenting a bit with OCR and tried out python3-tesserocr.
Unfortunately, it appears to be completely unusable:
~~~
$ python3
Python 3.7.3 (default, Mar 26 2019, 07:25:18)
Package: giada
Version: 0.15.2+ds1-1
Severity: serious
Justification: ftbfs
Dear Maintainer,
even with a fixed JUCE-5.4.1 (providing all the required opcodes for building a
plugin host), giada FTBFS with a number of unresolved symbols related to curl.
Either new JUCE requires to link against
Source: juce
Severity: serious
Tags: upstream
Justification: makes rdeps FTBFS
juce-5.4 has dropped the built-in VST2 support and now depends on the Steinberg
SDK (which - apart from being proprietary and non-free - is no longer
available) for download at all.
This has severe implications on the
Package: grub-common
Version: 2.02+dfsg1-2
Followup-For: Bug #871229
Dear Maintainer,
today, when running a regular unstable->unstable upgrade i also experienced a
segmentation fault.
i do these updates regularly, e.g. the last update of grub-common (2.02-2 ->
2.02+dfsg1-1) happened on "Sun, Feb
On 2017-07-14 16:10, Benoit Mortier wrote:
> Le 10/07/2017 à 23:12, Mike Gabriel a écrit :
>>
>> Indeed, this would have been a good idea. Sorry for that. The packaging
>> was done last minute unfortunately, so such delays got lost while being
>> "in a hurry".
>
> yes my bad in part i forgot to
Control: severity -1 normal
thanks
on second thought, the issue is easy enough to work-around by the the
local admin, and a "serious" severity is probably not justified.
sorry for the havoc,
fgmasd
IOhannes
On 2017-07-10 15:50, IOhannes m zmoelnig wrote:
> Control: severity -1 seri
Package: fusiondirectory
Version: 1.0.19-1
Severity: serious
Justification: Policy 3.3
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
Package: fusiondirectory
Version: 1.0.19-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after upgrading my fusiondirectory installation from jessie (1.0.8.2-5)
to stretch (1.0.19-1) the package has become practically unusable.
(that's after adding workarounds for
Package: src:pycryptopp
Followup-For: Bug #833217
Control: tags -1 pending
thanks
I've just uploaded an NMU with a fix (using gzip instead of bzip2) to DELAYED/5.
Please find the diff attached.
mfgards
IOhannes
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT
Package: src:unicap
Followup-For: Bug #825370
Control: reassign -1 cdbs
This is really a regression in CDBS.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64
Package: libtesseract4
Version: 3.04.01-1
Severity: serious
Justification: Policy 7.4
Dear Maintainer,
libtesseract4 provides at least one identical file as libtesseract3 without
declaring a "Conflicts" relationshipt, does breaking any upgrade:
> Preparing to unpack
Package: svn-all-fast-export
Version: 1.0.10-3
Followup-For: Bug #795081
I had no clue that this is related to svn-1.9, but I can confirm the symptoms.
it seems the problem is related to *deleting* files.
here's a simple self-contained example to reproduce the problem:
## 1st create an
Package: python3.4
Version: 3.4.3-4
Severity: critical
Followup-For: Bug #783787
Reproduced on amd64.
This makes *any* software that uses python3 unusable, so I'm escalating the
severity.
It also breaks the installation of packages (as this may use python3).
The issue seems to be that python3
Package: smartmontools
Version: 6.3+svn4002-2+b2
Followup-For: Bug #777583
Attached find a debdiff and a git-diff to add the or (at your option) any later
version clause to debian/copyright.
The debdiff is created using HEAD in git as the original package (so probably
NOT the version that is
Package: initramfs-tools
Version: 0.118
Followup-For: Bug #762984
i am hit by the same problem.
as a temporary fix, i added the 'vgchange -ay' to
/usr/share/initramfs-tools/scripts/local-top/lvm2
as adding it to
/etc/initramfs-tools/scripts/local-top/vgscan
somehow did not work (most likely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
reassign 731836 ftp.debian.org
thanks
On 2013-12-10 15:01, IOhannes m zmoelnig wrote:
severity 731836 serious reassign 731836 ftpmaster thanks
Justification: section 2.5 Packages must not depend on packages
with lower priority values
'gmerlin-avdecoder' (with the exception of
libgmerlin-avdec-dbg), namely:
libgmerlin-avdec1
libgmerlin-avdec-dev
libgmerlin-avdec-doc
gmerlin-plugins-avdecoder
cheers
On 2013-12-10 11:35, IOhannes m zmoelnig wrote:
Package: libgmerlin-avdec1 Version: 1.2.0~dfsg-3+b1 Severity:
minor
Dear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
severity 731836 serious
reassign 731836 ftpmaster
thanks
Justification: section 2.5 Packages must not depend on packages with
lower priority values (excluding build-time dependencies). In order to
ensure this, the priorities of one or more packages
the priority for the above gmerlin-avdecoder packages
from extra to optional. This package doesn't need to be in extra, and
as a library it might want to be used by other optional packages in
the future.
Thanks
On 2013-12-10 15:09, IOhannes m zmoelnig wrote:
severity 731835 serious reassign 731835
doesn't need to be in extra, and
as a library it might want to be used by other optional packages in
the future.
Thanks
On 2013-12-10 15:11, IOhannes m zmoelnig wrote:
reassign 731836 ftp.debian.org thanks
On 2013-12-10 15:01, IOhannes m zmoelnig wrote:
severity 731836 serious reassign 731836
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
severity 731835 serious
reassign 731835 ftp-master
thanks
Justification: section 2.5 Packages must not depend on packages with
lower priority values (excluding build-time dependencies). In order to
ensure this, the priorities of one or more
build-time dependencies). In
order to ensure this, the priorities of one or more packages may
need to be adjusted.
Either libdc1394-22 should be assigned priority optional, or its
reverse dependencies should be priority extra.
On Tue, Dec 10, 2013 at 11:33:52AM +0100, IOhannes m zmoelnig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
hi,
On 2013-10-28 22:08, Sebastian Ramacher wrote:
pd-iemambi fails to build on kfreebsd-* with: | /usr/bin/make -C
src CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -Wall CXXFLAGS=-g -O2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-10-30 15:12, Sebastian Ramacher wrote:
could anybody please confirm that it pd-iemambi does (not) build
on their kfreebsd-* systems?
I confirmed the build failure on fischer.d.o. Note that
/usr/include/machine/endian.h guards the
Package: grub-efi-amd64
Followup-For: Bug #720513
Dear Maintainer,
seems my problem somehow got solved, though i'm sure that i don't know why and
how.
yesterday i noticed that there are new grub-efi packages (2.00-18) so i
installed them.
before rebooting i checked `efibootmgr` and
Package: grub-efi-amd64
Version: 2.00-17
Severity: grave
Justification: renders package unusable
i'm running on a Lenovo S205 laptop that has both both Debian and W7 installed.
i'm booting via EFI.
today i upgraded grub vom 2.00-15 to 2.00-17.
after a reboot, grub stopped in 'rescue' mode.
my
Package: binutils-mingw-w64-i686
Version: 2.22-8+2+b1
Severity: serious
File: binutils-mingw-w64-i686
Justification: Policy 7.6
Dear Maintainer,
binutils-mingw-w64-i686 currently fails to install on a system where
binutils_2.23.52.20130612-1 is already installed, because both packages
seem to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-03 14:26, Moritz Muehlenhoff wrote:
On Fri, Mar 01, 2013 at 04:08:18PM -0800, Russ Allbery wrote:
At this point in the release process, I really think upgrading
with _FORTIFY_SOURCE disabled is the correct fix. Just
increasing a buffer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-28 06:44, Matthew Grant wrote:
Talk to upstream before turning on _FORTIFY_SOURCE please.
i double-checked and tried to run a fairly big patch and couldn't
reproduce the crash.
do you think you could produce a minimal patch showing
Package: flumotion
Version: 0.6.1-1.2
Followup-For: Bug #660553
seems to be a problem with the used python version
in wheey, python is python2.7
flumotion seems to require at most python2.6
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'),
)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
Content-Type: multipart/mixed; boundary9131115279258261871==
MIME-Version: 1.0
From: IOhannes m zmoelnig zmoel...@iem.at
To: Debian Bug Tracking
9e1930555261fc417473ceaefb870aec7e3bb770 Mon Sep 17 00:00:00 2001
From: IOhannes m zmoelnig zmoel...@umlauto.umlaeute.mur.at
Date: Sun, 8 Jan 2012 19:48:01 +0100
Subject: [PATCH] Only remove assets from gem-doc if it's there (Closes:
#655048)
on the buildbots, binary:all packages are not built, so there is no debian/gem-doc
-- no debconf information
From 0de66305925cfb86813c465bf9756799f3de4eaf Mon Sep 17 00:00:00 2001
From: IOhannes m zmoelnig zmoel...@umlauto.umlaeute.mur.at
Date: Sun, 8 Jan 2012 19:48:01 +0100
Subject: [PATCH] Only remove assets from gem-doc if it's there (Closes:
#655048)
on the buildbots, binary:all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-21 16:23, Adrian Knoth wrote:
On 11/19/11 00:48, Mònica Ramírez Arceda wrote:
Hi!
tags 643413 +patch
thanks
IOhannes: did you try to forward it to upstream? The patch header
doesn't mention anything related.
good question.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-24 06:58, Adrian Knoth wrote:
This is clearly a local issue, I'm running the same software without
problems.
Question is why.
iirc, this is a follow-up bug from puredata #645040, where puredata
works with alsa if you turn off
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-27 14:22, Didier Raboud wrote:
cc1plus: some warnings being treated as errors
make[3]: *** [tools/assimp_cmd/CMakeFiles/assimp_cmd.dir/WriteDumb.cpp.o]
Error 1
The full build log is available from:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-27 14:36, Didier Raboud wrote:
This happened because since dpkg 1.16.0 [0], hardening flags are enabled
under various conditions.
thanks for your bugreport.
a new upstream release is available that has this problem fixed.
i have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-06-08 17:19, Didier Raboud wrote:
Source: pd-bassemu
Version: 0.3-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110607 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all
On 2010-09-29 20:47, Julien Cristau wrote:
On Sun, Jul 25, 2010 at 18:19:02 +0200, Laurent Bonnaud wrote:
On Sun, 2010-07-25 at 15:08 +0200, Guus Sliepen wrote:
Can you provide me with a backtrace (using gdb, with the bt full command)
when it does crash?
I will not be able to do so until
Package: coriander
Version: 2.0.0-4
Severity: normal
i can confirm that coriander is currently unusable.
everytime i start coriander, i get a segmentation fault:
snip
Starting program: /usr/bin/coriander
[Thread
On 2010-06-22 12:23, Guus Sliepen wrote:
On Tue, Jun 22, 2010 at 10:11:23AM +0200, IOhannes m zmoelnig wrote:
i can confirm that coriander is currently unusable.
everytime i start coriander, i get a segmentation fault:
[...]
this is on i386 running 2.6.32-3.686 (default debian; JuJu-stack
Package: nvidia-kernel-legacy-96xx-source
Version: 96.43.16-1
Severity: normal
i can confirm that with the patch provided in #574476 the build problem goes
away.
fgmasdr
IOhannes
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500,
Andreas Henriksson wrote:
On mån, 2008-09-01 at 21:06 +0200, Thomas Viehmann wrote:
- gem: multiple RC bugs with NMU proposal without comment for more
than
two months, but also seems in bad shape from looking at the
non-RC bugs: a segfault unsanswered by the maintainer for
IOhannes m zmoelnig wrote:
Andreas Henriksson wrote:
On mån, 2008-09-01 at 21:06 +0200, Thomas Viehmann wrote:
- gem: multiple RC bugs with NMU proposal without comment for more
than
two months, but also seems in bad shape from looking at the
non-RC bugs: a segfault unsanswered
Andreas Jochens wrote:
Package: gem
Version: 1:0.90.0-18
Severity: serious
Tags: patch
When building 'gem' in a clean unstable chroot,
I get the following error:
[...]
With the attached patch which removes xlibmesa-glu-dev from the Build-Depends
'gem' can be built on unstable.
but your
Package: oftpd
Version: 20040304-1
Severity: grave
Justification: renders package unusable
oftpd is exposed to a Denial-of-Service attack, as described in
http://www.time-travellers.org/oftpd/oftpd-dos.html
the solution is to upgrade to 0.3.7
i think this has been fixed in woody (oftpd-0.3.6-6
Guenter Geiger wrote:
Hi,
Thanks for the patch. I am fighting with a changed API for ffmpeg on
unstable though. Did you compile on testing ?
for quicktime, neither quicktime/quicktime.h nor lqt/quicktime.h
should be included but plain quicktime.h (and the full include-path
returned by
55 matches
Mail list logo
