Processing commands for cont...@bugs.debian.org:
> block 933722 with 934340
Bug #933722 [camlp4] camlp4 is deprecated and almost dead upstream (and a key
package)
933722 was blocked by: 933992 933993 934220 934229 933994 934227 934222 934226
934225 934221
933722 was not blocking any bugs.
Added
Your message dated Sat, 10 Aug 2019 04:08:04 +
with message-id
and subject line Bug#925268: fixed in redmine-plugin-pretend 0.0.2+git20130821-5
has caused the Debian Bug report #925268,
regarding redmine-plugin-pretend: breaks configuration of redmine
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> forwarded 925268 https://github.com/batizhevsky/redmine_pretend/issues/31
Bug #925268 [redmine-plugin-pretend] redmine-plugin-pretend: breaks
configuration of redmine
Set Bug forwarded-to-address to
'https://github.com/batizhevsky/redmine_preten
Processing commands for cont...@bugs.debian.org:
> tags 925268 + upstream
Bug #925268 [redmine-plugin-pretend] redmine-plugin-pretend: breaks
configuration of redmine
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
925268: https://bugs.debi
Your message dated Sat, 10 Aug 2019 01:51:19 +
with message-id
and subject line Bug#924110: fixed in redmine-plugin-local-avatars 1.0.3-1
has caused the Debian Bug report #924110,
regarding redmine-plugin-local-avatars: fails to install: NoMethodError:
undefined method `to_prepare' for Action
Processing commands for cont...@bugs.debian.org:
> forwarded 924110 https://github.com/ncoders/redmine_local_avatars/issues/20
Bug #924110 [redmine-plugin-local-avatars] redmine-plugin-local-avatars: fails
to install: NoMethodError: undefined method `to_prepare' for
ActionDispatch::Callbacks:Cla
Processing commands for cont...@bugs.debian.org:
> tags 924110 + upstream
Bug #924110 [redmine-plugin-local-avatars] redmine-plugin-local-avatars: fails
to install: NoMethodError: undefined method `to_prepare' for
ActionDispatch::Callbacks:Class
Added tag(s) upstream.
> thanks
Stopping processin
Package: guayadeque
Version: 0.4.6.r2121.85c97c9~bionic-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
(guayadeque:4301): Gtk-ERROR **: 02:57:52.211: GTK+ 2.x symbols detected. Using
GTK+ 2.x and GTK+ 3 in the same process is not supported
-- System Information:
Deb
Source: zeroinstall-injector
Version: 2.12.3-2
Severity: serious
Dear Maintainer,
zeroinstall-injector build depends on obus, which is affected by
[1]. According to [2], it is an optional dependency. Please provide a
version of zeroinstall-injector without the dependency on obus.
It also seems t
Your message dated Sat, 10 Aug 2019 00:29:37 +0200
with message-id <20190809222937.uz3dsx7pelr6wnz5@function>
and subject line Re: kernel-wedge: HDA sound board detection takes 60s in d-i
has caused the Debian Bug report #931507,
regarding kernel-wedge: HDA sound board detection takes 60s in d-i
to
Processing commands for cont...@bugs.debian.org:
> tags 931507 + fixed-upstream
Bug #931507 [src:linux] kernel-wedge: HDA sound board detection takes 60s in d-i
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
931507: https://bugs.debia
Package: python-shade
Version: 1.30.0-2
Severity: serious
Tags: bullseye, sid
python-shade (build-)depends on the python-os-client-config and
python-openstacksdk binary packages which are no longer built by the
corresponding source packages.
It looks like it's time to drop python2 support from
Processing commands for cont...@bugs.debian.org:
> tags 933674 patch
Bug #933674 [pump] Buffer overflow during processing of large server replies in
"pump"
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
933674: https://bugs.debian.or
Yaroslav Halchenko wrote:
> If new version building is problematic, why not to upload just a patched
> version?
That would only delay the removal a bit: I'm sure that the current
version doesn't work with python3, so it's going to be removed sooner or
later from the archive.
Uploading the new up
Your message dated Fri, 09 Aug 2019 19:19:56 +
with message-id
and subject line Bug#934267: fixed in kconfig 5.54.0-2
has caused the Debian Bug report #934267,
regarding kconfig: CVE-2019-14744
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Processing commands for cont...@bugs.debian.org:
> found 934319 1.8.2-2
Bug #934319 {Done: Emmanuel Bourg } [src:icedtea-web]
CVE-2019-10181 CVE-2019-10182 CVE-2019-10185
Marked as found in versions icedtea-web/1.8.2-2.
> found 934319 1.7.2-2
Bug #934319 {Done: Emmanuel Bourg } [src:icedtea-web]
Processing commands for cont...@bugs.debian.org:
> tags 934319 + upstream
Bug #934319 {Done: Emmanuel Bourg } [src:icedtea-web]
CVE-2019-10181 CVE-2019-10182 CVE-2019-10185
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
934319: https://bug
Your message dated Fri, 09 Aug 2019 18:13:17 +
with message-id
and subject line Bug#933835: fixed in libreoffice 1:6.3.0-2
has caused the Debian Bug report #933835,
regarding libreoffice not start with fatal exception signal 11 when old
libreoffice-mysql-connector is installed
to be marked as
Processing control commands:
> tag -1 pending
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
when old libreoffice-mysql-connector is installed
Ignoring request to alter tags of bug #933835 to the same tags previously set
--
933835: https://bugs.debian.org/cgi-bin
Control: tag -1 pending
Hello,
Bug #933835 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/commit/22be2e
On Fri, Aug 09, 2019 at 08:18:53PM +0300, Timur Irikovich Davletshin wrote:
> I believe bug is to be reopened again to fix dependencies. Package
Did so (and fixed it in git)
> libreoffice-mysql-connector does exist for LO 6.3 and to be upgraded
> automatically or it will cause problem upgrading f
On Fri, Aug 09, 2019 at 08:21:55PM +0300, Timur Irikovich Davletshin wrote:
> If it was optional I don't get why it was changed? As far I understand
> it does exist in repo for LO 6.3.
Just as a dummy to upgrade to the new libreoffice-sdbc-mysql so that it
doesn't get lost in a upgrade.
in 6.1 it
Processing commands for cont...@bugs.debian.org:
> found 933835 1:6.2.0~alpha1-1
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
when old libreoffice-mysql-connector is installed
Marked as found in versions libreoffice/1:6.2.0~alpha1-1.
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> tags 933835 - moreinfo
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
when old libreoffice-mysql-connector is installed
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need ass
Processing commands for cont...@bugs.debian.org:
> tag 933835 + pending
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
when old libreoffice-mysql-connector is installed
Ignoring request to alter tags of bug #933835 to the same tags previously set
> thanks
Stopping
tag 933835 + pending
thanks
Hi,
On Fri, Aug 09, 2019 at 07:17:40PM +0200, Rene Engelhard wrote:
> On Fri, Aug 09, 2019 at 07:54:21PM +0300, Timur Irikovich Davletshin wrote:
> > I was wrong, problem is not in atk*. I rolled back snapshot of buster
> > to it's original state and tried to reproduce
Processing commands for cont...@bugs.debian.org:
> tags 933835 - unreproducible
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
when old libreoffice-mysql-connector is installed
Removed tag(s) unreproducible.
> thanks
Stopping processing here.
Please contact me if
Control: tag -1 pending
Hello,
Bug #933835 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/commit/22be2e
Processing control commands:
> tag -1 pending
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
when old libreoffice-mysql-connector is installed
Added tag(s) pending.
--
933835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933835
Debian Bug Tracking System
Con
If it was optional I don't get why it was changed? As far I understand
it does exist in repo for LO 6.3.
On Fri, 9 Aug 2019 19:10:28 +0200 Rene Engelhard
wrote:
> Or Conflicts. libreoffice-mysql-connector was an optional extension
> until 6.2
>
Processing commands for cont...@bugs.debian.org:
> reopen 933835
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
with old libreoffice-mysql-connector installed
Bug 933835 is not marked as done; doing nothing.
> retitle 933835 libreoffice not start with fatal excepti
Your message dated Fri, 09 Aug 2019 17:19:28 +
with message-id
and subject line Bug#934319: fixed in icedtea-web 1.8.3-1
has caused the Debian Bug report #934319,
regarding CVE-2019-10181 CVE-2019-10182 CVE-2019-10185
to be marked as done.
This means that you claim that the problem has been d
I confirm that purging works as expected now. I was asked before
deleting the data directory.
Michel Le Bihan
Le vendredi 09 août 2019 à 10:56 +0200, Christoph Berg a écrit :
> forcemerge 933368 923567
> close 933368 9.6.15-0+deb9u1
> thanks
>
> This has been fixed in yesterdays security release
Control: tag -1 pending
Hello,
Bug #934319 in icedtea-web 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/java-team/icedtea-web/commit/30836c182120405e218b31e6c
Processing control commands:
> tag -1 pending
Bug #934319 [src:icedtea-web] CVE-2019-10181 CVE-2019-10182 CVE-2019-10185
Added tag(s) pending.
--
934319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 09 Aug 2019 16:49:25 +
with message-id
and subject line Bug#934225: Removed package(s) from unstable
has caused the Debian Bug report #833513,
regarding Core needs update to cope with PPX-style syntax extensions
to be marked as done.
This means that you claim that the
Your message dated Fri, 09 Aug 2019 16:50:02 +
with message-id
and subject line Bug#870966: Removed package(s) from unstable
has caused the Debian Bug report #843312,
regarding Uninstallable on sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Your message dated Fri, 09 Aug 2019 16:50:02 +
with message-id
and subject line Bug#870966: Removed package(s) from unstable
has caused the Debian Bug report #843312,
regarding ocaml-textutils: FTBFS: build-dependency not installable:
libcore-ocaml-dev (>= 113.00.00-4~)
to be marked as done.
Your message dated Fri, 09 Aug 2019 16:49:25 +
with message-id
and subject line Bug#934225: Removed package(s) from unstable
has caused the Debian Bug report #843315,
regarding FTBFS: libsexplib-camlp4-dev is no longer available
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 09 Aug 2019 16:48:16 +
with message-id
and subject line Bug#934221: Removed package(s) from unstable
has caused the Debian Bug report #852913,
regarding ocaml-re2: FTBFS: unsatisfiable build-dependencies:
libcore-ocaml-dev, libpa-test-camlp4-dev, libbin-prot-camlp4-dev
Your message dated Fri, 09 Aug 2019 16:49:25 +
with message-id
and subject line Bug#934225: Removed package(s) from unstable
has caused the Debian Bug report #920146,
regarding janest-core-kernel: build-depends on libbin-prot-camlp4-dev
to be marked as done.
This means that you claim that the
Your message dated Fri, 09 Aug 2019 16:50:02 +
with message-id
and subject line Bug#870966: Removed package(s) from unstable
has caused the Debian Bug report #843312,
regarding FTBFS: libsexplib-camlp4-dev is no longer available
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 09 Aug 2019 16:47:44 +
with message-id
and subject line Bug#934220: Removed package(s) from unstable
has caused the Debian Bug report #904053,
regarding janest-core-extended: FTBFS (missing build-dep libbin-prot-camlp4-dev)
to be marked as done.
This means that you cla
Your message dated Fri, 09 Aug 2019 16:47:44 +
with message-id
and subject line Bug#934220: Removed package(s) from unstable
has caused the Debian Bug report #843320,
regarding FTBFS: libsexplib-camlp4-dev is no longer available
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 09 Aug 2019 16:44:06 +
with message-id
and subject line Bug#933943: Removed package(s) from unstable
has caused the Debian Bug report #885644,
regarding src:ovito: Configure failure with new qscintilla2 in experimental
to be marked as done.
This means that you claim th
Your message dated Fri, 09 Aug 2019 16:44:06 +
with message-id
and subject line Bug#933943: Removed package(s) from unstable
has caused the Debian Bug report #889557,
regarding ovito: (Build-)Depends on obsolete libbotan1.10-dev
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 09 Aug 2019 16:44:06 +
with message-id
and subject line Bug#933943: Removed package(s) from unstable
has caused the Debian Bug report #886340,
regarding FTBFS: Could not connect to display :0 during doc build
to be marked as done.
This means that you claim that the pro
Your message dated Fri, 09 Aug 2019 16:43:37 +
with message-id
and subject line Bug#933935: Removed package(s) from unstable
has caused the Debian Bug report #933821,
regarding python-tuskarclient (build-)depends on cruft package.
to be marked as done.
This means that you claim that the probl
Source: icedtea-web
Severity: grave
Tags: security
Please see https://www.openwall.com/lists/oss-security/2019/07/31/2
Cheers,
Moritz
Source: suricata
Version: 1:4.1.4-4
Severity: serious
Tags: patch upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
suricata fails to build with recent kernel versions:
| gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/lib/mips-l
Package: emacs
Version: 1:26.1+1-3.2
Severity: grave
Tags: upstream
The version of Emacs shipped in buster has a bug which causes synchronous HTTPS
requests to fail due to a GnuTLS race condition. It’s been reported and fixed
upstream: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34341
Known
Source: gertty
Version: 1.5.0-3
Severity: serious
Binary package python-alembic is no longer built from source and has
been removed from testing. As a result, gertty is currently unbuildable
in testing. Please make gertty build-depend on python3-alembic instead.
I have the same issue :
After upgrading to buster, the system doesn't boot anymore : it seems stuck
at "Loading initial ramdisk ..."
With kvm access, when I choose in grub menu xen-4.11-amd64 and either
kernel 4.9 or 4.19 , the system doesn't boot.
when I choose xen 4.8-amd64 and kernel 4.9 or
Processing commands for cont...@bugs.debian.org:
> tags 933930 upstream
Bug #933930 [network-manager] network-manager: Ethernet connection sometimes
fails with internal dhcp client
Added tag(s) upstream.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
93
On 2019-08-09 16:05:11 +0200, Beniamino Galvani wrote:
> in the traces I see that there are 3 servers and one of them
> advertises a subnet different from other two. This setup makes the
> behavior non-deterministic because clients can get an address either
> in the 10.0.1.0/24 or in the 140.77.12
Processing commands for cont...@bugs.debian.org:
> notfound 934301 2.24-1
Bug #934301 {Done: Axel Beckert } [ack] ack searches the
output file creating a loop
No longer marked as found in versions ack/2.24-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
934301
On Fri, Aug 09, 2019 at 01:10:55PM +0200, Vincent Lefevre wrote:
> On 2019-08-09 09:42:10 +0200, Beniamino Galvani wrote:
> > On Thu, Aug 08, 2019 at 06:07:41PM +0200, Vincent Lefevre wrote:
> ...
> > Could you capture DHCP packets with:
> >
> > tcpdump -i enp0s25 -s 0 -w dhcp.pcap udp port 67 o
Control: tags -1 + moreinfo
On Mon, 25 Feb 2019 at 10:58:49 +, Mark Hindley wrote:
> For desktops to be installable on such systems, policykit-1 needs to depend on
> the newly approved virtual packages default-logind and logind. In the latest
> upload of src:systemd, libpam-systemd provides de
Processing control commands:
> tags -1 + moreinfo
Bug #923240 [policykit-1] policykit-1: Please support alternative logind
implementations
Added tag(s) moreinfo.
--
923240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Your message dated Fri, 09 Aug 2019 12:35:22 +
with message-id
and subject line Bug#920339: fixed in matrix-synapse 1.2.1-2
has caused the Debian Bug report #920339,
regarding matrix-synapse: installation process hangs under sysvinit due to
matrix-synapse daemon not closing file descriptor fr
Hi
Thanks, I've been working on this in parallel and discovered the same
fixes :/
I'm testing metview-5.6, will merge changes
regards
Alastair
On 07/08/2019 16:31, Gianfranco Costamagna wrote:
Source: metview
Version: 5.3.0-3
Severity: serious
tags: patch
Hello, magics++ changed interpret
Package: rust-regex
Version: 1.2.1-1
Severity: serious
On 2019-08-09 12:10, Debian FTP Masters wrote:
>
>
> librust-regex-dev_1.2.1-1_s390x.deb: has 1 file(s) with a timestamp too far
> in the past:
> usr/share/cargo/registry/regex-1.2.1/Cargo.lock (Thu Jan 1 00:00:00 1970)
>
>
>
> ===
>
Hello,
Due to that the patch for polickit-1 in #923420 is not applied no
working desktop is possible w/o installing systemd (via libpam-systemd)
as pid 1. This effectively excludes usage of other init systems for
desktop usage. Please explain your decision on why desktops for other
init systems a
Processing commands for cont...@bugs.debian.org:
> severity 923240 serious
Bug #923240 [policykit-1] policykit-1: Please support alternative logind
implementations
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
923240:
Your message dated Fri, 09 Aug 2019 11:19:23 +
with message-id
and subject line Bug#933796: fixed in adios 1.13.1-19
has caused the Debian Bug report #933796,
regarding python3-adios: fails to upgrade from 'testing': unable to install new
version of '/usr/lib/python3/dist-packages/adios_openm
On 2019-08-09 09:42:10 +0200, Beniamino Galvani wrote:
> On Thu, Aug 08, 2019 at 06:07:41PM +0200, Vincent Lefevre wrote:
> > On 2019-08-08 13:37:04 +0200, Michael Biebl wrote:
> > > Bringing Vincent into the loop here.
> > >
> > > Vincent, can you gather the information Beniamino is asking for?
>
Your message dated Fri, 9 Aug 2019 13:08:01 +0200
with message-id <20190809110801.fhr3pjvvqr45c...@sym.noone.org>
and subject line Re: Bug#934301: ack searches the output file creating a loop
has caused the Debian Bug report #934301,
regarding ack searches the output file creating a loop
to be mark
Your message dated Fri, 09 Aug 2019 10:22:17 +
with message-id
and subject line Bug#930935: fixed in webkit2gtk 2.25.4-1
has caused the Debian Bug report #930935,
regarding webkit2gtk: Baseline violation on i386
to be marked as done.
This means that you claim that the problem has been dealt w
Control: severity -1 normal
Hi Judicael,
I cannot reproduce your issue here... So bug severity reduced to normal.
On Fr 09 Aug 2019 11:57:44 CEST, Judicael Courant wrote:
Control: reopen -1
Hi,
Thanks for your answer, unfortunately, the issue looks deeper:
I will close this bug, because
Processing control commands:
> severity -1 normal
Bug #933811 [src:fusiondirectory] fusiondirectory: Fusion directory install
fails as imagick is not detected
Severity set to 'normal' from 'grave'
--
933811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933811
Debian Bug Tracking System
Con
Processing control commands:
> reopen -1
Bug #933811 {Done: Mike Gabriel }
[src:fusiondirectory] fusiondirectory: Fusion directory install fails as
imagick is not detected
Bug reopened
Ignoring request to alter fixed versions of bug #933811 to the same values
previously set
--
933811: https:/
Control: reopen -1
Hi,
Thanks for your answer, unfortunately, the issue looks deeper:
> I will close this bug, because I think it's a user/admin issue. If you
> still think that fusiondirectory is buggy, please reopen this bug by
> putting "Control: reopen -1" into the first line of your rep
Package: ack
Version: 2.24-1
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
* What led up to the situation?
Searching a string in a folder with only a single file in it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I
Le 09/08/2019 à 11:06, Santiago Vila a écrit :
> Point releases exist to fix bugs like this one, so I don't see why I
> would have to stop reporting them.
If you do so, please amend the existing bugs instead of opening new ones
(in this case #909216 should have been unarchived and modified to cha
Processing commands for cont...@bugs.debian.org:
> unarchive 909216
Bug #909216 {Done: Emmanuel Bourg } [src:libjaxen-java]
libjaxen-java FTBFS: java.lang.IllegalArgumentException: Illegal character in
local name: 'pre:foo'
Unarchived Bug 909216
> found 909216 1.1.6-1
Bug #909216 {Done: Emmanuel
forcemerge 933368 923567
close 933368 9.6.15-0+deb9u1
thanks
This has been fixed in yesterdays security release.
On Thu, Aug 08, 2019 at 09:43:53AM +0200, Emmanuel Bourg wrote:
> If a build issue appeared *after* the release, due to a regression
> caused by a point release, then yes I think the issue is worth reporting
> (but I wouldn't bother reporting minor test failures that can be easily
> skipped to rebu
Processing commands for cont...@bugs.debian.org:
> forcemerge 933368 923567
Bug #933368 [postgresql-9.6] postgresql: Purging postgresql 9.6 removes content
of data_directory without any warning
Bug #923567 [postgresql-9.6] strong vote against deleting cluster on package
purge
Severity set to 'gr
Hi Salvatore,
> Although I'm late for the game ;-). You can use both
> 1:1.11.23-1~deb10u1 or 1:1.11.23-0+deb10u1. It is a matter of what you
> want the oxpress.
>
> 1:1.11.23-1~deb10u1 ... is mainly are rebuild of 1:1.11.23-1 with
> maybe some additional changes. Examples for this one are e.g. t
On Thu, Aug 08, 2019 at 06:07:41PM +0200, Vincent Lefevre wrote:
> On 2019-08-08 13:37:04 +0200, Michael Biebl wrote:
> > Bringing Vincent into the loop here.
> >
> > Vincent, can you gather the information Beniamino is asking for?
> >
> > Am 08.08.19 um 09:51 schrieb Beniamino Galvani:
> > > Wou
80 matches
Mail list logo
