Displaying 10 results from an estimated 10 matches for "nevr".
Did you mean:
never
2019 Jan 30
1
[PATCH v3] v2v: linux: use NEVR for querying RPM packages (RHBZ#1669395)
Use NEVR when querying RPM for the list of files of a package, instead
of ENVR. Also, use the epoch only when non-zero, and version of RPM
supports it.
The approach is basically copied from what supermin does in its RPM
package handler.
---
v2v/linux.ml | 59 +++++++++++++++++++++++++++++++++-------------...
2019 Jan 30
1
[PATCH v2] v2v: linux: use NEVR for querying RPM packages (RHBZ#1669395)
Use NEVR when querying RPM for the list of files of a package, instead
of ENVR. Also, use the epoch only when non-zero, and version of RPM
supports it.
The approach is basically copied from what supermin does in its RPM
package handler.
---
v2v/linux.ml | 55 ++++++++++++++++++++++++++++++++--------------...
2019 Jan 29
2
[PATCH] v2v: linux: use NEVR for querying RPM packages (RHBZ#1669395)
Use NEVR when querying RPM for the list of files of a package, instead
of ENVR. Also, use the epoch only when non-zero, and version of RPM
supports it.
The approach is basically copied from what supermin does in its RPM
package handler.
---
v2v/linux.ml | 52 +++++++++++++++++++++++++++++++---------------...
2019 Jan 30
0
Re: [PATCH] v2v: linux: use NEVR for querying RPM packages (RHBZ#1669395)
On Tue, Jan 29, 2019 at 03:29:44PM +0100, Pino Toscano wrote:
> Use NEVR when querying RPM for the list of files of a package, instead
> of ENVR. Also, use the epoch only when non-zero, and version of RPM
> supports it.
>
> The approach is basically copied from what supermin does in its RPM
> package handler.
> ---
> v2v/linux.ml | 52 +++++++++++...
2011 Apr 26
3
updating libvorbis
Hello,
On a machine with CentOS-5.6, I need libvorbis >= 1.2, so I have
recompiled and packaged libvorbis.
But I get the following error :
$ rpm -U /usr/src/redhat/RPMS/x86_64/libvorbis-1.2.3-phn.1.x86_64.rpm /usr/src/redhat/RPMS/x86_64/libvorbis-devel-1.2.3-phn.1.x86_64.rpm
package libvorbis-1.1.2-3.el5_4.4.x86_64 (which is newer than libvorbis-1.2.3-phn.1.x86_64) is already
2020 Jun 24
0
Blog article about the state of CentOS
...pass at this was built probably a month earlier based on the dates of
other packages, but something was probably found in QA that required a
rebuild, or the rebuild depended on something else that was late to build.
AND since this rebuilt package HAS TO KEEP THE SAME
Name/Epoch/Version/Release (NEVR) tuple to be RHEL-compatible, the first
N=bpftool V=4.18.0 R= 193.el8 could not be released; who knows, there
may have been a dozen of the same NVR (bpftool's %{EPOCH} is (none) and
so I don't count it)... ? If the first N=bpftool V=4.18.0 R= 193.el8
were to be released, then how, withi...
2020 Jun 20
3
Blog article about the state of CentOS
On 20/06/20 3:50 am, Johnny Hughes wrote:
> Your dates are significantly off
> Wikipedia has a delay listed in a table:
>
> It is, for CentOS-7, For example:
>
> 7.0 27
> 7.1 26
> 7.2 25
> 7.3 39
> 7.4 43
> 7.5 31
> 7.6 34
> 7.7 42
> 7.8 28
>
>
> For 6 .. since 6.2, it has bee3n between 10 and 18 days.
>
> For 8:
>
> 8.0
2010 May 10
1
Number and colon precedes some package names in yum.log
What is the meaning of the "4:", "2:", "30:" and "1:" prefixes for the
following entries in yum.log? Most entries in yum.log don't have
them.
grep "Installed: [0-9]*:" /var/log/yum.log
May 07 16:45:53 Installed: 4:perl-5.8.8-27.el5.i386
May 07 16:58:21 Installed: 2:xinetd-2.3.14-10.el5.i386
May 07 17:03:43 Installed:
2004 Sep 13
1
throughput of 300MB/s
Hello,
are there any experiences with samba as a _really_ fast server?
Assuming if the filesystem and network is fast enough, has anyone managed
to get a throughput in samba of of let's say 300 MB/s ?
Are there any benchmarks?
regards,
Martin
2019 Jan 29
1
[PATCH] v2v: Fix kernel disambiguation by dropping Epoch field (RHBZ#1669395).
When detecting kernels we have to list the files in the package to
find the right /boot/vmlinuz file.
In virt-v2v 1.28 we ran:
rpm -ql kernel
Because multiple kernels can be installed this gave incorrect results,
which was reported in RHBZ#1161250 and initially fixed in
commit 377bc302f11db3da4263f894c76a7d280fb25dbd. This changed the
command to:
rpm -ql [epoch:]kernel-version.release