[users] cacti new release

[Todd Lyons]

There is a new release of cacti, 0.8.7i, and version 0.8.7h is in the
repo. I just worked through an issue where some popular apache,
mysql, and mongodb templates are mishandled (graphs don't get created
properly) with 0.8.7h, but it does due to a bug fixed in 0.8.7i. I
wanted to request an update to the latest version. I built the new
version using a previous SRPM, it builds and packages with no issues.
I installed it on my machine and it fixes the problem I was facing.

I would also like to mention that the cacti-0.8.7g-3 and cacti-0.8.8h
srpms die with cpio errors when I try to install them. I used
cacti-0.8.7g-2 srpm to build the latest release.

...Todd

[David Hrbáč]

Post by Todd Lyons
There is a new release of cacti, 0.8.7i, and version 0.8.7h is in the
repo. I just worked through an issue where some popular apache,
mysql, and mongodb templates are mishandled (graphs don't get created
properly) with 0.8.7h, but it does due to a bug fixed in 0.8.7i. I
wanted to request an update to the latest version. I built the new
version using a previous SRPM, it builds and packages with no issues.
I installed it on my machine and it fixes the problem I was facing.
I would also like to mention that the cacti-0.8.7g-3 and cacti-0.8.8h
srpms die with cpio errors when I try to install them. I used
cacti-0.8.7g-2 srpm to build the latest release.
...Todd

Thanks, can you file the issue on GitHub cpio errors? Are you able to
submit spec pull request on GitHub?
Thanks,
DH

[Yury V. Zaytsev]

Post by David Hrbáč
Thanks, can you file the issue on GitHub cpio errors? Are you able to
submit spec pull request on GitHub?

I think it's just the RHEL5 / RHEL6 / sha1 / xz issue...

[Nico Kadel-Garcia]

Post by Yury V. Zaytsev

Post by David Hrbáč
Thanks, can you file the issue on GitHub cpio errors? Are you able to
submit spec pull request on GitHub?

I think it's just the RHEL5 / RHEL6 / sha1 / xz issue...
--
Sincerely yours,
Yury V. Zaytsev

Oh, goddess, that... I personally deal with it by using "mock" on an
RHEL 6 box to build for RHEL 5 environments.

The quick/dirty work around is to use 'rpm2cpio' to extract the
contents of the SRPM, and build a new RHEL 5 compatible SRPM.

cd /tmp
wget foo-1.0-1.el6.src.rpm
cd ~/rpm/SOURCES # or wherever your .rpmmacros is set to do
your builds from
rpm2cpio < /tmp/foo-1.0-1.el6.src.rpm | cpio -id
mv foo.spec ../SPECS
rpmbuild -bs --nodeps ../SPECS/foo.spec
rpmbuild --reubild ../SRPMS/foo-1.0-1.el5.src.rpm

The release names will be tweaked somewhat by the '%{?dist}' value in
the .spec file.

The problem is that RPM updated a number of specifications, especially
checksum handling, between RHEL 5 and 6, and between various versions
of Fedora.

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
Oh, goddess, that... I personally deal with it by using "mock" on an
RHEL 6 box to build for RHEL 5 environments.

Sure, I just wanted to let David know that there is probably nothing to
worry about...

By the way, I know that there is some commotion w.r.t. a backport to
RHEL5, but if you have an upstream subscription, contacting your manager
about that would really benefit all of us.

I've been working with them to solve some other packaging-related issues
that are impacting RepoForge and they've always been very helpful and
professional.

[David Hrbáč]

Post by Yury V. Zaytsev
Sure, I just wanted to let David know that there is probably nothing
to worry about...

Yury's right. My fault, text misreading.
DH

[David Hrbáč]

Post by Yury V. Zaytsev
Sure, I just wanted to let David know that there is probably nothing
to worry about...

Yury's right. My fault, text misreading.
DH

[Todd Lyons]

Post by Nico Kadel-Garcia
The quick/dirty work around is to use 'rpm2cpio' to extract the
contents of the SRPM, and build a new RHEL 5 compatible SRPM.
? ? ?cd /tmp
? ? ?wget foo-1.0-1.el6.src.rpm
? ? ?cd ~/rpm/SOURCES ? ?# or wherever your .rpmmacros is set to do
your builds from
? ? ?rpm2cpio < /tmp/foo-1.0-1.el6.src.rpm | cpio -id

