Bug#1056393: radare2-cutter: Cannot debug binary: File '' does not have executable permissions.
Package: radare2-cutter Version: 1.12.0-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: nathan.teodo...@canonical.com Dear Maintainer, 1. 'Cutter /bin/ls' or any other binary in your system. 2. Click start debug (F9). Expected Debugging starts. Observed A dialog window with "Cannot debug binary: File '' does not have executable permissions." appears. In stderr, r_config_get: variable 'file.path' not found appears. I can reproduce this both in Ubuntu 24.04 and Debian unstable. -- System Information: Debian Release: bookworm/sid APT prefers noble APT policy: (500, 'noble') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-9-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=pt_BR.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 radare2-cutter depends on: ii libc6 2.38-1ubuntu6 ii libcgraph6 2.42.2-7build3 ii libgcc-s1 13.2.0-6ubuntu1 ii libgvc62.42.2-7build3 ii libkf5syntaxhighlighting5 5.112.0-0ubuntu1 ii libpython3.11 3.11.6-3 ii libqt5core5a 5.15.10+dfsg-3 ii libqt5gui5 5.15.10+dfsg-3 ii libqt5network5 5.15.10+dfsg-3 ii libqt5svg5 5.15.10-2 ii libqt5widgets5 5.15.10+dfsg-3 ii libradare2-5.0.0 5.5.0+dfsg-1ubuntu1 ii libstdc++6 13.2.0-6ubuntu1 ii python33.11.4-5 ii python3-ipykernel 6.24.0-3 ii python3-jupyter-client 7.4.9-2 ii python3-notebook 6.4.12-2.2 ii python3-zmq24.0.1-4build1 radare2-cutter recommends no packages. radare2-cutter suggests no packages. -- no debconf information
Processed: severity of 1050300 is important
Processing commands for cont...@bugs.debian.org: > severity 1050300 important Bug #1050300 [mkbootimg] mkbootimg package missing gki module Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1050300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056334: marked as done (node-ast-types: autopkgtest failure)
Your message dated Wed, 22 Nov 2023 07:21:31 + with message-id and subject line Bug#1056334: fixed in node-ast-types 0.16.1-3 has caused the Debian Bug report #1056334, regarding node-ast-types: autopkgtest failure 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.) -- 1056334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-ast-types Version: 0.16.1-2 Severity: serious Hello, according to ci, the package autopkgtests looks failing. https://ci.debian.net/packages/n/node-ast-types/unstable/amd64/39617621/ 66s autopkgtest [20:34:26]: test pkg-js-autopkgtest: [--- 66s # Using ./package.(json|yaml) 66s # Node module name is ast-types 66s # Build files found: tsconfig.json 66s # Test files found: 66s # Found debian/tests/pkg-js/files, let's use it 66s # Files/dir to be installed from source: src 66s test 66s tsconfig* 66s ls: cannot access 'test': No such file or directory 66s # Copy debian/tests/pkg-js content 66s 'debian/tests/pkg-js' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js' 66s 'debian/tests/pkg-js/test' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js/test' 66s 'debian/tests/pkg-js/files' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js/files' 66s Found debian/tests/test_modules 66s # let's copy it 66s Found debian/nodejs/extlinks 67s @babel/parser linked into node_modules 67s @babel/types linked into node_modules 68s tslib linked into node_modules 68s @types/esprima linked into node_modules 69s @types/estree linked into node_modules 69s @types/glob linked into node_modules 70s @types/mocha linked into node_modules 70s # Searching module in /usr/lib/nodejs/ast-types 70s # Searching module in /usr/lib/*/nodejs/ast-types 70s # Searching module in /usr/share/nodejs/ast-types 70s # Found /usr/share/nodejs/ast-types 70s # Searching files to link in /usr/share/nodejs/ast-types 70s # Launch debian/tests/pkg-js/test with sh -ex 70s + test /tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp != 70s + rm -rf lib 70s + tsc 70s Version 4.8.4 70s tsc: The TypeScript Compiler - Version 4.8.4 70s 70s COMMON COMMANDS 70s 70s tsc 70s Compiles the current project (tsconfig.json in the working directory.) 70s 70s tsc app.ts util.ts 70s Ignoring tsconfig.json, compiles the specified files with default compiler options. 70s 70s tsc -b 70s Build a composite project in the working directory. 70s 70s tsc --init 70s Creates a tsconfig.json with the recommended settings in the working directory. 70s 70s tsc -p ./path/to/tsconfig.json 70s Compiles the TypeScript project located at the specified path. 70s 70s tsc --help --all 70s An expanded version of this information, showing all possible compiler options 70s 70s tsc --noEmit 70s tsc --target esnext 70s Compiles the current project, with additional settings. 70s 70s COMMAND LINE FLAGS 70s 70s --help, -h 70s Print this message. 70s 70s --watch, -w 70s Watch input files. 70s 70s --all 70s Show all compiler options. 70s 70s --version, -v 70s Print the compiler's version. 70s 70s --init 70s Initializes a TypeScript project and creates a tsconfig.json file. 70s 70s --project, -p 70s Compile the project given the path to its configuration file, or to a folder with a 'tsconfig.json'. 70s 70s --build, -b 70s Build one or more projects and their dependencies, if out of date 70s 70s --showConfig 70s Print the final configuration instead of building. 70s 70s COMMON COMPILER OPTIONS 70s 70s --pretty 70s Enable color and formatting in TypeScript's output to make compiler errors easier to read. 70s type: boolean 70s default: true 70s 70s --target, -t 70s Set the JavaScript language version for emitted JavaScript and include compatible library declarations. 70s one of: es3, es5, es6/es2015, es2016, es2017, es2018, es2019, es2020, es2021, es2022, esnext 70s default: es3 70s 70s --module, -m 70s Specify what module code is generated. 70s one of: none, commonjs, amd, umd, system, es6/es2015, es2020, es2022, esnext, node16, nodenext 70s default: undefined 70s 70s --lib 70s Specify a set of bundled library declaration files that describe the target runtime environment. 70s one or more: es5, es6/es2015, es7/es2016, es2017, es2018, es2019, es2020, es2021, es2022, esnext, dom, dom.iterable, webworker,
Bug#1053700: marked as done (python-xarray: autopkgtest regression on s390x)
Your message dated Wed, 22 Nov 2023 07:21:58 +
with message-id
and subject line Bug#1053700: fixed in python-xarray 2023.11.0-1
has caused the Debian Bug report #1053700,
regarding python-xarray: autopkgtest regression on s390x
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.)
--
1053700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 2023.09.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
There are new autopkgtest failures on s390x [1] which seem to be
related to endianness, dtype('>M8[ns]') vs dtype('https://ci.debian.net/packages/p/python-xarray/unstable/s390x/
207s _
test_roundtrip_datetime64_nanosecond_precision[1677-09-21T00:12:43.145224193-ns-int64-20-True]
_
207s
207s timestr = '1677-09-21T00:12:43.145224193', timeunit = 'ns'
207s dtype = , fill_value = 20, use_encoding = True
207s
207s @pytest.mark.parametrize(
207s "timestr, timeunit, dtype, fill_value, use_encoding",
207s [
207s ("1677-09-21T00:12:43.145224193", "ns", np.int64, 20, True),
207s ("1970-09-21T00:12:44.145224808", "ns", np.float64,
1e30, True),
207s (
207s "1677-09-21T00:12:43.145225216",
207s "ns",
207s np.float64,
207s -9.223372036854776e18,
207s True,
207s ),
207s ("1677-09-21T00:12:43.145224193", "ns", np.int64, None, False),
207s ("1677-09-21T00:12:43.145225", "us", np.int64, None, False),
207s ("1970-01-01T00:00:01.01", "us", np.int64, None, False),
207s ("1677-09-21T00:21:52.901038080", "ns", np.float32,
20.0, True),
207s ],
207s )
207s def test_roundtrip_datetime64_nanosecond_precision(
207s timestr: str,
207s timeunit: str,
207s dtype: np.typing.DTypeLike,
207s fill_value: int | float | None,
207s use_encoding: bool,
207s ) -> None:
207s # test for GH7817
207s time = np.datetime64(timestr, timeunit)
207s times = [np.datetime64("1970-01-01T00:00:00", timeunit),
np.datetime64("NaT"), time]
207s
207s if use_encoding:
207s encoding = dict(dtype=dtype, _FillValue=fill_value)
207s else:
207s encoding = {}
207s
207s var = Variable(["time"], times, encoding=encoding)
207s > assert var.dtype == np.dtype("M8[ns]') == dtype('M8[ns]') = \narray(['1970-01-01T00:00:00.0',
'NaT',\n '1677-09-21T00:12:43.145224193'],
dtype='datetime64[ns]').dtype
207s E+ and dtype('(' = np.dtype
--- End Message ---
--- Begin Message ---
Source: python-xarray
Source-Version: 2023.11.0-1
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
python-xarray, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated python-xarray 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, 22 Nov 2023 07:37:01 +0100
Source: python-xarray
Architecture: source
Version: 2023.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Andreas Tille
Closes: 1004869 1050854 1053700
Changes:
python-xarray (2023.11.0-1) unstable; urgency=medium
.
[ Andreas Tille ]
* Team upload.
* New upstream version. Closes: #1050854
* Remove trailing whitespace in debian/changelog (routine-update)
* Remove trailing whitespace in debian/control (routine-update)
* Remove trailing whitespace in debian/rules (routine-update)
* Add salsa-ci file (routine-update)
* Rules-Requires-Root: no (routine-update)
* Use secure URI in Homepage field.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
* Re-enable docs which do not segfault but do nothing else. Upstream might
provide docs in future - otherwise the python-xarray-doc package could be
dropped completely.
.
[
Bug#1050854: marked as done (python-xarray: autopkgtest failures)
Your message dated Wed, 22 Nov 2023 07:21:58 +
with message-id
and subject line Bug#1050854: fixed in python-xarray 2023.11.0-1
has caused the Debian Bug report #1050854,
regarding python-xarray: autopkgtest failures
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.)
--
1050854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 2023.08.0-1
Severity: serious
Tags: patch
Justification: autopkgtest failures
Dear Maintainer,
The autopkgtest for your package is failing:
230s === FAILURES
===
230s test_open_mfdataset_manyfiles[netcdf4-20-True-None-5]
_
230s
230s self = CachingFileManager(,
'/tmp/tmp4hr6i68_/temp-1120.nc', mode='r', kwargs={'clobber': True, 'diskless':
False, 'persist': False, 'format': 'NETCDF4'},
manager_id='abdbaa71-0b5f-4544-982d-afa923d39953')
230s needs_lock = True
230s
230s def _acquire_with_cache_info(self, needs_lock=True):
230s """Acquire a file, returning the file and whether it was
cached."""
230s with self._optional_lock(needs_lock):
230s try:
230s > file = self._cache[self._key]
230s
230s /usr/lib/python3/dist-packages/xarray/backends/file_manager.py:211:
230s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _
230s
230s self =
230s key = [,
('/tmp/tmp4hr6i68_/temp-1120.nc',), 'r', (('clobber', True), ('diskless',
False), ('format', 'NETCDF4'), ('persist', False)),
'abdbaa71-0b5f-4544-982d-afa923d39953']
230s
230s def __getitem__(self, key: K) -> V:
230s # record recent use of the key by moving it to the front of the
list
230s with self._lock:
230s > value = self._cache[key]
230s E KeyError: [,
('/tmp/tmp4hr6i68_/temp-1120.nc',), 'r', (('clobber', True), ('diskless',
False), ('format', 'NETCDF4'), ('persist', False)),
'abdbaa71-0b5f-4544-982d-afa923d39953']
230s
230s /usr/lib/python3/dist-packages/xarray/backends/lru_cache.py:56: KeyError
230s
230s During handling of the above exception, another exception occurred:
230s
230s readengine = 'netcdf4', nfiles = 20, parallel = True, chunks = None
230s file_cache_maxsize = 5
230s
230s @requires_dask
230s @pytest.mark.filterwarnings("ignore:use make_scale(name) instead")
230s def test_open_mfdataset_manyfiles(
230s readengine, nfiles, parallel, chunks, file_cache_maxsize
230s ):
230s # skip certain combinations
230s skip_if_not_engine(readengine)
230s
230s if ON_WINDOWS:
230s pytest.skip("Skipping on Windows")
230s
230s randdata = np.random.randn(nfiles)
230s original = Dataset({"foo": ("x", randdata)})
230s # test standard open_mfdataset approach with too many files
230s with create_tmp_files(nfiles) as tmpfiles:
230s writeengine = readengine if readengine != "pynio" else
"netcdf4"
230s # split into multiple sets of temp files
230s for ii in original.x.values:
230s subds = original.isel(x=slice(ii, ii + 1))
230s if writeengine != "zarr":
230s subds.to_netcdf(tmpfiles[ii], engine=writeengine)
230s else: # if writeengine == "zarr":
230s subds.to_zarr(store=tmpfiles[ii])
230s
230s # check that calculation on opened datasets works properly
230s > with open_mfdataset(
230s tmpfiles,
230s combine="nested",
230s concat_dim="x",
230s engine=readengine,
230s parallel=parallel,
230s chunks=chunks if (not chunks and readengine != "zarr")
else "auto",
230s ) as actual:
230s
230s /usr/lib/python3/dist-packages/xarray/tests/test_backends.py:3407:
230s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _
230s /usr/lib/python3/dist-packages/xarray/backends/api.py:1020: in
open_mfdataset
230s datasets, closers = dask.compute(datasets, closers)
230s /usr/lib/python3/dist-packages/dask/base.py:600: in compute
230s results = schedule(dsk, keys, **kwargs)
230s /usr/lib/python3/dist-packages/dask/threaded.py:89: in get
230s results = get_async(
230s /usr/lib/python3/dist-packages/dask/local.py:511: in get_async
230s raise_exception(exc, tb)
230s
Bug#1004869: marked as done (python-xarray: autopkgtest regression on i386)
Your message dated Wed, 22 Nov 2023 07:21:58 +
with message-id
and subject line Bug#1004869: fixed in python-xarray 2023.11.0-1
has caused the Debian Bug report #1004869,
regarding python-xarray: autopkgtest regression on i386
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.)
--
1004869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.21.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
python-xarray's autopkgtests are failing on the i386 architecture [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/p/python-xarray/unstable/i386/
=== FAILURES ===
___ test_interpolate_chunk_advanced[linear]
method = 'linear'
@requires_scipy
@requires_dask
@pytest.mark.parametrize("method", ["linear", "nearest"])
@pytest.mark.filterwarnings("ignore:Increasing number of chunks")
def test_interpolate_chunk_advanced(method):
"""Interpolate nd array with an nd indexer sharing coordinates."""
# Create original array
x = np.linspace(-1, 1, 5)
y = np.linspace(-1, 1, 7)
z = np.linspace(-1, 1, 11)
t = np.linspace(0, 1, 13)
q = np.linspace(0, 1, 17)
da = xr.DataArray(
data=np.sin(x[:, np.newaxis, np.newaxis, np.newaxis, np.newaxis])
* np.cos(y[:, np.newaxis, np.newaxis, np.newaxis])
* np.exp(z[:, np.newaxis, np.newaxis])
* t[:, np.newaxis]
+ q,
dims=("x", "y", "z", "t", "q"),
coords={"x": x, "y": y, "z": z, "t": t, "q": q, "label":
"dummy_attr"},
)
# Create indexer into `da` with shared coordinate
("full-twist" Möbius strip)
theta = np.linspace(0, 2 * np.pi, 5)
w = np.linspace(-0.25, 0.25, 7)
r = xr.DataArray(
data=1 + w[:, np.newaxis] * np.cos(theta),
coords=[("w", w), ("theta", theta)],
)
x = r * np.cos(theta)
y = r * np.sin(theta)
z = xr.DataArray(
data=w[:, np.newaxis] * np.sin(theta),
coords=[("w", w), ("theta", theta)],
)
kwargs = {"fill_value": None}
expected = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs, method=method)
da = da.chunk(2)
x = x.chunk(1)
z = z.chunk(3)
actual = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs, method=method)
> assert_identical(actual, expected)
E AssertionError: Left and right DataArray objects are not identical
E
E Differing values:
E L
E array([[[ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00],
E [ 1.239764e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-5.560517e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00]],
E
E [[ 3.603946e-01, 4.228946e-01, ..., 1.297895e+00,
1.360395e+00],
E [ 1.346533e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-5.109700e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 3.603946e-01, 4.228946e-01, ..., 1.297895e+00,
1.360395e+00]],
E
E ...,
E
E [[ 4.810764e-01, 5.435764e-01, ..., 1.418576e+00,
1.481076e+00],
E [ 1.878775e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-3.662163e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 4.810764e-01, 5.435764e-01, ..., 1.418576e+00,
1.481076e+00]],
E
E [[ 5.112469e-01, 5.737469e-01, ..., 1.448747e+00,
1.511247e+00],
E [ 2.044535e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-3.371783e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 5.112469e-01, 5.737469e-01, ..., 1.448747e+00,
1.511247e+00]]])
E R
E array([[[ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00],
E [ 1.239764e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E
Bug#1056334: marked as pending in node-ast-types
Control: tag -1 pending Hello, Bug #1056334 in node-ast-types reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-ast-types/-/commit/732f7a8b52206371c2840c750a6d565a9371f887 Clean debian/tests/pkg-js/files Closes: #1056334 (this message was generated automatically) -- Greetings https://bugs.debian.org/1056334
Processed: Bug#1056334 marked as pending in node-ast-types
Processing control commands: > tag -1 pending Bug #1056334 [src:node-ast-types] node-ast-types: autopkgtest failure Added tag(s) pending. -- 1056334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055144: marked as done (nvidia-open-gpu-kernel-modules: CVE-2023-31022)
Your message dated Wed, 22 Nov 2023 00:49:20 + with message-id and subject line Bug#1055144: fixed in nvidia-open-gpu-kernel-modules 525.147.05-1 has caused the Debian Bug report #1055144, regarding nvidia-open-gpu-kernel-modules: CVE-2023-31022 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.) -- 1055144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: normal Tags: security X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-31022 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-31022 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-31022 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-31022 Control: tag -5 + wontfix Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-31022 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-31022 Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-31022 Control: found -8 515.48.07-1 Control: found -8 525.60.13-1 Control: found -8 535.54.03-1 Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-31022 Control: found -9 520.56.06-1 Control: found -9 525.85.12-1 Control: found -9 530.30.02-1 Control: found -9 535.43.02-1 Control: found -9 545.23.06-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: found -1 535.43.02-1 Control: found -1 545.23.06-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5491 CVE-2023-31022 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a NULL-pointer dereference may lead to denial of service. Linux Driver Branch CVE IDs Addressed R545, R535, R525, R470 CVE-2023-31022 Driver Branch Affected Driver VersionsUpdated Driver Version R545All driver versions prior to 545.29.02 545.29.02 R535All driver versions prior to 535.129.03 535.129.03 R525All driver versions prior to 525.147.05 525.147.05 R470All driver versions prior to 470.223.02 470.223.02 Andreas --- End Message --- --- Begin Message --- Source: nvidia-open-gpu-kernel-modules Source-Version: 525.147.05-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-open-gpu-kernel-modules, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-open-gpu-kernel-modules 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, 22 Nov 2023 01:17:56 +0100 Source: nvidia-open-gpu-kernel-modules Architecture: source Version: 525.147.05-1 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1055144 Changes: nvidia-open-gpu-kernel-modules (525.147.05-1) unstable; urgency=medium . * New upstream production branch release 525.147.05 (2023-10-31). * Fixed CVE-2023-31022. (Closes:
Bug#1050854: xarray test failure on amd64
I have added what should be fixes for #1053700 and #1044869, but they are currently untested as salsa-ci only runs the autopkgtest on amd64. #1050854 appears to have been fixed (or at least xfailed - it passed on salsa-ci but they say it's flaky) by upstream.
Bug#1056340: 6.4+20231118-1 screws many terminal utilities
On Tue, Nov 21, 2023 at 04:02:20PM -0500, Thomas Dickey wrote: > On Tue, Nov 21, 2023 at 05:33:54PM +0100, Sven Joachim wrote: > > Control: reassign -1 libncursesw6 6.4+20231118-1 > > Control: severity -1 grave > > > > On 2023-11-21 12:32 +0100, Gianluigi Tiesi wrote: > > > > > Source: ncurses > > > Severity: important > > > X-Debbugs-Cc: sher...@gmail.com > > > > > > I've updated to 6.4+20231118-1 version of ncurses but many > > > utils are screwed, tested in konsole and linux console (vt) > > > > > > htop shows a lot of ^@ characters > > thanks - I can reproduce this (will fix) I see - I misread the older logic for waddnstr in last week's fix, and will amend that more/less as suggested. -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1056340: 6.4+20231118-1 screws many terminal utilities
On Tue, Nov 21, 2023 at 05:33:54PM +0100, Sven Joachim wrote: > Control: reassign -1 libncursesw6 6.4+20231118-1 > Control: severity -1 grave > > On 2023-11-21 12:32 +0100, Gianluigi Tiesi wrote: > > > Source: ncurses > > Severity: important > > X-Debbugs-Cc: sher...@gmail.com > > > > I've updated to 6.4+20231118-1 version of ncurses but many > > utils are screwed, tested in konsole and linux console (vt) > > > > htop shows a lot of ^@ characters thanks - I can reproduce this (will fix) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1056345: marked as done (firefox: 119.0.1 missing build on amd64)
Your message dated Wed, 22 Nov 2023 05:02:27 +0900 with message-id <20231121200227.vhrlawg7jhirl...@glandium.org> and subject line Re: Bug#1056345: firefox: 119.0.1 missing build on amd64 has caused the Debian Bug report #1056345, regarding firefox: 119.0.1 missing build on 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.) -- 1056345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox Version: 119.0.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Firefox 119.0.1-1 is missing build on amd64. Best, Amr -- Package-specific info: -- Addons package information -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) 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 firefox depends on: ii debianutils 5.14 ii fontconfig 2.14.2-6 ii libasound2 1.2.10-1 ii libatk1.0-0 2.50.0-1 ii libc62.37-12 ii libcairo-gobject21.18.0-1 ii libcairo21.18.0-1 ii libdbus-1-3 1.14.10-3 ii libdbus-glib-1-2 0.112-3 ii libevent-2.1-7 2.1.12-stable-8 ii libffi8 3.4.4-1 ii libfontconfig1 2.14.2-6 ii libfreetype6 2.13.2+dfsg-1 ii libgcc-s113.2.0-5 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-0 2.78.1-4 ii libgtk-3-0 3.24.38-6 ii libnspr4 2:4.35-1.1 ii libnss3 2:3.94-1 ii libpango-1.0-0 1.51.0+ds-3 ii libstdc++6 13.2.0-5 ii libvpx8 1.13.1-2 ii libx11-6 2:1.8.7-1 ii libx11-xcb1 2:1.8.7-1 ii libxcb-shm0 1.15-1 ii libxcb1 1.15-1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.6-1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxrandr2 2:1.5.2-2+b1 ii libxtst6 2:1.2.3-1.1 ii procps 2:4.0.4-2 ii zlib1g 1:1.2.13.dfsg-3 Versions of packages firefox recommends: ii libavcodec60 7:6.1-3 Versions of packages firefox suggests: ii fonts-lmodern 2.005-1 pn fonts-stix | otf-stix ii libcanberra0 0.30-11 ii libgssapi-krb5-2 1.20.1-5 pn pulseaudio -- no debconf information --- End Message --- --- Begin Message --- On Tue, Nov 21, 2023 at 01:17:55PM +0100, Amr Ibrahim wrote: > Package: firefox > Version: 119.0.1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) The failure looks like something a giveback will fix. Mike--- End Message ---
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Graham, Am Tue, Nov 21, 2023 at 06:20:01PM -0100 schrieb Graham Inggs: > I think this means at least r-cran-seuratobject (not r-cran-seurat > itself) is also in need of your fix [1], if only to silence that > warning. Would you please take care of that? Done. Thanks for checking Andreas. -- http://fam-tille.de
Bug#1056367: src:libgom: fails to migrate to testing for too long: FTBFS on i386 and mips64el
Source: libgom Version: 0.4-1 Severity: serious Control: close -1 0.4-1.1 X-Debbugs-CC: b...@debian.org Tags: sid trixie ftbfs 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:libgom has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable failed to build on i386 and mips64el. 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=libgom OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:libgom: fails to migrate to testing for too long: FTBFS on i386 and mips64el
Processing control commands: > close -1 0.4-1.1 Bug #1056367 [src:libgom] src:libgom: fails to migrate to testing for too long: FTBFS on i386 and mips64el Marked as fixed in versions libgom/0.4-1.1. Bug #1056367 [src:libgom] src:libgom: fails to migrate to testing for too long: FTBFS on i386 and mips64el Marked Bug as done -- 1056367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Andreas On Mon, 20 Nov 2023 at 13:07, Andreas Tille wrote: > Since I have no idea what the failures in r-cran-seurat test > log[6] mean I would prefer to wait until we can upload the latest > version. > > > [6] https://ci.debian.net/packages/r/r-cran-seurat/unstable/amd64/40043272/ I had a look at that log and I saw the following: Attaching SeuratObject ‘SeuratObject’ was built with package ‘Matrix’ 1.6.1.1 but the current version is 1.6.3; it is recomended that you reinstall ‘SeuratObject’ as the ABI for ‘Matrix’ may have changed I think this means at least r-cran-seuratobject (not r-cran-seurat itself) is also in need of your fix [1], if only to silence that warning. Would you please take care of that? Regards Graham [1] https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/commit/92579f72c2db4d51a45cf317f580d790da158f4f
Processed: python3-wikitrans: [wikimarkup.py] 'str' object has no attribute 'decode'
Processing control commands: > affects -1 dico-module-mediawiki Bug #1056360 [python3-wikitrans] python3-wikitrans: [wikimarkup.py] 'str' object has no attribute 'decode' Added indication that 1056360 affects dico-module-mediawiki -- 1056360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056360: python3-wikitrans: [wikimarkup.py] 'str' object has no attribute 'decode'
Package: python3-wikitrans
Version: 1.3-2
Severity: grave
Control: affects -1 dico-module-mediawiki
Usertags: pca.it-communication
Hi there,
after the dicod's `load python`[1] and `M4 quoting`[2], querying the
WikiMedia databases gives no match and the following errors in `dicod`:
```
root@harlock:~# /usr/bin/dicod --stderr -f
dicod: Info: dicod (GNU dico) 2.11 started
dicod: Info: Client info: "GNU dico 2.11"
dicod: Info: Client info: "GNU dico 2.11"
dicod: Debug: 57843 exited successfully
dicod: Info: Client info: "GNU dico 2.11"
dicod: Error: Traceback (most recent call last):
dicod: Error: File "/usr/share/dico/python/mediawiki.py", line 98, in
define_word
dicod: Error: wikiparser = TextWiktionaryMarkup (text=data)
dicod: Error:
dicod: Error: File "/usr/lib/python3/dist-packages/wikitrans/wiki2text.py",
line 278, in __init__
dicod: Error: super(TextWikiMarkup, self).__init__(*args, **keywords)
dicod: Error: File "/usr/lib/python3/dist-packages/wikitrans/wikimarkup.py",
line 1028, in __init__
dicod: Error: self.text = keywords[kw].decode('utf-8').split("\n")
dicod: Error: ^^^
dicod: Error: AttributeError: 'str' object has no attribute 'decode'. Did you
mean: 'encode'?
dicod: Debug: 57846 exited successfully
dicod: Debug: 57847 exited successfully
^Cdicod: Info: dicod (GNU dico) 2.11 terminating
root@harlock:~#
```
[1]
[2]
I am not a Python expert, the problem obviously disappears (and the
query succeeds) if I remove the conditional case at line 1027, which
seems bad to me since AFAIK only from Python3 `str` contains by
default UTF-8/Unicode characters[3] (and anyway user input could not
be in UTF-8):
```
elif kw == 'text':
if sys.version_info[0] > 2:
self.text = keywords[kw].decode('utf-8').split("\n")
else:
self.text = keywords[kw].split("\n")
```
[3]
Thx, bye,
Gismo / Luca
-- System Information:
Debian Release: 12.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500,
'stable'), (500, 'oldstable'), (100, 'bookworm-fasttrack'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-0.deb12.1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-wikitrans depends on:
ii python3 3.11.2-1+b1
python3-wikitrans recommends no packages.
python3-wikitrans suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
Processed: Re: Bug#1056340: 6.4+20231118-1 screws many terminal utilities
Processing control commands: > reassign -1 libncursesw6 6.4+20231118-1 Bug #1056340 [src:ncurses] 6.4+20231118-1 screws many terminal utilities Bug reassigned from package 'src:ncurses' to 'libncursesw6'. Ignoring request to alter found versions of bug #1056340 to the same values previously set Ignoring request to alter fixed versions of bug #1056340 to the same values previously set Bug #1056340 [libncursesw6] 6.4+20231118-1 screws many terminal utilities Marked as found in versions ncurses/6.4+20231118-1. > severity -1 grave Bug #1056340 [libncursesw6] 6.4+20231118-1 screws many terminal utilities Severity set to 'grave' from 'important' -- 1056340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Processed (with 1 error): Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)
Processing commands for cont...@bugs.debian.org: > severity 1055750 serious Bug #1055750 [plplot] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Severity set to 'serious' from 'normal' > merge 1055750 1055228 Bug #1055750 [plplot] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Bug #1055750 [plplot] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Added tag(s) sid, trixie, confirmed, and help. Bug #1055228 [plplot] plplot: FTBFS on armhf (test segfault) Merged 1055228 1055750 > End of message, stopping processing here. Please contact me if you need assistance. -- 1055228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055228 1055750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055228: Processed (with 1 error): Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)
severity 1055750 serious merge 1055750 1055228
Processed (with 1 error): Re: Bug#1013285: needrestart: Failed to check for processor microcode upgrades.
Processing control commands:
> reopen -1
Bug #1013285 {Done: Patrick Matthäi } [needrestart]
needrestart: Failed to check for processor microcode upgrades.
Bug #1032979 {Done: Patrick Matthäi } [needrestart]
needrestart: Failed to check for processor microcode upgrades.
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions needrestart/3.6-6.
No longer marked as fixed in versions needrestart/3.6-6.
> subscribe -1
Unknown command or malformed arguments to command.
--
1013285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013285
1032979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1013285: needrestart: Failed to check for processor microcode upgrades.
Control: reopen -1 Control: subscribe -1 On 2023-11-15 15:46:24, Antoine Beaupré wrote: > Control: tags -1 +patch > > On 2023-11-15 14:54:26, Antoine Beaupré wrote: >> On 2022-06-20 13:54:38, Nick Lewycky wrote: >>> Package: needrestart >>> Version: 3.6-1 >>> Severity: normal >>> >>> `sudo needrestart -w` always prints "Failed to check for processor >>> microcode upgrades." on my AMD Ryzen 9 3900X 12-Core Processor. >> >> [...] >> >> There's now a PR for this upstream: >> >> https://github.com/liske/needrestart/pull/285 >> >> People suffering from this issue are encouraged to test this and report >> back upstream (or here, if you can't upstream). > > I tested it and it doesn't work. It only *seemed* to work because the > author tested with -v, which *does* work around the issue. > > I found the issue, and sent this PR upstream to fix it: > > https://github.com/liske/needrestart/pull/288 > > Patch attached, people are again encouraged to test and report back. > > I also attach upstream commit v3.6-9-ge85bfe3 which also seem necessary > to fix firmware checks on my end... It doesn't *quite* fix it just yet. For platforms where the ucode is *not* provided (e.g. in my case it's the pcengines APU that don't have firmware upgrades), this *still* yields a UNKNOWN warning. After a brief discussion in the issue tracker, I decided to submit *another* PR as such: https://github.com/liske/needrestart/pull/290 ... and I think we should ship this in Debian as well. I also think we should make a stable update for this. This affects a bunch of machines on our end and we need this fixed in bookworm. So I'll file a bug with the release team and prepare a stable update. Patrick: objections? A. -- All governments are run by liars and nothing they say should be believed. - I. F. Stone
Bug#1055228: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)
Control: reassign -1 plplot Control: forwarded 1055228 https://sourceforge.net/p/plplot/bugs/206/ Control: merge -1 1055228 * Emanuele Rocca [2023-11-16 09:30]: To be honest I think it's safe to close 1055750 (gfortran) and mark 1055228 (plplot) as forwarded upstream though, I don't think we have any reasons to believe the compiler is at fault really. Thanks for the suggestion, Emanuele. I am hereby merging both bugs, which are now both assigned to plplot. Best, Rafael Laboissière
Processed (with 1 error): Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)
Processing control commands: > reassign -1 plplot Bug #1055750 [gfortran] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Bug reassigned from package 'gfortran' to 'plplot'. No longer marked as found in versions 13.2.0-1. Ignoring request to alter fixed versions of bug #1055750 to the same values previously set > forwarded 1055228 https://sourceforge.net/p/plplot/bugs/206/ Bug #1055228 [plplot] plplot: FTBFS on armhf (test segfault) Ignoring request to change the forwarded-to-address of bug#1055228 to the same value > merge -1 1055228 Bug #1055750 [plplot] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Unable to merge bugs because: severity of #1055228 is 'serious' not 'normal' Failed to merge 1055750: Did not alter merged bugs. -- 1055228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055228 1055750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)
Processing control commands: > reassign -1 plplot Bug #1055228 [src:plplot] plplot: FTBFS on armhf (test segfault) Bug reassigned from package 'src:plplot' to 'plplot'. No longer marked as found in versions plplot/5.15.0+dfsg2-6. Ignoring request to alter fixed versions of bug #1055228 to the same values previously set > forwarded 1055228 https://sourceforge.net/p/plplot/bugs/206/ Bug #1055228 [plplot] plplot: FTBFS on armhf (test segfault) Set Bug forwarded-to-address to 'https://sourceforge.net/p/plplot/bugs/206/'. > merge -1 1055228 Bug #1055228 [plplot] plplot: FTBFS on armhf (test segfault) Merged 1055228 -- 1055228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055580: marked as done (dlt-daemon: Runs daemon as user nobody with owned files on fsys)
Your message dated Tue, 21 Nov 2023 16:04:09 + with message-id and subject line Bug#1055580: fixed in dlt-daemon 2.18.10-8 has caused the Debian Bug report #1055580, regarding dlt-daemon: Runs daemon as user nobody with owned files on fsys 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.) -- 1055580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dlt-daemon Version: 2.18.0-1 Severity: serious Tags: security Hi! This daemon runs as user nobody, while creating multiple files on the filesystem owned by the same user, which are used as part of its security protection. This is a security issue, given that other daemons on the system might be running as the same user, and worse when dlt-daemon is writing and parsing files from hardcoded paths under /tmp. From base-passwd/users-and-groups.txt.gz: ,--- nobody, nogroup Daemons that need not own any files sometimes run as user nobody and group nogroup, although using a dedicated user is far preferable. Thus, no files on a system should be owned by this user or group. (Technically speaking, it does no harm for a file to be owned by group nogroup as long as the ownership confers no additional privileges, that is if the group and other permission bits are equal. However, this is sloppy practice and should be avoided.) If root-squashing is in use over NFS, root access from the client is performed as user nobody on the server. `--- If you are going to fix this by using a dedicated user/group, please make sure to namespace them with «_» to distinguish them as system users and avoid unnecessary collisions with non-system, users. (Such as _dlt or similar.) [ The version I used is the earliest I found with the same issue from the tracker.d.o page, earlier version might be affected too, dunno. ] Thanks, Guillem --- End Message --- --- Begin Message --- Source: dlt-daemon Source-Version: 2.18.10-8 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of dlt-daemon, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated dlt-daemon 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: Tue, 21 Nov 2023 13:18:22 +0100 Source: dlt-daemon Built-For-Profiles: noudeb Architecture: source Version: 2.18.10-8 Distribution: unstable Urgency: medium Maintainer: Aigars Mahinovs Changed-By: Gianfranco Costamagna Closes: 1055580 Changes: dlt-daemon (2.18.10-8) unstable; urgency=medium . * Make sure dlt runs as _dlt user, not as nobody (Closes: #1055580) * Start using upstream service files. * Enable systemd watchdog Checksums-Sha1: 5e63ba1ad2dbfb50f3ab97b5feba9a362cda2fbe 2147 dlt-daemon_2.18.10-8.dsc 7a806ae68a1bf306bbdcefa8db05b78ef396528c 7372 dlt-daemon_2.18.10-8.debian.tar.xz 330087dc0c1ce466f982e0d2f980fb81039d54fd 9817 dlt-daemon_2.18.10-8_source.buildinfo Checksums-Sha256: 6a13d7159dd5dcd4f32d1be0c47e726b7b6bb9ca2d061a28d077aa61a4ce5484 2147 dlt-daemon_2.18.10-8.dsc 52cdd1c010440d8304816b172280a0f0eaaf07b0c3935583713b98f306a3bee9 7372 dlt-daemon_2.18.10-8.debian.tar.xz df0fccaeb146eb000709d2fdd058de502f30e3721c64543b5c926b366103a9ae 9817 dlt-daemon_2.18.10-8_source.buildinfo Files: 4f44878f979f51a34d9164b55f8a760f 2147 libs optional dlt-daemon_2.18.10-8.dsc 46df7f263861bce808ad535da7343557 7372 libs optional dlt-daemon_2.18.10-8.debian.tar.xz 8cbf0c75a80cc4f1cea30b817234c072 9817 libs optional dlt-daemon_2.18.10-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmVc0fUACgkQ808JdE6f Xdm0ZQ//eg8K8YWQhm1IgvGocbmzOuPMR+205nEQsmZTfT8lukJrLRUeTk33bsLr vRgoFD3H9cVjtgJgCrWxkgpNVnGYnOmNbKlQQWo9pO77RHye6Z8DcCGEIfPP2okG TZpdULfNOVfmwfvc0KhFsZT8mKgtPl3yUn8NZsCy1apRNP+73EPExOaAzO7tZcos LXoBrQkL3QWFwtkblA2C9kIGkkI1bD8Wnm1wninqDZs7gxoBq1eIo379fVc8Vtdf
Bug#1056354: python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0
Package: python3-hinawa-utils Version: 0.3.0-3 Severity: serious src:libhinawa now builds gir1.2-hinawa-4.0 instead of gir1.2-hinawa-3.0
Bug#1053787: qbrz calls give internal error
Just for info. I uninstalled qbrz package, I downloaded qbrz 0.4.2, I builded it and I put builded qbrz plugin directory in /usr/lib/python3/dist-packages/breezy/plugins and now it works.
Processed: Re: ldc: diff for NMU version 1:1.35.0-1.1
Processing control commands: > severity -1 serious Bug #1055515 [ldc] ldc: diff for NMU version 1:1.35.0-1.1 Severity set to 'serious' from 'normal' -- 1055515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056348: FTBFS: tests fail in clean environment
Source: libssh2
Version: 1.9.0-2
Severity: serious
Tags: ftbfs patch
Hi!
Building libssh2 using debuild in a clean local chroot, I get test
failures and even a core dump!
...
PASS: mansyntax.sh
PASS: test_simple
FAIL: test_sshd.test 1 - sshd-test_ssh2
FAIL: test_sshd.test 2 - sshd-test_auth_pubkey_ok_ed25519
=
libssh2 -: tests/test-suite.log
=
# TOTAL: 4
# PASS: 2
# SKIP: 0
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: test_sshd
===
Fingerprint: 12 FD AD 1E 3B 31 B1 0B AB B0 0F 2A 8D 1B 9A 62 C3 26 BD 2F
Authentication methods: publickey,password,keyboard-interactive
Authentication by public key failed!
all done
./test_sshd.test: line 131: 2476672 Segmentation fault (core dumped)
"${test}"
# sshd executable: '/usr/sbin/sshd' (OpenSSH_9.4, OpenSSL 3.0.12 24 Oct 2023)
# ssh executable: '/usr/bin/ssh' (OpenSSH_9.4p1 Debian-1, OpenSSL 3.0.12 24 Oct
2023)
1..2
not ok 1 - sshd-test_ssh2
FAIL: test_sshd.test 1 - sshd-test_ssh2
not ok 2 - sshd-test_auth_pubkey_ok_ed25519
FAIL: test_sshd.test 2 - sshd-test_auth_pubkey_ok_ed25519
Testsuite summary for libssh2 -
# TOTAL: 4
# PASS: 2
# SKIP: 0
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
These are both down to environment: the test code assumes that "USER"
is a valid environment varliable, which is not necessarily
true. Here's a patch which fixes this for these two tests, and fails
cleanly with diagnostics if there's a problem.
-- System Information:
Debian Release: 11.8
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'oldoldstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-26-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/tests/session_fixture.c b/tests/session_fixture.c
index 3bb9da2..4671117 100644
--- a/tests/session_fixture.c
+++ b/tests/session_fixture.c
@@ -430,11 +430,18 @@ int test_auth_pubkey(LIBSSH2_SESSION *session, int flags,
/* Ignore our hard-wired Dockerfile user when not running under Docker */
if(!openssh_fixture_have_docker() && strcmp(username, "libssh2") == 0) {
-username = getenv("USER");
+if(getenv("USER"))
+username = getenv("USER");
+else if(getenv("LOGNAME"))
+username = getenv("LOGNAME");
#ifdef WIN32
-if(!username)
+else if(getenv("USERNAME"))
username = getenv("USERNAME");
#endif
+else {
+fprintf(stderr, "Failed to find a username from env\n");
+return 1;
+}
}
userauth_list = libssh2_userauth_list(session, username,
diff --git a/tests/test_ssh2.c b/tests/test_ssh2.c
index a637cdc..6e28598 100644
--- a/tests/test_ssh2.c
+++ b/tests/test_ssh2.c
@@ -63,10 +63,16 @@ int main(int argc, char *argv[])
if(getenv("USER"))
username = getenv("USER");
+else if(getenv("LOGNAME"))
+username = getenv("LOGNAME");
#ifdef WIN32
else if(getenv("USERNAME"))
username = getenv("USERNAME");
#endif
+else {
+fprintf(stderr, "Failed to find a username from env\n");
+return 1;
+}
if(getenv("PRIVKEY"))
privkey = getenv("PRIVKEY");
Bug#1056062: coq: FTBFS in sid (dune update?)
Hi, Le jeudi 16 novembre 2023 à 16:45 +0100, Gianfranco Costamagna a écrit : > Source: coq > Version: 8.17.0+dfsg-1 > Severity: serious > > Hello, > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/coq.html > > As said here, there is a build failure due to probably new dune or > something similar. > > > I can reproduce locally, but not always, looks some concurrency issue > but also running dune with -j1 doesn't fix the issue. I couldn't reproduce your failure even after several compilation tries, neither with the current 8.17.0+dfsg-1 nor with the next 8.18.0+dfsg-1. > $ (cd _build/default && /usr/bin/bash -e -u -o pipefail -c > 'doc/stdlib/make-library-index doc/stdlib/index-list.html > doc/stdlib/hidden-files') > Building file index-list.prehtml... Error: none of doc/stdlib/index- > list.html and doc/stdlib/hidden-files mention > theories/Arith/Between.v > grep: tmp: No such file or directory > grep: tmp: No such file or directory > > This is probably the culprit of the issue, but I don't really > understand why this is not found > I checked doc/stdlib/index-list.html.template in both 8.17.0+dfsg-1 and 8.18.0+dfsg-1, and they *do* mention theories/Arith/Between.v... how could that line disappear? Is it always theories/Arith/Between.v or sometimes another file? The compilation of the .html.template to .html might fail silently for you and then you see a later breakage? > and also why running it manually works > bash -e -u -o pipefail -c 'doc/stdlib/make-library-index > doc/stdlib/index-list.html doc/stdlib/hidden-files' > Building file index-list.prehtml... > Done > > Sorry for not providing a patch, but I really don't have much > knowledge about this build system, and despite my efforts I'm still > failing The fact that the only error message doesn't make sense and the problem isn't guaranteed to happen is puzzling. I'm using sbuild to compile my sources, with an unstable schroot I keep up to date, and it now uses ocaml-dune 3.11.1-1 to compile, just like in your failure log :-/ Thanks, JP
Bug#1056345: firefox: 119.0.1 missing build on amd64
Package: firefox Version: 119.0.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Firefox 119.0.1-1 is missing build on amd64. Best, Amr -- Package-specific info: -- Addons package information -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) 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 firefox depends on: ii debianutils 5.14 ii fontconfig 2.14.2-6 ii libasound2 1.2.10-1 ii libatk1.0-0 2.50.0-1 ii libc62.37-12 ii libcairo-gobject21.18.0-1 ii libcairo21.18.0-1 ii libdbus-1-3 1.14.10-3 ii libdbus-glib-1-2 0.112-3 ii libevent-2.1-7 2.1.12-stable-8 ii libffi8 3.4.4-1 ii libfontconfig1 2.14.2-6 ii libfreetype6 2.13.2+dfsg-1 ii libgcc-s113.2.0-5 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-0 2.78.1-4 ii libgtk-3-0 3.24.38-6 ii libnspr4 2:4.35-1.1 ii libnss3 2:3.94-1 ii libpango-1.0-0 1.51.0+ds-3 ii libstdc++6 13.2.0-5 ii libvpx8 1.13.1-2 ii libx11-6 2:1.8.7-1 ii libx11-xcb1 2:1.8.7-1 ii libxcb-shm0 1.15-1 ii libxcb1 1.15-1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.6-1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxrandr2 2:1.5.2-2+b1 ii libxtst6 2:1.2.3-1.1 ii procps 2:4.0.4-2 ii zlib1g 1:1.2.13.dfsg-3 Versions of packages firefox recommends: ii libavcodec60 7:6.1-3 Versions of packages firefox suggests: ii fonts-lmodern 2.005-1 pn fonts-stix | otf-stix ii libcanberra0 0.30-11 ii libgssapi-krb5-2 1.20.1-5 pn pulseaudio -- no debconf information
Bug#1055099: rust-async-task: Failing autopkgtests
On 21/11/2023 11:41, Jonas Smedegaard wrote: Quoting Peter Green (2023-11-21 09:16:21) Tags 1055099 +patch thanks The autopkgtests for rust-async-task began failing after the upgrade to from 4.4.1-1 to 4.5.0-1. This prevents its migration to Testing. I have prepared a patch which adds a feature guard to the example in question and hence fixes the autopkgtest. A debdiff is attatched, if I get no response I intend to NMU this soon. Thanks. Seems the intended attachment is missing, however. Sorry, attatched now. diff -Nru rust-async-task-4.5.0/debian/changelog rust-async-task-4.5.0/debian/changelog --- rust-async-task-4.5.0/debian/changelog 2023-10-19 12:46:47.0 + +++ rust-async-task-4.5.0/debian/changelog 2023-11-21 08:05:37.0 + @@ -1,3 +1,10 @@ +rust-async-task (4.5.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch 1001 to add feature requirement to example (Closes: #1055099) + + -- Peter Micheal Green Tue, 21 Nov 2023 08:05:37 + + rust-async-task (4.5.0-1) unstable; urgency=medium [ upstream ] diff -Nru rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch --- rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch 1970-01-01 00:00:00.0 + +++ rust-async-task-4.5.0/debian/patches/1001_example_feature_requirements.patch 2023-11-21 08:05:31.0 + @@ -0,0 +1,16 @@ +Description: add feature requirement for example + Avoids build failure in autopkgtest. +Author: Peter Micahel Green +Forwarded: no +Last-Update: 2023-11-21 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +Index: rust-async-task-4.5.0/examples/spawn-local.rs +=== +--- rust-async-task-4.5.0.orig/examples/spawn-local.rs rust-async-task-4.5.0/examples/spawn-local.rs +@@ -1,3 +1,4 @@ ++#![cfg(feature = "std")] + //! A simple single-threaded executor that can spawn non-`Send` futures. + + use std::cell::Cell; diff -Nru rust-async-task-4.5.0/debian/patches/series rust-async-task-4.5.0/debian/patches/series --- rust-async-task-4.5.0/debian/patches/series 2023-10-10 17:25:47.0 + +++ rust-async-task-4.5.0/debian/patches/series 2023-11-21 08:05:37.0 + @@ -1 +1,2 @@ +1001_example_feature_requirements.patch 2001_flaky-test.patch
Bug#1055099: rust-async-task: Failing autopkgtests
Quoting Peter Green (2023-11-21 09:16:21) > Tags 1055099 +patch > thanks > > > The autopkgtests for rust-async-task began failing after the upgrade > > to from 4.4.1-1 to 4.5.0-1. This prevents its migration to Testing. > > I have prepared a patch which adds a feature guard to the example in > question and hence fixes the autopkgtest. A debdiff is attatched, if > I get no response I intend to NMU this soon. Thanks. Seems the intended attachment is missing, however. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1055143: marked as done (nvidia-graphics-drivers-tesla: CVE-2023-31022)
Your message dated Tue, 21 Nov 2023 11:05:27 + with message-id and subject line Bug#1055143: fixed in nvidia-graphics-drivers-tesla 525.147.05-1 has caused the Debian Bug report #1055143, regarding nvidia-graphics-drivers-tesla: CVE-2023-31022 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.) -- 1055143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: normal Tags: security X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-31022 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-31022 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-31022 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-31022 Control: tag -5 + wontfix Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-31022 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-31022 Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-31022 Control: found -8 515.48.07-1 Control: found -8 525.60.13-1 Control: found -8 535.54.03-1 Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-31022 Control: found -9 520.56.06-1 Control: found -9 525.85.12-1 Control: found -9 530.30.02-1 Control: found -9 535.43.02-1 Control: found -9 545.23.06-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: found -1 535.43.02-1 Control: found -1 545.23.06-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5491 CVE-2023-31022 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a NULL-pointer dereference may lead to denial of service. Linux Driver Branch CVE IDs Addressed R545, R535, R525, R470 CVE-2023-31022 Driver Branch Affected Driver VersionsUpdated Driver Version R545All driver versions prior to 545.29.02 545.29.02 R535All driver versions prior to 535.129.03 535.129.03 R525All driver versions prior to 525.147.05 525.147.05 R470All driver versions prior to 470.223.02 470.223.02 Andreas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla Source-Version: 525.147.05-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla 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: Tue, 21 Nov 2023 11:06:32 +0100 Source: nvidia-graphics-drivers-tesla Architecture: source Version: 525.147.05-1 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1055143 Changes: nvidia-graphics-drivers-tesla (525.147.05-1) unstable; urgency=medium . * New upstream Tesla release 525.147.05 (2023-10-31). * Fixed CVE-2023-31022. (Closes: #1055143)
Processed: Re: [Pkg-javascript-devel] Bug#1056334: node-ast-types: autopkgtest failure
Processing control commands: > tags -1 + moreinfo Bug #1056334 [src:node-ast-types] node-ast-types: autopkgtest failure Added tag(s) moreinfo. -- 1056334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056334: [Pkg-javascript-devel] Bug#1056334: node-ast-types: autopkgtest failure
Control: tags -1 + moreinfo On 11/21/23 12:28, Gianfranco Costamagna wrote: Source: node-ast-types Version: 0.16.1-2 Severity: serious Hello, according to ci, the package autopkgtests looks failing. https://ci.debian.net/packages/n/node-ast-types/unstable/amd64/39617621/ 66s autopkgtest [20:34:26]: test pkg-js-autopkgtest: [--- 66s # Using ./package.(json|yaml) 66s # Node module name is ast-types 66s # Build files found: tsconfig.json 66s # Test files found: 66s # Found debian/tests/pkg-js/files, let's use it 66s # Files/dir to be installed from source: src 66s test 66s tsconfig* 66s ls: cannot access 'test': No such file or directory This is strange: it seems that the test isn't launched from source directory (which has a test subdir) 66s # Copy debian/tests/pkg-js content 66s 'debian/tests/pkg-js' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js' 66s 'debian/tests/pkg-js/test' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js/test' 66s 'debian/tests/pkg-js/files' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js/files' 66s Found debian/tests/test_modules 66s # let's copy it 66s Found debian/nodejs/extlinks 67s @babel/parser linked into node_modules 67s @babel/types linked into node_modules 68s tslib linked into node_modules 68s @types/esprima linked into node_modules 69s @types/estree linked into node_modules 69s @types/glob linked into node_modules 70s @types/mocha linked into node_modules 70s # Searching module in /usr/lib/nodejs/ast-types 70s # Searching module in /usr/lib/*/nodejs/ast-types 70s # Searching module in /usr/share/nodejs/ast-types 70s # Found /usr/share/nodejs/ast-types 70s # Searching files to link in /usr/share/nodejs/ast-types 70s # Launch debian/tests/pkg-js/test with sh -ex 70s + test /tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp != 70s + rm -rf lib 70s + tsc 70s Version 4.8.4 70s tsc: The TypeScript Compiler - Version 4.8.4 70s 70s COMMON COMMANDS The "copy" part of pkg-js-autopkgtest failed, then "tsconfig.json" is missing then tsc display this.
Bug#1054856: marked as done (lua-posix: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 255)
Your message dated Tue, 21 Nov 2023 09:50:03 +
with message-id
and subject line Bug#1054856: fixed in lua-posix 36.2.1-1
has caused the Debian Bug report #1054856,
regarding lua-posix: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_build] Error 255
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.)
--
1054856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-posix
Version: 33.4.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 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_build
> make --no-print-directory -f
> /usr/share/dh-lua/make/dh-lua.Makefile.multiple build
>
> Making target build for debian/lua5.1.posix.dh-lua.conf
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './config.guess'
> libtoolize: copying file './config.sub'
> libtoolize: copying file './install-sh'
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> cd debian/.dh_lua-libtool && ./configure --build=x86_64-linux-gnu
> --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
> --disable-option-checking --disable-silent-rules
> --libdir=\${prefix}/lib/x86_64-linux-gnu
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
> --disable-maintainer-mode --disable-dependency-tracking CFLAGS= LDFLAGS=
> LDFLAGS_STATIC=
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking how to print strings... printf
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether the compiler supports GNU C... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to enable C11 features... none needed
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu
> format... func_convert_file_noop
> checking how to convert x86_64-pc-linux-gnu file names to toolchain format...
> func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for file... file
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for strip... strip
> checking for ranlib... ranlib
> checking for gawk... no
> checking for mawk... mawk
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking for a working dd... /bin/dd
> checking how to truncate binary pipes... /bin/dd bs=4096 count=1
> checking for mt... no
> checking if : is a manifest tool... no
> checking for stdio.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for strings.h... yes
> checking for sys/stat.h... yes
> checking for sys/types.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether
Processed: tagging 1056059, found 1056147 in 0.2.33-1, found 1056146 in 1.01-3, tagging 1043419, tagging 1054188
Processing commands for cont...@bugs.debian.org:
> tags 1056059 + sid trixie
Bug #1056059 [dracut] dracut: systemd 255: dracut fails to boot due to lack of
systemd-executor
Added tag(s) sid and trixie.
> found 1056147 0.2.33-1
Bug #1056147 [src:midge] midge possibly contains non-DFSG-free examples
The source 'midge' and version '0.2.33-1' do not appear to match any binary
packages
Marked as found in versions midge/0.2.33-1.
> found 1056146 1.01-3
Bug #1056146 [src:xsok] xsok possibly contains non-DFSG-free data files
The source 'xsok' and version '1.01-3' do not appear to match any binary
packages
Marked as found in versions xsok/1.01-3.
> tags 1043419 + sid trixie experimental
Bug #1043419 {Done: Lorenzo Puliti } [runit] runit:
ineffective trigger interest due to /usr-merge
Added tag(s) sid, trixie, and experimental.
> tags 1054188 + sid trixie
Bug #1054188 {Done: Antonio Terceiro } [src:debci] debci:
installs systemd unit twice once dh_installsystemd installs to /usr
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1043419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043419
1054188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054188
1056059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056059
1056146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056146
1056147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1056334: node-ast-types: autopkgtest failure
Source: node-ast-types Version: 0.16.1-2 Severity: serious Hello, according to ci, the package autopkgtests looks failing. https://ci.debian.net/packages/n/node-ast-types/unstable/amd64/39617621/ 66s autopkgtest [20:34:26]: test pkg-js-autopkgtest: [--- 66s # Using ./package.(json|yaml) 66s # Node module name is ast-types 66s # Build files found: tsconfig.json 66s # Test files found: 66s # Found debian/tests/pkg-js/files, let's use it 66s # Files/dir to be installed from source: src 66s test 66s tsconfig* 66s ls: cannot access 'test': No such file or directory 66s # Copy debian/tests/pkg-js content 66s 'debian/tests/pkg-js' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js' 66s 'debian/tests/pkg-js/test' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js/test' 66s 'debian/tests/pkg-js/files' -> '/tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp/smokeXkrxbl/debian/tests/pkg-js/files' 66s Found debian/tests/test_modules 66s # let's copy it 66s Found debian/nodejs/extlinks 67s @babel/parser linked into node_modules 67s @babel/types linked into node_modules 68s tslib linked into node_modules 68s @types/esprima linked into node_modules 69s @types/estree linked into node_modules 69s @types/glob linked into node_modules 70s @types/mocha linked into node_modules 70s # Searching module in /usr/lib/nodejs/ast-types 70s # Searching module in /usr/lib/*/nodejs/ast-types 70s # Searching module in /usr/share/nodejs/ast-types 70s # Found /usr/share/nodejs/ast-types 70s # Searching files to link in /usr/share/nodejs/ast-types 70s # Launch debian/tests/pkg-js/test with sh -ex 70s + test /tmp/autopkgtest-lxc.2rswz7np/downtmp/autopkgtest_tmp != 70s + rm -rf lib 70s + tsc 70s Version 4.8.4 70s tsc: The TypeScript Compiler - Version 4.8.4 70s 70s COMMON COMMANDS 70s 70s tsc 70s Compiles the current project (tsconfig.json in the working directory.) 70s 70s tsc app.ts util.ts 70s Ignoring tsconfig.json, compiles the specified files with default compiler options. 70s 70s tsc -b 70s Build a composite project in the working directory. 70s 70s tsc --init 70s Creates a tsconfig.json with the recommended settings in the working directory. 70s 70s tsc -p ./path/to/tsconfig.json 70s Compiles the TypeScript project located at the specified path. 70s 70s tsc --help --all 70s An expanded version of this information, showing all possible compiler options 70s 70s tsc --noEmit 70s tsc --target esnext 70s Compiles the current project, with additional settings. 70s 70s COMMAND LINE FLAGS 70s 70s --help, -h 70s Print this message. 70s 70s --watch, -w 70s Watch input files. 70s 70s --all 70s Show all compiler options. 70s 70s --version, -v 70s Print the compiler's version. 70s 70s --init 70s Initializes a TypeScript project and creates a tsconfig.json file. 70s 70s --project, -p 70s Compile the project given the path to its configuration file, or to a folder with a 'tsconfig.json'. 70s 70s --build, -b 70s Build one or more projects and their dependencies, if out of date 70s 70s --showConfig 70s Print the final configuration instead of building. 70s 70s COMMON COMPILER OPTIONS 70s 70s --pretty 70s Enable color and formatting in TypeScript's output to make compiler errors easier to read. 70s type: boolean 70s default: true 70s 70s --target, -t 70s Set the JavaScript language version for emitted JavaScript and include compatible library declarations. 70s one of: es3, es5, es6/es2015, es2016, es2017, es2018, es2019, es2020, es2021, es2022, esnext 70s default: es3 70s 70s --module, -m 70s Specify what module code is generated. 70s one of: none, commonjs, amd, umd, system, es6/es2015, es2020, es2022, esnext, node16, nodenext 70s default: undefined 70s 70s --lib 70s Specify a set of bundled library declaration files that describe the target runtime environment. 70s one or more: es5, es6/es2015, es7/es2016, es2017, es2018, es2019, es2020, es2021, es2022, esnext, dom, dom.iterable, webworker, webworker.importscripts, webworker.iterable, scripthost, es2015.core, es2015.collection, es2015.generator, es2015.iterable, es2015.promise, es2015.proxy, es2015.reflect, es2015.symbol, es2015.symbol.wellknown, es2016.array.include, es2017.object, es2017.sharedmemory, es2017.string, es2017.intl, es2017.typedarrays, es2018.asyncgenerator, es2018.asynciterable/esnext.asynciterable, es2018.intl, es2018.promise, es2018.regexp, es2019.array, es2019.object, es2019.string, es2019.symbol/esnext.symbol, es2020.bigint/esnext.bigint, es2020.date, es2020.promise, es2020.sharedmemory, es2020.string, es2020.symbol.wellknown, es2020.intl, es2020.number, es2021.promise/esnext.promise, es2021.string, es2021.weakref/esnext.weakref, es2021.intl, es2022.array/esnext.array, es2022.error, es2022.intl, es2022.object,
Processed: re: rust-async-task: Failing autopkgtests
Processing commands for cont...@bugs.debian.org: > Tags 1055099 +patch Bug #1055099 [src:rust-async-task] rust-async-task: Failing autopkgtests Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055099: rust-async-task: Failing autopkgtests
Tags 1055099 +patch thanks The autopkgtests for rust-async-task began failing after the upgrade to from 4.4.1-1 to 4.5.0-1. This prevents its migration to Testing. I have prepared a patch which adds a feature guard to the example in question and hence fixes the autopkgtest. A debdiff is attatched, if I get no response I intend to NMU this soon.
Bug#1052909: marked as done (auctex: FTBFS: ! LaTeX Error: File `etoolbox.sty' not found.)
Your message dated Tue, 21 Nov 2023 09:04:12 +0100 with message-id <52a72f40-2f92-4100-b3f9-6a971aee9...@web.de> and subject line Re: Bug#1052909: auctex: FTBFS: ! LaTeX Error: File `etoolbox.sty' not found. has caused the Debian Bug report #1052909, regarding auctex: FTBFS: ! LaTeX Error: File `etoolbox.sty' not found. 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.) -- 1052909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: auctex Version: 12.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/latex' > /usr/bin/tex '\nonstopmode \input bootstrap.ins' > This is TeX, Version 3.141592653 (TeX Live 2023/Debian) (preloaded format=tex) > > (./bootstrap.ins (/usr/share/texlive/texmf-dist/tex/latex/base/docstrip.tex > Utility: `docstrip' v2.6b <2022-09-03> > English documentation<2022-09-03> > > ** > * This program converts documented macro-files into fast * > * loadable files by stripping off (nearly) all comments! * > ** > > > * No Configuration file found, using default settings. * > > > ) > > Generating file(s) preview-mk.ins > > Processing file preview.dtx (installer,make) -> preview-mk.ins > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % > % % % % % <*style <*!active . . . . . . . . . . . . % % % % % % % % % % % % . > > % % % % % % % <*active . . > % % % % % % % % % % % % % % % % % % % % % % % % > % % % <*!active . . . . . . % % % % . . . % % % % . . . . . . % % % % % % % % > % % % % % . . . . . % % % % % % % % . . . % % % % % % % % % % % % % % . . . . > . . . % % % % % % . . . . . . . . . . % % % . . % % % . . > % % % % % % > <*active % % % % % % . . % % % % % % . . . % % % % % % % % % % % % % % . . % % > % % % % % % . . % % % . . % % % % % % % % % % % % % % . . . . . . . . . . . . > . . . . . % % % % % % % % % % % % % % % . . . . . . . . . . . . . . . . . . . > . . . . . . . % % % % % % % % % % % % % % % % % % % % % % % % % % . . . . . . > . . . . . . . . . . . . . % % % % % % % % % % . . . . % % % % % % % % % % % % > % % % % % % % % % % % % % % . . . . . . . % % % % % % % % % . . . . % % % % % > % % % % % . . . . . . % % % % % % % % . % % % % % % . . . % % % % % % % % . . > . . . . . % % % % % % % . . % % % % % . . . . . % % % % % % % % . . . . . % % > % % % % % % . . . . . . . > % % % % % % % % % % % % <*!active . . . . . . . . > . . . . . . . . . . . . . % % % % % % % % % % % % % % % % . . . . . . . . . . > . . . . . . . . . > % % % % % <*active . > % % % % % <*!active . . . % % % % % > % % . . . . . . . . . . . . . . . . . . . . . . . . . % % % % . . . . % % % % > % % % % . . % % % % % % % . % % % % % % % . . . . . . . . . . % % % % % % % % > % % % % . . . . . . . % % % % % % % . % % % % . . . . . . . . % % % % % % % . > % % % % . . . . . % % % % % % % % % . . . . . . . . . . . . . . . . % % % % % > % . . . . . > % % % % % % % % % % <*active . . . . . . . . . . . . > % % % % % > % % % % % % % % % % % % % % % % % % <*!active . . % % % % % % % % % . . % % % > % % % . . > % % % % <*active . . . . . . . % % % % % % % % % . . . . . . . % % > % % % % . . . . . . . . . . . . . . . . . % % % % % . > > % % % % % % % % % % > % % % % % % % % % % %% % % % % % % % > > > > % % % % % % % % % % % % % % % % % % % > >% % % % % % %
