[suggest] Re: suggest Digest, Vol 66, Issue 3

[Nico Kadel-Garcia]

From: Fabian Arrotin <fabian.arrotin at arrfab.net>

I'm taking a look at updating git for some clients, but note that the
git at RPMforge is 1.7.3. That's cool: the latest release is 1.7.3.2,
but that's plenty recent.
? ? error: lin 48: Unknown tag: %filter_from_requires /^perl(packed-refs)*/d
There's clearly some RPM macro undefined there, but it's not in the
RHEL or CentOS 5 basic rpm-build setup. Does anyone understand where
this macro is normally set from, and what its value should be?

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/rpm-macros-rpmforge/rpm-macros-rpmforge.spec?revision=9320&view=markup

Oh, boy. That's a new one on me. Is this integrated into the mock
environment? Because if it's not, and this macro is required on a
widespread basis, I'm going to have a pain in the neck integrating it
there. This is especially true because I'm using the EPEL testing
mock, which is at version 1.0.13, produces much smaller mock chroot
cages by flushing unnecessary logs, makes much smaller cached
tarballs, and handles autofs enabled build hosts a lot better.

In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
Oh, boy. That's a new one on me. Is this integrated into the mock
environment?

What do you mean by integrated? Just create a local repo by downloading
this RPM and generate metadata with createrepo, then add it to your mock
config and tell it to install this package on build.

Post by Nico Kadel-Garcia
In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

As far as I know, the mock version that RPMForge ships has up to date
RPMForge configs, so that you just have to tell it to create an RPMForge
chroot (instead of EPEL) and rebuild your RPMForge packages there.

[Nico Kadel-Garcia]

From: Fabian Arrotin <fabian.arrotin at arrfab.net>

I'm taking a look at updating git for some clients, but note that the
git at RPMforge is 1.7.3. That's cool: the latest release is 1.7.3.2,
but that's plenty recent.
? ? error: lin 48: Unknown tag: %filter_from_requires /^perl(packed-refs)*/d
There's clearly some RPM macro undefined there, but it's not in the
RHEL or CentOS 5 basic rpm-build setup. Does anyone understand where
this macro is normally set from, and what its value should be?

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/rpm-macros-rpmforge/rpm-macros-rpmforge.spec?revision=9320&view=markup

Oh, boy. That's a new one on me. Is this integrated into the mock
environment? Because if it's not, and this macro is required on a
widespread basis, I'm going to have a pain in the neck integrating it
there. This is especially true because I'm using the EPEL testing
mock, which is at version 1.0.13, produces much smaller mock chroot
cages by flushing unnecessary logs, makes much smaller cached
tarballs, and handles autofs enabled build hosts a lot better.

In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
Oh, boy. That's a new one on me. Is this integrated into the mock
environment?

What do you mean by integrated? Just create a local repo by downloading
this RPM and generate metadata with createrepo, then add it to your mock
config and tell it to install this package on build.

Post by Nico Kadel-Garcia
In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

As far as I know, the mock version that RPMForge ships has up to date
RPMForge configs, so that you just have to tell it to create an RPMForge
chroot (instead of EPEL) and rebuild your RPMForge packages there.

[Nico Kadel-Garcia]

From: Fabian Arrotin <fabian.arrotin at arrfab.net>

I'm taking a look at updating git for some clients, but note that the
git at RPMforge is 1.7.3. That's cool: the latest release is 1.7.3.2,
but that's plenty recent.
? ? error: lin 48: Unknown tag: %filter_from_requires /^perl(packed-refs)*/d
There's clearly some RPM macro undefined there, but it's not in the
RHEL or CentOS 5 basic rpm-build setup. Does anyone understand where
this macro is normally set from, and what its value should be?

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/rpm-macros-rpmforge/rpm-macros-rpmforge.spec?revision=9320&view=markup

