<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-devtools/dosfstools/dosfstools_2.11.bb, branch nanbield</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=nanbield</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=nanbield'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2017-03-07T20:05:31+00:00</updated>
<entry>
<title>recipes: Move out stale GPLv2 versions to a seperate layer</title>
<updated>2017-03-07T20:05:31+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2017-03-02T12:04:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2345af9b4829ed3eed5abf60f2483055649f8af7'/>
<id>urn:sha1:2345af9b4829ed3eed5abf60f2483055649f8af7</id>
<content type='text'>
These are recipes where the upstream has moved to GPLv3 and these old
versions are the last ones under the GPLv2 license.

There are several reasons for making this move. There is a different
quality of service with these recipes in that they don't get security
fixes and upstream no longer care about them, in fact they're actively
hostile against people using old versions. The recipes tend to need a
different kind of maintenance to work with changes in the wider ecosystem
and there needs to be isolation between changes made in the v3 versions
and those in the v2 versions.

There are probably better ways to handle a "non-GPLv3" system but right
now having these in OE-Core makes them look like a first class citizen
when I believe they have potential for a variety of undesireable issues.

Moving them into a separate layer makes their different needs clearer, it
also makes it clear how many of these there are. Some are probably not
needed (e.g. mc), I also wonder whether some are useful (e.g. gmp)
since most things that use them are GPLv3 only already. Someone could
now more clearly see how to streamline the list of recipes here.

I'm proposing we mmove to this separate layer for 2.3 with its future
maintinership and testing to be determined in 2.4 and beyond.

(From OE-Core rev: 19b7e950346fb1dde6505c45236eba6cd9b33b4b)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dosfstools_2.11: fix build following removal of -e from EXTRA_OEMAKE</title>
<updated>2016-02-28T11:33:06+00:00</updated>
<author>
<name>Andre McCurdy</name>
<email>armccurdy@gmail.com</email>
</author>
<published>2016-02-26T05:24:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7651342ac11c0edd638e81e64067b03192b469de'/>
<id>urn:sha1:7651342ac11c0edd638e81e64067b03192b469de</id>
<content type='text'>
Also misc formatting tweaks to align with v3.0.28 recipe and remove
BBCLASSEXTEND = "native" (native builds should always use the GPLv3
recipe).

(From OE-Core rev: 375c26ce229cd9dc90b5e7c4b8e6d52d832b606e)

Signed-off-by: Andre McCurdy &lt;armccurdy@gmail.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dosfstools: Fix build with musl</title>
<updated>2015-04-21T06:20:24+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2015-04-16T02:00:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c94d444c79b5389dc28c6e3f2ef8c2ef2ee6f830'/>
<id>urn:sha1:c94d444c79b5389dc28c6e3f2ef8c2ef2ee6f830</id>
<content type='text'>
We need to pass _GNU_SOURCE and include fcntl.h

Change-Id: Ice0597ddac3b275400880d85793ece4b300bec9b
(From OE-Core rev: 022a96c7a396bd6bbf499984f4ea8639111fe3b7)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dosfstools: fix SRC_URI</title>
<updated>2015-02-03T14:53:52+00:00</updated>
<author>
<name>Robert Yang</name>
<email>liezhi.yang@windriver.com</email>
</author>
<published>2015-01-28T02:32:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b0a28c085addd93f6361a00c1bc6936348feaa04'/>
<id>urn:sha1:b0a28c085addd93f6361a00c1bc6936348feaa04</id>
<content type='text'>
Fixed:
WARNING: Failed to fetch URL ftp://ftp.uni-erlangen.de/pub/Linux/LOCAL/dosfstools/dosfstools-2.11.src.tar.gz, attempting MIRRORS if available

And add a HOMEPAGE for it, there is no dosfstools 2.11 on its official
page (but 3.x).

(From OE-Core rev: cba73a598abc396fae4fb582be98fc04cb2a580f)

Signed-off-by: Robert Yang &lt;liezhi.yang@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dosfstools: place files in /sbin, not in /usr/sbin</title>
<updated>2014-10-10T15:44:32+00:00</updated>
<author>
<name>Enrico Scholz</name>
<email>enrico.scholz@sigma-chemnitz.de</email>
</author>
<published>2014-10-07T12:07:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0cac199068a3c0614034989538b264beef15e665'/>
<id>urn:sha1:0cac199068a3c0614034989538b264beef15e665</id>
<content type='text'>
systemd expects fsck programs to be located in /sbin and fails for
dosfstools with

