Control: owner -1 John Scott
Control: tags -1 pending
I made a boo boo. An explanation and fix will be ready shortly
signature.asc
Description: This is a digitally signed message part
Control: tags -1 fixed-upstream
Control: block -1 by 1010735
I think this is fixed upstream. Apparently they were made aware that this
particular failing test just takes a long time, but if you give it a couple
minutes it does pass.
signature.asc
Description: This is a digitally signed
Control: forwarded -1
https://github.com/xournalpp/xournalpp/commit/9172ee831f4dfbb88dfeb13b66862e80e64a0d3f
Control: tags -1 fixed-upstream
It looks like this has been fixed upstream, so I'm setting the bug metadata as
such.
signature.asc
Description: This is a digitally signed message part
Hi,
I'm doing the build right now and it got past the part where it's been failing,
so I'm pretty sure we're good!
Adrian, would you be willing to sponsor my upload? I'll send a second mail when
it's ready. The change is extremely small, and to be frank I'll probably skip
running the test
Hi,
I see from previous mails that Blender upstream has decided not to support
32-bit architectures anymore. This is a friendly ping that the maintainer will
request its removal so it may migrate into Bookworm.
Thanks,
John
signature.asc
Description: This is a digitally signed message part
The fix is currently waiting in the NEW queue.
signature.asc
Description: This is a digitally signed message part
On Thu, 2021-09-30 at 09:18 -0400, John Scott wrote:
> Outside a minimal chroot, on my desktop system, zbarimg seems to
> process SVGs just fine. So this may be a case of a Recommends
> (somewhere) not being installed wreaking havok, but in my opinion
> zbarimg should still not beh
Control: reassign -1 zbar-tools
Control: notfound -1 zint/2.10.0-1
Control: owner -1 !
I think I've partially identified what is happening.
It turns out that the version of zint in testing, despite being passed
the --filetype=SVG flag, actually produces a PNG, which in the past has
been happily
On Sun, 2021-08-22 at 13:43 -0400, Taowa wrote:
> I'm planning on doing an upload this week to fix it- ideally today.
Do you still got this, Taowa?
signature.asc
Description: This is a digitally signed message part
Hey Matthias,
> checking for library containing inet_pton... none required
> checking for library containing socket... none required
> checking for GNU libc compatible malloc... yes
> configure: error: cannot run /bin/sh ./config.sub
Can you double-check this/run a rebuild and see if it was a
On Wed, 09 Jun 2021 00:32:02 + John Scott
wrote:
> I believe it's in the best interest of Debian users that this bug be
> downgraded for Bullseye so Sage can be used in the mostly-wholesome
> shape it's in, but since I lack expertise in maintaining it I too
> will leave this to
On Tue, 08 Jun 2021 17:15:44 +0200 Julien Puydt wrote:
> I've been convinced that getting a fragile sagemath in next stable
> wouldn't be a good thing.
You've put much more effort than I have into maintaining scientific
software in Debian, so I respect your opinion, but is it really
accurate to
Has anyone been able to reproduce this? Attempting to build Sage in a
fresh unstable environment succeeds for me; perhaps the build failure
was spurious.
signature.asc
Description: This is a digitally signed message part
On Wed, 10 Feb 2021 21:02:47 +0100 Bertrand Marc
wrote:
> Indeed, the original issue reported in this bug was fixed in 1.11-1.
> However, the general issue of flaky tests is still there:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libextractor.html
>
> Would you
According to upstream, the fix for this should've been included in the 1.11-1
upload. Can this issue be closed?
signature.asc
Description: This is a digitally signed message part.
Control: tags -1 patch fixed-upstream
Control: forwarded -1 https://github.com/Cisco-Talos/clamav-devel/commit/18306
I found that the build succeeds with the upstream patch. It seems like
ck_assert_msg() was missing an argument.
signature.asc
Description: This is a digitally signed message part.
To fix this on amd64 it's sufficient to add libopenexr-dev as a build-dep.
signature.asc
Description: This is a digitally signed message part.
On Thursday, October 29, 2020 9:08:12 AM EST Julian Andres Klode wrote:
> My suggestion is to set XB-Important: yes and Protected: yes on
> libgcc-s1 such that people cannot easily remove it after it's installed.
This has migrated to testing and is having an unexpected consequence for me:
>
On Thursday, August 6, 2020 6:38:33 PM EDT Ralph Giles wrote:
> I wanted to request approval from the maintainer team to upload the
> acmetool 0.2.1-2 package currently in testing/unstable to buster-
> backports.
>
> The version currently in buster (0.0.63) only supports the deprecated
> ACME v1
Control: tags -1 - fixed-upstream
On Wednesday, September 2, 2020 8:02:42 AM EDT Dmitry Shachnev wrote:
> My guess is that we need this patch (not applied upstream yet)
Thanks for the pointer, that patch applies cleanly and fixes the issue.
> But that bug (QTBUG-81313) is already fixed in Qt
Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-81313
Control: tags -1 upstream fixed-upstream
It turns out it is a clash both with Chromium (powers Qt WebEngine) and glibc.
Check out the Red Hat bugs
https://bugzilla.redhat.com/show_bug.cgi?id=1812482 (Qt)
Control: unblock -1 by 937695 937569
Control: block 937695 by -1
Control: block 937569 by -1
Control: merge -1 936632
> I have reached out to the gnumeric folks; they say a new version
> including python3 support should be out in a couple of months.
Thanks! Your citing the removal from Debian
Python 3 doesn't include hotshot, so the hotshot2calltree script should be
dropped. Upstream still includes it but it doesn't appear to have seen any
maintenance:
https://invent.kde.org/sdk/kcachegrind/-/tree/master/converters
signature.asc
Description: This is a digitally signed message part.
On Wednesday, September 11, 2019 4:03:59 AM EDT Chris Lamb wrote:
> I just ACCEPTed minder from NEW but noticed it was missing attribution
> for at least Tomáš Mráz.
This bug is against crypto-policies, but it appears you accepted minder too
the same day. Did you mean to file this against
Control: forwarded -1
https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html
Control: tags -1 fixed-upstream
> Hello,
>
> Le jeu. 4 juin 2020 à 18:43, John Scott a écrit :
> > I'm not the maintainer, just a prospective user taking a look, but Frama-C
Control: tags -1 help
Control: owner -1 jsc...@posteo.net
Hi,
I've been quiet on this important package for a little while and ought to give
an update, if nothing else to assure I've not bailed :).
Recently I've been taking time to get acquainted with the tools, like gbp and
friends, for a
Control: reassign 960614 src:normaliz,src:e-antic
Control: forcemerge -1 960614
See bug #960614, not only the test fails but normaliz is unusable as
installed.
signature.asc
Description: This is a digitally signed message part.
On Sat, 25 Apr 2020 21:40:14 -0400 FeRD wrote:
> If Debian maintains JUCE as a distro package, and it would be a compatible
> alternative to our JUCE-based "libopenshot-audio", I don't see any reason we
> can't add an option to libopenshot's CMake configuration that tells it to
> just
> use those
On Mon, 11 May 2020 19:57:52 +0900 Norbert Preining
wrote:
> Uploading in the a few minutes, after the binary build succeeded.
Just a ping in case you've moved on
signature.asc
Description: This is a digitally signed message part.
On Tuesday, April 28, 2020 2:16:11 AM EDT hikaru.deb...@web.de wrote:
> I'm sorry, but my Cubieboard is currently at my workplace, to which I have
no access. I'll try to get clearance to pick it up, but I can't promise if or
when that will be possible.
It's not urgent, I wanted to ensure that
On Mon, 4 Feb 2019 19:00:59 +0100 hikaru.deb...@web.de wrote:
> So I'd conclude this problem is specific to the Stretch/arm* architectures.
Thanks. This bug looks like #909498. That was also reported on Stretch with a
Raspberry Pi. Can you still reproduce it?
Also look at #949834, but both
Control: forcemerge 948708 -1
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1609535
Hi,
This looks like #948708 which indicates this might've been fixed in 68.5.0.
Could you upgrade if you haven't already and see if it crashes again?
signature.asc
Description: This is a
On Fri, 24 Apr 2020 23:33:59 -0400 FeRD wrote:
> Sorry, I realized I might have sent this reply to the wrong bug.
Yes, I sent my mail to both of the bugs (am doing now again, I guess). I am
also making noise :)
> What version of libopenshot is that result from? The Clang namespacing was
> fixed
Control: block 925754 by 925755
Control: notforwarded 925754
Control: forwarded 925755
https://github.com/OpenShot/libopenshot-audio/issues/33
Hi,
> On Wed, 29 Jan 2020 10:08:55 +0100 Matthias Klose wrote:
> > libopenshot-audio 0.1.8 still fails to build
>
> Quite right, sorry.
Control: forwarded -1 https://github.com/OpenShot/openshot-qt/issues/2237
Control: forwarded 925754
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754
Control: tags 925754 + fixed-upstream ftbfs
Hi,
> Version: 1:2.4.4-dmo4
OpenShot 2.4.4 isn't part of Debian yet. It seems you've probably
> thank you!
>
> I updated the package.
Hi,
I see you've fixed this upstream. firmware-ath9k-htc has been removed from
Bullseye, could you use some help with a new Debian package?
signature.asc
Description: This is a digitally signed message part.
This is caused by GLib => 2.58 which was uploaded in September 2018 long ago.
Likewise, libsignon-glib 1.12 lags behind upstream substantially.
It's 2.1 and the disparity causes the patch to not apply.
A cheap workaround might be to add a -Wno-error like is already done for
some other deprecated
I have now prepared merge requests for fixing ktp-common-internals,
ktp-accounts-kcm,
and kaccounts-providers respectively [1] [2] [3]. These issues are all fixed in
new upstream releases, but I am not comfortable with such an undertaking and
hope these fixes will suffice in the meantime.
[1]
On February 23, 2020 3:11:46 PM EST, Marco Bodrato
wrote:
>Ciao,
>
>Il Dom, 9 Febbraio 2020 9:34 pm, Steven Robbins ha scritto:
>> On Sunday, February 9, 2020 9:54:02 A.M. CST Marco Bodrato wrote:
>>> So, if the new release of the library is able to answer that the number
>>> 387047 is
Hello,
pax.jar seems to exist in version 2019.20191208-1 as well. If someone could
affirm this is not an issue introduced with the new upload, could one set this
bug as being found in 2019.20191208-1? This would enable the transition to
testing.
signature.asc
Description: This is a digitally
Control: forwarded -1 https://phabricator.kde.org/D25269
Control: tags -1 fixed-upstream patch
Control: reassign 949238 src:ktp-common-internals
Control: reassign 949239 src:ktp-common-internals
Control: forcemerge -1 949238 949239
Control: affects -1 + src:ktp-text-ui
Control: affects -1 +
Control: forwarded -1
https://cgit.kde.org/kaccounts-providers.git/commit/?id=fd6b3ebf
Control: tags -1 patch fixed-upstream
This was caused by the newer version of Qt and builds with the patch.
signature.asc
Description: This is a digitally signed message part.
Control: forwarded 949237 https://phabricator.kde.org/D25370
Control: tags 949237 patch fixed-upstream
This was caused by the new telepathy-qt and the patch suffices for it to build
on my system. #949239 in ktp-contacts-runner looks to be the same issue, but
its git log is much less
> Yes, it still crashes after opening any of images and trying to edit it or
> just usin program GUI.
If you had sent mail to the bug report before, it seems you're using a
different email address now and I don't know if you have sent any debugging
information before. Regardless, the following
Control: forwarded -1 https://github.com/emscripten-core/emscripten/issues/5488
Control
> The problem is that emscripten uses a fork of LLVM and I am reluctant to add
> yet-a-new-version of llvm in the archive...
> I have been waiting for the changes to be merged upstream and, with the
> recent
Control: forwarded -1 https://github.com/emscripten-core/emscripten/issues/5950
Control: tags -1 fixed-upstream
It appears it still supports Python 2 also for the time being
https://github.com/emscripten-core/emscripten/issues/7198
signature.asc
Description: This is a digitally signed message
Control: forwarded -1 https://github.com/emscripten-core/emscripten/issues/10146
Control: block 939477 by -1
I've reported this upstream since they're still using it.
signature.asc
Description: This is a digitally signed message part.
Control: forwarded -1
https://salsa.debian.org/qt-kde-team/kde/khotkeys/merge_requests/2
Control: tags -1 patch
This is fixed in KHotKeys 5.15.1. Alternatively, I've submitted a merge request
to enable a potential new upload of 5.14.5 with the patch.
signature.asc
Description: This is a
Control: tags -1 fixed-upstream
The package builds with the following two commits applied in order:
https://cgit.kde.org/khotkeys.git/diff/?id=67fd8f06
https://cgit.kde.org/khotkeys.git/diff/?id=ae574373
The former one makes many changes, but appears to be related only due to
removing a blank
Hello,
> Same situation here with openshot 2.4.4 from debian sid. I have an intel
gpu.
OpenShot 2.4.4 isn't in Debian Sid yet. Where did you install it from?
signature.asc
Description: This is a digitally signed message part.
Are you still able to reproduce this bug? In your logs I noticed the following
> Debian Release: bullseye/sid
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'),
> (110, 'unstable')>
> Architecture: amd64 (x86_64)
It looks like you have a
Control: tags -1 fixed-upstream
I think this is fixed upstream. I found these commits that seem to be related:
https://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git/commit/?id=05755b29
https://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git/commit/?id=96eda741
Control: tags -1 fixed-upstream
It looks like the current releases use Python 3 for svgtoipe now
https://github.com/otfried/ipe-tools/commit/60ccc014
signature.asc
Description: This is a digitally signed message part.
This bug has been open for a while and blocks Pinta getting into Debian
Bullseye. Can you confirm whether or not you can still reproduce this issue?
signature.asc
Description: This is a digitally signed message part.
Control: forwarded -1 https://github.com/LibreCAD/LibreCAD/pull/
Control: tags -1 upstream fixed-upstream ftbfs
This has been fixed upstream. The change is at
https://github.com/shawncurry/LibreCAD/commit/3bc93383
signature.asc
Description: This is a digitally signed message part.
Has anyone been working on this?
signature.asc
Description: This is a digitally signed message part.
e bug. However, I hope my suggestions are
helpful for you and that I'll be able to help Falcon in this way.
Sincerely,
John Scott
signature.asc
Description: This is a digitally signed message part.
Control: reassign -1 android-libboringssl/8.1.0+r23-1
Control: tags -1 upstream patch fixed-upstream
Control: retitle -1 adb crashes on startup with SIGBUS (armhf)
Control: forwarded -1
https://boringssl.googlesource.com/boringssl/+/672f6fc2486745d0cabc3aaeb4e0a3cd13b37b12%5E%21/
Control:
On Wed, 16 Oct 2019 10:00:15 + Georges Khaznadar
wrote:
> Source: falkon
> Source-Version: 3.1.0+dfsg1-4
>
> We believe that the bug you reported is fixed in the latest version of
> falkon, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this
Control: tags -1 patch
Merge request with fix at https://github.com/rhboot/shim/pull/170
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=401306
This appears to have been fixed upstream. There are a couple patches there.
ktp-contact-list has been kept out of testing for over a year, though this
issue is fixed by the patch and new upstream version. If help is wanted with
this, please let it be known.
On Mon, 14 Oct 2019 16:05:04 +0200 Thomas Goirand wrote:
> it wont change the fact that Python2 is being removed from Bullseye
because it's dead upstream on the 1st of January next year.
That's not a fact, Bullseye can still ship with Python 2 if needed
Control: block -1 by 933021
The FTBFS / 22,979 test failures are due to #933021, and until it's fixed I
don't think it can be determined whether libreadline8 might cause them too.
signature.asc
Description: This is a digitally signed message part.
Control: severity -1 important
Control: found -1 0.75-1
Could you be using Wayland by any chance, like with GNOME 3? For me,
mate-panel crashes there regardless of applets used. Since the applet works
fine for me, I hope you don't mind that I reduce the bug severity.
I suggest that you try
Package: etherape
Version: 0.9.16-1
Followup-For: Bug #894313
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I am able to reproduce this issue, but installing libgnomeui-0
(which provides libgnome.so) fixes it for me. Like the upstream
report suggests, this looks like a missing dependency.
-
Package: linuxbrew-wrapper
Version: 20170516-2
Severity: serious
Justification: Policy 2.2.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Though the linuxbrew-wrapper package is free just as Linuxbrew is, Linuxbrew
does not commit to only free software. Linuxbrew's OpenCV formula builds with
Package: xmoto
Version: 0.5.11+dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I've noticed that in package version 0.5.11+dfsg-3, text, both during
gameplay and in the menus, does nor show and makes the game completely
unplayable. Downgrading to
68 matches
Mail list logo
