[Buildroot] [PATCH] squashfs: update site to git.kernel.org

[Buildroot] [PATCH] squashfs: update site to git.kernel.org

[Matt Weber]

From: Atul Singh <atul.singh.mandla@rockwellcollins.com>

squashfs-tools development has been moved to git.kernel.org from
Sourceforge.

Signed-off-by: Atul Singh <atul.singh.mandla@rockwellcollins.com>
Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com>
---
 package/squashfs/squashfs.hash | 4 ++--
 package/squashfs/squashfs.mk   | 5 ++---
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/package/squashfs/squashfs.hash b/package/squashfs/squashfs.hash
index e308089..eb456be 100644
--- a/package/squashfs/squashfs.hash
+++ b/package/squashfs/squashfs.hash
@@ -1,2 +1,2 @@
-# Locally computed:
-sha256  0d605512437b1eb800b4736791559295ee5f60177e102e4d4ccd0ee241a5f3f6  squashfs4.3.tar.gz
+# Locally computed
+sha256	e807202ab4dcfeea214df49d3a728b9a85644a7e7262fc6fcd875a0def99d4ed	squashfs-9c1db6d13a51a2e009f0027ef336ce03624eac0d.tar.gz
diff --git a/package/squashfs/squashfs.mk b/package/squashfs/squashfs.mk
index cdeb9c8..9c8841a 100644
--- a/package/squashfs/squashfs.mk
+++ b/package/squashfs/squashfs.mk
@@ -4,9 +4,8 @@
 #
 ################################################################################
 
-SQUASHFS_VERSION = 4.3
-SQUASHFS_SOURCE = squashfs$(SQUASHFS_VERSION).tar.gz
-SQUASHFS_SITE = http://downloads.sourceforge.net/project/squashfs/squashfs/squashfs$(SQUASHFS_VERSION)
+SQUASHFS_VERSION = 9c1db6d13a51a2e009f0027ef336ce03624eac0d
+SQUASHFS_SITE = git://git.kernel.org/pub/scm/fs/squashfs/squashfs-tools.git
 SQUASHFS_LICENSE = GPLv2+
 SQUASHFS_LICENSE_FILES = COPYING
 SQUASHFS_MAKE_ARGS = XATTR_SUPPORT=1
-- 
1.9.1

[Buildroot] [PATCH] squashfs: update site to git.kernel.org

[Thomas Petazzoni]

Hello,

On Wed, 27 Jul 2016 16:32:18 -0500, Matt Weber wrote:
> From: Atul Singh <atul.singh.mandla@rockwellcollins.com>
> 
> squashfs-tools development has been moved to git.kernel.org from
> Sourceforge.

Yeah, but they haven't made any release since the last one available
from sourceforge. Are they planning on doing a new release? What is the
motivation from moving from a stable release to some seemingly random
Git commit?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH] squashfs: update site to git.kernel.org

[Matthew Weber]

Thomas,

On Thu, Jul 28, 2016 at 3:08 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Wed, 27 Jul 2016 16:32:18 -0500, Matt Weber wrote:
> > From: Atul Singh <atul.singh.mandla@rockwellcollins.com>
> >
> > squashfs-tools development has been moved to git.kernel.org from
> > Sourceforge.
>
> Yeah, but they haven't made any release since the last one available
> from sourceforge. Are they planning on doing a new release? What is the
> motivation from moving from a stable release to some seemingly random
> Git commit?
>
>
We pulled in that latest hash to fix a threading issue that we were seeing
on our large build machines. When creating images with 64 cores we would
sometimes get corrupted images that would fail to boot.


> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>



-- 
Matthew L Weber / Pr Software Engineer
Airborne Information Systems / Security Systems and Software / Secure
Platforms
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
www.rockwellcollins.com

Note: Any Export License Required Information and License Restricted Third
Party Intellectual Property (TPIP) content must be encrypted and sent to
matthew.weber at corp.rockwellcollins.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160728/6164d430/attachment.html>

[Buildroot] [PATCH] squashfs: update site to git.kernel.org

[Thomas Petazzoni]

Hello,

On Thu, 28 Jul 2016 07:59:46 -0500, Matthew Weber wrote:

> > Yeah, but they haven't made any release since the last one available
> > from sourceforge. Are they planning on doing a new release? What is the
> > motivation from moving from a stable release to some seemingly random
> > Git commit?
> >  
> We pulled in that latest hash to fix a threading issue that we were seeing
> on our large build machines. When creating images with 64 cores we would
> sometimes get corrupted images that would fail to boot.

OK. Exactly the type of explanation that would have been good to have
in the commit log :-)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com