Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Manphiz]

Nicholas D Steeves  writes:

> Hello,
>
> Would you like to fix this RC bug and adopt the package?
>
>   https://bugs.debian.org/1042911
>
> and the orphan bug is here: #1016558
>
> Best,
> Nicholas
>

Hi Nicolas,

Thanks for reaching out!  Looks like this was caused by the removal of
the obsolete "assoc" package in Emacs 29.1 which had been deprecated
since 24.  I'll try to work on a fix later this week.

-- 
Manphiz


signature.asc
Description: PGP signature

Bug#1042937: libsasl2-dev should depend on libssl-dev

[Sergio Durigan Junior]

Source: cyrus-sasl2
Version: 2.1.28+dfsg1-2
Severity: grave

Hi there,

I noticed that the last upload for cyrus-sasl2 removed the md5.h header
file (among other stuff).  As it turns out, /usr/include/sasl/hmac-md5.h
will include  which will make builds using the header
FTBFS.  This is currently the case with OpenLDAP.

I'd like to request that libsasl2-dev depend on libssl-dev so that we
can get a working md5.h.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1042936: scipy autopkg tests fail on armhf in unstable

[Matthias Klose]

Package: src:scipy
Version: 1.10.1-2
Severity: serious
Tags: sid trixie

one failure in the openblas autopkg tst

see https://ci.debian.net/data/autopkgtest/testing/armhf/s/scipy/36350169/log.gz

[...]
1593s === FAILURES 
===
1593s __ TestExpmFrechet.test_fuzz 
___
1593s /usr/lib/python3/dist-packages/scipy/linalg/tests/test_matfuncs.py:795: in 
test_fuzz

1593s assert_allclose(expected_expm, observed_expm, atol=5e-8)
1593s A  = array([[1.29500584e-01, 2.93812784e-02, 
4.06752600e-01],
1593s[1.06990066e+00, 1.92639780e-01, 1.89295833e-01],
1593s[9.04790698e-05, 1.52946804e-01, 9.71213319e-01]])
1593s A_original = array([[4.62247608e-01, 1.04875401e-01, 
1.45188856e+00],
1593s[3.81897135e+00, 6.87620661e-01, 6.75684567e-01],
1593s[3.22961737e-04, 5.45938033e-01, 3.46671049e+00]])
1593s A_original_norm_1 = 5.594283612854939
1593s E  = array([[1.05141771, 0.02556283, 0.30353237],
1593s[0.04803694, 1.38737301, 0.21559779],
1593s[0.33469411, 0.02223573, 0.20598777]])
1593s E_original = array([[3.75299715, 0.0912456 , 1.08344772],
1593s[0.1714661 , 4.95217733, 0.76956845],
1593s[1.19467841, 0.07936964, 0.73526584]])
1593s M  = array([[1.29500584e-01, 2.93812784e-02, 
4.06752600e-01, 1.05141771e+00,

1593s 2.55628339e-02, 3.03532371e-01],
1593s  ...-01],
1593s[0.e+00, 0.e+00, 0.e+00, 9.04790698e-05,
1593s 1.52946804e-01, 9.71213319e-01]])
1593s expected_expm = array([[1.17278791, 0.08410441, 0.36956138],
1593s[1.27548153, 1.27086948, 0.69467426],
1593s[0.12925538, 0.28389489, 2.69125205]])
1593s expected_frechet = array([[1.37086962, 0.16031551, 1.00697241],
1593s[1.71725501, 1.80776158, 1.2305117 ],
1593s[0.73936754, 0.26382299, 0.77190579]])
1593s i  = 79
1593s n  = 3
1593s ntests = 100
1593s observed_expm = array([[1.17278791, 0.08410441, 0.73912276],
1593s[1.27548153, 1.27086948, 0.69467426],
1593s[0.12925538, 0.28389489, 2.69125205]])
1593s observed_frechet = array([[1.37086962, 0.16031551, 1.00697241],
1593s[1.71725501, 1.80776158, 1.2305117 ],
1593s[0.73936754, 0.26382299, 0.77190579]])
1593s rfunc  = numpy.random.mtrand.RandomState object at 0xd0b266a8>
1593s rfuncs = (numpy.random.mtrand.RandomState object at 0xd0b266a8>, of numpy.r...ndomState object at 0xd0b266a8>, numpy.random.mtrand.RandomState object at 0xd0b266a8>)

1593s scale  = 0.2801541468532912
1593s self   = object at 0xcdccc250>

