Your message dated Thu, 14 Jun 2018 05:49:13 +
with message-id
and subject line Bug#828503: fixed in pinot 1.05-2
has caused the Debian Bug report #828503,
regarding pinot: FTBFS with openssl 1.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Thu, 14 Jun 2018 05:49:13 +
with message-id
and subject line Bug#833692: fixed in pinot 1.05-2
has caused the Debian Bug report #833692,
regarding pinot: links GPLv2+ code with OpenSSL
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:
> severity 900879 normal
Bug #900879 [bind9-dyndb-ldap] bind9-dyndb-ldap: does not work with current
bind9 anymore
Severity set to 'normal' from 'grave'
> --
Stopping processing here.
Please contact me if you need assistance.
--
900879:
[2018-06-14 00:32] Wouter Verhelst
> Hi,
Hi!
> On Wed, Jun 13, 2018 at 03:21:11AM +0300, kact...@gnu.org wrote:
> > I never worked with NSS, but how did it happen, that useradd {in postinst}
> > created user in a way, that userdel {in prerm} could not find?
>
> That's not what happened.
>
>
Processing commands for cont...@bugs.debian.org:
> block 894289 with 900011
Bug #894289 {Done: Andreas Tille } [src:htsjdk] htsjdk FTBFS
with openjdk-9
894289 was not blocked by any bugs.
894289 was not blocking any bugs.
Added blocking bug(s) of 894289: 900011
> thanks
Stopping processing here.
Adding the following lines to /etc/geoclue/geoclue.conf seems to be a good
workaround:
[redshift]
allowed=true
system=false
users=
I also have the demo agent installed, although I don't know if its important
--
My git repository:
https://github.com/freezeeedos
Also, here is the source of the workaround
https://github.com/jonls/redshift/issues/158
2018-06-14 5:08 GMT+02:00 quentin g :
> Adding the following lines to /etc/geoclue/geoclue.conf seems to be a good
> workaround:
>
> [redshift]
> allowed=true
> system=false
> users=
>
> I also have the demo
On Thu, Jun 14, 2018 at 12:45:38AM +0200, Jonas Smedegaard wrote:
> I still like pinot and believe there is a use for it in Debian as
> alternative to extract and tracker. But evidently it keeps falling too
> low on my priority list :-(
>
> Please do adopt it. Or co-maintain it with me, if
Package: acbuild
Severity: serious
acbuild build-depends on golang-go.crypto-dev which is no longer built by
golang-go.crypto, the replacement appears to be golang-golang-x-crypto-dev. I
was able to succesfully do a build in raspbian bister with the build-dependency
changed.
Processing commands for cont...@bugs.debian.org:
> forwarded 901290 https://gcc.gnu.org/PR86139
Bug #901290 [gcc-6] chromium: version 68 arm build causes internal compiler
error
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR86139'.
> tags 901290 + upstream
Bug #901290 [gcc-6] chromium:
Quoting Olly Betts (2018-05-31 23:47:10)
> On Thu, May 31, 2018 at 12:22:58AM +0200, Sebastian Andrzej Siewior wrote:
>> pinot has currently two RC bugs and failed to build during the curl4
>> transition / binNMU.
>> Does it make sense to add the two patches (Olly pointed to) and
>> upload it or
Hi,
On Wed, Jun 13, 2018 at 03:21:11AM +0300, kact...@gnu.org wrote:
> I never worked with NSS, but how did it happen, that useradd {in postinst}
> created user in a way, that userdel {in prerm} could not find?
That's not what happened.
The sreview user already existed before the sreview-common
Your message dated Wed, 13 Jun 2018 22:17:08 +
with message-id
and subject line Bug#894993: fixed in patch 2.7.5-1+deb9u1
has caused the Debian Bug report #894993,
regarding patch: CVE-2018-1000156: input validation vulnerability when
processing patch files
to be marked as done.
This means
Your message dated Wed, 13 Jun 2018 22:17:33 +
with message-id
and subject line Bug#900953: fixed in plexus-archiver 1.2-1+deb8u1
has caused the Debian Bug report #900953,
regarding plexus-archiver: CVE-2018-1002200
to be marked as done.
This means that you claim that the problem has been
Hi,
since there has not been any progress on this for a while now, I have
decided to prepare a non-maintainer upload myself, including the
latest upstream release, 1.1.24, as well as some minor maintenance
work.
Jonathan, could you have a look at this? Of course I won't upload a
NMU without your
Your message dated Wed, 13 Jun 2018 21:19:41 +
with message-id
and subject line Bug#897494: fixed in ditaa 0.10+ds1-1.2
has caused the Debian Bug report #897494,
regarding ditaa: FTBFS:
src/org/stathissideris/ascii2image/core/JavadocTaglet.java:26: error: package
com.sun.tools.doclets does
Control: tag -1 pending
Hello,
Bug #897494 in ditaa 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 #897494 [src:ditaa] ditaa: FTBFS:
src/org/stathissideris/ascii2image/core/JavadocTaglet.java:26: error: package
com.sun.tools.doclets does not exist
Ignoring request to alter tags of bug #897494 to the same tags previously set
--
897494:
Processing control commands:
> tags -1 pending patch
Bug #897494 [src:ditaa] ditaa: FTBFS:
src/org/stathissideris/ascii2image/core/JavadocTaglet.java:26: error: package
com.sun.tools.doclets does not exist
Added tag(s) patch and pending.
--
897494:
Control: tags -1 pending patch
Dear maintainer,
I have uploaded a new version of ditaa, versioned as 0.10+ds1-1.2, that
addresses the build failure with Java 10. The taglet class has been
removed and since a custom taglet is not really required for running the
program, I have dropped the
Le 13/06/2018 à 23:01, Adrian Bunk a écrit :
> The /usr/share/doc/default-jdk symlink is shipped in the default-jdk
> package that is not installed by the build dependencies of
> libgpars-groovy-java.
Ok, because libgpars-groovy-java build-depends on default-jdk-headless
instead of default-jdk
On Wed, Jun 13, 2018 at 10:54:05PM +0200, Emmanuel Bourg wrote:
> Control: tags -1 + help
>
> Le 13/06/2018 à 22:42, Adrian Bunk a écrit :
> > Control: reopen -1
> >
> > On Thu, May 17, 2018 at 09:39:07AM +, Debian Bug Tracking System wrote:
> >
> >
Source: bind9
Version: 1:9.11.3+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Hi,
The following vulnerability was published for bind9, affecting the
version present in unstable (older suites do not include the upstream
change #4777).
CVE-2018-5738[0]:
|Some
Control: tags -1 + help
Le 13/06/2018 à 22:42, Adrian Bunk a écrit :
> Control: reopen -1
>
> On Thu, May 17, 2018 at 09:39:07AM +, Debian Bug Tracking System wrote:
>
> https://buildd.debian.org/status/fetch.php?pkg=libgpars-groovy-java=all=1.2.1-8=1526551079=0
> javadoc: error - Error
Processing control commands:
> tags -1 + help
Bug #898902 [src:libgpars-groovy-java] libgpars-groovy-java: FTBFS with Java 10
due to javadoc issue
Added tag(s) help.
--
898902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898902
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> reopen -1
Bug #898902 {Done: Emmanuel Bourg }
[src:libgpars-groovy-java] libgpars-groovy-java: FTBFS with Java 10 due to
javadoc issue
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to
Control: reopen -1
On Thu, May 17, 2018 at 09:39:07AM +, Debian Bug Tracking System wrote:
>...
> libgpars-groovy-java (1.2.1-8) unstable; urgency=medium
>...
>* Added the missing build dependency on default-jdk-doc (Closes: #898902)
>...
> Source: libgpars-groovy-java
> Severity:
Processing commands for cont...@bugs.debian.org:
> tags 897535 + moreinfo
Bug #897535 [src:openafs] openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1
returned exit code 2
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897535:
Hello Adrian,
Sorry for my late answer.
I opened a bug against release.debian.org [1] to backport the fix, which
has been declined.
I'm afraid the dependency issue won't be solved in stable.
Cheers,
JB
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893705
On 20/03/2018 22:43, Adrian
Processing commands for cont...@bugs.debian.org:
> block 897321 with 897491
Bug #897321 {Done: Markus Koschany } [src:libjide-oss-java]
please remove (build) dependencies on OpenJDK 9
897321 was not blocked by any bugs.
897321 was not blocking any bugs.
Added blocking bug(s) of 897321: 897491
>
Processing commands for cont...@bugs.debian.org:
> tags 897491 + fixed-upstream
Bug #897491 [src:libjide-oss-java] libjide-oss-java: FTBFS: [javac]
/<>/libjide-oss-java-3.7.2+dfsg/src/com/jidesoft/plaf/LookAndFeelFactory.java:29:
error: package com.sun.java.swing.plaf.windows does not exist
Processing commands for cont...@bugs.debian.org:
> retitle 901293 matrix-synapse: CVE-2018-12291: Improper event filtering in
> get_missing_events handler
Bug #901293 {Done: Salvatore Bonaccorso }
[src:matrix-synapse] matrix-synapse: Improper event filtering in
get_missing_events handler
Processing commands for cont...@bugs.debian.org:
> found 901290 6.4.0-17
Bug #901290 [gcc-6] chromium: version 68 arm build causes internal compiler
error
Marked as found in versions gcc-6/6.4.0-17.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
901290:
Package: seabios
Version: 1.11.1-1
Severity: serious
Justification: Policy 4.15
Dear Maintainer,
SeaBIOS fails to build from source when building on sid and testing.
The error message is:
=
Compiling IASL src/fw/q35-acpi-dsdt.hex
Processing control commands:
> block 901155 by -1
Bug #901155 [release.debian.org] transition: octave-4.4
901155 was not blocked by any bugs.
901155 was not blocking any bugs.
Added blocking bug(s) of 901155: 901455
--
901155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901155
901455:
Package: src:libsbml
Version: 5.16.0+dfsg-2
Severity: serious
Control: block 901155 by -1
Dear Maintainer,
During a recompilation as part of the octave-4.4 transition, libsbml failed to
build (for a reason apparently unrelated to the transition):
Your message dated Wed, 13 Jun 2018 14:39:30 +
with message-id
and subject line Bug#878980: fixed in belenios 1.6+dfsg-1
has caused the Debian Bug report #878980,
regarding belenios FTBFS with OCaml 4.05.0
to be marked as done.
This means that you claim that the problem has been dealt with.
Hi,
Trying to load the various libs shipped with ruby-ncurses works fine at
the moment. Executing sup-mail and tpp too. reproducible-builds displays
a small sun for sup-mail and tpp.
This bug was probably triggered by some transition, and is not present
anymore. I am therefore closing this bug.
Your message dated Wed, 13 Jun 2018 16:10:31 +0200
with message-id <20180613141031.GA16738@shiraz>
and subject line loads fine now - probably a transitional bug
has caused the Debian Bug report #892181,
regarding ruby-ncurses fails to load with Ruby 2.5
to be marked as done.
This means that you
On Tue, 2018-06-12 at 20:01 +0800, Boyuan Yang wrote:
> Hi Pino, Ritesh,
>
> Three months have passed and I would kindly invite you to re-evaluate
> the
> status of robojournal in Debian.
>
> It is clear that upstream didn't show any activity in the last 3
> months and
> that rrs didn't make
Your message dated Wed, 13 Jun 2018 13:51:34 +
with message-id
and subject line Bug#888186: fixed in ruby-fakefs 0.14.2-1
has caused the Debian Bug report #888186,
regarding ruby-fakefs: FTBFS on ruby2.5: pread method is not available in File
:(
to be marked as done.
This means that you
Package: gdm3
Version: 3.28.2-2
Found extra info that, in my opinion, points to a race condition during
boot process, as already commented in my previous entry.
In my system, when I install debian SID in a mechanical hard disk, GDM3
boots fine and allows me to enter in both X11 and Wayland.
Your message dated Wed, 13 Jun 2018 11:37:11 +
with message-id
and subject line Bug#893610: fixed in ruby-sanitize 4.6.5-1
has caused the Debian Bug report #893610,
regarding ruby-sanitize: CVE-2018-3740
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 13/06/18 11:18, Pirate Praveen wrote:
> It would have been better if there was co-ordination before uploading
> such breaking changes. experimental first and heads up to failing
> reverse depends would have been better. Hopefully we can improve for
> future transitions.
Definitely. I am sorry
Processing control commands:
> block -1 by 899124
Bug #901318 [mkdocs] mkdocs: package contains broken symlink to font-awesome.ttf
901318 was not blocked by any bugs.
901318 was not blocking any bugs.
Added blocking bug(s) of 901318: 899124
--
901318:
Your message dated Wed, 13 Jun 2018 16:11:50 +0530
with message-id
and subject line closing
has caused the Debian Bug report #895107,
regarding ruby-kaminari: FTBFS: InvalidSpecificationException
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> fixed 895107 1.0.1-4
Bug #895107 [src:ruby-kaminari] ruby-kaminari: FTBFS:
InvalidSpecificationException
Marked as fixed in versions ruby-kaminari/1.0.1-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
895107:
fixed 895107 1.0.1-4
thanks
On Fri, 6 Apr 2018 23:25:13 -0700 Steve Langasek
wrote:
> Source: ruby-kaminari
> Version: 1.0.1-3
> Severity: serious
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu bionic
>
> Hi Pirate,
>
> The ruby-kaminari package fails to build in a clean,
On Wed, 13 Jun 2018 10:48:11 +0100 =?UTF-8?Q?Mart=c3=adn_Ferrari?=
wrote:
> I think the problem is the latest upload of
> golang-github-prometheus-client-golang-dev, which had some incompatible
> changes. It also affected docker go-metrics (#900597).
>
> Sadly, the only solution is to update to
On 13/06/18 07:54, Pirate Praveen wrote:
> On Sun, 10 Jun 2018 11:10:48 +0200 Andreas Beckmann wrote:
>> Justification: fails to build from source (but built successfully in the
>> past)
>
> seems broken by golang-github-prometheus-common-dev 0+git20180518.7600349-1
I think the problem is the
Followup-For: Bug #901102
Control: found -1 3.1.5+ds1-1
Hi,
there are still some issues upgrading from testing to the version in sid
since some files "moved around":
Selecting previously unselected package fireqos.
Preparing to unpack .../32-fireqos_3.1.5+ds1-1_all.deb ...
Unpacking
Processing control commands:
> found -1 3.1.5+ds1-1
Bug #901102 {Done: Jerome Benoit }
[firehol-doc,firehol-tools-doc,fireqos-doc]
firehol-doc,firehol-tools-doc,fireqos-doc: fails to install, trying to
overwrite other packages files
Marked as found in versions firehol/3.1.5+ds1-1; no longer
Package: rdiff-backup
Version: 1.2.8-7
Severity: grave
--- Please enter the report below this line. ---
I've been using rdiff-backup (as configured by backupninja) for years,
creating backups from 3 machines, one with Debian Lenny, another
with Debian Stretch, and the last one with Debian Buster
Confirmed - still problems with:
http://ftp.uk.debian.org/debian/pool/main/c/chromium-browser/chromium_67.0.3396.79-2_i386.deb
Errors seen on trying to play any YouTube video:
[1:22:0613/091758.102381:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"video decoder
Your message dated Wed, 13 Jun 2018 09:17:51 +0200
with message-id <20180613071751.mzn3dh4unt3il...@sar0.p1otr.com>
and subject line fixed in zzzeeksphinx 1.0.20-2
has caused the Debian Bug report #896623,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
to be marked as
On Sun, 10 Jun 2018 11:10:48 +0200 Andreas Beckmann wrote:
> Justification: fails to build from source (but built successfully in the past)
seems broken by golang-github-prometheus-common-dev 0+git20180518.7600349-1
signature.asc
Description: OpenPGP digital signature
> Since the recent upload of python-numpy on 2018-05-05, skimage has been
> failing its autopkgtests [1] and has now also started to FTBFS in
> unstable [2] with several errors similar to the following:
I see some changes adapting numpy 1.14 api change at upstream repo,
however they doesn't
On 2018-06-13 00:10:57 [+0200], Axel Beckert wrote:
> Hi Sebastian,
Hi Axel,
> Sebastian Andrzej Siewior wrote:
> > > I don't think so unless a future upload of OpenSSL to unstable fixes
> > > this. The recent one to unstable didn't.
> >
> > forwarded
58 matches
Mail list logo
