Your message dated Wed, 10 Jul 2019 05:51:50 +
with message-id
and subject line Bug#931714: fixed in node-request-promise 4.2.4-2
has caused the Debian Bug report #931714,
regarding node-request-promise: autopkgtest fails
to be marked as done.
This means that you claim that the problem has be
Package: bindgraph
Version: 0.2a-6
Severity: serious
Tags: patch
Hello,
the sysv init script for bindgraph fails on the stop action with the message
start-stop-daemon: matching only on non-root pidfile
/var/run/servergraph/bindgraph.pid is insecure
Relevant other bugs are 923421, 921016, and 9
Your message dated Wed, 10 Jul 2019 05:07:21 +
with message-id
and subject line Bug#878487: fixed in checkinstall 1.6.2-5
has caused the Debian Bug report #878487,
regarding checkinstall: Segmentation fault when invoking `checkinstall cmake -P
cmake_install.cmake`
to be marked as done.
This
Thanks for reporting this and providing a patch! I just uploaded checkinstall
1.6.2-5 which includes your patch. Unfortunately this didn’t make it into
buster but once this fixed version migrates to testing I will upload it to
buster-backports.
Thanks!
Stephen
It happens because you've installed some packages from the experimental
repository where Telegram Desktop was built against Qt 5.11.3. Now you
have to downgrade version of libqt5core5a. Install it from stable repo,
for example.
Also I would recommend you to decrease priority of the experimental
re
Package: telegram-desktop
Severity: grave
Justification: renders package unusable
I am unable to install this package.
For some reason it got uninstalled on Saturday after Buster's release and when
I try to install it, apt claims that it depends on qtbase-abi-5-11-3.
As the maintainer certaily k
Package: pytimechart
Version: 1.0.0~rc1-3.2
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for pytimechart (versioned as 1.0.0~rc1-3.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru pytimechart-1.0.0~rc1/deb
Your message dated Tue, 9 Jul 2019 22:27:30 +0200
with message-id <443dceef-cba7-9937-24aa-a0db201aa...@debian.org>
and subject line Re: should not be removed from Buster (important for visually
impaired users))
has caused the Debian Bug report #931490,
regarding should not be removed from Buster
Processing commands for cont...@bugs.debian.org:
> retitle 931730 libfile-stripnondeterminism-perl: build dependency cycle with
> libmonkey-patch-perl
Bug #931730 [libfile-stripnondeterminism-perl]
libfile-stripnondeterminism-perl: build dependency cycle with
libsub-identify-perl
Changed Bug ti
Hi Niko,
> the recently added libmonkey-patch-perl dependency in
> libfile-stripnondeterminism-perl has unfortunately resulted in a build
> dependency cycle
[…]
> I see this new dependency was introduced for normalizing zip archives
> (#858431) by changing the Archive::Zip behaviour on the fly. Is
Package: libfile-stripnondeterminism-perl
Version: 1.2.0-2
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.30-transition
X-Debbugs-Cc: debhel...@packages.debian.org, debian-p...@lists.debian.org
Hi,
the recently added libmonkey-patch-perl dependency in
libfile-stripnondeterm
On Tue, Jul 9, 2019 at 15:55:02 +0200, Christoph Berg wrote:
> Re: David Kalnischkies 2019-07-09 <20190709133107.gvib2ibj6w36j447@crossbow>
> > A Release file can declare that it will "soon" change its the value of
> > a field to foo and apt clients can notify users about this so
>
> Fwiw, I thi
Processing control commands:
> severity -1 normal
Bug #931669 [ephoto] ephoto doesn't even start up
Severity set to 'normal' from 'grave'
--
931669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 normal
Hi Michael,
I bet there's no rendering engine package installed. You can check
with: dpkg -l libevas1-engines*. If so, installing libevas1-engines-x
should fix the issue.
Currently, ephoto Depends on libevas1, which Recommends
libevas1-engines*. That can't be tight
Hi Carnë,
On Tue, Jul 09, 2019 at 04:53:31PM +0100, Carnë Draug wrote:
> On Tue, 9 Jul 2019 at 10:33, Andreas Tille wrote:
> >
> > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gbrowse_2.56+dfsg-4.rbuild.log.gz
>
> I have checked the output from that link and it's getting a
On Tue, 9 Jul 2019 at 10:33, Andreas Tille wrote:
>
> Hi Carnė,
>
> I have not checked but I could imagine that this issue is somehow
> connected to the the new upstream version of bioperl. Since you
> intended to to restructure the bioperl packages I think this is a good
> point in time. Since
Your message dated Tue, 09 Jul 2019 14:47:56 +
with message-id
and subject line Bug#931635: fixed in postgresql-common 203
has caused the Debian Bug report #931635,
regarding pg_upgradecluster writes data_directory to postgresql.auto.conf, and
gets confused by it on the next upgrade [DATA LOS
Processing control commands:
> severity -1 grave
Bug #931714 [node-request-promise] node-request-promise: autopkgtest fails
Warning: Unknown package 'node-request-promise'
Severity set to 'grave' from 'important'
Warning: Unknown package 'node-request-promise'
--
931714: https://bugs.debian.org/
Package: amarok
Version: 2.9.0-1+b1
Followup-For: Bug #921194
Dear maintainer.
The amarok builds just fine as per the steps outlined in
https://wiki.debian.org/BuildingTutorial#Rebuild_without_changes
No source changes are necessary.
I guess the only thing needed is the actual libmariadb* dep vers
On Wed, 2019-07-03 at 11:38 +0100, Luca Boccassi wrote:
> On Mon, 17 Jun 2019 11:39:13 +0100 Luca Boccassi <
> bl...@debian.org
>
> > wrote:
> > On Tue, 9 Apr 2019 15:52:52 +0200 Sylvain Beucler <
> >
>
> b...@beuc.net
>
>
> > > wrote:
> > > Package: evolution-ews
> > > Version: 3.30.5-1
> > >
Processing commands for cont...@bugs.debian.org:
> severity 931712 important
Bug #931712 [node-duplexer3] node-duplexer3 provides node-duplexer2 but is not
usable
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
931712: htt
After more search, the problem is that if /usr/lib/nodejs/duplexer2
isn't cleaned by dpkg, the link isn't created and the
/usr/lib/nodejs/duplexer2 stays empty.
Control: severity 931424 important
As documented in
https://lists.debian.org/debian-java/2019/07/msg9.html
the openjdk-13 packages (and follow-up non OpenJDK LTS releases should get a
little bit more exposure. We just should make sure that these packages are not
part of any Debian release
Processing control commands:
> severity 931424 important
Bug #931424 [src:openjdk-13] openjdk-13 should stay in unstable for now
Severity set to 'important' from 'serious'
--
931424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931424
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Your message dated Tue, 09 Jul 2019 14:12:55 +
with message-id
and subject line Bug#931214: fixed in python-os-collect-config 10.3.0-1
has caused the Debian Bug report #931214,
regarding ImportError: No module named oslo.config
to be marked as done.
This means that you claim that the problem
Re: David Kalnischkies 2019-07-09 <20190709133107.gvib2ibj6w36j447@crossbow>
> A) For a user with "debian stable" in sources.list the change of the
> Codename from buster to bullseye is a giant leap which should not
> be done carelessly or even automatically in the background.
I agree that stoppin
Processing commands for cont...@bugs.debian.org:
> affects 931712 node-request-promise node-module-deps node-multipipe
> node-static-module node-stream-combiner2
Bug #931712 [node-duplexer3] node-duplexer3 provides node-duplexer2 but is not
usable
Added indication that 931712 affects node-reques
On Mon, Jul 08, 2019 at 12:19:36PM +0200, Julian Andres Klode wrote:
> Anyway, this was not my thing so I might be misrepresenting or missing
> things :)
First of all: I am happy that I still manage to "break the world" (FSVO
world) – in other words that is "my thing" , but I mostly forgot about
i
Your message dated Tue, 09 Jul 2019 13:38:05 +
with message-id
and subject line Bug#930531: fixed in grub2 2.04-1
has caused the Debian Bug report #930531,
regarding grub2-common: grub-install --force-extra-removable does not work
properly with Secure Boot
to be marked as done.
This means th
Your message dated Tue, 09 Jul 2019 13:38:05 +
with message-id
and subject line Bug#931038: fixed in grub2 2.04-1
has caused the Debian Bug report #931038,
regarding missing Recommends: for shim-signed
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Package: node-duplexer3
Version: 0.1.4-4
Severity: grave
node-duplexer3 provides node-duplexer2: /usr/lib/nodejs/duplexer2 is a
symblik to /usr/lib/nodejs/duplexer3. Nodejs now looks at package.json
"name" field and refuse to load it:
$ node -e 'require("duplexer2")'
internal/modules/cjs/load
Your message dated Tue, 09 Jul 2019 13:34:16 +
with message-id
and subject line Bug#931709: fixed in diffoscope 117
has caused the Debian Bug report #931709,
regarding diffoscope: testsuite failure on all archs
to be marked as done.
This means that you claim that the problem has been dealt wi
Processing control commands:
> tag -1 pending
Bug #931709 [src:diffoscope] diffoscope: testsuite failure on all archs
Added tag(s) pending.
--
931709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #931709 in diffoscope 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/reproducible-builds/diffoscope/commit/8e811480e6e8a8ee7
Source: diffoscope
Version: 116
Severity: serious
Justification: autopkgtests failures are RC since bullseye
Tags: patch
Hello, you have an autopkgtest failure on sid for version 116, due to missing
tools at runtime.
While we are at it, there are a few tools that aren't available everywhere, due
Processing commands for cont...@bugs.debian.org:
> tags 931654 + sid bullseye
Bug #931654 [node-json3] node-json3: json3 is no more maintained
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
931654: https://bugs.debian.org/cgi-bin/bu
Followup-For: Bug #929450
Control: tag -1 - bullseye sid
The armel binaries have been removed from sid.
Andreas
Processing control commands:
> tag -1 - bullseye sid
Bug #929450 [caml-crush] caml-crush, build-dependencies unsatisfiable on armel
Removed tag(s) sid and bullseye.
--
929450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
Processing control commands:
> severity -1 serious
Bug #930869 [pm-utils] Don't release with buster
Severity set to 'serious' from 'wishlist'
--
930869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi Carnë,
I have not checked but I could imagine that this issue is somehow
connected to the the new upstream version of bioperl. Since you
intended to to restructure the bioperl packages I think this is a good
point in time. Since you are way more involved in bioperl than I I'd be
more than hap
Your message dated Tue, 09 Jul 2019 08:47:01 +
with message-id
and subject line Bug#926591: fixed in elogind 241.3-1+debian1
has caused the Debian Bug report #926591,
regarding libelogind0: does not ship SONAME link /lib//libelogind.so.0
-> libsystemd.so.0.25.0
to be marked as done.
This mea
41 matches
Mail list logo
