search for: source0

...4 01:50:01 2005 nullchard2 550267 srw-rw---- 1 moo moo 0 Aug 9 02:01:36 2005 socket0 550268 srw-rw---- 2 moo moo 0 Aug 4 02:05:00 2005 sockethard1 550268 srw-rw---- 2 moo moo 0 Aug 4 02:05:00 2005 sockethard2 550273 -rw-r----- 1 moo moo 0 Apr 16 21:47:16 2006 source0 550269 lrwxr-x--- 1 moo moo 7 Apr 16 21:57:12 2006 target1 -> source0 ## ok, now copy 0 to 1 using 0 as a reference... # the use of 0 as a reference when initializing the # first copy is valid though perhaps confusing. it also # happens to make writing backup scripts easier by # e...

On 2/6/19 9:35 AM, Ady Ady via Syslinux wrote: >> however, due to the issues with continuing >> to keep the main archive on kernel.org, I have moved the release archive to: > > Will the archive repo in kernel.org ever be updated again? > > Will the archive repo in kernel.org be updated when some > potential/hypothetical/future final/gold version gets released? >

...49 < %if %(rpmquery centos-release | grep -v 'not installed$' | grep -c -e '-[0-9]-[0-9].el[0-9]') --- > %if %(rpmquery centos-release | grep -v 'not installed$' | grep -c -e '-[0-9]-[0-9].[0-9]') 128c128 < Version: 2.7.2 --- > Version: 2.7.1 131c131 < Source0: R-%{version}.tar.gz --- > Source0: ftp://cran.r-project.org/pub/R/src/base/R-2/R-%{version}.tar.gz --GZVR6ND4mMseVXL/--

...wing may be useful for you (it Works For Me). Use it at your own risk, etc. The hardcode of 1.8 is probably a bad thing, but I''ll cross that bridge when I have to. Summary: Ruby RRD bindings Name: RubyRRDtool Version: 0.6.0 Release: 1 Epoch: 1 License: MIT Group: Application/Development Source0: %{name}-%{version}.tgz URL: http://rubyforge.org/projects/rubyrrdtool/ BuildRoot: %{_tmppath}/%{name}-root Requires: rrdtool, ruby BuildRequires: ruby, gcc, rrdtool-devel %define debug_package %{nil} %description RRD bindings for Ruby. %prep %setup -q %build ruby extconf.rb make %install insta...

...root 523 2011-09-09 15:35:59 centos-release-cr-ihc-1/etc/yum.repos.d/CentOS-cr.repo my spec file is /usr/local/rpmbuild/SPECS/centos-release-cr-ihc.spec the contents of which are: Summary: Package to set up IHC use of the centos-cr repository Name: centos-release-cr-ihc Version: 1 Release: 1 Source0: centos-release-cr-ihc-1.tar.gz License: GPL Group: IHC-config BuildArch: noarch BuildRoot: %{_tmppath}/%{name}-buildroot %description Package to set up IHC use of the centos-cr repository %prep %setup -q %build %install install -m 0755 -d /etc/yum.repos.d install -m 0755 etc/yum.repos.d/CentOS-cr....

...file of the resulting files Step 3 Turn this tar file into an RPM using the following spec file Name: mathematica Version: 6.0 Release: 1%{?dist} Summary: Mathematica Group: Development/Tools License: Commercial URL: http://www.wolfram.com/ Source0: mathematica.tar.bz2 BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) AutoReqProv: no #BuildRequires: #Requires: %description Long recognized as the world's most powerful mathematical software system #%prep #%build %install rm -rf $RPM_BUILD_ROOT m...

...s a redirection, yes, but the spectool can't trust the filename that is sent by the remote server, and uses only the filename extracted from the URL. Without extension, RPM doesn't know how to unpack the sources. So we have to do the following similarly odd trick (note the "#"): Source0: https://cran.r-project.org/package=%{packname}&version=%{version}#/%{packname}_%{version}.tar.gz Did you consider this problem? Is there any alternate immutable URL *with* extension? If not, is there any potential issue with the trick above? Regards, -- I?aki Ucar

...first needs to create an independent project and add it to either ``tools/`` or, using the MonoRepo layout, at the root of the repo alongside other projects. This project must contain the following minimal ``CMakeLists.txt``: .. code-block:: cmake add_llvm_pass_plugin(Name source0.cpp) The pass must provide two entry points for the new pass manager, one for static registration and one for dynamically loaded plugins: - ``llvm::PassPluginLibraryInfo get##Name##PluginInfo();`` - ``extern "C" ::llvm::PassPluginLibraryInfo llvmGetPassPluginInfo() LLVM_...

...it is: [bluethundr at repo SPECS]$ cat php.spec Name: php Version: 5.6.7 Release: 1%{?dist} Summary: PHP is a widely-used general-purpose scripting language. Group: Development/Languages License: PHP License v3.01 URL: http://www.php.net Source0: http://www.php.net/distributions/php-%{version}.tar.bz2 BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot Obsoletes: php %description PHP is a widely-used general-purpose scripting language that is especially suited for Web development and can be embedded into HTML....

