Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#1367 - pacman -Ql reports files not there (nvidia)

Attached to Project: Pacman
Opened by Tim Peeters (timp) - Wednesday, 01 September 2004, 18:39 GMT
Task Type Bug Report
Category
Status Closed
Assigned To No-one
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

$ pacman -Ql nvidia
nvidia /opt/
nvidia /opt/nvidia/
nvidia /opt/nvidia/NVIDIA-Linux-x86-1.0-6111-pkg0.run
$ ls /opt/nvidia/
ls: /opt/nvidia/: No such file or directory

This doesn't seem right. I guess the package contains /opt/nvidia/NVIDIA-Linux-x86-1.0-6111-pkg0.run which is ran to install the nvidia kernel driver to /lib/modules/2.6.8.1/kernel/drivers/video/nvidia.ko plus some other files and then removes /opt/nvidia/. But I think this way pacman may not be able to correctly delete the package..
This task depends upon

Closed by  Judd Vinet (judd)
Sunday, 19 December 2004, 00:30 GMT
Reason for closing:  Not a bug
Comment by Nikos Kouremenos (zeppelin) - Tuesday, 21 September 2004, 09:31 GMT
well that's true. I won't delete [AFAICT] the modules..
I can of course remove the modules too.

this is not a medium priority anyways..
Comment by Giulio Fidente (giulivo) - Monday, 06 December 2004, 11:36 GMT
so at the moment "pacman --remove nvidia" does not removes correctly the nvidia package?

i don't know very well how pacman works, but if that's true i think this is MORE than medium priority :P
Comment by Giulio Fidente (giulivo) - Monday, 06 December 2004, 11:41 GMT
probably a look to the crux's port of the nvidia driver can be useful:
http://clc.morpheus.net/portdb/?command=viewport&repo=contrib&name=nvidia
Comment by Judd Vinet (judd) - Sunday, 19 December 2004, 00:29 GMT
I believe the nvidia maintainer has done this because of the licensing on the nvidia binaries. Some closed-source licenses forbid us from unpacking the binaries or otherwise altering their state before they reach the end user.

We also do this with the ttf-ms-fonts package.

[jvinet@mars pacman]$ pacman -Ql ttf-ms-fonts
ttf-ms-fonts /tmp/
ttf-ms-fonts /tmp/ttf-ms-fonts/
ttf-ms-fonts /tmp/ttf-ms-fonts/andale32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/arial32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/arialb32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/comic32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/courie32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/georgi32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/impact32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/times32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/trebuc32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/verdan32.exe
ttf-ms-fonts /tmp/ttf-ms-fonts/webdin32.exe


The post-install scriptlet then unpacks these .exe/CAB files into the filesystem. The obvious downside is that pacman cannot properly remove the package. The upside is we don't piss off Microsoft.

Loading...