Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] rpm odd output of rpm macro
@ 2020-02-20 14:11 jirib
  2020-02-20 14:12 ` jirib
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: jirib @ 2020-02-20 14:11 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

New issue by jirib on void-packages repository

https://github.com/void-linux/void-packages/issues/19321

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
``Void 5.4.17_1 x86_64 GenuineIntel notuptodate rF``

* package:  
``ii rpm-4.15.1_2                              Red Hat Package Management Utils``

### Expected behavior
I would expect that `rpm --eval '%{_sharedstatedir}'` would return `/var/lib` as it is on CentOS; iirc actual value is from old EL.

```
$ cat /etc/redhat-release ; rpm --version ; rpm --eval '%{_sharedstatedir}'
CentOS Linux release 7.6.1810 (Core) 
RPM version 4.11.3
/var/lib
```
### Actual behavior
```
$ xuname ; rpm --version ; rpm --eval '%{_sharedstatedir}'
Void 5.4.17_1 x86_64 GenuineIntel notuptodate rF
RPM version 4.15.1
/usr/com
```
https://docs.fedoraproject.org/en-US/packaging-guidelines/RPMMacros/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: rpm odd output of rpm macro
  2020-02-20 14:11 [ISSUE] rpm odd output of rpm macro jirib
@ 2020-02-20 14:12 ` jirib
  2020-02-20 14:18 ` jirib
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: jirib @ 2020-02-20 14:12 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 302 bytes --]

New comment by jirib on void-packages repository

https://github.com/void-linux/void-packages/issues/19321#issuecomment-589065843

Comment:
```
$ grep sharedstatedir /usr/lib/rpm/platform/amd64-linux/macros 
%_sharedstatedir        %{_prefix}/com
```
strange, why does it return long unused value?

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: rpm odd output of rpm macro
  2020-02-20 14:11 [ISSUE] rpm odd output of rpm macro jirib
  2020-02-20 14:12 ` jirib
@ 2020-02-20 14:18 ` jirib
  2020-02-20 14:20 ` jirib
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: jirib @ 2020-02-20 14:18 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3656 bytes --]

New comment by jirib on void-packages repository

https://github.com/void-linux/void-packages/issues/19321#issuecomment-589065843

Comment:
```
$ grep sharedstatedir /usr/lib/rpm/platform/amd64-linux/macros 
%_sharedstatedir        %{_prefix}/com
```
strange, why does it return long unused value? should we patch macros from fedora so we are in sync with 21st centrury?

this is diff against CentOS:

```
--- /usr/lib/rpm/platform/amd64-linux/macros	2019-12-23 14:11:46.000000000 +0100
+++ /tmp/macros	2020-02-20 15:15:42.545675388 +0100
@@ -5,7 +5,7 @@
 #
 %_arch			x86_64
 %_build_arch		x86_64
-%_vendor		unknown
+%_vendor		redhat
 %_os			linux
 %_gnu			-gnu
 %_target_platform	%{_target_cpu}-%{_vendor}-%{_target_os}
@@ -27,20 +27,20 @@
 #
 %_prefix		/usr
 %_exec_prefix		%{_prefix}
-%_bindir		/usr/bin
-%_sbindir		/usr/bin
+%_bindir		%{_exec_prefix}/bin
+%_sbindir		%{_exec_prefix}/sbin
 %_libexecdir		%{_exec_prefix}/libexec
 %_datarootdir		%{_prefix}/share
 %_datadir		%{_datarootdir}
 %_sysconfdir		/etc
-%_sharedstatedir	%{_prefix}/com
+%_sharedstatedir	/var/lib
 %_localstatedir		/var
 %_lib			lib64
 %_libdir		%{_prefix}/lib64
 %_includedir		%{_prefix}/include
 %_oldincludedir		/usr/include
-%_infodir		/usr/share/info
-%_mandir		/usr/share/man
+%_infodir		%{_datarootdir}/info
+%_mandir		%{_datarootdir}/man
 %_initddir		%{_sysconfdir}/rc.d/init.d
 # Deprecated misspelling, present for backwards compatibility.
 %_initrddir		%{_initddir}
@@ -48,21 +48,9 @@
 
 %_defaultdocdir		%{_datadir}/doc
 
-# Maximum number of CPU's to use when building, 0 for unlimited.
-#%_smp_ncpus_max 0
-
-%_smp_build_ncpus %([ -z "$RPM_BUILD_NCPUS" ] \\\
-	&& RPM_BUILD_NCPUS="%{getncpus}"; \\\
-        ncpus_max=%{?_smp_ncpus_max}; \\\
-        if [ -n "$ncpus_max" ] && [ "$ncpus_max" -gt 0 ] && [ "$RPM_BUILD_NCPUS" -gt "$ncpus_max" ]; then RPM_BUILD_NCPUS="$ncpus_max"; fi; \\\
-        echo "$RPM_BUILD_NCPUS";)
-
-%_smp_mflags -j%{_smp_build_ncpus}
-
-# Maximum number of threads to use when building, 0 for unlimited
-#%_smp_nthreads_max 0
-
-%_smp_build_nthreads %{_smp_build_ncpus}
+%_smp_mflags %([ -z "$RPM_BUILD_NCPUS" ] \\\
+	&& RPM_BUILD_NCPUS="`/usr/bin/getconf _NPROCESSORS_ONLN`"; \\\
+	[ "$RPM_BUILD_NCPUS" -gt 1 ] && echo "-j$RPM_BUILD_NCPUS")
 
 #==============================================================================
 # ---- Build policy macros.
@@ -72,24 +60,12 @@
 #
 
 %__arch_install_post   %{nil}
-%_python_bytecompile_errors_terminate_build 0
-%_python_bytecompile_extra   1
-
-# Standard brp-macro naming:
-# convert all '-' in basename to '_', add two leading underscores.
-%__brp_compress %{_rpmconfigdir}/brp-compress %{?_prefix}
-%__brp_java_gcjcompile %{_rpmconfigdir}/brp-java-bytecompile
-%__brp_python_bytecompile %{_rpmconfigdir}/brp-python-bytecompile "" "%{?_python_bytecompile_errors_terminate_build}" "%{?_python_bytecompile_extra}"
-%__brp_strip %{_rpmconfigdir}/brp-strip %{__strip}
-%__brp_strip_comment_note %{_rpmconfigdir}/brp-strip-comment-note %{__strip} %{__objdump}
-%__brp_strip_shared %{_rpmconfigdir}/brp-strip-shared
-%__brp_strip_static_archive %{_rpmconfigdir}/brp-strip-static-archive %{__strip}
 
 %__os_install_post    \
-    %{?__brp_compress} \
-    %{?__brp_strip} \
-    %{?__brp_strip_static_archive} \
-    %{?__brp_strip_comment_note} \
+    %{_rpmconfigdir}/brp-compress \
+    %{_rpmconfigdir}/brp-strip %{__strip} \
+    %{_rpmconfigdir}/brp-strip-static-archive %{__strip} \
+    %{_rpmconfigdir}/brp-strip-comment-note %{__strip} %{__objdump} \
 %{nil}
 
 %__spec_install_post\
```

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: rpm odd output of rpm macro
  2020-02-20 14:11 [ISSUE] rpm odd output of rpm macro jirib
  2020-02-20 14:12 ` jirib
  2020-02-20 14:18 ` jirib
