Github messages for voidlinux
 help / color / mirror / Atom feed
From: jirib <jirib@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] rpm odd output of rpm macro
Date: Thu, 20 Feb 2020 15:11:32 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19321@inbox.vuxu.org> (raw)

[-- 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/

             reply	other threads:[~2020-02-20 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 14:11 jirib [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19321@inbox.vuxu.org \
    --to=jirib@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).