Red Hat Bugzilla – Bug 195365
Review Request: etcnet - /etc/net network configuration system
Last modified: 2014-02-08 18:29:47 EST
Spec URL: http://etcnet.org/files/Fedora.spec
SRPM URL: http://etcnet.org/files/etcnet-0.8.3-fc5.0.test4.src.rpm
Description: /etc/net should become an alternative way of configuring network in Fedora. It was designed with former and current limitations of initscripts-style configuration and is already known to work. More information is available with supplied manpages and at the project homepage: http://etcnet.org/
This package contains a lot of rpmlint errors
can you add Makefile to source package and make it clean? There are a lot
of files in source package but no proper way to handle them thru' Makefile
Created attachment 133478 [details]
Somehow clean SPEC version of original SPEC
Still there are a lot of rpmlint errors. In case you are there you can try to
clean it or i will post silent rpmlint version of SPEC later on
Thank you for review, I will post a better version soon.
Given that 195353 was closed WONTFIX, is there any point in continuing this
The short answer would be "there is a point". I am continuing my work.
A Makefile was added. Meaningful rpmlint errors were fixed. Some other
enhancements were done (see ChangeLog). I expect this snapshot to have little
difference from soon 0.8.4 release.
SRPM URL: http://etcnet.org/files/etcnet-0.8.4-0.test7.src.rpm
The package requires initscripts split. I have updated my initscripts patch to
the 8.39-1 version and set up a repository of initscripts+net-scripts+etcnet here:
Denis: Do you still wish to submit this package?
The URL's in comment #7 all appear to be unreachable. ;(
If this package requires changes to an already existing package to work, and the
maintainer refuses to make those changes I'm not sure there is any reason to
keep this submission around. Does it indeed require those changes?
If I don't hear anything in 1 week I will go ahead and close this submission.
I haven't investigated anything at all, but it seems clear to me
that a new network system shouldn't conflict with what is existing.
Moreover the network is brought up in a separate init.d script so
from a quick glance it seems that using etcnet simply means stopping
network and enabling the corresponding etcnet init script? Ok this
has to be done manually, but this is where to start, real integration
should be done later, when it has proven to be better than the current
In any case I am all for a alternative network system to play
I'd be all for an alternative as well, but the submitter hasn't responded.
I am going to close this review now.
Denis: Feel free to reopen this review request or submit a new one if you would
like to submit this package again.
For those interested in post mortem analysis in Russian (executive summary: blame initscripts maintainer for being unwilling to change it in any way):
<pilot> кроме записанного в этом баге было ещё и обсуждение в IRC
<pilot> тогдашний хозяин пакета initscripts сказал что-то в том роде, что я могу делать что хочу, если только не нужно менять пакет initscripts
<pilot> и ещё желательно initscripts при этом из системы не удалять
<pilot> я ж культурно попросил сетевую часть отделить в net-scripts и её замещать
<pilot> пакеты собрал для наглядности
<pilot> в общем, побился об стену и переключился на работу
<pilot> терпения не хватило, да
Due to other important concerns I'm not up to driving an integration attempt once again. If anyone is motivated to do that on their own, I can provide a couple of hints, but that would be all. /etc/net is now maintained by Sergey Bolshakov.