Package: libkf6textaddons-data
Version: 1.5.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental'
Package: dahdi-dkms
Version: 1:3.1.0+git20230717~dfsg-5
Severity: serious
DKMS make.log for dahdi-3.1.0+git20230717 for kernel 6.8.9-amd64 (x86_64)
Sun May 19 19:55:53 UTC 2024
make -C /lib/modules/6.8.9-amd64/build
KBUILD_EXTMOD=/var/lib/dkms/dahdi/3.1.0+git20230717/build/drivers/dahdi
) bookworm; urgency=medium
* Non-maintainer upload.
* Rebuild for bookworm.
-- Andreas Beckmann Fri, 17 May 2024 14:23:15 +0200
software-properties (0.99.30-4.1) unstable; urgency=medium
* Non-maintainer upload.
* software-properties-qt: Add Conflicts+Replaces: software-properties-kde
Package: apt
Version: 2.9.2
Severity: serious
one package to reproduce this bug is mpich 4.2.0-5.1
mpich-4.2.0# apt-get build-dep -y .
Note, using directory '.' to get the build dependencies
terminate called after throwing an instance of 'std::length_error'
what(): basic_string::_M_create
Package: libmpich-dev
Version: 4.2.0-5.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old
Package: plover
Version: 4.0.0~rc2-0.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version
Package: geki3
Version: 1.0.3-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the
Package: pcp
Version: 6.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the
Package: python3-nxtomo
Version: 1.2.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
Preparing to unpack
Package: python3-nabu
Version: 2024.1.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
Preparing to unpack
Package: redict-tools
Version: 7.3.0+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the
Package: thawab
Version: 4.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dependencies:
thawab : Depends: gir1.2-webkit2-4.0 but it is not
Package: mumble-server
Version: 1.5.517-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As
Package: sbws
Version: 1.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no
Package: ftp.debian.org
Severity: normal
Please remove the t64 renamed version of itk3 from experimental, the
t64 transition is not needed for this package.
https://bugs.debian.org/1062462
itk3 | 3.4.2-3.1 | unstable | source
itk3 | 3.4.2-3.1+b1 | unstable | amd64,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu gauche-gl_0.6-4 . ANY . unstable . -m "Rebuild against libgauche-0.98-0."
not a transition since the affected packages are in sid only
Andreas
Package: python3-pynpoint
Version: 0.11.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dependencies:
python3-pynpoint : Depends: python3-h5py
Source: gauche-c-wrapper
Version: 0.6.1-12
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts
dh_auto_build
make -j16
make[1]: Entering directory
Package: libpsml-dev
Version: 2.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dependencies:
libpsml-dev : Depends: libxmlf90-dev but it is
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu pytorch-cluster_1.6.3-1 . ANY . unstable . -m "Rebuild against pytorch 2.1"
python3-torch-cluster currently has an unsatisfiable dependency on libtorch2.0
Andreas
On Mon, 22 Apr 2024 09:31:00 +0200 Alexandre Rossi wrote:
Hi,
With the right versions, sorry for the noise.
nmu uwsgi-plugin-php_0.0.15 . ANY . unstable . -m "rebuild against new uwsgi.h"
nmu uwsgi-plugin-luajit_0.0.8 . ANY . unstable . -m "rebuild against new
uwsgi.h"
nmu
Followup-For: Bug #1071008
I noticed in piuparts that the package is currently uninstallable,
probably related to this bug.
Selecting previously unselected package libx52pro0.
Preparing to unpack .../libx52pro0_0.1.1-3_amd64.deb ...
Unpacking libx52pro0 (0.1.1-3) ...
dpkg: error
Furthermore in dkms.conf you should add
# linux/platform_profile.h, wmi_evaluate_method()
BUILD_EXCLUSIVE_CONFIG="CONFIG_ACPI_PLATFORM_PROFILE CONFIG_ACPI_WMI"
to skip building the module on unsupported kernel configurations
Andreas
Package: v4l2loopback-dkms
Version: 0.13.1-1
Severity: serious
DKMS make.log for v4l2loopback-0.13.1 for kernel 6.7.12-686-pae (i686)
Mon May 13 09:57:13 UTC 2024
++ To sign the module, you must set KBUILD_SIGN_KEY/KBUILD_SIGN_CERT to
point to the signing key/certificate!
++ For your
Package: ezurio-qcacld-2.0-dkms
Version: 0.0~git20230623.2cd31b6-1
Severity: serious
The module fails to build for several architectures and kernel versions:
Linux 6.6.*:
https://ci.debian.net/packages/e/ezurio-qcacld-2.0-dkms/testing/amd64/45828215/#L3674
243s
Package: legiond
Version: 0.0.10+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
legiond in main depends on lenovolegionlinux-dkms in contrib, which is
not permitted by the policy.
BTW, why is the -dkms package in contrib?
The -dkms package looks overly complicated:
-
On 05/05/2024 20.52, Adam D Barratt wrote:
Package: nvidia-graphics-drivers
Version: 470.239.06-1
Explanation: upstream security fixes [CVE-2022-42265 CVE-2024-0074
CVE-2024-0078]
Can we push these packages to bullseye-updates?
The kernel change that recently caused problems for the nvidia
On 08/05/2024 02.20, Braiden Kindt wrote:
Package: nvidia-kernel-dkms
Version: 470.223.02-1
There is already a newer driver version in oldstable-proposed-updates.
Does it fix the issue?
Andreas
Hi Adam,
while accepting the nvidia stack yesterday (many thanks for that!) you
missed to tag etc. this bug, while the package was accepted (perhaps
attributed to a different bug?).
Andreas
Followup-For: Bug #985017
Control: found -1 2.7.4+git6-g9134ad92-8
With python3.12 is installed, there are even more warnings:
Setting up python3-whoosh (2.7.4+git6-g9134ad92-8) ...
/usr/lib/python3/dist-packages/whoosh/analysis/filters.py:50: SyntaxWarning:
invalid escape sequence '\w'
Followup-For: Bug #1060444
Control: retitle -1 python3-networkx: SyntaxWarning during package installation
if python3.12 is installed
This only happens if python3.12 is installed (which is not yet the default).
Andreas
Package: python3-opengl
Version: 3.1.7+dfsg-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package emits a SyntaxWarning
during installation:
Setting up python3-opengl (3.1.7+dfsg-1) ...
Followup-For: Bug #1060444
Control: found -1 3.2.1-3
Setting up python3-networkx (3.2.1-3) ...
/usr/lib/python3/dist-packages/networkx/readwrite/tests/test_gml.py:557:
SyntaxWarning: invalid octal escape sequence '\420'
"graph [edge [ source u'u\4200' target u'u\4200' ] "
On 06/05/2024 07.38, Paul Gevers wrote:
Hi,
On 05-05-2024 8:04 p.m., Andreas Beckmann wrote:
167s autopkgtest [09:50:25]: test test-dm-writeboost.sh:
[---
168s II: Checking for 14G available disk space...SKIP
How much disk space is used already by the time you get
[*] attach debdiff against the package in (old)stable
[*] the issue is verified as fixed in unstable
[ Changes ]
dm-writeboost (2.2.17-0.2~deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
* Rebuild for bookworm.
-- Andreas Beckmann Sun, 05 May 2024 20:42:46 +0200
dm-writeboost
Package: python3-astrometry
Version: 0.93+dfsg-1.1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package emits a SyntaxWarning
during installation:
Setting up python3-astrometry (0.93+dfsg-1.1+b1) ...
On 28/04/2024 11.35, Paul Gevers wrote:
Hi,
On 28-04-2024 9:34 a.m., Andreas Beckmann wrote:
What kernel is running inside the test environment and what is the
best way to install its headers?
Can you help me find the answer? I guess you don't mean "the current
kernel of the suite
Package: liblirc-dev
Version: 0.10.2-0.8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old
Package: python-guizero-doc
Version: 1.5.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an
Followup-For: Bug #1066721
Control: tag -1 pending
I've now uploaded the NMU to DELAYED/5. Please let me know if I should
delay it lonegr.
Andreas
Package: ftp.debian.org
Severity: normal
Please remove the obsolete arch:all package papi-examples from
experimental.
papi-examples | 7.1.0-4 | experimental | all
papi-examples | 7.1.0-5 | unstable | amd64, arm64, armel, armhf,
i386, mips64el, ppc64el
Andreas
Package: ftp.debian.org
Severity: normal
Please remove the t64 renamed version of itcl3 from experimental, the
t64 transition is not needed for this package.
https://bugs.debian.org/1062461
itcl3 | 3.4.4-2| unstable | source
itcl3 | 3.4.4-2+b1 | unstable | amd64,
Package: vzlogger
Version: 0.8.3-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package's logrotate
configuration causes logrotate to exit with an error after the package
has been removed (*) or when logrote is run but no
Package: libcapi20-dev
Version: 1:3.27-3.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
X-Debbugs-Cc: Lukas Märdian
Hi,
a test with piuparts revealed that your package misses the copyright
file, which is a violation of Policy 12.5:
Package: bin86,elks-libc
Version: 0.16.17-3.5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
X-Debbugs-Cc: Bastian Germann
Hi,
a test with piuparts revealed that your package misses the copyright
file, which is a violation of Policy 12.5:
Package: libgnokii7t64
Version: 0.6.31+dfsg-5.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file, which is a violation of Policy 12.5:
Package: ukui-power-manager
Version: 4.0.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
Package: php-composer-pcre
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Control: affects -1 + src:composer
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'bullseye'.
It installed fine in 'bullseye', then the
Followup-For: Bug #1066213
Control: tag -1 patch pending
Hi,
this was fixed and tagged in git a week ago, but so far no upload
happened.
Andreas
Followup-For: Bug #1048058
Control: tag -1 patch
Attached patch cleans two more directories with files that are generated
during build, fixing building the package twice in a row.
Andreas
>From 996fe0699101d5f2683b6a329fad71fb72210094 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date:
Followup-For: Bug #1068665
Control: tag -1 pending
Hi,
in order to make progress with the t64 transition, I've uploaded
Emanuele's patch as a NMU to DELAYED/2. Please let me know if I should
delay it longer.
Andreas
Source: lyskom-elisp-client
Version: 0.48+git.20231226.364902c3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
lyskom-elisp-client FTBFS in the minimal chroots used by the buildds:
https://buildd.debian.org/status/package.php?p=lyskom-elisp-client
...
cp
Followup-For: Bug #1068610
Control: tag -1 pending
Hi,
I've taken Holgers patch and imported it into the git repository on
salsa and uploaded it to DELAYED/2 to make progress with the t64
transition. Please let me know if I should delay it longer.
I've also fixed building the package twice in a
On 04/05/2024 13.02, Andreas Beckmann wrote:
I have patched sendmail in order to enable O RejectNUL=True directive,
but I do not achieved the fact to enable it by default.
Andreas could you get a glimpse at how to render RejectNUL a default ?
Second attempt. Completely untested
ade1a2cac3892eedc07a5f2e47db2213950d0d6b Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Sat, 4 May 2024 10:31:04 +0200
Subject: [PATCH] enable 'O RejectNUL=true' in the default sendmail.cf
---
debian/cf/debian/sendmail.mc.in | 3 +++
debian/cf/feature/rejectnul.m4 | 3 +++
2 files changed, 6 insertions
Followup-For: Bug #1066278
Control: tag -1 patch pending
Hi,
I've imported the patch from Ubuntu and together with some minor fixes
uploaded it as a NMU to DELAYED/2. Please let me know if I should delay
it longer.
All changes have been pushed to the salsa.d.o repository.
(changelog
On 03/05/2024 22.27, Michael Tokarev wrote:
The move has happened in 4.19.6-2 which were uploaded a couple days ago.
The version in experimental (4.20) uploaded *before* the version in sid
(4.19.6) - I uploaded new upstream version to experimental to see how it
will work.
I didn't check the
Package: samba-dev
Version: 2:4.20.0+dfsg-1~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental'
On Mon, 22 Apr 2024 19:20:43 +0200 Paul Gevers wrote:
On 22-04-2024 1:37 p.m., Skyper x wrote:
> The erfs service was shut down and this tool is no longer functional. It
should be removed.
Please file an RM bug against the ftp.debian.org pseudo package.
Should it be removed from stable
On 28/04/2024 22.39, Adam D. Barratt wrote:
On Sun, 2024-04-28 at 13:43 +0200, Andreas Beckmann wrote:
Please reject nvidia-graphics-drivers/535.161.08-1~deb12u1, nvidia-
driver-full is uninstallable on ppc64el (but that was hidden by the
other t64 transition blockers).
Done, thanks
Source: rust-sequoia-octopus-librnp
Version: 1.8.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: time-t
rust-sequoia-octopus-librnp FTBFS on armel/armhf due to the t64
transition:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
The package in sid had a renaming t64 transition, but experimental
already has a different SOVERSION, so only a binNMU is needed.
nmu openmm_8.1.0+dfsg-2 . ANY . experimental . -m "Rebuild
Package: ftp.debian.org
After restricting osmo-hlr to 64-bit architectures, the t64 renaming
transition is no longer needed and the prepared package can go from
experimental.
osmo-hlr| 1.5.0+dfsg1-3.1~exp1 | experimental | source, amd64,
arm64, armel, armhf, i386, mips64el,
Package: ftp.debian.org
After restricting osmo-iuh to 64-bit architectures, the t64 renaming
transition is no longer needed and the prepared package can go from
experimental.
osmo-iuh | 1.3.0+dfsg1-5.1~exp1 | experimental | source
osmo-iuh | 1.3.0+dfsg1-7| testing
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: dicomnifti -- ROM; Obsolete
On Thu, 2 May 2024 12:15:48 -0400 Valerio Luccio
wrote:
Package: dicomnifti 2.33.1-5
Software not compatible with most recent DICOM image version and will
not be updated.
I assume you wanted to file a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu osmo-msc_1.9.0+dfsg1-2 . ANY . unstable . -m "Rebuild against libosmo-sccp
with t64 renaming reverted."
nmu osmo-sgsn_1.9.0+dfsg1-3 . ANY . unstable . -m "Rebuild against libosmo-sccp
Hi Daniel,
should qflow/experimental be removed as well?
It's a newer upstream version than what was removed from sid, but
nevertheless has now an unsatisfiable build dependency on graywolf.
(please file a new RM bug in case you opt for removal)
Andreas
On Tue, 30 Apr 2024 20:07:07 -0400 Boyuan Yang wrote:
I've prepared an NMU for sniproxy (versioned as 0.6.1+git20240321-0.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I
sniproxy is orphaned, so you should rather do an undelayed QA upload
(instead of a NMU) and update the
Source: nvidia-cuda-toolkit
Version: 4.0.13-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: Debian Security Team
https://nvidia.custhelp.com/app/answers/detail/a_id/5517
CVE-2024-0072 NVIDIA CUDA toolkit for all platforms contains a
vulnerability in cuobjdump and nvdisasm where an
Package: qa.debian.org
Severity: wishlist
Hi,
would it be possible to color-code the Excuses links based on the
migration status? I'd think about
* green -> "Will attempt migration"
* red -> "BLOCKED"
* (default) -> "check later"
Maybe the "red" flag could further be distinguished between
On 29/04/2024 09.59, Andreas Beckmann wrote:
A possible solution (which also handles all kernels that got the patch
Merged in dm-writeboost as
https://github.com/akiradeveloper/dm-writeboost/commit/1967beb97d63044043383721759c8928bc6353c6
Andreas
On 30/04/2024 07.40, Paul Gevers wrote:
On 30-04-2024 12:43 a.m., Andreas Beckmann wrote:
Testsuite: autopkgtest-pkg-dkms
Right. I was talking about Testsuite-Triggers in the sources file
generated by dpkg.
Perhaps you can spot what's wrong with this setup s.t. it does not
trigger
On 29/04/2024 19.49, Paul Gevers wrote:
As I hinted at in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069600#25, once
there's an *test* dependency relation with linux, this will be tested.
There should be a test dependency on linux-doc, but unfortunately I
cannot find any record that
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Control: block 1069878 with -1
Control: affects -1 + src:dm-writeboost
Hi,
the 6.1.85-1 kernel in bookworm-pu causes module build failures for
dm-writeboost-dkms (#1069878) and
A possible solution (which also handles all kernels that got the patch
backported) could be adapted from my pull request for dm-writeboost:
https://github.com/anbe42/dm-writeboost/commit/6af8e67052c970e85943429011588976f3f9423a
Andreas
Control: retitle -1 bookworm-pu: package
nvidia-graphics-drivers/535.161.08-2~deb12u1
On 29/03/2024 19.40, Adam D. Barratt wrote:
On Thu, 2024-03-28 at 18:40 +0100, Andreas Beckmann wrote:
The whole nvidia stack has now been uploaded,
src:nvidia-graphics-drivers is sitting in NEW.
It's now
Source: nginx
Version: 1.24.0-2
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t
X-Debbugs-Cc: Sebastian Ramacher , Steve Langasek
Control: block 1069482 with -1
While looking into #1069482 (libnginx-mod-http-lua: FTBFS on armhf) I
noticed that nginx has a
On 22/04/2024 19.46, Paul Gevers wrote:
you. In case you are not subscribed, this message again.
Thanks. Please keep me Cc:ed.
For this concrete case it may be as simple as adding dependency on
sudo. In case it is trivial for you to rerun the failing test with
Thanks for running the test.
Followup-For: Bug #1066703
Control: tag -1 patch
Attached is a patch that fixes the missing prototypes.
Andreas
>From fe497acc8ee1883cd9d061e43c864eaf5e5c3e1c Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Sun, 28 Apr 2024 08:23:21 +0200
Subject: [PATCH] fix building with -Wer
/clean or
d/rules.
Andreas
>From eaf3df4d725facee08964d2329335cf4c2a25cd4 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Sun, 28 Apr 2024 07:41:41 +0200
Subject: [PATCH 1/2] fix building with -Werror=implicit-function-declaration
---
debian/patches/missing-prototypes.patch |
upgrades from bullseye. (Closes: #1034993)
+
+ -- Andreas Beckmann Sat, 27 Apr 2024 21:08:49 +0200
+
software-properties (0.99.30-4) unstable; urgency=medium
* py3-software-properties: Depend on lazr.restfulclient (Closes: #1029047)
diff --git a/debian/control b/debian/control
index 94d20bd7
Followup-For: Bug #1069405
Control: retitle -1 x11-apps: FTBFS with libxcb 1.17: Package requirements
(x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met
Control: block -1 with 1069408
This happens on all architectures and is probably caused by the missing
libxcb-dri3-dev dependency
Followup-For: Bug #1066721
Control: tag -1 patch
I've committed a fix to the git repository. Will followup with a NMU in a
few days. I've also enabled the salsa-ci pipeline for the package.
Andreas
Followup-For: Bug #1069878
Control: tag -1 + bookworm
DKMS make.log for dm-writeboost-2.2.16 for kernel 6.1.0-20-cloud-amd64 (x86_64)
Sat Apr 27 11:45:49 UTC 2024
make -C /lib/modules/6.1.0-20-cloud-amd64/build
M=/var/lib/dkms/dm-writeboost/2.2.16/build modules
make[1]: Entering directory
Package: rapiddisk-dkms
Version: 9.1.0-2
Severity: serious
Control: found -1 9.0.0-1
DKMS make.log for rapiddisk-dkms-9.1.0 for kernel 6.7.12-amd64 (x86_64)
Fri Apr 26 21:35:41 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.7.12-amd64'
CC [M]
Followup-For: Bug #955260
Control: severity -1 serious
Control: found -1 2.3.1-1
Control: retitle -1 libkqueue: FTBFS: tests fail with ERROR: Program received
signal 6
This is now happening on the buildds as well and I can also reproduce it
locally on amd64.
Andreas
Source: lyskom-elisp-client
Version: 0.48+git.20231226.364902c3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
lyskom-elisp-client fails to build for arch:all due to missing emacs:
Package: ftp.debian.org
Severity: normal
after restricting jellyfish to 64-bit architectures the t64 transition
has been reverted and the corresponding packages can be removed again
from experimental.
jellyfish | 2.3.1-2.1~exp1 | experimental | source
jellyfish | 2.3.1-3|
Followup-For: Bug #1065993
Control: tag -1 pending
Hi,
I've uploaded this fix along with some more minor cleanup (can be found
in the git repository) as a NMU to DELAYED/2. Please let me know if I
should delay it longer.
Andreas
is enabled by default.
+ * Declare Rules-Requires-Root: no.
+
+ -- Andreas Beckmann Sat, 27 Apr 2024 02:39:58 +0200
+
libevdevplus (0.1.1-2) unstable; urgency=medium
* d/rules: set -DCMAKE_POSITION_INDEPENDENT_CODE=ON.
diff --git a/debian/control b/debian/control
index 1450393..de2a994 100644
/debian/changelog 2024-04-26 20:00:15.0 +0200
@@ -1,3 +1,19 @@
+gxr-openvr (0.15.1-2.1) unstable; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Fix building twice in a row.
+ * Switch B-D from pkg-config to pkgconf.
+
+ [ Michael Hudson-Doyle ]
+ * s/libgxr-0.15-0
On 26/04/2024 18.54, Dirk Lehmann wrote:
No, I am currently don't have `gnutls-bin` installed. Just `gnutls-bin` and the
sources are versioned to 3.8.5-2.
That was the most plausible package depending on libgnutls-dane0 ...
In sid and testing the binary packages `libgnutls30` and
On 26/04/2024 16.51, Dirk Lehmann wrote:
The following packages have unmet dependencies:
libgnutls-dane0 : Depends: libgnutls30 (= 3.8.3-1)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.
Do you have any packages on "hold" (apt-mark showhold)?
Control: reassign -1 src:gnutls28 3.8.3-1
Control: severity -1 normal
Control: tag -1 moreinfo
On Fri, 26 Apr 2024 12:41:45 +0200 Dirk Lehmann wrote:
Package: libgnutls30
Version: 3.8.3-1
since yesterday the .deb files for the architectures
* amd64 arm64 i386 mips64el ppc64el riscv64
.
+
+ -- Andreas Beckmann Fri, 26 Apr 2024 11:52:39 +0200
+
+cpu (1.4.3-14~deb12u1) bookworm; urgency=medium
+
+ * QA upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Mon, 25 Mar 2024 21:37:56 +0100
+
+cpu (1.4.3-14) unstable; urgency=medium
+
+ * QA upload.
+ * Actually provide a definition
Package: libccrtp-doc
Version: 2.0.9-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to
Followup-For: Bug #1069793
reform-setup-wizard misses
Breaks+Replaces: mnt-reform-setup-wizard (<< 0.1.0-3)
for the package rename.
Andreas
Source: stravalib
Version: 1.3.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
stravalib recently started to FTBFS, probably due to a change in on eof
its (transitive) build-depends:
ERRORS
On 24/04/2024 23.15, Jonathan Wiltshire wrote:
Is this apparent duplication correct? Sorry not to have spotted it before.
Yes, that's exactly how I want it. The history of n-g-d as part of
n-g-d-tesla-470. The changelog entry is duplicated because of the CVE
list, otherwise it would have
Followup-For: Bug #1064991
Control: severity -1 important
migration is currently blocked by the t64 migration
Andreas
1 - 100 of 15330 matches
Mail list logo
