Control: tags -1 patch
Merge request with fix at https://github.com/rhboot/shim/pull/170
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: 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:
Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-rele...@lists.debian.org, n...@sonic.net
Control: block 934976 by -1
The maintainer and author acknowledges that the game uses Bill Gates's
likeness and likely non-free audio samples from the Defender arcade game
and requests that it
Control: tags -1 fixed-upstream
I haven't been able to narrow it down to any particular release, but it
appears that Solaar does support Python 3. See this issue adding support for
Python 3.7 filed by the Fedora maintainer:
https://github.com/pwr-Solaar/Solaar/issues/447
And it looks to work
Control: tags -1 - moreinfo
> There are rdepends that need to be addressed first:
>
> Checking reverse dependencies...
> # Broken Depends:
> open-font-design-toolkit: open-font-design-toolkit
That doesn't look right; that's the same package. Is this a mistake?
signature.asc
Description: This
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: tags -1 upstream
I'm not running KMail 19.08 at the moment so I can't check for sure, but this
commit seems to suggest it's merely hidden by default now.
https://cgit.kde.org/kmail.git/commit/?id=d055c1bb
signature.asc
Description: This is a digitally signed message part.
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=248807
Control: tags -1 patch fixed-upstream
Patch is at https://cgit.kde.org/drkonqi.git/commit/?id=c07434bf
signature.asc
Description: This is a digitally signed message part.
wxMaxima FTBFS's for me with
$ pdf-engine /usr/bin/xelatex not known
I see that the 19.10.0 Debian package builds now by skipping the PDF manual
when it can't be built. I think I've found the root of the problem with
Pandoc.
It turns out this is a regression that's been there for ages and
On Thu, 11 Apr 2019 11:30:43 -0400 Nicholas D Steeves
wrote:
> I wonder if that package fulfills this RFP? If not, and if this bug
> remains inactive for a month, please ping me and I'll take a look.
Ping :)
signature.asc
Description: This is a digitally signed message part.
> Started kmail on wayland-plasma with active preview pane. The preview stays
> black at the beginning. When e.g. hovering with the mouse over the preview,
Do you see a black rectangle like in the image I've attached? That is
https://bugs.kde.org/show_bug.cgi?id=397825 . If not, try to get a
On Sat, 14 Dec 2019 22:55:17 +0100 Aurélien COUDERC
wrote:
> Would you have the possibility to test again and comment here with more
> information if the crash is still reproducible ?
Sure, I've attached a backtrace done with 'bt full' on the older version that
looks more comprehensible. I've
Source: opensc
Version: 0.19.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In the package descriptions OpenSC warns
Before purchasing any cards, please read carefully documentation in
/usr/share/doc/opensc/html/wiki/index.html
As best as I can tell, this file isn't
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.
An easy way to reproduce it is by rapidly clicking the button while pressing
escape to close the menu. I've attached a comprehensive backtrace. Help finding
whatever package has the debugging symbols for /usr/lib/x86_64-linux-gnu/
libgstvideo-1.0.so.0.1404.0 would be appreciated.Application:
Control: tags -1 patch
They have a two line patch that fixes this upstream
https://phabricator.kde.org/D21801
signature.asc
Description: This is a digitally signed message part.
Package: drkonqi
Version: 5.14.5-1
Severity: minor
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have tried to report a bug in Kamoso just now, but unfortunately my
backtrace is so huge Dr. Konqi doesn't like it. At 'Sending the Crash Report'
it says
Error sending the crash
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
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: 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.
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.
Control: tags -1 fixed-upstream
MyPaint has released their first 2.0 beta with Python 3 support. The
announcement suggests it's stable and it could use testing to find any
remaining bugs.
See https://github.com/mypaint/mypaint/releases/tag/v2.0.0-beta.0
signature.asc
Description: This is a
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
Has anyone been working on this?
signature.asc
Description: This is a digitally signed message part.
It appears that bugs haven't been filed to get reverse dependencies depending
on version 1 out of testing.
Britney [1] says
> trying: prompt-toolkit
> skipped: prompt-toolkit (39, 2, 91)
>
> got: 26+0: a-1:a-0:a-0:a-0:i-17:m-0:m-7:p-0:s-1
> * mipsel: caffe-cpu, python3-caffe-cpu,
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]
Source: kinfocenter
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The Samba status monitor dialog is blank and says
Error run smbstatus: execve: No such file or directory
As the samba package description points out, Samba users need not have this
package installed, so at
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
> > If there really is a problem with those files I would appreciate your
> > letting me know what I missed. Otherwise I hope you can avoid the
> > repacking trouble in the future.
> Probably not, but the repacking is not trouble.
Without a good reason, you really shouldn't repack [1]. I do not
Package: kaddressbook
Version: 4:19.08.3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Filing against KAddressBook for now since I don't know what broke.
Steps to reproduce:
1) do `nc -l -p 1999` to start a dummy LDAP server
2) in KAddressBook, go to Settings -> Configure
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
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.
On the off-chance they're relevant and Jmol is a red herring, I'm re-sending
my misplaced comments [1] about relevant parts of /usr/bin/sage here:
> By the way, looking at the header of that file I see
> # workaround #892622; unfortunately we can't simply run setarch -R when
> running Singular
The live images include firmware-ath9k-htc now, see #934522.
By the way, being unaware of this bug at the time I filed #900171, that
firmware-free should recommend firmware-ath9k-htc. This reflects the logical
relationship better, but it's a trivial difference and I wonder which would be
It appears Teeworlds has been using Python 3 for at least the past year:
https://github.com/teeworlds/teeworlds/commit/9bd2a2d98681add573e7e356eef361fde2ccd082
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
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
Source: kalzium
Severity: normal
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=416856
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I haven't narrowed down in what version this changed, but in Kalzium the
Molecular Editor button appears to be greyed out on the toolbar. Invoking
Package: sagemath-common
Version: 9.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On upgrading to the new version in Buster, I've gotten these warnings during
installation:
Setting up sagemath-common (9.0-1) ...
This still affects 19.08.2, but strangely doesn't affect Falkon.
I see Falkon depends on libssl1.1 but Konqueror doesn't. Could that be what
makes the difference?
signature.asc
Description: This is a digitally signed message part.
> I am not a Debian Developer (DD). This needs a DD to be uploaded to
> packages.debian.org.
If you are still looking for someone that can upload this for you, file a bug
against sponsorship-requests and block this bug by that one.
On Thu, 16 Jan 2020 17:36:21 +0100 Julien Puydt
wrote:
> I fixed the brial package which was the culprit for the missing
> symbols, and can confirm that what is needed is only :
>
> modify env.py so SAGE_SCRIPTS_DIR points to /usr/share/sagemath/bin
If SAGE_SCRIPTS_DIR were set to that
Package: sagemath-common
Version: 8.9-3
Severity: normal
Control: affects -1 cantor-backend-sage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I previously reported this as #923166 and it was fixed in 8.6-6. It seems
it's come back: sage -v says
/usr/bin/sage: line 16:
By the way, looking at the header of that file I see
# workaround #892622; unfortunately we can't simply run setarch -R when
running Singular
# because src/sage/libs/singular/singular.pyx loads libsingular.so into the
current process
if [ "$(arch)" = "mips64" -a -z "$SAGE_DEB_MIPS64_WORKAROUND"
On Thu, 2 Jan 2020 15:46:53 + Julian Gilbey wrote:
> > I'm using Anki w/ Plasma on Bullseye, and Ctrl+Enter works as expected on
> > both X11 and Wayland. So this does seem Buster-specific.
> Thanks John, that's really helpful to know. Are you using KDE?
Plasma is the name of KDE's desktop
On Thu, 02 Jan 2020 19:25:39 +0530 ra...@amaram.name wrote:
> It might be worth checking out in bullseye if the problem exists as well.
I'm using Anki w/ Plasma on Bullseye, and Ctrl+Enter works as expected on both
X11 and Wayland. So this does seem Buster-specific.
signature.asc
Description:
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
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-CC: debian-qt-...@lists.debian.org, he...@debian.org
Please remove Blogilo from unstable. It's been broken since Oct. 2018 when it
couldn't be built for a KDE PIM transition and its dependencies are
Control: reassign -1 ftp.debian.org
On Friday, January 3, 2020 4:20:00 PM EST you wrote:
> Unstable, or testing? The former is FTP team's balliwick, not Release.
Unstable. Thanks for the quick catch!
signature.asc
Description: This is a digitally signed message part.
>> If you still need me to test with different desktop environments: which o ne
>> would you suggest? I'd prefer one that is easy to install AND remove after
>> the test.
> I don't know other wayland-based desktops than gnome, so I leave this
> question to others :)
It's not easy to add or remove
Control: unblock -1 885677
Control: forwarded -1 https://github.com/coq/coq/pull/9279
Control: tags -1 fixed-upstream
Unfortunately CoqIDE wasn't rebuilt for Buster. CoqIDE 8.10 supports lablgtk3
though so it can be reintroduced
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
Control: reassign 935141 libwxgtk3.0-0v5 3.0.4+dfsg-8
Control: affects 935141 wxmaxima
It appears that my trouble with wxMaxima is probably fixed in wxWidgets 3.1.2
and I'd like to give it a try.
> It's not ABI stable, so it's just not suitable for packaging. Every new
> 3.1.x release would
Control: tags -1 moreinfo
I've upgraded to Bullseye and I'm still able to reproduce it. I've attached
new backtraces: one from gdb and a longer one from Dr. Konqi#0 0x7fffdf974af3 in linear_to_ytiled (mem_copy_align16=,
mem_copy=, swizzle_bit=,
src_pitch=,
src=0x7fffe02dbb90
The package is in great shape. The only challenge to getting the package in
the archive seems to be the copyright file. Coreboot's README says
> Some files are licensed under the "GPL (version 2, or any later version)",
> and some files are licensed under the "GPL, version 2". For some parts,
>
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://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
I'm not a DD and can't sponsor packages, but I hope my feedback can be helpful
for you.
I see Lutris bundles python-distro. This is available in Debian, so the
package should use it rather than installing a bundled copy. Debian's
Winetricks should be used also.
Since Winetricks is in contrib,
> 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
> 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.
> dima@fatty:~$ sudo apt install /tmp/gnuplot-data_5.2.8+dfsg1-2dima1_all.deb
> ...
> Note, selecting 'gnuplot-data' instead of
> '/tmp/gnuplot-data_5.2.8+dfsg1-2dima1_all.deb'
>
> So apt recognized that I asked it to install a file on disk, but
> instead of using that file, it decided to
Package: okular
Version: 4:19.12.3-2
Severity: normal
Tags: a11y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As remarked on this blog post [1] that tremendously helped me, Okular doesn't
complain if you try using the text-to-speech features without the necessary
libraries installed. It only
Just a random thought: maybe it has to do with Buster using LVM2 by default.
I'm reproducing this on a system installed as Buster also
Control: affects -1 python3-sagetex
Upgrading to 9.0-3 and installing SageTeX says
Setting up python3-sagetex (3.4+ds-1) ...
/usr/lib/python3/dist-packages/sagetexparse.py:135: SyntaxWarning: "is not"
with a literal. Did you mean "!="?
if t.format is not '':
signature.asc
Description: This
Control: fixed -1 22~exp1
It builds with gcc 9 now, but deferring to leave this bug open since it's in
experimental and not on its way to Bullseye yet.
signature.asc
Description: This is a digitally signed message part.
Control: reassign -1 src:qtwebengine-opensource-src
Control: affects -1 konqueror kaccounts-config
I've now noticed this appears to affect kaccounts-config also. I'm still
unable to identify the specific cause of the bug, but my attempts to get
at it with gdb indicate the culprit is probably Qt
Package: libreoffice-common
Version: 1:6.4.1-1
Severity: minor
User: pkg-apparmor-t...@lists.alioth.debian.org
Usertags: buggy-profile
Control: affects -1 gpg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The AppArmor profile doesn't allow reading GnuPG's tofu.db:
apparmor="DENIED"
Package: libreoffice
Version: 1:6.4.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Unlike #955271 which I just filed about digital signing, this issue doesn't
seem to arise out of the AppArmor profile.
1. Open LibreOffice and navigate to File -> Digital Signatures -> Sign
Control: reassign -1 kleopatra
Control: affects -1 kmail
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=363309
Hello,
I too would like to see KMail describe the information. I couldn't find a
KMail-specific upstream bug, but found a Kleopatra bug about it which
would probably fix it
Hi,
Are you saying that the mail isn't fetched automatically, but manual syncing
works okay?
By chance, does it seem to ask for your password when KMail would normally
remember others, or does it prompt an excessive number of times?
https://bugs.kde.org/show_bug.cgi?id=393002
signature.asc
Package: vim-editorconfig
Version: 0.3.3+dfsg-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I see in #851572 the dependency was added on vim-nox, but it appears to me
that this was done out of an abundance of caution. Caution is good, but I
mean to point out that the
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 -1 by 954861
> If no one dissents I'll try to get a fix landed there soon, at least in the
> Debian package first.
Sorry for the noise, I take this back. This may be a bug in wpa_supplicant
just fixed upstream: it has trouble with devices such that their names are the
maximum of
Control: owner -1 !
I've posted this with details on the GitHub issue [1], but it happens that
wpa_supplicant/nm upstream ships a file that specifically blacklists drivers
that don't work with NetworkManager's MAC randomization exactly as the
proposed 'workaround' here does.
The bug even
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.
Package: lynis
Version: 1.6.3-1
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Thanks for revamping the package. It provides a systemd service and timer at
/usr/share/lynis/extras/systemd/lynis.service/timer. The header of the former
reads
# Lynis service file for systemd
Package: gnuradio
Version: 3.7.11-3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
GNU Radio currently recommends python3-qwt-qt5—and recommended python-qwt-qt5
before that—but these packages have never existed as best as I can tell.
It had the '3' appended at [1], but
Source: scribus
Version: 1.5.1+dfsg-2
Severity: normal
Control: affects -1 src:scribus-doc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
scribus suggests scribus-ng-doc. This doesn't seem right and the matching
1.5.* version is only in experimental. scribus-doc isn't 1.5.* however.
Package: gnuradio
Version: 3.8.0.0-5
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I noticed libcanberra-gtk-module and libcanberra-gtk3-module were added to
gnuradio's dependencies for #921377, checking what packages installed depend
on GTK+ 2.
That user was using
Package: flashrom
Version: 1.2-5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It seems this is because I use my system with Secure Boot, so Lockdown
mode is enabled by default, but in principle I think it could be enabled by
anyone (maybe it's used by SELinux users as well)
Package: libqt5texttospeech5
Version: 5.12.5-1
Severity: normal
Tags: a11y
Control: block 955762 by -1
Control: tags 955762 - patch
Hi,
I filed #955762 on Okular because if one doesn't have at least one of
qtspeech5-flite-plugin or qtspeech5-speechd-plugin installed, the only error
it prints is
Package: apparmor-profiles-extra
Version: 1.27
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
An experimental freshclam profile is provided at
/usr/share/apparmor/extra-profiles/usr.bin.freshclam, but clamav-freshclam
provides its own more recent one in enforce mode at
Control: owner -1 !
Control: retitle -1 ITP: webext-librejs -- browser plugin to block non-free JS
I'm starting to work on this. When it starts taking shape, I hope it will be
welcome with the Web/MozExt team.
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.
> The package will be maintained with in the Debian GIS team where it will
> eventually replace the josm package.
Because this package will need to go in contrib or non-free, does this mean
JOSM will be removed from main? I think that is a substantial trade-off to
provide new backports. Could
Control: forwarded -1 https://bugzilla.samba.org/show_bug.cgi?id=13917
Control: tags -1 + upstream fixed-upstream
Control: fixed -1 2:4.11.0+dfsg-1
Control: affects -1 samba-common-bin
This was fixed upstream and they did apply the fix to Samba 4.9. I'm leaving
this bug open to assess whether it
Package: kde-telepathy-text-ui
Version: 17.08.3-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Searching 'Plugins' from the application menu one finds
/usr/share/applications/kcm_ktp_chat_messages.desktop which has
Exec=kcmshell4 kcm_ktp_message_filters
and kcmshell4
Control: tags -1 + upstream
On Tuesday, May 5, 2020 7:07:39 AM EDT Gürkan Myczko wrote:
> The error message:
> ERROR: Could not get I/O privileges (Operation not permitted).
> to me and #flashrom is not misleading at all.
I had overlooked that part and fixated on the last line about root.
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.
Package: libc6
Version: 2.31-3
Severity: normal
X-Debbugs-Cc:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I suspect this is an upstream problem but I'm reporting it here
first per their policy [1] since I'm unsure.
Both POSIX (including the Issue 8 draft) and the GNU C Library
manual say
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
Package: mupdf-tools
Version: 1.17.0+ds1-1
Severity: normal
X-Debbugs-Cc:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It appears mutool can't verify signed PDFs because it wasn't built
with OpenSSL support:
$ mutool sign -v signed.pdf
verifying signature 81
error: No OpenSSL support.
error
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: severity -1 serious
Control: affects -1 konqueror
(Forgot to send this to the bug; only sent to the submitter first time around.)
On Tuesday, September 1, 2020 2:32:54 PM EDT you wrote:
> I am pretty sure, the issue appeared with the change from 5.12 to 5.14,
around 5th of july.
101 - 200 of 425 matches
Mail list logo