1593s target_norm_1 = 1.567261752814723
1593s /usr/lib/python3.11/contextlib.py:81: in inner
1593s return func(*args, **kwds)
1593s E   AssertionError:
1593s E   Not equal to tolerance rtol=1e-07, atol=5e-08
1593s E
1593s E   Mismatched elements: 1 / 9 (11.1%)
1593s E   Max absolute difference: 0.36956138
1593s E   Max relative difference: 0.5
1593s Ex: array([[1.172788, 0.084104, 0.369561],
1593s E  [1.275482, 1.270869, 0.694674],
1593s E  [0.129255, 0.283895, 2.691252]])
1593s Ey: array([[1.172788, 0.084104, 0.739123],
1593s E  [1.275482, 1.270869, 0.694674],
1593s E  [0.129255, 0.283895, 2.691252]])
1593s args   = (.compare at 
0xcb71a2f8>, array([[1.17278791, 0.08410441, 0.36956138],

1593s[1.275...1, 0.08410441, 0.73912276],
1593s[1.27548153, 1.27086948, 0.69467426],
1593s[0.12925538, 0.28389489, 2.69125205]]))
1593s func   = 
1593s kwds   = {'equal_nan': True, 'err_msg': '', 'header': 'Not 
equal to tolerance rtol=1e-07, atol=5e-08', 'verbose': True}
1593s self   = 0xcffcab50>
1593s === short test summary info 

1593s FAILED ../../tests/test_matfuncs.py::TestExpmFrechet::test_fuzz - 
AssertionEr...
1593s = 1 failed, 1911 passed, 6 skipped, 1653 deselected, 14 xfailed, 1 xpassed 
in 30.57s =

Bug#1042935: sagemath autopkg tests fail on i386 in unstable

[Matthias Klose]

Package: src:sagemath
Version: 9.5-6
Severity: serious
Tags: sid trixie

see 
https://ci.debian.net/data/autopkgtest/testing/i386/s/sagemath/36323965/log.gz

[...]
7183s Total time for all tests: 6888.5 seconds
7183s cpu time: 10109.5 seconds
7183s cumulative wall time: 13105.7 seconds
7183s Features detected for doctesting: 
sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sagemath_doc_html,sphinx

7183s Pytest is not installed, skip checking tests that rely on it.
7183s Success: 186 tests failed, up to 200 failures are tolerated
7183s Error: critical test failures (e.g. timeout, segfault, etc.)
7183s make: *** [debian/tests.mk:57: had-few-failures] Error 1

Bug#1042934: pytango autopkg tests fail on amd64 in unstable

[Matthias Klose]

Package: src:pytango
Version: 9.3.6-2.1
Severity: serious
Tags: sid trixie

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytango/36334683/log.gz

[...]
155s === FAILURES 
===
155s ___ test_subscribe_data_ready_event[Futures] 
___

155s event_device = EventDevice(test/nodb/eventdevice)
155s
155s def test_subscribe_data_ready_event(event_device):
155s results_data_ready_event = []
155s
155s def callback_data_ready(evt):
155s results_data_ready_event.append(evt.ctr)
155s
155s # Subscribe to data ready event
155s eid_data_ready = event_device.subscribe_event(
155s "attr", EventType.DATA_READY_EVENT, callback_data_ready, 
wait=True)
155s assert eid_data_ready == 1
155s # Trigger an event
155s event_device.command_inout("send_data_ready_event", wait=True)
155s # Wait for tango event
155s retries = 20
155s for _ in range(retries):
155s event_device.read_attribute("state", wait=True)
155s if len(results_data_ready_event):
155s break
155s time.sleep(0.05)
155s # Test the event values
155s >   assert results_data_ready_event == [2]
155s E   assert [] == [2]
155s E Right contains one more item: 2
155s E Full diff:
155s E - [2]
155s E ?  -
155s E + []
155s
155s tests/test_event.py:146: AssertionError
155s  Captured stdout setup 
-

155s Ready to accept request
155s  Captured stderr setup 
-

155s Can't create notifd event supplier. Notifd event not available
155s === warnings summary 
===

155s ../../../../usr/lib/python3/dist-packages/tango/utils.py:176
155s   /usr/lib/python3/dist-packages/tango/utils.py:176: DeprecationWarning: 
`np.bool8` is a deprecated alias for `np.bool_`.  (Deprecated NumPy 1.24)

155s CmdArgType.DevBoolean: numpy.bool8,
155s
155s tests/test_client.py:19
155s 
/tmp/autopkgtest-lxc.p9321foh/downtmp/autopkgtest_tmp/tests/test_client.py:19: 
DeprecationWarning: The distutils package is deprecated and slated for removal 
in Python 3.12. Use setuptools or check PEP 632 for potential alternatives

155s from distutils.spawn import find_executable
155s
155s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
155s === short test summary info 


155s FAILED tests/test_event.py::test_subscribe_data_ready_event[Futures]
155s == 1 failed, 1092 passed, 26 xfailed, 2 warnings in 99.86s (0:01:39) 
===

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

[Matthias Klose]

Package: src:octave-statistics
Version: 1.6.0-1
Severity: serious
Tags: sid trixie

octave autopkg tests fail in unstable on amd64 (triggered by gcc-13).

https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-statistics/36329437/log.gz

Not sure which ones are the regressions, because all failures seem to be marked 
as "known failure".

Bug#1035640: marked as done (python-magic: FTBFS with tox 4)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 01:00:02 +
with message-id 
and subject line Bug#1035640: fixed in python-magic 2:0.4.27-1
has caused the Debian Bug report #1035640,
regarding python-magic: FTBFS with tox 4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1035640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-magic
Version: 2:0.4.26-3
Severity: normal

tox 4 is now available in experimental, but it causes git-magic to
FTBFS. See bug 1035635 for a discussion of the general issues around tox
4.

This appears to be caused by the whitelist_externals ->
allowlist_externals rename:
https://tox.wiki/en/latest/changelog.html#deprecations-and-removals-4-0-0rc4

Log snippet:

   dh_auto_test -O--buildsystem=pybuild -O--test-tox
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; tox -c 
/<>
/tox.ini --sitepackages -e py311
py311: install_deps .pybuild/cpython3_3.11/build> python -I -m pip install 
coverage pytest '.[
test]'
.pkg: install_requires .pybuild/cpython3_3.11/build> python -I -m pip install 
'setuptools>=40.
8.0' wheel
.pkg: _optional_hooks .pybuild/cpython3_3.11/build> python 
/usr/lib/python3/dist-packages/pypr
oject_api/_backend.py True setuptools.build_meta __legacy__
.pkg: get_requires_for_build_sdist .pybuild/cpython3_3.11/build> python 
/usr/lib/python3/dist-
packages/pyproject_api/_backend.py True setuptools.build_meta __legacy__
.pkg: prepare_metadata_for_build_wheel .pybuild/cpython3_3.11/build> python 
/usr/lib/python3/d
ist-packages/pyproject_api/_backend.py True setuptools.build_meta __legacy__
.pkg: build_sdist .pybuild/cpython3_3.11/build> python 
/usr/lib/python3/dist-packages/pyprojec
t_api/_backend.py True setuptools.build_meta __legacy__
py311: install_package .pybuild/cpython3_3.11/build> python -I -m pip install 
--force-reinstal
l --no-deps /<>/.tox/.tmp/package/1/python-magic-0.4.26.tar.gz
py311: commands[0] .pybuild/cpython3_3.11/build> python3-coverage run -m pytest
py311: failed with python3-coverage is not allowed, use allowlist_externals to 
allow it
.pkg: _exit .pybuild/cpython3_3.11/build> python 
/usr/lib/python3/dist-packages/pyproject_api/
_backend.py True setuptools.build_meta __legacy__
  py311: FAIL code 1 (4.34 seconds)
  evaluation failed :( (4.42 seconds)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11/build; tox -c /<>/tox.ini 
--sitepackages -e py311
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
returned exit code 13

Full log attached.

Stefano
sbuild (Debian sbuild) 0.85.0 (04 January 2023) on haydn.kardiogramm.net

+==+
| python-magic (amd64) Sat, 06 May 2023 19:14:24 + |
+==+

Package: python-magic
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 'autopkgtest-virt-dummy-location' with 
'<>'
I: NOTICE: Log filtering will replace 
'build/python-magic-fDhHNg/resolver-2kn04n' with '<>'

+--+
| Update chroot|
+--+

Get:1 http://deb.debian.org/debian unstable InRelease [188 kB]
Get:2 http://deb.debian.org/debian experimental InRelease [101 kB]
Get:3 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:4 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[63.6 kB]
Get:5 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index 
[63.3 kB]
Get:6 http://deb.debian.org/debian unstable/main Sources 
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [44.0 kB]
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages 
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [67.4 kB]
Get:6 http://deb.debian.org/debian unstable/main Sources 
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [44.0 kB]
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages 
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [67.4 kB]
Get:8 http://deb.debian.org/debian unstable/contrib amd64 Packages 
T-2023-05-05-0202.38-F-2023-04-30-2005.36.pdiff [581 B]
Get:8 http://deb.debian.org/debian unstable/contrib amd64 Packages 

Bug#1042009: marked as done (onetbb: FTBFS on armel: error: ‘void __atomic_store_1(volatile void*, unsigned char, int)’ writing 1 byte into a region of size 0 overflows the destination [-Werror=string

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 00:57:25 +
with message-id 
and subject line Bug#1042009: fixed in onetbb 2021.9.0-2
has caused the Debian Bug report #1042009,
regarding onetbb: FTBFS on armel: error: ‘void __atomic_store_1(volatile void*, 
unsigned char, int)’ writing 1 byte into a region of size 0 overflows the 
destination [-Werror=stringop-overflow=]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: onetbb
Version: 2021.9.0-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=onetbb=armel=2021.9.0-1=1689653659=0

FAILED: 
test/CMakeFiles/test_concurrent_monitor.dir/tbb/test_concurrent_monitor.cpp.o 
/usr/bin/c++  -I/<>/test/.. -I/<>/test 
-I/<>/src/tbb/../../include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -Wall 
-Wextra -Werror -Wfatal-errors -Wno-error=uninitialized -Wno-error=array-bounds 
-Wno-error=use-after-free -Wno-error=address -Wshadow -Wcast-qual 
-Woverloaded-virtual -Wnon-virtual-dtor -fno-strict-overflow 
-fno-delete-null-pointer-checks -fwrapv -MD -MT 
test/CMakeFiles/test_concurrent_monitor.dir/tbb/test_concurrent_monitor.cpp.o 
-MF 
test/CMakeFiles/test_concurrent_monitor.dir/tbb/test_concurrent_monitor.cpp.o.d 
-o 
test/CMakeFiles/test_concurrent_monitor.dir/tbb/test_concurrent_monitor.cpp.o 
-c /<>/test/tbb/test_concurrent_monitor.cpp
In file included from /usr/include/c++/13/atomic:41,
 from /<>/test/common/doctest.h:2990,
 from /<>/test/common/test.h:32,
 from /<>/test/tbb/test_concurrent_monitor.cpp:26:
In member function ‘void std::__atomic_base<_IntTp>::store(__int_type, 
std::memory_order) [with _ITp = bool]’,
inlined from ‘void std::atomic::store(bool, std::memory_order)’ at 
/usr/include/c++/13/atomic:104:20,
inlined from ‘void 
tbb::detail::r1::concurrent_monitor_base::notify_one_relaxed() [with 
Context = unsigned int]’ at 
/<>/test/tbb/../../src/tbb/concurrent_monitor.h:293:53,
inlined from ‘void 
tbb::detail::r1::concurrent_monitor_base::notify_one() [with Context = 
unsigned int]’ at 
/<>/test/tbb/../../src/tbb/concurrent_monitor.h:276:27,
inlined from ‘void DOCTEST_ANON_FUNC_35()’ at 
/<>/test/tbb/test_concurrent_monitor.cpp:87:44:
/usr/include/c++/13/bits/atomic_base.h:481:25: error: ‘void 
__atomic_store_1(volatile void*, unsigned char, int)’ writing 1 byte into a 
region of size 0 overflows the destination [-Werror=stringop-overflow=]
  481 | __atomic_store_n(&_M_i, __i, int(__m));
  | ^~
compilation terminated due to -Wfatal-errors.
cc1plus: all warnings being treated as errors

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: onetbb
Source-Version: 2021.9.0-2
Done: Petter Reinholdtsen 

We believe that the bug you reported is fixed in the latest version of
onetbb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated onetbb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Aug 2023 22:42:54 +0200
Source: onetbb
Architecture: source
Version: 2021.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Petter Reinholdtsen 
Closes: 1042009
Changes:
 onetbb (2021.9.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   * Added patch classiciation and added more metadata.
   * Avoid build problem on armel caused by strange compiler
 (Closes: #1042009).
Checksums-Sha1:
 4cc109b7b678df33426322e77d9ec0e7833af638 2488 onetbb_2021.9.0-2.dsc
 001dc2041fcbf0867df564ea10133458d2a6 17160 onetbb_2021.9.0-2.debian.tar.xz
 851ced66b3b8e7d4b482c1a35252e633febd738e 9413 
onetbb_2021.9.0-2_source.buildinfo

Bug#1037993: marked as done (dahdi-dkms: module fails to build for Linux 6.3)

[Debian Bug Tracking System]

Your message dated Thu, 03 Aug 2023 00:51:06 +
with message-id 
and subject line Bug#1037993: fixed in dahdi-linux 1:3.1.0+git20230717~dfsg-2
has caused the Debian Bug report #1037993,
regarding dahdi-dkms: module fails to build for Linux 6.3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dahdi-dkms
Version: 1:2.11.1.0.20170917~dfsg-8.4
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for dahdi-2.11.1.0.20170917 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 09:40:51 UTC 2023
make -C /lib/modules/6.3.0-1-amd64/build 
KBUILD_EXTMOD=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi 
DAHDI_INCLUDE=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/include 
DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes 
modules DAHDI_BUILD_ALL=m
make[1]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsi_cnct.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsst.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/bt/octapi_bt0.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/largmath/octapi_largmath.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/llman/octapi_llman.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x-user.o
  LD [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/base.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/vpm450m.o
  LD [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/wct4xxp.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wctc4xxp/base.o
In file included from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/string.h:254,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/bitmap.h:11,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/cpumask.h:12,
 from 

Bug#999962: silversearcher-ag: depends on obsolete pcre3 library

[Nicholas D Steeves]

Dear Hajime Mizuno, or whoever might be thinking about salvaging this
package,

The best solution appears to be encouraging and supporting this friendly
fork:

  https://github.com/ggreer/the_silver_searcher/issues/1515

The next best solution appears to be switching to a fork that fixed this
pcre3 issue (and added the new PCRE2 support); however, it's also
currently unmaintained.  Please see the above link for what I believe is
the locus of future community support for The Silver Searcher.


Sincerely,
Nicholas

https://wiki.debian.org/PackageSalvaging


signature.asc
Description: PGP signature

Processed: RE: ruby-moneta: FTBFS: ERROR: Test "ruby3.1" failed: cannot load such file -- ox/ox

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042218 [src:ruby-moneta] ruby-moneta: FTBFS: ERROR: Test "ruby3.1" 
failed: cannot load such file -- ox/ox
Added tag(s) pending.

-- 
1042218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042218: ruby-moneta: FTBFS: ERROR: Test "ruby3.1" failed: cannot load such file -- ox/ox

[Leandro Cunha]

Control: tag -1 pending

Hello,

A fix for this has already been discovered and I've already asked to
upload it for fix. It was already known to me and I apologize for the
delay.

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa
hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw
gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud
lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9
WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO
jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd
CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF
fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e
Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O
+SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX
UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW
fNdY6Ns=
=rdCA
-END PGP PUBLIC KEY BLOCK-

Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures

[Petter Reinholdtsen]

[M. Zhou]
> The issue still exists with armel:
> https://buildd.debian.org/status/package.php?p=onetbb

If so, this is a duplicate of 
https://bugs.debian.org/1042009 >, which is about the armel issue,
and should be closed.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures

[M. Zhou]

The issue still exists with armel:
https://buildd.debian.org/status/package.php?p=onetbb

On Wed, 2023-08-02 at 22:46 +0200, Petter Reinholdtsen wrote:
> [M. Zhou]
> > I'm aware of this issue. I'm slightly faster than buildd for
> > toolchain
> > upgrades. The issue will automatically disappear once our amd64
> > buildd
> > migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now.
> 
> Is this still an issue?

Processed: Re: Bug#1042918: reprotest: FTBFS with tox 4

[Debian Bug Tracking System]

Processing control commands:

> tags 1042918 pending
Bug #1042918 [src:reprotest] reprotest: FTBFS with tox 4
Added tag(s) pending.

-- 
1042918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042918: reprotest: FTBFS with tox 4

[Vagrant Cascadian]

Control: tags 1042918 pending

On 2023-08-02, Stefano Rivera wrote:
> I thought we'd managed to avoid this, in #1035645, but we just did the
> transition, and I see reprotest is FTBFS:
...
> py311: commands[0] .pybuild/cpython3_3.11_reprotest/build> 
> .tox/py311/bin/python -m coverage r
> un --omit '.tox/*' --parallel -m py.test tests/
> __path__ attribute not found on 'py' while trying to find 'py.test'
> py311: exit 1 (0.09 seconds) /<>> .tox/py311/bin/python -m 
> coverage run --omit '.
> tox/*' --parallel -m py.test tests/ pid=7370
>   py311: FAIL code 1 (2.31=setup[2.22]+cmd[0.09] seconds)
>   evaluation failed :( (2.36 seconds)
> E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
> /<>/.
> pybuild/cpython3_3.11_reprotest/build; tox -c /<>/tox.ini 
> --sitepackages --instal
> lpkg 
> /<>/.pybuild/cpython3_3.11_reprotest/reprotest-0.7.25-py3-none-any.whl
>  -e py311 
> dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
> --test-tox returned exit code 13
>
>
> I'm guessing you want to replace py.test there with pytest.

Great suggestion! Worked for me locally and in salsa-ci.

Pushed to git:

  
https://salsa.debian.org/reproducible-builds/reprotest/-/commit/3d01047ae75ffc3fc30ad11aeec1a0dd9994d849

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1042857: marked as done (coinor-libcbc3.1: Fails to install, conflicts with coinor-libcbc3:amd64)

[Debian Bug Tracking System]

Your message dated Wed, 02 Aug 2023 21:04:18 +
with message-id 
and subject line Bug#1042857: fixed in coinor-cbc 2.10.10+really2.10.10+ds1-3
has caused the Debian Bug report #1042857,
regarding coinor-libcbc3.1: Fails to install, conflicts with 
coinor-libcbc3:amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coinor-libcbc3.1
Version: 2.10.10+really2.10.10+ds1-2
Severity: serious
Justification: Fails to install

Hello,

While upgrading testing today:

Preparing to unpack .../coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb 
...
Unpacking coinor-libcbc3.1:amd64 (2.10.10+really2.10.10+ds1-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libCbc.so.3.10.10', which is 
also in package coinor-libcbc3:amd64 2.10.10+ds1-1
Errors were encountered while processing:
 /var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb
needrestart is being skipped since dpkg has failed

I guess there should be some breaks+replace or some renaming?

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages coinor-libcbc3.1 depends on:
ii  coinor-libcgl1  0.60.3+repack1-4
ii  coinor-libclp1  1.17.6-3
ii  coinor-libcoinutils3v5  2.11.4+repack1-2
ii  coinor-libosi1v50.108.6+repack1-2
ii  libc6   2.37-6
ii  libgcc-s1   13.1.0-6
ii  libstdc++6  13.1.0-6

coinor-libcbc3.1 recommends no packages.

coinor-libcbc3.1 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: coinor-cbc
Source-Version: 2.10.10+really2.10.10+ds1-3
Done: Pierre Gruet 

We believe that the bug you reported is fixed in the latest version of
coinor-cbc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated coinor-cbc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Aug 2023 21:52:00 +0200
Source: coinor-cbc
Architecture: source
Version: 2.10.10+really2.10.10+ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Pierre Gruet 
Closes: 1042857
Changes:
 coinor-cbc (2.10.10+really2.10.10+ds1-3) unstable; urgency=medium
 .
   * Adding Breaks+Replaces for the new shared lib package against the old one
 (Closes: #1042857)
Checksums-Sha1:
 0e2599677a3ad81bacceaab56a2c1a691ec5b49d 2471 
coinor-cbc_2.10.10+really2.10.10+ds1-3.dsc
 dd82520743819c696297af0c34e94733ad49cbde 16112 
coinor-cbc_2.10.10+really2.10.10+ds1-3.debian.tar.xz
 6d3436cbce64e4e9be1f486e7e05fefe9d8d820c 10454 
coinor-cbc_2.10.10+really2.10.10+ds1-3_amd64.buildinfo
Checksums-Sha256:
 2aca2347a846d575e2ca15296c653bd6bb7d3e98d8c6595e2d15c6d80118208e 2471 
coinor-cbc_2.10.10+really2.10.10+ds1-3.dsc
 9c9a63194b31626cb1813144fbe4ea630888f8b78d9b8bde26b27bb1ae3db6e8 16112 
coinor-cbc_2.10.10+really2.10.10+ds1-3.debian.tar.xz
 943e0ff6178ec7fbec08a8d12a330665ce7fd86e51bb0a5d5622403c3369a707 10454 
coinor-cbc_2.10.10+really2.10.10+ds1-3_amd64.buildinfo
Files:
 

Bug#1042885: / Bug# 1042886 Acknowledgement (initramfs-tools: breaks system boot after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1)

[CHRISTIAN PETER KISS]

‎Bug#1042885 / Bug# 1042886 

Hello,

as of Bullseye -rt-23 kernel part : 

it seems 
CONFIG_AS_VERSION=23502 
was absent in the kernel config.


this and or 5.10 dev 

fixed the rt-23 bullseye kernel boot

but not the bookworm issue with initrams.


#keypoint verify if this trigger can be the cause of dysfunct mkinitramfs 
initramfs-tools .
i suspect dysfunct zstd 1.54 andor 0.142 initramfstools are  the issue  


n o t  1.48 +0.140 bullseye 


greetings








  Original Message  
From: CHRISTIAN PETER KISS 
Sent: Wednesday, 2 August 2023 14:49
To: car...@deian.org
Subject: Salvatore this Bug#1042885 isforyou : Acknowledgement 
(initramfs-tools: breaks system boot after bios: initramfs-tools-core, 
initramfs-tools, zstd, libzstd1)


  Original Message  
From: Debian Bug Tracking System 
Sent: Wednesday, 2 August 2023 13:54
To: Christian Kiss
Subject: Bug#1042885: Acknowledgement (initramfs-tools: breaks system boot 
after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1)

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1042885: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042885.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
christianpeterk...@yahoo.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
Debian kernel team 

If you wish to submit further information on this problem, please
send it to 1042...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

-- 
1042885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures

[Petter Reinholdtsen]

[M. Zhou]
> I'm aware of this issue. I'm slightly faster than buildd for toolchain
> upgrades. The issue will automatically disappear once our amd64 buildd
> migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now.

Is this still an issue?
-- 
Happy hacking
Petter Reinholdtsen

Processed: block 1042916 with 1042921

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 1042916 with 1042921
Bug #1042916 [helvum] Unsatisfiable build-dependency on gtk4 0.16
1042916 was not blocked by any bugs.
1042916 was not blocking any bugs.
Added blocking bug(s) of 1042916: 1042921
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042253: marked as done (libxlsxwriter: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Wed, 02 Aug 2023 20:36:15 +
with message-id 
and subject line Bug#1042253: fixed in libxlsxwriter 1.1.5-1~exp2
has caused the Debian Bug report #1042253,
regarding libxlsxwriter: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_configure] Error 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxlsxwriter
Version: 1.1.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
> -DBUILD_SHARED_LIBS=ON \
> -DUSE_SYSTEM_MINIZIP=ON \
> -DUSE_OPENSSL_MD5=ON \
> -DBUILD_TESTS=ON \
> -DBUILD_EXAMPLES=ON \
> 
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DBUILD_SHARED_LIBS=ON -DUSE_SYSTEM_MINIZIP=ON -DUSE_OPENSSL_MD5=ON 
> -DBUILD_TESTS=ON -DBUILD_EXAMPLES=ON ..
> CMake Deprecation Warning at CMakeLists.txt:106 (cmake_minimum_required):
>   Compatibility with CMake < 3.5 will be removed from a future version of
>   CMake.
> 
>   Update the VERSION argument  value or use a ... suffix to tell
>   CMake that the project does not need compatibility with older versions.
> 
> 
> -- The C compiler identification is GNU 13.1.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- The CXX compiler identification is GNU 13.1.0
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> CMake Warning (dev) at /usr/share/cmake-3.27/Modules/FindZLIB.cmake:88 
> (message):
>   ZLIB does not provide any COMPONENTS.  Calling
> 
> find_package(ZLIB COMPONENTS ...)
> 
>   will always fail.
> Call Stack (most recent call first):
>   CMakeLists.txt:219 (find_package)
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> CMake Error at 
> /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 
> (message):
>   Could NOT find ZLIB (missing: 1.0) (found version "1.2.13")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:600 
> (_FPHSA_FAILURE_MESSAGE)
>   /usr/share/cmake-3.27/Modules/FindZLIB.cmake:200 
> (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
>   CMakeLists.txt:219 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Build libxlsxwriter examples
> BUILD_EXAMPLES:BOOL=ON
> 
> //No help, variable specified on the command line.
> BUILD_SHARED_LIBS:UNINITIALIZED=ON
> 
> //Build libxlsxwriter tests
> BUILD_TESTS:BOOL=ON
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> 

Bug#1042253: marked as done (libxlsxwriter: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Wed, 02 Aug 2023 20:35:58 +
with message-id 
and subject line Bug#1042253: fixed in libxlsxwriter 1.1.4-3
has caused the Debian Bug report #1042253,
regarding libxlsxwriter: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_configure] Error 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxlsxwriter
Version: 1.1.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
> -DBUILD_SHARED_LIBS=ON \
> -DUSE_SYSTEM_MINIZIP=ON \
> -DUSE_OPENSSL_MD5=ON \
> -DBUILD_TESTS=ON \
> -DBUILD_EXAMPLES=ON \
> 
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DBUILD_SHARED_LIBS=ON -DUSE_SYSTEM_MINIZIP=ON -DUSE_OPENSSL_MD5=ON 
> -DBUILD_TESTS=ON -DBUILD_EXAMPLES=ON ..
> CMake Deprecation Warning at CMakeLists.txt:106 (cmake_minimum_required):
>   Compatibility with CMake < 3.5 will be removed from a future version of
>   CMake.
> 
>   Update the VERSION argument  value or use a ... suffix to tell
>   CMake that the project does not need compatibility with older versions.
> 
> 
> -- The C compiler identification is GNU 13.1.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- The CXX compiler identification is GNU 13.1.0
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> CMake Warning (dev) at /usr/share/cmake-3.27/Modules/FindZLIB.cmake:88 
> (message):
>   ZLIB does not provide any COMPONENTS.  Calling
> 
> find_package(ZLIB COMPONENTS ...)
> 
>   will always fail.
> Call Stack (most recent call first):
>   CMakeLists.txt:219 (find_package)
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> CMake Error at 
> /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 
> (message):
>   Could NOT find ZLIB (missing: 1.0) (found version "1.2.13")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:600 
> (_FPHSA_FAILURE_MESSAGE)
>   /usr/share/cmake-3.27/Modules/FindZLIB.cmake:200 
> (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
>   CMakeLists.txt:219 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Build libxlsxwriter examples
> BUILD_EXAMPLES:BOOL=ON
> 
> //No help, variable specified on the command line.
> BUILD_SHARED_LIBS:UNINITIALIZED=ON
> 
> //Build libxlsxwriter tests
> BUILD_TESTS:BOOL=ON
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> 

Bug#1042921: rust-glib: feature "log" has disappeared

[Jonas Smedegaard]

Source: rust-glib
Version: 0.17.10-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

rust-glib was upgraded without coordination with reverse dependencies.
Don't do that.  It puts a stress on maintenance of reverse dependencies!

The upgrade patched away feature "log". Don't do that.  Yeah, I can see
that it requires a new package - then package that, don't break reverse
dependencies in Debian!

 - Jonas
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTKvpAACgkQLHwxRsGg
ASF5whAAho9hTN1h+vVnX0r9dcYsWAdMSKGGEJU8Gm95dd5OvgAayquIs9KkM+SH
TVpFTNy83VtyJ+pxBNjdmk76bOUJdrgECjD2A1ytgsHKUreoZjXeuB4ukswVqRFn
Ay4WKLjSY5rEh4acrUX2kVbDo3hUn2qz8NrImw0H7zzgOJik4Hpp9nlAX/XPvNDE
9wci98XsmEh/eaHr17HSqF/BZDyXxTgHT6s3vP1WPLKBpBgGjIsSHXLVfiRi1Woj
mng+scm2KlKFtSI5KZ/q1Bj8604yLXFpRvN1hzlnroY9/HTeGJdXJtyETOKV+ESU
/fVMFIK25DyqHA8jfipvyrA7DiSJxc7FTWajPi2bdj+RxTajRM4pSahONrNtI3xx
K88fnDHJEVCgwp4zlRnn7JJsK7dFW1+SEQBW0tH+tXHUquVM+mSu4VIgQTdjGv8j
gNV5dh8j/NtIP2xRrUOYK40OJ+RdgPW5sf2ZtqslN5DH2ZtZTIpcUAVO4ehOF3Ky
AV2VMmKINPpyhyCh30/PB6VD2ImWMz44hrvS20g6yTrq2I/bdIteiqbVR7LjvbFZ
ugFLXiEHl0pWkm33vSEZXnjnZR2g1X/PZVFv9mcoUFE7CeNQEMv4IxsMs5wU8YdE
IGfjrmvKLTI3s3pDsIsNNBvbLvUSXxI6nNcYpfMln8KNu7RZqRM=
=C2MK
-END PGP SIGNATURE-

Processed: bug 1037667 is forwarded to https://github.com/freeorion/freeorion/pull/4364

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1037667 https://github.com/freeorion/freeorion/pull/4364
Bug #1037667 [src:freeorion] freeorion: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/freeorion/freeorion/pull/4364'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042919: r-cran-leidenbase: autopkgtest failure with r-cran-igraph 1.5.0.1-1

[Adrian Bunk]

Source: r-cran-leidenbase
Version: 0.1.18-1
Severity: serious
Control: block 1038700 by -1

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-leidenbase/36306523/log.gz

...
 46s ══ Failed tests 

 46s ── Error ('test-leidenbase.R:43:3'): CPMVertexPartition membership and 
quality ──
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"CPMVertexPartition", 
 46s seed = 123456, resolution_parameter = 0.5)`: REAL() can only be 
applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:43:2
 46s ── Error ('test-leidenbase.R:61:3'): ModularityVertexPartition membership 
and quality ──
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"ModularityVertexPartition", 
 46s seed = 123456, resolution_parameter = 0.5)`: REAL() can only be 
applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:61:2
 46s ── Error ('test-leidenbase.R:79:3'): RBERVertexPartition membership and 
quality ──
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"RBERVertexPartition", 
 46s seed = 123456, resolution_parameter = 0.5)`: REAL() can only be 
applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:79:2
 46s ── Error ('test-leidenbase.R:97:3'): SignificanceVertexPartition 
membership and quality ──
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"SignificanceVertexPartition", 
 46s seed = 123456, resolution_parameter = 0.5)`: REAL() can only be 
applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:97:2
 46s ── Error ('test-leidenbase.R:115:3'): SurpriseVertexPartition membership 
and quality ──
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"SurpriseVertexPartition", 
 46s seed = 123456, resolution_parameter = 0.5)`: REAL() can only be 
applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:115:2
 46s ── Error ('test-leidenbase.R:137:3'): resolution_parameter parameter 
───
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"RBConfigurationVertexPartition", 
 46s resolution_parameter = 1, seed = 123456)`: REAL() can only be applied 
to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:137:2
 46s ── Error ('test-leidenbase.R:155:3'): num_iter parameter 
───
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"RBConfigurationVertexPartition", 
 46s num_iter = 5, seed = 123456, resolution_parameter = 0.5)`: REAL() can 
only be applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:155:2
 46s ── Error ('test-leidenbase.R:178:3'): initial_membership parameter 
─
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"RBConfigurationVertexPartition", 
 46s initial_membership = inimem, seed = 123456, resolution_parameter = 
0.5)`: REAL() can only be applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:178:2
 46s ── Error ('test-leidenbase.R:201:3'): edge_weights parameter 
───
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"RBConfigurationVertexPartition", 
 46s edge_weights = edgwgt, seed = 123456, resolution_parameter = 0.5)`: 
REAL() can only be applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:201:2
 46s ── Error ('test-leidenbase.R:224:3'): node_sizes parameter 
─
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"RBConfigurationVertexPartition", 
 46s node_sizes = nodsiz, seed = 123456, resolution_parameter = 0.5)`: 
REAL() can only be applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:224:2
 46s ── Error ('test-leidenbase.R:245:3'): modularity and significance return 
values ──
 46s Error in `leidenbase::leiden_find_partition(igraph, partition_type = 
"CPMVertexPartition", 
 46s seed = 123456, resolution_parameter = 0.1)`: REAL() can only be 
applied to a 'numeric', not a 'NULL'
 46s Backtrace:
 46s ▆
 46s  1. └─leidenbase::leiden_find_partition(...) at test-leidenbase.R:245:2
 46s 
 46s [ FAIL 11 | WARN 0 | SKIP 0 | PASS 6 ]
 46s Error: Test failures
 46s Execution halted
 46s autopkgtest [18:09:34]: test 

Processed: r-cran-leidenbase: autopkgtest failure with r-cran-igraph 1.5.0.1-1

[Debian Bug Tracking System]

Processing control commands:

> block 1038700 by -1
Bug #1038700 {Done: Paul Gevers } [src:r-cran-igraph] 
src:r-cran-igraph: fails to migrate to testing for too long: autopkgtest 
regression on i386
1038700 was not blocked by any bugs.
1038700 was not blocking any bugs.
Added blocking bug(s) of 1038700: 1042919

-- 
1038700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038700
1042919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Nicholas D Steeves]

Hello,

Would you like to fix this RC bug and adopt the package?

  https://bugs.debian.org/1042911

and the orphan bug is here: #1016558

Best,
Nicholas


signature.asc
Description: PGP signature

Bug#1041378: (no subject)

[Nicola Ferralis]

The most relevant change is in the file:

libavutil/hwcontext_qsv.h

where in ffmpeg 5.1.3 it used to read (line 22):

#include 

while in ffmpeg 6.0:

#include 

That said, simply adding the folder mfx/ in ffmpeg 6.0 leads to a 
compilation error for ffmpeg:


In file included from src/libavfilter/qsvvpp.h:32,
 from src/libavfilter/qsvvpp.c:30:
src/libavutil/hwcontext_qsv.h:22:10: fatal error: mfx/mfxvideo.h: No such file 
or directory
   22 | #include 
  |  ^~~~
compilation terminated.

Bug#1042857: coinor-libcbc3.1: Fails to install, conflicts with coinor-libcbc3:amd64

[Pierre Gruet]

Control: tags -1 pending confirmed

Hello,


On Tue, 1 Aug 2023 23:21:52 +0200 Samuel Thibault  
wrote:

> Package: coinor-libcbc3.1
> Version: 2.10.10+really2.10.10+ds1-2
> Severity: serious
> Justification: Fails to install
>
> Hello,
>
> While upgrading testing today:
>
> Preparing to unpack 
.../coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb ...

> Unpacking coinor-libcbc3.1:amd64 (2.10.10+really2.10.10+ds1-2) ...
> dpkg: error processing archive 
/var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb 
(--unpack):
> trying to overwrite '/usr/lib/x86_64-linux-gnu/libCbc.so.3.10.10', 
which is also in package coinor-libcbc3:amd64 2.10.10+ds1-1

> Errors were encountered while processing:
> 
/var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb

> needrestart is being skipped since dpkg has failed
>
> I guess there should be some breaks+replace or some renaming?


Thanks for the report, you're totally right.Fix coming.

>
> Samuel

Cheers,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: coinor-libcbc3.1: Fails to install, conflicts with coinor-libcbc3:amd64

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending confirmed
Bug #1042857 [coinor-libcbc3.1] coinor-libcbc3.1: Fails to install, conflicts 
with coinor-libcbc3:amd64
Added tag(s) confirmed and pending.

-- 
1042857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042857: coinor-libcbc3.1: Fails to install, conflicts with coinor-libcbc3:amd64

[Pierre Gruet]

On Tue, 1 Aug 2023 23:21:52 +0200 Samuel Thibault  
wrote:

> Package: coinor-libcbc3.1
> Version: 2.10.10+really2.10.10+ds1-2
> Severity: serious
> Justification: Fails to install
>
> Hello,
>
> While upgrading testing today:
>
> Preparing to unpack 
.../coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb ...

> Unpacking coinor-libcbc3.1:amd64 (2.10.10+really2.10.10+ds1-2) ...
> dpkg: error processing archive 
/var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb 
(--unpack):
> trying to overwrite '/usr/lib/x86_64-linux-gnu/libCbc.so.3.10.10', 
which is also in package coinor-libcbc3:amd64 2.10.10+ds1-1

> Errors were encountered while processing:
> 
/var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb

> needrestart is being skipped since dpkg has failed
>
> I guess there should be some breaks+replace or some renaming?
>
> Samuel
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers testing
> APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable-proposed-updates'), 
(500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), 
(500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')

> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, arm64
>
> Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE not set

> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages coinor-libcbc3.1 depends on:
> ii coinor-libcgl1 0.60.3+repack1-4
> ii coinor-libclp1 1.17.6-3
> ii coinor-libcoinutils3v5 2.11.4+repack1-2
> ii coinor-libosi1v5 0.108.6+repack1-2
> ii libc6 2.37-6
> ii libgcc-s1 13.1.0-6
> ii libstdc++6 13.1.0-6
>
> coinor-libcbc3.1 recommends no packages.
>
> coinor-libcbc3.1 suggests no packages.
>
>

Bug#1042918: reprotest: FTBFS with tox 4

[Stefano Rivera]

Source: reprotest
Version: 0.7.25
Severity: serious
Justification: ftbfs

I thought we'd managed to avoid this, in #1035645, but we just did the
transition, and I see reprotest is FTBFS:

I: pybuild base:275: cd 
/<>/.pybuild/cpython3_3.11_reprotest/build; tox -c /<>/tox.ini --sitepackages --installpkg 
/<>/.pybuild/cpython3_3.11_reprote
st/reprotest-0.7.25-py3-none-any.whl -e py311 
py311: install_deps .pybuild/cpython3_3.11_reprotest/build> python -I -m pip 
install coverage 
diffoscope pytest
py311: install_package_deps .pybuild/cpython3_3.11_reprotest/build> python -I 
-m pip install d
istro rstr
py311: install_package .pybuild/cpython3_3.11_reprotest/build> python -I -m pip 
install --forc
e-reinstall --no-deps 
/<>/.pybuild/cpython3_3.11_reprotest/reprotest-0.7.25-py3-n
one-any.whl
py311: commands[0] .pybuild/cpython3_3.11_reprotest/build> 
.tox/py311/bin/python -m coverage r
un --omit '.tox/*' --parallel -m py.test tests/
__path__ attribute not found on 'py' while trying to find 'py.test'
py311: exit 1 (0.09 seconds) /<>> .tox/py311/bin/python -m 
coverage run --omit '.
tox/*' --parallel -m py.test tests/ pid=7370
  py311: FAIL code 1 (2.31=setup[2.22]+cmd[0.09] seconds)
  evaluation failed :( (2.36 seconds)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.
pybuild/cpython3_3.11_reprotest/build; tox -c /<>/tox.ini 
--sitepackages --instal
lpkg 
/<>/.pybuild/cpython3_3.11_reprotest/reprotest-0.7.25-py3-none-any.whl
 -e py311 
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
--test-tox returned exit code 13


I'm guessing you want to replace py.test there with pytest.

Stefano

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1042917: rdflib-sqlalchemy: FTBFS with tox 4

[Stefano Rivera]

Source: rdflib-sqlalchemy
Version: 0.5.4-1
Severity: serious
Tags: upstream
Justification: ftbfs

With tox 4, rdflib-sqlalchemy FTBFS with:
   dh_auto_test -O--buildsystem=pybuild
E: pybuild pybuild:388: test: plugin distutils failed with: wheel is required 
to build wheels for distutils/setuptools packages. Build-Depend on 
python3-wheel.
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
returned exit code 13

I committed the fix for that to git, but the next issue is:

I: pybuild base:275: cd 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/build; tox -c 
/<>/tox.ini --sitepackages --installpkg 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/rdflib_sqlalchemy-0.5.4-py3-none-any.whl
 -e py311 
py311: install_deps .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> python -I 
-m pip install mysqlclient psycopg2 'pytest-cov>=2.5.1' 'pytest>=3.4.0'
py311: install_package_deps .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> 
python -I -m pip install 'SQLAlchemy<2.0.0,>=1.1.4' 'alembic>=0.8.8' 
'rdflib>=4.0' 'six>=1.10.0'
py311: install_package .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> python 
-I -m pip install --force-reinstall --no-deps 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/rdflib_sqlalchemy-0.5.4-py3-none-any.whl
py311: commands[0] .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> 
.tox/py311/bin/python setup.py clean --all
running clean
removing '/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/build' (and 
everything under it)
removing 'build/bdist.linux-x86_64' (and everything under it)
'build/scripts-3.11' does not exist -- can't clean it
removing 'build'
py311: commands[1] .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> pytest 
--cov=rdflib_sqlalchemy
py311: failed with pytest is not allowed, use allowlist_externals to allow it
  py311: FAIL code 1 (3.06 seconds)
  evaluation failed :( (3.12 seconds)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/build; tox -c 
/<>/tox.ini --sitepackages --installpkg 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/rdflib_sqlalchemy-0.5.4-py3-none-any.whl
 -e py311 
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
returned exit code 13

The fix here should be as simple as replacing "pytest" with "{envpython} -m 
pytest" in tox.ini

Stefano

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1042916: Unsatisfiable build-dependency on gtk4 0.16

[Matthias Geiger]

Package: helvum
Severity: grave
Justification: renders package installable
X-Debbugs-Cc: werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Jonas.

Yesterday I uploaded the new gtk-rs release which makes helvum uninstallable
as it depends on the no longer present 0.16 versions of the gtk-rs
libraries. The fix is simple, just dropping 2001_gtk.patch should
suffice. Please look into this as it blocks testing migration for gtk-rs
otherwise. 

Thanks,

Matthias

- -- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.2-surface (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages helvum depends on:
ii  libc62.36-9
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.76.3-1
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-4-1   4.10.3+ds-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpipewire-0.3-00.3.65-3

helvum recommends no packages.

helvum suggests no packages.

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmTKqk0VHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1yMsP9jRViLwDlXoyVxq5wSvWpVB1honZ
TqyTaPVWhjYsEZsWftKjeGWEv1Mf5cHy5A6d9rhXlIj7QIcGRKv9ss3SevQLplL8
7LwPBdQ/TIsPvNBhaHt8tOnTJlqWXT2uyVwHidjcE+UcIYN/QGW51UY2dpPPq4WS
0Qp3UTL8EvyYF0omjQ8/Gdaj7ufNKdcLsCPOMijRkGq2zcU9mIbY4a3lD/xiY4X4
NMD1GtqbFcZF1ND/FrzTQqD0Q8je0NBJzo9TJR2M1mF6ozkZjuM2ZgoVZEGwUWhl
o9kp5+69JxwAhOubPMi29TDpILHiKJfWKDph2S7I1APcjyvLBlCifDhpXVuEu6QA
rH10KWChI6j1nQ6PlcXjfD1fAnfqPLckACm2lkyLejDT3LzTjjQM1dmETepRN7h+
5Ibjxwj5+yIf0gsckru5Lj4VkMi9HRCh86TEvcG1BaS9oz0oir0CcNdw8Ytrnqrn
6+n8p257OBVCfwvLh4dQm0cJ7GyjIF6ojrM7ju0a54jASpA052PCxMM29wgC6riW
jj6weVhryZhdRlk9CJVE0GGMWhy7NjggUL7dQvoF18hevms5om0HHdMIU2uy49zg
dthnaYMLOESW9UlHV564KM/Tz1A7t0vDBdDEvHRjDBVsalu7j09CW/P1urYz3lO9
BU6yB9Q8g+5cMek=
=1f89
-END PGP SIGNATURE-

Bug#1041229: marked as done (libltdl-dev: cannot install more than one architecture due to M-A: same w/ Breaks/Provides/Replaces: libltdl3-dev)

[Debian Bug Tracking System]

Your message dated Wed, 02 Aug 2023 19:04:18 +
with message-id 
and subject line Bug#1041229: fixed in libtool 2.4.7-7
has caused the Debian Bug report #1041229,
regarding libltdl-dev: cannot install more than one architecture due to M-A: 
same w/ Breaks/Provides/Replaces: libltdl3-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libltdl-dev
Version: 2.4.7-6
Severity: grave
Justification: renders package unusable

When upgrading, I got:

E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of libltdl-dev:amd64:
 libltdl-dev:i386 (2.4.7-6) breaks libltdl3-dev and is unpacked but not 
configured.
  libltdl-dev:amd64 (2.4.7-6) provides libltdl3-dev.

dpkg: error processing package libltdl-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libltdl-dev:i386:
 libltdl-dev:amd64 (2.4.7-6) breaks libltdl3-dev and is unpacked but not 
configured.
  libltdl-dev:i386 (2.4.7-6) provides libltdl3-dev.

dpkg: error processing package libltdl-dev:i386 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libltdl-dev:amd64
 libltdl-dev:i386

In the /var/log/dpkg.log file, about libltdl*:

2023-07-16 00:13:59 upgrade libltdl-dev:i386 2.4.7-5 2.4.7-6
2023-07-16 00:13:59 status half-configured libltdl-dev:i386 2.4.7-5
2023-07-16 00:13:59 status unpacked libltdl-dev:i386 2.4.7-5
2023-07-16 00:13:59 status half-configured libltdl-dev:amd64 2.4.7-5
2023-07-16 00:13:59 status half-installed libltdl-dev:i386 2.4.7-5
2023-07-16 00:13:59 status unpacked libltdl-dev:i386 2.4.7-6
2023-07-16 00:13:59 upgrade libltdl-dev:amd64 2.4.7-5 2.4.7-6
2023-07-16 00:13:59 status unpacked libltdl-dev:amd64 2.4.7-5
2023-07-16 00:13:59 status half-installed libltdl-dev:amd64 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl-dev:amd64 2.4.7-6
2023-07-16 00:14:00 upgrade libltdl7:amd64 2.4.7-5 2.4.7-6
2023-07-16 00:14:00 status half-configured libltdl7:amd64 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl7:amd64 2.4.7-5
2023-07-16 00:14:00 status half-configured libltdl7:i386 2.4.7-5
2023-07-16 00:14:00 status half-installed libltdl7:amd64 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl7:amd64 2.4.7-6
2023-07-16 00:14:00 upgrade libltdl7:i386 2.4.7-5 2.4.7-6
2023-07-16 00:14:00 status unpacked libltdl7:i386 2.4.7-5
2023-07-16 00:14:00 status half-installed libltdl7:i386 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl7:i386 2.4.7-6
[...]
2023-07-16 00:14:23 configure libltdl7:amd64 2.4.7-6 
2023-07-16 00:14:23 status unpacked libltdl7:amd64 2.4.7-6
2023-07-16 00:14:23 status half-configured libltdl7:amd64 2.4.7-6
2023-07-16 00:14:23 status installed libltdl7:amd64 2.4.7-6
2023-07-16 00:14:23 configure libltdl7:i386 2.4.7-6 
2023-07-16 00:14:23 status unpacked libltdl7:i386 2.4.7-6
2023-07-16 00:14:23 status half-configured libltdl7:i386 2.4.7-6
2023-07-16 00:14:23 status installed libltdl7:i386 2.4.7-6

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libltdl-dev:amd64 depends on:
ii  automake [automake-1.16]  1:1.16.5-1.3
ii  libltdl7  2.4.7-6

Versions of packages libltdl-dev:amd64 recommends:
ii  libtool  2.4.7-6

Versions of packages libltdl-dev:amd64 suggests:
ii  libtool-doc  2.4.7-6

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: libtool
Source-Version: 2.4.7-7
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
libtool, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous 

Bug#1042889: vm: autopkgtest fails against Emacs 29.1

[Sean Whitton]

Hello,

On Wed 02 Aug 2023 at 02:49pm +01, Ian Jackson wrote:

> Sean Whitton writes ("Bug#1042889: vm: autopkgtest fails against Emacs 29.1"):
>> vm's autopkgtest fails with Emacs 29.1, which latter is now in sid.
>
> Hi, Sean, as you see we're looking into this.
> I have some questions for you as an Emacs expert:
>
> Is byte-compilation known to be sometimes broken?  Is there a
> recommended approach to problems caused by byte-compilation ?

The bytecompiler tends to get fussier with each Emacs release.
Usually it's worth fixing the problems with the code it identifies.
It's unlikely to be actually broken in a stable release of Emacs.

> We recently did an update to vm in Debian stable, to work around a
> critical problem with Emacs 28 (#1039105).  The autopkgtest which is
> now failing is new - I introduced it to detect future bugs, which it
> seems to have done.
>
> The previous bug was related to byte-compilation and we "fixed" it by
> turning off byte-compilation for at least some of vm's files (in what
> I feel was rather an ad-hoc way, albeit an effective one).
>
> Or to put it another way, is it possible that this is a bug in emacs
> 29.1 and if so what is the best workaround ?

Before disabling anything, it seems worth looking at the code and seeing
if you can figure out why there's a void-variable error being emitted at
all.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: severity of 1038468 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1038468 serious
Bug #1038468 [src:python-escript] python-escript: Stop using netcdf-cxx-legacy
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1038468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037567: abseil: ftbfs with GCC-13

[Benjamin Barenblat]

I’ve been procrastinating on starting the transition because of some
lingering MIPS issues. I think they’ve all been sorted out, and I just
uploaded my latest work to experimental. If that passes the buildds,
I’ll request a transition slot and do the transition as quickly as
possible.

If waiting on the transition is going to unacceptably delay the riscv64
bootstrap, please let me know. I think I know which patches I would have
to backport to 20220623 to get it to build with GCC 13, so I may be able
to fix this in unstable before the transition completes.

Processed: severity of 1035694 is serious, tagging 1035694

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1035694 serious
Bug #1035694 [src:python-bottle] python-bottle: tox 4 support: Build-Depend on 
python3-wheel
Severity set to 'serious' from 'normal'
> tags 1035694 + ftbfs
Bug #1035694 [src:python-bottle] python-bottle: tox 4 support: Build-Depend on 
python3-wheel
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1035694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1042907 to src:haskell-mode, forcibly merging 1042890 1042907

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1042907 src:haskell-mode
Bug #1042907 [elpa-haskell-mode] Breaks Emacs 29.1 upgrade: haskell.el:30:2: 
Error: Eager macro-expansion failure: (error "Misplaced t or ‘otherwise’ 
clause")
Bug reassigned from package 'elpa-haskell-mode' to 'src:haskell-mode'.
No longer marked as found in versions haskell-mode/17.2-5.
Ignoring request to alter fixed versions of bug #1042907 to the same values 
previously set
> forcemerge 1042890 1042907
Bug #1042890 [src:haskell-mode] haskell-mode: bytecompilation fails against 
Emacs 29.1
Bug #1042907 [src:haskell-mode] Breaks Emacs 29.1 upgrade: haskell.el:30:2: 
Error: Eager macro-expansion failure: (error "Misplaced t or ‘otherwise’ 
clause")
Removed indication that 1042907 affects emacs, emacs-pgtk, emacs-nox, 
emacs-lucid, and emacs-gtk
Marked as found in versions haskell-mode/17.2-5.
Merged 1042890 1042907
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042890
1042907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037814: marked as done (paraview: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 02 Aug 2023 17:23:22 +
with message-id 
and subject line Bug#1037814: fixed in paraview 5.11.0+dfsg-2
has caused the Debian Bug report #1037814,
regarding paraview: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:paraview
Version: 5.11.0+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/paraview_5.11.0+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
[  8%] Building CXX object 
VTK/Common/Core/CMakeFiles/CommonCore.dir/vtkUnsignedIntArray.cxx.o
cd /<>/build.python3.11/VTK/Common/Core && /usr/bin/c++ 
-DCommonCore_EXPORTS -DVTK_MODULE_ENABLE_VTK_loguru=1 
-I/<>/build.python3.11/VTK/Common/Core 
-I/<>/VTK/Common/Core 
-I/<>/build.python3.11/VTK/Common/Core/../DataModel 
-I/<>/build.python3.11/VTK/ThirdParty/loguru/vtkloguru 
-I/<>/VTK/ThirdParty/loguru/vtkloguru -isystem 
/<>/build.python3.11/VTK/Utilities/KWIML -isystem 
/<>/VTK/Utilities/KWIML -isystem 
/<>/build.python3.11/VTK/Utilities/KWSys -isystem 
/<>/VTK/Utilities/KWSys -isystem 
/<>/build.python3.11/VTK/ThirdParty/utf8 -isystem 
/<>/VTK/ThirdParty/utf8 -isystem /usr/include/utf8cpp -isystem 
/<>/build.python3.11/VTK/ThirdParty/loguru -isystem 
/<>/VTK/ThirdParty/loguru -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
 -O0  -g -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=c++11 -MD 
-MT VTK/Common/Core/CMakeFiles/CommonCore.dir/vtkUnsignedIntArray.cxx.o -MF 
CMakeFiles/CommonCore.dir/vtkUnsignedIntArray.cxx.o.d -o 
CMakeFiles/CommonCore.dir/vtkUnsignedIntArray.cxx.o -c 
/<>/VTK/Common/Core/vtkUnsignedIntArray.cxx
[  8%] Building CXX object 
VTK/Common/Core/CMakeFiles/CommonCore.dir/vtkUnsignedLongArray.cxx.o
cd /<>/build.python3.11/VTK/Common/Core && /usr/bin/c++ 
-DCommonCore_EXPORTS -DVTK_MODULE_ENABLE_VTK_loguru=1 
-I/<>/build.python3.11/VTK/Common/Core 
-I/<>/VTK/Common/Core 
-I/<>/build.python3.11/VTK/Common/Core/../DataModel 
-I/<>/build.python3.11/VTK/ThirdParty/loguru/vtkloguru 
-I/<>/VTK/ThirdParty/loguru/vtkloguru -isystem 
/<>/build.python3.11/VTK/Utilities/KWIML -isystem 
/<>/VTK/Utilities/KWIML -isystem 
/<>/build.python3.11/VTK/Utilities/KWSys -isystem 
/<>/VTK/Utilities/KWSys -isystem 
/<>/build.python3.11/VTK/ThirdParty/utf8 -isystem 
/<>/VTK/ThirdParty/utf8 -isystem /usr/include/utf8cpp -isystem 
/<>/build.python3.11/VTK/ThirdParty/loguru -isystem 
/<>/VTK/ThirdParty/loguru -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
 -O0  -g -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=c++11 -MD 
-MT VTK/Common/Core/CMakeFiles/CommonCore.dir/vtkUnsignedLongArray.cxx.o -MF 
CMakeFiles/CommonCore.dir/vtkUnsignedLongArray.cxx.o.d -o 
CMakeFiles/CommonCore.dir/vtkUnsignedLongArray.cxx.o -c 
/<>/VTK/Common/Core/vtkUnsignedLongArray.cxx
[  8%] Building CXX object 
VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/CMakeFiles/vtkm_cont.dir/internal/Buffer.cxx.o
cd 
/<>/build.python3.11/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont 
&& /usr/bin/c++ -DVTKMDIY_MPI_AS_LIB -DVTKMDIY_NO_THREADS -Dvtkm_cont_EXPORTS 
-I/<>/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m 
-I/<>/build.python3.11/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/include 

Bug#1038602: marked as done (paraview: Stop using netcdf-cxx-legacy)

[Debian Bug Tracking System]

Your message dated Wed, 02 Aug 2023 17:23:22 +
with message-id 
and subject line Bug#1038602: fixed in paraview 5.11.0+dfsg-2
has caused the Debian Bug report #1038602,
regarding paraview: Stop using netcdf-cxx-legacy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1038602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paraview
Version: 5.11.0+dfsg-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: netcdf-cxx-legacy-rm

Dear Maintainer,

Your package uses netcdf-cxx-legacy which is dead upstream and will be removed 
during the trixie development cycle.

The attached patch only drops the build dependency, as your package doesn't 
actually link to netcdf-cxx-legacy.

Kind Regards,

Bas
diff -Nru paraview-5.11.0+dfsg/debian/changelog 
paraview-5.11.0+dfsg/debian/changelog
--- paraview-5.11.0+dfsg/debian/changelog   2023-01-21 12:41:21.0 
+0100
+++ paraview-5.11.0+dfsg/debian/changelog   2023-06-18 16:07:08.0 
+0200
@@ -1,3 +1,10 @@
+paraview (5.11.0+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop using netcdf-cxx-legacy.
+
+ -- Bas Couwenberg   Sun, 18 Jun 2023 16:07:08 +0200
+
 paraview (5.11.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru paraview-5.11.0+dfsg/debian/control 
paraview-5.11.0+dfsg/debian/control
--- paraview-5.11.0+dfsg/debian/control 2023-01-21 12:41:21.0 +0100
+++ paraview-5.11.0+dfsg/debian/control 2023-06-18 16:06:56.0 +0200
@@ -55,7 +55,6 @@
libgl2ps-dev,
libeigen3-dev,
libnetcdf-dev (>= 1:4.9.0),
-   libnetcdf-cxx-legacy-dev,
libjsoncpp-dev,
libglew-dev,
libxdmf-dev,
--- End Message ---
--- Begin Message ---
Source: paraview
Source-Version: 5.11.0+dfsg-2
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
paraview, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1038...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated paraview package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Aug 2023 16:11:56 +0100
Source: paraview
Architecture: source
Version: 5.11.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Alastair McKinstry 
Closes: 1037814 1038602
Changes:
 paraview (5.11.0+dfsg-2) unstable; urgency=medium
 .
   * Drop build-dep on libnetcdf-cxx-legacy-dev: Closes: #1037814
   * g++-13.patch:  FTBFS with g++ 13. Closes: #1038602
   * Srandards-Version: 4.6.2
Checksums-Sha1:
 befc62233f7fbdb3401b6b5c42ea15e0dc7fc225 3142 paraview_5.11.0+dfsg-2.dsc
 c61c9dc783e2c4a68997b91a9cb3d963d50035b5 33580 
paraview_5.11.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 011532bbf0fa7fe087407ac6b54f81d44739969a4b2cfd600f356e7f28871a60 3142 
paraview_5.11.0+dfsg-2.dsc
 1f3e884a53855b1d39e8ee2ad5ad56561592c015d20abbfbd67e6fd08943b4a2 33580 
paraview_5.11.0+dfsg-2.debian.tar.xz
Files:
 f3026ecd9f8e787a05d15df25c3adc09 3142 science optional 
paraview_5.11.0+dfsg-2.dsc
 4e8dd82173f1c130ff008a20556bb66e 33580 science optional 
paraview_5.11.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmTKjRAACgkQy+a7Tl2a
06VBsA//epwenUuvk91E0Dsj4eN63vxzgDmfz5r9R1oDejHGwa2Rjhb1zSSIB0kl
TwDUaz5Ye3MdVn1/ska29X5MrpyKrjtoGwGBF/h0FNBwt6RyxJf53OgrXPhFnV56
rhZrHVfmAem1WMor6DiXM9yNR6rvtp3FCb0XVgmuklZgpr6KoV5dxalEMmdAgGfl
+wIkODGxOJuDvkyfWQy9vdkLcD3unOpz/sMBmIkH0jPkU6RlEidOAGhytG2oXBoB
tiFF88jf0XhqFYzkpX9QOTjXdN7qxuGr9RccE53JT3QmhdjtrjJqkmbEm/CqwfpO
ig97rRVvllCgpv8p8KiWkHSu3vvqKPgWWphd3xC9hocnQTNramEogsMciVC59jNf
+KidFBIdTIaBtzP56/GhUA4dEBR1WXl+gRS2HXioRwXfD1D3qzfraV1yssElZvM9
M+PtK9Oei8dQ/jXIb18ftP+uQ6MlebXAbW2eIhU4gz3qUzgNTGSGFHgGtakQGFUl
m+h0zLiCgTBw4/4DT65IVeCyZVrCgUwrQ4r6e7Dh8rc5RSHktzHgLutFIUyK2f9J
bSkuiAiZY3lWEeAwB4Cz1yZSdUIc97OuGDpeuDBnzEhqGCfmShlIuMI39gWbSdqm
tKaumLxoOxoHC/PL0c0D4sb29bB/KCIWdEVLnxFLQD20DF2D04M=
=6SAV
-END PGP 

Processed: severity of 1035639 is serious, tagging 1035639

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1035639 serious
Bug #1035639 [src:git-imerge] git-imerge: FTBFS with tox 4
Severity set to 'serious' from 'normal'
> tags 1035639 + ftbfs
Bug #1035639 [src:git-imerge] git-imerge: FTBFS with tox 4
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1035639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): forcibly merging 1042890 1042907

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1042890 1042907
Bug #1042890 [src:haskell-mode] haskell-mode: bytecompilation fails against 
Emacs 29.1
Unable to merge bugs because:
package of #1042907 is 'elpa-haskell-mode' not 'src:haskell-mode'
Failed to forcibly merge 1042890: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042890
1042907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1035640 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1035640 serious
Bug #1035640 [src:python-magic] python-magic: FTBFS with tox 4
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1035640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1035640

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1035640 + ftbfs
Bug #1035640 [src:python-magic] python-magic: FTBFS with tox 4
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1035640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042889: vm breakage with Emacs 29

[Dirk Eddelbuettel]

On 2 August 2023 at 14:41, Ian Jackson wrote:
| Dirk Eddelbuettel writes ("Re: vm breakage with Emacs 29"):
| > On 2 August 2023 at 13:17, Ian Jackson wrote:
| > | Hi.  Since you were helpful with #1039105 "Fails to start with Emacs
| > | 28" I thought I would draw your attention to #1042889
| > | "vm: autopkgtest fails against Emacs 29.1" [0]
| > | 
| > | I won't have time to look at this until next week, probably.  Any help
| > | or background research would be greatly appreciated.  We need to fix
| > | this to avoid vm getting autoremoved.
| > | 
| > | I did have a quick look at the test log [1] and the failure looks
| > | genuine.  I suggest we do any further diagnosis in the bug.
| > 
| > The band-aid I found and submitted for #1039105 (ie per Fedora's tracker,
| > "just do not byte compile") seems apt here, no?  I still do not really read
| > (or, for that matter, write) elisp but it seems to complain about byte code.
| > 
| > So I would try two things:
| >  - turn off elisp byte compilation as in #1039105
| 
| The patch from #1039105 is still in the package.

Ok.

| Do we need to add to a list of files in it, or something, do you

That was my hunch.

| think ?  Maybe it would be best to disable byte compilation
| completely.

Yes given the previous bug report and fix ensuring no byte-compilation takes
place for vm may be best. At least until someone (upstream? another dev?)
understand why it breaks vm.

Dirk

| 
| One thing that would be useful would be for someone to try out emacs
| and vm in a sid chroot; that would confirm that this isn't a spurious
| test failure (or confirm that it is).
| 
| Thanks,
| Ian.
| 
| -- 
| Ian JacksonThese opinions are my own.  
| 
| Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
| that is a private address which bypasses my fierce spamfilter.

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1042904: SOLVED: Acknowledgement (libvirt-clients: fail to start VM 'file' driver requires '/dev/vg0/UTM' to be a regular file)

[Daniel]

in xml files not only 'disk type' have to be changed to 'block' but also 
'source' to 'dev'


Can be closed as not a bug
--
Daniel

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Axel Beckert]

Package: elpa-muse
Version: 3.20+dfsg-7
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

Since upgrading to Emacs 29.1, byte-(re-)compilation fails as follows:

[…]
Install elpa-muse for emacs
install/muse-3.20: Handling install of emacsen flavor emacs
install/muse-3.20: byte-compiling for emacs

In toplevel form:
cgi.el:71:2: Warning: Package cl is deprecated
cgi.el:87:13: Warning: Unknown defun property ‘character’

In cgi-decode-string:
cgi.el:94:4: Warning: ‘do’ is an obsolete alias (as of 27.1); use ‘cl-do’ 
instead.
cgi.el:101:15: Warning: ‘incf’ is an obsolete alias (as of 27.1); use ‘cl-incf’ 
instead.
cgi.el:108:17: Warning: ‘incf’ is an obsolete alias (as of 27.1); use ‘cl-incf’ 
instead.

In cgi-decode:
cgi.el:124:6: Warning: ‘flet’ is an obsolete macro (as of 24.3); use either 
‘cl-flet’ or ‘cl-letf’.

In cgi-arguments:
cgi.el:161:13: Warning: ‘loop’ is an obsolete alias (as of 27.1); use ‘cl-loop’ 
instead.

In end of data:
cgi.el:197:16: Warning: the function ‘calendar-current-date’ might not be 
defined at runtime.

In toplevel form:
htmlize-hack.el:12:13: Warning: ‘loop’ is an obsolete alias (as of 27.1); use 
‘cl-loop’ instead.
htmlize-hack.el:17:8: Warning: ‘reduce’ is an obsolete function (as of 27.1); 
use ‘cl-reduce’ instead.

In muse-backlink-insert-hook-func:
muse-backlink.el:264:12: Warning: ‘font-lock-fontify-buffer’ is for interactive 
use only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead.

In end of data:
muse-backlink.el:313:33: Warning: the function ‘muse-make-link’ might not be 
defined at runtime.

In toplevel form:
muse-colors.el:60:2: Warning: custom-declare-variable 
`muse-colors-autogen-headings' docstring has wrong usage of unescaped single 
quotes (use \= or different
 quoting)
muse-colors.el:94:2: Warning: custom-declare-variable 
`muse-colors-inline-image-method' docstring has wrong usage of unescaped single 
quotes (use \= or differ
ent quoting)

In muse-colors-region:
muse-colors.el:577:10: Warning: ‘inhibit-point-motion-hooks’ is an obsolete 
variable (as of 25.1); use ‘cursor-intangible-mode’ or ‘cursor-sensor-mode’ 
instea
d

In muse-unhighlight-region:
muse-colors.el:732:10: Warning: ‘inhibit-point-motion-hooks’ is an obsolete 
variable (as of 25.1); use ‘cursor-intangible-mode’ or ‘cursor-sensor-mode’ 
instea
d

In muse-colors-lisp-tag:
muse-colors.el:775:30: Warning: ‘muse-looking-back’ called with 1 argument, but 
requires 2 or 3

In muse-docbook-markup-paragraph:
muse-docbook.el:233:41: Warning: ‘muse-looking-back’ called with 1 argument, 
but requires 2 or 3

In toplevel form:
muse-html.el:67:2: Warning: custom-declare-variable `muse-html-style-sheet' 
docstring wider than 80 characters
muse-html.el:96:2: Warning: custom-declare-variable `muse-xhtml-style-sheet' 
docstring wider than 80 characters
muse-html.el:399:2: Warning: custom-declare-variable 
`muse-html-meta-content-encoding' docstring has wrong usage of unescaped single 
quotes (use \= or differe
nt quoting)
muse-html.el:421:2: Warning: custom-declare-variable 
`muse-html-src-allowed-modes' docstring has wrong usage of unescaped single 
quotes (use \= or different q
uoting)

In muse-html-markup-paragraph:
muse-html.el:490:6: Warning: ‘muse-looking-back’ called with 1 argument, but 
requires 2 or 3

In muse-html-src-tag:
muse-html.el:670:16: Warning: ‘font-lock-fontify-buffer’ is for interactive use 
only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: Unknown defun property ‘character’
../../elpa-src/muse-3.20/cgi.el: Warning: ‘do’ is an obsolete alias (as of 
27.1); use ‘cl-do’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘incf’ is an obsolete alias (as of 
27.1); use ‘cl-incf’ instead.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘flet’ is an obsolete macro (as of 
24.3); use either ‘cl-flet’ or ‘cl-letf’.
../../elpa-src/muse-3.20/cgi.el: Warning: ‘loop’ is an obsolete alias (as of 
27.1); use ‘cl-loop’ instead.
../../elpa-src/muse-3.20/muse-ipc.el: Warning: ‘return-from’ is an obsolete 
alias (as of 27.1); use ‘cl-return-from’ instead.
../../elpa-src/muse-3.20/muse-ipc.el: Warning: ‘return-from’ is an obsolete 
alias (as of 27.1); use ‘cl-return-from’ instead.

In toplevel form:
muse-ipc.el:50:2: Warning: custom-declare-variable `muse-ipc-ignore-done' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
muse-ipc.el:80:2: Warning: ‘defun*’ is an obsolete alias (as of 27.1); use 
‘cl-defun’ instead.

In muse-ipc-server-filter:
muse-ipc.el:93:6: Warning: ‘return-from’ is an obsolete alias (as of 27.1); use 
‘cl-return-from’ instead.

In muse-journal-generate-pages:
muse-journal.el:186:24: Warning: value returned from 

Processed: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Debian Bug Tracking System]

Processing control commands:

> affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk
Bug #1042911 [elpa-muse] Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: 
Cannot open load file: No such file or directory, assoc
Added indication that 1042911 affects emacs, emacs-gtk, emacs-lucid, emacs-nox, 
and emacs-pgtk

-- 
1042911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1025559: fwupd: dependency on transitional policykit-1 package

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1025559 [src:fwupd] fwupd: dependency on transitional policykit-1 package
Added tag(s) patch.

-- 
1025559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025559: fwupd: dependency on transitional policykit-1 package

[Simon McVittie]

Control: tags -1 + patch

On Tue, 06 Dec 2022 at 13:22:40 +, Simon McVittie wrote:
> This package has a Depends and/or Build-Depends on the transitional
> package policykit-1, which has been separated into polkitd, pkexec and
> (deprecated) polkitd-pkla packages.

This package doesn't seem to use pkexec, so please consider the attached
patch, also available as
.

It compiles successfully but I have not otherwise tested it.

According to diffoscope, the only differences in the built binary packages
as a result of this change seem to be build paths and Build-IDs.

Thanks,
smcv
>From 03db339d5bffb44460b4c29fa83a6ffb480e0c09 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 2 Aug 2023 15:27:55 +0100
Subject: [PATCH] d/control, d/control.in: Use polkitd instead of transitional
 policykit-1

Closes: #1025559
---
 debian/control| 4 ++--
 debian/control.in | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/debian/control b/debian/control
index c3fb4c313..f0bc2cb75 100644
--- a/debian/control
+++ b/debian/control
@@ -55,7 +55,7 @@ Build-Depends:
 	mingw-w64-tools [amd64 arm64 armhf i386],
 	pandoc,
 	pkg-config,
-	policykit-1 (>> 0.105-14),
+	polkitd,
 	protobuf-c-compiler,
 	python3-gi-cairo,
 	python3-jinja2,
@@ -136,7 +136,7 @@ Depends: ${misc:Depends},
  dbus-x11,
  fwupd,
  gnome-desktop-testing,
- policykit-1,
+ polkitd,
  python3,
  python3-gi,
  python3-requests,
diff --git a/debian/control.in b/debian/control.in
index 85d1af4b4..ad7af9786 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -72,7 +72,7 @@ Depends: ${misc:Depends},
  dbus-x11,
  fwupd,
  gnome-desktop-testing,
- policykit-1,
+ polkitd,
  python3,
  python3-gi,
  python3-requests,
@@ -137,4 +137,4 @@ Description: GObject introspection data for libfwupd
  This package provides the introspection data for libfwupd.
  .
  It can be used by packages using the GIRepository format to generate
- dynamic bindings.
\ No newline at end of file
+ dynamic bindings.
-- 
2.40.1

Bug#1042908: src:hypercorn: fails to migrate to testing for too long: new build dependency not ready to migrate

[Paul Gevers]

Hi,

On Wed, 2 Aug 2023 17:31:30 +0200 Paul Gevers  wrote:
The version in unstable has a 
new Build-Depends, but that package isn't ready to migrate yet.


I hit the send button too fast. Right after sending I noticed that that 
package passed it's tests in unstable, so I triggered a retry for the 
migration tests, which, if I checked correctly, all passed now.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042723: src:r-cran-tmb: fails to migrate to testing for too long: autopkgtest regression

[Nilesh Patra]

On Mon, 31 Jul 2023 07:59:07 +0200 Paul Gevers  wrote:
> Source: r-cran-tmb
> Version: 1.9.2-1
> Severity: serious
> Control: close -1 1.9.4-1
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync

This needs fixing in two stages. The error is:

| 38s TMB was built with Matrix version 1.5.4.1
| 38s Current Matrix version is 1.5.3

So rmatrix's new version needs to go to testing, which is currently
1.6.0. So

1. rmatrix 1.6.0 needs to go to testing
2. tmb needs to be rebuilt against rmatrix 1.6.0

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: src:hypercorn: fails to migrate to testing for too long: new build dependency not ready to migrate

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.14.4-1
Bug #1042908 [src:hypercorn] src:hypercorn: fails to migrate to testing for too 
long: new build dependency not ready to migrate
Marked as fixed in versions hypercorn/0.14.4-1.
Bug #1042908 [src:hypercorn] src:hypercorn: fails to migrate to testing for too 
long: new build dependency not ready to migrate
Marked Bug as done

-- 
1042908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042908: src:hypercorn: fails to migrate to testing for too long: new build dependency not ready to migrate

[Paul Gevers]

Source: hypercorn
Version: 0.13.2-3
Severity: serious
Control: close -1 0.14.4-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:hypercorn has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The version in unstable has a 
new Build-Depends, but that package isn't ready to migrate yet.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=hypercorn



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042907: Breaks Emacs 29.1 upgrade: haskell.el:30:2: Error: Eager macro-expansion failure: (error "Misplaced t or ‘otherwise’ clause")

[Axel Beckert]

Package: elpa-haskell-mode
Version: 17.2-5
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

After upgrading Emacs to 29.1, byte-(re-)compiling fails as follows:

[…]
Install elpa-haskell-mode for emacs
install/haskell-mode-17.2snapshot: Handling install of emacsen flavor emacs
install/haskell-mode-17.2snapshot: byte-compiling for emacs
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 
'before will match ‘quote’.  If that’s intended, write (before quote) instead.  
Otherwise, don’t quote ‘before’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 'after 
will match ‘quote’.  If that’s intended, write (after quote) instead.  
Otherwise, don’t quote ‘after’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 
'single will match ‘quote’.  If that’s intended, write (single quote) instead.  
Otherwise, don’t quote ‘single’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'ghci will match ‘quote’.  If that’s intended, write (ghci quote) instead.  
Otherwise, don’t quote ‘ghci’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'cabal-repl will match ‘quote’.  If that’s intended, write (cabal-repl quote) 
instead.  Otherwise, don’t quote ‘cabal-repl’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'stack-ghci will match ‘quote’.  If that’s intended, write (stack-ghci quote) 
instead.  Otherwise, don’t quote ‘stack-ghci’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'unknown-command will match ‘quote’.  If that’s intended, write 
(unknown-command quote) instead.  Otherwise, don’t quote ‘unknown-command’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'option-missing will match ‘quote’.  If that’s intended, write (option-missing 
quote) instead.  Otherwise, don’t quote ‘option-missing’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'interactive-error will match ‘quote’.  If that’s intended, write 
(interactive-error quote) instead.  Otherwise, don’t quote ‘interactive-error’.

In toplevel form:
ghci-script-mode.el:20:2: Error: Eager macro-expansion failure: (error 
"Misplaced t or ‘otherwise’ clause")

In haskell-cabal-classify-line:
haskell-cabal.el:363:2: Warning: docstring wider than 80 characters
haskell-cabal.el:363:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)

In haskell-cabal-enum-targets:
haskell-cabal.el:496:2: Warning: docstring wider than 80 characters

In haskell-cabal-listify:
haskell-cabal.el:701:12: Warning: Case 'before will match ‘quote’.  If that’s 
intended, write (before quote) instead.  Otherwise, don’t quote ‘before’.
haskell-cabal.el:701:12: Warning: Case 'after will match ‘quote’.  If that’s 
intended, write (after quote) instead.  Otherwise, don’t quote ‘after’.
haskell-cabal.el:701:12: Warning: Case 'single will match ‘quote’.  If that’s 
intended, write (single quote) instead.  Otherwise, don’t quote ‘single’.

In haskell-cabal-line-filename:
haskell-cabal.el:926:2: Warning: docstring wider than 80 characters

In haskell-blank-line-p:
haskell-collapse.el:46:9: Warning: ‘point-at-eol’ is an obsolete function (as 
of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.

In haskell-hide-toggle-all:
haskell-collapse.el:95:19: Warning: ‘point-at-bol’ is an obsolete function (as 
of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.

In toplevel form:
haskell-commands.el:652:12: Error: Misplaced t or ‘otherwise’ clause

In toplevel form:
haskell-compile.el:42:2: Warning: custom-declare-variable 
`haskell-compile-cabal-build-command' docstring wider than 80 characters
haskell-compile.el:49:2: Warning: custom-declare-variable 
`haskell-compile-cabal-build-alt-command' docstring wider than 80 characters
haskell-compile.el:56:2: Warning: custom-declare-variable 
`haskell-compile-stack-build-command' docstring wider than 80 characters
haskell-compile.el:63:2: Warning: custom-declare-variable 
`haskell-compile-stack-build-alt-command' docstring wider than 80 characters
haskell-compile.el:70:2: Warning: custom-declare-variable 
`haskell-compile-command' docstring wider than 80 characters
haskell-compile.el:83:2: Warning: custom-declare-variable 
`haskell-compiler-type' docstring wider than 80 characters

In haskell-completions-grab-pragma-prefix:
haskell-completions.el:146:2: Warning: docstring has wrong usage of unescaped 
single quotes (use \= or different quoting)

In haskell-completions-grab-identifier-prefix:
haskell-completions.el:216:2: Warning: docstring has wrong usage of unescaped 
single quotes (use \= or different quoting)

In haskell-completions-grab-prefix:
haskell-completions.el:267:2: Warning: docstring has wrong usage of unescaped 
single quotes (use \= or different quoting)

In haskell-completions--simple-completions:

Processed: Breaks Emacs 29.1 upgrade: haskell.el:30:2: Error: Eager macro-expansion failure: (error "Misplaced t or ‘otherwise’ clause")

[Debian Bug Tracking System]

Processing control commands:

> affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk
Bug #1042907 [elpa-haskell-mode] Breaks Emacs 29.1 upgrade: haskell.el:30:2: 
Error: Eager macro-expansion failure: (error "Misplaced t or ‘otherwise’ 
clause")
Added indication that 1042907 affects emacs, emacs-gtk, emacs-lucid, emacs-nox, 
and emacs-pgtk

-- 
1042907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042904: libvirt-clients: fail to start VM 'file' driver requires '/dev/vg0/UTM' to be a regular file

[Daniel]

Package: libvirt-clients
Version: 9.0.0-4
Severity: grave
Justification: renders package unusable

The xml configuration file was working well on Debian 11. After 
upgrading to Bookworm I get this error, VM doesn't start:

virsh # start UTM
erreur :Failed to start domain 'UTM'
erreur :internal error: process exited while connecting to monitor: 
2023-08-02T14:13:20.203465Z kvm: -blockdev 
{"driver":"file","filename":"/dev/vg0/UTM","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: 
'file' driver requires '/dev/vg0/UTM' to be a regular file


Changing driver file to block give on xml validation:

erreur :XML document failed to validate against schema: Unable to 
validate doc against /usr/share/libvirt/schemas/domain.rng

Extra element devices in interleave
Element domain failed to validate content

Attached is the VM xml configuration file. All of our VMs are based on 
LVM disk, we can't use anymore VMs from this server !


-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvirt-clients depends on:
ii libc6 2.36-9+deb12u1
ii libgcc-s1 12.2.0-14
ii libglib2.0-0 2.74.6-2
ii libgnutls30 3.7.9-2
ii libreadline8 8.2-1.3
ii libvirt0 9.0.0-4
ii libxml2 2.9.14+dfsg-1.3~deb12u1
ii sensible-utils 0.0.17+nmu1

libvirt-clients recommends no packages.

Versions of packages libvirt-clients suggests:
pn libvirt-clients-qemu 
ii libvirt-daemon 9.0.0-4
pn libvirt-login-shell 

-- no debconf information



  UTM
  9dda06a5-689a-4656-9476-145897ede125
  4194304
  4194304
  2
  
hvm
  
  


  
  
  



  
  destroy
  restart
  restart
  


  
  
/usr/bin/kvm

  
  
  
  
  


  
  
  
  


  


  
  


  
  


  
  



  


  


  
  
  
  
  


  
  
  
  
  


  

  


  


  
  




  


  



  
  


  


  


  

  

Bug#1025552: calamares: dependency on transitional policykit-1 package

[Simon McVittie]

Control: tags -1 + patch

On Tue, 06 Dec 2022 at 13:16:06 +, Simon McVittie wrote:
> This package has a Depends and/or Build-Depends on the transitional
> package policykit-1, which has been separated into polkitd, pkexec and
> (deprecated) polkitd-pkla packages.

Proposed patch: attached or
https://salsa.debian.org/qt-kde-team/extras/calamares/-/merge_requests/4

Compiled successfully, otherwise untested. Unfortunately calamares'
build isn't reproducible, so I wasn't able to verify that the resulting
binaries are the same.

smcv
>From 95969c3c5fcbade88c040b4946355c9c9e63f27c Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 2 Aug 2023 13:03:21 +0100
Subject: [PATCH] Replace transitional build-dependency policykit-1 with
 polkitd

Closes: #1025552
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index df62061..322aead 100644
--- a/debian/control
+++ b/debian/control
@@ -27,7 +27,7 @@ Build-Depends: cmake,
os-prober ,
pkg-config,
pkg-kde-tools,
-   policykit-1 ,
+   polkitd ,
python3-dev,
qml-module-qtquick-layouts,
qml-module-qtquick-privatewidgets,
-- 
2.40.1

Processed: Re: Bug#1025552: calamares: dependency on transitional policykit-1 package

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1025552 [src:calamares] calamares: dependency on transitional policykit-1 
package
Added tag(s) patch.

-- 
1025552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025561: marked as done (deja-dup: recommends transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Wed, 2 Aug 2023 15:06:12 +0100
with message-id 
and subject line Re: Bug#1025561: packages with dependencies on transitional 
policykit-1 package
has caused the Debian Bug report #1025561,
regarding deja-dup: recommends transitional policykit-1 package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: deja-dup
Version: 44.0-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1

This package has a Recommends on the transitional package policykit-1,
which has been separated into polkitd, pkexec and (deprecated)
polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 44.2-2

On Sun, 11 Jun 2023 at 08:24:34 -0400, Michael Terry wrote:
> Good news! You can simply drop the Depends entirely for Deja Dup. It used to
> used pkexec, but no longer user policykit at all, since version 42.0 I 
> believe.

Looks like this was done, but without closing the bug. Closing it now.

Thanks,
smcv--- End Message ---

Bug#1042900: Breaks Emacs 29.1 upgrade: pointback.el:34:2: Error: Cannot open load file: No such file or directory, assoc

[Axel Beckert]

Package: elpa-pointback
Version: 0.2-4
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

Since the upgrade to Emacs 29.1-1, byte (re-)compilation fails as
follows:

[…]
Install elpa-pointback for emacs
install/pointback-0.2: Handling install of emacsen flavor emacs
install/pointback-0.2: byte-compiling for emacs

In toplevel form:
pointback.el:34:2: Error: Cannot open load file: No such file or directory, 
assoc
ERROR: install script from elpa-pointback package failed
dpkg: error processing package emacs-gtk (--configure):
 installed emacs-gtk package post-installation script subprocess returned error 
exit status 1
dpkg: dependency problems prevent configuration of emacs:
[…]

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages elpa-pointback depends on:
ii  dh-elpa-helper  2.0.17
ii  emacsen-common  3.0.5

Versions of packages elpa-pointback recommends:
iu  emacs  1:29.1+1-2
ih  emacs-gtk [emacs]  1:29.1+1-2

elpa-pointback suggests no packages.

-- no debconf information

Processed: Breaks Emacs 29.1 upgrade: pointback.el:34:2: Error: Cannot open load file: No such file or directory, assoc

[Debian Bug Tracking System]

Processing control commands:

> affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk
Bug #1042900 [elpa-pointback] Breaks Emacs 29.1 upgrade: pointback.el:34:2: 
Error: Cannot open load file: No such file or directory, assoc
Added indication that 1042900 affects emacs, emacs-gtk, emacs-lucid, emacs-nox, 
and emacs-pgtk

-- 
1042900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025635: marked as done (x2gothinclient: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Wed, 2 Aug 2023 15:02:22 +0100
with message-id 
and subject line Re: Bug#1025635: x2gothinclient: dependency on transitional 
policykit-1 package
has caused the Debian Bug report #1025635,
regarding x2gothinclient: dependency on transitional policykit-1 package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x2gothinclient
Version: 1.5.0.1-8.1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and/or Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 1.5.0.1-9

On Tue, 06 Dec 2022 at 19:02:47 +, Simon McVittie wrote:
> This package has a Depends and/or Build-Depends on the transitional
> package policykit-1, which has been separated into polkitd, pkexec and
> (deprecated) polkitd-pkla packages.

This seems to have been fixed in the meantime.

smcv--- End Message ---

Bug#1025631: marked as done (timekpr-next: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Wed, 2 Aug 2023 15:01:16 +0100
with message-id 
and subject line Re: Bug#1025631: timekpr-next: dependency on transitional 
policykit-1 package
has caused the Debian Bug report #1025631,
regarding timekpr-next: dependency on transitional policykit-1 package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: timekpr-next
Version: 0.5.2-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and/or Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 0.5.4-1

On Tue, 06 Dec 2022 at 18:59:31 +, Simon McVittie wrote:
> This package has a Depends and/or Build-Depends on the transitional
> package policykit-1, which has been separated into polkitd, pkexec and
> (deprecated) polkitd-pkla packages.

It appears this was fixed in 0.5.4-1 without closing the bug. Closing
it now.

smcv--- End Message ---

Bug#1042889: vm: autopkgtest fails against Emacs 29.1

[Ian Jackson]

Sean Whitton writes ("Bug#1042889: vm: autopkgtest fails against Emacs 29.1"):
> vm's autopkgtest fails with Emacs 29.1, which latter is now in sid.

Hi, Sean, as you see we're looking into this.
I have some questions for you as an Emacs expert:

Is byte-compilation known to be sometimes broken?  Is there a
recommended approach to problems caused by byte-compilation ?

We recently did an update to vm in Debian stable, to work around a
critical problem with Emacs 28 (#1039105).  The autopkgtest which is
now failing is new - I introduced it to detect future bugs, which it
seems to have done.

The previous bug was related to byte-compilation and we "fixed" it by
turning off byte-compilation for at least some of vm's files (in what
I feel was rather an ad-hoc way, albeit an effective one).

Or to put it another way, is it possible that this is a bug in emacs
29.1 and if so what is the best workaround ?

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1042889: vm breakage with Emacs 29

[Ian Jackson]

Dirk Eddelbuettel writes ("Re: vm breakage with Emacs 29"):
> On 2 August 2023 at 13:17, Ian Jackson wrote:
> | Hi.  Since you were helpful with #1039105 "Fails to start with Emacs
> | 28" I thought I would draw your attention to #1042889
> | "vm: autopkgtest fails against Emacs 29.1" [0]
> | 
> | I won't have time to look at this until next week, probably.  Any help
> | or background research would be greatly appreciated.  We need to fix
> | this to avoid vm getting autoremoved.
> | 
> | I did have a quick look at the test log [1] and the failure looks
> | genuine.  I suggest we do any further diagnosis in the bug.
> 
> The band-aid I found and submitted for #1039105 (ie per Fedora's tracker,
> "just do not byte compile") seems apt here, no?  I still do not really read
> (or, for that matter, write) elisp but it seems to complain about byte code.
> 
> So I would try two things:
>  - turn off elisp byte compilation as in #1039105

The patch from #1039105 is still in the package.

Do we need to add to a list of files in it, or something, do you
think ?  Maybe it would be best to disable byte compilation
completely.

One thing that would be useful would be for someone to try out emacs
and vm in a sid chroot; that would confirm that this isn't a spurious
test failure (or confirm that it is).

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1042023: opm-common: FTBFS on armel and mipsel

[Markus Blatt]

Thanks a lot for reporting this. We are aware of this but did not find 
the time to look into it, yet.


Is there a good howto/instructions how to debug such problems using e.g. 
qemu for emulating arm? Or is it possible to gain access to an arm 
machine as a Debian Maintainer?


That would help a lot.

Kind regards,

Markus

Bug#1042892: nvidia-legacy-390xx-kernel-dkms: dkms module does not build against kernel 6.4

[Vincent Lefevre]

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042081
for the same bug corresponding to nvidia-kernel-dkms.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Christoph Anton Mitterer]

Control: forwarded -1 https://github.com/strukturag/libheif/issues/933

Hey.

AFAICS, this had also been reported (and fixed meanwhile) upstream.

Cheers,
Chris.

Processed: Re: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/strukturag/libheif/issues/933
Bug #1041242 [libheif1] libheif1: 1.16.2-1+b1 breaks displaying any pictures
Set Bug forwarded-to-address to 
'https://github.com/strukturag/libheif/issues/933'.

-- 
1041242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042890: haskell-mode: bytecompilation fails against Emacs 29.1

[Sean Whitton]

Source: haskell-mode
Version: 17.2-5
Severity: serious

Dear maintainer,

haskell-mode fails to bytecompile against Emacs 29.1, which latter is
now in sid.

In toplevel form:
haskell.el:30:2: Error: Eager macro-expansion failure: (error "Misplaced t 
or ‘otherwise’ clause")

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1042889: vm: autopkgtest fails against Emacs 29.1

[Sean Whitton]

Source: vm
Version: 8.2.0b-10
Severity: serious

Dear maintainer,

vm's autopkgtest fails with Emacs 29.1, which latter is now in sid.

https://ci.debian.net/packages/v/vm/testing/amd64/

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025638 [src:ayatana-indicator-session] ayatana-indicator-session: 
autopkgtest depends on transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025635 [src:x2gothinclient] x2gothinclient: dependency on transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025633 [src:ukui-biometric-auth] ukui-biometric-auth: dependency on 
transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025631 [src:timekpr-next] timekpr-next: dependency on transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025603 [src:modem-manager-gui] modem-manager-gui: dependency on 
transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025602 [src:mate-system-monitor] mate-system-monitor: dependency on 
transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025600 [src:mate-settings-daemon] mate-settings-daemon: dependency on 
transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025589 [wicd-gtk] wicd-gtk: recommends transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025597 [src:mate-applets] mate-applets: dependency on transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025582 [src:lxde-metapackages] lxde-metapackages: recommends transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025581 [src:lxsession] lxsession: dependency on transitional policykit-1 
package
Severity set to 'serious' from 'important'

-- 
1025581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025576 [src:libgsecuredelete] libgsecuredelete: recommends transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025574 [src:hplip] hplip: dependency on transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025573 [src:hotspot] hotspot: dependency on transitional policykit-1 
package
Severity set to 'serious' from 'important'

-- 
1025573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025572 [src:hannah-foo2zjs] hannah-foo2zjs: dependency on transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025571 [src:guidedog] guidedog: dependency on transitional policykit-1 
package
Severity set to 'serious' from 'important'

-- 
1025571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025568 [src:gparted] gparted: dependency on transitional policykit-1 
package
Severity set to 'serious' from 'important'

-- 
1025568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025565 [src:gnome-multi-writer] gnome-multi-writer: dependency on 
transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025563 [src:gdebi] gdebi: dependency on transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025561 [deja-dup] deja-dup: recommends transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025559 [src:fwupd] fwupd: dependency on transitional policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025558 [src:fprintd] fprintd: dependency on transitional policykit-1 
package
Severity set to 'serious' from 'important'

-- 
1025558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #102 [src:cpupower-gui] cpupower-gui: dependency on transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025552 [src:calamares] calamares: dependency on transitional policykit-1 
package
Severity set to 'serious' from 'important'

-- 
1025552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025551 [src:caja-dropbox] caja-dropbox: dependency on transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dependencies on transitional policykit-1 package are now RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025550 [src:caja-admin] caja-admin: dependency on transitional 
policykit-1 package
Severity set to 'serious' from 'important'

-- 
1025550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems