RPM Build Issue

[Raman Gupta]

Problem

========

While building RPM for netopeer/server using command:-

   ./configure --enable-debug --disable-dbus --prefix=/usr  && make rpm

I got following error:-

config.status: creating config/Netopeer.xml.tmp

config.status: creating config/NETCONF-server.xml.tmp

config.status: error: cannot find input file: `config/ietf-netconf-server-data.rng.in'

error: Bad exit status from /var/tmp/rpm-tmp.zqsRiJ (%build)

RPM build errors:

    Bad exit status from /var/tmp/rpm-tmp.zqsRiJ (%build)

make: *** [rpm] Error 1

The file 'config/ietf-netconf-server-data.rng.in' exists but still rpmbuild is complaining that it is not able to find the file. 

How to fix this?

I am attaching the rpm-tmp.zqsRiJ file.

Details
=========

netopeer:-

------------------

Latest master@5d9d009eded0

RPM tools:-
-------------------
rpm-build-4.8.0-32.el6.x86_64
rpm-4.8.0-32.el6.x86_64
rpmlint-0.94-2.el6.noarch
rpm-devel-4.8.0-32.el6.x86_64
rpm-python-4.8.0-32.el6.x86_64
redhat-rpm-config-9.0.3-42.el6.noarch
rpm-libs-4.8.0-32.el6.x86_64
rpmdevtools-7.5-2.el6.noarch

OS
--------
CentOS6 with kernel version 2.6.32-431.29.2.el6.x86_64

[Radek Krejčí]

Hi,
thanks for the report, the issue should be fixed in the current master (34d39d9d278a). You will need to re-run the configure script since the bugfix is in the Makefile.in.

Best regards,
Radek

Dne 5.2.2015 v 12:01 Raman Gupta napsal(a):

--
You received this message because you are subscribed to the Google Groups "Netopeer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netopeer+u...@googlegroups.com.
Visit this group at http://groups.google.com/group/netopeer.
For more options, visit https://groups.google.com/d/optout.

[Raman Gupta]

Hi Radek

Thanks a lot for fixing this issue.

Now I got next problem:-

Found '/tmp/netopeer/netopeer/server/RPMBUILD/BUILDROOT/netopeer-server-0.6.0-1.x86_64' in installed files; aborting

error: Bad exit status from /var/tmp/rpm-tmp.HjP8ss (%install)

RPM build errors:

    Bad exit status from /var/tmp/rpm-tmp.HjP8ss (%install)

make: *** [rpm] Error 1

To fix this new  problem, I added 'QA_SKIP_BUILD_ROOT=1' before rpmbuild command under the 'rpm' target in Makefile.in:-

+         QA_SKIP_BUILD_ROOT=1 $(RPMBUILD) -ba $(NAME).spec \
-         $(RPMBUILD) -ba $(NAME).spec \



It worked and RPMs were generated.

--Raman

[Radek Krejčí]

Hi,
it's the same as in the case of libnetconf - I'm not able to replicate the issue. netopeer does not install nothing like netopeer-server-0.6.0-1.x86_64 file, so I don't understand what is it complaining for. Try to post the complete output of the make rpm command. I think that skipping building it does not solve the problem :)

Radek

Dne 6.2.2015 v 11:54 Raman Gupta napsal(a):

-- 
Radek Krejci
mobile  : +420 732 212 714
office  : +420 234 680 256
e-mail  : rkr...@cesnet.cz
LinkedIn: http://www.linkedin.com/in/radekkrejci

CESNET, Association of Legal Entities
Zikova 4
160 00 Praha 6
Czech Republic

[Raman Gupta]

Hi Radek,

Issue is same as was in libnetconf and I used same fix but I am not sure if that is the correct fix OR my system/env has some unique rpm build problems. The installation of generated RPMS was fine.

I am attaching the output of 'make rpm' and rpm-tmp file.

--Raman

[Radek Krejčí]

Hi Raman,

I was finally able to reproduce the problem :) (by setting /usr/lib/rpm/check-buildroot into my ~/.rpmmacros)

The problems should be fixed now in both masters (libnetconf and netopeer), so please re-run configure and try to build RPMs without switching off the buildroot check. There is one more bug in the netopeer-server since it does not include netopeer-configurator in the RPM package. However, it does not throw an error (at least not to me :)). I'm going to fix this issue later today or tomorow.

Regards,
Radek

Dne 6.2.2015 v 13:57 Raman Gupta napsal(a):

[Radek Krejčí]

Hello,
the mentioned issue with the netopeer-configurator should be fixed now
(master branch f5dd4c7a85b8).

Regards,
Radek


Dne 6.2.2015 v 17:24 Radek Krejčí napsal(a):

[Raman Gupta]

Hi,

Great! now I can create RPMs (both libnetconf & netopeer-server) without any problem and without applying SKIP flag. Both RPMs were speedily built also. 

I am attaching the startup logs of netopeer-server after creating and installing libnetconf & netopeer-server RPMs. 

Thanks for help.

But one small issue is that I was on libnetconf-0.9 and netopeeer-0.6 versions and this fix is latest in master branch. The master branch and released version branches have tons of differences and for me to take such huge changes without moving to next release versions of libnetconf and netopeer respectively is a challenge.

Any idea when next official release will be done and will these changes be a part of next release?

--Raman

[Radek Krejčí]

Hi Raman,
in libnetconf, I've just merged the bugfixes from master into the 0.9.x branch. The HEAD of 0.9.x branch is now versioned as libnetconf 0.9.1. Netopeer master HEAD should be compatible with libnetconf 0.9.1. libnetconf 0.9.1 is binary compatible with libnetconf 0.9.0

There are many new features in other (non-master) Netopeer branches, but I'm not able to merge it to the master before mid-March - currently I recommend using the Netopeer's master.

Netopeer version is actually quite confusing, since version 0.6 is there more than year and it is not changing :( We are planning to resuscitate versioning, but it won't be earlier than in March.

Regards,
Radek


Dne 8.2.2015 v 12:52 Raman Gupta napsal(a):

[Raman Gupta]

Hi,

Fair enough.

Thanks for clarifications and compatibility between libnetconf and netopeer.

--Raman

[shikhag...@gmail.com]

Hi,

Will the versioning fix of netopeer and its next release version alongwith moving of libnetconf release from 0.9.1 to its next version be done in March 2015?

--Raman

[Radek Krejčí]

Hi Raman,

probably, but I have to finnish some other project first, so it may be
done in the first half of April.

Radek

Dne 11.3.2015 v 13:19 shikhag...@gmail.com napsal(a):

[Raman Gupta]

Hi Radek,

Are we on the path for version fix of netopeer and its next release version along with moving of libnetconf release from 0.9.1 to its next version ?

--Raman

[Radek Krejčí]

Hi Raman,
it depends what you mean by version fix. The problem, from my perspective, in netopeer versioning was that there was no versioning or actually no moving in versions.

Currently, we are preparing release of libnetconf 0.9.2 (from libnetconf's 0.9.x branch) together with releasing netopeer server 0.6.1 (from netopeer's libnetconf-0.9.x branch). The change from 0.6.0 to 0.6.1 actually does not reflects the real changes in code, we just want to restart versioning in netopeer and 0.6.1 actually means "from the outside, it is still the same server, but there are some changes". These release should be available within a week or so.

Then, within a several weeks, we are going to release versions from the current master branches - probably 0.10.0 in libnetconf and 0.7.0 in netopeer. In case of netopeer, it should start regular versioning.

Does this answer your question?

Radek

Dne 28.4.2015 v 12:30 Raman Gupta napsal(a):

[Raman Gupta]

Hi Radek,

Yes, you have answered the question. So next major release is 0.10.0 libnetconf and 0.7.0 netopeer released from trunk. But meanwhile we will have patch release 0.9.2 and netopeer 0.6.1 .

I think with this plan netopeer regular versioning will start in parallel to libnetconf and we can then have well defined relationship/dependency between versions of the two.

Thanks.

--Raman