Search results

** python2-foo (provides python-foo as a virtual provide via %python_provides) ** python3-foo (uses %python_provides, which is currently no-op)

rpmlint -iv foo-1.0-1.src.rpm rpmlint -iv foo-1.0-1.fc5.i386.rpm

for executables in /usr/bin, for example. If the file /usr/bin/foo is * foo for the binaries

rpms/foo rpms/foo/test/

...レポジトリに{{command|package.cfg}} という設定ファイルを作り、ビルドのための設定が必要となります。例えば、{{command|foo}} パッケージの {{command|8}} というストリームブランチに� fedpkg clone foo

foo: foo-selinux:

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

BuildRequires: foo

...uses foo.conf, then the global default configuration <b>MUST</b> be named foo-default.conf ...<code>foo.conf</code>, then the Server version <b>MUST</b> be named <code>foo-server.conf</code>.

...GNU Emacs and XEmacs, the main package should be called emacs-common-foo. This main package should contain files common to both GNU Emacs and XEmacs ...flavour of (X)Emacs, the main package should be called emacs-foo or xemacs-foo. In both cases, elisp source should be packaged in separate sub-packages as

== Some FIXME foo ==

...ing an integer and the second one being a character, then, that function ''foo'' must always be defined and exported by the library, with at least those t

Name: foo Summary: Does foo in D

...cs and XEmacs should be placed in sub-packages called emacs-foo and xemacs-foo. ...flavour of (X)Emacs, the main package should be called emacs-foo or xemacs-foo.

...name must be in foo-{version}-{release}.tar.gz/foo-{version}-{release}.bz2/foo-{version}-{release}.zip format ...s its version number as 1.0.1 and its going to install binary file foo and foo.desktop and it contains documentation files COPYING,README in tarball.

...[[#Use_of_Epochs]] for details. A quick way to check the Epoch of package foo is to run: Requires: foo

Owners: foo bar Owners: bar foo

<name>Foo</name> Requires: php-pear(Foo) >= 2.0.0

* The stub package will also provide python2dist(foo), to match what Fedora provides automatically. ...y version of python-foo. If a host hasn't updated and so still has python-foo version 2 then the dependencies would all technically be satisfied but thin

fedpkg request-repo --exception python38-foo-epel * Any files in %{_bindir} must only be of the form %{_bindir}/foo-%{python3_version}