Processing control commands:
> tag 911620 pending
Bug #911620 {Done: Guillem Jover } [dpkg]
shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster
Added tag(s) pending.
--
911620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911620
Debian Bug Tracking System
Contact o
Control: tag 911620 pending
Hi!
Bug #911620 in package dpkg reported by you has been fixed in
the dpkg/dpkg.git Git repository. You can see the changelog below, and
you can check the diff of the fix at:
https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=7f43bf5f9
---
commit 7f43bf5f93c857bdb4
Your message dated Wed, 23 Jan 2019 07:37:37 +
with message-id
and subject line Bug#917654: fixed in texlive-base 2018.20190122-1
has caused the Debian Bug report #917654,
regarding xr.sty: breaks \include handling
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Wed, 23 Jan 2019 07:37:37 +
with message-id
and subject line Bug#917654: fixed in texlive-base 2018.20190122-1
has caused the Debian Bug report #917654,
regarding xr.sty: breaks \include handling
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Wed, 23 Jan 2019 07:14:22 +
with message-id
and subject line Bug#919680: fixed in anthy 1:0.3-8
has caused the Debian Bug report #919680,
regarding anthy-el: does not work with emacs >= 24.3
to be marked as done.
This means that you claim that the problem has been dealt wit
On 1/22/19 4:41 PM, Boyuan Yang wrote:
> Hi all,
>
> 在 2019-01-21一的 00:26 +0100，Ross Gammon写道：
>> tag 891756 + pending
>> tag 897806 + pending
>> tag 918242 + pending
>> thanks
>>
>> I have uploaded a fix. It is unfortunately waiting for my new signing
>> sub-key to be rolled into the Debian Keyrin
Source: dpkg
Version: 1.19.3
Severity: serious
Justification: makes the package in question unusable or mostly so
Dear Maintainer,
Since the 1.19.3 upgrade pbuilder environment are broken:
I: Extracting source
/sbin/start-stop-daemon: matching only on world-writable pidfile /dev/null is
insec
On 1/21/19 4:33 PM, Moritz Mühlenhoff wrote:
> On Sat, Jan 19, 2019 at 04:18:06PM -0500, Louis-Philippe Véronneau wrote:
>> Hello from the Montreal BSP!
>>
>> I tested the latest release of the upstream version (0.2.36) and it
>> worked fine for me on the latest Thunderbird in testing.
>>
>> I migr
Your message dated Wed, 23 Jan 2019 04:49:14 +
with message-id
and subject line Bug#905208: fixed in emms 5.1-1
has caused the Debian Bug report #905208,
regarding emms: fails to upgrade from 'stretch': emms-setup.el:98:15:Error:
Cannot open load file: No such file or directory, seq
to be mar
Your message dated Wed, 23 Jan 2019 04:49:14 +
with message-id
and subject line Bug#917968: fixed in emms 5.1-1
has caused the Debian Bug report #917968,
regarding emms: relies on default-major-mode (replaced by major-mode in emacs
26)
to be marked as done.
This means that you claim that the
Your message dated Wed, 23 Jan 2019 02:38:55 +
with message-id
and subject line Bug#895482: fixed in ca-certificates 20190110
has caused the Debian Bug report #895482,
regarding Fails to upgrade: installed ca-certificates package post-installation
script subprocess returned error exit status
Elana Hashman writes:
> So here's the issue with Leiningen and Java 11. We previously tracked
> down some sort of bytecode incompatibilty problem. When Leiningen is
> built with Java 11, it seems to recompile every time it's run, leading
> to unacceptable performance, and it results in *differ
Your message dated Wed, 23 Jan 2019 00:20:54 +
with message-id
and subject line Bug#919154: fixed in mailman-suite 0+20180916-3
has caused the Debian Bug report #919154,
regarding mailman3-web: mailman3-web-qcluster.service fails because ExecStart
is missing absolute path to python3
to be mar
Your message dated Wed, 23 Jan 2019 00:20:54 +
with message-id
and subject line Bug#919158: fixed in mailman-suite 0+20180916-3
has caused the Debian Bug report #919158,
regarding mailman3-web: cronjobs should be run with flock to avoid them running
amok
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> severity 920147 important
Bug #920147 [sagemath] sagemath FTBFS on mipsel and mips64el
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
920147: https://bugs.debia
Your message dated Tue, 22 Jan 2019 23:05:18 +
with message-id
and subject line Bug#919907: fixed in ntopng 3.8+dfsg1-1
has caused the Debian Bug report #919907,
regarding ntopng FTBFS with ndpi 2.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 22 Jan 2019 23:05:18 +
with message-id
and subject line Bug#919907: fixed in ntopng 3.8+dfsg1-1
has caused the Debian Bug report #919907,
regarding ntopng FTBFS with new ndpi
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 22 Jan 2019 23:05:17 +
with message-id
and subject line Bug#887318: fixed in ntopng 3.8+dfsg1-1
has caused the Debian Bug report #887318,
regarding ntopng FTBFS on ppc64el: No support for PowerPC 64 bit mode (yet)
to be marked as done.
This means that you claim that th
Your message dated Tue, 22 Jan 2019 22:35:52 +
with message-id
and subject line Bug#918421: fixed in node-prelude-ls 1.1.2+dfsg-3
has caused the Debian Bug report #918421,
regarding node-prelude-ls FTBFS with nodejs 10.15.0
to be marked as done.
This means that you claim that the problem has
Le mardi 22 janvier 2019 à 02:50:48+0100, Pierre-Elliott Bécue a écrit :
> Le mardi 22 janvier 2019 à 01:57:22+0100, Pierre-Elliott Bécue a écrit :
> > Le lundi 21 janvier 2019 à 14:37:36+0100, Thomas Goirand a écrit :
> > > Hi,
> > >
> > > Would you have any idea how to resolve this Debian bug?
>
Processing control commands:
> severity -1 important
Bug #893227 [src:libbluray] libbluray FTBFS with openjdk-9
Severity set to 'important' from 'serious'
--
893227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 important
On Tue, Jan 22, 2019 at 7:48 AM Emmanuel Bourg wrote:
> OpenJDK 8 will be kept in Buster but it should be used in exceptional
> cases (for example the lombok package requires both OpenJDK 8 and 11 to
> build). The default Java runtime for Buster is OpenJDK 11 and t
Control: tag -1 pending
Hello,
Bug #918421 in node-prelude-ls 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/js-team/node-prelude-ls/commit/2c1937d104beff04377
Processing control commands:
> tags -1 +patch
Bug #920227 [sbuild] invalid file format generated for dependencies
Added tag(s) patch.
> notfound -1 0.77.1-2
Bug #920227 [sbuild] invalid file format generated for dependencies
Ignoring request to alter found versions of bug #920227 to the same value
Processing control commands:
> tag -1 pending
Bug #918421 [src:node-prelude-ls] node-prelude-ls FTBFS with nodejs 10.15.0
Added tag(s) pending.
--
918421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 +patch
Control: notfound -1 0.77.1-2
Control: found -1 0.78.0-2
Control: forwarded -1 https://salsa.debian.org/debian/sbuild/merge_requests/5
I have verified this is a regression from 0.77.1. I can also confirm
there is an easy fix, attached and forwarded.
Thanks to James Clark f
Processing commands for cont...@bugs.debian.org:
> forwarded 918421 https://github.com/gkz/prelude-ls/issues/116
Bug #918421 [src:node-prelude-ls] node-prelude-ls FTBFS with nodejs 10.15.0
Set Bug forwarded-to-address to 'https://github.com/gkz/prelude-ls/issues/116'.
> tags 918421 + upstream
Bug
Package: sbuild
Version: 0.78.0-2
Severity: grave
Tags: upstream
Since the 0.78 upgrade, sbuild cannot build packages in jessie (and
maybe other suites). The build during the setup phase, while trying to
install the build-dependencies, with this error message:
W: Failed to fetch
gzip:/var/lib/ap
Your message dated Tue, 22 Jan 2019 21:50:07 +
with message-id
and subject line Bug#917884: fixed in mate-dock-applet 0.87-2
has caused the Debian Bug report #917884,
regarding mate-dock-applet: Adding a new dock does nothing
to be marked as done.
This means that you claim that the problem ha
Your message dated Tue, 22 Jan 2019 21:49:30 +
with message-id
and subject line Bug#919443: fixed in ifupdown2 1.2.5-1
has caused the Debian Bug report #919443,
regarding ifupdown2: leaves diversion after upgrade from stretch
to be marked as done.
This means that you claim that the problem ha
Processing commands for cont...@bugs.debian.org:
> notfound 919213 1.5.0-2
Bug #919213 {Done: Axel Beckert } [irqbalance] irqbalance:
endless loop during configure, system reaches maximum of open files
No longer marked as found in versions irqbalance/1.5.0-2.
> thanks
Stopping processing here.
P
Processing control commands:
> tag -1 pending
Bug #917884 [mate-dock-applet] mate-dock-applet: Adding a new dock does nothing
Added tag(s) pending.
--
917884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Tue, 22 Jan 2019 21:35:04 +
with message-id
and subject line Bug#912410: fixed in python-igraph 0.7.1.post6-6
has caused the Debian Bug report #912410,
regarding python-igraph's tests fail with Python 3.7
to be marked as done.
This means that you claim that the problem has
Control: tag -1 pending
Hello,
Bug #917884 in mate-dock-applet 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/debian-mate-team/mate-dock-applet/commit/6582c01b
This can easily be fixed by adding ocamlbuild to the build-dependencies.
But then:
File "src/gen/common.ml", line 73, characters 24-34:
Error: This expression has type Types.constructor_arguments
but an expression was expected of type Types.type_expr list
Command exited with code 2.
-Ralf
Processing commands for cont...@bugs.debian.org:
> forwarded 886664 https://github.com/d3/d3-timer/issues/37
Bug #886664 [src:node-d3-timer] node-d3-timer FTBFS: test failure
Set Bug forwarded-to-address to 'https://github.com/d3/d3-timer/issues/37'.
> tags 886664 + upstream
Bug #886664 [src:node-
Package: gnome-menus
Version: 3.31.4-2
Severity: serious
Justification: Policy 1.1
Dear Maintainer,
Testing on Ubuntu Budgie 19.04 which has a patched version of v3.31.4-2
currently in Sid
demonstrated a serious issue in budgie-desktop. No menu categories were
visible.
I then refreshed
Your message dated Tue, 22 Jan 2019 21:00:07 +
with message-id
and subject line Bug#919965: fixed in unyaffs 0.9.7-0.2
has caused the Debian Bug report #919965,
regarding unyaffs: Non-working maintainer address
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Tue, 22 Jan 2019 20:58:05 +
with message-id
and subject line Bug#917500: fixed in liggghts 3.8.0+repack1-4
has caused the Debian Bug report #917500,
regarding liggghts: FTBFS (style_atom.h: No such file or directory)
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #912410 [src:python-igraph] python-igraph's tests fail with Python 3.7
Added tag(s) pending.
--
912410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Tue, Jan 22, 2019 at 10:25:24AM +, Mike Gabriel wrote:
> I think, the missing dependency is python3-dbus.
>
> Do you think you can re-test the installation procedure, reproduce this bug
> and then try to install python3-dbus and see if that fixes things? If I
You are right. Went back to sy
Control: tag -1 pending
Hello,
Bug #912410 in python-igraph 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/python-team/modules/python-igraph/commit/0a493106dbb
Processing control commands:
> severity -1 serious
Bug #904374 [src:screenie-qt] screenie-qt: Should this package be removed?
Severity set to 'serious' from 'important'
--
904374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904374
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Source: gnome-keysign
Version: 1.0.1-1
Severity: serious
Tags: ftbfs
gnome-keysign fails to build from source in a clean unstable chroot as
seen on Ubuntu and with Debian Reproducible Builds. The build tests
are failing.
By the way, I encourage you to do source-only uploads:
https://wiki.debian.o
Source: apache2
Version: 2.4.37-1
Severity: grave
Tags: patch security upstream
Hi (Stefan),
I agree the severity is not the best choosen one for this issue, it is
more to ensure we could release buster with an appropriate fix already
before the release. If you disagree, please do downgrade.
The
Processing control commands:
> severity -1 serious
Bug #920136 [libgnutls30] libgnutls30: symbol lookup error...undefined symbol:
__gmpz_limbs_write
Severity set to 'serious' from 'critical'
--
920136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920136
Debian Bug Tracking System
Contact o
Your message dated Tue, 22 Jan 2019 18:49:41 +
with message-id
and subject line Bug#911620: fixed in dpkg 1.19.3
has caused the Debian Bug report #911620,
regarding shared-mime-info,gconf2: trigger cycle during upgrade from stretch to
buster
to be marked as done.
This means that you claim th
Control: severity -1 serious
On 2019-01-22 James Van Zandt wrote:
> Package: libgnutls30
> Version: 3.6.5-2
> Severity: critical
> Justification: breaks unrelated software
Hello,
I am downgrading severity. apt is not "unrelated", it *uses* gnutls.
> Dear Maintainer,
> Sun 20 Jan 2019 10:25:49
Source: galera-3
Version: 25.3.25-1
Severity: serious
Tags: ftbfs
Control: block 904316 by -1
Dear maintainer,
your new upload of galera-3 FTBFS on mipsel.
https://buildd.debian.org/status/fetch.php?pkg=galera-3&arch=mipsel&ver=25.3.25-1&stamp=1547845354&raw=0
It seems to be a failed test of sor
Processing control commands:
> block 904316 by -1
Bug #904316 [release.debian.org] transition: boost-defaults
904316 was not blocked by any bugs.
904316 was not blocking any bugs.
Added blocking bug(s) of 904316: 920209
--
904316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904316
920209:
Your message dated Tue, 22 Jan 2019 18:19:49 +
with message-id
and subject line Bug#917725: fixed in python-acora 2.2-1
has caused the Debian Bug report #917725,
regarding python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b .
subprocess returned exit status 2
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> found 920189 8.6.92-1
Bug #920189 [src:kopanocore] kopanocore: wrong installation directories
Marked as found in versions kopanocore/8.6.92-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920189: https://bugs.d
Processing commands for cont...@bugs.debian.org:
> severity 920189 serious
Bug #920189 [src:kopanocore] kopanocore: wrong installation directories
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920189: https://bugs.debian.o
[need to re-CC debian-legal again, sorry.]
On Tue, Jan 22, 2019 at 06:05:37PM +0100, Domenico Andreoli wrote:
> On Mon, Jan 21, 2019 at 03:58:19PM +, MJ Ray wrote:
> > Missed the bug off the CC for this. Sorry.
>
> It seems it did not arrive to debian-legal either.
>
> > Begin forwarded mess
On Mon, Jan 21, 2019 at 03:58:19PM +, MJ Ray wrote:
> Missed the bug off the CC for this. Sorry.
It seems it did not arrive to debian-legal either.
> Begin forwarded message:
>
> Date: Mon, 21 Jan 2019 13:34:13 +
> From: MJ Ray
> To: debian-le...@lists.debian.org
> Subject: Re: Bug#9193
Your message dated Tue, 22 Jan 2019 17:06:08 +
with message-id
and subject line Bug#920173: fixed in pmacct 1.7.2-3
has caused the Debian Bug report #920173,
regarding pmacct is missing build-dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 22 Jan 2019 16:22:07 +
with message-id
and subject line Bug#919734: fixed in node-yauzl 2.10.0-1
has caused the Debian Bug report #919734,
regarding node-yauzl: FTBFS (TypeError: FdSlicer is not a constructor)
to be marked as done.
This means that you claim that the pr
Your message dated Tue, 22 Jan 2019 16:22:25 +
with message-id
and subject line Bug#916168: fixed in sphinx-autorun 1.1.0-3
has caused the Debian Bug report #916168,
regarding python3-sphinx-autorun: pycon calls "python" - not "python3"
to be marked as done.
This means that you claim that the
Your message dated Tue, 22 Jan 2019 16:07:26 +
with message-id
and subject line Bug#915774: fixed in python-fakeredis 1.0~rc1-1
has caused the Debian Bug report #915774,
regarding python-fakeredis FTBFS: AttributeError: 'module' object has no
attribute 'BasePipeline'
to be marked as done.
Th
Your message dated Tue, 22 Jan 2019 16:07:03 +
with message-id
and subject line Bug#918552: fixed in lombok 1.16.22-6
has caused the Debian Bug report #918552,
regarding lombok FTBFS: The import
org.eclipse.jdt.internal.corext.refactoring.SearchResultGroup cannot be resolved
to be marked as d
Package: src:preload
Version: 0.6.4-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
Control: tag -1 pending
Hello,
Bug #918552 in lombok 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/java-team/lombok/commit/c2721ae83c0f09cc3a83bd37a07835a36bb
Processing control commands:
> tag -1 pending
Bug #918552 [src:lombok] lombok FTBFS: The import
org.eclipse.jdt.internal.corext.refactoring.SearchResultGroup cannot be resolved
Added tag(s) pending.
--
918552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918552
Debian Bug Tracking System
C
Hi all,
在 2019-01-21一的 00:26 +0100，Ross Gammon写道：
> tag 891756 + pending
> tag 897806 + pending
> tag 918242 + pending
> thanks
>
> I have uploaded a fix. It is unfortunately waiting for my new signing
> sub-key to be rolled into the Debian Keyring.
I've prepared an upload from git packaging rep
Your message dated Tue, 22 Jan 2019 15:35:52 +
with message-id
and subject line Bug#892398: fixed in kfreebsd-10 10.3~svn300087-4
has caused the Debian Bug report #892398,
regarding kfreebsd-10: build-depends on GCC 6
to be marked as done.
This means that you claim that the problem has been d
Package: src:python-xarray
Version: 0.11.2-1
Severity: serious
Tags: sid buster
make[2]: Entering directory '/<>/doc'
sphinx-build -b html -d _build/doctrees . _build/html
Running Sphinx v1.7.9
python exec: /usr/bin/python3
sys.path: ['/usr/share/sphinx/scripts/python3', '/<>',
'/usr/lib/python3
Your message dated Tue, 22 Jan 2019 15:06:40 +
with message-id
and subject line Bug#897156: fixed in node-cache-base 0.8.4-2
has caused the Debian Bug report #897156,
regarding node-cache-base: FTBFS and Debci failure with node-is-extendable
1.0.1-1
to be marked as done.
This means that you
Processing control commands:
> tag -1 pending
Bug #919846 [ruby-rails-assets-highlightjs] ruby-rails-assets-highlightjs:
missing Depends: libjs-highlight.js
Added tag(s) pending.
--
919846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919846
Debian Bug Tracking System
Contact ow...@bugs.de
Control: tag -1 pending
Hello,
Bug #919846 in ruby-rails-assets-highlightjs 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/ruby-team/ruby-rails-assets-highlig
Processing control commands:
> reassign -1 node-get-value 3.0.1+~3.0.1-1
Bug #920190 [node-isobject,node-get-value] node-isobject,node-get-value: trying
to overwrite '/usr/lib/nodejs/isobject/index.js'
Bug reassigned from package 'node-isobject,node-get-value' to 'node-get-value'.
Ignoring reques
Control: reassign -1 node-get-value 3.0.1+~3.0.1-1
Control: close -1 1:3.0.1-2
On Tue, Jan 22, 2019 at 03:44:28PM +0100, Christoph Berg wrote:
> Package: node-isobject,node-get-value
> Severity: serious
>
> node-isobject and node-get-value cannot be installed together:
>
> Unpacking node-get-val
Package: src:coda
Version: 2.20-2
Severity: serious
Tags: sid buster
coda ftbfs on ppc64el:
[...]
checking build Java interface... no
[...]
make[1]: Leaving directory '/<>'
dh_install -a
install -d debian/coda//usr/bin
cp --reflink=auto -a debian/tmp/usr/bin/codacheck
debian/t
Package: node-isobject,node-get-value
Severity: serious
node-isobject and node-get-value cannot be installed together:
Unpacking node-get-value (3.0.1+~3.0.1-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-F6WG6i/026-node-get-value_3.0.1+~3.0.1-1_all.deb
(--unpack):
trying to overw
Your message dated Tue, 22 Jan 2019 14:43:43 +
with message-id
and subject line Bug#919792: fixed in gyoto 1.3.1-1
has caused the Debian Bug report #919792,
regarding gyoto,gyoto-doc: both packages ship /usr/share/doc/gyoto/README.md
to be marked as done.
This means that you claim that the pr
Your message dated Tue, 22 Jan 2019 14:43:50 +
with message-id
and subject line Bug#919064: fixed in jarjar 1.4+svn142-10
has caused the Debian Bug report #919064,
regarding jarjar: ASM class ModuleHashesAttribute is missing
to be marked as done.
This means that you claim that the problem has
Package: libjs-bootstrap4
Version: 4.2.1+dfsg-1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Bootstrap4 requires Popper.js, but package libjs-bootstrap4 is built
with it.
Solution is to package node-poppler.js and have libjs-bootstrap4 b
Processing control commands:
> tag -1 pending
Bug #919064 [libjarjar-java] jarjar: ASM class ModuleHashesAttribute is missing
Added tag(s) pending.
--
919064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #919064 in jarjar 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/java-team/jarjar/commit/1808732905069364dc97ae7cb2666ad8c17
An update of node-union-value fixes the problem. Let's do it
found 917500 3.8.0+repack1-3
thanks
Hi. Sorry for the reopening but this does not seem fixed.
I can still reproduce the error in our test machine (using sbuild)
and it also fails (with a different error) in reproducible-builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/l
Processing commands for cont...@bugs.debian.org:
> found 917500 3.8.0+repack1-3
Bug #917500 {Done: Anton Gladky } [src:liggghts] liggghts:
FTBFS (style_atom.h: No such file or directory)
Marked as found in versions liggghts/3.8.0+repack1-3; no longer marked as fixed
in versions liggghts/3.8.0+re
Processing control commands:
> reassign -1 libjarjar-java
Bug #919064 [src:scala] scala FTBFS: java.lang.NoClassDefFoundError:
com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute
Bug reassigned from package 'src:scala' to 'libjarjar-java'.
No longer marked as found in versions scala/2.11.12
Control: reassign -1 libjarjar-java
Control: affects -1 src:scala
Control: retitle -1 jarjar: ASM class ModuleHashesAttribute is missing
Le 20/01/2019 à 08:06, Andreas Tille a écrit :
> I've seen that there is a new upstream
> version (2.12.8) - may be I should give it a try but I have no idea
>
Your message dated Tue, 22 Jan 2019 14:09:51 +0100
with message-id <20190122130950.ge28...@mapreri.org>
and subject line Re: [Pkg-javascript-devel] Bug#920182: node-get-value:
Circular dependency
has caused the Debian Bug report #920182,
regarding node-get-value: Circular dependency
to be marked a
Processing control commands:
> tag -1 pending
Bug #920182 [node-get-value] node-get-value: Circular dependency
Added tag(s) pending.
--
920182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #920182 in node-get-value 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/js-team/node-get-value/commit/14b75131462c7a4a0438a
Package: node-get-value
Version: 3.0.1+~3.0.1-1
Severity: serious
Tags: upstream
node-get-value build-depends on node-micromatch which depends on
node-get-value via some packages
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (600, 'testing'), (50, 'unstable
Hi Reinhard,
Le 22/01/2019 à 12:14, Reinhard Tartler a écrit :
> Can you please give us an update on the roadmap for Java?
> What's the status on removing openjdk-8 from buster?
OpenJDK 8 will be kept in Buster but it should be used in exceptional
cases (for example the lombok package requires b
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #920020,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #920020,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #920020,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #920020,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked a
1 - 100 of 135 matches
Mail list logo
