@ignatenkobrain Made the requested change.
--
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/pull/562#issuecomment-426472817___
ignatenkobrain commented on this pull request.
> @@ -1,3 +1,3 @@
%__pythondist_provides %{_rpmconfigdir}/pythondistdeps.py --provides
--majorver-provides
%__pythondist_requires %{_rpmconfigdir}/pythondistdeps.py --requires
-%__pythondist_path
Conan-Kudo commented on this pull request.
> @@ -1,3 +1,3 @@
%__pythondist_provides %{_rpmconfigdir}/pythondistdeps.py --provides
--majorver-provides
%__pythondist_requires %{_rpmconfigdir}/pythondistdeps.py --requires
-%__pythondist_path
@keszybz I've made the changes as requested.
--
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/pull/562#issuecomment-426244924___
Don't worry. I'll smash my commits after I'm back at my own machine, where I
can actually compile and check this stuff.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@ascherer pushed 1 commit.
6e2b98a DRY: Uniform error handling.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
It's not that the software doesn't have *some* version in such a situation,
it's just that the long-standing practise is to cram that info into the Release
tag which is completely wrong.
The right way to deal with such situations is to use the tilde operator, eg
```
Version: 0~git1234"
```
Closed #559.
--
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/559#event-1879008589___
Rpm-maint mailing list
@ascherer pushed 1 commit.
001509e Quit processing if tar fails.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
The top macro name you're seeing is simply the line in the spec. Try --trace
(or in older versions that don't support it, --eval '%trace') for more advanced
macro debugging.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@jasontibbitts: %luamacro would need to be implemented as a co-routine because
of rpm's embedded lua interpreter has a persistent global environment.
That is very different than shell code, where a sub-shell inherits but cannot
change its parent's environment. With rpm+lua, all lua invocations
@ascherer pushed 2 commits.
6036ec0 Source: file extraction may use other filters.
0b4473e Use default option macros for extractors.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
keszybz requested changes on this pull request.
> @@ -1,4 +1,4 @@
%__python_provides %{_rpmconfigdir}/pythondeps.sh --provides
%__python_requires %{_rpmconfigdir}/pythondeps.sh --requires
-%__python_path
13 matches
Mail list logo
