Followup-For: Bug #1016509
Do not forget python3-getfem:
Unpacking python3-getfem (5.4.1+dfsg1-1) ...
dpkg: error processing archive
/var/cache/apt/archives/python3-getfem_5.4.1+dfsg1-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/python3/dist-packages/getfem/__init__.py',
which
Processing control commands:
> block -1 with 1016510
Bug #1016511 [python3-pydevd] python3-pydevd: missing Breaks+Replaces:
python3-omegaconf (<< ???)
1016511 was not blocked by any bugs.
1016511 was not blocking any bugs.
Added blocking bug(s) of 1016511: 1016510
--
1016511:
Package: python3-pydevd
Version: 2.8.0+git20220714.32dee0b+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block -1 with 1016510
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files
Package: python3-omegaconf
Version: 2.1.0~rc1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Package: libgetfem-dev,libgetfem5,libgmm-dev
Version: 5.4.1+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Package: rapiddisk,rapiddisk-dkms
Version: 8.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Package: libghc-shake-doc,libghc-shake-dev,libghc-shake-data
Version: 0.19.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached
Am 01.08.2022 um 09:22 teilte Klaus Ethgen mit:
Am So den 31. Jul 2022 um 22:02 schrieb Hilmar Preuße:
Hi Klaus,
This sounds like a full file system during installation, which can lead to
various issues like this. I suggest to close the issue as "caused by full
file system".
Could be but I
On Sun, 2022-07-31 at 23:02 +0200, Andreas Beckmann wrote:
> Followup-For: Bug #1014633
>
> What about adding a superficial autopkgtest that tries to compile a
> dummy third-party kernel module using kbuild? That should help noticing
> such breakage earlier.
This is such an obviously good idea
Your message dated Mon, 01 Aug 2022 20:50:48 +
with message-id
and subject line Bug#1016305: fixed in nodejs 18.6.0+dfsg-4
has caused the Debian Bug report #1016305,
regarding nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1
to be marked as done.
This means that you claim that
Source: cctbx
Version: 2021.12+ds1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package cctbx, great. However,
it fails. Currently this failure is blocking the migration to testing
[1]. Can you please
Source: rope
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of rope the autopkgtest of rope fails in testing
when that autopkgtest is run with the binary packages of rope from
unstable. It passes when run with
Hi all,
This is a heads up that we are trying to remove python2.7 from bookworm.
Please either fix pam-python to use python3 or drop the dependency from
debian-edu-config.
Paul
[Release Team member hat on]
OpenPGP_signature
Description: OpenPGP digital signature
Installing the dbgsym packages makes the backtrace a little more
informative:
Backtrace for this error:
#0 0x7f889dd4b93f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
#1 0x7f889e3c5518 in __netcdf_nc_interfaces_MOD_addcnullchar
at
Your message dated Mon, 01 Aug 2022 20:10:30 +
with message-id
and subject line Bug#938345: fixed in redland-bindings 1.0.17.1+dfsg-2
has caused the Debian Bug report #938345,
regarding redland-bindings: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Source: python2-pip
Version: 20.3.4+dfsg-4
Severity: serious
Dear maintainers,
I'm surprised to see there's no RC bug against python2-pip yet, but
we're trying to not ship python2.7 with bookworm, which means this
package has to go too, right?
Paul
Control: tags 1015873 + patch
Control: tags 1015873 + pending
Dear maintainer,
I've prepared an NMU for libtirpc (versioned as 1.3.2-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
The corresponding merge request is at
Processing control commands:
> tags 1015873 + patch
Bug #1015873 [src:libtirpc] libtirpc: CVE-2021-46828
Added tag(s) patch.
> tags 1015873 + pending
Bug #1015873 [src:libtirpc] libtirpc: CVE-2021-46828
Added tag(s) pending.
--
1015873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015873
Hi,
Am Tue, Aug 02, 2022 at 01:38:58AM +0800 schrieb Shengjing Zhu:
> To fix the ABI breakage in spdlog/1.10, I request the fmt/9 transition
> afterwards.
> Since with fmt/9 translation, spdlog ABI will bump to
> libspdlog1-fmt9(from libspdlog1-fmt8) anyway.
A, OK, I missed that point. Feel
Hi Chris,
On 01-08-2022 21:24, Chris Lamb wrote:
b) Wait for the 4.x stream to become designated LTS. I believe this
should happen with version 4.2, due for release in about 6 or 7
months:
https://www.djangoproject.com/download/
That seems to happen after the Debian freeze
Hi Håvard, all,
On Wed, 27 Jul 2022 10:37:25 +0200 =?UTF-8?Q?H=c3=a5vard_F=2e_Aasen?=
wrote:
I have continued working on the redland-bindings package, cleaned it up a
bit, and enabled the Python 3 testsuite. I created an MR [1]. I believe
redland-bindings is ready to be uploaded to
Raphael Hertzog wrote:
> I'm surprised that we uploaded an non-LTS release to unstable.
>
> Chris, why did you do that?
Hmpf, this is deeply unfortunate. I was working under the incorrect
belief that the 4.0.x series was now the LTS branch. A number of
things encouraged this interpretation,
close 1015060 0.2.4.7-0.2
thanks
The bug has been fixed but was not properly marked as closed in the .changes
file.
--
â¢â£´â ¾â »â¢¶â£¦â
Processing commands for cont...@bugs.debian.org:
> close 1015060 0.2.4.7-0.2
Bug #1015060 [src:decopy] decopy: FTBFS: ValueError: Syntax or Parse error on
the line: "This file is called debian/copyright, but it doesn't follow the 1.0
format, on\n"
Marked as fixed in versions decopy/0.2.4.7-0.2.
Your message dated Mon, 1 Aug 2022 20:42:58 +0200
with message-id <5ff95d1b-3057-a349-bf75-69204f50f...@debian.org>
and subject line fixed in astrometry.net 0.89+dfsg-2
has caused the Debian Bug report #1016400,
regarding switch build depends on libnetpbm10-dev to libnetpbm-dev
to be marked as
Your message dated Mon, 1 Aug 2022 20:52:09 +0200
with message-id
and subject line Re: glib-d: FTBFS: ../meson.build:37:4: ERROR: Problem
encountered: Unable to build D intefaces from GIR:
has caused the Debian Bug report #1008403,
regarding glib-d: FTBFS: ../meson.build:37:4: ERROR: Problem
Processing commands for cont...@bugs.debian.org:
> severity 1010421 important
Bug #1010421 [ldc] gir-to-d: FTBFS with ldc 1.29
Bug #1011739 [ldc] gir-to-d: FTBFS: LinkedHasMap.d:27: undefined reference to
`_D6object__T8opEqualsTxC3gtd11GirFunctionQnTxQwZQBkFxQBexQBiZb'
Bug #1016433 [ldc] FTBFS:
severity 1010421 important
thankyou
Hi!
I'm reducing the severity since an easy-ish workaround is available and
keeping this at a blocking severity prevents the workaround-included
gir-to-d version to migrate.
This is still an important issue though which should be fixed for the
release, as
Processing commands for cont...@bugs.debian.org:
> reassign 1016433 ldc 1:1.29.0-1
Bug #1016433 [src:gir-to-d] FTBFS: undefined reference during linking
Bug reassigned from package 'src:gir-to-d' to 'ldc'.
No longer marked as found in versions gir-to-d/0.22.0-1.
Ignoring request to alter fixed
Heads up for those following this bug: qtav appears to be unmaintained
upstream.
My only interest in the package was to enable video playback in digikam.
Digikam upstream has taken most of the qtav code, incorporated into digikam
source tree and fixed it up. The next release of digikam
FTR,
To fix the ABI breakage in spdlog/1.10, I request the fmt/9 transition
afterwards.
Since with fmt/9 translation, spdlog ABI will bump to
libspdlog1-fmt9(from libspdlog1-fmt8) anyway.
See my comments on #1016418.
I'm not sure if the release team will be happy with that.
--
Shengjing Zhu
Processing commands for cont...@bugs.debian.org:
> affects 1016466 gnuradio
Bug #1016466 [libspdlog1] ImportError:
/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.10.3: undefined symbol
Bug #1015742 [libspdlog1] nheko: symbol lookup error: nheko: undefined symbol
Bug #1016408 [libspdlog1]
On Sun, 31 Jul 2022, Chris Hofstaedtler wrote:
I can't see a difference that should matter from userspace.
I have stared a bit at the kernel code... there have been quite some
changes and fixes in this area. Which kernel version were you
running when testing this?
Could you retry on
Processing commands for cont...@bugs.debian.org:
> retitle 1015742 libspdlog1: ABI breakage without SONAME bump
Bug #1015742 [libspdlog1] nheko: symbol lookup error: nheko: undefined symbol
Bug #1016408 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Bug #1016466 [libspdlog1]
Processing commands for cont...@bugs.debian.org:
> forcemerge 1015742 1016466
Bug #1015742 [libspdlog1] nheko: symbol lookup error: nheko: undefined symbol
Bug #1016408 [libspdlog1] libspdlog1: ABI breakage without SONAME bump
Bug #1016466 [libspdlog1] ImportError:
Hi Andreas,
On Sun, Jul 31, 2022 at 02:48:20PM +0200, Andreas Tille wrote:
> Hi Boyuan Yang,
>
> I admit symbols files are a maintenance burden for C++ libraries.
> However, it helps to spot ABI changes for new upstream versions. To
> reduce the maintenance burden while keeping that ABI change
Followup-For: Bug #1016385
The existing Breaks+Replaces must be bumped to (<< 0.9.28+dfsg-4)
since more files were moved into the -doc package.
Andreas
Your message dated Mon, 01 Aug 2022 16:36:55 +
with message-id
and subject line Bug#1016245: fixed in nanoflann 1.4.3+ds-2
has caused the Debian Bug report #1016245,
regarding mrpt: FTBFS: nanoflann.hpp:656:5: error: expected identifier before
numeric constant
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> block 1016180 by 1016396
Bug #1016180 [release.debian.org] transition: gnome-desktop 43
1016180 was blocked by: 1016175 1016171
1016180 was not blocking any bugs.
Added blocking bug(s) of 1016180: 1016396
>
End of message, stopping processing
Processing control commands:
> severity -1 normal
Bug #1016357 [golang-github-pion-turn.v2] Fails tests with insufficient network
connectivity
Severity set to 'normal' from 'serious'
--
1016357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016357
Debian Bug Tracking System
Contact
Control: severity -1 normal
On Fri, 29 Jul 2022 15:11:10 -0700 Sven Mueller
wrote:
> Package: golang-github-pion-turn.v2
> Version: 2.0.8-2
> Severity: Serious
>
> The package fails tests (see log of failing test below) when run on a
> machine with limited network (in this case: Can only reach
Your message dated Mon, 01 Aug 2022 13:06:32 +
with message-id
and subject line Bug#1016276: fixed in sight 21.1.1-2
has caused the Debian Bug report #1016276,
regarding sight: FTBFS: shared_ptr_base.h:1759:59: error: array subscript
‘sight::core::com::Slot,
const
Hi Paul,
I have checked in bonsai code base, and there is no reference to
should_close_asyncio_loop. It looks like a tornado thing.
However, looking at the full error trace, I can see that:
> ldapwhoami: unrecognized option -�
> Issue LDAP Who am I? operation to request user's authzid
>
>
With libx11-6 1.8.1 I get:
|glxinfo name of display: :0 glxinfo: ../nptl/pthread_mutex_lock.c:424:
__pthread_mutex_lock_full: Assertion `e != ESRCH || !robust' failed.
Abgebrochen|
rebuilding libx11 with the --disable-thread-safety-constructor flag
solved the issue.
|System: Host: box
On Tue, 26 Jul 2022, Paul Gevers wrote:
> Source: python-django
> Control: found -1 python-django/2:4.0.6-1
I'm surprised that we uploaded an non-LTS release to unstable.
Chris, why did you do that?
> I note that the changelog has this:
> "This security release mitigates the issue, but we have
Your message dated Mon, 01 Aug 2022 12:21:37 +
with message-id
and subject line Bug#1016449: fixed in samba 2:4.16.4+dfsg-1
has caused the Debian Bug report #1016449,
regarding samba: CVE-2022-2031 CVE-2022-32742 CVE-2022-32744 CVE-2022-32745
CVE-2022-32746
to be marked as done.
This means
Your message dated Mon, 01 Aug 2022 12:18:58 +
with message-id
and subject line Bug#1012908: fixed in cups-bjnp 2.0.3-4
has caused the Debian Bug report #1012908,
regarding cups-bjnp: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> forwarded 1016396
> https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/346
Bug #1016396 [src:squeekboard] squeekboard: fails to build on ppc64el
Set Bug forwarded-to-address to
Control: reassign -1 libspdlog1
Control: affects -1 gnuradio
* Jan - PE0SAT :
> ImportError: /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.10.3:
> undefined symbol:
> _ZN6spdlog5sinks15basic_file_sinkINS_7details10null_mutexEEC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb
Processing control commands:
> reassign -1 libspdlog1
Bug #1016466 [gnuradio] ImportError:
/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.10.3: undefined symbol
Bug reassigned from package 'gnuradio' to 'libspdlog1'.
No longer marked as found in versions gnuradio/3.10.3.0-2.
Ignoring request
Your message dated Mon, 01 Aug 2022 09:19:10 +
with message-id
and subject line Bug#1016226: fixed in entropybroker 2.9-7
has caused the Debian Bug report #1016226,
regarding entropybroker: FTBFS: graph.cpp:160:33: error: ‘localtime’ was not
declared in this scope
to be marked as done.
This
Your message dated Mon, 01 Aug 2022 09:04:23 +
with message-id
and subject line Bug#1016209: fixed in mangohud 0.6.8-1
has caused the Debian Bug report #1016209,
regarding mangohud fails with symbol lookup error
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> reassign -1 src:sphinx-markdown-tables
Bug #1016251 [src:python-lark] python-lark: FTBFS: Handler for event 'source-read' threw an exception
(exception: TableProcessor.__init__() missing 1 required positional argument:
'config')
Bug reassigned from package
Control: reassign -1 src:sphinx-markdown-tables
Control: found -1 0.0.15-3
Control: tags -1 + fixed-upstream
Control: affects -1 src:python-lark
thanks
Dear Lucas,
thanks for reporting this problem. It seems that the root cause of this
FTBFS issue is a breaking change in python-markdown 3.4
Your message dated Mon, 01 Aug 2022 07:40:38 +
with message-id
and subject line Bug#108: fixed in python2.7 2.7.18-13.2
has caused the Debian Bug report #108,
regarding libpython2.7-stdlib: Hardcoded dependency on libssl1.1
to be marked as done.
This means that you claim that the
reopen 1003165
thanks
The astrometry.net d.changelog contains a reference to the wrong bug.
Please consider using debchange --closes in future which checks that
the bug number assigned to the package being uploaded.
1016400 has not been closed.
On Sun, 31 Jul 2022 14:35:33 + Debian FTP
Processing commands for cont...@bugs.debian.org:
> reopen 1003165
Bug #1003165 {Done: Ole Streicher } [src:scikit-learn]
scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will
Processing commands for cont...@bugs.debian.org:
> reassign 1016245 libnanoflann-dev 1.4.3+ds-1
Bug #1016245 [src:mrpt] mrpt: FTBFS: nanoflann.hpp:656:5: error: expected
identifier before numeric constant
Bug reassigned from package 'src:mrpt' to 'libnanoflann-dev'.
No longer marked as found in
58 matches
Mail list logo
