The often stated public policy here with RPM4 is "Compatibility with RPM5 is a
negative goal."
Don't hold your breath for a patch: I will generate and distribute a patch as
soon as I understand
the full consequences of recent changes to the RPM format.
Yes, Yocto issues are well known. The
Regarding using RPM4 to manager RPM5 packages, the reason is that the previous
version of the distro was using RPM5. However due to incompatibilities with dnf
it was decided by uptream Yocto developers do switch to RPM4. In our
Yocto-based distro there are some leftover rpm files that weren't
@n3npq thanks for looking into this. This rpm may be the only one I'll have to
deal with and I can regenerate it using rpm4 reasonably easy. However I thought
it was important to notify upstream since when other distros update they may
face similar problems since they don't have much control
That is a package produced by RPM5:
```
$ /opt/local/bin/rpm -qp --yaml ./capsule-01.00.12-r0.core2_64.rpm | grep
Rpmversion
Rpmversion: 5.4.16
```
The package uses a non-repudiable signature and verifies fine:
```
$ /opt/local/bin/rpm -qvvp ./capsule-01.00.12-r0.core2_64.rpm
...
D: PUB:
[rpm_uuid.patch.gz](https://github.com/rpm-software-management/rpm/files/1163437/rpm_uuid.patch.gz)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
UUID's provide a common format for identification and database retrieval.
The attached patch adds a header tag format to RPM queries.
- UUIDv1 time stamps (for events like build/install times):
```
$ ./rpm -q --qf '%{buildtime:uuidv1}\n' bash
c60fd500-bc0a-11e7-804e-003048b801de
```
- UUIDv3
The replaceSigDigests function is only used in includeFileSignatures
when WITH_IMAEVM is defined. If not warning is generated.
Signed-off-by: Mark Wielaard
(this is same patch as posted to mailing list, sending it here since now we
have CI)
You can view, comment on, or merge
In the minisymtab section (the .gnu_debugdata embedded ELF image) we
do not need unallocated sections (except for the SYMTAB and STRTAB
sections we are creating). We already remove PROGBITS and NOTES. Also
remove NOBITS sections. They should not really take up much (any) space
but they still add
Merged #266.
--
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/266#event-1172459222___
Rpm-maint mailing list
LGTM :shipit:
--
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/266#issuecomment-316740455___
Rpm-maint mailing list
cgwalters commented on this pull request.
> @@ -0,0 +1,49 @@
+FROM fedora
+MAINTAINER Igor Gnatenko
+
+WORKDIR /opt/rpm
+COPY . .
+
+RUN echo -e "deltarpm=0\ninstall_weak_deps=0\ntsflags=nodocs" >>
/etc/dnf/dnf.conf
+RUN dnf -y update
+RUN dnf -y install \
Which
cgwalters commented on this pull request.
> @@ -0,0 +1,49 @@
+FROM fedora
+MAINTAINER Igor Gnatenko
+
+WORKDIR /opt/rpm
+COPY . .
+
+RUN echo -e "deltarpm=0\ninstall_weak_deps=0\ntsflags=nodocs" >>
/etc/dnf/dnf.conf
+RUN dnf -y update
+RUN dnf -y install \
In some
cc @markoa
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/266
-- Commit Summary --
* add Fedora's Dockerfile for CI
* tests: don't copy fstab to chroot
* ci: enable silent rules
-- File Changes --
A
On Wed, Jul 19, 2017 at 02:49:38PM +0200, Mark Wielaard wrote:
> glibc 2.25 introduced (really long and annoying) warnings for each use
> of the major/minor macros from the wrong header:
>
> lib/cpio.c: In function ‘rpmcpioHeaderWrite’:
> lib/cpio.c:245:13: warning: In the GNU C Library, "major"
```
...
make[2]: Entering directory '/opt/rpm/python'
CC rpmmodule.lo
CC header-py.lo
CC rpmarchive-py.lo
CC rpmds-py.lo
CC rpmfd-py.lo
CC rpmfi-py.lo
CC rpmfiles-py.lo
CC rpmkeyring-py.lo
CC rpmmi-py.lo
CC rpmii-py.lo
Pushed as #252
--
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/195#issuecomment-316702937___
Rpm-maint mailing list
Closed #195.
--
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/195#event-1172099300___
Rpm-maint mailing list
@ffesti Thanks!
--
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/252#issuecomment-316698441___
Rpm-maint mailing list
Pushed.
--
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/252#issuecomment-316698323___
Rpm-maint mailing list
Closed #252.
--
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/252#event-1172069958___
Rpm-maint mailing list
Conan-Kudo requested changes on this pull request.
So this can be a problem, because on LSB-compliant 64-bit systems (i.e. most of
them running RPM), `${libdir}` is `/usr/lib64`.
If we wanted to move it anywhere, we'd probably move it to `${libexecdir}`,
since that is static across
…uration and macros.
This can be named in various different ways, especially in cross-compilation
environments, so let's take it from the build setup.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/263
-- Commit Summary --
It has been used in redhat-rpm-config for long time and some
packages depend on it (though without `_` prefix).
It's just more convenient than writing %{_rpmconfigdir}/macros.d/...
Signed-off-by: Igor Gnatenko
You can view, comment on, or merge this pull
@markoa \o/ reaching out to you =)
--
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/261#issuecomment-316614406___
Rpm-maint
Hi folks, Semaphore cofounder here. We'd be support RPM with a free account
that can run more parallel jobs. Please reach out to us at
supp...@semaphoreci.com to discuss. :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
25 matches
Mail list logo