Package: nextcloud-desktop
Version: 3.0.1-1
Severity: grave
Justification: causes non-serious data loss
I had 3 synchronized folders, after upgrade I had only the first defined,
configuration of other synchronized folders was lost.
-- System Information:
Debian Release: bullseye/sid
APT prefe
Your message dated Tue, 8 Sep 2020 08:20:40 +0200
with message-id <20200908062040.ga15...@lorien.valinor.li>
and subject line Re: Bug#941712: hfs partitions corrupted when removing lots of
files over network
has caused the Debian Bug report #941712,
regarding hfs partitions corrupted when removing
Source: linux
Source-Version: 4.19.118-1
Hi Graham,
On Mon, Sep 07, 2020 at 01:45:00PM +1000, Graham Coster wrote:
> Hi Salvatore,
>
> Thank you for following up on this. Unfortunately I can no longer test
> this out. The hardware is no longer unavailable and since "upgrading" to
> Catalina I
Your message dated Tue, 08 Sep 2020 03:33:45 +
with message-id
and subject line Bug#966698: fixed in rasdaemon 0.6.6-2
has caused the Debian Bug report #966698,
regarding rasdaemon: fails to start by default under systemd due to
EnvironmentFile=/etc/sysconfig/rasdaemon
to be marked as done.
Your message dated Tue, 08 Sep 2020 03:33:45 +
with message-id
and subject line Bug#966698: fixed in rasdaemon 0.6.6-2
has caused the Debian Bug report #966698,
regarding rasdaemon: fails to start by default under systemd due to
EnvironmentFile=/etc/sysconfig/rasdaemon
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> reassign 969768 libio-socket-ip-perl
Bug #969768 [src:libio-socket-io-perl] lib-io-socket-ip-perl: do not release
with bullseye
Warning: Unknown package 'src:libio-socket-io-perl'
Bug reassigned from package 'src:libio-socket-io-perl' to
'libio-
Your message dated Mon, 07 Sep 2020 23:03:28 +
with message-id
and subject line Bug#964902: fixed in libio-socket-ip-perl 0.39-3
has caused the Debian Bug report #964902,
regarding libio-socket-ip-perl: AI_ADDRCONFIG breaks many test suites on
IPv6-only hosts
to be marked as done.
This means
Control: tags -1 + confirmed pending
Hi,
thanks for the report.
> Aug 31 16:47:00 tucano named[786855]: resolver.c:5125:
> INSIST(dns_name_issubdomain(&fctx->name, &fctx->domain)) failed, back trace
I see that Ondrej has added an upstream patch to fix this in the git repo.
https://salsa.debia
Processing control commands:
> tags -1 + confirmed pending
Bug #969448 [bind9] bind9: dies with assertion and does not restart
Added tag(s) pending and confirmed.
--
969448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Processing commands for cont...@bugs.debian.org:
> tags 969768 + sid bullseye
Bug #969768 [src:libio-socket-io-perl] lib-io-socket-ip-perl: do not release
with bullseye
Warning: Unknown package 'src:libio-socket-io-perl'
Added tag(s) bullseye and sid.
Warning: Unknown package 'src:libio-socket-io
Processing control commands:
> severity -1 serious
Bug #877740 [gedit-latex-plugin] gedit-latex-plugin: Depends: gvfs-bin, which
contains only deprecated tools
Severity set to 'serious' from 'normal'
--
877740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877740
Debian Bug Tracking System
Processing control commands:
> tag -1 pending
Bug #964902 [libio-socket-ip-perl] libio-socket-ip-perl: AI_ADDRCONFIG breaks
many test suites on IPv6-only hosts
Added tag(s) pending.
--
964902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964902
Debian Bug Tracking System
Contact ow...@bugs
Control: tag -1 pending
Hello,
Bug #964902 in libio-socket-ip-perl 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/perl-team/modules/packages/libio-socket-ip-pe
Source: libio-socket-io-perl
Version: 0.39-2
Severity: serious
Justification: maintainer
IO-Socket-IP is bundled with perl 5.30, so there is no need to ship
this separately.
Oh, the kernel error message might be helpful:
curl[4979] general protection ip:7f3a3da00bce sp:7fff5dc217d0 error:0 in
libcrypto.so.1.1[7f3a3d8fe000+19e000]
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of
Hello,
another additional diff:
--- diffoscope-159ubuntu1/tests/comparators/test_directory.py 2020-09-04
12:12:52.0 +0200
+++ diffoscope-159ubuntu2/tests/comparators/test_directory.py 2020-09-07
20:46:23.0 +0200
@@ -33,6 +33,7 @@
TEST_FILE2_PATH = data("text_ascii2")
+@
On Sun, Sep 6, 2020 at 02:37:22PM +0200, Bernhard Übelacker wrote:
> Hello Bruce Momjian,
> thanks for the details and confirmation.
>
>
> Am 05.09.20 um 17:32 schrieb Bruce Momjian,,,:
> > (gdb) print pmeth->init
> > $1 = (int (*)(EVP_PKEY_CTX *)) 0xf0e0d0c0b0a0908
>
> > gdb) print
Source: binutils-mingw-w64
Version: 8.9
Severity: serious
Control: close -1 8.10
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 964742
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of
Hi,
On Mon, 7 Sep 2020 22:12:21 +0200 Paul Gevers wrote:
> Currently this regression is blocking the migration of networkx to
> testing [1]. Due to the nature of this issue, I filed this bug report
> against both packages. Can you please investigate the situation and
> reassign the bug to the rig
Processing control commands:
> close -1 0.3.0-4
Bug #969757 [src:python-py2bit] src:python-py2bit: fails to migrate to testing
for too long: FTBFS on s390x
Marked as fixed in versions python-py2bit/0.3.0-4.
Bug #969757 [src:python-py2bit] src:python-py2bit: fails to migrate to testing
for too lo
Source: python-py2bit
Version: 0.3.0-3
Severity: serious
Control: close -1 0.3.0-4
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Processing control commands:
> close -1 8.10
Bug #969758 [src:binutils-mingw-w64] src:binutils-mingw-w64: fails to migrate
to testing for too long: FTBFS on s309x
Marked as fixed in versions binutils-mingw-w64/8.10.
Bug #969758 [src:binutils-mingw-w64] src:binutils-mingw-w64: fails to migrate
to
Processing control commands:
> found -1 networkx/2.5+ds-1
Bug #969756 [src:networkx, src:botch] networkx breaks botch autopkgtest:
KeyError: 'long'
Marked as found in versions networkx/2.5+ds-1.
> found -1 botch/0.22-4
Bug #969756 [src:networkx, src:botch] networkx breaks botch autopkgtest:
KeyE
Source: networkx, botch
Control: found -1 networkx/2.5+ds-1
Control: found -1 botch/0.22-4
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of networkx the autopkgt
[When possible/appropriate, please preserve the 968403-forwarded address
in replies.]
This was recently discovered by the Debian buildds in the unstable
distribution, and I can reliably reproduce it on an i386 porterbox in an
unstable i386 chroot. Please let me know if I can assist with any
fu
Your message dated Mon, 07 Sep 2020 14:02:28 -0500
with message-id <87h7s92ywr@trouble.defaultvalue.org>
has caused the report #968403,
regarding numbers.test fails on i386
to be marked as having been forwarded to the upstream software
author(s) bug-gu...@gnu.org
(NB: If you are a system adm
Source: diffoscope
Version: 159
Severity: serious
Hello, autopkgtests looks sad, pytest-with-recommends works, while pytest
doesn't, because of missing pgpdump
I did add some @skip_unless_tools_exist("pgpdump") around the failing tests
(attached the diff), however I don't know
if this is the ri
Control: tags -1 pending
Hi,
On 06-09-2020 21:05, Paul Gevers wrote:
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd. Unfortunately the Debian infrastructure
> doesn't allow arch:all packages to be properly binNMU'ed. Normally, I
> would do a no-ch
Processing control commands:
> tags -1 pending
Bug #969660 {Done: Paul Gevers } [src:cpio] src:cpio: fails
to migrate to testing for too long: maintainer built arch:all binaries
Ignoring request to alter tags of bug #969660 to the same tags previously set
--
969660: https://bugs.debian.org/cgi-
Processing control commands:
> tags -1 pending
Bug #969493 {Done: Paul Gevers } [src:nanook] src:nanook:
fails to migrate to testing for too long: maintainer built arch:all binaries
Ignoring request to alter tags of bug #969493 to the same tags previously set
--
969493: https://bugs.debian.org/
Control: tags -1 pending
Hi,
On 03-09-2020 20:46, Paul Gevers wrote:
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd. Unfortunately the Debian infrastructure
> doesn't allow arch:all packages to be properly binNMU'ed. Normally I
> would do a no-cha
On samedi 5 septembre 2020 13:14:55 CEST gregor herrmann wrote:
> Could not find CompUnit::Repository::Staging in:
> inst#/root/.raku
> inst#/usr/share/perl6/site
> inst#/usr/share/perl6/vendor
> inst#/usr/share/perl6/core
Perl6 modules are installed in /usr/lib/perl6. Raku is not
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:offlineimap
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Your message dated Mon, 07 Sep 2020 17:00:09 +
with message-id
and subject line Bug#969123: fixed in ublock-origin 1.29.0+dfsg-1
has caused the Debian Bug report #969123,
regarding webext-ublock-origin: FF80 broke ublock again
to be marked as done.
This means that you claim that the problem h
Package: xserver-xorg-core
Version: 2:1.20.9-1
Severity: grave
Same setup was working with 2:1.20.7-2, but with 2:1.20.9-1 crashes on
startup (xinit). /var/log/Xorg.0.log follows:
[881147.371]
X.Org X Server 1.20.9
X Protocol Version 11, Revision 0
[881147.371] Build Operating System: Linux 4.19.
@Bernhard:
> And if Thunar crashes too, are there also a segfault line?"
Sadly didn't find anything by the time I checked. I had to poweroff due to my
country going through a(nother) of its series of planned power outages.
Inkscape played up today again...
> But proper backtraces migh
Your message dated Mon, 07 Sep 2020 14:49:13 +
with message-id
and subject line Bug#964670: fixed in gsettings-qt 0.2-3
has caused the Debian Bug report #964670,
regarding gsettings-qt: FTBFS: QQmlComponent: Component is not ready
to be marked as done.
This means that you claim that the probl
Processing control commands:
> tag -1 pending
Bug #964670 [src:gsettings-qt] gsettings-qt: FTBFS: QQmlComponent: Component is
not ready
Added tag(s) pending.
--
964670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Control: tag -1 pending
Hello,
Bug #964670 in gsettings-qt 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/ubports-team/gsettings-qt/-/commit/39ca2a132860cf8a61
Your message dated Mon, 07 Sep 2020 12:18:47 +
with message-id
and subject line Bug#969316: fixed in qtpim-opensource-src
5.0~git20190618.8fec622c+dfsg1-2
has caused the Debian Bug report #969316,
regarding qtpim-opensource-src FTBFS: test failure
to be marked as done.
This means that you cl
Your message dated Mon, 07 Sep 2020 11:03:24 +
with message-id
and subject line Bug#967088: fixed in fflas-ffpack 2.4.3-2
has caused the Debian Bug report #967088,
regarding fflas-ffpack: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1
returned exit code 2
to be marked as done.
This mea
Your message dated Mon, 07 Sep 2020 09:03:30 +
with message-id
and subject line Bug#968981: fixed in qtfeedback-opensource-src
5.0~git20180329.a14bd0bb-2
has caused the Debian Bug report #968981,
regarding qtfeedback-opensource-src FTBFS: Error copying
/<>/doc/qtfeedback to
/<>/debian/tmp/u
Processing control commands:
> tag -1 pending
Bug #968981 [src:qtfeedback-opensource-src] qtfeedback-opensource-src FTBFS:
Error copying /<>/doc/qtfeedback to
/<>/debian/tmp/usr/share/qt5/doc/qtfeedback: Cannot open
/<>/doc/qtfeedback for input
Added tag(s) pending.
--
968981: https://bugs.de
Control: tag -1 pending
Hello,
Bug #968981 in qtfeedback-opensource-src 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/qt-kde-team/qt/qtfeedback/-/commit/05be5
Source: petsc4py
Version: 3.13.0-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 3.13.0-4, petsc4py has been failing its own
autopkgtests on ppc64el [1]. I've copied what I hope is the relevant
p
I think the upper bound is just bogus and should be removed. Upstream
seems to have added it under the assumption that cryptography follows
semver, but it does not: 2.9 to 3.0 offers the same compatibility
guarantees as 2.8 to 2.9.
46 matches
Mail list logo
