From glen at pld-linux.org Sat Oct 1 20:18:23 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 1 Oct 2016 21:18:23 +0300 Subject: apache-mod_wsgi.spec Message-ID: <57EFFDEF.6090008@pld-linux.org> so if wanting to build python3 version as well what would be the package names be? currently apache-mod_wsgi.spec builds apache-mod_wsgi package, using python2 some variants that i'm throwing in, the examples are binary package names, the spec name stays as it is "apache-mod_wsgi.spec": 1. apache-mod_wsgi = python2 apache-mod_wsgi3 = python3 2. apache-mod_wsgi = RIP apache-mod_wsgi-py2 = python2 apache-mod_wsgi-py3 = python3 3. apache-mod_wsgi = requires %name(mod_wsgi) apache-mod_wsgi-py2 = python2, provides %name(mod_wsgi) apache-mod_wsgi-py3 = python3, provides %name(mod_wsgi) the more suffix variants include: - -2, -3 - -py2, -py3 - -python2, -python3 -- glen From jajcus at jajcus.net Sat Oct 1 20:44:37 2016 From: jajcus at jajcus.net (Jacek Konieczny) Date: Sat, 01 Oct 2016 20:44:37 +0200 Subject: apache-mod_wsgi.spec In-Reply-To: <57EFFDEF.6090008@pld-linux.org> References: <57EFFDEF.6090008@pld-linux.org> Message-ID: <57F00415.1050003@jajcus.net> On 2016-10-01 20:18, Elan Ruusam?e wrote: > 1. > apache-mod_wsgi = python2 > apache-mod_wsgi3 = python3 That will encourage keeping python2 as 'the python' forever? > 2. > apache-mod_wsgi = RIP > apache-mod_wsgi-py2 = python2 > apache-mod_wsgi-py3 = python3 > > 3. > apache-mod_wsgi = requires %name(mod_wsgi) > apache-mod_wsgi-py2 = python2, provides %name(mod_wsgi) > apache-mod_wsgi-py3 = python3, provides %name(mod_wsgi) Both seem ok for me. The first one is even better, unless there are some common files to include there. And don't forget to add: Obsoletes: apache-mod_wsgi < first_version_split To -py2. > the more suffix variants include: > - -2, -3 > - -py2, -py3 > - -python2, -python3 -py2, -py3, seems good for me. '-2', '-3' could suggest it is wsgi, not Python version. '-python2', '-python3' would be good for packages that do not imply Python, like mod_wsgi does, but are not needed here ('py2' is clear enough). Jacek From glen at delfi.ee Mon Oct 3 14:53:21 2016 From: glen at delfi.ee (=?utf-8?Q?Elan_Ruusam=C3=A4e?=) Date: Mon, 3 Oct 2016 15:53:21 +0300 Subject: gcc Message-ID: <23347B9D-620D-4935-A23B-25510100B59F@delfi.ee> some unhanded deps: http://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=gcc&id=ea1f0705-b9b6-4be7-aa1a-69be341b1e29&action=tail poldek: Retrieving th::cloog-isl-devel-0.18.3-2.x86_64.rpm... poldek: ..............................done poldek: Executing pm-command.sh --upgrade -vh --test --root / --define _check_dirname_deps 1... poldek: Preparing... ################################################## poldek: error: Install/Erase problems: poldek: file /usr/include/cloog/clast.h from install of cloog-isl-devel-0.18.3-2.x86_64 conflicts with file from package cloog-ppl-devel-0.16.1-2.x86_64 poldek: file /usr/include/cloog/cloog.h from install of cloog-isl-devel-0.18.3-2.x86_64 conflicts with file from package cloog-ppl-devel-0.16.1-2.x86_64 From glen at pld-linux.org Tue Oct 4 18:21:31 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 4 Oct 2016 19:21:31 +0300 Subject: python in docker In-Reply-To: <5735FFD7.6030103@pld-linux.org> References: <572CBDA8.3030703@pld-linux.org> <5735FFD7.6030103@pld-linux.org> Message-ID: <57F3D70B.9050005@pld-linux.org> back to that, any objections for the split to make our packaging more docker friendly? On 13.05.2016 19:24, Elan Ruusam?e wrote: > > i was thinking adding tzdata-zoneinfo subpackage, this way wouldn't > break any existing installations, > altho clearly tzdata-init would be better package name. > > or add tzdata-init and tzdata require tzdata-init for some undefined > migration time? > > > On 06.05.2016 18:52, Elan Ruusam?e wrote: >> so, i install some stuff with pip, and one package pulled in whole >> distro: >> >> what you think should we make tzdata be optional with rc-scripts >> dependency somehow? >> >> python-dateutil-2.5.0-1.noarch marks tzdata-2016c-1.noarch (cap >> tzdata >= 2016a) >> tzdata-2016c-1.noarch marks rc-scripts-0.4.15-4.x86_64 (cap >> /etc/rc.d/init.d) >> rc-scripts-0.4.15-4.x86_64 marks gettext-0.19.7-2.x86_64 (cap >> /bin/gettext) >> rc-scripts-0.4.15-4.x86_64 marks procps-3.3.11-1.x86_64 (cap /bin/ps) >> procps-3.3.11-1.x86_64 marks systemd-libs-221-13.x86_64 (cap >> libsystemd.so.0()(64bit)) >> systemd-libs-221-13.x86_64 marks lz4-libs-r131-4.x86_64 (cap >> liblz4.so.1()(64bit)) >> rc-scripts-0.4.15-4.x86_64 marks SysVinit-tools-2.88-18.x86_64 (cap >> SysVinit-tools >= 2.88-1) >> rc-scripts-0.4.15-4.x86_64 marks findutils-4.6.0-1.x86_64 (cap >> findutils) >> rc-scripts-0.4.15-4.x86_64 marks hostname-3.17-1.x86_64 (cap hostname) >> rc-scripts-0.4.15-4.x86_64 marks libutempter-1.1.6-5.x86_64 (cap >> libutempter >= 1.1.6-2) >> libutempter-1.1.6-5.x86_64 marks pwdutils-3.2.19-4.x86_64 (cap >> /usr/sbin/groupadd) >> pwdutils-3.2.19-4.x86_64 marks pam-1.1.8-8.x86_64 (cap /etc/pam.d) >> pam-1.1.8-8.x86_64 marks pam-libs-1.1.8-8.x86_64 (cap >> /lib64/security/pam_filter) >> pam-1.1.8-8.x86_64 marks cracklib-2.9.6-2.x86_64 (cap cracklib >> >= 2.8.3) >> pam-1.1.8-8.x86_64 marks cracklib-dicts-2.9.6-1.noarch (cap >> cracklib-dicts >= 2.8.3) >> pam-1.1.8-8.x86_64 marks libtirpc-0.3.2-1.x86_64 (cap >> libtirpc.so.1()(64bit)) >> libtirpc-0.3.2-1.x86_64 marks heimdal-libs-1.5.3-5.x86_64 (cap >> heimdal-libs) >> heimdal-libs-1.5.3-5.x86_64 marks libcom_err-1.42.13-1.x86_64 >> (cap libcom_err >= 1.41.11) >> pam-1.1.8-8.x86_64 marks libxcrypt-3.0.2-3.x86_64 (cap >> libxcrypt.so.2()(64bit)) >> pwdutils-3.2.19-4.x86_64 marks openldap-libs-2.4.43-3.x86_64 (cap >> liblber-2.4.so.2()(64bit)) >> openldap-libs-2.4.43-3.x86_64 marks >> cyrus-sasl-libs-2.1.26-5.x86_64 (cap cyrus-sasl-libs = 2.1.26) >> pwdutils-3.2.19-4.x86_64 marks libnscd-2.0.2-4.x86_64 (cap >> libnscd.so.1()(64bit)) >> rc-scripts-0.4.15-4.x86_64 marks psmisc-22.21-1.x86_64 (cap psmisc >> >= 22.5-2) >> rc-scripts-0.4.15-4.x86_64 marks util-linux-2.27.1-2.x86_64 (cap >> util-linux >= 2.22.1) >> util-linux-2.27.1-2.x86_64 marks libblkid-2.27.1-2.x86_64 (cap >> libblkid = 2.27.1-2) >> libblkid-2.27.1-2.x86_64 marks libuuid-2.27.1-2.x86_64 (cap >> libuuid = 2.27.1-2) >> util-linux-2.27.1-2.x86_64 marks libcap-ng-0.7.7-3.x86_64 (cap >> libcap-ng.so.0()(64bit)) >> util-linux-2.27.1-2.x86_64 marks libfdisk-2.27.1-2.x86_64 (cap >> libfdisk = 2.27.1-2) >> util-linux-2.27.1-2.x86_64 marks libmount-2.27.1-2.x86_64 (cap >> libmount.so.1()(64bit)) >> util-linux-2.27.1-2.x86_64 marks libsmartcols-2.27.1-2.x86_64 (cap >> libsmartcols = 2.27.1-2) >> util-linux-2.27.1-2.x86_64 marks udev-libs-221-13.x86_64 (cap >> libudev.so.1()(64bit)) >> rc-scripts-0.4.15-4.x86_64 marks SysVinit-2.88-18.x86_64 (cap >> virtual(init-daemon)) >> ... >> > > -- glen From glen at pld-linux.org Tue Oct 4 18:23:49 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 4 Oct 2016 19:23:49 +0300 Subject: python in docker In-Reply-To: <57F3D70B.9050005@pld-linux.org> References: <572CBDA8.3030703@pld-linux.org> <5735FFD7.6030103@pld-linux.org> <57F3D70B.9050005@pld-linux.org> Message-ID: <57F3D795.70501@pld-linux.org> one option would be just add /etc/rc.d/init.d dir to filesystem.spec On 04.10.2016 19:21, Elan Ruusam?e wrote: > back to that, > > any objections for the split to make our packaging more docker friendly? > > On 13.05.2016 19:24, Elan Ruusam?e wrote: >> >> i was thinking adding tzdata-zoneinfo subpackage, this way wouldn't >> break any existing installations, >> altho clearly tzdata-init would be better package name. >> >> or add tzdata-init and tzdata require tzdata-init for some undefined >> migration time? >> >> >> On 06.05.2016 18:52, Elan Ruusam?e wrote: >>> so, i install some stuff with pip, and one package pulled in whole >>> distro: >>> >>> what you think should we make tzdata be optional with rc-scripts >>> dependency somehow? >>> >>> python-dateutil-2.5.0-1.noarch marks tzdata-2016c-1.noarch (cap >>> tzdata >= 2016a) >>> tzdata-2016c-1.noarch marks rc-scripts-0.4.15-4.x86_64 (cap >>> /etc/rc.d/init.d) >>> rc-scripts-0.4.15-4.x86_64 marks gettext-0.19.7-2.x86_64 (cap >>> /bin/gettext) >>> rc-scripts-0.4.15-4.x86_64 marks procps-3.3.11-1.x86_64 (cap /bin/ps) >>> procps-3.3.11-1.x86_64 marks systemd-libs-221-13.x86_64 (cap >>> libsystemd.so.0()(64bit)) >>> systemd-libs-221-13.x86_64 marks lz4-libs-r131-4.x86_64 (cap >>> liblz4.so.1()(64bit)) >>> rc-scripts-0.4.15-4.x86_64 marks SysVinit-tools-2.88-18.x86_64 >>> (cap SysVinit-tools >= 2.88-1) >>> rc-scripts-0.4.15-4.x86_64 marks findutils-4.6.0-1.x86_64 (cap >>> findutils) >>> rc-scripts-0.4.15-4.x86_64 marks hostname-3.17-1.x86_64 (cap >>> hostname) >>> rc-scripts-0.4.15-4.x86_64 marks libutempter-1.1.6-5.x86_64 (cap >>> libutempter >= 1.1.6-2) >>> libutempter-1.1.6-5.x86_64 marks pwdutils-3.2.19-4.x86_64 (cap >>> /usr/sbin/groupadd) >>> pwdutils-3.2.19-4.x86_64 marks pam-1.1.8-8.x86_64 (cap /etc/pam.d) >>> pam-1.1.8-8.x86_64 marks pam-libs-1.1.8-8.x86_64 (cap >>> /lib64/security/pam_filter) >>> pam-1.1.8-8.x86_64 marks cracklib-2.9.6-2.x86_64 (cap cracklib >>> >= 2.8.3) >>> pam-1.1.8-8.x86_64 marks cracklib-dicts-2.9.6-1.noarch (cap >>> cracklib-dicts >= 2.8.3) >>> pam-1.1.8-8.x86_64 marks libtirpc-0.3.2-1.x86_64 (cap >>> libtirpc.so.1()(64bit)) >>> libtirpc-0.3.2-1.x86_64 marks heimdal-libs-1.5.3-5.x86_64 (cap >>> heimdal-libs) >>> heimdal-libs-1.5.3-5.x86_64 marks libcom_err-1.42.13-1.x86_64 >>> (cap libcom_err >= 1.41.11) >>> pam-1.1.8-8.x86_64 marks libxcrypt-3.0.2-3.x86_64 (cap >>> libxcrypt.so.2()(64bit)) >>> pwdutils-3.2.19-4.x86_64 marks openldap-libs-2.4.43-3.x86_64 >>> (cap liblber-2.4.so.2()(64bit)) >>> openldap-libs-2.4.43-3.x86_64 marks >>> cyrus-sasl-libs-2.1.26-5.x86_64 (cap cyrus-sasl-libs = 2.1.26) >>> pwdutils-3.2.19-4.x86_64 marks libnscd-2.0.2-4.x86_64 (cap >>> libnscd.so.1()(64bit)) >>> rc-scripts-0.4.15-4.x86_64 marks psmisc-22.21-1.x86_64 (cap psmisc >>> >= 22.5-2) >>> rc-scripts-0.4.15-4.x86_64 marks util-linux-2.27.1-2.x86_64 (cap >>> util-linux >= 2.22.1) >>> util-linux-2.27.1-2.x86_64 marks libblkid-2.27.1-2.x86_64 (cap >>> libblkid = 2.27.1-2) >>> libblkid-2.27.1-2.x86_64 marks libuuid-2.27.1-2.x86_64 (cap >>> libuuid = 2.27.1-2) >>> util-linux-2.27.1-2.x86_64 marks libcap-ng-0.7.7-3.x86_64 (cap >>> libcap-ng.so.0()(64bit)) >>> util-linux-2.27.1-2.x86_64 marks libfdisk-2.27.1-2.x86_64 (cap >>> libfdisk = 2.27.1-2) >>> util-linux-2.27.1-2.x86_64 marks libmount-2.27.1-2.x86_64 (cap >>> libmount.so.1()(64bit)) >>> util-linux-2.27.1-2.x86_64 marks libsmartcols-2.27.1-2.x86_64 >>> (cap libsmartcols = 2.27.1-2) >>> util-linux-2.27.1-2.x86_64 marks udev-libs-221-13.x86_64 (cap >>> libudev.so.1()(64bit)) >>> rc-scripts-0.4.15-4.x86_64 marks SysVinit-2.88-18.x86_64 (cap >>> virtual(init-daemon)) >>> ... >>> >> >> > > -- glen From glen at pld-linux.org Tue Oct 4 18:25:56 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 4 Oct 2016 19:25:56 +0300 Subject: python in docker In-Reply-To: <57F3D795.70501@pld-linux.org> References: <572CBDA8.3030703@pld-linux.org> <5735FFD7.6030103@pld-linux.org> <57F3D70B.9050005@pld-linux.org> <57F3D795.70501@pld-linux.org> Message-ID: <57F3D814.2080701@pld-linux.org> i tried this hack: bash-4.3# echo /etc/rc.d/init.d >> /etc/rpm/sysinfo/Dirnames but deps pulled rc-scripts. poldek bug? On 04.10.2016 19:23, Elan Ruusam?e wrote: > one option would be just add /etc/rc.d/init.d dir to filesystem.spec > > > On 04.10.2016 19:21, Elan Ruusam?e wrote: >> back to that, >> >> any objections for the split to make our packaging more docker friendly? >> >> On 13.05.2016 19:24, Elan Ruusam?e wrote: >>> >>> i was thinking adding tzdata-zoneinfo subpackage, this way wouldn't >>> break any existing installations, >>> altho clearly tzdata-init would be better package name. >>> >>> or add tzdata-init and tzdata require tzdata-init for some undefined >>> migration time? >>> >>> >>> On 06.05.2016 18:52, Elan Ruusam?e wrote: >>>> so, i install some stuff with pip, and one package pulled in whole >>>> distro: >>>> >>>> what you think should we make tzdata be optional with rc-scripts >>>> dependency somehow? >>>> >>>> python-dateutil-2.5.0-1.noarch marks tzdata-2016c-1.noarch (cap >>>> tzdata >= 2016a) >>>> tzdata-2016c-1.noarch marks rc-scripts-0.4.15-4.x86_64 (cap >>>> /etc/rc.d/init.d) >>>> rc-scripts-0.4.15-4.x86_64 marks gettext-0.19.7-2.x86_64 (cap >>>> /bin/gettext) -- glen From mis at pld-linux.org Wed Oct 5 10:02:28 2016 From: mis at pld-linux.org (=?UTF-8?B?UGF3ZcWCIEEuIEdhamRh?=) Date: Wed, 5 Oct 2016 10:02:28 +0200 Subject: python in docker In-Reply-To: <57F3D814.2080701@pld-linux.org> References: <572CBDA8.3030703@pld-linux.org> <5735FFD7.6030103@pld-linux.org> <57F3D70B.9050005@pld-linux.org> <57F3D795.70501@pld-linux.org> <57F3D814.2080701@pld-linux.org> Message-ID: On Tue, Oct 4, 2016 at 6:25 PM, Elan Ruusam?e wrote: > > i tried this hack: > > bash-4.3# echo /etc/rc.d/init.d >> /etc/rpm/sysinfo/Dirnames Would not help as "path" dependencies are resolved based on package contents, in fact rpm/poldek does not care if file/dir really exists. From mis at pld-linux.org Wed Oct 5 10:04:25 2016 From: mis at pld-linux.org (=?UTF-8?B?UGF3ZcWCIEEuIEdhamRh?=) Date: Wed, 5 Oct 2016 10:04:25 +0200 Subject: python in docker In-Reply-To: References: <572CBDA8.3030703@pld-linux.org> <5735FFD7.6030103@pld-linux.org> <57F3D70B.9050005@pld-linux.org> <57F3D795.70501@pld-linux.org> <57F3D814.2080701@pld-linux.org> Message-ID: On Wed, Oct 5, 2016 at 10:02 AM, Pawe? A. Gajda wrote: > On Tue, Oct 4, 2016 at 6:25 PM, Elan Ruusam?e wrote: > >> >> i tried this hack: >> >> bash-4.3# echo /etc/rc.d/init.d >> /etc/rpm/sysinfo/Dirnames > > > Would not help as "path" dependencies are resolved based on package > contents, in fact rpm/poldek does not care if file/dir really exists. > Unless I'm wrong :) rpm installs with this "hack"? From glen at pld-linux.org Wed Oct 5 21:00:43 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 5 Oct 2016 22:00:43 +0300 Subject: [packages/lz4] BR: gcc-multilib-32 on x86_64 In-Reply-To: References: Message-ID: <57F54DDB.40205@pld-linux.org> On 05.10.2016 15:25, jajcus wrote: > commit a65ca274e017a51e493f3505a914eebe057bbc1f > Author: Jacek Konieczny > Date: Wed Oct 5 14:25:30 2016 +0200 > > BR: gcc-multilib-32 on x86_64 > > lz4.spec | 3 +++ > 1 file changed, 3 insertions(+) > --- > diff --git a/lz4.spec b/lz4.spec > index e20db04..784a4e1 100644 > --- a/lz4.spec > +++ b/lz4.spec > @@ -8,6 +8,9 @@ Group: Applications > Source0: https://github.com/Cyan4973/lz4/archive/%{version}/%{name}-%{version}.tar.gz > # Source0-md5: 42b09fab42331da9d3fb33bd5c560de9 > URL: http://www.lz4.org/ > +%ifarch %{x8664} > +BuildRequires: gcc-multilib-32 > +%endif > Requires: %{name}-libs = %{version}-%{release} > BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) > uh? this is for tests? or does really x86-64 build process compile 32bit libs somewhere? -- glen From glen at pld-linux.org Wed Oct 5 21:03:34 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 5 Oct 2016 22:03:34 +0300 Subject: python in docker In-Reply-To: References: <572CBDA8.3030703@pld-linux.org> <5735FFD7.6030103@pld-linux.org> <57F3D70B.9050005@pld-linux.org> <57F3D795.70501@pld-linux.org> <57F3D814.2080701@pld-linux.org> Message-ID: <57F54E86.1050506@pld-linux.org> On 05.10.2016 11:04, Pawe? A. Gajda wrote: > On Wed, Oct 5, 2016 at 10:02 AM, Pawe? A. Gajda wrote: > >> On Tue, Oct 4, 2016 at 6:25 PM, Elan Ruusam?e wrote: >> >>> i tried this hack: >>> >>> bash-4.3# echo /etc/rc.d/init.d >> /etc/rpm/sysinfo/Dirnames >> >> Would not help as "path" dependencies are resolved based on package >> contents, in fact rpm/poldek does not care if file/dir really exists. >> > Unless I'm wrong :) rpm installs with this "hack"? yes. and poldek can be told: -O 'auto directory dependencies=no' -- glen From qboosh at pld-linux.org Thu Oct 6 22:11:41 2016 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Thu, 6 Oct 2016 22:11:41 +0200 Subject: qemu sysprefix In-Reply-To: <57EAE164.8030803@pld-linux.org> References: <57EAD112.1050906@pld-linux.org> <20160927202034.GA31764@mail> <57EAE164.8030803@pld-linux.org> Message-ID: <20161006201141.GA32523@mail> On Wed, Sep 28, 2016 at 12:15:16AM +0300, Elan Ruusam?e wrote: > On 27.09.2016 23:20, Jakub Bogusz wrote: > >On Tue, Sep 27, 2016 at 11:05:38PM +0300, Elan Ruusam?e wrote: > >>anything against changing > >> > >> --interp-prefix=%{_libdir}/qemu/lib-%%M > >>to: > >> --interp-prefix=%{_prefix}/qemu-%%M > >What is _prefix in qemu? > >If /usr, then /usr/qemu-* is not FHS compliant. > yes, /usr > > i thought FHS allowed /usr/ paths for such purpose Creating additional hierarchies under /usr is not covered by FHS (except for X11R6 in the past)... cross* packages and uClibc are packaged in such way due to some inertia (dietlibc and klibc use more appropriate scheme). IMO they should use /usr/%{_lib}/triplet or /usr/lib/triplet (if host dependent files are not expected). > >>reason: > >> > >>qemu-user(-static) would expect target system libraries from there. > >>qemu-user(-static) does not require qemu-common, in which current > >>%{_libdir}/qemu is contained in. > >Is %{_libdir}/qemu dir ownership the only reason? > 1. dir ownership > 2. inconsistent path (it's different on all th arches due %{_libdir} prefix) > > btw, upstream default is: > > ??? ./configure --help|grep %M > use %M for cpu name [/usr/gnemul/qemu-%M] If no host dependent files are expected there, we could use /usr/lib/qemu-%M or /usr/lib/gnemul/qemu-%M (what "gnemul" stands for?) > >If so, you can even add it to every qemu-user* package. > > /usr/lib/binfmt.d also bothers, but that can be moved to filesystem.spec /usr/lib/binfmt.d seems to belong to systemd-units already... -- Jakub Bogusz http://qboosh.pl/ From glen at pld-linux.org Thu Oct 6 23:39:02 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 7 Oct 2016 00:39:02 +0300 Subject: qemu sysprefix In-Reply-To: <20161006201141.GA32523@mail> References: <57EAD112.1050906@pld-linux.org> <20160927202034.GA31764@mail> <57EAE164.8030803@pld-linux.org> <20161006201141.GA32523@mail> Message-ID: <57F6C476.3040308@pld-linux.org> On 06.10.2016 23:11, Jakub Bogusz wrote: >>> If so, you can even add it to every qemu-user* package. >> > >> >/usr/lib/binfmt.d also bothers, but that can be moved to filesystem.spec > /usr/lib/binfmt.d seems to belong to systemd-units already... i mean to install qemu-user-static, there should be no dependencies (because it's static binary) -- glen From glen at pld-linux.org Thu Oct 6 23:46:07 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 7 Oct 2016 00:46:07 +0300 Subject: qemu sysprefix In-Reply-To: <20161006201141.GA32523@mail> References: <57EAD112.1050906@pld-linux.org> <20160927202034.GA31764@mail> <57EAE164.8030803@pld-linux.org> <20161006201141.GA32523@mail> Message-ID: <57F6C61F.4020809@pld-linux.org> On 06.10.2016 23:11, Jakub Bogusz wrote: > If no host dependent files are expected there, we could use > /usr/lib/qemu-%M or /usr/lib/gnemul/qemu-%M (what "gnemul" stands for?) no idea, perhaps gnu-emulator? or just tarball that fabrice used for his guest os images? https://github.com/chtk/optware/blob/master/make/qemu-gnemul.mk -- glen From adwol at zonk.pl Sat Oct 8 23:59:00 2016 From: adwol at zonk.pl (Adam Osuchowski) Date: Sat, 8 Oct 2016 23:59:00 +0200 Subject: 64-bit binaries in /usr/lib Message-ID: <20161008215900.6b8b4567@zonk.pl> Simple question: why have some packages their arch-dependent executables placed in /usr/lib directory on x86-64 architecture? What principle determines that these binaries are forced to be in /usr/lib instead of /usr/lib64? From glen at pld-linux.org Sun Oct 9 13:03:07 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 9 Oct 2016 14:03:07 +0300 Subject: 64-bit binaries in /usr/lib In-Reply-To: <20161008215900.6b8b4567@zonk.pl> References: <20161008215900.6b8b4567@zonk.pl> Message-ID: <57FA23EB.5030506@pld-linux.org> On 09.10.2016 00:59, Adam Osuchowski wrote: > Simple question: why have some packages their arch-dependent executables > placed in /usr/lib directory on x86-64 architecture? What principle > determines that these binaries are forced to be in /usr/lib instead of > /usr/lib64? every package probably has reason, given examples it would be easier to explain. it may be deliberately packaged like this in pld, or just because upstream uses such packaging (and it's not "fixed" in pld) but the (--libdir) /usr/lib vs /usr/lib64 (and /usr/libx32) are for libraries (libfoo.so.1), so you could parallel install libfoo.so.1(ix84) and libfoo.so.1(x86-64). there's also --libexecdir which is %{_libdir} in pld, but %{_prefix}/libexec in other distros, and that path is used to provide private binaries for application (not intended to be used from $PATH), that is the most common case how binaries end up in /usr/lib* trees. i personally also think --libexecdir should be %{_prefix}/libexec. it would make configurations simpler, don't need to patch for %{_libdir} everywhere. -- glen From adwol at zonk.pl Sun Oct 9 14:08:52 2016 From: adwol at zonk.pl (Adam Osuchowski) Date: Sun, 9 Oct 2016 14:08:52 +0200 Subject: 64-bit binaries in /usr/lib In-Reply-To: <57FA23EB.5030506@pld-linux.org> References: <20161008215900.6b8b4567@zonk.pl> <57FA23EB.5030506@pld-linux.org> Message-ID: <20161009120852.6b8b4567@zonk.pl> Elan Ruusam?e wrote: > every package probably has reason, given examples it would be easier to > explain. $ rpm -qf `find {/usr,}/lib -type f -perm -0100 | xargs file | grep 'ELF 64-bit LSB executable' | cut -f1 -d:` | sort -u ConsoleKit-0.4.6-3.x86_64 cups-filters-1.8.3-3.x86_64 git-core-2.10.0-1.x86_64 git-core-svn-2.10.0-1.x86_64 libinput-1.4.1-1.x86_64 nagios-plugin-check_load-2.1.3-1.x86_64 nagios-plugins-2.1.3-1.x86_64 polkit-0.113-3.x86_64 rpm-5.4.15-37.x86_64 rpm-build-5.4.15-37.x86_64 rpm-utils-5.4.15-37.x86_64 sysstat-11.2.0-3.x86_64 udisks-1.0.5-3.x86_64 In particular, git-core kept its binaries in /usr/lib64 formerly but it was changed to /usr/lib. nagios-common contains both of them: $ rpm -qf /usr/lib{,64}/nagios/plugins nagios-common-4.0.8-5.x86_64 nagios-common-4.0.8-5.x86_64 cups and rpm keep /usr/lib all the time. > it may be deliberately packaged like this in pld, or just because > upstream uses such packaging (and it's not "fixed" in pld) It is rather PLD issue. > but the (--libdir) /usr/lib vs /usr/lib64 (and /usr/libx32) are for > libraries (libfoo.so.1), so you could parallel install libfoo.so.1(ix84) > and libfoo.so.1(x86-64). That is, shared libraries on x86-64 arch should be placed in {/usr,}/lib64 and binaries (not intended to run directly by user), scripts and other private package files in {/usr,}/lib. Do I understand it correctly? > there's also --libexecdir which is %{_libdir} in pld, but > %{_prefix}/libexec in other distros, and that path is used to provide > private binaries for application (not intended to be used from $PATH), that > is the most common case how binaries end up in /usr/lib* trees. > > i personally also think --libexecdir should be %{_prefix}/libexec. it would > make configurations simpler, don't need to patch for %{_libdir} everywhere. I know but now it is totally removed and no package use it: # ipoldek 'search -f /usr/libexec/*' Loading [pndir]th... Loading [pndir]th... 26078 packages read Loading [rpmdbcache]/var/lib/rpm... 3352 packages loaded Searching packages..........................................done. No package matches '/usr/libexec/*' Besides, FSB admits of using /usr/lib insted of /usr/libexec. From glen at pld-linux.org Sun Oct 9 18:29:00 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 9 Oct 2016 19:29:00 +0300 Subject: 64-bit binaries in /usr/lib In-Reply-To: <20161009120852.6b8b4567@zonk.pl> References: <20161008215900.6b8b4567@zonk.pl> <57FA23EB.5030506@pld-linux.org> <20161009120852.6b8b4567@zonk.pl> Message-ID: <57FA704C.3090008@pld-linux.org> On 09.10.2016 15:08, Adam Osuchowski wrote: > Elan Ruusam?e wrote: >> every package probably has reason, given examples it would be easier to >> explain. > $ rpm -qf `find {/usr,}/lib -type f -perm -0100 | xargs file | grep 'ELF 64-bit LSB executable' | cut -f1 -d:` | sort -u > ConsoleKit-0.4.6-3.x86_64 > cups-filters-1.8.3-3.x86_64 > git-core-2.10.0-1.x86_64 > git-core-svn-2.10.0-1.x86_64 > libinput-1.4.1-1.x86_64 > nagios-plugin-check_load-2.1.3-1.x86_64 > nagios-plugins-2.1.3-1.x86_64 > polkit-0.113-3.x86_64 > rpm-5.4.15-37.x86_64 > rpm-build-5.4.15-37.x86_64 > rpm-utils-5.4.15-37.x86_64 > sysstat-11.2.0-3.x86_64 > udisks-1.0.5-3.x86_64 > > In particular, git-core kept its binaries in /usr/lib64 formerly but it > was changed to /usr/lib. it's in changelog, to allow adding programs to git-core dir without forcing them to be "arch" packages, ie git-core-slug is itself noarch. > nagios-common contains both of them: > > $ rpm -qf /usr/lib{,64}/nagios/plugins > nagios-common-4.0.8-5.x86_64 > nagios-common-4.0.8-5.x86_64 the same reason: to allow libexec dir to be noarch to allow noarch packages. and the lib64 is kept for compatibility. > cups and rpm keep /usr/lib all the time. those are upstream decisions, but likely due same reasons as above two pld packagings. > >> it may be deliberately packaged like this in pld, or just because >> upstream uses such packaging (and it's not "fixed" in pld) > It is rather PLD issue. 1:1 so far with given examples, it's even! > >> but the (--libdir) /usr/lib vs /usr/lib64 (and /usr/libx32) are for >> libraries (libfoo.so.1), so you could parallel install libfoo.so.1(ix84) >> and libfoo.so.1(x86-64). > That is, shared libraries on x86-64 arch should be placed in {/usr,}/lib64 > and binaries (not intended to run directly by user), scripts and other > private package files in {/usr,}/lib. Do I understand it correctly? pld has not standardized this to my knowledge. and i haven't read FHS part which pld tries to follow. >> there's also --libexecdir which is %{_libdir} in pld, but >> %{_prefix}/libexec in other distros, and that path is used to provide >> private binaries for application (not intended to be used from $PATH), that >> is the most common case how binaries end up in /usr/lib* trees. >> >> i personally also think --libexecdir should be %{_prefix}/libexec. it would >> make configurations simpler, don't need to patch for %{_libdir} everywhere. > I know but now it is totally removed and no package use it: > > # ipoldek 'search -f /usr/libexec/*' > Loading [pndir]th... > Loading [pndir]th... > 26078 packages read > Loading [rpmdbcache]/var/lib/rpm... > 3352 packages loaded > Searching packages..........................................done. > No package matches '/usr/libexec/*' that is because %{_libexecdir} is defined as %{_libdir} in pld, and that gets passed so to configure --libexecdir argument so the applications using @libexecdir@ get their files placed to %{_libdir} some programs even have had issues with this because they want to place %{_libexecdir}/%{name} as directory and %{_libdir}/%{name} as executable which would both end up with /usr/lib64/mate-settings-daemon > Besides, FSB admits of using /usr/lib insted of /usr/libexec. FSB? you mean LSB? FHS? -- glen From glen at pld-linux.org Mon Oct 10 23:29:11 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 11 Oct 2016 00:29:11 +0300 Subject: glibc <> libselinux dep loop Message-ID: <57FC0827.6010701@pld-linux.org> proposition to move it to subpackage. question: by what name? what else to include in it? i think it's the tool used to make /var/db files that used to be in 'db' package... [~/rpm/packages/BUILD.x86_64-linux/1] ? rpm -ql glibc|xargs grep selinux 2>/dev/null Binary file /usr/bin/makedb matches Binary file /usr/share/locale/cs/LC_MESSAGES/libc.mo matches Binary file /usr/bin/makedb matches Binary file /usr/share/locale/cs/LC_MESSAGES/libc.mo matches Binary file /usr/bin/makedb matches Binary file /usr/share/locale/cs/LC_MESSAGES/libc.mo matches [~/rpm/packages/BUILD.x86_64-linux/1] ? ldd /usr/bin/makedb linux-vdso.so.1 (0x00007ffe6e510000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f5492ce1000) libc.so.6 => /lib64/libc.so.6 (0x00007f549293f000) libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f54926cd000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f54924c9000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f54922ac000) /lib64/ld-linux-x86-64.so.2 (0x00007f5492f03000) [~/rpm/packages/BUILD.x86_64-linux/1] ? file /usr/bin/makedb /usr/bin/makedb: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=ad9bf7490b95c93f3424a6afb9f3ef8d82414f65, stripped [~/rpm/packages/BUILD.x86_64-linux/1] ? makedb --help Usage: makedb [OPTION...] INPUT-FILE OUTPUT-FILE or: makedb [OPTION...] -o OUTPUT-FILE INPUT-FILE or: makedb [OPTION...] -u INPUT-FILE Create simple database from textual input. -f, --fold-case Convert key to lower case -g, --generated=CHAR Generated line not part of iteration -o, --output=NAME Write output to file NAME -q, --quiet Do not print messages while building database -u, --undo Print content of database file, one entry a line -?, --help Give this help list --usage Give a short usage message -V, --version Print program version Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. For bug reporting instructions, please see: . [~/rpm/packages/BUILD.x86_64-linux/1] ? -- glen From glen at pld-linux.org Mon Oct 10 23:32:25 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 11 Oct 2016 00:32:25 +0300 Subject: glibc <> libselinux dep loop In-Reply-To: <57FC0827.6010701@pld-linux.org> References: <57FC0827.6010701@pld-linux.org> Message-ID: <57FC08E9.8000000@pld-linux.org> On 11.10.2016 00:29, Elan Ruusam?e wrote: > proposition to move it to subpackage. btw, (i believe) it makes poldek stop processing dependencies and therefore failing to match all packages. ? poldek -e glibc-2.23-5.i686 libselinux-2.4-2.i686 mark glibc-2.23-5.i686 mark libselinux-2.4-2.i686 Processing dependencies... glibc-2.23-5.i686 marks burn-tools-0.1-1.i686 (req libc.so.6) glibc-2.23-5.i686 marks ism-cli-8.40.20.141-1.i686 (req libc.so.6) glibc-2.23-5.i686 marks compat-libstdc++-3.3-3.3.6-3.i686 (req libc.so.6) glibc-2.23-5.i686 marks libgcc-multilib-4.8.3-3.x86_64 (req libc.so.6) There are 6 packages to remove (4 marked by dependencies): R glibc-2.23-5.i686 libselinux-2.4-2.i686 D burn-tools-0.1-1.i686 compat-libstdc++-3.3-3.3.6-3.i686 ism-cli-8.40.20.141-1.i686 libgcc-multilib-4.8.3-3.x86_64 This operation will free 10.6MB of disk space. Proceed? [N/y] y Running pm-command.sh --erase --root /... error: Failed dependencies: libc.so.6 is needed by (installed) libffi-3.2.1-3.i686 libc.so.6 is needed by (installed) attr-2.4.47-2.i686 libc.so.6 is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6 is needed by (installed) libgcrypt-1.6.4-1.i686 libc.so.6 is needed by (installed) lz4-libs-r131-4.i686 libc.so.6 is needed by (installed) pcre-8.38-1.i686 libc.so.6 is needed by (installed) bzip2-libs-1.0.6-2.i686 libc.so.6 is needed by (installed) zlib-1.2.8-2.i686 libc.so.6 is needed by (installed) libpng-1.6.20-1.i686 libc.so.6 is needed by (installed) xorg-lib-libxshmfence-1.2-2.i686 libc.so.6 is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6 is needed by (installed) nss-softokn-freebl-3.21-1.i686 libc.so.6 is needed by (installed) xz-libs-5.2.2-1.i686 libc.so.6 is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6 is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6 is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6 is needed by (installed) libxcrypt-3.0.2-3.i686 libc.so.6 is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6 is needed by (installed) libjpeg-9a-1.i686 libc.so.6 is needed by (installed) jbigkit-2.1-3.i686 libc.so.6 is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6 is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6 is needed by (installed) wayland-1.9.0-1.i686 libc.so.6 is needed by (installed) lzo-2.08-2.i686 libc.so.6 is needed by (installed) lcms2-2.7-1.i686 libc.so.6 is needed by (installed) gdbm18-1.8.3-2.i686 libc.so.6 is needed by (installed) gdbm-1.11-2.i686 libc.so.6 is needed by (installed) lcms-1.19-4.i686 libc.so.6 is needed by (installed) libmng-2.0.3-1.i686 libc.so.6 is needed by (installed) libltdl-2.4.6-6.i686 libc.so.6 is needed by (installed) orc-0.4.24-1.i686 libc.so.6 is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6 is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6 is needed by (installed) libogg-1.3.2-2.i686 libc.so.6 is needed by (installed) speexdsp-1.2-0.rc3.3.i686 libc.so.6 is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6 is needed by (installed) libnl-3.2.25-2.i686 libc.so.6 is needed by (installed) json-c-0.12-2.i686 libc.so.6 is needed by (installed) flac-1.3.1-6.i686 libc.so.6 is needed by (installed) libvorbis-1.3.5-1.i686 libc.so.6 is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6 is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6 is needed by (installed) expat-2.1.1-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libffi-3.2.1-3.i686 libc.so.6(GLIBC_2.0) is needed by (installed) attr-2.4.47-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libgcrypt-1.6.4-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) lz4-libs-r131-4.i686 libc.so.6(GLIBC_2.0) is needed by (installed) pcre-8.38-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) bzip2-libs-1.0.6-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) zlib-1.2.8-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libpng-1.6.20-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) xorg-lib-libxshmfence-1.2-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) xz-libs-5.2.2-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.0) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libxcrypt-3.0.2-3.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libjpeg-9a-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) jbigkit-2.1-3.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) lzo-2.08-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) lcms2-2.7-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) gdbm18-1.8.3-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) lcms-1.19-4.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libmng-2.0.3-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libltdl-2.4.6-6.i686 libc.so.6(GLIBC_2.0) is needed by (installed) orc-0.4.24-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libogg-1.3.2-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) speexdsp-1.2-0.rc3.3.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libnl-3.2.25-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) json-c-0.12-2.i686 libc.so.6(GLIBC_2.0) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libvorbis-1.3.5-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6(GLIBC_2.0) is needed by (installed) expat-2.1.1-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libffi-3.2.1-3.i686 libc.so.6(GLIBC_2.1) is needed by (installed) attr-2.4.47-2.i686 libc.so.6(GLIBC_2.1) is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libgcrypt-1.6.4-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) bzip2-libs-1.0.6-2.i686 libc.so.6(GLIBC_2.1) is needed by (installed) zlib-1.2.8-2.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libpng-1.6.20-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.1) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) lcms2-2.7-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.1) is needed by (installed) lcms-1.19-4.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libltdl-2.4.6-6.i686 libc.so.6(GLIBC_2.1) is needed by (installed) orc-0.4.24-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libnl-3.2.25-2.i686 libc.so.6(GLIBC_2.1) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libvorbis-1.3.5-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6(GLIBC_2.1) is needed by (installed) expat-2.1.1-1.i686 libc.so.6(GLIBC_2.1.2) is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6(GLIBC_2.1.2) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libffi-3.2.1-3.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libgcrypt-1.6.4-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) lz4-libs-r131-4.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) pcre-8.38-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) bzip2-libs-1.0.6-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) zlib-1.2.8-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libpng-1.6.20-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) xorg-lib-libxshmfence-1.2-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) xz-libs-5.2.2-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libxcrypt-3.0.2-3.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libjpeg-9a-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) jbigkit-2.1-3.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) lzo-2.08-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) lcms2-2.7-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) gdbm18-1.8.3-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) lcms-1.19-4.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libmng-2.0.3-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libltdl-2.4.6-6.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) orc-0.4.24-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libogg-1.3.2-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) speexdsp-1.2-0.rc3.3.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libnl-3.2.25-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) json-c-0.12-2.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libvorbis-1.3.5-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6(GLIBC_2.1.3) is needed by (installed) expat-2.1.1-1.i686 libc.so.6(GLIBC_2.10) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.11) is needed by (installed) libpng-1.6.20-1.i686 libc.so.6(GLIBC_2.11) is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6(GLIBC_2.11) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.11) is needed by (installed) libmng-2.0.3-1.i686 libc.so.6(GLIBC_2.11) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.11) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.15) is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6(GLIBC_2.15) is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6(GLIBC_2.17) is needed by (installed) xz-libs-5.2.2-1.i686 libc.so.6(GLIBC_2.17) is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6(GLIBC_2.2) is needed by (installed) attr-2.4.47-2.i686 libc.so.6(GLIBC_2.2) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.2) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.2) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.2) is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6(GLIBC_2.2) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.2) is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6(GLIBC_2.2) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.2) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.2) is needed by (installed) orc-0.4.24-1.i686 libc.so.6(GLIBC_2.2) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.2) is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6(GLIBC_2.2.4) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.3) is needed by (installed) attr-2.4.47-2.i686 libc.so.6(GLIBC_2.3) is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libgcrypt-1.6.4-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) pcre-8.38-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) bzip2-libs-1.0.6-2.i686 libc.so.6(GLIBC_2.3) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.3) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) lcms2-2.7-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.3) is needed by (installed) lcms-1.19-4.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libltdl-2.4.6-6.i686 libc.so.6(GLIBC_2.3) is needed by (installed) orc-0.4.24-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libnl-3.2.25-2.i686 libc.so.6(GLIBC_2.3) is needed by (installed) json-c-0.12-2.i686 libc.so.6(GLIBC_2.3) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libvorbis-1.3.5-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6(GLIBC_2.3) is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6(GLIBC_2.3.2) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) attr-2.4.47-2.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libgcrypt-1.6.4-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) pcre-8.38-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) bzip2-libs-1.0.6-2.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) zlib-1.2.8-2.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libpng-1.6.20-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libxcrypt-3.0.2-3.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libjpeg-9a-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) lcms2-2.7-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) lcms-1.19-4.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libltdl-2.4.6-6.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) orc-0.4.24-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) speexdsp-1.2-0.rc3.3.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libnl-3.2.25-2.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) json-c-0.12-2.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6(GLIBC_2.3.4) is needed by (installed) expat-2.1.1-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libffi-3.2.1-3.i686 libc.so.6(GLIBC_2.4) is needed by (installed) attr-2.4.47-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) cracklib-2.9.6-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libgcrypt-1.6.4-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) pcre-8.38-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) bzip2-libs-1.0.6-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) zlib-1.2.8-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libpng-1.6.20-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) xorg-lib-libxshmfence-1.2-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) xz-libs-5.2.2-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.4) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libgpg-error-1.21-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libxcrypt-3.0.2-3.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libjpeg-9a-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) jbigkit-2.1-3.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libtiff-4.0.6-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libdrm-2.4.66-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) lzo-2.08-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) lcms2-2.7-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) lcms-1.19-4.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libmng-2.0.3-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libltdl-2.4.6-6.i686 libc.so.6(GLIBC_2.4) is needed by (installed) orc-0.4.24-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libogg-1.3.2-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libnl-3.2.25-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) json-c-0.12-2.i686 libc.so.6(GLIBC_2.4) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libvorbis-1.3.5-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) libsndfile-1.0.26-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6(GLIBC_2.4) is needed by (installed) expat-2.1.1-1.i686 libc.so.6(GLIBC_2.7) is needed by (installed) libffi-3.2.1-3.i686 libc.so.6(GLIBC_2.7) is needed by (installed) attr-2.4.47-2.i686 libc.so.6(GLIBC_2.7) is needed by (installed) xorg-lib-libpciaccess-0.13.4-1.i686 libc.so.6(GLIBC_2.7) is needed by (installed) libjpeg-turbo-1.4.2-1.i686 libc.so.6(GLIBC_2.7) is needed by (installed) libjpeg-9a-1.i686 libc.so.6(GLIBC_2.7) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.7) is needed by (installed) lcms2-2.7-1.i686 libc.so.6(GLIBC_2.7) is needed by (installed) gdbm-1.11-2.i686 libc.so.6(GLIBC_2.7) is needed by (installed) lcms-1.19-4.i686 libc.so.6(GLIBC_2.7) is needed by (installed) t1lib-5.1.2-9.i686 libc.so.6(GLIBC_2.7) is needed by (installed) libmpg123-1.22.4-1.i686 libc.so.6(GLIBC_2.7) is needed by (installed) libwrap-libs-7.6-47.i686 libc.so.6(GLIBC_2.7) is needed by (installed) flac-1.3.1-6.i686 libc.so.6(GLIBC_2.7) is needed by (installed) openssl-1.0.2h-1.i686 libc.so.6(GLIBC_2.8) is needed by (installed) audit-libs-2.4.4-3.i686 libc.so.6(GLIBC_2.8) is needed by (installed) pam-libs-1.1.8-8.i686 libc.so.6(GLIBC_2.8) is needed by (installed) libxcrypt-3.0.2-3.i686 libc.so.6(GLIBC_2.8) is needed by (installed) wayland-1.9.0-1.i686 libc.so.6(GLIBC_2.8) is needed by (installed) libnl-3.2.25-2.i686 libc.so.6(GLIBC_2.8) is needed by (installed) json-c-0.12-2.i686 libc.so.6(GLIBC_2.9) is needed by (installed) wayland-1.9.0-1.i686 libdl.so.2 is needed by (installed) nss-softokn-freebl-3.21-1.i686 libdl.so.2 is needed by (installed) pam-libs-1.1.8-8.i686 libdl.so.2 is needed by (installed) libxcrypt-3.0.2-3.i686 libdl.so.2 is needed by (installed) libltdl-2.4.6-6.i686 libdl.so.2 is needed by (installed) libnl-3.2.25-2.i686 libdl.so.2 is needed by (installed) openssl-1.0.2h-1.i686 libdl.so.2(GLIBC_2.0) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libdl.so.2(GLIBC_2.0) is needed by (installed) pam-libs-1.1.8-8.i686 libdl.so.2(GLIBC_2.0) is needed by (installed) libxcrypt-3.0.2-3.i686 libdl.so.2(GLIBC_2.0) is needed by (installed) libltdl-2.4.6-6.i686 libdl.so.2(GLIBC_2.0) is needed by (installed) libnl-3.2.25-2.i686 libdl.so.2(GLIBC_2.0) is needed by (installed) openssl-1.0.2h-1.i686 libdl.so.2(GLIBC_2.1) is needed by (installed) nss-softokn-freebl-3.21-1.i686 libdl.so.2(GLIBC_2.1) is needed by (installed) pam-libs-1.1.8-8.i686 libdl.so.2(GLIBC_2.1) is needed by (installed) libxcrypt-3.0.2-3.i686 libdl.so.2(GLIBC_2.1) is needed by (installed) libltdl-2.4.6-6.i686 libdl.so.2(GLIBC_2.1) is needed by (installed) libnl-3.2.25-2.i686 libdl.so.2(GLIBC_2.1) is needed by (installed) openssl-1.0.2h-1.i686 libm.so.6 is needed by (installed) libpng-1.6.20-1.i686 libm.so.6 is needed by (installed) libtiff-4.0.6-1.i686 libm.so.6 is needed by (installed) libdrm-2.4.66-1.i686 libm.so.6 is needed by (installed) lcms2-2.7-1.i686 libm.so.6 is needed by (installed) lcms-1.19-4.i686 libm.so.6 is needed by (installed) libmng-2.0.3-1.i686 libm.so.6 is needed by (installed) orc-0.4.24-1.i686 libm.so.6 is needed by (installed) t1lib-5.1.2-9.i686 libm.so.6 is needed by (installed) libmpg123-1.22.4-1.i686 libm.so.6 is needed by (installed) speexdsp-1.2-0.rc3.3.i686 libm.so.6 is needed by (installed) libnl-3.2.25-2.i686 libm.so.6 is needed by (installed) flac-1.3.1-6.i686 libm.so.6 is needed by (installed) libvorbis-1.3.5-1.i686 libm.so.6 is needed by (installed) libsndfile-1.0.26-1.i686 libm.so.6(GLIBC_2.0) is needed by (installed) libpng-1.6.20-1.i686 libm.so.6(GLIBC_2.0) is needed by (installed) libtiff-4.0.6-1.i686 libm.so.6(GLIBC_2.0) is needed by (installed) lcms2-2.7-1.i686 libm.so.6(GLIBC_2.0) is needed by (installed) lcms-1.19-4.i686 libm.so.6(GLIBC_2.0) is needed by (installed) libmng-2.0.3-1.i686 libm.so.6(GLIBC_2.0) is needed by (installed) orc-0.4.24-1.i686 libm.so.6(GLIBC_2.0) is needed by (installed) t1lib-5.1.2-9.i686 libm.so.6(GLIBC_2.0) is needed by (installed) libmpg123-1.22.4-1.i686 libm.so.6(GLIBC_2.0) is needed by (installed) speexdsp-1.2-0.rc3.3.i686 libm.so.6(GLIBC_2.0) is needed by (installed) flac-1.3.1-6.i686 libm.so.6(GLIBC_2.0) is needed by (installed) libsndfile-1.0.26-1.i686 libm.so.6(GLIBC_2.1) is needed by (installed) libdrm-2.4.66-1.i686 libm.so.6(GLIBC_2.1) is needed by (installed) lcms2-2.7-1.i686 libm.so.6(GLIBC_2.1) is needed by (installed) lcms-1.19-4.i686 libm.so.6(GLIBC_2.1) is needed by (installed) t1lib-5.1.2-9.i686 libm.so.6(GLIBC_2.1) is needed by (installed) speexdsp-1.2-0.rc3.3.i686 libm.so.6(GLIBC_2.1) is needed by (installed) libnl-3.2.25-2.i686 libm.so.6(GLIBC_2.1) is needed by (installed) flac-1.3.1-6.i686 libm.so.6(GLIBC_2.15) is needed by (installed) libvorbis-1.3.5-1.i686 libpthread.so.0 is needed by (installed) pcre-8.38-1.i686 libpthread.so.0 is needed by (installed) xz-libs-5.2.2-1.i686 libpthread.so.0 is needed by (installed) libtiff-4.0.6-1.i686 libpthread.so.0 is needed by (installed) wayland-1.9.0-1.i686 libpthread.so.0 is needed by (installed) lcms2-2.7-1.i686 libpthread.so.0 is needed by (installed) gdbm-1.11-2.i686 libpthread.so.0 is needed by (installed) libmng-2.0.3-1.i686 libpthread.so.0 is needed by (installed) orc-0.4.24-1.i686 libpthread.so.0 is needed by (installed) libnl-3.2.25-2.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) pcre-8.38-1.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) xz-libs-5.2.2-1.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) libtiff-4.0.6-1.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) wayland-1.9.0-1.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) lcms2-2.7-1.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) gdbm-1.11-2.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) orc-0.4.24-1.i686 libpthread.so.0(GLIBC_2.0) is needed by (installed) libnl-3.2.25-2.i686 libpthread.so.0(GLIBC_2.1) is needed by (installed) xz-libs-5.2.2-1.i686 libpthread.so.0(GLIBC_2.1) is needed by (installed) libnl-3.2.25-2.i686 libpthread.so.0(GLIBC_2.2) is needed by (installed) libtiff-4.0.6-1.i686 libpthread.so.0(GLIBC_2.2) is needed by (installed) gdbm-1.11-2.i686 libpthread.so.0(GLIBC_2.3.2) is needed by (installed) xz-libs-5.2.2-1.i686 libpthread.so.0(GLIBC_2.3.2) is needed by (installed) wayland-1.9.0-1.i686 libpthread.so.0(GLIBC_2.3.3) is needed by (installed) xz-libs-5.2.2-1.i686 librt.so.1 is needed by (installed) wayland-1.9.0-1.i686 librt.so.1(GLIBC_2.2) is needed by (installed) wayland-1.9.0-1.i686 [~] ? -- glen From qboosh at pld-linux.org Tue Oct 11 05:44:40 2016 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Tue, 11 Oct 2016 05:44:40 +0200 Subject: glibc <> libselinux dep loop In-Reply-To: <57FC0827.6010701@pld-linux.org> References: <57FC0827.6010701@pld-linux.org> Message-ID: <20161011034440.GA15341@mail> On Tue, Oct 11, 2016 at 12:29:11AM +0300, Elan Ruusam?e wrote: > proposition to move it to subpackage. > > question: by what name? what else to include in it? > > i think it's the tool used to make /var/db files that used to be in 'db' > package... AFAIK it's used with nss_db - so maybe separate %package -n nss_db (libnss_db*, makedb)? -- Jakub Bogusz http://qboosh.pl/ From glen at pld-linux.org Tue Oct 11 07:42:46 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 11 Oct 2016 08:42:46 +0300 Subject: glibc <> libselinux dep loop In-Reply-To: <20161011034440.GA15341@mail> References: <57FC0827.6010701@pld-linux.org> <20161011034440.GA15341@mail> Message-ID: <57FC7BD6.7020102@pld-linux.org> On 11.10.2016 06:44, Jakub Bogusz wrote: > On Tue, Oct 11, 2016 at 12:29:11AM +0300, Elan Ruusam?e wrote: >> proposition to move it to subpackage. >> >> question: by what name? what else to include in it? >> >> i think it's the tool used to make /var/db files that used to be in 'db' >> package... > AFAIK it's used with nss_db - so maybe separate %package -n nss_db > (libnss_db*, makedb)? > > ok, WIP on nss_db branch but to ensure safe upgrade must R: it from glibc? R: from basesystem? i personally do not use nss_db, so i'm not scared if it becames lost in system upgrade. imho it was stupid to include optional component in base glibc in first place. -- glen From glen at pld-linux.org Tue Oct 11 07:49:54 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 11 Oct 2016 08:49:54 +0300 Subject: glibc <> libselinux dep loop In-Reply-To: <57FC7BD6.7020102@pld-linux.org> References: <57FC0827.6010701@pld-linux.org> <20161011034440.GA15341@mail> <57FC7BD6.7020102@pld-linux.org> Message-ID: <57FC7D82.2010902@pld-linux.org> On 11.10.2016 08:42, Elan Ruusam?e wrote: > On 11.10.2016 06:44, Jakub Bogusz wrote: >> On Tue, Oct 11, 2016 at 12:29:11AM +0300, Elan Ruusam?e wrote: >>> proposition to move it to subpackage. >>> >>> question: by what name? what else to include in it? >>> >>> i think it's the tool used to make /var/db files that used to be in >>> 'db' >>> package... >> AFAIK it's used with nss_db - so maybe separate %package -n nss_db >> (libnss_db*, makedb)? >> >> > ok, WIP on nss_db branch > > but to ensure safe upgrade must R: it from glibc? R: from basesystem? > > i personally do not use nss_db, so i'm not scared if it becames lost > in system upgrade. imho it was stupid to include optional component in > base glibc in first place. > oh, and we already have nss_db in th. to be dropped? root at distrib ~# rpm -Uhv --test /srv/pld/th/PLD/x86_64/RPMS/nss_db-2.2.3-0.pre1.11.x86_64.rpm Preparing... ########################################### [100%] error: Install/Erase problems: file /lib64/libnss_db.so.2 from install of nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package glibc-2.24-3.x86_64 file /usr/bin/makedb from install of nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package glibc-2.24-3.x86_64 file /var/db/Makefile from install of nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package glibc-2.24-3.x86_64 -- glen From zbyniu at destrukcja.pl Tue Oct 11 08:59:22 2016 From: zbyniu at destrukcja.pl (Zbyniu Krzystolik) Date: Tue, 11 Oct 2016 08:59:22 +0200 Subject: glibc <> libselinux dep loop In-Reply-To: <57FC7D82.2010902@pld-linux.org> References: <57FC0827.6010701@pld-linux.org> <20161011034440.GA15341@mail> <57FC7BD6.7020102@pld-linux.org> <57FC7D82.2010902@pld-linux.org> Message-ID: <20161011065922.GF7036@destrukcja.pl> Elan Ruusam?e wrote: > On 11.10.2016 08:42, Elan Ruusam?e wrote: > > On 11.10.2016 06:44, Jakub Bogusz wrote: > >> On Tue, Oct 11, 2016 at 12:29:11AM +0300, Elan Ruusam?e wrote: > >>> proposition to move it to subpackage. > >>> > >>> question: by what name? what else to include in it? > >>> > >>> i think it's the tool used to make /var/db files that used to be in > >>> 'db' > >>> package... > >> AFAIK it's used with nss_db - so maybe separate %package -n nss_db > >> (libnss_db*, makedb)? > >> > >> > > ok, WIP on nss_db branch > > > > but to ensure safe upgrade must R: it from glibc? R: from basesystem? > > > > i personally do not use nss_db, so i'm not scared if it becames lost > > in system upgrade. imho it was stupid to include optional component in > > base glibc in first place. > > > oh, and we already have nss_db in th. to be dropped? > > root at distrib ~# rpm -Uhv --test > /srv/pld/th/PLD/x86_64/RPMS/nss_db-2.2.3-0.pre1.11.x86_64.rpm > Preparing... ########################################### [100%] > error: Install/Erase problems: > file /lib64/libnss_db.so.2 from install of > nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package > glibc-2.24-3.x86_64 > file /usr/bin/makedb from install of > nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package > glibc-2.24-3.x86_64 > file /var/db/Makefile from install of > nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package > glibc-2.24-3.x86_64 nss_db-2.2.3-0.pre1.11 + nss_updatedb-10-3 (LDAP backend) works for me for many years, while nss_db from glibc segfaults. Zbyniu -- %% Absolutely nothing we trust %% From glen at pld-linux.org Tue Oct 11 15:57:25 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 11 Oct 2016 16:57:25 +0300 Subject: glibc <> libselinux dep loop In-Reply-To: <20161011065922.GF7036@destrukcja.pl> References: <57FC0827.6010701@pld-linux.org> <20161011034440.GA15341@mail> <57FC7BD6.7020102@pld-linux.org> <57FC7D82.2010902@pld-linux.org> <20161011065922.GF7036@destrukcja.pl> Message-ID: <57FCEFC5.6060500@pld-linux.org> On 11.10.2016 09:59, Zbyniu Krzystolik wrote: > nss_db-2.2.3-0.pre1.11 + nss_updatedb-10-3 (LDAP backend) works for me > for many years, while nss_db from glibc segfaults. > > Zbyniu how did you install it? because there's fileconflict, you used --force? -- glen From glen at pld-linux.org Tue Oct 11 18:44:15 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 11 Oct 2016 19:44:15 +0300 Subject: glibc <> libselinux dep loop In-Reply-To: <57FC7D82.2010902@pld-linux.org> References: <57FC0827.6010701@pld-linux.org> <20161011034440.GA15341@mail> <57FC7BD6.7020102@pld-linux.org> <57FC7D82.2010902@pld-linux.org> Message-ID: <57FD16DF.3060108@pld-linux.org> On 11.10.2016 08:49, Elan Ruusam?e wrote: >> ok, WIP on nss_db branch >> >> but to ensure safe upgrade must R: it from glibc? R: from basesystem? >> >> i personally do not use nss_db, so i'm not scared if it becames lost >> in system upgrade. imho it was stupid to include optional component >> in base glibc in first place. >> > oh, and we already have nss_db in th. to be dropped? > > root at distrib ~# rpm -Uhv --test > /srv/pld/th/PLD/x86_64/RPMS/nss_db-2.2.3-0.pre1.11.x86_64.rpm i propose: 1. rename nss_db.spec -> nss_bdb.spec: https://github.com/pld-linux/nss_db/commit/c3050c19465c9a42bc8796dcb22bb3d3380cc785 2. package -n nss_db from glibc.spec 3. add to glibc.spec requires: nss_db = %{version} 4. add glibc.spec: conflicts: nss_db < 1:2.15 so that systems having nss_db 2.2 installed don't get accidentally upgraded to glibc version 5. after X time, remove 3 TBD: RM decision or define some date? -- glen From glen at pld-linux.org Tue Oct 11 18:45:13 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 11 Oct 2016 19:45:13 +0300 Subject: glibc <> libselinux dep loop In-Reply-To: <20161011065922.GF7036@destrukcja.pl> References: <57FC0827.6010701@pld-linux.org> <20161011034440.GA15341@mail> <57FC7BD6.7020102@pld-linux.org> <57FC7D82.2010902@pld-linux.org> <20161011065922.GF7036@destrukcja.pl> Message-ID: <57FD1719.3080509@pld-linux.org> On 11.10.2016 09:59, Zbyniu Krzystolik wrote: > nss_db-2.2.3-0.pre1.11 + nss_updatedb-10-3 (LDAP backend) works for me > for many years, while nss_db from glibc segfaults. does 2.5.0 from master also work for you? also, like to hear how you installed it (the file conflicts i mentioned in earlier replies) -- glen From glen at pld-linux.org Tue Oct 11 23:11:52 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 12 Oct 2016 00:11:52 +0300 Subject: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels In-Reply-To: References: <40db8660ee297f8a33dab7062e03dbd3d400d381_refs_heads_master@pld-linux.org> Message-ID: <57FD5598.1020101@pld-linux.org> On 11.10.2016 23:53, baggins wrote: > commit c856373d926bb13ff6e38acf0bd0fc5c5baef880 > Author: Jan R?korajski > Date: Tue Oct 11 22:53:04 2016 +0200 > > drop building intel drivers and nvidiabl for head kernels i'm using nvidiabl. why stuff gets secretly dropped? please announce if you're going to drop something. # lsmod|grep nvidiabl nvidiabl 53248 0 # uname -r 4.7.2-1 -- glen From baggins at pld-linux.org Tue Oct 11 23:15:27 2016 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Tue, 11 Oct 2016 23:15:27 +0200 Subject: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels In-Reply-To: <57FD5598.1020101@pld-linux.org> References: <40db8660ee297f8a33dab7062e03dbd3d400d381_refs_heads_master@pld-linux.org> <57FD5598.1020101@pld-linux.org> Message-ID: <20161011211527.GA6297@tachikoma> On Wed, 12 Oct 2016, Elan Ruusam?e wrote: > On 11.10.2016 23:53, baggins wrote: > > commit c856373d926bb13ff6e38acf0bd0fc5c5baef880 > > Author: Jan R?korajski > > Date: Tue Oct 11 22:53:04 2016 +0200 > > > > drop building intel drivers and nvidiabl for head kernels > > i'm using nvidiabl. why stuff gets secretly dropped? > > please announce if you're going to drop something. > > # lsmod|grep nvidiabl > nvidiabl 53248 0 > > # uname -r > 4.7.2-1 Fix it then. This driver is unmaintained for years and does not build with kernel 4.8. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Tue Oct 11 23:31:25 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 12 Oct 2016 00:31:25 +0300 Subject: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels In-Reply-To: <20161011211527.GA6297@tachikoma> References: <40db8660ee297f8a33dab7062e03dbd3d400d381_refs_heads_master@pld-linux.org> <57FD5598.1020101@pld-linux.org> <20161011211527.GA6297@tachikoma> Message-ID: <57FD5A2D.9030103@pld-linux.org> On 12.10.2016 00:15, Jan R?korajski wrote: > Fix it then. This driver is unmaintained for years and does not build > with kernel 4.8. that was not the point of the email to tell me "fix it then" the point was that you drop some package, don't even inform you are about to do so, or ask for help updating. with bulld errors, etc details like normal bugreports are created. and now you respond: "why don't i update myself?" because you've being doing it so well i don't even notice problems that i should bother myself with and can keep occupied with other projects. -- glen From baggins at pld-linux.org Tue Oct 11 23:44:51 2016 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Tue, 11 Oct 2016 23:44:51 +0200 Subject: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels In-Reply-To: <57FD5A2D.9030103@pld-linux.org> References: <40db8660ee297f8a33dab7062e03dbd3d400d381_refs_heads_master@pld-linux.org> <57FD5598.1020101@pld-linux.org> <20161011211527.GA6297@tachikoma> <57FD5A2D.9030103@pld-linux.org> Message-ID: <20161011214451.GB6297@tachikoma> On Wed, 12 Oct 2016, Elan Ruusam?e wrote: > On 12.10.2016 00:15, Jan R?korajski wrote: > > Fix it then. This driver is unmaintained for years and does not build > > with kernel 4.8. > that was not the point of the email to tell me "fix it then" > > the point was that you drop some package, don't even inform you are > about to do so, or ask for help updating. with bulld errors, etc details > like normal bugreports are createA I remove packages after I see breakage sitting around in th-test for a long time and no one interested in fixing it. Any dev breaking stuff should be aware of the consequences and take action to minimize breakage. I'm not a nanny or Mr. Fix-it for everything. > and now you respond: "why don't i update myself?" > > because you've being doing it so well i don't even notice problems that > i should bother myself with and can keep occupied with other projects. Sorry, but I'm sick of kernel modules being randomly dropped on ftp and then forgotten by package authors. I end up maintaining antiquated junk I have no way of testing, and until reently, we did ship not working crap there (chnages to kernel compile flags helped finding those). >From now on, if a kernel package does not build for new head kernel and no obvious fix is available, I will drop such package on head. If you want antique module, stick to old kernel. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Wed Oct 12 07:29:16 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 12 Oct 2016 08:29:16 +0300 Subject: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels In-Reply-To: <20161011214451.GB6297@tachikoma> References: <40db8660ee297f8a33dab7062e03dbd3d400d381_refs_heads_master@pld-linux.org> <57FD5598.1020101@pld-linux.org> <20161011211527.GA6297@tachikoma> <57FD5A2D.9030103@pld-linux.org> <20161011214451.GB6297@tachikoma> Message-ID: <57FDCA2C.8020305@pld-linux.org> On 12.10.2016 00:44, Jan R?korajski wrote: > On Wed, 12 Oct 2016, Elan Ruusam?e wrote: > >> >On 12.10.2016 00:15, Jan R?korajski wrote: >>> > >Fix it then. This driver is unmaintained for years and does not build >>> > >with kernel 4.8. >> >that was not the point of the email to tell me "fix it then" >> > >> >the point was that you drop some package, don't even inform you are >> >about to do so, or ask for help updating. with bulld errors, etc details >> >like normal bugreports are createA > I remove packages after I see breakage sitting around in th-test for a > long time and no one interested in fixing it. > > Any dev breaking stuff should be aware of the consequences and take > action to minimize breakage. > > I'm not a nanny or Mr. Fix-it for everything. > how i should know any of that? i do not read your /dev/brain! or monitor your /dev/tty to see what you are doing. and how exactly i broke anything personally here? i was just an user of a kernel module. -- glen From glen at pld-linux.org Wed Oct 12 07:31:21 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 12 Oct 2016 08:31:21 +0300 Subject: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels In-Reply-To: <20161011214451.GB6297@tachikoma> References: <40db8660ee297f8a33dab7062e03dbd3d400d381_refs_heads_master@pld-linux.org> <57FD5598.1020101@pld-linux.org> <20161011211527.GA6297@tachikoma> <57FD5A2D.9030103@pld-linux.org> <20161011214451.GB6297@tachikoma> Message-ID: <57FDCAA9.90904@pld-linux.org> On 12.10.2016 00:44, Jan R?korajski wrote: > From now on, if a kernel package does not build for new head kernel and > no obvious fix is available, I will drop such package on head. > If you want antique module, stick to old kernel. please announce any of such droppings. that's what i asked here! and have asked historycally as well. if you plan to drop something you announce the list of packages and the reason. -- glen From jajcus at jajcus.net Wed Oct 12 08:38:19 2016 From: jajcus at jajcus.net (Jacek Konieczny) Date: Wed, 12 Oct 2016 08:38:19 +0200 Subject: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels In-Reply-To: <57FDCAA9.90904@pld-linux.org> References: <40db8660ee297f8a33dab7062e03dbd3d400d381_refs_heads_master@pld-linux.org> <57FD5598.1020101@pld-linux.org> <20161011211527.GA6297@tachikoma> <57FD5A2D.9030103@pld-linux.org> <20161011214451.GB6297@tachikoma> <57FDCAA9.90904@pld-linux.org> Message-ID: <69896256-38aa-80c5-7737-278649f77ce1@jajcus.net> On 2016-10-12 07:31, Elan Ruusam?e wrote: > please announce any of such droppings. A nice way to say 'announce any of this shit' ;-) Jacek From glen at pld-linux.org Wed Oct 12 09:30:15 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 12 Oct 2016 10:30:15 +0300 Subject: [packages/ardour] force build with MMX and SSE In-Reply-To: <18043c1a1aa393cedbabd2bcdda35ed5db35ebf8_refs_heads_master@pld-linux.org> References: <691623f9df250ddf6768d3a3fb598601196e5ed0_refs_heads_master@pld-linux.org> <18043c1a1aa393cedbabd2bcdda35ed5db35ebf8_refs_heads_master@pld-linux.org> Message-ID: <57FDE687.8000600@pld-linux.org> you can enforce runtime probe dependency: $ grep -r Requires.*cpuinfo ~/all-specs /home/users/glen/all-specs/adobe-flash.spec:Requires: cpuinfo(sse2) /home/users/glen/all-specs/google-earth.spec:Requires: cpuinfo(sse2) /home/users/glen/all-specs/kernel.spec:Requires: cpuinfo(pae) /home/users/glen/all-specs/ClanLib.spec:%{?with_sse2:Requires: cpuinfo(sse2)} sorry if this is totally out of context. On 12.10.2016 09:33, jajcus wrote: > commit 18043c1a1aa393cedbabd2bcdda35ed5db35ebf8 > Author: Jacek Konieczny > Date: Wed Oct 12 08:29:26 2016 +0200 > > force build with MMX and SSE > > It won't build without it on i686. It is not a library, but end-user > application, so it won't break anything else. It seems safe to assume > that no one with older CPU would use it. > > no_proc_build.patch | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > --- > diff --git a/no_proc_build.patch b/no_proc_build.patch > index 9fa7da2..ecdbe9e 100644 > --- a/no_proc_build.patch > +++ b/no_proc_build.patch > @@ -1,11 +1,13 @@ > diff -dur Ardour-5.4.0.orig/wscript Ardour-5.4.0/wscript > --- Ardour-5.4.0.orig/wscript 2016-10-11 21:55:23.000000000 +0200 > +++ Ardour-5.4.0/wscript 2016-10-11 21:56:20.000000000 +0200 > -@@ -439,7 +439,7 @@ > +@@ -439,7 +439,9 @@ > > compiler_flags.append ("-DARCH_X86") > > - if platform == 'linux' : > ++ build_host_supports_sse = True > ++ compiler_flags.append ("-mmmx") > + if False : > -- glen From jajcus at jajcus.net Wed Oct 12 10:39:27 2016 From: jajcus at jajcus.net (Jacek Konieczny) Date: Wed, 12 Oct 2016 10:39:27 +0200 Subject: [packages/ardour] force build with MMX and SSE In-Reply-To: <57FDE687.8000600@pld-linux.org> References: <691623f9df250ddf6768d3a3fb598601196e5ed0_refs_heads_master@pld-linux.org> <18043c1a1aa393cedbabd2bcdda35ed5db35ebf8_refs_heads_master@pld-linux.org> <57FDE687.8000600@pld-linux.org> Message-ID: On 2016-10-12 09:30, Elan Ruusam?e wrote: > you can enforce runtime probe dependency: > > $ grep -r Requires.*cpuinfo ~/all-specs > /home/users/glen/all-specs/adobe-flash.spec:Requires: cpuinfo(sse2) > /home/users/glen/all-specs/google-earth.spec:Requires: cpuinfo(sse2) > /home/users/glen/all-specs/kernel.spec:Requires: cpuinfo(pae) > /home/users/glen/all-specs/ClanLib.spec:%{?with_sse2:Requires: > cpuinfo(sse2)} Good to know. Even better would be to also know what are the CPU extensions supposed to be available on our 'i686'. > sorry if this is totally out of context. No, it is not. It seems Ardour is supposed to detect and enable SSE on runtime, but I am not sure it works and I have no way to test it. MMX suuport seems to be hardcoded. Jacek From arekm at maven.pl Wed Oct 12 12:22:59 2016 From: arekm at maven.pl (Arkadiusz =?iso-8859-2?q?Mi=B6kiewicz?=) Date: Wed, 12 Oct 2016 12:22:59 +0200 Subject: Popsute KDE po aktualizacji kdelibs In-Reply-To: <1491446.g0Xu6ZCT2h@geralt> References: <3138415.oZq71K4YFb@geralt> <1491446.g0Xu6ZCT2h@geralt> Message-ID: <201610121222.59821.arekm@maven.pl> On Wednesday 12 of October 2016, ?ukasz Ma?ko wrote: > Dnia ?roda, 12 pa?dziernika 2016 10:58:05 ?ukasz Ma?ko pisze: > > Po dzisiejszej aktualizacji kde4-kdelibs-4.14.25-1 przesta?o mi wstawa? > > KDE. > > Ju? wiem. Nie wina KDE, a tzdata. Wersja 2016g jest poci?ta i po > aktualizacji nie zosta?y dodane paczki tzdata-zoneinfo*, przez co zabrak?o > pliku ze stref? czasow?. Omg... to jakie? Suggests chocia? by si? tam przyda?o. Why there is no suggests in tzdata for zoneinfo subpackage? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at pld-linux.org Wed Oct 12 20:35:34 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 12 Oct 2016 21:35:34 +0300 Subject: Popsute KDE po aktualizacji kdelibs In-Reply-To: <201610121222.59821.arekm@maven.pl> References: <3138415.oZq71K4YFb@geralt> <1491446.g0Xu6ZCT2h@geralt> <201610121222.59821.arekm@maven.pl> Message-ID: <57FE8276.70704@pld-linux.org> On 12.10.2016 13:22, Arkadiusz Mi?kiewicz wrote: > Why there is no suggests in tzdata for zoneinfo subpackage? should be requires as described in earlier posts. fixed. -- glen From qboosh at pld-linux.org Sun Oct 16 16:45:22 2016 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Sun, 16 Oct 2016 16:45:22 +0200 Subject: [packages/lighttpd] do not override _libdir macro In-Reply-To: References: <4428f15adb34cb4e49f6cb3511c980617ceaade8_refs_heads_master@pld-linux.org> Message-ID: <20161016144522.GA22911@mail> On Sun, Oct 16, 2016 at 04:22:13PM +0200, glen wrote: > commit f4599c5b40795c07193edffbb6cbf9343f789dd8 > Author: Elan Ruusam?e > Date: Sun Oct 16 17:19:19 2016 +0300 > > do not override _libdir macro > > it breaks my ccache setup > > lighttpd.spec | 77 ++++++++++++++++++++++++++++++----------------------------- > 1 file changed, 39 insertions(+), 38 deletions(-) > --- > diff --git a/lighttpd.spec b/lighttpd.spec > index 525a819..51f9aae 100644 > --- a/lighttpd.spec > +++ b/lighttpd.spec > @@ -165,7 +165,7 @@ Conflicts: logrotate < 3.7-4 > Conflicts: rpm < 4.4.2-0.2 > BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) > > -%define _libdir %{_prefix}/%{_lib}/%{name} > +%define _libexecdir %{_libdir}/%{name} I suggest custom macros for such uses (eg. %pkglibdir) or no macro at all (--libdir=%{_libdir}/%{name}, %{_libdir}/%{name}/... in files). Shared modules logically have nothing to do with libexecdir. -- Jakub Bogusz http://qboosh.pl/ From glen at pld-linux.org Tue Oct 18 16:42:05 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 18 Oct 2016 17:42:05 +0300 Subject: [packages/lftp] - rel 2; new mirror -F glob option In-Reply-To: References: Message-ID: <580634BD.8040701@pld-linux.org> On 18.10.2016 16:01, arekm wrote: > commit b6884ac30d41606f6b3720ae2935990893dedca7 > Author: Arkadiusz Mi?kiewicz > Date: Tue Oct 18 15:01:20 2016 +0200 > > - rel 2; new mirror -F glob option > > lftp-git.patch | 1178 +++++--------------------------------------------------- > lftp.spec | 2 +- > 2 files changed, 95 insertions(+), 1085 deletions(-) > --- still crappy commit messages. better one: "enabled git branch patch -- adds mirror -F glob option; rel 2" -- glen From arekm at maven.pl Tue Oct 18 16:46:33 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Tue, 18 Oct 2016 16:46:33 +0200 Subject: [packages/lftp] - rel 2; new mirror -F glob option In-Reply-To: <580634BD.8040701@pld-linux.org> References: <580634BD.8040701@pld-linux.org> Message-ID: <201610181646.33285.arekm@maven.pl> On Tuesday 18 of October 2016, Elan Ruusam?e wrote: > On 18.10.2016 16:01, arekm wrote: > > commit b6884ac30d41606f6b3720ae2935990893dedca7 > > Author: Arkadiusz Mi?kiewicz > > Date: Tue Oct 18 15:01:20 2016 +0200 > > > > - rel 2; new mirror -F glob option > > > > lftp-git.patch | 1178 > > +++++--------------------------------------------------- lftp.spec > > | 2 +- > > 2 files changed, 95 insertions(+), 1085 deletions(-) > > > > --- > > still crappy commit messages. > > better one: > > "enabled git branch patch -- adds mirror -F glob option; rel 2" It's not a branch patch. It's single commit taken out of a branch. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at pld-linux.org Tue Oct 18 23:51:53 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 19 Oct 2016 00:51:53 +0300 Subject: nginx-standard drop Message-ID: <58069979.9060301@pld-linux.org> proposition: drop nginx "-standard" suffix? in package and filenames rationale: why pld should be again unique and packaging nginx differently other reasons: could create docker base image using pld and behaving like official nginx image https://github.com/nginxinc/docker-nginx/blob/8921999083def7ba43a06fabd5f80e4406651353/mainline/jessie/Dockerfile i tried to hack in my base image adding symlinks, but even accesslogs are different /var/log/nginx/nginx-standard_error.log vs /var/log/nginx/access.log -- glen From glen at pld-linux.org Tue Oct 18 23:56:22 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 19 Oct 2016 00:56:22 +0300 Subject: nginx-standard drop In-Reply-To: <58069979.9060301@pld-linux.org> References: <58069979.9060301@pld-linux.org> Message-ID: <58069A86.2010807@pld-linux.org> seems 1.10 (?) supports =dynamic modules so all those "nonstandard" packages can be dropped (replaced with actual mod packages) to be investigated On 19.10.2016 00:51, Elan Ruusam?e wrote: > proposition: > drop nginx "-standard" suffix? in package and filenames > > rationale: > why pld should be again unique and packaging nginx differently > > other reasons: > could create docker base image using pld and behaving like official > nginx image > > https://github.com/nginxinc/docker-nginx/blob/8921999083def7ba43a06fabd5f80e4406651353/mainline/jessie/Dockerfile > > > i tried to hack in my base image adding symlinks, but even accesslogs > are different > > /var/log/nginx/nginx-standard_error.log > vs > /var/log/nginx/access.log > -- glen From jajcus at jajcus.net Wed Oct 19 09:28:09 2016 From: jajcus at jajcus.net (Jacek Konieczny) Date: Wed, 19 Oct 2016 09:28:09 +0200 Subject: nginx-standard drop In-Reply-To: <58069979.9060301@pld-linux.org> References: <58069979.9060301@pld-linux.org> Message-ID: <864a9e88-a5c2-7e72-c778-7db4165b4eb6@jajcus.net> On 2016-10-18 23:51, Elan Ruusam?e wrote: > proposition: > drop nginx "-standard" suffix? in package and filenames +1 And get rid of all other HTTP versions. The "-mail" can stay, I guess. Does anybody actually use anything other than "-standard"? I never changed it, not to break things for somebody who used it. And because I had no idea why anybody would split the package this way. > rationale: > why pld should be again unique and packaging nginx differently PLD does too much of that. > i tried to hack in my base image adding symlinks, but even accesslogs > are different > > /var/log/nginx/nginx-standard_error.log > vs > /var/log/nginx/access.log I would often just make my own nginx.conf file and own systemd unit nginx.service, with all paths restored to normal. Jacek From glen at pld-linux.org Wed Oct 19 11:30:53 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 19 Oct 2016 12:30:53 +0300 Subject: nginx-standard drop In-Reply-To: <864a9e88-a5c2-7e72-c778-7db4165b4eb6@jajcus.net> References: <58069979.9060301@pld-linux.org> <864a9e88-a5c2-7e72-c778-7db4165b4eb6@jajcus.net> Message-ID: <58073D4D.1090604@pld-linux.org> tl;dr; i see all the "flavours" can be dropped and replaced with dynamic modules so i'm dropping all subpackages (on dev-dynamic branch first) On 19.10.2016 10:28, Jacek Konieczny wrote: > On 2016-10-18 23:51, Elan Ruusam?e wrote: >> proposition: >> drop nginx "-standard" suffix? in package and filenames > > +1 > > And get rid of all other HTTP versions. The "-mail" can stay, I guess. mail can be dynamic too, from --help i see these can be built as shared: [~/rpm/packages/BUILD.x86_64-linux/nginx-1.11.3] ? ./configure --help|grep =dynamic --with-http_xslt_module=dynamic enable dynamic ngx_http_xslt_module --with-http_image_filter_module=dynamic --with-http_geoip_module=dynamic enable dynamic ngx_http_geoip_module --with-http_perl_module=dynamic enable dynamic ngx_http_perl_module --with-mail=dynamic enable dynamic POP3/IMAP4/SMTP proxy module --with-stream=dynamic enable dynamic TCP/UDP proxy module --with-stream_geoip_module=dynamic enable dynamic ngx_stream_geoip_module [~/rpm/packages/BUILD.x86_64-linux/nginx-1.11.3] ? but so far i can't understand why it doesn't build dynamic files. probably different build flavours just overwrite something so i'll drop all the flavours and do just single build and then figure out that dynamic thing. > > Does anybody actually use anything other than "-standard"? i don't use nginx, but i plan to. but wasn't it you who added "-light" version? > I never changed it, not to break things for somebody who used it. And > because I had no idea why anybody would split the package this way. there's git log for that :D > > rationale: > > why pld should be again unique and packaging nginx differently > > PLD does too much of that. > > > i tried to hack in my base image adding symlinks, but even accesslogs > > are different > > > > /var/log/nginx/nginx-standard_error.log > > vs > > /var/log/nginx/access.log > > I would often just make my own nginx.conf file and own systemd unit > nginx.service, with all paths restored to normal. > > Jacek -- glen From glen at pld-linux.org Sat Oct 22 15:04:16 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 22 Oct 2016 16:04:16 +0300 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <511b049148a2c8b621d586beb7a14ab8da4a5860_refs_heads_master@pld-linux.org> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <511b049148a2c8b621d586beb7a14ab8da4a5860_refs_heads_master@pld-linux.org> Message-ID: <580B63D0.5040703@pld-linux.org> On 21.10.2016 23:58, arekm wrote: > commit 511b049148a2c8b621d586beb7a14ab8da4a5860 > Author: Arkadiusz Mi?kiewicz > Date: Fri Oct 21 22:58:08 2016 +0200 > > - rel 3; allow building disto package for variants: with and without vserver patches > > iptables.spec | 69 ++++++++++++++++++++++++++++++----------------------------- > 1 file changed, 35 insertions(+), 34 deletions(-) > --- > diff --git a/iptables.spec b/iptables.spec > index 32a152e..99a7e64 100644 > --- a/iptables.spec > +++ b/iptables.spec > @@ -20,9 +20,10 @@ > %define with_ipt_IPV4OPTSSTRIP 1 > %define with_ipt_rpc 1 > %define with_xt_layer7 1 > -%define with_vserver 1 > %endif > > +%define orgname iptables > + > %define name6 ip6tables > Summary: Extensible packet filtering system && extensible NAT system > Summary(pl.UTF-8): System filtrowania pakiet?w oraz system translacji adres?w (NAT) > @@ -30,45 +31,45 @@ Summary(pt_BR.UTF-8): Ferramenta para controlar a filtragem de pacotes no kernel > Summary(ru.UTF-8): ??????? ??? ?????????? ????????? ????????? ???? Linux > Summary(uk.UTF-8): ??????? ??? ????????? ????????? ????????? ???? Linux > Summary(zh_CN.UTF-8): Linux????????? > -Name: iptables > +Name: iptables%{?with_vserver:-vs} > Version: 1.6.0 > -Release: 2%{?with_vserver:.vserver} > +Release: 3 what's the problem? what's the difference? where i should install which type of package? please document that in wiki https://www.pld-linux.org/packages/iptables -- glen From arekm at maven.pl Sat Oct 22 15:17:06 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Sat, 22 Oct 2016 15:17:06 +0200 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <580B63D0.5040703@pld-linux.org> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <511b049148a2c8b621d586beb7a14ab8da4a5860_refs_heads_master@pld-linux.org> <580B63D0.5040703@pld-linux.org> Message-ID: <201610221517.06650.arekm@maven.pl> On Saturday 22 of October 2016, Elan Ruusam?e wrote: > On 21.10.2016 23:58, arekm wrote: > > commit 511b049148a2c8b621d586beb7a14ab8da4a5860 > > Author: Arkadiusz Mi?kiewicz > > Date: Fri Oct 21 22:58:08 2016 +0200 > > > > - rel 3; allow building disto package for variants: with and without > > vserver patches > > > > iptables.spec | 69 > > ++++++++++++++++++++++++++++++----------------------------- 1 file > > changed, 35 insertions(+), 34 deletions(-) > > > > --- > > diff --git a/iptables.spec b/iptables.spec > > index 32a152e..99a7e64 100644 > > --- a/iptables.spec > > +++ b/iptables.spec > > @@ -20,9 +20,10 @@ > > > > %define with_ipt_IPV4OPTSSTRIP 1 > > %define with_ipt_rpc 1 > > %define with_xt_layer7 1 > > > > -%define with_vserver 1 > > > > %endif > > > > +%define orgname iptables > > + > > > > %define name6 ip6tables > > Summary: Extensible packet filtering system && extensible NAT system > > Summary(pl.UTF-8): System filtrowania pakiet?w oraz system translacji > > adres?w (NAT) > > > > @@ -30,45 +31,45 @@ Summary(pt_BR.UTF-8): Ferramenta para controlar a > > filtragem de pacotes no kernel > > > > Summary(ru.UTF-8): ??????? ??? ?????????? ????????? ????????? ???? > > Linux Summary(uk.UTF-8): ??????? ??? ????????? ????????? ????????? > > ???? Linux Summary(zh_CN.UTF-8): Linux????????? > > > > -Name: iptables > > +Name: iptables%{?with_vserver:-vs} > > > > Version: 1.6.0 > > > > -Release: 2%{?with_vserver:.vserver} > > +Release: 3 > > what's the problem? vserver patch changing size of owner-related structure making that functionality incompatible with non-vserver kernels > what's the difference? where i should install which > type of package? > > please document that in wiki https://www.pld-linux.org/packages/iptables -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at pld-linux.org Tue Oct 25 07:07:27 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 25 Oct 2016 08:07:27 +0300 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <201610221517.06650.arekm@maven.pl> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <511b049148a2c8b621d586beb7a14ab8da4a5860_refs_heads_master@pld-linux.org> <580B63D0.5040703@pld-linux.org> <201610221517.06650.arekm@maven.pl> Message-ID: <580EE88F.6070002@pld-linux.org> On 22.10.2016 16:17, Arkadiusz Mi?kiewicz wrote: >>> -Name: iptables >>> > >+Name: iptables%{?with_vserver:-vs} >>> > > >>> > > Version: 1.6.0 >>> > > >>> > >-Release: 2%{?with_vserver:.vserver} >>> > >+Release: 3 >> > >> >what's the problem? > vserver patch changing size of owner-related structure making that > functionality incompatible with non-vserver kernels > >> >what's the difference? where i should install which >> >type of package? >> > >> >please document that in wikihttps://www.pld-linux.org/packages/iptables you haven't given answer when to use one or another version. -- glen From arekm at maven.pl Tue Oct 25 07:34:55 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Tue, 25 Oct 2016 07:34:55 +0200 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <580EE88F.6070002@pld-linux.org> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <201610221517.06650.arekm@maven.pl> <580EE88F.6070002@pld-linux.org> Message-ID: <201610250734.55719.arekm@maven.pl> On Tuesday 25 of October 2016, Elan Ruusam?e wrote: > On 22.10.2016 16:17, Arkadiusz Mi?kiewicz wrote: > >>> -Name: iptables > >>> > >>> > >+Name: iptables%{?with_vserver:-vs} > >>> > > > >>> > > Version: 1.6.0 > >>> > > > >>> > >-Release: 2%{?with_vserver:.vserver} > >>> > >+Release: 3 > >> > > >> >what's the problem? > > > > vserver patch changing size of owner-related structure making that > > functionality incompatible with non-vserver kernels > > > >> >what's the difference? where i should install which > >> >type of package? > >> > > >> >please document that in wikihttps://www.pld-linux.org/packages/iptables > > you haven't given answer when to use one or another version. If you use functionality depending on that structure (owner matching) then vserver version for vserver enabled kernels, non-vserver for non-vserver kernels. If you don't use that funcionality then any version will do. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at pld-linux.org Tue Oct 25 07:40:58 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 25 Oct 2016 08:40:58 +0300 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <201610250734.55719.arekm@maven.pl> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <201610221517.06650.arekm@maven.pl> <580EE88F.6070002@pld-linux.org> <201610250734.55719.arekm@maven.pl> Message-ID: <580EF06A.2020108@pld-linux.org> On 25.10.2016 08:34, Arkadiusz Mi?kiewicz wrote: > > >vserver patch changing size of owner-related structure making that > > >functionality incompatible with non-vserver kernels > > > isn't it better (simplier?) to patch non-vserver kernel with dummy structure (pad it) so that the struct size matches? i mean how many out there are that use non-dist kernel anyway, but it will make simpler to handle dependencies on orchestrated systems. now i have to decide based on kernel version which iptables version to install. is this incompatibility tracked anywhere? bugtracker? mailinglist? is it planned to be solved? -- glen From arekm at maven.pl Tue Oct 25 08:00:48 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Tue, 25 Oct 2016 08:00:48 +0200 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <580EF06A.2020108@pld-linux.org> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <201610250734.55719.arekm@maven.pl> <580EF06A.2020108@pld-linux.org> Message-ID: <201610250800.48453.arekm@maven.pl> On Tuesday 25 of October 2016, Elan Ruusam?e wrote: > On 25.10.2016 08:34, Arkadiusz Mi?kiewicz wrote: > > > >vserver patch changing size of owner-related structure making that > > > >functionality incompatible with non-vserver kernels > > isn't it better (simplier?) to patch non-vserver kernel with dummy > structure (pad it) so that the struct size matches? i mean how many out > there are that use non-dist kernel anyway, but it will make simpler to > handle dependencies on orchestrated systems. now i have to decide based > on kernel version which iptables version to install. Best would be some runtime detection on iptables side but not sure if that's even possible. For our usage padding seems to be a smart solution (indeed breaking vanilla kernels though). > is this incompatibility tracked anywhere? bugtracker? mailinglist? is it > planned to be solved? AFAIK answer is "no" for all these questions. From arekm at maven.pl Tue Oct 25 08:02:08 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Tue, 25 Oct 2016 08:02:08 +0200 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <201610250800.48453.arekm@maven.pl> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <580EF06A.2020108@pld-linux.org> <201610250800.48453.arekm@maven.pl> Message-ID: <201610250802.08229.arekm@maven.pl> On Tuesday 25 of October 2016, Arkadiusz Mi?kiewicz wrote: > For our usage padding seems to be a smart solution (indeed breaking vanilla > kernels though). And breaking all our existing non vserver kernels, too obviously. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at pld-linux.org Tue Oct 25 08:27:58 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 25 Oct 2016 09:27:58 +0300 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <201610250802.08229.arekm@maven.pl> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <580EF06A.2020108@pld-linux.org> <201610250800.48453.arekm@maven.pl> <201610250802.08229.arekm@maven.pl> Message-ID: <580EFB6E.6000505@pld-linux.org> On 25.10.2016 09:02, Arkadiusz Mi?kiewicz wrote: > On Tuesday 25 of October 2016, Arkadiusz Mi?kiewicz wrote: > >> For our usage padding seems to be a smart solution (indeed breaking vanilla >> kernels though). > And breaking all our existing non vserver kernels, too obviously. > how that "breakage" represents itself? iptables -I failure? kernel memory trashing? kernel crash? and probably only you use that combination anyway (vserver+iptables+owner) otherwise there'd be more talk about that incompat in pld lists. -- glen From arekm at maven.pl Tue Oct 25 08:40:07 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Tue, 25 Oct 2016 08:40:07 +0200 Subject: [packages/iptables] - rel 3; allow building disto package for variants: with and without vserver patches In-Reply-To: <580EFB6E.6000505@pld-linux.org> References: <8417cd8c34c715387f1d25c446cb286452d2c719_refs_heads_master@pld-linux.org> <201610250802.08229.arekm@maven.pl> <580EFB6E.6000505@pld-linux.org> Message-ID: <201610250840.07574.arekm@maven.pl> On Tuesday 25 of October 2016, Elan Ruusam?e wrote: > On 25.10.2016 09:02, Arkadiusz Mi?kiewicz wrote: > > On Tuesday 25 of October 2016, Arkadiusz Mi?kiewicz wrote: > >> For our usage padding seems to be a smart solution (indeed breaking > >> vanilla kernels though). > > > > And breaking all our existing non vserver kernels, too obviously. > > how that "breakage" represents itself? iptables -I failure? kernel > memory trashing? kernel crash? iptables command exits with failure when trying to add the rule > and probably only you use that combination anyway > (vserver+iptables+owner) otherwise there'd be more talk about that > incompat in pld lists. Then for these people it doesn't matter which iptables varient they use. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at pld-linux.org Tue Oct 25 12:44:52 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 25 Oct 2016 13:44:52 +0300 Subject: dirtycow Message-ID: <580F37A4.7030604@pld-linux.org> what's the status of pld-th kernels? which versions are patched? which versions are upstream fixed? Dirty COW (CVE-2016-5195) is a privilege escalation vulnerability in the Linux Kernel https://dirtycow.ninja/ - 4.4 branch https://github.com/pld-linux/kernel/tree/LINUX_4_4 - 4.4.27 - updated 3 days ago - likely patched? - 3.18 branch https://github.com/pld-linux/kernel/tree/LINUX_3_18 - 3.18.43 - updated 11 days ago - not patched? what versions are supported anyway? i tried to update wiki page based on news from frontpage https://www.pld-linux.org/packages/kernel seems 4.4 lacks vserver support? -- glen From arekm at maven.pl Tue Oct 25 12:55:42 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Tue, 25 Oct 2016 12:55:42 +0200 Subject: dirtycow In-Reply-To: <580F37A4.7030604@pld-linux.org> References: <580F37A4.7030604@pld-linux.org> Message-ID: <201610251255.42422.arekm@maven.pl> On Tuesday 25 of October 2016, Elan Ruusam?e wrote: > what's the status of pld-th kernels? which versions are patched? which > versions are upstream fixed? > > Dirty COW (CVE-2016-5195) is a privilege escalation vulnerability in the > Linux Kernel > > https://dirtycow.ninja/ > > - 4.4 branch https://github.com/pld-linux/kernel/tree/LINUX_4_4 - 4.4.27 > - updated 3 days ago - likely patched? fixed versions are >= 4.4.26 ; see commit log > - 3.18 branch https://github.com/pld-linux/kernel/tree/LINUX_3_18 - > 3.18.43 - updated 11 days ago - not patched? 3.18.44+ has fix 4.8.3+ has fix 4.7 is EOL at upstream > https://www.pld-linux.org/packages/kernel > > seems 4.4 lacks vserver support? Yes, 4.1 series is latest one for vserver (>= 4.1.34-2 has dirtycow fix) -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at pld-linux.org Wed Oct 26 23:14:59 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Thu, 27 Oct 2016 00:14:59 +0300 Subject: nginx-standard drop In-Reply-To: <58069979.9060301@pld-linux.org> References: <58069979.9060301@pld-linux.org> Message-ID: <58111CD3.2020903@pld-linux.org> On 19.10.2016 00:51, Elan Ruusam?e wrote: > proposition: > drop nginx "-standard" suffix? in package and filenames so, zero feedback on my dev changes. i'm going to merge this to master in few days then. -- glen From jajcus at jajcus.net Thu Oct 27 16:17:46 2016 From: jajcus at jajcus.net (Jacek Konieczny) Date: Thu, 27 Oct 2016 16:17:46 +0200 Subject: nginx-standard drop In-Reply-To: <58111CD3.2020903@pld-linux.org> References: <58069979.9060301@pld-linux.org> <58111CD3.2020903@pld-linux.org> Message-ID: <9c3ab91d-0a7f-2a45-47f9-5cfa856a210c@jajcus.net> On 2016-10-26 23:14, Elan Ruusam?e wrote: > On 19.10.2016 00:51, Elan Ruusam?e wrote: >> proposition: >> drop nginx "-standard" suffix? in package and filenames > > so, zero feedback on my dev changes. i'm going to merge this to master > in few days then. I had not time to look into that, but if you push a package (before or after the merge, doesn't matter to me) into th-test I'll try to test it somewhere. The general idea seems right. I am a bit afraid of the transition, though. Jacek From zawadaa at gmail.com Thu Oct 27 23:50:30 2016 From: zawadaa at gmail.com (Andrzej Zawadzki) Date: Thu, 27 Oct 2016 23:50:30 +0200 Subject: cgroup_disable=memory Message-ID: <5f67b2b1-e229-08f4-85bb-5e553e093a59@gmail.com> Hi, what do you think about adding this option to /etc/sysconfig/grub by default? GRUB_CMDLINE_LINUX="cgroup_disable=memory" According to: [1]https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Lin ux/6/html/Resource_Management_Guide/sec-memory.html this can safe a lot of memory in most systems (98%? or even more) -- Andrzej References 1. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/sec-memory.html From zawadaa at gmail.com Thu Oct 27 23:52:23 2016 From: zawadaa at gmail.com (Andrzej Zawadzki) Date: Thu, 27 Oct 2016 23:52:23 +0200 Subject: Kernel upgrade - What is that? Message-ID: <05224ca5-ec77-bd47-2f67-755ae6659023@gmail.com> Kernel upgrade: /usr/lib/dracut/modules.d/90kernel-modules/module-setup.sh: line 15: warning: command substitution: ignored null byte in input x infinity ;-) -- Andrzej From groups at sq9mev.info Fri Oct 28 04:55:47 2016 From: groups at sq9mev.info (Bartek Radwan) Date: Fri, 28 Oct 2016 04:55:47 +0200 Subject: Kernel upgrade - What is that? In-Reply-To: <05224ca5-ec77-bd47-2f67-755ae6659023@gmail.com> References: <05224ca5-ec77-bd47-2f67-755ae6659023@gmail.com> Message-ID: <5812BE33.4090508@sq9mev.info> On 27.10.2016 23:52, Andrzej Zawadzki wrote: > Kernel upgrade: > > /usr/lib/dracut/modules.d/90kernel-modules/module-setup.sh: line 15: > warning: command substitution: ignored null byte in input > x infinity;-) > -- It's caused probably by bash-4.4: https://github.com/dracutdevs/dracut/issues/118 Does not last forever for me, initramfs has been generated with this warnings, hovewer it took much more time than usually. -- Regards, Bartek From glen at pld-linux.org Fri Oct 28 09:46:46 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 28 Oct 2016 10:46:46 +0300 Subject: nginx-standard drop In-Reply-To: <9c3ab91d-0a7f-2a45-47f9-5cfa856a210c@jajcus.net> References: <58069979.9060301@pld-linux.org> <58111CD3.2020903@pld-linux.org> <9c3ab91d-0a7f-2a45-47f9-5cfa856a210c@jajcus.net> Message-ID: <58130266.5070406@pld-linux.org> On 27.10.2016 17:17, Jacek Konieczny wrote: > On 2016-10-26 23:14, Elan Ruusam?e wrote: >> On 19.10.2016 00:51, Elan Ruusam?e wrote: >>> proposition: >>> drop nginx "-standard" suffix? in package and filenames >> >> so, zero feedback on my dev changes. i'm going to merge this to master >> in few days then. > > I had not time to look into that, but if you push a package (before or > after the merge, doesn't matter to me) into th-test I'll try to test > it somewhere. > > The general idea seems right. I am a bit afraid of the transition, > though. there's no transition (by design), you need to setup again using new package names. it will not upgrade automatically due broken (deliberately) package deps you can apply this patch to be just poldek -u nginx, but note the configs are not migrated [glen at carme-pld nginx]$ cat obsoletes.patch diff --git a/nginx.spec b/nginx.spec index daa05f8..d97b566 100644 --- a/nginx.spec +++ b/nginx.spec @@ -117,6 +117,8 @@ Requires(pre): /usr/sbin/useradd Requires: rc-scripts >= 0.2.0 Requires: systemd-units >= 38 Suggests: vim-syntax-nginx +Obsoletes: nginx-common +Obsoletes: nginx-standard Conflicts: rpm < 4.4.2-0.2 BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) [glen at carme-pld nginx]$ i do not plan to add upgrade path. because then i would be blamed i did it incomplete & wrong, etc. if somebody else does i do not mind. -- glen From jajcus at jajcus.net Fri Oct 28 10:09:18 2016 From: jajcus at jajcus.net (Jacek Konieczny) Date: Fri, 28 Oct 2016 10:09:18 +0200 Subject: nginx-standard drop In-Reply-To: <58130266.5070406@pld-linux.org> References: <58069979.9060301@pld-linux.org> <58111CD3.2020903@pld-linux.org> <9c3ab91d-0a7f-2a45-47f9-5cfa856a210c@jajcus.net> <58130266.5070406@pld-linux.org> Message-ID: On 2016-10-28 09:46, Elan Ruusam?e wrote: > On 27.10.2016 17:17, Jacek Konieczny wrote: >> On 2016-10-26 23:14, Elan Ruusam?e wrote: >>> On 19.10.2016 00:51, Elan Ruusam?e wrote: >>>> proposition: >>>> drop nginx "-standard" suffix? in package and filenames >>> >>> so, zero feedback on my dev changes. i'm going to merge this to master >>> in few days then. >> >> I had not time to look into that, but if you push a package (before or >> after the merge, doesn't matter to me) into th-test I'll try to test >> it somewhere. >> >> The general idea seems right. I am a bit afraid of the transition, >> though. > > there's no transition (by design), > you need to setup again using new package names. it will not upgrade > automatically due broken (deliberately) package deps That is ok with me. > you can apply this patch to be just poldek -u nginx, but note the > configs are not migrated I prefer the deliberately-broken deps approach. > i do not plan to add upgrade path. because then i would be blamed i did > it incomplete & wrong, etc. makes sense :) Jacek From glen at pld-linux.org Sat Oct 29 10:25:31 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 29 Oct 2016 11:25:31 +0300 Subject: mysql/percona/maria... Message-ID: <58145CFB.9050405@pld-linux.org> hi how is it planned to handle that mysql.spec is now different product (mysql vs percona) and all those mariadb and percona-server packages. mysql 5.6 -> 5.7 MAY NOT be upgraded automatically. if someone used features from percona-server 5.6 that are now not present in mysql-community version in mysql.spec 5.7 their systems would be BROKEN. some idea: rename mysql.spec to mysql-community.spec ? should we introduce mysql57, mysql80 packages instead? ps: fedora has their mysql named as community-mysql.spec -- glen From glen at pld-linux.org Sat Oct 29 10:30:46 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 29 Oct 2016 11:30:46 +0300 Subject: mysql/percona/maria... In-Reply-To: <58145CFB.9050405@pld-linux.org> References: <58145CFB.9050405@pld-linux.org> Message-ID: <58145E36.5010700@pld-linux.org> On 29.10.2016 11:25, Elan Ruusam?e wrote: > hi > > how is it planned to handle that mysql.spec is now different product > (mysql vs percona) > and all those mariadb and percona-server packages. > > mysql 5.6 -> 5.7 MAY NOT be upgraded automatically. if someone used > features from percona-server 5.6 that are now not present in > mysql-community version in mysql.spec 5.7 their systems would be BROKEN. > > some idea: rename mysql.spec to mysql-community.spec ? > > should we introduce mysql57, mysql80 packages instead? > > ps: fedora has their mysql named as community-mysql.spec > here's some idea: 1. make percona-server.spec:5.7 clean upgrade path from mysql.spec:5.6 2. do not build mysql.spec officially at all 3. build system tools using percona-server-devel via "Provides: mysql-devel" 4. mariadb - ship it only if it does not conflict with mysql-libs or mysql-devel -- glen From arekm at maven.pl Sat Oct 29 11:17:22 2016 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Sat, 29 Oct 2016 11:17:22 +0200 Subject: mysql/percona/maria... In-Reply-To: <58145E36.5010700@pld-linux.org> References: <58145CFB.9050405@pld-linux.org> <58145E36.5010700@pld-linux.org> Message-ID: <201610291117.22848.arekm@maven.pl> On Saturday 29 of October 2016, Elan Ruusam?e wrote: > On 29.10.2016 11:25, Elan Ruusam?e wrote: > > hi > > > > how is it planned to handle that mysql.spec is now different product > > (mysql vs percona) > > and all those mariadb and percona-server packages. > > > > mysql 5.6 -> 5.7 MAY NOT be upgraded automatically. Here oracle 5.7 started fine with percona 5.6 db files but you are probably right and in some cases it won't work. > > if someone used > > features from percona-server 5.6 that are now not present in > > mysql-community version in mysql.spec 5.7 their systems would be BROKEN. > > > > some idea: rename mysql.spec to mysql-community.spec ? > > > > should we introduce mysql57, mysql80 packages instead? Only if there are incompatible on upgrade path. To be verified with docs. Otherwise all versions as mysql package. > > > > ps: fedora has their mysql named as community-mysql.spec > > here's some idea: > > 1. make percona-server.spec:5.7 clean upgrade path from mysql.spec:5.6 > 2. do not build mysql.spec officially at all > 3. build system tools using percona-server-devel via "Provides: > mysql-devel" 4. mariadb - ship it only if it does not conflict with > mysql-libs or mysql-devel Sounds good to me. (I would switch entire distribution to mariadb though (but keep percona server package, too) -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From jajcus at jajcus.net Sat Oct 29 11:46:26 2016 From: jajcus at jajcus.net (Jacek Konieczny) Date: Sat, 29 Oct 2016 11:46:26 +0200 Subject: mysql/percona/maria... In-Reply-To: <201610291117.22848.arekm@maven.pl> References: <58145CFB.9050405@pld-linux.org> <58145E36.5010700@pld-linux.org> <201610291117.22848.arekm@maven.pl> Message-ID: <58146FF2.1090402@jajcus.net> On 2016-10-29 11:17, Arkadiusz Mi?kiewicz wrote: > On Saturday 29 of October 2016, Elan Ruusam?e wrote: >> On 29.10.2016 11:25, Elan Ruusam?e wrote: >>> should we introduce mysql57, mysql80 packages instead? > > Only if there are incompatible on upgrade path. To be verified with docs. > Otherwise all versions as mysql package. That (nameXY) would be more usefull for PostgreSQL, where old and new version need to be installed for a database upgrade between different major versions. Currently PostgreSQL upgrade in PLD is a problem. Though, I am not sure doing it right and maintaining later is worth the effort for our tiny team. >> here's some idea: >> >> 1. make percona-server.spec:5.7 clean upgrade path from mysql.spec:5.6 >> 2. do not build mysql.spec officially at all >> 3. build system tools using percona-server-devel via "Provides: >> mysql-devel" 4. mariadb - ship it only if it does not conflict with >> mysql-libs or mysql-devel > > Sounds good to me. > > (I would switch entire distribution to mariadb though (but keep percona server > package, too) Sound goot to me to. It seems other distributions do similarily ? mariadb is used instead of Oracle mysql and no non-Oracle mysql fork is packaged as 'mysql'. Jacek From glen at pld-linux.org Sat Oct 29 13:45:20 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 29 Oct 2016 14:45:20 +0300 Subject: mysql/percona/maria... In-Reply-To: <201610291117.22848.arekm@maven.pl> References: <58145CFB.9050405@pld-linux.org> <58145E36.5010700@pld-linux.org> <201610291117.22848.arekm@maven.pl> Message-ID: <58148BD0.6050505@pld-linux.org> On 29.10.2016 12:17, Arkadiusz Mi?kiewicz wrote: >>> mysql 5.6 -> 5.7 MAY NOT be upgraded automatically. > Here oracle 5.7 started fine with percona 5.6 db files but you are probably > right and in some cases it won't work. > percona used to apply some performance patches which changed precision of some variables. millisecs vs seconds, resuilting all queries being logged to slow.log causing disk to fill up quickly. that's just one incompatibility, some maybe even use performance_schema which maybe is different for those two vendors. so as long there's no automatic switch of upgrading same package replacing with different vendor binary i'm fine. altho i'd prefer to stay to percona version because we've been using it for so long. don't know what's the difference between maria/percona/oracle versions though. probably should search for some comparison table. -- glen From glen at pld-linux.org Sat Oct 29 17:28:13 2016 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 29 Oct 2016 18:28:13 +0300 Subject: utmp group to setup Message-ID: <5814C00D.1040001@pld-linux.org> todo: move utmp group to setup package, we already have "http" and "stats" users there it makes pam required base dependency, but i do not need pam in docker: bash-4.4# poldek -e pam mark pam-1.3.0-2.x86_64 Processing dependencies... pam-1.3.0-2.x86_64 marks pwdutils-3.2.19-4.x86_64 (req pam >= 0.99.7.1) pwdutils-3.2.19-4.x86_64 marks libutempter-1.1.6-5.x86_64 (req /usr/sbin/groupadd) libutempter-1.1.6-5.x86_64 marks rc-scripts-0.4.16-1.x86_64 (req libutempter >= 1.1.6-2) pwdutils-3.2.19-4.x86_64 marks SysVinit-2.88-18.x86_64 (req /usr/sbin/groupadd) pam-1.3.0-2.x86_64 marks util-linux-2.28-2.x86_64 (req pam >= 1:1.1.8-5) There are 6 packages to remove (5 marked by dependencies): R pam-1.3.0-2.x86_64 D SysVinit-2.88-18.x86_64 libutempter-1.1.6-5.x86_64 pwdutils-3.2.19-4.x86_64 rc-scripts-0.4.16-1.x86_64 util-linux-2.28-2.x86_64 This operation will free 14.8MB of disk space. Proceed? [N/y] n bash-4.4# -- glen From gotar at polanet.pl Sat Oct 29 19:17:38 2016 From: gotar at polanet.pl (Tomasz Pala) Date: Sat, 29 Oct 2016 19:17:38 +0200 Subject: mysql/percona/maria... In-Reply-To: <58146FF2.1090402@jajcus.net> References: <58145CFB.9050405@pld-linux.org> <58145E36.5010700@pld-linux.org> <201610291117.22848.arekm@maven.pl> <58146FF2.1090402@jajcus.net> Message-ID: <20161029171738.GA1932@polanet.pl> On Sat, Oct 29, 2016 at 11:46:26 +0200, Jacek Konieczny wrote: > That (nameXY) would be more usefull for PostgreSQL, where old and new > version need to be installed for a database upgrade between different > major versions. Hm? Actually never did that for years... "pg_upgrade supports upgrades from 8.4.X and later to the current major release of PostgreSQL, including snapshot and alpha releases." What does require old version, and not just the previous one, but EVERY one in-between, is ownCloud: "Make sure that you dont skip a major release when upgrading via repositories. For example you cant upgrade from 8.1.x to 9.0.x directly as you would skip the 8.2.x major release" -- Tomasz Pala