From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/8] logrotate: replace fedorahosted.org SRC_URI with yoctoproject.org source
Date: Mon, 3 Apr 2017 12:09:52 +0300 [thread overview]
Message-ID: <957114aa-76e3-2eff-a5c1-9e7d4c75badc@linux.intel.com> (raw)
In-Reply-To: <CAHiDW_Ee=0nyBAsHkagd0hfS0orWBDu9ahh4k=2uQHR0tet2Fg@mail.gmail.com>
On 04/03/2017 11:30 AM, Jussi Kukkonen wrote:
> This is true, there's not that much in the repo itself to create trust.
> The major show of trust is here though:
> http://pkgs.fedoraproject.org/cgit/rpms/logrotate.git/commit/?id=9cb55142e51b82085d6c3136448c1f441454e351
> Fedora/Red Hat themselves changed to use this repo when the fedorahosted
> repos were EOL'd (see also Red Hat folks working on the github issues in
> January).
>
> If the release tarballs have been re-generated and the hashes no longer
> match, I'd still prefer modifying the recipe to use github (after
> manually diffing to make sure they are the same source release of
> course) but I can understand a differing viewpoint in this case.
>
> It would be good to mention the issue in the commit message, whichever
> way this is solved.
If github is not trustworthy, I'd say taking the tarball from Debian
should be good enough. Same applies to chkconfig - we just shouldn't
self-host these things, as that guarantees support headaches.
Alex
next prev parent reply other threads:[~2017-04-03 9:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 2:51 [PATCH 0/8] Remove all use of fedorahosted SRC_URI [YOCTO #11226] yin.thong.choong
2017-04-03 2:51 ` [PATCH 1/8] selftest/recipetool: replace fedorahosted.org SRC_URI with yoctoproject.org source yin.thong.choong
2017-04-03 2:51 ` [PATCH 2/8] xmlto: replace fedorahosted.org SRC_URI with pagure.io source yin.thong.choong
2017-04-03 2:51 ` [PATCH 3/8] libuser: " yin.thong.choong
2017-04-03 2:51 ` [PATCH 4/8] logrotate: replace fedorahosted.org SRC_URI with yoctoproject.org source yin.thong.choong
2017-04-03 7:46 ` Jussi Kukkonen
2017-04-03 7:53 ` Choong, Yin Thong
2017-04-03 8:30 ` Jussi Kukkonen
2017-04-03 9:09 ` Alexander Kanavin [this message]
2017-04-03 9:17 ` Burton, Ross
2017-04-03 11:00 ` Choong, Yin Thong
2017-04-03 11:13 ` Burton, Ross
2017-04-03 11:46 ` Jussi Kukkonen
2017-04-03 2:51 ` [PATCH 5/8] libnewt: replace fedorahosted.org SRC_URI with pagure.io source yin.thong.choong
2017-04-03 2:51 ` [PATCH 6/8] liberation-fonts: " yin.thong.choong
2017-04-03 2:51 ` [PATCH 7/8] chkconfig: replace fedorahosted.org SRC_URI with github.com source yin.thong.choong
2017-04-03 9:11 ` Alexander Kanavin
2017-04-03 9:12 ` Burton, Ross
2017-04-03 9:18 ` Choong, Yin Thong
2017-04-03 2:51 ` [PATCH 8/8] cronie: " yin.thong.choong
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=957114aa-76e3-2eff-a5c1-9e7d4c75badc@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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