[OpenWrt-Devel] Chaos Calmer 15.05-rc3
Cristian Morales Vega
cristian at samknows.com
Fri Jul 17 12:25:09 EDT 2015
On 17 July 2015 at 16:43, Jonas Gorski <jogo at openwrt.org> wrote:
> On 17.07.2015 16:16, Karl Palsson wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> Jonas Gorski <jogo at openwrt.org> wrote:
>>> On Thu, Jul 16, 2015 at 7:08 PM, Arturo Rinaldi <arturo at doghunter.org>
>>>> after running the git 'reset' command :
>>>> $ git reset --hard 171f0fd10830acd3259f7c229f1b65b95595f388
>>>> in the trunk directory returns me :
>>>> fatal: Could not parse object '171f0fd10830acd3259f7c229f1b65b95595f388'
>>>> is by any chance the right commit the one updating openssl to v1.0.2.d ?
>>> AFAICT the build isn't exactly one revision; it's r46163 + r46286 (the
>>> OpenSSL update to 1.0.2d), but none of the fixes between them.
>>> the feed revisions are:
>>> luci cf2e3f6c20dbdfdc3d8c4d4115cf9c533444e61f
>>> packages 7551321fab9b5676ae7824b18a51d53be2a48cb0
>>> mangement ab76d576a5cbcb01075757d5d8c6e1d83f1e9ffc
>>> routing f5eab926d75396d5e95d7b7eebcac34aab30f6f7
>>> telephony 6375e2a4aaba77aacc9b2cdea18e29fafe4cd2d5
>> Could the feeds and the repo maybe get tagged? you can put tag names in
>> feeds.conf with "url;tag_name" that would make some of this a little
> You can also define specific commits with "url^revision" ;)
What I don't understand is why there is so much interest in
replicating RC3. It makes sense to have a RC3 so there are binaries
and more people test it. But if you are going to build it yourself,
shouldn't you just use whatever is the latest commit in
git://git.openwrt.org/15.05/openwrt.git? That already has the tags for
the feeds (http://git.openwrt.org/?p=15.05/openwrt.git;a=blob_plain;f=feeds.conf.default;hb=HEAD).
Why to build a RC3 with the bugs that have already been solved and
will not be there in RC4/final?
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel