Well, apparently by what it fundamentally addresses.
But I provided a specific pointer to an extant description (which is far better
than "read the source code", AFAIR) and a offer to translate it into something
being worth to be called "documentation".
Hence one might argue that this issue
I am interested in this as well.
This does not need to be fully implemented by rpmbuild itself. The list of
"components" used for the build can be gathered by the build system. E.g., Mock
can already do that
https://rpm-software-management.github.io/mock/Plugin-PackageState In this
case, the
Any chance this could be looked at for a future release? Seems like it could be
a pretty quick tweak.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/646#issuecomment-1512165378
You are receiving this because you are subscribed to this
It is pretty common that package maintainers do an mistake in the SPEC file and
forget a BuildRequires. It passes for them in plain rpmbuild on their
workstation will full set of packages. But when the build is run in Koji or
Mock the package that defines macro is missing. E.g. %py3_build. For
Here's the documentation for
[pgpParsePkts](https://github.com/rpm-software-management/rpm/blob/457bd287cf84323209e8daebe843c25054f1808e/include/rpm/rpmpgp.h#L1034):
```
/** \ingroup rpmpgp
* Parse armored OpenPGP packets from memory.
* @param armor armored OpenPGP packet string
*
Problem: After first packet function returns. Next packet are ignored.
Example solutions:
1. Parse all packets.
2. New function that parse one packet but returns one more parameter with
offset of the packet ends. To be able to call the function again from that
point.
--
Reply to this email
You need it for koji? Couldn't they also switch to the [shim
module](https://github.com/packit/rpm-shim)?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2361#discussioncomment-5641171
You are receiving this because you are
maybe to late for me, I have issues with `rpm-py-installer`, I thought then I
need to go back to cry to
https://github.com/junaruga/rpm-py-installer/issues/260 :)
--
Reply to this email directly or view it on GitHub:
No, `specfile` now depends on the shim module rather than `rpm-py-installer`.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2361#discussioncomment-5638789
You are receiving this because you are subscribed to this thread.
Message
@nforro @hroncok @TomasTomecek thanks for the discussion, so this is blocked on
#2345 ?
We hit this again with new pip, and need to stick to pip < 23.1, where even the
old does not install anymore ;(
https://gitlab.com/testing-farm/gluetool-modules/-/merge_requests/438/diffs
--
Reply to
Reopened #2474.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2474#event-9025128067
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
hmpf
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2474#issuecomment-1511439562
You are receiving this because you are subscribed to this thread.
Message ID: ___
Rpm-maint mailing list
Actually, it should be `/usr/share/dbus-1/system.d/`
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2474#issuecomment-1511399657
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #2486 as not planned.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2486#event-9024780445
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint
Ok.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2486#issuecomment-1511389601
You are receiving this because you are subscribed to this thread.
Message ID: ___
Rpm-maint mailing list
@rhabacker pushed 4 commits.
357226d505af0a27264b5bd44d9487fa7ce41516 Add macro '%-x**' containing all
occurrences of the flag '-x' or '-x '.
352165ced88ea834bb3918af29607263b7b71e69 Add test case for macro '%-x**'
a425f2210b503ae5ddb796953daa76cdb8571007 Add test case for macro '%-x'
@rhabacker pushed 2 commits.
357226d505af0a27264b5bd44d9487fa7ce41516 Add macro '%-x**' containing all
occurrences of the flag '-x' or '-x '.
352165ced88ea834bb3918af29607263b7b71e69 Add test case for macro '%-x**'
--
View it on GitHub:
> This may fix a use-case for you but is likely to break it for several others.
A number of conditions are required for this to cause a problem:
1. in the parameter list of a macro `x:`must be specified.
2. `%-x` is used in the macro in question
3. the calling program supports only `-x` and `-x `
The case of payloaddigestalt is for uncompressed payload: you can take a
compressed payload from a package, uncompress it and replace the compressed
payload in the package, and it'll work. There's no reason not to.
--
Reply to this email directly or view it on GitHub:
19 matches
Mail list logo
