search for: tarbal

...????????? (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw> wrote: > > > > > Hi Pawel, > > > > > > PTX already be replaced with NVPTX. However, PTX subdirectory > > > still sit in lib/Target in 3.2 release. Do you think update the > > > release tarball is a good idea? Also could you remove it from > > > the trunk? > > > > Please do not, under no circumstances, change the 3.2 release tarballs at this point. They are mirrored around the world now with cryptographic hashes and signatures. Changing them will break things for ma...

This is not specifically a CentOS question, but I am creating RPMS for CentOS 6 from some CRAN tarballs. I run R2spec -s tarball to create a spec file, and most of the time it works ok, but sometimes (RPostgresSQL, Rcpp for example) the package has test or example programs that start with #!/usr/bin/r with lower case r, and the resulting package then winds up with a dependency on /usr/bin/r, w...

...>>> <chenwj at iis.sinica.edu.tw> wrote: >>> >>>> Hi Pawel, >>>> >>>> PTX already be replaced with NVPTX. However, PTX subdirectory >>>> still sit in lib/Target in 3.2 release. Do you think update >>>> the release tarball is a good idea? Also could you remove it >>>> from the trunk? >>> >>> Please do not, under no circumstances, change the 3.2 release >>> tarballs at this point. They are mirrored around the world now >>> with cryptographic hashes and signatures. Ch...

Hi, Where''s the master repository for downloading open source Xen source tarballs? In the past, I''ve always just gone to the xensource web page, clicked on download, and then followed the "Open Source Xen" link. However, this link seems to no longer be there. I found a Univ of Cambridge download page ( http://www.cl.cam.ac.uk/research/srg/netos/xen/downl...

On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > What you're probably missing is that 3.8.1 is made in release_38 > branch. So, everything is there and already mirrored. > > Source tarballs will be available upon the release. Which are just coming, now that final has been tested successfully. :) They'll be announced in the list and available here: http://llvm.org/releases/download.html#3.8.1 cheers, --renato

...t linaro.org> wrote: > On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> What you're probably missing is that 3.8.1 is made in release_38 >> branch. So, everything is there and already mirrored. >> >> Source tarballs will be available upon the release. > > Which are just coming, now that final has been tested successfully. :) > > They'll be announced in the list and available here: > > http://llvm.org/releases/download.html#3.8.1 > Thanks you both for your answers. Can you or Tom (a...

....sinica.edu.tw> wrote: > >>> > >>>> Hi Pawel, > >>>> > >>>> PTX already be replaced with NVPTX. However, PTX subdirectory > >>>> still sit in lib/Target in 3.2 release. Do you think update > >>>> the release tarball is a good idea? Also could you remove it > >>>> from the trunk? > >>> > >>> Please do not, under no circumstances, change the 3.2 release > >>> tarballs at this point. They are mirrored around the world now > >>> with cryptographic...

...s Hahnfeld <hahnjo at hahnjo.de> wrote: > On 2018-08-27 09:44, Sedat Dilek wrote: >> >> Yeah, I see. >> You have an unusual development process seen from my POV. > > > GNOME does the same, to pick one example: > https://wiki.gnome.org/ThreePointTwentynine > Tarballs are due on Monday, official release and announcement are on > Wednesday. > >> IMHO you can provide the tarballs before the "binaries" are uploaded >> which means "prebuilt binaries". >> That could increase the quality of developing when different arch/o...

Due to a packaging error, the tarball released on Friday night did not have a version number embedded in it, which results in various strange build errors and other odd behavior. The tarball on the FTP servers has been updated to correct this situation. Sorry for the inconvenience :-)

Pawel, We all understand that you're pretty new to release process, etc., but I think you should understand the implications of your actions. You just created a lot of harm for really huge pile of users - the ones who downloads the tarball via some automated build system and rely on the known good checksum. This includes, but not limited to to the users of FreeBSD, Gentoo, etc. Even worse, you did this silently. Without any announcement, with any e-mail to llvm-dev, etc. And all this at the same time when people do wide announcemen...

...is.sinica.edu.tw> wrote: > >>> > >>>> Hi Pawel, > >>>> > >>>> PTX already be replaced with NVPTX. However, PTX subdirectory > >>>> still sit in lib/Target in 3.2 release. Do you think update > >>>> the release tarball is a good idea? Also could you remove it > >>>> from the trunk? > >>> > >>> Please do not, under no circumstances, change the 3.2 release > >>> tarballs at this point. They are mirrored around the world now > >>> with cryptographic has...

Am 05.09.2015 um 10:18 schrieb peter dalgaard: > >> On 05 Sep 2015, at 08:28 , Rainer Hurling <rhurlin at gwdg.de> wrote: >> >> Is there any reason that the R-devel tarball at [1] stucks on r69202? >> >> It seems, that newer R-devel versions are now published on >> /pub/misc/cran/src/base-prerelease, for example at >> http://ftp5.gwdg.de/pub/misc/cran/, but without an R-devel.tar.gz >> tarball ... >> >> Is this intended? Any...

Is there any reason that the R-devel tarball at [1] stucks on r69202? It seems, that newer R-devel versions are now published on /pub/misc/cran/src/base-prerelease, for example at http://ftp5.gwdg.de/pub/misc/cran/, but without an R-devel.tar.gz tarball ... Is this intended? Any clarification would be appreciated. Thanks and greetings, Ra...

Greetings, During the past week, there have been some requests for nightly tarballs to help making testing new Asterisk code easier. There was some debate as to whether they would be useful. The reason that they may not be useful is because you can get equivalent access to new code just by accessing the subversion repository directly. However, for one reason or another, some...

On 6/5/2015 3:09 AM, Peter wrote: > On 06/04/2015 07:49 AM, Tony Schreiner wrote: >> I run R2spec -s tarball to create a spec file, and most of the time it >> works ok, but sometimes (RPostgresSQL, Rcpp for example) the package has >> test or example programs that start with >> >> #!/usr/bin/r >> >> with lower case r, and the resulting package then winds up with a &g...

...:34 PM, Phil Wyett wrote: > On Tue, 2016-12-13 at 14:16 -0800, Alice Wonder wrote: >> I'm getting spec files from centos git which is really convenient when >> the related source is easy to find. But some things - e.g. from a spec file >> >> # How to create the source tarball: >> # >> # git clone git://git.fedorahosted.org/git/python-rhsm.git/ >> # cd client/python-rhsm >> # tito build --tag python-rhsm-$VERSION-$RELEASE --tgz >> >> Never used tito before, so I install it and try, and rather than giving >> me the source package...

Hi,all: I've couple of large tarballs such as www.tar and images.tar. Is it possible to extract a single file or a list of files from a large tarball such as images.tar instead of extracting the entire tarball? How do I extract specific files under Linux / UNIX operating systems? Thanks in advance ~~ -------------- next part ----...

...wrote: >>>>> >>>>>> Hi Pawel, >>>>>> >>>>>> PTX already be replaced with NVPTX. However, PTX >>>>>> subdirectory still sit in lib/Target in 3.2 release. Do >>>>>> you think update the release tarball is a good idea? Also >>>>>> could you remove it from the trunk? >>>>> >>>>> Please do not, under no circumstances, change the 3.2 >>>>> release tarballs at this point. They are mirrored around >>>>> the world now with c...

Hi Tom, [1] does not list any 3.9.1rc2 pre-release tarballs, can you please upload? Thanks in advance. Regards, - Sedat - [1] http://www.llvm.org/pre-releases/

Yeah, I see. You have an unusual development process seen from my POV. IMHO you can provide the tarballs before the "binaries" are uploaded which means "prebuilt binaries". That could increase the quality of developing when different arch/os maintainers give their OK. But for 7.0.0rc1 I see only prebuilt binaries for... * macOS * FreeBSD10 AMD64 * Windows (32-bit) * Windows (64-...