From glen at delfi.ee Sun Jun 2 13:48:20 2019 From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 2 Jun 2019 14:48:20 +0300 Subject: git push: No space left on device In-Reply-To: <98921370-6bac-4810-7a70-686928bb88ef@maven.pl> References: <98921370-6bac-4810-7a70-686928bb88ef@maven.pl> Message-ID: <82b77f9f-5174-8673-058f-97cdda7b9f4a@delfi.ee> On 31/05/2019 12:28, Arkadiusz Mi?kiewicz wrote: > Deleted few things - now it's 1.4GB free. and already down by 700mb. something is continuing to eat space ``` root at 1822-cvs repositories/SPECS.git# df / Filesystem???? Type? Size? Used Avail Use% Mounted on /dev/sda3????? ext3?? 16G?? 14G? 687M? 96% / ``` imho /var, /var/log should be on separate partition: ``` root at 1822-cvs repositories/SPECS.git# df /var /var/log Filesystem???? Type? Size? Used Avail Use% Mounted on /dev/sda3????? ext3?? 16G?? 14G? 686M? 96% / /dev/sda3????? ext3?? 16G?? 14G? 686M? 96% / ``` From glen at delfi.ee Sun Jun 2 13:55:21 2019 From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 2 Jun 2019 14:55:21 +0300 Subject: git push: No space left on device In-Reply-To: <82b77f9f-5174-8673-058f-97cdda7b9f4a@delfi.ee> References: <98921370-6bac-4810-7a70-686928bb88ef@maven.pl> <82b77f9f-5174-8673-058f-97cdda7b9f4a@delfi.ee> Message-ID: nuked pldnotify tmp files: ``` root at 1822-cvs ~# df Filesystem????????? Type????? Size? Used Avail Use% Mounted on /dev/sda3?????????? ext3?????? 16G?? 14G? 686M? 96% / root at 1822-cvs /tmp# l total 1022M -rw------- 1 arekm cvsadm 8.2M Jun? 2 00:37 3sUCfg -rw------- 1 arekm cvsadm 8.2M May 22 11:37 3yngEZ ... -rw------- 1 arekm cvsadm? 42M May 27 14:03 LC09qj -rw------- 1 arekm cvsadm? 42M May 30 08:27 rTG3Ny -rw------- 1 arekm cvsadm? 42M Jun? 2 02:39 9fFusL root at 1822-cvs /tmp# ls 3sUCfg? 7aisYm? AOgDej? CjoYBs? egzPBi????? GVVgYV? IMdYCY ky6SZM? MJyqun? pkwwYX? rTG3Ny?????????? tkKQTz?????? TxCKfd vNKbVx? xgrXUW? ZmX3wX 3yngEZ? 9fFusL? bKLMXg? ckcKZR? EtVuKX????? H0wUjP? kqyavX LC09qj? nQaRqB? q72abZ? s8IY3M?????????? tmux-35000/? ugz5GH W64ejM? XQ6rPW? ZQNqbE 4VHvgg? ACfosT? BuCxRS? cRVWBO? fhOWil????? h6wHPL? KsfiDO lNOI6y? o07mvf? qhiWzM? ssh-QpoL8zO4Iw/? tNamQj?????? US5wV06C3e XCwOX6? yHKpFZ? zXfBXz 6ZGCBe? AgrapI? bUpvI4? DjRrgV? GtyfHwtvvV? HLv5DW? kuD1Hb lVWGWS? p2b6GH? QnZwka? sYw019?????????? TNWyoP?????? vbufmU XG2nxD? Z29c7L root at 1822-cvs /tmp# rm -vf ?????? removed '3sUCfg' removed '3yngEZ' removed '4VHvgg' ... root at 1822-cvs /tmp# df / Filesystem???? Type? Size? Used Avail Use% Mounted on /dev/sda3????? ext3?? 16G?? 13G? 1.7G? 89% / ``` On 02/06/2019 14:48, Elan Ruusam?e wrote: > > and already down by 700mb. something is continuing to eat space > > > ``` > root at 1822-cvs repositories/SPECS.git# df / > Filesystem???? Type? Size? Used Avail Use% Mounted on > /dev/sda3????? ext3?? 16G?? 14G? 687M? 96% / From baggins at pld-linux.org Sun Jun 2 22:13:34 2019 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sun, 2 Jun 2019 22:13:34 +0200 Subject: firefox and builders... Message-ID: <20190602201240.GA8181@tachikoma.lan> After long trial and error process I managed to get firefox to build, unfortunately our automation is overprotective and the build doesn't work on builders - I can run it manually on builders, but not in automatated way. Until someone finds out why nodejs doesn't start during firefox build process I'm going to remove the package from th. firefox-bin will remain. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at delfi.ee Sun Jun 2 22:22:46 2019 From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 2 Jun 2019 23:22:46 +0300 Subject: firefox and builders... In-Reply-To: <20190602201240.GA8181@tachikoma.lan> References: <20190602201240.GA8181@tachikoma.lan> Message-ID: <84b4d20a-9b6d-ceab-acad-19a3fac25792@delfi.ee> On 02/06/2019 23:13, Jan R?korajski wrote: > After long trial and error process I managed to get firefox to build, > unfortunately our automation is overprotective and the build doesn't > work on builders - I can run it manually on builders, but not in > automatated way. > > Until someone finds out why nodejs doesn't start during firefox build > process I'm going to remove the package from th. maybe update node to next lts (node 10): - https://github.com/nodejs/Release From baggins at pld-linux.org Mon Jun 3 07:25:31 2019 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Mon, 3 Jun 2019 07:25:31 +0200 Subject: firefox and builders... In-Reply-To: <84b4d20a-9b6d-ceab-acad-19a3fac25792@delfi.ee> References: <20190602201240.GA8181@tachikoma.lan> <84b4d20a-9b6d-ceab-acad-19a3fac25792@delfi.ee> Message-ID: <20190603052531.GA1845@starbug> On Sun, 02 Jun 2019, Elan Ruusam?e wrote: > On 02/06/2019 23:13, Jan R?korajski wrote: > > > After long trial and error process I managed to get firefox to build, > > unfortunately our automation is overprotective and the build doesn't > > work on builders - I can run it manually on builders, but not in > > automatated way. > > > > Until someone finds out why nodejs doesn't start during firefox build > > process I'm going to remove the package from th. > > maybe update node to next lts (node 10): > > - https://github.com/nodejs/Release > I don't believe it's nodejs problem, I think it's builder security/networking problem. I can build firefox at home, I can build it on builder if I log in there and run it by hand. But when I send a request this happens: 4:16.50 Executing "/usr/bin/nodejs /tmp/B.5vhgKn/BUILD/firefox-67.0/devtools/client/shared/build/build.js /tmp/B.5vhgKn/BUILD/firefox-67.0/devtools/client/debugger/new/src/main.development.js /tmp/B.5vhgKn/BUILD/firefox-67.0/devtools/client/debugger/new/src/main.js /tmp/B.5vhgKn/BUILD/firefox-67.0/devtools/client/debugger/new/src/vendors.js" 4:16.57 dns.js:221 4:16.57 this._handle = new ChannelWrap(); 4:16.57 ^ 4:16.57 Error: EFILE http://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=firefox&id=afcecd08-58e5-4b54-9bdc-4b4ed6574182&action=tail -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From jajcus at jajcus.net Mon Jun 3 08:19:42 2019 From: jajcus at jajcus.net (Jacek Konieczny) Date: Mon, 3 Jun 2019 08:19:42 +0200 Subject: firefox and builders... In-Reply-To: <20190603052531.GA1845@starbug> References: <20190602201240.GA8181@tachikoma.lan> <84b4d20a-9b6d-ceab-acad-19a3fac25792@delfi.ee> <20190603052531.GA1845@starbug> Message-ID: <99c42dfd-7d02-9d28-24bb-5be7ea57067a@jajcus.net> On 03/06/2019 07.25, Jan R?korajski wrote> > I don't believe it's nodejs problem, I think it's builder > security/networking problem. But the security/networking restrictions are there for a reason. If we allow build process to download anything it wants, then we could skip shipping source packages at all. Yes it sucks in today's world, especially when trying to build something like Node or Java crap. Proper source packages are harder and harder to find, even for C code (e.g. when code is available only on github and includes submodules)? Maybe we should rethink our policy?, but just removing the restrictions because one package stopped to build doesn't seem a right way to do it. Jacek From j.rekorajski at gmail.com Mon Jun 3 09:46:58 2019 From: j.rekorajski at gmail.com (=?UTF-8?Q?Jan_R=C4=99korajski?=) Date: Mon, 3 Jun 2019 09:46:58 +0200 Subject: firefox and builders... In-Reply-To: <99c42dfd-7d02-9d28-24bb-5be7ea57067a@jajcus.net> References: <20190602201240.GA8181@tachikoma.lan> <84b4d20a-9b6d-ceab-acad-19a3fac25792@delfi.ee> <20190603052531.GA1845@starbug> <99c42dfd-7d02-9d28-24bb-5be7ea57067a@jajcus.net> Message-ID: That nodejs in firefox is not downloading anything AFAIK, it's just convoluted build process that needs nodejs started and it cannot start without dns :/ I don't remember how we run builds, but maybe if we point resolv.conf at 127.0.0.1 it will be enough for it. On Mon, Jun 3, 2019 at 8:19 AM Jacek Konieczny wrote: > On 03/06/2019 07.25, Jan R?korajski wrote> > > I don't believe it's nodejs problem, I think it's builder > > security/networking problem. > But the security/networking restrictions are there for a reason. If we > allow build process to download anything it wants, then we could skip > shipping source packages at all. > > Yes it sucks in today's world, especially when trying to build something > like Node or Java crap. Proper source packages are harder and harder to > find, even for C code (e.g. when code is available only on github and > includes submodules)? > > Maybe we should rethink our policy?, but just removing the restrictions > because one package stopped to build doesn't seem a right way to do it. > > Jacek > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en > -- Jan R?korajski | SysAdm | PLD/Linux | http://www.pld-linux.org/ bagginspld-linux.org From mike at altlinux.org Mon Jun 3 12:55:55 2019 From: mike at altlinux.org (Michael Shigorin) Date: Mon, 3 Jun 2019 13:55:55 +0300 Subject: firefox and builders... In-Reply-To: <99c42dfd-7d02-9d28-24bb-5be7ea57067a@jajcus.net> References: <20190602201240.GA8181@tachikoma.lan> <84b4d20a-9b6d-ceab-acad-19a3fac25792@delfi.ee> <20190603052531.GA1845@starbug> <99c42dfd-7d02-9d28-24bb-5be7ea57067a@jajcus.net> Message-ID: <20190603105554.GD24019@imap.altlinux.org> On Mon, Jun 03, 2019 at 08:19:42AM +0200, Jacek Konieczny wrote: > On 03/06/2019 07.25, Jan R?korajski wrote> > > I don't believe it's nodejs problem, I think it's builder > > security/networking problem. > But the security/networking restrictions are there for a reason. If we > allow build process to download anything it wants, then we could skip > shipping source packages at all. It's about reproducibility as well. > Yes it sucks in today's world, especially when trying to build something > like Node or Java crap. Proper source packages are harder and harder to > find, even for C code (e.g. when code is available only on github and > includes submodules)? We tend to fix tags at least, submodules is a major hassle indeed... > Maybe we should rethink our policy?, but just removing the restrictions > because one package stopped to build doesn't seem a right way to do it. ALT is building its repos without network access, maybe some patches or approaches will be reuseful to you too. In particular, fx67 has just landed: https://packages.altlinux.org/en/sisyphus/srpms/firefox I'm not into nodejs but it's sort of there too: https://packages.altlinux.org/en/sisyphus/srpms/node https://packages.altlinux.org/en/search?query=nodejs -- ?---- WBR, Michael Shigorin / http://altlinux.org ??------ http://opennet.ru / http://anna-news.info From baggins at pld-linux.org Mon Jun 3 20:58:47 2019 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Mon, 3 Jun 2019 20:58:47 +0200 Subject: [packages/firefox] - bump libicu-devel to 63.1; builds fine with nodejs 10 even with no read access to resolv.conf In-Reply-To: <28dc894f0a27bdc080bbfc821d2841760a70927b_refs_heads_master@pld-linux.org> References: <89fa0d5a7a0026611c439451a1e69057b08ee904_refs_heads_master@pld-linux.org> <28dc894f0a27bdc080bbfc821d2841760a70927b_refs_heads_master@pld-linux.org> Message-ID: <20190603185846.GB1845@starbug> On Mon, 03 Jun 2019, arekm wrote: > commit 28dc894f0a27bdc080bbfc821d2841760a70927b > Author: Arkadiusz Mi?kiewicz > Date: Mon Jun 3 15:09:13 2019 +0200 > > - bump libicu-devel to 63.1; builds fine with nodejs 10 even with no read access to resolv.conf > > firefox.spec | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > --- > diff --git a/firefox.spec b/firefox.spec > index de14e08..c60c946 100644 > --- a/firefox.spec > +++ b/firefox.spec > @@ -293,7 +293,7 @@ BuildRequires: libatomic-devel > BuildRequires: libevent-devel >= 1.4.7 > # standalone libffi 3.0.9 or gcc's from 4.5(?)+ > BuildRequires: libffi-devel >= 6:3.0.9 > -%{?with_system_icu:BuildRequires: libicu-devel >= 59.1} > +%{?with_system_icu:BuildRequires: libicu-devel >= 63.1} > # requires libjpeg-turbo implementing at least libjpeg 6b API > BuildRequires: libjpeg-devel >= 6b > BuildRequires: libjpeg-turbo-devel > ================================================================ No, it does not: http://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=firefox&id=05da2df8-250e-48ea-b5a4-93a6dbdf387f&action=tail -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From arekm at maven.pl Mon Jun 3 21:22:25 2019 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Mon, 3 Jun 2019 21:22:25 +0200 Subject: [packages/firefox] - bump libicu-devel to 63.1; builds fine with nodejs 10 even with no read access to resolv.conf In-Reply-To: <20190603185846.GB1845@starbug> References: <89fa0d5a7a0026611c439451a1e69057b08ee904_refs_heads_master@pld-linux.org> <28dc894f0a27bdc080bbfc821d2841760a70927b_refs_heads_master@pld-linux.org> <20190603185846.GB1845@starbug> Message-ID: <756a313b-8231-f91c-6e5b-83138ec9aa18@maven.pl> On 03/06/2019 20:58, Jan R?korajski wrote: > On Mon, 03 Jun 2019, arekm wrote: > >> commit 28dc894f0a27bdc080bbfc821d2841760a70927b >> Author: Arkadiusz Mi?kiewicz >> Date: Mon Jun 3 15:09:13 2019 +0200 >> >> - bump libicu-devel to 63.1; builds fine with nodejs 10 even with no read access to resolv.conf >> >> firefox.spec | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> --- >> diff --git a/firefox.spec b/firefox.spec >> index de14e08..c60c946 100644 >> --- a/firefox.spec >> +++ b/firefox.spec >> @@ -293,7 +293,7 @@ BuildRequires: libatomic-devel >> BuildRequires: libevent-devel >= 1.4.7 >> # standalone libffi 3.0.9 or gcc's from 4.5(?)+ >> BuildRequires: libffi-devel >= 6:3.0.9 >> -%{?with_system_icu:BuildRequires: libicu-devel >= 59.1} >> +%{?with_system_icu:BuildRequires: libicu-devel >= 63.1} >> # requires libjpeg-turbo implementing at least libjpeg 6b API >> BuildRequires: libjpeg-devel >= 6b >> BuildRequires: libjpeg-turbo-devel >> ================================================================ > > No, it does not: > > http://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=firefox&id=05da2df8-250e-48ea-b5a4-93a6dbdf387f&action=tail > builders don't have nodejs 10, it's only in our git (and in .test-builds) -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at delfi.ee Wed Jun 19 20:22:28 2019 From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 19 Jun 2019 21:22:28 +0300 Subject: [packages/binutils] - updated info patch (its purpose is to align info directory, ie. default info/pinfo page) In-Reply-To: References: <46bb88534583af2e8c64293f88b7b4a90d8be9aa_refs_heads_master@pld-linux.org> Message-ID: On 19/06/2019 10:22, qboosh wrote: > commit f81d24890fc099cfa33b9951c6d77b0a6fb14c23 > Author: Jakub Bogusz > Date: Wed Jun 19 09:23:47 2019 +0200 > > - updated info patch > (its purpose is to align info directory, ie. default info/pinfo page) not that i care of this patch, but this explanation gives nothing: 1. why the patch is needed 2. why it's never submitted upstream From glen at delfi.ee Wed Jun 19 22:48:28 2019 From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 19 Jun 2019 23:48:28 +0300 Subject: carme-x86_64 readline broken? Message-ID: seems all operations that require some kind of interactivity are broken on carme. random examples: 1. coreutils prompts fail to prompt with bogus error closing file message 2. nvim segfaults 3. git interactive stage fails to prompt (returns to shell) ``` [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? rm -i /dev/null rm: remove character special file '/dev/null'? rm: error closing file [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? nvim Segmentation fault [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? git add -p diff --git a/php.spec b/php.spec index 2b4de4f..1b8f04d 100644 --- a/php.spec +++ b/php.spec @@ -164,7 +164,7 @@ Summary(ru.UTF-8):? PHP ?????? 7 - ???? ??????????????? ?Summary(uk.UTF-8):???? PHP ?????? 7 - ???? ??????????????? HTML-??????, ?????????? ?? ??????? ?Name:????????? %{orgname}%{php_suffix} ?Version:?????? 7.4.0 -Release:?????? 0.1 +Release:?????? 0.2 ?Epoch:???????? 4 ?# All files licensed under PHP version 3.01, except ?# Zend is licensed under Zend Stage this hunk [y,n,q,a,d,j,J,g,/,e,?]? [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? ``` From arekm at maven.pl Wed Jun 19 23:27:22 2019 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Wed, 19 Jun 2019 23:27:22 +0200 Subject: carme-x86_64 readline broken? In-Reply-To: References: Message-ID: <74889197-9327-1a1d-ad0a-9582df70fb3f@maven.pl> On 19/06/2019 22:48, Elan Ruusam?e wrote: > seems all operations that require some kind of interactivity are broken > on carme. > > > random examples: > > 1. coreutils prompts fail to prompt with bogus error closing file message carme has git version of readline-devel, so there can be mixed libraries linked (indirectly) with both readline versions. That could be the cause. > > 2. nvim segfaults > > 3. git interactive stage fails to prompt (returns to shell) > > > ``` > [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? rm -i /dev/null > rm: remove character special file '/dev/null'? rm: error closing file > [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? nvim > Segmentation fault > [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? > [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? git add -p > diff --git a/php.spec b/php.spec > index 2b4de4f..1b8f04d 100644 > --- a/php.spec > +++ b/php.spec > @@ -164,7 +164,7 @@ Summary(ru.UTF-8):? PHP ?????? 7 - ???? ??????????????? > ?Summary(uk.UTF-8):???? PHP ?????? 7 - ???? ??????????????? HTML-??????, > ?????????? ?? ??????? > ?Name:????????? %{orgname}%{php_suffix} > ?Version:?????? 7.4.0 > -Release:?????? 0.1 > +Release:?????? 0.2 > ?Epoch:???????? 4 > ?# All files licensed under PHP version 3.01, except > ?# Zend is licensed under Zend > Stage this hunk [y,n,q,a,d,j,J,g,/,e,?]? > [~/rpm/packages/php(7.4.0) (dev-7.4)??] ? > > ``` > > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From glen at delfi.ee Fri Jun 21 12:34:30 2019 From: glen at delfi.ee (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 21 Jun 2019 13:34:30 +0300 Subject: carme-x86_64 readline broken? In-Reply-To: <74889197-9327-1a1d-ad0a-9582df70fb3f@maven.pl> References: <74889197-9327-1a1d-ad0a-9582df70fb3f@maven.pl> Message-ID: On 20/06/2019 00:27, Arkadiusz Mi?kiewicz wrote: > On 19/06/2019 22:48, Elan Ruusam?e wrote: >> seems all operations that require some kind of interactivity are broken >> on carme. >> >> >> random examples: >> >> 1. coreutils prompts fail to prompt with bogus error closing file message > carme has git version of readline-devel, so there can be mixed libraries > linked (indirectly) with both readline versions. > > That could be the cause. > > ee, no? package installed year ago, and does not seem it's installed manually either ``` [~/rpm/packages/Firebird(3.0.4.33054) (master)??] ? pkgbytime readline Fri Jul 27 08:35:36 2018 readline-7.0.5-1.x86_64 Fri Jul 27 08:35:36 2018 readline-devel-7.0.5-1.x86_64 Fri Jul 27 08:35:36 2018 readline-static-7.0.5-1.x86_64 [~/rpm/packages/Firebird(3.0.4.33054) (master)??] ? rpm -V readline readline-devel [~/rpm/packages/Firebird(3.0.4.33054) (master)??] ? ``` could this be resolved please