Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1267223 > unrolled thread

Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1

Started byAndreas Beckmann <anbe@debian.org>
First post2025-10-23 21:40 +0200
Last post2025-11-13 21:30 +0100
Articles 7 — 3 participants

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1 Andreas Beckmann <anbe@debian.org> - 2025-10-23 21:40 +0200
    Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1 "Adam D. Barratt" <adam@adam-barratt.org.uk> - 2025-11-01 12:10 +0100
    Bug#1118673: dkms 3.2.2-1~deb13u1 flagged for acceptance Adam D Barratt <adam@adam-barratt.org.uk> - 2025-11-02 13:10 +0100
    Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1 "Adam D. Barratt" <adam@adam-barratt.org.uk> - 2025-11-09 12:00 +0100
      Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1 Andreas Beckmann <anbe@debian.org> - 2025-11-09 12:40 +0100
        Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1 "Adam D. Barratt" <adam@adam-barratt.org.uk> - 2025-11-09 12:50 +0100
          Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1 Andreas Beckmann <anbe@debian.org> - 2025-11-13 21:30 +0100

#1267223 — Bug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1

FromAndreas Beckmann <anbe@debian.org>
Date2025-10-23 21:40 +0200
SubjectBug#1118673: trixie-pu: package dkms/3.2.2-1~deb13u1
Message-ID<LJ9kd-7pD7-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Package: release.debian.org
Severity: normal
Tags: trixie
User: release.debian.org@packages.debian.org
Usertags: pu
X-Debbugs-Cc: dkms@packages.debian.org
Control: affects -1 + src:dkms

[ Reason ]
I'd like to update dkms to a new upstream bugfix release.
This reverts the addition of the systemd unit (which was not really
needed) and the dependency cycle with cloud-init-network.service.
#1107232
There are a few more small bugfixes from the upstream releases and git
repository that correct the behavior in some corner cases.

[ Impact ]
Systemd unit dependency cycle in cloud installations.

[ Tests ]
autopkgtest for the upstream testsuite.
Manual tests of the problematic package combination.

[ Risks ]
Low, no problems reported in sid during the last 4 weeks.

[ Checklist ]
  [*] *all* changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in (old)stable
  [*] the issue is verified as fixed in unstable

[ Changes ]
  * New upstream release.
