Processing control commands:
> tag -1 pending
Bug #975584 [src:consul] consul: CVE-2020-28053
Added tag(s) pending.
--
975584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #975584 in consul 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 Thu, 03 Dec 2020 06:48:24 +
with message-id
and subject line Bug#975878: fixed in yade 2020.01a-13
has caused the Debian Bug report #975878,
regarding libyade is still linked with libpython3.8
to be marked as done.
This means that you claim that the problem has been dealt
The following packages have unmet dependencies:
android-libadb : Depends: android-libbase (= 1:8.1.0+r23-8) but
1:10.0.0+r36-1~stage1.1 is to be installed
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) android-libbase
Control: tag 970878 + patch
Hi Jonas (2020.10.23_03:07:27_-0700)
FWIW I found the offending upstream commit and reverting it seems to do
the trick. I prefer fixing problems to reverting changes, but the bug
wasn't obvious to me, and the commit doesn't seem critical.
The commit is "txtwrite -
Processing control commands:
> tag 970878 + patch
Bug #970878 [src:ghostscript] ghostscript breaks doc-rfc autopkgtest:
segmentation fault
Added tag(s) patch.
--
970878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
> > @Norbert: could fix this in upstream?
l3packages has moved from collection-latexrecommended to
collection-latex in svn 57048.
Thus, a new checkout with the respective
filemove;texlive-latex-recommended;texlive-latex-base;2020.20201203
needs to be added to tpm2deb.cfg, and rebuilt.
Your message dated Thu, 03 Dec 2020 04:03:22 +
with message-id
and subject line Bug#976135: fixed in php-gettext 1.0.12-2
has caused the Debian Bug report #976135,
regarding Breaks tt-rss
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Dear colleagues,
On Thu, 03 Dec 2020 03:34:52 +0100 Andreas Beckmann wrote:
> Probably some files are being accessed that are not created in this mode:
I have already fixed it and a bunch of another issues but I have not uploaded
the fix yet to Salsa.
Today I am going to build the latest trunk
severity 971570 normal
retitle 971570 check whether binNMU transition to libgit2 1.0 is successful
thanks
Ajusting severity according to what I wrote. I keep the bug open to
remind us that we should check that the binNMU facility actually worked.
Nothing else should be necessary.
Norbert
On
Processing commands for cont...@bugs.debian.org:
> severity 971570 normal
Bug #971570 [julia] julia: libgit2 1.0 transition
Severity set to 'normal' from 'serious'
> retitle 971570 check whether binNMU transition to libgit2 1.0 is successful
Bug #971570 [julia] julia: libgit2 1.0 transition
Processing commands for cont...@bugs.debian.org:
> fixed 971721 3.65
Bug #971721 {Done: Charles Plessy } [mime-support]
mime-support: missing dependency on perl
Marked as fixed in versions mime-support/3.65.
> found 976254 2.1.2-5
Bug #976254 {Done: Andreas Tille } [src:rnahybrid] rnahybrid:
Source: atop
Version: 2.5.0-1+exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
atop FTBFS twice in a row because 'make clean' does not remove the
generated 'atopsar':
fakeroot debian/rules clean
dh clean
debian/rules
Your message dated Thu, 03 Dec 2020 02:46:42 +
with message-id
and subject line Bug#975994: fixed in python-libzim 0.0.3-2
has caused the Debian Bug report #975994,
regarding zimlib breaks python-libzim autopkgtest: segfaults
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 03 Dec 2020 02:38:25 +
with message-id
and subject line Bug#975754: fixed in cruft-ng 0.4.9
has caused the Debian Bug report #975754,
regarding cruft-ng: FTBFS: mlocate.cc:5:10: fatal error: mlocate/db.h: No such
file or directory
to be marked as done.
This means
Source: kodi
Version: 2:19.0~alpha3+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
kodi/experimental FTBFS during a separate binary-indep build,
i.e. dpkg-buildpackage -A
Source: astra-toolbox
Version: 1.8.3-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
astra-toolbox FTBFS twice in a row. After the first (and successful) build,
the package source gets cleaned but leaves some artifacts lying around
which breaks the subsequent
Hi,
On 11/30/20 11:25 AM, Paul Gevers wrote:
That versioned Depends relation should be enough for CI. But what about
users that do a partial upgrade? (Yes, I know, officially not supported
in Debian, but in practice it works pretty well).
Good point. I'll do that as well.
-- Kunal
tag 976135 + patch
thanks
On Mon, 30 Nov 2020 09:45:48 +0100 Andrey Rahmatullin
wrote:
[...]
>
> PHP Fatal error: Uncaught Error: Call to a member function evaluate() on
> null in /usr/share/php/php-php-gettext/gettext.php:325
This is a silly error I made in a patch to fix the security issue
Your message dated Thu, 03 Dec 2020 01:52:41 +
with message-id
and subject line Bug#967216: fixed in telepathy-haze 0.8.0-3
has caused the Debian Bug report #967216,
regarding telepathy-haze: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tag 976135 + patch
Bug #976135 [php-php-gettext] Breaks tt-rss
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976135
Debian Bug
Source: volk
Version: 2.4.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
volk/experimental FTBFS during a separate binary-indep build,
i.e. dpkg-buildpackage -A
Package: util-linux
Version: 2.36.1-2
Followup-For: Bug #975727
X-Debbugs-Cc: hyil...@gmail.com
Just pulled to util-linux 2.36.1-2 from unstable into testing and rebooted just
to be sure, but am still seeing the same error davfs2 1.6.0-1.
-- System Information:
Debian Release: bullseye/sid
Source: xalan
Version: 1.12-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
xalan FTBFS during a separate binary-indep build, i.e. dpkg-buildpackage -A,
because it tries to run unittests whose binaries have not been built.
This
Hi,
Is there any dependency that needs to be packaged for the package to
be updated? I remember seeing on the tracker that there are packages
in python2 that according to a Debian Developer told me that it is not
being allowed to enter the official repositories. The number of CVEs
continues to
Processing commands for cont...@bugs.debian.org:
> # there was a typo in my previous mail
> found 976072 0.13-4
Bug #976072 [topydo] topydo: Fails to upgrade: update-alternatives: error:
alternative todo can't be master: it is a slave of todo.txt
Marked as found in versions topydo/0.13-4.
>
Processing control commands:
> reopen -1
Bug #976072 {Done: David Steele } [topydo] topydo: Fails to
upgrade: update-alternatives: error: alternative todo can't be master: it is a
slave of todo.txt
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will
Control: reopen -1
Control: fouund -1 0.13-4
Hi David
Debian Bug Tracking System wrote:
>* Accommodate autopkgtests with the old todo.txt-base (Closes: #976111,
> #976072).
#976072 had nothing todo with autopkgtests.
And the issue is still there in 0.13-4:
Preparing to unpack
Your message dated Wed, 02 Dec 2020 22:06:56 +
with message-id
and subject line Bug#976111: fixed in topydo 0.13-4
has caused the Debian Bug report #976111,
regarding topydo 0.13-3 upload seems to hang ci.debian.net workers while
testing todo.txt-base
to be marked as done.
This means that
Your message dated Wed, 02 Dec 2020 22:06:56 +
with message-id
and subject line Bug#976072: fixed in topydo 0.13-4
has caused the Debian Bug report #976072,
regarding topydo: Fails to upgrade: update-alternatives: error: alternative
todo can't be master: it is a slave of todo.txt
to be
Hi Xavier (2020.10.12_02:18:06_-0700)
> node-xterm is incompatible with current tsc. It requires ^3.5.3.
FWIW, the new upstream 4.9.0 supports typescript 4
https://github.com/xtermjs/xterm.js/releases/tag/4.9.0
But it also comes with new dependencies, and packaging work.
SR
--
Stefano Rivera
Control: tags 957107 + patch
Control: tags 957107 + pending
--
Dear maintainer,
I've prepared an NMU for crashmail (versioned as 1.7-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru crashmail-1.7/debian/changelog
Processing control commands:
> tags 957107 + patch
Bug #957107 [src:crashmail] crashmail: ftbfs with GCC-10
Added tag(s) patch.
> tags 957107 + pending
Bug #957107 [src:crashmail] crashmail: ftbfs with GCC-10
Added tag(s) pending.
--
957107:
Your message dated Wed, 02 Dec 2020 21:49:01 +
with message-id
and subject line Bug#957379: fixed in isc-dhcp 4.4.1-2.2
has caused the Debian Bug report #957379,
regarding isc-dhcp: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 02 Dec 2020 21:33:29 +
with message-id
and subject line Bug#957228: fixed in freebirth 0.3.2-9.3
has caused the Debian Bug report #957228,
regarding freebirth: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 02 Dec 2020 21:19:47 +
with message-id
and subject line Bug#974726: fixed in q2-metadata 2020.11.0+dfsg-1
has caused the Debian Bug report #974726,
regarding q2-metadata: unsatisfiable build-dependencies
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 02 Dec 2020 21:18:27 +
with message-id
and subject line Bug#957184: fixed in eurephia 1.1.0-6.1
has caused the Debian Bug report #957184,
regarding eurephia: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: design-desktop-web
Version: 3.0.20
Severity: serious
Justification: chromium removal
Hi Jonas,
With my Release Team member hat on, please drop chromium from the list
of Depends of design-desktop-web. The reason I'm asking is that we want
to remove chromium from bullseye because it's
Source: rails
Version: 2:6.0.3.4+dfsg-1
Severity: serious
Justification: removal of chromium
Dear rails maintainers,
I love tests. As one of the maintainers of the ci.debian.net
infrastructure, I really do. However, with my Release Team member hat
on, I'm asking you to stop Build-Depending on
Hi,
Is it possible to update the version of khal that is being built
here? One of the failures in the latest build log was fixed in
0.10.2 and I'm not sure about the other, and there's currently
no version in testing.
Thanks!
Hi,
On Sun, 8 Nov 2020 22:21:36 +0100 Paul Gevers wrote:
> If you believe your package is unable to migrate to testing due to
> issues beyond your control, don't hesitate to contact the Release Team.
The removal bug has been filed some time ago. We'll just have to wait
until ftp-masters process
Hi
On Tue, 20 Oct 2020 22:07:09 +0200 Paul Gevers wrote:
> If you believe your package is unable to migrate to testing due to
> issues beyond your control, don't hesitate to contact the Release Team.
This package is waiting for python3-defaults, which should migrate in a
couple of days. Pinging
Processing control commands:
> close -1 1.4.2-1
Bug #976288 [src:srt] src:srt: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions srt/1.4.2-1.
Bug #976288 [src:srt] src:srt: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
>
Source: srt
Version: 1.4.1-5
Severity: serious
Control: close -1 1.4.2-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 971754
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync
Package: ruby-azure-storage
Version: 0.15.0~preview-2
Severity: serious
Autopkgtest fails with error (rebuild should see the same failure)
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday' (~> 0.9) - did find: [faraday-1.1.0]
(Gem::MissingSpecVersionError)
Package: ruby-azure-core
Version: 0.1.15-1
Severity: serious
Autopkgtest failed with this error (rebuild should see the same error)
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday' (~> 0.9) - did find: [faraday-1.1.0]
(Gem::MissingSpecVersionError)
Full
Your message dated Wed, 02 Dec 2020 17:34:21 +
with message-id
and subject line Bug#967214: fixed in telepathy-gabble 0.18.4-4
has caused the Debian Bug report #967214,
regarding telepathy-gabble: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that
Your message dated Wed, 02 Dec 2020 17:18:46 +
with message-id
and subject line Bug#976254: fixed in rnahybrid 2.1.2-6
has caused the Debian Bug report #976254,
regarding rnahybrid: Does not build from source "multiple definition of"
to be marked as done.
This means that you claim that the
On 2020, ഡിസംബർ 2 9:33:04 PM IST, Utkarsh Gupta wrote:
>Hi Praveen,
>
>On Wed, Dec 2, 2020 at 8:06 PM Pirate Praveen wrote:
>> I can see there is already a patch for relaxing faraday.
>> https://salsa.debian.org/puppet-team/ruby-puppet-forge/-/blob/master/debian/patches/002_loosen_deps.patch
Hi Praveen,
On Wed, Dec 2, 2020 at 8:06 PM Pirate Praveen wrote:
> I can see there is already a patch for relaxing faraday.
> https://salsa.debian.org/puppet-team/ruby-puppet-forge/-/blob/master/debian/patches/002_loosen_deps.patch
> This will need to be extended to cover ruby-faraday-middleware
Your message dated Wed, 02 Dec 2020 15:48:45 +
with message-id
and subject line Bug#963302: fixed in farstream-0.2 0.2.9-1
has caused the Debian Bug report #963302,
regarding farstream-0.2: FTBFS: fs-enumtypes.c:6:1: error: stray ‘\’ in program
to be marked as done.
This means that you claim
Your message dated Wed, 02 Dec 2020 15:48:45 +
with message-id
and subject line Bug#970740: fixed in farstream-0.2 0.2.9-1
has caused the Debian Bug report #970740,
regarding farstream-0.2 build-depends unsatisfiable in testing
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 02 Dec 2020 15:18:36 +
with message-id
and subject line Bug#967218: fixed in telepathy-rakia 0.8.0-4
has caused the Debian Bug report #967218,
regarding telepathy-rakia: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that
Your message dated Wed, 2 Dec 2020 15:31:46 +0100
with message-id
and subject line q2cli build time test failure fixed in version 2020.11.0-1
has caused the Debian Bug report #954601,
regarding q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i
python{version} -p 3.8 -s custom
Package: ruby-puppet-forge
Version: 2.3.2-1
Severity: serious
autopkgtest is failing with ruby-faraday-middleware 1.0.
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday_middleware' (< 0.14.0, >= 0.9.0) - did find:
[faraday_middleware-1.0.0]
Hi,
That is a common problem with legacy code being compiled with gcc-10, since
it defaults to "-fno-common". It can be solved for legacy packages by
passing "CFLAGS=-fcommon" to the `configure` (e.g `./configure
CFLAGS=-fcommon`), then `make` will succeed.
More information from
> @Norbert: could fix this in upstream?
I'll discuss with Karl.
Thanks
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C
On Wed, Dec 02, 2020 at 01:50:55PM +0100, Étienne Mollier wrote:
> Synchronizing work on q2-* modules update, I think I'm on a good
> trail for q2cli.
Great! Andreas.
--
http://fam-tille.de
Hi,
Synchronizing work on q2-* modules update, I think I'm on a good
trail for q2cli.
Kind Regards,
--
Étienne Mollier
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.
signature.asc
Description: PGP signature
On Wed, Dec 02, 2020 at 12:10:43PM +0100, Moritz Muehlenhoff wrote:
> I'll compare them with yours tonight, but I'd expect them to be identical
> given
> how close buster is to upstream.
>
Yeah, they're the same. Thanks for getting this rolling.
Cheers,
Julien
Processing commands for cont...@bugs.debian.org:
> tags 966439 + ftbfs
Bug #966439 [clickhouse] clickhouse ftbfs with gcc-10
Ignoring request to alter tags of bug #966439 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966439:
Am 02.12.2020 um 00:31 teilte Hilmar Preuße mit:
Hi,
I could solve the issue by installing texlive-latex-recommended,
which introduces
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.ltx
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse-generic.tex
Processing commands for cont...@bugs.debian.org:
> tags 966439 + ftbfs
Bug #966439 [clickhouse] clickhouse ftbfs with gcc-10
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966439
Hi,
On Wed, Dec 02, 2020 at 09:41:01AM +0100, Vincent Bernat wrote:
> ❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff:
> > Michael has been heroically keeping up with this beast of a codebase for
> > years,
> > but we clearly need a broader base to sustain it going forward.
> In the past, it
Your message dated Wed, 02 Dec 2020 11:34:45 +
with message-id
and subject line Bug#954604: fixed in mailman-hyperkitty 1.1.0-9.1
has caused the Debian Bug report #954604,
regarding mailman-hyperkitty: FTBFS: dh_auto_test: error: pybuild --test
--test-nose2 -i python{version} -p "3.7 3.8"
On Wed, Dec 02, 2020 at 11:49:24AM +0100, Julien Cristau wrote:
> Hi,
>
> On Tue, Dec 01, 2020 at 05:58:56PM +0100, Salvatore Bonaccorso wrote:
> > The following vulnerabilities were published for xorg-server.
> >
> > CVE-2020-25712[0]:
> > | Fix XkbSetDeviceInfo() and SetDeviceIndicators() heap
Your message dated Wed, 02 Dec 2020 11:04:09 +
with message-id
and subject line Bug#975579: fixed in xorg-server 2:1.20.10-1
has caused the Debian Bug report #975579,
regarding src:xorg-server: fails to migrate to testing for too long: FTBFS on
mips*el
to be marked as done.
This means that
Your message dated Wed, 02 Dec 2020 11:04:09 +
with message-id
and subject line Bug#976216: fixed in xorg-server 2:1.20.10-1
has caused the Debian Bug report #976216,
regarding xorg-server: CVE-2020-25712 CVE-2020-14360
to be marked as done.
This means that you claim that the problem has
Am 02.12.2020 um 00:31 teilte Hilmar Preuße mit:
Hi,
I could solve the issue by installing texlive-latex-recommended, which
introduces
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.ltx
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse-generic.tex
Your message dated Wed, 02 Dec 2020 10:49:15 +
with message-id
and subject line Bug#957802: fixed in sipsak 0.9.7-2
has caused the Debian Bug report #957802,
regarding sipsak: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hi,
On Tue, Dec 01, 2020 at 05:58:56PM +0100, Salvatore Bonaccorso wrote:
> The following vulnerabilities were published for xorg-server.
>
> CVE-2020-25712[0]:
> | Fix XkbSetDeviceInfo() and SetDeviceIndicators() heap overflows
>
> CVE-2020-14360[1]:
> | Check SetMap request length carefully
>
Package: src:linux
Version: 5.9.9-1
Severity: critical
Justification: causes serious data loss
X-Debbugs-Cc:
t...@mirbsd.de,reply+aagshfu5klm2qb2dozdxppf5z5jydevbnhhcvex...@reply.github.com
A bit of backstory, since this is not the first place I had to
report this to (feels like being sent from
Processing control commands:
> tags -1 help
Bug #976254 [src:rnahybrid] rnahybrid: Does not build from source "multiple
definition of"
Added tag(s) help.
--
976254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi,
no idea why this was not catched in the usual gcc-10 rebuilds. Any volunteer?
Kind regards
Andreas.
On Wed, Dec 02, 2020 at 12:08:32AM +0100, Andreas Tille wrote:
> Source: rnahybrid
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
>
> Hi,
>
> I tried
Control: severity -1 normal
Control: tags -1 + moreinfo
signature.asc
Description: PGP signature
Processing control commands:
> severity -1 normal
Bug #976147 [mariadb-server-10.5] Upgrade from mariadb-server-10.3 to
mariadb-server-10.5 fails
Severity set to 'normal' from 'critical'
> tags -1 + moreinfo
Bug #976147 [mariadb-server-10.5] Upgrade from mariadb-server-10.3 to
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
So, 5.9.11 has just reached testing. Too bad I can not upgrade to it because of
this bug here.
I will wait for 5.10 to reach the repos and hope that a patch will be found by
then.
❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff:
> Michael has been heroically keeping up with this beast of a codebase for
> years,
> but we clearly need a broader base to sustain it going forward.
In the past, it was team-maintained. I don't remember exactly, but I
think there was a
Source: rnahybrid
Severity: serious
Tags: ftbfs
Justification: FTBFS
Hi,
I tried to rebuild the package but the build ends in:
...
gcc -g -O2 -fdebug-prefix-map=/build/rnahybrid-2.1.2=. -fstack-protector-strong
-Wformat -Werror=format-security -g -O2
79 matches
Mail list logo