@ 2020-02-20 14:20 ` jirib
  2020-02-28  6:34 ` jirib
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: jirib @ 2020-02-20 14:20 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 319 bytes --]

New comment by jirib on void-packages repository

https://github.com/void-linux/void-packages/issues/19321#issuecomment-589074416

Comment:
Plus, IMO it would be nice to have this file included too:

```
$ grep -IR _unitdir /usr/lib/rpm
/usr/lib/rpm/macros.d/macros.systemd:%_unitdir /usr/lib/systemd/system
```


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: rpm odd output of rpm macro
  2020-02-20 14:11 [ISSUE] rpm odd output of rpm macro jirib
                   ` (2 preceding siblings ...)
  2020-02-20 14:20 ` jirib
@ 2020-02-28  6:34 ` jirib
  2021-03-22 19:51 ` jirib
  2021-03-22 19:51 ` [ISSUE] [CLOSED] " jirib
  5 siblings, 0 replies; 7+ messages in thread
From: jirib @ 2020-02-28  6:34 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 197 bytes --]

New comment by jirib on void-packages repository

https://github.com/void-linux/void-packages/issues/19321#issuecomment-592336970

Comment:
I will try to get a file with systemd (or other macros).

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: rpm odd output of rpm macro
  2020-02-20 14:11 [ISSUE] rpm odd output of rpm macro jirib
                   ` (3 preceding siblings ...)
  2020-02-28  6:34 ` jirib
@ 2021-03-22 19:51 ` jirib
  2021-03-22 19:51 ` [ISSUE] [CLOSED] " jirib
  5 siblings, 0 replies; 7+ messages in thread
From: jirib @ 2021-03-22 19:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 183 bytes --]

New comment by jirib on void-packages repository

https://github.com/void-linux/void-packages/issues/19321#issuecomment-804349370

Comment:
Closing old bugs, no interest to "fix" it.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ISSUE] [CLOSED] rpm odd output of rpm macro
  2020-02-20 14:11 [ISSUE] rpm odd output of rpm macro jirib
                   ` (4 preceding siblings ...)
  2021-03-22 19:51 ` jirib
@ 2021-03-22 19:51 ` jirib
  5 siblings, 0 replies; 7+ messages in thread
From: jirib @ 2021-03-22 19:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

Closed issue by jirib on void-packages repository

https://github.com/void-linux/void-packages/issues/19321

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
``Void 5.4.17_1 x86_64 GenuineIntel notuptodate rF``

* package:  
``ii rpm-4.15.1_2                              Red Hat Package Management Utils``

### Expected behavior
I would expect that `rpm --eval '%{_sharedstatedir}'` would return `/var/lib` as it is on CentOS; iirc actual value is from old EL.

```
$ cat /etc/redhat-release ; rpm --version ; rpm --eval '%{_sharedstatedir}'
CentOS Linux release 7.6.1810 (Core) 
RPM version 4.11.3
/var/lib
```
### Actual behavior
```
$ xuname ; rpm --version ; rpm --eval '%{_sharedstatedir}'
Void 5.4.17_1 x86_64 GenuineIntel notuptodate rF
RPM version 4.15.1
/usr/com
```
https://docs.fedoraproject.org/en-US/packaging-guidelines/RPMMacros/

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-03-22 19:51 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-20 14:11 [ISSUE] rpm odd output of rpm macro jirib
2020-02-20 14:12 ` jirib
2020-02-20 14:18 ` jirib
2020-02-20 14:20 ` jirib
2020-02-28  6:34 ` jirib
2021-03-22 19:51 ` jirib
2021-03-22 19:51 ` [ISSUE] [CLOSED] " jirib

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).