Search results

Processing files: foo-1-1.noarch Provides: foo = 1-1 group(foo1)

git commit -am "Update of foobar to update foo to 1.2" git commit -am "Update of foobaz to update foo to 1.2"

** Example: <nowiki>[[Join the Foo Project]]; [[Setting up USB boot media]]; [[FAQ on SELinux]]; [[Standing in ...ly rename without nesting, putting all pages in an appropriate [[:Category:Foo Project]] category.

| Foo Bar || foo at bar.org || Y || leave blank before event || sample

{{Anchor|Issue-Foo}} === Issue Foo (example) ===

...or="#eeeeee"><tt><font color="#407a40">-foo would remove the package named foo</font></tt></td></tr> ...</font></th><td width="100%" bgcolor="#eeeeee"><tt><font color="#407a40">-@foo won't work</font></tt></td></tr>

** Example: <nowiki>[[Join the Foo Project]]; [[Setting up USB boot media]]; [[FAQ on SELinux]]; [[Standing in ...ly rename without nesting, putting all pages in an appropriate [[:Category:Foo Project]] category.

Foo in very specific version (e.g. <code>use Foo 0.2001;</code>). If you just copy the version to spec file (<code>Requires: perl(Foo) >= 0.2001</code>) you

For example, if foo-game needs libbar to run, but will not work with libbar that is older than ...to look in alternate locations for the -compat files, so the foo-devel and foo-compat-devel packages need to <code>Conflict:</code>. Whenever possible, th

...uish otherwise identical provides between packages $foo, $foo-openmpi and $foo-mpich.

...r package is named foo-1.0.0-1.src.rpm, then the spec file should be named foo.spec. foo-1.1.0-0.1.BETA (this is a prerelease, first beta)

...ctory is installed into <code>%{buildroot}%{assistant_path}/assistants/crt/foo</code>.

...el/init/dbus, do a full reboot. Otherwise, for system daemons do "service foo restart".

...me thing there. For example consider package foo requiring python3-bar; if foo's maintainer wishes to require system-python instead of python3, they must ...'s|#!%{__python3}|#!%{_libexecdir}/system-python|' %{buildroot}%{_bindir}/foo}</code>

git commit -am "Update of foobar to update foo to 1.2" git commit -am "Update of foobaz to update foo to 1.2"

...Product "foo|bar": match any device with a product name containing either "foo" or "bar" ...or "foo|bar|baz": match any device with a vendor string containing either "foo", "bar", or "baz"

...nd e.g. automatically change any Requires: python-foo to Requires: python2-foo. But this is not in the scope of this Change.

...ave we considered switching from foo to bar?" is great, "Why are you using foo! bar is better, we should switch to it right now" is not.

sshpass -P assphrase -v -e ssh -i /path/to/your/private/key foo@bar.com command sshpass -P assphrase -v -e scp -i /path/to/your/private/key local_content foo@bar.com:/destination

|| 2 ||[[User:Foo|Joe Smith]] || {{check}} || {{check}} || {{check}} || Speaker || || Yes