From glen at pld-linux.org Mon Feb 1 10:35:45 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Mon, 1 Feb 2021 11:35:45 +0200 Subject: [packages/ca-certificates] don't mark ca-certificates.crt as %config(noreplace) In-Reply-To: <7bc3bef894722f37879324960a96540fc9945a14_refs_heads_master@pld-linux.org> References: <63b09917a97a706619caad739f87b65022752558_refs_heads_master@pld-linux.org> <7bc3bef894722f37879324960a96540fc9945a14_refs_heads_master@pld-linux.org> Message-ID: <66dedb7d-3e28-c4c7-ef67-f72c19450c36@pld-linux.org> On 30.01.2021 13:30, atler wrote: > commit 7bc3bef894722f37879324960a96540fc9945a14 > Author: Jan Palus > Date: Sat Jan 30 12:24:52 2021 +0100 > > don't mark ca-certificates.crt as %config(noreplace) > > ...or it may never get updated after single installation of > ca-certificates-update. Let's assume anyone with custom certificates has > ca-certificates-update which will update ca-certificates.crt after > upgrade > > ca-certificates.spec | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > --- > diff --git a/ca-certificates.spec b/ca-certificates.spec > index 7da43aa..b500452 100644 > --- a/ca-certificates.spec > +++ b/ca-certificates.spec > @@ -214,7 +214,7 @@ rm -rf $RPM_BUILD_ROOT > %dir /etc/ssl/certs > /etc/ssl/certs/ca-certificates.crt > %config(noreplace) %verify(not md5 mtime size) /etc/pki/tls/certs/ca-bundle.crt > -%config(noreplace) %verify(not md5 mtime size) %{certsdir}/ca-certificates.crt > +%verify(not md5 mtime size) %{certsdir}/ca-certificates.crt > i propose to use %config so it would at least keep backup as .rpmold From glen at pld-linux.org Mon Feb 1 10:43:30 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Mon, 1 Feb 2021 11:43:30 +0200 Subject: [PLDWWW] page changed: packages:rpm In-Reply-To: References: Message-ID: <6049673e-69d4-0afe-67f6-1dd1fa53a68c@pld-linux.org> On 30.01.2021 18:19, "Jan R?korajski (baggins)" wrote: > + > + ===== Spec development ===== > + > + * rpm.org rpm generates ''rpmlib(ShortCircuited)'' dependencies when package is build using ''--short-circuit'' option. To disable that add ''disable_short_circuited_deps 0'' to ~/.rpmrc shouldn't that be `%disable_short_circuited_deps 0` and to `~/.rpmmacros` or that's another thing being changed/deprecated/restored? From atler at pld-linux.org Tue Feb 2 14:11:48 2021 From: atler at pld-linux.org (Jan Palus) Date: Tue, 2 Feb 2021 14:11:48 +0100 Subject: git default branch Message-ID: <20210202130459.ou4vyutyxqzmvmhh@pine> Could someone please silent this hint? FWIW "master" is still perfectly fine as far as I'm concerned. $ git pld init alacritty hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m Initialized empty Git repository in /cvs/root/gitolite/repositories/packages/alacritty.git/ From arekm at maven.pl Tue Feb 2 14:30:42 2021 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Tue, 2 Feb 2021 14:30:42 +0100 Subject: git default branch In-Reply-To: <20210202130459.ou4vyutyxqzmvmhh@pine> References: <20210202130459.ou4vyutyxqzmvmhh@pine> Message-ID: W dniu 02.02.2021 o?14:11, Jan Palus pisze: > Could someone please silent this hint? FWIW "master" is still perfectly > fine as far as I'm concerned. > > $ git pld init alacritty > hint: Using 'master' as the name for the initial branch. This default branch name > hint: is subject to change. To configure the initial branch name to use in all > hint: of your new repositories, which will suppress this warning, call: > hint: > hint: git config --global init.defaultBranch > hint: > hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and > hint: 'development'. The just-created branch can be renamed via this command: > hint: > hint: git branch -m > Initialized empty Git repository in /cvs/root/gitolite/repositories/packages/alacritty.git/ git config --global init.defaultBranch master doesn't make it silent aka is this from local or remote git? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From atler at pld-linux.org Tue Feb 2 14:39:22 2021 From: atler at pld-linux.org (Jan Palus) Date: Tue, 2 Feb 2021 14:39:22 +0100 Subject: git default branch In-Reply-To: References: <20210202130459.ou4vyutyxqzmvmhh@pine> Message-ID: <20210202133922.fwmykonr7hkdg5su@pine> On 02.02.2021 14:30, Arkadiusz Mi?kiewicz wrote: > W dniu 02.02.2021 o?14:11, Jan Palus pisze: > > Could someone please silent this hint? FWIW "master" is still perfectly > > fine as far as I'm concerned. > > > > $ git pld init alacritty > > hint: Using 'master' as the name for the initial branch. This default branch name > > hint: is subject to change. To configure the initial branch name to use in all > > hint: of your new repositories, which will suppress this warning, call: > > hint: > > hint: git config --global init.defaultBranch > > hint: > > hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and > > hint: 'development'. The just-created branch can be renamed via this command: > > hint: > > hint: git branch -m > > Initialized empty Git repository in /cvs/root/gitolite/repositories/packages/alacritty.git/ > > git config --global init.defaultBranch master > > doesn't make it silent aka is this from local or remote git? remote I believe, especially judging by last line. defaultBranch was already set in my local config. From zawadaa at gmail.com Tue Feb 2 20:45:37 2021 From: zawadaa at gmail.com (Andrzej Zawadzki) Date: Tue, 2 Feb 2021 20:45:37 +0100 Subject: sudo after upgrade Message-ID: Hi, I've just upgrade to newest test and after restart I'm not at wheel group anymore.... id zawada uid=1000(zawada) gid=1000(users) grupy=1000(users) but: cat /etc/group|grep zawada wheel::10:root,zawada Bug or feature? -- Andrzej Zawadzki From glen at pld-linux.org Wed Feb 3 13:49:15 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 3 Feb 2021 14:49:15 +0200 Subject: git default branch In-Reply-To: References: <20210202130459.ou4vyutyxqzmvmhh@pine> Message-ID: On 02.02.2021 15:30, Arkadiusz Mi?kiewicz wrote: > W dniu 02.02.2021 o?14:11, Jan Palus pisze: >> Could someone please silent this hint? FWIW "master" is still perfectly >> fine as far as I'm concerned. >> >> $ git pld init alacritty >> hint: Using 'master' as the name for the initial branch. This default branch name >> hint: is subject to change. To configure the initial branch name to use in all >> hint: of your new repositories, which will suppress this warning, call: >> hint: >> hint: git config --global init.defaultBranch >> hint: >> hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and >> hint: 'development'. The just-created branch can be renamed via this command: >> hint: >> hint: git branch -m >> Initialized empty Git repository in /cvs/root/gitolite/repositories/packages/alacritty.git/ > git config --global init.defaultBranch master > > doesn't make it silent aka is this from local or remote git? > this needs to be executed under git user in git.pld-linux.org as the message comes from cvs server From arekm at maven.pl Wed Feb 3 14:22:49 2021 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Wed, 3 Feb 2021 14:22:49 +0100 Subject: git default branch In-Reply-To: References: <20210202130459.ou4vyutyxqzmvmhh@pine> Message-ID: <7a8b230d-275c-c893-f97b-524d2e363599@maven.pl> W dniu 03.02.2021 o?13:49, Elan Ruusam?e pisze: > On 02.02.2021 15:30, Arkadiusz Mi?kiewicz wrote: > >> W dniu 02.02.2021 o?14:11, Jan Palus pisze: >>> Could someone please silent this hint? FWIW "master" is still perfectly >>> fine as far as I'm concerned. >>> >>> $ git pld init alacritty >>> hint: Using 'master' as the name for the initial branch. This default >>> branch name >>> hint: is subject to change. To configure the initial branch name to >>> use in all >>> hint: of your new repositories, which will suppress this warning, call: >>> hint: >>> hint:???? git config --global init.defaultBranch >>> hint: >>> hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and >>> hint: 'development'. The just-created branch can be renamed via this >>> command: >>> hint: >>> hint:???? git branch -m >>> Initialized empty Git repository in >>> /cvs/root/gitolite/repositories/packages/alacritty.git/ >> git config --global init.defaultBranch master >> >> doesn't make it silent aka is this from local or remote git? >> > this needs to be executed under git user in git.pld-linux.org as the > message comes from cvs server It is changed already. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From krzysztof at mrozowicz.eu Sat Feb 6 04:07:28 2021 From: krzysztof at mrozowicz.eu (Krzysztof Mrozowicz) Date: Sat, 6 Feb 2021 03:07:28 +0000 Subject: audacious-plugins 4.1 Message-ID: <01020177754f02cf-c096b119-e3fb-48a5-b87a-b39960011539-000000@eu-west-1.amazonses.com> Hi! I just updated audacious and audacious-plugins to version 4.1, but as I'm not a programmer, despite my efforts, I have no idea how to fix audacious-plugins-verbose_make.patch. Can anybody help me with this, please? Once fixed, it has to be uncommented in %prep section in the spec file. -- Krzysiek From glen at pld-linux.org Sat Feb 6 19:22:38 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 6 Feb 2021 20:22:38 +0200 Subject: [PLDWWW] page changed: packages:rpm In-Reply-To: References: Message-ID: <20b71178-560c-77b0-e02d-0dadfcb3bdf0@pld-linux.org> On 06.02.2021 11:13, "Jan R?korajski (baggins)" wrote: > + * rpm.org rpm generates ''rpmlib(ShortCircuited)'' dependencies when package is build using ''--short-circuit'' option. To disable that add ''%disable_short_circuited_deps 0'' to ~/.rpmrc what's the difference of ~/.rpmrc and ~/.rpmmacros? i thought ~/.rpmrc was deprecated by jbj, but now it's back due rpm.org code? and .rpmrc used different synta From ngompa13 at gmail.com Sat Feb 6 19:27:44 2021 From: ngompa13 at gmail.com (Neal Gompa) Date: Sat, 6 Feb 2021 13:27:44 -0500 Subject: [PLDWWW] page changed: packages:rpm In-Reply-To: <20b71178-560c-77b0-e02d-0dadfcb3bdf0@pld-linux.org> References: <20b71178-560c-77b0-e02d-0dadfcb3bdf0@pld-linux.org> Message-ID: On Sat, Feb 6, 2021 at 1:23 PM Elan Ruusam?e wrote: > > > On 06.02.2021 11:13, "Jan R?korajski (baggins)" wrote: > > + * rpm.org rpm generates ''rpmlib(ShortCircuited)'' dependencies when package is build using ''--short-circuit'' option. To disable that add ''%disable_short_circuited_deps 0'' to ~/.rpmrc > > > what's the difference of ~/.rpmrc and ~/.rpmmacros? i thought ~/.rpmrc > was deprecated by jbj, but now it's back due rpm.org code? and .rpmrc > used different synta You put it in ~/.rpmmacros, not ~/.rpmrc. The latter is only for managing compiler flags and arch maps. -- ?????????/ Always, there's only one truth! From glen at pld-linux.org Sun Feb 7 09:18:49 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 7 Feb 2021 10:18:49 +0200 Subject: [PLDWWW] page changed: packages:rpm In-Reply-To: References: <20b71178-560c-77b0-e02d-0dadfcb3bdf0@pld-linux.org> Message-ID: On 06.02.2021 20:27, Neal Gompa wrote: > On Sat, Feb 6, 2021 at 1:23 PM Elan Ruusam?e wrote: >> >> On 06.02.2021 11:13, "Jan R?korajski (baggins)" wrote: >>> + * rpm.org rpm generates ''rpmlib(ShortCircuited)'' dependencies when package is build using ''--short-circuit'' option. To disable that add ''%disable_short_circuited_deps 0'' to ~/.rpmrc >> >> what's the difference of ~/.rpmrc and ~/.rpmmacros? i thought ~/.rpmrc >> was deprecated by jbj, but now it's back due rpm.org code? and .rpmrc >> used different synta > You put it in ~/.rpmmacros, not ~/.rpmrc. The latter is only for > managing compiler flags and arch maps. > that's what i asked in previous email: - http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2021-February/026127.html but @baggins changed only macro part. From baggins at pld-linux.org Mon Feb 8 00:16:30 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Mon, 8 Feb 2021 00:16:30 +0100 Subject: sudo after upgrade In-Reply-To: References: Message-ID: <20210207231630.GA1869@starbug> On Tue, 02 Feb 2021, Andrzej Zawadzki wrote: > Hi, > > I've just upgrade to newest test and after restart I'm not at wheel > group anymore.... > > id zawada > uid=1000(zawada) gid=1000(users) grupy=1000(users) > > but: > > cat /etc/group|grep zawada > wheel::10:root,zawada > > Bug or feature? Sorry, SOA#1 uid=2896(baggins) gid=1000(users) groups=1000(users),4(adm),6(disk),10(wheel),11(icmp),16(dialout),23(audio),78(usb),221(vbox) $ rpm -q glibc glibc-2.33-2.x86_64 And everything else up to date wrt th-test. Maybe you have a space at the end of line somewhere? -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From atler at pld-linux.org Mon Feb 8 14:46:39 2021 From: atler at pld-linux.org (Jan Palus) Date: Mon, 8 Feb 2021 14:46:39 +0100 Subject: sudo after upgrade In-Reply-To: References: Message-ID: <20210208134639.obdjz3pb7iciq2fo@kalarepa> On 02.02.2021 20:45, Andrzej Zawadzki wrote: > Hi, > > I've just upgrade to newest test and after restart I'm not at wheel > group anymore.... > > id zawada > uid=1000(zawada) gid=1000(users) grupy=1000(users) > > but: > > cat /etc/group|grep zawada > wheel::10:root,zawada > > Bug or feature? Encountered it on one machine as well... You have outdated /etc/nsswitch.conf most likely with entry that breaks group membership completely: initgroups: [SUCCESS=continue] files From atler at pld-linux.org Mon Feb 8 15:16:27 2021 From: atler at pld-linux.org (Jan Palus) Date: Mon, 8 Feb 2021 15:16:27 +0100 Subject: sudo after upgrade In-Reply-To: <20210208134639.obdjz3pb7iciq2fo@kalarepa> References: <20210208134639.obdjz3pb7iciq2fo@kalarepa> Message-ID: <20210208141627.e6dufdp2pf3dvwkn@kalarepa> On 08.02.2021 14:46, Jan Palus wrote: > On 02.02.2021 20:45, Andrzej Zawadzki wrote: > > Hi, > > > > I've just upgrade to newest test and after restart I'm not at wheel > > group anymore.... > > > > id zawada > > uid=1000(zawada) gid=1000(users) grupy=1000(users) > > > > but: > > > > cat /etc/group|grep zawada > > wheel::10:root,zawada > > > > Bug or feature? > > Encountered it on one machine as well... You have outdated > /etc/nsswitch.conf most likely with entry that breaks group membership > completely: > > initgroups: [SUCCESS=continue] files There supposed to be "db" before [SUCCESS=continue] but it was stripped by us glibc.spec: sed -e 's#\([ \t]\)db\([ \t]\)#\1#g' nss/nsswitch.conf > $RPM_BUILD_ROOT%{_sysconfdir}/nsswitch.conf hence if I understand it correctly: if db succeeded skip files, otherwise do files. Apparently glibc 2.33 changed semantics of such broken entry and files are not processed at all resulting in heavily crippled system (but hey, root works fine ;) ). Note that above sed is no longer necessary since at least glibc 2.31 which dropped "db" in default config: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=4b7c74179c8928d971d370e1137d202f891a4cf5;hp=a289ea09ea843ced6e5277c2f2e63c357bc7f9a3 From arekm at maven.pl Tue Feb 9 22:53:27 2021 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Tue, 9 Feb 2021 22:53:27 +0100 Subject: PLD New Rescue Th-20210209 Message-ID: Hello. If anyone is interested: PLD New Rescue x86_64 image based on Th main (as of 20210209): https://github.com/arekm/pld-new-rescue/releases/tag/th-current-20210209 -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From arekm at maven.pl Wed Feb 10 15:30:58 2021 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Wed, 10 Feb 2021 15:30:58 +0100 Subject: PLD New Rescue Th-20210209 In-Reply-To: References: Message-ID: <320cdf45-d0f3-eec8-d6c0-b5db47c16f68@maven.pl> W dniu 09.02.2021 o?22:53, Arkadiusz Mi?kiewicz pisze: > Hello. > > If anyone is interested: > > PLD New Rescue x86_64 image based on Th main (as of 20210209): > > https://github.com/arekm/pld-new-rescue/releases/tag/th-current-20210209 > Added 32bit/i686 images. -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From atler at pld-linux.org Fri Feb 12 01:21:10 2021 From: atler at pld-linux.org (Jan Palus) Date: Fri, 12 Feb 2021 01:21:10 +0100 Subject: [packages/rpm-pld-macros/rpm.org] - add conversion from PLD rich noauto deps to poor rpm.org implementation In-Reply-To: <260cc2eb0ed6d678e77ffc27c124fd5c06dfced4_refs_heads_rpm.org@pld-linux.org> References: <260cc2eb0ed6d678e77ffc27c124fd5c06dfced4_refs_heads_rpm.org@pld-linux.org> Message-ID: <20210212002110.527xsmibgyiwzu75@kalarepa> On 31.01.2021 20:52, baggins wrote: > commit 260cc2eb0ed6d678e77ffc27c124fd5c06dfced4 > Author: Jan R?korajski > Date: Sun Jan 31 20:50:47 2021 +0100 > > - add conversion from PLD rich noauto deps to poor rpm.org implementation This commit causes serious regression -- autoreqs and autoprovs are completely gone. > +%__noautodep_helper() %(awk -v x="%*" 'BEGIN { > + RS = "\n([ \t]+\n)+"; > + FS = " "; > + split(x, F); > + printf("("); > + for (i=1; i<=length(F); i++) { > + s = F[i]; > + sub(/#.*/, "z&z", s); > + if (s ~ /^$/) { continue; }; > + printf(s); > + if (i != length(F)) { printf("|"); }; > + }; > + printf(")"); > +}') Looks like it's because of pattern being '()' on empty input hence matching everything. I suppose whole block starting with first printf should be guarded by condition length(F) > 0. From atler at pld-linux.org Fri Feb 12 01:32:59 2021 From: atler at pld-linux.org (Jan Palus) Date: Fri, 12 Feb 2021 01:32:59 +0100 Subject: [packages/poldek] - add cpuinfo() deps support for rpm.org - disable directory dependencies for rpm.org, unsupported b In-Reply-To: <7f01416d06a257ce15e0ea468e836d4fdcd891ca_refs_heads_master@pld-linux.org> References: <43ec59dd0ef605c4dd3800bfe30d03d1cd183573_refs_heads_master@pld-linux.org> <7f01416d06a257ce15e0ea468e836d4fdcd891ca_refs_heads_master@pld-linux.org> Message-ID: <20210212003259.z22vgbkq2floxvo7@kalarepa> On 15.11.2020 10:33, baggins wrote: > commit 7f01416d06a257ce15e0ea468e836d4fdcd891ca > Author: Jan R?korajski > Date: Sun Nov 15 10:32:40 2020 +0100 > > - add cpuinfo() deps support for rpm.org > - disable directory dependencies for rpm.org, unsupported by rpm > > poldek.spec | 2 ++ > rpm4-cpuinfo-deps.patch | 12 ++++++++++++ > rpm4-no-dir-deps.patch | 21 +++++++++++++++++++++ I don't really follow what rpm4-no-dir-deps.patch does but poldek still complained about missing build-id directories. What actually worked for me was changing poldek.conf: auto directory dependencies = no From glen at pld-linux.org Fri Feb 12 13:49:52 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 12 Feb 2021 14:49:52 +0200 Subject: [packages/rpm-pld-macros/rpm.org] - add conversion from PLD rich noauto deps to poor rpm.org implementation In-Reply-To: <20210212002110.527xsmibgyiwzu75@kalarepa> References: <260cc2eb0ed6d678e77ffc27c124fd5c06dfced4_refs_heads_rpm.org@pld-linux.org> <20210212002110.527xsmibgyiwzu75@kalarepa> Message-ID: On 12.02.2021 02:21, Jan Palus wrote: > +%__noautodep_helper() %(awk -v x="%*" 'BEGIN { the helper could be perhaps written in lua. maybe it's more readable then. to make things even more fancy, maybe the helper could even be placed into separate file, then .lua extension would have proper syntax in editor. From kruk.jaroslaw at gmail.com Fri Feb 12 21:13:39 2021 From: kruk.jaroslaw at gmail.com (Jaroslaw Kruk) Date: Fri, 12 Feb 2021 21:13:39 +0100 Subject: sudo after upgrade In-Reply-To: References: Message-ID: I have the same :-( wt., 2 lut 2021 o 20:46 Andrzej Zawadzki napisa?(a): > Hi, > > I've just upgrade to newest test and after restart I'm not at wheel > group anymore.... > > id zawada > uid=1000(zawada) gid=1000(users) grupy=1000(users) > > but: > > cat /etc/group|grep zawada > wheel::10:root,zawada > > Bug or feature? > > -- > > Andrzej Zawadzki > _______________________________________________ > pld-devel-en mailing list > pld-devel-en at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en > -- Jaros?aw Kruk : jareq at pld-linux.org kruk.jaroslaw at gmail.com GPG key Id : 0x78730F33 GPG FingerPrint : FD00 0082 DFBD 65AE 2FD9 A13F B879 7FB0 7873 0F33 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x78730F33 From baggins at pld-linux.org Sun Feb 14 21:29:12 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sun, 14 Feb 2021 21:29:12 +0100 Subject: Packages to be removed from Th Message-ID: <20210214202912.GD1869@starbug> The following packages will be removed from Th soon, if no one steps up to fixing them. All these packages are old and broken wrt current compilers and deps. ekiga h323plus neovim psiconv Special mention goes to php*-pecl-imagick I seem to be unable to rebuild it, the magical scripts don't do anything. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From krzysztof at mrozowicz.eu Tue Feb 16 10:20:38 2021 From: krzysztof at mrozowicz.eu (Krzysztof Mrozowicz) Date: Tue, 16 Feb 2021 09:20:38 +0000 Subject: systemd-init upgade problem Message-ID: <01020177aa24416c-f888dd86-79eb-47c8-8989-436018559e5a-000000@eu-west-1.amazonses.com> Hi everyone, I have the th-ready repo enabled and just run upgrade on my laptop. All went OK except systemd-init. It gave me the following error: poldek:/all-avail> upgrade systemd-init-246.10-1.x86_64 Processing dependencies... systemd-init-246.6-1.x86_64 obsoleted by systemd-init-246.10-1.x86_64 ? orphaned rc-scripts-0.4.19-2.x86_64 marks SysVinit-2.98-1.x86_64 (cap virtual(init-daemon)) ?? SysVinit-2.98-1.x86_64 marks mingetty-1.08-2.x86_64 (cap mingetty) error: systemd-init-246.10-1.x86_64 conflicts with SysVinit-2.98-1.x86_64 There are 3 packages to install (2 marked by dependencies), 1 to remove: U systemd-init-(246.6 => 246.10)-1.x86_64 A SysVinit-2.98-1.x86_64? mingetty-1.08-2.x86_64 This operation will use 296.0KB of disk space. Need to get 220.6KB of archives (220.6KB to download). Any suggestions? -- Krzysiek From atler at pld-linux.org Tue Feb 16 10:32:53 2021 From: atler at pld-linux.org (Jan Palus) Date: Tue, 16 Feb 2021 10:32:53 +0100 Subject: systemd-init upgade problem In-Reply-To: <01020177aa24416c-f888dd86-79eb-47c8-8989-436018559e5a-000000@eu-west-1.amazonses.com> References: <01020177aa24416c-f888dd86-79eb-47c8-8989-436018559e5a-000000@eu-west-1.amazonses.com> Message-ID: <20210216093253.d22uwkrftbzuqfxv@kalarepa> On 16.02.2021 09:20, Krzysztof Mrozowicz wrote: > Hi everyone, > I have the th-ready repo enabled and just run upgrade on my laptop. All went > OK except systemd-init. > It gave me the following error: > > poldek:/all-avail> upgrade systemd-init-246.10-1.x86_64 > Processing dependencies... > systemd-init-246.6-1.x86_64 obsoleted by systemd-init-246.10-1.x86_64 > ? orphaned rc-scripts-0.4.19-2.x86_64 marks SysVinit-2.98-1.x86_64 (cap > virtual(init-daemon)) > ?? SysVinit-2.98-1.x86_64 marks mingetty-1.08-2.x86_64 (cap mingetty) > error: systemd-init-246.10-1.x86_64 conflicts with SysVinit-2.98-1.x86_64 > There are 3 packages to install (2 marked by dependencies), 1 to remove: > U systemd-init-(246.6 => 246.10)-1.x86_64 > A SysVinit-2.98-1.x86_64? mingetty-1.08-2.x86_64 > This operation will use 296.0KB of disk space. > Need to get 220.6KB of archives (220.6KB to download). > > Any suggestions? Try again with rc-scripts-0.4.19-3 from th-test. From ed at yen.ipipan.waw.pl Tue Feb 16 10:33:53 2021 From: ed at yen.ipipan.waw.pl (Peri Noid) Date: Tue, 16 Feb 2021 10:33:53 +0100 Subject: systemd-init upgade problem In-Reply-To: <01020177aa24416c-f888dd86-79eb-47c8-8989-436018559e5a-000000@eu-west-1.amazonses.com> References: <01020177aa24416c-f888dd86-79eb-47c8-8989-436018559e5a-000000@eu-west-1.amazonses.com> Message-ID: <5830038.G0OjidicZr@laptok> Dnia wtorek, 16 lutego 2021 10:20:38 CET Krzysztof Mrozowicz pisze: > Hi everyone, > I have the th-ready repo enabled and just run upgrade on my laptop. All > went OK except systemd-init. > It gave me the following error: > > poldek:/all-avail> upgrade systemd-init-246.10-1.x86_64 > Processing dependencies... > systemd-init-246.6-1.x86_64 obsoleted by systemd-init-246.10-1.x86_64 > orphaned rc-scripts-0.4.19-2.x86_64 marks SysVinit-2.98-1.x86_64 (cap > virtual(init-daemon)) > SysVinit-2.98-1.x86_64 marks mingetty-1.08-2.x86_64 (cap mingetty) > error: systemd-init-246.10-1.x86_64 conflicts with SysVinit-2.98-1.x86_64 > There are 3 packages to install (2 marked by dependencies), 1 to remove: > U systemd-init-(246.6 => 246.10)-1.x86_64 > A SysVinit-2.98-1.x86_64 mingetty-1.08-2.x86_64 > This operation will use 296.0KB of disk space. > Need to get 220.6KB of archives (220.6KB to download). > > Any suggestions? The reason is, the name of a dependency has changed: poldek:/all-avail> desc -p systemd-init-246.6-1.x86_64 systemd- init-246.10-1.x86_64 Package: systemd-init-246.10-1.x86_64 Provides: virtual-init-daemon Package: systemd-init-246.6-1.x86_64 Provides: readahead = 1:1.5.7-3, virtual(init-daemon) I used --nodeps --nofollow for this package. -- ?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 krzysztof at mrozowicz.eu Tue Feb 16 10:53:08 2021 From: krzysztof at mrozowicz.eu (Krzysztof Mrozowicz) Date: Tue, 16 Feb 2021 09:53:08 +0000 Subject: systemd-init upgade problem In-Reply-To: <20210216093253.d22uwkrftbzuqfxv@kalarepa> References: <01020177aa24416c-f888dd86-79eb-47c8-8989-436018559e5a-000000@eu-west-1.amazonses.com> <20210216093253.d22uwkrftbzuqfxv@kalarepa> Message-ID: <01020177aa420258-96975320-92df-490f-9aaf-21ceb9cc68f4-000000@eu-west-1.amazonses.com> W dniu 16.02.2021 o?09:32, Jan Palus pisze: > On 16.02.2021 09:20, Krzysztof Mrozowicz wrote: >> Hi everyone, >> I have the th-ready repo enabled and just run upgrade on my laptop. All went >> OK except systemd-init. >> >> >> Any suggestions? > Try again with rc-scripts-0.4.19-3 from th-test. Perfect! That fixed the problem. The updated version of rc-scripts should be moved to th-ready ASAP so others didn't have similar problems. -- Krzysiek From glen at pld-linux.org Wed Feb 17 15:40:08 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 17 Feb 2021 16:40:08 +0200 Subject: pam 1.5 Message-ID: https://github.com/linux-pam/linux-pam/releases/tag/v1.5.0 * Removed deprecated pam_cracklib module, use pam_passwdqc (from passwdqc project) or pam_pwquality (from libpwquality project) instead. * Removed deprecated pam_tally and pam_tally2 modules, use pam_faillock instead. what's our action? 1. follow the flow and remove them as well? 2. alternatively could copy them from 1.4.0 tarball, so at least we don't lag behind because afraid to update to 1.5.x if someone really needs those removed modules, a separate .spec is more appropriate solution to the problem. From glen at pld-linux.org Thu Feb 18 13:47:33 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Thu, 18 Feb 2021 14:47:33 +0200 Subject: pam 1.5 In-Reply-To: References: Message-ID: <5544c8fb-ff91-3527-0807-94bde26db693@pld-linux.org> On 17.02.2021 16:40, Elan Ruusam?e wrote: > > https://github.com/linux-pam/linux-pam/releases/tag/v1.5.0 > > > * Removed deprecated pam_cracklib module, use pam_passwdqc (from > passwdqc project) > or pam_pwquality (from libpwquality project) instead. > * Removed deprecated pam_tally and pam_tally2 modules, use > pam_faillock instead. > > > what's our action? > > 1. follow the flow and remove them as well? > > 2. alternatively could copy them from 1.4.0 tarball, so at least we > don't lag behind because afraid to update to 1.5.x > > > if someone really needs those removed modules, a separate .spec is > more appropriate solution to the problem. > there's also pam-pld-1.1.2-1.tar.gz included in pam.spec, there's no info how that file was generated. could put the two new abandoned modules there as well. altho i feel better to just create new tarball with tally and cracklib From zawadaa at gmail.com Thu Feb 18 22:16:25 2021 From: zawadaa at gmail.com (Andrzej Zawadzki) Date: Thu, 18 Feb 2021 22:16:25 +0100 Subject: sudo after upgrade In-Reply-To: <20210208134639.obdjz3pb7iciq2fo@kalarepa> References: <20210208134639.obdjz3pb7iciq2fo@kalarepa> Message-ID: <6e8e8889-ebbb-0fe5-4675-0a1a395393f2@gmail.com> On 08.02.2021 14:46, Jan Palus wrote: On 02.02.2021 20:45, Andrzej Zawadzki wrote: Hi, I've just upgrade to newest test and after restart I'm not at wheel group anymore.... id zawada uid=1000(zawada) gid=1000(users) grupy=1000(users) but: cat /etc/group|grep zawada wheel::10:root,zawada Bug or feature? Encountered it on one machine as well... You have outdated /etc/nsswitch.conf most likely with entry that breaks group membership completely: initgroups: [SUCCESS=continue] files Yep! Exactly! Thanks for help! I changed this file one day - I added: hosts: files resolve ... because: resolve Use systemd resolved resolver (dns subsystem runs much smoother when networks are changing) and now, after upgrade I got new nsswitch.conf but with "rpmnew" suffix. Wrong, old initgroups still was there. ps. sometimes debs are better. ;-) -- Andrzej Zawadzki From glen at pld-linux.org Fri Feb 19 08:23:42 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 19 Feb 2021 09:23:42 +0200 Subject: rpm 4.16: bind Message-ID: looks like this is major breakage in packaging. you can not package symlinks with absolute paths to inaccessible paths anymore? so, absolute symlinks not permitted, must use relative symlinks when packaging? bind.spec @ ed2fd6d (master) ``` RPM build errors: ??? line 130: It's not recommended to have unversioned Obsoletes: Obsoletes:??? caching-nameserver ??? Explicit %attr() mode not applicable to symlink: /home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/etc/named.conf ??? Explicit %attr() mode not applicable to symlink: /home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/etc/bind.keys ??? Explicit %attr() mode not applicable to symlink: /home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/usr/sbin/named-compilezone ??? Explicit %attr() mode not applicable to symlink: /home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/usr/sbin/tsig-keygen ??? Explicit %attr() mode not applicable to symlink: /home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/var/log/named ??? Explicit %attr() mode not applicable to symlink: /home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/var/log/named.stats ??? absolute symlink: /etc/bind.keys -> /var/lib/named/etc/bind.keys ??? absolute symlink: /etc/named.conf -> /var/lib/named/etc/named.conf ??? absolute symlink: /var/log/named -> /var/lib/named/named.log ??? absolute symlink: /var/log/named.stats -> /var/lib/named/named.stats ??? Recognition of file "/home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/etc/bind.keys" failed: mode 120777 broken symbolic link to /var/lib/named/etc/bind.keys (Permission denied) ??? Recognition of file "/home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/etc/named.conf" failed: mode 120777 broken symbolic link to /var/lib/named/etc/named.conf (Permission denied) ??? Recognition of file "/home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/var/log/named" failed: mode 120777 broken symbolic link to /var/lib/named/named.log (Permission denied) ??? Recognition of file "/home/users/glen/tmp/bind-9.16.12-x86_64-root-glen/var/log/named.stats" failed: mode 120777 broken symbolic link to /var/lib/named/named.stats (Permission denied) ``` From glen at pld-linux.org Fri Feb 19 08:30:16 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 19 Feb 2021 09:30:16 +0200 Subject: [packages/bind] - up to 9.16.12; fixes CVE-2020-8625; new way of soname versioning In-Reply-To: References: Message-ID: On 18.02.2021 20:33, arekm wrote: > commit ed2fd6d7570a08eb64041b761353c5d35db5cc02 > Author: Arkadiusz Mi?kiewicz > Date: Thu Feb 18 19:33:19 2021 +0100 > > - up to 9.16.12; fixes CVE-2020-8625; new way of soname versioning > > rm -rf _doc > cp -a doc _doc > @@ -642,20 +639,13 @@ fi > > %files libs > %defattr(644,root,root,755) > -%attr(755,root,root) %{_libdir}/libbind9.so.*.*.* > -%attr(755,root,root) %ghost %{_libdir}/libbind9.so.1600 > -%attr(755,root,root) %{_libdir}/libdns.so.*.*.* > -%attr(755,root,root) %ghost %{_libdir}/libdns.so.1611 > -%attr(755,root,root) %{_libdir}/libirs.so.*.*.* > -%attr(755,root,root) %ghost %{_libdir}/libirs.so.1601 > -%attr(755,root,root) %{_libdir}/libisc.so.*.*.* > -%attr(755,root,root) %ghost %{_libdir}/libisc.so.1609 > -%attr(755,root,root) %{_libdir}/libisccc.so.*.*.* > -%attr(755,root,root) %ghost %{_libdir}/libisccc.so.1600 > -%attr(755,root,root) %{_libdir}/libisccfg.so.*.*.* > -%attr(755,root,root) %ghost %{_libdir}/libisccfg.so.1603 > -%attr(755,root,root) %{_libdir}/libns.so.*.*.* > -%attr(755,root,root) %ghost %{_libdir}/libns.so.1607 > +%attr(755,root,root) %ghost %{_libdir}/libbind9-%{version}.so > +%attr(755,root,root) %ghost %{_libdir}/libdns-%{version}.so > +%attr(755,root,root) %ghost %{_libdir}/libirs-%{version}.so > +%attr(755,root,root) %ghost %{_libdir}/libisc-%{version}.so > +%attr(755,root,root) %ghost %{_libdir}/libisccc-%{version}.so > +%attr(755,root,root) %ghost %{_libdir}/libisccfg-%{version}.so > +%attr(755,root,root) %ghost %{_libdir}/libns-%{version}.so did you actually test this built rpm? seems to me, you have packaged the actual libraries as %ghost. From arekm at maven.pl Fri Feb 19 08:57:04 2021 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Fri, 19 Feb 2021 08:57:04 +0100 Subject: [packages/bind] - up to 9.16.12; fixes CVE-2020-8625; new way of soname versioning In-Reply-To: References: Message-ID: <9fad7273-dfff-0930-c7f5-b64c4ce15a11@maven.pl> W dniu 19.02.2021 o?08:30, Elan Ruusam?e pisze: > > On 18.02.2021 20:33, arekm wrote: >> commit ed2fd6d7570a08eb64041b761353c5d35db5cc02 >> Author: Arkadiusz Mi?kiewicz >> Date:?? Thu Feb 18 19:33:19 2021 +0100 >> >> ???? - up to 9.16.12; fixes CVE-2020-8625; new way of soname versioning > > build only -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From baggins at pld-linux.org Fri Feb 19 09:22:19 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Fri, 19 Feb 2021 09:22:19 +0100 Subject: rpm 4.16: bind In-Reply-To: References: Message-ID: <20210219082219.GE1869@starbug> On Fri, 19 Feb 2021, Elan Ruusam?e wrote: > looks like this is major breakage in packaging. > > you can not package symlinks with absolute paths to inaccessible paths > anymore? > > so, absolute symlinks not permitted, must use relative symlinks when > packaging? Should be fixed with http://git.pld-linux.org/gitweb.cgi?p=packages/rpm.git;a=commitdiff;h=d42a01a648b725059ec32c6c369af2563f0fcb28 -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From baggins at pld-linux.org Mon Feb 22 19:59:15 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Mon, 22 Feb 2021 19:59:15 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th Message-ID: <20210222185915.GF1869@starbug> rpm 4.16.1.2 and all dependant packages are now available in th-test. More details about the update can be found on https://www.pld-linux.org/packages/rpm Th builders has been upgraded and all builds will now use rpm.org rpm. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Tue Feb 23 09:28:51 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 23 Feb 2021 10:28:51 +0200 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210222185915.GF1869@starbug> References: <20210222185915.GF1869@starbug> Message-ID: On 22.02.2021 20:59, Jan R?korajski wrote: > rpm 4.16.1.2 and all dependant packages are now available in th-test. hey. great work! From glen at pld-linux.org Tue Feb 23 10:22:58 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 23 Feb 2021 11:22:58 +0200 Subject: [packages/telepathy-qt4] - updated to 0.9.8 - switched off bcond qt4. I'm afraid qt4 version is not compilable In-Reply-To: <7b494749b266da984436556e9f9facf42fc71c73_refs_heads_master@pld-linux.org> References: <7b494749b266da984436556e9f9facf42fc71c73_refs_heads_master@pld-linux.org> Message-ID: <60605015-65a6-faa9-782c-a46d034dc524@pld-linux.org> On 20.02.2021 15:35, witekfl wrote: > commit 7b494749b266da984436556e9f9facf42fc71c73 > Author: Witold Filipczyk > Date: Sat Feb 20 14:33:33 2021 +0100 > > - updated to 0.9.8 > - switched off bcond qt4. I'm afraid qt4 version is not compilable > > telepathy-qt4.spec | 12 ++++++------ > 1 file changed, 6 insertions(+), 6 deletions(-) > --- > diff --git a/telepathy-qt4.spec b/telepathy-qt4.spec > index 121928c..e3488a2 100644 > --- a/telepathy-qt4.spec > +++ b/telepathy-qt4.spec > @@ -1,6 +1,6 @@ > # > # Conditional build: > -%bcond_without qt4 # Qt4 interface > +%bcond_with qt4 # Qt4 interface > %bcond_without qt5 # Qt5 interface perhaps time to revise package naming. this is somewhat silly now. From glen at pld-linux.org Tue Feb 23 11:36:49 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 23 Feb 2021 12:36:49 +0200 Subject: [packages/rpm-build-tools] LANG=C is not enough to disable translations, add LC_ALL=C everywhere In-Reply-To: References: <857fd9dfaa14e06cdac6beea3abd578b2f297ac5_refs_heads_master@pld-linux.org> Message-ID: On 23.02.2021 11:55, baggins wrote: > commit ae0dd942e0b1f73604de4bb1a2adea3dccaf8b8b > Author: Jan R?korajski > Date: Tue Feb 23 10:54:50 2021 +0100 > > LANG=C is not enough to disable translations, add LC_ALL=C everywhere > > builder.sh | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > --- > diff --git a/builder.sh b/builder.sh > index e0f1da3..f94b0a3 100755 > --- a/builder.sh > +++ b/builder.sh > @@ -479,7 +479,7 @@ Usage: builder [--all-branches] [-D|--debug] [-V|--version] [--short-version] [ > is_rpmorg() { > local v > > - v=$(LANG=C rpm --version 2>&1) > + v=$(LC_ALL=C LANG=C rpm --version 2>&1) to my knowledge you need only LC_ALL=C, so the LANG=C is now superfluous. From ngompa13 at gmail.com Tue Feb 23 13:39:19 2021 From: ngompa13 at gmail.com (Neal Gompa) Date: Tue, 23 Feb 2021 07:39:19 -0500 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210222185915.GF1869@starbug> References: <20210222185915.GF1869@starbug> Message-ID: On Mon, Feb 22, 2021 at 2:00 PM Jan R?korajski wrote: > > rpm 4.16.1.2 and all dependant packages are now available in th-test. > > More details about the update can be found on > > https://www.pld-linux.org/packages/rpm > > Th builders has been upgraded and all builds will now use rpm.org rpm. > Congratulations on making that happen! I'm pleased to see that the transition has gone quite smoothly. :) -- ?????????/ Always, there's only one truth! From gotar at polanet.pl Tue Feb 23 15:35:20 2021 From: gotar at polanet.pl (Tomasz Pala) Date: Tue, 23 Feb 2021 15:35:20 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210222185915.GF1869@starbug> References: <20210222185915.GF1869@starbug> Message-ID: <20210223143519.GA28703@polanet.pl> On Mon, Feb 22, 2021 at 19:59:15 +0100, Jan R?korajski wrote: > rpm 4.16.1.2 and all dependant packages are now available in th-test. > > More details about the update can be found on > > https://www.pld-linux.org/packages/rpm Since --repackage is gone, some nice warning for people that might have relied on this feature would be welcome. And some rpmrebuild update maybe:) -- Tomasz Pala From baggins at pld-linux.org Tue Feb 23 16:48:52 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Tue, 23 Feb 2021 16:48:52 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210223143519.GA28703@polanet.pl> References: <20210222185915.GF1869@starbug> <20210223143519.GA28703@polanet.pl> Message-ID: <20210223154852.GG1869@starbug> On Tue, 23 Feb 2021, Tomasz Pala wrote: > On Mon, Feb 22, 2021 at 19:59:15 +0100, Jan R?korajski wrote: > > > rpm 4.16.1.2 and all dependant packages are now available in th-test. > > > > More details about the update can be found on > > > > https://www.pld-linux.org/packages/rpm > > Since --repackage is gone, some nice warning for people that might have relied > on this feature would be welcome. And some rpmrebuild update maybe:) Added a big fat warning about repackage on the wiki page. What do you mean by rpmrebuild? -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Tue Feb 23 23:08:07 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Wed, 24 Feb 2021 00:08:07 +0200 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210223154852.GG1869@starbug> References: <20210222185915.GF1869@starbug> <20210223143519.GA28703@polanet.pl> <20210223154852.GG1869@starbug> Message-ID: On 23.02.2021 17:48, Jan R?korajski wrote: > On Tue, 23 Feb 2021, Tomasz Pala wrote: > >> On Mon, Feb 22, 2021 at 19:59:15 +0100, Jan R?korajski wrote: >> >>> rpm 4.16.1.2 and all dependant packages are now available in th-test. >>> >>> More details about the update can be found on >>> >>> https://www.pld-linux.org/packages/rpm >> Since --repackage is gone, some nice warning for people that might have relied >> on this feature would be welcome. And some rpmrebuild update maybe:) > Added a big fat warning about repackage on the wiki page. > > What do you mean by rpmrebuild? it's a package: - https://github.com/pld-linux/rpmrebuild apparently not present in pld-th, otherwise you would have noticed it. From gotar at polanet.pl Wed Feb 24 02:41:16 2021 From: gotar at polanet.pl (Tomasz Pala) Date: Wed, 24 Feb 2021 02:41:16 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210223154852.GG1869@starbug> References: <20210222185915.GF1869@starbug> <20210223143519.GA28703@polanet.pl> <20210223154852.GG1869@starbug> Message-ID: <20210224014116.GA23094@polanet.pl> On Tue, Feb 23, 2021 at 16:48:52 +0100, Jan R?korajski wrote: >> Since --repackage is gone, some nice warning for people that might have relied >> on this feature would be welcome. And some rpmrebuild update maybe:) > > Added a big fat warning about repackage on the wiki page. Thanks. > What do you mean by rpmrebuild? git.pld-linux.org/packages/rpmrebuild - the project seems to be actively maintained, last release 2.16-1 at 2021-01-17: http://rpmrebuild.sourceforge.net/changelog.html and apparently this is the preferred ("official") way to replace --repackage. There is one drawback (it's not hooked to --erase operation). And maybe some some rpm-behaviour related: http://rpmrebuild.sourceforge.net/faq.html#use1 And a few more advantages: - can create rpm file without actual --erase (note the rpm --repackage --test --erase something in rpm5 created _empty_ something.rpm), - can keep spec file (-s), It needs some polishing, like verifying bash requirement, moving to /usr/libexec maybe (paths hardcoded), path sanitization: MY_LIB_DIR=$( dirname "$0" ) || ( echo "ERROR rpmrebuild.sh dirname $0"; exit 1) RPMREBUILD_TMPDIR=${RPMREBUILD_TMPDIR:-~/.tmp/rpmrebuild.$$} and general review (well, never trust shell script doing rm -rf "$Dir"): eval $change_arch $BUILDCMD --define "'buildroot $BUILDROOT'" $rpm_defines -bb $rpm_verbose $additional ${FIC_SPEC} What worries me most is that some obvious script errors (like using not quoted $Dir, this is more that purely bad programming practice) was fixed recently (2021-01-03). It doesn't even seem to be locale-safe. Basically this is a pile of workaround hacks that might crash in more ways one can imagine, but with a bit of trust to the sanity of installed packages (we don't expect any hacky filenames with newlines or some special characters) it might do it's job. -- Tomasz Pala From arekm at maven.pl Wed Feb 24 08:48:54 2021 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Wed, 24 Feb 2021 08:48:54 +0100 Subject: PLD New Rescue Th-20210209 In-Reply-To: <320cdf45-d0f3-eec8-d6c0-b5db47c16f68@maven.pl> References: <320cdf45-d0f3-eec8-d6c0-b5db47c16f68@maven.pl> Message-ID: <3f12d95e-72af-1423-532c-13dbb28c73f8@maven.pl> W dniu 10.02.2021 o?15:30, Arkadiusz Mi?kiewicz pisze: > W dniu 09.02.2021 o?22:53, Arkadiusz Mi?kiewicz pisze: >> Hello. >> >> If anyone is interested: >> >> PLD New Rescue x86_64 image based on Th main (as of 20210209): >> >> https://github.com/arekm/pld-new-rescue/releases/tag/th-current-20210209 >> > > Added 32bit/i686 images. > And reuploaded to new place https://github.com/pld-linux-org/pld-new-rescue/releases/tag/th-current-20210209 -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From baggins at pld-linux.org Wed Feb 24 23:00:11 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Wed, 24 Feb 2021 23:00:11 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210224014116.GA23094@polanet.pl> References: <20210222185915.GF1869@starbug> <20210223143519.GA28703@polanet.pl> <20210223154852.GG1869@starbug> <20210224014116.GA23094@polanet.pl> Message-ID: <20210224215748.GA21858@tachikoma> On Wed, 24 Feb 2021, Tomasz Pala wrote: > On Tue, Feb 23, 2021 at 16:48:52 +0100, Jan R?korajski wrote: > > >> Since --repackage is gone, some nice warning for people that might have relied > >> on this feature would be welcome. And some rpmrebuild update maybe:) > > > > Added a big fat warning about repackage on the wiki page. > > Thanks. > > > What do you mean by rpmrebuild? > > git.pld-linux.org/packages/rpmrebuild Thanks. Updated to the latest version and sent to th-test. Feel free to update wiki page, I have o clue how to use this, I have always found repackage rather useless. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From arekm at maven.pl Thu Feb 25 08:15:12 2021 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Thu, 25 Feb 2021 08:15:12 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210222185915.GF1869@starbug> References: <20210222185915.GF1869@starbug> Message-ID: W dniu 22.02.2021 o?19:59, Jan R?korajski pisze: > rpm 4.16.1.2 and all dependant packages are now available in th-test. > > More details about the update can be found on > > https://www.pld-linux.org/packages/rpm > > Th builders has been upgraded and all builds will now use rpm.org rpm. > There is rpm-build-tools/rediff-patches.py which can help rediffing patches if needed rediff-patches.py somespec.spec rediff-patches.py -p 1,2,3 somespec.spec - will rediff 1 2 and 3 only rediff-patches.py -s 0 kernel.spec - will rediff all but skipping patch 0 -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From atler at pld-linux.org Thu Feb 25 18:40:23 2021 From: atler at pld-linux.org (Jan Palus) Date: Thu, 25 Feb 2021 18:40:23 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210222185915.GF1869@starbug> References: <20210222185915.GF1869@starbug> Message-ID: <20210225174023.jpwngue45nrlkj5z@kalarepa> On 22.02.2021 19:59, Jan R?korajski wrote: > rpm 4.16.1.2 and all dependant packages are now available in th-test. > > More details about the update can be found on > > https://www.pld-linux.org/packages/rpm > > Th builders has been upgraded and all builds will now use rpm.org rpm. Looks like /usr/lib/rpm/fileattrs/kernel.attr still refers to kmod-deps.sh which is no longer part of rpm. Not sure whether script should be brought back or rather its use should be dropped. From baggins at pld-linux.org Thu Feb 25 23:53:56 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Thu, 25 Feb 2021 23:53:56 +0100 Subject: rpm 4.16.1.2 from rpm.org has landed in Th In-Reply-To: <20210225174023.jpwngue45nrlkj5z@kalarepa> References: <20210222185915.GF1869@starbug> <20210225174023.jpwngue45nrlkj5z@kalarepa> Message-ID: <20210225225356.GH1869@starbug> On Thu, 25 Feb 2021, Jan Palus wrote: > On 22.02.2021 19:59, Jan R?korajski wrote: > > rpm 4.16.1.2 and all dependant packages are now available in th-test. > > > > More details about the update can be found on > > > > https://www.pld-linux.org/packages/rpm > > > > Th builders has been upgraded and all builds will now use rpm.org rpm. > > Looks like /usr/lib/rpm/fileattrs/kernel.attr still refers to > kmod-deps.sh which is no longer part of rpm. Not sure whether script > should be brought back or rather its use should be dropped. Fixed. That was in rpm, I added the script to rpm-pld-macros. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From qboosh at pld-linux.org Fri Feb 26 18:54:44 2021 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Fri, 26 Feb 2021 18:54:44 +0100 Subject: rpm.org python dependency generator Message-ID: <20210226175444.GA919@mail> What about python provides change (python3egg vs python3dist, probably similarly for python2)? While python3 packaged will be rebuilt anyway due to python 3.9, there is no need to rebuild python2 packages (other than provides scheme change). -- Jakub Bogusz http://qboosh.pl/ From baggins at pld-linux.org Fri Feb 26 19:47:55 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Fri, 26 Feb 2021 19:47:55 +0100 Subject: rpm.org python dependency generator In-Reply-To: <20210226175444.GA919@mail> References: <20210226175444.GA919@mail> Message-ID: <20210226184755.GI1869@starbug> On Fri, 26 Feb 2021, Jakub Bogusz wrote: > What about python provides change (python3egg vs python3dist, probably > similarly for python2)? > > While python3 packaged will be rebuilt anyway due to python 3.9, there > is no need to rebuild python2 packages (other than provides scheme > change). I'm inclined to switch. We don't use those deps in *Requires, and since we already have to rebuild ~1000 packages for python3 upgrade, we can as well rebuild everything. A side effect will be rpm.org ecosystem compatible dependencies. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From baggins at pld-linux.org Fri Feb 26 20:30:49 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Fri, 26 Feb 2021 20:30:49 +0100 Subject: rpm.org python dependency generator In-Reply-To: <20210226184755.GI1869@starbug> References: <20210226175444.GA919@mail> <20210226184755.GI1869@starbug> Message-ID: <20210226193049.GA2813347@tachikoma.lan> On Fri, 26 Feb 2021, Jan R?korajski wrote: > On Fri, 26 Feb 2021, Jakub Bogusz wrote: > > > What about python provides change (python3egg vs python3dist, probably > > similarly for python2)? > > > > While python3 packaged will be rebuilt anyway due to python 3.9, there > > is no need to rebuild python2 packages (other than provides scheme > > change). > > I'm inclined to switch. We don't use those deps in *Requires, and since > we already have to rebuild ~1000 packages for python3 upgrade, we can as > well rebuild everything. A side effect will be rpm.org ecosystem > compatible dependencies. One more thing, rpm5 had directory dependencies, while rpm.org does not, so those versioned pythonX.Ydist() deps are the way forward to figure out that we need a version related update. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From baggins at pld-linux.org Fri Feb 26 23:54:50 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Fri, 26 Feb 2021 23:54:50 +0100 Subject: noarch subpackages Message-ID: <20210226225450.GJ1869@starbug> $ testmvpkg ready PLD * ERR: kernel-4.4-4.4.258-1 moving would remove archs: th-noarch ERR: kernel-4.19-4.19.177-1 moving would remove archs: th-noarch ERR: kernel-4.14-4.14.222-1 moving would remove archs: th-noarch ERR: kernel-4.9-4.9.258-1 moving would remove archs: th-noarch ERR: kernel-5.4-5.4.100-1 moving would remove archs: th-noarch I've just had enough of the "if BLARGH BuildArch: noarch" BS. We have had an rpm that supports it for almost 10 years (maybe more, I can't remember if 4.4.9 didn't support it really). I am removing *all* contitionals on noarch subpackages and consecutively will drop %noarchpackage from rpm macros. Time to move on with the times, if anyone wants to support antiquated rpm version, please do it on a branch. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Sat Feb 27 20:58:22 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 27 Feb 2021 21:58:22 +0200 Subject: noarch subpackages In-Reply-To: <20210226225450.GJ1869@starbug> References: <20210226225450.GJ1869@starbug> Message-ID: <1f9b2280-41dd-03c7-c58b-69c997422d99@pld-linux.org> On 27.02.2021 00:54, Jan R?korajski wrote: > I am removing *all* contitionals on noarch subpackages and consecutively > will drop %noarchpackage from rpm macros. how about adapter.awk patch to do that? :) From glen at pld-linux.org Sat Feb 27 21:17:27 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 27 Feb 2021 22:17:27 +0200 Subject: [packages/rpm-build-tools] Use rpm-specdump if it exists, rpm.org rpm can't do 'rpm dump %prep' In-Reply-To: References: <1cae170bdc241db73745a05f48a94b3c6164c689_refs_heads_master@pld-linux.org> Message-ID: <7d47a275-1369-f81a-a748-f6527008a020@pld-linux.org> On 26.02.2021 09:59, baggins wrote: > commit efec12ac5420b483fb368b05ba3c7f04c06d05ab > Author: Jan R?korajski > Date: Fri Feb 26 08:58:12 2021 +0100 > > Use rpm-specdump if it exists, rpm.org rpm can't do 'rpm dump %prep' why even bother supporting configurations without rpm-specdump installed? abort script if tool is missing and move along. ps: is the note about "Icon:" tag even valid?? does rpm-specdump fail too? i don't think we have any .spec with Icon: present From baggins at pld-linux.org Sat Feb 27 22:04:25 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sat, 27 Feb 2021 22:04:25 +0100 Subject: [packages/bind] Use relative symlinks, remove %attr for symlinks In-Reply-To: References: Message-ID: <20210227210425.GK1869@starbug> On Sat, 27 Feb 2021, glen wrote: > commit bf478371683c84f5ab0a5c76d8b93427e2c3992a > Author: Elan Ruusam?e > Date: Sat Feb 27 22:04:20 2021 +0200 > > Use relative symlinks, remove %attr for symlinks > > All for rpm 4.16 compatibility: > > - Explicit %attr() mode not applicable to symlink > - Absolute symlink You don't need to do relative symlinks, I patched our rpm for this. http://git.pld-linux.org/gitweb.cgi?p=packages/rpm.git;a=commit;h=d42a01a648b725059ec32c6c369af2563f0fcb28 -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Sun Feb 28 09:17:17 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 28 Feb 2021 10:17:17 +0200 Subject: [packages/bind] Use relative symlinks, remove %attr for symlinks In-Reply-To: <20210227210425.GK1869@starbug> References: <20210227210425.GK1869@starbug> Message-ID: On 27.02.2021 23:04, Jan R?korajski wrote: > On Sat, 27 Feb 2021, glen wrote: > >> commit bf478371683c84f5ab0a5c76d8b93427e2c3992a >> Author: Elan Ruusam?e >> Date: Sat Feb 27 22:04:20 2021 +0200 >> >> Use relative symlinks, remove %attr for symlinks >> >> All for rpm 4.16 compatibility: >> >> - Explicit %attr() mode not applicable to symlink >> - Absolute symlink > You don't need to do relative symlinks, I patched our rpm for this. > > http://git.pld-linux.org/gitweb.cgi?p=packages/rpm.git;a=commit;h=d42a01a648b725059ec32c6c369af2563f0fcb28 > i know you patched, but absolute symlinks have bothered me too, if you ever checked system outside chroot, you will understand the pain having to follow links manually when inspecting system.