From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/glibc: switch to using the maintenance branch
Date: Sat, 28 Oct 2017 19:43:33 +0200 [thread overview]
Message-ID: <82d53666-e0e2-9e64-a0c7-1db7f452bcaa@gmail.com> (raw)
In-Reply-To: <20171028145058.GH3280@scaer>
Yann, All,
Le 28/10/2017 ? 16:50, Yann E. MORIN a ?crit?:
> Romain, All,
>
> On 2017-10-28 16:03 +0200, Romain Naour spake thusly:
>> Le 28/10/2017 ? 15:24, Yann E. MORIN a ?crit?:
>>> Romain, All,
>>>
>>> On 2017-10-28 14:00 +0200, Romain Naour spake thusly:
>>>> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>>> glibc upstream has ruled against doing regular point-releases, but they
>>>> do have a lot of interesting and important fixes for regressions and
>>>> security.
>>> [--SNIP--]
>>>> diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
>>>> index 0b8b440..d71137b 100644
>>>> --- a/package/glibc/glibc.mk
>>>> +++ b/package/glibc/glibc.mk
>>>> @@ -9,9 +9,16 @@ GLIBC_VERSION = arc-2017.09-eng010
>>>> GLIBC_SITE = $(call github,foss-for-synopsys-dwc-arc-processors,glibc,$(GLIBC_VERSION))
>>>> GLIBC_SOURCE = glibc-$(GLIBC_VERSION).tar.gz
>>>> else
>>>> -GLIBC_VERSION = 2.26
>>>> -GLIBC_SITE = $(BR2_GNU_MIRROR)/libc
>>>> -GLIBC_SOURCE = glibc-$(GLIBC_VERSION).tar.xz
>>>> +# Generate version string using:
>>>> +# git describe --match 'glibc-*' --abbrev=40 origin/release/MAJOR.MINOR/master
>>>> +GLIBC_VERSION = glibc-2.26-73-g4b692dffb95ac4812b161eb6a16113d7e824982e
>>>> +# Upstream doesn't officially provide an https download link.
>>>> +# There is one (https://sourceware.org/git/glibc.git) but it's not reliable,
>>>> +# sometimes the connection time out. So use a git mirror using https.
>>>> +# Before bumping the version, first verify that the sha1 really
>>>> +# exists on the git mirror tree.
>>>
>>> No, I really meant "exists in the official git tree".
>>>
>>> The idea is that we use the gthub mirror, but it is not official. So
>>> nothing guarantees us that it only contains legit commits.
>>
>> bminor seems really used as mirror of the official repo, so no new commit appear
>> from here.
>
> Yet, it really is advertised as an "Unofficial mirror of sourceware
> glibc repository." As such, we can't trust it at all, whatever the
> current situation is.
>
>>> So, we want to get the version from the *official* git tree, and only do
>>> the download from the mirror.
>>
>> Right obviously, but remember that the github mirror is sync each day from the
>> upstream repo. So if you use a sha1 from the upstream repo (ex: stable branch
>> HEAD), you have to make sure that the same commit is also present in the git mirror.
>>
>> I guess we should extend the comment for both cases.
>
> What about:
>
> # When updating the version, check it on the official repository;
> # *NEVER* decide on a version string by looking at the mirror.
> # Then check that the mirror has been synced already (happens once
> # a day.)
I'm ok with this comment.
Should I send a v4 or it can be fixed while applied ?
Best regards,
Romain
>
> Regards,
> Yann E. MORIN.
>
>> Best regards,
>> Romain
>>
>>>
>>>> +GLIBC_SITE = https://github.com/bminor/glibc.git
>>>> +GLIBC_SITE_METHOD = git
>>>> endif
>>>>
>>>> GLIBC_SRC_SUBDIR = .
>>>> --
>>>> 2.9.5
>>>>
>>>
>>
>
prev parent reply other threads:[~2017-10-28 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 12:00 [Buildroot] [PATCH v3] package/glibc: switch to using the maintenance branch Romain Naour
2017-10-28 13:24 ` Yann E. MORIN
2017-10-28 14:03 ` Romain Naour
2017-10-28 14:50 ` Yann E. MORIN
2017-10-28 17:43 ` Romain Naour [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82d53666-e0e2-9e64-a0c7-1db7f452bcaa@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox