Like said, in *released versions* the tests run unconditionally, plus various
related fixes have gone into git master. If it's reproducable there too then
you'll need to provide actual details of how you're building it, this doesn't
happen in my environment.
--
You are receiving this because
So I've added --enable-python to configure options, I've commented out in the
spec %build
```
#pushd python
#%{__python2} setup.py build
#%{__python3} setup.py build
#popd
```
and in %install
```
#pushd python
#%{__python2} setup.py install --skip-build --root %{buildroot}
#%{__python3}
4.14.2.1
Yep in Fedora spec file there is no --enable-python.
Going to test what will happen when this option is added.
Nevertheless even if --enable-python is not used python tests are fired in
check target.
--
You are receiving this because you are subscribed to this thread.
Reply to this
@mlschroe Well, when we're referring to hg/git/svn snapshot dates, that's
considered as part of upstream versioning. This is done in openSUSE and we want
to move to that in Fedora to simplify automation of package (re)builds and
things like that.
--
You are receiving this because you are
@mlschroe, would you mind implementing this in libsolv? Or should I do so?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I don't mind having this, '^' should not break existing EVR uses.
I'm a bit uncertain about the use case, wouldn't you put the '20160101' from
the example in the release? 'Version' usually comes from upstream and 'Release'
comes from the packager.
But, as said, I'm not opposed ;-)
--
You are
LSB is terribly outdated wrt modern rpm, but is probably the most complete
thing there is:
http://refspecs.linuxbase.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/pkgformat.html
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Indeed. I had figured out the supported fields list using ’rpm --querytags’.
Yet I fail to discover a way to print each tag description; Do you have a
suggestion for that?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The --qf applies to headers, not output rows. You're asking for two different
things about a single header in that query: the requires, and the name +
description of the "rpm" package.
To get the name name + description of all of rpm's dependencies you'll need
nested queries, something like:
Closed #600.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/600#event-1974623901___
Rpm-maint mailing list
Command option '_--qf_' applies **only** to **parameter attached** to option
'-_q_' (here _rpm_), not to each output row as expected. (Possible bug)
Actual result:
```
$ rpm -qR rpm --qf '%{NAME} – %{DESCRIPTION}'
/usr/bin/bash
(...)
rpm – The RPM Package Manager (RPM) (...)
(...) a
I know precisely nothing about Amazon Linux, but this sounds like the Python
2.7.x version on that platform is not packaged as "python" but something else.
'rpm -qf /usr/bin/python' ought to tell you what that something else is.
Doesn't sound like an rpm bug though.
--
You are receiving this
Closed #598.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/598#event-1974138443___
Rpm-maint mailing list
What rpm version, how are you building it? IIRC this happens with released
versions you build without explicitly enabling the python bindings build in
configure. In git master the python tests get skipped if it's not enabled.
--
You are receiving this because you are subscribed to this thread.
14 matches
Mail list logo
