[SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

ajstein · 2014-07-26 18:51:38

I am trying to use pacman v4.1.2 - libalpm v8.0.2 on my laptop. I want to use VLC and Minitube (no-Flash dedicated app for Youtube) and it has issues with VLC's libpulse plugin, even if I do not use libpulse on my system. I have tried a few variants of NoExtract, having read the forums and documentation, to remove the plugin. I have tried the following:

Full file and path:

NoExtract   =  /usr/lib/vlc/plugins/audio_output/libpulse_plugin.so

Just file name:

NoExtract   =  libpulse_plugin.so

File path with pattern globbing (I know have the right version, but this was not even supported until recently)

NoExtract   =  /usr/lib/vlc/plugins/audio_output/libpulse_plugin*

File name with globbing

NoExtract   = libpulse_plugin*

None of these worked when I remove the package and reinstalled (pacman -Syu minitube; pacman -Rcs minitube # vlc and friends are include and just edited the pacman.conf; pacman -Syu minitube) it never works. Is it because the package is cached? I doubt that makes no difference. Any thoughts?

Last edited by ajstein (2014-07-26 19:54:26)

WorMzy · 2014-07-26 18:54:57

Reread the documentaton. Particularly the part that starts: "These files refer to files in the package archive".

ajstein · 2014-07-26 19:19:55

WorMzy wrote:

Reread the documentaton. Particularly the part that starts: "These files refer to files in the package archive".

Well thanks for the suggestion, but can you be more specific?

[me@laptop ~]$ tar -tvf /var/cache/pacman/pkg/vlc-2.1.5-1-x86_64.pkg.tar.xz | grep libpulse
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
-rwxr-xr-x root/root     18840 2014-07-09 16:11 usr/lib/vlc/plugins/services_discovery/libpulselist_plugin.so
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
-rwxr-xr-x root/root     31456 2014-07-09 16:11 usr/lib/vlc/plugins/audio_output/libpulse_plugin.so
-rwxr-xr-x root/root     23024 2014-07-09 16:11 usr/lib/vlc/plugins/access/libpulsesrc_plugin.so
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'

Is the name in the package any different from the options I have tried to specify or am I misunderstanding you?

lolilolicon · 2014-07-26 19:20:29

WorMzy wrote:

Reread the documentaton. Particularly the part that starts: "These files refer to files in the package archive".

You left out the newbie friendly "so do not include the leading slash"; oh our man pages are so homy

WorMzy · 2014-07-26 19:30:25

ajstein wrote:

WorMzy wrote:
Reread the documentaton. Particularly the part that starts: "These files refer to files in the package archive".
Well thanks for the suggestion, but can you be more specific?

The seven words that immediately follow the part I quoted.

lolilolicon has spoilt the surprise somewhat.

lolilolicon · 2014-07-26 19:47:00

My post should have been prefixed in big red bold italic uppercase "SPOILER ALERT!!! SPOILER ALERT!!!" -- or should every man page be?

EDIT: wait, did you just count 9 as seven? Do you count in months?
EDIT²: NVM, counted the wrong words.

Last edited by lolilolicon (2014-07-26 19:50:04)

WorMzy · 2014-07-26 19:50:59

I didn't include the part in brackets in the calulation.

karol · 2014-07-26 19:51:20

'so do not include the leading slash' is 7 words.

lolilolicon, I've already prepared popcorn and you've ruined it all :-(

ajstein · 2014-07-26 19:54:12

WorMzy wrote:

ajstein wrote:
WorMzy wrote:
Reread the documentaton. Particularly the part that starts: "These files refer to files in the package archive".
Well thanks for the suggestion, but can you be more specific?
The seven words that immediately follow the part I quoted.
lolilolicon has spoilt the surprise somewhat.

Well I am sorry to be a newb about that. I suspected but I thought honestly I should list the files by name only, not including full path. Examples on the web are spotty, and the only other BBS post about this no one made the correction or insight. I thought I must be really confused because the examples mentioned only refer to file name, not included path (full or relative path name).

NoExtract = file ...
All files listed with a NoExtract directive will never be extracted from a package into the filesystem. This can be useful when you don’t want part of a package to be installed. For
example, if your httpd root uses an index.php, then you would not want the index.html file to be extracted from the apache package. These files refer to files in the
package archive, so do not include the leading slash (the RootDir) when specifying them. Shell-style glob patterns are allowed.

Thanks to all of you. I appreciate the rapid response time. I clearly was too tired and skimming over the important part, but rest assured I realize this was retarded of me to ask and I am kind of embarassed.

Last edited by ajstein (2014-07-26 19:55:30)

lolilolicon · 2014-07-26 20:03:14

karol wrote:

'so do not include the leading slash' is 7 words.

lolilolicon, I've already prepared popcorn and you've ruined it all :-(

Mail them to me; I don't mind ruined popcorn as long as it's popped properly

WorMzy · 2014-07-26 20:06:26

It's a pretty easy oversight to make. The important thing to take away from this is to not skim over manpages, read them carefully, or you may miss the very answer you're looking for.

jjacky · 2014-07-26 20:32:03

ajstein wrote:

I thought I must be really confused because the examples mentioned only refer to file name, not included path (full or relative path name).

Just for the record, the example included on top of the man page does actually use path (without leading slash, as expected). It does use NoUpgrade and not NoExtract, but they're similar in terms of syntax.

ajstein · 2014-07-26 20:58:11

WorMzy wrote:

It's a pretty easy oversight to make. The important thing to take away from this is to not skim over manpages, read them carefully, or you may miss the very answer you're looking for.

I try not to. I am in my first year of Arch, not my first year of Linux. I am sorry for taking your time with this. Always sleep on it a day before going public. That is where the eureka moments happen of course.

Arch Linux

#1 2014-07-26 18:51:38

[SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#2 2014-07-26 18:54:57

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#3 2014-07-26 19:19:55

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#4 2014-07-26 19:20:29

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#5 2014-07-26 19:30:25

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#6 2014-07-26 19:47:00

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#7 2014-07-26 19:50:59

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#8 2014-07-26 19:51:20

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#9 2014-07-26 19:54:12

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#10 2014-07-26 20:03:14

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#11 2014-07-26 20:06:26

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#12 2014-07-26 20:32:03

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

#13 2014-07-26 20:58:11

Re: [SOLVED] Pacman 4.1.2 and NoExtract Directive Does Not Work for Me

Board footer