Processing commands for cont...@bugs.debian.org:
> reassign 922639 src:marble marble/4:17.08.3-3.1
Bug #922639 [marble-qt] marble-qt: building process does not complete
Bug reassigned from package 'marble-qt' to 'src:marble'.
No longer marked as found in versions marble/4:17.08.3-3.1.
Ignoring
Your message dated Sun, 29 Sep 2019 04:49:02 +
with message-id
and subject line Bug#912888: fixed in clamtk 6.01-1
has caused the Debian Bug report #912888,
regarding clamtk: Depends on libgtk2-perl, that won't be part of Bullseye
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #940485 in git-lfs 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 #940485 [git-lfs] git-lfs: FTBFS: tests fail
Added tag(s) pending.
--
940485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch
Bug #936099 [src:rust-num-traits] rust-num-traits: test failure on i386
Added tag(s) patch.
--
936099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tags -1 patch
On Fri, 30 Aug 2019 08:57:01 +0200 Gianfranco Costamagna
wrote:
> Source: rust-num-traits
> Version: 0.2.8-1
> Severity: serious
> Forwarded: https://github.com/rust-num/num-traits/issues/124
>
> Hello, looks like enabling the testsuite resulted in a failure on i386
>
On Sat, Sep 28, 2019 at 02:53:56AM +0200, Thorsten Glaser wrote:
> On Fri, 27 Sep 2019, Mark Hindley wrote:
>
> > Thanks. The aim of preventing accidental removal of systemd is very
> > reasonable. However, using this approach the hurdle you create even to a
> > user
> > who really wants to
On Fri, 27 Sep 2019, Julien Cristau wrote:
> So one thing I think we should ensure is we don't end up uninstalling
> systemd without an explicit user choice.
I’ve proposed to suggest to the systemd maintainers to add
Important: yes to libsystemd0. (On a different level, adding
it to systemd
On Fri, 27 Sep 2019, Mark Hindley wrote:
> Thanks. The aim of preventing accidental removal of systemd is very
> reasonable. However, using this approach the hurdle you create even to a user
> who really wants to uninstall is pretty high. Few people will continue having
> seen the 'You are about
On Fri, 27 Sep 2019, Adam Borowski wrote:
> > The "init" package has the "Important: yes" control field which as I
> That flag is not for "without an explicit user choice". It's for "you're
> breaking the packaging system, far more than ignoring dependencies".
This is wrong.
> It's the
Package: python-pymzml
Followup-For: Bug #933582
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch
This can be fixed by replacing texlive-generic-extra with a build-dependency
on texlive-plain-extra which replaces it.
In the process of fixing this in Ubuntu, I also
On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> 1. install sysvinit-core; that removes systemd-sysv but nothing else
>systemd related
> Souldn't that work?
It would, if but for libpam-systemd having a (somewhat questionable
but understandable) dependency on systemd-sysv. This is
Control: reassign -1 xorg-server
Control: retitle -1 xorg-server: build target must depend on build-*
Control: tags -1 ftbfs
Timo Aaltonen:
> Package: debhelper
> Severity: important
>
> Hi, debhelper 12.4 was fine but the current one broke xorg-server build,
> build-indep isn't run at all. With
Processing control commands:
> reassign -1 xorg-server
Bug #941128 [debhelper] xorg-server FTBFS
Bug reassigned from package 'debhelper' to 'xorg-server'.
Ignoring request to alter found versions of bug #941128 to the same values
previously set
Ignoring request to alter fixed versions of bug
Processing commands for cont...@bugs.debian.org:
> severity 941128 serious
Bug #941128 [debhelper] xorg-server FTBFS
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
941128:
On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote:
> On Fri, Sep 27, 2019 at 09:19:10AM -0400, Sam Hartman wrote:
> So one thing I think we should ensure is we don't end up uninstalling
> systemd without an explicit user choice.
Julien,
I appreciate that you are suggesting some
Your message dated Sat, 28 Sep 2019 18:36:27 +
with message-id
and subject line Bug#941139: fixed in e2fsprogs 1.43.4-2+deb9u1
has caused the Debian Bug report #941139,
regarding CVE-2019-5094: malicious fs can cause buffer overrun in e2fsck
to be marked as done.
This means that you claim
Your message dated Sat, 28 Sep 2019 18:32:08 +
with message-id
and subject line Bug#941139: fixed in e2fsprogs 1.44.5-1+deb10u2
has caused the Debian Bug report #941139,
regarding CVE-2019-5094: malicious fs can cause buffer overrun in e2fsck
to be marked as done.
This means that you claim
You can use version 1.2.49-3 which is the last version that does not
add the conflicting symbolic links.
On Sat, Sep 28, 2019 at 07:02:31AM +0200, Gianfranco Costamagna wrote:
> control: severity -1 serious
> control: found -1 0.35+git20181129+dfsg-3
>
> I know this isn't the right bug, but since this bug is about a non-existing
> version that FTBFS, lets recycle it :)
I think you wanted to alter
Your message dated Sat, 28 Sep 2019 15:05:37 +
with message-id
and subject line Bug#941308: fixed in fetchmail 6.4.1-1
has caused the Debian Bug report #941308,
regarding fetchmail: Fail to start with buffer overflow detected
to be marked as done.
This means that you claim that the problem
On 28 sept. 2019 16:17, Matthias Andree wrote:
> Control: tags -1 upstream fixed-upstream confirmed
> Control: severity -1 grave
>
> Christian, thanks for the report. It is a known issue that happens with
> fortifying compilers.
> Please use either the former rc3, rc4 or the upcoming 6.4.1.
Control: tags -1 upstream fixed-upstream confirmed
Control: severity -1 grave
Christian, thanks for the report. It is a known issue that happens with
fortifying compilers.
Please use either the former rc3, rc4 or the upcoming 6.4.1. László
(gcs@) is aware of it.
Processing control commands:
> tags -1 upstream fixed-upstream confirmed
Bug #941308 [fetchmail] fetchmail: Fail to start with buffer overflow detected
Added tag(s) confirmed, fixed-upstream, and upstream.
> severity -1 grave
Bug #941308 [fetchmail] fetchmail: Fail to start with buffer overflow
Your message dated Sat, 28 Sep 2019 13:34:30 +
with message-id
and subject line Bug#940774: fixed in rakudo 2019.07.1-4
has caused the Debian Bug report #940774,
regarding rakudo: upgrade issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: fetchmail
Version: 6.4.0-1
Severity: Serious
Dear Maintainer,
After upgrading from 6.4.0~rc4-2 to 6.4.0-1 fetchmail doesn't start
insserv: warning: current stop runlevel(s) (empty) of script `fetchmail'
overrides LSB defaults (0 1 6).
Job for fetchmail.service failed because the
Your message dated Sat, 28 Sep 2019 10:08:48 +
with message-id
and subject line Bug#932942: fixed in vistrails 3.0~git+9dc22bd-1
has caused the Debian Bug report #932942,
regarding vistrails depends on cruft package.
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 28 Sep 2019 10:08:48 +
with message-id
and subject line Bug#935353: fixed in vistrails 3.0~git+9dc22bd-1
has caused the Debian Bug report #935353,
regarding vistrails: Qt4 removal from Bullseye
to be marked as done.
This means that you claim that the problem has been
Mark,
On Fri, 27 Sep 2019, Mark Hindley wrote:
>
> Thanks. The aim of preventing accidental removal of systemd is very
> reasonable. However, using this approach the hurdle you create even
> to a user who really wants to uninstall is pretty high. Few people
> will continue having seen the
Source: kwayland-integration
Version: 5.14.5-1
Severity: serious
Tags: ftbfs
kwayland-integration fails to build from source on amd64 using sbuild:
| [ 41%] Building CXX object
src/windowsystem/CMakeFiles/KF5WindowSystemKWaylandPlugin.dir/plugin.cpp.o
| cd
Your message dated Sat, 28 Sep 2019 07:04:18 +
with message-id
and subject line Bug#939066: fixed in libodsstream 0.7.0-3
has caused the Debian Bug report #939066,
regarding libodsstream-qt5-dev: depends on dropped libquazip-dev
to be marked as done.
This means that you claim that the
Hello, none for now, but there might be a backport-alike debian new repository
without restrictions, I might give it a shot soon
Il giovedì 26 settembre 2019, 13:36:09 CEST, Michael Prokop
ha scritto:
Hi!
* Gianfranco Costamagna [Fri Aug 23, 2019 at 08:33:09AM +]:
> I'm not
32 matches
Mail list logo