| Checking was requested for ..., but /sbin/fsck.vfat cannot be used: No such file or directory

Other fsck programs (e.g. ext4) are located in /sbin already so move
vfat programs into this directory too.

(From OE-Core rev: fa579cb243b8441d95e6c129e07d9e141f808539)

Signed-off-by: Enrico Scholz &lt;enrico.scholz@sigma-chemnitz.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Don't set DESCRIPTION to the same value as SUMMARY</title>
<updated>2013-12-03T17:45:52+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-11-25T18:50:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=46533029401655872a1905c073a6cbb4e7b95333'/>
<id>urn:sha1:46533029401655872a1905c073a6cbb4e7b95333</id>
<content type='text'>
Setting DESCRIPTION to the same value as SUMMARY doesn't do anything,
since the value of DESCRIPTION will be derived from SUMMARY if not
specified.

(From OE-Core rev: e1e888585c84175580ad822d4a6c93f62e5ce16c)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dosfstools: really compile supporting large files</title>
<updated>2013-03-29T10:40:55+00:00</updated>
<author>
<name>Joe Slater</name>
<email>jslater@windriver.com</email>
</author>
<published>2013-03-25T20:49:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7698f261496c2f1cd7c86805836e11b36f5d9339'/>
<id>urn:sha1:7698f261496c2f1cd7c86805836e11b36f5d9339</id>
<content type='text'>
Makefile in the package tries to set _FILE_OFFSET_BITS=64,
but we clobber that with our CFLAGS, so we add it in
the recipe.

[CQID: 409915]

(From OE-Core rev: ac904b9e10ec9641686bc35dcf200b9b855899b1)

Signed-off-by: Joe Slater &lt;jslater@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Add missing SUMMARY fields to various recipes</title>
<updated>2011-12-19T09:29:16+00:00</updated>
<author>
<name>Scott Garman</name>
<email>scott.a.garman@intel.com</email>
</author>
<published>2011-12-18T23:06:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6ea9711c490465ac5f1ea241a5777c345a9c9c0e'/>
<id>urn:sha1:6ea9711c490465ac5f1ea241a5777c345a9c9c0e</id>
<content type='text'>
This adds the SUMMARY field to the following recipes which were
missing it:

* dosfstools
* grep
* icu
* libevent
* libnfsidmap
* qemu-helper-nativesdk

(From OE-Core rev: e8c194a627e091ef9da3b7fa83ea3897bd283d9e)

Signed-off-by: Scott Garman &lt;scott.a.garman@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dosfstools: fix populated image creation with dirs</title>
<updated>2011-12-15T14:36:24+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2011-12-13T23:26:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8413a9b4e80b65e0ad0ddac659cc6abbd305ba35'/>
<id>urn:sha1:8413a9b4e80b65e0ad0ddac659cc6abbd305ba35</id>
<content type='text'>
This fixes bug: [YOCTO #1783]

Fix populated image creation. Earlier subdirectories support
was broken, and files can only be placed in the root directory.
Now directory hirarchy is supported in the image. Also support
for long names is extended to directory names.

There are some outstanding issues as documented in the patch
header, these issues can be worked around by running
dosfsck tool after populated image creation. The dosfsck tool
is also part of this package.

(From OE-Core rev: 2de8f008b304017de7ca116aa79ef778ab40362d)

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>dosfstools: Add patch to disable fat32 autoselection and behave as 2.10</title>
<updated>2011-12-13T14:06:40+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-12-13T14:01:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=995a09e7bf3aee7853b17a7757cbf6cbc4edf6b8'/>
<id>urn:sha1:995a09e7bf3aee7853b17a7757cbf6cbc4edf6b8</id>
<content type='text'>
It appears msdos image population and fat32 images are incompatible.
This reverts to the 2.10 behaviour of defaulting to fat16 instead of
using fat32 for large images, allowing image generation to work
correctly. This is a workaround and a proper fix is really needed.

(From OE-Core rev: c2de8d41236cf1293db9e6c69d69e8d14f55ffd1)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