I have the latest kernel with the drivers for my 3ware 9550SX built in. Where can I find the tools and monitoring apps for this card? Are there rpms hiding somewhere, or do I need to build it from source? -- Bowie

...39;s inpossible. 2) The rpmbuild -ba zbr.spec indeed installs the software in the building stage. That's odd, isn't it ? Following my signature is an openssl.spec file Any help would be appreciated. Warm regards, M?rio Gamito -- Summary: OpenSSL Name: openssl Version: 0.9.8b Release: 6 Source0: %{name}-%{version}.tar.gz License: GPL Source: http://www.mirrorservice.org/sites/ftp.openssl.org/source/openssl-0.9.8b.tar.gz Group: Applications/Communications %description OpenSSL provides encryption for Apache, SMTP, POP3 and IMAP. %prep %setup -q %build ./config no-idea shared make depend ma...

...ls from the kernel section of Fedora Koji,and the Fedora rpm-tools howto. http://fedoraproject.org/wiki/PackageMaintainers/CreatingPackageHowTo I've ran rpmlint -i linux-2.6.36-nouveau.i686.spec to test my spec file,but I keep getting this error: linux-2.6.36-nouveau.i686.spec: W: invalid-url Source0: /root/opt/linux-2.6/linux-2.6.36-nouveau.tar.gz The value should be a valid, public HTTP, HTTPS, or FTP URL. I've tried both url's for the linux-2.6 git repository,and also linus's url for the kernel,but I still keep getting the same error. I have attached the spec file I've been...

Stephen John Smoogen wrote: > On Wed, Dec 27, 2017 at 3:41 PM <m.roth at 5-cent.us> wrote: > >> I'm trying to build a package to create a directory and install some >> files. My rpmbuild keeps failing, unable to cd into the directory, "no >> such". Now, in the tmpfile, I *see* it cd'ing into BUILD/opt, and the >> source was unzipped and untared

...just for simple curiosity. > > > > That is TBD, but probably not. > > -hpa > Then perhaps, at some point, some of the references to kernel.org should be reconsidered. Examples: _ doc/SubmittingPatches.txt _ man/syslinux2ansi.1 _ man/syslinux.1 and the important ("Source0"): _ syslinux.spec I suspect that 'syslinux.spec' needs additional updates too (considering the changes that RPM-based distros already perform on it, for some time now). Regards, Ady.

...ld and rpmdevtools packages. If you have installed the latter then you can use vi (vim/gvim) to automatically create an empty spec template file simply by opening any new file name ending in '.spec'. It will look like this: Name: Version: Release: 1%{?dist} Summary: Group: License: URL: Source0: BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX) BuildRequires: Requires: %description %prep %setup -q %build %configure make %{?_smp_mflags} %install rm -rf %{buildroot} make install DESTDIR=%{buildroot} %clean rm -rf %{buildroot} %files %defattr(-,root,root,-...

...t it creates its own tree, with a clone of the rpmbuild tree under *that*. So, from the specfile, I'm trying to understand, after much googling, what I need to change the Source and BuildRoot to. My latest try for the latter is BuildRoot: %{_builddir}/BUILD/%{name}-%{version}-%{release} For Source0, I want to use the file in SOURCES. Anyone got a better example than what I've been googling? mark

...rpmdev-newspec -t minimal smipmicfg It will create a file smipmicfg.spec, and it will be fully populated with a mimimal spec file. You can probably just remove the %build section entirely, and just use the %install section to extract the contents of the tarball (or just create the dir and copy %{SOURCE0} to %buildroot/opt/smipmicfg-1.20.0 if it's just one file and not a tarball). It sounds like most of the problems you're having is that you've got a fragment of a SPEC file and not the whole thing. Don't build as root, let it build in your homedir (or use mock, but lets leave that...

...; spectool can't trust the filename that is sent by the remote server, > and uses only the filename extracted from the URL. > > Without extension, RPM doesn't know how to unpack the sources. So we > have to do the following similarly odd trick (note the "#"): > > Source0: > https://cran.r-project.org/package=%{packname}&version=%{version}#/%{packname}_%{version}.tar.gz > > Did you consider this problem? Is there any alternate immutable URL > *with* extension? If not, is there any potential issue with the trick > above? > > Regards, > --...

...; Version: 5.6.7 > > Release: 1%{?dist} > > Summary: PHP is a widely-used general-purpose scripting language. > > > > Group: Development/Languages > > License: PHP License v3.01 > > URL: http://www.php.net > > Source0: http://www.php.net/distributions/php-%{version}.tar.bz2 > > BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot > > > > Obsoletes: php > > > > %description > > PHP is a widely-used general-purpose scripting language that is > espec...

...ld how to know he is building kernel module package? Based on which condition? Here is mpt3sas.spec: Name: mpt3sas Version: 26.00.00.00 Release: 1 Summary: RHEL Driver Update Program package Group: System/Kernel License: GPLv2 URL: http://www.lsilogic.com Distribution: LSI Corporation Source0: %{name}-%{version}.tar.bz2 Source1: %{name}.files Source2: %{name}.conf BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX) BuildRequires: %kernel_module_package_buildreqs %global kernel_version `uname -r` %kernel_module_package -f %{SOURCE1} default %description LSI MPT F...