Your message dated Tue, 11 Aug 2020 08:10:30 +0200
with message-id <159712623030.814989.15967189281065842851@localhost>
and subject line Re: Bug#968217: python is priority:standard but not installable
has caused the Debian Bug report #968217,
regarding python is priority:standard but not installabl
A smiliar issue was reported for mapproxy in #966979, which was not an
issue in mapproxy but in sphinx, and fixed in sphinx (2.4.3-5).
I have not tested the build of this package, but the dh_sphinxdoc issue
is mostl likely fixed with sphinx (2.4.3-5) as well.
Kind Regards,
Bas
--
GPG Key ID:
Processing commands for cont...@bugs.debian.org:
> affects 959828 -src:e17
Bug #959828 [systemctl] systemctl: `Provides: systemd`, but doesn't provide
what systemd does
Removed indication that 959828 affects src:e17
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> affects 966979 src:behave
Bug #966979 {Done: Dmitry Shachnev } [src:sphinx] mapproxy:
FTBFS: dh_sphinxdoc: error:
debian/mapproxy-doc/usr/share/doc/mapproxy/html/search.html does not load
searchindex.js
Added indication that 966979 affects src:
Processing commands for cont...@bugs.debian.org:
> notfound 966947 behave/1.2.6-2
Bug #966947 [src:behave] behave: FTBFS: dh_sphinxdoc: error:
debian/python-behave-doc/usr/share/doc/python-behave-doc/html/search.html does
not load searchindex.js
No longer marked as found in versions behave/1.2.6
On 8/11/20 2:04 AM, Johannes 'josch' Schauer wrote:
> Package: python
> Version: 2.7.17-2
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> the python package is currently uninstallable in Debian unstable:
yes
> Maybe this is intentional because of the imminent removal of
I have reached out to the gnumeric folks; they say a new version
including python3 support should be out in a couple of months. See
https://gitlab.gnome.org/GNOME/gnumeric/-/issues/419
[]'s,
Francisco M Neto
signature.asc
Description: This is a digitally signed message part
Package: python3-statsmodels
Version: 0.11.1-4
Severity: serious
arm64 fail in TestZeroInflatedModel_probit.test_fit_regularized:
https://buildd.debian.org/status/fetch.php?pkg=statsmodels&arch=arm64&ver=0.11.1-4&stamp=1597051632&raw=0
https://ci.debian.net/packages/s/statsmodels/testing/arm64/
Package: python3-pandas
Version: 0.25.3+dfsg2-4
Severity: serious
One test fails on i386 with a 1-in-last-place difference, probably due
to different rounding (x87 extra precision?).
https://buildd.debian.org/status/fetch.php?pkg=pandas&arch=i386&ver=0.25.3%2Bdfsg2-4&stamp=1597048961&raw=0
Package: python
Version: 2.7.17-2
Severity: grave
Justification: renders package unusable
Hi,
the python package is currently uninstallable in Debian unstable:
output-version: 1.2
report:
-
package: python
version: 2.7.17-2
architecture: amd64
status: broken
Your message dated Mon, 10 Aug 2020 23:03:35 +
with message-id
and subject line Bug#968184: fixed in calculix-cgx 2.17+dfsg-2
has caused the Debian Bug report #968184,
regarding autopkgtest is infinitely outputting "ERROR: not valid"
to be marked as done.
This means that you claim that the pr
Upstream has moved to python3 in commit 8e2f442e[1]. This should be
just a matter of updating the packaging and dependencies, but I'm not
familiar with the package itself (although I'm a regular user of
gnumeric). I'd be willing to help if needed.
[1]
https://gitlab.gnome.org/GNOME/gnumeric/-/com
Control: tags -1 pending
Greetings,
I verified it is safe to remove zlib1g-dev from the biobambam2
package dependencies by running the autopkgtest suite with the
patched libmaus2, which now pulls zlib1g as dependency of
libmaus2-2. The routine-update also pulled the libmaus patch
level 2.0.743.
Processing control commands:
> tags -1 pending
Bug #966470 [src:libmaus2] ZlibInterface dlopens libz.so rather than libz.so.1
Added tag(s) pending.
--
966470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: scheme48
Version: 1.9.2-1
Severity: serious
Justification: missing source
While looking into a build issue with scheme48, I was looking for the
source of S48_DETERMINE_BITS_PER_BYTE as referenced in configure.in.
Unfortunately, I couldn't find the relevant source. Am I missing
something?
Your message dated Mon, 10 Aug 2020 23:40:13 +0200
with message-id <20200810214013.ga22...@ramacher.at>
and subject line Re: Bug#968066: haskell-hgettext: autopkgtest fails with newer
version of ghc
has caused the Debian Bug report #968066,
regarding haskell-hgettext: autopkgtest fails with newer
On Sun, 2020-08-09 at 20:22 -0400, Peter Colberg wrote:
> Please feel free to go ahead with backporting acmetool and needed
> golang dependencies to buster.
Thanks for the approval, Peter! We'll backport and follow-up with the
go-team if there are issues.
Cheers,
Ralph
signature.asc
Descriptio
Your message dated Mon, 10 Aug 2020 20:22:38 +
with message-id
and subject line Bug#957086: fixed in chordii 4.5.3+repack-0.2
has caused the Debian Bug report #957086,
regarding chordii: ftbfs with GCC-10
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:
> found 965218 3.0.0-1
Bug #965218 [ruby-sentry-raven] ruby-sentry-raven: FTBFS with rails 6 in
experimental
Marked as found in versions ruby-sentry-raven/3.0.0-1.
> affects 966470 + src:biobambam2
Bug #966470 [src:libmaus2] ZlibInterface dlopens l
On Sun, Aug 9, 2020 at 23:54, Pirate Praveen
wrote:
From the previous comment on this bug, it appears to be caused by
ruby-google-protobuf and ruby-grpc.
Can you try the new gitlab version I just uploaded?
I can also reproduce the crash now. Try with older protobuf/grpc as a
workaround
Package: podman
Version: 2.0.4+dfsg2-1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
Installing podman or upgrading from 2.0.2+dfsg1-3 to 2.0.3+dfsg1-1
(transcript below, re-testing with 2.0.4
* What was the outcome of this ac
Processing commands for cont...@bugs.debian.org:
> reopen 966470
Bug #966470 {Done: =?utf-8?q?=C3=89tienne_Mollier?=
} [biobambam2] biobambam2: autopkgtest failures:
Segmentation fault bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam
'reopen' may be inappropriate when a bug has been closed
Control: tags 957761 + patch
Control: tags 957761 + pending
Dear maintainer,
I've prepared an NMU for restartd (versioned as 0.2.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru restartd-0.2.3/debian/changelog restartd-0.2.3/debi
Processing control commands:
> tags 957761 + patch
Bug #957761 [src:restartd] restartd: ftbfs with GCC-10
Added tag(s) patch.
> tags 957761 + pending
Bug #957761 [src:restartd] restartd: ftbfs with GCC-10
Added tag(s) pending.
--
957761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957761
D
Hi John,
John Marshall, on 2020-08-10 11:04:05 +:
> Étienne Mollier wrote:
> > After appending the zlib1g-dev package to dependencies of the
> > biobambam2 package,
>
> It is in fact libmaus2 that is dlopening "libz.so", so it would be better to
> add to the dependencies of that package, whi
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:nfstrace
> # 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
Se
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:ruby-faye
> # 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
S
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:imagemagick
> # 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 commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:printrun
> # 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
Se
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:verilator
> # 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
S
Your message dated Mon, 10 Aug 2020 17:48:43 +
with message-id
and subject line Bug#968013: fixed in swi-prolog 8.2.1+dfsg-2
has caused the Debian Bug report #968013,
regarding swi-prolog: time bomb in swi-prolog-test, and failing autopkgtest
to be marked as done.
This means that you claim th
Your message dated Mon, 10 Aug 2020 16:03:35 +
with message-id
and subject line Bug#968120: fixed in castle-game-engine 6.4+dfsg1-5
has caused the Debian Bug report #968120,
regarding castle-game-engine: FTBFS with fpc 3.2.0
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> # issue publicliy accessible
> forwarded 961302 https://gitlab.com/sane-project/backends/-/issues/279
Bug #961302 {Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= }
[src:sane-backends] sane-backends 1.0.30 released with security fixes
Set Bug forwa
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
As suggested by Andreas, I've been in touch with the FTP team.
Following this discussion, I've uploaded orthanc-1.7.2+dfsg-3 to
unstable, that doesn't contain the NEW changes.
For reference, here are the two changesets to revert once
"liborthancframework-dev" and "liborthancframework1" subpac
Your message dated Mon, 10 Aug 2020 14:50:02 +
with message-id
and subject line Bug#957649: fixed in osmo-bsc 1.3.0-3
has caused the Debian Bug report #957649,
regarding osmo-bsc: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Your message dated Mon, 10 Aug 2020 14:49:56 +
with message-id
and subject line Bug#966655: fixed in orthanc 1.7.2+dfsg-3
has caused the Debian Bug report #966655,
regarding orthanc: using tzdata but missing dependency on it?
to be marked as done.
This means that you claim that the problem ha
Your message dated Mon, 10 Aug 2020 14:50:08 +
with message-id
and subject line Bug#957655: fixed in osmo-sgsn 1.3.0-3
has caused the Debian Bug report #957655,
regarding osmo-sgsn: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Control: tag -1 pending
Hello,
Bug #966655 in orthanc 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:
https://salsa.debian.org/med-team/orthanc/-/commit/baef575e15d0a86ec5b36d2d95b50ae4
Processing control commands:
> tag -1 pending
Bug #966655 [src:orthanc] orthanc: using tzdata but missing dependency on it?
Added tag(s) pending.
--
966655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #931566 [apt] Don't complain about suite changes
(Acquire::AllowReleaseInfoChange::Suite should be "true")
Added tag(s) pending.
--
931566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931566
Debian Bug Tracking System
Contact ow...@bugs.de
Control: tag -1 pending
Hello,
Bug #931566 in apt 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:
https://salsa.debian.org/apt-team/apt/-/commit/64b45e294f0c6931a9b57ae6cc99ecded8f6a2d3
Processing commands for cont...@bugs.debian.org:
> severity 932659 important
Bug #932659 [nodejs] node: modules are not getting detected in a fresh sid
chroot environment
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
932
Processing commands for cont...@bugs.debian.org:
> forwarded 956285 https://github.com/arvidn/libtorrent/issues/4951
Bug #956285 [libtorrent-rasterbar] Problems identified in debian/copyright
Set Bug forwarded-to-address to
'https://github.com/arvidn/libtorrent/issues/4951'.
> thanks
Stopping pro
Processing commands for cont...@bugs.debian.org:
> tags 968157 + ftbfs
Bug #968157 [src:haskell-cborg] src:haskell-cborg: testsuite fails due to bus
errors on armhf
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
968157: https://bugs.debian.or
Processing control commands:
> severity -1 serious
Bug #968184 [src:calculix-cgx] autopkgtest is infinitely outputting "ERROR: not
valid"
Ignoring request to change severity of Bug 968184 to the same value.
--
968184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968184
Debian Bug Tracking
Control: severity -1 serious
On Mon, Aug 10, 2020 at 11:32:42AM +0100, Iain Lane wrote:
> I've pinged the Debian CI people, will report back & upgrade the
> severity if they confirm it is happening on Debian too.
Yeah, same here
https://ci.debian.net/data/autopkgtest/testing/arm64/c/calculix
Processing control commands:
> severity -1 serious
Bug #968184 [src:calculix-cgx] autopkgtest is infinitely outputting "ERROR: not
valid"
Severity set to 'serious' from 'normal'
--
968184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968184
Debian Bug Tracking System
Contact ow...@bugs.deb
Package: src:dh-python
Version: 4.20200804
Severity: serious
Tags: sid bullseye patch
The dh-python autopkg tests fail, still needing the unversioned python binary.
Please adjust those, or disable those as done already by Stefano.
patch at
https://patches.ubuntu.com/d/dh-python/dh-python_4.202008
Processing control commands:
> tags -1 + patch
Bug #968046 [dh-python] dh-python: missing Breaks+Replaces: python2 (<< 2.7.18)
Added tag(s) patch.
--
968046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
the break against python is wrong, or at least unnecessary. The files shipped in
python2 in buster.
diff -Nru dh-python-4.20200804/debian/changelog
dh-python-4.20200804.1/debian/changelog
--- dh-python-4.20200804/debian/changelog 2020-08-04 10:10:12.0
+020
Your message dated Mon, 10 Aug 2020 12:03:42 +
with message-id
and subject line Bug#957237: fixed in fteqcc 3343+svn3400-4
has caused the Debian Bug report #957237,
regarding fteqcc: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Severity: important
Tags: moreinfo
Le mar. 17 mars 2020 à 14:45, Josh de Kock a écrit :
>
> Hi,
>
> This still occurs for me. I have a armhf chroot of Sid. It seems to be
> using a node path relative to the current directory (as far as I can
> tell). These paths should probably be /usr prefixed
Your message dated Mon, 10 Aug 2020 12:03:28 +
with message-id
and subject line Bug#957019: fixed in atlc 4.6.1-2.1
has caused the Debian Bug report #957019,
regarding atlc: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Étienne Mollier wrote:
> I had a look at the autopkgtest failure affecting biobambam2,
> and since these segmentation faults were showing up only in my
> autopkgtest environment, and not when using the package directly
> on my system, it felt like a missing dependency. So I trapped
> system calls
Your message dated Mon, 10 Aug 2020 11:18:25 +
with message-id
and subject line Bug#867666: fixed in curlpp 0.8.1-2.1
has caused the Debian Bug report #867666,
regarding libcurlpp-dev should depend on libcurl-dev
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 10 Aug 2020 13:13:03 +0200
with message-id <122e29db-679a-ad38-0501-bcba0a227...@debian.org>
and subject line Re: python-pam: Unversioned Python removal in sid/bullseye
has caused the Debian Bug report #967203,
regarding python-pam: Unversioned Python removal in sid/bullseye
Package: python3-rgain3
Version: 1.0.0-1
Severity: serious
Justification: maintainer says so
Tags: upstream
Forwarded: https://github.com/chaudum/rgain/issues/29
Upstream changes in rgain3 have broken the import ABI. This doesn't mean
anything for the replaygain and collectiongain CLI tools, but w
Package: libopenmpi3
Followup-For: Bug #965352
mpi4py upstream (Lisandro Dalcin) suggests in the short term to skip
the failing mpi4py tests for openmpi 4.0.4 (the failing tests are in
test_rma.py and test_rma_nb.py, and also one in test_win.py)
Lisandro suggests also it could be helpful for catc
AFAICT lxc-4.0.4 got rid of security_context_t:
commit 15d82dfe4f7900be54e06b6ca0a79321ee2a9b34
Author: Christian Brauner
Date: Sat Jul 25 11:36:46 2020 +0200
selinux: remove security_context_t usage as it's deprecated
Link: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1888705
Processing control commands:
> fixed -1 2.17+dfsg-1
Bug #957063 [src:calculix-cgx] calculix-cgx: ftbfs with GCC-10
Marked as fixed in versions calculix-cgx/2.17+dfsg-1.
> close -1
Bug #957063 [src:calculix-cgx] calculix-cgx: ftbfs with GCC-10
Marked Bug as done
--
957063: https://bugs.debian.org
control: fixed -1 2.17+dfsg-1
control: close -1
We can consider it "fixed" in the new release
G.
On Fri, 17 Apr 2020 10:57:34 + Matthias Klose wrote:
> Package: src:calculix-cgx
> Version: 2.11+dfsg-1
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ft
I am using LXC 4.0.2 on about 25 systems without problems. None of these
hosts does nested virtualization, though.
Nested virtualization and cgroups vs cgroups2 is a *highly* complex issue.
Can you reproduce this problem outside of your Docker setup? I wouldn't
like to see LXC dropped for Bullsey
A fix for compiling paraview 5.7.0-4 with gcc10 can be found in bug
#959387 [1], esp. [2].
Ref.:
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959387
[2]
https://git.inf.h-brs.de/jmeng2m/debian-package-paraview/-/commit/35d8cae30d4e9d1c6da980f2b359b428a5beea89
signature.asc
Description
Your message dated Mon, 10 Aug 2020 10:03:50 +
with message-id
and subject line Bug#966984: fixed in tryton-server 5.0.23-2
has caused the Debian Bug report #966984,
regarding tryton-server: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 returned exit code 13
to be marke
Your message dated Mon, 10 Aug 2020 09:50:50 +
with message-id
and subject line Bug#967037: fixed in python-socksipy 1.6.8+dfsg-1.1
has caused the Debian Bug report #967037,
regarding python-socksipy: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim t
Your message dated Mon, 10 Aug 2020 09:49:03 +
with message-id <5f31180f4cbd_3d02ad0833625bc11...@godard.mail>
and subject line Bug#966984 fixed in tryton-server
has caused the Debian Bug report #966984,
regarding tryton-server: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p
Control: tag -1 pending
Hello,
Bug #966984 in tryton-server 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:
https://salsa.debian.org/tryton-team/tryton-server/-/commit/ac126e92fbd259b8a
Processing control commands:
> tag -1 pending
Bug #966984 {Done: Mathias Behrle }
[src:tryton-server] tryton-server: FTBFS: dh_auto_test: error: pybuild --test
-i python{version} -p 3.8 returned exit code 13
Added tag(s) pending.
--
966984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966
Control: notfound -1 1:1.5.2-2
Control: notfound -1 1:1.5.1-2
Technically the missing epochs are also in stable,
but since there were no new symbols add in 1.5.2
this is not a problem when upgrading from 1.5.1
in oldstable.
The package in oldstable is not affected by chance since
dpkg-gensymbol
Processing control commands:
> notfound -1 1:1.5.2-2
Bug #966409 {Done: Adrian Bunk } [src:libjpeg-turbo]
libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
Bug #966419 {Done: Adrian Bunk } [src:libjpeg-turbo]
libjpeg-turbo: versions in debian/*.symbols files are missing th
Your message dated Mon, 10 Aug 2020 09:18:33 +
with message-id
and subject line Bug#966320: fixed in dico 2.9-5
has caused the Debian Bug report #966320,
regarding dico: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Mon, 10 Aug 2020 09:20:01 +
with message-id
and subject line Bug#957856: fixed in systemc 2.3.3-5
has caused the Debian Bug report #957856,
regarding systemc: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 10 Aug 2020 10:58:07 +0200
with message-id
and subject line Re: [libnode-dev] libnode-dev: broken symlinks
has caused the Debian Bug report #905415,
regarding libnode-dev: broken symlinks:
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
to be marked
Source: gdcm
Version: 3.0.7-2
Severity: serious
Hello, your debian/control file is missing the restrictions for archs (e.g.
ports, and mips64el),
leading to BD-uninstallabilities where mono is not available.
Please refresh the file to make it build everywhere
thanks
Gianfranco
Your message dated Mon, 10 Aug 2020 07:48:27 +
with message-id
and subject line Bug#966393: fixed in pandas 0.25.3+dfsg2-4
has caused the Debian Bug report #966393,
regarding pandas: FTBFS: TypeError: use() got an unexpected keyword argument
'warn'
to be marked as done.
This means that you c
Your message dated Mon, 10 Aug 2020 07:48:33 +
with message-id
and subject line Bug#966712: fixed in statsmodels 0.11.1-4
has caused the Debian Bug report #966712,
regarding statsmodels: debci tests fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Source: llvm-toolchain-9
Version: 1:9.0.1-13
Severity: serious
Tags: ftbfs
Dear Maintainer,
llvm-toolchain-9 FTBFS on ppc64el:
> [...]
> cd /<>/build-llvm/lib/Target/X86 && /usr/bin/g++-10
> -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
> -D__STDC_LIMIT_MACROS -I/<>/build-llvm
On 06/08/2020 11:05, Andreas Tille wrote:
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /build/jimfs-1.1/jimfs/src/main/java/com/google/common/jimfs/PathServi
79 matches
Mail list logo
