From arekm at maven.pl  Fri Mar  9 20:53:22 2018
From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=)
Date: Fri, 9 Mar 2018 20:53:22 +0100
Subject: ns1 down, buildlogs up but dns entry is wrong
Message-ID: <201803092053.22181.arekm@maven.pl>


ns1 dns service is down and doesn't propagate dns zone changes made in svn 
which makes buildlogs.pld-linux.org not working (IP has changed).

Unfortunately I'm unable to contact adamg who rarely responds to sms/mail/fb 
(maybe some else has better access to him).

I guess the only solution for repeatable problems is to move nameservers and 
other resources to other machines... but no one has the access, so that's 
currently impossible to do, too.

Solutions?

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From baggins at pld-linux.org  Sat Mar 10 09:07:06 2018
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sat, 10 Mar 2018 09:07:06 +0100
Subject: ns1 down, buildlogs up but dns entry is wrong
In-Reply-To: <201803092053.22181.arekm@maven.pl>
References: <201803092053.22181.arekm@maven.pl>
Message-ID: <20180310080705.GD21082@starbug.lan>

On Fri, 09 Mar 2018, Arkadiusz Mi?kiewicz wrote:

> 
> ns1 dns service is down and doesn't propagate dns zone changes made in svn 
> which makes buildlogs.pld-linux.org not working (IP has changed).
> 
> Unfortunately I'm unable to contact adamg who rarely responds to sms/mail/fb 
> (maybe some else has better access to him).
> 
> I guess the only solution for repeatable problems is to move nameservers and 
> other resources to other machines... but no one has the access, so that's 
> currently impossible to do, too.

Do we know what other resources we would need to move? I'm sure about
lists, ns1, ns2, and I think it's also b.mx and team (forum, STBR, etc),
anything else?

> Solutions?

Moving just DNS shouldn't be a problem, I guess. This one is completely
automated.

OTOH moving the rest is quite hard without Adam's help, so no idea here.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From arekm at maven.pl  Sat Mar 10 12:43:38 2018
From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=)
Date: Sat, 10 Mar 2018 12:43:38 +0100
Subject: ns1 down, buildlogs up but dns entry is wrong
In-Reply-To: <20180310080705.GD21082@starbug.lan>
References: <201803092053.22181.arekm@maven.pl>
 <20180310080705.GD21082@starbug.lan>
Message-ID: <201803101243.38343.arekm@maven.pl>

On Saturday 10 of March 2018, Jan R?korajski wrote:
> On Fri, 09 Mar 2018, Arkadiusz Mi?kiewicz wrote:
> > ns1 dns service is down and doesn't propagate dns zone changes made in
> > svn which makes buildlogs.pld-linux.org not working (IP has changed).
> > 
> > Unfortunately I'm unable to contact adamg who rarely responds to
> > sms/mail/fb (maybe some else has better access to him).
> > 
> > I guess the only solution for repeatable problems is to move nameservers
> > and other resources to other machines... but no one has the access, so
> > that's currently impossible to do, too.
> 
> Do we know what other resources we would need to move? I'm sure about
> lists, ns1, ns2, and I think it's also b.mx and team (forum, STBR, etc),
> anything else?

These PLD related vserver guests were (and likely are on new machine) on 
akcyza:

dns
ftp
lists
mx
wwwpld

I was doing backup of these until adamg changed machines and access was lost 
(so no more backup of these on my side; that was in Feb 2017).

> 
> > Solutions?
> 
> Moving just DNS shouldn't be a problem, I guess. This one is completely
> automated.

I'll look at dns (can provide 3 dns servers in different networks and 
locations, too)

> 
> OTOH moving the rest is quite hard without Adam's help, so no idea here.


-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From atler at pld-linux.org  Sat Mar 10 15:04:17 2018
From: atler at pld-linux.org (Jan Palus)
Date: Sat, 10 Mar 2018 15:04:17 +0100
Subject: TEST build ERRORS: fontconfig.spec
In-Reply-To: <pld-builder.1520689728.657433.24176@ymir-builder>
References: <8f71e737-212f-407c-8379-f49726bd20d7@pld.src.builder>
 <pld-builder.1520689728.657433.24176@ymir-builder>
