by Douglas
Ah I see the other thread now, all the fun. If the patch is intended
to be dropped after an update, having a naming scheme as per Arjan's
suggestion in the patch thread would be nice to keep.
On Mon, Mar 16, 2020 at 9:21 AM Douglas, William
<william.douglas(a)intel.com > wrote:
>
> Hrm this diff isn't super helpful, why is the encoding patch added?
>
> On Mon, Mar 16, 2020 at 7:55 AM Ross Burton <ross.burton(a)intel.com > wrote:
> >
> > ---
> > release | 2 +-
> > series | 1 +
> > udisks2.spec | 8 +++++---
> > 3 files changed, 7 insertions(+), 4 deletions(-)
> >
> > diff --git a/series b/series
> > index 75e72d0..4940b15 100644
> > --- a/series
> > +++ b/series
> > @@ -1 +1,2 @@
> > 0001-Add-support-for-a-stateless-configuration-file.patch
> > +encoding.patch
> > diff --git a/udisks2.spec b/udisks2.spec
> > index 8b3e7ca..2df6cc9 100644
> > --- a/udisks2.spec
> > +++ b/udisks2.spec
> > @@ -54,6 +54,7 @@ BuildRequires : pkgconfig(mount)
> > BuildRequires : pkgconfig(polkit-agent-1)
> > BuildRequires : pkgconfig(polkit-gobject-1)
> > Patch1: 0001-Add-support-for-a-stateless-configuration-file.patch
> > +Patch2: encoding.patch
> >
> > %description
> > CI status
> > @@ -168,13 +169,14 @@ services components for the udisks2 package.
> > %setup -q -n udisks-2.8.4
> > cd %{_builddir}/udisks-2.8.4
> > %patch1 -p1
> > +%patch2 -p1
> >
> > %build
> > export http_proxy=http://127.0.0.1:9/
> > export https_proxy=http://127.0.0.1:9/
> > export no_proxy=localhost,127.0.0.1,0.0.0.0
> > export LANG=C.UTF-8
> > export GCC_IGNORE_WERROR=1
> > export CFLAGS="$CFLAGS -fno-lto "
> > export FCFLAGS="$CFLAGS -fno-lto "
> > _______________________________________________
> > Dev mailing list -- dev(a)lists.clearlinux.org
> > To unsubscribe send an email to dev-leave(a)lists.clearlinux.org
by Ross Burton
On 16/03/2020 16:21, Douglas, William wrote:
> Hrm this diff isn't super helpful, why is the encoding patch added?
Well I obviously drove git wrong at some point and got it added to the
'remove obsolete patch' commit accidentally. I also note that for some
reason my explanation as to why this patch is needed was dropped somewhere.
I'll fix it all and send a v2 :/
Ross
by Ross Burton
On 16/03/2020 16:17, Melo, Anselmo wrote:
>> ________________________________________
>> From: Ross Burton [ross.burton(a)intel.com ]
>> Sent: Monday, March 16, 2020 7:49 AM
>> To: dev(a)lists.clearlinux.org
>> Subject: [Clr-dev] [PATCH udisks2] Remove obsolete patch
>
>> CVE-2018-17336 was fixed in udisks 2.8.1 onwards.
>> ---
>> CVE-2018-17336.patch | 32 ---------------------------
>> encoding.patch | 52 ++++++++++++++++++++++++++++++++++++++++++++
>
> CVE patch removal: +1
>
> Was adding encoding.patch intended?
No, that was meant to be part of 2/2. I'll fix up the history before
pushing.
Ross
by Ross Burton
Daniel Playfair Cal (9):
Increment version number following 0.34 release
Service: filter changesets when performing writes such that changed events are only emitted if new values differ from existing values
Service: Add unit tests for dconf_changeset_filter_changes
Changeset: make dconf_changeset_filter_changes filter out key/path resets when appropriate
Changeset: factor out some memory management from test_filter_changes
Service: add tests exercising new functionality to avoid redundant writes
Service: avoid redundant writes even after other non redundant writes have succeeded
Update NEWS for 0.35.1 release
Increment version number post 0.35.1 release
Diego Escalante Urrelo (2):
gsettings: Update abicheck.sh script
build: Update use of link_whole for meson-0.52
Marek Kasik (1):
Prepare 0.36 release
Philip Withnall (1):
build: Drop redundant `install` key from `configure_file()`
---
Makefile | 2 +-
NEWS | 18 ++++++++++++++++++
buildreq_cache | 5 ++---
dconf.spec | 36 ++++++++++++++++++++++--------------
options.conf | 5 +++--
release | 2 +-
symbols | 1 +
symbols32 | 1 +
testresults | 4 ++--
upstream | 2 +-
versions | 2 +-
11 files changed, 53 insertions(+), 25 deletions(-)
diff --git a/dconf.spec b/dconf.spec
index 761ce96..dc9b9a9 100644
--- a/dconf.spec
+++ b/dconf.spec
@@ -160,7 +159,7 @@ export FFLAGS="$CFLAGS -O3 -Os -fdata-sections -ffat-lto-objects -ffunction-sect
export CXXFLAGS="$CXXFLAGS -O3 -Os -fdata-sections -ffat-lto-objects -ffunction-sections -flto=4 -fno-semantic-interposition "
CFLAGS="$CFLAGS" CXXFLAGS="$CXXFLAGS" LDFLAGS="$LDFLAGS" meson --libdir=lib64 --prefix=/usr --buildtype=plain builddir
ninja -v -C builddir
-pushd ../build32
+pushd ../build32/
export PKG_CONFIG_PATH="/usr/lib32/pkgconfig"
export ASFLAGS="${ASFLAGS}${ASFLAGS:+ }--32"
export CFLAGS="${CFLAGS}${CFLAGS:+ }-m32 -mstackrealign"
@@ -170,10 +169,19 @@ meson --libdir=lib32 --prefix=/usr --buildtype=plain builddir
ninja -v -C builddir
popd
+%check
+meson test -C builddir || :
+cd ../build32;
+meson test -C builddir || : || :
+
%install
mkdir -p %{buildroot}/usr/share/package-licenses/dconf
-cp COPYING %{buildroot}/usr/share/package-licenses/dconf/COPYING
-pushd ../build32
+cp %{_builddir}/dconf-0.36.0/COPYING %{buildroot}/usr/share/package-licenses/dconf/9a1929f4700d2407c70b507b3b2aaf6226a9543c
+pushd ../build32/
DESTDIR=%{buildroot} ninja -C builddir install
if [ -d %{buildroot}/usr/lib32/pkgconfig ]
then
@@ -235,7 +243,7 @@ DESTDIR=%{buildroot} ninja -C builddir install
%files license
%defattr(0644,root,root,0755)
-/usr/share/package-licenses/dconf/COPYING
+/usr/share/package-licenses/dconf/9a1929f4700d2407c70b507b3b2aaf6226a9543c
%files man
%defattr(0644,root,root,0755)
diff --git a/options.conf b/options.conf
index 2c230f8..002c4bc 100644
--- a/options.conf
+++ b/options.conf
@@ -1,8 +1,9 @@
[package]
name = dconf
-url = https://download.gnome.org/sources/dconf/0.34/dconf-0.34.0.tar.xz
+url = https://download.gnome.org/sources/dconf/0.36/dconf-0.36.0.tar.xz
archives =
giturl = https://github.com/GNOME/dconf.git
+domain =
[autospec]
# build 32 bit libraries
diff --git a/testresults b/testresults
index 92c6b06..7c81bc2 100644
--- a/testresults
+++ b/testresults
@@ -1,5 +1,5 @@
+Total : 26
+Pass : 26
Fail : 0
Skip : 0
XFail : 0
by Ross Burton
CVE-2018-17336 was fixed in udisks 2.8.1 onwards.
---
CVE-2018-17336.patch | 32 ---------------------------
encoding.patch | 52 ++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 52 insertions(+), 32 deletions(-)
delete mode 100644 CVE-2018-17336.patch
create mode 100644 encoding.patch
diff --git a/CVE-2018-17336.patch b/CVE-2018-17336.patch
deleted file mode 100644
index c3c083d..0000000
--- a/CVE-2018-17336.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-From e369a9b4b08e9373c814c05328b366c938284eb5 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Kai=20L=C3=BCke?= <kailueke(a)riseup.net >
-Date: Tue, 18 Sep 2018 13:12:14 +0200
-Subject: [PATCH] Fix string format vulnerability
-
-If the message in g_log_structured itself
-contained format sequences like %d or %n they
-were applied again, leading to leaked stack contents
-and possibly memory corruption. It can be triggered
-e.g. by a volume label containing format sequences.
-
-Print the message argument itself into a "%s" string
-to avoid intepreting format sequences.
-
-https://github.com/storaged-project/udisks/issues/578
----
- src/udiskslogging.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/udiskslogging.c b/src/udiskslogging.c
-index ab49fcbf..47a3af23 100644
---- a/src/udiskslogging.c
-+++ b/src/udiskslogging.c
-@@ -60,7 +60,7 @@ udisks_log (UDisksLogLevel level,
-
- #if GLIB_CHECK_VERSION(2, 50, 0)
- g_log_structured ("udisks", (GLogLevelFlags) level,
-- "MESSAGE", message, "THREAD_ID", "%d", (gint) syscall (SYS_gettid),
-+ "MESSAGE", "%s", message, "THREAD_ID", "%d", (gint) syscall (SYS_gettid),
- "CODE_FUNC", function, "CODE_FILE", location);
- #else
- g_log ("udisks", level, "[%d]: %s [%s, %s()]", (gint) syscall (SYS_gettid), message, location, function);
diff --git a/encoding.patch b/encoding.patch
new file mode 100644
index 0000000..e939b11
--- /dev/null
+++ b/encoding.patch
@@ -0,0 +1,52 @@
+Fix the test suite failing with latest GLib
+
+Upstream-Status: Backport [https://github.com/storaged-project/udisks/pull/729 ]
+Signed-off-by: Ross Burton <ross.burton(a)intel.com >
+
+From 60a0c1c967821d317046d9494e45b9a8e4e7a1c1 Mon Sep 17 00:00:00 2001
+From: Philip Withnall <withnall(a)endlessm.com >
+Date: Mon, 17 Feb 2020 16:08:28 +0000
+Subject: [PATCH] udisksspawnedjob: Clear encoding of stdout and stderr
+ channels
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+We want to be able to read binary data from the stderr and stdout of
+spawned processes, so unset the encoding for those channels — otherwise
+it will be validated as UTF-8 and invalid data (particularly embedded
+nuls) will be dropped.
+
+GLib became stricter at validating this with
+https://gitlab.gnome.org/GNOME/glib/merge_requests/967 in GLib 2.63.0,
+but it’s not an API break.
+
+Signed-off-by: Philip Withnall <withnall(a)endlessm.com >
+
+Fixes: #724
+---
+ src/udisksspawnedjob.c | 4 ++++
+ 1 file changed, 4 insertions(+)
+
+diff --git a/src/udisksspawnedjob.c b/src/udisksspawnedjob.c
+index 9d12aa842..8062c1e3c 100644
+--- a/src/udisksspawnedjob.c
++++ b/src/udisksspawnedjob.c
+@@ -1032,6 +1032,8 @@ void udisks_spawned_job_start (UDisksSpawnedJob *job)
+ }
+
+ job->child_stdout_channel = g_io_channel_unix_new (job->child_stdout_fd);
++ /* we want to read binary, suppress checking the encoding: */
++ g_io_channel_set_encoding (job->child_stdout_channel, NULL, NULL);
+ g_io_channel_set_flags (job->child_stdout_channel, G_IO_FLAG_NONBLOCK, NULL);
+ job->child_stdout_source = g_io_create_watch (job->child_stdout_channel, G_IO_IN);
+ #if __GNUC__ >= 8
+@@ -1050,6 +1052,8 @@ void udisks_spawned_job_start (UDisksSpawnedJob *job)
+ g_source_unref (job->child_stdout_source);
+
+ job->child_stderr_channel = g_io_channel_unix_new (job->child_stderr_fd);
++ /* we want to read binary, suppress checking the encoding: */
++ g_io_channel_set_encoding (job->child_stderr_channel, NULL, NULL);
+ g_io_channel_set_flags (job->child_stderr_channel, G_IO_FLAG_NONBLOCK, NULL);
+ job->child_stderr_source = g_io_create_watch (job->child_stderr_channel, G_IO_IN);
+ #if __GNUC__ >= 8
--
2.25.1
by Mayuresh Kathe
The installer built by the core team is wonderful, would like to use
that same widget set for a project I am targetting specifically for
developing GUI applications for Clear Linux OS - Desktop Edition.
Can I know which widget set was used and request pointers to
documentation for using the same? Or should I be working with Vala?
by William Douglas
For a long time Clear Linux has had two gcc packages. This has caused
the occasional issue with the packages not being in sync and generally
making things harder to maintain. This change moves the avx2 and
avx512 library versions into the main gcc package so that the
libgfortran-avx package can be dropped.
---
gcc.spec | 200 +++++++++++++++++++++++++++++++++++++++++++++++++++++--
release | 2 +-
2 files changed, 196 insertions(+), 6 deletions(-)
diff --git a/gcc.spec b/gcc.spec
index 2605b21..534d80d 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -14,7 +14,7 @@
Name : gcc
Version : 9.2.1
-Release : 806
+Release : 807
URL : http://www.gnu.org/software/gcc/
Source0 : https://gcc.gnu.org/pub/gcc/releases/gcc-9.2.0/gcc-9.2.0.tar.xz
Source1 : https://gcc.gnu.org/pub/gcc/infrastructure/isl-0.16.1.tar.bz2
@@ -298,6 +298,118 @@ make %{?_smp_mflags} profiledbootstrap
popd
+rm -rf ../gcc-build-avx2
+mkdir ../gcc-build-avx2
+pushd ../gcc-build-avx2
+unset CFLAGS
+unset CXXFLAGS
+export CFLAGS="-march=ivybridge -g -O3 -fstack-protector -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z,max-page-size=0x1000"
+export CXXFLAGS="-march=ivybridge -g -O3 -Wl,-z,max-page-size=0x1000"
+export CFLAGS_FOR_TARGET="$CFLAGS -march=haswell -mtune=skylake -fno-semantic-interposition "
+export CXXFLAGS_FOR_TARGET="$CXXFLAGS -march=haswell -mtune=skylake -fno-semantic-interposition "
+export FFLAGS_FOR_TARGET="$FFLAGS -march=haswell -mtune=skylake -fno-semantic-interposition "
+
+export CPATH=/usr/include
+export LIBRARY_PATH=%{_libdir}
+../%{gccpath}/configure \
+ --prefix=%{_prefix} \
+ --with-pkgversion='Clear Linux OS for Intel Architecture'\
+ --libdir=/usr/lib64 \
+ --enable-libstdcxx-pch\
+ --libexecdir=/usr/lib64 \
+ --with-system-zlib\
+ --enable-shared\
+ --enable-gnu-indirect-function \
+ --disable-vtable-verify \
+ --enable-threads=posix\
+ --enable-__cxa_atexit\
+ --enable-plugin\
+ --enable-ld=default\
+ --enable-clocale=gnu\
+ --disable-multiarch\
+ --disable-multilib\
+ --enable-lto\
+ --enable-linker-build-id \
+ --build=%{gcc_target}\
+ --target=%{gcc_target}\
+ --enable-languages="c,c++,fortran" \
+ --with-ppl=yes \
+ --with-isl \
+ --includedir=%{_includedir} \
+ --with-gxx-include-dir=%{_includedir}/c++/ \
+ --exec-prefix=%{_prefix} \
+ --with-glibc-version=2.19 \
+ --with-system-libunwind \
+ --with-gnu-ld \
+ --with-tune=haswell \
+ --with-arch=haswell \
+ --disable-bootstrap \
+ --enable-cet \
+ --disable-libmpx \
+ --with-gcc-major-version-only \
+ --enable-default-pie
+
+make %{?_smp_mflags}
+
+popd
+
+rm -rf ../gcc-build-avx512
+mkdir ../gcc-build-avx512
+pushd ../gcc-build-avx512
+unset CFLAGS
+unset CXXFLAGS
+export CFLAGS="-march=ivybridge -g -O3 -fstack-protector -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z,max-page-size=0x1000"
+export CXXFLAGS="-march=ivybridge -g -O3 -Wl,-z,max-page-size=0x1000"
+export CFLAGS_FOR_TARGET="$CFLAGS -march=skylake-avx512 -mtune=skylake -fno-semantic-interposition "
+export CXXFLAGS_FOR_TARGET="$CXXFLAGS -march=skylake-avx512 -mtune=skylake -fno-semantic-interposition "
+export FFLAGS_FOR_TARGET="$FFLAGS -march=skylake-avx512 -mtune=skylake -fno-semantic-interposition "
+
+export CPATH=/usr/include
+export LIBRARY_PATH=%{_libdir}
+
+../%{gccpath}/configure \
+ --prefix=%{_prefix} \
+ --with-pkgversion='Clear Linux OS for Intel Architecture'\
+ --libdir=/usr/lib64 \
+ --enable-libstdcxx-pch\
+ --libexecdir=/usr/lib64 \
+ --with-system-zlib\
+ --enable-shared\
+ --enable-gnu-indirect-function \
+ --disable-vtable-verify \
+ --enable-threads=posix\
+ --enable-__cxa_atexit\
+ --enable-plugin\
+ --enable-ld=default\
+ --enable-clocale=gnu\
+ --disable-multiarch\
+ --disable-multilib\
+ --enable-lto\
+ --enable-linker-build-id \
+ --build=%{gcc_target}\
+ --target=%{gcc_target}\
+ --enable-languages="c,c++,fortran" \
+ --with-ppl=yes \
+ --with-isl \
+ --includedir=%{_includedir} \
+ --with-gxx-include-dir=%{_includedir}/c++/ \
+ --exec-prefix=%{_prefix} \
+ --with-glibc-version=2.19 \
+ --with-system-libunwind \
+ --with-gnu-ld \
+ --with-tune=skylake-avx512 \
+ --with-arch=skylake-avx512 \
+ --disable-bootstrap \
+ --enable-cet \
+ --disable-libmpx \
+ --with-gcc-major-version-only \
+ --enable-default-pie
+
+make %{?_smp_mflags}
+
+popd
+
+
# Work around libstdc++'s use of weak symbols to libpthread in static
# mode: libpthread doesn't get pulled in and therefore we get crashes
# due to the calls being resolved to address 0x0.
@@ -339,6 +451,33 @@ done
%install
export CPATH=/usr/include
export LIBRARY_PATH=/usr/lib64
+
+pushd ../gcc-build-avx512
+%make_install
+popd
+rm -rf %{buildroot}/usr/share
+rm -rf %{buildroot}/usr/bin
+rm -rf %{buildroot}/usr/lib64/gcc/
+rm -rf %{buildroot}/usr/lib64/*.a
+rm -rf %{buildroot}/usr/lib64/*.o
+rm -rf %{buildroot}/usr/lib64/*.so
+rm -rf %{buildroot}/usr/lib64/*.spec
+mkdir -p %{buildroot}/usr/lib64/haswell/avx512_1
+mv %{buildroot}/usr/lib64/*so* %{buildroot}/usr/lib64/haswell/avx512_1
+
+pushd ../gcc-build-avx2
+%make_install
+popd
+rm -rf %{buildroot}/usr/share
+rm -rf %{buildroot}/usr/bin
+rm -rf %{buildroot}/usr/lib64/gcc/
+rm -rf %{buildroot}/usr/lib64/*.a
+rm -rf %{buildroot}/usr/lib64/*.o
+rm -rf %{buildroot}/usr/lib64/*.so
+rm -rf %{buildroot}/usr/lib64/*.spec
+mkdir -p %{buildroot}/usr/lib64/haswell
+mv %{buildroot}/usr/lib64/*so* %{buildroot}/usr/lib64/haswell/
+
pushd ../gcc-build
%make_install
cd -
@@ -355,8 +494,8 @@ fi
ln -sf %{gcc_target}-g++ g++
ln -sf %{gcc_target}-gcc gcc
#ln -sf %{gcc_target}-cpp cpp
-install -d %{buildroot}/lib
-ln -sf /usr/bin/cpp %{buildroot}/lib/cpp
+install -d %{buildroot}/usr/lib
+ln -sf /usr/bin/cpp %{buildroot}/usr/lib/cpp
ln -sf g++ c++
ln -sf gcc cc
cd -
@@ -424,7 +563,7 @@ cat *.lang > gcc.lang
/usr/bin/gcc-ranlib
/usr/bin/gcov
/usr/bin/gcov-tool
-/lib/cpp
+/usr/lib/cpp
/usr/bin/cpp
#/usr/lib64/libvtv*
/usr/lib64/libcc1*
@@ -567,6 +706,12 @@ cat *.lang > gcc.lang
%files -n libgcc1
/usr/lib64/libgcc_s.so.1
+#avx2
+%exclude /usr/lib64/haswell/libgcc_s.so.1
+
+#avx512
+%exclude /usr/lib64/haswell/avx512_1/libgcc_s.so.1
+
%files libs-math
/usr/lib64/libssp.so*
/usr/lib64/libgomp*so*
@@ -575,6 +720,24 @@ cat *.lang > gcc.lang
/usr/lib64/libquadmath*.so.*
/usr/lib64/libgfortran*.so.*
+#avx2
+/usr/lib64/haswell/libgomp.so.1
+/usr/lib64/haswell/libgomp.so.1.0.0
+%exclude /usr/lib64/haswell/libitm.so.1
+%exclude /usr/lib64/haswell/libitm.so.1.0.0
+/usr/lib64/haswell/libquadmath.so.0
+/usr/lib64/haswell/libquadmath.so.0.0.0
+/usr/lib64/haswell/libgfortran.so.5
+/usr/lib64/haswell/libgfortran.so.5.0.0
+
+#avx512
+%exclude /usr/lib64/haswell/avx512_1/libgomp.so.1
+%exclude /usr/lib64/haswell/avx512_1/libgomp.so.1.0.0
+/usr/lib64/haswell/avx512_1/libquadmath.so.0
+/usr/lib64/haswell/avx512_1/libquadmath.so.0.0.0
+/usr/lib64/haswell/avx512_1/libgfortran.so.5
+/usr/lib64/haswell/avx512_1/libgfortran.so.5.0.0
+
%files libgcc32
/usr/lib32/libasan.so.5
/usr/lib32/libasan.so.5.0.0
@@ -605,10 +768,17 @@ cat *.lang > gcc.lang
#/usr/lib/libvtv.so.0
#/usr/lib/libvtv.so.0.0.0
-
%files -n libstdc++
/usr/lib64/libstdc++.so.*
+#avx2
+/usr/lib64/haswell/libstdc++.so.6
+/usr/lib64/haswell/libstdc++.so.6.0.*
+
+#avx512
+/usr/lib64/haswell/avx512_1/libstdc++.so.6
+/usr/lib64/haswell/avx512_1/libstdc++.so.6.0.*
+
%files libstdc++32
/usr/lib32/libstdc++.so.*
@@ -648,3 +818,23 @@ cat *.lang > gcc.lang
/usr/lib64/libtsan*
/usr/lib64/liblsan*
/usr/lib64/libsanit*
+
+#avx2
+%exclude /usr/lib64/haswell/libubsan.so.1
+%exclude /usr/lib64/haswell/libubsan.so.1.0.0
+%exclude /usr/lib64/haswell/libasan.so.5
+%exclude /usr/lib64/haswell/libasan.so.5.0.0
+%exclude /usr/lib64/haswell/libtsan.so.0
+%exclude /usr/lib64/haswell/libtsan.so.0.0.0
+%exclude /usr/lib64/haswell/liblsan.so.0
+%exclude /usr/lib64/haswell/liblsan.so.0.0.0
+
+#avx512
+%exclude /usr/lib64/haswell/avx512_1/libubsan.so.1
+%exclude /usr/lib64/haswell/avx512_1/libubsan.so.1.0.0
+%exclude /usr/lib64/haswell/avx512_1/libasan.so.5
+%exclude /usr/lib64/haswell/avx512_1/libasan.so.5.0.0
+%exclude /usr/lib64/haswell/avx512_1/libtsan.so.0
+%exclude /usr/lib64/haswell/avx512_1/libtsan.so.0.0.0
+%exclude /usr/lib64/haswell/avx512_1/liblsan.so.0
+%exclude /usr/lib64/haswell/avx512_1/liblsan.so.0.0.0
diff --git a/release b/release
index 85fd1d2..882e319 100644
--- a/release
+++ b/release
@@ -1 +1 @@
-806
+807
--
2.25.1
by puneet.sethi＠linux.intel.com
From: puneetse <puneet.sethi(a)linux.intel.com >
The sensors-detect script complains about these missing after
execution.
---
install_append | 1 +
lm-sensors.spec | 24 +++++++++++++++++++++---
options.conf | 1 +
release | 2 +-
4 files changed, 24 insertions(+), 4 deletions(-)
diff --git a/install_append b/install_append
index eeb7c36..9dc45fa 100644
--- a/install_append
+++ b/install_append
@@ -1,2 +1,3 @@
mkdir -p %{buildroot}/usr/share/doc/lm-sensors/examples
cp -a %{buildroot}/etc %{buildroot}/usr/share/doc/lm-sensors/examples
+install -D -m644 prog/init/*.service -t %{buildroot}/usr/lib/systemd/system
diff --git a/lm-sensors.spec b/lm-sensors.spec
index 342a3c3..a0b4fa9 100644
--- a/lm-sensors.spec
+++ b/lm-sensors.spec
@@ -13,6 +13,7 @@ License : GPL-2.0 LGPL-2.1
Requires: lm-sensors-bin = %{version}-%{release}
Requires: lm-sensors-lib = %{version}-%{release}
Requires: lm-sensors-license = %{version}-%{release}
+Requires: lm-sensors-services = %{version}-%{release}
BuildRequires : bison
BuildRequires : flex
Patch1: build.patch
@@ -28,6 +29,7 @@ versions, you have to use lm-sensors version 2.
Summary: bin components for the lm-sensors package.
Group: Binaries
Requires: lm-sensors-license = %{version}-%{release}
+Requires: lm-sensors-services = %{version}-%{release}
%description bin
bin components for the lm-sensors package.
@@ -70,8 +72,17 @@ Group: Default
license components for the lm-sensors package.
+%package services
+Group: Systemd services
+
+%description services
+services components for the lm-sensors package.
+
+
%prep
%setup -q -n lm-sensors-3-6-0
%patch1 -p1
%build
@@ -101,6 +112,7 @@ cp %{_builddir}/lm-sensors-3-6-0/COPYING.LGPL %{buildroot}/usr/share/package-lic
## install_append content
mkdir -p %{buildroot}/usr/share/doc/lm-sensors/examples
cp -a %{buildroot}/etc %{buildroot}/usr/share/doc/lm-sensors/examples
+install -D -m644 prog/init/*.service -t %{buildroot}/usr/lib/systemd/system
## install_append end
%files
@@ -145,3 +157,9 @@ cp -a %{buildroot}/etc %{buildroot}/usr/share/doc/lm-sensors/examples
%defattr(0644,root,root,0755)
/usr/share/package-licenses/lm-sensors/01a6b4bf79aca9b556822601186afab86e8c4fbf
/usr/share/package-licenses/lm-sensors/06877624ea5c77efe3b7e39b0f909eda6e25a4ec
+
+%files services
+%defattr(-,root,root,-)
+/usr/lib/systemd/system/fancontrol.service
+/usr/lib/systemd/system/lm_sensors.service
+/usr/lib/systemd/system/sensord.service
diff --git a/options.conf b/options.conf
index 0af16cf..032d6e6 100644
--- a/options.conf
+++ b/options.conf
@@ -4,6 +4,7 @@ url = https://github.com/lm-sensors/lm-sensors/archive/V3-6-0/lm-sensors-3.6.0.t
archives =
giturl = https://github.com/lm-sensors/lm-sensors.git
domain =
+alias =
[autospec]
# build 32 bit libraries
by Mayuresh Kathe
By when is the Clear Linux OS team planning to provide the previously
discussed commercial channel for proprietary software?
by Otavio Pontes
There is a recent change in swupd that can affect you if you are a mix
maintainer. As we have previously announced swupd now checks for a
correct signature of the lastest file (version/formatXX/latetest)
created on every new release.
If you use any recent mixer (> v5.9.1), that file is already being
signed and there's no change expected on your side, but if you want to
be sure, check if file version/formatXX/latest.sig is being created and
test if swupd is able to update. Swupd will print error messages in case
your signature is invalid.
Swupd updates from mixes where latest signature is missing is still
going to work for now, but warning messages will be printed. Enforcement
of latest file signature will be released in the following weeks, so if
you are having this kind of problems it's important to work on fixing it
sooner than later.
Regards,
Otavio