Oh, boy. That's a new one on me. Is this integrated into the mock
environment? Because if it's not, and this macro is required on a
widespread basis, I'm going to have a pain in the neck integrating it
there. This is especially true because I'm using the EPEL testing
mock, which is at version 1.0.13, produces much smaller mock chroot
cages by flushing unnecessary logs, makes much smaller cached
tarballs, and handles autofs enabled build hosts a lot better.

In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
Oh, boy. That's a new one on me. Is this integrated into the mock
environment?

What do you mean by integrated? Just create a local repo by downloading
this RPM and generate metadata with createrepo, then add it to your mock
config and tell it to install this package on build.

Post by Nico Kadel-Garcia
In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

As far as I know, the mock version that RPMForge ships has up to date
RPMForge configs, so that you just have to tell it to create an RPMForge
chroot (instead of EPEL) and rebuild your RPMForge packages there.

[Nico Kadel-Garcia]

From: Fabian Arrotin <fabian.arrotin at arrfab.net>

I'm taking a look at updating git for some clients, but note that the
git at RPMforge is 1.7.3. That's cool: the latest release is 1.7.3.2,
but that's plenty recent.
? ? error: lin 48: Unknown tag: %filter_from_requires /^perl(packed-refs)*/d
There's clearly some RPM macro undefined there, but it's not in the
RHEL or CentOS 5 basic rpm-build setup. Does anyone understand where
this macro is normally set from, and what its value should be?

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/rpm-macros-rpmforge/rpm-macros-rpmforge.spec?revision=9320&view=markup

Oh, boy. That's a new one on me. Is this integrated into the mock
environment? Because if it's not, and this macro is required on a
widespread basis, I'm going to have a pain in the neck integrating it
there. This is especially true because I'm using the EPEL testing
mock, which is at version 1.0.13, produces much smaller mock chroot
cages by flushing unnecessary logs, makes much smaller cached
tarballs, and handles autofs enabled build hosts a lot better.

In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
Oh, boy. That's a new one on me. Is this integrated into the mock
environment?

What do you mean by integrated? Just create a local repo by downloading
this RPM and generate metadata with createrepo, then add it to your mock
config and tell it to install this package on build.

Post by Nico Kadel-Garcia
In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

As far as I know, the mock version that RPMForge ships has up to date
RPMForge configs, so that you just have to tell it to create an RPMForge
chroot (instead of EPEL) and rebuild your RPMForge packages there.

[Nico Kadel-Garcia]

From: Fabian Arrotin <fabian.arrotin at arrfab.net>

I'm taking a look at updating git for some clients, but note that the
git at RPMforge is 1.7.3. That's cool: the latest release is 1.7.3.2,
but that's plenty recent.
? ? error: lin 48: Unknown tag: %filter_from_requires /^perl(packed-refs)*/d
There's clearly some RPM macro undefined there, but it's not in the
RHEL or CentOS 5 basic rpm-build setup. Does anyone understand where
this macro is normally set from, and what its value should be?

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/rpm-macros-rpmforge/rpm-macros-rpmforge.spec?revision=9320&view=markup

Oh, boy. That's a new one on me. Is this integrated into the mock
environment? Because if it's not, and this macro is required on a
widespread basis, I'm going to have a pain in the neck integrating it
there. This is especially true because I'm using the EPEL testing
mock, which is at version 1.0.13, produces much smaller mock chroot
cages by flushing unnecessary logs, makes much smaller cached
tarballs, and handles autofs enabled build hosts a lot better.

In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
Oh, boy. That's a new one on me. Is this integrated into the mock
environment?

What do you mean by integrated? Just create a local repo by downloading
this RPM and generate metadata with createrepo, then add it to your mock
config and tell it to install this package on build.

Post by Nico Kadel-Garcia
In fact, updating mock would be good, but I've not found time to
attack that for RPMforge use.

As far as I know, the mock version that RPMForge ships has up to date
RPMForge configs, so that you just have to tell it to create an RPMForge
chroot (instead of EPEL) and rebuild your RPMForge packages there.