Your message dated Tue, 05 Feb 2019 15:34:03 +
with message-id
and subject line Bug#920881: fixed in debianbuttons 2.3-2
has caused the Debian Bug report #920881,
regarding webext-debianbuttons should list firefox-esr as first dependency
alternative
to be marked as done.
This means that you
Le 05/02/2019 à 15:05, Emmanuel Bourg a écrit :
> The real issue is lombok, it needs both Java 8 and 11 to build (and even
> 6 and 7! But we managed do to without that).
Erratum: I've just figured out how to build lombok with Java 11 only.
Once ivyplusplus is taught about the new javac 'release'
Your message dated Tue, 5 Feb 2019 17:07:44 +0200
with message-id <20190205150744.GH17997@localhost>
and subject line The freevo packages have been removed from unstable
has caused the Debian Bug report #899894,
regarding kaa-metadata: Invalid maintainer address
Your message dated Tue, 5 Feb 2019 17:07:44 +0200
with message-id <20190205150744.GH17997@localhost>
and subject line The freevo packages have been removed from unstable
has caused the Debian Bug report #899819,
regarding kaa-imlib2: Invalid maintainer address
Your message dated Tue, 05 Feb 2019 15:06:04 +
with message-id
and subject line Bug#921357: fixed in node-dequeue 1.0.5-2
has caused the Debian Bug report #921357,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.
This means that you claim that the
Your message dated Tue, 5 Feb 2019 17:07:44 +0200
with message-id <20190205150744.GH17997@localhost>
and subject line The freevo packages have been removed from unstable
has caused the Debian Bug report #899512,
regarding freevo: Invalid maintainer address
pkg-freevo-ma...@lists.alioth.debian.org
Your message dated Tue, 5 Feb 2019 17:07:44 +0200
with message-id <20190205150744.GH17997@localhost>
and subject line The freevo packages have been removed from unstable
has caused the Debian Bug report #899557,
regarding kaa-base: Invalid maintainer address
Your message dated Tue, 5 Feb 2019 17:07:44 +0200
with message-id <20190205150744.GH17997@localhost>
and subject line The freevo packages have been removed from unstable
has caused the Debian Bug report #866425,
regarding freevo: depends on obsolete python-imaging (replace with python3-pil
or
Your message dated Tue, 5 Feb 2019 17:07:44 +0200
with message-id <20190205150744.GH17997@localhost>
and subject line The freevo packages have been removed from unstable
has caused the Debian Bug report #891097,
regarding python-freevo: python-beautifulsoup is replaced with python-bs4
to be marked
Your message dated Tue, 5 Feb 2019 17:07:44 +0200
with message-id <20190205150744.GH17997@localhost>
and subject line The freevo packages have been removed from unstable
has caused the Debian Bug report #834162,
regarding freevo: obsolete
to be marked as done.
This means that you claim that the
Processing control commands:
> severity -1 important
Bug #920977 [mercurial-common] Breaks loading of db backends in Trac
Severity set to 'important' from 'serious'
--
920977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
control: reassign -1 x2goserver
thanks
On Tue, Feb 05, 2019 at 04:22:06PM +0200, Adrian Bunk wrote:
> control: severity -1 serious
> # x2go-server is now in buster
right, thanks for raising the severity.
> > On Tue, Feb 20, 2018 at 10:30:57AM +0100, Wolfgang Schweer wrote:
> > > > If NX do not
Control: severity -1 important
On 2/2/19 11:00 AM, Julien Cristau wrote:
> On 1/31/19 9:11 AM, Andras Korn wrote:
>> Package: mercurial-common
>> Version: 4.8.2-1
>> Severity: important
>>
>> Hi,
>>
>> as long as mercurial-common is installed, the postgres and sqlite db backend
>> driver of Trac
Processing control commands:
> reassign -1 x2goserver
Bug #890517 [killer] killer's CRON logs out users once per hour
Bug reassigned from package 'killer' to 'x2goserver'.
Ignoring request to alter found versions of bug #890517 to the same values
previously set
Ignoring request to alter fixed
Your message dated Tue, 05 Feb 2019 14:52:03 +
with message-id
and subject line Bug#921359: fixed in node-security 1.0.0-1
has caused the Debian Bug report #921359,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.
This means that you claim that the
Your message dated Tue, 05 Feb 2019 14:51:55 +
with message-id
and subject line Bug#873719: fixed in mpqc 2.3.1-19
has caused the Debian Bug report #873719,
regarding /usr/bin/sc-libtool: Command not found
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 05 Feb 2019 14:50:01 +
with message-id
and subject line Bug#915733: fixed in gcc-mingw-w64 21
has caused the Debian Bug report #915733,
regarding gcc-mingw-w64 is still based on GCC 7
to be marked as done.
This means that you claim that the problem has been dealt
Since upstream claimed this issue could not be reproduced, I decided to run a
test on zelenka.debian.org
The build did fail with a testsuite failure, but it looked nothing like the one in the
buildd log. Rather than most tests passing and a few failing most tests failed, I looked
at a few of
Processing control commands:
> tag 919462 + pending
Bug #919462 [src:coq] coq FTBFS on architectures without native OCaml backends
Added tag(s) pending.
--
919462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #890517 [killer] killer's CRON logs out users once per hour
Severity set to 'serious' from 'important'
--
890517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: release.debian.org
Severity: serious
User: release.debian@packages.debian.org
Usertags: binnmu
dolfin has started to FTBFS, see
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/dolfin_2018.1.0.post1-13.rbuild.log.gz
The dolfin build error comes from mpi4py. The
Control: tag 919462 + pending
Sorry for the radio silence. I misdiagnosed the issue in #10, but I have
properly diagnosed it now and have a fix pending. I’m rolling the fix
into my upload of 8.9.0, which should be coming in the next day.
Hi all,
Le 05/02/2019 à 14:24, Per Lundberg a écrit :
> is this the correct list of packages which can only be built w/ openjdk-8
That's almost correct:
- jzmq and openjfx are built with openjdk-11 already
- openjdk-8-jre-dcevm has just been removed, replaced by
openjdk-11-jre-dcevm (not in
Hi Dmitry,
On 2019-02-05 02:29, Dmitry Smirnov wrote:
> I've committed some changes on top of yours but then I've stumbled upon
> "Cannot Connect to Database: Unsupported option provided to mysql_options()"
> problem:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917083
>
> Do you
On 2/4/19 10:07 PM, Moritz Mühlenhoff wrote:
> What is the specific use case for this, is there some package which
> needs 8 and can't be fixed in time for 11?
Yes, it was stated in this thread earlier that such packages do exist.
Emmanuel/others, is this the correct list of packages which can
Package: libssl1.1-dbgsym
Severity: serious
Tags: upstream
Justification: Policy 7.2
Dear Maintainer,
I tried to install libssl1.1-dbgsym on my machine.
However, apt refuses to install it:
he following packages have unmet dependencies:
libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.0f-3+deb9u2)
Package: libssl1.0.2-dbgsym
Severity: serious
Justification: Policy 7.2
Dear Maintainer,
I tried to install libssl1.0.2-dbgsym on my machine.
However, apt refuses to install it:
he following packages have unmet dependencies:
libssl1.0.2-dbgsym : Depends: libssl1.0.2 (= 1.0.2l-2+deb9u3) but
Package: hotspot
Version: 1.1.0+git20180816-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
when capturing or reading laready existent "perf.data" files, Debian's
hotspot does not shown any information in any tab, except for the
graph showing the CPU use. Upstream
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:
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918273,
regarding eficas build depends on python-openturns that is currently not in
buster
to be marked
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918296,
regarding php-log build depends on php-db that is currently not in buster
to be marked as done.
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918275,
regarding graphite-api build depends on python3-xcffib that is currently not in
buster
to be
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918300,
regarding ruby-compat-resource build depends on ruby-cheffish that is currently
not in buster
to
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918287,
regarding linux-patch-grsecurity2 build depends on dh-kpatches that is
currently not in buster
to
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918274,
regarding foodcritic build depends on chef that is currently not in buster
to be marked as done.
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918267,
regarding android-platform-frameworks-data-binding build depends on
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918278,
regarding i8c build depends on python3-libi8x that is currently not in buster
to be marked as
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918286,
regarding linux-patch-debianlogo build depends on dh-kpatches that is currently
not in buster
to
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918297,
regarding php-services-weather build depends on php-db that is currently not in
buster
to be
Your message dated Tue, 5 Feb 2019 13:32:16 +0200
with message-id <20190205113216.GG17997@localhost>
and subject line Packages have been removed from testing
has caused the Debian Bug report #918268,
regarding bugs-everywhere build depends on monotone that is currently not in
buster
to be marked
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
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
Appreciate it Andreas, thank you. Working the NMU changes into a new
release along with some other important changes that have come up.
I'll look at moving things over to salsa.debian.org when time permits --
thanks for the suggestion.
On Wed, Jan 30, 2019 at 12:21 AM Andreas Tille wrote:
>
Package: letsencrypt
Version: 0.28.0-1
Severity: grave
Justification: causes data loss
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco
Steps to reproduce:
1. Start on sid
2. apt install letsencrypt # using transitional package
3. Use letsencrypt or certbot
4. Later, note the
Package: src:gcc-8-cross-mipsen
Version: 2~c1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
dpkg-buildpackage
-
dpkg-buildpackage: info:
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
> >>
>
Processing control commands:
> retitle -1 starpu: FTBFS while building documentation
Bug #921301 [src:starpu] starpu: FTBFS with upcoming doxygen 1.8.15
Changed Bug title to 'starpu: FTBFS while building documentation' from 'starpu:
FTBFS with upcoming doxygen 1.8.15'.
--
921301:
Control: retitle -1 starpu: FTBFS while building documentation
Hi Paolo,
On Mon, 4 Feb 2019 01:17:19 +0100 Paolo Greppi
wrote:
> Source: starpu
> Severity: serious
> I tested your package against a draft package for doxygen 1.8.15:
> https://bugs.debian.org/919413
>
> and it FTBFS with this
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
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 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:
> 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'
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
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
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
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)
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
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
101 - 162 of 162 matches
Mail list logo
