Bug 1062959

Using my build example for installing httpd, would I execute those commands first?


# yum fs filter nodocs
# yum fs filter langs en
# yum fs refilter
# yum install .... httpd
# tar ... | docker

James,
could you please point me to some documentation of the new feature? From the examples above I do not quite follow what it is supposed to do. Thank you.

(In reply to Daniel Walsh from comment #1)
> Using my build example for installing httpd, would I execute those commands
> first?
> 
> 
> # yum fs filter nodocs
> # yum fs filter langs en

 Yeh, this is the setup. Telling yum to put tsflags=nodocs and _install_langs=en in all future transactions.

> # yum fs refilter

 This says to reinstall all packages which were installed using different nodocs/langs configuration than the current one.
 Note that bug#1062957 (and it's dep.) creates problems here, so I'd have to create some kind of "yum fs clean-filter" to remove the files on the FS that shouldn't be there. :(.

> # yum install .... httpd

 It would also apply to all future transaction though, so this would also have nodocs and langs=en.

> # tar ... | docker

(In reply to Karel Srot from comment #2)
> James,
> could you please point me to some documentation of the new feature? From the
> examples above I do not quite follow what it is supposed to do. Thank you.

 Sure, as soon as I write them :).

James, no way to get this to only effect one yum command.  IE I might want docs/lanquages on the host, but not in a chroot I am installing.

I guess you could always revert it.

 Yeh, you can use --setopt on the "yum install" you are doing for the container. EG.


 yum --setopt=override_install_langs=en --setopt=tsflags=nodocs --installroot=... install httpd

Awesome, when can I get this in Rawhide?  RHEL7?

Built for rawhide today, should be in it tomorrow ... also in the rawhide rebuild repos. Eg. http://copr-fe.cloud.fedoraproject.org/coprs/james/yum-rawhide/builds/


...Karel, I also did some docs in the man page.


       fs     This  command  has  a  few sub-commands to act on the filesystem
              data of the host, mainly  for  removing  languages/documentation
              for minimal installs:

               yum fs filters

               yum fs filter languages en:es

               yum fs filter documentation

               yum fs refilter [package(s)]

               yum fs refilter-cleanup [package(s)]

               yum fs du [path]

               yum fs status [path]

               yum fs diff [path]

              the first 3 being a simple interface to change yum.conf altering
              the  tsflags  and  override_install_langs  configurations.   The
              refilter  command is an optimized way of calling "yum reinstall"
              to reinstall the packages with  the  new  filters  applied.  The
              refilter-cleanup  command is needed because rpm doesn't actually
              remove the files on reinstall, as it  should.  And  the  du/sta‐
              tus/diff  commands  are included so you can easily see the space
              used/saved and any other changes.

FYI, I have reported bug 1062959.

James, could you please describe a bit more the 'diff' subcommand? I didn't identify what it is supposed to due. Thank you.

Probably easiest explanation is by example:

 yum fs diff /etc

...that's basically diff -ru on /etc vs. what is in the packages that are installed.

Thank you. I think I missed that information in the output between tons of warnings due to bug 1072258. :-)

James, are there any yum command that directly update yum.conf? I am not aware of any bug I do not such detailed insight and therefore I can't tell how such commands are supposed to work with yum.conf.

Why I am asking. I tried this:

# cp /etc/yum.conf /tmp
# yum -c /tmp/yum.conf fs filter docs
...
Enabling documentation filter.
fs filter done

# grep docs /tmp/yum.conf
# grep docs /etc/yum.conf
tsflags =nodocs

So the /etc/yum.conf was updated.. Funny thing starts when I try 

# yum -c /tmp/yum.conf fs filter nodocs
...
Already disabled documentation filter.
fs filter done

which is true for /tmp/yum.conf but previously yum was updating /etc/yum.conf.

So wouldn't it make sense to edit the config file passed via the -c option instead of /etc/yum.conf?

Yeh, not updating the -c version is a bit buggy ... the code was "borrowed" from yum-config-manager which does the same thing (ignores -c).

We could probably move to using .conf.config_file_path, but we'd need to tweak the surrounding code to work as well with installroot ... I think.

FYI, filed as bugs 1075706 and 1075708.

Hi James,
I am getting traceback after executing refilter-cleanup. yum is not able to delete a directory.

Running 'yum --disablerepo=\* --enablerepo=yum-fs-test -y fs refilter dummyPkgA dummyPkgB' (Expected 0, got 0)
Loaded plugins: auto-update-debuginfo, kabi, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Loading support for Red Hat kernel ABI
Removing: /usr/share/doc/dummyPkgA-1.0
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 355, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 174, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 571, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 4885, in doCommand
    ret = self._fs_refilter_cleanup(base, extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 4724, in _fs_refilter_cleanup
    misc.unlink_f(fname)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 953, in unlink_f
    os.unlink(filename)
OSError: [Errno 21] Is a directory: '/usr/share/doc/dummyPkgA-1.0'

Ok, I have a fix for this. Pushing to rawhide now, and push to el7 tomorrow.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.