search for: spectool

...s way, a SPEC would build correctly even if the package was updated and the old version was archived (is this guaranteed to continue to work in future? I assumed so...). There is an odd thing about this format though, and that is the absence of a file extension. This is 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/pa...

...rectly even if the package was updated > and the old version was archived (is this guaranteed to continue to > work in future? I assumed so...). > > There is an odd thing about this format though, and that is the > absence of a file extension. This is 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: &...

...other repos, epel for example it only versions specs and patches, all binary files are downloaded in the time that the srpms are built to send to mock (koji in their case), fedora is swiching from a Makefile per package to a fedpkg tool to work with package sources. I see that a friend will be spectool, and some of scripting i can get a build system from source version control, but i think that this already is made, so i'm don't want to reinvent the well, i prefer help other people in make more robust system. There is a currently model for package metadata store and common task work?...

...1.html - Matroska: http://matroska.org/technical/specs/index.html - EBML: http://matroska-org.github.io/libebml/specs.html - FLAC: https://xiph.org/flac/format.html Development Versions: - FFV1: https://github.com/ffmpeg/ffv1 - Matroska:https://github.com/Matroska-Org/foundation-source/blob/master/spectool/specdata.xml - EBML: https://github.com/Matroska-Org/ebml-specification The Working Group will seek consensus and refinements for specifications for both FFV1 and Matroska in order to provide authoritative, standardized specifications for users and developers. Backward compatibility with existing...

Hello, I hope the is the right list to send this suggestion to. I was wondering if it might be possible to have CRAN store the most current version of a package's source tarball at a location that does not change. As an example, the source tarball for `httr` is stored at https://cran.r-project.org/src/contrib/httr_1.3.1.tar.gz. However, once the next version of `httr` is released, the URL for

...778124 [src:slirp] slirp: ftbfs with GCC-5 Severity set to 'serious' from 'important' > severity 778125 serious Bug #778125 [src:solarpowerlog] solarpowerlog: ftbfs with GCC-5 Severity set to 'serious' from 'important' > severity 778128 serious Bug #778128 [src:spectools] spectools: ftbfs with GCC-5 Severity set to 'serious' from 'important' > severity 778129 serious Bug #778129 [src:squeak-plugins-scratch] squeak-plugins-scratch: ftbfs with GCC-5 Severity set to 'serious' from 'important' > severity 778130 serious Bug #778130...

...[src:solarpowerlog] solarpowerlog: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 778126 important Bug #778126 [src:soprano] soprano: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 778128 important Bug #778128 [src:spectools] spectools: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 778129 important Bug #778129 [src:squeak-plugins-scratch] squeak-plugins-scratch: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 778130 important Bug #7781...