Actually, if ```%include``` automatically included the referenced file into
SRPM, that would be helpful as well. I realize, that the path could be
arbitrary, but if there was restriction, that could work ...
--
You are receiving this because you are subscribed to this thread.
Reply to this
Currently, the changelog entries can be either listed in a .spec file or they
could be included by ```%include``` directive. However, usage of the
```%include``` has one major downside, that the included file must be
explicitly listed as one of sources, otherwise the file would not be available
Yeah set versions is no doubt clever. Problem is it's too clever for my taste.
Call me a chicken anytime you like but I'm not this thing in:
http://git.altlinux.org/gears/r/rpm.git?p=rpm.git;a=blob;f=lib/set.c;h=9474a2ee6d7c9ce321d131cc310bfb4e80bdc6e4;hb=HEAD
--
You are receiving this because
Closed #362.
--
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/362#event-1469470480___
Rpm-maint mailing list
Reading the linked issue that might be a problem with how fsharp was handling
their symbols. I really don't know what to do here. Closing for now. Feel free
to reopen if new details emerge.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
Closed #185.
--
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/185#event-1469468134___
Rpm-maint mailing list
NAK for paths, it creates more problems than it solves.
Having rpm default to a modern dist-git style layout (or a trivial one-liner
way to enable it) would be more useful.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #352.
--
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/352#event-1469447590___
Rpm-maint mailing list
Closed #277.
--
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/277#event-1469399085___
Rpm-maint mailing list
I guess there was a point where distro settings would mess our test-suite, but
that's no longer the case. Other than that, we'll just fix the tests if/when
start defaulting to debugsource on.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
The declarative macro files are fine the way they are, we don't want spec
parser-style complex conditionals in rpm configuration.
A more productive path might be having a kind of include path that you could
use from specs, think of eg `%include `. I think there's a bug/ticket
for something
Closed #309.
--
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/309#event-1469378396___
Rpm-maint mailing list
I guess I got a bit lost between them all. Thanks for the fix :).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Same with Lua support, although those tests are more scattered around.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #236.
--
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/236#event-1469344602___
Rpm-maint mailing list
Yeah, Group already exists and yet nobody these days sees it as serving
anything useful, so adding another classifier tag doesn't seem that productive.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #364.
--
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/364#event-1469283490___
Rpm-maint mailing list
Yeah it's a bit strange - those "config files" are not supposed to be changed
then they're not really config files, are they? Anyway, commit
99887fec108110f0c85c060fcce48d13f807d058 added a mode where you can sign the
configs too if you so wish.
--
You are receiving this because you are
Fixed in commit faf7d87fda3456382cf161ff11a2ad8e00ae4ab0, thanks for the report
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #373.
--
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/373#event-1469261044___
Rpm-maint mailing list
Oh, I copied the new message to the ticket but not the commit, doh. Anyway:
```
$ ./rpm -e mlocate < /dev/null
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission
denied)
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
Yes. Don't do that!
--
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/315#issuecomment-364895755___
Rpm-maint mailing list
Your commit shows the old message, but not the new one. What does it show now?
If I'm decoding my past self's comments correctly, I was concerned not to have
the message be EBADF since that also seems quite puzzling.
--
You are receiving this because you are subscribed to this thread.
Reply
Closed #315.
--
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/315#event-1469249127___
Rpm-maint mailing list
Fixed by restoring errno around isatty() instead in commit
b89eb35c6034d43a8048ac9d452a1921596071a7
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #355.
--
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/355#event-1469240148___
Rpm-maint mailing list
First part was already fixed in commit
df053dd36461042e4d11a21a97e9be9058204658, second half now in commit
b89eb35c6034d43a8048ac9d452a1921596071a7:
```
[pmatilai@sopuli rpm]$ ./rpm -e mlocate
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission
denied)
[pmatilai@sopuli
If we had `%build_requires -f
Merged, thanks for the patch.
--
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/374#issuecomment-364853667___
Rpm-maint mailing
Merged #374.
--
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/374#event-1468954438___
Rpm-maint mailing list
30 matches
Mail list logo