Message-ID: <20180310140417.2mtbywwtrbpetv5k@kalarepa>

On 10.03.2018 13:48, PLD th-x86_64 builder wrote:
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See test/test-suite.log

would someone with proper access be so kind to send me above file from any
builder?


From arekm at maven.pl  Sun Mar 11 09:58:19 2018
From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=)
Date: Sun, 11 Mar 2018 09:58:19 +0100
Subject: TEST build ERRORS: fontconfig.spec
In-Reply-To: <20180310140417.2mtbywwtrbpetv5k@kalarepa>
References: <8f71e737-212f-407c-8379-f49726bd20d7@pld.src.builder>
 <pld-builder.1520689728.657433.24176@ymir-builder>
 <20180310140417.2mtbywwtrbpetv5k@kalarepa>
Message-ID: <201803110958.20207.arekm@maven.pl>

On Saturday 10 of March 2018, Jan Palus wrote:
> On 10.03.2018 13:48, PLD th-x86_64 builder wrote:
> > # FAIL:  1
> > # XPASS: 0
> > # ERROR: 0
> > =========================================================================
> > === See test/test-suite.log
> 
> would someone with proper access be so kind to send me above file from any
> builder?

builder deletes these files automatically.

You need to modify spec file to cat test/test-suite.log on failure.

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From qboosh at pld-linux.org  Sun Mar 11 10:03:59 2018
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Sun, 11 Mar 2018 10:03:59 +0100
Subject: TEST build ERRORS: fontconfig.spec
In-Reply-To: <20180310140417.2mtbywwtrbpetv5k@kalarepa>
References: <8f71e737-212f-407c-8379-f49726bd20d7@pld.src.builder>
 <pld-builder.1520689728.657433.24176@ymir-builder>
 <20180310140417.2mtbywwtrbpetv5k@kalarepa>
Message-ID: <20180311090359.GA23807@mail>

On Sat, Mar 10, 2018 at 03:04:17PM +0100, Jan Palus wrote:
> On 10.03.2018 13:48, PLD th-x86_64 builder wrote:
> > # FAIL:  1
> > # XPASS: 0
> > # ERROR: 0
> > ============================================================================
> > See test/test-suite.log
> 
> would someone with proper access be so kind to send me above file from any
> builder?

rpm -q bubblewrap
Too old kernel or insufficient privileges?

Some test tries to run via bubblewrap, which uses some prctl available
since 3.5.


-- 
Jakub Bogusz    http://qboosh.pl/


From atler at pld-linux.org  Sun Mar 11 11:34:55 2018
From: atler at pld-linux.org (Jan Palus)
Date: Sun, 11 Mar 2018 11:34:55 +0100
Subject: TEST build ERRORS: fontconfig.spec
In-Reply-To: <20180311090359.GA23807@mail>
References: <8f71e737-212f-407c-8379-f49726bd20d7@pld.src.builder>
 <pld-builder.1520689728.657433.24176@ymir-builder>
 <20180310140417.2mtbywwtrbpetv5k@kalarepa>
 <20180311090359.GA23807@mail>
Message-ID: <1520764495.2342181.1298941296.3EBEEF62@webmail.messagingengine.com>

> 69f4b771-2f60-43f1-bcca-ece370059cce/tmp/B.af_pNM/BUILD/fontconfig-2.13.0/test/cache.dir/b9d99059-517f-4a54-9228-3fc60336fa91-le32d4.cache-7
> No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'.
> *** Test failed: Basic functionality with the bind-mounted cache dir
> file property doesn't points to the new place: /tmp/fontconfig.EiWDNCv2/fonts/4x6.pcf

To be honest I don't really follow, can someone advise whether this is expected behavior on builders?


From arekm at maven.pl  Sun Mar 11 12:14:49 2018
From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=)
Date: Sun, 11 Mar 2018 12:14:49 +0100
Subject: [packages/fontconfig] temporarily enable showing
 test/test-suite.log on test failure
In-Reply-To: <daca2f49b2979db9aa0aa164cb879fc559d29035_refs_heads_master@pld-linux.org>
References: <224401c717892f5027aeb6f59e99a52caeb49814_refs_heads_master@pld-linux.org>
 <daca2f49b2979db9aa0aa164cb879fc559d29035_refs_heads_master@pld-linux.org>
