Date: Wed, 20 Nov 2019 14:28:16 -0800 From: Julian Elischer <julian@freebsd.org> To: Mark Millard <marklmi@yahoo.com>, bob prohaska <fbsd@www.zefox.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Reverting -current by date. Message-ID: <31c4b575-1b5c-6219-2c44-f263dcfbb192@freebsd.org> In-Reply-To: <54416FF2-B542-4EDB-B371-B53E4F17731A@yahoo.com> References: <54416FF2-B542-4EDB-B371-B53E4F17731A.ref@yahoo.com> <54416FF2-B542-4EDB-B371-B53E4F17731A@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/20/19 1:51 PM, Mark Millard wrote: > Bob P. wrote for an aarch64 context: > >> From time to time it would be handy to revert freebsd-current to >> an older, well-behaved revision. >> >> Is there a mechanism for identifying revision numbers that >> will at least compile and boot, by date? >> >> In my case buildworld seems to be markedly slower than, say, >> six months ago. Maybe it's hardware, maybe something else. Is >> there a way to pick a revision number to revert to, that's >> better than merely guessing? > You can explore the history of installable world/kernel materials > at places matching the pattern: > > https://artifact.ci.freebsd.org/snapshot/head/r*/arm64/aarch64/* I find that https://svnweb.freebsd.org/base/ is good enough to allow exploration of revisions. If you add a revision in the given field you will only see revs show up that are older than that. > > Some r* will exist without having arm64/aarch64 material but having > mateirals for other platforms. The * matches a svn revision number. > > These are from ci.freebsd.org builds, not the announced/released > snaphots. These go back a long ways. ci.freebsd.org does not try > to build every svn revision. (It does not build that fast relative > to svn updating.) > > I sometimes use these for approximate bisection without building. > > The https://artifact.ci.freebsd.org/snapshot/head/r*/arm64/aarch64/* > materials are compressed tar archives (*.txz) and a MANIFEST file. > bsdinstall uses these files, although I've at times done basic > testing activities based on just manually expanding the tars. > > (The materials do not span u-boot or other such and need to have > file system(s) to expand into.) > > (From a different message:) >> I hoped for a more mechanical approach. For example, snapshots are >> generated from time to time. Presumably, they're vetted in some way >> and knowing what revisions made it to the snapshot stage might be a >> starting point. The snapshot server does not appear to contain that >> information for earlier offerings. > Snapshots are not vetted as far as I know --and sometimes do not boot > in contexts that I've tried. This applies both to artifact.ci.freebsd.org > materials and the announced snapshots put under > https://download.freebsd.org/ftp/snapshots/ . > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31c4b575-1b5c-6219-2c44-f263dcfbb192>