From arekm at maven.pl Sat Nov 1 20:16:59 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Sat, 1 Nov 2014 20:16:59 +0100 Subject: kde konsole underline behaviour In-Reply-To: <3750853.8FWWRTyRhE@laptok> References: <201410162009.53382.arekm@maven.pl> <201410162104.05987.arekm@maven.pl> <3750853.8FWWRTyRhE@laptok> Message-ID: <201411012016.59451.arekm@maven.pl> On Thursday 16 of October 2014, ?ukasz Ma?ko wrote: > > Do you youse konsole color scheme with black background? If not try one > > (white on black for example) > > Nope, still works correctly. I assume your setup is up to date th (including th-test etc) ? Still wasn't able to track that down... I can reproduce it with konsole + irssi, too, see videos in bug report: https://bugs.kde.org/show_bug.cgi?id=340031 -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From ed at yen.ipipan.waw.pl Sat Nov 1 21:43:52 2014 From: ed at yen.ipipan.waw.pl (=?utf-8?B?xYF1a2FzeiBNYcWba28=?=) Date: Sat, 01 Nov 2014 21:43:52 +0100 Subject: kde konsole underline behaviour In-Reply-To: <201411012016.59451.arekm@maven.pl> References: <201410162009.53382.arekm@maven.pl> <3750853.8FWWRTyRhE@laptok> <201411012016.59451.arekm@maven.pl> Message-ID: <7818632.NjVgpc3pcV@laptok> Dnia sobota, 1 listopada 2014 20:16:59 Arkadiusz Mi?kiewicz pisze: > On Thursday 16 of October 2014, ?ukasz Ma?ko wrote: > > > Do you youse konsole color scheme with black background? If not try one > > > (white on black for example) > > > > Nope, still works correctly. > > I assume your setup is up to date th (including th-test etc) ? Yes. The latest possible we have. And I cannot reproduce it. -- ?ukasz Ma?ko _o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafryka?skie s?owo oznaczaj?ce "Nie umiem zainstalowa? Debiana" From glen at delfi.ee Mon Nov 3 21:53:24 2014 From: glen at delfi.ee (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Mon, 03 Nov 2014 22:53:24 +0200 Subject: rpm 5.4.15 creates invalid rpms Message-ID: <5457EB44.4000207@delfi.ee> seems rpm 4.5.15 creates rpms that rpm 4.5 is unable to install. this sounds soo familiar already. something like payload not padded, containing random memory etc... Executing rpm --upgrade -vh --root / --define _check_dirname_deps 1... error: jenkins-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 error: jenkins-1.580.1-1.noarch.rpm cannot be installed error: jenkins-plugin-maven-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 error: jenkins-plugin-maven-1.580.1-1.noarch.rpm cannot be installed those rpms ARE NOT signed. raw what rpmbuild wrote. rpm used in build machine: $ rpmbuild --version rpmbuild (RPM) 5.4.15 $ rpm -q rpm-build rpm-build-5.4.15-1.i686 rpm used in target machine: # rpm --version RPM version 4.5 # rpm -q rpm rpm-4.5-70.i686 i've placed the offending rpm's here: http://carme.pld-linux.org/~glen/rpm5/ (filenames you already know in case mod_dirlisting is not working) -- glen From n3npq at me.com Mon Nov 3 21:59:09 2014 From: n3npq at me.com (Jeffrey Johnson) Date: Mon, 03 Nov 2014 15:59:09 -0500 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <5457EB44.4000207@delfi.ee> References: <5457EB44.4000207@delfi.ee> Message-ID: <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> On Nov 3, 2014, at 3:53 PM, Elan Ruusam?e wrote: > seems rpm 4.5.15 creates rpms that rpm 4.5 is unable to install. > Why are you still using rpm-4.5? Presumably yopu mean 5.4.15. > this sounds soo familiar already. something like payload not padded, containing random memory etc... > > Executing rpm --upgrade -vh --root / --define _check_dirname_deps 1... > error: jenkins-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 > error: jenkins-1.580.1-1.noarch.rpm cannot be installed > error: jenkins-plugin-maven-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 > error: jenkins-plugin-maven-1.580.1-1.noarch.rpm cannot be installed > > those rpms ARE NOT signed. raw what rpmbuild wrote. > > rpm used in build machine: > $ rpmbuild --version > rpmbuild (RPM) 5.4.15 > > $ rpm -q rpm-build > rpm-build-5.4.15-1.i686 > > > rpm used in target machine: > # rpm --version > RPM version 4.5 > > # rpm -q rpm > rpm-4.5-70.i686 > > i've placed the offending rpm's here: > http://carme.pld-linux.org/~glen/rpm5/ > (filenames you already know in case mod_dirlisting is not working) > The RSA v4 keyid is not correctly implementedin rpm-4.5. Use DSA or go fix rpm-4.5. All packages produced by rpmbuild-5.4.15 are signed automatically. Been that way for several years. 73 de Jeff > -- > glen > > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en From glen at delfi.ee Mon Nov 3 23:12:57 2014 From: glen at delfi.ee (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Tue, 04 Nov 2014 00:12:57 +0200 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> Message-ID: <5457FDE9.1060500@delfi.ee> On 03.11.2014 22:59, Jeffrey Johnson wrote: > On Nov 3, 2014, at 3:53 PM, Elan Ruusam?e wrote: > >> seems rpm 4.5.15 creates rpms that rpm 4.5 is unable to install. >> > Why are you still using rpm-4.5? Presumably yopu mean 5.4.15. no. i mean 4.5 there are several reasons: i use 4.5 because in 5.4 this does not work: $ rpm -q $JOB_NAME-*-*.build$BUILD_NUMBER i.e: $ rpm -q ftask-*-*.build36 ftask-1.0-4.0.svn56721.build36.noarch and i need it for automatics. secondly, /var/lib/rpm size is ENOURMOUS comparing to what rpm 4.5 had: 4.5: # du -s /var/lib/rpm 33M /var/lib/rpm 5.4.x: # du -s /var/lib/rpm 347M /var/lib/rpm (not same packages installed, but you'll get the idea) >> this sounds soo familiar already. something like payload not padded, containing random memory etc... >> >> Executing rpm --upgrade -vh --root / --define _check_dirname_deps 1... >> error: jenkins-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 >> error: jenkins-1.580.1-1.noarch.rpm cannot be installed >> error: jenkins-plugin-maven-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 >> error: jenkins-plugin-maven-1.580.1-1.noarch.rpm cannot be installed >> >> those rpms ARE NOT signed. raw what rpmbuild wrote. >> >> rpm used in build machine: >> $ rpmbuild --version >> rpmbuild (RPM) 5.4.15 >> >> $ rpm -q rpm-build >> rpm-build-5.4.15-1.i686 >> >> >> rpm used in target machine: >> # rpm --version >> RPM version 4.5 >> >> # rpm -q rpm >> rpm-4.5-70.i686 >> >> i've placed the offending rpm's here: >> http://carme.pld-linux.org/~glen/rpm5/ >> (filenames you already know in case mod_dirlisting is not working) >> > The RSA v4 keyid is not correctly implementedin rpm-4.5. Use DSA or go fix rpm-4.5. baggins: we probably should revert it then. > All packages produced by rpmbuild-5.4.15 are signed automatically. Been that way > for several years. yep. that's what i recalled problem being familiar. > 73 de Jeff -- glen From n3npq at me.com Tue Nov 4 00:19:10 2014 From: n3npq at me.com (Jeffrey Johnson) Date: Mon, 03 Nov 2014 18:19:10 -0500 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <5457FDE9.1060500@delfi.ee> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> Message-ID: Sent from my iPhone > On Nov 3, 2014, at 5:12 PM, Elan Ruusam?e wrote: > >> On 03.11.2014 22:59, Jeffrey Johnson wrote: >>> On Nov 3, 2014, at 3:53 PM, Elan Ruusam?e wrote: >>> >>> seems rpm 4.5.15 creates rpms that rpm 4.5 is unable to install. >> Why are you still using rpm-4.5? Presumably yopu mean 5.4.15. > no. i mean 4.5 > > there are several reasons: > > i use 4.5 because in 5.4 this does not work: > > $ rpm -q $JOB_NAME-*-*.build$BUILD_NUMBER > i.e: > $ rpm -q ftask-*-*.build36 > ftask-1.0-4.0.svn56721.build36.noarch > Sure it works. Rewrite as a *RE not a glob and prefix with ^ to trigger a pattern lookup (from memory on iPhone, will send worked example if you can't figure out from GOOG) 10x faster (at least) as well. > and i need it for automatics. > > secondly, /var/lib/rpm size is ENOURMOUS comparing to what rpm 4.5 had: > > 4.5: > # du -s /var/lib/rpm > 33M /var/lib/rpm > > 5.4.x: > # du -s /var/lib/rpm > 347M /var/lib/rpm > You need to be more specific. Yes rpm-5.4.15 is transactionally protected and largely eliminatesautomates the need to do rpm --rebuilddb > (not same packages installed, but you'll get the idea) Whatever: there just haven't been serious changes to an rpmdb schematic all century >>> this sounds soo familiar already. something like payload not padded, containing random memory etc... >>> >>> Executing rpm --upgrade -vh --root / --define _check_dirname_deps 1... >>> error: jenkins-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 >>> error: jenkins-1.580.1-1.noarch.rpm cannot be installed >>> error: jenkins-plugin-maven-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 >>> error: jenkins-plugin-maven-1.580.1-1.noarch.rpm cannot be installed >>> >>> those rpms ARE NOT signed. raw what rpmbuild wrote. >>> >>> rpm used in build machine: >>> $ rpmbuild --version >>> rpmbuild (RPM) 5.4.15 >>> >>> $ rpm -q rpm-build >>> rpm-build-5.4.15-1.i686 >>> >>> >>> rpm used in target machine: >>> # rpm --version >>> RPM version 4.5 >>> >>> # rpm -q rpm >>> rpm-4.5-70.i686 >>> >>> i've placed the offending rpm's here: >>> http://carme.pld-linux.org/~glen/rpm5/ >>> (filenames you already know in case mod_dirlisting is not working) >> The RSA v4 keyid is not correctly implementedin rpm-4.5. Use DSA or go fix rpm-4.5. > baggins: we probably should revert it then. > > >> All packages produced by rpmbuild-5.4.15 are signed automatically. Been that way >> for several years. > yep. that's what i recalled problem being familiar. >> 73 de Jeff > > > -- > glen > > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en From baggins at pld-linux.org Tue Nov 4 08:31:57 2014 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Tue, 4 Nov 2014 08:31:57 +0100 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <5457FDE9.1060500@delfi.ee> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> Message-ID: <20141104073157.GA2082@home.lan> On Tue, 04 Nov 2014, Elan Ruusam?e wrote: > On 03.11.2014 22:59, Jeffrey Johnson wrote: > > On Nov 3, 2014, at 3:53 PM, Elan Ruusam?e wrote: > > > >> Executing rpm --upgrade -vh --root / --define _check_dirname_deps 1... > >> error: jenkins-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 > >> error: jenkins-1.580.1-1.noarch.rpm cannot be installed > >> error: jenkins-plugin-maven-1.580.1-1.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 403fdcd0 > >> error: jenkins-plugin-maven-1.580.1-1.noarch.rpm cannot be installed > >> > >> those rpms ARE NOT signed. raw what rpmbuild wrote. > >> > >> rpm used in build machine: > >> $ rpmbuild --version > >> rpmbuild (RPM) 5.4.15 > >> > >> $ rpm -q rpm-build > >> rpm-build-5.4.15-1.i686 > >> > >> > >> rpm used in target machine: > >> # rpm --version > >> RPM version 4.5 > >> > >> # rpm -q rpm > >> rpm-4.5-70.i686 > >> > >> i've placed the offending rpm's here: > >> http://carme.pld-linux.org/~glen/rpm5/ > >> (filenames you already know in case mod_dirlisting is not working) > >> > > The RSA v4 keyid is not correctly implementedin rpm-4.5. Use DSA or go fix rpm-4.5. > baggins: we probably should revert it then. I'd leave it in test for now, but I'm ok with the downgrade you did on builders. > > All packages produced by rpmbuild-5.4.15 are signed automatically. Been that way > > for several years. > yep. that's what i recalled problem being familiar. If it's been there for years, then why the problems started on 5.4.15? -- Jan R?korajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsgoogle.com bagginspld-linux.org From n3npq at me.com Tue Nov 4 16:39:13 2014 From: n3npq at me.com (Jeffrey Johnson) Date: Tue, 04 Nov 2014 10:39:13 -0500 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <20141104073157.GA2082@home.lan> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> <20141104073157.GA2082@home.lan> Message-ID: On Nov 4, 2014, at 2:31 AM, Jan R?korajski wrote: > > If it's been there for years, then why the problems started on 5.4.15? > Because multiple problems were fixed in rpm-5.4.15 and you insist on testing with ancient (7y ago) software that has no upgrade path. I've addressed the issues with rpm-4.5 in PLD multiple times. The multiple issues with RSA in RPM (all versions) are very well known ... ... future issues will be addressed promptly (but not in rpm-4.5). 73 de Jeff > -- > Jan R?korajski | PLD/Linux > SysAdm | http://www.pld-linux.org/ > bagginsgoogle.com > bagginspld-linux.org > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en From glen at pld-linux.org Tue Nov 4 17:50:09 2014 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Tue, 04 Nov 2014 18:50:09 +0200 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <20141104073157.GA2082@home.lan> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> <20141104073157.GA2082@home.lan> Message-ID: <545903C1.8070700@pld-linux.org> On 04.11.2014 09:31, Jan R?korajski wrote: >>> The RSA v4 keyid is not correctly implementedin rpm-4.5. Use DSA or go fix rpm-4.5. >> >baggins: we probably should revert it then. > I'd leave it in test for now, but I'm ok with the downgrade you did on > builders. i failed to downgrade actually... still trying >>> > >All packages produced by rpmbuild-5.4.15 are signed automatically. Been that way >>> > >for several years. >> >yep. that's what i recalled problem being familiar. > If it's been there for years, then why the problems started on 5.4.15? as i understand, then it's because it started to create RSAv4 not RSAv3 headers. i'm still looking for code diffs, so it's either one of these rpm defines: # +# Choose the non-repudiable signature algorithm: +# DSA (default) +# RSA (implies SHA1) +# ECDSA (implies SHA256) +# DSA/SHA1 +# DSA/SHA224 +# DSA/SHA256 +# DSA/SHA384 +# DSA/SHA512 +# RSA/SHA1 +# RSA/SHA224 +# RSA/SHA256 +# RSA/SHA384 +# RSA/SHA512 +# ECDSA/SHA224 (using NIST P-224) +# ECDSA/SHA256 (using NIST P-256) +# ECDSA/SHA384 (using NIST P-384) +# ECDSA/SHA512 (using NIST P-521) +# +%_build_sign RSA/SHA1 @@ -281,9 +303,13 @@ # 109 Jenkins lookup3.c hashlittle() # 111 RIPEMD-256 # 112 RIPEMD-320 +# 188 BLAKE2B +# 189 BLAKE2BP +# 190 BLAKE2S +# 191 BLAKE2SP # -# Note: choosing anything but MD5 introduces instant legacy incompatibility. -%_build_file_digest_algo 1 +#%_build_file_digest_algo 1 -- glen From glen at pld-linux.org Tue Nov 4 17:52:44 2014 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Tue, 04 Nov 2014 18:52:44 +0200 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> <20141104073157.GA2082@home.lan> Message-ID: <5459045C.5030402@pld-linux.org> On 04.11.2014 17:39, Jeffrey Johnson wrote: > software that has no upgrade path. what do you mean? no upgrade path? it any newer version is on it's upgrade path! be it rpm 5.4.x or rpm 4.12.x! and in pld we do not want to deliberately break old upgrades, especially if there's no actual win for enabling something incompatible. -- glen From glen at pld-linux.org Tue Nov 4 17:55:12 2014 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Tue, 04 Nov 2014 18:55:12 +0200 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <20141104073157.GA2082@home.lan> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> <20141104073157.GA2082@home.lan> Message-ID: <545904F0.8040807@pld-linux.org> On 04.11.2014 09:31, Jan R?korajski wrote: >>> The RSA v4 keyid is not correctly implementedin rpm-4.5. Use DSA or go fix rpm-4.5. >> >baggins: we probably should revert it then. > I'd leave it in test for now, but I'm ok with the downgrade you did on > builders. > actually i meant revert keyid change (use DSA, whatever) not the new version of rpm.... -- glen From n3npq at me.com Tue Nov 4 18:00:58 2014 From: n3npq at me.com (Jeffrey Johnson) Date: Tue, 04 Nov 2014 12:00:58 -0500 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <545903C1.8070700@pld-linux.org> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> <20141104073157.GA2082@home.lan> <545903C1.8070700@pld-linux.org> Message-ID: <34772DFE-8E88-40E1-AD79-45E53A9A8356@me.com> On Nov 4, 2014, at 11:50 AM, Elan Ruusam?e wrote: > On 04.11.2014 09:31, Jan R?korajski wrote: >>>> The RSA v4 keyid is not correctly implementedin rpm-4.5. Use DSA or go fix rpm-4.5. >>> >baggins: we probably should revert it then. >> I'd leave it in test for now, but I'm ok with the downgrade you did on >> builders. > i failed to downgrade actually... still trying >>>> > >All packages produced by rpmbuild-5.4.15 are signed automatically. Been that way >>>> > >for several years. >>> >yep. that's what i recalled problem being familiar. >> If it's been there for years, then why the problems started on 5.4.15? > as i understand, then it's because it started to create RSAv4 not RSAv3 headers. > Yes. But there multiple obscure issues that were fixed, not just generating a V4 keyid correctly. E.g. rpm-4.5 did not get bit counts correct and assumed 8 * byte count was "gud enuf". The assumption is true for DSA but not RSA. So 1 out of 256 RSA parameters will have 8 bits of leading zeroes and the byte count will be wrong. Adjust your testing accoringly: 255 out of 256 RSA signatures will Just Work. > > i'm still looking for code diffs, so it's either one of these rpm defines: > > # > +# Choose the non-repudiable signature algorithm: > +# DSA (default) > +# RSA (implies SHA1) > +# ECDSA (implies SHA256) > +# DSA/SHA1 > +# DSA/SHA224 > +# DSA/SHA256 > +# DSA/SHA384 > +# DSA/SHA512 > +# RSA/SHA1 > +# RSA/SHA224 > +# RSA/SHA256 > +# RSA/SHA384 > +# RSA/SHA512 > +# ECDSA/SHA224 (using NIST P-224) > +# ECDSA/SHA256 (using NIST P-256) > +# ECDSA/SHA384 (using NIST P-384) > +# ECDSA/SHA512 (using NIST P-521) > +# > +%_build_sign RSA/SHA1 > Change to "DSA" for maximum compatibility with rpm-4.5. Note that rpm-5.4.15 was deliberately released with "RSA/SHA1" default to flush out problems as you have reported as early as possible. FYI: rpm-5.4.16 switches from BeeCrypt to LibTomCrypt and uses ECDSA in RPMTAG_ECDSAHEADER = RPMTAG_SIG_BASE+16, /* x */ which avoids (because that tag isn't known) in all legacy and competing versions of RPM. > > @@ -281,9 +303,13 @@ > # 109 Jenkins lookup3.c hashlittle() > # 111 RIPEMD-256 > # 112 RIPEMD-320 > +# 188 BLAKE2B > +# 189 BLAKE2BP > +# 190 BLAKE2S > +# 191 BLAKE2SP > # > -# Note: choosing anything but MD5 introduces instant legacy incompatibility. > -%_build_file_digest_algo 1 > +#%_build_file_digest_algo 1 > And BLAKE2BP (with 256bit protection and faster than MD5) is the preferred default in RPM5 releases. 73 de Jeff > > > -- > glen > > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en From n3npq at me.com Tue Nov 4 18:04:05 2014 From: n3npq at me.com (Jeffrey Johnson) Date: Tue, 04 Nov 2014 12:04:05 -0500 Subject: rpm 5.4.15 creates invalid rpms In-Reply-To: <5459045C.5030402@pld-linux.org> References: <5457EB44.4000207@delfi.ee> <6E9B5CD5-6B51-4A1C-89FC-CC80B4B0C4A0@me.com> <5457FDE9.1060500@delfi.ee> <20141104073157.GA2082@home.lan> <5459045C.5030402@pld-linux.org> Message-ID: <1A6F61A4-BC73-4BC4-B260-C50333883B5B@me.com> On Nov 4, 2014, at 11:52 AM, Elan Ruusam?e wrote: > On 04.11.2014 17:39, Jeffrey Johnson wrote: >> software that has no upgrade path. > what do you mean? no upgrade path? it any newer version is on it's upgrade path! > be it rpm 5.4.x or rpm 4.12.x! > By "no upgrade path", I mean that there will never be any future releases for rpm-4.5.x. Nor am I interested in generating patches for retired software, > and in pld we do not want to deliberately break old upgrades, especially if there's no actual win for enabling something incompatible. > So configure "DSA" and stop claiming Incompatibilities! 73 de Jeff > -- > glen > > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en From arekm at maven.pl Sun Nov 9 14:56:39 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Sun, 9 Nov 2014 14:56:39 +0100 Subject: incomplete mirrors Message-ID: <201411091456.39178.arekm@maven.pl> Hello. Looks like our mirrors are not up to date and thus incomplete. And right now primary ftp1/ep09 is down due to maintenance. Currently we have mirrors like below. adamg, ankry, blues, speedy: can you check your mirrors or declare these dead? ftp 10m CNAME ftp4 ftp1 10m CNAME ftp.sk ; ankry ftp2 10m CNAME fly.mif.pg.gda.pl. ftp3 CNAME ftp.zorg ftp4 10m CNAME ftp.atm ; empty content ;ftp5 10m CNAME ftp.task ftp5 CNAME ftp.task ftp6 10m CNAME ftp.task ; dead ; ftp7 10m CNAME ftp.intersec master-ftp 10m CNAME ep09 rsync-ftp 10m CNAME rsync ; adamg ftp.atm A 217.149.246.5 ; rmf ftp.pk A 149.156.143.253 ftp.sk CNAME ep09 ftp.sk2 A 217.73.31.17 ; ankry ftp.pg A 153.19.42.122 ; blues ftp.task A 153.19.251.224 ; speedy ftp.zorg A 91.198.97.250 -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From atler at pld-linux.org Tue Nov 11 17:10:43 2014 From: atler at pld-linux.org (Jan Palus) Date: Tue, 11 Nov 2014 17:10:43 +0100 Subject: ERRORS: xorg-driver-video-nvidia.spec In-Reply-To: References: Message-ID: <20141111161043.GB15257@cukinia.lan> On 10.11.2014 19:12, PLD th-i486 builder wrote: > + exec nice -n 0 rpmbuild -bb --define '_smp_mflags -j9' --define '_make_opts -Otarget' --define '_pld_builder 1' --define '_topdir /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003' --define '_specdir %{_topdir}' --define '_sourcedir %{_specdir}' --define '_rpmdir %{_topdir}/RPMS' --define '_builddir %{_topdir}/BUILD' --without userspace --target i486-pld-linux --define 'build_kernels 3.4,3.10,3.14' /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/xorg-driver-video-nvidia.spec > Building target platforms: i486-pld-linux > Executing(%prep): /bin/sh -e /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/BUILD/tmp/rpm-tmp.93635 > + umask 022 > + cd /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/BUILD > + cd /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/BUILD > + rm -rf 'NVIDIA-Linux-x86*-340.58*' > + /bin/sh /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/NVIDIA-Linux-x86-340.58.run --extract-only > ERROR: Temporary directory /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/BUILD/tmp is not executable - use the --tmpdir option to specify a different one. > error: Bad exit status from /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/BUILD/tmp/rpm-tmp.93635 (%prep) > > > RPM build errors: > Bad exit status from /tmp/B.43eb9149-96e3-485f-845a-eef43a2b8003/BUILD/tmp/rpm-tmp.93635 (%prep) > ended at: Mon Nov 10 20:12:34 2014, done in 0:00:05.752894 > error: No files produced. anyone has an idea why it happens from time to time? From j.rekorajski at gmail.com Wed Nov 12 13:22:26 2014 From: j.rekorajski at gmail.com (=?UTF-8?Q?Jan_R=C4=99korajski?=) Date: Wed, 12 Nov 2014 13:22:26 +0100 Subject: [packages/FlightGear] - release 3 (by relup.sh) In-Reply-To: <756ca1e7f32056778178f26e56d1a73b2c94472d_refs_heads_master@pld-linux.org> References: <756ca1e7f32056778178f26e56d1a73b2c94472d_refs_heads_master@pld-linux.org> Message-ID: On Wed, Nov 12, 2014 at 1:05 PM, arekm wrote: > commit 756ca1e7f32056778178f26e56d1a73b2c94472d > Author: Arkadiusz Mi?kiewicz > Date: Wed Nov 12 13:05:05 2014 +0100 > > - release 3 (by relup.sh) Did you try if it works? It segfaults for me. -- Jan R?korajski | SysAdm | PLD/Linux | http://www.pld-linux.org/ bagginspld-linux.org From arekm at maven.pl Wed Nov 12 13:25:32 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Wed, 12 Nov 2014 13:25:32 +0100 Subject: [packages/FlightGear] - release 3 (by relup.sh) In-Reply-To: References: <756ca1e7f32056778178f26e56d1a73b2c94472d_refs_heads_master@pld-linux.org> Message-ID: <201411121325.36572.arekm@maven.pl> On Wednesday 12 of November 2014, Jan R?korajski wrote: > On Wed, Nov 12, 2014 at 1:05 PM, arekm wrote: > > commit 756ca1e7f32056778178f26e56d1a73b2c94472d > > Author: Arkadiusz Mi?kiewicz > > Date: Wed Nov 12 13:05:05 2014 +0100 > > > > - release 3 (by relup.sh) > > Did you try if it works? It segfaults for me. Nope, only build tested. Build killed then. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From arekm at maven.pl Thu Nov 13 20:49:53 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Thu, 13 Nov 2014 20:49:53 +0100 Subject: kde konsole underline behaviour In-Reply-To: <7818632.NjVgpc3pcV@laptok> References: <201410162009.53382.arekm@maven.pl> <201411012016.59451.arekm@maven.pl> <7818632.NjVgpc3pcV@laptok> Message-ID: <201411132049.53220.arekm@maven.pl> On Saturday 01 of November 2014, ?ukasz Ma?ko wrote: > Dnia sobota, 1 listopada 2014 20:16:59 Arkadiusz Mi?kiewicz pisze: > > On Thursday 16 of October 2014, ?ukasz Ma?ko wrote: > > > > Do you youse konsole color scheme with black background? If not try > > > > one (white on black for example) > > > > > > Nope, still works correctly. > > > > I assume your setup is up to date th (including th-test etc) ? > > Yes. The latest possible we have. And I cannot reproduce it. Which font do you use for konsole? Please try with Liberation Mono (remember to start new konsole to be sure). If using Liberation Mono will not be enough then please: - set liberation mono as konsole font - xrandr --dpi some-non-default-value-like-80-or-100 - start new konsole - try vim /etc/passwd + cursorline then -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From ed at yen.ipipan.waw.pl Fri Nov 14 08:22:33 2014 From: ed at yen.ipipan.waw.pl (=?utf-8?B?xYF1a2FzeiBNYcWba28=?=) Date: Fri, 14 Nov 2014 08:22:33 +0100 Subject: kde konsole underline behaviour In-Reply-To: <201411132049.53220.arekm@maven.pl> References: <201410162009.53382.arekm@maven.pl> <7818632.NjVgpc3pcV@laptok> <201411132049.53220.arekm@maven.pl> Message-ID: <5346809.9sHJa2rg3C@laptok> Dnia czwartek, 13 listopada 2014 20:49:53 Arkadiusz Mi?kiewicz pisze: [...] > Which font do you use for konsole? I'm using Terminus. > Please try with Liberation Mono (remember to start new konsole to be sure). Where can I find this font? Can you send it to me? -- ?ukasz Ma?ko _o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafryka?skie s?owo oznaczaj?ce "Nie umiem zainstalowa? Debiana" From arekm at maven.pl Fri Nov 14 08:35:31 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Fri, 14 Nov 2014 08:35:31 +0100 Subject: kde konsole underline behaviour In-Reply-To: <5346809.9sHJa2rg3C@laptok> References: <201410162009.53382.arekm@maven.pl> <201411132049.53220.arekm@maven.pl> <5346809.9sHJa2rg3C@laptok> Message-ID: <201411140835.31356.arekm@maven.pl> On Friday 14 of November 2014, ?ukasz Ma?ko wrote: > Dnia czwartek, 13 listopada 2014 20:49:53 Arkadiusz Mi?kiewicz pisze: > [...] > > > Which font do you use for konsole? > > I'm using Terminus. > > > Please try with Liberation Mono (remember to start new konsole to be > > sure). > > Where can I find this font? Can you send it to me? fonts-TTF-RedHat-liberation1 package -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From ed at yen.ipipan.waw.pl Fri Nov 14 11:02:33 2014 From: ed at yen.ipipan.waw.pl (=?utf-8?B?xYF1a2FzeiBNYcWba28=?=) Date: Fri, 14 Nov 2014 11:02:33 +0100 Subject: kde konsole underline behaviour In-Reply-To: <201411140835.31356.arekm@maven.pl> References: <201410162009.53382.arekm@maven.pl> <5346809.9sHJa2rg3C@laptok> <201411140835.31356.arekm@maven.pl> Message-ID: <1673992.Zv7NW8xO3T@laptok> Dnia pi?tek, 14 listopada 2014 08:35:31 Arkadiusz Mi?kiewicz pisze: > On Friday 14 of November 2014, ?ukasz Ma?ko wrote: > > Dnia czwartek, 13 listopada 2014 20:49:53 Arkadiusz Mi?kiewicz pisze: > > [...] > > > > > Which font do you use for konsole? > > > > I'm using Terminus. > > > > > Please try with Liberation Mono (remember to start new konsole to be > > > sure). > > > > Where can I find this font? Can you send it to me? > > fonts-TTF-RedHat-liberation1 package OK. With both liberation font and dpi set to 80 I've reproduced your problem. It was exacltly like on your video. -- ?ukasz Ma?ko _o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafryka?skie s?owo oznaczaj?ce "Nie umiem zainstalowa? Debiana" From qboosh at pld-linux.org Mon Nov 17 18:25:14 2014 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Mon, 17 Nov 2014 18:25:14 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> Message-ID: <20141117172514.GA1119@mail> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY changed ltmain.sh (and other files) location again. Now it's /usr/share/libtool/build-aux. -- Jakub Bogusz http://qboosh.pl/ From arekm at maven.pl Mon Nov 17 18:34:55 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Mon, 17 Nov 2014 18:34:55 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: <20141117172514.GA1119@mail> References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <20141117172514.GA1119@mail> Message-ID: <201411171834.55583.arekm@maven.pl> On Monday 17 of November 2014, Jakub Bogusz wrote: > php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY changed > ltmain.sh (and other files) location again. > Now it's /usr/share/libtool/build-aux. Will symlink as temporary solution work? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From j.rekorajski at gmail.com Mon Nov 17 18:37:15 2014 From: j.rekorajski at gmail.com (=?UTF-8?Q?Jan_R=C4=99korajski?=) Date: Mon, 17 Nov 2014 18:37:15 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: <201411171834.55583.arekm@maven.pl> References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <20141117172514.GA1119@mail> <201411171834.55583.arekm@maven.pl> Message-ID: On Mon, Nov 17, 2014 at 6:34 PM, Arkadiusz Mi?kiewicz wrote: > On Monday 17 of November 2014, Jakub Bogusz wrote: >> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY changed >> ltmain.sh (and other files) location again. >> Now it's /usr/share/libtool/build-aux. > > Will symlink as temporary solution work? Please don't, that temporary solution will stay forever and will cause mysterious breakage later on. -- Jan R?korajski | SysAdm | PLD/Linux | http://www.pld-linux.org/ bagginspld-linux.org From arekm at maven.pl Mon Nov 17 18:40:22 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Mon, 17 Nov 2014 18:40:22 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <201411171834.55583.arekm@maven.pl> Message-ID: <201411171840.23032.arekm@maven.pl> On Monday 17 of November 2014, Jan R?korajski wrote: > On Mon, Nov 17, 2014 at 6:34 PM, Arkadiusz Mi?kiewicz wrote: > > On Monday 17 of November 2014, Jakub Bogusz wrote: > >> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY changed > >> ltmain.sh (and other files) location again. > >> Now it's /usr/share/libtool/build-aux. > > > > Will symlink as temporary solution work? > > Please don't, that temporary solution will stay forever and will cause > mysterious > breakage later on. Downgraded libtool for now, it will be back after 2014 snap. I hope it's fine for you? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From qboosh at pld-linux.org Mon Nov 17 19:01:06 2014 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Mon, 17 Nov 2014 19:01:06 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: <201411171840.23032.arekm@maven.pl> References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <201411171834.55583.arekm@maven.pl> <201411171840.23032.arekm@maven.pl> Message-ID: <20141117180106.GA1342@mail> On Mon, Nov 17, 2014 at 06:40:22PM +0100, Arkadiusz Mi?kiewicz wrote: > On Monday 17 of November 2014, Jan R?korajski wrote: > > On Mon, Nov 17, 2014 at 6:34 PM, Arkadiusz Mi?kiewicz > wrote: > > > On Monday 17 of November 2014, Jakub Bogusz wrote: > > >> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY changed > > >> ltmain.sh (and other files) location again. > > >> Now it's /usr/share/libtool/build-aux. > > > > > > Will symlink as temporary solution work? > > > > Please don't, that temporary solution will stay forever and will cause > > mysterious > > breakage later on. > > Downgraded libtool for now, it will be back after 2014 snap. I hope it's fine > for you? It's just a matter of changing one symlink in %{_libdir}/php/build in php.spec (* all its branches) and rebuilding base php package(s) (without touching external modules). -- Jakub Bogusz http://qboosh.pl/ From j.rekorajski at gmail.com Mon Nov 17 19:13:15 2014 From: j.rekorajski at gmail.com (=?UTF-8?Q?Jan_R=C4=99korajski?=) Date: Mon, 17 Nov 2014 19:13:15 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: <20141117180106.GA1342@mail> References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <201411171834.55583.arekm@maven.pl> <201411171840.23032.arekm@maven.pl> <20141117180106.GA1342@mail> Message-ID: On Mon, Nov 17, 2014 at 7:01 PM, Jakub Bogusz wrote: > On Mon, Nov 17, 2014 at 06:40:22PM +0100, Arkadiusz Mi?kiewicz wrote: >> On Monday 17 of November 2014, Jan R?korajski wrote: >> > On Mon, Nov 17, 2014 at 6:34 PM, Arkadiusz Mi?kiewicz >> wrote: >> > > On Monday 17 of November 2014, Jakub Bogusz wrote: >> > >> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY changed >> > >> ltmain.sh (and other files) location again. >> > >> Now it's /usr/share/libtool/build-aux. >> > > >> > > Will symlink as temporary solution work? >> > >> > Please don't, that temporary solution will stay forever and will cause >> > mysterious >> > breakage later on. >> >> Downgraded libtool for now, it will be back after 2014 snap. I hope it's fine >> for you? > > It's just a matter of changing one symlink in %{_libdir}/php/build in > php.spec (* all its branches) and rebuilding base php package(s) > (without touching external modules). If this is such a simple change I see no point in downgrading. -- Jan R?korajski | SysAdm | PLD/Linux | http://www.pld-linux.org/ bagginspld-linux.org From arekm at maven.pl Mon Nov 17 19:25:07 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Mon, 17 Nov 2014 19:25:07 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <20141117180106.GA1342@mail> Message-ID: <201411171925.07738.arekm@maven.pl> On Monday 17 of November 2014, Jan R?korajski wrote: > On Mon, Nov 17, 2014 at 7:01 PM, Jakub Bogusz wrote: > > On Mon, Nov 17, 2014 at 06:40:22PM +0100, Arkadiusz Mi?kiewicz wrote: > >> On Monday 17 of November 2014, Jan R?korajski wrote: > >> > On Mon, Nov 17, 2014 at 6:34 PM, Arkadiusz Mi?kiewicz > >> > >> wrote: > >> > > On Monday 17 of November 2014, Jakub Bogusz wrote: > >> > >> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY > >> > >> changed ltmain.sh (and other files) location again. > >> > >> Now it's /usr/share/libtool/build-aux. > >> > > > >> > > Will symlink as temporary solution work? > >> > > >> > Please don't, that temporary solution will stay forever and will cause > >> > mysterious > >> > breakage later on. > >> > >> Downgraded libtool for now, it will be back after 2014 snap. I hope it's > >> fine for you? > > > > It's just a matter of changing one symlink in %{_libdir}/php/build in > > php.spec (* all its branches) and rebuilding base php package(s) > > (without touching external modules). > > If this is such a simple change I see no point in downgrading. So fix lftp then ;-) -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From qboosh at pld-linux.org Mon Nov 17 20:23:07 2014 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Mon, 17 Nov 2014 20:23:07 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: <201411171925.07738.arekm@maven.pl> References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <20141117180106.GA1342@mail> <201411171925.07738.arekm@maven.pl> Message-ID: <20141117192307.GA1649@mail> On Mon, Nov 17, 2014 at 07:25:07PM +0100, Arkadiusz Mi?kiewicz wrote: > On Monday 17 of November 2014, Jan R?korajski wrote: > > On Mon, Nov 17, 2014 at 7:01 PM, Jakub Bogusz wrote: > > > On Mon, Nov 17, 2014 at 06:40:22PM +0100, Arkadiusz Mi?kiewicz wrote: > > >> On Monday 17 of November 2014, Jan R?korajski wrote: > > >> > On Mon, Nov 17, 2014 at 6:34 PM, Arkadiusz Mi?kiewicz > > >> > > >> wrote: > > >> > > On Monday 17 of November 2014, Jakub Bogusz wrote: > > >> > >> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY > > >> > >> changed ltmain.sh (and other files) location again. > > >> > >> Now it's /usr/share/libtool/build-aux. > > >> > > > > >> > > Will symlink as temporary solution work? > > >> > > > >> > Please don't, that temporary solution will stay forever and will cause > > >> > mysterious > > >> > breakage later on. > > >> > > >> Downgraded libtool for now, it will be back after 2014 snap. I hope it's > > >> fine for you? > > > > > > It's just a matter of changing one symlink in %{_libdir}/php/build in > > > php.spec (* all its branches) and rebuilding base php package(s) > > > (without touching external modules). > > > > If this is such a simple change I see no point in downgrading. > > So fix lftp then ;-) Generic workaround: mv build-aux/snippet{,.save} libtoolize mv build-aux/snippet{.save,} But now I found a patch, which will be applied in libtool 2.4.4: https://lists.gnu.org/archive/html/libtool-patches/2014-10/msg00018.html -- Jakub Bogusz http://qboosh.pl/ From baggins at pld-linux.org Mon Nov 17 21:21:40 2014 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Mon, 17 Nov 2014 21:21:40 +0100 Subject: [packages/php-pecl-apcu] libtool fix In-Reply-To: <20141117192307.GA1649@mail> References: <19cb3b4600545e6eed9c87992a202bae70782e07_refs_heads_master@pld-linux.org> <20141117180106.GA1342@mail> <201411171925.07738.arekm@maven.pl> <20141117192307.GA1649@mail> Message-ID: <20141117202140.GA2002@home.lan> On Mon, 17 Nov 2014, Jakub Bogusz wrote: > On Mon, Nov 17, 2014 at 07:25:07PM +0100, Arkadiusz Mi?kiewicz wrote: > > On Monday 17 of November 2014, Jan R?korajski wrote: > > > On Mon, Nov 17, 2014 at 7:01 PM, Jakub Bogusz wrote: > > > > On Mon, Nov 17, 2014 at 06:40:22PM +0100, Arkadiusz Mi?kiewicz wrote: > > > >> On Monday 17 of November 2014, Jan R?korajski wrote: > > > >> > On Mon, Nov 17, 2014 at 6:34 PM, Arkadiusz Mi?kiewicz > > > >> > > > >> wrote: > > > >> > > On Monday 17 of November 2014, Jakub Bogusz wrote: > > > >> > >> php (all versions of) needs fixing wrt. libtool 2.4.3 - THEY > > > >> > >> changed ltmain.sh (and other files) location again. > > > >> > >> Now it's /usr/share/libtool/build-aux. > > > >> > > > > > >> > > Will symlink as temporary solution work? > > > >> > > > > >> > Please don't, that temporary solution will stay forever and will cause > > > >> > mysterious > > > >> > breakage later on. > > > >> > > > >> Downgraded libtool for now, it will be back after 2014 snap. I hope it's > > > >> fine for you? > > > > > > > > It's just a matter of changing one symlink in %{_libdir}/php/build in > > > > php.spec (* all its branches) and rebuilding base php package(s) > > > > (without touching external modules). > > > > > > If this is such a simple change I see no point in downgrading. > > > > So fix lftp then ;-) > > Generic workaround: > > mv build-aux/snippet{,.save} > libtoolize > mv build-aux/snippet{.save,} > > But now I found a patch, which will be applied in libtool 2.4.4: > > https://lists.gnu.org/archive/html/libtool-patches/2014-10/msg00018.html Applied to libtool. -- Jan R?korajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginspld-linux.org From gzohop at gmail.com Tue Nov 25 23:04:18 2014 From: gzohop at gmail.com (Grzesiek) Date: Tue, 25 Nov 2014 23:04:18 +0100 Subject: Th 2013 snapshot In-Reply-To: <20131214163752.GA1377@home.mimuw.edu.pl> References: <20131214163752.GA1377@home.mimuw.edu.pl> Message-ID: <5474FCE2.2080306@gmail.com> W dniu 14.12.2013 o 17:37, Jan R?korajski pisze: > Hi, > To celebrate new year I'm going to make 2013 snapshot of Th line > at the end of December. It will contain the current state of > main/ready/test tree. > > If you know of any problems in current package set please report > and/or fix them. > Will there be th2014 snapshot ? From arekm at maven.pl Tue Nov 25 23:20:16 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Tue, 25 Nov 2014 23:20:16 +0100 Subject: 2014 snapshot (was Re: Th 2013 snapshot) In-Reply-To: <5474FCE2.2080306@gmail.com> References: <20131214163752.GA1377@home.mimuw.edu.pl> <5474FCE2.2080306@gmail.com> Message-ID: <201411252320.17059.arekm@maven.pl> On Tuesday 25 of November 2014, Grzesiek wrote: > W dniu 14.12.2013 o 17:37, Jan R?korajski pisze: > > Hi, > > To celebrate new year I'm going to make 2013 snapshot of Th line > > at the end of December. It will contain the current state of > > main/ready/test tree. > > > > If you know of any problems in current package set please report > > and/or fix them. > > Will there be th2014 snapshot ? Will be really soon: 22:02 < baggins> BTW, if you have anything to update you thinks should be in the snap now is your last chance -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From atler at pld-linux.org Sun Nov 30 11:56:55 2014 From: atler at pld-linux.org (atler) Date: Sun, 30 Nov 2014 11:56:55 +0100 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <14539.1417284117@distfiles.pld-linux.org> References: <14539.1417284117@distfiles.pld-linux.org> Message-ID: <20141130105655.GA17107@cukinia.lan> On 29.11.2014 19:01, atler wrote: > Request by: atler > > wget -nv --no-check-certificate --user-agent=PLD/distfiles -O ./tmp/01bf67c4-9979-47ad-b145-5981d6803b73/367509550c0d21b2cf4066c6d59a4a13/groovy-binary-2.3.8.zip https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip: > https://d29vzk4ow07wi7.cloudfront.net/ad64d8ab15376d529ad4a217cc564fa75f96969f?response-content-disposition=attachment;filename=%22groovy-binary-2.3.8.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvYWQ2NGQ4YWIxNTM3NmQ1MjlhZDRhMjE3Y2M1NjRmYTc1Zjk2OTY5Zj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMmdyb292eS1iaW5hcnktMi4zLjguemlwJTIyIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDE3Mjg0MTcyfSwiSXBBZGRyZXNzIjp7IkFXUzpTb3VyY2VJcCI6IjAuMC4wLjAvMCJ9fX1dfQ__&Signature=WJaq7BeCw5gkoVvzIw3Yxm2nVicoiINI8eK9BlXNqNJCLK~Fj5-jyZsWR36NzbQ75fILecQW4m1CPyIf2HnfxrN1Og5laoJXqfFa-ieJeAZAXqYlHdPHY~D-uyE7O30TJcyJCsav~mHj42ccr~gyuG93sAUoL4hYYE63Am5ohHmm6Fods~5nzZlJhCOSZOHjNxiSPt2J1zLh3R-5~GX-YAwStmWB3Mu5buXea4cTAEW9OZkhd2peMV4eI-kw~42i~pIt-jlN-SbXG4A7tZmDeci0YQQ1mTb3IyIsc-kcLXYGWiG69U030UQPNX-sky3Ur1XM3SqwvlsIVryvJSqZBA__&Key-Pair-Id=APKAIQIOJCQ5764M5VTQ: > 2014-11-29 19:01:53 ERROR 403: Forbidden. Together with bintray's support we're trying to figure out why above happens on distfiles machine, so could anyone with appropriate permissions send me output of wget -V and above command without -nv argument (executed on the same machine obviously)? From baggins at pld-linux.org Sun Nov 30 13:04:55 2014 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sun, 30 Nov 2014 13:04:55 +0100 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <20141130105655.GA17107@cukinia.lan> References: <14539.1417284117@distfiles.pld-linux.org> <20141130105655.GA17107@cukinia.lan> Message-ID: <20141130120455.GA2127@home.lan> On Sun, 30 Nov 2014, atler wrote: > On 29.11.2014 19:01, atler wrote: > > Request by: atler > > > > wget -nv --no-check-certificate --user-agent=PLD/distfiles -O ./tmp/01bf67c4-9979-47ad-b145-5981d6803b73/367509550c0d21b2cf4066c6d59a4a13/groovy-binary-2.3.8.zip https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip: > > https://d29vzk4ow07wi7.cloudfront.net/ad64d8ab15376d529ad4a217cc564fa75f96969f?response-content-disposition=attachment;filename=%22groovy-binary-2.3.8.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvYWQ2NGQ4YWIxNTM3NmQ1MjlhZDRhMjE3Y2M1NjRmYTc1Zjk2OTY5Zj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMmdyb292eS1iaW5hcnktMi4zLjguemlwJTIyIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDE3Mjg0MTcyfSwiSXBBZGRyZXNzIjp7IkFXUzpTb3VyY2VJcCI6IjAuMC4wLjAvMCJ9fX1dfQ__&Signature=WJaq7BeCw5gkoVvzIw3Yxm2nVicoiINI8eK9BlXNqNJCLK~Fj5-jyZsWR36NzbQ75fILecQW4m1CPyIf2HnfxrN1Og5laoJXqfFa-ieJeAZAXqYlHdPHY~D-uyE7O30TJcyJCsav~mHj42ccr~gyuG93sAUoL4hYYE63Am5ohHmm6Fods~5nzZlJhCOSZOHjNxiSPt2J1zLh3R-5~GX-YAwStmWB3Mu5buXea4cTAEW9OZkhd2peMV4eI-kw~42i~pIt-jlN-SbXG4A7tZmDeci0YQQ1mTb3IyIsc-kcLXYGWiG69U030UQPNX-sky3Ur1XM3SqwvlsIVryvJSqZBA__&Key-Pair-Id=APKAIQIOJCQ5764M5VTQ: > > 2014-11-29 19:01:53 ERROR 403: Forbidden. > > Together with bintray's support we're trying to figure out why above > happens on distfiles machine, so could anyone with appropriate > permissions send me output of wget -V and above command without -nv > argument (executed on the same machine obviously)? $ wget --no-check-certificate https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip converted 'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (ANSI_X3.4-1968) -> 'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (UTF-8) --2014-11-30 12:59:31-- https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip Resolving dl.bintray.com (dl.bintray.com)... 5.153.24.114 Connecting to dl.bintray.com (dl.bintray.com)|5.153.24.114|:443... connected. HTTP request sent, awaiting response... 302 Location: https://d29vzk4ow07wi7.cloudfront.net/ad64d8ab15376d529ad4a217cc564fa75f96969f?response-content-disposition=attachment%3Bfilename%3D%22groovy-binary-2.3.8.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvYWQ2NGQ4YWIxNTM3NmQ1MjlhZDRhMjE3Y2M1NjRmYTc1Zjk2OTY5Zj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMmdyb292eS1iaW5hcnktMi4zLjguemlwJTIyIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDE3MzQ4ODMyfSwiSXBBZGRyZXNzIjp7IkFXUzpTb3VyY2VJcCI6IjAuMC4wLjAvMCJ9fX1dfQ__&Signature=UHBUm6VRB2DJ7qLIoV0PI5yWayuef62gGRqS0ErpERzywpMxEwy2WlKu-Lapvvbq0~7MOmQHzxEYnQqDDJ--HViKXq7WBfQOcmrTDB4Un0mnCI0SRo0Z7KKBiV4wIEk5aIie6EY9CHwMbTye4LtOx6Vuys6fEls5zHqF8ia52qai6Z9-tfjCGyIkQClQ~V~ggkP5d09kBRKF2lUXAnhfFzoOCjlHPeF8obY9AV~2HD-hO05cWXD05F7Zqx~0S5zlJhOsHhi0-zJmZpBZYb-cJraUS1Fwj0X1toYZkcLsskeiY26S1yG7cxHiE1ay7INt92dgKAHG0PBX0ZpMfpWMhw__&Key-Pair-Id=APKAIQIOJCQ5764M5VTQ [following] converted 'https://d29vzk4ow07wi7.cloudfront.net/ad64d8ab15376d529ad4a217cc564fa75f96969f?response-content-disposition=attachment%3Bfilename%3D%22groovy-binary-2.3.8.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvYWQ2NGQ4YWIxNTM3NmQ1MjlhZDRhMjE3Y2M1NjRmYTc1Zjk2OTY5Zj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMmdyb292eS1iaW5hcnktMi4zLjguemlwJTIyIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDE3MzQ4ODMyfSwiSXBBZGRyZXNzIjp7IkFXUzpTb3VyY2VJcCI6IjAuMC4wLjAvMCJ9fX1dfQ__&Signature=UHBUm6VRB2DJ7qLIoV0PI5yWayuef62gGRqS0ErpERzywpMxEwy2WlKu-Lapvvbq0~7MOmQHzxEYnQqDDJ--HViKXq7WBfQOcmrTDB4Un0mnCI0SRo0Z7KKBiV4wIEk5aIie6EY9CHwMbTye4LtOx6Vuys6fEls5zHqF8ia52qai6Z9-tfjCGyIkQClQ~V~ggkP5d09kBRKF2lUXAnhfFzoOCjlHPeF8obY9AV~2HD-hO05cWXD05F7Zqx~0S5zlJhOsHhi0-zJmZpBZYb-cJraUS1Fwj0X1toYZkcLsskeiY26S1yG7cxHiE1ay7INt92dgKAHG0PBX0ZpMfpWMhw__&Key-Pair-Id=APKAIQIOJCQ5764M5VTQ' (ANSI_X3.4-1968) -> 'https://d29vzk4ow07wi7.cloudfront.net/ad64d8ab15376d529ad4a217cc564fa75f96969f?response-content-disposition=attachment;filename="groovy-binary-2.3.8.zip"&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvYWQ2NGQ4YWIxNTM3NmQ1MjlhZDRhMjE3Y2M1NjRmYTc1Zjk2OTY5Zj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMmdyb292eS1iaW5hcnktMi4zLjguemlwJTIyIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDE3MzQ4ODMyfSwiSXBBZGRyZXNzIjp7IkFXUzpTb3VyY2VJcCI6IjAuMC4wLjAvMCJ9fX1dfQ__&Signature=UHBUm6VRB2DJ7qLIoV0PI5yWayuef62gGRqS0ErpERzywpMxEwy2WlKu-Lapvvbq0~7MOmQHzxEYnQqDDJ--HViKXq7WBfQOcmrTDB4Un0mnCI0SRo0Z7KKBiV4wIEk5aIie6EY9CHwMbTye4LtOx6Vuys6fEls5zHqF8ia52qai6Z9-tfjCGyIkQClQ~V~ggkP5d09kBRKF2lUXAnhfFzoOCjlHPeF8obY9AV~2HD-hO05cWXD05F7Zqx~0S5zlJhOsHhi0-zJmZpBZYb-cJraUS1Fwj0X1toYZkcLsskeiY26S1yG7cxHiE1ay7INt92dgKAHG0PBX0ZpMfpWMhw__&Key-Pair-Id=APKAIQIOJCQ5764M5VTQ' (UTF-8) --2014-11-30 12:59:32-- https://d29vzk4ow07wi7.cloudfront.net/ad64d8ab15376d529ad4a217cc564fa75f96969f?response-content-disposition=attachment;filename=%22groovy-binary-2.3.8.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvYWQ2NGQ4YWIxNTM3NmQ1MjlhZDRhMjE3Y2M1NjRmYTc1Zjk2OTY5Zj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMmdyb292eS1iaW5hcnktMi4zLjguemlwJTIyIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDE3MzQ4ODMyfSwiSXBBZGRyZXNzIjp7IkFXUzpTb3VyY2VJcCI6IjAuMC4wLjAvMCJ9fX1dfQ__&Signature=UHBUm6VRB2DJ7qLIoV0PI5yWayuef62gGRqS0ErpERzywpMxEwy2WlKu-Lapvvbq0~7MOmQHzxEYnQqDDJ--HViKXq7WBfQOcmrTDB4Un0mnCI0SRo0Z7KKBiV4wIEk5aIie6EY9CHwMbTye4LtOx6Vuys6fEls5zHqF8ia52qai6Z9-tfjCGyIkQClQ~V~ggkP5d09kBRKF2lUXAnhfFzoOCjlHPeF8obY9AV~2HD-hO05cWXD05F7Zqx~0S5zlJhOsHhi0-zJmZpBZYb-cJraUS1Fwj0X1toYZkcLsskeiY26S1yG7cxHiE1ay7INt92dgKAHG0PBX0ZpMfpWMhw__&Key-Pair-Id=APKAIQIOJCQ5764M5VTQ Resolving d29vzk4ow07wi7.cloudfront.net (d29vzk4ow07wi7.cloudfront.net)... 54.239.168.99, 54.239.168.134, 54.230.200.21, ... Connecting to d29vzk4ow07wi7.cloudfront.net (d29vzk4ow07wi7.cloudfront.net)|54.239.168.99|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-11-30 12:59:32 ERROR 403: Forbidden. Important line is: converted 'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (ANSI_X3.4-1968) -> 'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (UTF-8) Download works If I either set locale to something.UTF-8 or add --local-encoding=UTF-8 option to wget. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Sun Nov 30 14:56:12 2014 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Sun, 30 Nov 2014 15:56:12 +0200 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <20141130120455.GA2127@home.lan> References: <14539.1417284117@distfiles.pld-linux.org> <20141130105655.GA17107@cukinia.lan> <20141130120455.GA2127@home.lan> Message-ID: <547B21FC.60408@pld-linux.org> On 30.11.2014 14:04, Jan R?korajski wrote: > Important line is: > > converted 'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (ANSI_X3.4-1968) ->'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (UTF-8) > > Download works If I either set locale to something.UTF-8 or > add --local-encoding=UTF-8 option to wget. > > -- perhaps they should set proper content-type to avoid wget trying charset translation. what i see now is: Content-Type: application/unknown -- glen From jajcus at jajcus.net Sun Nov 30 15:06:50 2014 From: jajcus at jajcus.net (Jacek Konieczny) Date: Sun, 30 Nov 2014 15:06:50 +0100 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <547B21FC.60408@pld-linux.org> References: <14539.1417284117@distfiles.pld-linux.org> <20141130105655.GA17107@cukinia.lan> <20141130120455.GA2127@home.lan> <547B21FC.60408@pld-linux.org> Message-ID: <547B247A.2030502@jajcus.net> On 2014-11-30 14:56, Elan Ruusam?e wrote: > On 30.11.2014 14:04, Jan R?korajski wrote: >> Download works If I either set locale to something.UTF-8 or >> add --local-encoding=UTF-8 option to wget. >> >> -- > perhaps they should set proper content-type to avoid wget trying charset > translation. what i see now is: > > Content-Type: application/unknown 'application/*' is not 'text/*', no sane utility should ever try charset conversion for 'application/*'. Jacek From atler at pld-linux.org Sun Nov 30 15:17:16 2014 From: atler at pld-linux.org (Jan Palus) Date: Sun, 30 Nov 2014 15:17:16 +0100 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <547B21FC.60408@pld-linux.org> References: <14539.1417284117@distfiles.pld-linux.org> <20141130105655.GA17107@cukinia.lan> <20141130120455.GA2127@home.lan> <547B21FC.60408@pld-linux.org> Message-ID: <20141130141716.GA28287@cukinia.lan> On 30.11.2014 15:56, Elan Ruusam?e wrote: > On 30.11.2014 14:04, Jan R?korajski wrote: > > Important line is: > > > > converted 'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (ANSI_X3.4-1968) ->'https://dl.bintray.com/groovy/maven/groovy-binary-2.3.8.zip' (UTF-8) > > > > Download works If I either set locale to something.UTF-8 or > > add --local-encoding=UTF-8 option to wget. > > > > -- > perhaps they should set proper content-type to avoid wget trying charset > translation. what i see now is: > > Content-Type: application/unknown If I read above correctly conversion is applied to url only before any http request happens and probably it's something about converted url that breaks download process. Anyway thanks Jan, reproducer was shared with bintray's support and let's see if they come up with a solution. From glen at pld-linux.org Sun Nov 30 15:25:29 2014 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Sun, 30 Nov 2014 16:25:29 +0200 Subject: cp or neccessary? Message-ID: <547B28D9.5040702@pld-linux.org> is this lousy copy-paste, or neccessary have that obsoletes in rather unrelated packages? ? grep -r ^Obsoletes:.*perl-libxml-enno ~/all-specs /home/users/glen/all-specs/perl-XML-Checker.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-DOM.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-Filter-DetectWS.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-Filter-Reindent.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-Filter-SAXT.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-Handler-Composer.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-Handler-PrintEvents.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-RegExp.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-UM.spec:Obsoletes: perl-libxml-enno /home/users/glen/all-specs/perl-XML-XQL.spec:Obsoletes: perl-libxml-enno ? -- glen From atler at pld-linux.org Sun Nov 30 21:50:07 2014 From: atler at pld-linux.org (Jan Palus) Date: Sun, 30 Nov 2014 21:50:07 +0100 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <20141130141716.GA28287@cukinia.lan> References: <14539.1417284117@distfiles.pld-linux.org> <20141130105655.GA17107@cukinia.lan> <20141130120455.GA2127@home.lan> <547B21FC.60408@pld-linux.org> <20141130141716.GA28287@cukinia.lan> Message-ID: <20141130205007.GA14561@cukinia.lan> On 30.11.2014 15:17, Jan Palus wrote: > Anyway thanks Jan, reproducer was shared with bintray's support and > let's see if they come up with a solution. Few hours after my email they identified IRI support to be responsible for above behaviour (on by default) and provided two workarounds: 1. Adding --no-iri to wget 2. Adding parameter to URL to skip redirection (now in spec) Not sure if we consider first solution but anyway I'm pretty impressed with their support team, especially taking into account that it's Sunday today. With above workarounds available they're not willing to fix handling of "converted" URL - at least for now. From glen at pld-linux.org Sun Nov 30 22:03:05 2014 From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Sun, 30 Nov 2014 23:03:05 +0200 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <20141130205007.GA14561@cukinia.lan> References: <14539.1417284117@distfiles.pld-linux.org> <20141130105655.GA17107@cukinia.lan> <20141130120455.GA2127@home.lan> <547B21FC.60408@pld-linux.org> <20141130141716.GA28287@cukinia.lan> <20141130205007.GA14561@cukinia.lan> Message-ID: <547B8609.7000701@pld-linux.org> On 30.11.2014 22:50, Jan Palus wrote: > On 30.11.2014 15:17, Jan Palus wrote: >> >Anyway thanks Jan, reproducer was shared with bintray's support and >> >let's see if they come up with a solution. > Few hours after my email they identified IRI support to be responsible for > above behaviour (on by default) and provided two workarounds: > > 1. Adding --no-iri to wget i would disable IRI (wtf is it anyway and why "on" by default) for next decade. definately do that in distfiles, interactive cli may stay broken to get more more bugreports. -- glen From baggins at pld-linux.org Sun Nov 30 22:10:24 2014 From: baggins at pld-linux.org (=?UTF-8?Q?Jan_R=C4=99korajski?=) Date: Sun, 30 Nov 2014 22:10:24 +0100 Subject: DISTFILES: groovy: ERRORS: groovy-binary-2.3.8.zip In-Reply-To: <547B8609.7000701@pld-linux.org> References: <14539.1417284117@distfiles.pld-linux.org> <20141130105655.GA17107@cukinia.lan> <20141130120455.GA2127@home.lan> <547B21FC.60408@pld-linux.org> <20141130141716.GA28287@cukinia.lan> <20141130205007.GA14561@cukinia.lan> <547B8609.7000701@pld-linux.org> Message-ID: On Sun, Nov 30, 2014 at 10:03 PM, Elan Ruusam?e wrote: > On 30.11.2014 22:50, Jan Palus wrote: >> >> On 30.11.2014 15:17, Jan Palus wrote: >>> >>> >Anyway thanks Jan, reproducer was shared with bintray's support and >>> >let's see if they come up with a solution. >> >> Few hours after my email they identified IRI support to be responsible for >> above behaviour (on by default) and provided two workarounds: >> >> 1. Adding --no-iri to wget > > i would disable IRI (wtf is it anyway and why "on" by default) for next > decade. > > definately do that in distfiles, interactive cli may stay broken to get more > more bugreports. Done in distfiles. -- Jan R?korajski | SysAdm | PLD/Linux | http://www.pld-linux.org/ bagginspld-linux.org From baggins at pld-linux.org Sun Nov 30 22:20:57 2014 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sun, 30 Nov 2014 22:20:57 +0100 Subject: Th 2014 snapshot Message-ID: <20141130212056.GB2127@home.lan> The current state of Th main/ready is going to become 2014 snapshot next weekend (6,7 Dec). If you know of any breakage or want a package updated, please report/fix/update it before end of the week. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/