Your message dated Tue, 05 Feb 2019 19:07:33 +
with message-id
and subject line Bug#918858: fixed in meep-lam4 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of
python-meep
to be marked as done.
This means that you
Your message dated Tue, 05 Feb 2019 19:07:33 +
with message-id
and subject line Bug#918077: fixed in meep-lam4 1.7.0-3
has caused the Debian Bug report #918077,
regarding python-meep-mpich2 fails to install, postinst script looks for wrong
package name.
to be marked as done.
This means that
On Sun, Dec 02, 2018 at 04:18:30PM -0800, Chris Kuehl wrote:
> Hi Adrian,
>
> Thanks for filing this. I can't be certain, but I have a strong
> suspicion that this is caused by a bug that we fixed upstream with
> dumb-init 1.2.2 which was causing flakiness in the test suite on
> certain
Le mar. 5 févr. 2019 à 20:21, Rebecca N. Palmer a
écrit :
> Package: clsparse
> Severity: serious
> X-Debbugs-Cc: debian-scie...@lists.debian.org, ghisv...@gmail.com
> (plus an identical one for freefem3d)
>
> This package is dead upstream, and it has been suggested [0] that
> because of this,
On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> And then there is the unrelated #908269 that currently prevents testing
> migration of pbbam.
> Steve seems to be addressing this with
> http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz
Hi Steve,
On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > And then there is the unrelated #908269 that currently prevents testing
> > migration of pbbam.
>
> > Steve seems to be addressing this with
> >
Your message dated Tue, 05 Feb 2019 21:23:03 +
with message-id
and subject line Bug#921364: fixed in node-active-x-obfuscator 0.0.2-2
has caused the Debian Bug report #921364,
regarding Not suitable for buster, package unmaintained
to be marked as done.
This means that you claim that the
Your message dated Tue, 05 Feb 2019 21:35:26 +
with message-id
and subject line Bug#918858: fixed in meep-openmpi 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of
python-meep
to be marked as done.
This means that
gcc-8 8.2.0-18 will have the upstream fix for that issue.
Your message dated Tue, 05 Feb 2019 21:49:46 +
with message-id
and subject line Bug#787603: fixed in genshi 0.7.1-1
has caused the Debian Bug report #787603,
regarding [src:genshi] Some sources are not included in your package
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> severity 920031 serious
Bug #920031 [schleuder] schleuder: DEP8 failures with ruby-mail 2.7.1
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920031:
Your message dated Tue, 05 Feb 2019 21:49:46 +
with message-id
and subject line Bug#910442: fixed in genshi 0.7.1-1
has caused the Debian Bug report #910442,
regarding genshi FTBFS: tests fail: RuntimeError: generator raised StopIteration
to be marked as done.
This means that you claim that
Package: clsparse
Severity: serious
X-Debbugs-Cc: debian-scie...@lists.debian.org, ghisv...@gmail.com
(plus an identical one for freefem3d)
This package is dead upstream, and it has been suggested [0] that
because of this, it should not be fixed for buster.
I don't know enough about it to
Hello folks,
Thank you for your efforts, bug reporting and triaging. I am the author of
ooo-thumbnailer and the Debian maintainer for this package. There have been
several barriers to continuing my work on it, and for this reason I will be
orphaning this package so that another maintainer can
Package: freefem3d
Severity: serious
This package is dead upstream, and it has been suggested [0] that
because of this, it should not be fixed for buster.
I don't know enough about it to have an opinion on this: I am opening
this bug as a "don't waste your time fixing it" notice.
If this
Source: rust-rusty-tags
Version: 3.3.0-1
Severity: serious
https://tracker.debian.org/media/packages/r/rust-rusty-tags/control-3.3.0-1
Source: rust-rusty-tags
Section: FIXME-(source.section)
...
This is likely the reason why the buildds don't upload the built
packages and similar weirdnesses.
On Tue, Feb 05, 2019 at 09:45:33PM +0100, Andreas Tille wrote:
> Hi Steve,
> On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> > On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > > And then there is the unrelated #908269 that currently prevents testing
> > >
Hi!
On Tue, 5 Feb 2019 at 22:34, Andreas Tille wrote:
> I can also add r-cran-tibble via
>
> apt-get install --no-install-recommends r-cran-tibble
>
> and the test suite keeps on succeeding! However, after intalling
> r-cran-dplyr the described error occures while after deinstalling
>
Processing commands for cont...@bugs.debian.org:
> tags 921460 + buster sid
Bug #921460 [clsparse] dead upstream - keep out of testing
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921460:
Processing commands for cont...@bugs.debian.org:
> tags 921459 + buster sid
Bug #921459 [freefem3d] dead upstream - keep out of testing
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921459:
Processing control commands:
> block 918633 by -1
Bug #918633 {Done: Ralf Treinen } [why3-coq] why3-coq:
package should Depend on a specific Coq version
918633 was not blocked by any bugs.
918633 was not blocking any bugs.
Added blocking bug(s) of 918633: 921465
--
918633:
Source: why3
Version: 1.1.1-3
Severity: serious
Tags: ftbfs
Control: block 918633 by -1
https://buildd.debian.org/status/package.php?p=why3
...
dh_install -a -XLICENSE
dh_install: Cannot find (any matches for)
"debian/tmp/usr/local/lib/ocaml/*/why3" (tried in ., debian/tmp)
dh_install:
Hi Philipp,
On Tue, Feb 05, 2019 at 07:01:42PM +0100, Philipp Angerer wrote:
> Hi! Umm, why me? I’m neither the tibble author nor a Debian package
> maintainer :D
Sure you are not the Debian maintainer but the test case of repr
failes if latest r-cran-tibble Debian package is installed. Thus
I
Your message dated Tue, 05 Feb 2019 19:39:08 +
with message-id
and subject line Bug#918074: fixed in meep-mpich2 1.7.0-3
has caused the Debian Bug report #918074,
regarding python-meep-mpich2 fails to install, postinst script looks for wrong
package name.
to be marked as done.
This means
Your message dated Tue, 05 Feb 2019 19:38:54 +
with message-id
and subject line Bug#918858: fixed in meep-mpi-default 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of
python-meep
to be marked as done.
This means
Your message dated Tue, 05 Feb 2019 19:39:08 +
with message-id
and subject line Bug#918858: fixed in meep-mpich2 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of
python-meep
to be marked as done.
This means that
Control: tag -1 pending
Hello,
Bug #921364 in node-active-x-obfuscator 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 Tue, Feb 05, 2019 at 12:56:53PM -0800, Steve Langasek wrote:
>
> Regardless, the autopkgtest problem is not amd64-specific, because at least
> for Ubuntu, we do not size our autopkgtest runners any differently on amd64
> than on other architectures. Fixing the autopkgtest to not require a
On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > And then there is the unrelated #908269 that currently prevents testing
> > migration of pbbam.
>
> > Steve seems to be addressing this with
> >
Hi,
I have the same problem with the same version of fetchmail package.
I didn't find the fetchmail-dbgsym package, but here is what the
suggested command displays:
$ env LC_ALL=C fetchmail -v -v -v --nodetach --nosyslog
Processing commands for cont...@bugs.debian.org:
> block 916369 with 919462
Bug #916369 {Done: Benjamin Barenblat } [libcoq-ocaml]
libcoq-ocaml depends and build-depends on cruft packages.
916369 was not blocked by any bugs.
916369 was not blocking any bugs.
Added blocking bug(s) of 916369:
On Tue, Feb 05, 2019 at 09:45:33PM +0100, Andreas Tille wrote:
> Hi Steve,
>
> On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> > On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > > And then there is the unrelated #908269 that currently prevents testing
> > >
On Tue, Feb 5, 2019 at 10:36 PM Sébastien Dinot wrote:
> I didn't find the fetchmail-dbgsym package, but here is what the
> suggested command displays:
[...]
> fetchmail: POP3> LIST 1
> fetchmail: POP3< +OK 1 474
> fetchmail: POP3> RETR 1
> fetchmail: POP3< +OK 474 octets
> reading message
Package: pdf2htmlex
Severity: serious
Should pdf2htmlex be removed? It's RC-buggy for over a year and upstream
development seems to have stopped:
http://pdf2htmlex.blogspot.de/2016/12/looking-for-new-maintainer.html
Cheers,
Moritz
On Tue, 05 Feb 2019 23:12:03 +0100 Moritz Muehlenhoff wrote:
> Should pdf2htmlex be removed? It's RC-buggy for over a year and upstream
> development seems to have stopped:
> http://pdf2htmlex.blogspot.de/2016/12/looking-for-new-maintainer.html
Yes, possibly.
Funny, that you are reporting this
Control: tags -1 fixed-upstream patch
These look like the upstream fixes, though I haven't actually tried them
yet.
for index:
https://github.com/arrayfire/arrayfire/commit/58ac59497b50257631713e689a6b0ddffb73361a
for assign:
Processing control commands:
> tags -1 fixed-upstream patch
Bug #892288 [src:arrayfire] arrayfire FTBFS on i386: test segfaults
Added tag(s) patch and fixed-upstream.
--
892288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892288
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing commands for cont...@bugs.debian.org:
> notfound 920031 2.7.1+dfsg1-1
Bug #920031 {Done: Georg Faerber } [schleuder] schleuder:
DEP8 failures with ruby-mail 2.7.1
There is no source info for the package 'schleuder' at version '2.7.1+dfsg1-1'
with architecture ''
Unable to make a
Package: mtail
Version: 3.0.0~rc19-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
From the attached log (scroll to the bottom...):
Selecting
Processing commands for cont...@bugs.debian.org:
> tags 921473 + sid buster
Bug #921473 [calibre] calibre: Invalid maintainer address
Added tag(s) buster and sid.
> found 921471 0.14.6+ds-4
Bug #921471 [pdf2htmlex] Should pdf2htmlex be removed?
There is no source info for the package 'pdf2htmlex'
Processing control commands:
> found -1 1:2.24.5-3
Bug #886836 {Done: Simon McVittie }
[libgtkmm-2.4-dev,libgtkmm-2.4-doc] libgtkmm-2.4-dev,libgtkmm-2.4-doc: both
ship usr/share/doc/libgtkmm-2.4-dev/examples/*
Marked as found in versions gtkmm2.4/1:2.24.5-3; no longer marked as fixed in
Control: found -1 1:2.24.5-3
On 2019-02-05 01:24, Debian Bug Tracking System wrote:
>* Fix "both ship usr/share/doc/libgtkmm-2.4-dev/examples/*":
> Install all demos into the -dev package, and only there;
> and also install Makefile*.
libgtkmm-2.4-dev now needs Breaks+Replaces:
Hi
I am arriving a little late to this disucussion, so please forgive me if
this is old news or I have misunderstood.
First, a small comment. Even though there might be only a few debian
packages that requires java 8, there are still a lot of projects, both
amateur and professional that
Package: calibre
Version: 3.39.1+dfsg-1
Severity: serious
Justification: Policy 3.3
Debian policy requires a valid maintainer address:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
Your message dated Tue, 5 Feb 2019 23:44:18 +0100
with message-id <09283296-c75d-5d69-fa1e-8fd5dd084...@debian.org>
and subject line Re: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym
since packet is outdated
has caused the Debian Bug report #921432,
regarding libssl1.1-dbgsym: Cannot
- Mail original -
> Thanks! Do you get the message via procmail and / or does it get
> deleted from your server?
Each time I launch fetchmail, I retrieve a copy of the same first message in my
local mailbox, but this message is not deleted from my server.
I don't know if this other
Your message dated Tue, 5 Feb 2019 23:44:18 +0100
with message-id <09283296-c75d-5d69-fa1e-8fd5dd084...@debian.org>
and subject line Re: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym
since packet is outdated
has caused the Debian Bug report #921430,
regarding libssl1.0.2-dbgsym: Cannot
Em qui, 3 de jan de 2019 às 22:56, Frank Heckenbach
escreveu:
>
> According to https://release.debian.org/buster/freeze_policy.html:
>
> 2019-01-12 - Transition freeze
>
> Is there still time yet to get a fix in, or is it FUBAR already?
Transition freeze means ABI changes in libraries are
Package: python3-spf-engine
Version: 2.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Package: lxqt-branding-debian
Version: 0.14.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite
On Tue, Feb 05, 2019 at 11:10:15PM +0200, Adrian Bunk wrote:
> On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> > On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > > And then there is the unrelated #908269 that currently prevents testing
> > > migration of pbbam.
Processing commands for cont...@bugs.debian.org:
> tags 921476 + pending
Bug #921476 [python3-spf-engine] python3-spf-engine: missing Breaks+Replaces:
postfix-policyd-spf-python (<< 2.9)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Thank you very much, nice finding. No discussions, my fault.
Your message dated Tue, 05 Feb 2019 22:49:55 +
with message-id
and subject line Bug#920031: fixed in schleuder 3.3.0-8
has caused the Debian Bug report #920031,
regarding schleuder: DEP8 failures with ruby-mail 2.7.1
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 05 Feb 2019 22:49:55 +
with message-id
and subject line Bug#919072: fixed in schleuder 3.3.0-8
has caused the Debian Bug report #919072,
regarding schleuder: FTBFS in both buster and sid
to be marked as done.
This means that you claim that the problem has been dealt
Control: found -1 0.9.0-2
On 2019-02-04 14:54, Debian Bug Tracking System wrote:
>* Breaks / Replaces: python-surfer (<= 0.7-1)
buster has 0.7-2.1 with the file in the old location.
Andreas
Processing control commands:
> found -1 0.9.0-2
Bug #921183 {Done: Andreas Tille } [python3-surfer]
python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0)
Marked as found in versions pysurfer/0.9.0-2; no longer marked as fixed in
versions pysurfer/0.9.0-2 and reopened.
--
921183:
Processing commands for cont...@bugs.debian.org:
> affects 921437 python3-mpi4py src:dolfin
Bug #921437 [release.debian.org] nmu: mpi4py_2.0.0-3+b2
Added indication that 921437 affects python3-mpi4py and src:dolfin
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On February 5, 2019 11:50:47 PM UTC, Nicholas D Steeves
wrote:
>Hi Scott,
>
>Reply follows inline.
>
>On Tue, Feb 05, 2019 at 05:31:23PM -0500, Scott Kitterman wrote:
>> Package: calibre
>> Version: 3.39.1+dfsg-1
>> Severity: serious
>> Justification: Policy 3.3
>>
>> Debian policy requires
On Tue, 5 Feb 2019 19:22:21 +0100
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= wrote:
> Control: tags -1 +unreproducible moreinfo
>
> Hi James,
>
> On Tue, Feb 5, 2019 at 6:09 PM James Henried wrote:
> > fetchmail has stopped working in version 6.4.0~beta4-2.
> Which previous version
Processing commands for cont...@bugs.debian.org:
> found 920031 3.3.0-6
Bug #920031 {Done: Georg Faerber } [schleuder] schleuder:
DEP8 failures with ruby-mail 2.7.1
Marked as found in versions schleuder/3.3.0-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Thanks for the report! I prepared a new version to fix this issue [0]
and will double-check the section field in the future (though I am
surprised that lintian did not catch that).
[0]
https://salsa.debian.org/rust-team/debcargo-conf/commit/bcda3d8c5b6efbd1b5b3f6ea0ffa3afea45dbc66
Hi Scott,
Reply follows inline.
On Tue, Feb 05, 2019 at 05:31:23PM -0500, Scott Kitterman wrote:
> Package: calibre
> Version: 3.39.1+dfsg-1
> Severity: serious
> Justification: Policy 3.3
>
> Debian policy requires a valid maintainer address:
>
> A message that you sent could not be delivered
Your message dated Wed, 6 Feb 2019 01:20:57 +0100
with message-id
and subject line Re: iw: Invalid maintainer address
pkg-wpa-de...@lists.alioth.debian.org
has caused the Debian Bug report #899558,
regarding iw: Invalid maintainer address pkg-wpa-de...@lists.alioth.debian.org
to be marked as
Your message dated Wed, 06 Feb 2019 01:24:18 +
with message-id
and subject line Bug#921126: fixed in wine-development 4.1-1
has caused the Debian Bug report #921126,
regarding wine-development: checks for /run/user instead of /run/user/$uid
to be marked as done.
This means that you claim
Your message dated Wed, 06 Feb 2019 01:22:34 +
with message-id
and subject line Bug#921479: fixed in lxqt-branding-debian 0.14.0.1
has caused the Debian Bug report #921479,
regarding lxqt-branding-debian: fails to upgrade from 'stable' to 'sid' -
trying to overwrite /etc/xdg/lxqt/panel.conf
> Em qui, 3 de jan de 2019 às 22:56, Frank Heckenbach
> escreveu:
> >
> > According to https://release.debian.org/buster/freeze_policy.html:
> >
> > 2019-01-12 - Transition freeze
> >
> > Is there still time yet to get a fix in, or is it FUBAR already?
>
> Transition freeze means ABI changes in
Package: webext-browserpass
Version: 2.0.22-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
I am curious to know why there is a debian/background.js as well as a
debian/manifest.json? They are not documented in debian/copyright. The
manifest seems to have a bogus
Package: libmariadb3
Version: 1:10.3.12-2
Severity: serious
Affects: w1retap
Justification: renders many Debian packages undistributable
Hello,
It's come to my attention that in buster and unstable, packages which
build-depend on default-libmysqlclient-dev wind up linked against
libmariadb3,
Hello!
The OpenSSL licence will change from 3.0.0 onwards
(https://www.openssl.org/source/license.html) but you are right that
for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
OpenSSL exception, and YaSSL has been used due to earlier
interpretation by non-maintainers that it
Hi Barak,
On Thu, Jan 31, 2019 at 2:54 AM Barak A. Pearlmutter
wrote:
>
> Thanks, that was very kind of you. Much appreciated. I'm in the
> process of preparing to upload.
> But next time feel free to just NMU, 0 day, tell me after, I totally don't
> mind!
> (This goes for any of my packages.)
Your message dated Wed, 06 Feb 2019 01:23:14 +
with message-id
and subject line Bug#921476: fixed in spf-engine 2.9.0-2
has caused the Debian Bug report #921476,
regarding python3-spf-engine: missing Breaks+Replaces:
postfix-policyd-spf-python (<< 2.9)
to be marked as done.
This means that
On Tue, Feb 05, 2019 at 10:42:25AM +, Robie Basak wrote:
> Expected: logs still exist back to the beginning, or at least since step
> 4.
>
> Actual: logs are gone.
>
> Real use case: users upgrading through the regular upgrade path will,
> upon purging old transitional packages, lose their
Your message dated Wed, 06 Feb 2019 03:54:12 +
with message-id
and subject line Bug#921423: fixed in python-certbot 0.28.0-2
has caused the Debian Bug report #921423,
regarding /var/log/letsencrypt gets wiped on transitional package purge
to be marked as done.
This means that you claim that
Your message dated Wed, 06 Feb 2019 04:07:56 +
with message-id
and subject line Bug#919477: fixed in gcl 2.6.12-83
has caused the Debian Bug report #919477,
regarding acl2 ftbfs on armel, armhf, arm64 and ppc64el
to be marked as done.
This means that you claim that the problem has been dealt
On Tue, Feb 5, 2019 at 10:57 PM Mattia Rizzolo wrote:
> Sure, of course that's the cause, but your suggested fix would instead
> introduce the other bug that "purge does not delete related logs", which
> is what everybody is expecting "purge" to do.
Hi Mattia,
The bug here is that the
Processing commands for cont...@bugs.debian.org:
> fixed 887733 1.6.0-3+deb9u2
Bug #887733 [src:unbound] unbound: CVE-2017-15105: vulnerability in the
processing of wildcard synthesized NSEC records
Marked as fixed in versions unbound/1.6.0-3+deb9u2.
> thanks
Stopping processing here.
Please
Hi,
I have the same problem, I run testing + some bits from unstable on this
machine.
$ env LC_ALL=C fetchmail -v -v -v --nodetach --nosyslog -b 2
Old UID list from mail.riseup.net:
Scratch list of UIDs:
fetchmail: removing stale lockfile
fetchmail: 6.4.0.beta4 querying mail.riseup.net
Thank you for the advice!
That works.
- Alex
On 05.02.19 23:45, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libssl1.1-dbgsym package:
>
> #921432: libssl1.1-dbgsym: Cannot install libssl1.1-dbgsym since packet is
Thank you for the advice!
That works.
- Alex
On 05.02.19 23:45, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libssl1.0.2-dbgsym package:
>
> #921430: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym since
Hi Lev and Matthias,
On Wed, Feb 6, 2019 at 8:00 AM Lev Lamberov wrote:
> I have the same problem, I run testing + some bits from unstable on this
> machine.
> $ env LC_ALL=C fetchmail -v -v -v --nodetach --nosyslog -b 2
[...]
> fetchmail: POP3> DELE 1
> fetchmail: POP3< +OK Marked to be
On Wed, Feb 06, 2019 at 07:21:46AM +0200, Otto Kekäläinen wrote:
> The OpenSSL licence will change from 3.0.0 onwards
> (https://www.openssl.org/source/license.html) but you are right that
> for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
> OpenSSL exception, and YaSSL has
Hi Werner,
> I don't know which source of mytop is included in mariadb-client-10.1 and
> cannot estimate if the standalone package of mytop makes sense or not in
> stretch. I assume the Maintainers of MariaDB do things right so I won't look
> further into this.
Would you be willing to
Processing control commands:
> retitle -1 cannot build jgdi with recent Java: sun.rmi.server
Bug #875404 [src:gridengine] FTBFS with Java 9: sun.rmi.server
Changed Bug title to 'cannot build jgdi with recent Java: sun.rmi.server' from
'FTBFS with Java 9: sun.rmi.server'.
> severity -1 wishlist
Control: retitle -1 cannot build jgdi with recent Java: sun.rmi.server
Control: severity -1 wishlist
Control: tag -1 - ftbfs
The part of the package that fails to build with recent Java versions is
JGDI. Without a proper patch to fix JGDI, I've excluded it for now (in
gridengine/8.1.9+dfsg-9)
Hi Philipp,
the continuous integration test in Debian has uncovered an issue after
tibble 2.0.0 was uploaded. Please have a look below. The full build
log can be found here:
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-repr/1847462/log.gz
(Please scroll down to the very
On Wed, Jan 16, 2019 at 08:47:37AM -0500, Benjamin Barenblat wrote:
> Control: retitle 919462 coq FTBFS on architectures without native OCaml
> backends
> Control: owner 919462 !
>
> Coq actually does build, but the test suite fails because I messed up
> plugin loading on architectures that
Your message dated Tue, 05 Feb 2019 09:06:44 +
with message-id
and subject line Bug#920009: fixed in golang-google-cloud 0.9.0-8
has caused the Debian Bug report #920009,
regarding golang-google-cloud FTBFS with golang-google-genproto-dev
0.0~git20190111.db91494-1
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> forcemerge 918916 919060
Bug #918916 {Done: Hleb Valoshka <375...@gmail.com>} [unicorn] Unicorn not
reporting proper version for gemfile?
Bug #919060 [unicorn] gitlab: Could not find gem 'unicorn (~> 5.1)'
Severity set to 'grave' from 'serious'
Processing commands for cont...@bugs.debian.org:
> reassign 919060 unicorn
Bug #919060 [gitlab] gitlab: Could not find gem 'unicorn (~> 5.1)'
Bug reassigned from package 'gitlab' to 'unicorn'.
No longer marked as found in versions gitlab/11.5.6+dfsg-1.
Ignoring request to alter fixed versions of
Processing commands for cont...@bugs.debian.org:
> fixed 919060 5.4.1-2
Bug #919060 [unicorn] gitlab: Could not find gem 'unicorn (~> 5.1)'
Marked as fixed in versions unicorn/5.4.1-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919060:
Processing commands for cont...@bugs.debian.org:
> found 919060 5.4.1-1
Bug #919060 [unicorn] gitlab: Could not find gem 'unicorn (~> 5.1)'
Marked as found in versions unicorn/5.4.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919060:
Processing commands for cont...@bugs.debian.org:
> affects 919060 gitlab
Bug #919060 {Done: Hleb Valoshka <375...@gmail.com>} [unicorn] gitlab: Could
not find gem 'unicorn (~> 5.1)'
Bug #918916 {Done: Hleb Valoshka <375...@gmail.com>} [unicorn] Unicorn not
reporting proper version for gemfile?
Processing control commands:
> severity -1 serious
Bug #921301 [src:starpu] starpu: FTBFS with upcoming doxygen 1.8.15
Severity set to 'serious' from 'important'
--
921301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Your message dated Tue, 05 Feb 2019 09:35:30 +
with message-id
and subject line Bug#921317: fixed in ruby-blade-qunit-adapter 2.0.1-2
has caused the Debian Bug report #921317,
regarding ruby-blade-qunit-adapter: Incomplete debian/copyright?
to be marked as done.
This means that you claim
On Mon, 04 Feb 2019 15:30:20 +0500 Pirate Praveen
wrote:
>
>
> On തി, ഫെബ്രു 4, 2019 at 1:26 വൈകു, Pirate
> Praveen wrote:
> >
> >
> > On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb
> > wrote:
> >> Hi,
> >>
> >>> redis-server service is failing to start in buster lxc container
> >>
>
Your message dated Tue, 05 Feb 2019 11:04:45 +
with message-id
and subject line Bug#918579: fixed in freeipa 4.7.2-1
has caused the Debian Bug report #918579,
regarding freeipa: The node-uglify build dependency needs the same architecture
list as the nodejs one
to be marked as done.
This
Your message dated Tue, 05 Feb 2019 11:04:45 +
with message-id
and subject line Bug#918579: fixed in freeipa 4.7.2-1
has caused the Debian Bug report #918579,
regarding freeipa: Still depends on nodejs on all architectures
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 05 Feb 2019 11:05:24 +
with message-id
and subject line Bug#921355: fixed in libpng1.6 1.6.36-4
has caused the Debian Bug report #921355,
regarding libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c
to be marked as done.
This means that you claim that
Source: canl-java
Version: 2.5.0-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/canl-java.html
...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on
project canl: MavenReportException:
1 - 100 of 162 matches
Mail list logo
