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 continue
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
Bu
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) [1].
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 don’t
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
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 b
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'
M
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 b
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: https://bugs.debian.org
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: https://bugs.debian.org
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?
A
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 prob
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 that
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: https://bugs.d
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 er
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
> >>
> >
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: sour
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 pr
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:
> Hi,
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 mea
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 b
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, 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 a
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.
T
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
libandroid-tools-annotations-j
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 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 #918286,
regarding linux-patch-debianlogo build depends on dh-kpatches that is currently
not in buster
to b
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 b
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 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 #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 #918296,
regarding php-log build depends on php-db that is currently not in buster
to be marked as done.
Th
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 marke
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 marke
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:
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 perf
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
1.0
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) but
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 o
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 have
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 test
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.
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 dol
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 problems
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
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 t
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 with.
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.
I
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 proble
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 ver
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 u
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 p
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 pr
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 pyth
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 #899557,
regarding kaa-base: Invalid maintainer address
pkg-freevo-ma...@lists.alioth.debian.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 #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 #899819,
regarding kaa-imlib2: Invalid maintainer address
pkg-freevo-ma...@lists.alioth.debian.
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 problem
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
pkg-freevo-ma...@lists.alioth.debia
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, 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
Your message dated Tue, 05 Feb 2019 15:34:57 +
with message-id
and subject line Bug#920524: fixed in valabind 1.7.0-1
has caused the Debian Bug report #920524,
regarding valabind: valabind does not start, libvalaccodegen.so not found.
to be marked as done.
This means that you claim that the p
Source: ddnet
Version: 11.7.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=ddnet&suite=sid
...
/usr/bin/c++ -DCONF_AUTOUPDATE -DCONF_OPENSSL -DCONF_SQL -DCONF_WEBSOCKETS
-DGLEW_STATIC -D_FORTIFY_SOURCE=2 -I/<>/obj-aarch64-linux-gnu/src
-I/<>/src -I/usr/include
Your message dated Tue, 05 Feb 2019 15:49:33 +
with message-id
and subject line Bug#921371: fixed in node-log4js 4.0.2-1
has caused the Debian Bug report #921371,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.
This means that you claim that the problem
Thanks a lot for the reference to $DPKG_MAINTSCRIPT_PACKAGE, an updated
package is on its way ...
Thorsten
Package: fetchmail
Version: 6.4.0~beta4-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
fetchmail has stopped working in version 6.4.0~beta4-2.
Running the daemon gets the first mail in the queue delivered, but then it
segfaults.
>From /var/log/syslog:
Feb 5 10:58:
Your message dated Tue, 05 Feb 2019 17:19:29 +
with message-id
and subject line Bug#659321: fixed in ooo-thumbnailer 0.2-5.1
has caused the Debian Bug report #659321,
regarding ooo-thumbnailer: No thumbnail generated in Gnome 3 Nautilus
to be marked as done.
This means that you claim that the
On Fri, Feb 01, 2019 at 07:37:38PM +0100, Bruno Kleinert wrote:
> Am Samstag, den 26.01.2019, 15:23 +0100 schrieb Bruno Kleinert:
> > Hi David,
> >
> > please consider addressing this RC bug.
> >
> > Just to raise awareness: I plan to NMU with my previously attached
> > patch around week 7.
> >
Control: tag -1 pending
Hello,
Bug #914410 in ruby-validate-url 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-validate-url/commit/d363a5532add4
Processing commands for cont...@bugs.debian.org:
> severity 921176 serious
Bug #921176 [redis-server] redis-server service is failing to start in buster
lxc container
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921176: h
severity 921176 serious
thanks
Hi Pirate,
[Dropping severity as it only affects LXC right now]
> It is working on the same host machine with stretch(-backports)
> container (5:5.0.3-3~bpo9+2). So host machine seems fine.
Thanks for looking into this and providing some LXC basics.
(However, I am
Hi! Umm, why me? I’m neither the tibble author nor a Debian package
maintainer :D
Andreas Tille schrieb am Di., 5. Feb. 2019 um 10:36 Uhr:
> 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 bu
Your message dated Tue, 05 Feb 2019 18:08:22 +
with message-id
and subject line Bug#914410: fixed in ruby-validate-url 1.0.2+git-2
has caused the Debian Bug report #914410,
regarding ruby-validate-url FTBFS: test failure
to be marked as done.
This means that you claim that the problem has bee
Your message dated Tue, 05 Feb 2019 18:05:02 +
with message-id
and subject line Bug#919583: fixed in ebtables 2.0.10.4+snapshot20181205-2
has caused the Debian Bug report #919583,
regarding ebtables: broken symlinks: /sbin/ebtables{,-restore,-save} ->
/usr/sbin/ebtables{,-restore,-save}
to be
Control: tags -1 + pending
Hello,
Andreas Beckmann, le mar. 05 févr. 2019 10:54:49 +0100, a ecrit:
> Control: retitle -1 starpu: FTBFS while building documentation
Ok, I give up with building the pdf version, doxygen+latex is too much
of a hassle.
(FTR, Nathalie told me that the issue encounter
Processing control commands:
> tags -1 + pending
Bug #921301 [src:starpu] starpu: FTBFS while building documentation
Added tag(s) pending.
--
921301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 +unreproducible moreinfo
Bug #921450 [fetchmail] fetchmail: Fetchmail segfaults upon execution
Added tag(s) unreproducible and moreinfo.
--
921450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921450
Debian Bug Tracking System
Contact ow...@bugs.debian
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 did you use?
> Running the daemon gets the first mail in the queue delivered, but then it
> segfaults.
Plea
Your message dated Tue, 05 Feb 2019 18:37:23 +
with message-id
and subject line Bug#921301: fixed in starpu 1.2.6+dfsg-6
has caused the Debian Bug report #921301,
regarding starpu: FTBFS while building documentation
to be marked as done.
This means that you claim that the problem has been dea
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 environmen
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 c
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
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 have
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 step
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 re
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, it
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 tha
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 tha
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 you
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: https://bugs.debian.org/cgi-bin/bugreport.cg
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: https://bugs.debian.org/cgi-bin/bugreport.c
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: 91946
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
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: https://bugs.debian.o
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: libwhy3-
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.
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 w
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
> > http://lau
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:
https://salsa.debian.org/js-team/node-active-x-obfuscator/commit/f
1 - 100 of 162 matches
Mail list logo
