Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=253630
lexual <lex.lists(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|lex.lists(a)gmail.com |
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Unnecessary Requires - shorewall and tcpwrappers
https://bugzilla.redhat.com/show_bug.cgi?id=781341
Summary: Unnecessary Requires - shorewall and tcpwrappers
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: unspecified
Component: fail2ban
AssignedTo: axel.thimm(a)atrpms.net
ReportedBy: vogel(a)folz.de
QAContact: extras-qa(a)fedoraproject.org
CC: herrold(a)owlriver.com, mattdm(a)mattdm.org,
axel.thimm(a)atrpms.net, tim(a)niemueller.de,
vogel(a)folz.de, jonathan.underwood(a)gmail.com,
ruben(a)rubenkerkhof.com, wdierkes(a)rackspace.com,
triage(a)lists.fedoraproject.org,
maxamillion(a)fedoraproject.org,
voronin.andrey(a)gmail.com,
bugzilla.redhat.com(a)ewood.users.cementhorizon.com
Estimated Hours: 0.0
Classification: Fedora
Story Points: ---
Clone Of: 244275
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
+++ This bug was initially created as a clone of Bug #244275 +++
Description of problem (copied from Bug #244275):
fail2ban doesn't require shorewall to function, and in fact, as we ship it, it
makes use of the Fedora firewall - installing an extra firewall which is the
not
used in the default configuration is a bit gratuitous and confusing to the
user.
Also, the Requires: tcpwrappers isn't needed unless the user decides to enable
the tcpwrapper action (disabled by default)
Additional information:
Bug #244275 contains suggestions and possible patches for a fix, but was closed
with NOTABUG as noted in the comment from the EPEL maintainer:
--- Additional comment from maxamillion(a)fedoraproject.org on 2012-01-12
22:46:49 EST ---
Since this is just the EPEL package and I don't maintain fail2ban for Fedora, I
will be keeping it in line with Fedora proper. Please feel free to discuss this
with the Fedora package maintainer.
As I wrote in some comments in Bug #244275, I'm interested in a fix for Fedora,
which is why I file this bug now.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=126342
--- Comment #61 from Josh Boyer <jwboyer(a)redhat.com> ---
*** Bug 860712 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=126342
Josh Boyer <jwboyer(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |d.okias(a)gmail.com
--- Comment #60 from Josh Boyer <jwboyer(a)redhat.com> ---
*** Bug 860712 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=305431
--- Comment #11 from Fedora Update System <updates(a)fedoraproject.org> ---
valgrind-3.8.1-1.fc18 has been pushed to the Fedora 18 stable repository. If
problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
--- Comment #103 from Mads Kiilerich <mads(a)kiilerich.com> ---
(In reply to comment #101)
This old messy closed-but-resurrected bug is perhaps not the best place to
discuss any specific problem or improvements to the situation in general, but:
I doubt many users would know where to add that --debug option; they just run
rpm/yum/somefancygui and install a new kernel. Even the current error message
would make a lot more sense if the user knew which command was being run.
Some option in /etc/sysconfig/kernel that makes new-kernel-pkg show what it is
doing and turn on debugging would perhaps be a prerequisite for making an
actual improvement.
A remaining problem would be that half of grubby runs in posttrans where all
output is sent to /dev/null. It would perhaps be better to log with syslog.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
--- Comment #102 from Eric Sandeen <esandeen(a)redhat.com> ---
And, if the new info reported doesn't point to a problem with mkinitrd/grubby
but some other problem, and grubby is just the messenger, I'd really suggest
not adding that info to this poor old bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
--- Comment #101 from Eric Sandeen <esandeen(a)redhat.com> ---
Shouldn't this be against the grubby component now?
Also, I had forgotten that as of
* Tue Dec 20 2011 Peter Jones <pjones(a)redhat.com> - 8.7-1
- Add a --debug to try to help diagnose "No suitable template".
(sandeen,pjones)
you guys could try --debug to see what has really gone wrong, and report new
info if it helps.
You'll get such info as:
"marked to skip" or ""no line found" or "line has only %d elements" or ""access
to %s failed" or many others.
It's entirely possible that the failure is due to some system change or
misconfiguration, and not a bug in grubby at all.
Peter, maybe a hint in the standard output would be good:
"No suitable template found; rerun with --debug for more info."
I'll send a patch ;)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
--- Comment #100 from josip(a)icase.edu <jl-icase(a)comcast.net> ---
Grubby must provide enough information to help a Linux administrator identify
the source of the problem. Just giving up with a generic message is
unacceptable because if the problem can't be tracked to a more precise source,
it can't be fixed -- as evidenced by 8+ years of complaints.
I vote to keep this bug open and to FIX the uninformative grubby message(s).
--
You are receiving this mail because:
You are on the CC list for the bug.