-> multiple minor bugfixes
  (new features have been postponed for upstream 3.3)
  * Stop shipping dkms.service. Not really needed and causes a dependency
    cycle with cloud-init-network.service.  (Closes: #1107232)
-> this is the RC bug
  * common.postinst: Emit a warning if no kernel headers were found.
    (Closes: #1114731)
-> Be more verbose on missing kernel headers, but don't fail.
  * Drop Pre-Depends: lsb-release, no longer used since 3.0.12.
-> packaging cruft
  * Add Breaks against more obsolete *-dkms packages.
-> updated the list after the trixie release

[ Other info ]
This is a rebuild of the package from sid with no further changes.


Andreas

[toc] | [next] | [standalone]


#1268594

From"Adam D. Barratt" <adam@adam-barratt.org.uk>
Date2025-11-01 12:10 +0100
Message-ID<LMhEB-9DCY-9@gated-at.bofh.it>
In reply to#1267223
Control: tags -1 + confirmed

On Thu, 2025-10-23 at 21:24 +0200, Andreas Beckmann wrote:
> I'd like to update dkms to a new upstream bugfix release.
> This reverts the addition of the systemd unit (which was not really
> needed) and the dependency cycle with cloud-init-network.service.
> #1107232
> There are a few more small bugfixes from the upstream releases and
> git
> repository that correct the behavior in some corner cases.

Please go ahead.

Regards,

Adam

[toc] | [prev] | [next] | [standalone]


#1268760 — Bug#1118673: dkms 3.2.2-1~deb13u1 flagged for acceptance

FromAdam D Barratt <adam@adam-barratt.org.uk>
Date2025-11-02 13:10 +0100
SubjectBug#1118673: dkms 3.2.2-1~deb13u1 flagged for acceptance
Message-ID<LMF4d-9TEw-9@gated-at.bofh.it>
In reply to#1267223
package release.debian.org
tags 1118673 = trixie pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian trixie.

Thanks for your contribution!

Upload details
==============

Package: dkms
Version: 3.2.2-1~deb13u1

Explanation: new upstream release; stop shipping dkms.service, fixing dependency cycle with cloud-init-network.service; emit a warning if no kernel headers were found

[toc] | [prev] | [next] | [standalone]


#1269630

From"Adam D. Barratt" <adam@adam-barratt.org.uk>
Date2025-11-09 12:00 +0100
Message-ID<LPbjj-bDsB-3@gated-at.bofh.it>
In reply to#1267223
On Thu, 2025-10-23 at 21:24 +0200, Andreas Beckmann wrote:
> I'd like to update dkms to a new upstream bugfix release.
> This reverts the addition of the systemd unit (which was not really
> needed) and the dependency cycle with cloud-init-network.service.
> #1107232
> There are a few more small bugfixes from the upstream releases and
> git repository that correct the behavior in some corner cases.
> 
> [ Impact ]
> Systemd unit dependency cycle in cloud installations.
> 
> [ Tests ]
> autopkgtest for the upstream testsuite.

piuparts is failing while trying to upgrade "dkms-replace-test-dkms":

 Building initial module dkms_test/1.0 for 6.12.43+deb13-amd64
  Sign command: /lib/modules/6.12.43+deb13-amd64/build/scripts/sign-file
  Signing key: /var/lib/dkms/mok.key
  Public certificate (MOK): /var/lib/dkms/mok.pub
  Certificate or key are missing, generating self signed certificate for MOK...
  openssl not found, can't generate key and certificate.
  
  Building module(s)... done.
  Module /lib/modules/6.12.43+deb13-amd64/updates/dkms/dkms_test.ko.xz already installed at version 1.0, override by specifying --force
  
  Error! Installation aborted.
  dpkg: error processing package dkms-test-dkms (--configure):
   installed dkms-test-dkms package post-installation script subprocess returned error exit status 6
  dpkg: dependency problems prevent configuration of dkms-replace-test-dkms:
   dkms-replace-test-dkms depends on dkms-test-dkms; however:
    Package dkms-test-dkms is not configured yet.
  
  dpkg: error processing package dkms-replace-test-dkms (--configure):
   dependency problems - leaving unconfigured

Regards,

Adam

[toc] | [prev] | [next] | [standalone]


#1269633

FromAndreas Beckmann <anbe@debian.org>
Date2025-11-09 12:40 +0100
Message-ID<LPbW1-bDXk-1@gated-at.bofh.it>
In reply to#1269630
On 11/9/25 11:58, Adam D. Barratt wrote:
> piuparts is failing while trying to upgrade "dkms-replace-test-dkms":

Can you point me to the full log? I didn't see it on ci.debian.net. 
There all tests in stable with "dkms/3.2.2-1~deb13u1 src:dkms from 
proposed-updates" looked fine.

 >   openssl not found, can't generate key and certificate.

This also sounds a bit suspicious, since the script has
   test -x /usr/bin/openssl || \
     apt-get install --no-install-recommends -yq openssl </dev/null 2>&1
(in case of older autodep8 versions that didn't generate this dependency)

I'll try to reproduce that, but if dkms-replace-test-dkms is the only 
test failing, I think this failure can be ignored. Replacement of 
modules is a fragile bit and a dkms corner case (and the test is a very 
special hack since usually a dkms package would replace a module from 
linux-image-* and not a different *-dkms package). Maybe it's just an 
installation order variation. The identical package didn't show anything 
abnormal in ci tests in sid and forky.

If the test failed on a different test environment than ci.debian.net, 
is a different autodep8 version being used?


Andreas

[toc] | [prev] | [next] | [standalone]


#1269634

From"Adam D. Barratt" <adam@adam-barratt.org.uk>
Date2025-11-09 12:50 +0100
Message-ID<LPc5H-bE1t-1@gated-at.bofh.it>
In reply to#1269633
On Sun, 2025-11-09 at 12:33 +0100, Andreas Beckmann wrote:
> On 11/9/25 11:58, Adam D. Barratt wrote:
> > piuparts is failing while trying to upgrade "dkms-replace-test-
> > dkms":
> 
> Can you point me to the full log? I didn't see it on ci.debian.net. 
> There all tests in stable with "dkms/3.2.2-1~deb13u1 src:dkms from 
> proposed-updates" looked fine.

Sure -
https://piuparts.debian.org/trixie2next/fail/dkms-replace-test-dkms_3.2.2-1~deb13u1.log

>  >   openssl not found, can't generate key and certificate.
> 
> This also sounds a bit suspicious, since the script has
>    test -x /usr/bin/openssl || \
>      apt-get install --no-install-recommends -yq openssl </dev/null
> 2>&1
> (in case of older autodep8 versions that didn't generate this
> dependency)
> 
> I'll try to reproduce that, but if dkms-replace-test-dkms is the only
> test failing, I think this failure can be ignored. Replacement of 
> modules is a fragile bit and a dkms corner case (and the test is a
> very special hack since usually a dkms package would replace a module
> from linux-image-* and not a different *-dkms package). Maybe it's
> just an installation order variation. The identical package didn't
> show anything  abnormal in ci tests in sid and forky.

Ack, thanks.

> If the test failed on a different test environment than
> ci.debian.net, is a different autodep8 version being used?

I don't think piuparts is running the package's tests here, rather it's
trying to install the p-u package in a chroot that already has the
version from stable installed. The log for the failing invocation
includes:

0m50.7s DEBUG: Starting command: ['chroot',
'/srv/piuparts.debian.org/tmp/tmpklakudmn', 'apt-get', '-y', 'install',
'dkms-replace-test-dkms']

Regards,

Adam

[toc] | [prev] | [next] | [standalone]


#1270062

FromAndreas Beckmann <anbe@debian.org>
Date2025-11-13 21:30 +0100
Message-ID<LQM77-cJQY-1@gated-at.bofh.it>
In reply to#1269634
On 11/9/25 12:42, Adam D. Barratt wrote:
> On Sun, 2025-11-09 at 12:33 +0100, Andreas Beckmann wrote:
>> On 11/9/25 11:58, Adam D. Barratt wrote:
>>> piuparts is failing while trying to upgrade "dkms-replace-test-
>>> dkms":
>>
>> Can you point me to the full log? I didn't see it on ci.debian.net.
>> There all tests in stable with "dkms/3.2.2-1~deb13u1 src:dkms from
>> proposed-updates" looked fine.
> 
> Sure -
> https://piuparts.debian.org/trixie2next/fail/dkms-replace-test-dkms_3.2.2-1~deb13u1.log

Already your initial report stated piuparts, but I only thought about 
autopkgtests ... these should be working OK, actually I didn't think 
about trying these packages in piuparts.
The dkms-replace-test-dkms package is most likely not working in upgrade 
scenarios, it was never designed for that (or even tested in such a 
scenario) and this failure shows that it actually doesn't. Probably the 
same happens in sid/testing. The autopkgtests only cover installation 
and removal, not upgrades.
In real instances of such module replacement one will not have two dkms 
modules stepping on each others feet but a dkms module and a shipped 
kernel module which will cause a bit less confusion on upgrades.
So, yes, please ignore this failure. Maybe that test package (which is 
not supposed to be installed on any users system) should be blacklisted 
in piuparts for upgrade tests (failing by design).


Andreas

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web