Re: What happened to branches other than dragonfly-2010Q3
No, these tarballs will just put the existing files in place. The normal quarterly branches will work just as well. The ones at netbsd.org will maybe have a CVS directory, and downloading from Github (I assume) gets you a .git directory in there. On Sat, Aug 20, 2011 at 3:41 AM, Siju George wrote: > On Sat, Aug 20, 2011 at 1:38 AM, Justin Sherrill > wrote: >> There's tarballs (or bzip, etc.) for recent branches and >> pkgsrc-current at ftp.netbsd.org. For example >> >> ftp://ftp.netbsd.org/pub/pkgsrc/pkgsrc-2011Q2/ >> >> Plus Matthias pointed out you can grab from github too. >> > > Thanks :-) Just one question will those tar ball have dragonfly-* branches? > > --Siju >
Re: What happened to branches other than dragonfly-2010Q3
On Sat, Aug 20, 2011 at 1:38 AM, Justin Sherrill wrote: > There's tarballs (or bzip, etc.) for recent branches and > pkgsrc-current at ftp.netbsd.org. For example > > ftp://ftp.netbsd.org/pub/pkgsrc/pkgsrc-2011Q2/ > > Plus Matthias pointed out you can grab from github too. > Thanks :-) Just one question will those tar ball have dragonfly-* branches? --Siju
Re: What happened to branches other than dragonfly-2010Q3
There's tarballs (or bzip, etc.) for recent branches and pkgsrc-current at ftp.netbsd.org. For example ftp://ftp.netbsd.org/pub/pkgsrc/pkgsrc-2011Q2/ Plus Matthias pointed out you can grab from github too. On Fri, Aug 19, 2011 at 12:40 PM, Siju George wrote: > On Fri, Aug 19, 2011 at 6:32 PM, Justin Sherrill > wrote: >> I've seen a number of people say they get errors when downloading >> dragonfly pkgsrc via git. I don't know what's causing it, but 2 >> workaround for now would be to either grab it the old-fashioned way >> via CVS: (assuming tcsh) >> > > Also why not consider providing a pkgsrc.tgz snapshot for download > once a week or so? > It would be easier to pull through http/ftp since it can be resumed? > > I said because I guess it is what OpenBSD does > > http://ftp.openbsd.org/pub/OpenBSD/snapshots/ > > Is that going to be too difficult to automate? Or is there already > such setup some where? > > Thanks :-) > > --Siju >
Re: What happened to branches other than dragonfly-2010Q3
On Freitag, 19. August 2011 at 18:40, Siju George wrote: > > Also why not consider providing a pkgsrc.tgz snapshot for download > once a week or so? > It would be easier to pull through http/ftp since it can be resumed? That would be redundant now that there's https://github.com/jsonn/pkgsrc – Github already offers automatic .tar.gz and .zip snapshots of all branches. -m.
Re: What happened to branches other than dragonfly-2010Q3
On Fri, Aug 19, 2011 at 6:32 PM, Justin Sherrill wrote: > I've seen a number of people say they get errors when downloading > dragonfly pkgsrc via git. I don't know what's causing it, but 2 > workaround for now would be to either grab it the old-fashioned way > via CVS: (assuming tcsh) > Also why not consider providing a pkgsrc.tgz snapshot for download once a week or so? It would be easier to pull through http/ftp since it can be resumed? I said because I guess it is what OpenBSD does http://ftp.openbsd.org/pub/OpenBSD/snapshots/ Is that going to be too difficult to automate? Or is there already such setup some where? Thanks :-) --Siju
Re: What happened to branches other than dragonfly-2010Q3
On Freitag, 19. August 2011 at 15:02, Justin Sherrill wrote: > > I'm curious to see if git chokes when downloading from a different source... In this case it definitely will – the repos were created by completely different scripts and ways (they convert CVS -> Fossil -> git AFAIK), so the commit IDs won't match. In general, adding another clone of the *same* repo as a git remote works fine (e.g. you have a clone of dragonfly.git on your home server, clone that on your workstation, then add the git.dragonflybsd.org or leaf repos). But the NetBSD pkgsrc git mirror and the DragonFly git mirror have to be considered completely separate. -m.
Re: What happened to branches other than dragonfly-2010Q3
I've seen a number of people say they get errors when downloading dragonfly pkgsrc via git. I don't know what's causing it, but 2 workaround for now would be to either grab it the old-fashioned way via CVS: (assuming tcsh) setenv CVSROOT anon...@anoncvs.netbsd.org:/cvsroot setenv CVS_RSH ssh cd /usr cvs -q checkout -rpkgsrc-2011Q1 -P pkgsrc Or switch to Joerg Sonnenberger's git : (warning, this is off the top of my head; untested) in /usr/pkgsrc: git remote add github https://github.com/jsonn/pkgsrc.git git fetch github git branch pkgsrc-2011Q1 github/pkgsrc-2011Q1 git checkout pkgsrc-2011Q1 git pull I'm curious to see if git chokes when downloading from a different source... On Fri, Aug 19, 2011 at 7:27 AM, Siju George wrote: > Hi, > > When I list remote branches in the newly checked out repository it show only > > dfly-blkbuild# git branch -r > origin/dragonfly-2010Q3 > origin/dragonfly-master > origin/master > > but in an older pkgsrc it shows > > dfly-bkpsrv# git branch -r > origin/dragonfly-2010Q3 > origin/dragonfly-master > origin/master > origin/pkgsrc-2010Q1 > origin/pkgsrc-2010Q2 > origin/pkgsrc-2010Q3 > origin/pkgsrc-2010Q4 > origin/pkgsrc-2011Q1 > > How Do I get origin/pkgsrc-2010Q1 in the new one? > > The new one gave this error too > > dfly-blkbuild# git pull > From git://git.dragonflybsd.org/pkgsrcv2 > * [new branch] dragonfly-master -> origin/dragonfly-master > * [new branch] master -> origin/master > Bus error (core dumped) > > > Thanks > > --Siju >
