| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Systemd requires a version >= 2.27.1, and 2.28 also includes
various btrfs fixes.
For more infromation see the release notes:
http://git.baserock.org/cgit/delta/util-linux.git/tree/Documentation/releases/v2.28-ReleaseNotes
Change-Id: If6d44eb3d06eb7f511b9a5b6ea2166a7cf0af468
|
|
|
|
| |
Change-Id: Ie9a866a7b9aa29e46986aa62fb0816e0bca71bf8
|
|
|
|
|
|
|
| |
Note: Migration scripts live now in:
http://git.baserock.org/cgit/baserock/baserock/spec.git
Change-Id: Ica4fd12d96e563e5195172318d2d65847266146f
|
|
|
|
|
|
|
|
|
|
|
| |
Also, switch to using upstream v2.4.6 tag of GNU Libtool.
This is easy to do once definitions V8 is merged -- no more
.gitmodules patching!
Tested by building a minimal-system-x86_64
Change-Id: If2f01507d364245736727699a33225ce929655dc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This contains commit 9831e92bfa833ee9c0ce464bbc2f941ae6c2698d which
removes the path_name() function. That fixes a remote-code execution
security hole, described in CVE-2016-2315 and CVE-2016-2324.
I have read in some places that 2.7.1 and later are not vulnerable,
but I've not been able to prove that, nor find proof. At time of writing
the Debian advisory doesn't show that 2.7.1 and later are safe, only
2.8.0-rc2:
https://security-tracker.debian.org/tracker/CVE-2016-2324
See also:
https://ma.ttias.be/remote-code-execution-git-versions-client-server-2-7-1-cve-2016-2324-cve-2016-2315/
Change-Id: I8948b295030f2f498780777aa62a54f2337518b5
|
|
|
|
| |
Change-Id: Ib445f6589cfed3d9b430a70415d92d42e11ff36e
|
|
|
|
|
|
| |
This is already done in DEFAULT 'configure-commands'
Change-Id: I43b29165a42c9951c17647dbba935135dae6f633
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This release fixes:
CVE-2013-2877
CVE-2014-0191
CVE-2014-3660
CVE-2015-1819
CVE-2015-5312
CVE-2015-7497
CVE-2015-7498
CVE-2015-7499
CVE-2015-7500
CVE-2015-7941
CVE-2015-7942
CVE-2015-8035
CVE-2015-8242
Change-Id: I0b156764126261b9c02f27f561ec646527fee49d
|
|
|
|
| |
Change-Id: Ieb0fdd4a0cba09296e3316fefd235b6f9e1bfd3a
|
|
|
|
| |
Change-Id: Ide3893f85f52070fe8ce66424ee1463951006004
|
|
|
|
| |
Change-Id: I425f6abc94c0dfd9764faf7024454f7de64053e8
|
|
|
|
| |
Change-Id: I8a463b2dcef83f4baffd82ecba92e0ffb4fc3e9a
|
|
|
|
|
|
| |
linux-user-chroot also uses it
Change-Id: I0f8874e18e93d79a66a85ea4db0684fca2a149f3
|
|
|
|
|
|
|
|
|
|
|
| |
This patch uses the new upstream delta based on the 2015 default
certificates used by debian, and drops the delta which was used
to force an update-ca-certificates invokation at make install time.
Now we no longer run the update-ca-certificates at make install time
and only run it at system-integration time.
Change-Id: I0de520d64f45c64aa3d213b9099211b5ab8a50dd
|
|
|
|
|
|
|
|
|
|
|
| |
Without this, compilation of libcurl succeeds but does not
have a default path to search for CA certs at runtime, and
most libcurl depending software does not provide it's own
certificates or set the default path.
Also removed build dependency on ca-certificates.
Change-Id: I5f3d33858e3fe65d57d93a38397239c1a421e69a
|
|
|
|
|
|
|
|
|
|
| |
WebKit requires at least 2.8.0, upgrading to release tag v2.9.1.
There is a 2.9.2 release at this time also, however it fails
to pass configure so let's stick with 2.9.1, the latest release
tag which actually builds.
Change-Id: I20d7cf39431d34be4928850a97d264c3e2e4cbbc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit renames git in core to git-minimal and adds a git chunk into
devtools, the git chunk will replace git-minimal and will build and
install git's man pages.
It seems difficult to modify git in core so that it builds with docs
without creating circular dependencies, chunks such as libtool depend
on git, libxml2 depends on libtool, so libxml2 depends on git, but
docutils depends on libxml2, and we need to make git depend on docutils,
the fact that python2 is no longer in core also adds to the difficulty
since asciidoc's build process depends on python2.
Change-Id: Ifc64019b941740c85db058d36183b4a210c60e15
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From [1]:
"Python 2.x is legacy, Python 3.x is the present and future of the language"
As a reference, python3 is already the default python version in Arch,
and other distros like Ubuntu/Debian [2] or Fedora [3] are planning to
switch soon
[1] https://wiki.python.org/moin/Python2orPython3
[2] https://wiki.ubuntu.com/Python/3
[3] https://fedoraproject.org/wiki/Changes/Python_3_as_Default
Change-Id: I6d4d11844d4424bfa49b37fe7d9a3639547c0139
|
|
|
|
|
|
| |
This version of util-linux will be needed for new versions of systemd.
Change-Id: Ie1ebfeed53abdccf991ba91a0c8766ef70d75ed0
|
|
|
|
| |
Change-Id: I3845c77e8872ce2e1e8bc6a60e3ce7f184c32f58
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Moving chunks around so its easy to identify what are actually
dependencies of other chunks, and wicht ones are there because
are dependencies of other strata, and maybe can be removed in
the future (in the bottom)
As it is, the core stratum can be read as:
- Build autotools (autoconf, automake, libtool, gettext)
- Build util-linux and deps
- Build some chunks needed by other strata
Change-Id: I5c778786f2f2ccfae5d5f1f2368481d39f4d41f9
|
|
|
|
|
|
|
|
|
|
|
|
| |
This actually revert some changes we made a while back (74ce6a18, 7cb71771,
7c2bfac9)
I realize we will have to patch a lot of modules manually following this route.
Also, I remember to see some commands from chunks that, even they build fine,
they will show UNKNOWN if you type <command> --version
Basically the chunks assume that if you are building from git, you have git
installed
Change-Id: I886288553e8edf05ffc1cb497fabbadb468819b7
|
|
|
|
| |
Change-Id: I1bcc28de68c9b61b25929cf142e1dd8ea63f8d6f
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent autoconf (and autoconf generated ./configure files) uses
the "file" program to work out what binary format is currently
being produced by the compiler when the architecture is MIPS.
If "file" doesn't exist, or it fails to identify the binary
format, autoconf/configure silently disables the building of
shared libraries, which causes later chunks to fail to build at
link stage due to missing .so files.
Change-Id: Ia98a22d121fc8cb95d36bcb1d3ae2ce44cc6ddf5
|
|
|
|
| |
Change-Id: I1e96327e30051079968e39db0032b98e0c81d352
|
|
|
|
| |
Change-Id: I309f2ee3d9ff0569907c51ee9984b365b31cdbf5
|
|
|
|
| |
Change-Id: I1faa4db9e3bb5c2e8e3ef80d88b3ef3e5cf2ae26
|
|
|
|
|
|
| |
Also attr doesnt depend on automake to build
Change-Id: Ied3ba4af7991c44ed080362a8dae5d00092e5514
|
|
|
|
| |
Change-Id: I7947f088ed59948deb68760a03714d722840a00a
|
|
|
|
|
| |
libtool-tarball is still needed to build the libtool dependencies
Change-Id: Icd90c0c92574812f860a649f40343bf13930b0ad
|
|
|
|
|
|
| |
But in automake, autoconf, mini-utils and bison
Change-Id: I6333bd5a6665697805c0acbd8f18928e32cdbde6
|
|
|
|
|
|
| |
At least systemd fails to build if you remove the git dependency
from util-linux and you dont apply this workaround
Change-Id: Ife649e811aea2ffb2eb4fa6d042e2dfbaf390430
|
|
|
|
|
|
|
| |
Also, backport a patch needed to build with latest
texinfo
Change-Id: I1f1e0e81091fb4212bd111e16c8054ce548f4ae8
|
|
|
|
|
|
|
|
| |
Without this patch, you get:
~ #patch --version
GNU patch UNKNOWN
Change-Id: I63c554ac9372306a5c8faa8324a31237ae6c9972
|
|
|
|
|
| |
... to avoid build failure when building gobject-introspection
Change-Id: I9efdbe7063595fe147e00b4e5335ba6a32afa582
|
|
|
|
| |
Change-Id: Idd1a0c155f2872c2b4aba64fa388e505e04fe7ab
|
|
|
|
| |
Change-Id: I6bd38c933bcb86376a31fb36a6e40d2bd156822d
|
|
|
|
|
|
|
|
|
| |
These dependencies are:
- Autoconf
- Automake
- Libtool
Change-Id: Id4bb6ec40311c681b1708cad2114fc603a525b82
|
|
|
|
|
|
|
|
|
|
|
| |
Also, use autotools instead the experimental cmake system as It
doesnt seem to generate the correct libexpat.so.x files.
Thanks to Daniel Silverstone for the automake line to add
the missing automake files (like install-sh) as upstream doesnt
have them
Change-Id: Ide6ad8ecb9ed35a42348a882cb9acc3b36fc4e34
|
|
|
|
| |
Change-Id: I943416ae89987a053d42e5161a86d9f37f7fea78
|
|
|
|
|
|
|
|
| |
So cross- systems doesnt depend on the whole foundation
(cross- systems include morph, which depends on ostree,
wich depends on e2fsprogs)
Change-Id: I77918e2a2a66e9bd7c8ce77d2447e390d192a1c8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This involves:
* Reordering the chunks linux-pam, acl, attr and libcap2 - this means
moving them into the 'core' stratum, and fixing errors that occur
because of the move.
* Configuring pam correctly.
* Fix acl failing to build in core.
* Fix shadow to build against pam and reconfigure shadow to not do
things covered by pam.
* Fix tar not building - I am not sure what caused this to fail to
build, but fixing it involved stopping it from trying to init
submodules that were already checked out.
Change-Id: I1b00ca0158c31ce5f31c11fe60816434508a05a1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Morph now depend on pygobject (to access ostree features).
Also ostree depends on libsoup.
Both libsoup and pygobject depends on GLib.
morph is in cross-* systems, so we move GLib
to the core stratum to not have to build the entire foundation
stratum in the cross-* systems.
Also the change makes sense as GLib is a dependency of strata
that not necessarily depend on foundation (like
multimedia-gstreamer)
Change-Id: I9d1527b5057c71704ef5a0fe3d3e5f348f2908e5
|
|
|
|
|
|
|
|
|
|
|
| |
Some interesting changes:
- The command hwclock(8) uses the drift correction for all relevant
operations and it is unnecessary yo specify --adjust on the hwclock
command line now
- zramctl(8):
this NEW COMMAND allows to control /dev/zramN devices
Change-Id: I196d3a9a0f38bcb10c2adf10a200acc4d4218a9b
|
|
|
|
|
|
|
|
|
| |
Even it can be see as a GNOME dependency, this is only
a group of autoconf macros (in the process of being
upstreamed in autoconf-archive, but we need this here
as is still being used by several projects)
Change-Id: Ia1e510283110c522eebd8f72597f4e505de7a021
|
|
|
|
|
|
|
|
| |
This enables kmod python bindings required for iscsi tools.
Enabling python in the kmod chunk requires cython for compiling
so cython is moved to core.morph.
Change-Id: Ic394d75f801efcb0be1e4ec17d9bc907f9d086a0
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nano was broken; its binary not ending up in the systems.
Here we fix that, update to 2.4.0 (which has full undo/redo
functionality), and provide useful default config (enabling
syntax highlighting, etc).
Nano has also been moved from core to devtools. This stops
morph from wanting to rebuild the world when you update Nano.
Change-Id: I702b070cde6731fde04fc8a0810e2191e0bd4e6d
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit c5240343053398d288cc500ff54379a3b0de5309.
The original clean-up patch breaks the native build phase of
cross-bootstrap on tested platforms - armv8l64, armv8b64, and
x86_64.
In the bootstrap environment, the native build of bison does
rely on being run with bash rather than sh.
Change-Id: Id8ed8793f8a179615a2f8733e867445cac544043
|
|
|
|
| |
Change-Id: I6a0b0ebe0fb7d2505ac0fdcdba6a482763724808
|
|
|
|
| |
Change-Id: I58caaebe296d6c7e5684ff6836c1f2b4a155ab8f
|