All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo
Date: Mon, 6 Jul 2015 10:40:05 +0200	[thread overview]
Message-ID: <20150706084005.GA8098@ad.chargestorm.se> (raw)
In-Reply-To: <20150706051954.GF6806@ulm-bmuc496424.bmw-carit.de>

* Clemens Lang <clemens.lang@bmw-carit.de> [150706 07:24]:
> On Fri, Jun 26, 2015 at 09:31:14AM +0100, Burton, Ross wrote:
> > Github also can and will regenerate these tarballs whenever it feels
> > like it, so you'll need to periodically update the checksums.
> > Obviously as existing developers will tend to have the tarballs cached
> > locally, it can be a while before this failure is reported back.

> While that does happen from time to time it's pretty rare. I see maybe
> one case of this every couple of months in MacPorts. 

Well, we've tried this before, and the changed checksums is causing us
all a lot of problems.

> Additionally, after a while the checksums generally change back again
> in almost all cases.

Well, then that's almost twice as bad... That means that once the
changed checksum has been detected and patches been submitted, it's
likely to change again... :(

> So, yes, this brings its own set of problems, but is still a worthwhile
> improvement over the current situation IMO.

Well, no. Tarballs that has changing checksums is not acceptable. It's
going to break new builds, new autobuilders, etc, and just cause
everyone unacceptable pain.

It's going to give a lot of us a huge support nightmare again...

If the checksums can be guaranteed to be stable, then, yes, such a
change can be looked upon.

Shallow clones is in this case a lot more likely to be usefull, though,
implementing that might have a few issues on it's own...

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB


  reply	other threads:[~2015-07-06  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  4:16 [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo Jon Szymaniak
2015-06-26  8:31 ` Burton, Ross
2015-06-26  9:07   ` Gary Thomas
2015-06-26  9:09     ` Burton, Ross
2015-06-26 14:16   ` Jon Szymaniak
2015-06-26 14:19     ` Burton, Ross
2015-06-26 14:42       ` Jon Szymaniak
2015-06-26 14:46         ` Burton, Ross
2015-07-05 19:19     ` Petter Mabäcker
2015-07-06  5:19   ` Clemens Lang
2015-07-06  8:40     ` Anders Darander [this message]
2015-07-06  9:48       ` Nikolay Dimitrov
2015-07-06 10:58         ` Paul Eggleton
2015-07-09 20:13           ` Andrei Gherzan
2015-07-10  8:47             ` Nikolay Dimitrov

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=20150706084005.GA8098@ad.chargestorm.se \
    --to=anders@chargestorm.se \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.