Hello Tobi,
On 11/9/18 7:57 PM, Tobias Frost wrote:
> Go ahead with the NMU ( you can also do a teamupload, as the package is in
> the Debian group of salsa... At least I think it is, but I can't check due to
> weak internet here))
I interpreted that as an Ack to upload to delayed/0. I kept it
On Thu, Nov 8, 2018 at 3:57 AM Haworth, David
wrote:
> Here's the gdb backtrace from pulseaudio -vvv (the last few lines of the
> verbose output are at the top)
Looks like the crash is happening inside libasound2-plugins. Does the crash
go away if you downgrade that back to version 1.1.6-1?
My `TLS_TRUSTCERTS=` was blank. Setting it to `/etc/ssl/certs` did not
resolve the problem.
The certificate I am using is generated by Let's Encrypt. I use the
combined.pem, which includes the entire chain, so the `TLS_TRUSTCERTS`
shouldn't be needed in my case.
The certificate is also used
Processing control commands:
> affects -1 src:pluto-lunar
Bug #913369 [src:pluto-jpl-eph] pluto-jpl-eph: Release to unstable
Added indication that 913369 affects src:pluto-lunar
--
913369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913369
Debian Bug Tracking System
Contact
Source: pluto-jpl-eph
Version: 0.0~git20180228-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:pluto-lunar
pluto-lunar can't be built in unstable because it build-depends on
packages from pluto-jpl-eph which is only in experimental. Please
upload pluto-jpl-eph to fix this issue.
Thanks,
Processing control commands:
> forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/360
Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes
needed, otherwise fails to launch
Changed Bug forwarded-to-address to
Control: forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/360
signature.asc
Description: This is a digitally signed message part.
Hi,
I just wanted to add that I'd been having this issue too and rolling
back libasound2 altogether, not just the plugins packages was
required. With the plugins packages rolled back I stopped having
segv's but the bigger issue was that nothing in a dbus session could
see the changes; alsa could
Before getting this bug report, I uploaded
uhd 3.13.0.2-3 which fixes this bug.
-Maitland
package: gmrender-resurrect
version: 0.0.7~git20180618.d0f46f5-2
severity: serious
gmrender-resurrect build-depends on libupnp1.8-dev and it's binary package
gmrender depends on libupnp10. These packages are no longer built by pupnp-1.8.
They appear to have been replaced by libupnp-dev and
Package: apt-show-versions
Version: 0.22.8
Followup-For: Bug #912709
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation? Installing Webmin
* What exactly did you do (or not do) that was effective (or
Package: tpm2-pk11
Version: 0~git20180426-1
Severity: serious
tpm2-pk11 build-depends on libsapi-dev and depends on libsapi0, these packages
are no longer built by source package tpm2-tss. They appear to have been
replaced by libtss2-dev and libtss2-esys0 .
Processing commands for cont...@bugs.debian.org:
> reassign 913367 src:tpm2-abrmd 1.3.1-1.1
Bug #913367 [tpm2-abrmd] tpm2-abrmd (build-)depends on cruft packages.
Bug reassigned from package 'tpm2-abrmd' to 'src:tpm2-abrmd'.
No longer marked as found in versions tpm2-abrmd/1.3.1-1.1.
Ignoring
Processing commands for cont...@bugs.debian.org:
> reassign 913368 src:tpm2-pk11 0~git20180426-1
Bug #913368 [tpm2-pk11] tpm2-pk11 (build-)depends on cruft packages.
Bug reassigned from package 'tpm2-pk11' to 'src:tpm2-pk11'.
No longer marked as found in versions tpm2-pk11/0~git20180426-1.
Processing commands for cont...@bugs.debian.org:
> reassign 913370 src:gmrender-resurrect
Bug #913370 [gmrender-resurrect] gmrender-resurrect (build-)depends on cruft
packages.
Bug reassigned from package 'gmrender-resurrect' to 'src:gmrender-resurrect'.
No longer marked as found in versions
Package: torbrowser-launcher
Version: 0.3.1-1
Severity: grave
Tags: upstream patch
Justification: renders package unusable
I had applied the patch before, but I guess it got overwritten with a
new version (which I thought wasn't supposed to happen without asking).
Applied the patch again and then
Control: forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/
360
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/
Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes
needed, otherwise fails to launch
Set Bug forwarded-to-address to
Package: tpm2-abrmd
Version: 1.3.1-1.1
Severity: serious
tpm2-abrmd build-depends on libsapi-dev and depends on libsapi0, these packages
are no longer built by source package tpm2-tss. They appear to have been
replaced by libtss2-dev and libtss2-esys0 .
Your message dated Fri, 9 Nov 2018 20:41:36 -0500
with message-id <20181109204136.021ec...@216-moncure.alexandria.va.us>
and subject line Re: Bug#913355: libuhd-dev: UHDConfig.cmake includes
nonexisting UHDTargets.cmake
has caused the Debian Bug report #913355,
regarding libuhd-dev:
Processing control commands:
> tags -1 + moreinfo
Bug #913350 [sa-compile] chmod: changing permissions of '/.../body_neg100.so':
Operation not permitted
Added tag(s) moreinfo.
> severity -1 normal
Bug #913350 [sa-compile] chmod: changing permissions of '/.../body_neg100.so':
Operation not
Control: tags -1 + moreinfo
Control: severity -1 normal
On Fri, Nov 09, 2018 at 08:40:14PM +0100, Sebastian Ramacher wrote:
> > | chmod: changing permissions of
> > '/var/lib/spamassassin/compiled/5.024/3.004001/auto/Mail/SpamAssassin/CompiledRegexps/body_neg100/body_neg100.so':
> > Operation
Your message dated Fri, 09 Nov 2018 20:41:49 +
with message-id
and subject line Bug#913162: fixed in pdns-recursor 4.1.7-1
has caused the Debian Bug report #913162,
regarding CVE-2018-10851 CVE-2018-14626 CVE-2018-14644
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> # will be fixed in DSA and needs fix in untstable
> severity 910431 grave
Bug #910431 [src:qemu] qemu: CVE-2018-10839: integer overflow leads to buffer
overflow issue
Severity set to 'grave' from 'important'
> severity 910431 grave
Bug #910431
Processing commands for cont...@bugs.debian.org:
> # will be fixed in DSA and needs fix in untstable
> severity 910431 grave
Bug #910431 [src:qemu] qemu: CVE-2018-10839: integer overflow leads to buffer
overflow issue
Ignoring request to change severity of Bug 910431 to the same value.
>
Your message dated Fri, 09 Nov 2018 21:03:54 +
with message-id
and subject line Bug#913300: fixed in gmrender-resurrect
0.0.7~git20180618.d0f46f5-2.1
has caused the Debian Bug report #913300,
regarding gmrender-resurrect: fails to autobuild because of libupnp transition
to be marked as done.
Re: Jeremy Bicha 2018-10-13
> dds fails to build on i386, in the build test stage:
>
>
> LD_LIBRARY_PATH=src examples/DealerPar
> terminate called after throwing an instance of 'std::length_error'
> what(): vector::_M_default_append
> Aborted
Fwiw, I'm
reopen 913336
thanks
Michael Tokarev dixit:
>> pn qemu-system-gui
>
>Ditto as for #913336.
Nope.
1. I still get “Display 'sdl' is not available.” if I select it.
2. qemu *still* runs a VNC server by default if the above package
is not installed.
Additionally, GTK+3 is… problematic and
Package: libuhd-dev
Version: 3.13.0.2-2
Severity: serious
Control: affects -1 src:gnuradio src:soapyuhd
https://buildd.debian.org/status/package.php?p=gnuradio
...
-- Enabling gr-trellis support.
-- Override with -DENABLE_GR_TRELLIS=ON/OFF
CMake Error at
Processing control commands:
> affects -1 src:gnuradio src:soapyuhd
Bug #913355 [libuhd-dev] libuhd-dev: UHDConfig.cmake includes nonexisting
UHDTargets.cmake
Added indication that 913355 affects src:gnuradio and src:soapyuhd
--
913355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913355
On 2018-09-26 14:56:16, Daniel Lange wrote:
[...]
> In any case, a repo with just the split files but no maintained history clones
> in ~12s in the above test setup. It also brings the (bare) repo down from
> 3,3GB
> to 189MB. So the issue is really the data/CVE/list file.
So I've looked in
Your message dated Fri, 9 Nov 2018 22:15:17 +0100
with message-id <2d48b4bd-d65d-7e4c-0d3f-c1523dada...@apache.org>
and subject line Re: libsmali-1-java FTBFS with OpenJDK 11
has caused the Debian Bug report #912243,
regarding libsmali-1-java: FTBFS with Java 11 due to Gradle incompatibility
to be
On 2018-11-09 16:05:06, Antoine Beaupré wrote:
> 2. do a crazy filter-branch to send commits to the right
> files. considering how long an initial clone takes, i can't even
> begin to imagine how long *that* would take. but it would be the
> most accurate simulation.
>
> Short of
10.11.2018 00:34, Thorsten Glaser wrote:
> reopen 913336
> thanks
>
> Michael Tokarev dixit:
>
>>> pn qemu-system-gui
>>
>> Ditto as for #913336.
>
> Nope.
>
> 1. I still get “Display 'sdl' is not available.” if I select it.
*if* you select it, yes, because sdl display isn't being built.
Control: clone -1 -2
Control: severity -2 normal
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: postgresql-10 -- ROM; superseded by postgresql-11
Re: To Debian Bug Tracking System 2018-11-01
<20181101123712.ga32...@msg.df7cb.de>
> postgresql-10 should be removed from testing, as
Processing control commands:
> clone -1 -2
Bug #912573 [postgresql-10] Remove postgresql-10 from testing (also, will fail
to binNMU)
Bug 912573 cloned as bug 913353
> severity -2 normal
Bug #913353 [postgresql-10] Remove postgresql-10 from testing (also, will fail
to binNMU)
Severity set to
Hi Gianfranco
Let's keep this open until it is confirmed that the changes 5.2.20 ->
5.2.22 are actually enough.
Did you got any confirmation on your query to upstream?
Regards,
Salvatore
Source: checkbox-support
Version: 0.22-1
Severity: serious
Tags: buster sid
I believe the checkbox stuff is no longer maintained. I expect someone
will file the RM bugs soon. Meanwhile, we can remove this package from
Testing with this RC bug.
Thanks,
Jeremy Bicha
Processing commands for cont...@bugs.debian.org:
> reopen 913137
Bug #913137 {Done: Gianfranco Costamagna }
[src:virtualbox] virtualbox: VirtualBox E1000 Guest-to-Host Escape
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may
Control: retitle -1 mysql-connector-java: removal from Debian
Control: block -1 by 913323 913354 913360 913343 913362
So here we go. The removal of mysql-connector-java is currently blocked
by five bugs. I have submitted patches for four of them and I will take
care of netbeans myself. I'm
Processing control commands:
> retitle -1 mysql-connector-java: removal from Debian
Bug #912916 [mysql-connector-java] mysql-connector-java: CVE-2018-3258: allows
low privileged attacker to compromise it
Changed Bug title to 'mysql-connector-java: removal from Debian' from
Hi,
Em qui, 8 de nov de 2018 às 11:59, IOhannes m zmölnig (Debian/GNU)
escreveu:
>
> (resending)
>
> my packages are marked for AUTORM by end of november, because they B-D
> on ftgl.
> i would really like to avoid having them removed from testing.
Thanks for the ping, I certainly did miss the
severity 908884 important
fixed 908884 8.5.35-1
close 908884
With javax.activation.jar added to the classpath the build now fails due
to the removal of JAXB:
[javac] import javax.xml.bind.JAXBContext;
[javac] ^
[javac]
/build/scilab-6.0.1/modules/xcos/src/java/org/scilab/modules/xcos/palette/PaletteManager.java:27:
error:
Your message dated Fri, 09 Nov 2018 11:20:19 +
with message-id
and subject line Bug#892133: fixed in node-rollup 0.50.0-2
has caused the Debian Bug report #892133,
regarding node-rollup: does not work after a no-change rebuild (the one in the
archive is not suitable for main?)
to be marked
Processing commands for cont...@bugs.debian.org:
> severity 908884 important
Bug #908884 [libtomcat8-java] i2p: FTBFS (autobuilder hangs)
Severity set to 'important' from 'serious'
> fixed 908884 8.5.35-1
Bug #908884 [libtomcat8-java] i2p: FTBFS (autobuilder hangs)
There is no source info for the
Processing commands for cont...@bugs.debian.org:
> tags 892438 + pending
Bug #892438 [src:xplanet] xplanet: Please use 'pkg-config' to find FreeType 2
Added tag(s) pending.
> tags 835821 + pending
Bug #835821 [xplanet-images] /usr/share/doc/xplanet-images/README should be a
file, not a directory
Your message dated Fri, 09 Nov 2018 11:35:09 +
with message-id
and subject line Bug#913137: fixed in virtualbox 5.2.22-dfsg-1
has caused the Debian Bug report #913137,
regarding virtualbox: VirtualBox E1000 Guest-to-Host Escape
to be marked as done.
This means that you claim that the problem
Source: gmrender-resurrect
Version: 0.0.7~git20180618.d0f46f5-2
Severity: serious
Justification: broken build depends
Hello,
pupnp-1.8 provides since its last upload libupnp-dev but not
libupnp1.8-dev any more. This makes the binnmu that is part of the
libupnp transition fail to complete with
The @Generated annotations can be safely removed, they only have a
documentation purpose at the source level.
But after removing them there is another issue related to the removal
of the javax.activation API in Java 11:
[javac]
Your message dated Fri, 9 Nov 2018 16:17:07 +0100
with message-id <9b839aa0-129b-4628-b275-812ea6d30...@apache.org>
and subject line Re: graxxia FTBFS with OpenJDK 11
has caused the Debian Bug report #912644,
regarding graxxia: FTBFS with Java 11 due to Gradle incompatibility
to be marked as done.
Your message dated Fri, 9 Nov 2018 16:23:59 +0100
with message-id
and subject line Re: libscout FTBFS with OpenJDK 11
has caused the Debian Bug report #912378,
regarding libscout: FTBFS with Java 11 due to Gradle incompatibility
to be marked as done.
This means that you claim that the problem
Hi,
igv also FTBFS with Java 11 now. However the fix is trivial. The package
must build-depend on libjaxb-api-java because those classes were removed
from the JDK. Then you need to remove the
--add-modules', 'java.xml.bind'
line in fix_gradle.patch.
Please find attached a patch that makes the
Control: clone 896087 -1
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: tcl8.5 -- ROM; obsolete
Control: affects -1 src:tcl8.5
On Thu, Apr 19, 2018 at 1:54 PM Sergei Golovan wrote:
>
> Tcl/Tk 8.5 has reached its end-of-life, so it's time to remove it from Debian.
> Applications
Processing control commands:
> clone 896087 -1
Bug #896087 [src:tcl8.5] tcl8.5: Time to remove from Debian
Bug 896087 cloned as bug 913293
No valid blocking bug(s) given; not doing anything
Failed to clone 896087: Unknown/archived blocking bug(s):893029.
> reassign -1 ftp.debian.org
Bug #896087
Supplementary.
The complete error message (without installed package "chromium-sandbox") looks
like this:
$ chromium
[32211:32211:1109/090528.982469:FATAL:zygote_host_impl_linux.cc(116)] No usable
sandbox! Update your kernel or see
Later the build fails when generating the javadoc, because the
"--add-modules=java.activation,java.xml.bind" option was specified to
build with Java 9, but these modules have been removed in Java 11.
Control: found -1 2.13.1-2
It's still reproducible for me:
$ strace -o '| grep -w EACCES' /usr/lib/firefox-esr/firefox-bin
...
openat(AT_FDCWD, "/usr/share/fonts/truetype/mononoki/.uuid.TMP-lrzetE",
O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE|O_CLOEXEC, 0600) = -1 EACCES (Permission denied)
Processing control commands:
> found -1 2.13.1-2
Bug #909750 {Done: Vincas Dargis } [libfontconfig1]
applications tries to write to /usr/* directories via libfontconfig1
Marked as found in versions fontconfig/2.13.1-2; no longer marked as fixed in
versions fontconfig/2.13.1-2 and reopened.
--
Hello,
On Fri, Nov 09, 2018 at 11:20:28AM +0100, Uwe Kleine-König wrote:
> Source: gmrender-resurrect
> Version: 0.0.7~git20180618.d0f46f5-2
> Severity: serious
> Justification: broken build depends
>
> pupnp-1.8 provides since its last upload libupnp-dev but not
> libupnp1.8-dev any more. This
Processing commands for cont...@bugs.debian.org:
> reassign 912603 libsane 1.0.27-3.1
Bug #912603 [libsane1] libsane1: discolored bar (genesys_gl847)
Bug reassigned from package 'libsane1' to 'libsane'.
No longer marked as found in versions sane-backends/1.0.27-3.
Ignoring request to alter fixed
Your message dated Fri, 09 Nov 2018 11:49:20 +
with message-id
and subject line Bug#908800: fixed in nautilus 3.30.3-1
has caused the Debian Bug report #908800,
regarding missing dependency on tracker
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 09 Nov 2018 11:49:20 +
with message-id
and subject line Bug#908800: fixed in nautilus 3.30.3-1
has caused the Debian Bug report #908800,
regarding nautilus: can't use nautilus without tracker
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 09 Nov 2018 11:49:20 +
with message-id
and subject line Bug#908800: fixed in nautilus 3.30.3-1
has caused the Debian Bug report #908800,
regarding Undeclared dependency on tracker
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 09 Nov 2018 11:49:20 +
with message-id
and subject line Bug#908800: fixed in nautilus 3.30.3-1
has caused the Debian Bug report #908800,
regarding nautilus: Trace/breakpoint trap
to be marked as done.
This means that you claim that the problem has been dealt with.
If
> According to Debian Policy 8.6.2, renaming of the SONAME and the
> library package name is possible for non-backwards compatible ABI
> changes.
Respectfully, the soname was not bumped. If you think that it should
be, why don't you ask the sane-backends developers to do that?
But I agree with
Your message dated Fri, 9 Nov 2018 14:30:48 +0200
with message-id <20181109123048.GJ18621@localhost>
and subject line Seems fixed in 0.7-1
has caused the Debian Bug report #868744,
regarding dcmstack FTBFS: UnicodeDecodeError: 'charmap' codec can't decode byte
0x81 in position 5136: character
Your message dated Fri, 09 Nov 2018 12:34:27 +
with message-id
and subject line Bug#913262: fixed in germinate 2.30
has caused the Debian Bug report #913262,
regarding germinate FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte
0xc4 in position 60
to be marked as done.
This means
Processing control commands:
> tags -1 + patch
Bug #912392 [src:scilab] scilab: FTBFS with Java 11 due to javax.annotation
removal
Added tag(s) patch.
--
912392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
I sent a merge request on Salsa [1]. It's only build tested, please
check if it's also ok at runtime.
[1] https://salsa.debian.org/science-team/scilab/merge_requests/2
Your message dated Fri, 09 Nov 2018 13:34:57 +
with message-id
and subject line Bug#899664: fixed in python-azure-devtools 1.1.1-1
has caused the Debian Bug report #899664,
regarding python-azure-devtools: Invalid maintainer address
pkg-azure-t...@lists.alioth.debian.org
to be marked as
Processing control commands:
> tag -1 moreinfo
Bug #912015 [nvidia-legacy-340xx-kernel-dkms] nvidia-legacy-340xx-kernel-dkms:
dkms module does not build against kernel 4.19
Added tag(s) moreinfo.
> severity -1 normal
Bug #912015 [nvidia-legacy-340xx-kernel-dkms] nvidia-legacy-340xx-kernel-dkms:
Control: tag -1 moreinfo
Control: severity -1 normal
Hi,
your problems seem to be related to your custom kernel, I do cannot
reproduce it with the official Debian kernel (4.19.0-rc7-amd64 in
experimental).
On 2018-10-27 11:47, Anuprita Duggal wrote:
> Assembler messages:
> Error: can't open
Your message dated Fri, 9 Nov 2018 18:01:15 +0100
with message-id <7a3ec1bf-b3ac-813c-0571-d09be3dc6...@apache.org>
and subject line Re: gkl FTBFS with OpenJDK 11
has caused the Debian Bug report #912250,
regarding gkl: FTBFS with Java 11 due to Gradle incompatibility
to be marked as done.
This
Control: severity -1 important
Control: tag -1 moreinfo
On 2018-09-17 23:44, Phil Miller wrote:
> When I suspend and resume my computer multiple times with a live
> X session with multiple applications running, it tends to crash
> the X server and terminate the session. These crashes seem to be
Processing control commands:
> severity -1 important
Bug #909059 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: Crash ends
session after multiple suspend/resume cycles
Severity set to 'important' from 'grave'
> tag -1 moreinfo
Bug #909059 [nvidia-legacy-340xx-driver]
Processing commands for cont...@bugs.debian.org:
> tags 913335 + security
Bug #913335 [qemu-system-x86] qemu-system-i386: Display 'sdl' is not available.
Added tag(s) security.
> severity 913335 serious
Bug #913335 [qemu-system-x86] qemu-system-i386: Display 'sdl' is not available.
Severity set
Your message dated Fri, 9 Nov 2018 20:58:21 +0300
with message-id <1c317644-86f3-8fc5-be41-6fadac9a3...@msgid.tls.msk.ru>
and subject line Re: Bug#913335: qemu-system-i386: Display 'sdl' is not
available.
has caused the Debian Bug report #913335,
regarding qemu-system-i386: Display 'sdl' is not
Package: libsane1
Version: 1.0.27-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
libsane1 cannot be updated using aptitude. It seems to be a dependancy
problem.
libsane1 depends on libsane-common (= 1.0.27-3)
Should it make any sense to change it to this:
Your message dated Fri, 9 Nov 2018 19:23:42 +0100
with message-id <3b9677b2-242d-7355-cb55-016a5814d...@apache.org>
and subject line Re: android-platform-tools-analytics-library FTBFS with
OpenJDK 11
has caused the Debian Bug report #912260,
regarding android-platform-tools-analytics-library:
Am 9. November 2018 14:07:51 GMT+02:00 schrieb "Uwe Kleine-König"
:
>Hello,
>
>On Fri, Nov 09, 2018 at 11:20:28AM +0100, Uwe Kleine-König wrote:
>> Source: gmrender-resurrect
>> Version: 0.0.7~git20180618.d0f46f5-2
>> Severity: serious
>> Justification: broken build depends
>>
>> pupnp-1.8
Your message dated Fri, 09 Nov 2018 19:19:57 +
with message-id
and subject line Bug#913163: fixed in pdns 4.1.5-1
has caused the Debian Bug report #913163,
regarding CVE-2018-14626 CVE-2018-10851
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: firefox-esr
Version: 60.3.0esr-1~deb8u1
Followup-For: Bug #911364
Dear Maintainer,
what could possibly go wrong when updating Firefox ESR to the next major
release?
This issue now arrived in Debian Jessie. I can confirm and reproduce it
with this steps. Prerequisite is that a
Package: sa-compile
Version: 3.4.2-1~deb9u1
Severity: grave
Upgrading sa-compile to the version in stretch-proposed-updates fails with
| Setting up sa-compile (3.4.2-1~deb9u1) ...
| Running sa-compile (may take a long time)
| chmod: changing permissions of
Your message dated Fri, 9 Nov 2018 20:29:52 +0100
with message-id <85685ae6-9ac4-a709-a509-6ec0915ca...@apache.org>
and subject line Re: android-platform-dalvik FTBFS with OpenJDK 11
has caused the Debian Bug report #912252,
regarding android-platform-dalvik: FTBFS with Java 11 due to Gradle
Your message dated Fri, 9 Nov 2018 20:39:08 +0100
with message-id <2cf384d1-31e0-c800-aae2-217613eb4...@apache.org>
and subject line Re: gatk-native-bindings FTBFS with OpenJDK 11
has caused the Debian Bug report #912248,
regarding gatk-native-bindings: FTBFS with Java 11 due to Gradle
On 2018-11-09 20:27:03, Sebastian Ramacher wrote:
> Package: sa-compile
> Version: 3.4.2-1~deb9u1
> Severity: grave
>
> Upgrading sa-compile to the version in stretch-proposed-updates fails with
> | Setting up sa-compile (3.4.2-1~deb9u1) ...
> | Running sa-compile (may take a long time)
> |
Your message dated Fri, 9 Nov 2018 18:38:04 +0100
with message-id <51ba49b6-9680-888f-eb38-bb0c697f9...@apache.org>
and subject line Re: android-sdk-helper FTBFS with OpenJDK 11
has caused the Debian Bug report #912263,
regarding android-sdk-helper: FTBFS with Java 11 due to Gradle incompatibility
Your message dated Fri, 9 Nov 2018 18:23:42 +0100
with message-id
and subject line Re: wala FTBFS with OpenJDK 11
has caused the Debian Bug report #912278,
regarding wala: FTBFS with Java 11 due to Gradle incompatibility
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 9 Nov 2018 18:30:59 +0100
with message-id <902a497a-dcdb-7acf-19a0-cd56ce11e...@apache.org>
and subject line Re: uncommons-watchmaker FTBFS with OpenJDK 11
has caused the Debian Bug report #912275,
regarding uncommons-watchmaker: FTBFS with Java 11 due to Gradle
Your message dated Fri, 9 Nov 2018 18:55:08 +0100
with message-id <800feced-8a2d-6da6-daa3-381b02ce2...@apache.org>
and subject line Re: android-platform-frameworks-data-binding FTBFS with
OpenJDK 11
has caused the Debian Bug report #912262,
regarding android-platform-frameworks-data-binding:
91 matches
Mail list logo
