Processing commands for cont...@bugs.debian.org:
> close 963495
Bug #963495 [selinux-policy-default] selinux-policy-default: reportbug
Segmentation faulted when Selinux is in Enforcing mode
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> close 963497
Bug #963497 [selinux-policy-default] selinux-policy-default: Let's Encrypt
certbot tools crashed into Segmentation fault with SELinux Enforcing mode
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> close 976211 9.4.35-1
Bug #976211 [src:jetty9] jetty9: CVE-2020-27218
Marked as fixed in versions jetty9/9.4.35-1.
Bug #976211 [src:jetty9] jetty9: CVE-2020-27218
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you
close 976211 9.4.35-1
thanks
>From a quick check it looks the asm for ARM is present, it's just put
directly in the header
x86/mips (and their 64-bit variants) have AsmGetRegs*.S
arm and aarch64 has it in the header file,
see:
Processing control commands:
> tags -1 patch
Bug #972958 [src:pipemeter] pipemeter FTBFS: error: format not a string literal
and no format arguments
Added tag(s) patch.
--
972958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972958
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Package: pipemeter
Version: 1.1.4-1
Followup-For: Bug #972958
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
*
Your message dated Thu, 31 Dec 2020 05:18:21 +
with message-id
and subject line Bug#957127: fixed in ddccontrol 0.4.4-1.1
has caused the Debian Bug report #957127,
regarding ddccontrol: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: chardet
Version: 4.0.0-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:requests src:qgis
Dear Maintainer,
Upgrading python3-chardet causes the removal of many packages:
The following packages will be REMOVED:
Processing control commands:
> affects -1 src:requests src:qgis
Bug #978739 [chardet] chardet: Upgrading python3-chardet breaks many packages
Added indication that 978739 affects src:requests and src:qgis
--
978739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978739
Debian Bug Tracking
Your message dated Thu, 31 Dec 2020 04:33:51 +
with message-id
and subject line Bug#978437: fixed in geoclue-2.0 2.5.7-2
has caused the Debian Bug report #978437,
regarding geoclue-2.0: regression in 2.5.7-1, no geolocation returned
to be marked as done.
This means that you claim that the
On Tue, Dec 29, 2020 at 02:35:11PM -0500, Justin Erenkrantz wrote:
> The OpenSSL devs intended this to be a breaking change - but it's not
> documented anywhere. Sigh.
>
> I've got a WIP patch against trunk that causes test_ssl to pass - see below.
> It also seems to work with OpenSSL 1.1.1h as
Your message dated Thu, 31 Dec 2020 03:33:26 +
with message-id
and subject line Bug#975539: fixed in buku 4.5+ds-1
has caused the Debian Bug report #975539,
regarding buku's autopkg tests fail with Python 3.9
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> forwarded 978437 https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/142
Bug #978437 [geoclue-2.0] geoclue-2.0: regression in 2.5.7-1, no geolocation
returned
Set Bug forwarded-to-address to
forwarded 978437 https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/142
thanks
Le 30/12/20 à 16:43, gregor herrmann a écrit :
Thanks for the testing!
The following line is actually the real problem, I did all my tests on
laptop with wifi cards, I just tried on my desktop and I get the
Processing commands for cont...@bugs.debian.org:
> severity 978437 serious
Bug #978437 [geoclue-2.0] geoclue-2.0: regression in 2.5.7-1, no geolocation
returned
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978437:
On Wed, 30 Dec 2020 10:35:52 +, Holger Levsen wrote:
> On Wed, Dec 30, 2020 at 06:12:55AM +0100, Axel Beckert wrote:
> > gregoa: I'll leave up to you if you already want to close the bug
> > report or not. Feel free to replace my fixed tag with a pending tag or
> > so.
> I've already closed
Your message dated Thu, 31 Dec 2020 00:34:15 +
with message-id
and subject line Bug#975668: fixed in lxpanel 0.10.0-3
has caused the Debian Bug report #975668,
regarding lxpanel FTBFS: includes without
dependency
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> reassign 972659 tpm2-tss
Bug #972659 {Done: Ying-Chun Liu (PaulLiu) }
[libtss2-esys0] libtss2-esys0: bumps SONAME without changing package name
Bug reassigned from package 'libtss2-esys0' to 'tpm2-tss'.
No longer marked as found in versions
also, it looks like libunwindstack uses asm and there isn't any for ARM.
So if someone wants to keep the arm packages, they'll need to figure
that out. I have zero asm skills.
Roger Shimizu:
On Wed, Dec 30, 2020 at 3:46 AM Hans-Christoph Steiner wrote:
Ok, I fixed the dependency issue, now it gets reliably to the point rosh
gets to:
Thanks for fixing the build dependency issue!
I fixed a few other issues (operator script & mterp generation, etc),
and pushed to
Your message dated Wed, 30 Dec 2020 23:33:27 +
with message-id
and subject line Bug#978347: fixed in foxeye 0.12.1-3
has caused the Debian Bug report #978347,
regarding foxeye: FTBFS: configure:9276: error: possibly undefined macro:
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
to be
Am 27.12.2020 um 12:42 teilte Rene Engelhard mit:
Hi Rene,
Many thanks for the report!
dist-upgrade buster->bullseye which just caused my system to not get out of apt
-f install anymore:
Entpacken von texlive-base (2020.20201203-2) über (2018.20190227-2) ...
dpkg: Fehler beim Bearbeiten des
Your message dated Wed, 30 Dec 2020 22:49:49 +
with message-id
and subject line Bug#977225: fixed in openscad 2019.05-4
has caused the Debian Bug report #977225,
regarding openscad FTBFS with Boost 1.74
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Tue, 29 Dec 2020 23:26:38 +0530, Utkarsh Gupta said:
> Hi Hubert,
> On Tue, Dec 29, 2020 at 11:17 PM Hubert Chathi wrote:
>> Hmm. Can you try installing libfmt7 (from sid) and see if that fixes
>> it?
> The issue could be fixed by rebuilding nheko against the newly updated
> libfmt-dev
Processing control commands:
> tags -1 patch
Bug #978194 [src:openms] openms: FTBFS: glpk.h:36:16: error: using typedef-name
‘glp_prob’ after ‘struct’
Added tag(s) patch.
--
978194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978194
Debian Bug Tracking System
Contact
Package: openms
Version: 2.6.0+cleaned1-1
Followup-For: Bug #978194
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
*
Your message dated Wed, 30 Dec 2020 21:18:29 +
with message-id
and subject line Bug#963058: fixed in android-platform-art 10.0.0+r36-1~stage1
has caused the Debian Bug report #963058,
regarding android-platform-art ftbfs on arm64
to be marked as done.
This means that you claim that the
Your message dated Wed, 30 Dec 2020 19:48:43 +
with message-id
and subject line Bug#978520: fixed in tao-pegtl 2.8.3-3
has caused the Debian Bug report #978520,
regarding tao-pegtl: non-standard gcc/g++ used for build (gcc-9)
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 30 Dec 2020 12:46:02 -0700
with message-id <87v9cj5b7p@melete.silentflame.com>
and subject line Re: Bug#976092: ocrmypd fails autopkg tests in testing
has caused the Debian Bug report #976092,
regarding ocrmypd fails autopkg tests in testing
to be marked as done.
This
On Wed, Dec 30, 2020 at 06:36:23PM +0300, Sergei Golovan wrote:
> There isn't Tcl/Tk 8.7 in unstable yet, only an alpha in experimantal.
> After the Tcl/Tk 8.7 will be released, I'll deal with this bug in
> unstable.
ah, ok, makes sense.
probably it would still be nicer to downgrade this bug to
Your message dated Wed, 30 Dec 2020 17:04:08 +
with message-id
and subject line Bug#960454: fixed in chromium 87.0.4280.88-0.4
has caused the Debian Bug report #960454,
regarding chromium: Make Chromium ask before downloading and enabling DRM
to be marked as done.
This means that you claim
thanks for the reports, I will fix this in the next couple days
Sebastian Ramacher writes:
> On 2020-12-30 15:06:19 +0100, Sebastian Ramacher wrote:
>> Source: securefs
>> Version: 0.11.1+ds-1
>> Severity: serious
>> X-Debbugs-Cc: sramac...@debian.org
>>
>> securefs' autopkgtests hard-code
Dear Gianfranco,
Thanks for filing this bug report. I’m away for the next couple of days and
could not check, but wouldn’t just patching the pkgconfig file (your second
option) be a lot easier? Upstream merged both libraries and they probably just
forgot to change the pkgconfig file as well.
Package: notepadqq
Version: 2.0.0~beta1-1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When notepadqq is started you expect to see an empty tab
or tabs with reason files, but neither happens. Try to open a tab
resolves in a frozen application and if started from
Hi Holger,
On Wed, Dec 30, 2020 at 6:26 PM Holger Levsen wrote:
>
> Hi Sergei,
>
> On Wed, Dec 30, 2020 at 05:26:53PM +0300, Sergei Golovan wrote:
> > This bug is actually about blt 2.5.3+dfsg-5 and failure to build with
> > Tcl/Tk 8.7. So the serious severity is justified. The bug title is
> >
Hi,
Please ignore my previous message, was sent by mistake. Apologies for
the spam.
Regards,
Domenico
--
rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
Hi Sergei,
On Wed, Dec 30, 2020 at 05:26:53PM +0300, Sergei Golovan wrote:
> This bug is actually about blt 2.5.3+dfsg-5 and failure to build with
> Tcl/Tk 8.7. So the serious severity is justified. The bug title is
> misleading though, so I'm changing it. Sorry for not doing it sooner.
ah,
Your message dated Wed, 30 Dec 2020 15:19:08 +
with message-id
and subject line Bug#971209: fixed in rust-redox-syscall 0.1.57-2
has caused the Debian Bug report #971209,
regarding rust-redox-syscall: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo build returned exit code 101
to be
Processing commands for cont...@bugs.debian.org:
> tag 978681 -pending
Bug #978681 [xfce4-mpc-plugin] xfce4-mpc-plugin: build-depends on obsolete
package.
Ignoring request to alter tags of bug #978681 to the same tags previously set
> tag 978691 +pending
Bug #978691 [src:dwarves-dfsg]
Your message dated Wed, 30 Dec 2020 15:54:23 +0100
with message-id
and subject line Build failure solved
has caused the Debian Bug report #976586,
regarding boxbackup: FTBFS: latex undefined control sequence
to be marked as done.
This means that you claim that the problem has been dealt with.
If
set -1 +pending
thanks
--
rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
Processing commands for cont...@bugs.debian.org:
> retitle 947272 blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error: argument
> 'argv' doesn't match prototype
Bug #947272 [src:blt] blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:
Changed Bug title to 'blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3):
On Wed, Dec 30, 2020 at 3:46 AM Hans-Christoph Steiner wrote:
>
> Ok, I fixed the dependency issue, now it gets reliably to the point rosh
> gets to:
Thanks for fixing the build dependency issue!
I fixed a few other issues (operator script & mterp generation, etc),
and pushed to rosh/refine
retitle 947272 blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:
argument 'argv' doesn't match prototype
severity 947272 serious
thanks
Hi Holger!
This bug is actually about blt 2.5.3+dfsg-5 and failure to build with
Tcl/Tk 8.7. So the serious severity is justified. The bug title is
misleading
Hi William,
I indeed missed your call for help on Debian-Devel, sorry about it and
thank you for forwarding it to me quickly. I’m adding the Debian PHP
PEAR (and Composer) Maintainers list in the hope someone may join the
effort (and thus copying your whole message after mine to provide the
Processing commands for cont...@bugs.debian.org:
> retitle 947272 blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:
Bug #947272 [src:blt] blt: FTBFS with GCC 9: error: argument 'argv' doesn't
match prototype
Changed Bug title to 'blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:' from
'blt: FTBFS
Your message dated Wed, 30 Dec 2020 14:21:08 +
with message-id
and subject line Bug#978427: fixed in ppp 2.4.8-1+2
has caused the Debian Bug report #978427,
regarding enablement symlinks are not cleaned up on upgrades
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 30 Dec 2020 14:21:08 +
with message-id
and subject line Bug#978427: fixed in ppp 2.4.8-1+2
has caused the Debian Bug report #978427,
regarding ppp: Updates create a copy of /lib/systemd/system/pppd-dns.service
and dangling symlink
to be marked as done.
This means
On 2020-12-30 15:06:19 +0100, Sebastian Ramacher wrote:
> Source: securefs
> Version: 0.11.1+ds-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
>
> securefs' autopkgtests hard-code dependencies on a bunch of shared
> libraries: libcrypto++6, libfuse2, libjsoncpp1, and libutf8profc2.
Source: securefs
Version: 0.11.1+ds-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
securefs' autopkgtests hard-code dependencies on a bunch of shared
libraries: libcrypto++6, libfuse2, libjsoncpp1, and libutf8profc2. This
is most certainly wrong when securefs is rebuilt for transitions.
Processing control commands:
> severity -1 important
Bug #947272 [src:blt] blt: FTBFS with GCC 9: error: argument 'argv' doesn't
match prototype
Severity set to 'important' from 'serious'
--
947272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947272
Debian Bug Tracking System
Contact
control: severity -1 important
thanks
Hi Andreas,
it seems blt builds fine with gcc-10 as can be seen from the recent upload,
so I'm downgrading the severity and am wondering if we should actually close
this bug (=ftbfs with gcc-9). What do you think?
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
Your message dated Wed, 30 Dec 2020 15:05:09 +0100
with message-id <73cfacdd-ac1d-3019-1fa2-741771d9f...@web.de>
and subject line Build failure solved
has caused the Debian Bug report #976544,
regarding fontconfig: FTBFS: latex errors
to be marked as done.
This means that you claim that the
Your message dated Wed, 30 Dec 2020 13:48:49 +
with message-id
and subject line Bug#911464: fixed in free42-nologo 2.5.22+ds-1
has caused the Debian Bug report #911464,
regarding free42-nologo: Numbers entered incorrectly on arm architectures
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> tags 977246 fixed-upstream
Bug #977246 [lutris] lutris should depend on python3-dbus
Added tag(s) fixed-upstream.
> tags 978557 fixed-upstream
Bug #978557 [lutris] lutris: Add German translation
Added tag(s) fixed-upstream.
> thanks
Stopping
Your message dated Wed, 30 Dec 2020 12:33:36 +
with message-id
and subject line Bug#978517: fixed in seqan3 3.0.2+ds-6
has caused the Debian Bug report #978517,
regarding seqan3: non-standard gcc/g++ used for build (gcc-9)
to be marked as done.
This means that you claim that the problem has
Control: reassign -1 python3-fife 0.4.2-2
Control: affects -1 + unknown-horizons
On Tue, 29 Dec 2020 at 20:54:44 +0100, Steffen Langenbach wrote:
> I encountered a problem starting unknown-horizons.
...
> File "/usr/lib/python3/dist-
> packages/fife/extensions/serializers/simplexml.py", line
Processing control commands:
> reassign -1 python3-fife 0.4.2-2
Bug #978657 [unknown-horizons] unknown-horizons: Crash on startup with xml
AttributeError "no attribute 'getchildren'"
Bug reassigned from package 'unknown-horizons' to 'python3-fife'.
No longer marked as found in versions
hi Axel,
On Wed, Dec 30, 2020 at 06:12:55AM +0100, Axel Beckert wrote:
> gregoa: I'll leave up to you if you already want to close the bug
> report or not. Feel free to replace my fixed tag with a pending tag or
> so.
I've already closed the bug :)
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
Your message dated Wed, 30 Dec 2020 10:06:08 +
with message-id <20201230100608.gb6...@layer-acht.org>
and subject line Re: Bug#978675: Acknowledgement (libsys-hostname-long-perl:
FTBFS, tests fail)
has caused the Debian Bug report #978675,
regarding libsys-hostname-long-perl: FTBFS, tests
Processing commands for cont...@bugs.debian.org:
> tags 911464 + pending
Bug #911464 [free42-nologo] free42-nologo: Numbers entered incorrectly on arm
architectures
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
911464:
Processing commands for cont...@bugs.debian.org:
> retitle 977604 fails to compile templates
Bug #977604 [smarty3] smarty3: broken internal parsetree code
Changed Bug title to 'fails to compile templates' from 'smarty3: broken
internal parsetree code'.
> thanks
Stopping processing here.
Please
Your message dated Wed, 30 Dec 2020 09:18:39 +
with message-id
and subject line Bug#975803: fixed in lnav 0.9.0-1
has caused the Debian Bug report #975803,
regarding lnav: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned
exit code 2
to be marked as done.
This means that you
Processing control commands:
> tag -1 pending
Bug #975803 [src:lnav] lnav: FTBFS: dh_auto_test: error: make -j4 check
VERBOSE=1 returned exit code 2
Added tag(s) pending.
--
975803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975803
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #975803 in lnav reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id
and subject line Bug#977926: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977926,
regarding DistributionNotFound: 'hyperframe>=6.0' due to missing dependencies
to be marked as done.
This means that you claim that
Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id
and subject line Bug#977927: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977927,
regarding DistributionNotFound: 'hyperframe>=6.0' due to missing dependencies
to be marked as done.
This means that you claim that
Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id
and subject line Bug#977927: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977927,
regarding Missing required dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id
and subject line Bug#977926: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977926,
regarding Missing required dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> severity 978686 normal
Bug #978686 [src:dh-python] dh-python cannot parse python_version dependency
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978686:
Processing commands for cont...@bugs.debian.org:
> unmerge 977926
Bug #977926 [mitmproxy] Missing required dependencies
Bug #977927 [mitmproxy] DistributionNotFound: 'hyperframe>=6.0' due to missing
dependencies
Disconnected #977926 from all other report(s).
> clone 977926 -2
Bug #977926
72 matches
Mail list logo
