Your message dated Wed, 09 Oct 2019 03:49:34 +
with message-id
and subject line Bug#941524: fixed in gitmagic 20160304-1.1
has caused the Debian Bug report #941524,
regarding gitmagic: build-depend on texlive-plain-generic, not obsolete
texlive-generic-recommended
to be marked as done.
This
Your message dated Tue, 8 Oct 2019 21:42:39 -0400
with message-id
and subject line Re: gnome: unable to start gnome-shell, cursor only with no
login
has caused the Debian Bug report #941908,
regarding gnome: unable to start gnome-shell, cursor only with no login
to be marked as done.
This
We had 5 computer affected by this problem. Every one of them booted
normally into the Gnome shell (one took two tries) after a full-
upgrade.
So as far as I can tell, this problem is solved.
Thanks for the hard work. One day after I submitted the report is
pretty good, even if the changes were
Your message dated Wed, 09 Oct 2019 00:49:27 +
with message-id
and subject line Bug#941880: fixed in gnome-shell-extension-easyscreencast
1.0.2+git20191008-1
has caused the Debian Bug report #941880,
regarding gnome-shell-extension-easyscreencast: Depends on gnome-shell << 3.33
to be marked
Processing commands for cont...@bugs.debian.org:
> found 941531 2.6.0-3
Bug #941531 {Done: Dirk Eddelbuettel } [gsl-doc] gsl-doc:
build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended
There is no source info for the package 'gsl-doc' at version '2.6.0-3' with
Processing commands for cont...@bugs.debian.org:
> found 941888 1.4~bzr32-1
Bug #941888 [qtqr] python-zbar: requires libzbar0 (= 0.22-1) but installed
libzbar0 is 0.23-1.1+b1
Marked as found in versions qr-tools/1.4~bzr32-1.
> tags 941888 + sid bullseye
Bug #941888 [qtqr] python-zbar: requires
Your message dated Wed, 09 Oct 2019 00:27:52 +
with message-id
and subject line Bug#941837: fixed in texlive-extra 2019.20190930-3
has caused the Debian Bug report #941837,
regarding texlive-fonts-extra: file conflice with (older)
texlive-fonts-extra-links
to be marked as done.
This means
Your message dated Wed, 9 Oct 2019 00:58:34 +0100
with message-id
and subject line re: check-manifest: needs a source-only upload
has caused the Debian Bug report #941957,
regarding check-manifest: needs a source-only upload
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 08 Oct 2019 23:49:11 +
with message-id
and subject line Bug#925628: fixed in afnix 2.9.2-2
has caused the Debian Bug report #925628,
regarding afnix: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> reassign 941143 src:graphviz 2.40.1-7
Bug #941143 {Done: Laszlo Boszormenyi (GCS) }
[libcgraph6,libcdt5,libpathplan4,libgvpr2,libxdot1,liblab-gamut1] multiarchify
graphviz libraries
Warning: Unknown package 'libxdot1'
Bug reassigned from
On Mon, Oct 07, 2019 at 10:44:12PM +0200, Thorsten Glaser wrote:
> On Mon, 7 Oct 2019, Jean-Marc LACROIX wrote:
> > It seems that now all is ok, because sysvinit is correctly installed on
> > Debian
> > 10.1
>
> Yes, but the other packages are not yet ready for elogind
> in Debian 10.anything
On Tue, 08 Oct 2019, Hilmar Preuße wrote:
> Do you have some time to care about this? I'm lost, sorry!
Uploading soon. Rather simple, the BerenisADFProSC fonts were obviously
dropped from Debian, so I reincluded them and they end up in the
texlive-extra-fonts package, while the links previously
On 10/8/19 2:06 PM, Moritz Mühlenhoff wrote:
> On Mon, Sep 30, 2019 at 09:34:46AM -0700, Matt Taggart wrote:
>> Hi,
>>
>>
>> I think it's fine for check-mk to be removed from unstable, if it does
>> end up in Debian again it will be repackaged and should go through NEW
>> again anyway.
>
> Ack,
Control: tag -1 - fixed-upstream
COntrol: notforwarded -1
On Tue, 08 Oct 2019 14:10:19 -0700, Chris Lamb wrote:
> This has apparently been fixed (again) upstream in version 1.67:
>
>
> https://github.com/redhotpenguin/perl-Archive-Zip/issues/51#issuecomment-539679696
Thanks for the notice
Processing control commands:
> tag -1 - fixed-upstream
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Removed tag(s) fixed-upstream.
> notforwarded -1
Bug #940973 [src:libarchive-zip-perl]
tags 940973 + fixed-upstream
thanks
This has apparently been fixed (again) upstream in version 1.67:
https://github.com/redhotpenguin/perl-Archive-Zip/issues/51#issuecomment-539679696
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
Processing commands for cont...@bugs.debian.org:
> tags 940973 + fixed-upstream
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please
On 10/6/19 10:04 AM, Ansgar Burchardt wrote:
Hi Norbert,
> when upgrading in Debian testing I saw the following error message:
>
> +---
> | Unpacking texlive-fonts-extra (2019.20190930-2) over (2019.20190830-1) ...
> | dpkg: error processing archive
>
On Mon, Sep 30, 2019 at 09:34:46AM -0700, Matt Taggart wrote:
> Hi,
>
>
> I think it's fine for check-mk to be removed from unstable, if it does
> end up in Debian again it will be repackaged and should go through NEW
> again anyway.
Ack, I've just filed a removal bug. I suppose the version
Source: dune-grid
Severity: serious
Dear Maintainer,
dune-grid build-depends on the python-vtk6 package, which was dropped
due to the python2-removal.
Please remove the package from build-depends.
Thanks,
Anton
Hi,
Am Dienstag, 8. Oktober 2019 schrieb Vlad Orlov:
> Hi,
>
> The migration to Python 3 and GI had been done in caja-dropbox 1.22.0.
> I guess we can close this
This can only ve closed once the Debian packaging has switched to Py3. I will
look into that after my VAC.
Mike
--
Gesendet von
Source: kopanocore
Version: 8.7.0-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: issue
Control: affects -1 src:perl
Dear maintainers,
With a recent upload of perl the autopkgtest of kopanocore fails in
testing when that
Processing control commands:
> affects -1 src:perl
Bug #941999 [src:kopanocore] kopanocore: autopkgtest tries to install packages
itself but doesn't exit appropriately if that fails
Added indication that 941999 affects src:perl
--
941999:
On 2019-10-08 16:03:40 +0200, gregor herrmann wrote:
> On Tue, 08 Oct 2019 15:47:50 +0200, Vincent Lefevre wrote:
>
> > Package: libsys-info-base-perl
> > Version: 0.7807-2
> > Severity: grave
> > Justification: renders package unusable
> >
> > I wanted to get the number of CPUs (see
Your message dated Tue, 08 Oct 2019 19:19:34 +
with message-id
and subject line Bug#941531: fixed in gsl-doc 2.6-1
has caused the Debian Bug report #941531,
regarding gsl-doc: build-depend on texlive-plain-generic, not obsolete
texlive-generic-recommended
to be marked as done.
This means
Package: openmpi-bin
Version: 3.1.3-11
Severity: serious
Hi,
This is tracked upstream as https://github.com/open-mpi/ompi/issues/7035 .
mpirun segfaults during MTL OFI provider section when run on a machine
with an InfiniBand network. This happens for the following reason: Until
version 3.1.2,
Your message dated Tue, 08 Oct 2019 19:07:59 +
with message-id
and subject line Bug#938804: fixed in vtk6 6.3.0+dfsg2-4
has caused the Debian Bug report #938804,
regarding vtk6: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding postgresql-11: fails to start after upgrade: EPERM on SSL snakeoil key
to be marked as done.
This means that you claim that
Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding postgresql-common: postgresql fails to start via systemd
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding perl 5.30.0 - Unable to set supplementary group IDs
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding FATAL: could not access private key file
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
to be marked as done.
Package: gnome-shell
Version: 3.34.0-2
Severity: grave
Justification: renders package unusable
On my computer, after upgrading to gnome-shell 3.34, I consistently get a
gnome-shell catastrophic failure about 10 seconds after logging in, but only
when running under Wayland. This error appears in
On Mon, 9 Sep 2019 14:25:31 +0200 Gianfranco Costamagna
wrote:
> Source: nftables
> Version: 0.9.2-1
> Severity: serious
> Justification: breaks another package from working correctly
>
> Hello, according to firewalld upstream devs, we need 2 commits to fixup their
> test failures.
> I also
Processing commands for cont...@bugs.debian.org:
> affects 939838 - firewalld
Bug #939838 [src:nftables] nftables: please apply upstream commits to fix
firewalld testsuite failures
Removed indication that 939838 affects firewalld
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> affects 939838 + firewalld
Bug #939838 [src:nftables] nftables: please apply upstream commits to fix
firewalld testsuite failures
Added indication that 939838 affects firewalld
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> affects 939838 + src:firewalld
Bug #939838 [src:nftables] nftables: please apply upstream commits to fix
firewalld testsuite failures
Added indication that 939838 affects src:firewalld
> thanks
Stopping processing here.
Please contact me if you
Control: tags -1 + patch
Hi,
Michael Crusoe a écrit le 04/10/2019 à 16:01 :
> Attached is a patch to force gcc 8; so far it has gotten farther than
> the previous failure for me (but my local build is still at 86%)
Looking at the related lines of /usr/include/c++/9/bits/stl_function.h,
it seems
Processing control commands:
> tags -1 + patch
Bug #935086 [src:insighttoolkit4] insighttoolkit4: FTBFS with GCC-9: use of
undeclared identifier '__builtin_is_constant_evaluated'
Added tag(s) patch.
--
935086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935086
Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:
> forcemerge 941948 941985
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL
snakeoil key
Bug #941973 [perl] FATAL: could not access private key
Your message dated Tue, 08 Oct 2019 17:06:48 +
with message-id
and subject line Bug#941650: fixed in python3.7 3.7.5~rc1-2
has caused the Debian Bug report #941650,
regarding python-iptables ftbfs in unstable: segfault
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> block 935737 with -1
Bug #935737 [release.debian.org] transition: perl
935737 was blocked by: 941920 941915 941933 941917 941919 941935 941926 941934
935737 was not blocking any bugs.
Added blocking bug(s) of 935737: 941989
--
935737:
Source: slic3r-prusa
Version: 1.41.2+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: block 935737 with -1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
During the perl transition we noticed that slic3r-prusa failed to
Package: perl
Version: 5.30.0-5
Forwarded: https://rt.perl.org/Public/Bug/Display.html?id=134169
Severity: serious
A regression in perl 5.30.0 breaks setting supplementary groups by
assigning a space-separated string to the $) variable. This breaks
postgresql-common, which relies on taking on
Hello,
back in 2009 Laszlo Kajan did quite some effort to package several
projects from rostlab.org for official Debian. There was a very good
cooperation between RostLab and Debian - mediated by Laszlo who was
introducing other members (who probably left Rostlab meanwhile to find
other jobs).
Source: backintime
Version: 1.1.24-0.1
Severity: serious
Dear maintainer,
Files in the source package matching qt4/docbook/en/* look to be under
the GFDL, not the GPL, as implied by d/copyright.
--
Sean Whitton
signature.asc
Description: PGP signature
Processing commands for cont...@bugs.debian.org:
> forwarded 941948 https://rt.perl.org/Ticket/Display.html?id=134169
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL
snakeoil key
Bug #941973
Processing commands for cont...@bugs.debian.org:
> reassign 941948 perl 5.30.0-5
Bug #941948 [postgresql-common] postgresql-common: postgresql fails to start
via systemd
Bug #941967 [postgresql-common] postgresql-11: fails to start after upgrade:
EPERM on SSL snakeoil key
Bug #941973
On Tue, 8 Oct 2019, Andreas Kurth wrote:
> A better fix is to add
>
> User=postgres
>
> to the [Service] section of your systemd unit file. This should be
Note that systemd-less operation with sysvinit is also broken,
so that alone is no fix.
bye,
//mirabilos
--
tarent solutions GmbH
On Tue, 8 Oct 2019, Christoph Berg wrote:
> reassign 941967 postgresql-common
Interestingly enough, the last postgresql-common update was
a week ago and did not introduce any errors (unless it’s the
combination of buggy postgresql-common and newer postgresql-11
of course).
bye,
//mirabilos
--
Processing control commands:
> clone -1 -2
Bug #941948 [postgresql-common] postgresql-common: postgresql fails to start
via systemd
Bug #941967 [postgresql-common] postgresql-11: fails to start after upgrade:
EPERM on SSL snakeoil key
Bug #941973 [postgresql-common] FATAL: could not access
Control: clone -1 -2
Control: reassign -2 perl 5.30.0-5
Control: severity -2 grave
Control: retitle -2 Setting groups via $) is broken in perl 5.30
Control: forwarded -2 https://rt.perl.org/Ticket/Display.html?id=134169
Control: block -1 -2
Re: C. Dominik Bodi 2019-10-07
Hi again,
I'm sorry to repeat myself but please pretty please help finding some
solution. Freemedform-project is about to be removed from Debian and
I see no way to prevent this.
Kind regards
Andreas.
On Sat, Sep 21, 2019 at 08:45:05AM +0200, Andreas Tille wrote:
> Hi Eric,
>
> any
Processing commands for cont...@bugs.debian.org:
> reassign 941967 postgresql-common
Bug #941967 [postgresql-11] postgresql-11: fails to start after upgrade: EPERM
on SSL snakeoil key
Bug reassigned from package 'postgresql-11' to 'postgresql-common'.
No longer marked as found in versions
On Tue, 08 Oct 2019 15:47:50 +0200, Vincent Lefevre wrote:
> Package: libsys-info-base-perl
> Version: 0.7807-2
> Severity: grave
> Justification: renders package unusable
>
> I wanted to get the number of CPUs (see Sys::Info::Device::CPU man page),
> but this fails at "use Sys::Info;":
>
> $
Package: libsys-info-base-perl
Version: 0.7807-2
Severity: grave
Justification: renders package unusable
I wanted to get the number of CPUs (see Sys::Info::Device::CPU man page),
but this fails at "use Sys::Info;":
$ perl -MSys::Info -e ''
Can't locate Sys/Info.pm in @INC (you may need to
Your message dated Tue, 08 Oct 2019 14:39:22 +0200
with message-id <87ftk3s96t@msgid.hilluzination.de>
and subject line Re: Bug#941934: libnbd: FTBFS on several architectures
has caused the Debian Bug report #941934,
regarding libnbd: FTBFS on several architectures
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> severity 937162 serious
Bug #937162 [src:nototools] nototools: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937162:
Your message dated Tue, 08 Oct 2019 11:19:33 +
with message-id
and subject line Bug#936579: fixed in gamin 0.1.10-6
has caused the Debian Bug report #936579,
regarding gamin: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
On Tue, Oct 08, 2019 at 03:51:47AM -0700, Robert Vaser wrote:
> Hi Andreas, yes I have a plan how to deal with it but I am not available for
> a week or more. Will let you know.
Thanks a lot. Just take your time until end of October since I'll be not
available until then. ;-)
Your message dated Tue, 08 Oct 2019 10:52:03 +
with message-id
and subject line Bug#941249: fixed in virt-manager 1:2.2.1-2
has caused the Debian Bug report #941249,
regarding virt-manager: Can not open detail of connection and detail or console
of a VM
to be marked as done.
This means that
Your message dated Tue, 08 Oct 2019 10:52:03 +
with message-id
and subject line Bug#941249: fixed in virt-manager 1:2.2.1-2
has caused the Debian Bug report #941249,
regarding virt-manager: Missing dependency from gir1.2-gtksource-4
to be marked as done.
This means that you claim that the
Your message dated Tue, 8 Oct 2019 06:27:49 -0400
with message-id
and subject line Re: caja-dropbox: Depends on unmaintained pygtk
has caused the Debian Bug report #885263,
regarding caja-dropbox: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 8 Oct 2019 06:25:56 -0400
with message-id
and subject line Re: epiphany-browser: arch:all builds fails
has caused the Debian Bug report #935786,
regarding epiphany-browser: arch:all builds fails
to be marked as done.
This means that you claim that the problem has been
clone 941971 -1
reassign -1 raspi-firmware
found -1 1.20190819-1
thanks
On Tue, 8 Oct 2019, Thorsten Glaser wrote:
> /etc/kernel/postinst.d/z50-raspi3-firmware contains this gem:
Same in sid: /etc/kernel/postinst.d/z50-raspi-firmware has:
91 if [ "$CONSOLES" = "auto" ]; then
92
Processing commands for cont...@bugs.debian.org:
> clone 941971 -1
Bug #941971 [raspi3-firmware] raspi3-firmware: serial console output sent to
bluetooth port with kernel 5.x
Bug 941971 cloned as bug 941974
> reassign -1 raspi-firmware
Bug #941974 [raspi3-firmware] raspi3-firmware: serial
On Mon, 07 Oct 2019 14:26:28 -0500 william l-k
wrote:
> Thank you for your suggestions. I'll give it try and report back.
gnome-shell 3.34 released to testing yesterday solving a similar issue (see
https://bugs.debian.org/941782).
Can you check if the problem you reported is also solved now
Package: raspi3-firmware
Version: 1.20190215-1+deb10u1
Severity: critical
Justification: breaks the whole system
I’ve set the severity high because this MIGHT break hardware,
but it it doesn’t (I don’t know enough to judge) feel free to
classify as less critical.
Hi,
The migration to Python 3 and GI had been done in caja-dropbox 1.22.0.
I guess we can close this?
On Tue, 8 Oct 2019, Thorsten Glaser wrote:
> [master ac9ac01] committing changes in /etc made by "apt-get --purge
> dist-upgrade"
FWIW, this upgrade was:
Unpacking postgresql-11 (11.5-3sid2) over (11.5-2+b1) ...
> Starting PostgreSQL 11 database server: mainError:
>
Package: postgresql-11
Version: 11.5-3sid2
Severity: grave
Justification: renders package unusable
[master ac9ac01] committing changes in /etc made by "apt-get --purge
dist-upgrade"
5 files changed, 4 insertions(+), 7 deletions(-)
E: Sub-process /usr/bin/dpkg returned an error code (1)
Your message dated Tue, 8 Oct 2019 09:59:38 +0200
with message-id <0ee01bdf-25d2-b055-01d2-fe68d0c1d...@debian.org>
and subject line Re: Bug#941913: [Debian Buster 10.1] [arm64] [python-dev] The
following packages have unmet dependencies:
has caused the Debian Bug report #941913,
regarding
On 10/4/19 3:07 PM, Andreas Tille wrote:
> Hi Olivier,
>
> On Fri, Oct 04, 2019 at 02:14:02PM +0200, olivier sallou wrote:
>>> Program received signal SIGSEGV: Segmentation fault - invalid memory
>>> reference.
>> I really do not see what error could be. Maybe a fortran issue after an
>> upgrade
control: severity -1 important
thanks
Hi Cord,
On Mon, Oct 07, 2019 at 01:44:51PM +0200, Cord Beermann wrote:
> Severity: grave
> all Plugins produce this Error after perl 5.30 migration
the mail on d-d-a asked not to file serious (or higher) bugs for issues
due to the perl transition, until
Processing control commands:
> severity -1 important
Bug #941898 [munin-node] munin-node: all Plugins fail with "Can't drop
privileges: at /usr/share/perl5/Munin/Node/Service.pm line 228."
Severity set to 'important' from 'grave'
--
941898:
74 matches
Mail list logo
