Processing commands for cont...@bugs.debian.org:
> affects 877496 src:eliom
Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type
Obj.t but an expression was expected of type extension_constructor
Added indication that 877496 affects src:eliom
> thanks
Stopping
Hi Rhonda,
I'm just pinging both RC bugs to reset the autoremoval from testing
counter. I just realised that the package might not migrate to testing
due to a missing arm64 build. I leave it to you to decide about the
action to take but just wanted to prevent that you will be hit by an
Processing commands for cont...@bugs.debian.org:
> affects 877496 src:ocsigenserver
Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type
Obj.t but an expression was expected of type extension_constructor
Added indication that 877496 affects src:ocsigenserver
> thanks
Your message dated Wed, 27 Feb 2019 07:49:18 +
with message-id
and subject line Bug#923208: fixed in libp11 0.4.9-4
has caused the Debian Bug report #923208,
regarding libengine-pkcs11-openssl: libengines-pkcs11-openssl is installing to
the wrong engine directory on x86
to be marked as done.
Hi Utkarsh,
I realised that you intend to take over this package but for a reason I
do not understand myself it does not migrate to testing (see testing
excuses at the tracker page:
https://tracker.debian.org/pkg/ejs.js
).
I admit I have no idea why but if you really want to save this
Your message dated Wed, 27 Feb 2019 06:04:19 +
with message-id
and subject line Bug#923228: fixed in gringo 5.3.0-7
has caused the Debian Bug report #923228,
regarding FTBS: new symbols
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Hello,
fluffywolf, le mar. 26 févr. 2019 20:41:54 -0800, a ecrit:
> brltty's default behavior seems to to not just claim all usb serial devices,
No, only of serial devices which have generic USB ids for which there
are known Braille devices using it.
> Some possible suggestions:
> 1) Don't
Source: slapos.core
Severity: serious
As per upstream request, this package should not be available in testing and
hence in stable release so filling this bug report.
Regards,
Arnaud Fontaine
Package: brltty
Version: 5.4-7+deb9u1
Severity: critical
brltty's default behavior seems to to not just claim all usb serial devices,
but to send random data to them, potentially causing harm to the connected
device.
Grabbing all usb serial devices breaks every single other package related to
Hello Moritz,
i'm not sure what kind of input you're expecting from (if at all, and
this RC is mostly for the RT), but i'll reply
> mysql-connector-python is affected by Oracle's policy of not disclosing
> what security fixes they fix.
>
> CVE-2019-2435 is labeled with a CVSS 8.1/10 score and
Processing commands for cont...@bugs.debian.org:
> # reassign to source package
> reassign 840151 src:swift-im 3.0.4-1
Bug #840151 [swift-im] swift-im: FTBFS on i386: Qt wants this to be built with
-fPIC
Bug reassigned from package 'swift-im' to 'src:swift-im'.
No longer marked as found in
Your message dated Wed, 27 Feb 2019 05:04:37 +
with message-id
and subject line Bug#921747: fixed in didjvu 0.8.2-2
has caused the Debian Bug report #921747,
regarding src:didjvu: Build-depends/suggests uninstallable python-libxmp
to be marked as done.
This means that you claim that the
Your message dated Wed, 27 Feb 2019 00:34:30 +
with message-id
and subject line Bug#918467: fixed in lxpanel 0.10.0-1
has caused the Debian Bug report #918467,
regarding lxpanel: Weather plugin uses obsolete APIs, does not work.
to be marked as done.
This means that you claim that the
Hello,
On Sun 24 Feb 2019 at 11:26PM -05, Elana Hashman wrote:
> Note that Leiningen is still a lot slower and has different behaviour on
> jdk11, and users will likely prefer to run it on jdk8, but they can
> override the default Java by exporting JAVA_CMD fwiw. I might include a
> note of this
On 2/26/19 10:11 PM, Cesare Leonardi wrote:
Hello Dragan, do you know if the patch was eventually included upstream
and possibly in which version?
Hello, Cesare. It was included in 4.20.11 and 4.19.24.
Dragan
Processing commands for cont...@bugs.debian.org:
> reopen 922305
Bug #922305 {Done: Norbert Preining }
[texlive-extra-utils] latexindent: please add dependency with
liblog-log4perl-perl
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared,
Processing commands for cont...@bugs.debian.org:
> reassign 923282 freezegun 0.3.11-0.1
Bug #923282 [src:freezegun, src:cached-property] freezegun breaks
cached-property autopkgtest
Bug reassigned from package 'src:freezegun, src:cached-property' to 'freezegun'.
No longer marked as found in
Processing control commands:
> tag -1 pending
Bug #923330 [jajuk] jajuk: Fails to start with Java Runtime Environment 1.7
minimum required. You use a JVM ext.JVM@23fc625e
Added tag(s) pending.
--
923330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923330
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #923330 in jajuk 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:
Am 26.02.19 um 21:34 schrieb Markus Koschany:
> Thanks for reporting and the hint how to fix this problem. I'll take a
> closer look soon.
Unfortunately there is another issue that prevents jajuk from starting.
This appears to be the same one which affects triplea as well.
Your message dated Tue, 26 Feb 2019 23:38:10 +
with message-id
and subject line Bug#914632: fixed in uw-imap 8:2007f~dfsg-6
has caused the Debian Bug report #914632,
regarding uw-imap: CVE-2018-19518
to be marked as done.
This means that you claim that the problem has been dealt with.
If
OK, I think something more with the networking is going on. It still
works, but something is off. I'll investigate more tomorrow.
-Paul
Processing commands for cont...@bugs.debian.org:
> forwarded 923358 https://github.com/tobyink/p5-dist-inkt/issues/3
Bug #923358 [libdist-inkt-perl] libdist-inkt-perl: Stuffs full path into tarball
Set Bug forwarded-to-address to
'https://github.com/tobyink/p5-dist-inkt/issues/3'.
> thanks
On 2019-02-26 21:11, Cesare Leonardi wrote:
On 13/02/19 18:21, Dragan Milenkovic wrote:
This patch is already on its way to stable branches. I have tested it
and confirmed that it resolves the problem.
Hello Dragan, do you know if the patch was eventually included
upstream and possibly in
Processing commands for cont...@bugs.debian.org:
> tags 919344 + patch
Bug #919344 [openssh-client] adequate reports obsolete-conffile in
openssh-client
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919344:
Hi,
> This file now lives in openssh-server, since it's only needed by sshd.
> Unfortunately I'd forgotten that moving conffiles between packages
> requires some non-trivial effort, and so this is going to involve some
> complexity in maintainer scripts.
How about the attached approach?
It uses
Package: src:ftgl
Version: 2.4.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
(Yes, I know that it built ok 4 hours ago, but apparently not anymore)
[...]
Your message dated Tue, 26 Feb 2019 22:20:18 +
with message-id
and subject line Bug#922395: fixed in smokeping 2.7.3-2
has caused the Debian Bug report #922395,
regarding smokeping: fails to stop and to upgrade: start-stop-daemon: matching
only on non-root pidfile
Package: libitext-java
Version: 2.1.7-12
Severity: serious
Tags: patch
Hey,
When rebuilding bouncy-castle the jar doesn't seem to have the same classpath
built-in as older builds did; specifically comparing a rebuild with an old
debian build the MANIFEST.MF has the following diff (among other
* Ivo De Decker:
> The change should really be reverted and 3.0.5 should be re-uploaded
> to unstable (obviously using a version number that is higher than
> what's there now). Not only is this an uncoordinated transition long
> after the transition freeze, it will also block new uploads of qemu
Package: src:pacemaker
Version: 2.0.1~rc5-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3
Package: libdist-inkt-perl
Version: 0.024-4
Severity: grave
Tags: upstream
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The command distinkt-dist is completely useless:
Produces tarballs containing full path (not paths relative to build dir),
and then
On 13/02/19 18:21, Dragan Milenkovic wrote:
This patch is already on its way to stable branches. I have tested it
and confirmed that it resolves the problem.
Hello Dragan, do you know if the patch was eventually included upstream
and possibly in which version?
Cesare.
On Mon, 25 Feb 2019 16:59:57 + Colin Watson wrote:
> Control: severity -1 serious
>
> On Tue, Jan 15, 2019 at 06:44:55AM +, shirish शिरीष wrote:
> > While updating today, adequate informs me about this -
> >
> > $ adequate openssh-client
> > openssh-client: obsolete-conffile
OK, a little more info, just running the command:
ptp4l -m -i eth0
Breaks sshd until a reboot (existing sessions continue, but new
sessions are unable to start), restarting the networking or stopping
the ptp4l command doesn't help.
Also this is with two Ethernet adapters using the macb driver.
Your message dated Tue, 26 Feb 2019 21:45:16 +0100
with message-id <730ddbaf-b7c0-4541-cee9-925980416...@debian.org>
and subject line Re: jruby FTBFS with openjdk-9
has caused the Debian Bug report #893244,
regarding jruby FTBFS with openjdk-9
to be marked as done.
This means that you claim that
Processing control commands:
> severity -1 grave
Bug #923330 [jajuk] jajuk: Fails to start with Java Runtime Environment 1.7
minimum required. You use a JVM ext.JVM@23fc625e
Severity set to 'grave' from 'important'
--
923330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923330
Debian Bug
The disable command was actually "systemctl disable ptp4l"
thanks,
Paul
Processing control commands:
> tags -1 + pending
Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole data)
Added tag(s) pending.
--
922306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + pending
On Sun, Feb 24, 2019 at 09:40:59AM +0100, Salvatore Bonaccorso wrote:
> Control: found -1 4.3~rc5-1~exp1
> Control: tags -1 + upstream patch
>
> Upstream patch submission at
> https://lore.kernel.org/linux-btrfs/20190214151720.23563-1-fdman...@kernel.org/
Pending in
Dear all,
Leafpad is dead upstream. Maybe we could use one of the forks from
github perhaps ?
https://github.com/EEVV/leafpad3
https://github.com/stevenhoneyman/l3afpad
I am sure that gtk2 would probably be on its way out soonish as now
gtk3 is more or less mainstream and even gtk4 is there in
Processing commands for cont...@bugs.debian.org:
> tags 922306 + confirmed
Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole data)
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922306:
On Tue, Feb 26, 2019 at 03:05:48PM +0100, Markus Koschany wrote:
>
> [...]
>
> The FTBFS bug got fixed yesterday. I should complain more often. Andrej
> uploaded version 9.1.17 to unstable. This is not the latest one but I
> guess better than nothing? The original bug has not been closed yet.
>
Processing commands for cont...@bugs.debian.org:
> severity 913119 serious
Bug #913119 [src:linux] linux-image-4.18.0-2-amd64: Hangs on lvm raid1
Severity set to 'serious' from 'normal'
> found 913119 4.19.16-1
Bug #913119 [src:linux] linux-image-4.18.0-2-amd64: Hangs on lvm raid1
Marked as found
Package: linuxptp
Version: 1.8-1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
After installing linuxptp sshd no longer works, tail of
/var/log/auth.log shows entries like:
"ssh_dispatch_run_fatal: Connection from 10.244.33.4 port 52630:
Resource temporarily
Source: mysql-connector-python
Severity: serious
mysql-connector-python is affected by Oracle's policy of not disclosing
what security fixes they fix.
CVE-2019-2435 is labeled with a CVSS 8.1/10 score and only fixed in
8.x, while the version in stretch (2.1.x) is marked as vulnerable,
but no
Your message dated Tue, 26 Feb 2019 19:19:59 +
with message-id
and subject line Bug#923284: fixed in gradle 4.4.1-5
has caused the Debian Bug report #923284,
regarding FTBS: Doesn't handle depencencies that were build using openjdk 11
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #923284 [gradle] FTBS: Doesn't handle depencencies that were build using
openjdk 11
Bug #923317 [gradle] FTBS: Doesn't handle depencencies that were build using
openjdk 11
Added tag(s) pending.
Added tag(s) pending.
--
923284:
Control: tag -1 pending
Hello,
Bug #923284 in gradle 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:
On Fri, Feb 15, 2019 at 07:28:57PM +0100, Cyril Brulebois wrote:
> Right, this also breaks the build of the debian-installer source package
> on amd64 since its build dependencies cannot be satisfied.
Is there an ETA for a fix?
Cheers,
Moritz
Package: libradare2-dev
Version: 3.2.1+dfsg-4
Severity: serious
Control: block 923321 by -1
At least libuv and liblz4 are listed in Requires.private of the .pc files yet
the -dev package doesn't depend on their -dev packages. This leads to
pkg-config --cflags r_core failing.
-- System
Processing control commands:
> block 923321 by -1
Bug #923321 [src:radare2-cutter] radare2-cutter: FTBFS (dh_auto_configure fails)
923321 was not blocked by any bugs.
923321 was not blocking any bugs.
Added blocking bug(s) of 923321: 923341
--
923321:
Processing commands for cont...@bugs.debian.org:
> retitle 923226 openarena: startup fails on Intel Ironlake Mobile: Couldn't
> compile shader
Bug #923226 [ioquake3] Compiling shader doesn't work - game doesn't work
Changed Bug title to 'openarena: startup fails on Intel Ironlake Mobile:
On Tue, Feb 26, 2019 at 11:18:18AM +, Santiago Vila wrote:
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
> -DSYSCONFDIR='"/etc"' -I./../libdynaloginclient -Wdate-time
> -D_FORTIFY_SOURCE=2 -pthread -DLINUX -D_REENTRANT -D_GNU_SOURCE
>
Didier 'OdyX' Raboud dijo [Mon, Feb 25, 2019 at 02:58:09PM +0100]:
> === Resolution ===
>
> The Technical Committee resolves to decline to override the debootstrap
> maintainers.
>
> Furthermore, using its §6.1.5 "Offering advice" power, the Technical
> Committee considers that the desirable
On Tue, 2019-02-26 at 09:30 +, Colin Watson wrote:
> Thanks. At some point it would be nice to find a way to force the
> choice texts to be unambiguous without overflow, e.g. by prepending or
> appending a number. But this works as far as it goes and fixes an IMO
> serious bug, so I've just
On 2019-02-26 15:20:10 +, Colin Watson wrote:
> On Tue, Feb 26, 2019 at 04:01:33PM +0100, Vincent Lefevre wrote:
> > On 2019-02-26 12:44:41 +, Colin Watson wrote:
> > > Of course, the grub-pc maintainer script doesn't know either. All it
> > > has available to it is a /dev/disk/by-id/
Processing commands for cont...@bugs.debian.org:
> unarchive 478281
Bug #478281 {Done: Colin Watson } [debconf] an error in
displaying of multiselect dialogues in text form
Unarchived Bug 478281
> forcemerge 919029 920053
Bug #919029 [grub-pc] grub-pc: meaningless message "RUB boot loader was
On Tue, Feb 26, 2019 at 04:01:33PM +0100, Vincent Lefevre wrote:
> On 2019-02-26 12:44:41 +, Colin Watson wrote:
> > Of course, the grub-pc maintainer script doesn't know either. All it
> > has available to it is a /dev/disk/by-id/ path that no longer points to
> > a disk. The case I had in
Processing commands for cont...@bugs.debian.org:
> unblock 919029 with 478281
Bug #919029 [grub-pc] grub-pc: meaningless message "RUB boot loader was
previously installed..."
No valid blocking bug(s) given; not doing anything
Failed to set blocking bugs of 919029: Unknown/archived blocking
On 2019-02-26 12:44:41 +, Colin Watson wrote:
> Of course, the grub-pc maintainer script doesn't know either. All it
> has available to it is a /dev/disk/by-id/ path that no longer points to
> a disk. The case I had in mind when writing that code, and I think
> almost certainly the
On Tue, Feb 26, 2019 at 11:25:49AM +0100, Andreas Tille wrote:
> > The eigen3 maintainer and I are happy to simply rebuild affected
> > packages after every eigen3 update, but Emilio considers it an upstream bug.
> > Unfortunately I could not find anybody able to shed more light on the
> > eigen3
Your message dated Tue, 26 Feb 2019 14:44:15 +
with message-id
and subject line Bug#922217: fixed in python-os-api-ref 1.5.0+dfsg1-4
has caused the Debian Bug report #922217,
regarding python-os-api-ref: FTBFS (failing tests)
to be marked as done.
This means that you claim that the problem
Hi,
On Tue, 26 Feb 2019 at 15:20, Emmanuel Bourg wrote:
> Le 26/02/2019 à 15:05, Markus Koschany a écrit :
> > The FTBFS bug got fixed yesterday. I should complain more often. Andrej
> > uploaded version 9.1.17 to unstable. This is not the latest one but I
> > guess better than nothing? The
Processing control commands:
> forcemerge 919029 -1
Bug #919029 [grub-pc] grub-pc: meaningless message "RUB boot loader was
previously installed..."
Bug #920053 [grub-pc] grub-pc: Got a sudden prompt about needing to reinstall,
but that fails
Severity set to 'grave' from 'normal'
No valid
Touch bug #922404
Le 26/02/2019 à 15:05, Markus Koschany a écrit :
> The FTBFS bug got fixed yesterday. I should complain more often. Andrej
> uploaded version 9.1.17 to unstable. This is not the latest one but I
> guess better than nothing? The original bug has not been closed yet.
> Andrej, can we close it now
Control: tag -1 pending
Hello,
Bug #922217 in python-os-api-ref 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 #922217 [src:python-os-api-ref] python-os-api-ref: FTBFS (failing tests)
Added tag(s) pending.
--
922217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
Am 25.02.19 um 19:40 schrieb Miguel Landaeta:
> Hi Markus,
>
> On Sun, Feb 24, 2019 at 08:39:48PM +0100, Markus Koschany wrote:
>> JRuby is a mess. I guess we "just" need to package the latest upstream
>> release to fix the FTBFS bugs. Nobody felt like doing that in the past
>> twelve
Your message dated Tue, 26 Feb 2019 13:49:19 +
with message-id
and subject line Bug#918647: fixed in morfologik-stemming 1.9.0+dfsg-1
has caused the Debian Bug report #918647,
regarding morfologik-stemming: FTBFS (cannot find symbol IntIntOpenHashMap)
to be marked as done.
This means that
Processing control commands:
> tag -1 pending
Bug #923298 [chromium] chromium: file overlap with chromium-sandbox without
Conficts and/or Replaces
Added tag(s) pending.
--
923298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923298
Debian Bug Tracking System
Contact ow...@bugs.debian.org
control: tag -1 pending
On Tue, Feb 26, 2019 at 4:39 AM Lee Garrett wrote:
> your issue is related to mixing stable and testing, which is not supported and
> causing your issue here.
This may not be common knowledge, but mixed suites have always been a
supported configuration. This is a
On Tue, 2019-02-26 at 12:40 +0100, Emmanuel Bourg wrote:
> Le 26/02/2019 à 12:22, Sjoerd Simons a écrit :
>
> > ASM7 mode seems to have been introduced in the gradle v5.x series.
> > Not
> > sure if it makes sense for buster to upgrade to that (I really
> > don't
> > know much about java, so no
Didier 'OdyX' Raboud writes:
> === Resolution ===
>
> The Technical Committee resolves to decline to override the debootstrap
> maintainers.
>
> Furthermore, using its §6.1.5 "Offering advice" power, the Technical
> Committee considers that the desirable solution at the time of `bullseye` is:
>
Processing control commands:
> tag -1 pending
Bug #919029 [grub-pc] grub-pc: meaningless message "RUB boot loader was
previously installed..."
Added tag(s) pending.
--
919029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Your message dated Tue, 26 Feb 2019 12:49:19 +
with message-id
and subject line Bug#915559: fixed in coreutils 8.30-2
has caused the Debian Bug report #915559,
regarding coreutils: Use renameat2 from glibc instead of syscall
to be marked as done.
This means that you claim that the problem
Control: tag -1 pending
Hello,
Bug #919029 in grub2 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:
FWIW, the debconf bug that cut off the message has been fixed (in
1.5.70, although it required a follow-up fix in 1.5.71).
On Sat, Jan 19, 2019 at 11:49:54AM +0100, Vincent Lefevre wrote:
> On 2019-01-12 13:33:35 +, Colin Watson wrote:
> > I can see the argument that it might be convenient to
Package: src:radare2-cutter
Version: 1.7.4-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --buildsystem=cmake
Processing commands for cont...@bugs.debian.org:
> reassign 923284 gradle
Bug #923284 [src:bsh] Seemingly miscompiles with jdk-11
Bug reassigned from package 'src:bsh' to 'gradle'.
No longer marked as found in versions bsh/2.0b4-19.
Ignoring request to alter fixed versions of bug #923284 to the
Hi Different55,
I have uploaded 2:2.7+git20190128+0c1e29f-2 last week [1], could you
please give it a try?
[1]: https://packages.qa.debian.org/w/wpa/news/20190219T183431Z.html
--
Cheers,
Andrej
Le 26/02/2019 à 12:22, Sjoerd Simons a écrit :
> ASM7 mode seems to have been introduced in the gradle v5.x series. Not
> sure if it makes sense for buster to upgrade to that (I really don't
> know much about java, so no idea about the impact)?
We can't upgrade to Gradle 5 unfortunately, not
Hi Magnus,
On Sun, Feb 24, 2019 at 08:28:00PM +0100, Magnus Holmgren wrote:
> söndag 30 december 2018 kl. 09:38:57 CET skrev Salvatore Bonaccorso:
> > There is an alternative approach wich was raised by Magnus in the
> > respective bug: https://bugs.debian.org/914632#12 (and see followup
> >
On Tue, 2019-02-26 at 11:35 +0100, Emmanuel Bourg wrote:
> Le 26/02/2019 à 10:20, Sjoerd Simons a écrit :
>
> > I've atteched the output of running docker build on the DockerFile
> > i
> > attached to reproduce the issue; The relevant part in the gradle
> > build
> > seems to be:
>
> Thank you!
Package: src:dynalogin
Version: 1.0.0-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
test -x debian/rules
mkdir -p "."
set
Your message dated Tue, 26 Feb 2019 11:11:05 +
with message-id
and subject line Bug#919790: fixed in openjdk-12 12~33-1
has caused the Debian Bug report #919790,
regarding openjdk-12-dbg: file conflict with openjdk-11-dbg:
Your message dated Tue, 26 Feb 2019 11:04:10 +
with message-id
and subject line Bug#883619: fixed in ceres-solver 1.14.0-4
has caused the Debian Bug report #883619,
regarding libceres-dev: dependency on libeigen3-dev isn't strong enough
to be marked as done.
This means that you claim that
Your message dated Tue, 26 Feb 2019 11:04:10 +
with message-id
and subject line Bug#883619: fixed in ceres-solver 1.14.0-4
has caused the Debian Bug report #883619,
regarding colmap: FTBFS (dh_auto_configure fails)
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 26 Feb 2019 10:48:59 +
with message-id
and subject line Bug#92: fixed in nacl 20110221-6.1
has caused the Debian Bug report #92,
regarding Please build nacl with -fPIC and use CFLAGS from dpkg-buildflags
to be marked as done.
This means that you claim that the
Le lundi, 25 février 2019, 14.58:09 h CET Didier 'OdyX' Raboud a écrit :
> === Resolution ===
>
> The Technical Committee resolves to decline to override the debootstrap
> maintainers.
>
> Furthermore, using its §6.1.5 "Offering advice" power, the Technical
> Committee considers that the
Le 26/02/2019 à 11:23, Sjoerd Simons a écrit :
> This may or may not be related to 923284
This is the same issue. Gradle breaks when its dependencies use Java 11
bytecode.
Emmanuel Bourg
Your message dated Tue, 26 Feb 2019 10:35:04 +
with message-id
and subject line Bug#921762: fixed in timeshift 19.01+ds-1
has caused the Debian Bug report #921762,
regarding timeshift: FTBFS (error: The type name `AppExcludeEntry' could not be
found)
to be marked as done.
This means that
Your message dated Tue, 26 Feb 2019 10:34:47 +
with message-id
and subject line Bug#912545: fixed in jruby-openssl 0.9.21-2
has caused the Debian Bug report #912545,
regarding jruby-openssl: FTBFS with Java 11 due to javax.annotation removal
to be marked as done.
This means that you claim
Le 26/02/2019 à 10:20, Sjoerd Simons a écrit :
> I've atteched the output of running docker build on the DockerFile i
> attached to reproduce the issue; The relevant part in the gradle build
> seems to be:
Thank you! The "Malformed jar" message is just a warning. The actual
issue is:
> Caused
Hi Philipp,
On Tue, Feb 26, 2019 at 10:45:52AM +0100, Philipp Huebner wrote:
>
> > I mean: There is no *effective* change since the Build-Depends we set is
> > fullfilled anyway by the existing packages. Its just that it is
> > explicitly declared in the package metadata.
>
> IMO that's a
On Mon, 2019-02-25 at 23:59 +0100, Emmanuel Bourg wrote:
> Thank you for the report Sjoerd. What error did you get when
> compiling
> gradle with the rebuilt bsh?
>
> Emmanuel Bourg
Btw; I tested with forcing bsh to build with openjdk-8 instead and then
the issue doesn't occur while building
Ping #920467
--
http://fam-tille.de
Your message dated Tue, 26 Feb 2019 09:50:19 +
with message-id
and subject line Bug#922279: fixed in debconf 1.5.71
has caused the Debian Bug report #922279,
regarding debconf: Can't select long choices in dialog (whiptail) multiselect
to be marked as done.
This means that you claim that the
On Thu, Feb 14, 2019 at 09:44:46AM -0700, Kevin Locke wrote:
> On Thu, 2019-02-14 at 13:52 +, Colin Watson wrote:
> > On Wed, Feb 13, 2019 at 10:51:17PM -0700, Kevin Locke wrote:
> >> The problem is that the ellipsized choice text can't be mapped back
> >> to the choice value. I have attached
1 - 100 of 107 matches
Mail list logo
