FS#8885 - Improper error message when /tmp is full

Attached to Project: Pacman
Opened by Post (post) - Monday, 10 December 2007, 18:23 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 19 December 2007, 01:57 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.6
Due in Version 3.1.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

Improper error message when /tmp is full.

Steps to Reproduce:

root@cipherspace ~# pacman -S cddb_get
resolving dependencies... done.
looking for inter-conflicts... done.

Targets: cddb_get-2.27-2

Total Package Size: 0.10 MB

Proceed with installation? [Y/n]
checking package integrity... done.
error: missing package name in /var/cache/pacman/pkg/cddb_get-2.27-2-i686.pkg.tar.gz
error: failed to commit transaction (invalid or corrupted package)

root@cipherspace ~# pacman -S wireless_tools
resolving dependencies... done.
looking for inter-conflicts... done.

Targets: wireless_tools-29-2

Total Package Size: 0.10 MB

Proceed with installation? [Y/n]
checking package integrity... done.
error: missing package name in /var/cache/pacman/pkg/wireless_tools-29-2-i686.pkg.tar.gz
error: failed to commit transaction (invalid or corrupted package)
This task depends upon

This task blocks these from closing
 FS#8109 - Pacman 3.1 Release Roadmap 
Closed by  Dan McGee (toofishes)
Wednesday, 19 December 2007, 01:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in git
Comment by Post (post) - Monday, 10 December 2007, 18:32 GMT
Fuck! I discovered that this error arise because /tmp was full.
Comment by Aaron Griffin (phrakture) - Monday, 10 December 2007, 18:57 GMT
  • Field changed: Summary (pacman doesn't install packages which have "_" in their name → Improper error message when /tmp is full)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Dan McGee (toofishes), Aaron Griffin (phrakture)
Hmmm, I'm going to keep this around. The reason: The /tmp error should have some output. This should be straightforward to fix, though
Comment by Scott H (stonecrest) - Monday, 17 December 2007, 03:56 GMT
I just ran into this issue as well (although both /tmp and / were full).

Debug log attached.
   foo (17.5 KiB)

Loading...