Message-ID: <201803111214.49571.arekm@maven.pl>

On Sunday 11 of March 2018, atler wrote:
> commit daca2f49b2979db9aa0aa164cb879fc559d29035
> Author: Jan Palus <atler at pld-linux.org>
> Date:   Sun Mar 11 11:26:13 2018 +0100
> 
>     temporarily enable showing test/test-suite.log on test failure
> 
>  fontconfig.spec | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> ---
> diff --git a/fontconfig.spec b/fontconfig.spec
> index 8e3b181..2affe47 100644
> --- a/fontconfig.spec
> +++ b/fontconfig.spec
> @@ -149,7 +149,7 @@ export HASDOCBOOK=no
>  	--%{?with_static_libs:en}%{!?with_static_libs:dis}able-static
>  %{__make}
> 
> -%{?with_tests:%{__make} check}
> +%{?with_tests:%{__make} check || cat test/test-suite.log}

It's ok to leave it as permanent but it needs to fail finally in such case 
(above won't fail)

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From jajcus at jajcus.net  Wed Mar 14 09:26:52 2018
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Wed, 14 Mar 2018 09:26:52 +0100
Subject: openssl manual pages broken?
Message-ID: <1752e166-2f96-555a-12bd-bff971a1512a@jajcus.net>


[jajcus at jajo ~]$ man openssl-pkcs12
man: /usr/share/man/man1/openssl-pkcs12.1 is self referencing
No manual entry for openssl-pkcs12
[jajcus at jajo ~]$ cat /usr/share/man/man1/openssl-pkcs12.1
.so man1/openssl-pkcs12.1

And the same for most openssl-* pages.

Jacek


From qboosh at pld-linux.org  Tue Mar 20 18:39:57 2018
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Tue, 20 Mar 2018 18:39:57 +0100
Subject: openssl manual pages broken?
In-Reply-To: <1752e166-2f96-555a-12bd-bff971a1512a@jajcus.net>
References: <1752e166-2f96-555a-12bd-bff971a1512a@jajcus.net>
Message-ID: <20180320173957.GA15221@mail>

On Wed, Mar 14, 2018 at 09:26:52AM +0100, Jacek Konieczny wrote:
> 
> [jajcus at jajo ~]$ man openssl-pkcs12
> man: /usr/share/man/man1/openssl-pkcs12.1 is self referencing
> No manual entry for openssl-pkcs12
> [jajcus at jajo ~]$ cat /usr/share/man/man1/openssl-pkcs12.1
> .so man1/openssl-pkcs12.1
> 
> And the same for most openssl-* pages.

rpm -q openssl?
There was a bug in 1.0.2n-1, for me it seems fixed in 1.0.2n-2.


-- 
Jakub Bogusz    http://qboosh.pl/


From gotar at polanet.pl  Fri Mar 23 19:35:37 2018
From: gotar at polanet.pl (Tomasz Pala)
Date: Fri, 23 Mar 2018 19:35:37 +0100
Subject: docker: various utils not found in $PATH
Message-ID: <20180323183537.GA31080@polanet.pl>

msg="devmapper: Error while creating filesystem ext4 on device docker-9:2-1199725-base: exec: \"mkfs.ext4\": executable file not found in $PATH"
msg="[graphdriver] prior storage driver devicemapper failed: exec: \"mkfs.ext4\": executable file not found in $PATH"
exec: "mkfs.ext4": executable file not found in $PATH
exec: "tune2fs": executable file not found in $PATH
error: exec: \"modprobe\": executable file not found in $PATH"

These start to work when linked into /usr/*bin.



Actually I have similar problem with some older systemd:
systemd-fsck[4620]: fsck.ext4 doesn't exist, not checking file system on /dev/md4
- basically, the splitted /usr is being depreciated all over the place
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/

-- 
Tomasz Pala <gotar at pld-linux.org>


From baggins at pld-linux.org  Sun Mar 25 10:23:08 2018
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sun, 25 Mar 2018 10:23:08 +0200
Subject: Packages to be dropped from th
Message-ID: <20180325082308.GA2580@starbug.lan>

I'm removing the following packages from th. Feel free to fix them, but
for the time being they are too old, too broken and/or unsupported upstream.

california
gnome-code-assistance
hhvm
Yap


-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From gotar at polanet.pl  Mon Mar 26 03:52:27 2018
From: gotar at polanet.pl (Tomasz Pala)
Date: Mon, 26 Mar 2018 03:52:27 +0200
Subject: docker: various utils not found in $PATH
In-Reply-To: <3f11a259-743f-b66d-ee2b-94a8e1c39b9b@delfi.ee>
References: <20180323183537.GA31080@polanet.pl>
 <3f11a259-743f-b66d-ee2b-94a8e1c39b9b@delfi.ee>
Message-ID: <20180326015227.GA3655@polanet.pl>

On Sun, Mar 25, 2018 at 23:28:58 +0300, Elan Ruusam?e wrote:

>> msg="devmapper: Error while creating filesystem ext4 on device docker-9:2-1199725-base: exec: \"mkfs.ext4\": executable file not found in $PATH"
>> msg="[graphdriver] prior storage driver devicemapper failed: exec: \"mkfs.ext4\": executable file not found in $PATH"
>> exec: "mkfs.ext4": executable file not found in $PATH
>> exec: "tune2fs": executable file not found in $PATH
>> error: exec: \"modprobe\": executable file not found in $PATH"
> docker version? are your running under systemd?

Current: docker-ce-17.12.0-1.x86_64, under older systemd-232-7.

> what is the $PATH of dockerd environ?
> 
> # cat /proc/`pidof dockerd`/environ|tr '\0' '\n'|grep PATH
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin

-- 
Tomasz Pala <gotar at pld-linux.org>


From blues at pld-linux.org  Mon Mar 26 15:41:41 2018
From: blues at pld-linux.org (=?ISO-8859-2?Q?Pawe=B3_Go=B3aszewski?=)
Date: Mon, 26 Mar 2018 15:41:41 +0200 (CEST)
Subject: Packages to be dropped from th
In-Reply-To: <20180325082308.GA2580@starbug.lan>
References: <20180325082308.GA2580@starbug.lan>
Message-ID: <alpine.DEB.2.20.1803261540380.2763@fgnss.gnfx.tqn.cy>

On Sun, 25 Mar 2018, Jan R?korajski wrote:
> I'm removing the following packages from th. Feel free to fix them, but
> for the time being they are too old, too broken and/or unsupported upstream.
>
> california

abandonware, to be removed.

gnome-calendar can be set as "obsoletes" and even "provides".


-- 
pozdr.  Pawe? Go?aszewski          p.golaszewski<at>gda<dot>pl
--------------------------------------------------------------------------

From glen at delfi.ee  Sat Mar 31 14:12:53 2018
From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=)
Date: Sat, 31 Mar 2018 15:12:53 +0300
Subject: docker: various utils not found in $PATH
In-Reply-To: <20180326015227.GA3655@polanet.pl>
References: <20180323183537.GA31080@polanet.pl>
 <3f11a259-743f-b66d-ee2b-94a8e1c39b9b@delfi.ee>
 <20180326015227.GA3655@polanet.pl>
Message-ID: <991a35dc-725e-11e9-1f4c-41d392e4bc7d@delfi.ee>

On 26/03/2018 04:52, Tomasz Pala wrote:

> On Sun, Mar 25, 2018 at 23:28:58 +0300, Elan Ruusam?e wrote:
>
>>> msg="devmapper: Error while creating filesystem ext4 on device docker-9:2-1199725-base: exec: \"mkfs.ext4\": executable file not found in $PATH"
>>> msg="[graphdriver] prior storage driver devicemapper failed: exec: \"mkfs.ext4\": executable file not found in $PATH"
>>> exec: "mkfs.ext4": executable file not found in $PATH
>>> exec: "tune2fs": executable file not found in $PATH
>>> error: exec: \"modprobe\": executable file not found in $PATH"
>> docker version? are your running under systemd?
> Current: docker-ce-17.12.0-1.x86_64, under older systemd-232-7.
>
>> what is the $PATH of dockerd environ?
>>
>> # cat /proc/`pidof dockerd`/environ|tr '\0' '\n'|grep PATH
>> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
>
so, the intermediate fix is to figure out why the PATH of yours is 
without /sbin and /boin