upstream: https://github.com/ksnip/kImageAnnotator/issues/185[1]
Sincerely yours
Damir Islamov
email: da...@secretlaboratory.ru
[1] https://github.com/ksnip/kImageAnnotator/issues/185
signature.asc
Description: This is a digitally signed message part.
Processing commands for cont...@bugs.debian.org:
> close 973167 0.5.2-1
Bug #973167 [src:ufonormalizer] ufonormalizer: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Marked as fixed in versions ufonormalizer/0.5.2-1.
Bug #973167
Hi Vincas,
> Package: libkwaylandserver5
> Version: 5.20.4-2
> /usr/bin/kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5:
> undefined symbol:
> _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShe
> llSurfaceInterfaceE
Which version of kwin do you have installed?
Processing commands for cont...@bugs.debian.org:
> reassign 977329 lxqt-qtplugin
Bug #977329 [krita] krita segfaults when try to open with libQt5Gui.so.5.15.1
Bug reassigned from package 'krita' to 'lxqt-qtplugin'.
No longer marked as found in versions krita/1:4.4.1+dfsg-1.
Ignoring request to
Processing control commands:
> close -1 0.11.10-1
Bug #978035 [src:sublime-music] src:sublime-music: fails to migrate to testing
for too long: Dependencies can't migrate
Marked as fixed in versions sublime-music/0.11.10-1.
Bug #978035 [src:sublime-music] src:sublime-music: fails to migrate to
Source: sublime-music
Version: 0.9.1-2
Severity: serious
Control: close -1 0.11.10-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 972803
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
Processing control commands:
> close -1 1.0.194-1
Bug #978034 [src:tools-cli-clojure] src:tools-cli-clojure: fails to migrate to
testing for too long: maintainer built arch:all binaries
Marked as fixed in versions tools-cli-clojure/1.0.194-1.
Bug #978034 [src:tools-cli-clojure]
Source: tools-cli-clojure
Version: 0.3.5-2
Severity: serious
Control: close -1 1.0.194-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync
Your message dated Thu, 24 Dec 2020 20:49:46 +
with message-id
and subject line Bug#977900: fixed in node-autoprefixer 10.1.0+~cs11.3.2.0-1
has caused the Debian Bug report #977900,
regarding node-autoprefixer: FTBFS: ENOENT: no such file or directory, open
'path'
to be marked as done.
This
Source: python-cobra
Version: 0.19.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The autopkgtests of python-cobra recently started to fail in testing [1].
I've copied what I hope is the
Hi gregor,
On 24-12-2020 02:57, gregor herrmann wrote:
> So this looks like a potential for improvement for the tooling to
> detect "key packages", namely to take Provides into account.
Our tooling [1] already does that, but IIRC it prefers real packages
over Provides.
Paul
Processing commands for cont...@bugs.debian.org:
> retitle 971271 rainloop: ftbfs with node-postcss 8.0
Bug #971271 [rainloop] rainloop: ftbfs with node-postcss 8.0 in experimental
Changed Bug title to 'rainloop: ftbfs with node-postcss 8.0' from 'rainloop:
ftbfs with node-postcss 8.0 in
Processing control commands:
> retitle rainloop: ftbfs with node-postcss 8.0
Unknown command or malformed arguments to command.
> severity -1 serious
Bug #971271 [rainloop] rainloop: ftbfs with node-postcss 8.0 in experimental
Severity set to 'serious' from 'important'
--
971271:
Package: kvpm
Version: 0.9.10-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I can't launch kvpm it crashes after launch !
kvpm: symbol lookup error: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: undefined
symbol: ucol_open_63
I get the same kind of problem with
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package swi-prolog
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing control commands:
> forwarded -1 https://github.com/seccomp/libseccomp-golang/issues/61
Bug #976943 [src:golang-github-seccomp-libseccomp-golang]
golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src
pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go
Control: forwarded -1 https://github.com/seccomp/libseccomp-golang/issues/61
Control: severity -1 important
On Thu, Dec 24, 2020 at 9:12 PM Lucas Nussbaum wrote:
>
> On 14/12/20 at 14:36 -0500, Reinhard Tartler wrote:
> >
> >
> > > === RUN TestRuleAddAndLoad
> > > seccomp_test.go:588:
Package: libopenmpi3
Version: 3.1.3-11
Severity: serious
Even with the fixed libpmix2_4.0.0~rc1-2, I am getting runtime failures
trying to run MPI programs, e.g. the nwchem autopkgtests all fail like
this:
| Running tests/water/water_md
|
| cleaning scratch
| copying input and verified
hi
is this bug existed in testing kernel 5.9.11 ?
Package: src:linux
Version: 5.10.2-1~exp1
Followup-For: Bug #977645
Just wanted to mention that this version as well as 5.10.1 do boot
on a RPi3B+. It's not in any way contradicting this bug, but may be
useful to know nonetheless.
-- Package-specific info:
** Version:
Linux version
Hi!
On Thu, 24 Dec 2020 14:37:09 +0100 Michel Le Bihan wrote:
> Hello,
>
> This issue is about Chromium crashing just after startup with debug
> when it did not crash that quickly without debug. Is Chromium as stable
> with debug as without it?
>
> All Chromium packages in Debian unstable and
is this bug happen in the current testing kernel 5.9.11 ?
Processing control commands:
> tags -1 pending
Bug #977900 [src:node-autoprefixer] node-autoprefixer: FTBFS: ENOENT: no such
file or directory, open 'path'
Added tag(s) pending.
--
977900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977900
Debian Bug Tracking System
Contact
Control: tags -1 pending
On Tue, 22 Dec 2020 16:25:36 +0100 Andreas Beckmann
wrote:
> debian/autoprefixer.js → dist/autoprefixer.js...
> [!] Error: Could not load path (imported by
./../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such
file or directory, open 'path'
> Error:
Your message dated Thu, 24 Dec 2020 15:00:12 +
with message-id
and subject line Bug#976583: fixed in ompl 1.5.1+ds1-1
has caused the Debian Bug report #976583,
regarding ompl: FTBFS: Failed to copy 'usr/bin/ompl_benchmark_statistics.py':
No such file or directory at
Your message dated Thu, 24 Dec 2020 15:00:09 +
with message-id
and subject line Bug#973999: fixed in armnn 20.08-1
has caused the Debian Bug report #973999,
regarding armnn: FTBFS: error: no matching function for call to
‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(const
Processing control commands:
> block -1 by 977900
Bug #977688 [node-css-loader] node-css-loader: please embed additional postcss
extensions
977688 was not blocked by any bugs.
977688 was not blocking any bugs.
Added blocking bug(s) of 977688: 977900
> tag 977900 help
Bug #977900
Processing commands for cont...@bugs.debian.org:
> forcemerge 973848 975060
Bug #973848 {Done: Michel Le Bihan } [chromium] chromium:
Unsupported version, many security bugs unfixed
Bug #973858 {Done: Michel Le Bihan } [chromium] chromium:
Outdated version, more than 100 open security issues
Processing commands for cont...@bugs.debian.org:
> merge 973848 975060
Bug #973848 {Done: Michel Le Bihan } [chromium] chromium:
Unsupported version, many security bugs unfixed
Bug #973858 {Done: Michel Le Bihan } [chromium] chromium:
Outdated version, more than 100 open security issues
Unable
Processing commands for cont...@bugs.debian.org:
> merge 975060 973848
Bug #975060 [chromium] chromium: Chromium stuck in version 83
Unable to merge bugs because:
severity of #973858 is 'grave' not 'normal'
done of #973858 is 'Michel Le Bihan ' not ''
severity of #973848 is 'grave' not 'normal'
Your message dated Thu, 24 Dec 2020 13:33:53 +
with message-id
and subject line Bug#977960: fixed in node-jquery 3.5.1+dfsg+~3.5.5-3
has caused the Debian Bug report #977960,
regarding dangling /usr/share/javascript/jquery/jquery.js symlink
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> forwarded 976910 https://github.com/Blosc/python-blosc/issues/227
Bug #976910 [src:python-blosc] python-blosc: FTBFS on ppc64el: KeyError: 'flags'
Set Bug forwarded-to-address to
'https://github.com/Blosc/python-blosc/issues/227'.
> thanks
tags 977243 -pending
thanks
CC-ing on of upstream contributors.
@Casey could you please take a look? This part of the code
fails with the newer boost_1.74? Thanks!
It looks like the last version in git still fails to build.
===
ceph/src/common/async/completion.h: In instantiation of 'void
Processing commands for cont...@bugs.debian.org:
> tags 977243 -pending
Bug #977243 [src:ceph] ceph FTBFS with Boost 1.74
Removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977243
Processing control commands:
> tag -1 pending
Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js
symlink
Added tag(s) pending.
--
977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #977960 in node-jquery 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, 24 Dec 2020 13:18:29 +
with message-id
and subject line Bug#976430: fixed in freecad
0.19~pre1+git20201221.3b449e1ce9+dfsg1-2
has caused the Debian Bug report #976430,
regarding libfreecad-python3-0.19: missing Breaks+Replaces:
libfreecad-python3-0.18
to be marked as
Your message dated Thu, 24 Dec 2020 14:08:55 +0100
with message-id <20201224130855.gc12...@xanadu.blop.info>
and subject line Re: node-opencv: FTBFS on ppc64el: not ok 197 Error: Command
failed: node /<>/examples/motion-track.js terminate called after
throwing an instance of 'cv::Exception'
On 14/12/20 at 14:36 -0500, Reinhard Tartler wrote:
>
>
> > === RUN TestRuleAddAndLoad
> > seccomp_test.go:588: Syscall should have returned error code!
> > --- FAIL: TestRuleAddAndLoad (0.00s)
>
>
> Source code is here:
>
Hi Adam,
On 18/12/20 at 08:46 +0100, Adam Borowski wrote:
> Control: tags -1 + moreinfo unreproducible
>
> Hi Lucas!
>
> > On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote:
> > > Source: memkind
>
> > > During a rebuild of all packages in sid, your package failed to build
> > >
HI Nilesh
On Thu, 24 Dec 2020 at 10:48, Nilesh wrote:
>
> I can't seem to reproduce this, can you initiate a rebuild for this?
>
> I suspect if new apertium upload fixed this somehow. Attaching the log in any
> case.
Reproducible builds [1] shows apertium-kaz-tat is currently building
I've reproduced same issue on VM.
It seems that I have go perform `full-upgrade` that removes `user-manager`.
After that KDE desktop works.
If I try to install `user-manager` again, I get suggestion to remove whole
kde-plasma-dekstop & friends...
Processing control commands:
> reopen -1
Bug #977960 {Done: Xavier Guimard } [libjs-jquery] dangling
/usr/share/javascript/jquery/jquery.js symlink
'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.
Bug
Control: reopen -1
Control: found -1 3.5.1+dfsg+~3.5.5-2
$ ls -l /usr/share/nodejs/jquery/dist/
total 0
lrwxrwxrwx 1 root root 34 Dec 23 22:00 jquery.js ->
../../nodejs/jquery/dist/jquery.js
lrwxrwxrwx 1 root root 38 Dec 23 22:00 jquery.min.js ->
../../nodejs/jquery/dist/jquery.min.js
lrwxrwxrwx
Dear colleagues,
Thanks for reporting this! Unfortunately I got the reference to the bug only
from kodi tracker.d.o page. I will investigate the issue and upload the fix to
Git.
--
Vasyl Gello
==
Certified SolidWorks Expert
Mob.:+380 (98) 465 66
Your message dated Thu, 24 Dec 2020 11:04:13 +
with message-id
and subject line Bug#978001: fixed in snapcast 0.22.0+dfsg1-1
has caused the Debian Bug report #978001,
regarding snapcast: switch to default libboost-dev
to be marked as done.
This means that you claim that the problem has been
Package: libkwaylandserver5
Version: 5.20.4-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After today Sid upgrades my KDE desktop failed to fully load after login. I see
background and KDE spinner, but desktop does not appear.
I've found this in
On 2020-12-24 09:04:50 +0900, Norbert Preining wrote:
> Hi,
>
> > Control: severity -1 serious
>
> Pushing severity will not change the fact that the released version of
> Julia does not support llvm11 and cannot be built with it.
> As far as I see support for llvm11 is included in the 1.6.0
Your message dated Thu, 24 Dec 2020 09:34:00 +
with message-id
and subject line Bug#977901: fixed in chromium 87.0.4280.88-0.3
has caused the Debian Bug report #977901,
regarding chromium: Inconsistent SEGV
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> retitle -1 llvmlite: stop using llvm-toolchain-10
Bug #974778 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Bug #974824 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Changed Bug title to 'llvmlite: stop using llvm-toolchain-10' from
I can't seem to reproduce this, can you initiate a rebuild for this?
I suspect if new apertium upload fixed this somehow. Attaching the log in any
case.
sbuild (Debian sbuild) 0.79.1 (22 April 2020) on debian
+==+
|
Source: clfft
Version: 2.12.2-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
clfft is unable to migrate to testing due to autopkgtest regressions:
| autopkgtest [23:13:07]: test build-examples: [---
| cp: cannot stat '/usr/share/doc/libclfft-doc/examples/*': No such
Processing control commands:
> block 978000 by -1
Bug #978000 [src:boost1.71] boost1.71: should not be part of bullseye
978000 was not blocked by any bugs.
978000 was not blocking any bugs.
Added blocking bug(s) of 978000: 978001
--
978000:
Source: snapcast
Version: 0.19.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Control: block 978000 by -1
snapcast currently has build dependency on libboost1.71-dev but we are
trying to remove boost 1.71 from bullseye. So, please switch to
the unversioned libboost-dev which currently
Source: boost1.71
Version: 1.71.0-7
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
With boost 1.74 as the default, let's make sure that boost 1.71 is not
part of bullseye. Once the remanining reverse dependencies are fixed,
please reassign this bug to ftp.debian.org and get it removed.
Hello,
Yes, I gave you the wrong file. Just uploaded the correct one under the
same url.
Michel Le Bihan
Le mercredi 23 décembre 2020 à 23:01 -0600, Boyd Stephen Smith Jr. a
écrit :
> On Wednesday, December 23, 2020 4:16:19 PM CST Michel Le Bihan wrote:
> > Could you please test if you are
56 matches
Mail list logo