Ah, my bad. I tried to use cpio directly and got an ugly error and
thought that confirmed the issue. I was not thinking well yesterday
apparently.

I will submit a new spec pull request for cacti.

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
Oh, goddess, that... I personally deal with it by using "mock" on an
RHEL 6 box to build for RHEL 5 environments.

Sure, I just wanted to let David know that there is probably nothing to
worry about...

By the way, I know that there is some commotion w.r.t. a backport to
RHEL5, but if you have an upstream subscription, contacting your manager
about that would really benefit all of us.

I've been working with them to solve some other packaging-related issues
that are impacting RepoForge and they've always been very helpful and
professional.

[Todd Lyons]

Post by Nico Kadel-Garcia
The quick/dirty work around is to use 'rpm2cpio' to extract the
contents of the SRPM, and build a new RHEL 5 compatible SRPM.
? ? ?cd /tmp
? ? ?wget foo-1.0-1.el6.src.rpm
? ? ?cd ~/rpm/SOURCES ? ?# or wherever your .rpmmacros is set to do
your builds from
? ? ?rpm2cpio < /tmp/foo-1.0-1.el6.src.rpm | cpio -id

Ah, my bad. I tried to use cpio directly and got an ugly error and
thought that confirmed the issue. I was not thinking well yesterday
apparently.

I will submit a new spec pull request for cacti.

[Nico Kadel-Garcia]

Post by Yury V. Zaytsev

Post by David Hrbáč
Thanks, can you file the issue on GitHub cpio errors? Are you able to
submit spec pull request on GitHub?

I think it's just the RHEL5 / RHEL6 / sha1 / xz issue...
--
Sincerely yours,
Yury V. Zaytsev

Oh, goddess, that... I personally deal with it by using "mock" on an
RHEL 6 box to build for RHEL 5 environments.

The quick/dirty work around is to use 'rpm2cpio' to extract the
contents of the SRPM, and build a new RHEL 5 compatible SRPM.

cd /tmp
wget foo-1.0-1.el6.src.rpm
cd ~/rpm/SOURCES # or wherever your .rpmmacros is set to do
your builds from
rpm2cpio < /tmp/foo-1.0-1.el6.src.rpm | cpio -id
mv foo.spec ../SPECS
rpmbuild -bs --nodeps ../SPECS/foo.spec
rpmbuild --reubild ../SRPMS/foo-1.0-1.el5.src.rpm

The release names will be tweaked somewhat by the '%{?dist}' value in
the .spec file.

The problem is that RPM updated a number of specifications, especially
checksum handling, between RHEL 5 and 6, and between various versions
of Fedora.

[Yury V. Zaytsev]

Post by David Hrbáč
Thanks, can you file the issue on GitHub cpio errors? Are you able to
submit spec pull request on GitHub?

I think it's just the RHEL5 / RHEL6 / sha1 / xz issue...

[Todd Lyons]

There is a new release of cacti, 0.8.7i, and version 0.8.7h is in the
repo. I just worked through an issue where some popular apache,
mysql, and mongodb templates are mishandled (graphs don't get created
properly) with 0.8.7h, but it does due to a bug fixed in 0.8.7i. I
wanted to request an update to the latest version. I built the new
version using a previous SRPM, it builds and packages with no issues.
I installed it on my machine and it fixes the problem I was facing.

I would also like to mention that the cacti-0.8.7g-3 and cacti-0.8.8h
srpms die with cpio errors when I try to install them. I used
cacti-0.8.7g-2 srpm to build the latest release.

...Todd

[David Hrbáč]

Post by Todd Lyons
There is a new release of cacti, 0.8.7i, and version 0.8.7h is in the
repo. I just worked through an issue where some popular apache,
mysql, and mongodb templates are mishandled (graphs don't get created
properly) with 0.8.7h, but it does due to a bug fixed in 0.8.7i. I
wanted to request an update to the latest version. I built the new
version using a previous SRPM, it builds and packages with no issues.
I installed it on my machine and it fixes the problem I was facing.
I would also like to mention that the cacti-0.8.7g-3 and cacti-0.8.8h
srpms die with cpio errors when I try to install them. I used
cacti-0.8.7g-2 srpm to build the latest release.
...Todd

Thanks, can you file the issue on GitHub cpio errors? Are you able to
submit spec pull request on GitHub?
Thanks,
DH