<div dir="ltr">Echoing jjs' response, I really wouldn't run anything "critical" on fedora or anything that has less than three years support life time (which includes non-lts ubuntu). You just found out one of the reasons: on "bleeding-edge" distros, stuff are not as thouroughly tested.<div><br></div><div>Since you already have centos 7 and ubuntu lts, just use either of them as your container host. If an app needs F20 (for whatever reason), run them inside a container.</div><div><br></div><div>Anyway, what version of lxc do you run on centos 7? The same packages should be usable on F20. And if you absolutely need latest lxc git, either do the things I mentioned earlier (patch yourself, yada yada yada) or use one of your ubuntu systems with daily ppa.</div><div><br></div><div>-- </div><div>Fajar</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 22, 2014 at 6:33 AM, CDR <span dir="ltr"><<a href="mailto:venefax@gmail.com" target="_blank">venefax@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes, 1/3 in Fedora, 1/3 in Centos 7, and 1/3 in Ubuntu 14.04<br>
But that is the server, 100% of my apps are in LXC<br>
I need to simplify it, though.<br>
<div class="HOEnZb"><div class="h5"><br>
On Sat, Sep 20, 2014 at 7:36 PM, jjs - mainphrame <<a href="mailto:jjs@mainphrame.com">jjs@mainphrame.com</a>> wrote:<br>
> Yikes! you're running critical line of business apps on fedora?<br>
><br>
> On Sat, Sep 20, 2014 at 4:35 PM, CDR <<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>> wrote:<br>
>><br>
>> This technology is being used on critical line-of-business<br>
>> applications, at least in my company.<br>
>> I wish that Stepahane or other would follow a more predictable<br>
>> patch-releasing schedule.<br>
>><br>
>><br>
>> On Sat, Sep 20, 2014 at 6:22 PM, Michael H. Warfield <<a href="mailto:mhw@wittsend.com">mhw@wittsend.com</a>><br>
>> wrote:<br>
>> > On Sat, 2014-09-20 at 03:23 -0400, CDR wrote:<br>
>> >> I did a "git pull" and ´when I issued a "make rpm", it failed<br>
>> >><br>
>> >> error: Installed (but unpackaged) file(s) found:<br>
>> >> /usr/lib/systemd/system/lxc-net.service<br>
>> >> RPM build errors:<br>
>> >> File listed twice:<br>
>> >> /usr/lib64/python3.3/site-packages/_lxc-0.1-py3.3.egg-info<br>
>> >> File listed twice:<br>
>> >> /usr/lib64/python3.3/site-packages/_<a href="http://lxc.cpython-33m.so" target="_blank">lxc.cpython-33m.so</a><br>
>> >> File listed twice:<br>
>> >> /usr/lib64/python3.3/site-packages/lxc/__init__.py<br>
>> >> File listed twice:<br>
>> >> /usr/lib64/python3.3/site-packages/lxc/__pycache__<br>
>> >> File listed twice:<br>
>> >><br>
>> >> /usr/lib64/python3.3/site-packages/lxc/__pycache__/__init__.cpython-33.pyc<br>
>> >> File listed twice:<br>
>> >><br>
>> >> /usr/lib64/python3.3/site-packages/lxc/__pycache__/__init__.cpython-33.pyo<br>
>> >> File listed twice: /usr/libexec/lxc/lxc-autostart-helper<br>
>> >> File listed twice: /usr/libexec/lxc/lxc-devsetup<br>
>> >> File listed twice: /usr/libexec/lxc/lxc-user-nic<br>
>> >> Installed (but unpackaged) file(s) found:<br>
>> >> /usr/lib/systemd/system/lxc-net.service<br>
>> >> make: *** [rpm] Error 1<br>
>> >><br>
>> >> Any idea how can I compile the software?<br>
>> ><br>
>> > You raised this issue on 08/09 for 1.1.0alpha1 under Fedora 20. At that<br>
>> > time yours was the second report and I was already looking into it. You<br>
>> > then raised the issue again on the -devel list on 09/05 for 1.1.0alpha1<br>
>> > under CentOS 7 - exact same issue. At that time the patches had already<br>
>> > been submitted on 08/25 to Stéphane and were then under review. I<br>
>> > responded to you to that effect on 09/09 along with the reason for the<br>
>> > original failure and a pointer to my patches that had been posted to the<br>
>> > list.<br>
>> ><br>
>> > The patches are still being reviewed as he's been exceptionally busy<br>
>> > lately and the patches are fairly involved and involved some<br>
>> > disagreements in approach which were discussed in private E-Mail between<br>
>> > the involved parties.<br>
>> ><br>
>> > The patches have not been committed to git master to date and he's<br>
>> > working on integrating the changes. As a consequence, the answer I gave<br>
>> > to you on 09/09 on the -devel list remains the same and is equally<br>
>> > applicable to 1.1.0alpha1 and to git master...<br>
>> ><br>
>> > i.e. ... You can either apply the patches I posted to the -devel list<br>
>> > several weeks ago or you can wait for Stéphane to commit the fully<br>
>> > integrated patches to git master. At this time, applying my changes<br>
>> > will result in some patch warnings due to others submitting some warning<br>
>> > changes in parallel patches.<br>
>> ><br>
>> > I would recommend monitoring the -devel list for further (cough)<br>
>> > developments (yes, pun intended).<br>
>> ><br>
>> > Regards,<br>
>> > Mike<br>
>> ><br>
>> > On Tue, 2014-09-09 at 12:06 -0400, Michael H. Warfield wrote:<br>
>> >> This was due to a refactoring of the upstart init network code nearly<br>
>> >> a<br>
>> >> month ago by someone, AFAIK, not currently on the list which created<br>
>> >> some files in an incorrect location and the creation of dependencies<br>
>> >> on<br>
>> >> it in the systemd code. Patches for this fax paux have been submitted<br>
>> >> by me and Stéphane is currently evaluating my patch set to correct the<br>
>> >> problems that were created by the earlier submission by another that<br>
>> >> inadvertently broke all the rpm based systems. This was reported<br>
>> >> several weeks ago and I submitted my fix, after some private<br>
>> >> discussion,<br>
>> >> on 08/25.<br>
>> >><br>
>> >> Please review the following thread, starting on 08/25/2014, on this<br>
>> >> list<br>
>> >> for the patches and some discussion...<br>
>> ><br>
>> ><br>
>> >> Thanks,<br>
>> >> Philip<br>
>> >> _______________________________________________<br>
>> >> lxc-users mailing list<br>
>> >> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
>> >> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
>> >><br>
>> ><br>
>> > --<br>
>> > Michael H. Warfield (AI4NB) | (770) 978-7061 | mhw@WittsEnd.com<br>
>> > /\/\|=mhw=|\/\/ | (678) 463-0932 |<br>
>> > <a href="http://www.wittsend.com/mhw/" target="_blank">http://www.wittsend.com/mhw/</a><br>
>> > NIC whois: MHW9 | An optimist believes we live in the best<br>
>> > of all<br>
>> > PGP Key: 0x674627FF | possible worlds. A pessimist is sure of<br>
>> > it!<br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > lxc-users mailing list<br>
>> > <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
>> > <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
>> _______________________________________________<br>
>> lxc-users mailing list<br>
>> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
>> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> lxc-users mailing list<br>
> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a></div></div></blockquote></div><br></div>