Groups | Search | Server Info | Login | Register
Groups > linux.debian.devel.testing > #1498
| From | Phil Armstrong <phil@kantaka.co.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.devel.testing |
| Subject | Bug#1110740: upgrade-reports: spamassassin upgrade configure step fails on Bookworm->Trixie upgrade |
| Date | 2025-08-10 18:50 +0200 |
| Message-ID | <Lihp7-6xYI-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Package: upgrade-reports Severity: normal X-Debbugs-Cc: Noah Meyerhans <noahm@debian.org> My previous release is: Bookworm I am upgrading to: Trixie Archive date: Sun, 10 Aug 2025 15:11:51 +0000 Upgrade date: 2025-08-10 uname -a before upgrade: Don’t have this, but it was the stock Bookworm kernel. uname -a after upgrade: Linux rocinante 6.12.38+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.38-1 (2025-07-16) x86_64 GNU/Linux Method: apt full-upgrade Contents of /etc/apt/sources.list: # Modernized from /etc/apt/sources.list Types: deb URIs: https://deb.debian.org/debian/ Suites: trixie Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: https://security.debian.org/debian-security/ Suites: trixie-security Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: https://deb.debian.org/debian/ Suites: trixie-updates Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg - Were there any non-Debian packages installed before the upgrade? If so, what were they? All packages came from Debian archives. - Was the system pre-update a 'pure' system only containing packages from the previous release? If not, which packages were not from that release? Latest emacs from bookworm-backports. Otherise stock Bookworm. - Did any packages fail to upgrade? spamassassin. - Were there any problems with the system after upgrading? No. Further Comments/Problems: During an upgrade from Bookworm to Trixie, the installation of the Trixie version of Spamassassin failed with the following error: # dpkg --configure -a Setting up spamassassin (4.0.1-5) ... mktemp: failed to create file via template ‘/tmp/user/0/tmp.XXXXXXXXXX.r000.tgz’: Permission denied dpkg: error processing package spamassassin (--configure): installed spamassassin package post-installation script subprocess returned error exit status 1 Further investigation revealed that this machine was not using tmpfs & mktemp was trying to create a file inside /tmp/user/0 (which already existed) as the user debian-spamd. Since /tmp/user/0 has permissions drwx------ 3 root root 120 Aug 10 17:04 0 this obviously fails. Making /tmp/user/0 (temporarily) world rwx allows the configuration of spamassassin to complete & the upgrade to Trixie to finish. cheers, Phil
Back to linux.debian.devel.testing | Previous | Next | Find similar
Bug#1110740: upgrade-reports: spamassassin upgrade configure step fails on Bookworm->Trixie upgrade Phil Armstrong <phil@kantaka.co.uk> - 2025-08-10 18:50 +0200
csiph-web