Your message dated Thu, 24 Dec 2020 07:48:25 +
with message-id
and subject line Bug#976487: fixed in grpc-java 1.26.0+ds-1
has caused the Debian Bug report #976487,
regarding grpc-java: FTBFS: CensusStatsModule.java:21: error: cannot find symbol
to be marked as done.
This means that you
Your message dated Thu, 24 Dec 2020 05:49:08 +
with message-id
and subject line Bug#976955: fixed in ts-node 9.1.1-2
has caused the Debian Bug report #976955,
regarding FTBFS: semver not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tag -1 pending
Hello,
Bug #976955 in ts-node 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 #976955 [ts-node] FTBFS: semver not found
Added tag(s) pending.
--
976955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 977357 + ftbfs
Bug #977357 [src:libgdf] libgdf ftbfs on s390x (test failures)
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977357:
Control: tag -1 pending
Hello,
Bug #975174 in librtr 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 #975174 [src:librtr] librtr: FTBFS: dpkg-gensymbols: error: some symbols or
patterns disappeared in the symbols file: see diff output below
Added tag(s) pending.
--
975174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975174
Debian Bug
Hi Alexander,
On Tue, Dec 22, 2020 at 07:57:15PM +0300, Alexander Gerasiov wrote:
> On Sun, 20 Dec 2020 11:50:42 +0200
> Adrian Bunk wrote:
> > this is a regression in 1.2.1+dfsg-2 that is currently in both
> > buster-security (which was done on top of 1.2.1+dfsg-2 that
> > introduced the
Your message dated Thu, 24 Dec 2020 04:48:26 +
with message-id
and subject line Bug#974779: fixed in julia 1.5.3+dfsg-3
has caused the Debian Bug report #974779,
regarding julia: Please upgrade to llvm-toolchain-11
to be marked as done.
This means that you claim that the problem has been
Control: tag -1 pending
Hello,
Bug #974779 in julia 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 #974779 [julia] julia: Please upgrade to llvm-toolchain-11
Added tag(s) pending.
--
974779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> Either you go back to -9 or move to -11
I will try to go to -9
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 DC13
Thanks Houben, I appreciate your efforts!
Sam
Quoting Rens Houben (2020-12-22 16:07:00)
> Hello,
>
> I've come across the same bug while trying to set up a new service at work.
>
> After some digging (we've currently got a mishmash of Jessie and Buster
> systems, not all of them have been
On Fri, 18 Dec 2020 19:43:40 +0100, Paul Gevers wrote:
> On 18-12-2020 16:47, Dominic Hargreaves wrote:
> > It sounds like we should file a bug with the release team for
> > manual removal from testing instead in this case? What makes the package
> > "key" OOI? The package is provided by perl so
Processing commands for cont...@bugs.debian.org:
> retitle 977647 5.10.2 Debian kernel does not boot on amd64 with btrfs rootfs
Bug #977647 [src:linux] 5.10.1 Debian kernel does not boot on amd64 with btrfs
rootfs
Changed Bug title to '5.10.2 Debian kernel does not boot on amd64 with btrfs
Processing commands for cont...@bugs.debian.org:
> fixed 948040 2.4.2-1
Bug #948040 {Done: Nilesh Patra } [src:brian] brian: FTBFS
with python3.8
Marked as fixed in versions brian/2.4.2-1.
> found 974779 1.5.3+dfsg-2
Bug #974779 [julia] julia: Please upgrade to llvm-toolchain-11
Marked as found
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 branch of
Julia, but that is probbly far off, and definitely not ready
Your message dated Wed, 23 Dec 2020 23:34:08 +
with message-id
and subject line Bug#944714: fixed in moonshot-trust-router 3.5.4+1
has caused the Debian Bug report #944714,
regarding moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7
to be marked as done.
This means that you
Your message dated Thu, 24 Dec 2020 00:16:55 +0100
with message-id
and subject line Re: Bug#966770: opencv: Unversioned Python removal in
sid/bullseye
has caused the Debian Bug report #966770,
regarding opencv: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> notfound 966770 4.3.0+dfsg-1
Bug #966770 [src:opencv] opencv: Unversioned Python removal in sid/bullseye
No longer marked as found in versions opencv/4.3.0+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Source: os-autoinst
Version: 4.6.1604525166.912dfbd-0.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
os-autoinst FTBFS on i386:
| 3: ./29-backend-generalhw.t . ok
| 3:
| 3: #
Processing commands for cont...@bugs.debian.org:
> reassign 977988 src:kimageannotator
Bug #977988 [kde-spectacle] /usr/bin/spectacle: does not start
(libkImageAnnotator.so.0.3.2 not found)
Bug reassigned from package 'kde-spectacle' to 'src:kimageannotator'.
No longer marked as found in
reassign 977988 src:kimageannotator
forcemerge 977649 977988
thanks
In data mercoledì 23 dicembre 2020 22:26:13 CET, Dominik George ha scritto:
> Package: kde-spectacle
> Version: 20.12.0-1
> Severity: grave
> File: /usr/bin/spectacle
> Justification: renders package unusable
>
> After a recent
Hello,
I opened a merge request, but merging all branches into your repo might cause
issues in the upstream branch in the future due to the merge commits. Instead,
it will be best to pull all branches from my repo into branches of your repo,
but without adding merge commits or at least without
Hello,
My build just finished. Could you please test if you are still getting
this issue in https://lebihan.pl/files/chromium.tar.gz ?
Michel Le Bihan
Your message dated Wed, 23 Dec 2020 22:54:39 +0100
with message-id
and subject line Re: insighttoolkit4: FTBFS in sid
has caused the Debian Bug report #977986,
regarding insighttoolkit4: FTBFS in sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
As far as I know, the blocker for fastbook is android-platform-art. It
has a crazy upstream build system. Right now, it almost building, but
the build is currently dying on this error:
clang++ -o runtime/compiler_filter.o -g -O2
-fdebug-prefix-map=/build/android-platform-art-10.0.0+r36=.
Package: kde-spectacle
Version: 20.12.0-1
Severity: grave
File: /usr/bin/spectacle
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After a recent update, spectacle stoppede working, and errors out on start with:
spectacle: error while loading shared
Processing commands for cont...@bugs.debian.org:
> block 977567 by 895837
Bug #977567 [wnpp] ITP: jruby-utils-clojure -- A library for creating and
interacting with a pool of JRuby instances in Clojure
977567 was not blocked by any bugs.
977567 was not blocking any bugs.
Added blocking bug(s) of
Processing commands for cont...@bugs.debian.org:
> tags 977986 + ftbfs
Bug #977986 [src:insighttoolkit4] insighttoolkit4: FTBFS in sid
Added tag(s) ftbfs.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
977986:
Your message dated Wed, 23 Dec 2020 21:19:14 +
with message-id
and subject line Bug#977960: fixed in node-jquery 3.5.1+dfsg+~3.5.5-2
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
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:
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
Source: insighttoolkit4
Version: 4.13.3withdata-dfsg1-3
Severity: serious
Hello, looks like itk4 ftbfs in sid because of test failures (at least on
amd64).
You can download the build log here:
http://debomatic-amd64.debian.net/distribution#unstable/insighttoolkit4/4.13.3withdata-dfsg1-3/buildlog
Processing control commands:
> severity -1 serious
Bug #974779 [julia] julia: Please upgrade to llvm-toolchain-11
Severity set to 'serious' from 'important'
--
974779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 23 Dec 2020 20:19:38 +
with message-id
and subject line Bug#975844: fixed in sphinx-tabs 1.2.1+ds-3
has caused the Debian Bug report #975844,
regarding sphinx-tabs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.8 3.9" returned exit
Hello,
I made
https://salsa.debian.org/mimi8/chromium/-/commit/6d21c52698147ca072d223e4e6c2854053319531
and still am waiting for it to build. Is it OK?
Michel Le Bihan
Le mercredi 23 décembre 2020 à 14:13 -0600, Boyd Stephen Smith Jr. a
écrit :
> On Wednesday, December 23, 2020 4:30:48 AM
On Wednesday, December 23, 2020 4:30:48 AM CST Boyd Stephen Smith Jr. wrote:
> On Wednesday, December 23, 2020 4:19:43 AM CST Michel Le Bihan wrote:
> > The Debian patch for #963548
> > https://salsa.debian.org/mimi8/chromium/-/blob/ece23b4ca107cd968ac9a40
> > 9f
> >
Processing commands for cont...@bugs.debian.org:
> block 976493 by 977979
Bug #976493 [src:ruby-psych] ruby-psych: FTBFS: NameError: undefined method
`default_specifications_dir' for class `#'
976493 was not blocked by any bugs.
976493 was not blocking any bugs.
Added blocking bug(s) of 976493:
block 976493 by 977979
thanks
This is caused by a bug in jruby and can probably by fixed by exporting
the DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable in d/rules.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org
⠈⠳⣄
OpenPGP_signature
Your message dated Wed, 23 Dec 2020 19:34:51 +
with message-id
and subject line Bug#977229: fixed in kcollectd 0.11.99.0-1.1
has caused the Debian Bug report #977229,
regarding kcollectd FTBFS with Boost 1.74
to be marked as done.
This means that you claim that the problem has been dealt
Package: jruby
Version: 9.1.17.0-3
Severity: grave
Dear maintainers,
It seems jruby fails to run without declaring the
DEBIAN_DISABLE_RUBYGEMS_INTEGRATION environment variable:
jruby -e "puts 'Hello World'"
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective
Your message dated Wed, 23 Dec 2020 19:18:31 +
with message-id
and subject line Bug#977265: fixed in dds 2.9.0-8.1
has caused the Debian Bug report #977265,
regarding dds ftbfs with boost1.74
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 23 Dec 2020 23:10:02 +0530
with message-id
and subject line Re: brian: FTBFS with python3.8
has caused the Debian Bug report #948040,
regarding brian: FTBFS with python3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing control commands:
> severity -1 normal
Bug #976924 [src:golang-github-hashicorp-raft] golang-github-hashicorp-raft:
FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd
obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160
github.com/hashicorp/raft
Hello,
On Wed, Dec 23, 2020 at 10:12 PM Roger Shimizu wrote:
> On Wed, Dec 23, 2020 at 5:38 AM Hans-Christoph Steiner
> wrote:
> >
> > Thanks for jumping in Roger! I reviewed it with cdesai, and we thought
> > those libraries were not used on the "host" version, only when built as
> > part of
Control: severity -1 normal
Looking at the logs, it really looks like timeouts in the testsuite. We could
disable the tests on problematic architectures, patches welcome. As a
workaround, I'd suggest building the package with export
DEB_BUILD_OPTIONS=notest. With this, I'm downgrading the
On Wed, Dec 23, 2020 at 5:38 AM Hans-Christoph Steiner wrote:
>
> Thanks for jumping in Roger! I reviewed it with cdesai, and we thought
> those libraries were not used on the "host" version, only when built as
> part of Android OS. I do think libfec would be useful if someone wants
> to
Your message dated Wed, 23 Dec 2020 16:33:39 +
with message-id
and subject line Bug#976509: fixed in golang-github-shirou-gopsutil 2.19.11-4
has caused the Debian Bug report #976509,
regarding golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd
obj-aarch64-linux-gnu && go test
Your message dated Wed, 23 Dec 2020 18:18:30 +0200
with message-id
and subject line
has caused the Debian Bug report #977968,
regarding Fwd: cinnamon keep crashing after latest migration to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> tag -1 pending
Bug #976509 [src:golang-github-shirou-gopsutil] golang-github-shirou-gopsutil:
FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p
4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu
Control: close
i see
thank you for telling me
i will wait for the update i will close this bug
Control: tag -1 pending
Hello,
Bug #976509 in golang-github-shirou-gopsutil 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, 23 Dec 2020 15:33:26 +
with message-id
and subject line Bug#977502: fixed in libpod 2.2.1+dfsg1-1
has caused the Debian Bug report #977502,
regarding podman,golang-github-containers-common: both ship
/usr/share/man/man5/containers-mounts.conf.5.gz
to be marked as
I have the same issue. Only Alt + F2 and keyboard shortcuts work.
The (cinnamon) menu doesn't do anything.
--
Regards,
Max Minenko
Il 23/12/2020 15:27, Mina Morcose Farage ha scritto:
> i also tried clean testing install on virtualbox to element any
> possibility of drive or package conflict and same error happened
should be the same of bug 977890, "solved" but need to wait new build
migrating to testing for solves it;
i also tried clean testing install on virtualbox to element any possibility
of drive or package conflict and same error happened
Processing commands for cont...@bugs.debian.org:
> block 976397 with 977248 976911
Bug #976397 [release.debian.org] transition: opencv
976397 was not blocked by any bugs.
976397 was not blocking any bugs.
Added blocking bug(s) of 976397: 976911 and 977248
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> severity 977248 serious
Bug #977248 [src:php-facedetect] FTBFS against opencv 4.5.0
Severity set to 'serious' from 'normal'
> tags 977248 + ftbfs sid bullseye
Bug #977248 [src:php-facedetect] FTBFS against opencv 4.5.0
Added tag(s) sid, ftbfs,
Package: cinnamon
Version: 4.6.7-1
Severity: critical
after updating to this version which is the latest version in testing it
boot up but after trying to open any program it go to fallback mode and
offer a restart and after the restart if fail again and so on it closed
loop which make the
Your message dated Wed, 23 Dec 2020 13:49:06 +
with message-id
and subject line Bug#977873: fixed in pmix 4.0.0~rc1-2
has caused the Debian Bug report #977873,
regarding libpmix2: broken library symlink
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 23 Dec 2020 13:23:17 +
with message-id
and subject line Bug#973114: fixed in python-future 0.18.2-5
has caused the Debian Bug report #973114,
regarding python-future: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.8" returned
Le 23/12/2020 à 12:34, Matthias Klose a écrit :
> On 12/23/20 12:19 PM, Xavier wrote:
>> Control: tags -1 + moreinfo
>>
>> Le 23/12/2020 à 12:06, Matthias Klose a écrit :
>>> Package: libjs-jquery
>>> Version: 3.5.1+dfsg+~3.5.5-1
>>> Severity: serious
>>> Tags: sid bullseye
>>>
>>> There's at
Processing control commands:
> severity -1 important
Bug #977962 [webpack,node-compression-webpack-plugin] webpack: mkdirp > 1 patch
seems broken
Severity set to 'important' from 'serious'
> retitle -1 node-compression-webpack-plugin: enable test
Bug #977962
Control: severity -1 important
Control: retitle -1 node-compression-webpack-plugin: enable test
Le 23/12/2020 à 13:27, Pirate Praveen a écrit :
> Package: webpack,node-compression-webpack-plugin
> Version: 4.43.0-6
> Severity: serious
>
> To reproduce this issue,
>
> run
> jest --ci
Package: webpack,node-compression-webpack-plugin
Version: 4.43.0-6
Severity: serious
To reproduce this issue,
run
jest --ci test/CompressionPlugin.test.js
in node-compression-webpack-plugin
● CompressionPlugin › should work and show compress assets in stats
TypeError: callback must be a
Hey,
parallel to Michel's very nice work to get chromium into unstable
(thanks to him!), I tried to build the current version in a buster
chroot. At the moment I struggle that there seems a difference how
SFINAE[1] in a special case [2] is handled different between buster's
and unstable's clang
Hi all,
now that sid has seen an update of Chromium to v87 (hooray and thanks
everybody!) does anybody know it there's activity or plans towards
updating chromium in Debian stable?
Chromium from sid is not installable in Debian stable due to
Depends: libc6 (>= 2.29)
whereas stable has
Processing control commands:
> tags -1 - moreinfo
Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js
symlink
Removed tag(s) moreinfo.
--
977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 - moreinfo
On 12/23/20 12:19 PM, Xavier wrote:
> Control: tags -1 + moreinfo
>
> Le 23/12/2020 à 12:06, Matthias Klose a écrit :
>> Package: libjs-jquery
>> Version: 3.5.1+dfsg+~3.5.5-1
>> Severity: serious
>> Tags: sid bullseye
>>
>> There's at least one dangling
On 12/23/20 12:19 PM, Xavier wrote:
> Control: tags -1 + moreinfo
>
> Le 23/12/2020 à 12:06, Matthias Klose a écrit :
>> Package: libjs-jquery
>> Version: 3.5.1+dfsg+~3.5.5-1
>> Severity: serious
>> Tags: sid bullseye
>>
>> There's at least one dangling /usr/share/javascript/jquery/jquery.js
Quoting Rens Houben (2020-12-22 18:35:52)
> Okay, this is quick-and-dirty because I didn't have a great deal of time and
> I'm not /that/ great with systemd service files to begin with.
>
> ---
> [Unit]
> Description=uWSGI Emperor
> After=syslog.target
>
> [Service]
>
Processing control commands:
> tags -1 + moreinfo
Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js
symlink
Added tag(s) moreinfo.
--
977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
Le 23/12/2020 à 12:06, Matthias Klose a écrit :
> Package: libjs-jquery
> Version: 3.5.1+dfsg+~3.5.5-1
> Severity: serious
> Tags: sid bullseye
>
> There's at least one dangling /usr/share/javascript/jquery/jquery.js symlink
>
> $ dpkg -S
Package: libjs-jquery
Version: 3.5.1+dfsg+~3.5.5-1
Severity: serious
Tags: sid bullseye
There's at least one dangling /usr/share/javascript/jquery/jquery.js symlink
$ dpkg -S /usr/share/javascript/jquery/jquery.js
libjs-jquery: /usr/share/javascript/jquery/jquery.js
$ ls -l
Your message dated Wed, 23 Dec 2020 11:04:07 +
with message-id
and subject line Bug#967232: fixed in xscreensaver 5.45+dfsg1-1
has caused the Debian Bug report #967232,
regarding xscreensaver: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Wed, 23 Dec 2020 10:48:42 +
with message-id
and subject line Bug#973121: fixed in cairocffi 1.2.0-1
has caused the Debian Bug report #973121,
regarding cairocffi: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.9 3.8" returned exit code 13
to be marked
On Wednesday, December 23, 2020 4:19:43 AM CST Michel Le Bihan wrote:
> The Debian patch for #963548
> https://salsa.debian.org/mimi8/chromium/-/blob/ece23b4ca107cd968ac9a409f
> 40eb11edf8a0266/debian/patches/fixes/serviceworker-double-destruction.patch
> is clearly in upstream 87.0.4280.88:
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548 also has a fix
(https://salsa.debian.org/chromium-team/chromium/-/commit/
b904fa41d40b967dcc8f6984db52f7a2f6a2c83d) related to the cyclic
SerivceWorker.*ObjectHost objects and their deletion.
The chromium team noticed the same thing:
Source: sigviewer
Version: 0.6.4-1
Severity: serious
Tags: ftbfs
sigviewer fails to build from source in unstable. A build ends with:
| g++ -Wl,-z,relro -Wl,-z,now -o bin/release/sigviewer tmp/release/data_block.o
tmp/release/exception.o tmp/release/fixed_data_block.o tmp/release/math_utils.o
Your message dated Wed, 23 Dec 2020 10:24:45 +
with message-id
and subject line re: chromium: Received signal 11 SEGV_ACCERR 04c03193.
can't load pages and extensions
has caused the Debian Bug report #965960,
regarding chromium 83.0.4103.116-3+b1 crash immediately, SEGV_MAPERR
to be
Your message dated Wed, 23 Dec 2020 10:24:45 +
with message-id
and subject line re: chromium: Received signal 11 SEGV_ACCERR 04c03193.
can't load pages and extensions
has caused the Debian Bug report #965960,
regarding chromium: Received signal 11 SEGV_ACCERR 04c03193. can't load
Hello,
The Debian patch for #963548
https://salsa.debian.org/mimi8/chromium/-/blob/ece23b4ca107cd968ac9a409f40eb11edf8a0266/debian/patches/fixes/serviceworker-double-destruction.patch
is clearly in upstream 87.0.4280.88:
On Wednesday, December 23, 2020 3:49:06 AM CST Boyd Stephen Smith Jr. wrote:
> On Wednesday, December 23, 2020 2:38:32 AM CST Boyd Stephen Smith Jr. wrote:
> > I got a crash (attached)
>
> Looks like https://bugs.chromium.org/p/chromium/issues/detail?id=1135070 to
> me, which has a fix, but I
On Wednesday, December 23, 2020 2:38:32 AM CST Boyd Stephen Smith Jr. wrote:
> I got a crash (attached)
Looks like https://bugs.chromium.org/p/chromium/issues/detail?id=1135070 to
me, which has a fix, but I haven't yet figured out what release(s) the fix
made it into.
--
Boyd Stephen Smith
On Tuesday, December 22, 2020 11:22:21 PM CST Boyd Stephen Smith Jr. wrote:
> I'll have to play around with disabling extensions to see which one(s) cause
> a crash within 30 minutes. Super annoying since I do use every one of them
> literally every day. :(
Looks like maybe Proxy SwitchyOmega
Hello.
Here is the full history, just in case.
mipsel mips64el
18-4 OK OK
19.2-1 fails OK
19.2-2 fails OK
19.2-3 -mxgot OK OK
20.0-1 -mxgot fails fails
21.0.0-1
Your message dated Wed, 23 Dec 2020 09:21:03 +0100
with message-id <01a0f3a0-b50a-84f6-13a5-bcd070f6f...@debian.org>
and subject line Re: Bug#977920: python3-distutils and python3-lib2to3 depend
on unavailable version of python3:any
has caused the Debian Bug report #977920,
regarding
88 matches
Mail list logo
