Your message dated Thu, 18 Feb 2021 23:04:08 +
with message-id
and subject line Bug#982559: fixed in xscorch 0.2.1-1+nmu6
has caused the Debian Bug report #982559,
regarding xscorch Build-Depends on libreadline-gplv2-dev which has been removed
to be marked as done.
This means that you claim
I would thus propose simply dropping the build-dependency, a debdiff doing that
is
attached, I may or may not NMU it later.
I have gone ahead with the NMU, final debdiff is attatched.
diff -Nru xscorch-0.2.1/debian/changelog xscorch-0.2.1/debian/changelog
--- xscorch-0.2.1/debian/changelog
Processing commands for cont...@bugs.debian.org:
> fixed 980564 88.0.4324.146-1~deb10u1
Bug #980564 {Done: Michel Le Bihan } [src:chromium]
chromium: 88.0.4324.96 stable release
Marked as fixed in versions chromium/88.0.4324.146-1~deb10u1.
> fixed 972134 88.0.4324.146-1~deb10u1
Bug #972134
Processing commands for cont...@bugs.debian.org:
> reopen 982882
Bug #982882 {Done: Tomasz Buchert } [src:stellarium]
stellarium FTBFS on armel and mipsel
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Processing commands for cont...@bugs.debian.org:
> fixed 972134 88.0.4324.96-1~deb10u1
Bug #972134 {Done: Michael Gilbert } [chromium] chromium:
please, consider moving the package to team-maintainance to properly maintain it
There is no source info for the package 'chromium' at version
Processing commands for cont...@bugs.debian.org:
> fixed 980564 88.0.4324.96-1~deb10u1
Bug #980564 {Done: Michel Le Bihan } [src:chromium]
chromium: 88.0.4324.96 stable release
The source 'chromium' and version '88.0.4324.96-1~deb10u1' do not appear to
match any binary packages
Marked as fixed
On Sat, Feb 13, 2021 at 5:01 AM Andreas Henriksson wrote:
> > For systems where awk is not yet installed (chroots), installation of
> > dash will currently fail since it's postinst calls add-shell from
> > debianutils.
>
> Please share details about how to reproduce this situation!
>
> You say you
Your message dated Thu, 18 Feb 2021 21:19:21 +
with message-id
and subject line Bug#982769: fixed in php-horde-text-filter 2.3.7-1
has caused the Debian Bug report #982769,
regarding php-horde-text-filter: CVE-2021-26929
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> severity -1 normal
Bug #939733 [lsb-release] lsb-release: lsb_release does not show point release
on Debian 10.1
Severity set to 'normal' from 'serious'
--
939733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939733
Debian Bug Tracking System
Contact
Control: severity -1 normal
* Dmitry Bogatov [2019-09-11 16:15]:
> control: severity -1 +normal
That appears to have failed. Trying again, as a service :-)
Your message dated Thu, 18 Feb 2021 20:19:24 +
with message-id
and subject line Bug#982882: fixed in stellarium 0.20.4-2
has caused the Debian Bug report #982882,
regarding stellarium FTBFS on armel and mipsel
to be marked as done.
This means that you claim that the problem has been dealt
Hi Adrian,
Adrian Bunk writes:
> On Sat, Jan 30, 2021 at 10:09:03PM -0500, Nicholas D Steeves wrote:
>> Hi Adrian,
>
> Hi Nicholas,
>
>> Thank you for checking in with this bug! Please let me know ASAP if
>> another autoremoval exception will be provided, because if necessary I
>> can do the
On 15/02/21 20:54, Paul Gevers wrote:
> Source: stellarium
> Version: 0.20.4-1
> Severity: serious
> Tags: ftbfs
>
> [...]
Seems like it is
https://github.com/Stellarium/stellarium/issues/1131. This has been
solved with https://bugreports.qt.io/browse/QTBUG-87010.
Surprisingly, the fix is not in
On Thu, 18 Feb 2021, Salvatore Bonaccorso wrote:
> On Thu, Feb 11, 2021 at 08:33:58AM +0100, Sebastien Delafond wrote:
> > The recently applied patch still creates the file with the default
> > umask[0], before chmod'ing down to 0600, so an attacker could still open
> > it in the meantime.
>
>
close 981976
On Thu, Feb 18, 2021 at 5:51 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Your message dated Thu, 18 Feb 2021 17:48:49 +
> with message-id
> and subject line Bug#981976: fixed in icingaweb2-module-businessprocess
> 2.3.0-2
> has caused the Debian Bug report
Graham,
Thanks for the bug tracker follow-up which made me aware of the ongoing
discussion in #665 at glmmTMB. It's frustrating to have the run around but it
really looks like as I argued all along: not an issue in Matrix. Now, TMB is
of course a complex package too.. Appreciate you chasing
The attached patch excludes fortune from the package in case no one
will track this down on a porterbox. I looked at it on amd64 and
found nothing suspicious sticking out.
9base_nofortune.patch.gz
Description: application/gzip
Your message dated Thu, 18 Feb 2021 17:48:49 +
with message-id
and subject line Bug#981976: fixed in icingaweb2-module-businessprocess 2.3.0-2
has caused the Debian Bug report #981976,
regarding icingaweb2-module-businessprocess: depends on nonexistent
icingaweb2-ipl
to be marked as done.
Your message dated Thu, 18 Feb 2021 17:33:28 +
with message-id
and subject line Bug#980219: fixed in flowblade 2.8.0.2-1
has caused the Debian Bug report #980219,
regarding flowblade: Fails to start without python3-distutils
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:rmatrix,
> src:r-cran-glmmtmb
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Control: tag -1 pending
Hello,
Bug #983018 in qttools-opensource-src 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:
Processing control commands:
> tag -1 pending
Bug #983018 [qdbus] qdbus: Needs package downgrade from Buster to Bullseye
(missing epoch in transitional package)
Added tag(s) pending.
--
983018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983018
Debian Bug Tracking System
Contact
On Thu, Feb 18, 2021 at 09:32:24AM +0100, Paul Gevers wrote:
>Hi Limonciello,
>
>On 18-02-2021 07:15, Limonciello, Mario wrote:
>> I don't have the power to manually run it. So there is nothing I can do.
>> With the new 1.5.6-1 upload someone will need to manually run it again.
>
>I recognize what
Hi nicoo
On 2021-02-16 15:59:19, nicoo wrote:
> On Sun, Feb 14, 2021 at 02:49:27PM +0100, Sebastian Ramacher wrote:
> > The upload of 0.12.0-2 just started a transition. Note that we are in
> > soft freeze and hence transitions are no longer acceptable for bullseye.
>
> Apologies for this: I had
Processing commands for cont...@bugs.debian.org:
> severity 983026 serious
Bug #983026 [libglib2.0-0] libglib2.0-0: After update GDM3 does not longer start
Severity set to 'serious' from 'important'
> tags 983026 + experimental
Bug #983026 [libglib2.0-0] libglib2.0-0: After update GDM3 does not
Your message dated Thu, 18 Feb 2021 15:48:41 +
with message-id
and subject line Bug#939568: fixed in icingaweb2-module-graphite 1.1.0-2
has caused the Debian Bug report #939568,
regarding icingaweb2-module-graphite: Incomplete debian/copyright?
to be marked as done.
This means that you claim
On Thu, 18 Feb 2021 at 12:06:58 +0100, Pino Toscano wrote:
> In data lunedì 15 febbraio 2021 13:07:13 CET, Simon McVittie ha scritto:
> > > In Cairo and Pango (which have a similar structure with multiple binary
> > > packages making use of each other's implementation details), I added a
> > >
On Wed, Feb 17, 2021 at 09:38:16PM +0530, Ritesh Raj Sarraf wrote:
> Source: swt4-gtk
> Version: 4.17.0-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
Hi Ritesh,
It seems that a local sbuild in a clean chroot doesn't set the
Package: libqt5widgets5
Version: 5.15.2+dfsg-4
Severity: critical
Tags: upstream newcomer
Justification: breaks unrelated software
Dear Maintainer,
Recently i found a bug in QGLWidget (one of the widgets included in
libqt5widgets5) that
creates a segfault. This bug was accepted as upstream bug
On 2021-02-18 02:32:10, Sadie Powell wrote:
> Charybdis' development was terminated due to (among other reasons) threats by
> a former maintainer. It probably won't be revived.
>
> It's successor is probably Solanum (https://github.com/solanum-ircd/solanum)
> which is a fork that is led by
Joerg Jaspert schrieb am 13. February 2021:
> i just removed guile-2.0 from unstable.
> While your package already won't be part of the next release, it will
> now also be unusable in unstable.
>
> Please either upload a fixed version
A fixed version sits at debian mentors looking for a
Processing commands for cont...@bugs.debian.org:
> # reassign reopened the bug
> close 982833
Bug #982833 [manpages-l10n] man2html,man2html-base,manpages-it: manpage
conflicts: man2html.1, hman.1
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> found -1 4.9.1-5
Bug #982833 [manpages-l10n] man2html,man2html-base,manpages-it: manpage
conflicts: man2html.1, hman.1
There is no source info for the package 'manpages-l10n' at version '4.9.1-5'
with architecture ''
Unable to make a source version for version
Followup-For: Bug #982833
Control: found -1 4.9.1-5
Hi,
the conflicting manpages are still present in manpages-it 4.9.1-5:
/usr/share/man/it/man1/hman.1.gz
/usr/share/man/it/man1/man2html.1.gz
Andreas
Processing commands for cont...@bugs.debian.org:
> found 981976 2.1.0-2
Bug #981976 [icingaweb2-module-businessprocess]
icingaweb2-module-businessprocess: depends on nonexistent icingaweb2-ipl
Marked as found in versions icingaweb2-module-businessprocess/2.1.0-2.
> thanks
Stopping processing
found 981976 2.1.0-2
thanks
Hi,
this bug has been found in above version.
Regards,
David
>
> On 18. 2. 2021, at 14:39, Paul Gevers wrote:
>
> autopkgtest [13:11:38]: test command1: cd imagick-*/tests && phpunit
Gah, whoever did this (well, and I definitely have merged it, so it’s my fault
anyway),
it’s wrong, it needs to iterate through the directories.
Thanks for the poke.
Source: php-imagick
Version: 3.4.4+php8.0+3.4.4-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of php-imagick the autopkgtest of php-imagick fails
in testing when that autopkgtest is run
Hi folks,
I think this is a consequence of running autopkgtest-pkg-r blindly for all
bioc packages since we are adding
Testsuite: autopkgtest-pkg-r
automatically to all packages. The "manual" test is prevented by simply
renaming the debian/tests/control file to
Your message dated Thu, 18 Feb 2021 13:33:38 +
with message-id
and subject line Bug#983008: fixed in silver-platter 0.4.1-2
has caused the Debian Bug report #983008,
regarding silver-platter: autopkgtest regression: cannot import name
'debcommit' from 'breezy.plugins.debian.changelog'
to be
Package: plasma-workspace-wayland
Version: 4:5.20.5-3
Severity: grave
Dear Maintainer,
from SDDM I try to start a Wayland KDE session.
The whole GUI freezes.
CTRL-ALT-FN2 cannot be used to open a terminal session.
SSH login is still possible.
Top reports 100 % CPU load for ksplashqml.
Processing commands for cont...@bugs.debian.org:
> # fix version tracking info
> reassign 982833 manpages-l10n
Bug #982833 {Done: Helge Kreutzmann }
[man2html,man2html-base,manpages-it] man2html,man2html-base,manpages-it:
manpage conflicts: man2html.1, hman.1
Bug reassigned from package
Source: lava
Version: 2020.12-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails often (since
around January on amd64 and arm64) [1].
Because the
Source: splint
Version: 1:3.1.2+dfsg-4
Severity: serious
Tags: ftbfs
Justification: ftbfs
splint-data 1:3.1.2+dfsg-4 is missing, so that splint cannot be
installed.
https://buildd.debian.org/status/package.php?p=splint signals a
build failure for "all" (thus affecting splint-data):
make[1]:
Source: r-bioc-mutationalpatterns
Version: 2.0.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent (October 2020) change somewhere outside of your package
the autopkgtest of your package started to
Your message dated Thu, 18 Feb 2021 11:19:24 +
with message-id
and subject line Bug#982519: fixed in libzstd 1.4.8+dfsg-2
has caused the Debian Bug report #982519,
regarding zstd: Race condition allows attacker to access world-readable
destination file
to be marked as done.
This means that
Hi Simon,
In data lunedì 15 febbraio 2021 13:07:13 CET, Simon McVittie ha scritto:
> Control: retitle 969907 epdfinfo crashing with mismatched libpoppler102 and
> libpoppler-glib8
> Control: tags 969907 + patch
>
> Sorry, this reply should have gone to the clone in libpoppler-glib8,
> not to
Processing commands for cont...@bugs.debian.org:
> # this variant with short window affects both Buster and Stretch
> found 982519 1.3.8+dfsg-3+deb10u1
Bug #982519 [zstd] zstd: Race condition allows attacker to access
world-readable destination file
Marked as found in versions
On Mon, 15 Feb 2021 at 12:07:13 +, Simon McVittie wrote:
> On Mon, 15 Feb 2021 at 12:03:35 +, Simon McVittie wrote:
> > I don't think this is actually about whether libpoppler-glib added new ABI
> > without bumping the shlibs version - it has a .symbols file that tracks
> > the version in
Control: tag -1 pending
Hi Sébastien, Hi Salvatore,
Salvatore Bonaccorso, on 2021-02-18 06:19:29 +0100:
> FTR, this has been fixed upstream.
Thanks the ping, I inlined upstream patch in the next iteration
of libzstd: 1.4.8+dfsg-2. Upload will occur with urgency=high.
Changes are available on
Processing control commands:
> tag -1 pending
Bug #982519 [zstd] zstd: Race condition allows attacker to access
world-readable destination file
Added tag(s) pending.
--
982519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982519
Debian Bug Tracking System
Contact ow...@bugs.debian.org
On Mon, 18 Jan 2021 at 11:27:35 +, Simon McVittie wrote:
> On Mon, 18 Jan 2021 at 10:54:30 +, Simon McVittie wrote:
> > Unfortunately, unlike #980369, I was not able to find a combination of
> > libraries that I could add to spirv.pc to fix this bug.
>
> I think the attached might do it?
Processing control commands:
> severity -1 important
Bug #983014 [manpages-de] manpages-de: Fails to upgrade from 4.2.0-1 to
4.9.1-5: This installation run will require temporarily removing the essential
package manpages-de:amd64 due to a Conflicts/Pre-Depends loop.
Severity set to 'important'
Control: severity -1 important
Control: reassign -1 apt 2.1.20
Hi David,
thanks for having a look at this.
David Kalnischkies wrote:
> On Thu, Feb 18, 2021 at 08:12:06AM +0100, Axel Beckert wrote:
> > I though have no idea why apt regards manpages-de as
> > essential. X-Debbugs-Cc'ing the APT
Hi,
On Sun, 7 Feb 2021 19:22:30 +0100 Chris Hofstaedtler
wrote:
> I guess one can change all the tests to use ::1 instead of
> 127.0.0.1, but that will just introduce other failure modes.
If no proper solution can be found shortly, can this package please be
uploaded with these specific tests
Hi,
On Fri, 29 Jan 2021 20:50:07 +0100 Sebastian Andrzej Siewior
wrote:
> > The release team considers these bugs release critical.
>
> it would be easier to enforce to have all buildds configured equally so
> the package does not fail on a random buildd.
I *guess* that's not trivial as I
On Thu, Feb 18, 2021 at 08:12:06AM +0100, Axel Beckert wrote:
> I though have no idea why apt regards manpages-de as
> essential. X-Debbugs-Cc'ing the APT developers at
Does the output of
$ apt rdepends manpages-de --important
include more than task-german and parl-desktop-eu?
In particular,
Hi,
On Thu, 18 Feb 2021 08:28:06 +0100 Paul Gevers wrote:
> shoogle has an autopkgtest, great. However, on i386 it fails more often
^^^ oops, that's what you get for reusing an old mail.
> I copied the output at the bottom of this report. Can you please look
> into it and make the test
Processing commands for cont...@bugs.debian.org:
> forwarded 983013 https://gitlab.com/m2crypto/m2crypto/-/issues/293
Bug #983013 [src:m2crypto] m2crypto: autopkgtest needs update for new version
of openssl: M2Crypto.RSA.RSAError: sslv3 rollback attack
Set Bug forwarded-to-address to
forwarded 983013 https://gitlab.com/m2crypto/m2crypto/-/issues/293
thanks
I've created an upstream issue for it.
Hi Limonciello,
On 18-02-2021 07:15, Limonciello, Mario wrote:
> I don't have the power to manually run it. So there is nothing I can do.
> With the new 1.5.6-1 upload someone will need to manually run it again.
I recognize what you say. However, *in my opinion* you can't just upload
the
Processing commands for cont...@bugs.debian.org:
> # Forgot to set the actual version in the bug report
> found 983018 5.15.2-3
Bug #983018 [qdbus] qdbus: Needs package downgrade from Buster to Bullseye
(missing epoch in transitional package)
Marked as found in versions
Source: x11vnc
Version: 0.9.16-6
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails often [1].
Because the unstable-to-testing migration software now blocks on
Dear maintainer,
> [ERROR] LazyFont - Failed to read font file
> /usr/share/texlive/texmf-dist/fonts/opentype/public/stix2-otf/STIX2Math.otf
It's easy enough to locate the files which mention the font,
it is doc/user-manuals/fop.xconf in all three affected packages.
Package: qdbus
Severity: serious
Justification: §3.2 and https://wiki.debian.org/SystemDowngrade
Hi,
on one system I wondered why qdbus is still on Qt4. Then I noticed that
the version of the Qt4 qdbus package from Buster is higher (!) than the
version of the Qt5 qdbus package in Bullseye:
$
Processing commands for cont...@bugs.debian.org:
> forwarded 983010 https://github.com/Debian/debiman/issues/127
Bug #983010 [src:mdocml, src:debiman] mdocml breaks debiman autopkgtest:
different output
Set Bug forwarded-to-address to 'https://github.com/Debian/debiman/issues/127'.
> thanks
On 2021-02-18 08:15:15 [+0100], Paul Gevers wrote:
>
> I copied some of the output at the bottom of this report. I *think*
> this may be related to CVE-2020-25657 "bleichenbacher timing attacks in
> the RSA decryption API" against m2crypto, hence I file this bug against
> m2crypto.
The openssl
Processing commands for cont...@bugs.debian.org:
> tags 982992 - sid
Bug #982992 [src:node-regjsparser, src:node-regexpu-core] node-regjsparser
breaks node-regexpu-core autopkgtest: Missing expected exception (Error).
Removed tag(s) sid.
> thanks
Stopping processing here.
Please contact me if
69 matches
Mail list logo
